I have an embedded board (a PCEngines Wrap board) which has no persistent clock. With earlier configurations I set the clock with ntpdate once the network was up.
But with current sid I have a problem in that fsck in util-linux-ng 2.16 complains that the "Superblock last mount time (Sat Jan 1 00:01:08 2000, now = Sat Jan 1 00:00:49) is in the future". Even if I do an fsck on the machine manually and then reboot, it always fails. I have found some mentions on forums that swapping the order in which init starts up helps, by ensuring that the system clock is set properly, but I can not do that until much later when I have a network. Any ideas as to how to proceed. Is there some way to supress this time check? David -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
