Re: kernel 2027

"Arkady V.Belousov" <[email protected]> Sun, 10 Nov 2002 09:17:57 +0300 (MSK)
Newsgroups gmane.os.freedos.devel
Message-ID <[email protected]>
X-Comment-To: Bart Oldeman

Hi!

10-Ноя-2002 00:49 [email protected] (Bart Oldeman) wrote to
[email protected]:

>>      ? Why you think that in this guilty PKUNZIP? AFAIR, .ZIP format not
>> contains TZ info, which will[n't] be applied at unzipping time.
BO> It does, IF you zip using INFO-ZIP and unzip using INFO-ZIP -- the zip has
BO> this info in extra fields that PKUNZIP doesn't know about. This is done

     Which one UNZIP I should test/use? Precise URL, please. And it
shouldn't require DOS extenders.

BO> precisely because of the problem you see: portability between timezones
BO> and OSes.

     See the difference: in many (most? all?) cases file time should be
unchanged and unaffected by TZ. If you wrote file at 13:25, then your
moving into other TZ doesn't mean that file's writting time changes, it
anyway was written at 13:25 (but in other TZ, though).

     If you need to know in which TZ file was written, then FS, archiver,
etc. sholud keep TZ info near to file time, but not change time itself!

BO> PKUNZIP simply doesn't care because it thinks that local times
BO> don't change when you move.

     And this is good point. Your subjective time not changed. If you love
to write texts between 13:00 and 14:00, then moving into another TZ not
changes this - you will continue to work between 13:00 and 14:00.

BO> Now my FD-kernel copy is on a Linux ext3 filesystem and contains local
BO> times in EST now. When I moved to the US all these times were shifted --
BO> because internally there are stored using UTC and externally displayed
BO> using the local time.

     How bad. :( Why I should count my time relative GMT (AFAIK, UTC=GMT)?
Why time of my files should be changed when I move into another TZ? Imagine:
I make file, then move into neighboring city (in different TZ), then show my
boss that I make this file at given time... ups, time automagically
unexpectedly shifted...

     I.e. should be stored local time (with optional information for which
TZ it local), not some abstract (Universal=Greenwich, why not Galactic?
Universe?) time with correction for reality info...

>> This is your (as archive creator) task to place files into archive with
>> unchanged attributes.
BO> For me, whether I do unzip -l ke2026bsrc.zip or unzip -l ke2027src.zip I
BO> get the same timestamps. That you don't is your problem, not mine (except
BO> for the NLS stuff though, that I cannot explain).