Re: locking down scsi device id's in 6.2

2007-04-14 Thread Robert Marella
On Sat, 14 Apr 2007 01:51:12 -0400 Dave [EMAIL PROTECTED] wrote: Hi, Thanks. Still no good, basically it just brought me back to where i was. Do you know anyone else who might have an idea on this? Thanks for all your help. Dave. Perhaps I have been leading you on a wild goose

Re: locking down scsi device id's in 6.2

2007-04-14 Thread Dave
PROTECTED] To: Dave [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Saturday, April 14, 2007 8:42 PM Subject: Re: locking down scsi device id's in 6.2 On Sat, 14 Apr 2007 01:51:12 -0400 Dave [EMAIL PROTECTED] wrote: Hi, Thanks. Still no good, basically it just brought me back to where i was. Do you

Re: locking down scsi device id's in 6.2

2007-04-13 Thread Robert Marella
On Fri, 13 Apr 2007 13:49:43 -0400 Dave [EMAIL PROTECTED] wrote: Hi, Either i've got a syntax error or my devices aren't wiring obeying /boot/device.hints. I've added: hint.scbus.0.at=ahc0 to my config. The tape drive is consistent on scbus0, target5, lun0, if i change it's target

Re: locking down scsi device id's in 6.2

2007-04-13 Thread Dave
Hello, Thanks for your reply. Please see below for responses. - Original Message - From: Robert Marella [EMAIL PROTECTED] To: Dave [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Friday, April 13, 2007 9:06 PM Subject: Re: locking down scsi device id's in 6.2 On Fri, 13 Apr 2007 13:49

Re: locking down scsi device id's in 6.2

2007-04-13 Thread Robert Marella
On Fri, 13 Apr 2007 21:39:42 -0400 Dave [EMAIL PROTECTED] wrote: Hello, Thanks for your reply. Please see below for responses. Here is my add-ons to /boot/device.hints: # custom devices hint.scbus.0.at=ahc0 #find this with dmesg hint.sa.0.at=scbus0 hint.sa.0.target=5

Re: locking down scsi device id's in 6.2

2007-04-12 Thread Dave
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

Re: locking down scsi device id's in 6.2

2007-04-12 Thread Robert Marella
On Thu, 12 Apr 2007 21:15:22 -0400 Dave [EMAIL PROTECTED] wrote: 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

Re: locking down scsi device id's in 6.2

2007-04-09 Thread Robert Marella
On Sat, 7 Apr 2007 21:16:50 -0400 Dave [EMAIL PROTECTED] wrote: (Format recovered: Please do not top post) On Fri, 6 Apr 2007 19:15:27 -0400 Dave [EMAIL PROTECTED] wrote: Hello, I've got a situation where three devices, one a scsi tape drive and the other two ide burners under scsi

Re: locking down scsi device id's in 6.2

2007-04-07 Thread Robert Marella
On Fri, 6 Apr 2007 19:15:27 -0400 Dave [EMAIL PROTECTED] wrote: Hello, I've got a situation where three devices, one a scsi tape drive and the other two ide burners under scsi emulation with atapicam are fighting for scsi id's and i'd like to lock them down to specific id's. When the tape

locking down scsi device id's in 6.2

2007-04-06 Thread Dave
Hello, I've got a situation where three devices, one a scsi tape drive and the other two ide burners under scsi emulation with atapicam are fighting for scsi id's and i'd like to lock them down to specific id's. When the tape drive isn't plugged in the burners get 000 and 010 scsi ids, but