IMHO what is called “automounter” for years in Unix/Linux and is configured starting with /etc/auto.master (it mounts (NFS) partitions when one needs the data inside that partition) is completely different from what a lot of people here call automounting.
They mean the actions taken by HAL (replaced newly by, sorry forgot the name), on behalf of a desktop when USB storage devices are connected to a system. HAL mounts inside /media (hard coded). See also SDB:Basics of partitions, filesystems, mount points - openSUSE.
Hi Henk, thanks for the clarification - I will check out hal/udev.
There still must be some interplay between the auto.master and udev, because modifying auto.master in the manner I described seems to break the function meant to be performed by udev… I’ll get to the bottom of it though.
There is a big difference between udev and the rest. the udevd sees that the special files in* /dev/* are created. These are directly related to (simulated) hardware. When it is about storage, the the special files in /dev/ can be used for a mount (regardless if this mounting is done through Hal or not). But you can also mount using other things then special files in* /dev*, think about an NFS mount using a <Host>:<directory> expression.
It is not exactly clear to me why configuring the automounter influences HAL (and that is one of the reasons I answered to this, being curious ;)). But it could be related to the fact that HAL does not handle special files that are allready in* /etc/fstab*. The idea behind it is imho that when there is an entry in* /etc/fstab* then the sysadmin allready claims he knows what should be done, thus there is no task for HAL.
EDIT: I forgot to give you a welcome here on the forums. Seeing now that you have two posts, the start of this thread must have been your first post. Welcome again and enjoy.