source: chapter08/fstab.xml@ 6c3ab2e

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 6c3ab2e was 32fa31b, checked in by Bruce Dubbs <bdubbs@…>, 13 years ago

Remove reference to /dev/shm in fstab description

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@9637 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

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