source: chapter10/fstab.xml@ 3d7b4f6

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 12.2 12.2-rc1 arm bdubbs/gcc13 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/loongarch-12.2 xry111/mips64el xry111/multilib xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 3d7b4f6 was fcc02767, checked in by Bruce Dubbs <bdubbs@…>, 4 years ago

Initial commit of alternative cross LFS

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/cross2@11897 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 5.9 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 revision="sysv"><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 nosuid,noexec,nodev 0 0
31sysfs /sys sysfs nosuid,noexec,nodev 0 0
32devpts /dev/pts devpts gid=5,mode=620 0 0
33tmpfs /run tmpfs defaults 0 0
34devtmpfs /dev devtmpfs mode=0755,nosuid 0 0
35
36# End /etc/fstab</literal>
37EOF</userinput></screen>
38
39<screen revision="systemd"><userinput>cat &gt; /etc/fstab &lt;&lt; "EOF"
40<literal># Begin /etc/fstab
41
42# file system mount-point type options dump fsck
43# order
44
45/dev/<replaceable>&lt;xxx&gt;</replaceable> / <replaceable>&lt;fff&gt;</replaceable> defaults 1 1
46/dev/<replaceable>&lt;yyy&gt;</replaceable> swap swap pri=1 0 0
47
48# End /etc/fstab</literal>
49EOF</userinput></screen>
50
51 <para>Replace <replaceable>&lt;xxx&gt;</replaceable>,
52 <replaceable>&lt;yyy&gt;</replaceable>, and <replaceable>&lt;fff&gt;</replaceable>
53 with the values appropriate for the system, for example, <filename
54 class="partition">sda2</filename>, <filename
55 class="partition">sda5</filename>, and <systemitem
56 class="filesystem">ext4</systemitem>. For details on the six
57 fields in this file, see <command>man 5 fstab</command>.</para>
58
59 <para>Filesystems with MS-DOS or Windows origin (i.e. vfat, ntfs, smbfs,
60 cifs, iso9660, udf) need a special option, utf8, in order for non-ASCII
61 characters in file names to be interpreted properly. For non-UTF-8 locales,
62 the value of <option>iocharset</option> should be set to be the same as the
63 character set of the locale, adjusted in such a way that the kernel
64 understands it. This works if the relevant character set definition (found
65 under File systems -&gt; Native Language Support when configuring the kernel)
66 has been compiled into the kernel or built as a module. However, if the
67 character set of the locale is UTF-8, the corresponding option
68 <option>iocharset=utf8</option> would make the file system case sensitive. To
69 fix this, use the special option <option>utf8</option> instead of
70 <option>iocharset=utf8</option>, for UTF-8 locales. The
71 <quote>codepage</quote> option is also needed for vfat and smbfs filesystems.
72 It should be set to the codepage number used under MS-DOS in your country.
73 For example, in order to mount USB flash drives, a ru_RU.KOI8-R user would
74 need the following in the options portion of its mount line in
75 <filename>/etc/fstab</filename>:</para>
76
77<screen><literal>noauto,user,quiet,showexec,codepage=866,iocharset=koi8r</literal></screen>
78
79 <para>The corresponding options fragment for ru_RU.UTF-8 users is:</para>
80
81<screen><literal>noauto,user,quiet,showexec,codepage=866,utf8</literal></screen>
82
83 <para>Note that using <option>iocharset</option> is the default for
84 <literal>iso8859-1</literal> (which keeps the file system case
85 insensitive), and the <option>utf8</option> option tells
86 the kernel to convert the file names using UTF-8 so they can be
87 interpreted in the UTF-8 locale.</para>
88
89 <!--note>
90 <para>In the latter case, the kernel emits the following message:</para>
91
92<screen><computeroutput>FAT: utf8 is not a recommended IO charset for FAT filesystems,
93 filesystem will be case sensitive!</computeroutput></screen>
94
95 <para>This negative recommendation should be ignored, since all other values
96 of the <quote>iocharset</quote> option result in wrong display of filenames in
97 UTF-8 locales.</para>
98 </note-->
99
100 <para>It is also possible to specify default codepage and iocharset values for
101 some filesystems during kernel configuration. The relevant parameters
102 are named
103 <quote>Default NLS Option</quote> (<option>CONFIG_NLS_DEFAULT)</option>,
104 <quote>Default Remote NLS Option</quote> (<option>CONFIG_SMB_NLS_DEFAULT</option>),
105 <quote>Default codepage for FAT</quote> (<option>CONFIG_FAT_DEFAULT_CODEPAGE</option>), and
106 <quote>Default iocharset for FAT</quote> (<option>CONFIG_FAT_DEFAULT_IOCHARSET</option>).
107 There is no way to specify these settings for the
108 ntfs filesystem at kernel compilation time.</para>
109
110 <para>It is possible to make the ext3 filesystem reliable across power
111 failures for some hard disk types. To do this, add the
112 <option>barrier=1</option> mount option to the appropriate entry in
113 <filename>/etc/fstab</filename>. To check if the disk drive supports
114 this option, run
115 <ulink url="&blfs-book;general/hdparm.html">hdparm</ulink>
116 on the applicable disk drive. For example, if:</para>
117
118<screen role="nodump"><userinput>hdparm -I /dev/sda | grep NCQ</userinput></screen>
119
120 <para>returns non-empty output, the option is supported.</para>
121
122 <para>Note: Logical Volume Management (LVM) based partitions cannot use the
123 <option>barrier</option> option.</para>
124
125</sect1>
Note: See TracBrowser for help on using the repository browser.