Jacques Nilo wrote: > > ----- Original Message ----- > From: "arne @ loopback . org" <[EMAIL PROTECTED]> > > 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...
> I do not [understand] the interest of doing that in > an LRP distro. You will need libc > and ld-linux libraries anyway so why not putting them in initrd.gz ? > If you compile statically even with uClibc you would > loose disk space at the end... Oxygen development had busybox compiled with uClibc and this is very useful, actually. It permits the removal of glibc from root.lrp, which means that glibc can be updated just by adding the appropriate glibc package - with appropriate room, of course. My thought, too, is that all packages EXCEPT root.lrp could be put on the network on an FTP host or such like - and thus, not only could the system be updated on the fly, but if you had multiple hosts they would all have their sources updated at the same time, and so on. >From a development standpoint, it is also nice because it shrinks root.lrp down by about half, and also means that loading root.lrp goes faster. Only thing is, MY compiled busybox is contains dozens and dozens of applications - not the minimalist version envisioned by Arne. > > 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 do not understand that. If you need to mount a special driver to read > your boot medium, obviously you cannot have either the original root.lrp > nor my boomod.lrp package on this boot medium. The bootable CDROM is a perfect example of this quandry. Syslinux can boot the CDROM, and load the Linux kernel, and so on - but the "floppy" image is not accessible by Linux (only by syslinux). So once the kernel is loaded and running, all packages must come from the CDROM itself, not from the bootable image. > Well I guess we will have to move to glibc 2.1 or 2.2 > at some point. But we all know that will lead to > a somewhat bigger LRP distro... Oxygen is using glibc 2.1 on floppy in its development versions - and it works well. Converting to glibc 2.2 is a little scary - just how much space would I lose THEN....? At least the upgrade is easy: # rm libc6.lrp # cp /tmp/new/libc6.lrp /mnt/floppy :-) _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
