Re: klibc development release

[Rob Landley <landley@trommello.org>]

On Friday 09 August 2002 06:03 pm, Oliver Xymoron wrote:
> On 8 Aug 2002, H. Peter Anvin wrote:
> > Okay, I'm starting to have enough guts about this to release for
> > testing...
> >
> > klibc is a tiny C library subset intended to be integrated into the
> > kernel source tree and being used for initramfs stuff.  Thus,
> > initramfs+rootfs can be used to move things that are currently in
> > kernel space, such as ip autoconfiguration or nfsroot (in fact,
> > mounting root in general) into user space.
>
> Remind me why we'd want this in the kernel source tree when we don't even
> have modutils there?

It's optional: CONFIG_MODULES=n

> Or a real bootloader?

Also optional: cat bzImage > /dev/fd0 (ugly but still works)

> There is no requirement that
> the kernel must be able to build a bootable image with ip autoconf and
> nfsroot, etc. without using external tools.

How about partition detection?  When initramfs goes in that's one of the 
things they're threatening to move to userspace.  Also lots of the hardware 
detection and setup (ACPI, hotplug style PCI probing...)

If that sort of stuff goes into userspace, you may not be able to boot ANY 
linux system without it.

> A minimal 'parse command line
> to mount root and call real init' might be nice, but mostly as an
> example, like the example watchdog code.

See "partition detection in userspace".  How minimal is "minimal"?

> I think a better way to go is to simply roll an initbootutils.tar.gz,
> point to it in the kernel CHANGES, etc., start pulling stuff into it, and
> people will catch on in no time.

Possibly it could be gotten to work before being split off?  And then there's 
the question of upgrading your kernel without upgrading the initbootutils: if 
this never happens, what exactly is the benefit of it being in another 
tarball?  (I.E. how tight is the binding gonna be?  I certainly don't know 
yet...)

Rob