| mount.8 (e867267b31968312f67b78db2ce8b7fa0cc1957e) | mount.8 (7f8047281e778c38c70cef35f69bbdc820b72df5) |
|---|---|
| 1.\" Copyright (c) 1980, 1989, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 65 unchanged lines hidden (view full) --- 74this list is printed. 75.Pp 76The options are as follows: 77.Bl -tag -width indent 78.It Fl a 79All the filesystems described in 80.Xr fstab 5 81are mounted. | 1.\" Copyright (c) 1980, 1989, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 65 unchanged lines hidden (view full) --- 74this list is printed. 75.Pp 76The options are as follows: 77.Bl -tag -width indent 78.It Fl a 79All the filesystems described in 80.Xr fstab 5 81are mounted. |
| 82Exceptions are those marked as ``noauto'', excluded by the | 82Exceptions are those marked as 83.Dq noauto , 84excluded by the |
| 83.Fl t 84flag (see below), or if they are already mounted (except the 85root filesystem which is always remounted to preserve 86traditional single user mode behavior). 87.It Fl d 88Causes everything to be done except for the actual system call. 89This option is useful in conjunction with the 90.Fl v --- 10 unchanged lines hidden (view full) --- 101.It Fl o 102Options are specified with a 103.Fl o 104flag followed by a comma separated string of options. 105In case of conflicting options being specified, the rightmost option 106takes effect. 107The following options are available: 108.Bl -tag -width indent | 85.Fl t 86flag (see below), or if they are already mounted (except the 87root filesystem which is always remounted to preserve 88traditional single user mode behavior). 89.It Fl d 90Causes everything to be done except for the actual system call. 91This option is useful in conjunction with the 92.Fl v --- 10 unchanged lines hidden (view full) --- 103.It Fl o 104Options are specified with a 105.Fl o 106flag followed by a comma separated string of options. 107In case of conflicting options being specified, the rightmost option 108takes effect. 109The following options are available: 110.Bl -tag -width indent |
| 109.It async | 111.It Cm async |
| 110All 111.Tn I/O 112to the file system should be done asynchronously. 113This is a 114.Em dangerous 115flag to set, 116and should not be used unless you are prepared to recreate the file 117system should your system crash. | 112All 113.Tn I/O 114to the file system should be done asynchronously. 115This is a 116.Em dangerous 117flag to set, 118and should not be used unless you are prepared to recreate the file 119system should your system crash. |
| 118.It current | 120.It Cm current |
| 119When used with the 120.Fl u 121flag, this is the same as specifying the options currently in effect for 122the mounted filesystem. | 121When used with the 122.Fl u 123flag, this is the same as specifying the options currently in effect for 124the mounted filesystem. |
| 123.It force | 125.It Cm force |
| 124The same as 125.Fl f ; 126forces the revocation of write access when trying to downgrade 127a filesystem mount status from read-write to read-only. 128Also 129forces the R/W mount of an unclean filesystem (dangerous; use with caution). | 126The same as 127.Fl f ; 128forces the revocation of write access when trying to downgrade 129a filesystem mount status from read-write to read-only. 130Also 131forces the R/W mount of an unclean filesystem (dangerous; use with caution). |
| 130.It fstab | 132.It Cm fstab |
| 131When used with the 132.Fl u 133flag, this is the same as specifying all the options listed in the 134.Xr fstab 5 135file for the filesystem. | 133When used with the 134.Fl u 135flag, this is the same as specifying all the options listed in the 136.Xr fstab 5 137file for the filesystem. |
| 136.It noasync | 138.It Cm noasync |
| 137Metadata I/O should be done synchronously, while data I/O should be done | 139Metadata I/O should be done synchronously, while data I/O should be done |
| 138asynchronously. This is the default. 139.It noatime | 140asynchronously. 141This is the default. 142.It Cm noatime |
| 140Do not update the file access time when reading from a file. 141This option 142is useful on filesystems where there are large numbers of files and 143performance is more critical than updating the file access time (which is | 143Do not update the file access time when reading from a file. 144This option 145is useful on filesystems where there are large numbers of files and 146performance is more critical than updating the file access time (which is |
| 144rarely ever important). This option is currently only supported on local 145filesystems. 146.It noauto 147This filesystem should be skipped when mount is run with the | 147rarely ever important). 148This option is currently only supported on local filesystems. 149.It Cm noauto 150This filesystem should be skipped when 151.Nm 152is run with the |
| 148.Fl a 149flag. | 153.Fl a 154flag. |
| 150.It noclusterr | 155.It Cm noclusterr |
| 151Disable read clustering. | 156Disable read clustering. |
| 152.It noclusterw | 157.It Cm noclusterw |
| 153Disable write clustering. | 158Disable write clustering. |
| 154.It nodev | 159.It Cm nodev |
| 155Do not interpret character or block special devices on the file system. 156This option is useful for a server that has file systems containing 157special devices for architectures other than its own. | 160Do not interpret character or block special devices on the file system. 161This option is useful for a server that has file systems containing 162special devices for architectures other than its own. |
| 158.It noexec | 163.It Cm noexec |
| 159Do not allow execution of any binaries on the mounted file system. 160This option is useful for a server that has file systems containing 161binaries for architectures other than its own. | 164Do not allow execution of any binaries on the mounted file system. 165This option is useful for a server that has file systems containing 166binaries for architectures other than its own. |
| 162.It nosuid | 167.It Cm nosuid |
| 163Do not allow set-user-identifier or set-group-identifier bits to take effect. 164Note: this option is worthless if a public available suid or sgid 165wrapper like 166.Xr suidperl 1 167is installed on your system. | 168Do not allow set-user-identifier or set-group-identifier bits to take effect. 169Note: this option is worthless if a public available suid or sgid 170wrapper like 171.Xr suidperl 1 172is installed on your system. |
| 168.It nosymfollow | 173.It Cm nosymfollow |
| 169Do not follow symlinks 170on the mounted file system. | 174Do not follow symlinks 175on the mounted file system. |
| 171.It rdonly | 176.It Cm rdonly |
| 172The same as 173.Fl r ; 174mount the file system read-only (even the super-user may not write it). | 177The same as 178.Fl r ; 179mount the file system read-only (even the super-user may not write it). |
| 175.It sync | 180.It Cm sync |
| 176All 177.Tn I/O 178to the file system should be done synchronously. | 181All 182.Tn I/O 183to the file system should be done synchronously. |
| 179.It suiddir 180A directory on the mounted filesystem will respond to the SUID bit | 184.It Cm suiddir 185A directory on the mounted filesystem will respond to the SUID bit |
| 181being set, by setting the owner of any new files to be the same 182as the owner of the directory. 183New directories will inherit the bit from their parents. 184Execute bits are removed from 185the file, and it will not be given to root. 186.Pp 187This feature is designed for use on fileservers serving PC users via 188ftp, SAMBA, or netatalk. 189It provides security holes for shell users and as 190such should not be used on shell machines, especially on home directories. 191This option requires the SUIDDIR 192option in the kernel to work. 193Only UFS filesystems support this option. 194See 195.Xr chmod 2 196for more information. | 186being set, by setting the owner of any new files to be the same 187as the owner of the directory. 188New directories will inherit the bit from their parents. 189Execute bits are removed from 190the file, and it will not be given to root. 191.Pp 192This feature is designed for use on fileservers serving PC users via 193ftp, SAMBA, or netatalk. 194It provides security holes for shell users and as 195such should not be used on shell machines, especially on home directories. 196This option requires the SUIDDIR 197option in the kernel to work. 198Only UFS filesystems support this option. 199See 200.Xr chmod 2 201for more information. |
| 197.It update | 202.It Cm update |
| 198The same as 199.Fl u ; 200indicate that the status of an already mounted file system should be changed. | 203The same as 204.Fl u ; 205indicate that the status of an already mounted file system should be changed. |
| 201.It union | 206.It Cm union |
| 202Causes the namespace at the mount point to appear as the union 203of the mounted filesystem root and the existing directory. 204Lookups will be done in the mounted filesystem first. 205If those operations fail due to a non-existent file the underlying 206directory is then accessed. 207All creates are done in the mounted filesystem. 208.El 209.Pp --- 23 unchanged lines hidden (view full) --- 233which are not internally known 234(see the description of the 235.Fl t 236option below) 237may be described in the manual pages for the associated 238.Pa /sbin/mount_ Ns Sy XXX 239utilities. 240.It Fl p | 207Causes the namespace at the mount point to appear as the union 208of the mounted filesystem root and the existing directory. 209Lookups will be done in the mounted filesystem first. 210If those operations fail due to a non-existent file the underlying 211directory is then accessed. 212All creates are done in the mounted filesystem. 213.El 214.Pp --- 23 unchanged lines hidden (view full) --- 238which are not internally known 239(see the description of the 240.Fl t 241option below) 242may be described in the manual pages for the associated 243.Pa /sbin/mount_ Ns Sy XXX 244utilities. 245.It Fl p |
| 241Print mount information in fstab format. | 246Print mount information in 247.Xr fstab 5 248format. |
| 242Implies also the 243.Fl v 244option. 245.It Fl r 246The file system is to be mounted read-only. 247Mount the file system read-only (even the super-user may not write it). 248The same as the | 249Implies also the 250.Fl v 251option. 252.It Fl r 253The file system is to be mounted read-only. 254Mount the file system read-only (even the super-user may not write it). 255The same as the |
| 249.Dq rdonly | 256.Cm rdonly |
| 250argument to the 251.Fl o 252option. | 257argument to the 258.Fl o 259option. |
| 253.It Fl t Ar ufs | Ar external_type | 260.It Fl t Ar ufs | external_type |
| 254The argument following the 255.Fl t 256is used to indicate the file system type. 257The type 258.Ar ufs 259is the default. | 261The argument following the 262.Fl t 263is used to indicate the file system type. 264The type 265.Ar ufs 266is the default. |
| 260The | 267The |
| 261.Fl t 262option can be used 263to indicate that the actions should only be taken on 264filesystems of the specified type. 265More than one type may be specified in a comma separated list. 266The list of filesystem types can be prefixed with 267.Dq no 268to specify the filesystem types for which action should --- 16 unchanged lines hidden (view full) --- 285will attempt to execute a program in 286.Pa /sbin/mount_ Ns Sy XXX 287where 288.Sy XXX 289is replaced by the type name. 290For example, nfs filesystems are mounted by the program 291.Pa /sbin/mount_nfs . 292.Pp | 268.Fl t 269option can be used 270to indicate that the actions should only be taken on 271filesystems of the specified type. 272More than one type may be specified in a comma separated list. 273The list of filesystem types can be prefixed with 274.Dq no 275to specify the filesystem types for which action should --- 16 unchanged lines hidden (view full) --- 292will attempt to execute a program in 293.Pa /sbin/mount_ Ns Sy XXX 294where 295.Sy XXX 296is replaced by the type name. 297For example, nfs filesystems are mounted by the program 298.Pa /sbin/mount_nfs . 299.Pp |
| 293Most filesystems will be dynamically loaded by their mount programs | 300Most filesystems will be dynamically loaded by their 301.Nm 302programs |
| 294if not already present in the kernel, using the 295.Xr vfsload 3 | 303if not already present in the kernel, using the 304.Xr vfsload 3 |
| 296subroutine. Because this mechanism requires writable temporary space, | 305subroutine. 306Because this mechanism requires writable temporary space, |
| 297the filesystem type containing 298.Pa /tmp 299must be compiled into the kernel, and the filesystems containing | 307the filesystem type containing 308.Pa /tmp 309must be compiled into the kernel, and the filesystems containing |
| 300.Pa /tmp | 310.Pa /tmp |
| 301and | 311and |
| 302.Pa /usr/bin/ld | 312.Pa /usr/bin/ld |
| 303must be listed in 304.Pa /etc/fstab 305before any filesystems which might be dynamically loaded. 306.It Fl u 307The 308.Fl u 309flag indicates that the status of an already mounted file 310system should be changed. 311Any of the options discussed above (the 312.Fl o 313option) 314may be changed; 315also a file system can be changed from read-only to read-write 316or vice versa. 317An attempt to change from read-write to read-only will fail if any 318files on the filesystem are currently open for writing unless the 319.Fl f 320flag is also specified. | 313must be listed in 314.Pa /etc/fstab 315before any filesystems which might be dynamically loaded. 316.It Fl u 317The 318.Fl u 319flag indicates that the status of an already mounted file 320system should be changed. 321Any of the options discussed above (the 322.Fl o 323option) 324may be changed; 325also a file system can be changed from read-only to read-write 326or vice versa. 327An attempt to change from read-write to read-only will fail if any 328files on the filesystem are currently open for writing unless the 329.Fl f 330flag is also specified. |
| 321The set of options is determined by applying the options specified 322in the argument to 323.Fl o | 331The set of options is determined by applying the options specified 332in the argument to 333.Fl o |
| 324and finally applying the 325.Fl r 326or 327.Fl w 328option. 329.It Fl v 330Verbose mode. 331.It Fl w 332The file system object is to be read and write. 333.Sh DIAGNOSTICS 334Various, most of them are self-explanatory. 335.Pp 336.Dl XXXXX filesystem is not available 337.Pp | 334and finally applying the 335.Fl r 336or 337.Fl w 338option. 339.It Fl v 340Verbose mode. 341.It Fl w 342The file system object is to be read and write. 343.Sh DIAGNOSTICS 344Various, most of them are self-explanatory. 345.Pp 346.Dl XXXXX filesystem is not available 347.Pp |
| 338The kernel doesn't support the respective filesystem type. Note that | 348The kernel does not support the respective filesystem type. 349Note that |
| 339support for a particular filesystem might be provided either on a static 340(kernel compile-time), or dynamic basis (loaded as a kernel module by | 350support for a particular filesystem might be provided either on a static 351(kernel compile-time), or dynamic basis (loaded as a kernel module by |
| 341.Xr kldload 8 ). | 352.Xr kldload 8 ) . |
| 342Normally, 343.Nm 344or its subprocesses attempt to dynamically load a filesystem module if | 353Normally, 354.Nm 355or its subprocesses attempt to dynamically load a filesystem module if |
| 345it hasn't been configured statically, using | 356it has not been configured statically, using |
| 346.Xr vfsload 3 . | 357.Xr vfsload 3 . |
| 347In this case, the above error message can also mean that you didn't | 358In this case, the above error message can also mean that you did not |
| 348have permission to load the module. 349.Sh FILES 350.Bl -tag -width /etc/fstab -compact 351.It Pa /etc/fstab 352file system table 353.El 354.Sh SEE ALSO 355.Xr mount 2 , --- 16 unchanged lines hidden (view full) --- 372.Xr mount_procfs 8 , 373.Xr mount_std 8 , 374.Xr mount_umap 8 , 375.Xr mount_union 8 , 376.Xr umount 8 377.Sh BUGS 378It is possible for a corrupted file system to cause a crash. 379.Sh CAVEATS | 359have permission to load the module. 360.Sh FILES 361.Bl -tag -width /etc/fstab -compact 362.It Pa /etc/fstab 363file system table 364.El 365.Sh SEE ALSO 366.Xr mount 2 , --- 16 unchanged lines hidden (view full) --- 383.Xr mount_procfs 8 , 384.Xr mount_std 8 , 385.Xr mount_umap 8 , 386.Xr mount_union 8 , 387.Xr umount 8 388.Sh BUGS 389It is possible for a corrupted file system to cause a crash. 390.Sh CAVEATS |
| 380After a successful mount, the permissions on the original mount point 381determine if 382.Pa ".." 383is accessible from the mounted file system. The minimum permissions for 384the mount point for traversal across the mount point in both | 391After a successful 392.Nm , 393the permissions on the original mount point determine if 394.Pa ..\& 395is accessible from the mounted file system. 396The minimum permissions for 397the mount point for traversal across the mount point in both |
| 385directions to be possible for all users is 0111 (execute for all). 386.Sh HISTORY 387A 388.Nm 389command appeared in 390.At v1 . | 398directions to be possible for all users is 0111 (execute for all). 399.Sh HISTORY 400A 401.Nm 402command appeared in 403.At v1 . |