From: Adrian Bunk <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Should systemd be marked as incompatible with musl?
Date: Fri, 24 May 2019 20:27:37 +0300 [thread overview]
Message-ID: <20190524172737.GA6813@localhost> (raw)
In-Reply-To: <f10fea91-06a4-529a-1b42-0c12dc46f54c@gmail.com>
On Fri, May 24, 2019 at 09:13:08AM -0700, Khem Raj wrote:
>
>
> On 5/24/19 3:12 AM, Adrian Bunk wrote:
> > On Thu, May 23, 2019 at 07:16:53PM -0700, Khem Raj wrote:
> > > ...
> > > but I think dropping
> > > systemd support completely from musl is not an option I would like to go
> > > with, there are cases where this makes sense. Especially when you have to
> > > cater to different set of devices from small to big, userspace remaining
> > > same is big advantage atleast in the world I am in.
> > > ...
> >
> > That's a good point - when arguing against systemd as default init system.
> >
> > systemd is bigger than glibc, therefore on very small systems where the
> > size of the C library matters using systemd is usually not an option.
>
> Yes, design-wise I concur, in practice, desktop distros rule the linux world
> and systemd is quite prevalent there,
Desktop distros don't use musl - it wouldn't make sense.
> so sometimes you have to wear the
> shoes of same color, atleast thats what I see.
Is any musl-using distribution supporting it with systemd?
After a cursory look around it doesn't seem that trying to support the
weird combination of systemd and musl brings compatibility with anyone
else.
> apps want to run uniformly on both OE and non-OE systems
This implies using glibc, which is the correct choice in most cases.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-05-24 17:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 10:33 Should systemd be marked as incompatible with musl? Adrian Bunk
2019-05-23 12:22 ` Burton, Ross
2019-05-24 1:45 ` ChenQi
2019-05-24 2:16 ` Khem Raj
2019-05-24 10:12 ` Adrian Bunk
2019-05-24 16:13 ` Khem Raj
2019-05-24 17:27 ` Adrian Bunk [this message]
2019-05-24 17:31 ` Khem Raj
2019-05-24 17:58 ` Adrian Bunk
2019-05-24 18:04 ` Khem Raj
2019-05-24 18:45 ` Adrian Bunk
2019-05-24 19:34 ` Andre McCurdy
2019-05-24 19:47 ` Khem Raj
2019-05-24 20:28 ` Adrian Bunk
2019-05-24 22:25 ` Andre McCurdy
2019-05-25 7:25 ` Adrian Bunk
2019-05-28 23:10 ` Andre McCurdy
2019-05-29 7:31 ` Adrian Bunk
2019-05-29 9:01 ` Khem Raj
2019-05-29 10:29 ` Adrian Bunk
2019-05-29 19:04 ` Andre McCurdy
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=20190524172737.GA6813@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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 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.