Package: util-linux Version: 2.12r-10 Severity: normal
I'm having a minor issue with a small mipsel system which does not have any hardware clock (so it can not keep track of time accross reboots). I set up the system's clock using ntpdate, but that can only happen once the network is up, which only happens after various partitions are mounted. In the mean time I'd like the system to have an approximate idea of time, if only just to have periodic fsck checks work as expected. My proposal would be to add the following in /etc/init.d/hwclockfirst.sh, before the first HWCLOCKACCESS test: if [ "$FIRST" = yes ] && [ -f /var/log/wtmp ] && \ [ `date +%s` -lt `date +%s -r /var/log/wtmp` ]; then date -s "`date -r /var/log/wtmp`" fi The idea is that the date should not be earlier than the last reboot date as taken from /var/log/wtmp, and that we can use that as a good-enough estimate for the purposes of running fsck checks at boot time. It'd be fine too if this was under an additional configuration setting which could be set under /etc/defaults. Versions of packages util-linux depends on: ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries ii libncurses5 5.5-3 Shared libraries for terminal hand ii libslang2 2.0.6-3 The S-Lang programming library - r ii libuuid1 1.39-1 universally unique id library ii lsb-base 3.1-15 Linux Standard Base 3.1 init scrip ii zlib1g 1:1.2.3-13 compression library - runtime Thanks, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]