> (Are you subscribed to the list or do we need to CC you?) I subscribed. > No problem. For some questions #debian-boot on irc.debian.org (OFTC) may > be an option. If you don't get an answer there, try the list.
OFTC? (Sorry ...) > > The biggest problem I had last time around was that after manually > > loading all the modules and installing the system on the medley device, > > the initrd image was created without the medley driver and the system > > wouldn't boot! > > This can be solved relatively easily now by including the following > command in a script once you are certain the module will be needed: > register-module -i <module> Except that the individual ataraid modules (hptraid.o, medley.o et al.) are no longer used in 2.6 - dmraid covers them all. I don't think dm-mod is actually necessary to identify and read from the arrays; if so it would not need including in the initrd. What would be necessary is the dmraid -s -c command to identify the array(s), then some kind of scripting to use /dev/mapper/<raid-device> (or maybe such device would then be found/used automatically?). I hope that makes sense. The more you learn, the more you realise you don't know. CC -- The mailserver at terminalarrogance.com runs a whitelist. If you wish to contact me off-list, I am known as rantingman at the popular webmail service run by Google. -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.10.3/395 - Release Date: 21/07/2006
