Bug#342887: hwclock.sh runs too late

2006-10-31 Thread Sven Joachim
Michael Biebl writes: > As /etc/localtime is a copy and not a symlink anymore, hwclock.sh could > be started even earlier than S11. The only requirement I see is S03udev > (because of /dev/rtc). So the earliest possible time would be S04. As > Thomas pointed out earlier, it should also be started

Bug#342887: hwclock.sh runs too late

2006-10-31 Thread Henrique de Moraes Holschuh
On Tue, 31 Oct 2006, Sven Joachim wrote: > In this case, hwclock.sh cannot write to /etc/adjtime because the root > filesystem is still mounted read-only. Currently hwclock.sh creates > /etc/adjtime if it doesn't exist, but that might not be necessary, I don't > know. hwclock can cope well with r

Bug#342887: hwclock.sh runs too late

2006-10-31 Thread Michael Biebl
I also had to discover, that running hwclock.sh that late (S50) causes some very strange behaviour. See bug #396137 as a reference. In short, it kills the roaming mode of wpasupplicant, because networking is started at 40 and hwclock afterwards at 50. I have to agree, that hwclock.sh has to be run

Bug#342887: hwclock.sh runs too late

2006-10-31 Thread Michael Biebl
As /etc/localtime is a copy and not a symlink anymore, hwclock.sh could be started even earlier than S11. The only requirement I see is S03udev (because of /dev/rtc). So the earliest possible time would be S04. As Thomas pointed out earlier, it should also be started before S10checkroot.sh. So som

Bug#342887: hwclock.sh runs too late, files have incorrect timestamps

2006-10-27 Thread Sven Joachim
reopen 342887 thanks Quoting /usr/share/doc/util-linux/changelog.Debian.gz: , | * drop hwclockfirst.sh, and put hwclock.sh back at 50. See #50572 and | Closes: #342887 ` Ahem, shouldn't hwclock.sh be run as early as possible, not as late as possible?! I have UTC=no and several fi