Marko Vojinovic wrote: > > If there is a DE running, this "something" catches the signal, internal gears > and wheels of DE start clicking, and eventually the device gets mounted using > the hal database. A file manager is opened, and everyone is happy. In case of > Gnome, the gnome-mount does the work (creates a mount point, reads off the > data from hal, mounts the device), and it is called upon from > gnome-vfs-daemon and/or gnome-volume-manager and/or other gnome-* stuff. As > for KDE, the same thing happens, only with some other tools doing the work > (which ones?). > > However, if there in *no* DE running, **nothing happens**. The device does > *not* get mounted automatically, and one has to go about creating the mount > point manually, and doing > > # mount -t something /dev/something /media/something > > by hand, in order to mount the device. After that, only root has access to the > data (without further hassling), and everyone is *not* happy. > > So, which service should be doing this instead of me? > Check and see what happens if you run: gnome-mount -td /dev/something This should work as a normal user from the command line without a DE running. But it may only work for a local login, and not an ssh login, depending on the security settings. There are other options to gnome-mount to give more control of the mounting. If you do not use them, then the HAL rules determine how the drive is mounted. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
Attachment:
signature.asc
Description: OpenPGP digital signature
