Hi,
I'm a bit confused about syspatch and kernel updates. One of machines after
latest syspatch (009) and after reboot it lists old kernel date.
This happens only on this machine. I've seen it happen before, not sure if it
was on the same one or some other box.
machine1:
# syspatch -l
001_xserver
002_syspatch
003_portsmash
004_lockf
005_perl
006_uipc
007_smtpd
008_qcow2
009_recvwait
# uname -prsv
OpenBSD 6.4 GENERIC.MP#364 amd64
# sysctl kern.version
kern.version=OpenBSD 6.4 (GENERIC.MP) #364: Thu Oct 11 13:30:23 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
machine2:
# syspatch -l
001_xserver
002_syspatch
003_portsmash
004_lockf
005_perl
006_uipc
007_smtpd
008_qcow2
009_recvwait
# uname -prsv
OpenBSD 6.4 GENERIC.MP#2 amd64
# sysctl kern.version
kern.version=OpenBSD 6.4 (GENERIC.MP) #2: Tue Dec 18 13:17:16 CET 2018
r...@syspatch-64-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
on machine1 relink.log seems fine:
# cat /usr/share/relink/kernel/GENERIC.MP/relink.log
(SHA256) /bsd: OK
LD="ld" sh makegap.sh 0xcccccccc
ld -T ld.script -X --warn-common -nopie -o newbsd ${SYSTEM_HEAD} vers.o ${OBJS}
text data bss dec hex
10495948 2796320 671744 13964012 d512ec
mv newbsd newbsd.gdb
ctfstrip -S -o newbsd newbsd.gdb
mv -f newbsd bsd
umask 077 && cp bsd /nbsd && mv /nbsd /bsd && sha256 -h /var/db/kernel.SHA256
/bsd
Kernel has been relinked and is active on next reboot.
SHA256 (/bsd) = 8b216c359324a4a938bd35c2c97416b62ffec8c8b955f8b86d65ddf9dc0d71b1
Also /bsd has newer date so it seems updated.
# ls -ld /bsd
-rwx------ 1 root wheel 15461926 Dec 19 10:04 /bsd*
# ls -ld /usr/share/relink/kernel/GENERIC.MP/relink.log
-rw-r--r-- 1 root wheel 486 Dec 19 10:04
/usr/share/relink/kernel/GENERIC.MP/relink.log
can someone explain this?
thanks
G
