[Karmic] mountmanager usability flaws

[Roland Hughes]

Per bug 409039

I made the mistake of choosing /dos as the mount point for my FreeDOS partition instead of /drive_c like I wanted during installation. The FAT-32 extended partition I use for transferring data between other platforms is mounted as /drive_d and I wanted to keep the naming schema consistent. Someone suggested I use MountManager to fix the issue since fstab seems to be of little to no value these days.

1) MountManager wouldn't let me key in a new mount point. I had to manually create a /drive_c directory, then select that directory as a mount point.

2) Somehow it changed the settings on /drive_d (which wasn't even touched) to not automatically mount. I had to manually click on it and provide the root password.

3) It left the /dos directory sitting out there and useless and there was no method I tried which would delete it.

4) Further experimentation got /drive_d to consistently mount, but "root" now owned all of the files even though the settings said "current user" in MountManager. Most likely this was because the mount occurs during system startup and root happens to be what is running.

5) I had to manually go back in and force my username to be both owner and group because even with access set to RWE in MountManager, I could not update or create a file from within a text editor like SciTE or a word processor like LOTUS Symphony.

roland@logikaldesktop:~$ lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10