Code:
root@ws1:~# mkinitrd -c -u -k 3.4.4-custom -m ext:ehci-hcd:uhci-hcd:usbhid -f ext4 -r /dev/rootvg/lvroot -l uk -L -C /dev/sda5 -o /boot/initrd-new.gz
WARNING: could not open /boot/initrd-tree/lib/modules/3.4.4-custom/modules.order: No such file or directory
WARNING: could not open /boot/initrd-tree/lib/modules/3.4.4-custom/modules.builtin: No such file or directory
24820 blocks
/boot/initrd-new.gz created.
Be sure to run lilo again if you use it.
root@ws1:~# ls -l /boot/initrd-tree/lib/modules/3.4.4-custom
total 28
-rw-r--r-- 1 root root 45 Jun 29 18:59 modules.alias
-rw-r--r-- 1 root root 12 Jun 29 18:59 modules.alias.bin
-rw-r--r-- 1 root root 0 Jun 29 18:59 modules.builtin.bin
-rw-r--r-- 1 root root 0 Jun 29 18:59 modules.dep
-rw-r--r-- 1 root root 12 Jun 29 18:59 modules.dep.bin
-rw-r--r-- 1 root root 52 Jun 29 18:59 modules.devname
-rw-r--r-- 1 root root 131 Jun 29 18:59 modules.softdep
-rw-r--r-- 1 root root 49 Jun 29 18:59 modules.symbols
-rw-r--r-- 1 root root 12 Jun 29 18:59 modules.symbols.bin
I haven't tried booting from this new initrd yet, so I don't know whether this is fatal or not, but I was wondering whether the kmod update is going to require changes to mkinitrd and possibly the mod tools that are in the initrd's busybox?
UPDATE 2: I was incorrect. It doesn't prevent booting after all, as I made a typo in the mkinitrd. Sorry all.
