From: Michael Tokarev <mjt@tls.msk.ru>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
klibc@zytor.com, torvalds@osdl.org, akpm@osdl.org
Subject: Re: Merge strategy for klibc
Date: Tue, 21 Mar 2006 15:39:38 +0300 [thread overview]
Message-ID: <441FF40A.1050501@tls.msk.ru> (raw)
In-Reply-To: <441F0859.2010703@zytor.com>
H. Peter Anvin wrote:
> Okay, as of this point, I think klibc is in quite good shape; my
> testing so far is showing that it can be used as a drop-in replacement
> for the kernel root-mounting code.
[]
> Thus, it's not clear to me what particular approach makes most sense for
> pushing upstream.
Why this needs to be "pushed" upstream in the first place? Isn't it
simpler/easier/whatever to just require klibc to be present on the
build system for kernel? If klibc is "sufficiently" independent of
the kernel (is it? I see no reason it shouldn't), why it should go
with kernel? Just point your CONFIG_INITRAMFS_SOURCE to some klibc
directory tree and be done with it, no need to distribute/build
klibc with kernel..
Thanks.
/mjt
prev parent reply other threads:[~2006-03-21 12:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 19:54 Merge strategy for klibc H. Peter Anvin
2006-03-20 20:19 ` Jan-Benedict Glaw
2006-03-20 21:24 ` H. Peter Anvin
2006-03-20 20:22 ` Al Viro
2006-03-20 21:17 ` [klibc] " H. Peter Anvin
2006-03-20 20:54 ` Ingo Oeser
2006-03-20 22:09 ` Roman Zippel
2006-03-22 0:27 ` H. Peter Anvin
2006-03-22 14:47 ` Antonio Vargas
2006-03-22 16:11 ` H. Peter Anvin
2006-03-21 12:39 ` Michael Tokarev [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=441FF40A.1050501@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=akpm@osdl.org \
--cc=hpa@zytor.com \
--cc=klibc@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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