Perhaps a bit of clarification is in order.
I understand that I can manipulate the order of module loads once I've got a booting a machine. The point is that loading Linux (Redhat in this case) in the configuration in question results in a machine that will not boot, due to the device names are not the same as when the box was installed. Therefore, I can't make new kernels, edit files, etc.
I suppose I should look at a stand-alone boot floppy or some such.
I also have found a few places where changing the source code could produce the desired result, although on this machine changing drivers/scsi/hosts.c results in a kernel that panics. I think that this also precludes building a non-modules version of the kernel.
The point is that there should be a simple way for the average joe to specify these sorts of details about the boot proceedure without resulting to editing kernel sources and/or having a second machine to build kernels for a non-working machine. I suppose what I *really* want is a way to specify the controller order from the LILO prompt, or at least during the install.
- Ken
- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED]