[klibc] klibc and what's the next step?

Theodore Tso tytso at mit.edu
Sat Jul 1 17:38:15 PDT 2006

On Sat, Jul 01, 2006 at 05:17:17PM -0700, H. Peter Anvin wrote:
> One of the criticisms I've gotten for klibc has been why I have included 
> dash and a whole bunch of shell utilities when they're not used by the 
> default kernel build.  It certainly hasn't been just to prove a point; 
> as a matter of fact, getting dash to build correctly under Kbuild proved 
> to be surprisingly difficult.  However, by making sure that one can 
> *easily* pull together an interactive environment -- even if one didn't 
> have one from the start -- one has more readily access to a debuggable 
> environment.

Well, I wouldn't be one of those folks.  In fact, how big is dash and
some select set of shell utilities?  If they aren't that big, it might
make sense to include them all the time so that a simple command-line
option on boot is all that's necessary in order to break into a
pre-kinit interactive shell.  That would make the resulting system
more debuggable by definition.  Then all we will would have to do is
make sure the distro's use the kernel-supplied kinit solution, instead
of rolling their own non-standard version.

						- Ted

More information about the klibc mailing list