-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2007-01-20 at 20:12 -0600, Greg Wallace wrote:
local based (I never adjusted the hardware clock).
No, but your linux will do that for you behind your back :-p
Ok. I checked my BIOS clock and it had indeed been advanced 6 hours to show UTC. Still don't see how that fixed the fsck problem, but it is working and, as you say, that's all that matters.
Right :-) Possibly the fsck routine was using the cmos clock to know the current time. Yeah, that's it. Look: nimrodel:~ # ls /etc/init.d/boot.d/*localfs /etc/init.d/boot.d/*clock /etc/init.d/boot.d/K18boot.clock /etc/init.d/boot.d/S07boot.localfs /etc/init.d/boot.d/K19boot.localfs /etc/init.d/boot.d/S08boot.clock The S07boot.localfs executes before /etc/init.d/boot.d/S08boot.clock, meaning that the fsck program runs before the system clock is properly set up. ( See how nice is an small email, trimmed to the point? ;-) ) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFs9N+tTMYHG2NR9URAoBCAJ93vbVTaN+LfkrqaXhKk6+tr2KarQCfQvSd Czkd/WXlbAgpfgZS1ij0uMM= =LmRa -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org