[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#159541: acknowledged by developer (closing)



On Mon, 01 Dec 2003 22:35:22 -0600,
owner@bugs.debian.org (Debian Bug Tracking System) wrote:
 > I am putting this bug report down to user error, since noone else has
 > ever reported a problem like it with base-config.

I think I managed to come up with a hypothesis of what was actually
going on there, but I haven't had the misfortune to have to test it :-) 
and so I never got around to following up on this.

I'm speculating that the systems where I was seeing this were dual
boot systems and that Windows got a chance to intervene with the
hardware clock in between the times that Debian gained control over
the machine. This would explain the odd "seesaw" effect -- there's a
FAQ in one of the timekeeping HOWTOs about this.

I had one system which was booting via LOADLIN in Windows 95 and its
clock would be off by one hour each time it came up. This had nothing
with base-config to do, of course, but it sure would be nice if there
was a way to cope with this at least in the situation where the system
is likely to be rebooted at least twice in relatively rapid succession
(first to start the installer, then to finish the install).

I can't come up with any sane way to cope with this so I suppose it's
best to leave this closed (although that violates my sense of order --
a bug which isn't fixed is an open bug, really).

/* era */

-- 
formail -s procmail <http://www.iki.fi/era/spam/ >http://www.euro.cauce.org/
cat | more | cat<http://www.iki.fi/era/unix/award.html>http://www.debian.org/



Reply to: