From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: barubary@cox.net (Barubary)
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk (Alan Cox)
Subject: Re: ISO9660 bug and loopback driver bug
Date: Tue, 26 Feb 2002 12:37:36 +0000 (GMT) [thread overview]
Message-ID: <E16fgrQ-0000Vo-00@the-village.bc.nu> (raw)
In-Reply-To: <009201c1bebd$7a5f5910$a7eb0544@CX535256D> from "Barubary" at Feb 26, 2002 04:02:34 AM
> Why is it locale-dependent? All ISO9660 file times are stored as Gregorian
> calendar dates regardless of who made them, and the target (UNIX file time)
Thanks - I wasn't aware it was always defined to be the gregorian calendar
in ISO9660. The orthodox calendar differs in computation (its more accurate)
and the two actually diverge in 2800. (Pan Orthodox congress 1923 if anyone
actually cares)
> isn't locale-dependent either. Why would it affect the calculation if the
> local system used the Muslim calendar?
Unix file time is clean of those problems
> Shouldn't there be a gregorian_date_to_unix_time() function in the kernel so
> that every driver that needs such conversion can share that implementation?
> It would keep date processing consistent and make it easy to spot date bugs.
Not a bad idea if there are enough file systems doing it.
prev parent reply other threads:[~2002-02-26 12:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 11:37 ISO9660 bug and loopback driver bug Barubary
2002-02-26 11:54 ` Jesper Juhl
2002-02-26 12:01 ` Rainer Ellinger
2002-02-26 12:08 ` Barubary
2002-02-26 12:17 ` Change that to an NTFS bug not loopback Barubary
2002-02-27 0:03 ` Richard Russon
2002-02-26 12:04 ` ISO9660 bug and loopback driver bug Alan Cox
2002-02-26 12:02 ` Barubary
2002-02-26 12:37 ` Alan Cox [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=E16fgrQ-0000Vo-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=barubary@cox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.