On Tue, Sep 18, 2007 at 01:08:10PM -0700, David Miller wrote:
> From: "H. Peter Anvin" <[EMAIL PROTECTED]>
> Date: Tue, 18 Sep 2007 12:27:04 -0700
>
> > Well, what I was referring to here, of course, was the initramfs
> > integrated in the kernel image, so it all comes out of the kernel build
> > tree and produces a single bootable image. The fact that part of it
> > contains userspace code is in that way invisible.
> >
> > That was kind of the point here, and the only reason for pushing klibc
> > into the kernel build tree at all. Under the "distros use external
> > initrd anyway" school of thought, whatever libc used for that can be
> > external anyway.
>
> Sounds good to me :)
Except there seems to be great resistance to include userland code in the
kernel as demonstrated at last KS. Or this is maybe just a single vocal
person and the topic were brought up late?
Anyway - if we again consider klibc I will do my best to make the
build stuff as smooth as possible.
Sam
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
