/[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.20 Revision 1.35
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/1.0 --> 5<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.20 2004/01/19 18:48:52 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.35 2004/07/03 10:05:28 swift Exp $ -->
8 8
9<sections> 9<sections>
10<section> 10<section>
11<title>Filesystem Information</title> 11<title>Filesystem Information</title>
12<subsection> 12<subsection>
73</pre> 73</pre>
74 74
75<p> 75<p>
76Let us take a look at how we write down the options for the <path>/boot</path> 76Let us take a look at how we write down the options for the <path>/boot</path>
77partition. This is just an example, so if your architecture doesn't require a 77partition. This is just an example, so if your architecture doesn't require a
78<path>/boot</path> partition, don't copy it verbatim. 78<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim.
79</p> 79</p>
80 80
81<p> 81<p>
82In our default x86 partitioning example <path>/boot</path> is the 82In our default x86 partitioning example <path>/boot</path> is the
83<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. It shouldn't 83<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem.
84be mounted automatically (<c>noauto</c>) but does need to be checked. So we 84It needs to be checked during boot, so we would write down:
85would write down:
86</p> 85</p>
87 86
88<pre caption="An example /boot line for /etc/fstab"> 87<pre caption="An example /boot line for /etc/fstab">
89/dev/hda1 /boot ext2 noauto 1 2 88/dev/hda1 /boot ext2 defaults 1 2
89</pre>
90
91<p>
92Some users don't want their <path>/boot</path> partition to be mounted
93automatically. Those people should substitute <c>defaults</c> with
94<c>noauto</c>. This does mean that you need to manually mount this partition
95every time you want to use it.
90</pre> 96</p>
91 97
92<p> 98<p>
93Now, to improve performance, most users would want to add the <c>noatime</c> 99Now, to improve performance, most users would want to add the <c>noatime</c>
94option as mountoption, which results in a faster system since access times 100option as mountoption, which results in a faster system since access times
95aren't registered (you don't need those generally anyway): 101aren't registered (you don't need those generally anyway):
133<c>user</c> makes it possible for non-root users to mount the CD. 139<c>user</c> makes it possible for non-root users to mount the CD.
134</p> 140</p>
135 141
136<p> 142<p>
137Now use the above example to create your <path>/etc/fstab</path>. If you are a 143Now use the above example to create your <path>/etc/fstab</path>. If you are a
138SPARC-user, you should add the following line to your <path>/etc/fstab</path> 144<b>SPARC</b>-user, you should add the following line to your
145<path>/etc/fstab</path>
139too: 146too:
140</p> 147</p>
141 148
142<pre caption="Adding openprom filesystem to /etc/fstab"> 149<pre caption="Adding openprom filesystem to /etc/fstab">
143none /proc/openprom openpromfs defaults 0 0 150none /proc/openprom openpromfs defaults 0 0
150<pre caption="Adding usbfs filesystem to /etc/fstab"> 157<pre caption="Adding usbfs filesystem to /etc/fstab">
151none /proc/bus/usb usbfs defaults 0 0 158none /proc/bus/usb usbfs defaults 0 0
152</pre> 159</pre>
153 160
154<p> 161<p>
155Reread your <path>/etc/fstab</path>, save and quit to continue. 162Double-check your <path>/etc/fstab</path>, save and quit to continue.
156</p> 163</p>
157 164
158</body> 165</body>
159</subsection> 166</subsection>
160</section> 167</section>
163<subsection> 170<subsection>
164<title>Hostname, Domainname etc.</title> 171<title>Hostname, Domainname etc.</title>
165<body> 172<body>
166 173
167<p> 174<p>
168One of the choices the user has to make is name his PC. This seems to be quite 175One of the choices the user has to make is name his/her PC. This seems to be
169easy, but <e>lots</e> of users are having difficulties finding the appropriate 176quite easy, but <e>lots</e> of users are having difficulties finding the
170name for their Linux-pc. To speed things up, know that any name you choose can 177appropriate name for their Linux-pc. To speed things up, know that any name you
171be changed afterwards. For all we care, you can just call your system 178choose can be changed afterwards. For all we care, you can just call your system
172<c>tux</c> and domain <c>homenetwork</c>. 179<c>tux</c> and domain <c>homenetwork</c>.
173</p> 180</p>
174 181
175<p> 182<p>
176We use these values in the next examples. First we set the hostname: 183We use these values in the next examples. First we set the hostname:
242iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>" 249iface_eth0="<i>&lt;your ip address&gt;</i> broadcast <i>&lt;your broadcast address&gt;</i> netmask <i>&lt;your netmask&gt;</i>"
243</pre> 250</pre>
244 251
245<p> 252<p>
246If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 253If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c>
254to <c>dhcp</c>. If you use rp-pppoe (e.g. for ADSL), set it to <c>up</c>.
247to <c>dhcp</c>. However, if you need to setup your network manually and you're 255If you need to setup your network manually and you're
248not familiar with all the above terms, please read the section on <uri 256not familiar with all the above terms, please read the section on <uri
249link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 257link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network
250Terminology</uri> if you haven't done so already. 258Terminology</uri> if you haven't done so already.
251</p> 259</p>
252 260
253<p> 261<p>
254So let us give two examples; the first one uses DHCP, the second one a static IP 262So let us give three examples; the first one uses DHCP, the second one a static
255(192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and gateway 263IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and
256192.168.0.1: 264gateway 192.168.0.1 while the third one just activates the interface for
265rp-pppoe usage:
257</p> 266</p>
258 267
259<pre caption="Examples for /etc/conf.d/net"> 268<pre caption="Examples for /etc/conf.d/net">
260<comment>(For DHCP:)</comment> 269<comment>(For DHCP)</comment>
261iface_eth0="dhcp" 270iface_eth0="dhcp"
262 271
263<comment>(For static IP:)</comment> 272<comment>(For static IP)</comment>
264iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0" 273iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
265gateway="eth0/192.168.0.1" 274gateway="eth0/192.168.0.1"
275
276<comment>(For rp-pppoe)</comment>
277iface_eth0="up"
266</pre> 278</pre>
267 279
268<p> 280<p>
269If you have several network interfaces, create extra <c>iface_eth</c> variables, 281If you have several network interfaces, create extra <c>iface_eth</c> variables,
270like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable 282like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable
322# <i>nano -w /etc/hosts</i> 334# <i>nano -w /etc/hosts</i>
323</pre> 335</pre>
324 336
325<pre caption="Filling in the networking information"> 337<pre caption="Filling in the networking information">
326127.0.0.1 localhost 338127.0.0.1 localhost
327192.168.0.5 jenny 339192.168.0.5 jenny.homenetwork jenny
328192.168.0.6 benny 340192.168.0.6 benny.homenetwork benny
329192.168.0.7 tux 341192.168.0.7 tux.homenetwork tux
330</pre> 342</pre>
331 343
332<p> 344<p>
333If your system is the only system (or the nameservers handle all name 345If your system is the only system (or the nameservers handle all name
334resolution) a single line is sufficient: 346resolution) a single line is sufficient:
335</p> 347</p>
336 348
337<pre caption="/etc/hosts for lonely or fully integrated PCs"> 349<pre caption="/etc/hosts for lonely or fully integrated PCs">
338127.0.0.1 localhost tux 350127.0.0.1 localhost
339</pre> 351</pre>
340 352
341<p> 353<p>
342Save and exit the editor to continue. 354Save and exit the editor to continue.
343</p> 355</p>
352</subsection> 364</subsection>
353<subsection> 365<subsection>
354<title>Optional: Get PCMCIA Working</title> 366<title>Optional: Get PCMCIA Working</title>
355<body> 367<body>
356 368
369<note>
370pcmcia-cs is only available for x86, amd64 and ppc platforms.
371</note>
372
357<p> 373<p>
358PCMCIA-users should first install the <c>pcmcia-cs</c> package: 374PCMCIA-users should first install the <c>pcmcia-cs</c> package. The
375<c>USE="-X"</c> is necessary to avoid installing XFree86 at this moment:
359</p> 376</p>
360 377
361<pre caption="Installing pcmcia-cs"> 378<pre caption="Installing pcmcia-cs">
362# <i>emerge --usepkg pcmcia-cs</i> 379# <i>USE="-X" emerge pcmcia-cs</i>
363</pre> 380</pre>
364 381
365<p> 382<p>
366When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e> 383When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
367runlevel: 384runlevel:
393you select the wrong <c>KEYMAP</c> you will get weird results when typing on 410you select the wrong <c>KEYMAP</c> you will get weird results when typing on
394your keyboard. 411your keyboard.
395</p> 412</p>
396 413
397<note> 414<note>
398Users of USB-based SPARC systems and SPARC clones might need to select an i386 415Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to
399keymap (such as "us") instead of "sunkeymap". 416select an i386 keymap (such as "us") instead of "sunkeymap".
400</note> 417</note>
418
419<p>
420<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use
421ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have
422to set a mac/ppc keymap in <path>rc.conf</path>.
423</p>
401 424
402<p> 425<p>
403When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then 426When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then
404continue with <uri link="?part=1&amp;chap=9">Configuring the Bootloader</uri>. 427continue with <uri link="?part=1&amp;chap=9">Configuring the Bootloader</uri>.
405</p> 428</p>

Legend:
Removed from v.1.20  
changed lines
  Added in v.1.35

  ViewVC Help
Powered by ViewVC 1.1.20