Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #176
Difficulty: Easy
Apple's first product was the Apple I, invented by Apple co-founder Steve Wozniak.
True or False?
Linux & Unix Commands - Search Man Pages

fstab(5) [ultrix man page]

fstab(5)							File Formats Manual							  fstab(5)

       fstab - file containing static information about known file systems

       The  file  contains  descriptive information about the known file systems.  By convention, is created and maintained as a read-only file by
       the system administrator.  Each file system is described by its own line within The order of these lines and the file systems  they  repre-
       sent is important because and sequentially process in the performance of their tasks.

       The format of each file system description in is as follows:
       The meanings of these fields are:

       spec	 The block special file name of the device on which the file system is located.  It can also be a network name for such as or

       file	 The pathname of the directory on which the file system is mounted.

       type	 How the file system is mounted.  The ways in which a file system can be mounted are:
		 rw - mount the file system read-write
		 ro - mount the file system read only
		 rq - mount the file system read-write with quotas
		 sw - make the special file part of the swap space
		 xx - ignore the entry

       freq	 The frequency (in days) with which the command dumps the rw, ro, and rq file systems.

       passno	 The order in which the command checks the rw, ro, and rq file systems at reboot time.

       name	 The  name  of	the file system type.  File systems can have the following types: ufs -- ULTRIX file system and nfs -- SUN Network
		 file system.

       options	 The options field.  This field contains an arbitrary string meaningful only when mounting file systems with  the  specified  file
		 system type name, such as NFS.  The specific options are described in the reference pages.

       Special	actions  occur for file systems of type sw and rq at system boot time.	File systems of type sw are made part of the swap space by
       the command and disk quotas are automatically processed by the command and then enabled by the command for rq file systems.

       Here is a sample file:
       The last three entries in the sample shown use NFS options as described in the reference page.

       The passno field of the root file system should be specified as 1.  Other file systems should have larger values.  File systems on the same
       device  should  have  distinct  passno  fields.	File systems on different devices may have the identical passno fields to allow them to be
       simultaneously checked.

       All field delimiters (:) must exist within each file system description; only the options field may not	be  present.   However,  only  the
       fields spec and type are meaningful to sw file systems and only the type field is meaningful to xx file systems.

       The file system description within should be parsed only through use of the routines.

       File system information file

See Also
       getfsent(3x), dump(8), fsck(8), mount(8), mount(8nfs), mount(8ufs) quotacheck(8), quotaon(8), swapon(8)


Check Out this Related Man Page

mount(8ufs)															       mount(8ufs)

       mount - mount the local ULTRIX File System (UFS)

       /etc/mount [ -t ufs -r ] [ options ] device directory

       The  command announces to the system that a file system is present on the device device.  The specified device must be a local device.  The
       file directory must exist and it must be a directory.  It becomes the name of the newly mounted file system.

       To further protect from system crashes, only file systems that have been cleanly checked by are	mounted.   In  emergency  situations,  the
       superuser can override this requirement by using the option as shown below.

       General users can mount file systems with certain restrictions in addition to those listed in The file system must have the clean byte set.
       To ensure the clean byte is set, run the command on the file system first.  You can also try the mount and if it fails, then run  and  then
       try the mount again.

       Note that the user must have execute permissions on the device.

       A successful ufs-mount may generate the following warning message:
       "Warning, device has exceeded xxx threshold, fsck(8) is advised"
       where  xxx  is  which metric was exceeded to cause the clean byte timeout factor to reach zero. See for an explanation of the timeout algo-

       Physically write-protected disks and magnetic tape file systems must be mounted read only or an error will occur at mount time.

       See the reference page for a description of the -t option.

       -o options  Specifies options as a sequence of comma-separated words from the list below.

		   force	 The superuser can force the mounting of unclean file systems.	You should use the flag only in  single-user  mode
				 when repairing or recovering damaged file systems.

		   nodev	 Block and character special devices cannot be accessed from this file system. If you are concerned with nfs secu-
				 rity, all ufs file systems that will be exported via nfs should be ufs mounted with the option.

		   noexec	 Binaries cannot be executed from this file system.

		   nosuid	 The and programs may not be executed from this file system. If you are concerned with nfs security, all ufs  file
				 systems that will be exported via nfs with the option specified in the file should be ufs mounted with the nosuid

		   pgthresh=##	 Set the paging threshold for this file system in kilobytes.  The default is 64 kilobytes.

		   sync 	 All writes are immediately written to disk (synchronously) as well as to the buffer cache.  For the option to	be
				 meaningful, the file system must be mounted with write permissions.

       -r	   Mounts the device on directory read only.

       The command should only be invoked by the command.  Users (and superusers) should not invoke the command.

       The command calls to do its work and is the preferred interface.  A sample command is:

	    # mount -t ufs -o nodev,nosuid,noexec,pgthresh=100 /dev/ra0g /usr

       UFS-specific mount program

See Also
       getmnt(2), mount(2), fsck(8), mount(8)


Featured Tech Videos