/[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.33
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.33 2004/04/15 07:06:36 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. It shouldn't
133<c>user</c> makes it possible for non-root users to mount the CD. 133<c>user</c> makes it possible for non-root users to mount the CD.
134</p> 134</p>
135 135
136<p> 136<p>
137Now use the above example to create your <path>/etc/fstab</path>. If you are a 137Now 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> 138<b>SPARC</b>-user, you should add the following line to your
139<path>/etc/fstab</path>
139too: 140too:
140</p> 141</p>
141 142
142<pre caption="Adding openprom filesystem to /etc/fstab"> 143<pre caption="Adding openprom filesystem to /etc/fstab">
143none /proc/openprom openpromfs defaults 0 0 144none /proc/openprom openpromfs defaults 0 0
163<subsection> 164<subsection>
164<title>Hostname, Domainname etc.</title> 165<title>Hostname, Domainname etc.</title>
165<body> 166<body>
166 167
167<p> 168<p>
168One of the choices the user has to make is name his PC. This seems to be quite 169One 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 170quite 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 171appropriate 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 172choose can be changed afterwards. For all we care, you can just call your system
172<c>tux</c> and domain <c>homenetwork</c>. 173<c>tux</c> and domain <c>homenetwork</c>.
173</p> 174</p>
174 175
175<p> 176<p>
176We use these values in the next examples. First we set the hostname: 177We 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>" 243iface_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> 244</pre>
244 245
245<p> 246<p>
246If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c> 247If you use DHCP (automatic IP retrieval), you should just set <c>iface_eth0</c>
248to <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 249If you need to setup your network manually and you're
248not familiar with all the above terms, please read the section on <uri 250not familiar with all the above terms, please read the section on <uri
249link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network 251link="?part=1&amp;chap=3#doc_chap4_sect3">Understanding Network
250Terminology</uri> if you haven't done so already. 252Terminology</uri> if you haven't done so already.
251</p> 253</p>
252 254
253<p> 255<p>
254So let us give two examples; the first one uses DHCP, the second one a static IP 256So 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 257IP (192.168.0.2) with netmask 255.255.255.0, broadcast 192.168.0.255 and
256192.168.0.1: 258gateway 192.168.0.1 while the third one just activates the interface for
259rp-pppoe usage:
257</p> 260</p>
258 261
259<pre caption="Examples for /etc/conf.d/net"> 262<pre caption="Examples for /etc/conf.d/net">
260<comment>(For DHCP:)</comment> 263<comment>(For DHCP)</comment>
261iface_eth0="dhcp" 264iface_eth0="dhcp"
262 265
263<comment>(For static IP:)</comment> 266<comment>(For static IP)</comment>
264iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0" 267iface_eth0="192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0"
265gateway="eth0/192.168.0.1" 268gateway="eth0/192.168.0.1"
269
270<comment>(For rp-pppoe)</comment>
271iface_eth0="up"
266</pre> 272</pre>
267 273
268<p> 274<p>
269If you have several network interfaces, create extra <c>iface_eth</c> variables, 275If 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 276like <c>iface_eth1</c>, <c>iface_eth2</c> etc. The <c>gateway</c> variable
322# <i>nano -w /etc/hosts</i> 328# <i>nano -w /etc/hosts</i>
323</pre> 329</pre>
324 330
325<pre caption="Filling in the networking information"> 331<pre caption="Filling in the networking information">
326127.0.0.1 localhost 332127.0.0.1 localhost
327192.168.0.5 jenny 333192.168.0.5 jenny.homenetwork jenny
328192.168.0.6 benny 334192.168.0.6 benny.homenetwork benny
329192.168.0.7 tux 335192.168.0.7 tux.homenetwork tux
330</pre> 336</pre>
331 337
332<p> 338<p>
333If your system is the only system (or the nameservers handle all name 339If your system is the only system (or the nameservers handle all name
334resolution) a single line is sufficient: 340resolution) a single line is sufficient:
335</p> 341</p>
336 342
337<pre caption="/etc/hosts for lonely or fully integrated PCs"> 343<pre caption="/etc/hosts for lonely or fully integrated PCs">
338127.0.0.1 localhost tux 344127.0.0.1 localhost
339</pre> 345</pre>
340 346
341<p> 347<p>
342Save and exit the editor to continue. 348Save and exit the editor to continue.
343</p> 349</p>
352</subsection> 358</subsection>
353<subsection> 359<subsection>
354<title>Optional: Get PCMCIA Working</title> 360<title>Optional: Get PCMCIA Working</title>
355<body> 361<body>
356 362
363<note>
364pcmcia-cs is only available for x86, amd64 and ppc platforms.
365</note>
366
357<p> 367<p>
358PCMCIA-users should first install the <c>pcmcia-cs</c> package: 368PCMCIA-users should first install the <c>pcmcia-cs</c> package. The
369<c>USE="-X"</c> is necessary to avoid installing XFree86 at this moment:
359</p> 370</p>
360 371
361<pre caption="Installing pcmcia-cs"> 372<pre caption="Installing pcmcia-cs">
362# <i>emerge --usepkg pcmcia-cs</i> 373# <i>USE="-X" emerge pcmcia-cs</i>
363</pre> 374</pre>
364 375
365<p> 376<p>
366When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e> 377When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e>
367runlevel: 378runlevel:
393you select the wrong <c>KEYMAP</c> you will get weird results when typing on 404you select the wrong <c>KEYMAP</c> you will get weird results when typing on
394your keyboard. 405your keyboard.
395</p> 406</p>
396 407
397<note> 408<note>
398Users of USB-based SPARC systems and SPARC clones might need to select an i386 409Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to
399keymap (such as "us") instead of "sunkeymap". 410select an i386 keymap (such as "us") instead of "sunkeymap".
400</note> 411</note>
412
413<p>
414<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use
415ADB keymaps on boot have to enable ADB keycode sendings in their kernel and have
416to set a mac/ppc keymap in <path>rc.conf</path>.
417</p>
401 418
402<p> 419<p>
403When you're finished configuring <path>/etc/rc.conf</path>, save and exit, then 420When 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>. 421continue with <uri link="?part=1&amp;chap=9">Configuring the Bootloader</uri>.
405</p> 422</p>

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

  ViewVC Help
Powered by ViewVC 1.1.20