Right. But in doing this we also don't want to bloat the very small
programs/functionality we currently hack directly in
> I'm sure that this will be used in lots of innovative ways that people
> haven't even thought of yet.
Yes, but how many of these require a 'klibc' ? One of the other tiny
libcs is probably a better bet for any sort of 'large' project. IMHO,
the klibc stuff should be just big enough to support the 'normal' cases,
ie stuff we do now and related.
> So, I guess what I'd like to see with the initramfs build system is a
> easy way to build little apps like sfdisk and mkreiserfs against the
> libc it (normally) uses and add them to the ramdisk.
Well, occording to the spec file hpa posted, it's just a cpio(1)
archive, so anything is possible.
-- Tom Rini (TR1265) http://gate.crashing.org/~trini/ - 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/