Bootloader rootfs

[Andy Green]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:

>> Some bloat is OK if we don't have to pull everything to even get booted,
>> ie, we use a rootfs.  I like uclibc because I used it before with good
>> results, but we shouldn't consider it if it isn't used with our main
>> packages.
> 
> Yeah, it's a reasonably easy choice if we find that glibc is getting
> too heavy. The more such choices we have, the better.

That's my point, it isn't reasonable to redo your own filesystem here
when we can use what we have.  We have already been down the road of
people rolling their own filesystems and so on, it makes problems.

Of course it is not true about having more choices being good to create
and maintain that only do the same thing.

Just use the standard one and save all that time.

>> We should stop this alternate boot filesystem being a project of its own
>> and just make it another (smaller) kind of buildhost rootfs you can get
>> and modify at a package level,
> 
> That's actually my long-term vision for kboot. Right now, it's kind

kboot is a disconnected side issue that can be there or not.  This is
about ANY fallback kernel and rootfs.

I snipped the rest because we are just repeating ourselves.  Summary:

Andy:   Get John to create and maintain a cut-down normal rootfs with
appropriate packages in it for the "recovery" boot.

Werner: New empire of packages, new libc, kboot, special initrd

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFH4oc8OjLpvpq7dMoRAi2DAJ9S9nZxRwwFmFrvdhETFbhWc6o1fQCeI94A
ndVfru/z37HZbJvkz/m2eq8=
=+o+/
-----END PGP SIGNATURE-----