Bug 59068 - updfstab doesn't detect Y-E Data USB floppy disk drive
updfstab doesn't detect Y-E Data USB floppy disk drive
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: kudzu (Show other bugs)
7.2
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-01-30 09:13 EST by Need Real Name
Modified: 2014-03-16 22:25 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-02-13 15:51:49 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)

  None (edit)
Description Need Real Name 2002-01-30 09:13:48 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [de] (X11; U; Linux 2.4.7-10smp i686)

Description of problem:
updfstab doesn't detect Y-E Data USB floppy disk drive.


Version-Release number of selected component (if applicable): kudzu 0.99.23


How reproducible:
Always

Steps to Reproduce:
1.Plug in usb floppy disk drive


Actual Results:  Nothing happens.

Expected Results:  1. updfstab should update /etc/fstab
2. updfstab should create /mnt/floppy/


Additional info:

Line 54 in updfstab.c is buggy:

wrong:
{ "floppy",   CLASS_HD,     0,  0, "USB-FDU"            },

correct:
{ "floppy",   CLASS_FLOPPY, 0,  0, "USB-FDU"            },
Comment 1 Bill Nottingham 2002-01-30 10:01:19 EST
Hm, that works for some floppies here. I suppose it depends on the floppy model
in particular.
Comment 2 Need Real Name 2002-01-30 10:14:26 EST
No problem, simply put two lines into updfstab, one with CLASS_HD, and one with
CLASS_FLOPPY.

In fact, I don't have a Y-E floppy, but a Sony PCGA-UFD5 which identifies itself
as a Y-E floppy. Maybe these devices are a little bit different.
Comment 3 Bill Nottingham 2003-02-13 15:51:49 EST
This should work with current code.

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