Re: initrd question

At the moment mkinitrd goes through a big hoo-hah where it tries to determine what precise set of kernel modules are needed to mount the root filesystem, and no more. But I don't understand why we don't just put every possible block device driver / LVM / crypto module / etc. into the initrd. The ramdisk is discarded as soon as the root filesystem is mounted, so at most we're saving a few kilobytes of disk space. At the same time, mkinitrd is massively more complicated than it really needs to be, and initrd images are non-portable between machines[*].