On Wed, 2010-10-20 at 17:40 +0200, Dj YB wrote: > On Wednesday October 20 2010 14:03:31 Sonic wrote: > > On 10/20/2010 11:36 AM, Dj YB wrote: > > > sorry for the misunderstanding. > > > the same mount point they automount now. > > > /media/PARTITION-LABEL > > > > In that case, you don't need an fstab entry. > > Open KDE System Settings > Removable Devices. > > Select 'Enable automatic mounting of removable media' > > Select the sub-entries you find necessary and add any device specific > > exceptions in the list below. > > that is already configured that way, the problem arise when there is an > abnormal disconnection and the mount point is not deleted. > resulting in the need to create a new mount point next time. > for example: > inserting usb device YB-PORTABLE and disconnecting abnormally (e.g. system > crash) > the mount point /media/YB-PORTABLE remain. > reconnecting usb device a new mount point will be created /media/YB-PORTABLE-1 > this is not good since all links point to /media/YB-PORTABLE/ I have the same problem from time to time, though the circumstances are not completely clear, i.e. I work a lot with a pendrive and am always very careful to mount/umount (via the Device Manager, and watching the confirmation icon in the panel when unmounting). Nevertheless, every once in a while the unmount seems to leave an undeleted mount point behind, as you say. Furthermore, the mountpoint can't be deleted even by root as the system seems to think it's still busy. Using 'fuser' shows no active processes holding it open, but I've found that logging out will enable root to delete the mountpoint. Something makes me think this is all GVFS's fault, but maybe I have a suspicious mind. In any case, it's a PITA. poc _______________________________________________ kde mailing list kde@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
