What we are looking at here is NOT automounting. Automount is an extension to NFS. Like NFS started by Sun Microsystems years ago. It is about mounting NFS mounts only when needed. That is when a user accesses a file inside the mount, that mount is then done. after some time of none usage, an umount is done. The main configuration is in /etc/auto.master. I repeat, that is NOT what we are talking about here.
Understood, I am not talking about NFS, just talking about automatically mounted usb devices. Specifically, a card reader with vfat filesystem.
I do not know what you mean by “enumerating devices”. When a device shows up, the kernel gives it an unique number (MINOR) within the category (MAJOR) it belongs to. The kernel then signals the udev daemon and udevd then creates the device special files like /dev/sdf, /dev/sdf1, /dev/sr0 and the /dev/disk/by-… entries in /dev/ (whatever is needed).
HAL is signaled by udevd. HAL checks if there is an entry for the device in /etc/fstab. When yes, HAL sees this as prove that the device is not to be handled by HAL and does not do anything. When HAL decides that is has to mount, it creates a mount point. For this it creates a directory in /media. The name of this directory will be the volume label of the partition. When no volume lable is available it will use the class of the device (disk, cd, dvd) and when allready in use it will add numbers to this (disk-1) to make them unique (thus, today the mountpoint may be /media/disk and tomorrow, when allready another device is connnected earlier, it may be /dev/disk-1 for tthe same device).
This clears things up for me a bit, thanks.
Hal then does the mount (and here lies our big question: WHERE DO THE FS PARANMETERS COME FROM?).
This is my main issue, if it’s HAL that does the mount, then how do I properly edit the configuration to use shortname=win95? Whatever I edit doesn’t seem to affect the operation of HAL in any significant way.
The mount is not done by any component of your desktop for the simple reason that they do not run as root.
What you’re saying is that gnome-mount could not be responsible for mounting, since it’s not run as root?
HAL communicates with the desktop to find out who must be the owner of the mount point. HAL signals back to the desktop that it mounted and the desktop can then inform the user (e.g. by pop-up window). One of the problems here is that Linux is a multi user system. Thus which one of the running desktop sessions is involved here?
The above to make the whole process a bit more transparent to you. I am not a Gnome user, thus I do not know how the Gnome desktop handles this together with HAL.
From what you said, it seems that the mount is desktop-agnostic, and would probably be mounted by the same daemon/program/process whether on KDE or Gnome. The question is which one? And where does that process store it’s settings.