> I'm surprised the root filesystem is read-only at the point where
systemd starts. Isn't it remounted rw by the initramfs? (It is in
Debian.)
No, it shouldn't; Usually grub passes the "ro" option in which case
initramfs should leave it as readonly (see /usr/share/initramfs-
tools/init). rw mounti
Simon,
Also, I just tested with an empty /etc/machine-id file... in this case,
systemd does correctly create a write a random machine-id.
Which kinda makes me wonder if systemd is erroneously concluding the
rootfs is mounted read-write when the /etc/machine-id file is missing
altogether.
--
Yo
Simon,
I've never really dug into initramfs-tools enough to know for sure, but
my guess has always been that the rootfs got remounted based on what's
in /etc/fstab, which as far as I know is handled by systemd. But perhaps
the initramfs remounts the rootfs read-write, and then it is remounted a
3r
I'm surprised the root filesystem is read-only at the point where
systemd starts. Isn't it remounted rw by the initramfs? (It is in
Debian.)
>From context on lp:1508697 you're using some sort of "golden image"
creation process: install once, delete unique IDs and other transient
state, then dd the
** Description changed:
If /etc/machine-id is missing at boot, systemd does not create it.
I came across lp:1387090 in which Martin Pitt mentions that it should be
created if missing, but is unsure why this doesn't work.
I'm likewise unsure why it doesn't work, but this bit from dmes
