About a week ago I dl’ed the live version of Haiku - burned it to a disk then booted it up. After playing with it for a while I quit, and rebooted my machine. I was a little worried to discover during the reboot that
Haiku (which had set the time to something other than local time) had been writing to my HD and that because some of what it had written was dated in the future my system had to do an fschk.
Can anyone tell me why and what Haiku found so important it had to write to my HD. I thought the whole point of a live CD was to NOT have to worry about what’s on the HD while you try out a new system ??
the time had been changed in the bios when you played with Haiku (probably you set it yourself to the correct time), so when you rebooted, the other system read the time from the bios, not on the hard drive.
I don’t think Haiku ever wrote on your hard drive.
Yes, this all sounds timestamp-related, I seriously doubt Haiku touched your disk(s) unless you mounted some FAT and made changes to it.
I’ve seen the same thing happen after changing the time on my machine in another OS and rebooting into Linux (for example, using Windows to change my BIOS time on a dual-boot machine).
The Haiku installer and/or DriveSetup allows you to modify partition tables, and write a new bootsector, but these are certainly not done automatically.
Even mounting ext2/3 would have made no changes since the driver for that is completely readonly.
I have (very) limited Haiku knowledge, but this sounds more like the bios clock being set via the OS, and the other OS reading that info. This happens somtimes when you ‘distrohop’ with Linux, or even dual boot with some OS’s.
if you set the the time to be changed via ntp and ensure you set the correct timezone/locale on each os tried it happens less often.
Jase