From: Sam Ravnborg <sam@ravnborg.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Roman Zippel <zippel@linux-m68k.org>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: klibc - another libc?
Date: Sat, 10 Jun 2006 19:28:07 +0200 [thread overview]
Message-ID: <20060610172807.GA15818@mars.ravnborg.org> (raw)
In-Reply-To: <448AF226.7060003@tls.msk.ru>
On Sat, Jun 10, 2006 at 08:24:06PM +0400, Michael Tokarev wrote:
> Embedded folks are using uclibc or dietlibc - i see no reason for another
> "more small" libc for booting, regular tools (linked against uc or diet)
> can be used just fine.
Then they can just use uclibc or dietlibc. There is nothing that
prevents you from providing everything fr the initramfs.
klibc is the default choice so the kernel can provide a functional set
of programs. Without klibc it would be almost impossible to factor out
all the code that ought to run in userspace but are part of the ekrnel
because there were no other way to do it.
And klibc being temporary is some odd argument. Why should it be
temporary. Are there other alternatives when bundling a 'libc' with the
kernel?
Sam
next prev parent reply other threads:[~2006-06-10 17:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 8:51 Michael Tokarev
2006-06-07 21:17 ` H. Peter Anvin
2006-06-07 22:42 ` Roman Zippel
2006-06-08 15:32 ` H. Peter Anvin
2006-06-09 14:13 ` Roman Zippel
2006-06-09 19:02 ` H. Peter Anvin
2006-06-09 19:13 ` Michael Tokarev
2006-06-09 19:29 ` H. Peter Anvin
2006-06-10 1:28 ` Roman Zippel
2006-06-10 16:24 ` Michael Tokarev
2006-06-10 17:28 ` Sam Ravnborg [this message]
2006-06-11 0:21 ` Roman Zippel
2006-06-10 1:15 ` Roman Zippel
2006-06-10 6:13 ` Sam Ravnborg
2006-06-10 23:37 ` Roman Zippel
2006-06-13 2:31 ` Paul Dickson
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=20060610172807.GA15818@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®