Operating Systems > Linux and UNIX
disk full up!!! why???
voidmain:
I have no idea what could be causing your "freeze" problem. Never seen such a thing. But as far as automount. Yes it will automount the floppy if you have it so configured but if you press the eject button while it's mounted you are going to have problems as there is no way the system can tell when you are planning on pressing the eject button. With CDs there is an "eject" command which will unmount the CD before ejecting.
There are several ways you can unmount the disk as a normal user. I would suggest the best way is to add the "user" tag in the options in /etc/fstab in the entry for your floppy. Now since you are using KDE if you have a floppy device ICON on your desktop you should also get the "unmount" option when you right click on it.
I suspect the "freeze" problem might be associated with ejecting the floppy while it is mounted and KDE expects to still see the file system there and it would have to wait for a time-out (could be a very long time). Maybe I've never run across this problem because I always unmount before ejecting.. I don't know if there is a way to set a timeout to a lower setting, or what would even need to be adjusted.
Pantso:
Ah! Unmounting. Might seem like one of those Linux oddities at first, but it's a very important and practical characteristic. It could prove to be a very important feature in a multi-user enviroment as well, where you have several programs and users wanting access to the same medium at the same time.
Basically what mount does is to incorporate or register the medium on the directory tree. And as void main said, never take the medium out of the drive before you unmount because your system would propably freeze.
Calum:
voidmain, thank you for your thoughts however i think i may have inadvertantly handed you the wrong end of the stick,
i use XFce now as my desktop, so cannot have icons on the desktop, now the freezing i experience happens immediately a couple of seconds after i attempt to drag and drop from a /mnt/home/ window onto a /mnt/floppy window, but it only happens sometimes. maybe 20-30% of the time. it also happens in other file browsers too.
it's not an X thing either, and the floppy drive does not spin while doing it either.
do you think this may also be a caching issue? some sort of loop? where the files to be transferred get cached but do not get put on the disk, and maybe the data all back up against itself?
just a wild stab in the dark.
thanks for the thoughts anyway, chaps! :D
voidmain:
Does the same thing happen in KDE? It should have nothing to do with caching because that is all done well below the window manager level and is something that shouldn't even be known to the window manager. If it doesn't have problems copying files to the floppy at a shell prompt or from any other Window manager then I would suggest the problem lies with XFce. Now, since the floppy is a much slower device maybe that is exposing a problem with XFce. Let me know if the problem also exists outside of XFce and I'll do a little research for ya.
KernelPanic:
this is probably completely wrong (is it void main?) but couldnt you use the CLI copy command in a terminal window and copy from /home/calum to /dev/fd0.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version