Devhda3 on type reiserfs rwacluserxattr proc on proc type proc rw tmpfs on devshm type tmpfs rw

devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/hda2 on /home type reiserfs (rw,acl,user_xattr)

/dev/hdc on /media/dvd type subfs (ro,nosuid,nodev,fs=cdfss,procuid,iocharset=utf8) /dev/fd0 on /media/floppy type subfs (rw,nosuid,nodev,sync,fs=floppyfss,procuid) usbfs on /proc/bus/usb type usbfs (rw) /dev/hda5 on /mnt type ext2 (rw)

As most commonly used, the mount command takes two arguments — the block device that the filesystem resides on and the directory you want to mount it under. The /mnt directory is a general-purpose directory that is present on most Linux systems and is used for mounting filesystems that you want to use for a single session only. For filesystems that you want to use regularly, it is customary to either create a directory under /mnt or follow the procedure to mount a filesystem on a regular basis, as discussed later in this chapter in the section "Mounting Filesystems Automatically." If you want to mount filesystems permanently for specific purposes, it is a good idea to create or identify a directory that is permanently associated with that specific filesystem. For example, if you want to store the /var hierarchy on a different disk, you would mount it permanently outside of /mnt.

The mount command's -t option enables you to specify the type of filesystem that you are mounting but is unnecessary in many cases because the kernel tries to automatically sense the filesystem type. But if necessary you can explicitly identify the type of filesystem that a partition contains by using the -t type option when you issue the mount command. If a filesystem is failing to mount for some reason, looking at the messages from the kernel using the command dmesg or in /var/log/messages may help you understand what the problem is.

Was this article helpful?

0 0

Post a comment