Alexander Graf wrote: > > > On 20/03/2017 16:11, Eric Curtin wrote: >> Yeah "iburst" was all that this needed. It's perfect for my needs at >> least. Haven't seen anything like that in my dracut scripts either. >> Similar to Per, I may not be looking for the right thing. > > I can't find it anymore either. Odd. > > So historically we used to have a hack that set the system time to the > initrd build time if it was bogus: > >https://github.com/openSUSE/mkinitrd/blob/ad190ad24a9f3881afa11c47aecc8625b286d0d4/scripts/boot-start.sh#L210 > > That got removed with the transition to dracut and I seem to remember > that the hack we then added was to take the last mounted time from > your / file system and apply that as system time. But I agree that I > can't find any reference to it. > > I'm surprised any of the non-RTC ARM systems boot at all then - ext3 > used to complain really loudly if the last mount time was newer than > the system time.
I've just had to reboot my nanopi, it came up with "2017-01-10 11:53:57". In dmesg, the built-in rtc reports [ 6.965339] sun6i-rtc 1f00000.rtc: setting system clock to 1970-01-01 00:00:13 UTC (13) Looking at the root file system: # tune2fs -l /dev/mmcblk0p2 tune2fs 1.43.3 (04-Sep-2016) Filesystem volume name: ROOT Last mounted on: / [snip] Filesystem created: Thu Jan 19 04:00:24 2017 Last mount time: Tue Jan 10 11:54:03 2017 Last write time: Tue Jan 10 11:53:59 2017 Mount count: 57 Maximum mount count: -1 Last checked: Tue Mar 7 21:59:21 2017 So, something did set the time? I mean, that timestamp from 2017/01/10 must come from somewhere? -- Per Jessen, Zürich (5.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
