Don't see the problem - I disable automount and do it by hand (mount /dev/sdXn /mnt/whatever) - that's how it was meant to be and that's how I use it. Automount (to _my_ simple mind) is an abolition - what's wrong with a simple 'dmesg|tail' to see what you've got and then manually mount it? (mind you, by this time I just _know_ what the sdX is, so no need for the 'dmesg|tail' ...

Well, that's okay for you and me, for my 75 year old mother I prefer automount. And to be honest, switching external harddrives, usb sticks and sd cards all the time, I'm thankful for automount, too.

For the sake of clarity it might help if people don't use 'automount' to refer to hotplug/udev/hal/udisks/Desktop-Environment based assisted/automatic mounting. 'automount' has an established meaning and refers to linux autofs, Berkeley amd, or original Sun automounter daemons and it gets very confusing when people use the same term to refer to both solutions.

hald interfaces with udev via an "deprecrated interface". Which is of course only deprecated for the sole reason of intentionally breaking hald by removing the interface.

It's not that I choose keeping hald, because it is so great. But as long as there is "legacy" software, which depends on it, it has to stay.

This thread is about modifying the behavior of udev/udisks to make it compatible with the FHS.

"I don't need this and do mounting by hand" is not in any way a helpful addition to this discussion, it's off topic and clutters the thread. Please stop that.

This guy makes a couple of points:

http://www.pappp.net/?p=948

"Where do discs plugged in before a user logs in go? How about if you have multiple interactive users logged in?"

I've a server where I may have one user logged in locally and a different one remotely, both using X. Which one gets control of the one or more flashdrives that I plug in from time to time?

As it happens I've configured static mountpoints in /mnt for them (ETA: and with the option "user" in fstab), but that's because I'm using XFE as my file manager, but it does sound as though the developers are stuck in the single-user mentality.

Sounds like he and I are on the same wavelength.

I realised about the second question almost as soon as I posted it it, that depending on the desktop environment, there will be a notification that a removable device has been inserted, but it's not yet mounted at that stage. So, whichever user acts on that first, it will then be mounted. The issue then becomes permissions-oriented.

You're correct. UDev does have HAL at it's mercy and it won't be long until Lennart and Kay have the udev maintainers remove it entirely and break HAL completely for systemd, which will in turn break DRM content since DeviceKit and it's related projects doesn't fully replace HAL at all, nor can accurately duplicate it's functionality.

I'm honestly surprised that hotplug still works even though it hasn't been updated in the longest time.

I've been holding out hope that mdev, eudev, and hotplug2 can become fully viable and gain some ground in the mainstream.

Time for a new patch ?
14.1 is out and it's udisks2 version is 2.1 .

I will look into it once I have 14.1 up and running and keep you updated on this thread.

So here is a /media patch for the udisks 2.1 SlackBuild source. It builds successfully, but I can't test yet if it works on 14.1. If you are eager to try, I would appreciate your feedback.

As always, after downloading the patch files, the .txt extension must be removed.

Cool, thanks.
I'll try it as soon as possible and report.

About the patch, the medias are mounted in /media, but the mount point is not removed, so i now have /media/usbkey1, /media/usbkey2

Didn't test the link above. Sounds nice.