Bug 117005 – updfstab: catch-all patterns in configuration file?

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 117005 - updfstab: catch-all patterns in configuration file?

Summary:	updfstab: catch-all patterns in configuration file?

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	kudzu (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-02-27 05:29 EST by Tim Waugh
Modified:	2014-03-16 22:42 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2005-03-31 16:59:41 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
output of /proc/scsi/usb-storage-0/1 with device attached (204 bytes, text/plain) 2004-04-16 20:11 EDT, Tammy Fox	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Tim Waugh 2004-02-27 05:29:14 EST

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

Comment 1 Bill Nottingham 2004-02-27 09:35:58 EST

The matching is done on the SCSI entry, not the USB entry.

Comment 2 Tammy Fox 2004-03-01 09:31:28 EST

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

Comment 3 Bill Nottingham 2004-03-01 22:51:28 EST

Ugh. USB MASS STORAGE DEVICE doesn't really lend itself to any good
name. :/

Comment 4 Bill Nottingham 2004-04-16 00:40:26 EDT

Can you attach /proc/scsi/usb-storage-* when this is attached?

Comment 5 Tammy Fox 2004-04-16 20:11:20 EDT

Created attachment 99504 [details]
output of /proc/scsi/usb-storage-0/1 with device attached

Comment 6 Bill Nottingham 2004-04-16 22:25:30 EDT

Unfortunately, that really doesn't have *any* distinguishing data. I
suppose we could have a /mnt/stuff entry. :)

Comment 7 Bill Nottingham 2005-03-31 16:59:41 EST

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.

Note You need to log in before you can comment on or make changes to this bug.