Time stamp during the boot sequence

[kt53]

Greetings:

I have a dual boot laptop with W10H/CentOS 7.4.1708 (Core). After set up, it became clear that the evil corporation (M$) is messing the time for Linux. Since M$ cannot stop its meddling, I let the CentOS get the time from the hardware clock. I have used either of these two options below:

hwclock --systohc --localtime
or
timedatectl set-local-rtc 1 --adjust-system-clock

Reading and learning from other forum posts, I checked the boot sequence:

$ journalctl -k
-- Logs begin at Wed 2018-03-07 14:48:09 EST, end at Wed 2018-03-07 20:00:20 EST. --
Mar 07 14:48:09 euler kernel: microcode: microcode updated early to revision 0xba, date = 2017-04-09
Mar 07 14:48:09 euler kernel: Initializing cgroup subsys cpuset
Mar 07 14:48:09 euler kernel: Initializing cgroup subsys cpu
Mar 07 14:48:09 euler kernel: Initializing cgroup subsys cpuacct
Mar 07 14:48:09 euler kernel: Linux version 3.10.0-693.17.1.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ) #1 SMP Thu Jan 25 20:13:58 UTC 2018
Mar 07 14:48:09 euler kernel: Command line: BOOT_IMAGE=/vmlinuz-3.10.0-693.17.1.el7.x86_64 root=UUID=38d0b7ee-d294-4561-96f2-af0c306a1ec7 ro LANG=en_US.utf8
Mar 07 14:48:09 euler kernel: e820: BIOS-provided physical RAM map:
'
'
Mar 07 14:48:11 euler kernel: usb 1-11: new full-speed USB device number 5 using xhci_hcd
Mar 07 14:48:11 euler kernel: usb 1-11: New USB device found, idVendor=8087, idProduct=0a2b
Mar 07 14:48:11 euler kernel: usb 1-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Mar 07 14:48:11 euler kernel: EXT4-fs (sdb4): mounted filesystem with ordered data mode. Opts: (null)
Mar 07 19:48:12 euler systemd-journald[133]: Received SIGTERM from PID 1 (systemd).
Mar 07 19:48:12 euler kernel: type=1404 audit(1520452091.769:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
Mar 07 19:48:12 euler kernel: SELinux: 2048 avtab hash slots, 106006 rules.
'
'
Mar 07 19:48:33 euler kernel: Bluetooth: RFCOMM TTY layer initialized
Mar 07 19:48:33 euler kernel: Bluetooth: RFCOMM socket layer initialized
Mar 07 19:48:33 euler kernel: Bluetooth: RFCOMM ver 1.11
Mar 07 19:49:35 euler kernel: TCP: lp registered
$

It appears that boot sequence time starts 5 hours behind and after 3 seconds shows the correct time. My questions are:

Is this normal?
is there a better way of setting up the Linux time?

Thanks,
KT

[hunter86_bg]

Actually, you can tell windows to stop messing with the clock.
Here is a short howto, but it depends which OS will be running more often.
I've modified my Win, as I use it rarely (win internet time should be off).
Which one will you use most often?

[kt53]

I am aware of the windows registry hack, but my search (over two years ago) showed that it was unreliable and would not survive a major update. However, your link also includes the hack for a 64 bit system that could be a "permanent" fix.

I mostly use Linux. Has your fix on your system been reliable?

[kt53]

I have an older machines that was dual-booted with XP/OpenSUSE. XP is immune to M$ time shenanigans and both OS's showed the correct time. I replaced the OpenSUSE with Fedora 27 and checked the journalctl.

Fedora also starts the boot sequence time stamp 5 hours behind and about 6 seconds later (slower machine) shows the correct time. So, there must be some logic here that I am missing.
___________________________
PS. Blivet-gui is very nice.
PPS. Fedora 27 WS is bloated.

[MartinR]

Is that a case of switching between GMT and EST?

[hunter86_bg]

I am aware of the windows registry hack, but my search (over two years ago) showed that it was unreliable and would not survive a major update. However, your link also includes the hack for a 64 bit system that could be a "permanent" fix.

I mostly use Linux. Has your fix on your system been reliable?

Never had a problem with that, but my system has Win7 which is not so "smart"... You should try both methods and pick the most suitable to you.