From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Subject: RFE: make the init manager an image feature (again)
Date: Fri, 15 Feb 2013 19:19:47 +0100 [thread overview]
Message-ID: <lyk3q9sam4.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
Hello,
it would be nice when the decision to make the init manager a distribution
feature will be reverted to the old oe-meta mechanism.
Being a distribution feature means, that packages are created in such a
way that it is impossible to split off unwanted and heavy weighted
functionality at image creation time.
E.g. on most of my systems, I create two kinds of images: a full
featured, systemd based one and a very minimal rescue system with
busybox and some filesystem utilities. With recent systemd packaging
change, the rescue image size grow up from 5.9 MiB to 27 MiB because
systemd dependencies are hardcoded in mandatory packages.
Formerly, systemd dependencies could be avoided by adding the -systemd
packages to BAD_RECOMMENDATIONS (e.g. due to busybox-syslog ->
busybox-syslog-systemd rrecommend).
I am aware that initscripts were always part of the main package. But
sysvinit was very lightweighted and the extra space either negligible or
easy to recover by removing some files in IMAGE_PREPROCESS_COMMAND.
Hence my recommendation: make the init manager an image feature again
and create -systemd and -sysv packages with the corresponding scripts.
OpenEmbedded is still for embedded devices where size matters.
Of course, systemd can be still a distribution feature to enable things
like socket activation as part of PACKAGE_CONFIG. But dependencies on
init system packages should be RRECOMMENDS which can be overridden
easily at image creation time.
Enrico
next reply other threads:[~2013-02-15 18:35 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 18:19 Enrico Scholz [this message]
2013-02-15 18:47 ` RFE: make the init manager an image feature (again) Otavio Salvador
2013-02-15 23:44 ` Martin Jansa
2013-02-16 9:15 ` Richard Purdie
2013-02-16 10:47 ` Otavio Salvador
2013-02-16 12:53 ` Richard Purdie
2013-02-16 13:41 ` Otavio Salvador
2013-02-24 8:50 ` Khem Raj
2013-02-24 14:10 ` Otavio Salvador
2013-02-25 10:28 ` Enrico Scholz
2013-02-17 23:20 ` Martin Jansa
2013-02-18 10:17 ` Enrico Scholz
2013-02-20 19:58 ` Burton, Ross
2013-02-21 10:34 ` Enrico Scholz
2013-02-21 10:40 ` Burton, Ross
2013-02-21 11:34 ` Enrico Scholz
2013-02-21 11:50 ` Otavio Salvador
2013-02-21 12:01 ` Phil Blundell
2013-02-16 11:57 ` Enrico Scholz
2013-02-16 12:34 ` Richard Purdie
2013-02-16 13:28 ` Otavio Salvador
2013-02-16 19:40 ` Martin Jansa
2013-02-16 19:49 ` Otavio Salvador
2013-02-17 13:06 ` Enrico Scholz
2013-02-21 15:35 ` Burton, Ross
2013-02-21 15:49 ` Otavio Salvador
2013-02-21 17:20 ` Enrico Scholz
2013-02-24 10:37 ` Ross Burton
2013-02-24 10:45 ` Ross Burton
2013-02-24 14:06 ` Otavio Salvador
2013-02-24 22:04 ` Ross Burton
2013-02-25 7:38 ` Martin Jansa
2013-02-25 7:46 ` Andreas Müller
2013-02-25 11:45 ` Otavio Salvador
2013-02-25 11:28 ` Enrico Scholz
2013-02-26 6:45 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2013-02-16 20:20 Daniel Lazzari
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=lyk3q9sam4.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
/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