[systemd-devel] systemd-journald.service failed to start with systemd v189
lennart at poettering.net
Mon Sep 24 13:27:19 PDT 2012
On Mon, 24.09.12 17:04, Nicolas Aguirre (aguirre.nicolas at gmail.com) wrote:
> To fix my problem, i will create a service which will mount the fs in
> rw, create the /etc/machine-id and remount fs in ro if the machine-id
> is not found. It should work in my case because i'm using ubifs, but
> how to fix such problem in case of squashfs for example ?
/etc/machine-id really needs to exist. Either as a valid file or as an
empty file we can over-mount with something randomly generated at
boot. Also see machine-id(5) for more information about this.
We probably should make PID 1 refuse boot-up entirely if the file is not
around, so that this is not that difficult to debug and stumble over.
Lennart Poettering - Red Hat, Inc.
More information about the systemd-devel