I have a set of machines that don't have battery backups for the real time clock. when the power is cycled on these machines, the real time clock resets to the BIOS epoch time which is usually a year or two in the past. Each time I boot, I get fsck failure because the superblock time is in the future. I am aware of the e2fsck configuration file that I can put into /etc with the broken_clock option, however I still get log files that have the time set in the past. Having invalid times in the log files can make debugging boot problems very problematic. I have hacked together a dracut ntpd module that will set the time but it requires modifications to the network module to turn on the network even when netroot is not set. I guess I don't really have a question because what I have done seems to work, but I was wondering what others think of this to see if it might be a worthwhile addition to dracut or if I should just keep going with my hacked version. -- To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
