|
|
Subject: mcopy a: 'stuck' after initial fail ?
From: problems@gmail
Date: 11/17/2007 10:27:46 AM
If I do a
mcopy <filID> a:
without a diskette inserted, I obviously get the error message.
But ! when I then insert a good diskette, where
mdir a:
is OK, I get: : "Can't open /dev/fd0: Read-only file system
Cannot initialise 'A': "
Also mount ..... shows 'Read-only'.
This is on FC1. Why does mature software still have bugs ?
Probably most new boxes don't even have fd0?
I can't reboot and lose all my setting, just to clear this
bug and I need to move stuff via fd0 to another box.
What should I do ?
== Chris Glur.
Subject: mcopy a: 'stuck' after initial fail ?
From: Bob Hauck
Date: 11/17/2007 12:28:17 PM
["Followup-To:" header set to comp.os.linux.misc.]
On Sat, 17 Nov 2007 10:27:46 -0600, problems@gmail <problems@gmail>
wrote:
> But ! when I then insert a good diskette, where
> mdir a:
> is OK, I get: : "Can't open /dev/fd0: Read-only file system
> Cannot initialise 'A': "
What are the permissions on /dev/fd0? Is the write-protect tab
activated on the floppy?
> This is on FC1. Why does mature software still have bugs ?
Because it does, but I'm doubtful you've found one in this case.
--
-| Bob Hauck
-| "Reality has a well-known liberal bias." -- Stephen Colbert
-| http://www.haucks.org/
Subject: mcopy a: 'stuck' after initial fail ?
From: Bill Marcum
Date: 11/17/2007 3:22:05 PM
On 2007-11-17, Dave {Reply Address in.Sig} <noone$$@llondel.org> wrote:
> In message <1195316841.296475@vasbyt.isdsl.net>, problems@gmail wrote:
>
>> If I do a
>> mcopy <filID> a:
>> without a diskette inserted, I obviously get the error message.
>>
>> But ! when I then insert a good diskette, where
>> mdir a:
>> is OK, I get: : "Can't open /dev/fd0: Read-only file system
>> Cannot initialise 'A': "
>>
>> Also mount ..... shows 'Read-only'.
>>
>> This is on FC1. Why does mature software still have bugs ?
>> Probably most new boxes don't even have fd0?
>> I can't reboot and lose all my setting, just to clear this
>> bug and I need to move stuff via fd0 to another box.
>>
>> What should I do ?
>>
> Have you tried remounting fd0 as r/w? Aer you sure the write-protect tab
> isn't set wrong on the disk itself? It could even be a fault in the drive
> that thinks it is.
>
mdir and mcopy don't require fd0 to be mounted. It could be the root
filesystem that needs to be remounted rw.
|