From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: RFE: make the init manager an image feature (again)
Date: Mon, 25 Feb 2013 12:28:09 +0100 [thread overview]
Message-ID: <lymwus3a5y.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <E79C80CE9122499B9C7D2D855CDF6319@intel.com> (Ross Burton's message of "Sun, 24 Feb 2013 10:37:26 +0000")
Ross Burton <ross.burton-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
writes:
> the source, so enabling systemd may well lead to libsystemd-* libraries
> sneaking into your rescue image.
for socket activation and sd_notify(), only libsystemd-daemon is required
which is
-rwxr-xr-x 1 root root 11644 Feb 25 09:27 /lib/libsystemd-daemon.so.0.0.7
~ # ldd /lib/libsystemd-daemon.so.0.*
libdl.so.2 => /lib/libdl.so.2 (0x441e0000)
librt.so.1 => /lib/librt.so.1 (0x441c8000)
libc.so.6 => /lib/libc.so.6 (0x44040000)
/lib/ld-linux.so.3 (0x44010000)
libpthread.so.0 => /lib/libpthread.so.0 (0x441a0000)
~ # ldd -u -r /lib/libsystemd-daemon.so.0.*
Unused direct dependencies:
/lib/libdl.so.2
Ok, it needs more space than nothing and small things like this can sum
up easily. But it is still a significant difference between having
libsystemd-daemon in the image or the whole systemd.
> The systemd libraries will have to be reviewed to verify that installing
> one of them doesn't pull in systemd itself.
afair, libsystemd-daemon was designed to be as light weighted as possible
and will never depend on the rest of systemd.
Enrico
next prev parent reply other threads:[~2013-02-25 11:44 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 18:19 RFE: make the init manager an image feature (again) Enrico Scholz
2013-02-15 18:47 ` 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 [this message]
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=lymwus3a5y.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