Comment 38 for bug 281993

Initially, modules are loaded from a ram disk at kernel boot time. The ram disk is created using a ram disk image (initrd) located in /boot and must be updated to reflect module changes at boot time.

@Lucas Gadani: This explains why my system obviously did not need /lim/modules to boot up properly.

I think, a following whould be inserted Adam Dorseys mini howto between steps 7 and 8:
7.1) change to /boot and rename the old initrd: mv initrd.img-$(uname -r) initrd.img-$(uname -r).disabled
7.2) create a new ram disk image: mkinitramfs -o initrd.img-$(uname -r) $(uname -r)

CAVE: I am no kernel guru or anything. If this operation fails, any system can (recoverable) become unbootable. This at least worked for my.

Can some more sophisticated than me can review and prove this proposal, please?