On Thu, Sep 10, 2009 at 10:57:54PM +0200, Stephan Kulow wrote: > > The work flow is as such: > - boot into live cd, live cd thinks system is UTC, mounts sda1 (ro) > at 9am, umounts cleanly, updates mount time to 11am (hardware clock) That doesn't make any sense. The mount time is only set if the filesystem is mounted read/write. So if you only mounted the filesystem read/only, the mount time wouldn't be changed. Watch: # dumpe2fs -h /dev/closure/test | grep time: dumpe2fs 1.41.9 (22-Aug-2009) Last mount time: Tue Sep 1 00:00:00 2009 Last write time: Tue Sep 1 00:00:00 2009 # mount -t ext3 -o ro /dev/closure/test /mnt # umount /mnt # dumpe2fs -h /dev/closure/test | grep time: dumpe2fs 1.41.9 (22-Aug-2009) Last mount time: Tue Sep 1 00:00:00 2009 Last write time: Tue Sep 1 00:00:00 2009 # mount -t ext4 -o ro /dev/closure/test /mnt # umount /mnt # dumpe2fs -h /dev/closure/test | grep time: dumpe2fs 1.41.9 (22-Aug-2009) Last mount time: Tue Sep 1 00:00:00 2009 Last write time: Tue Sep 1 00:00:00 2009 # date Thu Sep 10 20:51:48 EDT 2009 See? Now, if the Live CD is going to be repairing a filesystem, it should mount the root filesystem read/only, extract the time zone, fix the system clock, and only then mount the filesystem read/write. Or the Live CD should fix the system clock over the network before it tries mounting any hard drives. The point is, there are ways for the Live CD to do the right thing. If it's not willing to do that, then its init scripts are buggy. :-) - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
