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 read-only adjtime, if you do things right, EVEN when you depend on adjtime to keep your clock working right (which nowadays mostly nobody does, as chrony and ntp have taken over). This was one of the reasons behind the split into hwclockfirst and hwclock initscripts. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
