At first glance it doesn''t seem very hard to do something like this on kernel install: ln -s raid456.ko /lib/modules/2.6.20-1.2933.fc6/kernel/drivers/md/raid4.ko ln -s raid456.ko /lib/modules/2.6.20-1.2933.fc6/kernel/drivers/md/raid5.ko ln -s raid456.ko /lib/modules/2.6.20-1.2933.fc6/kernel/drivers/md/raid6.ko We could have left mkinitrd alone if the %post script for the kernel that combined those three modules into one had done this.
Chuck Ebbert wrote:> At first glance it doesn''t seem very hard to do something like this > on kernel install: > > ln -s raid456.ko /lib/modules/2.6.20-1.2933.fc6/kernel/drivers/md/raid4.ko > ln -s raid456.ko /lib/modules/2.6.20-1.2933.fc6/kernel/drivers/md/raid5.ko > ln -s raid456.ko /lib/modules/2.6.20-1.2933.fc6/kernel/drivers/md/raid6.ko > > We could have left mkinitrd alone if the %post script for the kernel that > combined those three modules into one had done this.Problem is that then, you''re stuck doing that :-) Jon.
Jon Masters wrote:> Chuck Ebbert wrote: >> At first glance it doesn''t seem very hard to do something like this >> on kernel install: >> >> ln -s raid456.ko >> /lib/modules/2.6.20-1.2933.fc6/kernel/drivers/md/raid4.ko >> ln -s raid456.ko >> /lib/modules/2.6.20-1.2933.fc6/kernel/drivers/md/raid5.ko >> ln -s raid456.ko >> /lib/modules/2.6.20-1.2933.fc6/kernel/drivers/md/raid6.ko >> >> We could have left mkinitrd alone if the %post script for the kernel that >> combined those three modules into one had done this. > > Problem is that then, you''re stuck doing that :-)I figured after a few rounds of that you''d vacuum out the crud and put it in mkinitrd where it belongs. :) This would just allow some slack so the two didn''t have to be released in lockstep.