Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 Apr 2007 21:15:22 -0400
From:      "Dave" <dmehler26@woh.rr.com>
To:        <freebsd-questions@freebsd.org>
Subject:   Re: locking down scsi device id's in 6.2
Message-ID:  <001701c77d69$360a20e0$0200a8c0@satellite>
References:  <000501c778a1$769989b0$0200a8c0@satellite> <20070407124555.3243bbcb@p4> <000501c7797b$961a9010$0200a8c0@satellite> <20070409072701.0687c6cd@p4>

next in thread | previous in thread | raw e-mail | index | archive | help
Hello,
    My thanks to everyone who has helped thus far with this situation. I've 
gone over scsi(4) and have added the below to device.hints:

hint.sa.0.at="scbus0"
hint.sa.0.target="5"
hint.sa.0.unit="0"
hint.cd.0.at="scbus0"
hint.cd.0.target="0"
hint.cd.0.unit="0"
hint.cd.1.at="scbus0"
hint.cd.1.target="1"
hint.cd.1.unit="0"

camcontrol devlist shows:
<Quantum DLT4000 D996>             at scbus0 target 5 lun 0 (sa0,pass0)
<LITE-ON LTR-48246S SS06>          at scbus2 target 0 lun 0 (cd2,pass1)
<LITE-ON DVDRW SOHW-1633S BS0K>    at scbus2 target 1 lun 0 (cd3,pass2)

I used the wired example, but my device didn't wire. Any suggestions as to 
what i missed?
Thanks.
Dave.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001701c77d69$360a20e0$0200a8c0>