On Sat, Mar 29, 2008 at 04:53:38PM +0100, Gerhard Brauer wrote:
Maybe a little more technical discussion from those who care?
Ok, i've done another test (at the moment i could reproduce it in virtualbox): I've started the installation on 18:01 localtime (here CET). ,---- | inside the VM: | date | Sat Mar 29 18:01:23 UTC 2008 | hwclock | same time as above date `---- After creating and formatting the disk i have on sda3(=/): ,----[ dumpe2fs -h /dev/sda3 ] | Filesystem created: Sat Mar 29 18:06:04 2008 | Last mount time: Sat Mar 29 18:06:13 2008 | Last write time: Sat Mar 29 18:06:13 2008 | Mount count: 1 | Maximum mount count: 30 | Last checked: Sat Mar 29 18:06:04 2008 | Check interval: 15552000 (6 months) | Next check after: Thu Sep 25 18:06:04 2008 `---- Then i go over configure system, also set the Timezone to Europe/Berlin but leave the HARDWARECLOCK to localtime. Doing this current time in virtual machine is: Sat Mar 29 18:42:23 CET 2008 (only timezone gets changed, not the time itself) And here i think it "happend": ,----[ dumpe2fs -h /dev/sda3 ] | Filesystem created: Sat Mar 29 19:06:04 2008 | Last mount time: Sat Mar 29 19:06:13 2008 | Last write time: Sat Mar 29 19:06:13 2008 | Mount count: 1 | Maximum mount count: 30 | Last checked: Sat Mar 29 19:06:04 2008 | Check interval: 15552000 (6 months) | Next check after: Thu Sep 25 20:06:04 2008 `---- sda3 is still mounted, but the creation time is in the future. The same what fsck found fault with on the next(first) boot. I think the error is to change timezone during install but leave the time itself unchanged. Or something like that, i'm not sure ;-) But i think to ask the user before install: What is your clock set (UTC/localtime) and then *set* the clock (maybe also hwclock) before mkfs could solve this creation times conflicts. Regards Gerhard -- Heute ist das Morgen wovor du gestern Angst hattest...