Moving 'setclock' to earlier in the boot sequence

Dan Nicholson dbn.lists at
Tue May 27 13:17:31 PDT 2008

On Tue, May 27, 2008 at 1:04 PM, Gerard Beekmans
<gerard at> wrote:
>> I think it's always the right thing to get the kernel file systems
>> mounted, modules loaded and devices created as soon as possible. I
>> don't believe the cleanfs issue is important enough to merit wedging
>> the setclock script in front of those steps. I'd personally rather
>> change cleanfs to operate in a different way that's independent of
>> those 3 services.
> Look at it this way as well. If you wanted to keep track of boot logs
> and whatnot with timestamps, they are pretty useless if the time is
> wrong. Of course there's the argument that you then will want to sync
> with an NTP server as well while you're at it.
> However, to at least set the CMOS clock to proper time (with timezone
> conversion if needed), is a step up to get the boot logging a bit more
> accurate.

But syslogd is started well after setclock. Furthermore, /var is not
guaranteed to be writable until after mountfs runs, which is after
setclock, too. So, logging should be fine now and with any of the
proposed changes. Unless you mean something else by boot logging.


More information about the lfs-dev mailing list