Bug 1030 - mtools has trouble reading msdos disks
Summary: mtools has trouble reading msdos disks
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mtools
Version: 5.2
Hardware: alpha
OS: Linux
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-02-03 00:10 UTC by ehm
Modified: 2013-09-04 14:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-03-29 21:39:42 UTC

Attachments (Terms of Use)

Description ehm 1999-02-03 00:10:04 UTC
I tried all mtools versions shipped with RH 5.0 5.1 and 5.2.
I configured the /etc/mtools.conf file by hand.
I ruled out the disk drive and disks as a source of error.
I tried compiling mtools from the source with both gcc, and
egcs, makes no difference.
I tried tweaking the makefile with different compiler
options (eg. no optimization, etc...).  No difference.
Actually it could read the disks with mdir, but it
complained of file io errors when I tried to run mcopy.  The
same files could be read on i386 machines with the same
version of mtools.  The mtools work fine on our i386
machines, just doesn't want to work on our Alphas (we have
two, both running RH 5.2).  Any help is appreciated.

Comment 1 visser 1999-03-09 07:36:59 UTC
check the write permission on /dev/fd0
(you'll probably find that mtools works fine if you are logged in as
a crude workaround is: su root, chmod o+w /dev/fd0, but be aware
that this makes the floppy writable by everyone...

Comment 2 Preston Brown 1999-03-29 21:39:59 UTC
this has been fixed in the latest version of mtools in RawHide.  If
you would like, you can get a SRPM from there and compile it on 5.2,
or you can wait until Red Hat Linux 6.0 is released, which will have
the fixed mtools included.

Comment 3 CFME Bot 2013-09-04 14:33:44 UTC
Commit pushed to master at https://github.com/ManageIQ/cfme

Remove padding from custom logo in new CFME banner

Issue #1030
Bug 1001784

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