On Monday 11 December 2006 20:57, maximilian attems <[EMAIL PROTECTED]> wrote: > > The major issue is that the depmod > > program is simply larger than a full modules.dep file when compressed. > > Given that most sane configurations will not have the complete set of > > kernel modules (I use modules=list for a very small set of modules) the > > modules.dep file will often be smaller than depmod when uncompressed. > > > > Using the modules.dep file saves initramfs size in every case, and saves > > memory in some common cases. > > first of all MODULES=most is the default, so that is the common case! > the case you brought up had a small 1k difference, > so that's not the place to optimize.
MODULES=most will give a smaller modules.dep than the one that lives under /lib/modules. The modules.dep that comes from /lib/modules will take up less space when compressed than depmod, so the MODULES=most case will save even more space. > > > i really don't see your antipathy on BUSYBOX=n > > > there you can get rid of glibc which is taking a _huge_ > > > place on initramfs. > > > > I use lvm root over a software RAID-1 on all my important machines (apart > > hmm ok, i thought you were squeezing for some embedded board. Just generally squeezing because I don't like wasting space. > sure by default any etch user will have glibc on initramfs due to > busysbox, udev and module-init-tools. OK, as the default requires glibc therefore doing everything in busybox will save space. Long-term we should consider getting modprobe and other programs included in busybox (modprobe used to be there for 2.4.x, we can do it again). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]