From: "Jörg Schummer" <ext-jorg.2.schummer@nokia.com>
To: ext Jamie Lokier <jamie@shareable.org>
Cc: "hirofumi@mail.parknet.co.jp" <hirofumi@mail.parknet.co.jp>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH take 3][RFC] fat: Save FAT root directory timestamps to volume label
Date: Wed, 09 Sep 2009 10:47:47 +0300 [thread overview]
Message-ID: <1252482467.5782.12.camel@jorg-desktop> (raw)
In-Reply-To: <20090908153949.GD5579@shareable.org>
On Tue, 2009-09-08 at 17:39 +0200, ext Jamie Lokier wrote:
> Jorg Schummer wrote:
> > Standard FAT implementations cannot store any of the FAT root directory's
> > timestamps. This commit adds the mount option 'rootts', which allows saving
> > the FAT root directory timestamps as the timestamps of the FAT volume label
> > directory entry. At least Mac OS X is known to support the same mechanism
> > and interoperate with this commit.
> >
> > When mounting, the following values can be specified for the 'rootts' mount
> > option:
> >
> > "rootts=ignore" ignores root directory timestamps. All timestamps are
> > reset to 0 (1/1/1970). This has been the FAT behaviour
> > prior to this patch.
> >
> > "rootts=preserve" tries to load and save the root directory's timestamps
> > if a volume label entry exists. The mtime and atime are
> > corrected based on root directory entries' ctime. This
> > is the default.
> >
> > "rootts=save" tries to load and save the root directory's timestamps.
> > The mtime and atime are corrected based on root
> > directory entries' ctime. If the root directory was
> > accessed but no volume label entry exists, the label
> > "NO NAME" is created.
>
> Does Mac OS X do the same "NO NAME" thing?
AFAIK: No. It only supports the general mechanism of storing / loading
the root dir timestamps to / from the volume label entry.
But feel free to re-check that one.
Jörg
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-09-09 7:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1248274841-3586-1-git-send-email-ext-jorg.2.schummer@nokia.com>
2009-07-24 9:43 ` [PATCH take 2][RFC] fat: Save FAT root directory timestamps to volume label Jorg Schummer
2009-07-25 5:48 ` OGAWA Hirofumi
2009-07-27 10:47 ` Jörg Schummer
2009-07-27 11:47 ` OGAWA Hirofumi
2009-07-27 13:03 ` Jörg Schummer
2009-07-27 14:56 ` Jörg Schummer
2009-07-27 15:10 ` OGAWA Hirofumi
2009-08-04 8:42 ` Jörg Schummer
2009-08-04 10:32 ` OGAWA Hirofumi
2009-09-08 14:28 ` [PATCH take 3][RFC] " Jörg Schummer
2009-09-08 14:34 ` Jorg Schummer
2009-09-08 15:39 ` Jamie Lokier
2009-09-09 7:47 ` Jörg Schummer [this message]
2009-09-15 11:03 ` Jörg Schummer
2009-09-18 11:33 ` OGAWA Hirofumi
2009-09-18 12:14 ` jorg
2009-09-19 14:46 ` OGAWA Hirofumi
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=1252482467.5782.12.camel@jorg-desktop \
--to=ext-jorg.2.schummer@nokia.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).