From: Joe Peterson <joe@skyrush.com>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] UTC timestamp option for FAT filesystems
Date: Thu, 26 Jun 2008 11:06:17 -0600 [thread overview]
Message-ID: <4863CC89.9070705@skyrush.com> (raw)
In-Reply-To: <87zlp8w4br.fsf@devron.myhome.or.jp>
OGAWA Hirofumi wrote:
> I think we agreed to fix sys_tz is good thing.
Yep, but doesn't have to be fixed before adding a new option, since they
are separate issues and uses, I think.
> If so, I'd like to see "tz=xxx" or something for the future, instead of
> "utc", don't you think so? I really hate to add the random options.
Can you help be to understand what "tz=xxx" (if not =0) would be good
for? It seems to me that either you want the "local time" functionality
(which deals, to a degree, with DST, in which case you use the existing
behavior) or you use tz=0 (which is the same as utc).
If someone were to, say, set "tz=-7", it would not work correctly with a
camera or with a Windows-written volume.
For a camera, since DST is not taken into account. If you really want
to set your camera to local time and are willing to accept the inherent
issues, why not just use local time FAT behavior as it is now in Linux.
If you are talking about using a Windows FAT partition in a different
time zone, setting tz=xxx would not help either, since all files are
just written in local time whichever time zone the person was in (the
traveling laptop example). Again, the only solution in that case is to
use the default local time behavior.
So, which cases benefit from tz=xxx that would not benefit from utc
(which is eseentially tz=0)?
-Joe
next prev parent reply other threads:[~2008-06-26 18:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 5:24 [PATCH] UTC timestamp option for FAT filesystems Joe Peterson
2008-06-25 22:33 ` Andi Kleen
2008-06-25 23:56 ` Joe Peterson
2008-06-26 2:44 ` Joe Peterson
2008-06-26 7:32 ` OGAWA Hirofumi
2008-06-26 13:23 ` Joe Peterson
2008-06-26 14:37 ` OGAWA Hirofumi
2008-06-26 15:45 ` Joe Peterson
2008-06-26 16:26 ` OGAWA Hirofumi
2008-06-26 17:06 ` Joe Peterson [this message]
2008-06-28 22:24 ` James Cloos
2008-06-29 5:03 ` Joe Peterson
2008-06-29 8:20 ` Bernd Eckenfels
2008-06-26 17:21 ` Joe Peterson
2008-06-26 18:15 ` OGAWA Hirofumi
2008-06-27 5:12 ` Joe Peterson
2008-07-01 23:25 ` Andrew Morton
2008-07-02 4:43 ` Joe Peterson
2008-07-01 23:27 ` Andrew Morton
2008-07-02 14:47 ` Joe Peterson
2008-06-26 16:01 ` Joe Peterson
2008-06-26 17:08 ` OGAWA Hirofumi
-- strict thread matches above, loose matches on Subject: below --
2008-06-25 13:31 barry bouwsma
2008-06-25 14:42 ` Joe Peterson
2008-06-25 19:35 ` barry bouwsma
2008-06-26 4:24 ` Joe Peterson
2008-06-26 19:07 ` barry bouwsma
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=4863CC89.9070705@skyrush.com \
--to=joe@skyrush.com \
--cc=andi@firstfloor.org \
--cc=hirofumi@mail.parknet.co.jp \
--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