On 21/03/2017 09:52, Per Jessen wrote:
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.
Sounds like a pretty good idea.
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.
AFAICT, my nanopi neo air does have an RTC, but it still comes up with
clock set to 1970 <something> on boot.
There's a separate RTC module on sale as far as I can tell, but nothing
built in.
You can usually tell quite easily whether you have a working RTC by
searching for a battery on the board. No battery means no working RTC,
as there's nothing that would preserve the time while it's not plugged in.
Alex
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
