SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
go to the storage media section
right click on the one for your USB stick->Properties->Mounting tab
It should tell you where it mounted it (eg. /media/disk).
You can also run the mount command (with no options) in a terminal as your normal user before and after the USB drive is mounted. Note the difference, and this should tell you where it is mounted.
To automount things, I followed the HAL sticky and you must add device nodes and corresponding mount points where they are to be mounted to your '/etc/fstab'. How is that wrong ?
To automount things, I followed the HAL sticky and you must add device nodes and corresponding mount points where they are to be mounted to your '/etc/fstab'. How is that wrong ?
Well I didn't do either of those things and HAL auto-mounts all the removable media I can throw at it. There are no USB devices in my /etc/fstab file.
i didn't add anything to /etc/fstab and everything mounts for me too
Just to clear some things up. From the 'man fstab';
Quote:
FSTAB(5) Linux Programmer's Manual FSTAB(5)
NAME
fstab - static information about the filesystems
SYNOPSIS
#include <fstab.h>
DESCRIPTION
The file fstab contains descriptive information about the various file
systems. fstab is only read by programs, and not written; it is the
duty of the system administrator to properly create and maintain this
file.
HAL does not write to the '/etc/fstab' file either as noted by the 'static label' and the definition.
The /dev/cdrom line in /etc/fstab is commented out by default, as it interferes
with HAL. HAL defaults to on, so if you do not wish to use it, you will need
to chmod -x /etc/rc.d/rc.hald and uncomment the /dev/cdrom line in /etc/fstab
Note that HAL will honor settings in /etc/fstab if a device is present there,
so you could technically have removable devices defined in /etc/fstab, but if
the fstab settings do not allow normal users to mount them (with the "user" or
"users" option), then HAL/dbus will not allow them to be mounted either.
Also note that you will need to run "/etc/rc.d/rc.messagebus reload" after
adding any users to plugdev, power, or video groups so that it re-reads the
/etc/group file.
As noted HAL will use the '/etc/fstab' if the device is defined.
Notice the user/users are not allowed to mount via HAL if not allowed in '/etc/fstab'.
So, using fstab you can define where something *will* be mounted (by HAL or otherwise), or you use `mount` (which reads /etc/mtab) to see where something *has* been mounted.
Couple this with `dmesg` and you shall have no more mount-mysteries!
So, using fstab you can define where something *will* be mounted (by HAL or otherwise), or you use `mount` (which reads /etc/mtab) to see where something *has* been mounted.
Couple this with `dmesg` and you shall have no more mount-mysteries!
Hua!
- Piete.
Not completely correct. You can use the mount command not only to see what has been mounted but to also to do actual mounting (regardless of whether it is defined in fstab or anywhere else). The entries in fstab can allow a filesystem to be automatically mounted when "mount -a" is called (usually during bootscripts). If you define where a device should be mounted then. yes, that will be where HAL will mount it, but if it is not in fstab HAL will dynamically choose a mountpoint typically in /media. udev can also be a player and its rules can define all kinds of things when a device is attached. With udev rules you can, for instance, have the filesystem auto-mounted in a place you choose (with the owner and perms you specify of course), have programs run upon device insertion, and more.
If you define where a device should be mounted then. yes, that will be where HAL will mount it, but if it is not in fstab HAL will dynamically choose a mountpoint typically in /media.
I see, well that makes more sense. I defined the mountpoints in fstab because I didn't know HAL would "dynamically choose a mountpoint" if it wasn't in fstab.
Apologies, I should've made it clear that the command `mount` has more than just the use I stated, such as being able to mount arbitrary filesystems in arbitrary places =)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.