fstab.xml 5.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117
  1. <?xml version="1.0" encoding="ISO-8859-1"?>
  2. <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
  3. "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
  4. <!ENTITY % general-entities SYSTEM "../general.ent">
  5. %general-entities;
  6. ]>
  7. <sect1 id="ch-bootable-fstab">
  8. <?dbhtml filename="fstab.html"?>
  9. <title>Creating the /etc/fstab File</title>
  10. <indexterm zone="ch-bootable-fstab">
  11. <primary sortas="e-/etc/fstab">/etc/fstab</primary>
  12. </indexterm>
  13. <para>The <filename>/etc/fstab</filename> file is used by some programs to
  14. determine where file systems are to be mounted by default, in which order, and
  15. which must be checked (for integrity errors) prior to mounting. Create a new
  16. file systems table like this:</para>
  17. <screen><userinput>cat &gt; /etc/fstab &lt;&lt; "EOF"
  18. <literal># Begin /etc/fstab
  19. # file system mount-point type options dump fsck
  20. # order
  21. /dev/<replaceable>&lt;xxx&gt;</replaceable> / <replaceable>&lt;fff&gt;</replaceable> defaults 1 1
  22. /dev/<replaceable>&lt;yyy&gt;</replaceable> swap swap pri=1 0 0
  23. proc /proc proc nosuid,noexec,nodev 0 0
  24. sysfs /sys sysfs nosuid,noexec,nodev 0 0
  25. devpts /dev/pts devpts gid=5,mode=620 0 0
  26. tmpfs /run tmpfs defaults 0 0
  27. devtmpfs /dev devtmpfs mode=0755,nosuid 0 0
  28. # End /etc/fstab</literal>
  29. EOF</userinput></screen>
  30. <para>Replace <replaceable>&lt;xxx&gt;</replaceable>,
  31. <replaceable>&lt;yyy&gt;</replaceable>, and <replaceable>&lt;fff&gt;</replaceable>
  32. with the values appropriate for the system, for example, <filename
  33. class="partition">hda2</filename>, <filename
  34. class="partition">hda5</filename>, and <systemitem
  35. class="filesystem">ext3</systemitem>. For details on the six
  36. fields in this file, see <command>man 5 fstab</command>.</para>
  37. <!--
  38. <para>The <filename class="directory">/dev/shm</filename> mount point
  39. for <systemitem class="filesystem">tmpfs</systemitem> is included to
  40. allow enabling POSIX-shared memory. The kernel must have the required
  41. support built into it for this to work (more about this is in the next
  42. section). Please note that very little software currently uses
  43. POSIX-shared memory. Therefore, consider the <filename
  44. class="directory">/dev/shm</filename> mount point optional. For more
  45. information, see
  46. <filename>Documentation/filesystems/tmpfs.txt</filename> in the kernel
  47. source tree.</para>
  48. -->
  49. <para>Filesystems with MS-DOS or Windows origin (i.e.: vfat, ntfs, smbfs, cifs,
  50. iso9660, udf) need the <quote>iocharset</quote> mount option in order for
  51. non-ASCII characters in file names to be interpreted properly. The value
  52. of this option should be the same as the character set of your locale,
  53. adjusted in such a way that the kernel understands it. This works if the
  54. relevant character set definition (found under File systems -&gt;
  55. Native Language Support) has been compiled into the kernel
  56. or built as a module. The <quote>codepage</quote> option is also needed for
  57. vfat and smbfs filesystems. It should be set to the codepage number used
  58. under MS-DOS in your country. E.g., in order to mount USB flash drives, a
  59. ru_RU.KOI8-R user would need the following in the options portion of its
  60. mount line in <filename>/etc/fstab</filename>:</para>
  61. <screen><literal>noauto,user,quiet,showexec,iocharset=koi8r,codepage=866</literal></screen>
  62. <para>The corresponding options fragment for ru_RU.UTF-8 users is:</para>
  63. <screen><literal>noauto,user,quiet,showexec,iocharset=utf8,codepage=866</literal></screen>
  64. <note>
  65. <para>In the latter case, the kernel emits the following message:</para>
  66. <screen><computeroutput>FAT: utf8 is not a recommended IO charset for FAT filesystems,
  67. filesystem will be case sensitive!</computeroutput></screen>
  68. <para>This negative recommendation should be ignored, since all other values
  69. of the <quote>iocharset</quote> option result in wrong display of filenames in
  70. UTF-8 locales.</para>
  71. </note>
  72. <para>It is also possible to specify default codepage and iocharset values for
  73. some filesystems during kernel configuration. The relevant parameters
  74. are named
  75. <quote>Default NLS Option</quote> (<option>CONFIG_NLS_DEFAULT)</option>,
  76. <quote>Default Remote NLS Option</quote> (<option>CONFIG_SMB_NLS_DEFAULT</option>),
  77. <quote>Default codepage for FAT</quote> (<option>CONFIG_FAT_DEFAULT_CODEPAGE</option>), and
  78. <quote>Default iocharset for FAT</quote> (<option>CONFIG_FAT_DEFAULT_IOCHARSET</option>).
  79. There is no way to specify these settings for the
  80. ntfs filesystem at kernel compilation time.</para>
  81. <!-- Personally, I find it more foolproof to always specify the iocharset and
  82. codepage in /etc/fstab for MS-based filesystems - Alexander E. Patrakov -->
  83. <para>It is possible to make the ext3 filesystem reliable across power
  84. failures for some hard disk types. To do this, add the
  85. <option>barrier=1</option> mount option to the appropriate entry in
  86. <filename>/etc/fstab</filename>. To check if the disk drive supports
  87. this option, run
  88. <ulink url="http://www.linuxfromscratch.org/blfs/view/cvs/general/hdparm.html">hdparm</ulink>
  89. on the applicable disk drive. For example, if:</para>
  90. <screen role="nodump"><userinput>hdparm -I /dev/sda | grep NCQ</userinput></screen>
  91. <para>returns non-empty output, the option is supported.</para>
  92. <para>Note: Logical Volume Management (LVM) based partitions cannot use the
  93. <option>barrier</option> option.</para>
  94. </sect1>