On Mon, Sep 22, 2008 at 10:57:49PM +0300, Andrei Popescu wrote:
On Mon, 22 Sep 2008 14:08:24 -0400 Thomas H. George wrote:
Last month when lilo could not boot a stock 2.6.26-1-amd64 debian
system it was pointed out to me that the initrd.img was too big and
that the solution was to edit /etc/initramfs-tools/initramfs.conf and
change MODULES=most to MODULES=dep. This indeed reduced the size of
the initrd.img from about 9000000 to 5008590 and all was well until
the most recent update of update-initramfs. Now even with MODULES=dep
update-initramfs generates a 7787042 initrd.img and again lilo cannot
boot the system.
Try with
BUSYBOX=no
Something indeed has happened, but I don't think it's initramfs-tools.
My initrd for 2.6.25 is 1,5M and the one for 2.6.26 is 6,2M...
With BUSYBOX=n the initrd.img file size is reduced to 6683876 but bootup
still fails.