From: "Walter Dnes" <waltdnes@waltdnes.org>
Date: Sun, 25 Mar 2012 17:10:42 -0400
To: alpine-devel@lists.alpinelinux.org
Subject: [alpine-devel] Questions about doing a glibc-based build
Message-ID: <20120325211042.GA29428@waltdnes.org>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)

  This is for experimentation on my part.  Right now, I'm running Gentoo
and have substituted mdev for udev.  For now it looks like Gentoo will
continue to support both openrc and systemd for startup/init.  If it
goes to systemd-only, then udev becomes mandatory.  I don't want to get
into the /usr on / flamewar here.  Let's just say I want a Plan B in the
event that Gentoo gets dragged into systemd-only mode down the road.

  I'm not a developer or a C programmer.  However, as a Gentoo user, I'm
familiar with "make menuconfig" and building the kernel.  Is there a way
for me to get ahold of the Alpine source code, including kernel, and
drop in glibc in place of uclibc?

  I'd probably have to rebuild everything, because it's been linked to
uclibc.  I understand that uclibc has a different internal api from
glibc, which would kill stuff like Flash and proprietary video card
drivers.

-- 
Walter Dnes <waltdnes@waltdnes.org>


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---