initramfs and where user space truly begins

Posted Jul 13, 2006 15:49 UTC (Thu) by dlang (guest, #313)
In reply to: initramfs and where user space truly begins by nix
Parent article: initramfs and where user space truly begins

nothing says that your initramfs can't have some programs with klibc and some whilt glibc (although that does waste some space)

they are working on getting the programs that you mention to run with klibc so it's a temporary problem (and one that will be easier to fix once klibc is included with the kernel, which will ease the maintinance burden that's involved with tracking kernel changes, allowing for more time to be spent on any changes to klibc that need to be done)

to post comments

initramfs and where user space truly begins

Posted Jul 13, 2006 16:26 UTC (Thu) by nix (subscriber, #2304) [Link] (1 responses)

IIRC Rob Landley was using words like 'no chance' regarding getting large parts of busybox to work (please correct me if I'm talking nonsense, Rob, my memory is hazy right now due to insomnia).

initramfs and where user space truly begins

Posted Jul 14, 2006 5:09 UTC (Fri) by dlang (guest, #313) [Link]

not all the work needs to be done by Rob or the busybox developers

remember that maintaining a large patch out-of-kernel is a significant drain on a projects resources, once it can move into the kernel that drain is stopped and the time can be spent on other things, including (in this case) plugging the holes tha prevent it from working with more apps (to a large degree anyway, they don't want to have to support every function call forever)