On Fri, 03.10.14 07:07, Jan Synacek (jsyna...@redhat.com) wrote: > >> Now I was determined to fix this bug, however I'm left clueless as to > >> how this is actually supposed to work. Is the entire logic in this piece > >> of code wrong, or am I missing something? How is the > >> (re)generating/mounting of machine-id supposed to work? > > > > I am pretty sure we *should* fail to boot if /etc/machine-id cannot be > > initialized because the root dir is read-only. However, we probably > > should print a good messages in this case, explaining the rationale. > > Thanks for the explanation! And yes, "Cannot open %s" isn't that helpful > in this case.
I'd be delighted to take a patch for this! ;-) Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
