9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: matt <mattmobile@proweb.co.uk>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: patch/list sorry/proc-mtime
Date: Fri, 31 Mar 2006 11:52:07 +0100	[thread overview]
Message-ID: <442D09D7.1070709@proweb.co.uk> (raw)
In-Reply-To: <22bde5614000d885106987413c69bb88@swtch.com>


> Maybe in someone else's humble opinion the modification time
> (there is no creation time in Plan 9) of /proc should be the time of
> the last call to fork or exits, i.e. the last time the directory actually
> changed.  There isn't an obvious value here.
>
> Overloading mtime for all these purposes
> is misguided, as none of them are actually modification times.


Sure, I don't disagree that there are any number of "good" values one
could pop into the mtime & atime. That's the point of discussing it,
"what do people think should go in the mtime & atime"

On FreeBSD they are both the current system time for /proc

My thoughts, but no action, on the subject is that it is perhaps the
concept of mtime and atime that are wrong. They seem to be terms welded
to a disk based system.

If there are plenty of values that *could* be available, shouldn't we be
open to finding a way to expose them ?





  reply	other threads:[~2006-03-31 10:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <dfb566242e58a31d6d4f97b379b4f487@plan9.bell-labs.com>
2006-03-29 23:07 ` uriel
2006-03-29 23:34   ` Russ Cox
2006-03-30  0:13   ` quanstro
2006-03-29 23:34     ` Federico G. Benavento
2006-03-30  8:31   ` Charles Forsyth
2006-03-30 10:09     ` lucio
2006-03-30 11:33     ` Gabriel Diaz
2006-03-30 13:42       ` Anthony Sorace
2006-03-30 14:17         ` Russ Cox
2006-03-30 14:52           ` Gorka guardiola
2006-03-30 16:22             ` uriel
2006-03-30 16:50               ` matt
2006-03-30 17:19                 ` Russ Cox
2006-03-31 10:52                   ` matt [this message]
2006-03-30 17:24         ` rog
2006-03-30 17:32           ` uriel
2006-03-30 16:37 Fco. J. Ballesteros

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=442D09D7.1070709@proweb.co.uk \
    --to=mattmobile@proweb.co.uk \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).