From: Robert Schwebel <r.schwebel@pengutronix.de>
To: buildroot@busybox.net
Subject: [Buildroot] systemd
Date: Sun, 20 Nov 2011 20:15:21 +0100 [thread overview]
Message-ID: <20111120191521.GG12903@pengutronix.de> (raw)
In-Reply-To: <87obw9rvc7.fsf@macbook.be.48ers.dk>
Hi,
On Fri, Nov 18, 2011 at 10:09:44PM +0100, Peter Korsgaard wrote:
> Belisko> when looking for ELCE 2011 videos one video was very
> Belisko> interesting:http://events.linuxfoundation.org/events/embedded-linux-conference-europe/kooi
> Belisko> There is a lot of discussion about decreasing boot time for embedded
> Belisko> systems and systemd seems not yet included in buildroot (OE have it
> Belisko> also angstrom).
ptxdist has systemd support as well. We are in fact migrating all our
newer BSPs to systemd.
> Notice that systemd pulls in quite some dependencies, so it might not
> really be a net gain in the end depending on your setup - In Koens
> presentation he mentioned that his OE setup spends more than a minute
> from init to finished booting, which is quite far from a typical
> buildroot boot.
Our impression after half a year of experience with systemd in embedded
scenarios is that it is worth the effort. The whole beast is a really,
really great idea, because it solves so many standard problems in a very
clean and clever way. However, don't expect magic when it comes to boot
times. The old strategy that a system boots the quicker the less it does
is still vaild. If you do a lot of things, it will take it's time.
Where we find it helpful is:
- have a clean abstraction of "services"
- be able to deal with services via an API (not just scripts)
- integration of application scenarios ontop of a base operating system
- watchdog handling (we are trying to integrate watchdog into systemd
mainline)
- security aware environments (it may be possible to run systems without
a shell)
- and of course all the other selling points which have been outlined by
the systemd people.
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2011-11-20 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 20:02 [Buildroot] systemd Belisko Marek
2011-11-18 21:09 ` Peter Korsgaard
2011-11-20 19:15 ` Robert Schwebel [this message]
2011-11-20 8:28 ` Thomas Petazzoni
2011-11-21 9:34 ` Maxime Ripard
2011-11-23 7:49 ` Arnout Vandecappelle
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=20111120191521.GG12903@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=buildroot@busybox.net \
/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