Barf wrote:
Instead the "solution" you present is to let the operating system (udev) automatically mount the file system, regardless of the error messages. Mounting a file system is a different thing from "fixing" it, and I get pretty cold feet by just ignoring the errors.
To be honest, I couldn't give a stuff about the error messages if the remote automounted on all Linux systems. But on my computer, it mounts on MX18.3 but not on the forthcoming MX19. It used to mount on PCLinuxOS but now it does not. And you said that it no longer mounts on Fedora. So it was worth looking at both successful and failed mounts, and checking for differences.
After getting no help with requests to a number of sites, I managed to get it to automount using bits and pieces of knowledge picked up from various online searches, and a little guesswork. Clearly, the matter is of little interest outside of a handful of Linux users who also use theses remotes.
Anyway, I did have to make changes to the system to get them to mount automatically so that I can use them. And the other side to it was that I also had to change a setting in RMIR itself as it no longer autodetected the plugged-in remote, this was the first time I'd ever had to do it manually, and that took me a while to work out.
I'd like to smooth off one or two rough edges. I'd particularly like to find a way to get the remotes mounted to the current user, not a named one. Anyway, the link to the PCLOS site is adequate for now. If I can sort out the remaining questions in my mind, I'd like to do either a comprehensive document or a sticky, and all the old stuff can be deleted.