lkml.org 
[lkml]   [2003]   [Mar]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [BK PATCH] klibc for 2.5.64 - try 2
From
Date
"H. Peter Anvin" <hpa@zytor.com> writes:

> Eric W. Biederman wrote:
> > I don't recall anything about the contents of initramfs being specified.
> > What I was expecting to see was a good set of general purpose policies
> > being included in the default kernel binary. And just replacing
> > /sbin/kinit if I wanted something dramatically different. And that is
> > what I remember Al Viro working on.
> > So I don't think building a very specific /sbin/kinit that
> > only does what the kernel currently does right now is a problem.
> >
>
> It does matter how the initramfs is built. /bin/sh may or may not be necessary
> (but klibc /bin/sh is just over 50K on i386 -- 55K static, whereas glibcx
> /bin/bash is 600K plus the glibc binary), but one of the goals with initramfs is
>
> to at least make it feasible to give someone who comes and asks "I have a
> weird-ass site with 20000 hosts and we need X" a better answer then "well, go
> hack the kernel."

I agree the size of glibc 1.1M and /bin/bash 600K are substantial.
And in most cases if I had to drop one it would be /bin/bash. But 2M
is not that bad if you already need 14M for your modules.

There are still cases where you need to fit through a very narrow pipe
like a floppy, and for those any extra size is a show stopper. But I
also don't see needing a lot of flexibility after coming through a
very narrow pipe.

> /sbin/kinit is a feasible way to do it, but it's important to keep the
> flexibility option open.

I agree, flexibility is important.

My basic point was it sounds like the development process is backwards.
It feels like we are starting big and then going small, instead of the
other way around.

And if starting big keeps the code from being incorporated into
the kernel, I'm not in favor of it. I am in favor of any code that
works.

How I have always expected to use this code is to either use
what is provided in the kernel or replace it entirely.

> > So I think we should have a very small very specific /sbin/kinit
> > that does in user space what the kernel does in kernel space right
> > now. Regardless of klibc the default /sbin/kinit should be gpl'd
> > because we are moving code from code from the kernel into it, and we
> > shouldn't need to double check the licenses to move code from the
> > kernel into it.
>
> Agreed (although it's harder than you think to move code from the kernel into it
>
> -- frequently it has been easier to just write code from scratch; it's cleaner
> that way, too.)

I am not surprised. In kernel and out of the kernel the APIs are noticeably
different.

There are some things like table parsers that I expect would remain unchanged
moving from kernel to user space. Using the information would be quite
different but the same data structures could be used to represent it.

The important thing is when people have an itch to move code they can glance
at it and not have to worry about the license. If something looks hard
at first glance it might not happen. If it looks easy it more likely to happen
even if it is hard :)

> The reason I wanted to use BSD/MIT license only really applies to the library.

Quite reasonable, and I have no problem with BSD/MIT for just the
library as long as it has a GPL compatible license.

Eric

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:33    [W:0.101 / U:0.396 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site