Messages in this thread | | | Date | Mon, 03 Jul 2006 19:02:01 -0700 | From | "H. Peter Anvin" <> | Subject | Re: [klibc] klibc and what's the next step? |
| |
Jeff Bailey wrote: > Le lundi 03 juillet 2006 à 20:46 +0200, maximilian attems a écrit : >> well but busybox is big nowadays and generally compiled against glibc. >> i'm quite eager to kick busybox out of default Debian initramfs-tools >> to have an klibc only default initramfs. those tools are needed atm, >> and there is not enough yet. afaik suse adds sed on klibc with a minimal >> patch and we'd liked to have stat, kill and readlink on klibc-utils. >> >> how about busybox on klibc? > > I made a brief attempt to do busybox on klibc before klcc was working > right for me. I should try that again. In Ubuntu, we already do a > separate build pass of busybox to get just the features that we want, it > would be easy to play with this. > > I'll let you know. It'll take me a couple days - between travelling and > the long weekend, I'm a bit behind. >
I think the main things that aren't in klibc are the userid and the network databases. They should be reasonably easy to stub out.
-hpa - 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/
| |