[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<BN7PR21MB16844C6415A2C8A365FA5523E09F0@BN7PR21MB1684.namprd21.prod.outlook.com>
Date: Sun, 14 Jun 2020 20:43:35 +0000
From: John Starks <John.Starks@...rosoft.com>
To: "musl@...ts.openwall.com" <musl@...ts.openwall.com>
Subject: RE: [EXTERNAL] Re: Advocating musl to in windows subsystem and
OS X
> From: Markus Wichmann <nullplan@....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.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
