http://qa.mandrakesoft.com/show_bug.cgi?id=2846
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WONTFIX |
------- Additional Comments From [EMAIL PROTECTED] 2003-28-07 19:11 -------
Yes, a setuid wrapper could be made for exemple to solve the problem.
I don't know if supermount can be modified safely to release floppy as soon as
an application try to open /dev/fd0 in writing, but it should be possible too
and it could be the best place to fix the problem.
Note: formating a floppy while mounted is impossible, the device is busy, there
is nothing to do here unless umounting the floppy (in root furthermore when
using supermount).
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: REOPENED
creation_date:
description:
The GNOME floppy formatter only works when /mnt/floppy is manually umounted
first. There is nothing to indicate to the user what the problem is when he
tries to format a floppy and it gives a weird error message.
Suggestion: start the floppy formatter with a script that umounts the floppy
(needs suid=root??) first and remounts afterwards.
