From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnout Vandecappelle Date: Tue, 20 Dec 2011 07:49:10 +0100 Subject: [Buildroot] [RFC] Add systemd to buildroot In-Reply-To: <1322047811-12933-1-git-send-email-maxime.ripard@free-electrons.com> References: <1322047811-12933-1-git-send-email-maxime.ripard@free-electrons.com> Message-ID: <201112200749.10389.arnout@mind.be> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On Wednesday 23 November 2011 12:30:08 Maxime Ripard wrote: > Hi list, > > 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. You didn't get much comments, so I'll try to do some review. No testing though. > 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. This is of course a show-stopper for inclusion. People expect the git HEAD to work. > 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. I guess you mean the S20urandom and S40network in the skeleton? For the moment, I don't think it's a problem to leave them there. To fix it, you could include a target-install hook that removes them (which obviously still leaves the init scripts installed by other packages, but that should be fixed separately per package). Regards, Arnout -- Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286540 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43