**** BEGIN LOGGING AT Tue Dec 29 02:59:57 2020
Dec 29 22:00:10 <flying_sausages> lol anyone know why this is like this? `stat /proc` https://termbin.com/ydpc
Dec 29 22:01:55 <ogra> how do you mean ?
Dec 29 22:02:39 <ogra> (proc is a virtual filesystem)
Dec 29 22:02:44 <flying_sausages> `/proc` should be created on boot though
Dec 29 22:02:52 <ogra> it does ...
Dec 29 22:03:00 <ogra> obviously even before your clock is set
Dec 29 22:03:01 <flying_sausages> the time created should be the boot time like it is on amd64
Dec 29 22:03:17 <ogra> if you solder an RTC onto your board you will have that 😛
Dec 29 22:03:33 <ogra> else it is the epoch until the clock is set
Dec 29 22:03:43 <flying_sausages> this is in a VM
Dec 29 22:03:52 <flying_sausages> clock should be available, no?
Dec 29 22:03:58 <ogra> dunno
Dec 29 22:05:19 <ogra> if you have defined an rt device in your VM config it surely should ... else it will sync the clock either when the network comes online or if you have the "fixrtc" kernel cmdline option set, it will set the clock to the last mount time of the rootfs from the initrd
Dec 29 22:05:57 <ogra> but proc gets created way before the initrd scripts run ... so unless your kernel inits the RTC on its own the clock wont be set at that time
Dec 29 22:31:14 <flying_sausages> I wonder if the issue is in Parallels or lower  https://ssg.land/irc/uploads/b511d0df7af86033/image.png
Dec 29 22:31:27 <flying_sausages> I know it's an issue on RPi3s too
Dec 29 22:33:38 <ogra> it happens on all pi's but it isnt "an issue"
Dec 29 22:34:15 <ogra> clocks are set eventually (eiher by fixrtc or from the network)
Dec 29 22:34:48 <ogra> apart from some odd timestamps in logs there should be no issues with that
**** ENDING LOGGING AT Wed Dec 30 02:59:57 2020