Bug#84439: base: System Clock set too late (problems when HW Clock in local time)
At boot up, the system clock is set by the kernel from the HW clock.
If HW clock is in local time, that means: since boot up,
and until init.d/hwclock.sh is started, the system clock is
E.g. init.d/modutils is started *before* hwclock.sh. When it
calculates module dependencies, the modules.dep file gets a bad
timestamp, eventually (*) sooner than /etc/modules.conf timestamp.
So /sbin/modprobe keeps complaining that we have modified
(*) if you are to the west from GMT, and you have changed
Of course, you can imagine other kind of problems.
Proposed solution: start init.d/hwclock.sh as the very first moment
(I made a symlink of it as rcS.d/S00hwclock.sh).
-- System Information
Debian Release: 2.2
Kernel Version: Linux yup 2.2.12 #1 Sun Dec 3 22:49:21 UYT 2000 i586 unknown