Re: How do I get rid of systemd

[Philip Balister <philip@balister.org>]

On 01/18/2012 09:21 AM, Koen Kooi wrote:
> 
> Op 18 jan. 2012, om 14:43 heeft Sergey 'Jin' Bostandzhyan het volgende geschreven:
> 
>> Hi Rainer,
>>
>> On Wed, Jan 18, 2012 at 02:16:12PM +0100, Rainer Koenig wrote:
>>> built my first basic customized console image (based on angstrom's
>>> console-image.bb) and managed to get SystemV init pulled in by deleting
>>> the systemd entry for the init manager.
>>>
>>> But systemd is still pulled in via connman, dhcp, rsyslog and ntp. How
>>> can I get totally rid of systemd so that I don't need a kernel with CGROUPS?
>>
>> I also did not want systemd in my image, I had to create a layer and patch
>> out systemd from each package that was pulling it in, one by one.
>>
>> Surely not the nicest solution, but I did not find any other ways to solve this.
> 
> It's really easy, create your own image, no patching needed. The systemd dependencies are all in ${PN}-systemd, so just don't include those in your image. I you do include ${PN}-systemd in your image you shouldn't be surprised that systemd ends up in it.

I'm working through this now. The meta-oe task-basic is sucking in
rsyslog-systemd. I already made a renamed copy of this so I could use
openssh instead of dropbear, so this was an easy fix for me.

But it would be a good idea to keep references to systemd (or sysvinit)
out of core tasks to make life easier for people.

And, it would be really nice not to have the ssh daemon determined in
task-basic. I do not want to use a local var to override that setting,
since then my task-basic is different from everyone elses.

Philip