Re: systemd 183, boot problem

On Sun, May 27, 2012 at 9:01 PM, Allin Cottrell <[email protected]> wrote:
> I just tried updating from systemd 44 + udev 182. On booting I saw:
>
> "Could not find module by name='<binary-garbage>'"
> (That is, no readable module name)
>
> "Failed to insert ipv6"
>
> "Cannot create mount unit for API file system /sys/kernel/security.
> Refusing."
>
> I was then dumped into emergency mode. Grubbing through the source I saw
> that /sys/kernel/security is needed by IMA, so I reconfigured systemd-183
> with --disable-ima, rebuilt, reinstalled and rebooted. That didn't help; I
> landed in emergency mode again. So I ended up reinstalling 44 + 182;
> fortunately that gave me back a usable system.
>
> I think the new securityfs requirement ought to be mentioned in NEWS, and
> made conditional on enabling IMA.

I don't have securityfs enabled in the kernel and it works fine here.

The message should only be debug log, I see that too, if I enable
debugging. It should not be an error and the cause of the failure you
see.

Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html