David Douthitt wrote:
> 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. I like net loading, and I don't mind doing so after the system is 98% up and booted, meaning as an RCDLINKS="2,S99" sort of netloading snarf script. > > 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....? Personally, I think the boot diskette is overtly generic. I must have got back about 100k after I deleted all those .o modules I didn't need. This is the backlash from a one size fits all mindset. Ok, so nobody looks forward to maintaining a whole bunch of versions of their release, but we have no web based root.lrp/modules.lrp creator to make a custom boot setup. How hard would it be to click some check boxes? I can't believe how much space I have on my boot floppy right now, about 109KB. Oh, and David, does ipkg need a umt-boot fuction call in the space() function? It's leaving the floppy mounted. And ntop seg faults. Regards, Matthew > 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
