KEYofR wrote:
> Also a question about the udev rules [...] if you detect a device by vendor foo on scsi
You're right -- some of the udev rules posted above are overly general. You can make them more specific by specifying the model of drive, or even the drive serial number if you want to be that specific.
Here's the contents of my udev rule file, "/etc/udev/rules.d/50-fix_usb_hd.rules". Notice the ATTRS{model}, specifying the drive model.
KEYofR wrote:
> Also a question about the udev rules [...] if you detect a device by vendor foo on scsi
You're right -- some of the udev rules posted above are overly general. You can make them more specific by specifying the model of drive, or even the drive serial number if you want to be that specific.
Here's the contents of my udev rule file, "/etc/udev/ rules.d/ 50-fix_ usb_hd. rules". Notice the ATTRS{model}, specifying the drive model.
# /etc/udev/ rules.d/ 50-fix_ usb_hd. rules ="scsi" , ATTRS{vendor} =="Seagate" , ATTRS{model} =="FreeAgentDes ktop", RUN+="/ usr/bin/ usbhdfix %k"
SUBSYSTEMS=
You can display the drive's model name (and other drive-specific stuff that you could query on) with this command:
udevinfo --attribute-walk --name=/dev/sdc
(where /dev/sdc is where your drive's currently located)