* How do I get rid of systemd @ 2012-01-18 13:16 Rainer Koenig 2012-01-18 13:28 ` Koen Kooi 2012-01-18 13:43 ` Sergey 'Jin' Bostandzhyan 0 siblings, 2 replies; 10+ messages in thread From: Rainer Koenig @ 2012-01-18 13:16 UTC (permalink / raw) To: Openembedded Core 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 -- 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:Rainer.Koenig@ts.fujitsu.com Internet ts.fujtsu.com Company Details ts.fujitsu.com/imprint.html ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How do I get rid of systemd 2012-01-18 13:16 How do I get rid of systemd Rainer Koenig @ 2012-01-18 13:28 ` Koen Kooi 2012-01-18 14:15 ` Rainer Koenig 2012-01-18 13:43 ` Sergey 'Jin' Bostandzhyan 1 sibling, 1 reply; 10+ messages in thread From: Koen Kooi @ 2012-01-18 13:28 UTC (permalink / raw) To: Patches and discussions about the oe-core layer Op 18 jan. 2012, om 14:16 heeft Rainer Koenig het volgende geschreven: > 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? ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How do I get rid of systemd 2012-01-18 13:28 ` Koen Kooi @ 2012-01-18 14:15 ` Rainer Koenig 2012-01-18 14:22 ` Koen Kooi 0 siblings, 1 reply; 10+ messages in thread From: Rainer Koenig @ 2012-01-18 14:15 UTC (permalink / raw) To: openembedded-core Am 18.01.2012 14:28, schrieb Koen Kooi: > 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 -- 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:Rainer.Koenig@ts.fujitsu.com Internet ts.fujtsu.com Company Details ts.fujitsu.com/imprint.html ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How do I get rid of systemd 2012-01-18 14:15 ` Rainer Koenig @ 2012-01-18 14:22 ` Koen Kooi 0 siblings, 0 replies; 10+ messages in thread From: Koen Kooi @ 2012-01-18 14:22 UTC (permalink / raw) To: Patches and discussions about the oe-core layer Op 18 jan. 2012, om 15:15 heeft Rainer Koenig het volgende geschreven: > Am 18.01.2012 14:28, schrieb Koen Kooi: > >> 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. It's really easy, just create your own image. But don't come complaining if you use a task that depends on systemd. ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How do I get rid of systemd 2012-01-18 13:16 How do I get rid of systemd Rainer Koenig 2012-01-18 13:28 ` Koen Kooi @ 2012-01-18 13:43 ` Sergey 'Jin' Bostandzhyan 2012-01-18 14:21 ` Koen Kooi 1 sibling, 1 reply; 10+ messages in thread From: Sergey 'Jin' Bostandzhyan @ 2012-01-18 13:43 UTC (permalink / raw) To: Patches and discussions about the oe-core layer 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. Actually, it would be nice to have a global variable setting for it... i.e. build with/without systemd :P Kind regards, Jin ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How do I get rid of systemd 2012-01-18 13:43 ` Sergey 'Jin' Bostandzhyan @ 2012-01-18 14:21 ` Koen Kooi 2012-01-18 14:34 ` Rainer Koenig 2012-01-18 14:34 ` Philip Balister 0 siblings, 2 replies; 10+ messages in thread From: Koen Kooi @ 2012-01-18 14:21 UTC (permalink / raw) To: Patches and discussions about the oe-core layer 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. ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How do I get rid of systemd 2012-01-18 14:21 ` Koen Kooi @ 2012-01-18 14:34 ` Rainer Koenig 2012-01-18 15:13 ` Koen Kooi 2012-01-18 14:34 ` Philip Balister 1 sibling, 1 reply; 10+ messages in thread From: Rainer Koenig @ 2012-01-18 14:34 UTC (permalink / raw) To: openembedded-core Am 18.01.2012 15:21, schrieb Koen Kooi: > 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? -- 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:Rainer.Koenig@ts.fujitsu.com Internet ts.fujtsu.com Company Details ts.fujitsu.com/imprint.html ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How do I get rid of systemd 2012-01-18 14:34 ` Rainer Koenig @ 2012-01-18 15:13 ` Koen Kooi 0 siblings, 0 replies; 10+ messages in thread From: Koen Kooi @ 2012-01-18 15:13 UTC (permalink / raw) To: Patches and discussions about the oe-core layer Op 18 jan. 2012, om 15:34 heeft Rainer Koenig het volgende geschreven: > Am 18.01.2012 15:21, schrieb Koen Kooi: > >> 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? task-basic ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How do I get rid of systemd 2012-01-18 14:21 ` Koen Kooi 2012-01-18 14:34 ` Rainer Koenig @ 2012-01-18 14:34 ` Philip Balister 2012-01-22 3:25 ` Khem Raj 1 sibling, 1 reply; 10+ messages in thread From: Philip Balister @ 2012-01-18 14:34 UTC (permalink / raw) To: Patches and discussions about the oe-core layer 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 ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How do I get rid of systemd 2012-01-18 14:34 ` Philip Balister @ 2012-01-22 3:25 ` Khem Raj 0 siblings, 0 replies; 10+ messages in thread From: Khem Raj @ 2012-01-22 3:25 UTC (permalink / raw) To: Patches and discussions about the oe-core layer On (18/01/12 09:34), Philip Balister wrote: > 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. I guess define PACKAGE_GROUPS for both and then user can chose whichever one wants in an image. > > Philip > > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core -- -Khem ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2012-01-22 3:32 UTC | newest] Thread overview: 10+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2012-01-18 13:16 How do I get rid of systemd Rainer Koenig 2012-01-18 13:28 ` Koen Kooi 2012-01-18 14:15 ` Rainer Koenig 2012-01-18 14:22 ` Koen Kooi 2012-01-18 13:43 ` Sergey 'Jin' Bostandzhyan 2012-01-18 14:21 ` Koen Kooi 2012-01-18 14:34 ` Rainer Koenig 2012-01-18 15:13 ` Koen Kooi 2012-01-18 14:34 ` Philip Balister 2012-01-22 3:25 ` Khem Raj
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.