From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org,
viro@parcelfarce.linux.theplanet.co.uk, greg@kroah.com,
bos@serpentine.com, linux-raid@vger.kernel.org
Subject: Re: [PATCH] klibc update
Date: Tue, 16 Mar 2004 11:34:10 -0500 [thread overview]
Message-ID: <40572C82.6020505@pobox.com> (raw)
In-Reply-To: <20040316005229.53e08c0c.akpm@osdl.org>
Andrew Morton wrote:
> Jeff Garzik <jgarzik@pobox.com> wrote:
>
>>Too big to post,
>>
>> http://www.kernel.org/pub/linux/kernel/people/jgarzik/patchkits/2.6/2.6.5-rc1-klibc1.patch.bz2
>> or
>> bk://kernel.bkbits.net/jgarzik/klibc-2.5
>>
>> IIRC, this is: my update of Bryan O'Sullivan's update of Greg KH's
>> update of my merge of hpa's and viro's hacking :)
>>
>> WRT overall klibc merge: when it can do md RAID autorun, it's
>> mergeable. And didn't somebody write a tiny mdctl program...
>
>
> It's so long since klibc was discussed (ie: more than five minutes ago)
> that I forget the reasons why it should be delivered via the kernel tree.
>
> Remind me please?
Several reasons. The big one in my mind is, it will be delivering
pieces without which the kernel will not boot, so you really really want
to keep that software in sync with the latest kernel... at least until
all the details are worked out. Otherwise version skew will as we
remove code from the kernel and move it to userspace will be painful --
users would be rebuilding their external klibc trees just about every
day, as code was moved from kernel to early-userspace.
Jeff
prev parent reply other threads:[~2004-03-16 16:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 7:46 [PATCH] klibc update Jeff Garzik
2004-03-16 8:52 ` Andrew Morton
2004-03-16 15:37 ` Greg KH
2004-03-16 19:10 ` Andrew Morton
2004-03-16 19:16 ` Jeff Garzik
2004-03-16 19:24 ` Greg KH
2004-03-16 19:32 ` Jeff Garzik
2004-03-16 19:53 ` Andrew Morton
2004-03-16 20:02 ` Jeff Garzik
2004-03-16 20:11 ` Bryan O'Sullivan
2004-03-16 20:19 ` Sam Ravnborg
2004-03-16 16:34 ` Jeff Garzik [this message]
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=40572C82.6020505@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=bos@serpentine.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).