From: arisawa <arisawa@ar.aichi-u.ac.jp>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] curious mtime of cwfs
Date: Sun, 3 Mar 2013 12:30:16 +0900 [thread overview]
Message-ID: <23C5BBD0-CF9F-40EE-A962-5B1EE2617A4D@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <63188117309934af43024565d042f5a6@coraid.com>
Hell erik,
Thanks for your attention.
I looked old Plan 9 manual ver.2.
The quoted portion of stat(5) is not changed since that time.
Plan 9 does not have ctime.
If the directory mtime is not updated in changing wstat info,
It will be bothersome to detect changes in permission etc since given time.
And in addition, if cwfs works same as manual, we can quickly get correct info of changes in each dump.
Kenji Arisawa
On 2013/03/03, at 6:08, erik quanstrom <quanstro@labs.coraid.com> wrote:
>> From stat(5):
>>
>> For a plain file, mtime is the time of the most recent
>> create, open with truncation, or write; for a directory
>> it is the time of the most recent remove, create, or
>> wstat of a file in the directory.
>
> does this apply to synthetic file servers as well? does any
> one know the reasoning behind this change? at first
> glance, it seems like a relatively large impact considering
> the potential gain.
>
> - erik
>
prev parent reply other threads:[~2013-03-03 3:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 1:04 arisawa
2013-02-25 1:17 ` arisawa
2013-02-25 5:55 ` cinap_lenrek
2013-02-25 7:24 ` arisawa
2013-02-25 8:23 ` cinap_lenrek
2013-02-25 10:17 ` arisawa
2013-02-25 10:34 ` Anthony Martin
2013-02-25 11:27 ` cinap_lenrek
2013-02-25 11:39 ` arisawa
2013-03-02 21:08 ` erik quanstrom
2013-03-03 3:30 ` arisawa [this message]
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=23C5BBD0-CF9F-40EE-A962-5B1EE2617A4D@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--cc=9fans@9fans.net \
/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).