On Thu, 12.09.13 14:37, Olivier Brunel (j...@jjacky.com) wrote:
> Can help since the journal requires /etc/machine-id to exists in order to
> start,
> and will simply silently exit when it does not.
> ---
> Not sure if the behavior is known/expected or a bug, but when e.g. booting a
> system with
On Thu, 12.09.13 14:37, Olivier Brunel (j...@jjacky.com) wrote:
> Can help since the journal requires /etc/machine-id to exists in order to
> start,
> and will simply silently exit when it does not.
> ---
> Not sure if the behavior is known/expected or a bug, but when e.g. booting a
> system with
On Thu, Sep 12, 2013 at 2:37 PM, Olivier Brunel wrote:
> Can help since the journal requires /etc/machine-id to exists in order to
> start,
> and will simply silently exit when it does not.
> ---
> Not sure if the behavior is known/expected or a bug, but when e.g. booting a
> system with a read-o
Can help since the journal requires /etc/machine-id to exists in order to start,
and will simply silently exit when it does not.
---
Not sure if the behavior is known/expected or a bug, but when e.g. booting a
system with a read-only rootfs where /etc/machine-id doesn't exist, the journal
would jus
