On Thu, 2010-09-30 at 23:40 +0200, KP Kirchdoerfer wrote: > > > > Agreed. I did not intend this comparison to be exhaustive, just a > > starting point... > > That's how I understood, and hoped to say in my response. OK, good; I was just checking you understood my intention...
> > IMHO the more important question is "what should be added to kmodules?". > > As long as we did have a floppy only versin in mind, we've been very > restrictive adding modules to save space for the floppy image. > This can be changed, as we are not forced to fit to a floppy any more. Agreed. You may remember that Andrew suggested generating moddb.lrp at first boot by interrogating the hardware and extracting the needed entries from modules.tgz. Wouldn't that solve the problem of deciding what to add to kmodules? Personally, for my development testing, I have been using a "full" moddb.lrp containing every .ko in modules.tgz but that is 10x the size of the current moddb.lrp (6666285 versus 665012 bytes) and takes a long time to load. IMHO we should still try to keep the space requirements relatively low, both on the install media and on the RAM disk. Part of my thinking for buildimage.pl was to let us create alternative disk images for specific, common hardware platforms (like ALIX) where the devices are known so the modules can be selected carefully and moddb.lrp kept small. dMb ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ leaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-devel
