/[gentoo]/xml/htdocs/doc/en/handbook/hb-install-config.xml
Gentoo

Diff of /xml/htdocs/doc/en/handbook/hb-install-config.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.77 Revision 1.81
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> 2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3 3
4<!-- The content of this document is licensed under the CC-BY-SA license --> 4<!-- The content of this document is licensed under the CC-BY-SA license -->
5<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 5<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.77 2006/05/15 07:00:22 nightmorph Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.81 2006/08/30 22:52:28 nightmorph Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>2.18</version> 11<version>7.0</version>
12<date>2006-03-28</date> 12<date>2006-08-30</date>
13 13
14<section> 14<section>
15<title>Filesystem Information</title> 15<title>Filesystem Information</title>
16<subsection> 16<subsection>
17<title>What is fstab?</title> 17<title>What is fstab?</title>
18<body> 18<body>
19 19
20<p> 20<p>
21Under Linux, all partitions used by the system must be listed in 21Under Linux, all partitions used by the system must be listed in
22<path>/etc/fstab</path>. This file contains the mountpoints of those partitions 22<path>/etc/fstab</path>. This file contains the mount points of those partitions
23(where they are seen in the file system structure), how they should be mounted 23(where they are seen in the file system structure), how they should be mounted
24and with what special options (automatically or not, whether users can mount 24and with what special options (automatically or not, whether users can mount
25them or not, etc.) 25them or not, etc.)
26</p> 26</p>
27 27
41<li> 41<li>
42 The first field shows the <b>partition</b> described (the path to the device 42 The first field shows the <b>partition</b> described (the path to the device
43 file) 43 file)
44</li> 44</li>
45<li> 45<li>
46 The second field shows the <b>mountpoint</b> at which the partition should be 46 The second field shows the <b>mount point</b> at which the partition should be
47 mounted 47 mounted
48</li> 48</li>
49<li> 49<li>
50 The third field shows the <b>filesystem</b> used by the partition 50 The third field shows the <b>filesystem</b> used by the partition
51</li> 51</li>
52<li> 52<li>
53 The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it 53 The fourth field shows the <b>mount options</b> used by <c>mount</c> when it
54 wants to mount the partition. As every filesystem has its own mountoptions, 54 wants to mount the partition. As every filesystem has its own mount options,
55 you are encouraged to read the mount man page (<c>man mount</c>) for a full 55 you are encouraged to read the mount man page (<c>man mount</c>) for a full
56 listing. Multiple mountoptions are comma-separated. 56 listing. Multiple mount options are comma-separated.
57</li> 57</li>
58<li> 58<li>
59 The fifth field is used by <c>dump</c> to determine if the partition needs to 59 The fifth field is used by <c>dump</c> to determine if the partition needs to
60 be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero). 60 be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero).
61</li> 61</li>
65 The root filesystem should have <c>1</c> while the rest should have <c>2</c> 65 The root filesystem should have <c>1</c> while the rest should have <c>2</c>
66 (or <c>0</c> if a filesystem check isn't necessary). 66 (or <c>0</c> if a filesystem check isn't necessary).
67</li> 67</li>
68</ul> 68</ul>
69 69
70<p> 70<impo>
71The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid 71The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid
72fstab file</e>, so start <c>nano</c> (or your favorite editor) to create your 72fstab file</e>, You <b>have to create</b> your own <path>/etc/fstab</path>.
73<path>/etc/fstab</path>: 73</impo>
74</p>
75 74
76<pre caption="Opening /etc/fstab"> 75<pre caption="Opening /etc/fstab">
77# <i>nano -w /etc/fstab</i> 76# <i>nano -w /etc/fstab</i>
78</pre> 77</pre>
79 78
79</body>
80<body test="func:keyval('/boot')">
81
80<p> 82<p>
81Let us take a look at how we write down the options for the <path>/boot</path> 83Let us take a look at how we write down the options for the <path>/boot</path>
82partition. This is just an example, so if your architecture doesn't require a 84partition. This is just an example, if you didn't or couldn't create a
83<path>/boot</path> partition (such as Apple <b>PPC</b> machines), don't copy it 85<path>/boot</path>, don't copy it.
84verbatim.
85</p>
86
87<p> 86</p>
87
88<p test="contains(func:keyval('/boot'), '/dev/hd')">
88In our default x86 partitioning example <path>/boot</path> is the 89In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
89<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. 90usually the <path><keyval id="/boot"/></path> partition (or
91<path>/dev/sda*</path> if you use SCSI or SATA drives), with <c>ext2</c> as
90It needs to be checked during boot, so we would write down: 92filesystem. It needs to be checked during boot, so we would write down:
93</p>
94
95<p test="contains(func:keyval('/boot'), '/dev/sd')">
96In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is
97usually the <path><keyval id="/boot"/></path> partition, with <c>ext2</c> as
98filesystem. It needs to be checked during boot, so we would write down:
91</p> 99</p>
92 100
93<pre caption="An example /boot line for /etc/fstab"> 101<pre caption="An example /boot line for /etc/fstab">
94/dev/hda1 /boot ext2 defaults 1 2 102<keyval id="/boot"/> /boot ext2 defaults 1 2
95</pre> 103</pre>
96 104
97<p> 105<p>
98Some users don't want their <path>/boot</path> partition to be mounted 106Some users don't want their <path>/boot</path> partition to be mounted
99automatically to improve their system's security. Those people should 107automatically to improve their system's security. Those people should
100substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to 108substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to
101manually mount this partition every time you want to use it. 109manually mount this partition every time you want to use it.
102</p> 110</p>
103 111
112</body>
113<body>
114
115<p test="not(func:keyval('arch')='SPARC')">
116Add the rules that match your partitioning scheme and append rules for
117<path>/proc</path>, <c>tmpfs</c>, for your CD-ROM drive(s), and of course, if
118you have other partitions or drives, for those too.
104<p> 119</p>
105Now, to improve performance, most users would want to add the <c>noatime</c>
106option as mountoption, which results in a faster system since access times
107aren't registered (you don't need those generally anyway):
108</p>
109 120
110<pre caption="An improved /boot line for /etc/fstab"> 121<p test="func:keyval('arch')='SPARC'">
111/dev/hda1 /boot ext2 defaults,noatime 1 2 122Add the rules that match your partitioning schema and append rules for
112</pre> 123<path>/proc/openprom</path>, <path>/proc</path>, <c>tmpfs</c> , for your CD-ROM
113 124drive(s), and of course, if you have other partitions or drives, for those too.
114<p> 125</p>
115If we continue with this, we would end up with the following three lines (for 126
116<path>/boot</path>, <path>/</path> and the swap partition):
117</p> 127<p>
118 128Now use the <e>example</e> below to create your <path>/etc/fstab</path>:
119<pre caption="Three /etc/fstab lines">
120/dev/hda1 /boot ext2 defaults,noatime 1 2
121/dev/hda2 none swap sw 0 0
122/dev/hda3 / ext3 noatime 0 1
123</pre>
124
125<p> 129</p>
126To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c>
127(required) and for your CD-ROM drive (and of course, if you have other
128partitions or drives, for those too):
129</p>
130 130
131<pre caption="A full /etc/fstab example"> 131<pre caption="A full /etc/fstab example" test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86'">
132/dev/hda1 /boot ext2 defaults,noatime 1 2 132<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
133/dev/hda2 none swap sw 0 0 133/dev/hda2 none swap sw 0 0
134/dev/hda3 / ext3 noatime 0 1 134/dev/hda3 / ext3 noatime 0 1
135 135
136none /proc proc defaults 0 0 136none /proc proc defaults 0 0
137none /dev/shm tmpfs nodev,nosuid,noexec 0 0 137none /dev/shm tmpfs nodev,nosuid,noexec 0 0
138 138
139/dev/cdrom /mnt/cdrom auto noauto,user 0 0
140</pre>
141
142<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'">
143<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
144/dev/sda3 none swap sw 0 0
145/dev/sda4 / ext3 noatime 0 1
146
147none /proc proc defaults 0 0
148none /dev/shm tmpfs nodev,nosuid,noexec 0 0
149
150/dev/cdrom /mnt/cdrom auto noauto,user 0 0
151</pre>
152
153<pre caption="A full /etc/fstab example" test="func:keyval('arch')='Alpha' or func:keyval('arch')='MIPS'">
154<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2
155/dev/sda2 none swap sw 0 0
156/dev/sda3 / ext3 noatime 0 1
157
158none /proc proc defaults 0 0
159none /dev/shm tmpfs nodev,nosuid,noexec 0 0
160
161/dev/cdrom /mnt/cdrom auto noauto,user 0 0
162</pre>
163
164<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'">
165/dev/sda1 / ext3 noatime 0 1
166/dev/sda2 none swap sw 0 0
167/dev/sda4 /usr ext3 noatime 0 2
168/dev/sda5 /var ext3 noatime 0 2
169/dev/sda6 /home ext3 noatime 0 2
170
171none /proc/openprom openpromfs defaults 0 0
172none /proc proc defaults 0 0
173none /dev/shm tmpfs nodev,nosuid,noexec 0 0
174
139/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 175/dev/cdrom /mnt/cdrom auto noauto,user 0 0
176</pre>
177
178<note test="func:keyval('arch')='PPC'">
179There are important variations between PPC machine types. Please make sure you
180adapt the following example to your system.
181</note>
182
183<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC'">
184/dev/hda4 / ext3 noatime 0 1
185/dev/hda3 none swap sw 0 0
186
187none /proc proc defaults 0 0
188none /dev/shm tmpfs nodev,nosuid,noexec 0 0
189
190/dev/cdrom /mnt/cdrom auto noauto,user 0 0
191</pre>
192
193<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC64'">
194/dev/sda4 / ext3 noatime 0 1
195/dev/sda3 none swap sw 0 0
196
197none /proc proc defaults 0 0
198none /dev/shm tmpfs nodev,nosuid,noexec 0 0
199
200/dev/cdrom /mnt/cdrom auto noauto,user 0 0
140</pre> 201</pre>
141 202
142<p> 203<p>
143<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for 204<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for
144removable media as they can be created with one of many filesystems) and 205removable media as they can be created with one of many filesystems) and
145<c>user</c> makes it possible for non-root users to mount the CD. 206<c>user</c> makes it possible for non-root users to mount the CD.
146</p> 207</p>
147 208
148<p> 209<p>
149Now use the above example to create your <path>/etc/fstab</path>. If you are a 210To improve performance, most users would want to add the <c>noatime</c>
150<b>SPARC</b>-user, you should add the following line to your 211mount option, which results in a faster system since access times
151<path>/etc/fstab</path> 212aren't registered (you don't need those generally anyway).
152too:
153</p>
154
155<pre caption="Adding openprom filesystem to /etc/fstab">
156none /proc/openprom openpromfs defaults 0 0
157</pre> 213</p>
158 214
159<p> 215<p>
160Double-check your <path>/etc/fstab</path>, save and quit to continue. 216Double-check your <path>/etc/fstab</path>, save and quit to continue.
161</p> 217</p>
162 218
164</subsection> 220</subsection>
165</section> 221</section>
166<section> 222<section>
167<title>Networking Information</title> 223<title>Networking Information</title>
168<subsection> 224<subsection>
169<title>Hostname, Domainname etc.</title> 225<title>Host name</title>
170<body> 226<body>
171 227
172<p> 228<p>
173One of the choices the user has to make is name his/her PC. This seems to be 229One of the choices the user has to make is name his/her PC. This seems to be
174quite easy, but <e>lots</e> of users are having difficulties finding the 230quite easy, but <e>lots</e> of users are having difficulties finding the
175appropriate name for their Linux-pc. To speed things up, know that any name you 231appropriate name for their Linux-pc. To speed things up, know that any name you
176choose can be changed afterwards. For all we care, you can just call your system 232choose can be changed afterwards. For all we care, you can just call your system
177<c>tux</c> and domain <c>homenetwork</c>. 233<c>tux</c> and domain <c>homenetwork</c>.
178</p> 234</p>
179 235
180<p>
181We use these values in the next examples. First we set the hostname:
182</p>
183
184<pre caption="Setting the hostname"> 236<pre caption="Setting the host name">
185# <i>nano -w /etc/conf.d/hostname</i> 237# <i>nano -w /etc/conf.d/hostname</i>
186 238
187<comment>(Set the HOSTNAME variable to your hostname)</comment> 239<comment>(Set the HOSTNAME variable to your host name)</comment>
188HOSTNAME="<i>tux</i>" 240HOSTNAME="<i>tux</i>"
189</pre>
190
191<p>
192Second we set the domainname:
193</p>
194
195<pre caption="Setting the domainname">
196# <i>nano -w /etc/conf.d/domainname</i>
197
198<comment>(Set the DNSDOMAIN variable to your domain name)</comment>
199DNSDOMAIN="<i>homenetwork</i>"
200</pre>
201
202<p>
203If you have a NIS domain (if you don't know what that is, then you don't have
204one), you need to define that one too:
205</p>
206
207<pre caption="Setting the NIS domainname">
208# <i>nano -w /etc/conf.d/domainname</i>
209
210<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment>
211NISDOMAIN="<i>my-nisdomain</i>"
212</pre> 241</pre>
213 242
214</body> 243</body>
215</subsection> 244</subsection>
216<subsection> 245<subsection>
320use <c>ln</c> to do this: 349use <c>ln</c> to do this:
321</p> 350</p>
322 351
323<pre caption="Creating extra initscripts"> 352<pre caption="Creating extra initscripts">
324# <i>cd /etc/init.d</i> 353# <i>cd /etc/init.d</i>
325# <i>ln -s net.eth0 net.eth1</i> 354# <i>ln -s net.lo net.eth1</i>
326# <i>rc-update add net.eth1 default</i> 355# <i>rc-update add net.eth1 default</i>
327</pre> 356</pre>
328 357
329</body> 358</body>
330</subsection> 359</subsection>
332<title>Writing Down Network Information</title> 361<title>Writing Down Network Information</title>
333<body> 362<body>
334 363
335<p> 364<p>
336You now need to inform Linux about your network. This is defined in 365You now need to inform Linux about your network. This is defined in
337<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses 366<path>/etc/hosts</path> and helps in resolving host names to IP addresses for
338for hosts that aren't resolved by your nameserver. For instance, if your 367hosts that aren't resolved by your nameserver. You need to define your system.
339internal network consists of three PCs called <c>jenny</c> (192.168.0.5), 368You may also want to define other systems on your network if you don't want to
340<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would 369set up your own internal DNS system.
341open <path>/etc/hosts</path> and fill in the values:
342</p> 370</p>
343 371
344<pre caption="Opening /etc/hosts"> 372<pre caption="Opening /etc/hosts">
345# <i>nano -w /etc/hosts</i> 373# <i>nano -w /etc/hosts</i>
346</pre> 374</pre>
347 375
348<pre caption="Filling in the networking information"> 376<pre caption="Filling in the networking information">
349127.0.0.1 localhost 377<comment>(This defines the current system)</comment>
378127.0.0.1 tux.homenetwork tux localhost
379
380<comment>(Define extra systems on your network,
381they need to have a static IP to be defined this way.)</comment>
350192.168.0.5 jenny.homenetwork jenny 382192.168.0.5 jenny.homenetwork jenny
351192.168.0.6 benny.homenetwork benny 383192.168.0.6 benny.homenetwork benny
352192.168.0.7 tux.homenetwork tux
353</pre>
354
355<p>
356If your system is the only system (or the nameservers handle all name
357resolution) a single line is sufficient. For instance, if you want to call your
358system <c>tux</c>:
359</p>
360
361<pre caption="/etc/hosts for lonely or fully integrated PCs">
362127.0.0.1 localhost tux
363</pre> 384</pre>
364 385
365<p> 386<p>
366Save and exit the editor to continue. 387Save and exit the editor to continue.
367</p> 388</p>
368 389
369<p> 390<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
370If you don't have PCMCIA, you can now continue with <uri 391If you don't have PCMCIA, you can now continue with <uri
371link="#doc_chap3">System Information</uri>. PCMCIA-users should read the 392link="#sysinfo">System Information</uri>. PCMCIA-users should read the
372following topic on PCMCIA. 393following topic on PCMCIA.
373</p> 394</p>
374 395
375</body> 396</body>
376</subsection> 397</subsection>
377<subsection> 398<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'">
378<title>Optional: Get PCMCIA Working</title> 399<title>Optional: Get PCMCIA Working</title>
379<body> 400<body>
380
381<note>
382pcmcia-cs is only available for x86, amd64 and ppc platforms.
383</note>
384 401
385<p> 402<p>
386PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also 403PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also
387includes users who will be working with a 2.6 kernel (even though they won't be 404includes users who will be working with a 2.6 kernel (even though they won't be
388using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary 405using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary
403</pre> 420</pre>
404 421
405</body> 422</body>
406</subsection> 423</subsection>
407</section> 424</section>
408<section> 425
426<section id="sysinfo">
409<title>System Information</title> 427<title>System Information</title>
410<subsection> 428<subsection>
411<title>Root Password</title> 429<title>Root Password</title>
412<body> 430<body>
413 431
465<p> 483<p>
466Take special care with the <c>KEYMAP</c> variable. If you select the wrong 484Take special care with the <c>KEYMAP</c> variable. If you select the wrong
467<c>KEYMAP</c>, you will get weird results when typing on your keyboard. 485<c>KEYMAP</c>, you will get weird results when typing on your keyboard.
468</p> 486</p>
469 487
488<note test="func:keyval('arch')='SPARC'">
489Users of USB-based SPARC systems and SPARC clones might need to select an i386
490keymap (such as "us") instead of "sunkeymap".
470<note> 491</note>
471Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to 492
472select an i386 keymap (such as "us") instead of "sunkeymap". <b>PPC</b> uses x86 493<note test="substring(func:keyval('arch'),1,3)='PPC'">
473keymaps on most systems. Users who want to be able to use ADB keymaps on boot 494PPC uses x86 keymaps on most systems. Users who want to be able to use ADB
474have to enable ADB keycode sendings in their kernel and have to set a mac/ppc 495keymaps on boot have to enable ADB keycode sendings in their kernel and have to
475keymap in <path>/etc/conf.d/keymaps</path>. 496set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>.
476</note> 497</note>
477 498
478<p> 499<p>
479When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and 500When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and
480exit. 501exit.
499<p> 520<p>
500When you're finished configuring <path>/etc/conf.d/clock</path>, save and 521When you're finished configuring <path>/etc/conf.d/clock</path>, save and
501exit. 522exit.
502</p> 523</p>
503 524
525<p test="not(func:keyval('arch')='PPC64')">
526Please continue with <uri link="?part=1&amp;chap=9">Installing Necessary System
527Tools</uri>.
504<p> 528</p>
505If you are not installing Gentoo on IBM PPC64 hardware, continue with
506<uri link="?part=1&amp;chap=9">Installing Necessary System Tools</uri>.
507</p>
508 529
509</body> 530</body>
510</subsection>
511<subsection> 531</subsection>
532<subsection test="func:keyval('arch')='PPC64'">
512<title>Configuring the Console</title> 533<title>Configuring the Console</title>
513<body> 534<body>
514 535
515<note>
516The following section applies to the IBM PPC64 hardware platforms.
517</note>
518
519<p> 536<p>
520If you are running Gentoo on IBM PPC64 hardware and using a virtual console 537If you are using a virtual console, you must uncomment the appropriate line in
521you must uncomment the appropriate line in <path>/etc/inittab</path> for the 538<path>/etc/inittab</path> for the virtual console to spawn a login prompt.
522virtual console to spawn a login prompt.
523</p> 539</p>
524 540
525<pre caption="Enabling hvc or hvsi support in /etc/inittab"> 541<pre caption="Enabling hvc or hvsi support in /etc/inittab">
526hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0 542hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
527hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0 543hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0

Legend:
Removed from v.1.77  
changed lines
  Added in v.1.81

  ViewVC Help
Powered by ViewVC 1.1.20