[systemd-devel] Systemd port on custom embedded linux

[Lennart Poettering]

On Fri, 17.09.10 16:49, Cristian Axenie (cristian.axenie at gmail.com) wrote:

> Hi !
> I've managed to solve some problems appearing during boot but some persist.
> The current setup makes the system freeze in the current step :
> 
> [   10.230000] systemd[1]: systemd 8 running in system mode. (+PAM +LIBWRAP
> -AUDIT -SELINUX -IPV6 -SYSVINIT)
> [   10.250000] systemd[1]: No hostname configured.
> [   10.260000] systemd[1]: Set hostname to <localhost>.
> [   10.290000] systemd[1]: Failed to fully start up daemon: No such file or
> directory
> [   10.370000] systemd[1]: Failed to initialize automounter: No such file or
> directory
> [   10.380000] systemd[1]: Unit proc-sys-fs-binfmt_misc.automount entered
> maintenance state.
> Starting /etc/rc.local Compatibility...
> 
> Regarding the automounter, I have used autofs v5 and not autofs4, should
> this make a difference ?

No. We actually rely on v5 features. it's a bit confusing that the
kernel still exposes that under the label "autofs4" though.

> Any ideas of those return messages when automounter enters the waiting state
> (Failed to initialize automounter: No such file or directory) and themanager
> startup problem ( Failed to fully start up daemon: No such file or
> directory) ?

This looks as if your /dev/autofs node is missing. Normally this should
be created via devtmpfs and hence be available already when systemd
first looks at it.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.