On Thu, Nov 08, 2001 at 09:45:33PM +0100, Jacques Nilo wrote: > > Using a Linux-specific initrd.gz you're stuck. Also, what's the point > > of root.lrp if initrd.gz contains everything? > Well I think initrd.gz should contain as few things as possible. In my > proposal it boils down basically to libc6, ld-linux, ash, busybox, sed > and root.linuxrc.
I would go a step further. make a minimal busybox only containing very few applets(tar,msh as shell,mount,ls,cat,...) And link it statically with uClibc. This will result in a quite small binary and you don't need to include a big libc... > That is why you really don't need to back-up this as you would need it > for a standard package with config files and the like. And I also do > not see the need to make modification to root.linuxrc in the LRP > environnement: there is not reason to change this script outside of LRP > development. > My only concern with this is the initial module loading introduced by > Charles in dachstein. But I think I have found a solution to take care > of this. See previous post. The Problem with your previous post is, that you can not load the loadmod.lrp from the boot medium cause you need the modules from there to access your boot medium. I would prefer to put it into the kernel, this would lead to a few customed kernels, but only a few. As i want to concentrate my work on LRP for Systems with CD,harddisk or flashdisk i have no Problem with a larger kernel. My main Problem is to have it the size to fit on a floppy. But if we do not use a embedded libc we will run into problems anyway, as fewer programs will support glibc-2.0.7 and we have to switch to another libc. This will break the floppy stuff (as using kernel 2.4 might). > Jacques > > --arne _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
