Craig White wrote:
On Tue, 2006-04-04 at 16:58 -0500, Mike McCarty wrote:
Anne Wilson wrote:
On Tuesday 04 April 2006 18:54, Matt Arnilo S. Baluyos (Mailing Lists) wrote:
Error trying to open /dev/hdd exclusively ... retrying in 1 second.
There may be other problems, but this one suggests that something, probably
automount, is grabbing the device. Make sure you have closed any file
manager windows, and if a device icon has come onto the desktop, use it to
umount the device.
Erm, not on my machine. I have to use umount from a CLI. Using
the desktop icon results in the disc being ejected.
----
which would probably work because a program such as K3b would call for
it to be inserted and not mount such a disk but rather perform whatever
is needed to erase and start writing.
Now who's speaking out of ignorance? :-)
No, because when K3b calls for the door to close, the automounter
finds it and mounts it. And if it's blank, using this technique
causes the "CD Maker" to start up, preventing K3b from working right.
The only thing that works on my machine is
(1) Insert the disc
(2) If it was blank, wait for the CD Maker to start, then kill it
(3) If it was not blank, wait for it to mount, start a CLI, and umount it
(4) Start or continue with K3b.
I never have approved of auto mouting like this. IMO, MicroSoft products
handle removable media better than UNIX like OSs, especially floppies.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
