From: Sam Ravnborg <sam@ravnborg.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: klibc - another libc?
Date: Sat, 10 Jun 2006 08:13:28 +0200 [thread overview]
Message-ID: <20060610061327.GD8120@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0606100257550.17704@scrub.home>
> Well for now you pretty much just moved code, that was in the kernel
> before. What I'm trying to find out is what is coming next. How does e.g.
> udev or modules fit into the picture?
udev and module-init-tools fits nicely with the kernel. I never have
understood this 'keep-everyhig-separate' mantra. Just see how many
people had troubles with missing module-init-tools or people having
troubles with non-backward compatible udev.
> For -mm that's fine, but do you seriously expect it to get merged like
> that. Again, what makes klibc so special, that it doesn't have to follow
> standard rules?
So part of what you ask for is a set of incremental patches that shows
all the kernal modifications?
That should be doable with some effort but unfortunately I'm not up to
the task.
Sam
next prev parent reply other threads:[~2006-06-10 6:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 8:51 klibc - another libc? 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
2006-06-11 0:21 ` Roman Zippel
2006-06-10 1:15 ` Roman Zippel
2006-06-10 6:13 ` Sam Ravnborg [this message]
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=20060610061327.GD8120@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.