From: Joe Peterson <joe@skyrush.com>
To: free_beer_for_all@yahoo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] UTC timestamp option for FAT filesystems
Date: Wed, 25 Jun 2008 22:24:33 -0600 [thread overview]
Message-ID: <48631A01.1020009@skyrush.com> (raw)
In-Reply-To: <943360.32984.qm@web46103.mail.sp1.yahoo.com>
barry bouwsma wrote:
> I think 100% of it refers to GMT+2
> (in my present time zone), so I wonder if in different languages,
> there's a preference for casual use of the phrase GMT (a quick
> look in my dictionary shows an entry for GMT, nothing for UTC,
> but then, it has no entry for `operating system' or its translated
> equivalent.
Well, your question certainly prompted me to go and read up on it again.
In my work (unmanned space missions - solar system stuff), we deal with
many representations of time, and so I am used to being anal about it.
For example, there is GMT, UTC, TDT, ET, etc. They all differ ever so
slightly.
> --- /mnt/usr/local/src/linux-2.6.24/fs/fat/inode.c-DIST 2008-01-30 10:59:19.000000000 +0100
> +++ /mnt/usr/local/src/linux-2.6.24/fs/fat/inode.c 2008-04-13 07:09:10.000000000 +0200
> @@ -826,6 +829,9 @@ static int fat_show_options(struct seq_f
> seq_puts(m, ",showexec");
> if (opts->sys_immutable)
> seq_puts(m, ",sys_immutable");
> +/* XXX HACK */
> + if (opts->utc)
> + seq_puts(m, ",utc");
> if (!isvfat) {
> if (opts->dotsOK)
> seq_puts(m, ",dotsOK=yes");
>
Indeed! Thanks, I'll put this in the patch. The above is actually not
needed for the mount command or /etc/mtab, but it *is* used for, e.g.,
/proc/mounts.
-Joe
next prev parent reply other threads:[~2008-06-26 4:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 13:31 [PATCH] UTC timestamp option for FAT filesystems barry bouwsma
2008-06-25 14:42 ` Joe Peterson
2008-06-25 19:35 ` barry bouwsma
2008-06-26 4:24 ` Joe Peterson [this message]
2008-06-26 19:07 ` barry bouwsma
-- strict thread matches above, loose matches on Subject: below --
2008-06-25 5:24 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
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
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=48631A01.1020009@skyrush.com \
--to=joe@skyrush.com \
--cc=free_beer_for_all@yahoo.com \
--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