I have a third party application that I want to run a CentOS4 box that is expecting to access the generic SCSI devices through /dev/sga, /dev/sgb, etc. However, the devices set up by udev are /dev/sg0, /dev/sg1 etc.
Does anyone know what syntax I could use to create a udev rule that creates symlinks sga -> sg0 etc. for each sg[0-N] device?
Thanks
James Pearson
James Pearson wrote:
I have a third party application that I want to run a CentOS4 box that is expecting to access the generic SCSI devices through /dev/sga, /dev/sgb, etc. However, the devices set up by udev are /dev/sg0, /dev/sg1 etc.
just curious, what sort of scsi controller is that? every CentOS 4 system with regular SCSI (or SAS or whatever) that I've seen has created /dev/sda /dev/sdb, etc... only exceptions I've seen are are things like Compaq/HP SmartArray controllers that use /dev/cciss/c0d0
John R Pierce wrote:
James Pearson wrote:
I have a third party application that I want to run a CentOS4 box that is expecting to access the generic SCSI devices through /dev/sga, /dev/sgb, etc. However, the devices set up by udev are /dev/sg0, /dev/sg1 etc.
just curious, what sort of scsi controller is that? every CentOS 4 system with regular SCSI (or SAS or whatever) that I've seen has created /dev/sda /dev/sdb, etc... only exceptions I've seen are are things like Compaq/HP SmartArray controllers that use /dev/cciss/c0d0
Unfortunately, a typo crept into the subject line (which I've now changed) ...
I'm not talking about the block devices (/dev/sda etc) but the generic SCSI devices using the sg (sg.ko) module - which have /dev entries of /dev/sg0, /dev/sg1 etc.
James Pearson
-
James Pearson -
John R Pierce