I've been biten by this issue too. When a PC in basement, which were running for several years has been rebooted (power lost, clean shutdown off UPS) and later it turned out it had bad CMOS battery. Actually it had bad battery for quite some time and I knew it, but it is such a large issue to get to the machine, and before, it required just a few seconds after bootup to set correct time using ntp.
But today it refused to start, asking for the root password because fsck failed on all filesystems. So now I've a question: _why_ fsck wants to know the system time? Why it compares the last-mounted time with current time? Before, it merely warned that the filesystem mount time is in the future and continued, but now it treats this condition as a serious error. Why? I understand that I'll have to set buggy_init_scripts=1 to get past this issue, but I should also remember that this is false statement. If fsck _really_ needs correct time, can we please at least have the real name for this option? Thanks. /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
