On Sat, 18 Mar 2006 07:22:44 -0600 James Bottomley wrote: > On Sat, 2006-03-18 at 01:24 -0500, Douglas Gilbert wrote: > > Ah, if scsi_debug is a module, nothing is going to > > load it automatically (at least the PCI subsystem > > won't load it). However if it is built in then > > it will "steal" /dev/sda (if some other SCSI LLD > > hasn't already got it). That would then cause > > a SATA driver to get /dev/sdb ... That is enough > > to cause a kernel parameter like "root=/dev/sda8" > > to flounder and give the "could not find root filesystem" > > error. > > Is there actually any purpose for not compiling scsi_debug as a module? > i.e. isn't the problem really that we simply shouldn't allow it to be > built directly into the kernel and it should only be compilable as a > module? I don't see a need to be that restrictive about it. As long as SCSI_DEBUG is last, it won't affect the device order (boot or other devices), which is the problem IMO. Yes, the scsi-debug device(s) could become different devices depending on what other SCSI devices were found, so maybe someone's scripts would have to change (scripts should be flexible :). But that would also happen if SCSI_DEBUG=m. Anyway, I'll let Doug/James decide. --- ~Randy - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
