[prev in list] [next in list] [prev in thread] [next in thread] 

List:       musl
Subject:    Re: [musl] RE: [EXTERNAL] Re: [musl] Advocating musl to in windows subsystem and OS X
From:       Rich Felker <dalias () libc ! org>
Date:       2020-06-15 23:30:49
Message-ID: 20200615233047.GG6430 () brightrain ! aerifal ! cx
[Download RAW message or body]

On Sun, Jun 14, 2020 at 08:43:35PM +0000, John Starks wrote:
> > From: Markus Wichmann <nullplan@gmx.net>
> > On Fri, Jun 12, 2020 at 06:56:28PM +0200, Brian Peregrine wrote:
> > > Microsoft probably uses glibc (as the subsystem seems to be
> > > canonical-made and they use glibc in ubuntu),
> > 
> > The distribution you install is just a collection of the exact binaries you would
> > get in a normal install. Therefore it is the distribution itself which has a libc,
> > and whether that is glibc, musl, or dietlibc (just to name an utterly outlandish
> > option) is up to the distribution.
> > However, there is one additional file installed, called /init, which is also the
> > root of the emulated process tree. And that file is statically linked against
> > musl (as you can tell by running "strings" on it). It apparently generates a
> > couple of files from Windows' current system settings (like /etc/resolv.conf).
> 
> Yes, originally we dynamically linked our infrastructure binaries to
> glibc and relied on the distro to ship it. These days we are happy
> users of (statically-linked) musl. We additionally try to make sure
> that musl-based distros such as Alpine work well within WSL.

Thanks. Can you fill us in on if WSL1 is still a thing that's
supported/in-use? If so is there any chance we could get some action
on https://github.com/microsoft/WSL/issues/830 ?

Rich
[prev in list] [next in list] [prev in thread] [next in thread]