Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Add systemd to buildroot
Date: Wed, 23 Nov 2011 22:35:54 +0100	[thread overview]
Message-ID: <4ECD673A.7000405@free-electrons.com> (raw)
In-Reply-To: <CAAfyv35NYoDU9qaGT-LBbS++b_s+0e7LWAp=DCYzFUn90E9aKA@mail.gmail.com>

Hi Marek,

Le 23/11/2011 22:14, Belisko Marek a ?crit :
> On Wed, Nov 23, 2011 at 12:30 PM, Maxime Ripard
> <maxime.ripard@free-electrons.com>  wrote:
>> I've been working for some time on adding systemd to buildroot in a nice way. It
>> is now in a pretty nice state I guess, at least nice enough to send an RFC and
>> get some review about the basic mechanics.
>>
>> While the system should boot with systemd, for a reason unknown to me, udev
>> doesn't take into account its rules, and don't tag the devices for systemd,
>> which, in turn, doesn't expose a getty.
>>
>> Another problem is that I still have some sysv init scripts added to the
>> filesystem through the skeleton. Since it is completely static, I don't find a
>> good way around this problem. Maybe we don't care. I don't know.
>>
>> So, give it a look, and please tell me what you think :)
> thanks for good work. I don't see any patches where adding systemd
> specific services.
> Are they in your queue or this was only basic patches?

It's still a work to be done.
Once we will have a nice way to add systemd to buildroot, which is not 
sure yet, I guess we will add the systemd units one unit at a time.

This patchset was more to send a proof of concept and all agree on the 
path to follow, so adding the units seem a little too early.

Maxime

  reply	other threads:[~2011-11-23 21:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 11:30 [Buildroot] [RFC] Add systemd to buildroot Maxime Ripard
2011-11-23 11:30 ` [Buildroot] [PATCH 1/3] Add the systemd package Maxime Ripard
2011-11-23 11:57   ` Baruch Siach
2011-11-23 13:53     ` Maxime Ripard
2011-12-20  7:05   ` Arnout Vandecappelle
2012-01-02  9:35     ` Maxime Ripard
2011-11-23 11:30 ` [Buildroot] [PATCH 2/3] Rework of the init system Maxime Ripard
2011-12-20  8:03   ` Arnout Vandecappelle
2012-01-02  9:52     ` Maxime Ripard
2012-01-02 14:52       ` Thomas Petazzoni
2012-01-06  7:13       ` Arnout Vandecappelle
2012-01-06  9:15         ` Maxime Ripard
2012-01-09  6:37           ` Arnout Vandecappelle
2011-11-23 11:30 ` [Buildroot] [PATCH 3/3] Migrate the packages to the new infra Maxime Ripard
2011-12-20 21:29   ` Arnout Vandecappelle
2012-01-02 10:02     ` Maxime Ripard
2012-01-06  6:52       ` Arnout Vandecappelle
2011-11-23 14:05 ` [Buildroot] [RFC] Add systemd to buildroot Maxime Ripard
2011-11-23 21:14 ` Belisko Marek
2011-11-23 21:35   ` Maxime Ripard [this message]
2011-12-20 21:14     ` Arnout Vandecappelle
2011-12-14 10:43 ` Maxime Ripard
2011-12-20  6:49 ` Arnout Vandecappelle
2012-01-02  9:58   ` Maxime Ripard

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=4ECD673A.7000405@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