Skip to contentSkip to conversation

How do I get rid of systemd

DISCUSSION Rainer Koenig 5 participants 10 messages Jan 18, 2012 – Jan 22, 2012

lore
Share & tools
lore
#0 lore raw

Ok,

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?

Regards
Rainer

Signature · 15 lines
Dipl.-Inf. (FH) Rainer Koenig
Project Manager Linux Clients
Dept. PDG WPS R&D SW OSE

Fujitsu Technology Solutions
Bürgermeister-Ullrich-Str. 100
86199 Augsburg
Germany

Telephone: +49-821-804-3321
Telefax:   +49-821-804-2131
Mail:      mailto:[email protected]

Internet         ts.fujtsu.com
Company Details  ts.fujitsu.com/imprint.html
#1 lore raw

Op 18 jan. 2012, om 14:16 heeft Rainer Koenig het volgende geschreven:

Quoted 8 lines

Ok,

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?

What's wrong with cgroups?

#2 lore raw

Am 18.01.2012 14:28, schrieb Koen Kooi:

Quoted 1 line

What's wrong with cgroups?

Probably nothing. But now I've got an image that has both systemd and systemv to boot up and that results in an endless loop with kernel messages about omap_i2c.

My idea was that OE is a toolchain that enables me to build a customized distribution, so I thought I have the choice to use
systemd or systemv with a configuration setting. But it came out, that systemd is sort of mandatory nowadays and its not that easy to get rid of it.

Regards
Rainer

Signature · 15 lines
Dipl.-Inf. (FH) Rainer Koenig
Project Manager Linux Clients
Dept. PDG WPS R&D SW OSE

Fujitsu Technology Solutions
Bürgermeister-Ullrich-Str. 100
86199 Augsburg
Germany

Telephone: +49-821-804-3321
Telefax:   +49-821-804-2131
Mail:      mailto:[email protected]

Internet         ts.fujtsu.com
Company Details  ts.fujitsu.com/imprint.html
#3 lore raw

Op 18 jan. 2012, om 15:15 heeft Rainer Koenig het volgende geschreven:

Quoted 8 lines

Am 18.01.2012 14:28, schrieb Koen Kooi:

Quoted 1 line

What's wrong with cgroups?

Probably nothing. But now I've got an image that has both systemd and systemv to boot up and that results in an endless loop with kernel messages about omap_i2c.

Quoted 5 lines

My idea was that OE is a toolchain that enables me to build a customized distribution, so I thought I have the choice to use
systemd or systemv with a configuration setting. But it came out, that systemd is sort of mandatory nowadays and its not that easy to get rid of it.

It's really easy, just create your own image. But don't come complaining if you use a task that depends on systemd.

#4 lore raw
In reply to Rainer Koenig

Hi Rainer,

Quoted 6 lines · Rainer Koenig

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.

Actually, it would be nice to have a global variable setting for it... i.e. build with/without systemd :P

Kind regards,
Jin

#5 lore raw

Op 18 jan. 2012, om 14:43 heeft Sergey 'Jin' Bostandzhyan het volgende geschreven:

Quoted 7 lines

Hi Rainer,

Quoted 4 lines · Rainer Koenig

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.

Quoted 7 lines
Quoted 2 lines

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.

#6 lore raw

Am 18.01.2012 15:21, schrieb Koen Kooi:

Quoted 4 lines

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.

Ok. Got 2 files for my image:

---------------------8<-snip---------------------

$ cat magna-base-image.bb

LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58"

IMAGE_PREPROCESS_COMMAND = "rootfs_update_timestamp"

IMAGE_INSTALL += " \
        angstrom-task-boot \
        task-basic \
        ${CONMANPKGS} \

"
CONMANPKGS = "connman connman-plugin-loopback connman-plugin-ethernet" CONMANPKGS_libc-uclibc = ""

IMAGE_DEV_MANAGER   = "udev"
IMAGE_INIT_MANAGER  = " "
IMAGE_INITSCRIPTS   = " "

IMAGE_LOGIN_MANAGER = "tinylogin shadow"

export IMAGE_BASENAME = "magna-base-image"

inherit image

$ cat magna-c-image.bb

#Angstrom bootstrap image
require magna-base-image.bb

DEPENDS += "task-base-extended \
           "
IMAGE_INSTALL += "task-base-extended \
            "

export IMAGE_BASENAME = "magna-c-image"
---------------------8<-snip---------------------

Pretty much the same what Angstrom does, just changed the IMAGE_INIT_MANAGER.

So where did I include ${PN}-systemd?

Signature · 15 lines
Dipl.-Inf. (FH) Rainer Koenig
Project Manager Linux Clients
Dept. PDG WPS R&D SW OSE

Fujitsu Technology Solutions
Bürgermeister-Ullrich-Str. 100
86199 Augsburg
Germany

Telephone: +49-821-804-3321
Telefax:   +49-821-804-2131
Mail:      mailto:[email protected]

Internet         ts.fujtsu.com
Company Details  ts.fujitsu.com/imprint.html
#7 lore raw

Op 18 jan. 2012, om 15:34 heeft Rainer Koenig het volgende geschreven:

Quoted 46 lines

Am 18.01.2012 15:21, schrieb Koen Kooi:

Quoted 4 lines

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.

Ok. Got 2 files for my image:

---------------------8<-snip---------------------

$ cat magna-base-image.bb

LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58"

IMAGE_PREPROCESS_COMMAND = "rootfs_update_timestamp"

IMAGE_INSTALL += " \
       angstrom-task-boot \
       task-basic \
       ${CONMANPKGS} \

"
CONMANPKGS = "connman connman-plugin-loopback connman-plugin-ethernet" CONMANPKGS_libc-uclibc = ""

IMAGE_DEV_MANAGER   = "udev"
IMAGE_INIT_MANAGER  = " "
IMAGE_INITSCRIPTS   = " "

IMAGE_LOGIN_MANAGER = "tinylogin shadow"

export IMAGE_BASENAME = "magna-base-image"

inherit image

$ cat magna-c-image.bb

#Angstrom bootstrap image
require magna-base-image.bb

DEPENDS += "task-base-extended \
          "
IMAGE_INSTALL += "task-base-extended \
           "
Quoted 7 lines

export IMAGE_BASENAME = "magna-c-image"
---------------------8<-snip---------------------

Pretty much the same what Angstrom does, just changed the IMAGE_INIT_MANAGER.

So where did I include ${PN}-systemd?

task-basic

#8 lore raw
In reply to Koen Kooi
Quoted 13 lines · Koen Kooi

Op 18 jan. 2012, om 14:43 heeft Sergey 'Jin' Bostandzhyan het volgende geschreven:

Quoted 10 lines

Hi Rainer,

Quoted 6 lines · Rainer Koenig

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?

Quoted 6 lines
Quoted 4 lines

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

#9 lore raw
Quoted 25 lines · Philip Balister
Quoted 13 lines · Koen Kooi

Op 18 jan. 2012, om 14:43 heeft Sergey 'Jin' Bostandzhyan het volgende geschreven:

Quoted 10 lines

Hi Rainer,

Quoted 6 lines · Rainer Koenig

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?

Quoted 6 lines
Quoted 4 lines

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.

Quoted 6 lines

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.

I guess define PACKAGE_GROUPS for both and then user can chose whichever one wants in an image.

Quoted 7 lines

Philip

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Signature · 1 line
-Khem