1 |
fox2mike 06/02/10 17:46:25 |
2 |
|
3 |
Modified: xml/htdocs/doc/en/handbook/draft/2006.0 hb-install-about.xml |
4 |
hb-install-x86-medium.xml |
5 |
Added: xml/htdocs/doc/en/handbook/draft/2006.0 |
6 |
hb-install-x86-about.xml hb-install-x86-network.xml |
7 |
Log: |
8 |
More fixes for x86 + fixing my earlier messup of removing install-x86-about |
9 |
|
10 |
Revision Changes Path |
11 |
1.3 +26 -26 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml |
12 |
|
13 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
14 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml?rev=1.3&content-type=text/plain&cvsroot=gentoo |
15 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml.diff?r1=1.2&r2=1.3&cvsroot=gentoo |
16 |
|
17 |
Index: hb-install-about.xml |
18 |
=================================================================== |
19 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml,v |
20 |
retrieving revision 1.2 |
21 |
retrieving revision 1.3 |
22 |
diff -u -r1.2 -r1.3 |
23 |
--- hb-install-about.xml 9 Feb 2006 19:17:28 -0000 1.2 |
24 |
+++ hb-install-about.xml 10 Feb 2006 17:46:25 -0000 1.3 |
25 |
@@ -4,12 +4,12 @@ |
26 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
27 |
<!-- See http://creativecommons.org/licenses/by-sa/2.0 --> |
28 |
|
29 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml,v 1.2 2006/02/09 19:17:28 fox2mike Exp $ --> |
30 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml,v 1.3 2006/02/10 17:46:25 fox2mike Exp $ --> |
31 |
|
32 |
<sections> |
33 |
|
34 |
-<version>5.0</version> |
35 |
-<date>2005-08-08</date> |
36 |
+<version>5.1</version> |
37 |
+<date>2006-02-09</date> |
38 |
|
39 |
<section> |
40 |
<title>Introduction</title> |
41 |
@@ -19,28 +19,27 @@ |
42 |
|
43 |
<p> |
44 |
First of all, <e>welcome</e> to Gentoo. You are about to enter the world |
45 |
-of choices and performance. Gentoo is all about choices. When |
46 |
-installing Gentoo, this is made clear to you several times -- you can |
47 |
-choose how much you want to compile yourself, how to install Gentoo, |
48 |
-what system logger you want, etc. |
49 |
+of customization and performance. When installing Gentoo, this is made clear to |
50 |
+you several times -- you can choose how much you want to compile yourself, how |
51 |
+to install Gentoo, what system logger you want, etc. |
52 |
</p> |
53 |
|
54 |
<p> |
55 |
-Gentoo is a fast, modern metadistribution with a clean and flexible |
56 |
+Gentoo is a fast, modern meta-distribution with a clean and flexible |
57 |
design. Gentoo is built around free software and doesn't hide from its |
58 |
users what is beneath the hood. Portage, the package maintenance system |
59 |
which Gentoo uses, is written in Python, meaning you can easily view and |
60 |
modify the source code. Gentoo's packaging system uses source code |
61 |
(although support for precompiled packages is included too) and |
62 |
-configuring Gentoo happens through regular textfiles. In other words, |
63 |
+configuring Gentoo happens through regular text files. In other words, |
64 |
openness everywhere. |
65 |
</p> |
66 |
|
67 |
<p> |
68 |
-It is very important that you understand that <e>choices</e> are what |
69 |
-makes Gentoo run. We try not to force you onto anything you don't like. |
70 |
-If you feel like we do, please <uri |
71 |
-link="http://bugs.gentoo.org">bugreport</uri> it. |
72 |
+It is very important that you understand that <e>empowerment</e> is what makes |
73 |
+Gentoo run. We try not to force anything on our users and try our best to |
74 |
+empower you to make the choices you wish. If you feel a change should be made, |
75 |
+please file a <uri link="http://bugs.gentoo.org">bug report</uri> about it. |
76 |
</p> |
77 |
|
78 |
</body> |
79 |
@@ -126,11 +125,9 @@ |
80 |
</p> |
81 |
|
82 |
<p> |
83 |
-This document covers the installation using the Universal Installation CD, a |
84 |
+This document covers the installation using the Installer LiveCD, a |
85 |
bootable CD that contains everything you need to get Gentoo Linux up and |
86 |
-running. You can optionally use one of our Package CDs as well to install a |
87 |
-complete system in a matter of minutes after having installed the Gentoo base |
88 |
-system. |
89 |
+running. |
90 |
</p> |
91 |
|
92 |
<p> |
93 |
@@ -162,8 +159,8 @@ |
94 |
If you find a problem in the installation (or in the installation |
95 |
documentation), please check the errata from our <uri |
96 |
link="/proj/en/releng/">Gentoo Release Engineering Project</uri>, |
97 |
-visit our <uri link="http://bugs.gentoo.org">bugtracking |
98 |
-system</uri> and check if the bug is known. If not, please create a bugreport |
99 |
+visit our <uri link="http://bugs.gentoo.org">bug tracking |
100 |
+system</uri> and check if the bug is known. If not, please create a bug report |
101 |
for it so we can take care of it. Do not be afraid of the developers who are |
102 |
assigned to (your) bugs -- they generally don't eat people. |
103 |
</p> |
104 |
@@ -212,7 +209,7 @@ |
105 |
of Gentoo to speed up the installation process. The GRP consists of all |
106 |
packages required to have a fully functional Gentoo installation. They are not |
107 |
just the ones you need to have a base installation up to speed in no time, but |
108 |
-all lengthier builds (such as KDE, xorg-x11, GNOME, OpenOffice, Mozilla, ...) |
109 |
+all lengthier builds (such as xorg-x11, GNOME, OpenOffice, Mozilla, ...) |
110 |
are available as GRP packages too. |
111 |
</p> |
112 |
|
113 |
@@ -263,21 +260,24 @@ |
114 |
|
115 |
<ul> |
116 |
<li> |
117 |
- The <b>i686</b> architecture (athlon, athlon-xp, athlon-mp, pentium-pro, |
118 |
- pentium2, pentium3, pentium4 and pentium-m) |
119 |
- Note: The i686 packages are available on the Installer LiveCD. |
120 |
+ The <b>alpha</b> architecture (alpha) |
121 |
</li> |
122 |
<li> |
123 |
The <b>amd64</b> architecture (amd64) |
124 |
</li> |
125 |
<li> |
126 |
- The <b>sparc</b> architecture (sparc64) |
127 |
+ The <b>hppa</b> architecture (hppa1.1, hppa2.0) |
128 |
+ </li> |
129 |
+ <li> |
130 |
+ The <b>ppc</b> architecture (ppc32, ppc64) |
131 |
</li> |
132 |
<li> |
133 |
- The <b>ppc</b> architecture (G3, G4, G5) |
134 |
+ The <b>sparc</b> architecture (sparc64) |
135 |
</li> |
136 |
<li> |
137 |
- The <b>alpha</b> architecture |
138 |
+ The <b>x86</b> architecture (athlon, athlon-xp, athlon-mp, pentium-pro, |
139 |
+ pentium2, pentium3, pentium4 and pentium-m) Note: The packages are for x86 |
140 |
+ and are available on the Installer LiveCD. |
141 |
</li> |
142 |
</ul> |
143 |
|
144 |
|
145 |
|
146 |
|
147 |
1.4 +192 -54 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml |
148 |
|
149 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml?rev=1.4&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
150 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml?rev=1.4&content-type=text/plain&cvsroot=gentoo |
151 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml.diff?r1=1.3&r2=1.4&cvsroot=gentoo |
152 |
|
153 |
Index: hb-install-x86-medium.xml |
154 |
=================================================================== |
155 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml,v |
156 |
retrieving revision 1.3 |
157 |
retrieving revision 1.4 |
158 |
diff -u -r1.3 -r1.4 |
159 |
--- hb-install-x86-medium.xml 9 Feb 2006 19:19:30 -0000 1.3 |
160 |
+++ hb-install-x86-medium.xml 10 Feb 2006 17:46:25 -0000 1.4 |
161 |
@@ -4,12 +4,12 @@ |
162 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
163 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
164 |
|
165 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml,v 1.3 2006/02/09 19:19:30 fox2mike Exp $ --> |
166 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml,v 1.4 2006/02/10 17:46:25 fox2mike Exp $ --> |
167 |
|
168 |
<sections> |
169 |
|
170 |
-<version>5.5</version> |
171 |
-<date>2005-11-29</date> |
172 |
+<version>5.6</version> |
173 |
+<date>2006-02-09</date> |
174 |
|
175 |
<section> |
176 |
<title>Hardware Requirements</title> |
177 |
@@ -19,7 +19,7 @@ |
178 |
|
179 |
<p> |
180 |
Before we start, we first list what hardware requirements you need to |
181 |
-successfully install Gentoo on your box. |
182 |
+successfully install Gentoo on your box using the Installer LiveCD. |
183 |
</p> |
184 |
|
185 |
</body> |
186 |
@@ -31,11 +31,11 @@ |
187 |
<table> |
188 |
<tr> |
189 |
<th>CPU</th> |
190 |
- <ti>i486 or later</ti> |
191 |
+ <ti>i686 or later</ti> |
192 |
</tr> |
193 |
<tr> |
194 |
<th>Memory</th> |
195 |
- <ti>64 MB</ti> |
196 |
+ <ti>128 MB</ti> |
197 |
</tr> |
198 |
<tr> |
199 |
<th>Diskspace</th> |
200 |
@@ -90,11 +90,10 @@ |
201 |
|
202 |
<ul> |
203 |
<li> |
204 |
- The Installer LiveCD contains everything you need to install |
205 |
- Gentoo. It provides a graphical environment, a graphical as well as console |
206 |
- based installer which automatically carries out the installation for you, |
207 |
- source code for the extra applications you need to choose from, GRP |
208 |
- Packages and of course, the installation instructions for your architecture. |
209 |
+ The Installer LiveCD contains everything you need to install Gentoo. It |
210 |
+ provides a graphical environment, a graphical as well as console based |
211 |
+ installer which automatically carries out the installation for you, and of |
212 |
+ course, the installation instructions for your architecture. |
213 |
</li> |
214 |
<li> |
215 |
The Minimal Installation CD contains only a minimal environment that allows |
216 |
@@ -104,15 +103,6 @@ |
217 |
</li> |
218 |
</ul> |
219 |
|
220 |
-<p> |
221 |
-The Gentoo Linux Installer LiveCD also provides an additional resource that you |
222 |
-can exploit during the installation of your Gentoo system. It contains prebuilt |
223 |
-packages (also known as the GRP set) that allow you to easily and quickly |
224 |
-install additional applications (such as OpenOffice.org, GNOME, ...) |
225 |
-immediately after the Gentoo installation and right before you update your |
226 |
-Portage tree. |
227 |
-</p> |
228 |
- |
229 |
</body> |
230 |
</subsection> |
231 |
</section> |
232 |
@@ -246,30 +236,152 @@ |
233 |
<p> |
234 |
You can also provide kernel options. They represent optional settings you can |
235 |
(de)activate at will. The following list is the same as the one you receive |
236 |
-when you press F2 at the bootscreen. |
237 |
+when you press F2 through F7 at the bootscreen. |
238 |
</p> |
239 |
|
240 |
<pre caption="Options available to pass to your kernel of choice"> |
241 |
-- agpgart loads agpgart (use if you have graphic problems,lockups) |
242 |
-- acpi=on loads support for ACPI firmware |
243 |
-- ide=nodma force disabling of DMA for malfunctioning IDE devices |
244 |
-- doscsi scan for scsi devices (breaks some ethernet cards) |
245 |
-- dopcmcia starts pcmcia service for PCMCIA cdroms |
246 |
-- nofirewire disables firewire modules in initrd (for firewire cdroms,etc) |
247 |
-- nokeymap disables keymap selection for non-us keyboard layouts |
248 |
-- docache cache the entire runtime portion of cd in RAM, allows you |
249 |
- to umount /mnt/cdrom to mount another cdrom. |
250 |
-- nodetect causes hwsetup/kudzu and hotplug not to run |
251 |
-- nousb disables usb module load from initrd, disables hotplug |
252 |
-- nodhcp dhcp does not automatically start if nic detected |
253 |
-- nohotplug disables loading hotplug service |
254 |
-- noapic disable apic (try if having hardware problems nics,scsi,etc) |
255 |
-- noevms2 disable loading of EVMS2 modules |
256 |
-- nolvm2 disable loading of LVM2 modules |
257 |
-- hdx=stroke allows you to partition the whole harddrive even when your BIOS |
258 |
- can't handle large harddrives |
259 |
-- noload=module1[,module2[,...]] |
260 |
- disable loading of specific kernel modules |
261 |
+<comment>Hardware options:</comment> |
262 |
+ |
263 |
+acpi=on This loads support for ACPI and also causes the acpid daemon to |
264 |
+ be started by the CD on boot. This is only needed if your |
265 |
+ system requires ACPI to function properly. This is not |
266 |
+ required for Hyperthreading support. |
267 |
+ |
268 |
+acpi=off Completely disables ACPI. This is useful on some older |
269 |
+ systems, and is also a requirement for using APM. This will |
270 |
+ disable any Hyperthreading support of your processor. |
271 |
+ |
272 |
+console=X This sets up serial console access for the CD. The first |
273 |
+ option is the device, usually ttyS0 on x86, followed by any |
274 |
+ connection options, which are comma separated. The default |
275 |
+ options are 9600,8,n,1. |
276 |
+ |
277 |
+dmraid=X This allows for passing options to the device-mapper RAID |
278 |
+ subsystem. Options should be encapsulated in quotes. |
279 |
+ |
280 |
+doapm This loads APM driver support. This requires you to also use |
281 |
+ acpi=off. |
282 |
+ |
283 |
+dobladecenter This adds some extra pauses into the boot process for the slow |
284 |
+ USB CDROM of the IBM BladeCenter. |
285 |
+ |
286 |
+dopcmcia This loads support for PCMCIA and Cardbus hardware and also |
287 |
+ causes the pcmcia cardmgr to be started by the CD on boot. |
288 |
+ This is only required when booting from a PCMCIA/Cardbus device. |
289 |
+ |
290 |
+doscsi This loads support for most SCSI controllers. This is also a |
291 |
+ requirement for booting most USB devices, as they use the SCSI |
292 |
+ subsystem of the kernel. |
293 |
+ |
294 |
+hda=stroke This allows you to partition the whole hard disk even when your |
295 |
+ BIOS is unable to handle large disks. This option is only used |
296 |
+ on machines with an older BIOS. Replace hda with the device |
297 |
+ that is requiring this option. |
298 |
+ |
299 |
+ide=nodma This forces the disabling of DMA in the kernel and is required |
300 |
+ by some IDE chipsets and also by some CDROM drives. If your |
301 |
+ system is having trouble reading from your IDE CDROM, try this |
302 |
+ option. This also disables the default hdparm settings from |
303 |
+ being executed. |
304 |
+ |
305 |
+noapic This disables the Advanced Programmable Interrupt Controller |
306 |
+ that is present on newer motherboards. It has been known to |
307 |
+ cause some problems on older hardware. |
308 |
+ |
309 |
+nodetect This disables all of the autodetection done by the CD, |
310 |
+ including device autodetection and DHCP probing. This is |
311 |
+ useful for doing debugging of a failing CD or driver. |
312 |
+ |
313 |
+nodhcp This disables DHCP probing on detected network cards. This is |
314 |
+ useful on networks with only static addresses. |
315 |
+ |
316 |
+nodmraid Disables support for device-mapper RAID, such as that used for |
317 |
+ on-board IDE/SATA RAID controllers. |
318 |
+ |
319 |
+nofirewire This disables the loading of Firewire modules. This should only |
320 |
+ be necessary if your Firewire hardware is causing a problem |
321 |
+ with booting the CD. |
322 |
+ |
323 |
+nogpm This diables gpm console mouse support. |
324 |
+ |
325 |
+nohotplug This disables the loading of the hotplug and coldplug init |
326 |
+ scripts at boot. This is useful for doing debugging of a |
327 |
+ failing CD or driver. |
328 |
+ |
329 |
+nokeymap This disables the keymap selection used to select non-US |
330 |
+ keyboard layouts. |
331 |
+ |
332 |
+nolapic This disables the local APIC on Uniprocessor kernels. |
333 |
+ |
334 |
+nosata This disables the loading of Serial ATA modules. This is |
335 |
+ useful if your system is having problems with the SATA subsystem. |
336 |
+ |
337 |
+nosmp This disables SMP, or Symmetric Multiprocessing, on SMP-enabled |
338 |
+ kernels. This is useful for debugging SMP-related issues with |
339 |
+ certain drivers and motherboards. |
340 |
+ |
341 |
+nosound This disables sound support and volume setting. This is useful |
342 |
+ for systems where sound support causes problems. |
343 |
+ |
344 |
+nousb This disables the autoloading of USB modules. This is useful |
345 |
+ for debugging USB issues. |
346 |
+ |
347 |
+<comment>Volume/Device Management:</comment> |
348 |
+ |
349 |
+dodevfs This enables the deprecated device filesystem on 2.6 systems. |
350 |
+ You will also need to use noudev for this to take effect. |
351 |
+ Since devfs is the only option with a 2.4 kernel, this option |
352 |
+ has no effect if booting a 2.4 kernel. |
353 |
+ |
354 |
+doevms2 This enables support for IBM's pluggable EVMS, or Enterprise |
355 |
+ Volume Management System. This is not safe to use with lvm2. |
356 |
+ |
357 |
+dolvm2 This enables support for Linux's Logical Volume Management. |
358 |
+ This is not safe to use with evms2. |
359 |
+ |
360 |
+noudev This disables udev support on 2.6 kernels. This option |
361 |
+ requires that dodevfs is used. Since udev is not an option for |
362 |
+ 2.4 kernels, this options has no effect if booting a 2.4 |
363 |
+ kernel. |
364 |
+ |
365 |
+unionfs Enables support for Unionfs on supported CD images. This will |
366 |
+ create a writable Unionfs overlay in a tmpfs, allowing you to |
367 |
+ change any file on the CD. |
368 |
+ |
369 |
+unionfs=X Enables support for Unionfs on supported CD images. This will |
370 |
+ create a writable Unionfs overlay on the device you specify. |
371 |
+ The device must be formatted with a filesystem recognized and |
372 |
+ writable by the kernel. |
373 |
+ |
374 |
+<comment>Other options:</comment> |
375 |
+ |
376 |
+debug Enables debugging code. This might get messy, as it displays |
377 |
+ a lot of data to the screen. |
378 |
+ |
379 |
+docache This caches the entire runtime portion of the CD into RAM, |
380 |
+ which allows you to umount /mnt/cdrom and mount another CDROM. |
381 |
+ This option requires that you have at least twice as much |
382 |
+ available RAM as the size of the CD. |
383 |
+ |
384 |
+doload=X This causes the initial ramdisk to load any module listed, as |
385 |
+ well as dependencies. Replace X with the module name. Multiple |
386 |
+ modules can be specified by a comma-separated list. |
387 |
+ |
388 |
+noload=X This causes the initial ramdisk to skip the loading of a |
389 |
+ specific module that may be causing a problem. Syntax matches |
390 |
+ that of doload. |
391 |
+ |
392 |
+nox This causes an X-enabled LiveCD to not automatically start X, |
393 |
+ but rather, to drop to the command line instead. |
394 |
+ |
395 |
+scandelay This causes the CD to pause for 10 seconds during certain |
396 |
+ portions the boot process to allow for devices that are slow to |
397 |
+ initialize to be ready for use. |
398 |
+ |
399 |
+scandelay=X This allows you to specify a given delay, in seconds, to be |
400 |
+ added to certain portions of the boot process to allow for |
401 |
+ devices that are slow to initialize to be ready for use. |
402 |
+ Replace X with the number of seconds to pause. |
403 |
</pre> |
404 |
|
405 |
<p> |
406 |
@@ -288,13 +400,24 @@ |
407 |
installing Gentoo on a system with a non-US keyboard, make sure you |
408 |
immediately press Alt-F1 to switch to verbose mode and follow the prompt. If no |
409 |
selection is made in 10 seconds the default (US keyboard) will be accepted and |
410 |
-the boot process will continue. Once the boot process completes, Gnome will start |
411 |
-up and you will be automatically logged in to the "Live" Gentoo Linux as |
412 |
-"gentoo" in graphical mode. You will be logged in as "root", the superuser on |
413 |
-the other consoles and should have a root ("#") prompt there. You can switch to |
414 |
-those consoles by pressing Alt-F2, Alt-F3, Alt-F4 Alt-F5, Alt-F6. Get back to |
415 |
-the graphical desktop you started on by pressing Alt-F7. |
416 |
-</p> |
417 |
+the boot process will continue. Once the boot process completes, Gnome will |
418 |
+start up and you will be automatically logged in to the "Live" Gentoo Linux |
419 |
+system as "gentoo" in graphical mode. You will be logged in as "root", the |
420 |
+superuser on the other consoles and should have a root ("#") prompt there. You |
421 |
+can switch to those consoles by pressing Alt-F2, Alt-F3, Alt-F4 Alt-F5, Alt-F6. |
422 |
+Get back to the graphical desktop you started on by pressing Alt-F7. To switch |
423 |
+to other consoles from within X, you must prefix the above with Ctrl. You are |
424 |
+able to run commands as root from any terminal within the graphical environment |
425 |
+by using the <c>sudo</c> application. You can even become root within a |
426 |
+terminal to perform multiple tasks. |
427 |
+</p> |
428 |
+ |
429 |
+<pre caption="Using sudo to run applications"> |
430 |
+<comment>(Editing the group file)</comment> |
431 |
+# <i>sudo vi /etc/group</i> |
432 |
+<comment>(Becoming root for a session)</comment> |
433 |
+# <i>sudo su -</i> |
434 |
+</pre> |
435 |
|
436 |
</body> |
437 |
</subsection> |
438 |
@@ -308,7 +431,7 @@ |
439 |
vast majority of cases, it does a very good job. However, in some cases, it |
440 |
may not auto-load the kernel modules you need. If the PCI auto-detection |
441 |
missed some of your system's hardware, you will have to load the appropriate |
442 |
-kernel modules manually. |
443 |
+kernel modules manually. These tasks require root access. |
444 |
</p> |
445 |
|
446 |
<p> |
447 |
@@ -336,9 +459,9 @@ |
448 |
|
449 |
<p> |
450 |
If you are an advanced user, you might want to tweak the IDE hard disk |
451 |
-performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
452 |
-test the performance of your disk (execute it several times to get a |
453 |
-more precise impression): |
454 |
+performance using <c>hdparm</c>. You will need root access to use <c>hdparm</c>. |
455 |
+With the <c>-tT</c> options you can test the performance of your disk (execute |
456 |
+it several times to get a more precise impression): |
457 |
</p> |
458 |
|
459 |
<pre caption="Testing disk performance"> |
460 |
@@ -366,7 +489,8 @@ |
461 |
If you plan on giving other people access to your installation |
462 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
463 |
security reasons), you need to create the necessary user accounts and change |
464 |
-the root password. |
465 |
+the root password. You need root access to change the root password and add new |
466 |
+users. |
467 |
</p> |
468 |
|
469 |
<p> |
470 |
@@ -374,6 +498,7 @@ |
471 |
</p> |
472 |
|
473 |
<pre caption="Changing the root password"> |
474 |
+$ <i>sudo su -</i> |
475 |
# <i>passwd</i> |
476 |
New password: <comment>(Enter your new password)</comment> |
477 |
Re-enter password: <comment>(Re-enter your password)</comment> |
478 |
@@ -401,6 +526,18 @@ |
479 |
# <i>su - john</i> |
480 |
</pre> |
481 |
|
482 |
+<p> |
483 |
+You can also change the password for the "gentoo" user in the graphical |
484 |
+environment. This account is already suitable for use on the Internet. |
485 |
+</p> |
486 |
+ |
487 |
+<pre caption="Changing the gentoo password"> |
488 |
+$ <i>passwd</i> |
489 |
+New password: <comment>(Enter your new password)</comment> |
490 |
+Re-enter password: <comment>(Re-enter your password)</comment> |
491 |
+</pre> |
492 |
+ |
493 |
+ |
494 |
</body> |
495 |
</subsection> |
496 |
<subsection> |
497 |
@@ -450,7 +587,8 @@ |
498 |
Gentoo installation (perhaps because those users are going to help you |
499 |
install Gentoo, or even do it for you), you need to create a user |
500 |
account for them and perhaps even provide them with your root password |
501 |
-(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
502 |
+(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). Starting the |
503 |
+SSH daemon requires root access. |
504 |
</p> |
505 |
|
506 |
<p> |
507 |
|
508 |
|
509 |
|
510 |
1.3 +23 -21 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-about.xml |
511 |
|
512 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-about.xml?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
513 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-about.xml?rev=1.3&content-type=text/plain&cvsroot=gentoo |
514 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-about.xml.diff?r1=1.2&r2=1.3&cvsroot=gentoo |
515 |
|
516 |
|
517 |
|
518 |
|
519 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-network.xml |
520 |
|
521 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-network.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
522 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-network.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
523 |
|
524 |
Index: hb-install-x86-network.xml |
525 |
=================================================================== |
526 |
<?xml version='1.0' encoding='UTF-8'?> |
527 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
528 |
|
529 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
530 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
531 |
|
532 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-network.xml,v 1.1 2006/02/10 17:46:25 fox2mike Exp $ --> |
533 |
|
534 |
<sections> |
535 |
|
536 |
<version>5.1</version> |
537 |
<date>2006-02-09</date> |
538 |
|
539 |
<section> |
540 |
<title>Do you need Networking?</title> |
541 |
<subsection> |
542 |
<title>Who can do without?</title> |
543 |
<body> |
544 |
|
545 |
<p> |
546 |
Generally, you don't need a working network connection to install Gentoo using |
547 |
the Installer LiveCD. However, there are some circumstances where you do want |
548 |
to have a working Internet connection: |
549 |
</p> |
550 |
|
551 |
<ul> |
552 |
<li> |
553 |
The stage3 file that is generated by the Installer LiveCD does not |
554 |
match your architecture and you need to download the correct stage3 file |
555 |
</li> |
556 |
<li> |
557 |
You need to install a specific networking application that will allow you to |
558 |
connect to the Internet which isn't available on the Installer LiveCD |
559 |
CD but is supported by the LiveCD (i.e. you can connect to the |
560 |
Internet using the LiveCD but the necessary sources are not |
561 |
available on the LiveCD) |
562 |
</li> |
563 |
<li> |
564 |
You want remote assistance during the installation (using SSH or through |
565 |
direct conversations using IRC) |
566 |
</li> |
567 |
</ul> |
568 |
|
569 |
</body> |
570 |
</subsection> |
571 |
<subsection> |
572 |
<title>Do I need Networking?</title> |
573 |
<body> |
574 |
|
575 |
<p> |
576 |
The stage3 file built by the Installer LiveCD is optimized for i686 or better |
577 |
machines and uses NPTL. |
578 |
</p> |
579 |
|
580 |
<p> |
581 |
If you, on the other hand, want to use a stage3 file optimized for your |
582 |
architecture and the LiveCD's stage3 file is not sufficient, then you will |
583 |
need networking to download the appropriate stage3 file. |
584 |
</p> |
585 |
|
586 |
<p> |
587 |
So, if you don't need networking, you can skip the rest of this chapter and |
588 |
continue with <uri link="?part=1&chap=4">Preparing the Disks</uri>. |
589 |
Otherwise, continue with the networking configuration sections below. |
590 |
</p> |
591 |
|
592 |
</body> |
593 |
</subsection> |
594 |
</section> |
595 |
<section> |
596 |
<title>Automatic Network Detection</title> |
597 |
<subsection> |
598 |
<title>Maybe it just works?</title> |
599 |
<body> |
600 |
|
601 |
<p> |
602 |
If your system is plugged into an Ethernet network with a DHCP server, it is |
603 |
very likely that your networking configuration has already been set up |
604 |
automatically for you. If so, you should be able to take advantage of the many |
605 |
included network-aware commands on the Installation CD such as <c>ssh</c>, |
606 |
<c>scp</c>, <c>ping</c>, <c>irssi</c>, <c>wget</c> and <c>links</c>, among |
607 |
others. |
608 |
</p> |
609 |
|
610 |
<p> |
611 |
If networking has been configured for you, the <c>/sbin/ifconfig</c> command |
612 |
should list some network interfaces besides lo, such as eth0: |
613 |
</p> |
614 |
|
615 |
<pre caption="/sbin/ifconfig for a working network configuration"> |
616 |
# <i>/sbin/ifconfig</i> |
617 |
<comment>(...)</comment> |
618 |
eth0 Link encap:Ethernet HWaddr 00:50:BA:8F:61:7A |
619 |
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 |
620 |
inet6 addr: fe80::50:ba8f:617a/10 Scope:Link |
621 |
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 |
622 |
RX packets:1498792 errors:0 dropped:0 overruns:0 frame:0 |
623 |
TX packets:1284980 errors:0 dropped:0 overruns:0 carrier:0 |
624 |
collisions:1984 txqueuelen:100 |
625 |
RX bytes:485691215 (463.1 Mb) TX bytes:123951388 (118.2 Mb) |
626 |
Interrupt:11 Base address:0xe800 |
627 |
</pre> |
628 |
|
629 |
</body> |
630 |
</subsection> |
631 |
<subsection> |
632 |
<title>Optional: Configure any Proxies</title> |
633 |
<body> |
634 |
|
635 |
<p> |
636 |
If you access the Internet through a proxy, you might need to set up proxy |
637 |
information during the installation. It is very easy to define a proxy: you just |
638 |
need to define a variable which contains the proxy server information. |
639 |
</p> |
640 |
|
641 |
<p> |
642 |
In most cases, you can just define the variables using the server hostname. As |
643 |
an example, we assume the proxy is called <c>proxy.gentoo.org</c> and the port |
644 |
is <c>8080</c>. |
645 |
</p> |
646 |
|
647 |
<pre caption="Defining proxy servers"> |
648 |
<comment>(If the proxy filters HTTP traffic)</comment> |
649 |
# <i>export http_proxy="http://proxy.gentoo.org:8080"</i> |
650 |
<comment>(If the proxy filters FTP traffic)</comment> |
651 |
# <i>export ftp_proxy="ftp://proxy.gentoo.org:8080"</i> |
652 |
<comment>(If the proxy filters RSYNC traffic)</comment> |
653 |
# <i>export RSYNC_PROXY="proxy.gentoo.org:8080"</i> |
654 |
</pre> |
655 |
|
656 |
<p> |
657 |
If your proxy requires a username and password, you should use the following |
658 |
syntax for the variable: |
659 |
</p> |
660 |
|
661 |
<pre caption="Adding username/password to the proxy variable"> |
662 |
http://<i>username</i>:<i>password</i>@proxy.gentoo.org:8080 |
663 |
</pre> |
664 |
|
665 |
</body> |
666 |
</subsection> |
667 |
<subsection> |
668 |
<title>Testing the Network</title> |
669 |
<body> |
670 |
|
671 |
<p> |
672 |
You may want to try pinging your ISP's DNS server (found in |
673 |
<path>/etc/resolv.conf</path>) and a Web site of your choice, just to make sure |
674 |
that your packets are reaching the net, DNS name resolution is working |
675 |
correctly, etc. |
676 |
</p> |
677 |
|
678 |
<pre caption="Further network testing"> |
679 |
# <i>ping -c 3 www.yahoo.com</i> |
680 |
</pre> |
681 |
|
682 |
<p> |
683 |
If you are now able to use your network, you can skip the rest of this |
684 |
section and continue with <uri link="?part=1&chap=4">Preparing the |
685 |
Disks</uri>. If not, read on. |
686 |
</p> |
687 |
|
688 |
</body> |
689 |
</subsection> |
690 |
</section> |
691 |
<section> |
692 |
<title>Automatic Network Configuration</title> |
693 |
<subsection> |
694 |
<body> |
695 |
|
696 |
<p> |
697 |
If the network doesn't work immediately, some installation media allow you to |
698 |
use <c>net-setup</c> (for regular or wireless networks), <c>adsl-setup</c> |
699 |
(for ADSL-users) or <c>pptp</c> (for PPTP-users - only available on x86). |
700 |
</p> |
701 |
|
702 |
<p> |
703 |
If your installation medium does not contain any of these tools or your network |
704 |
doesn't function yet, continue with <uri link="#doc_chap3">Manual Network |
705 |
Configuration</uri>. |
706 |
</p> |
707 |
|
708 |
<ul> |
709 |
<li> |
710 |
Regular Ethernet users should continue with <uri |
711 |
link="#net-setup">Default: Using net-setup</uri> |
712 |
</li> |
713 |
<li> |
714 |
ADSL users should continue with <uri link="#rp-pppoe">Alternative: |
715 |
Using RP-PPPoE</uri> |
716 |
</li> |
717 |
<li> |
718 |
PPTP users should continue with <uri link="#pptp">Alternative: |
719 |
Using PPTP</uri> |
720 |
</li> |
721 |
</ul> |
722 |
|
723 |
</body> |
724 |
</subsection> |
725 |
<subsection id="net-setup"> |
726 |
<title>Default: Using net-setup</title> |
727 |
<body> |
728 |
|
729 |
<p> |
730 |
The simplest way to set up networking if it didn't get configured |
731 |
automatically is to run the <c>net-setup</c> script: |
732 |
</p> |
733 |
|
734 |
<pre caption="Running the net-setup script"> |
735 |
# <i>net-setup eth0</i> |
736 |
</pre> |
737 |
|
738 |
<p> |
739 |
<c>net-setup</c> will ask you some questions about your network |
740 |
environment. When all is done, you should have a working network |
741 |
connection. Test your network connection as stated before. If the tests |
742 |
are positive, congratulations! You are now ready to install Gentoo. Skip |
743 |
the rest of this section and continue with <uri |
744 |
link="?part=1&chap=4">Preparing the Disks</uri>. |
745 |
</p> |
746 |
|
747 |
<p> |
748 |
If your network still doesn't work, continue with <uri link="#doc_chap3">Manual |
749 |
Network Configuration</uri>. |
750 |
</p> |
751 |
|
752 |
|
753 |
</body> |
754 |
</subsection> |
755 |
<subsection id="rp-pppoe"> |
756 |
<title>Alternative: Using RP-PPPoE</title> |
757 |
<body> |
758 |
|
759 |
<p> |
760 |
Assuming you need PPPoE to connect to the internet, the Installation CD (any |
761 |
version) has made things easy for you by including <c>rp-pppoe</c>. Use the |
762 |
provided <c>adsl-setup</c> script to configure your connection. You will be |
763 |
prompted for the ethernet device that is connected to your adsl modem, your |
764 |
username and password, the IPs of your DNS servers and if you need a basic |
765 |
firewall or not. |
766 |
</p> |
767 |
|
768 |
<pre caption="Using rp-pppoe"> |
769 |
# <i>adsl-setup</i> |
770 |
# <i>adsl-start</i> |
771 |
</pre> |
772 |
|
773 |
<p> |
774 |
If something goes wrong, double-check that you correctly typed your username and |
775 |
password by looking at <path>/etc/ppp/pap-secrets</path> or |
776 |
<path>/etc/ppp/chap-secrets</path> and make sure you are using the right |
777 |
ethernet device. If your ethernet device doesn't exist, you will have to load |
778 |
the appropriate network modules. In that case you should continue with |
779 |
<uri link="#doc_chap3">Manual Network Configuration</uri> as we explain how to |
780 |
load the appropriate network modules there. |
781 |
</p> |
782 |
|
783 |
<p> |
784 |
If everything worked, continue with <uri link="?part=1&chap=4">Preparing the |
785 |
Disks</uri>. |
786 |
</p> |
787 |
|
788 |
</body> |
789 |
</subsection> |
790 |
<subsection id="pptp"> |
791 |
<title>Alternative: Using PPTP</title> |
792 |
<body> |
793 |
|
794 |
<note> |
795 |
PPTP support is only available for x86 |
796 |
</note> |
797 |
|
798 |
<p> |
799 |
If you need PPTP support, you can use <c>pptpclient</c> which is provided by our |
800 |
Installation CDs. But first you need to make sure that your configuration is |
801 |
correct. Edit <path>/etc/ppp/pap-secrets</path> or |
802 |
<path>/etc/ppp/chap-secrets</path> so it contains the correct username/password |
803 |
combination: |
804 |
</p> |
805 |
|
806 |
<pre caption="Editing /etc/ppp/chap-secrets"> |
807 |
# <i>nano -w /etc/ppp/chap-secrets</i> |
808 |
</pre> |
809 |
|
810 |
<p> |
811 |
Then adjust <path>/etc/ppp/options.pptp</path> if necessary: |
812 |
</p> |
813 |
|
814 |
<pre caption="Editing /etc/ppp/options.pptp"> |
815 |
# <i>nano -w /etc/ppp/options.pptp</i> |
816 |
</pre> |
817 |
|
818 |
<p> |
819 |
When all that is done, just run <c>pptp</c> (along with the options you couldn't |
820 |
set in <path>options.pptp</path>) to connect the server: |
821 |
</p> |
822 |
|
823 |
<pre caption="Connection to a dial-in server"> |
824 |
# <i>pptp <server ip></i> |
825 |
</pre> |
826 |
|
827 |
<p> |
828 |
Now continue with <uri link="?part=1&chap=4">Preparing the Disks</uri>. |
829 |
</p> |
830 |
|
831 |
</body> |
832 |
</subsection> |
833 |
</section> |
834 |
<section> |
835 |
<title>Manual Network Configuration</title> |
836 |
<subsection> |
837 |
<title>Loading the Appropriate Network Modules</title> |
838 |
<body> |
839 |
|
840 |
<p> |
841 |
When the Installation CD boots, it tries to detect all your hardware devices and |
842 |
loads the appropriate kernel modules (drivers) to support your hardware. In the |
843 |
vast majority of cases, it does a very good job. However, in some cases, |
844 |
it may not auto-load the kernel modules you need. |
845 |
</p> |
846 |
|
847 |
<p> |
848 |
If <c>net-setup</c> or <c>adsl-setup</c> failed, then it is possible that |
849 |
your network card wasn't found immediately. This means you may have to load |
850 |
the appropriate kernel modules manually. |
851 |
</p> |
852 |
|
853 |
<p> |
854 |
To find out what kernel modules we provide for networking, use |
855 |
<c>ls</c>: |
856 |
</p> |
857 |
|
858 |
<pre caption="Searching for provided modules"> |
859 |
# <i>ls /lib/modules/`uname -r`/kernel/drivers/net</i> |
860 |
</pre> |
861 |
|
862 |
<p> |
863 |
If you find a driver for your network card, use <c>modprobe</c> to load |
864 |
the kernel module: |
865 |
</p> |
866 |
|
867 |
<pre caption="Using modprobe to load a kernel module"> |
868 |
<comment>(As an example, we load the pcnet32 module)</comment> |
869 |
# <i>modprobe pcnet32</i> |
870 |
</pre> |
871 |
|
872 |
<p> |
873 |
To check if your network card is now detected, use <c>ifconfig</c>. A |
874 |
detected network card would result in something like this: |
875 |
</p> |
876 |
|
877 |
<pre caption="Testing availability of your network card, successful"> |
878 |
# <i>ifconfig eth0</i> |
879 |
eth0 Link encap:Ethernet HWaddr FE:FD:00:00:00:00 |
880 |
BROADCAST NOARP MULTICAST MTU:1500 Metric:1 |
881 |
RX packets:0 errors:0 dropped:0 overruns:0 frame:0 |
882 |
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 |
883 |
collisions:0 txqueuelen:0 |
884 |
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) |
885 |
</pre> |
886 |
|
887 |
<p> |
888 |
If however you receive the following error, the network card is not |
889 |
detected: |
890 |
</p> |
891 |
|
892 |
<pre caption="Testing availability of your network card, failed"> |
893 |
# <i>ifconfig eth0</i> |
894 |
eth0: error fetching interface information: Device not found |
895 |
</pre> |
896 |
|
897 |
<p> |
898 |
If you have multiple network cards in your system they are named <e>eth0</e>, |
899 |
<e>eth1</e>, etc. Make sure that the network card you want to use works well and |
900 |
remember to use the correct naming throughout this document. We will assume that |
901 |
the network card <e>eth0</e> is used. |
902 |
</p> |
903 |
|
904 |
<p> |
905 |
Assuming that you now have a detected network card, you can |
906 |
retry <c>net-setup</c> or <c>adsl-setup</c> again (which should work |
907 |
now), but for the hardcore people amongst you we explain how to configure your |
908 |
network manually. |
909 |
</p> |
910 |
|
911 |
<p> |
912 |
Select one of the following sections based on your network setup: |
913 |
</p> |
914 |
|
915 |
<ul> |
916 |
<li><uri link="#dhcp">Using DHCP</uri> for automatic IP retrieval</li> |
917 |
<li> |
918 |
<uri link="#wireless">Preparing for Wireless Access</uri> if you have a |
919 |
wireless card |
920 |
</li> |
921 |
<li> |
922 |
<uri link="#network_term">Understanding Network Terminology</uri> explains |
923 |
what you need to know about networking |
924 |
</li> |
925 |
<li> |
926 |
<uri link="#ifconfig_route">Using ifconfig and route</uri> explains how to |
927 |
set up your networking manually |
928 |
</li> |
929 |
</ul> |
930 |
|
931 |
</body> |
932 |
</subsection> |
933 |
<subsection id="dhcp"> |
934 |
<title>Using DHCP</title> |
935 |
<body> |
936 |
|
937 |
<p> |
938 |
DHCP (Dynamic Host Configuration Protocol) makes it possible to |
939 |
automatically receive networking information (IP address, netmask, |
940 |
broadcast address, gateway, nameservers etc.). This only works if you |
941 |
have a DHCP server in your network (or if your provider provides a DHCP |
942 |
service). To have a network interface receive this information automatically, |
943 |
use <c>dhcpcd</c>: |
944 |
</p> |
945 |
|
946 |
<pre caption="Using dhcpcd"> |
947 |
# <i>dhcpcd eth0</i> |
948 |
<comment>Some network admins require that you use the</comment> |
949 |
<comment>hostname and domainname provided by the DHCP server.</comment> |
950 |
<comment>In that case, use</comment> |
951 |
# <i>dhcpcd -HD eth0</i> |
952 |
</pre> |
953 |
|
954 |
<p> |
955 |
If this works (try pinging some internet server, like <uri |
956 |
link="http://www.google.com">Google</uri>), then you are all set and |
957 |
ready to continue. Skip the rest of this section and continue with <uri |
958 |
link="?part=1&chap=4">Preparing the Disks</uri>. |
959 |
</p> |
960 |
|
961 |
</body> |
962 |
</subsection> |
963 |
<subsection id="wireless"> |
964 |
<title>Preparing for Wireless Access</title> |
965 |
<body> |
966 |
|
967 |
<note> |
968 |
Support for the <c>iwconfig</c> command is only available on x86, amd64 and ppc |
969 |
Installation CDs. You can still get the extensions working otherwise |
970 |
by following the instructions of the |
971 |
<uri link="ftp://ftp.linux-wlan.org/pub/linux-wlan-ng/README">linux-wlan-ng |
972 |
project</uri>. |
973 |
</note> |
974 |
|
975 |
<p> |
976 |
If you are using a wireless (802.11) card, you may need to configure your |
977 |
wireless settings before going any further. To see the current wireless settings |
978 |
on your card, you can use <c>iwconfig</c>. Running <c>iwconfig</c> might show |
979 |
something like: |
980 |
</p> |
981 |
|
982 |
<pre caption="Showing the current wireless settings"> |
983 |
# <i>iwconfig eth0</i> |
984 |
eth0 IEEE 802.11-DS ESSID:"GentooNode" |
985 |
Mode:Managed Frequency:2.442GHz Access Point: 00:09:5B:11:CC:F2 |
986 |
Bit Rate:11Mb/s Tx-Power=20 dBm Sensitivity=0/65535 |
987 |
Retry limit:16 RTS thr:off Fragment thr:off |
988 |
Power Management:off |
989 |
Link Quality:25/10 Signal level:-51 dBm Noise level:-102 dBm |
990 |
Rx invalid nwid:5901 Rx invalid crypt:0 Rx invalid frag:0 Tx |
991 |
excessive retries:237 Invalid misc:350282 Missed beacon:84 |
992 |
</pre> |
993 |
|
994 |
<note> |
995 |
Some wireless cards may have a device name of <c>wlan0</c> or <c>ra0</c> instead |
996 |
of <c>eth0</c>. Run <c>iwconfig</c> without any command-line parameters to |
997 |
determine the correct device name. |
998 |
</note> |
999 |
|
1000 |
<p> |
1001 |
For most users, there are only two settings that might be important to change, |
1002 |
the ESSID (aka wireless network name) or the WEP key. If the ESSID and Access |
1003 |
Point address listed are already that of your access point and you are not using |
1004 |
WEP, then your wireless is working. If you need to change your ESSID, or add a |
1005 |
WEP key, you can issue the following commands: |
1006 |
</p> |
1007 |
|
1008 |
<pre caption="Changing ESSID and/or adding WEP key"> |
1009 |
<comment>(This sets the network name to "GentooNode")</comment> |
1010 |
# <i>iwconfig eth0 essid GentooNode</i> |
1011 |
|
1012 |
<comment>(This sets a hex WEP key)</comment> |
1013 |
# <i>iwconfig eth0 key 1234123412341234abcd</i> |
1014 |
|
1015 |
<comment>(This sets an ASCII key - prefix it with "s:")</comment> |
1016 |
# <i>iwconfig eth0 key s:some-password</i> |
1017 |
</pre> |
1018 |
|
1019 |
<p> |
1020 |
You can then confirm your wireless settings again by using <c>iwconfig</c>. |
1021 |
Once you have wireless working, you can continue configuring the IP level |
1022 |
networking options as described in the next section (<uri |
1023 |
link="#network_term">Understanding Network Terminology</uri>) or use the |
1024 |
<c>net-setup</c> tool as described previously. |
1025 |
</p> |
1026 |
|
1027 |
</body> |
1028 |
</subsection> |
1029 |
<subsection id="network_term"> |
1030 |
<title>Understanding Network Terminology</title> |
1031 |
<body> |
1032 |
|
1033 |
<note> |
1034 |
If you know your IP address, broadcast address, netmask and nameservers, |
1035 |
then you can skip this subsection and continue with <uri |
1036 |
link="#ifconfig_route">Using ifconfig and route</uri>. |
1037 |
</note> |
1038 |
|
1039 |
<p> |
1040 |
If all of the above fails, you will have to configure your network manually. |
1041 |
This is not difficult at all. However, you need to be familiar with some |
1042 |
network terminology, as you will need it to be able to |
1043 |
configure your network to your satisfaction. After reading this, you |
1044 |
will know what a <e>gateway</e> is, what a <e>netmask</e> serves for, |
1045 |
how a <e>broadcast</e> address is formed and why you need |
1046 |
<e>nameservers</e>. |
1047 |
</p> |
1048 |
|
1049 |
<p> |
1050 |
In a network, hosts are identified by their <e>IP address</e> (Internet |
1051 |
Protocol address). Such an address is a combination of four numbers |
1052 |
between 0 and 255. Well, at least that is how we perceive it. In |
1053 |
reality, such an IP address consists of 32 bits (ones and zeros). Let's |
1054 |
view an example: |
1055 |
</p> |
1056 |
|
1057 |
<pre caption="Example of an IP address"> |
1058 |
IP Address (numbers): 192.168.0.2 |
1059 |
IP Address (bits): 11000000 10101000 00000000 00000010 |
1060 |
-------- -------- -------- -------- |
1061 |
192 168 0 2 |
1062 |
</pre> |
1063 |
|
1064 |
<p> |
1065 |
Such an IP address is unique to a host as far as all accessible networks are |
1066 |
concerned (i.e. every host that you are able to reach must have a unique IP |
1067 |
address). In order to distinguish between hosts inside and outside a |
1068 |
network, the IP address is divided in two parts: the |
1069 |
<e>network</e> part and the <e>host</e> part. |
1070 |
</p> |
1071 |
|
1072 |
<p> |
1073 |
The separation is written down with the <e>netmask</e>, a collection of |
1074 |
ones followed by a collection of zeros. The part of the IP that can be |
1075 |
mapped on the ones is the network-part, the other one is the host-part. |
1076 |
As usual, the netmask can be written down as an IP-address. |
1077 |
</p> |
1078 |
|
1079 |
<pre caption="Example of network/host separation"> |
1080 |
IP-address: 192 168 0 2 |
1081 |
11000000 10101000 00000000 00000010 |
1082 |
Netmask: 11111111 11111111 11111111 00000000 |
1083 |
255 255 255 0 |
1084 |
+--------------------------+--------+ |
1085 |
Network Host |
1086 |
</pre> |
1087 |
|
1088 |
<p> |
1089 |
In other words, 192.168.0.14 is still part of our example network, but |
1090 |
192.168.1.2 is not. |
1091 |
</p> |
1092 |
|
1093 |
<p> |
1094 |
The <e>broadcast</e> address is an IP-address with the same network-part |
1095 |
as your network, but with only ones as host-part. Every host on your |
1096 |
network listens to this IP address. It is truly meant for broadcasting |
1097 |
packets. |
1098 |
</p> |
1099 |
|
1100 |
<pre caption="Broadcast address"> |
1101 |
IP-address: 192 168 0 2 |
1102 |
11000000 10101000 00000000 00000010 |
1103 |
Broadcast: 11000000 10101000 00000000 11111111 |
1104 |
192 168 0 255 |
1105 |
+--------------------------+--------+ |
1106 |
Network Host |
1107 |
</pre> |
1108 |
|
1109 |
<p> |
1110 |
To be able to surf on the internet, you must know which host shares the |
1111 |
Internet connection. This host is called the <e>gateway</e>. Since it is |
1112 |
a regular host, it has a regular IP address (for instance 192.168.0.1). |
1113 |
</p> |
1114 |
|
1115 |
<p> |
1116 |
We previously stated that every host has its own IP address. To be able |
1117 |
to reach this host by a name (instead of an IP address) you need a |
1118 |
service that translates a name (such as <e>dev.gentoo.org</e>) to an IP |
1119 |
address (such as <e>64.5.62.82</e>). Such a service is called a name |
1120 |
service. To use such a service, you must define the necessary <e>name |
1121 |
servers</e> in <path>/etc/resolv.conf</path>. |
1122 |
</p> |
1123 |
|
1124 |
<p> |
1125 |
In some cases, your gateway also serves as nameserver. Otherwise you |
1126 |
will have to enter the nameservers provided by your ISP. |
1127 |
</p> |
1128 |
|
1129 |
<p> |
1130 |
To summarise, you will need the following information before continuing: |
1131 |
</p> |
1132 |
|
1133 |
<table> |
1134 |
<tr> |
1135 |
<th>Network Item</th> |
1136 |
<th>Example</th> |
1137 |
</tr> |
1138 |
<tr> |
1139 |
<ti>Your IP address</ti> |
1140 |
<ti>192.168.0.2</ti> |
1141 |
</tr> |
1142 |
<tr> |
1143 |
<ti>Netmask</ti> |
1144 |
<ti>255.255.255.0</ti> |
1145 |
</tr> |
1146 |
<tr> |
1147 |
<ti>Broadcast</ti> |
1148 |
<ti>192.168.0.255</ti> |
1149 |
</tr> |
1150 |
<tr> |
1151 |
<ti>Gateway</ti> |
1152 |
<ti>192.168.0.1</ti> |
1153 |
</tr> |
1154 |
<tr> |
1155 |
<ti>Nameserver(s)</ti> |
1156 |
<ti>195.130.130.5, 195.130.130.133</ti> |
1157 |
</tr> |
1158 |
</table> |
1159 |
|
1160 |
</body> |
1161 |
</subsection> |
1162 |
<subsection id="ifconfig_route"> |
1163 |
<title>Using ifconfig and route</title> |
1164 |
<body> |
1165 |
|
1166 |
<p> |
1167 |
Setting up your network consists of three steps. First we assign |
1168 |
ourselves an IP address using <c>ifconfig</c>. Then we set up routing to |
1169 |
the gateway using <c>route</c>. Then we finish up by placing the |
1170 |
nameserver IPs in <path>/etc/resolv.conf</path>. |
1171 |
</p> |
1172 |
|
1173 |
<p> |
1174 |
To assign an IP address, you will need your IP address, broadcast |
1175 |
address and netmask. Then execute the following command, substituting |
1176 |
<c>${IP_ADDR}</c> with your IP address, <c>${BROADCAST}</c> with your |
1177 |
broadcast address and <c>${NETMASK}</c> with your netmask: |
1178 |
</p> |
1179 |
|
1180 |
<pre caption="Using ifconfig"> |
1181 |
# <i>ifconfig eth0 ${IP_ADDR} broadcast ${BROADCAST} netmask ${NETMASK} up</i> |
1182 |
</pre> |
1183 |
|
1184 |
<p> |
1185 |
Now set up routing using <c>route</c>. Substitute <c>${GATEWAY}</c> with |
1186 |
your gateway IP address: |
1187 |
</p> |
1188 |
|
1189 |
<pre caption="Using route"> |
1190 |
# <i>route add default gw ${GATEWAY}</i> |
1191 |
</pre> |
1192 |
|
1193 |
<p> |
1194 |
Now open <path>/etc/resolv.conf</path> with your favorite editor (in our |
1195 |
example, we use <c>nano</c>): |
1196 |
</p> |
1197 |
|
1198 |
<pre caption="Creating /etc/resolv.conf"> |
1199 |
# <i>nano -w /etc/resolv.conf</i> |
1200 |
</pre> |
1201 |
|
1202 |
<p> |
1203 |
Now fill in your nameserver(s) using the following as a template. Make |
1204 |
sure you substitute <c>${NAMESERVER1}</c> and <c>${NAMESERVER2}</c> with |
1205 |
the appropriate nameserver addresses: |
1206 |
</p> |
1207 |
|
1208 |
<pre caption="/etc/resolv.conf template"> |
1209 |
nameserver ${NAMESERVER1} |
1210 |
nameserver ${NAMESERVER2} |
1211 |
</pre> |
1212 |
|
1213 |
<p> |
1214 |
That's it. Now test your network by pinging some Internet server (like |
1215 |
<uri link="http://www.google.com">Google</uri>). If this works, |
1216 |
congratulations then. You are now ready to install Gentoo. Continue with <uri |
1217 |
link="?part=1&chap=4">Preparing the Disks</uri>. |
1218 |
</p> |
1219 |
|
1220 |
</body> |
1221 |
</subsection> |
1222 |
</section> |
1223 |
</sections> |
1224 |
|
1225 |
|
1226 |
|
1227 |
-- |
1228 |
gentoo-doc-cvs@g.o mailing list |