From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Device management
Date: Tue, 24 Jul 2018 16:06:52 +0200 [thread overview]
Message-ID: <7097945.HuMLGqmjqx@ada> (raw)
In-Reply-To: <HE1PR0702MB38049F985B94DADF4E8DC9D098550@HE1PR0702MB3804.eurprd07.prod.outlook.com>
Hei hei,
Am Dienstag, 24. Juli 2018, 13:46:47 CEST schrieb Jakov Simunic:
> 2. Is systemd really a good option for embedded systems?
You don't need to use it. We still use busybox-init with plain old init
scripts and monit for monitoring.
> 4. If I have config_devtmpfs and config_devtmpfs_mount options enabled do
> I even need udev/mdev/eudev?
Depends? On an arm target with a recent kernel and device tree we use devtmpfs
with CONFIG_DEVTMPFS=y and CONFIG_DEVTMPFS_MOUNT=y and that's sufficient to
find all hardware. However we are not using USB or any other plug'n'play
hardware. So on that target no udev, no systemd. But that's more for historic
reasons, it is just no one took the effort to switch to systemd.
Greets
Alex
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2018-07-24 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 13:46 Jakov Simunic
2018-07-24 14:06 ` Alexander Dahl [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7097945.HuMLGqmjqx@ada \
--to=ada@thorsis.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox