Package: e2fsprogs Version: 1.38+1.39-WIP-2005.12.10-1 Followup-For: Bug #343662
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The trick about moving the symbolic link in /etc/rcS indeed works, but only if moved to somewhere WAY early in the boot process. In my case, this meant moving to S03hwclockfirst.sh instead, giving me this rcS: README S30procps.sh S43portmap S01glibc.sh S35mountall.sh S45mountnfs.sh S02mountvirtfs S36discover S48console-screen.sh S03hwclockfirst.sh S36mountvirtfs S50hwclock.sh S04udev S36udev-mtab S51ntpdate S05bootlogd S37setkey S55bootmisc.sh S05initrd-tools.sh S38pppd-dns S55urandom S05keymap.sh S39dns-clean S70nviboot S10checkroot.sh S39ifupdown S70x11-common S18ifupdown-clean S40hostname.sh S71xserver-xorg S20module-init-tools S40hotplug S75sudo S20modutils S40networking S30checkfs.sh S41hotplug-net Btw, the problem also affects systems where /etc/default/rcS has UTC=yes (such as this PPC workstation). I'd also like to point out that S22 is valid for fresh Sarge installs, but Woody installs had S18 instead (God knows what default Potato had). Thus, given how critical the position of this symbolic link is, it might be a good idea for the postinst script to call update-rc.d to delete all current symbolic links for hwclockfirst.sh and to upgrade them. This of course means cloning this bug and assigning it to 'util-linux' as well. Finally, I'd like to remind you that this fixed 'e2fsprogs' cannot go into Testing unless you explicitely ask the Release Manager to unfreeze it. PS: Wouldn't now be a good time to review the boot order of ALL packages with priority Standard or higher, before we enter the Etch base freeze? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDw9wHeXr56x4Muc0RAs0rAKCrk5N7ZQKsUaBXsVTBmJbxA6D2tgCbBTPX /TgpyWpFiI6pJhQnq954KH0= =mRgu -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
