Re: I just updated to main-n261544-cee09bda03c8 based (via source) and now /etc/machine-id and /var/db/machine-id disagree ; more

The 13.1-RELEASE (snapshot) to 13.2-RC3 freebsd-update's
upgrade sequence did not go well relative to my being
prompted to do the right thing to establish /etc/machine-id .
After the last reboot (kernel upgrade, presumably) it had me
continue with. . .

# /usr/sbin/freebsd-update install
src component not installed, skipped
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Installing updates...
install: ///var/db/etcupdate/current/etc/rc.d/growfs_fstab: No such file or directory
install: ///var/db/etcupdate/current/etc/rc.d/var_run: No such file or directory
install: ///var/db/etcupdate/current/etc/rc.d/zpoolreguid: No such file or directory
Scanning //usr/share/certs/blacklisted for certificates...
Scanning //usr/share/certs/trusted for certificates...
rmdir: ///usr/tests/usr.bin/timeout: Directory not empty
 done.
root@generic:~ # cat /etc/hostid /etc/mach*
cat: No match.

It did not indicate the need for another reboot to
end up with a /etc/machine-id file.

I tried "shutdown -r now" anyway. It did establish
an /etc/machine-id file during the reboot:

# ls  -Tld /etc/hostid /etc/machine-id 
-rw-r--r--  1 root  wheel  37 May 12 08:46:21 2022 /etc/hostid
-rw-r--r--  1 root  wheel  33 May 13 09:46:56 2022 /etc/machine-id

So the basic implementation is operational but just
lacks an indication of the need to reboot again.

The date/time is because it is a RPi4B context (no
time of its own) and time is not automatically being
established via ntp, apparently. (I did not make such
adjustments to the snapshot before starting the
upgrade.)

I do not know if any of the "install: ///var/db/etcupdate/ . . . "
lines or the rmdir line are important.

It earlier indicated 5708 patches were fetched and that 377
files were as well.

===
Mark Millard
marklmi at yahoo.com