mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
* [ptxdist] systemd configuration
@ 2014-11-23 21:08 Matthias Klein
  2014-11-25  9:03 ` Michael Olbrich
  0 siblings, 1 reply; 2+ messages in thread
From: Matthias Klein @ 2014-11-23 21:08 UTC (permalink / raw)
  To: ptxdist

Hello,

I try to evaluate systemd as busybox init replacement on an ARM board 
where we mount the root filesystem read-only.

I got the system booting into a console with only one error:

● kmod-static-nodes.service - Create list of required static device 
nodes for the current kernel
    Loaded: loaded (/lib/systemd/system/kmod-static-nodes.service; static)
    Active: failed (Result: exit-code) since Thu 1970-01-01 00:00:08 
UTC; 46min ago
   Process: 71 ExecStart=/bin/kmod static-nodes --format=tmpfiles 
--output=/run/tmpfiles.d/kmod.conf (code=exited, status=203/EXEC)
  Main PID: 71 (code=exited, status=203/EXEC)

Warning: Journal has been rotated since unit was started. Log output is 
incomplete or unavailable.


I don't have a /bin/kmod on my target. We are using busybox insmod etc. 
where no /bin/kmod is installed.
For me it looks like the kmod-static-nodes.service is not needed. How 
can I disable it in the ptxdist project?

What is the right way to configure / adjust which uints and targets 
systemd will start?
Normally this all done at runtime using systemctl, but how can this be 
done "offline" / during creation of the root filesystem by ptxdist?


Best regards,
Matthias


-- 
ptxdist mailing list
ptxdist@pengutronix.de

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-11-25  9:03 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-11-23 21:08 [ptxdist] systemd configuration Matthias Klein
2014-11-25  9:03 ` Michael Olbrich

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox