[systemd-devel] Systemd port on custom embedded linux

Cristian Axenie cristian.axenie at gmail.com
Tue Sep 21 04:11:41 PDT 2010


Hi ! I've managed to boot my system with systemd although I still have some
problems with autofs.

[   10.690000] Freeing init memory: 152K
[   11.050000] systemd[1]: systemd 8 running in system mode. (+PAM +LIBWRAP
-AUDIT -SELINUX -IPV6 -SYSVINIT)
[   11.070000] systemd[1]: No hostname configured.
[   11.080000] systemd[1]: Set hostname to <localhost>.
[   11.120000] systemd[1]: Failed to fully start up daemon: No such file or
directory
[   11.200000] systemd[1]: Failed to initialize automounter: No such file or
directory
[   11.210000] systemd[1]: Unit proc-sys-fs-binfmt_misc.automount entered
maintenance state.
Starting /etc/rc.local Compatibility...
Starting Getty on ttyS0...

localhost login: _

Now I'm facing some problems when trying to shutdown / halt / reboot the
board. The following message is similar for all the mentioned commands :

Broadcast message from root (Thu Jan  1 00:04:52 2009):

The system is going down for system halt NOW!
[  296.080000] systemd-initctl[698]: Received environment initctl request.
This is not implemented in systemd.

The system freezes !

Best !


On Tue, Sep 21, 2010 at 1:28 AM, Lennart Poettering
<lennart at poettering.net>wrote:

> 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20100921/a6464605/attachment.html>


More information about the systemd-devel mailing list