fstab.5 (241440) | fstab.5 (252310) |
---|---|
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. --- 16 unchanged lines hidden (view full) --- 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)fstab.5 8.1 (Berkeley) 6/5/93 | 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. --- 16 unchanged lines hidden (view full) --- 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)fstab.5 8.1 (Berkeley) 6/5/93 |
33.\" $FreeBSD: head/share/man/man5/fstab.5 241440 2012-10-11 07:54:29Z stefanf $ | 33.\" $FreeBSD: head/share/man/man5/fstab.5 252310 2013-06-27 18:28:45Z hrs $ |
34.\" | 34.\" |
35.Dd October 11, 2012 | 35.Dd June 21, 2013 |
36.Dt FSTAB 5 37.Os 38.Sh NAME 39.Nm fstab 40.Nd static information about the file systems 41.Sh SYNOPSIS 42.In fstab.h 43.Sh DESCRIPTION --- 136 unchanged lines hidden (view full) --- 180to be automatically mounted at system startup, 181the 182.Va extra_netfs_types 183.Xr rc.conf 5 184variable must be used to extend the 185.Xr rc 8 186startup script's list of network file system types. 187.Pp | 36.Dt FSTAB 5 37.Os 38.Sh NAME 39.Nm fstab 40.Nd static information about the file systems 41.Sh SYNOPSIS 42.In fstab.h 43.Sh DESCRIPTION --- 136 unchanged lines hidden (view full) --- 180to be automatically mounted at system startup, 181the 182.Va extra_netfs_types 183.Xr rc.conf 5 184variable must be used to extend the 185.Xr rc 8 186startup script's list of network file system types. 187.Pp |
188If the option 189.Dq late 190is specified, the file system will be automatically mounted 191at a stage of system startup after remote mount points are mounted. 192For more detail about this option, 193see the 194.Xr mount 8 195manual page. 196.Pp |
|
188The type of the mount is extracted from the 189.Fa fs_mntops 190field and stored separately in the 191.Fa fs_type 192field (it is not deleted from the 193.Fa fs_mntops 194field). 195If 196.Fa fs_type 197is 198.Dq rw 199or 200.Dq ro 201then the file system whose name is given in the 202.Fa fs_file 203field is normally mounted read-write or read-only on the 204specified special file. | 197The type of the mount is extracted from the 198.Fa fs_mntops 199field and stored separately in the 200.Fa fs_type 201field (it is not deleted from the 202.Fa fs_mntops 203field). 204If 205.Fa fs_type 206is 207.Dq rw 208or 209.Dq ro 210then the file system whose name is given in the 211.Fa fs_file 212field is normally mounted read-write or read-only on the 213specified special file. |
214.Pp |
|
205If 206.Fa fs_type 207is 208.Dq sw 209then the special file is made available as a piece of swap 210space by the 211.Xr swapon 8 212command at the end of the system reboot procedure. | 215If 216.Fa fs_type 217is 218.Dq sw 219then the special file is made available as a piece of swap 220space by the 221.Xr swapon 8 222command at the end of the system reboot procedure. |
223For vnode-backed swap spaces, 224.Dq file 225is supported in the 226.Fa fs_mntops 227field. 228When 229.Fa fs_spec 230is an 231.Xr md 4 232device file 233.Pq Do md Dc or Do md[0-9]* Dc 234and 235.Dq file 236is specified in 237.Fa fs_mntopts , 238an 239.Xr md 4 240device is created with the specified file used as backing store, 241and then the new device is used as swap space. |
|
213The fields other than 214.Fa fs_spec 215and 216.Fa fs_type 217are unused. 218If 219.Fa fs_type 220is specified as --- 136 unchanged lines hidden --- | 242The fields other than 243.Fa fs_spec 244and 245.Fa fs_type 246are unused. 247If 248.Fa fs_type 249is specified as --- 136 unchanged lines hidden --- |