Archief - chmod folder

-t vfstype
    The argument following the -t is used to indicate the file system type. The file system types which are currently supported include: adfs, affs, autofs, cifs, coda, coherent, cramfs, debugfs, devpts, efs, ext, ext2, ext3, hfs, hpfs, iso9660, jfs, minix, msdos, ncpfs, nfs, nfs4, ntfs, proc, qnx4, ramfs, reiserfs, romfs, smbfs, sysv, tmpfs, udf, ufs, umsdos, usbfs, vfat, xenix, xfs, xiafs. Note that coherent, sysv and xenix are equivalent and that xenix and coherent will be removed at some point in the future -- use sysv instead. Since kernel version 2.1.21 the types ext and xiafs do not exist anymore. Earlier, usbfs was known as usbdevfs.

    For most types all the mount program has to do is issue a simple mount(2) system call, and no detailed knowledge of the filesystem type is required. For a few types however (like nfs, nfs4, cifs, smbfs, ncpfs) ad hoc code is necessary. The nfs ad hoc code is built in, but cifs, smbfs, and ncpfs have a separate mount program. In order to make it possible to treat all types in a uniform way, mount will execute the program /sbin/mount.TYPE (if that exists) when called with type TYPE. Since various versions of the smbmount program have different calling conventions, /sbin/mount.smbfs may have to be a shell script that sets up the desired call.

    If no -t option is given, or if the auto type is specified, mount will try to guess the desired type. If mount was compiled with the blkid library, the guessing is done by this library. Otherwise, mount guesses itself by probing the superblock; if that does not turn up anything that looks familiar, mount will try to read the file /etc/filesystems, or, if that does not exist, /proc/filesystems. All of the filesystem types listed there will be tried, except for those that are labeled "nodev" (e.g., devpts, proc, nfs, and nfs4). If /etc/filesystems ends in a line with a single * only, mount will read /proc/filesystems afterwards.

    The auto type may be useful for user-mounted floppies. Creating a file /etc/filesystems can be useful to change the probe order (e.g., to try vfat before msdos or ext3 before ext2) or if you use a kernel module autoloader. Warning: the probing uses a heuristic (the presence of appropriate 'magic'), and could recognize the wrong filesystem type, possibly with catastrophic consequences. If your data is valuable, don't ask mount to guess.

    More than one type may be specified in a comma separated list. The list of file system types can be prefixed with no to specify the file system types on which no action should be taken. (This can be meaningful with the -a option.)

    For example, the command:

mount -a -t nomsdos,ext mounts all file systems except those of type msdos and ext.

root@IR1337:/home/dennisf# umask 777 /mnt/xfer
root@IR1337:/home/dennisf# mount /dev/sda8 /mnt/xfer
mount: /dev/sda8 already mounted or /mnt/xfer busy
mount: according to mtab, /dev/sda8 is already mounted on /mnt/xfer
root@IR1337:/home/dennisf# umount /mnt/xfer
root@IR1337:/home/dennisf# umask 777 /mnt/xfer
root@IR1337:/home/dennisf# umask u=rwx /mnt/xfer
root@IR1337:/home/dennisf# mount /dev/sda8 /mnt/xfer
root@IR1337:/home/dennisf# umask u=rwx /mnt/xfer
root@IR1337:/home/dennisf# umount /mnt/xfer
root@IR1337:/home/dennisf# mount -t fat32 /dev/sda8 /mnt/xfer
mount: unknown filesystem type 'fat32'
mount: maybe you meant 'vfat'?
root@IR1337:/home/dennisf# mount -t vfat /dev/sda8 /mnt/xfer
root@IR1337:/home/dennisf# umask 777 /mnt/xfer
root@IR1337:/home/dennisf# umask 777 /dev/sda8
root@IR1337:/home/dennisf# chown dennisf /mnt/xfer
chown: changing ownership of `/mnt/xfer': Operation not permitted
root@IR1337:/home/dennisf#