Thanks.
So at boot, one would run "erase-machine-id". Then create a random 30-character hexadecimal number. And then either set "the systemd.machine_id= kernel command line parameter" to it. Or pass it via "the option --machine-id= to systemd".
No.
% system-control cat machine-id
start:#!/bin/nosh
start:true
stop:#!/bin/nosh
stop:envdir env
stop:erase-machine-id
run:#!/bin/nosh
run:#Set up and tear down the machine ID
run:envdir env
run:setup-machine-id
restart:#!/bin/sh
restart:exec false # ignore script arguments
%OK, thanks.
So "setup-machine-id". Does that generate a value that's unrelated to any preexisting versions, analogs, etc?
I ask because, when I deleted /etc/machine-id and ran "systemd-machine-id-setup", it generated a new machine-id by copying the D-Bus machine ID.
Machine IDs are stored in several places, some of which are not even files.
* http://jdebp.uk./Softwares/nosh/guide/commands/machine-id.xm...
They can be resurrected if not all storage locations are dealt with. Moreover, some systems use things like the SMBIOS product UUID.
* http://jdebp.uk./Softwares/nosh/guide/commands/setup-machine...
The correct approach is not deleting files.
* http://jdebp.uk./Softwares/nosh/guide/commands/erase-machine...
* https://lists.debian.org/debian-user/2019/03/msg00550.html