Red Hat Bugzilla – Bug 117005
updfstab: catch-all patterns in configuration file?
Last modified: 2014-03-16 22:42:49 EDT
Description of problem: Shouldn't updfstab have some patterns in its configuration file to match devices not caught by others but where it's clear what the devices do? For example, this entry (it's a USB CF card reader, but it could be anything) from hwconf: class: HD bus: USB detached: 0 driver: usb-storage desc: "unknown" usbclass: 8 usbsubclass: 6 usbprotocol: 50 usbbus: 2 usblevel: 1 usbport: 0 usbdev: 3 vendorId: 0c45 deviceId: 1050 The class, bus, and driver show that this is a USB mass storage device of some sort, so it would be nice if an fstab entry could be added, even if the partition number can only be guessed at. kudzu-1.1.46-1
The matching is done on the SCSI entry, not the USB entry.
Output of /proc/scsi/scsi with card reader inserted: Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: _NEC Model: CD-RW NR-9100A Rev: 108A Type: CD-ROM ANSI SCSI revision: 02 Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: USB MASS Model: STORAGE DEVICE Rev: 0.1 Type: Direct-Access ANSI SCSI revision: 02
Ugh. USB MASS STORAGE DEVICE doesn't really lend itself to any good name. :/
Can you attach /proc/scsi/usb-storage-* when this is attached?
Created attachment 99504 [details] output of /proc/scsi/usb-storage-0/1 with device attached
Unfortunately, that really doesn't have *any* distinguishing data. I suppose we could have a /mnt/stuff entry. :)
As updfstab is no longer used in current releases (removable media mounting is done via HAL, fstab-sync, and gnome-volume-manager), changes to updfstab will almost certainly not be addressed.