Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Fatherhood.Org

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 170 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

fstab



SYNOPSIS

       #include <fstab.h>


DESCRIPTION

       The  file fstab contains descriptive information about the
       various file systems.  fstab is only read by programs, and
       not written; it is the duty of the system administrator to
       properly create and maintain this file.   Each  filesystem
       is  described  on a separate line; fields on each line are
       separated by tabs or spaces.  Lines starting with '#'  are
       comments.   The  order  of  records  in fstab is important
       because  fsck(8),  mount(8),  and  umount(8)  sequentially
       iterate through fstab doing their thing.

       The  first  field,  (fs_spec), describes the block special
       device or remote filesystem to be mounted.

       For ordinary mounts it will hold (a link to) a block  spe­
       cial  device  node (as created by mknod(8)) for the device
       to be mounted, like `/dev/cdrom' or `/dev/sdb7'.  For  NFS
       mounts one will have <host>:<dir>, e.g., `knuth.aeb.nl:/'.
       For procfs, use `proc'.

       Instead of giving the device explicitly, one may  indicate
       the  (ext2 or xfs) filesystem that is to be mounted by its
       UUID or volume label (cf.   e2label(8)  or  xfs_admin(8)),
       writing  LABEL=<label>  or UUID=<uuid>, e.g., `LABEL=Boot'
       or `UUID=3e6be9de-8139-11d1-9106-a43f08d823a6'.  This will
       make  the  system  more  robust: adding or removing a SCSI
       disk changes the disk device name but not  the  filesystem
       volume label.

       The second field, (fs_file), describes the mount point for
       the filesystem.  For swap partitions, this field should be
       specified  as  `none'. If the name of the mount point con­
       tains spaces these can be escaped as `\040'.

       The third field, (fs_vfstype), describes the type  of  the
       filesystem.  Linux supports lots of filesystem types, such
       as adfs, affs, autofs,  coda,  coherent,  cramfs,  devpts,
       efs,  ext2,  ext3,  hfs, hpfs, iso9660, jfs, minix, msdos,
       ncpfs, nfs, ntfs,  proc,  qnx4,  reiserfs,  romfs,  smbfs,
       sysv,  tmpfs, udf, ufs, umsdos, vfat, xenix, xfs, and pos­
       sibly others. For more details,  see  mount(8).   For  the
       filesystems currently supported by the running kernel, see
       /proc/filesystems.  An entry swap denotes a file or parti­
       tion  to  be  used  for swapping, cf. swapon(8).  An entry
       ignore causes the line to be ignored.  This is  useful  to
       show disk partitions which are currently unused.

       The fourth field, (fs_mntops), describes the mount options
       associated with the filesystem.
       The  fifth field, (fs_freq), is used for these filesystems
       by the dump(8) command to determine which filesystems need
       to  be dumped.  If the fifth field is not present, a value
       of zero is returned and dump will assume that the filesys­
       tem does not need to be dumped.

       The  sixth field, (fs_passno), is used by the fsck(8) pro­
       gram to determine the order in which filesystem checks are
       done at reboot time.  The root filesystem should be speci­
       fied with a fs_passno of 1, and other  filesystems  should
       have a fs_passno of 2.  Filesystems within a drive will be
       checked sequentially, but filesystems on different  drives
       will  be  checked  at the same time to utilize parallelism
       available in the hardware.  If the sixth field is not pre­
       sent  or  zero,  a value of zero is returned and fsck will
       assume that the filesystem does not need to be checked.

       The proper way to read records from fstab is  to  use  the
       routines getmntent(3).


FILES

       /etc/fstab


SEE ALSO

       getmntent(3), mount(8), swapon(8), fs(5) nfs(5)


HISTORY

       The ancestor of this fstab file format appeared in 4.0BSD.

Linux 2.2                  15 June 1999                  FSTAB(5)
  




Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
You can choose larger fonts by selecting a different themes.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.05 Seconds