3 ms·

I'll test that. Edit: OK, so I created a Debian VM, noted /etc/machine-id, deleted it, and rebooted. And found that it was still missing. Running systemd-mach

I'll test that. Edit: OK, so I created a Debian VM, noted /etc/machine-id, deleted it, and rebooted. And found that it was still missing. Running systemd-machine-id-setup generated a new machine-id from the D-Bus machine ID. And it was the same as the initial one. But I also see in man machine-id: > The machine-id may also be set, for example when network booting, by setting the systemd.machine_id= kernel command line parameter or passing the option --machine-id= to systemd. A machine-id may not be set to all zeros.

patrickg_zill 8y ago
Does something like dd if=/dev/urandom bs=1 count=16 | hexdump Give you something that you can use?
- mirimir 8y ago
  Well, the machine-id of that Debian VM was ... 38d05397c25548b4f4bda7751b5062 ... and ... $ FOO=`cat /dev/urandom | tr -dc a-z0-9 | head -c${1:-30}` $ echo $FOO 6we4gvnmx00w208ffty6i11m82rw6d But I have no clue whether systemd would be happy with that. Maybe later I can test more. Edit: Oops. Make that ... $ FOO=`cat /dev/urandom | tr -dc abcdef0-9 | head -c${1:-30}` $ echo $FOO b486935dbb9e9fe603328a19e2b5b4
  - deleted 8y ago
    [deleted]
  - justinclift 8y ago
    Maybe use pwgen? Something like: $ pwgen -1s 31 qHfKU46H2RA2WUr0EZ1zBHfIBLKZKuT
    - mirimir 8y ago
      I think that it needs to be hexadecimal. But not sure.
      - justinclift 8y ago
        No worries. :)