On Sunday 17 May 2009 03:18:10 Jörg Sommer wrote: > I would much more prefer to get prompted for the correct time, because > with a wrong time fsck fail due to the last fsck is in the future. But I > don't know how to do prompting in init scripts correctly. I did think about this, but didn't go this way for a couple of reasons. . I just want to get the time/date into the correct year so that things like kdm/ gdm will startup. Otherwise the user is presented with a console login which doesn't pass the WAF. I have been asked a number of times by the other half over the phone what does she do when the screen is black and just says $ with a flashing cursor :-( . I have ntpdate set so when the network interface is brought up, we then sync to exact time. Much more precise than asking the user the time. . I don't think you are allowed to block for input with the init.d scripts. That said I can see merit in asking the user the time, especially if you aren't going to connect to the network soon.. > And to guess if the hardware clock is wrong I think we can look at the > installation time of the module directory of the kernel. > /boot/vmlinux-$(uname -r) is possible, too. Yes, I'm surprised that a warning isn't set off if the time is set to the date before the kernel was complied. Mark
Attachment:
signature.asc
Description: This is a digitally signed message part.