From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] systemd
Date: Mon, 21 Nov 2011 10:34:32 +0100 [thread overview]
Message-ID: <4ECA1B28.50907@free-electrons.com> (raw)
In-Reply-To: <CAAfyv34FVf5V-ZH4-xapeG8F+2VSgXOWMsf+5O03m9wimRx1Ug@mail.gmail.com>
Hi,
On 18/11/2011 21:02, Belisko Marek wrote:
> Hi,
>
> when looking for ELCE 2011 videos one video was very
> interesting:http://events.linuxfoundation.org/events/embedded-linux-conference-europe/kooi
> There is a lot of discussion about decreasing boot time for embedded
> systems and systemd seems not yet included in buildroot (OE have it
> also angstrom).
>
> Is there anybody who working on this or can I start integration to buildroot?
After attending this exact talk, I've begun to work on some integration
of systemd in Buildroot.
This has been stalled lately because I didn't have time to improve my
initial implementation, but basically, I have for now :
- Made the systemd package
- Added new package variables to define both Sys-V and systemd-format
init scripts
- Added the needed logic so that you can only select one of the init
systems available in Buildroot (sysvinit, Busybox, systemd)
- Migrated the existing packages to use the mentionned variables.
I still have some issues that I need to address, that explains why I
haven't yet posted the patches :
- I have a bug that adds the sysv init scripts to the target even if
it shouldn't
- I have not tested it "live" yet
I'll try to work on it this week
Maxime
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-11-21 9:34 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
2011-11-20 8:28 ` Thomas Petazzoni
2011-11-21 9:34 ` Maxime Ripard [this message]
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=4ECA1B28.50907@free-electrons.com \
--to=maxime.ripard@free-electrons.com \
--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