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: Thu, 30 Mar 2006 17:50:45 +0100	[thread overview]
Message-ID: <442C0C65.1060607@proweb.co.uk> (raw)
In-Reply-To: <cbaec0a748afc5e3b6734d03077eeed8@cat-v.org>

 > it duplicates information already in the status file,
 > and it would be the *only* kernel device file in the system
 > that didn't use kerndate as the mtime.  when did the
 > plan 9 approach become "there's more than one way to do it"?

hmm I wonder when the kernel was written to the file system

ls -l /proc

ahh, now I know


 > It's not useless, and it's the same as essentially every other
 > device file in the system.

Then perhaps they convey the wrong information.
Note the "essentially every other". Not "every other".

That means you can't take a devices mtime to be kerndate, which means
making *some* of them have kerndate presents duplicate data that is also
untrustworthy and therefore meaningless and arbitrary.

If we are assigning arbitrary pieces of data as the mtime then why not
the start time of when the process was created and therefore the
creation date of /proc/pid

IMHO the creation time of /proc should be the boot time of the kernel.
Kerndate should be somewhere but it is it really relevant to the current
running state of the system ?


 > If it were different, I would find that confusing.
 > Just because you're confused doesn't mean everyone is.

That is a weak argument against the idea.

And would it really confuse you ?

Surely you would remember this conversation.

The question should surely be on the merit of the idea AND "will the
break any existing code".







  reply	other threads:[~2006-03-30 16:50 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 [this message]
2006-03-30 17:19                 ` Russ Cox
2006-03-31 10:52                   ` matt
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=442C0C65.1060607@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).