1 |
swift 07/08/01 18:25:54 |
2 |
|
3 |
Added: handbook-amd64.xml handbook-hppa.xml |
4 |
handbook-ppc64.xml handbook-ppc.xml |
5 |
handbook-sparc.xml handbook-x86.xml |
6 |
hb-install-about.xml hb-install-config.xml |
7 |
hb-install-finalise.xml hb-install-gli-dialog.xml |
8 |
hb-install-gli-medium.xml hb-install-gtkfe.xml |
9 |
hb-install-hppa-bootloader.xml |
10 |
hb-install-hppa-disk.xml hb-install-hppa-kernel.xml |
11 |
hb-install-hppa-medium.xml hb-install-network.xml |
12 |
hb-install-next.xml hb-install-ppc64-bootloader.xml |
13 |
hb-install-ppc64-disk.xml |
14 |
hb-install-ppc64-kernel.xml |
15 |
hb-install-ppc64-medium.xml |
16 |
hb-install-ppc-bootloader.xml |
17 |
hb-install-ppc-disk.xml hb-install-ppc-kernel.xml |
18 |
hb-install-ppc-medium.xml |
19 |
hb-install-sparc-bootloader.xml |
20 |
hb-install-sparc-disk.xml |
21 |
hb-install-sparc-kernel.xml |
22 |
hb-install-sparc-medium.xml hb-install-stage.xml |
23 |
hb-install-system.xml hb-install-tools.xml |
24 |
index.xml |
25 |
Log: |
26 |
Adding 2007.1 skeleton = full 2007.0 copy |
27 |
|
28 |
Revision Changes Path |
29 |
1.1 xml/htdocs/doc/en/handbook/2007.1/handbook-amd64.xml |
30 |
|
31 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-amd64.xml?rev=1.1&view=markup |
32 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-amd64.xml?rev=1.1&content-type=text/plain |
33 |
|
34 |
Index: handbook-amd64.xml |
35 |
=================================================================== |
36 |
<?xml version='1.0' encoding='UTF-8'?> |
37 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
38 |
|
39 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-amd64.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
40 |
|
41 |
<book link="/doc/en/handbook/2007.0/handbook-amd64.xml"> |
42 |
<title>Gentoo Linux 2007.0 AMD64 Networkless Handbook</title> |
43 |
|
44 |
<values> |
45 |
<key id="arch">AMD64</key> |
46 |
<key id="release-dir">releases/amd64/2007.0/</key> |
47 |
<key id="online-book">2007.0/handbook-amd64.xml</key> |
48 |
</values> |
49 |
|
50 |
<author title="Author"> |
51 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
52 |
</author> |
53 |
<author title="Author"> |
54 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
55 |
</author> |
56 |
<author title="Author"> |
57 |
<mail link="uberlord@g.o">Roy Marples</mail> |
58 |
</author> |
59 |
<author title="Author"> |
60 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
61 |
</author> |
62 |
<author title="Author"> |
63 |
<mail link="chouser@g.o">Chris Houser</mail> |
64 |
</author> |
65 |
<author title="Author"> |
66 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
67 |
</author> |
68 |
<author title="Author"> |
69 |
<mail link="nightmorph@g.o">Joshua Saddler</mail> |
70 |
</author> |
71 |
<author title="Gentoo x86 Developer"> |
72 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
73 |
</author> |
74 |
<author title="Gentoo Alpha Developer"> |
75 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
76 |
</author> |
77 |
<!-- Does not want to be listed on the rendered page |
78 |
<author title="Gentoo Developer"> |
79 |
Aron Griffis |
80 |
</author> |
81 |
--> |
82 |
<author title="Gentoo AMD64 Developer"> |
83 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
84 |
</author> |
85 |
<author title="Gentoo HPPA developer"> |
86 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
87 |
</author> |
88 |
<author title="Gentoo PPC developer"> |
89 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
90 |
</author> |
91 |
<author title="Gentoo SPARC developer"> |
92 |
<mail link="blademan@g.o">Joe Kallar</mail> |
93 |
</author> |
94 |
<author title="Editor"> |
95 |
<mail link="zhen@g.o">John P. Davis</mail> |
96 |
</author> |
97 |
<author title="Editor">Pierre-Henri Jondot</author> |
98 |
<author title="Editor"> |
99 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
100 |
</author> |
101 |
<author title="Editor"> |
102 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
103 |
</author> |
104 |
<author title="Editor"> |
105 |
<mail link="seo@g.o">Jungmin Seo</mail> |
106 |
</author> |
107 |
<author title="Editor"> |
108 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
109 |
</author> |
110 |
<author title="Editor"> |
111 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
112 |
</author> |
113 |
<author title="Editor"> |
114 |
<mail link="peitolm@g.o">Colin Morey</mail> |
115 |
</author> |
116 |
<author title="Editor"> |
117 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
118 |
</author> |
119 |
<author title="Editor"> |
120 |
<mail link="carl@g.o">Carl Anderson</mail> |
121 |
</author> |
122 |
<author title="Editor"> |
123 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
124 |
</author> |
125 |
<author title="Editor"> |
126 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
127 |
</author> |
128 |
<author title="Editor"> |
129 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
130 |
</author> |
131 |
<author title="Editor"> |
132 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
133 |
</author> |
134 |
<author title="Editor"> |
135 |
<mail link="erwin@g.o">Erwin</mail> |
136 |
</author> |
137 |
<author title="Editor"> |
138 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
139 |
</author> |
140 |
<author title="Editor"> |
141 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
142 |
</author> |
143 |
<author title="Editor"> |
144 |
<mail link="neysx@g.o">Xavier Neys</mail> |
145 |
</author> |
146 |
<author title="Editor"> |
147 |
<mail link="fox2mike@g.o">Shyam Mani</mail> |
148 |
</author> |
149 |
<author title="Reviewer"> |
150 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
151 |
</author> |
152 |
<author title="Reviewer"> |
153 |
<mail link="dberkholz@g.o">Donnie Berkholz</mail> |
154 |
</author> |
155 |
<author title="Reviewer"> |
156 |
<mail link="antifa@g.o">Ken Nowack</mail> |
157 |
</author> |
158 |
<author title="Contributor"> |
159 |
<mail link="pylon@g.o">Lars Weiler</mail> |
160 |
</author> |
161 |
|
162 |
<abstract> |
163 |
This is the Gentoo Networkless Handbook, an effort to centralise Gentoo/Linux |
164 |
information. This handbook contains the installation instructions for a |
165 |
networkless installation on AMD64 & EM64T systems and parts about working |
166 |
with Gentoo and Portage. |
167 |
</abstract> |
168 |
|
169 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
170 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
171 |
<license/> |
172 |
|
173 |
<version>8.1</version> |
174 |
<date>2007-06-06</date> |
175 |
|
176 |
<part> |
177 |
<title>Installing Gentoo</title> |
178 |
<abstract> |
179 |
In this part you learn how to install Gentoo on your system. |
180 |
</abstract> |
181 |
|
182 |
<chapter> |
183 |
<title>About the Gentoo Linux Installation</title> |
184 |
<abstract> |
185 |
Users not familiar with Gentoo do not always know that choice is what |
186 |
Gentoo is all about. |
187 |
</abstract> |
188 |
<include href="hb-install-about.xml"/> |
189 |
</chapter> |
190 |
|
191 |
<chapter> |
192 |
<title>Booting the Installer LiveCD</title> |
193 |
<abstract> |
194 |
Using our Installer LiveCD you can boot up your system into a running |
195 |
environment that allows you to install Gentoo. |
196 |
</abstract> |
197 |
<include href="hb-install-gli-medium.xml"/> |
198 |
</chapter> |
199 |
|
200 |
<chapter> |
201 |
<title>Using the GTK+ based Gentoo Linux Installer</title> |
202 |
<abstract> |
203 |
You now have an option of using our graphical installer to install Gentoo. |
204 |
Configure the options you need through an easy to use GUI and you're ready to |
205 |
go. |
206 |
</abstract> |
207 |
<include href="hb-install-gtkfe.xml" /> |
208 |
</chapter> |
209 |
|
210 |
<chapter> |
211 |
<title>Using the Dialog based Gentoo Linux Installer</title> |
212 |
<abstract> |
213 |
You also have an option of using our text based installer to install Gentoo. |
214 |
Configure the options you need through an easy to use set of menus and you're |
215 |
ready to go. |
216 |
</abstract> |
217 |
<include href="hb-install-gli-dialog.xml" /> |
218 |
</chapter> |
219 |
|
220 |
<chapter> |
221 |
<title>Where to go from here?</title> |
222 |
<abstract> |
223 |
Now you have your Gentoo system, but what's next? |
224 |
</abstract> |
225 |
<include href="hb-install-next.xml"/> |
226 |
</chapter> |
227 |
</part> |
228 |
|
229 |
<part> |
230 |
<title>Working with Gentoo</title> |
231 |
<abstract> |
232 |
Learn how to work with Gentoo: installing software, altering variables, |
233 |
changing Portage behaviour etc. |
234 |
</abstract> |
235 |
|
236 |
<chapter> |
237 |
<title>A Portage Introduction</title> |
238 |
<abstract> |
239 |
This chapter explains the "simple" steps a user definitely needs to know to |
240 |
maintain the software on his system. |
241 |
</abstract> |
242 |
<include href="../hb-working-portage.xml"/> |
243 |
</chapter> |
244 |
|
245 |
<chapter> |
246 |
<title>USE flags</title> |
247 |
<abstract> |
248 |
USE flags are a very important aspect of Gentoo. In this chapter, you learn to |
249 |
work with USE flags and understand how USE flags interact with your system. |
250 |
</abstract> |
251 |
<include href="../hb-working-use.xml"/> |
252 |
</chapter> |
253 |
|
254 |
<chapter> |
255 |
<title>Portage Features</title> |
256 |
<abstract> |
257 |
Discover the features Portage has, such as support for distributed compiling, |
258 |
ccache and more. |
259 |
</abstract> |
260 |
<include href="../hb-working-features.xml"/> |
261 |
</chapter> |
262 |
|
263 |
<chapter> |
264 |
<title>Initscripts</title> |
265 |
<abstract> |
266 |
Gentoo uses a special initscript format which, amongst other features, allows |
267 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
268 |
these aspects and explains how to deal with these scripts. |
269 |
</abstract> |
270 |
<include href="../hb-working-rcscripts.xml"/> |
271 |
</chapter> |
272 |
|
273 |
<chapter> |
274 |
<title>Environment Variables</title> |
275 |
<abstract> |
276 |
With Gentoo you can easily manage the environment variables for your system. |
277 |
This chapter explains how you do that, and also describes frequently used |
278 |
variables. |
279 |
</abstract> |
280 |
<include href="../hb-working-variables.xml"/> |
281 |
</chapter> |
282 |
</part> |
283 |
|
284 |
<part> |
285 |
<title>Working with Portage</title> |
286 |
<abstract> |
287 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
288 |
Software Management Tool. |
289 |
</abstract> |
290 |
|
291 |
<chapter> |
292 |
<title>Files and Directories</title> |
293 |
<abstract> |
294 |
Once you want to know Portage in-depth you need to know where it stores its |
295 |
files and data. |
296 |
</abstract> |
297 |
<include href="../hb-portage-files.xml"/> |
298 |
</chapter> |
299 |
|
300 |
<chapter> |
301 |
<title>Configuring through Variables</title> |
302 |
<abstract> |
303 |
Portage is completely configurable through various variables you can set in the |
304 |
configuration file or as environment variable. |
305 |
</abstract> |
306 |
<include href="../hb-portage-configuration.xml"/> |
307 |
</chapter> |
308 |
|
309 |
<chapter> |
310 |
<title>Mixing Software Branches</title> |
311 |
<abstract> |
312 |
Gentoo provides software separated in several branches, depending on stability |
313 |
and architectural support. "Mixing Software Branches" inform you how these |
314 |
branches can be configured and how you can override this separation |
315 |
individually. |
316 |
</abstract> |
317 |
<include href="../hb-portage-branches.xml"/> |
318 |
</chapter> |
319 |
|
320 |
<chapter> |
321 |
<title>Additional Portage Tools</title> |
322 |
<abstract> |
323 |
Portage comes with a few extra tools that might make your Gentoo experience even |
324 |
better. Read on to discover how to use dispatch-conf and other tools. |
325 |
</abstract> |
326 |
<include href="../hb-portage-tools.xml"/> |
327 |
</chapter> |
328 |
|
329 |
<chapter> |
330 |
<title>Diverting from the Official Tree</title> |
331 |
<abstract> |
332 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
333 |
your own Portage tree, how to synchronise only the categories you want, inject |
334 |
packages and more. |
335 |
</abstract> |
336 |
<include href="../hb-portage-diverttree.xml"/> |
337 |
</chapter> |
338 |
</part> |
339 |
|
340 |
<part> |
341 |
<title>Gentoo Network Configuration</title> |
342 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
343 |
|
344 |
<chapter> |
345 |
<title>Getting Started</title> |
346 |
<abstract> |
347 |
A guide to quickly get your network interface up and running in most common |
348 |
environments. |
349 |
</abstract> |
350 |
<include href="../hb-net-start.xml"/> |
351 |
</chapter> |
352 |
|
353 |
<chapter> |
354 |
<title>Advanced Configuration</title> |
355 |
<abstract> |
356 |
Here we learn about how the configuration works - you need to know this |
357 |
before we learn about modular networking. |
358 |
</abstract> |
359 |
<include href="../hb-net-advanced.xml"/> |
360 |
</chapter> |
361 |
|
362 |
<chapter> |
363 |
<title>Modular Networking</title> |
364 |
<abstract> |
365 |
Gentoo provides you flexible networking - here you are told about choosing |
366 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
367 |
</abstract> |
368 |
<include href="../hb-net-modules.xml"/> |
369 |
</chapter> |
370 |
|
371 |
<chapter> |
372 |
<title>Wireless Networking</title> |
373 |
<abstract> |
374 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
375 |
</abstract> |
376 |
<include href="../hb-net-wireless.xml"/> |
377 |
</chapter> |
378 |
|
379 |
<chapter> |
380 |
<title>Adding Functionality</title> |
381 |
<abstract> |
382 |
If you're feeling adventurous, you can add your own functions to networking. |
383 |
</abstract> |
384 |
<include href="../hb-net-functions.xml"/> |
385 |
</chapter> |
386 |
|
387 |
<chapter> |
388 |
<title>Network Management</title> |
389 |
<abstract> |
390 |
For laptop users or people who move their computer around different networks. |
391 |
</abstract> |
392 |
<include href="../hb-net-management.xml"/> |
393 |
</chapter> |
394 |
</part> |
395 |
|
396 |
</book> |
397 |
|
398 |
|
399 |
|
400 |
1.1 xml/htdocs/doc/en/handbook/2007.1/handbook-hppa.xml |
401 |
|
402 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-hppa.xml?rev=1.1&view=markup |
403 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-hppa.xml?rev=1.1&content-type=text/plain |
404 |
|
405 |
Index: handbook-hppa.xml |
406 |
=================================================================== |
407 |
<?xml version='1.0' encoding='UTF-8'?> |
408 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
409 |
|
410 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-hppa.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
411 |
|
412 |
<book link="/doc/en/handbook/2007.0/handbook-hppa.xml"> |
413 |
<title>Gentoo Linux 2007.0 HPPA Networkless Handbook</title> |
414 |
|
415 |
<values> |
416 |
<key id="arch">HPPA</key> |
417 |
<key id="/boot">/dev/sda2</key> |
418 |
<key id="kernel-version">2.6.20.1-hppa</key> |
419 |
<key id="kernel-name">kernel-2.6.20.1-hppa</key> |
420 |
<key id="online-book">2007.0/handbook-hppa.xml</key> |
421 |
<key id="release-dir">releases/hppa/2007.0/hppa2.0/</key> |
422 |
<key id="stage3">stage3-hppa2.0-2007.0.tar.bz2</key> |
423 |
<key id="CFLAGS">-march=2.0 -O2 -pipe</key> |
424 |
</values> |
425 |
|
426 |
<author title="Author"> |
427 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
428 |
</author> |
429 |
<author title="Author"> |
430 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
431 |
</author> |
432 |
<author title="Author"> |
433 |
<mail link="uberlord@g.o">Roy Marples</mail> |
434 |
</author> |
435 |
<author title="Author"> |
436 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
437 |
</author> |
438 |
<author title="Author"> |
439 |
<mail link="chouser@g.o">Chris Houser</mail> |
440 |
</author> |
441 |
<author title="Author"> |
442 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
443 |
</author> |
444 |
<author title="Gentoo x86 Developer"> |
445 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
446 |
</author> |
447 |
<author title="Gentoo Alpha Developer"> |
448 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
449 |
</author><!-- Does not want to be listed on the rendered page |
450 |
<author title="Gentoo Developer"> |
451 |
Aron Griffis |
452 |
</author> |
453 |
--> |
454 |
<author title="Gentoo AMD64 Developer"> |
455 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
456 |
</author> |
457 |
<author title="Gentoo HPPA developer"> |
458 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
459 |
</author> |
460 |
<author title="Gentoo PPC developer"> |
461 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
462 |
</author> |
463 |
<author title="Gentoo SPARC developer"> |
464 |
<mail link="blademan@g.o">Joe Kallar</mail> |
465 |
</author> |
466 |
<author title="Editor"> |
467 |
<mail link="zhen@g.o">John P. Davis</mail> |
468 |
</author> |
469 |
<author title="Editor">Pierre-Henri Jondot</author> |
470 |
<author title="Editor"> |
471 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
472 |
</author> |
473 |
<author title="Editor"> |
474 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
475 |
</author> |
476 |
<author title="Editor"> |
477 |
<mail link="seo@g.o">Jungmin Seo</mail> |
478 |
</author> |
479 |
<author title="Editor"> |
480 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
481 |
</author> |
482 |
<author title="Editor"> |
483 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
484 |
</author> |
485 |
<author title="Editor"> |
486 |
<mail link="peitolm@g.o">Colin Morey</mail> |
487 |
</author> |
488 |
<author title="Editor"> |
489 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
490 |
</author> |
491 |
<author title="Editor"> |
492 |
<mail link="carl@g.o">Carl Anderson</mail> |
493 |
</author> |
494 |
<author title="Editor"> |
495 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
496 |
</author> |
497 |
<author title="Editor"> |
498 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
499 |
</author> |
500 |
<author title="Editor"> |
501 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
502 |
</author> |
503 |
<author title="Editor"> |
504 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
505 |
</author> |
506 |
<author title="Editor"> |
507 |
<mail link="erwin@g.o">Erwin</mail> |
508 |
</author> |
509 |
<author title="Editor"> |
510 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
511 |
</author> |
512 |
<author title="Editor"> |
513 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
514 |
</author> |
515 |
<author title="Editor"> |
516 |
<mail link="neysx@g.o">Xavier Neys</mail> |
517 |
</author> |
518 |
<author title="Editor"> |
519 |
<mail link="nightmorph@g.o">Joshua Saddler</mail> |
520 |
</author> |
521 |
<author title="Reviewer"> |
522 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
523 |
</author> |
524 |
<author title="Reviewer"> |
525 |
<mail link="dberkholz@g.o">Donnie Berkholz</mail> |
526 |
</author> |
527 |
<author title="Reviewer"> |
528 |
<mail link="antifa@g.o">Ken Nowack</mail> |
529 |
</author> |
530 |
<author title="Contributor"> |
531 |
<mail link="pylon@g.o">Lars Weiler</mail> |
532 |
</author> |
533 |
|
534 |
<abstract> |
535 |
This is the Gentoo Networkless Handbook, an effort to centralise Gentoo/Linux |
536 |
information. This handbook contains the installation instructions for a |
537 |
networkless installation on HPPA systems and parts about working with Gentoo |
538 |
and Portage. |
539 |
</abstract> |
540 |
|
541 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
542 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
543 |
<license/> |
544 |
|
545 |
<version>8.1</version> |
546 |
<date>2007-06-06</date> |
547 |
|
548 |
<part> |
549 |
<title>Installing Gentoo</title> |
550 |
<abstract> |
551 |
In this part you learn how to install Gentoo on your system. |
552 |
</abstract> |
553 |
|
554 |
<chapter> |
555 |
<title>About the Gentoo Linux Installation</title> |
556 |
<abstract> |
557 |
Users not familiar with Gentoo do not always know that choice is what |
558 |
Gentoo is all about. |
559 |
</abstract> |
560 |
<include href="hb-install-about.xml"/> |
561 |
</chapter> |
562 |
|
563 |
<chapter> |
564 |
<title>Booting the Universal Installation CD</title> |
565 |
<abstract> |
566 |
Using our Universal Installation CD you can boot up your system into a running |
567 |
environment that allows you to install Gentoo. |
568 |
</abstract> |
569 |
<include href="hb-install-hppa-medium.xml"/> |
570 |
</chapter> |
571 |
|
572 |
<chapter> |
573 |
<title>Configuring your Network</title> |
574 |
<abstract> |
575 |
If you need networking, this is the place where the network (and Internet |
576 |
connection) is configured. |
577 |
</abstract> |
578 |
<include href="hb-install-network.xml"/> |
579 |
</chapter> |
580 |
|
581 |
<chapter> |
582 |
<title>Preparing the Disks</title> |
583 |
<abstract> |
584 |
To be able to install Gentoo, you must create the necessary partitions. |
585 |
This chapter describes how to partition a disk for future usage. |
586 |
</abstract> |
587 |
<include href="hb-install-hppa-disk.xml"/> |
588 |
</chapter> |
589 |
|
590 |
<chapter> |
591 |
<title>Installing the Gentoo Installation Files</title> |
592 |
<abstract> |
593 |
Gentoo installs work through so-called stage-files. In this chapter we |
594 |
describe how you extract a stage-file and configure Portage. |
595 |
</abstract> |
596 |
<include href="hb-install-stage.xml"/> |
597 |
</chapter> |
598 |
|
599 |
<chapter> |
600 |
<title>Chrooting into the Gentoo Base System</title> |
601 |
<abstract> |
602 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
603 |
the USE variable. |
604 |
</abstract> |
605 |
<include href="hb-install-system.xml"/> |
606 |
</chapter> |
607 |
|
608 |
<chapter> |
609 |
<title>Configuring the Kernel</title> |
610 |
<abstract> |
611 |
The Linux kernel is the core of every distribution. This chapter |
612 |
explains how to configure your kernel. |
613 |
</abstract> |
614 |
<include href="hb-install-hppa-kernel.xml"/> |
615 |
</chapter> |
616 |
|
617 |
<chapter> |
618 |
<title>Configuring your System</title> |
619 |
<abstract> |
620 |
You need to edit some important configuration files. In this chapter |
621 |
you receive an overview of these files and an explanation on how to |
622 |
proceed. |
623 |
</abstract> |
624 |
<include href="hb-install-config.xml"/> |
625 |
</chapter> |
626 |
|
627 |
<chapter> |
628 |
<title>Installing Necessary System Tools</title> |
629 |
<abstract> |
630 |
As mentioned before, Gentoo is about customization. In this chapter we help you |
631 |
choose and install some important tools. |
632 |
</abstract> |
633 |
<include href="hb-install-tools.xml"/> |
634 |
</chapter> |
635 |
|
636 |
<chapter> |
637 |
<title>Configuring the Bootloader</title> |
638 |
<abstract> |
639 |
In this chapter we'll describe the PALO bootloader |
640 |
and step you through the process of configuring PALO to your |
641 |
needs. |
642 |
</abstract> |
643 |
<include href="hb-install-hppa-bootloader.xml"/> |
644 |
</chapter> |
645 |
|
646 |
<chapter> |
647 |
<title>Finalizing your Gentoo Installation</title> |
648 |
<abstract> |
649 |
You're almost done. We'll just create one (or more) users for your |
650 |
system and (optionally) install prebuilt packages. |
651 |
</abstract> |
652 |
<include href="hb-install-finalise.xml"/> |
653 |
</chapter> |
654 |
|
655 |
<chapter> |
656 |
<title>Where to go from here?</title> |
657 |
<abstract> |
658 |
Now you have your Gentoo system, but what's next? |
659 |
</abstract> |
660 |
<include href="hb-install-next.xml"/> |
661 |
</chapter> |
662 |
</part> |
663 |
|
664 |
<part> |
665 |
<title>Working with Gentoo</title> |
666 |
<abstract> |
667 |
Learn how to work with Gentoo: installing software, altering variables, changing |
668 |
Portage behaviour etc. |
669 |
</abstract> |
670 |
|
671 |
<chapter> |
672 |
<title>A Portage Introduction</title> |
673 |
<abstract> |
674 |
This chapter explains the "simple" steps a user definitely needs to know to |
675 |
maintain the software on his system. |
676 |
</abstract> |
677 |
<include href="../hb-working-portage.xml"/> |
678 |
</chapter> |
679 |
|
680 |
<chapter> |
681 |
<title>USE flags</title> |
682 |
<abstract> |
683 |
USE flags are a very important aspect of Gentoo. In this chapter, you learn to |
684 |
work with USE flags and understand how USE flags interact with your system. |
685 |
</abstract> |
686 |
<include href="../hb-working-use.xml"/> |
687 |
</chapter> |
688 |
|
689 |
<chapter> |
690 |
<title>Portage Features</title> |
691 |
<abstract> |
692 |
Discover the features Portage has, such as support for distributed compiling, |
693 |
ccache and more. |
694 |
</abstract> |
695 |
<include href="../hb-working-features.xml"/> |
696 |
</chapter> |
697 |
|
698 |
<chapter> |
699 |
<title>Initscripts</title> |
700 |
<abstract> |
701 |
Gentoo uses a special initscript format which, amongst other features, allows |
702 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
703 |
these aspects and explains how to deal with these scripts. |
704 |
</abstract> |
705 |
<include href="../hb-working-rcscripts.xml"/> |
706 |
</chapter> |
707 |
|
708 |
<chapter> |
709 |
<title>Environment Variables</title> |
710 |
<abstract> |
711 |
With Gentoo you can easily manage the environment variables for your system. |
712 |
This chapter explains how you do that, and also describes frequently used |
713 |
variables. |
714 |
</abstract> |
715 |
<include href="../hb-working-variables.xml"/> |
716 |
</chapter> |
717 |
</part> |
718 |
|
719 |
<part> |
720 |
<title>Working with Portage</title> |
721 |
<abstract> |
722 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
723 |
Software Management Tool. |
724 |
</abstract> |
725 |
|
726 |
<chapter> |
727 |
<title>Files and Directories</title> |
728 |
<abstract> |
729 |
Once you want to know Portage in-depth you need to know where it stores its |
730 |
files and data. |
731 |
</abstract> |
732 |
<include href="../hb-portage-files.xml"/> |
733 |
</chapter> |
734 |
|
735 |
<chapter> |
736 |
<title>Configuring through Variables</title> |
737 |
<abstract> |
738 |
Portage is completely configurable through various variables you can set in the |
739 |
configuration file or as environment variable. |
740 |
</abstract> |
741 |
<include href="../hb-portage-configuration.xml"/> |
742 |
</chapter> |
743 |
|
744 |
<chapter> |
745 |
<title>Mixing Software Branches</title> |
746 |
<abstract> |
747 |
Gentoo provides software separated in several branches, depending on stability |
748 |
and architectural support. "Mixing Software Branches" inform you how these |
749 |
branches can be configured and how you can override this separation |
750 |
individually. |
751 |
</abstract> |
752 |
<include href="../hb-portage-branches.xml"/> |
753 |
</chapter> |
754 |
|
755 |
<chapter> |
756 |
<title>Additional Portage Tools</title> |
757 |
<abstract> |
758 |
Portage comes with a few extra tools that might make your Gentoo experience even |
759 |
better. Read on to discover how to use dispatch-conf and other tools. |
760 |
</abstract> |
761 |
<include href="../hb-portage-tools.xml"/> |
762 |
</chapter> |
763 |
|
764 |
<chapter> |
765 |
<title>Diverting from the Official Tree</title> |
766 |
<abstract> |
767 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
768 |
your own Portage tree, how to synchronise only the categories you want, inject |
769 |
packages and more. |
770 |
</abstract> |
771 |
<include href="../hb-portage-diverttree.xml"/> |
772 |
</chapter> |
773 |
</part> |
774 |
|
775 |
<part> |
776 |
<title>Gentoo Network Configuration</title> |
777 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
778 |
|
779 |
<chapter> |
780 |
<title>Getting Started</title> |
781 |
<abstract> |
782 |
A guide to quickly get your network interface up and running in most common |
783 |
environments. |
784 |
</abstract> |
785 |
<include href="../hb-net-start.xml"/> |
786 |
</chapter> |
787 |
|
788 |
<chapter> |
789 |
<title>Advanced Configuration</title> |
790 |
<abstract> |
791 |
Here we learn about how the configuration works - you need to know this |
792 |
before we learn about modular networking. |
793 |
</abstract> |
794 |
<include href="../hb-net-advanced.xml"/> |
795 |
</chapter> |
796 |
|
797 |
<chapter> |
798 |
<title>Modular Networking</title> |
799 |
<abstract> |
800 |
Gentoo provides you flexible networking - here you are told about choosing |
801 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
802 |
</abstract> |
803 |
<include href="../hb-net-modules.xml"/> |
804 |
</chapter> |
805 |
|
806 |
<chapter> |
807 |
<title>Wireless Networking</title> |
808 |
<abstract> |
809 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
810 |
</abstract> |
811 |
<include href="../hb-net-wireless.xml"/> |
812 |
</chapter> |
813 |
|
814 |
<chapter> |
815 |
<title>Adding Functionality</title> |
816 |
<abstract> |
817 |
If you're feeling adventurous, you can add your own functions to networking. |
818 |
</abstract> |
819 |
<include href="../hb-net-functions.xml"/> |
820 |
</chapter> |
821 |
|
822 |
<chapter> |
823 |
<title>Network Management</title> |
824 |
<abstract> |
825 |
For laptop users or people who move their computer around different networks. |
826 |
</abstract> |
827 |
<include href="../hb-net-management.xml"/> |
828 |
</chapter> |
829 |
</part> |
830 |
|
831 |
</book> |
832 |
|
833 |
|
834 |
|
835 |
1.1 xml/htdocs/doc/en/handbook/2007.1/handbook-ppc64.xml |
836 |
|
837 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-ppc64.xml?rev=1.1&view=markup |
838 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-ppc64.xml?rev=1.1&content-type=text/plain |
839 |
|
840 |
Index: handbook-ppc64.xml |
841 |
=================================================================== |
842 |
<?xml version='1.0' encoding='UTF-8'?> |
843 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
844 |
|
845 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-ppc64.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
846 |
|
847 |
<book link="/doc/en/handbook/2007.0/handbook-ppc64.xml"> |
848 |
<title>Gentoo Linux 2007.0 PPC64 Networkless Handbook</title> |
849 |
|
850 |
<values> |
851 |
<key id="arch">PPC64</key> |
852 |
<key id="kernel-version">2.6.19-r7</key> |
853 |
<key id="kernel-name">kernel-2.6.19-gentoo-r7</key> |
854 |
<key id="online-book">2007.0/handbook-ppc64.xml</key> |
855 |
<key id="release-dir">releases/ppc/2007.0/ppc64/</key> |
856 |
<key id="stage3">stage3-ppc64-32ul-2007.0.tar.bz2</key> |
857 |
<key id="CFLAGS">-O2 -pipe</key> |
858 |
</values> |
859 |
|
860 |
<author title="Author"> |
861 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
862 |
</author> |
863 |
<author title="Author"> |
864 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
865 |
</author> |
866 |
<author title="Author"> |
867 |
<mail link="uberlord@g.o">Roy Marples</mail> |
868 |
</author> |
869 |
<author title="Author"> |
870 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
871 |
</author> |
872 |
<author title="Author"> |
873 |
<mail link="chouser@g.o">Chris Houser</mail> |
874 |
</author> |
875 |
<author title="Author"> |
876 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
877 |
</author> |
878 |
<author title="Gentoo x86 Developer"> |
879 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
880 |
</author> |
881 |
<author title="Gentoo Alpha Developer"> |
882 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
883 |
</author><!-- Does not want to be listed on the rendered page |
884 |
<author title="Gentoo Developer"> |
885 |
Aron Griffis |
886 |
</author> |
887 |
--> |
888 |
<author title="Gentoo AMD64 Developer"> |
889 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
890 |
</author> |
891 |
<author title="Gentoo HPPA developer"> |
892 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
893 |
</author> |
894 |
<author title="Gentoo PPC developer"> |
895 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
896 |
</author> |
897 |
<author title="Gentoo SPARC developer"> |
898 |
<mail link="blademan@g.o">Joe Kallar</mail> |
899 |
</author> |
900 |
<author title="Editor"> |
901 |
<mail link="zhen@g.o">John P. Davis</mail> |
902 |
</author> |
903 |
<author title="Editor">Pierre-Henri Jondot</author> |
904 |
<author title="Editor"> |
905 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
906 |
</author> |
907 |
<author title="Editor"> |
908 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
909 |
</author> |
910 |
<author title="Editor"> |
911 |
<mail link="seo@g.o">Jungmin Seo</mail> |
912 |
</author> |
913 |
<author title="Editor"> |
914 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
915 |
</author> |
916 |
<author title="Editor"> |
917 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
918 |
</author> |
919 |
<author title="Editor"> |
920 |
<mail link="peitolm@g.o">Colin Morey</mail> |
921 |
</author> |
922 |
<author title="Editor"> |
923 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
924 |
</author> |
925 |
<author title="Editor"> |
926 |
<mail link="carl@g.o">Carl Anderson</mail> |
927 |
</author> |
928 |
<author title="Editor"> |
929 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
930 |
</author> |
931 |
<author title="Editor"> |
932 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
933 |
</author> |
934 |
<author title="Editor"> |
935 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
936 |
</author> |
937 |
<author title="Editor"> |
938 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
939 |
</author> |
940 |
<author title="Editor"> |
941 |
<mail link="erwin@g.o">Erwin</mail> |
942 |
</author> |
943 |
<author title="Editor"> |
944 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
945 |
</author> |
946 |
<author title="Editor"> |
947 |
<mail link="neysx@g.o">Xavier Neys</mail> |
948 |
</author> |
949 |
<author title="Editor"> |
950 |
<mail link="nightmorph@g.o">Joshua Saddler</mail> |
951 |
</author> |
952 |
<author title="Reviewer"> |
953 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
954 |
</author> |
955 |
<author title="Reviewer"> |
956 |
<mail link="dberkholz@g.o">Donnie Berkholz</mail> |
957 |
</author> |
958 |
<author title="Reviewer"> |
959 |
<mail link="antifa@g.o">Ken Nowack</mail> |
960 |
</author> |
961 |
<author title="Contributor"> |
962 |
<mail link="pylon@g.o">Lars Weiler</mail> |
963 |
</author> |
964 |
<author title="Editor"> |
965 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
966 |
</author> |
967 |
|
968 |
<abstract> |
969 |
This is the Gentoo Networkless Handbook, an effort to centralise Gentoo/Linux |
970 |
information. This handbook contains the installation instructions for a |
971 |
networkless installation on PPC64 systems and parts about working with Gentoo |
972 |
and Portage. |
973 |
</abstract> |
974 |
|
975 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
976 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
977 |
<license/> |
978 |
|
979 |
<version>8.1</version> |
980 |
<date>2007-06-06</date> |
981 |
|
982 |
<part> |
983 |
<title>Installing Gentoo</title> |
984 |
<abstract> |
985 |
In this part you learn how to install Gentoo on your system. |
986 |
</abstract> |
987 |
|
988 |
<chapter> |
989 |
<title>About the Gentoo Linux Installation</title> |
990 |
<abstract> |
991 |
Users not familiar with Gentoo do not always know that choice is what |
992 |
Gentoo is all about. |
993 |
</abstract> |
994 |
<include href="hb-install-about.xml"/> |
995 |
</chapter> |
996 |
|
997 |
<chapter> |
998 |
<title>Booting the Universal Installation CD</title> |
999 |
<abstract> |
1000 |
Using our Universal Installation CD you can boot up your system into a running |
1001 |
environment that allows you to install Gentoo. |
1002 |
</abstract> |
1003 |
<include href="hb-install-ppc64-medium.xml"/> |
1004 |
</chapter> |
1005 |
|
1006 |
<chapter> |
1007 |
<title>Configuring your Network</title> |
1008 |
<abstract> |
1009 |
If you need networking, this is the place where the network (and Internet |
1010 |
connection) is configured. |
1011 |
</abstract> |
1012 |
<include href="hb-install-network.xml"/> |
1013 |
</chapter> |
1014 |
|
1015 |
<chapter> |
1016 |
<title>Preparing the Disks</title> |
1017 |
<abstract> |
1018 |
To be able to install Gentoo, you must create the necessary partitions. |
1019 |
This chapter describes how to partition a disk for future usage. |
1020 |
</abstract> |
1021 |
<include href="hb-install-ppc64-disk.xml"/> |
1022 |
</chapter> |
1023 |
|
1024 |
<chapter> |
1025 |
<title>Installing the Gentoo Installation Files</title> |
1026 |
<abstract> |
1027 |
In this chapter we describe how you extract a stage3 file and how to configure |
1028 |
Portage. |
1029 |
</abstract> |
1030 |
<include href="hb-install-stage.xml"/> |
1031 |
</chapter> |
1032 |
|
1033 |
<chapter> |
1034 |
<title>Chrooting into the Gentoo Base System</title> |
1035 |
<abstract> |
1036 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
1037 |
the USE variable. |
1038 |
</abstract> |
1039 |
<include href="hb-install-system.xml"/> |
1040 |
</chapter> |
1041 |
|
1042 |
<chapter> |
1043 |
<title>Configuring the Kernel</title> |
1044 |
<abstract> |
1045 |
The Linux kernel is the core of every distribution. This chapter |
1046 |
explains how to configure your kernel. |
1047 |
</abstract> |
1048 |
<include href="hb-install-ppc64-kernel.xml"/> |
1049 |
</chapter> |
1050 |
|
1051 |
<chapter> |
1052 |
<title>Configuring your System</title> |
1053 |
<abstract> |
1054 |
You need to edit some important configuration files. In this chapter |
1055 |
you receive an overview of these files and an explanation on how to |
1056 |
proceed. |
1057 |
</abstract> |
1058 |
<include href="hb-install-config.xml"/> |
1059 |
</chapter> |
1060 |
|
1061 |
<chapter> |
1062 |
<title>Installing Necessary System Tools</title> |
1063 |
<abstract> |
1064 |
As mentioned before, Gentoo is about customization. In this chapter we help you |
1065 |
choose and install some important tools. |
1066 |
</abstract> |
1067 |
<include href="hb-install-tools.xml"/> |
1068 |
</chapter> |
1069 |
|
1070 |
<chapter> |
1071 |
<title>Configuring the Bootloader</title> |
1072 |
<abstract> |
1073 |
Several bootloaders exist. Each one of them has its own way of |
1074 |
configuration. In this chapter we'll describe all possibilities for you |
1075 |
and step you through the process of configuring a bootloader to your |
1076 |
needs. |
1077 |
</abstract> |
1078 |
<include href="hb-install-ppc64-bootloader.xml"/> |
1079 |
</chapter> |
1080 |
|
1081 |
|
1082 |
<chapter> |
1083 |
<title>Finalizing your Gentoo Installation</title> |
1084 |
<abstract> |
1085 |
You're almost done. We'll just create one (or more) users for your |
1086 |
system and (optionally) install prebuilt packages. |
1087 |
</abstract> |
1088 |
<include href="hb-install-finalise.xml"/> |
1089 |
</chapter> |
1090 |
|
1091 |
<chapter> |
1092 |
<title>Where to go from here?</title> |
1093 |
<abstract> |
1094 |
Now you have your Gentoo system, but what's next? |
1095 |
</abstract> |
1096 |
<include href="hb-install-next.xml"/> |
1097 |
</chapter> |
1098 |
</part> |
1099 |
|
1100 |
<part> |
1101 |
<title>Working with Gentoo</title> |
1102 |
<abstract> |
1103 |
Learn how to work with Gentoo: installing software, altering variables, changing |
1104 |
Portage behaviour etc. |
1105 |
</abstract> |
1106 |
|
1107 |
<chapter> |
1108 |
<title>A Portage Introduction</title> |
1109 |
<abstract> |
1110 |
This chapter explains the "simple" steps a user definitely needs to know to |
1111 |
maintain the software on his system. |
1112 |
</abstract> |
1113 |
<include href="../hb-working-portage.xml"/> |
1114 |
</chapter> |
1115 |
|
1116 |
<chapter> |
1117 |
<title>USE flags</title> |
1118 |
<abstract> |
1119 |
USE flags are a very important aspect of Gentoo. In this chapter, you learn to |
1120 |
work with USE flags and understand how USE flags interact with your system. |
1121 |
</abstract> |
1122 |
<include href="../hb-working-use.xml"/> |
1123 |
</chapter> |
1124 |
|
1125 |
<chapter> |
1126 |
<title>Portage Features</title> |
1127 |
<abstract> |
1128 |
Discover the features Portage has, such as support for distributed compiling, |
1129 |
ccache and more. |
1130 |
</abstract> |
1131 |
<include href="../hb-working-features.xml"/> |
1132 |
</chapter> |
1133 |
|
1134 |
<chapter> |
1135 |
<title>Initscripts</title> |
1136 |
<abstract> |
1137 |
Gentoo uses a special initscript format which, amongst other features, allows |
1138 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
1139 |
these aspects and explains how to deal with these scripts. |
1140 |
</abstract> |
1141 |
<include href="../hb-working-rcscripts.xml"/> |
1142 |
</chapter> |
1143 |
|
1144 |
<chapter> |
1145 |
<title>Environment Variables</title> |
1146 |
<abstract> |
1147 |
With Gentoo you can easily manage the environment variables for your system. |
1148 |
This chapter explains how you do that, and also describes frequently used |
1149 |
variables. |
1150 |
</abstract> |
1151 |
<include href="../hb-working-variables.xml"/> |
1152 |
</chapter> |
1153 |
</part> |
1154 |
|
1155 |
<part> |
1156 |
<title>Working with Portage</title> |
1157 |
<abstract> |
1158 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
1159 |
Software Management Tool. |
1160 |
</abstract> |
1161 |
|
1162 |
<chapter> |
1163 |
<title>Files and Directories</title> |
1164 |
<abstract> |
1165 |
Once you want to know Portage in-depth you need to know where it stores its |
1166 |
files and data. |
1167 |
</abstract> |
1168 |
<include href="../hb-portage-files.xml"/> |
1169 |
</chapter> |
1170 |
|
1171 |
<chapter> |
1172 |
<title>Configuring through Variables</title> |
1173 |
<abstract> |
1174 |
Portage is completely configurable through various variables you can set in the |
1175 |
configuration file or as environment variable. |
1176 |
</abstract> |
1177 |
<include href="../hb-portage-configuration.xml"/> |
1178 |
</chapter> |
1179 |
|
1180 |
<chapter> |
1181 |
<title>Mixing Software Branches</title> |
1182 |
<abstract> |
1183 |
Gentoo provides software separated in several branches, depending on stability |
1184 |
and architectural support. "Mixing Software Branches" inform you how these |
1185 |
branches can be configured and how you can override this separation |
1186 |
individually. |
1187 |
</abstract> |
1188 |
<include href="../hb-portage-branches.xml"/> |
1189 |
</chapter> |
1190 |
|
1191 |
<chapter> |
1192 |
<title>Additional Portage Tools</title> |
1193 |
<abstract> |
1194 |
Portage comes with a few extra tools that might make your Gentoo experience even |
1195 |
better. Read on to discover how to use dispatch-conf and other tools. |
1196 |
</abstract> |
1197 |
<include href="../hb-portage-tools.xml"/> |
1198 |
</chapter> |
1199 |
|
1200 |
<chapter> |
1201 |
<title>Diverting from the Official Tree</title> |
1202 |
<abstract> |
1203 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
1204 |
your own Portage tree, how to synchronise only the categories you want, inject |
1205 |
packages and more. |
1206 |
</abstract> |
1207 |
<include href="../hb-portage-diverttree.xml"/> |
1208 |
</chapter> |
1209 |
</part> |
1210 |
|
1211 |
<part> |
1212 |
<title>Gentoo Network Configuration</title> |
1213 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
1214 |
|
1215 |
<chapter> |
1216 |
<title>Getting Started</title> |
1217 |
<abstract> |
1218 |
A guide to quickly get your network interface up and running in most common |
1219 |
environments. |
1220 |
</abstract> |
1221 |
<include href="../hb-net-start.xml"/> |
1222 |
</chapter> |
1223 |
|
1224 |
<chapter> |
1225 |
<title>Advanced Configuration</title> |
1226 |
<abstract> |
1227 |
Here we learn about how the configuration works - you need to know this |
1228 |
before we learn about modular networking. |
1229 |
</abstract> |
1230 |
<include href="../hb-net-advanced.xml"/> |
1231 |
</chapter> |
1232 |
|
1233 |
<chapter> |
1234 |
<title>Modular Networking</title> |
1235 |
<abstract> |
1236 |
Gentoo provides you flexible networking - here you are told about choosing |
1237 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
1238 |
</abstract> |
1239 |
<include href="../hb-net-modules.xml"/> |
1240 |
</chapter> |
1241 |
|
1242 |
<chapter> |
1243 |
<title>Wireless Networking</title> |
1244 |
<abstract> |
1245 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
1246 |
</abstract> |
1247 |
<include href="../hb-net-wireless.xml"/> |
1248 |
</chapter> |
1249 |
|
1250 |
<chapter> |
1251 |
<title>Adding Functionality</title> |
1252 |
<abstract> |
1253 |
If you're feeling adventurous, you can add your own functions to networking. |
1254 |
</abstract> |
1255 |
<include href="../hb-net-functions.xml"/> |
1256 |
</chapter> |
1257 |
|
1258 |
<chapter> |
1259 |
<title>Network Management</title> |
1260 |
<abstract> |
1261 |
For laptop users or people who move their computer around different networks. |
1262 |
</abstract> |
1263 |
<include href="../hb-net-management.xml"/> |
1264 |
</chapter> |
1265 |
</part> |
1266 |
|
1267 |
</book> |
1268 |
|
1269 |
|
1270 |
|
1271 |
1.1 xml/htdocs/doc/en/handbook/2007.1/handbook-ppc.xml |
1272 |
|
1273 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-ppc.xml?rev=1.1&view=markup |
1274 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-ppc.xml?rev=1.1&content-type=text/plain |
1275 |
|
1276 |
Index: handbook-ppc.xml |
1277 |
=================================================================== |
1278 |
<?xml version='1.0' encoding='UTF-8'?> |
1279 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
1280 |
|
1281 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-ppc.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
1282 |
|
1283 |
<book link="/doc/en/handbook/2007.0/handbook-ppc.xml"> |
1284 |
<title>Gentoo Linux 2007.0 PPC Networkless Handbook</title> |
1285 |
|
1286 |
<values> |
1287 |
<key id="arch">PPC</key> |
1288 |
<key id="kernel-version">2.6.19-r5</key> |
1289 |
<key id="kernel-name">kernel-2.6.19-gentoo-r5</key> |
1290 |
<key id="kernel-gentoo">2.6.19-gentoo-r5</key> |
1291 |
<key id="online-book">2007.0/handbook-ppc.xml</key> |
1292 |
<key id="release-dir">releases/ppc/2007.0/ppc32/</key> |
1293 |
<key id="stage3">stage3-ppc-2007.0.tar.bz2</key> |
1294 |
<key id="CFLAGS">-O2 -mcpu=powerpc -mtune=powerpc -fno-strict-aliasing -pipe</key> |
1295 |
</values> |
1296 |
|
1297 |
<author title="Author"> |
1298 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
1299 |
</author> |
1300 |
<author title="Author"> |
1301 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
1302 |
</author> |
1303 |
<author title="Author"> |
1304 |
<mail link="uberlord@g.o">Roy Marples</mail> |
1305 |
</author> |
1306 |
<author title="Author"> |
1307 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
1308 |
</author> |
1309 |
<author title="Author"> |
1310 |
<mail link="chouser@g.o">Chris Houser</mail> |
1311 |
</author> |
1312 |
<author title="Author"> |
1313 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
1314 |
</author> |
1315 |
<author title="Gentoo x86 Developer"> |
1316 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
1317 |
</author> |
1318 |
<author title="Gentoo Alpha Developer"> |
1319 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
1320 |
</author><!-- Does not want to be listed on the rendered page |
1321 |
<author title="Gentoo Developer"> |
1322 |
Aron Griffis |
1323 |
</author> |
1324 |
--> |
1325 |
<author title="Gentoo AMD64 Developer"> |
1326 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
1327 |
</author> |
1328 |
<author title="Gentoo HPPA developer"> |
1329 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
1330 |
</author> |
1331 |
<author title="Gentoo PPC developer"> |
1332 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
1333 |
</author> |
1334 |
<author title="Gentoo SPARC developer"> |
1335 |
<mail link="blademan@g.o">Joe Kallar</mail> |
1336 |
</author> |
1337 |
<author title="Editor"> |
1338 |
<mail link="zhen@g.o">John P. Davis</mail> |
1339 |
</author> |
1340 |
<author title="Editor">Pierre-Henri Jondot</author> |
1341 |
<author title="Editor"> |
1342 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
1343 |
</author> |
1344 |
<author title="Editor"> |
1345 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
1346 |
</author> |
1347 |
<author title="Editor"> |
1348 |
<mail link="seo@g.o">Jungmin Seo</mail> |
1349 |
</author> |
1350 |
<author title="Editor"> |
1351 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
1352 |
</author> |
1353 |
<author title="Editor"> |
1354 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
1355 |
</author> |
1356 |
<author title="Editor"> |
1357 |
<mail link="peitolm@g.o">Colin Morey</mail> |
1358 |
</author> |
1359 |
<author title="Editor"> |
1360 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
1361 |
</author> |
1362 |
<author title="Editor"> |
1363 |
<mail link="carl@g.o">Carl Anderson</mail> |
1364 |
</author> |
1365 |
<author title="Editor"> |
1366 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
1367 |
</author> |
1368 |
<author title="Editor"> |
1369 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
1370 |
</author> |
1371 |
<author title="Editor"> |
1372 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
1373 |
</author> |
1374 |
<author title="Editor"> |
1375 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
1376 |
</author> |
1377 |
<author title="Editor"> |
1378 |
<mail link="erwin@g.o">Erwin</mail> |
1379 |
</author> |
1380 |
<author title="Editor"> |
1381 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
1382 |
</author> |
1383 |
<author title="Editor"> |
1384 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
1385 |
</author> |
1386 |
<author title="Editor"> |
1387 |
<mail link="pylon@g.o">Lars Weiler</mail> |
1388 |
</author> |
1389 |
<author title="Editor"> |
1390 |
<mail link="sejo@g.o">Jochen Maes </mail> |
1391 |
</author> |
1392 |
<author title="Editor"> |
1393 |
<mail link="neysx@g.o">Xavier Neys</mail> |
1394 |
</author> |
1395 |
<author title="Editor"> |
1396 |
<mail link="josejx@g.o">Joseph Jezak</mail> |
1397 |
</author> |
1398 |
<author title="Editor"> |
1399 |
<mail link="nightmorph@g.o">Joshua Saddler</mail> |
1400 |
</author> |
1401 |
<author title="Reviewer"> |
1402 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
1403 |
</author> |
1404 |
<author title="Reviewer"> |
1405 |
<mail link="dberkholz@g.o">Donnie Berkholz</mail> |
1406 |
</author> |
1407 |
<author title="Reviewer"> |
1408 |
<mail link="antifa@g.o">Ken Nowack</mail> |
1409 |
</author> |
1410 |
|
1411 |
<abstract> |
1412 |
This is the Gentoo Networkless Handbook, an effort to centralise Gentoo/Linux |
1413 |
information. This handbook contains the installation instructions for a |
1414 |
networkless installation on PPC systems and parts about working with Gentoo and |
1415 |
Portage. |
1416 |
</abstract> |
1417 |
|
1418 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
1419 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
1420 |
<license/> |
1421 |
|
1422 |
<version>8.1</version> |
1423 |
<date>2007-06-06</date> |
1424 |
|
1425 |
<part> |
1426 |
<title>Installing Gentoo</title> |
1427 |
<abstract> |
1428 |
In this part you learn how to install Gentoo on your system. |
1429 |
</abstract> |
1430 |
|
1431 |
<chapter> |
1432 |
<title>About the Gentoo Linux Installation</title> |
1433 |
<abstract> |
1434 |
Users not familiar with Gentoo do not always know that choice is what |
1435 |
Gentoo is all about. |
1436 |
</abstract> |
1437 |
<include href="hb-install-about.xml"/> |
1438 |
</chapter> |
1439 |
|
1440 |
<chapter> |
1441 |
<title>Booting the Universal Installation CD</title> |
1442 |
<abstract> |
1443 |
Using our Universal Installation CD you can boot up your system into a running |
1444 |
environment that allows you to install Gentoo. |
1445 |
</abstract> |
1446 |
<include href="hb-install-ppc-medium.xml"/> |
1447 |
</chapter> |
1448 |
|
1449 |
<chapter> |
1450 |
<title>Configuring your Network</title> |
1451 |
<abstract> |
1452 |
If you need networking, this is the place where the network (and Internet |
1453 |
connection) is configured. |
1454 |
</abstract> |
1455 |
<include href="hb-install-network.xml"/> |
1456 |
</chapter> |
1457 |
|
1458 |
<chapter> |
1459 |
<title>Preparing the Disks</title> |
1460 |
<abstract> |
1461 |
To be able to install Gentoo, you must create the necessary partitions. |
1462 |
This chapter describes how to partition a disk for future usage. |
1463 |
</abstract> |
1464 |
<include href="hb-install-ppc-disk.xml"/> |
1465 |
</chapter> |
1466 |
|
1467 |
<chapter> |
1468 |
<title>Installing the Gentoo Installation Files</title> |
1469 |
<abstract> |
1470 |
In this chapter we describe how you extract a stage3 file and how to configure |
1471 |
Portage. |
1472 |
</abstract> |
1473 |
<include href="hb-install-stage.xml"/> |
1474 |
</chapter> |
1475 |
|
1476 |
<chapter> |
1477 |
<title>Chrooting into the Gentoo Base System</title> |
1478 |
<abstract> |
1479 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
1480 |
the USE variable. |
1481 |
</abstract> |
1482 |
<include href="hb-install-system.xml"/> |
1483 |
</chapter> |
1484 |
|
1485 |
<chapter> |
1486 |
<title>Configuring the Kernel</title> |
1487 |
<abstract> |
1488 |
The Linux kernel is the core of every distribution. This chapter |
1489 |
explains how to configure your kernel. |
1490 |
</abstract> |
1491 |
<include href="hb-install-ppc-kernel.xml"/> |
1492 |
</chapter> |
1493 |
|
1494 |
<chapter> |
1495 |
<title>Configuring your System</title> |
1496 |
<abstract> |
1497 |
You need to edit some important configuration files. In this chapter |
1498 |
you receive an overview of these files and an explanation on how to |
1499 |
proceed. |
1500 |
</abstract> |
1501 |
<include href="hb-install-config.xml"/> |
1502 |
</chapter> |
1503 |
|
1504 |
<chapter> |
1505 |
<title>Installing Necessary System Tools</title> |
1506 |
<abstract> |
1507 |
As mentioned before, Gentoo is about customization. In this chapter we help you |
1508 |
choose and install some important tools. |
1509 |
</abstract> |
1510 |
<include href="hb-install-tools.xml"/> |
1511 |
</chapter> |
1512 |
|
1513 |
<chapter> |
1514 |
<title>Configuring the Bootloader</title> |
1515 |
<abstract> |
1516 |
Several bootloaders exist. Each one of them has its own way of |
1517 |
configuration. In this chapter we'll describe all possibilities for you |
1518 |
and step you through the process of configuring a bootloader to your |
1519 |
needs. |
1520 |
</abstract> |
1521 |
<include href="hb-install-ppc-bootloader.xml"/> |
1522 |
</chapter> |
1523 |
|
1524 |
<chapter> |
1525 |
<title>Finalizing your Gentoo Installation</title> |
1526 |
<abstract> |
1527 |
You're almost done. We'll just create one (or more) users for your |
1528 |
system and (optionally) install prebuilt packages. |
1529 |
</abstract> |
1530 |
<include href="hb-install-finalise.xml"/> |
1531 |
</chapter> |
1532 |
|
1533 |
<chapter> |
1534 |
<title>Where to go from here?</title> |
1535 |
<abstract> |
1536 |
Now you have your Gentoo system, but what's next? |
1537 |
</abstract> |
1538 |
<include href="hb-install-next.xml"/> |
1539 |
</chapter> |
1540 |
</part> |
1541 |
|
1542 |
<part> |
1543 |
<title>Working with Gentoo</title> |
1544 |
<abstract> |
1545 |
Learn how to work with Gentoo: installing software, altering variables, changing |
1546 |
Portage behaviour etc. |
1547 |
</abstract> |
1548 |
|
1549 |
<chapter> |
1550 |
<title>A Portage Introduction</title> |
1551 |
<abstract> |
1552 |
This chapter explains the "simple" steps a user definitely needs to know to |
1553 |
maintain the software on his system. |
1554 |
</abstract> |
1555 |
<include href="../hb-working-portage.xml"/> |
1556 |
</chapter> |
1557 |
|
1558 |
<chapter> |
1559 |
<title>USE flags</title> |
1560 |
<abstract> |
1561 |
USE flags are a very important aspect of Gentoo. In this chapter, you learn to |
1562 |
work with USE flags and understand how USE flags interact with your system. |
1563 |
</abstract> |
1564 |
<include href="../hb-working-use.xml"/> |
1565 |
</chapter> |
1566 |
|
1567 |
<chapter> |
1568 |
<title>Portage Features</title> |
1569 |
<abstract> |
1570 |
Discover the features Portage has, such as support for distributed compiling, |
1571 |
ccache and more. |
1572 |
</abstract> |
1573 |
<include href="../hb-working-features.xml"/> |
1574 |
</chapter> |
1575 |
|
1576 |
<chapter> |
1577 |
<title>Initscripts</title> |
1578 |
<abstract> |
1579 |
Gentoo uses a special initscript format which, amongst other features, allows |
1580 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
1581 |
these aspects and explains how to deal with these scripts. |
1582 |
</abstract> |
1583 |
<include href="../hb-working-rcscripts.xml"/> |
1584 |
</chapter> |
1585 |
|
1586 |
<chapter> |
1587 |
<title>Environment Variables</title> |
1588 |
<abstract> |
1589 |
With Gentoo you can easily manage the environment variables for your system. |
1590 |
This chapter explains how you do that, and also describes frequently used |
1591 |
variables. |
1592 |
</abstract> |
1593 |
<include href="../hb-working-variables.xml"/> |
1594 |
</chapter> |
1595 |
</part> |
1596 |
|
1597 |
<part> |
1598 |
<title>Working with Portage</title> |
1599 |
<abstract> |
1600 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
1601 |
Software Management Tool. |
1602 |
</abstract> |
1603 |
|
1604 |
<chapter> |
1605 |
<title>Files and Directories</title> |
1606 |
<abstract> |
1607 |
Once you want to know Portage in-depth you need to know where it stores its |
1608 |
files and data. |
1609 |
</abstract> |
1610 |
<include href="../hb-portage-files.xml"/> |
1611 |
</chapter> |
1612 |
|
1613 |
<chapter> |
1614 |
<title>Configuring through Variables</title> |
1615 |
<abstract> |
1616 |
Portage is completely configurable through various variables you can set in the |
1617 |
configuration file or as environment variable. |
1618 |
</abstract> |
1619 |
<include href="../hb-portage-configuration.xml"/> |
1620 |
</chapter> |
1621 |
|
1622 |
<chapter> |
1623 |
<title>Mixing Software Branches</title> |
1624 |
<abstract> |
1625 |
Gentoo provides software separated in several branches, depending on stability |
1626 |
and architectural support. "Mixing Software Branches" inform you how these |
1627 |
branches can be configured and how you can override this separation |
1628 |
individually. |
1629 |
</abstract> |
1630 |
<include href="../hb-portage-branches.xml"/> |
1631 |
</chapter> |
1632 |
|
1633 |
<chapter> |
1634 |
<title>Additional Portage Tools</title> |
1635 |
<abstract> |
1636 |
Portage comes with a few extra tools that might make your Gentoo experience even |
1637 |
better. Read on to discover how to use dispatch-conf and other tools. |
1638 |
</abstract> |
1639 |
<include href="../hb-portage-tools.xml"/> |
1640 |
</chapter> |
1641 |
|
1642 |
<chapter> |
1643 |
<title>Diverting from the Official Tree</title> |
1644 |
<abstract> |
1645 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
1646 |
your own Portage tree, how to synchronise only the categories you want, inject |
1647 |
packages and more. |
1648 |
</abstract> |
1649 |
<include href="../hb-portage-diverttree.xml"/> |
1650 |
</chapter> |
1651 |
</part> |
1652 |
|
1653 |
<part> |
1654 |
<title>Gentoo Network Configuration</title> |
1655 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
1656 |
|
1657 |
<chapter> |
1658 |
<title>Getting Started</title> |
1659 |
<abstract> |
1660 |
A guide to quickly get your network interface up and running in most common |
1661 |
environments. |
1662 |
</abstract> |
1663 |
<include href="../hb-net-start.xml"/> |
1664 |
</chapter> |
1665 |
|
1666 |
<chapter> |
1667 |
<title>Advanced Configuration</title> |
1668 |
<abstract> |
1669 |
Here we learn about how the configuration works - you need to know this |
1670 |
before we learn about modular networking. |
1671 |
</abstract> |
1672 |
<include href="../hb-net-advanced.xml"/> |
1673 |
</chapter> |
1674 |
|
1675 |
<chapter> |
1676 |
<title>Modular Networking</title> |
1677 |
<abstract> |
1678 |
Gentoo provides you flexible networking - here you are told about choosing |
1679 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
1680 |
</abstract> |
1681 |
<include href="../hb-net-modules.xml"/> |
1682 |
</chapter> |
1683 |
|
1684 |
<chapter> |
1685 |
<title>Wireless Networking</title> |
1686 |
<abstract> |
1687 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
1688 |
</abstract> |
1689 |
<include href="../hb-net-wireless.xml"/> |
1690 |
</chapter> |
1691 |
|
1692 |
<chapter> |
1693 |
<title>Adding Functionality</title> |
1694 |
<abstract> |
1695 |
If you're feeling adventurous, you can add your own functions to networking. |
1696 |
</abstract> |
1697 |
<include href="../hb-net-functions.xml"/> |
1698 |
</chapter> |
1699 |
|
1700 |
<chapter> |
1701 |
<title>Network Management</title> |
1702 |
<abstract> |
1703 |
For laptop users or people who move their computer around different networks. |
1704 |
</abstract> |
1705 |
<include href="../hb-net-management.xml"/> |
1706 |
</chapter> |
1707 |
</part> |
1708 |
|
1709 |
</book> |
1710 |
|
1711 |
|
1712 |
|
1713 |
1.1 xml/htdocs/doc/en/handbook/2007.1/handbook-sparc.xml |
1714 |
|
1715 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-sparc.xml?rev=1.1&view=markup |
1716 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-sparc.xml?rev=1.1&content-type=text/plain |
1717 |
|
1718 |
Index: handbook-sparc.xml |
1719 |
=================================================================== |
1720 |
<?xml version='1.0' encoding='UTF-8'?> |
1721 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
1722 |
|
1723 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-sparc.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
1724 |
|
1725 |
<book link="/doc/en/handbook/2007.0/handbook-sparc.xml"> |
1726 |
<title>Gentoo Linux 2007.0 SPARC Networkless Handbook</title> |
1727 |
|
1728 |
<values> |
1729 |
<key id="arch">SPARC</key> |
1730 |
<key id="kernel-name">kernel-2.6.20-gentoo-r4</key> |
1731 |
<key id="kernel-version">2.6.20-r4</key> |
1732 |
<key id="online-book">2007.0/handbook-sparc.xml</key> |
1733 |
<key id="release-dir">releases/sparc/2007.0/sparc64/</key> |
1734 |
<key id="stage3">stage3-sparc64-2007.0.tar.bz2</key> |
1735 |
<key id="CFLAGS">-O2 -mcpu=ultrasparc -pipe</key> |
1736 |
</values> |
1737 |
|
1738 |
<author title="Author"> |
1739 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
1740 |
</author> |
1741 |
<author title="Author"> |
1742 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
1743 |
</author> |
1744 |
<author title="Author"> |
1745 |
<mail link="uberlord@g.o">Roy Marples</mail> |
1746 |
</author> |
1747 |
<author title="Author"> |
1748 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
1749 |
</author> |
1750 |
<author title="Author"> |
1751 |
<mail link="chouser@g.o">Chris Houser</mail> |
1752 |
</author> |
1753 |
<author title="Author"> |
1754 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
1755 |
</author> |
1756 |
<author title="Gentoo x86 Developer"> |
1757 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
1758 |
</author> |
1759 |
<author title="Gentoo Alpha Developer"> |
1760 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
1761 |
</author><!-- Does not want to be listed on the rendered page |
1762 |
<author title="Gentoo Developer"> |
1763 |
Aron Griffis |
1764 |
</author> |
1765 |
--> |
1766 |
<author title="Gentoo AMD64 Developer"> |
1767 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
1768 |
</author> |
1769 |
<author title="Gentoo HPPA developer"> |
1770 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
1771 |
</author> |
1772 |
<author title="Gentoo PPC developer"> |
1773 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
1774 |
</author> |
1775 |
<author title="Gentoo SPARC developer"> |
1776 |
<mail link="blademan@g.o">Joe Kallar</mail> |
1777 |
</author> |
1778 |
<author title="Editor"> |
1779 |
<mail link="zhen@g.o">John P. Davis</mail> |
1780 |
</author> |
1781 |
<author title="Editor">Pierre-Henri Jondot</author> |
1782 |
<author title="Editor"> |
1783 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
1784 |
</author> |
1785 |
<author title="Editor"> |
1786 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
1787 |
</author> |
1788 |
<author title="Editor"> |
1789 |
<mail link="seo@g.o">Jungmin Seo</mail> |
1790 |
</author> |
1791 |
<author title="Editor"> |
1792 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
1793 |
</author> |
1794 |
<author title="Editor"> |
1795 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
1796 |
</author> |
1797 |
<author title="Editor"> |
1798 |
<mail link="peitolm@g.o">Colin Morey</mail> |
1799 |
</author> |
1800 |
<author title="Editor"> |
1801 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
1802 |
</author> |
1803 |
<author title="Editor"> |
1804 |
<mail link="carl@g.o">Carl Anderson</mail> |
1805 |
</author> |
1806 |
<author title="Editor"> |
1807 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
1808 |
</author> |
1809 |
<author title="Editor"> |
1810 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
1811 |
</author> |
1812 |
<author title="Editor"> |
1813 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
1814 |
</author> |
1815 |
<author title="Editor"> |
1816 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
1817 |
</author> |
1818 |
<author title="Editor"> |
1819 |
<mail link="erwin@g.o">Erwin</mail> |
1820 |
</author> |
1821 |
<author title="Editor"> |
1822 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
1823 |
</author> |
1824 |
<author title="Editor"> |
1825 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
1826 |
</author> |
1827 |
<author title="Editor"> |
1828 |
<mail link="neysx@g.o">Xavier Neys</mail> |
1829 |
</author> |
1830 |
<author title="Editor"> |
1831 |
<mail link="nightmorph@g.o">Joshua Saddler</mail> |
1832 |
</author> |
1833 |
<author title="Reviewer"> |
1834 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
1835 |
</author> |
1836 |
<author title="Reviewer"> |
1837 |
<mail link="dberkholz@g.o">Donnie Berkholz</mail> |
1838 |
</author> |
1839 |
<author title="Reviewer"> |
1840 |
<mail link="antifa@g.o">Ken Nowack</mail> |
1841 |
</author> |
1842 |
<author title="Contributor"> |
1843 |
<mail link="pylon@g.o">Lars Weiler</mail> |
1844 |
</author> |
1845 |
|
1846 |
<abstract> |
1847 |
This is the Gentoo Networkless Handbook, an effort to centralise Gentoo/Linux |
1848 |
information. This handbook contains the installation instructions for a |
1849 |
networkless installation on Sparc systems and parts about working with Gentoo |
1850 |
and Portage. |
1851 |
</abstract> |
1852 |
|
1853 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
1854 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
1855 |
<license/> |
1856 |
|
1857 |
<version>8.1</version> |
1858 |
<date>2007-06-06</date> |
1859 |
|
1860 |
<part> |
1861 |
<title>Installing Gentoo</title> |
1862 |
<abstract> |
1863 |
In this part you learn how to install Gentoo on your system. |
1864 |
</abstract> |
1865 |
|
1866 |
<chapter> |
1867 |
<title>About the Gentoo Linux Installation</title> |
1868 |
<abstract> |
1869 |
Users not familiar with Gentoo do not always know that choice is what |
1870 |
Gentoo is all about. |
1871 |
</abstract> |
1872 |
<include href="hb-install-about.xml"/> |
1873 |
</chapter> |
1874 |
|
1875 |
<chapter> |
1876 |
<title>Booting the Universal Installation CD</title> |
1877 |
<abstract> |
1878 |
Using our Universal Installation CD you can boot up your system into a running |
1879 |
environment that allows you to install Gentoo. |
1880 |
</abstract> |
1881 |
<include href="hb-install-sparc-medium.xml"/> |
1882 |
</chapter> |
1883 |
|
1884 |
<chapter> |
1885 |
<title>Configuring your Network</title> |
1886 |
<abstract> |
1887 |
If you need networking, this is the place where the network (and Internet |
1888 |
connection) is configured. |
1889 |
</abstract> |
1890 |
<include href="hb-install-network.xml"/> |
1891 |
</chapter> |
1892 |
|
1893 |
<chapter> |
1894 |
<title>Preparing the Disks</title> |
1895 |
<abstract> |
1896 |
To be able to install Gentoo, you must create the necessary partitions. |
1897 |
This chapter describes how to partition a disk for future usage. |
1898 |
</abstract> |
1899 |
<include href="hb-install-sparc-disk.xml"/> |
1900 |
</chapter> |
1901 |
|
1902 |
<chapter> |
1903 |
<title>Installing the Gentoo Installation Files</title> |
1904 |
<abstract> |
1905 |
In this chapter we describe how you extract a stage3 file and how to configure |
1906 |
Portage. |
1907 |
</abstract> |
1908 |
<include href="hb-install-stage.xml"/> |
1909 |
</chapter> |
1910 |
|
1911 |
<chapter> |
1912 |
<title>Chrooting into the Gentoo Base System</title> |
1913 |
<abstract> |
1914 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
1915 |
the USE variable. |
1916 |
</abstract> |
1917 |
<include href="hb-install-system.xml"/> |
1918 |
</chapter> |
1919 |
|
1920 |
<chapter> |
1921 |
<title>Configuring the Kernel</title> |
1922 |
<abstract> |
1923 |
The Linux kernel is the core of every distribution. This chapter |
1924 |
explains how to configure your kernel. |
1925 |
</abstract> |
1926 |
<include href="hb-install-sparc-kernel.xml"/> |
1927 |
</chapter> |
1928 |
|
1929 |
<chapter> |
1930 |
<title>Configuring your System</title> |
1931 |
<abstract> |
1932 |
You need to edit some important configuration files. In this chapter |
1933 |
you receive an overview of these files and an explanation on how to |
1934 |
proceed. |
1935 |
</abstract> |
1936 |
<include href="hb-install-config.xml"/> |
1937 |
</chapter> |
1938 |
|
1939 |
<chapter> |
1940 |
<title>Installing Necessary System Tools</title> |
1941 |
<abstract> |
1942 |
As mentioned before, Gentoo is about customization. In this chapter we help you |
1943 |
choose and install some important tools. |
1944 |
</abstract> |
1945 |
<include href="hb-install-tools.xml"/> |
1946 |
</chapter> |
1947 |
|
1948 |
<chapter> |
1949 |
<title>Configuring the Bootloader</title> |
1950 |
<abstract> |
1951 |
The SPARC architecture uses the SILO bootloader to fire up your Linux system. In |
1952 |
this chapter we step you through the process of configuring this bootloader to |
1953 |
your needs. |
1954 |
</abstract> |
1955 |
<include href="hb-install-sparc-bootloader.xml"/> |
1956 |
</chapter> |
1957 |
|
1958 |
<chapter> |
1959 |
<title>Finalizing your Gentoo Installation</title> |
1960 |
<abstract> |
1961 |
You're almost done. We'll just create one (or more) users for your |
1962 |
system and (optionally) install prebuilt packages. |
1963 |
</abstract> |
1964 |
<include href="hb-install-finalise.xml"/> |
1965 |
</chapter> |
1966 |
|
1967 |
<chapter> |
1968 |
<title>Where to go from here?</title> |
1969 |
<abstract> |
1970 |
Now you have your Gentoo system, but what's next? |
1971 |
</abstract> |
1972 |
<include href="hb-install-next.xml"/> |
1973 |
</chapter> |
1974 |
</part> |
1975 |
|
1976 |
<part> |
1977 |
<title>Working with Gentoo</title> |
1978 |
<abstract> |
1979 |
Learn how to work with Gentoo: installing software, altering variables, changing |
1980 |
Portage behaviour etc. |
1981 |
</abstract> |
1982 |
|
1983 |
<chapter> |
1984 |
<title>A Portage Introduction</title> |
1985 |
<abstract> |
1986 |
This chapter explains the "simple" steps a user definitely needs to know to |
1987 |
maintain the software on his system. |
1988 |
</abstract> |
1989 |
<include href="../hb-working-portage.xml"/> |
1990 |
</chapter> |
1991 |
|
1992 |
<chapter> |
1993 |
<title>USE flags</title> |
1994 |
<abstract> |
1995 |
USE flags are a very important aspect of Gentoo. In this chapter, you learn to |
1996 |
work with USE flags and understand how USE flags interact with your system. |
1997 |
</abstract> |
1998 |
<include href="../hb-working-use.xml"/> |
1999 |
</chapter> |
2000 |
|
2001 |
<chapter> |
2002 |
<title>Portage Features</title> |
2003 |
<abstract> |
2004 |
Discover the features Portage has, such as support for distributed compiling, |
2005 |
ccache and more. |
2006 |
</abstract> |
2007 |
<include href="../hb-working-features.xml"/> |
2008 |
</chapter> |
2009 |
|
2010 |
<chapter> |
2011 |
<title>Initscripts</title> |
2012 |
<abstract> |
2013 |
Gentoo uses a special initscript format which, amongst other features, allows |
2014 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
2015 |
these aspects and explains how to deal with these scripts. |
2016 |
</abstract> |
2017 |
<include href="../hb-working-rcscripts.xml"/> |
2018 |
</chapter> |
2019 |
|
2020 |
<chapter> |
2021 |
<title>Environment Variables</title> |
2022 |
<abstract> |
2023 |
With Gentoo you can easily manage the environment variables for your system. |
2024 |
This chapter explains how you do that, and also describes frequently used |
2025 |
variables. |
2026 |
</abstract> |
2027 |
<include href="../hb-working-variables.xml"/> |
2028 |
</chapter> |
2029 |
</part> |
2030 |
|
2031 |
<part> |
2032 |
<title>Working with Portage</title> |
2033 |
<abstract> |
2034 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
2035 |
Software Management Tool. |
2036 |
</abstract> |
2037 |
|
2038 |
<chapter> |
2039 |
<title>Files and Directories</title> |
2040 |
<abstract> |
2041 |
Once you want to know Portage in-depth you need to know where it stores its |
2042 |
files and data. |
2043 |
</abstract> |
2044 |
<include href="../hb-portage-files.xml"/> |
2045 |
</chapter> |
2046 |
|
2047 |
<chapter> |
2048 |
<title>Configuring through Variables</title> |
2049 |
<abstract> |
2050 |
Portage is completely configurable through various variables you can set in the |
2051 |
configuration file or as environment variable. |
2052 |
</abstract> |
2053 |
<include href="../hb-portage-configuration.xml"/> |
2054 |
</chapter> |
2055 |
|
2056 |
<chapter> |
2057 |
<title>Mixing Software Branches</title> |
2058 |
<abstract> |
2059 |
Gentoo provides software separated in several branches, depending on stability |
2060 |
and architectural support. "Mixing Software Branches" inform you how these |
2061 |
branches can be configured and how you can override this separation |
2062 |
individually. |
2063 |
</abstract> |
2064 |
<include href="../hb-portage-branches.xml"/> |
2065 |
</chapter> |
2066 |
|
2067 |
<chapter> |
2068 |
<title>Additional Portage Tools</title> |
2069 |
<abstract> |
2070 |
Portage comes with a few extra tools that might make your Gentoo experience even |
2071 |
better. Read on to discover how to use dispatch-conf and other tools. |
2072 |
</abstract> |
2073 |
<include href="../hb-portage-tools.xml"/> |
2074 |
</chapter> |
2075 |
|
2076 |
<chapter> |
2077 |
<title>Diverting from the Official Tree</title> |
2078 |
<abstract> |
2079 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
2080 |
your own Portage tree, how to synchronise only the categories you want, inject |
2081 |
packages and more. |
2082 |
</abstract> |
2083 |
<include href="../hb-portage-diverttree.xml"/> |
2084 |
</chapter> |
2085 |
</part> |
2086 |
|
2087 |
<part> |
2088 |
<title>Gentoo Network Configuration</title> |
2089 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
2090 |
|
2091 |
<chapter> |
2092 |
<title>Getting Started</title> |
2093 |
<abstract> |
2094 |
A guide to quickly get your network interface up and running in most common |
2095 |
environments. |
2096 |
</abstract> |
2097 |
<include href="../hb-net-start.xml"/> |
2098 |
</chapter> |
2099 |
|
2100 |
<chapter> |
2101 |
<title>Advanced Configuration</title> |
2102 |
<abstract> |
2103 |
Here we learn about how the configuration works - you need to know this |
2104 |
before we learn about modular networking. |
2105 |
</abstract> |
2106 |
<include href="../hb-net-advanced.xml"/> |
2107 |
</chapter> |
2108 |
|
2109 |
<chapter> |
2110 |
<title>Modular Networking</title> |
2111 |
<abstract> |
2112 |
Gentoo provides you flexible networking - here you are told about choosing |
2113 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
2114 |
</abstract> |
2115 |
<include href="../hb-net-modules.xml"/> |
2116 |
</chapter> |
2117 |
|
2118 |
<chapter> |
2119 |
<title>Wireless Networking</title> |
2120 |
<abstract> |
2121 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
2122 |
</abstract> |
2123 |
<include href="../hb-net-wireless.xml"/> |
2124 |
</chapter> |
2125 |
|
2126 |
<chapter> |
2127 |
<title>Adding Functionality</title> |
2128 |
<abstract> |
2129 |
If you're feeling adventurous, you can add your own functions to networking. |
2130 |
</abstract> |
2131 |
<include href="../hb-net-functions.xml"/> |
2132 |
</chapter> |
2133 |
|
2134 |
<chapter> |
2135 |
<title>Network Management</title> |
2136 |
<abstract> |
2137 |
For laptop users or people who move their computer around different networks. |
2138 |
</abstract> |
2139 |
<include href="../hb-net-management.xml"/> |
2140 |
</chapter> |
2141 |
</part> |
2142 |
|
2143 |
</book> |
2144 |
|
2145 |
|
2146 |
|
2147 |
1.1 xml/htdocs/doc/en/handbook/2007.1/handbook-x86.xml |
2148 |
|
2149 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-x86.xml?rev=1.1&view=markup |
2150 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-x86.xml?rev=1.1&content-type=text/plain |
2151 |
|
2152 |
Index: handbook-x86.xml |
2153 |
=================================================================== |
2154 |
<?xml version='1.0' encoding='UTF-8'?> |
2155 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
2156 |
|
2157 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/handbook-x86.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
2158 |
|
2159 |
<book link="/doc/en/handbook/2007.0/handbook-x86.xml"> |
2160 |
<title>Gentoo Linux 2007.0 x86 Networkless Handbook</title> |
2161 |
|
2162 |
<values> |
2163 |
<key id="arch">x86</key> |
2164 |
<key id="release-dir">releases/x86/2007.0/</key> |
2165 |
<key id="online-book">2007.0/handbook-x86.xml</key> |
2166 |
</values> |
2167 |
|
2168 |
<author title="Author"> |
2169 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
2170 |
</author> |
2171 |
<author title="Author"> |
2172 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
2173 |
</author> |
2174 |
<author title="Author"> |
2175 |
<mail link="uberlord@g.o">Roy Marples</mail> |
2176 |
</author> |
2177 |
<author title="Author"> |
2178 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
2179 |
</author> |
2180 |
<author title="Author"> |
2181 |
<mail link="chouser@g.o">Chris Houser</mail> |
2182 |
</author> |
2183 |
<author title="Author"> |
2184 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
2185 |
</author> |
2186 |
<author title="Author"> |
2187 |
<mail link="nightmorph@g.o">Joshua Saddler</mail> |
2188 |
</author> |
2189 |
<author title="Gentoo x86 Developer"> |
2190 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
2191 |
</author> |
2192 |
<author title="Gentoo Alpha Developer"> |
2193 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
2194 |
</author><!-- Does not want to be listed on the rendered page |
2195 |
<author title="Gentoo Developer"> |
2196 |
Aron Griffis |
2197 |
</author> |
2198 |
--> |
2199 |
<author title="Gentoo AMD64 Developer"> |
2200 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
2201 |
</author> |
2202 |
<author title="Gentoo HPPA developer"> |
2203 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
2204 |
</author> |
2205 |
<author title="Gentoo PPC developer"> |
2206 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
2207 |
</author> |
2208 |
<author title="Gentoo SPARC developer"> |
2209 |
<mail link="blademan@g.o">Joe Kallar</mail> |
2210 |
</author> |
2211 |
<author title="Editor"> |
2212 |
<mail link="zhen@g.o">John P. Davis</mail> |
2213 |
</author> |
2214 |
<author title="Editor">Pierre-Henri Jondot</author> |
2215 |
<author title="Editor"> |
2216 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
2217 |
</author> |
2218 |
<author title="Editor"> |
2219 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
2220 |
</author> |
2221 |
<author title="Editor"> |
2222 |
<mail link="seo@g.o">Jungmin Seo</mail> |
2223 |
</author> |
2224 |
<author title="Editor"> |
2225 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
2226 |
</author> |
2227 |
<author title="Editor"> |
2228 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
2229 |
</author> |
2230 |
<author title="Editor"> |
2231 |
<mail link="peitolm@g.o">Colin Morey</mail> |
2232 |
</author> |
2233 |
<author title="Editor"> |
2234 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
2235 |
</author> |
2236 |
<author title="Editor"> |
2237 |
<mail link="carl@g.o">Carl Anderson</mail> |
2238 |
</author> |
2239 |
<author title="Editor"> |
2240 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
2241 |
</author> |
2242 |
<author title="Editor"> |
2243 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
2244 |
</author> |
2245 |
<author title="Editor"> |
2246 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
2247 |
</author> |
2248 |
<author title="Editor"> |
2249 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
2250 |
</author> |
2251 |
<author title="Editor"> |
2252 |
<mail link="erwin@g.o">Erwin</mail> |
2253 |
</author> |
2254 |
<author title="Editor"> |
2255 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
2256 |
</author> |
2257 |
<author title="Editor"> |
2258 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
2259 |
</author> |
2260 |
<author title="Editor"> |
2261 |
<mail link="neysx@g.o">Xavier Neys</mail> |
2262 |
</author> |
2263 |
<author title="Editor"> |
2264 |
<mail link="fox2mike@g.o">Shyam Mani</mail> |
2265 |
</author> |
2266 |
<author title="Reviewer"> |
2267 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
2268 |
</author> |
2269 |
<author title="Reviewer"> |
2270 |
<mail link="dberkholz@g.o">Donnie Berkholz</mail> |
2271 |
</author> |
2272 |
<author title="Reviewer"> |
2273 |
<mail link="antifa@g.o">Ken Nowack</mail> |
2274 |
</author> |
2275 |
<author title="Contributor"> |
2276 |
<mail link="pylon@g.o">Lars Weiler</mail> |
2277 |
</author> |
2278 |
|
2279 |
<abstract> |
2280 |
This is the Gentoo Networkless Handbook, an effort to centralise Gentoo/Linux |
2281 |
information. This handbook contains the installation instructions for a |
2282 |
networkless installation on x86 systems and parts about working with Gentoo and |
2283 |
Portage. |
2284 |
</abstract> |
2285 |
|
2286 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
2287 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
2288 |
<license/> |
2289 |
|
2290 |
<version>8.1</version> |
2291 |
<date>2007-06-06</date> |
2292 |
|
2293 |
<part> |
2294 |
<title>Installing Gentoo</title> |
2295 |
<abstract> |
2296 |
In this part you learn how to install Gentoo on your system. |
2297 |
</abstract> |
2298 |
|
2299 |
<chapter> |
2300 |
<title>About the Gentoo Linux Installation</title> |
2301 |
<abstract> |
2302 |
Users not familiar with Gentoo do not always know that choice is what |
2303 |
Gentoo is all about. |
2304 |
</abstract> |
2305 |
<include href="hb-install-about.xml"/> |
2306 |
</chapter> |
2307 |
|
2308 |
<chapter> |
2309 |
<title>Booting the Installer LiveCD</title> |
2310 |
<abstract> |
2311 |
Using our Installer LiveCD you can boot up your system into a running |
2312 |
environment that allows you to install Gentoo. |
2313 |
</abstract> |
2314 |
<include href="hb-install-gli-medium.xml"/> |
2315 |
</chapter> |
2316 |
|
2317 |
<chapter> |
2318 |
<title>Using the GTK+ based Gentoo Linux Installer</title> |
2319 |
<abstract> |
2320 |
You now have an option of using our graphical installer to install Gentoo. |
2321 |
Configure the options you need through an easy to use GUI and you're ready to |
2322 |
go. |
2323 |
</abstract> |
2324 |
<include href="hb-install-gtkfe.xml" /> |
2325 |
</chapter> |
2326 |
|
2327 |
<chapter> |
2328 |
<title>Using the Dialog based Gentoo Linux Installer</title> |
2329 |
<abstract> |
2330 |
You also have an option of using our text based installer to install Gentoo. |
2331 |
Configure the options you need through an easy to use set of menus and you're |
2332 |
ready to go. |
2333 |
</abstract> |
2334 |
<include href="hb-install-gli-dialog.xml" /> |
2335 |
</chapter> |
2336 |
|
2337 |
<chapter> |
2338 |
<title>Where to go from here?</title> |
2339 |
<abstract> |
2340 |
Now you have your Gentoo system, but what's next? |
2341 |
</abstract> |
2342 |
<include href="hb-install-next.xml"/> |
2343 |
</chapter> |
2344 |
</part> |
2345 |
|
2346 |
<part> |
2347 |
<title>Working with Gentoo</title> |
2348 |
<abstract> |
2349 |
Learn how to work with Gentoo: installing software, altering variables, |
2350 |
changing Portage behaviour etc. |
2351 |
</abstract> |
2352 |
|
2353 |
<chapter> |
2354 |
<title>A Portage Introduction</title> |
2355 |
<abstract> |
2356 |
This chapter explains the "simple" steps a user definitely needs to know to |
2357 |
maintain the software on his system. |
2358 |
</abstract> |
2359 |
<include href="../hb-working-portage.xml"/> |
2360 |
</chapter> |
2361 |
|
2362 |
<chapter> |
2363 |
<title>USE flags</title> |
2364 |
<abstract> |
2365 |
USE flags are a very important aspect of Gentoo. In this chapter, you learn to |
2366 |
work with USE flags and understand how USE flags interact with your system. |
2367 |
</abstract> |
2368 |
<include href="../hb-working-use.xml"/> |
2369 |
</chapter> |
2370 |
|
2371 |
<chapter> |
2372 |
<title>Portage Features</title> |
2373 |
<abstract> |
2374 |
Discover the features Portage has, such as support for distributed compiling, |
2375 |
ccache and more. |
2376 |
</abstract> |
2377 |
<include href="../hb-working-features.xml"/> |
2378 |
</chapter> |
2379 |
|
2380 |
<chapter> |
2381 |
<title>Initscripts</title> |
2382 |
<abstract> |
2383 |
Gentoo uses a special initscript format which, amongst other features, allows |
2384 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
2385 |
these aspects and explains how to deal with these scripts. |
2386 |
</abstract> |
2387 |
<include href="../hb-working-rcscripts.xml"/> |
2388 |
</chapter> |
2389 |
|
2390 |
<chapter> |
2391 |
<title>Environment Variables</title> |
2392 |
<abstract> |
2393 |
With Gentoo you can easily manage the environment variables for your system. |
2394 |
This chapter explains how you do that, and also describes frequently used |
2395 |
variables. |
2396 |
</abstract> |
2397 |
<include href="../hb-working-variables.xml"/> |
2398 |
</chapter> |
2399 |
</part> |
2400 |
|
2401 |
<part> |
2402 |
<title>Working with Portage</title> |
2403 |
<abstract> |
2404 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
2405 |
Software Management Tool. |
2406 |
</abstract> |
2407 |
|
2408 |
<chapter> |
2409 |
<title>Files and Directories</title> |
2410 |
<abstract> |
2411 |
Once you want to know Portage in-depth you need to know where it stores its |
2412 |
files and data. |
2413 |
</abstract> |
2414 |
<include href="../hb-portage-files.xml"/> |
2415 |
</chapter> |
2416 |
|
2417 |
<chapter> |
2418 |
<title>Configuring through Variables</title> |
2419 |
<abstract> |
2420 |
Portage is completely configurable through various variables you can set in the |
2421 |
configuration file or as environment variable. |
2422 |
</abstract> |
2423 |
<include href="../hb-portage-configuration.xml"/> |
2424 |
</chapter> |
2425 |
|
2426 |
<chapter> |
2427 |
<title>Mixing Software Branches</title> |
2428 |
<abstract> |
2429 |
Gentoo provides software separated in several branches, depending on stability |
2430 |
and architectural support. "Mixing Software Branches" inform you how these |
2431 |
branches can be configured and how you can override this separation |
2432 |
individually. |
2433 |
</abstract> |
2434 |
<include href="../hb-portage-branches.xml"/> |
2435 |
</chapter> |
2436 |
|
2437 |
<chapter> |
2438 |
<title>Additional Portage Tools</title> |
2439 |
<abstract> |
2440 |
Portage comes with a few extra tools that might make your Gentoo experience even |
2441 |
better. Read on to discover how to use dispatch-conf and other tools. |
2442 |
</abstract> |
2443 |
<include href="../hb-portage-tools.xml"/> |
2444 |
</chapter> |
2445 |
|
2446 |
<chapter> |
2447 |
<title>Diverting from the Official Tree</title> |
2448 |
<abstract> |
2449 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
2450 |
your own Portage tree, how to synchronise only the categories you want, inject |
2451 |
packages and more. |
2452 |
</abstract> |
2453 |
<include href="../hb-portage-diverttree.xml"/> |
2454 |
</chapter> |
2455 |
</part> |
2456 |
|
2457 |
<part> |
2458 |
<title>Gentoo Network Configuration</title> |
2459 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
2460 |
|
2461 |
<chapter> |
2462 |
<title>Getting Started</title> |
2463 |
<abstract> |
2464 |
A guide to quickly get your network interface up and running in most common |
2465 |
environments. |
2466 |
</abstract> |
2467 |
<include href="../hb-net-start.xml"/> |
2468 |
</chapter> |
2469 |
|
2470 |
<chapter> |
2471 |
<title>Advanced Configuration</title> |
2472 |
<abstract> |
2473 |
Here we learn about how the configuration works - you need to know this |
2474 |
before we learn about modular networking. |
2475 |
</abstract> |
2476 |
<include href="../hb-net-advanced.xml"/> |
2477 |
</chapter> |
2478 |
|
2479 |
<chapter> |
2480 |
<title>Modular Networking</title> |
2481 |
<abstract> |
2482 |
Gentoo provides you flexible networking - here you are told about choosing |
2483 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
2484 |
</abstract> |
2485 |
<include href="../hb-net-modules.xml"/> |
2486 |
</chapter> |
2487 |
|
2488 |
<chapter> |
2489 |
<title>Wireless Networking</title> |
2490 |
<abstract> |
2491 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
2492 |
</abstract> |
2493 |
<include href="../hb-net-wireless.xml"/> |
2494 |
</chapter> |
2495 |
|
2496 |
<chapter> |
2497 |
<title>Adding Functionality</title> |
2498 |
<abstract> |
2499 |
If you're feeling adventurous, you can add your own functions to networking. |
2500 |
</abstract> |
2501 |
<include href="../hb-net-functions.xml"/> |
2502 |
</chapter> |
2503 |
|
2504 |
<chapter> |
2505 |
<title>Network Management</title> |
2506 |
<abstract> |
2507 |
For laptop users or people who move their computer around different networks. |
2508 |
</abstract> |
2509 |
<include href="../hb-net-management.xml"/> |
2510 |
</chapter> |
2511 |
</part> |
2512 |
|
2513 |
</book> |
2514 |
|
2515 |
|
2516 |
|
2517 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-about.xml |
2518 |
|
2519 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-about.xml?rev=1.1&view=markup |
2520 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-about.xml?rev=1.1&content-type=text/plain |
2521 |
|
2522 |
Index: hb-install-about.xml |
2523 |
=================================================================== |
2524 |
<?xml version='1.0' encoding='UTF-8'?> |
2525 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
2526 |
|
2527 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
2528 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
2529 |
|
2530 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-about.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
2531 |
|
2532 |
<sections> |
2533 |
|
2534 |
<version>8.2</version> |
2535 |
<date>2007-06-02</date> |
2536 |
|
2537 |
<section> |
2538 |
<title>Introduction</title> |
2539 |
<subsection> |
2540 |
<title>Welcome!</title> |
2541 |
<body> |
2542 |
|
2543 |
<p> |
2544 |
First of all, <e>welcome</e> to Gentoo. You are about to enter the world |
2545 |
of customization and performance. When installing Gentoo, this is made clear to |
2546 |
you several times -- you can choose how much you want to compile yourself, how |
2547 |
to install Gentoo, what system logger you want, etc. |
2548 |
</p> |
2549 |
|
2550 |
<p> |
2551 |
Gentoo is a fast, modern meta-distribution with a clean and flexible |
2552 |
design. Gentoo is built around free software and doesn't hide from its |
2553 |
users what is beneath the hood. Portage, the package maintenance system |
2554 |
which Gentoo uses, is written in Python, meaning you can easily view and |
2555 |
modify the source code. Gentoo's packaging system uses source code |
2556 |
(although support for precompiled packages is included too) and |
2557 |
configuring Gentoo happens through regular text files. In other words, |
2558 |
openness everywhere. |
2559 |
</p> |
2560 |
|
2561 |
<p> |
2562 |
It is very important that you understand that <e>empowerment</e> is what makes |
2563 |
Gentoo run. We try not to force anything on our users and try our best to |
2564 |
empower you to make the choices you wish. If you feel a change should be made, |
2565 |
please file a <uri link="http://bugs.gentoo.org">bug report</uri> about it. |
2566 |
</p> |
2567 |
|
2568 |
</body> |
2569 |
</subsection> |
2570 |
<!-- for all arches that DO have an installer liveCD --> |
2571 |
<subsection test="contains('AMD64 x86', func:keyval('arch'))"> |
2572 |
<title>How do I go about Installing Gentoo?</title> |
2573 |
<body> |
2574 |
|
2575 |
<p> |
2576 |
Gentoo Linux comes with two versions of an easy to use Installer. A GTK+ based |
2577 |
installer (for use with an X based environment) and a Dialog based installer for |
2578 |
use on the console. Chapter 3 of the handbook deals with the GTK+ based |
2579 |
installer while Chapter 4 is for the Dialog based one. |
2580 |
</p> |
2581 |
|
2582 |
</body> |
2583 |
</subsection> |
2584 |
<!-- for all arches that do NOT have an installer liveCD --> |
2585 |
<subsection test="not(contains('AMD64 x86', func:keyval('arch')))"> |
2586 |
<title>How is the Installation Structured?</title> |
2587 |
<body> |
2588 |
|
2589 |
<p> |
2590 |
The Gentoo Installation can be seen as a 10-step procedure, |
2591 |
corresponding to chapters 2 - 11. Every step results in |
2592 |
a certain state: |
2593 |
</p> |
2594 |
|
2595 |
<ul> |
2596 |
<li> |
2597 |
After step 1, you are in a working environment ready to install Gentoo |
2598 |
</li> |
2599 |
<li> |
2600 |
After step 2, your internet connection is prepared in case you need it (this |
2601 |
is however optional) |
2602 |
</li> |
2603 |
<li> |
2604 |
After step 3, your hard disks are initialized to house your Gentoo |
2605 |
installation |
2606 |
</li> |
2607 |
<li> |
2608 |
After step 4, your installation environment is prepared and you are |
2609 |
ready to chroot into the new environment |
2610 |
</li> |
2611 |
<li> |
2612 |
After step 5, core packages, which are the same on all Gentoo |
2613 |
installations, are installed |
2614 |
</li> |
2615 |
<li> |
2616 |
After step 6, you have compiled your Linux kernel |
2617 |
</li> |
2618 |
<li> |
2619 |
After step 7, you have written most of your Gentoo system |
2620 |
configuration files |
2621 |
</li> |
2622 |
<li> |
2623 |
After step 8, necessary system tools (which you can choose from a nice |
2624 |
list) are installed |
2625 |
</li> |
2626 |
<li> |
2627 |
After step 9, your choice of bootloader has been installed and |
2628 |
configured and you are logged in into your new Gentoo installation |
2629 |
</li> |
2630 |
<li> |
2631 |
After step 10, your Gentoo Linux environment is ready to be explored |
2632 |
</li> |
2633 |
</ul> |
2634 |
|
2635 |
<p> |
2636 |
When you are given a certain choice, we try our best to explain what the pros |
2637 |
and cons are. We will continue then with a default |
2638 |
choice, identified by "Default: " in the title. The other |
2639 |
possibilities are marked by "Alternative: ". Do <e>not</e> |
2640 |
think that the default is what we recommend. It is however what we |
2641 |
believe most users will use. |
2642 |
</p> |
2643 |
|
2644 |
<p> |
2645 |
Sometimes you can pursue an optional step. Such steps are marked as |
2646 |
"Optional: " and are therefore not needed to install Gentoo. |
2647 |
However, some optional steps are dependant on a previous decision you |
2648 |
made. We will inform you when this happens, both when you make the |
2649 |
decision, and right before the optional step is described. |
2650 |
</p> |
2651 |
|
2652 |
</body> |
2653 |
</subsection> |
2654 |
<subsection> |
2655 |
<title>What are my Options?</title> |
2656 |
<body> |
2657 |
|
2658 |
<p> |
2659 |
You can install Gentoo in many different ways. You can download and install from |
2660 |
one of our Installation CDs, from an existing distribution, |
2661 |
from a bootable CD (such as Knoppix), from a netbooted environment, from a |
2662 |
rescue floppy, etc. |
2663 |
</p> |
2664 |
|
2665 |
<p> |
2666 |
This document covers the installation using a Gentoo Linux Installation CD, a |
2667 |
bootable CD that contains everything you need to get Gentoo Linux up and |
2668 |
running. There are two types of Installation CDs, the InstallCD and the |
2669 |
Installer LiveCD. The InstallCD is a minimal environment which contains only |
2670 |
those packages necessary for installing Gentoo Linux. The LiveCD is a complete |
2671 |
Gentoo Linux environment and can be used for multiple tasks, one of which is |
2672 |
installing Gentoo Linux. The LiveCD is not available on all architectures at |
2673 |
this time. If your architecture does not have a LiveCD, then this document will |
2674 |
refer to the Universal InstallCD for you. |
2675 |
</p> |
2676 |
|
2677 |
<p> |
2678 |
This installation approach however does not immediately use the latest version |
2679 |
of the available packages; if you want this you should check out the |
2680 |
Installation Instructions inside our <uri |
2681 |
link="/doc/en/handbook/index.xml">Gentoo Linux Handbooks</uri>. |
2682 |
</p> |
2683 |
|
2684 |
<p> |
2685 |
For help on the other installation approaches, |
2686 |
please read our <uri link="/doc/en/altinstall.xml">Alternative Installation |
2687 |
Guide</uri>. We also provide a <uri |
2688 |
link="/doc/en/gentoo-x86-tipsntricks.xml">Gentoo Installation Tips & |
2689 |
Tricks</uri> document that might be useful to read as well. If you feel that |
2690 |
the current installation instructions are too elaborate, feel free to use our |
2691 |
Quick Installation Guide available from our <uri |
2692 |
link="/doc/en/index.xml">Documentation Resources</uri> if your architecture |
2693 |
has such a document available. |
2694 |
</p> |
2695 |
|
2696 |
</body> |
2697 |
</subsection> |
2698 |
<subsection> |
2699 |
<title>Troubles?</title> |
2700 |
<body> |
2701 |
|
2702 |
<p> |
2703 |
If you find a problem in the installation (or in the installation |
2704 |
documentation), please check the errata from our <uri |
2705 |
link="/proj/en/releng/">Gentoo Release Engineering Project</uri>, |
2706 |
visit our <uri link="http://bugs.gentoo.org">bug tracking |
2707 |
system</uri> and check if the bug is known. If not, please create a bug report |
2708 |
for it so we can take care of it. Do not be afraid of the developers who are |
2709 |
assigned to (your) bugs -- they generally don't eat people. |
2710 |
</p> |
2711 |
|
2712 |
<p> |
2713 |
Note though that, although the document you are now reading is |
2714 |
architecture-specific, it will contain references to other architectures as |
2715 |
well. This is due to the fact that large parts of the Gentoo Handbook use source |
2716 |
code that is common for all architectures (to avoid duplication of efforts and |
2717 |
starvation of development resources). We will try to keep this to a minimum |
2718 |
to avoid confusion. |
2719 |
</p> |
2720 |
|
2721 |
<p> |
2722 |
If you are uncertain if the problem is a user-problem (some error you |
2723 |
made despite having read the documentation carefully) or a |
2724 |
software-problem (some error we made despite having tested the |
2725 |
installation/documentation carefully) you are free to join #gentoo on |
2726 |
irc.freenode.net. Of course, you are welcome otherwise too :) |
2727 |
</p> |
2728 |
|
2729 |
<p> |
2730 |
If you have a question regarding Gentoo, check out our <uri |
2731 |
link="/doc/en/faq.xml">Frequently Asked |
2732 |
Questions</uri>, available from the <uri |
2733 |
link="/doc/en/">Gentoo Documentation</uri>. You can |
2734 |
also view the <uri |
2735 |
link="http://forums.gentoo.org/viewforum.php?f=40">FAQs</uri> on our |
2736 |
<uri link="http://forums.gentoo.org">forums</uri>. If you can't find the answer |
2737 |
there ask on #gentoo, our IRC-channel on irc.freenode.net. Yes, several of |
2738 |
us are freaks who sit on IRC :-) |
2739 |
</p> |
2740 |
|
2741 |
</body> |
2742 |
</subsection> |
2743 |
</section> |
2744 |
<section> |
2745 |
<title>Fast Installation using the Gentoo Reference Platform</title> |
2746 |
<subsection> |
2747 |
<title>What is the Gentoo Reference Platform?</title> |
2748 |
<body> |
2749 |
|
2750 |
<p> |
2751 |
The Gentoo Reference Platform, from now on abbreviated to GRP, is a snapshot of |
2752 |
prebuilt packages users (that means you!) can install during the installation |
2753 |
of Gentoo to speed up the installation process. The GRP consists of all |
2754 |
packages required to have a fully functional Gentoo installation. They are not |
2755 |
just the ones you need to have a base installation up to speed in no time, but |
2756 |
all lengthier builds (such as xorg-x11, GNOME, OpenOffice, Mozilla, ...) |
2757 |
are available as GRP packages too. |
2758 |
</p> |
2759 |
|
2760 |
<p> |
2761 |
However, these prebuilt packages aren't maintained during the lifetime of the |
2762 |
Gentoo distribution. They are snapshots released at every Gentoo release and |
2763 |
make it possible to have a functional environment in a short amount of time. You |
2764 |
can then upgrade your system in the background while working in your Gentoo |
2765 |
environment. |
2766 |
</p> |
2767 |
|
2768 |
</body> |
2769 |
</subsection> |
2770 |
<subsection> |
2771 |
<title>How Portage Handles GRP Packages</title> |
2772 |
<body> |
2773 |
|
2774 |
<p> |
2775 |
Your Portage tree - the collection of <e>ebuilds</e> (files that contain all |
2776 |
information about a package, such as its description, homepage, sourcecode URLs, |
2777 |
compilation instructions, dependencies, etc.) - must be synchronised with the |
2778 |
GRP set: the versions of the available ebuilds and their accompanying GRP |
2779 |
packages must match. |
2780 |
</p> |
2781 |
|
2782 |
<p> |
2783 |
For this reason you can only benefit from the GRP packages Gentoo provides while |
2784 |
performing the current installation approach. GRP is not available for those |
2785 |
interested in performing an installation using the latest versions of all |
2786 |
available packages. |
2787 |
</p> |
2788 |
|
2789 |
</body> |
2790 |
</subsection> |
2791 |
<subsection> |
2792 |
<title>Is GRP Available?</title> |
2793 |
<body> |
2794 |
|
2795 |
<p> |
2796 |
Not all architectures provide GRP packages. That doesn't mean GRP isn't |
2797 |
supported on the other architectures, but it means that we don't have the |
2798 |
resources to build and test the GRP packages. |
2799 |
</p> |
2800 |
|
2801 |
<p> |
2802 |
At present we provide GRP packages for the following architectures: |
2803 |
</p> |
2804 |
|
2805 |
<ul> |
2806 |
<li> |
2807 |
The <b>amd64</b> architecture (amd64). Note: The packages are available on |
2808 |
the Installer LiveCD. |
2809 |
</li> |
2810 |
<li> |
2811 |
The <b>ppc</b> architecture (ppc32) |
2812 |
</li> |
2813 |
<li> |
2814 |
The <b>sparc</b> architecture (sparc64) |
2815 |
</li> |
2816 |
<li> |
2817 |
The <b>x86</b> architecture (athlon, athlon-xp, athlon-mp, pentium-pro, |
2818 |
pentium2, pentium3, pentium4 and pentium-m) Note: The packages are for i686 |
2819 |
and are available on the Installer LiveCD. |
2820 |
</li> |
2821 |
</ul> |
2822 |
|
2823 |
<p> |
2824 |
If your architecture (or subarchitecture) isn't on this list, you are not |
2825 |
able to opt for a GRP installation. |
2826 |
</p> |
2827 |
|
2828 |
<p> |
2829 |
Now that this introduction is over, let's continue with <uri |
2830 |
link="?part=1&chap=2">Booting the Universal InstallCD/Installer |
2831 |
LiveCD</uri>. |
2832 |
</p> |
2833 |
|
2834 |
</body> |
2835 |
</subsection> |
2836 |
</section> |
2837 |
</sections> |
2838 |
|
2839 |
|
2840 |
|
2841 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-config.xml |
2842 |
|
2843 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-config.xml?rev=1.1&view=markup |
2844 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-config.xml?rev=1.1&content-type=text/plain |
2845 |
|
2846 |
Index: hb-install-config.xml |
2847 |
=================================================================== |
2848 |
<?xml version='1.0' encoding='UTF-8'?> |
2849 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
2850 |
|
2851 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
2852 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
2853 |
|
2854 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-config.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
2855 |
|
2856 |
<sections> |
2857 |
|
2858 |
<version>8.2</version> |
2859 |
<date>2007-05-15</date> |
2860 |
|
2861 |
<section> |
2862 |
<title>Filesystem Information</title> |
2863 |
<subsection> |
2864 |
<title>What is fstab?</title> |
2865 |
<body> |
2866 |
|
2867 |
<p> |
2868 |
Under Linux, all partitions used by the system must be listed in |
2869 |
<path>/etc/fstab</path>. This file contains the mountpoints of those partitions |
2870 |
(where they are seen in the file system structure), how they should be mounted |
2871 |
and with what special options (automatically or not, whether users can mount |
2872 |
them or not, etc.) |
2873 |
</p> |
2874 |
|
2875 |
</body> |
2876 |
</subsection> |
2877 |
<subsection> |
2878 |
<title>Creating /etc/fstab</title> |
2879 |
<body> |
2880 |
|
2881 |
<p> |
2882 |
<path>/etc/fstab</path> uses a special syntax. Every line consists of six |
2883 |
fields, separated by whitespace (space(s), tabs or a mixture). Each field has |
2884 |
its own meaning: |
2885 |
</p> |
2886 |
|
2887 |
<ul> |
2888 |
<li> |
2889 |
The first field shows the <b>partition</b> described (the path to the device |
2890 |
file) |
2891 |
</li> |
2892 |
<li> |
2893 |
The second field shows the <b>mountpoint</b> at which the partition should be |
2894 |
mounted |
2895 |
</li> |
2896 |
<li> |
2897 |
The third field shows the <b>filesystem</b> used by the partition |
2898 |
</li> |
2899 |
<li> |
2900 |
The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it |
2901 |
wants to mount the partition. As every filesystem has its own mountoptions, |
2902 |
you are encouraged to read the mount man page (<c>man mount</c>) for a full |
2903 |
listing. Multiple mountoptions are comma-separated. |
2904 |
</li> |
2905 |
<li> |
2906 |
The fifth field is used by <c>dump</c> to determine if the partition needs to |
2907 |
be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero). |
2908 |
</li> |
2909 |
<li> |
2910 |
The sixth field is used by <c>fsck</c> to determine the order in which |
2911 |
filesystems should be <b>check</b>ed if the system wasn't shut down properly. |
2912 |
The root filesystem should have <c>1</c> while the rest should have <c>2</c> |
2913 |
(or <c>0</c> if a filesystem check isn't necessary). |
2914 |
</li> |
2915 |
</ul> |
2916 |
|
2917 |
<impo> |
2918 |
The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid |
2919 |
fstab file</e>. You <b>have to create</b> your own <path>/etc/fstab</path>. |
2920 |
</impo> |
2921 |
|
2922 |
<pre caption="Opening /etc/fstab"> |
2923 |
# <i>nano -w /etc/fstab</i> |
2924 |
</pre> |
2925 |
|
2926 |
</body> |
2927 |
<body test="func:keyval('/boot')"> |
2928 |
|
2929 |
<p> |
2930 |
Let us take a look at how we write down the options for the <path>/boot</path> |
2931 |
partition. This is just an example, if you didn't or couldn't create a |
2932 |
<path>/boot</path>, don't copy it. |
2933 |
</p> |
2934 |
|
2935 |
<p test="contains(func:keyval('/boot'), '/dev/hd')"> |
2936 |
In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is |
2937 |
usually the <path><keyval id="/boot"/></path> partition (or |
2938 |
<path>/dev/sda*</path> if you use SCSI or SATA drives), with <c>ext2</c> as |
2939 |
filesystem. It needs to be checked during boot, so we would write down: |
2940 |
</p> |
2941 |
|
2942 |
<p test="contains(func:keyval('/boot'), '/dev/sd')"> |
2943 |
In our default <keyval id="arch"/> partitioning example, <path>/boot</path> is |
2944 |
usually the <path><keyval id="/boot"/></path> partition, with <c>ext2</c> as |
2945 |
filesystem. It needs to be checked during boot, so we would write down: |
2946 |
</p> |
2947 |
|
2948 |
<pre caption="An example /boot line for /etc/fstab"> |
2949 |
<keyval id="/boot"/> /boot ext2 defaults 1 2 |
2950 |
</pre> |
2951 |
|
2952 |
<p> |
2953 |
Some users don't want their <path>/boot</path> partition to be mounted |
2954 |
automatically to improve their system's security. Those people should |
2955 |
substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to |
2956 |
manually mount this partition every time you want to use it. |
2957 |
</p> |
2958 |
|
2959 |
</body> |
2960 |
<body> |
2961 |
|
2962 |
<p test="not(func:keyval('arch')='SPARC')"> |
2963 |
Add the rules that match your partitioning scheme and append rules for |
2964 |
<path>/proc</path>, <c>tmpfs</c>, for your CD-ROM drive(s), and of course, if |
2965 |
you have other partitions or drives, for those too. |
2966 |
</p> |
2967 |
|
2968 |
<p test="func:keyval('arch')='SPARC'"> |
2969 |
Add the rules that match your partitioning schema and append rules for |
2970 |
<path>/proc/openprom</path>, <path>/proc</path>, <c>tmpfs</c> , for your CD-ROM |
2971 |
drive(s), and of course, if you have other partitions or drives, for those too. |
2972 |
</p> |
2973 |
|
2974 |
<p> |
2975 |
Now use the <e>example</e> below to create your <path>/etc/fstab</path>: |
2976 |
</p> |
2977 |
|
2978 |
<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'"> |
2979 |
<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2 |
2980 |
/dev/sda3 none swap sw 0 0 |
2981 |
/dev/sda4 / ext3 noatime 0 1 |
2982 |
|
2983 |
proc /proc proc nodev,nosuid,noexec 0 0 |
2984 |
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
2985 |
|
2986 |
/dev/cdrom /mnt/cdrom auto noauto,user 0 0 |
2987 |
</pre> |
2988 |
|
2989 |
<pre caption="A full /etc/fstab example" test="func:keyval('arch')='Alpha' or func:keyval('arch')='MIPS'"> |
2990 |
<keyval id="/boot"/> /boot ext2 defaults,noatime 1 2 |
2991 |
/dev/sda2 none swap sw 0 0 |
2992 |
/dev/sda3 / ext3 noatime 0 1 |
2993 |
|
2994 |
proc /proc proc nodev,nosuid,noexec 0 0 |
2995 |
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
2996 |
|
2997 |
/dev/cdrom /mnt/cdrom auto noauto,user 0 0 |
2998 |
</pre> |
2999 |
|
3000 |
<pre caption="A full /etc/fstab example" test="func:keyval('arch')='SPARC'"> |
3001 |
/dev/sda1 / ext3 noatime 0 1 |
3002 |
/dev/sda2 none swap sw 0 0 |
3003 |
/dev/sda4 /usr ext3 noatime 0 2 |
3004 |
/dev/sda5 /var ext3 noatime 0 2 |
3005 |
/dev/sda6 /home ext3 noatime 0 2 |
3006 |
|
3007 |
openprom /proc/openprom openpromfs defaults 0 0 |
3008 |
proc /proc proc nodev,nosuid,noexec 0 0 |
3009 |
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
3010 |
|
3011 |
/dev/cdrom /mnt/cdrom auto noauto,user 0 0 |
3012 |
</pre> |
3013 |
|
3014 |
<note test="func:keyval('arch')='PPC'"> |
3015 |
There are important variations between PPC machine types. Please make sure you |
3016 |
adapt the following example to your system. |
3017 |
</note> |
3018 |
|
3019 |
<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC'"> |
3020 |
/dev/hda4 / ext3 noatime 0 1 |
3021 |
/dev/hda3 none swap sw 0 0 |
3022 |
|
3023 |
proc /proc proc nodev,nosuid,noexec 0 0 |
3024 |
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
3025 |
|
3026 |
/dev/cdrom /mnt/cdrom auto noauto,user 0 0 |
3027 |
</pre> |
3028 |
|
3029 |
<pre caption="A full /etc/fstab example" test="func:keyval('arch')='PPC64'"> |
3030 |
/dev/sda4 / ext3 noatime 0 1 |
3031 |
/dev/sda3 none swap sw 0 0 |
3032 |
|
3033 |
proc /proc proc nodev,nosuid,noexec 0 0 |
3034 |
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
3035 |
|
3036 |
/dev/cdrom /mnt/cdrom auto noauto,user 0 0 |
3037 |
</pre> |
3038 |
|
3039 |
<p> |
3040 |
<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for |
3041 |
removable media as they can be created with one of many filesystems) and |
3042 |
<c>user</c> makes it possible for non-root users to mount the CD. |
3043 |
</p> |
3044 |
|
3045 |
<p> |
3046 |
To improve performance, most users would want to add the <c>noatime</c> |
3047 |
mount option, which results in a faster system since access times |
3048 |
aren't registered (you don't need those generally anyway). |
3049 |
</p> |
3050 |
|
3051 |
<p> |
3052 |
Double-check your <path>/etc/fstab</path>, save and quit to continue. |
3053 |
</p> |
3054 |
|
3055 |
</body> |
3056 |
</subsection> |
3057 |
</section> |
3058 |
<section> |
3059 |
<title>Networking Information</title> |
3060 |
<subsection> |
3061 |
<title>Hostname, Domainname etc.</title> |
3062 |
<body> |
3063 |
|
3064 |
<p> |
3065 |
One of the choices the user has to make is name his/her PC. This seems to be |
3066 |
quite easy, but <e>lots</e> of users are having difficulties finding the |
3067 |
appropriate name for their Linux-pc. To speed things up, know that any name you |
3068 |
choose can be changed afterwards. For all we care, you can just call your system |
3069 |
<c>tux</c> and domain <c>homenetwork</c>. |
3070 |
</p> |
3071 |
|
3072 |
<p> |
3073 |
We use these values in the next examples. First we set the hostname: |
3074 |
</p> |
3075 |
|
3076 |
<pre caption="Setting the hostname"> |
3077 |
# <i>nano -w /etc/conf.d/hostname</i> |
3078 |
|
3079 |
<comment>(Set the HOSTNAME variable to your hostname)</comment> |
3080 |
HOSTNAME="<i>tux</i>" |
3081 |
</pre> |
3082 |
|
3083 |
<p> |
3084 |
Second, <e>if</e> you need a domainname, set it in <path>/etc/conf.d/net</path>. |
3085 |
You only need a domain if your ISP or network administrator says so, or if you |
3086 |
have a DNS server but not a DHCP server. You don't need to worry about DNS or |
3087 |
domainnames if your networking is setup for DHCP. |
3088 |
</p> |
3089 |
|
3090 |
<pre caption="Setting the domainname"> |
3091 |
# <i>nano -w /etc/conf.d/net</i> |
3092 |
|
3093 |
<comment>(Set the dns_domain variable to your domain name)</comment> |
3094 |
dns_domain_lo="<i>homenetwork</i>" |
3095 |
</pre> |
3096 |
|
3097 |
<note> |
3098 |
If you choose not to set a domainname, you can get rid of the "This is |
3099 |
hostname.(none)" messages at your login screen by editing |
3100 |
<path>/etc/issue</path>. Just delete the string <c>.\O</c> from that file. |
3101 |
</note> |
3102 |
|
3103 |
<p> |
3104 |
If you have a NIS domain (if you don't know what that is, then you don't have |
3105 |
one), you need to define that one too: |
3106 |
</p> |
3107 |
|
3108 |
<pre caption="Setting the NIS domainname"> |
3109 |
# <i>nano -w /etc/conf.d/net</i> |
3110 |
|
3111 |
<comment>(Set the nis_domain variable to your NIS domain name)</comment> |
3112 |
nis_domain_lo="<i>my-nisdomain</i>" |
3113 |
</pre> |
3114 |
|
3115 |
<note> |
3116 |
For more information on configuring DNS and NIS, please read the examples |
3117 |
provided in <path>/etc/conf.d/net.example</path>. Also, you may want to emerge |
3118 |
<c>resolvconf-gentoo</c> to help manage your DNS/NIS setup. |
3119 |
</note> |
3120 |
|
3121 |
</body> |
3122 |
</subsection> |
3123 |
<subsection> |
3124 |
<title>Configuring your Network</title> |
3125 |
<body> |
3126 |
|
3127 |
<p> |
3128 |
Before you get that "Hey, we've had that already"-feeling, you should remember |
3129 |
that the networking you set up in the beginning of the Gentoo installation was |
3130 |
just for the installation. Right now you are going to configure networking for |
3131 |
your Gentoo system permanently. |
3132 |
</p> |
3133 |
|
3134 |
<note> |
3135 |
More detailed information about networking, including advanced topics like |
3136 |
bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri |
3137 |
link="?part=4">Gentoo Network Configuration</uri> section. |
3138 |
</note> |
3139 |
|
3140 |
<p> |
3141 |
All networking information is gathered in <path>/etc/conf.d/net</path>. It uses |
3142 |
a straightforward yet not intuitive syntax if you don't know how to set up |
3143 |
networking manually. But don't fear, we'll explain everything. A fully |
3144 |
commented example that covers many different configurations is available in |
3145 |
<path>/etc/conf.d/net.example</path>. |
3146 |
</p> |
3147 |
|
3148 |
<p> |
3149 |
DHCP is used by default and does not require any further configuration. |
3150 |
</p> |
3151 |
|
3152 |
<p> |
3153 |
If you need to configure your network connection either because you need |
3154 |
specific DHCP options or because you do not use DHCP at all, open |
3155 |
<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in |
3156 |
this example): |
3157 |
</p> |
3158 |
|
3159 |
<pre caption="Opening /etc/conf.d/net for editing"> |
3160 |
# <i>nano -w /etc/conf.d/net</i> |
3161 |
</pre> |
3162 |
|
3163 |
<p> |
3164 |
You will see the following file: |
3165 |
</p> |
3166 |
|
3167 |
<pre caption="Default /etc/conf.d/net"> |
3168 |
# This blank configuration will automatically use DHCP for any net.* |
3169 |
# scripts in /etc/init.d. To create a more complete configuration, |
3170 |
# please review /etc/conf.d/net.example and save your configuration |
3171 |
# in /etc/conf.d/net (this file :]!). |
3172 |
</pre> |
3173 |
|
3174 |
<p> |
3175 |
To enter your own IP address, netmask and gateway, you need |
3176 |
to set both <c>config_eth0</c> and <c>routes_eth0</c>: |
3177 |
</p> |
3178 |
|
3179 |
<pre caption="Manually setting IP information for eth0"> |
3180 |
config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" ) |
3181 |
routes_eth0=( "default via 192.168.0.1" ) |
3182 |
</pre> |
3183 |
|
3184 |
<p> |
3185 |
To use DHCP and add specific DHCP options, define <c>config_eth0</c> and |
3186 |
<c>dhcp_eth0</c>: |
3187 |
</p> |
3188 |
|
3189 |
<pre caption="Automatically obtaining an IP address for eth0"> |
3190 |
config_eth0=( "dhcp" ) |
3191 |
dhcp_eth0="nodns nontp nonis" |
3192 |
</pre> |
3193 |
|
3194 |
<p> |
3195 |
Please read <path>/etc/conf.d/net.example</path> for a list of all available |
3196 |
options. |
3197 |
</p> |
3198 |
|
3199 |
<p> |
3200 |
If you have several network interfaces repeat the above steps for |
3201 |
<c>config_eth1</c>, <c>config_eth2</c>, etc. |
3202 |
</p> |
3203 |
|
3204 |
<p> |
3205 |
Now save the configuration and exit to continue. |
3206 |
</p> |
3207 |
|
3208 |
</body> |
3209 |
</subsection> |
3210 |
<subsection> |
3211 |
<title>Automatically Start Networking at Boot</title> |
3212 |
<body> |
3213 |
|
3214 |
<p> |
3215 |
To have your network interfaces activated at boot, you need to add them to the |
3216 |
default runlevel. |
3217 |
</p> |
3218 |
|
3219 |
<pre caption="Adding net.eth0 to the default runlevel"> |
3220 |
# <i>rc-update add net.eth0 default</i> |
3221 |
</pre> |
3222 |
|
3223 |
<p> |
3224 |
If you have several network interfaces, you need to create the appropriate |
3225 |
<path>net.eth1</path>, <path>net.eth2</path> etc. initscripts for those. You can |
3226 |
use <c>ln</c> to do this: |
3227 |
</p> |
3228 |
|
3229 |
<pre caption="Creating extra initscripts"> |
3230 |
# <i>cd /etc/init.d</i> |
3231 |
# <i>ln -s net.lo net.eth1</i> |
3232 |
# <i>rc-update add net.eth1 default</i> |
3233 |
</pre> |
3234 |
|
3235 |
</body> |
3236 |
</subsection> |
3237 |
<subsection> |
3238 |
<title>Writing Down Network Information</title> |
3239 |
<body> |
3240 |
|
3241 |
<p> |
3242 |
You now need to inform Linux about your network. This is defined in |
3243 |
<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses for |
3244 |
hosts that aren't resolved by your nameserver. You need to define your system. |
3245 |
You may also want to define other systems on your network if you don't want to |
3246 |
set up your own internal DNS system. |
3247 |
</p> |
3248 |
|
3249 |
<pre caption="Opening /etc/hosts"> |
3250 |
# <i>nano -w /etc/hosts</i> |
3251 |
</pre> |
3252 |
|
3253 |
<pre caption="Filling in the networking information"> |
3254 |
<comment>(This defines the current system)</comment> |
3255 |
127.0.0.1 tux.homenetwork tux localhost |
3256 |
|
3257 |
<comment>(Define extra systems on your network, |
3258 |
they need to have a static IP to be defined this way.)</comment> |
3259 |
192.168.0.5 jenny.homenetwork jenny |
3260 |
192.168.0.6 benny.homenetwork benny |
3261 |
</pre> |
3262 |
|
3263 |
<p> |
3264 |
Save and exit the editor to continue. |
3265 |
</p> |
3266 |
|
3267 |
<p test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'"> |
3268 |
If you don't have PCMCIA, you can now continue with <uri |
3269 |
link="#sysinfo">System Information</uri>. PCMCIA-users should read the |
3270 |
following topic on PCMCIA. |
3271 |
</p> |
3272 |
|
3273 |
</body> |
3274 |
</subsection> |
3275 |
<subsection test="func:keyval('arch')='AMD64' or func:keyval('arch')='x86' or substring(func:keyval('arch'),1,3)='PPC'"> |
3276 |
<title>Optional: Get PCMCIA Working</title> |
3277 |
<body> |
3278 |
|
3279 |
<p> |
3280 |
PCMCIA users should first install the <c>pcmciautils</c> package. |
3281 |
</p> |
3282 |
|
3283 |
<pre caption="Installing pcmciautils"> |
3284 |
# <i>emerge pcmciautils</i> |
3285 |
</pre> |
3286 |
|
3287 |
</body> |
3288 |
</subsection> |
3289 |
</section> |
3290 |
|
3291 |
<section id="sysinfo"> |
3292 |
<title>System Information</title> |
3293 |
<subsection> |
3294 |
<title>Root Password</title> |
3295 |
<body> |
3296 |
|
3297 |
<p> |
3298 |
First we set the root password by typing: |
3299 |
</p> |
3300 |
|
3301 |
<pre caption="Setting the root password"> |
3302 |
# <i>passwd</i> |
3303 |
</pre> |
3304 |
|
3305 |
<p> |
3306 |
If you want root to be able to log on through the serial console, add |
3307 |
<c>tts/0</c> to <path>/etc/securetty</path>: |
3308 |
</p> |
3309 |
|
3310 |
<pre caption="Adding tts/0 to /etc/securetty"> |
3311 |
# <i>echo "tts/0" >> /etc/securetty</i> |
3312 |
</pre> |
3313 |
|
3314 |
</body> |
3315 |
</subsection> |
3316 |
<subsection> |
3317 |
<title>System Information</title> |
3318 |
<body> |
3319 |
|
3320 |
<p> |
3321 |
Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. |
3322 |
Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :) |
3323 |
</p> |
3324 |
|
3325 |
<pre caption="Opening /etc/rc.conf"> |
3326 |
# <i>nano -w /etc/rc.conf</i> |
3327 |
</pre> |
3328 |
|
3329 |
<p> |
3330 |
When you're finished configuring <path>/etc/rc.conf</path>, save and exit. |
3331 |
</p> |
3332 |
|
3333 |
<p> |
3334 |
As you can see, this file is well commented to help you set up the necessary |
3335 |
configuration variables. You can configure your system to use unicode and |
3336 |
define your default editor and your display manager (like gdm or kdm). |
3337 |
</p> |
3338 |
|
3339 |
<p> |
3340 |
Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration. |
3341 |
Edit it to configure your keyboard. |
3342 |
</p> |
3343 |
|
3344 |
<pre caption="Opening /etc/conf.d/keymaps"> |
3345 |
# <i>nano -w /etc/conf.d/keymaps</i> |
3346 |
</pre> |
3347 |
|
3348 |
<p> |
3349 |
Take special care with the <c>KEYMAP</c> variable. If you select the wrong |
3350 |
<c>KEYMAP</c>, you will get weird results when typing on your keyboard. |
3351 |
</p> |
3352 |
|
3353 |
<note test="substring(func:keyval('arch'),1,3)='PPC'"> |
3354 |
PPC uses x86 keymaps on most systems. Users who want to be able to use ADB |
3355 |
keymaps on boot have to enable ADB keycode sendings in their kernel and have to |
3356 |
set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>. |
3357 |
</note> |
3358 |
|
3359 |
<p> |
3360 |
When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and |
3361 |
exit. |
3362 |
</p> |
3363 |
|
3364 |
<p> |
3365 |
Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it |
3366 |
according to your needs. |
3367 |
</p> |
3368 |
|
3369 |
<pre caption="Opening /etc/conf.d/clock"> |
3370 |
# <i>nano -w /etc/conf.d/clock</i> |
3371 |
</pre> |
3372 |
|
3373 |
<p> |
3374 |
If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to |
3375 |
the file. Otherwise you will notice some clock skew. |
3376 |
</p> |
3377 |
|
3378 |
<p> |
3379 |
You should define the timezone that you previously copied to |
3380 |
<path>/etc/localtime</path> so that further upgrades of the |
3381 |
<c>sys-libs/timezone-data</c> package can update <path>/etc/localtime</path> |
3382 |
automatically. For instance, if you used the GMT timezone, you would add |
3383 |
<c>TIMEZONE="GMT"</c> |
3384 |
</p> |
3385 |
|
3386 |
<p> |
3387 |
When you're finished configuring <path>/etc/conf.d/clock</path>, save and |
3388 |
exit. |
3389 |
</p> |
3390 |
|
3391 |
<p test="not(func:keyval('arch')='PPC64')"> |
3392 |
Please continue with <uri link="?part=1&chap=9">Installing Necessary System |
3393 |
Tools</uri>. |
3394 |
</p> |
3395 |
|
3396 |
</body> |
3397 |
</subsection> |
3398 |
<subsection test="func:keyval('arch')='PPC64'"> |
3399 |
<title>Configuring the Console</title> |
3400 |
<body> |
3401 |
|
3402 |
<p> |
3403 |
If you are using a virtual console, you must uncomment the appropriate line in |
3404 |
<path>/etc/inittab</path> for the virtual console to spawn a login prompt. |
3405 |
</p> |
3406 |
|
3407 |
<pre caption="Enabling hvc or hvsi support in /etc/inittab"> |
3408 |
hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0 |
3409 |
hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0 |
3410 |
</pre> |
3411 |
|
3412 |
<p> |
3413 |
You should also take this time to verify that the appropriate console is |
3414 |
listed in <path>/etc/securetty</path>. |
3415 |
</p> |
3416 |
|
3417 |
<p> |
3418 |
You may now continue with <uri link="?part=1&chap=9">Installing Necessary |
3419 |
System Tools</uri>. |
3420 |
</p> |
3421 |
|
3422 |
</body> |
3423 |
</subsection> |
3424 |
</section> |
3425 |
</sections> |
3426 |
|
3427 |
|
3428 |
|
3429 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-finalise.xml |
3430 |
|
3431 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-finalise.xml?rev=1.1&view=markup |
3432 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-finalise.xml?rev=1.1&content-type=text/plain |
3433 |
|
3434 |
Index: hb-install-finalise.xml |
3435 |
=================================================================== |
3436 |
<?xml version='1.0' encoding='UTF-8'?> |
3437 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
3438 |
|
3439 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
3440 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
3441 |
|
3442 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-finalise.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
3443 |
|
3444 |
<sections> |
3445 |
|
3446 |
<version>8.0</version> |
3447 |
<date>2007-05-07</date> |
3448 |
|
3449 |
<section> |
3450 |
<title>User Administration</title> |
3451 |
<subsection> |
3452 |
<title>Adding a User for Daily Use</title> |
3453 |
<body> |
3454 |
|
3455 |
<p> |
3456 |
Working as root on a Unix/Linux system is <e>dangerous</e> and should be avoided |
3457 |
as much as possible. Therefore it is <e>strongly</e> recommended to add a user |
3458 |
for day-to-day use. |
3459 |
</p> |
3460 |
|
3461 |
<p> |
3462 |
The groups the user is member of define what activities the user can perform. |
3463 |
The following table lists a number of important groups you might wish to use: |
3464 |
</p> |
3465 |
|
3466 |
<table> |
3467 |
<tr> |
3468 |
<th>Group</th> |
3469 |
<th>Description</th> |
3470 |
</tr> |
3471 |
<tr> |
3472 |
<ti>audio</ti> |
3473 |
<ti>be able to access the audio devices</ti> |
3474 |
</tr> |
3475 |
<tr> |
3476 |
<ti>cdrom</ti> |
3477 |
<ti>be able to directly access optical devices</ti> |
3478 |
</tr> |
3479 |
<tr> |
3480 |
<ti>floppy</ti> |
3481 |
<ti>be able to directly access floppy devices</ti> |
3482 |
</tr> |
3483 |
<tr> |
3484 |
<ti>games</ti> |
3485 |
<ti>be able to play games</ti> |
3486 |
</tr> |
3487 |
<tr> |
3488 |
<ti>portage</ti> |
3489 |
<ti>be able to use <c>emerge --pretend</c> as a normal user</ti> |
3490 |
</tr> |
3491 |
<tr> |
3492 |
<ti>usb</ti> |
3493 |
<ti>be able to access USB devices</ti> |
3494 |
</tr> |
3495 |
<tr> |
3496 |
<ti>plugdev</ti> |
3497 |
<ti> |
3498 |
Be able to mount and use pluggable devices such as cameras and USB sticks |
3499 |
</ti> |
3500 |
</tr> |
3501 |
<tr> |
3502 |
<ti>video</ti> |
3503 |
<ti> |
3504 |
be able to access video capturing hardware and doing hardware |
3505 |
acceleration |
3506 |
</ti> |
3507 |
</tr> |
3508 |
<tr> |
3509 |
<ti>wheel</ti> |
3510 |
<ti>be able to use <c>su</c></ti> |
3511 |
</tr> |
3512 |
</table> |
3513 |
|
3514 |
<p> |
3515 |
For instance, to create a user called <c>john</c> who is member of the |
3516 |
<c>wheel</c>, <c>users</c> and <c>audio</c> groups, log in as root first |
3517 |
(only root can create users) and run <c>useradd</c>: |
3518 |
</p> |
3519 |
|
3520 |
<pre caption="Adding a user for day-to-day use"> |
3521 |
Login: <i>root</i> |
3522 |
Password: <comment>(Your root password)</comment> |
3523 |
|
3524 |
# <i>useradd -m -G users,wheel,audio -s /bin/bash john</i> |
3525 |
# <i>passwd john</i> |
3526 |
Password: <comment>(Enter the password for john)</comment> |
3527 |
Re-enter password: <comment>(Re-enter the password to verify)</comment> |
3528 |
</pre> |
3529 |
|
3530 |
<p> |
3531 |
If a user ever needs to perform some task as root, they can use <c>su -</c> |
3532 |
to temporarily receive root privileges. Another way is to use the <c>sudo</c> |
3533 |
package which is, if correctly configured, very secure. |
3534 |
</p> |
3535 |
|
3536 |
</body> |
3537 |
</subsection> |
3538 |
</section> |
3539 |
<section> |
3540 |
<title>Optional: Install GRP Packages</title> |
3541 |
<body> |
3542 |
|
3543 |
<impo> |
3544 |
This part is for GRP users only. Other users should skip this part and continue |
3545 |
with <uri link="?part=1&chap=12">Where to go from here?</uri>. |
3546 |
</impo> |
3547 |
|
3548 |
<p> |
3549 |
Now that your system is booted, log on as the user you created (for instance, |
3550 |
<c>john</c>) and use <c>su -</c> to gain root privileges: |
3551 |
</p> |
3552 |
|
3553 |
<pre caption="Gaining root privileges"> |
3554 |
$ <i>su -</i> |
3555 |
Password: <comment>(Enter your root password)</comment> |
3556 |
</pre> |
3557 |
|
3558 |
<p> |
3559 |
Now we need to change the Portage configuration to look for the prebuilt |
3560 |
binaries from the second CD (Gentoo Packages CD). First mount this CD: |
3561 |
</p> |
3562 |
|
3563 |
<pre caption="Mount the Packages CD"> |
3564 |
<comment>(Put the Gentoo Packages CD in the CD tray)</comment> |
3565 |
# <i>mount /mnt/cdrom</i> |
3566 |
</pre> |
3567 |
|
3568 |
<p> |
3569 |
Now configure Portage to use <path>/mnt/cdrom</path> for its prebuilt packages: |
3570 |
</p> |
3571 |
|
3572 |
<pre caption="Configuring Portage to use /mnt/cdrom"> |
3573 |
# <i>ls /mnt/cdrom</i> |
3574 |
|
3575 |
<comment>(If there is a /mnt/cdrom/packages directory:)</comment> |
3576 |
# <i>export PKGDIR="/mnt/cdrom/packages"</i> |
3577 |
|
3578 |
<comment>(Otherwise:)</comment> |
3579 |
# <i>export PKGDIR="/mnt/cdrom"</i> |
3580 |
</pre> |
3581 |
|
3582 |
<p> |
3583 |
Now install the packages you want. The Packages CD contains several prebuilt |
3584 |
binaries, for instance KDE and GNOME. |
3585 |
</p> |
3586 |
|
3587 |
<pre caption="Installing GNOME"> |
3588 |
# <i>emerge --usepkg gnome</i> |
3589 |
</pre> |
3590 |
|
3591 |
<p> |
3592 |
To find out what prebuilt packages are available, do a quick listing of all |
3593 |
the files in <path>/mnt/cdrom/All</path>. For instance, to find out if KDE is |
3594 |
emergeable: |
3595 |
</p> |
3596 |
|
3597 |
<pre caption="Finding out if KDE is installable"> |
3598 |
# <i>ls /mnt/cdrom/All/kde*</i> |
3599 |
</pre> |
3600 |
|
3601 |
<p> |
3602 |
Be sure to install the binaries now. When you do an <c>emerge --sync</c> to |
3603 |
update Portage (as you will learn later), the prebuilt binaries might not match |
3604 |
against the ebuilds in your updated Portage. You can try to circumvent this by |
3605 |
using <c>emerge --usepkgonly</c> instead of <c>emerge --usepkg</c>. |
3606 |
</p> |
3607 |
|
3608 |
<p> |
3609 |
Congratulations, your system is now fully equipped! Continue with <uri |
3610 |
link="?part=1&chap=12">Where to go from here?</uri> to learn more about |
3611 |
Gentoo. |
3612 |
</p> |
3613 |
|
3614 |
</body> |
3615 |
</section> |
3616 |
</sections> |
3617 |
|
3618 |
|
3619 |
|
3620 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-gli-dialog.xml |
3621 |
|
3622 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-gli-dialog.xml?rev=1.1&view=markup |
3623 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-gli-dialog.xml?rev=1.1&content-type=text/plain |
3624 |
|
3625 |
Index: hb-install-gli-dialog.xml |
3626 |
=================================================================== |
3627 |
<?xml version='1.0' encoding='UTF-8'?> |
3628 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
3629 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-gli-dialog.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
3630 |
|
3631 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
3632 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
3633 |
|
3634 |
<sections> |
3635 |
|
3636 |
<version>3.0</version> |
3637 |
<date>2007-05-07</date> |
3638 |
|
3639 |
<section> |
3640 |
<title>Welcome</title> |
3641 |
<subsection> |
3642 |
<title>Before you begin</title> |
3643 |
<body> |
3644 |
|
3645 |
<p> |
3646 |
After you boot the Gentoo Linux Installer LiveCD, it will attempt to load a |
3647 |
graphical desktop. If it is unable to do so, it will instead display a command |
3648 |
line prompt. To launch the installer, simply type: |
3649 |
</p> |
3650 |
|
3651 |
<pre caption="Start the installer"> |
3652 |
# <i>installer-dialog</i> |
3653 |
</pre> |
3654 |
|
3655 |
<p> |
3656 |
Once the installer has finished loading, you will be greeted by the welcome |
3657 |
screen. It provides a friendly introduction to the process of installing Gentoo |
3658 |
on your computer. Remember to read each option carefully. There is detailed |
3659 |
help available for each step of installation at the top of the screen. We |
3660 |
recommend that you always read the help provided before making your choices. |
3661 |
Note that at any time during the installation process, you can save your |
3662 |
configuration progress in case you need to resume your installation at a later |
3663 |
time. Use the <c>Tab</c> key (on your keyboard) to move around the menus within |
3664 |
a screen and the <c>Enter</c> key to confirm an action. |
3665 |
</p> |
3666 |
|
3667 |
<p> |
3668 |
There are two types of installation modes available, <c>Standard</c> and |
3669 |
<c>Advanced</c>. The first mode will set a number of options without requiring |
3670 |
your intervention, while the second mode will require you to make several more |
3671 |
choices during installation. |
3672 |
</p> |
3673 |
|
3674 |
<p> |
3675 |
If you choose <c>Standard</c>, skip ahead to <uri |
3676 |
link="#partitioning">Partitioning</uri>. Otherwise, continue reading. |
3677 |
</p> |
3678 |
|
3679 |
</body> |
3680 |
</subsection> |
3681 |
</section> |
3682 |
|
3683 |
<section> |
3684 |
<title>Advanced: Preinstallation Configuration</title> |
3685 |
<subsection> |
3686 |
<title>Manual Network Configuration</title> |
3687 |
<body> |
3688 |
|
3689 |
<p> |
3690 |
Even though you will be installing without a connection to the internet, you |
3691 |
can manually set up connections to your local area network (LAN), in case you |
3692 |
want to install Gentoo from another machine on your LAN. |
3693 |
</p> |
3694 |
|
3695 |
<p> |
3696 |
If you wish to enable SSH access to the machine (for remote installation), you |
3697 |
can start <c>sshd</c> and specify a root password. |
3698 |
</p> |
3699 |
|
3700 |
</body> |
3701 |
</subsection> |
3702 |
<subsection> |
3703 |
<title>Load Additional Kernel Modules</title> |
3704 |
<body> |
3705 |
|
3706 |
<p> |
3707 |
If you need to load more kernel modules to support your hardware, enter their |
3708 |
names, each separated by a space. |
3709 |
</p> |
3710 |
|
3711 |
</body> |
3712 |
</subsection> |
3713 |
</section> |
3714 |
|
3715 |
<section id="partitioning"> |
3716 |
<title>Partitioning</title> |
3717 |
<subsection> |
3718 |
<title>Preparing the disks</title> |
3719 |
<body> |
3720 |
|
3721 |
<p> |
3722 |
In order to install Gentoo on your machine, you will need to prepare your |
3723 |
disks. The <c>Partitioning</c> screen will show you a list of detected disks and |
3724 |
allow you to specify the filesystems you would like to have on your |
3725 |
partitions. Selecting <c>Clear partitions</c> will erase all previous partitions on |
3726 |
your disk, so be careful with this option!<!-- It is also possible to resize |
3727 |
certain partition types. --> |
3728 |
</p> |
3729 |
|
3730 |
<p> |
3731 |
If you choose to go with the <c>Recommended layout</c>, the installer will |
3732 |
create three partitions: 100MB for <path>/boot</path>, a <path>/swap</path> |
3733 |
partition up to 512MB in size, and the rest of the available space on the disk |
3734 |
is used for <path>/</path>, the root partition. |
3735 |
</p> |
3736 |
|
3737 |
<warn> |
3738 |
As with any partitioning application, you should backup your system before |
3739 |
making changes to your partition table, as any possible bugs could cause data |
3740 |
loss. |
3741 |
</warn> |
3742 |
|
3743 |
</body> |
3744 |
</subsection> |
3745 |
</section> |
3746 |
|
3747 |
<section> |
3748 |
<title>System Configuration</title> |
3749 |
<subsection> |
3750 |
<title>Installation type</title> |
3751 |
<body> |
3752 |
|
3753 |
<p> |
3754 |
Since you are performing a GRP/networkless install, you must select |
3755 |
<c>Networkless</c>, then continue with the installation. |
3756 |
</p> |
3757 |
|
3758 |
</body> |
3759 |
</subsection> |
3760 |
<subsection> |
3761 |
<title>Timezone</title> |
3762 |
<body> |
3763 |
|
3764 |
<p> |
3765 |
Study the list and select the region closest to your actual location. |
3766 |
</p> |
3767 |
|
3768 |
</body> |
3769 |
</subsection> |
3770 |
<subsection> |
3771 |
<title>Networking</title> |
3772 |
<body> |
3773 |
|
3774 |
<p> |
3775 |
On this screen, you will be able to configure the various network interface |
3776 |
devices detected on your computer. Read the available options carefully. |
3777 |
</p> |
3778 |
|
3779 |
<p> |
3780 |
The next screen gives you a choice between DHCP and manual IP address |
3781 |
configuration. Once your network interface is properly configured, you will |
3782 |
need to create a hostname for your system. Optionally, you may specify a |
3783 |
domainname and any DNS server information needed. |
3784 |
</p> |
3785 |
|
3786 |
</body> |
3787 |
</subsection> |
3788 |
<subsection> |
3789 |
<title>Bootloader</title> |
3790 |
<body> |
3791 |
|
3792 |
<p> |
3793 |
This screen allows to you choose your bootloader (<c>grub</c>, or no |
3794 |
bootloader). Next, select your boot device and (optionally) specify any |
3795 |
additional boot options. |
3796 |
</p> |
3797 |
|
3798 |
</body> |
3799 |
</subsection> |
3800 |
<subsection> |
3801 |
<title>Users and groups</title> |
3802 |
<body> |
3803 |
|
3804 |
<p> |
3805 |
First set the root password for the system administrator (the <e>root</e> |
3806 |
user). |
3807 |
</p> |
3808 |
|
3809 |
<p> |
3810 |
We <e>strongly</e> recommend that you create a regular user for daily work. |
3811 |
Working as root all the time is <e>dangerous</e> and should be avoided! Create |
3812 |
your users, set their passwords, and add them to the appropriate groups. You can |
3813 |
optionally change their home directories and select their login shell. |
3814 |
</p> |
3815 |
|
3816 |
</body> |
3817 |
</subsection> |
3818 |
<subsection> |
3819 |
<title>Extra Packages</title> |
3820 |
<body> |
3821 |
|
3822 |
<p> |
3823 |
The LiveCD contains a number of available pre-built packages. If you wish to |
3824 |
install any of them, check the appropriate box. |
3825 |
</p> |
3826 |
|
3827 |
</body> |
3828 |
</subsection> |
3829 |
<subsection> |
3830 |
<title>Startup Services</title> |
3831 |
<body> |
3832 |
|
3833 |
<p> |
3834 |
This screen allows you to choose various services to load at system boot. Study |
3835 |
the available options and their descriptions carefully, and then select your |
3836 |
desired services. For example, if you have chosen to install <c>xorg-x11</c> |
3837 |
and want to boot straight into a graphical desktop, then you would select |
3838 |
"xdm" from the list. |
3839 |
</p> |
3840 |
|
3841 |
</body> |
3842 |
</subsection> |
3843 |
<subsection> |
3844 |
<title>Other Settings</title> |
3845 |
<body> |
3846 |
|
3847 |
<p> |
3848 |
If you chose to perform an <c>Advanced</c> installation, you now will be able to |
3849 |
change various settings, including keyboard layout, graphical display manager, |
3850 |
the default editor, and whether to set your hardware clock to UTC or local |
3851 |
time. |
3852 |
</p> |
3853 |
|
3854 |
</body> |
3855 |
</subsection> |
3856 |
</section> |
3857 |
|
3858 |
<section> |
3859 |
<title>Finishing Up</title> |
3860 |
<subsection> |
3861 |
<body> |
3862 |
|
3863 |
<p> |
3864 |
The installer will ask if you want to save your <c>installation profile</c> for |
3865 |
later use. The installer will alert you when it has finished. It will then |
3866 |
return you to the command prompt. All you need to do to reboot is type: |
3867 |
</p> |
3868 |
|
3869 |
<pre caption="Rebooting"> |
3870 |
# <i>shutdown -r now</i> |
3871 |
</pre> |
3872 |
|
3873 |
<p> |
3874 |
Congratulations, your system is now fully equipped! Continue with <uri |
3875 |
link="?part=1&chap=5">Where to go from here?</uri> to learn more about |
3876 |
Gentoo. |
3877 |
</p> |
3878 |
|
3879 |
</body> |
3880 |
</subsection> |
3881 |
</section> |
3882 |
</sections> |
3883 |
|
3884 |
|
3885 |
|
3886 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-gli-medium.xml |
3887 |
|
3888 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-gli-medium.xml?rev=1.1&view=markup |
3889 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-gli-medium.xml?rev=1.1&content-type=text/plain |
3890 |
|
3891 |
Index: hb-install-gli-medium.xml |
3892 |
=================================================================== |
3893 |
<?xml version='1.0' encoding='UTF-8'?> |
3894 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
3895 |
|
3896 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
3897 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
3898 |
|
3899 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-gli-medium.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
3900 |
|
3901 |
<sections> |
3902 |
|
3903 |
<version>8.2</version> |
3904 |
<date>2007-06-29</date> |
3905 |
|
3906 |
<section> |
3907 |
<title>Hardware Requirements</title> |
3908 |
<subsection> |
3909 |
<title>Introduction</title> |
3910 |
<body> |
3911 |
|
3912 |
<p> |
3913 |
Before we start, we first list what hardware requirements you need to |
3914 |
successfully install Gentoo on your box using the Installer LiveCD. |
3915 |
</p> |
3916 |
|
3917 |
</body> |
3918 |
</subsection> |
3919 |
<subsection> |
3920 |
<title>Hardware Requirements</title> |
3921 |
<body> |
3922 |
|
3923 |
<table> |
3924 |
<tr test="func:keyval('arch')='x86'"> |
3925 |
<th>CPU</th> |
3926 |
<ti>i686 or later</ti> |
3927 |
</tr> |
3928 |
<tr test="func:keyval('arch')='AMD64'"> |
3929 |
<th>CPU</th> |
3930 |
<ti>Any AMD64 or EM64T CPU</ti> |
3931 |
</tr> |
3932 |
<tr> |
3933 |
<th>Memory</th> |
3934 |
<ti>256 MB</ti> |
3935 |
</tr> |
3936 |
<tr> |
3937 |
<th>Diskspace</th> |
3938 |
<ti>1.5 GB (excluding swap space)</ti> |
3939 |
</tr> |
3940 |
<tr> |
3941 |
<th>Swap space</th> |
3942 |
<ti>At least 256 MB</ti> |
3943 |
</tr> |
3944 |
</table> |
3945 |
|
3946 |
</body> |
3947 |
</subsection> |
3948 |
</section> |
3949 |
<!-- General description, propagated to other architectures as well --> |
3950 |
<!-- START --> |
3951 |
<section> |
3952 |
<title>The Gentoo Linux Installer LiveCD</title> |
3953 |
<subsection> |
3954 |
<title>Introduction</title> |
3955 |
<body> |
3956 |
|
3957 |
<p> |
3958 |
A LiveCD is a bootable medium which contains a self-sustained Gentoo |
3959 |
environment. It allows you to boot Linux from the CD. During the boot process |
3960 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
3961 |
Installation CDs are maintained by Gentoo developers. |
3962 |
</p> |
3963 |
|
3964 |
<p> |
3965 |
There currently are two Installation CDs available: |
3966 |
</p> |
3967 |
|
3968 |
<ul> |
3969 |
<li> |
3970 |
The Installer LiveCD contains everything you need to install Gentoo. It |
3971 |
provides a graphical environment, a graphical as well as console based |
3972 |
installer which automatically carries out the installation for you, and of |
3973 |
course, the installation instructions for your architecture. |
3974 |
</li> |
3975 |
<li> |
3976 |
The Minimal Installation CD contains only a minimal environment that allows |
3977 |
you to boot up and configure your network so you can connect to the |
3978 |
Internet. It does not contain any additional files and cannot be used |
3979 |
during the current installation approach. |
3980 |
</li> |
3981 |
</ul> |
3982 |
|
3983 |
</body> |
3984 |
</subsection> |
3985 |
</section> |
3986 |
<!-- STOP --> |
3987 |
<section> |
3988 |
<title>Download, Burn and Boot the Gentoo Linux Installer LiveCD</title> |
3989 |
<subsection> |
3990 |
<title>Downloading and Burning the Installer LiveCD</title> |
3991 |
<body> |
3992 |
|
3993 |
<p> |
3994 |
You can download the Installer LiveCDs from one of our <uri |
3995 |
link="/main/en/mirrors.xml">mirrors</uri>. They are located in the |
3996 |
<path><keyval id="release-dir"/>livecd/</path> directory. |
3997 |
</p> |
3998 |
|
3999 |
<p> |
4000 |
Inside that directory you'll find an ISO-file. That is a full CD image which |
4001 |
you can write on a CD-R. |
4002 |
</p> |
4003 |
|
4004 |
<p> |
4005 |
After downloading the file, you can verify its integrity to see if it is |
4006 |
corrupted or not: |
4007 |
</p> |
4008 |
|
4009 |
<ul> |
4010 |
<li> |
4011 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
4012 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or <uri |
4013 |
link="http://www.etree.org/md5com.html">md5sum</uri> for Windows) |
4014 |
</li> |
4015 |
<li> |
4016 |
You can verify the cryptographic signature that we provide. You need to |
4017 |
obtain the public key we use (17072058) before you proceed though. |
4018 |
</li> |
4019 |
</ul> |
4020 |
|
4021 |
<p> |
4022 |
To fetch our public key using the GnuPG application, run the following command: |
4023 |
</p> |
4024 |
|
4025 |
<pre caption="Obtaining the public key"> |
4026 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
4027 |
</pre> |
4028 |
|
4029 |
<p> |
4030 |
Now verify the signature: |
4031 |
</p> |
4032 |
|
4033 |
<pre caption="Verify the cryptographic signature"> |
4034 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
4035 |
</pre> |
4036 |
|
4037 |
<p> |
4038 |
To burn the downloaded ISO(s), you have to select raw-burning. How you do this |
4039 |
is highly program-dependent. We will discuss <c>cdrecord</c> and <c>K3B</c> |
4040 |
here; more information can be found in our <uri |
4041 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
4042 |
</p> |
4043 |
|
4044 |
<ul> |
4045 |
<li> |
4046 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
4047 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
4048 |
path). |
4049 |
</li> |
4050 |
<li> |
4051 |
With K3B, select <c>Tools</c> > <c>Burn CD Image</c>. Then you can locate |
4052 |
your ISO file within the 'Image to Burn' area. Finally click <c>Start</c>. |
4053 |
</li> |
4054 |
</ul> |
4055 |
|
4056 |
</body> |
4057 |
</subsection> |
4058 |
<subsection> |
4059 |
<title>Booting the Installer LiveCD</title> |
4060 |
<body> |
4061 |
|
4062 |
<impo> |
4063 |
Read this whole subsection before continuing, as you will probably not have the |
4064 |
opportunity to read it before doing things later. |
4065 |
</impo> |
4066 |
|
4067 |
<p> |
4068 |
Once you have burned your LiveCD, it is time to boot it. Remove all CDs from |
4069 |
your CD drives, reboot your system and enter the BIOS. This is usually done by |
4070 |
hitting DEL, F1 or ESC, depending on your BIOS. Inside the BIOS, change the |
4071 |
boot order so that the CD-ROM is tried before the hard disk. This is often |
4072 |
found under "CMOS Setup". If you don't do this, your system will just reboot |
4073 |
from the hard disk, ignoring the CD-ROM. |
4074 |
</p> |
4075 |
|
4076 |
<p> |
4077 |
Now place the LiveCD in the CD-ROM drive and reboot. You should see a boot |
4078 |
prompt. At this screen, you can hit Enter to begin the boot process with the |
4079 |
default boot options, or boot the LiveCD with custom boot options by specifying |
4080 |
a kernel followed by boot options and then hitting Enter. |
4081 |
</p> |
4082 |
|
4083 |
<p> |
4084 |
Specifying a kernel? Yes, we provide a few kernels on our LiveCD. The default |
4085 |
one is <c>gentoo</c>. Other kernels are for specific hardware needs and the |
4086 |
<c>-nofb</c> variants which disable framebuffer. |
4087 |
</p> |
4088 |
|
4089 |
<p> |
4090 |
Below you'll find a short overview on the available kernels: |
4091 |
</p> |
4092 |
|
4093 |
<table> |
4094 |
<tr> |
4095 |
<th>Kernel</th> |
4096 |
<th>Description</th> |
4097 |
</tr> |
4098 |
<tr test="func:keyval('arch')='x86'"> |
4099 |
<ti>gentoo</ti> |
4100 |
<ti>Default 2.6 kernel with support for multiple CPUs</ti> |
4101 |
</tr> |
4102 |
<tr test="func:keyval('arch')='x86'"> |
4103 |
<ti>gentoo-nofb</ti> |
4104 |
<ti>Same as <c>gentoo</c> but without framebuffer support</ti> |
4105 |
</tr> |
4106 |
<tr test="func:keyval('arch')='AMD64'"> |
4107 |
<ti>gentoo</ti> |
4108 |
<ti> |
4109 |
Default kernel with support for K8 CPUS (including NUMA support) and EM64T |
4110 |
CPUs |
4111 |
</ti> |
4112 |
</tr> |
4113 |
<tr> |
4114 |
<ti>memtest86</ti> |
4115 |
<ti>Test your local RAM for errors</ti> |
4116 |
</tr> |
4117 |
</table> |
4118 |
|
4119 |
<p> |
4120 |
You can also provide kernel options. They represent optional settings you can |
4121 |
(de)activate at will. The following list is the same as the one you receive |
4122 |
when you press F2 through F7 at the bootscreen. |
4123 |
</p> |
4124 |
|
4125 |
<pre caption="Options available to pass to your kernel of choice"> |
4126 |
<comment>Hardware options:</comment> |
4127 |
|
4128 |
acpi=on This loads support for ACPI and also causes the acpid daemon to |
4129 |
be started by the CD on boot. This is only needed if your |
4130 |
system requires ACPI to function properly. This is not |
4131 |
required for Hyperthreading support. |
4132 |
|
4133 |
acpi=off Completely disables ACPI. This is useful on some older |
4134 |
systems, and is also a requirement for using APM. This will |
4135 |
disable any Hyperthreading support of your processor. |
4136 |
|
4137 |
console=X This sets up serial console access for the CD. The first |
4138 |
option is the device, usually ttyS0 on x86, followed by any |
4139 |
connection options, which are comma separated. The default |
4140 |
options are 9600,8,n,1. |
4141 |
|
4142 |
dmraid=X This allows for passing options to the device-mapper RAID |
4143 |
subsystem. Options should be encapsulated in quotes. |
4144 |
|
4145 |
doapm This loads APM driver support. This requires you to also use |
4146 |
acpi=off. |
4147 |
|
4148 |
doslowusb This adds some extra pauses into the boot process for the slow |
4149 |
USB CDROM of the IBM BladeCenter. |
4150 |
|
4151 |
dopcmcia This loads support for PCMCIA and Cardbus hardware and also |
4152 |
causes the pcmcia cardmgr to be started by the CD on boot. |
4153 |
This is only required when booting from a PCMCIA/Cardbus device. |
4154 |
|
4155 |
doscsi This loads support for most SCSI controllers. This is also a |
4156 |
requirement for booting most USB devices, as they use the SCSI |
4157 |
subsystem of the kernel. |
4158 |
|
4159 |
hda=stroke This allows you to partition the whole hard disk even when your |
4160 |
BIOS is unable to handle large disks. This option is only used |
4161 |
on machines with an older BIOS. Replace hda with the device |
4162 |
that is requiring this option. |
4163 |
|
4164 |
ide=nodma This forces the disabling of DMA in the kernel and is required |
4165 |
by some IDE chipsets and also by some CDROM drives. If your |
4166 |
system is having trouble reading from your IDE CDROM, try this |
4167 |
option. This also disables the default hdparm settings from |
4168 |
being executed. |
4169 |
|
4170 |
noapic This disables the Advanced Programmable Interrupt Controller |
4171 |
that is present on newer motherboards. It has been known to |
4172 |
cause some problems on older hardware. |
4173 |
|
4174 |
nodetect This disables all of the autodetection done by the CD, |
4175 |
including device autodetection and DHCP probing. This is |
4176 |
useful for doing debugging of a failing CD or driver. |
4177 |
|
4178 |
nodhcp This disables DHCP probing on detected network cards. This is |
4179 |
useful on networks with only static addresses. |
4180 |
|
4181 |
nodmraid Disables support for device-mapper RAID, such as that used for |
4182 |
on-board IDE/SATA RAID controllers. |
4183 |
|
4184 |
nofirewire This disables the loading of Firewire modules. This should only |
4185 |
be necessary if your Firewire hardware is causing a problem |
4186 |
with booting the CD. |
4187 |
|
4188 |
nogpm This disables gpm console mouse support. |
4189 |
|
4190 |
nohotplug This disables the loading of the hotplug and coldplug init |
4191 |
scripts at boot. This is useful for doing debugging of a |
4192 |
failing CD or driver. |
4193 |
|
4194 |
nokeymap This disables the keymap selection used to select non-US |
4195 |
keyboard layouts. |
4196 |
|
4197 |
nolapic This disables the local APIC on Uniprocessor kernels. |
4198 |
|
4199 |
nosata This disables the loading of Serial ATA modules. This is |
4200 |
useful if your system is having problems with the SATA subsystem. |
4201 |
|
4202 |
nosmp This disables SMP, or Symmetric Multiprocessing, on SMP-enabled |
4203 |
kernels. This is useful for debugging SMP-related issues with |
4204 |
certain drivers and motherboards. |
4205 |
|
4206 |
nosound This disables sound support and volume setting. This is useful |
4207 |
for systems where sound support causes problems. |
4208 |
|
4209 |
nousb This disables the autoloading of USB modules. This is useful |
4210 |
for debugging USB issues. |
4211 |
|
4212 |
<comment>Volume/Device Management:</comment> |
4213 |
|
4214 |
dodevfs This enables the deprecated device filesystem on 2.6 systems. |
4215 |
You will also need to use noudev for this to take effect. |
4216 |
Since devfs is the only option with a 2.4 kernel, this option |
4217 |
has no effect if booting a 2.4 kernel. |
4218 |
|
4219 |
doevms2 This enables support for IBM's pluggable EVMS, or Enterprise |
4220 |
Volume Management System. This is not safe to use with lvm2. |
4221 |
|
4222 |
dolvm2 This enables support for Linux's Logical Volume Management. |
4223 |
This is not safe to use with evms2. |
4224 |
|
4225 |
noudev This disables udev support on 2.6 kernels. This option |
4226 |
requires that dodevfs is used. Since udev is not an option for |
4227 |
2.4 kernels, this options has no effect if booting a 2.4 |
4228 |
kernel. |
4229 |
|
4230 |
unionfs Enables support for Unionfs on supported CD images. This will |
4231 |
create a writable Unionfs overlay in a tmpfs, allowing you to |
4232 |
change any file on the CD. |
4233 |
|
4234 |
unionfs=X Enables support for Unionfs on supported CD images. This will |
4235 |
create a writable Unionfs overlay on the device you specify. |
4236 |
The device must be formatted with a filesystem recognized and |
4237 |
writable by the kernel. |
4238 |
|
4239 |
<comment>Other options:</comment> |
4240 |
|
4241 |
debug Enables debugging code. This might get messy, as it displays |
4242 |
a lot of data to the screen. |
4243 |
|
4244 |
docache This caches the entire runtime portion of the CD into RAM, |
4245 |
which allows you to umount /mnt/cdrom and mount another CDROM. |
4246 |
This option requires that you have at least twice as much |
4247 |
available RAM as the size of the CD. |
4248 |
|
4249 |
doload=X This causes the initial ramdisk to load any module listed, as |
4250 |
well as dependencies. Replace X with the module name. Multiple |
4251 |
modules can be specified by a comma-separated list. |
4252 |
|
4253 |
noload=X This causes the initial ramdisk to skip the loading of a |
4254 |
specific module that may be causing a problem. Syntax matches |
4255 |
that of doload. |
4256 |
|
4257 |
nox This causes an X-enabled LiveCD to not automatically start X, |
4258 |
but rather, to drop to the command line instead. |
4259 |
|
4260 |
scandelay This causes the CD to pause for 10 seconds during certain |
4261 |
portions the boot process to allow for devices that are slow to |
4262 |
initialize to be ready for use. |
4263 |
|
4264 |
scandelay=X This allows you to specify a given delay, in seconds, to be |
4265 |
added to certain portions of the boot process to allow for |
4266 |
devices that are slow to initialize to be ready for use. |
4267 |
Replace X with the number of seconds to pause. |
4268 |
</pre> |
4269 |
|
4270 |
<p> |
4271 |
Now boot your CD, select a kernel (if you are not happy with the default |
4272 |
<c>gentoo</c> kernel) and boot options. As an example, we show you how |
4273 |
to boot the <c>gentoo</c> kernel, with <c>dopcmcia</c> as kernel |
4274 |
parameters: |
4275 |
</p> |
4276 |
|
4277 |
<pre caption="Booting an Installation CD"> |
4278 |
boot: <i>gentoo dopcmcia</i> |
4279 |
</pre> |
4280 |
|
4281 |
<p> |
4282 |
You will then be greeted with a boot screen and progress bar. If you are |
4283 |
installing Gentoo on a system with a non-US keyboard, make sure you |
4284 |
immediately press Alt-F1 to switch to verbose mode and follow the prompt. If no |
4285 |
selection is made in 10 seconds the default (US keyboard) will be accepted and |
4286 |
the boot process will continue. Once the boot process completes, Gnome will |
4287 |
start up and you will be automatically logged in to the "Live" Gentoo Linux |
4288 |
system as "gentoo" in graphical mode. You will be logged in as "root", the |
4289 |
superuser on the other consoles and should have a root ("#") prompt there. You |
4290 |
can switch to those consoles by pressing Alt-F2, Alt-F3, Alt-F4 Alt-F5, Alt-F6. |
4291 |
Get back to the graphical desktop you started on by pressing Alt-F7. To switch |
4292 |
to other consoles from within X, you must prefix the above with Ctrl. You are |
4293 |
able to run commands as root from any terminal within the graphical environment |
4294 |
by using the <c>sudo</c> application. You can even become root within a |
4295 |
terminal to perform multiple tasks. |
4296 |
</p> |
4297 |
|
4298 |
<pre caption="Using sudo to run applications"> |
4299 |
<comment>(Example only)</comment> |
4300 |
<comment>(Editing the group file)</comment> |
4301 |
# <i>sudo vi /etc/group</i> |
4302 |
<comment>(Becoming root for a session)</comment> |
4303 |
# <i>sudo su -</i> |
4304 |
</pre> |
4305 |
|
4306 |
</body> |
4307 |
</subsection> |
4308 |
<subsection id="hardware"> |
4309 |
<title>Extra Hardware Configuration</title> |
4310 |
<body> |
4311 |
|
4312 |
<p> |
4313 |
When the LiveCD boots, it tries to detect all your hardware devices and loads |
4314 |
the appropriate kernel modules to support your hardware. In the vast majority |
4315 |
of cases, it does a very good job. However, in some cases, it may not auto-load |
4316 |
the kernel modules you need. If the PCI auto-detection missed some of your |
4317 |
system's hardware, you will have to load the appropriate kernel modules |
4318 |
manually. These tasks require root access. |
4319 |
</p> |
4320 |
|
4321 |
<p> |
4322 |
In the next example we try to load the <c>8139too</c> module (support for |
4323 |
certain kinds of network interfaces): |
4324 |
</p> |
4325 |
|
4326 |
<pre caption="Loading kernel modules"> |
4327 |
# <i>modprobe 8139too</i> |
4328 |
</pre> |
4329 |
|
4330 |
</body> |
4331 |
</subsection> |
4332 |
<subsection> |
4333 |
<title>Optional: Tweaking Hard Disk Performance</title> |
4334 |
<body> |
4335 |
|
4336 |
<p> |
4337 |
If you are an advanced user, you might want to tweak the IDE hard disk |
4338 |
performance using <c>hdparm</c>. You will need root access to use <c>hdparm</c>. |
4339 |
With the <c>-tT</c> options you can test the performance of your disk (execute |
4340 |
it several times to get a more precise impression): |
4341 |
</p> |
4342 |
|
4343 |
<pre caption="Testing disk performance"> |
4344 |
# <i>hdparm -tT /dev/hda</i> |
4345 |
</pre> |
4346 |
|
4347 |
<p> |
4348 |
To tweak, you can use any of the following examples (or experiment |
4349 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
4350 |
disk): |
4351 |
</p> |
4352 |
|
4353 |
<pre caption="Tweaking hard disk performance"> |
4354 |
<comment>(Activate DMA:)</comment> |
4355 |
# <i>hdparm -d 1 /dev/hda</i> |
4356 |
<comment>(Or with Safe Performance Options:)</comment> |
4357 |
# <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
4358 |
</pre> |
4359 |
|
4360 |
</body> |
4361 |
</subsection> |
4362 |
<subsection id="useraccounts"> |
4363 |
<title>Optional: User Accounts</title> |
4364 |
<body> |
4365 |
|
4366 |
<p> |
4367 |
If you plan on giving other people access to your installation environment or |
4368 |
you want to chat using <c>irssi</c> without root privileges (for security |
4369 |
reasons), you need to create the necessary user accounts and change the root |
4370 |
password. You need root access to change the root password and add new users. |
4371 |
</p> |
4372 |
|
4373 |
<p> |
4374 |
To change the root password, use the <c>passwd</c> utility: |
4375 |
</p> |
4376 |
|
4377 |
<pre caption="Changing the root password"> |
4378 |
$ <i>sudo su -</i> |
4379 |
# <i>passwd</i> |
4380 |
New password: <comment>(Enter your new password)</comment> |
4381 |
Re-enter password: <comment>(Re-enter your password)</comment> |
4382 |
</pre> |
4383 |
|
4384 |
<p> |
4385 |
To create a user account, we first enter their credentials, followed by its |
4386 |
password. We use <c>useradd</c> and <c>passwd</c> for these tasks. In the next |
4387 |
example, we create a user called "john". |
4388 |
</p> |
4389 |
|
4390 |
<pre caption="Creating a user account"> |
4391 |
# <i>useradd -m -G users john</i> |
4392 |
# <i>passwd john</i> |
4393 |
New password: <comment>(Enter john's password)</comment> |
4394 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
4395 |
</pre> |
4396 |
|
4397 |
<p> |
4398 |
You can change your user id from root to the newly created user by using |
4399 |
<c>su</c>: |
4400 |
</p> |
4401 |
|
4402 |
<pre caption="Changing user id"> |
4403 |
# <i>su - john</i> |
4404 |
</pre> |
4405 |
|
4406 |
<p> |
4407 |
You can also change the password for the "gentoo" user in the graphical |
4408 |
environment. This account is already suitable for use on the Internet. |
4409 |
</p> |
4410 |
|
4411 |
<pre caption="Changing the gentoo password"> |
4412 |
$ <i>passwd</i> |
4413 |
New password: <comment>(Enter your new password)</comment> |
4414 |
Re-enter password: <comment>(Re-enter your password)</comment> |
4415 |
</pre> |
4416 |
|
4417 |
</body> |
4418 |
</subsection> |
4419 |
<subsection> |
4420 |
<title>Optional: Viewing Documentation while Installing</title> |
4421 |
<body> |
4422 |
|
4423 |
<p> |
4424 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
4425 |
installation, you can view it with Mozilla Firefox (from the graphical |
4426 |
environment) or with <c>links</c> (from a terminal environment). |
4427 |
</p> |
4428 |
|
4429 |
<pre caption="Viewing the on-CD documentation with Firefox"> |
4430 |
# <i>firefox /mnt/cdrom/docs/handbook/html/index.html</i> |
4431 |
</pre> |
4432 |
|
4433 |
<p> |
4434 |
If you would prefer to use <c>links</c> to see a text-only version of the |
4435 |
handbook, make sure you have created a user account (see <uri |
4436 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> |
4437 |
to go to a new terminal and log in. |
4438 |
</p> |
4439 |
|
4440 |
<pre caption="Viewing the on-CD documentation with links"> |
4441 |
# <i>links /mnt/cdrom/docs/handbook/html/index.html</i> |
4442 |
</pre> |
4443 |
|
4444 |
<p> |
4445 |
You can go back to your original window by pressing <c>Alt-F7</c>. |
4446 |
</p> |
4447 |
|
4448 |
<p> |
4449 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
4450 |
more recent than the one provided on the CD. You can view it using Firefox or |
4451 |
<c>links</c> as well, but only after having completed the <e>Configuring your |
4452 |
Network</e> chapter (otherwise you won't be able to go on the Internet to view |
4453 |
the document): |
4454 |
</p> |
4455 |
|
4456 |
<pre caption="Viewing the online documentation with Firefox"> |
4457 |
# <i>firefox http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i> |
4458 |
</pre> |
4459 |
|
4460 |
<pre caption="Viewing the online documentation with links"> |
4461 |
# <i>links http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i> |
4462 |
</pre> |
4463 |
|
4464 |
<p> |
4465 |
You can now choose to proceed by using the <uri link="?part=1&chap=3">GTK+ |
4466 |
based installer</uri> (which needs X) or the <uri |
4467 |
link="?part=1&chap=4">Dialog based installer</uri> that can be run on a |
4468 |
console. |
4469 |
</p> |
4470 |
|
4471 |
</body> |
4472 |
</subsection> |
4473 |
</section> |
4474 |
</sections> |
4475 |
|
4476 |
|
4477 |
|
4478 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-gtkfe.xml |
4479 |
|
4480 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-gtkfe.xml?rev=1.1&view=markup |
4481 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-gtkfe.xml?rev=1.1&content-type=text/plain |
4482 |
|
4483 |
Index: hb-install-gtkfe.xml |
4484 |
=================================================================== |
4485 |
<?xml version='1.0' encoding='UTF-8'?> |
4486 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
4487 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-gtkfe.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
4488 |
|
4489 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
4490 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
4491 |
|
4492 |
<sections> |
4493 |
|
4494 |
<version>3.3</version> |
4495 |
<date>2007-06-02</date> |
4496 |
|
4497 |
<section> |
4498 |
<title>Welcome</title> |
4499 |
<subsection> |
4500 |
<title>Before you begin</title> |
4501 |
<body> |
4502 |
|
4503 |
<p> |
4504 |
Once the Gentoo Linux Installer (GLI) has finished loading, you will be greeted |
4505 |
by the welcome screen. It provides a friendly introduction to the process of |
4506 |
installing Gentoo on your computer. Remember to read each option carefully. |
4507 |
There is detailed help available for each step of installation; just look to the |
4508 |
left of each screen. We recommend that you always read the help pages before |
4509 |
making your choices. Note that at any time during the installation process, you |
4510 |
can save your configuration progress in case you need to resume your |
4511 |
installation at a later time. |
4512 |
</p> |
4513 |
|
4514 |
<p> |
4515 |
There are three types of installation modes available. Choose <c>Networkless</c> |
4516 |
to begin installing Gentoo Linux. |
4517 |
</p> |
4518 |
|
4519 |
<note> |
4520 |
Selecting <c>Networkless</c> will make some later configuration options |
4521 |
unavailable. |
4522 |
</note> |
4523 |
|
4524 |
</body> |
4525 |
</subsection> |
4526 |
</section> |
4527 |
|
4528 |
<section> |
4529 |
<title>Partitioning</title> |
4530 |
<subsection> |
4531 |
<title>Preparing the disks</title> |
4532 |
<body> |
4533 |
|
4534 |
<p> |
4535 |
In order to install Gentoo on your machine, you will need to prepare your |
4536 |
disks. The <e>Partitioning</e> screen will show you a list of detected disks and |
4537 |
allow you to specify the filesystems you would like to have on your |
4538 |
partitions. Clicking <c>Clear partitions</c> will erase all previous partitions on |
4539 |
your disk, so be careful with this option! It is also possible to resize |
4540 |
certain partition types. |
4541 |
</p> |
4542 |
|
4543 |
<p> |
4544 |
If you choose to go with the <c>Recommended layout</c>, the installer will erase |
4545 |
any previous partitions on your disk and create three partitions: 100MB for |
4546 |
<path>/boot</path>, a <path>/swap</path> partition up to 512MB in size, and the |
4547 |
rest of the available space on the disk is used for <path>/</path>, the root |
4548 |
partition. |
4549 |
</p> |
4550 |
|
4551 |
<warn> |
4552 |
As with any partitioning application, you should backup your system before |
4553 |
making changes to your partition table, as any possible bugs could cause data |
4554 |
loss. Any changes you make to your partition table will be performed by the |
4555 |
installer immediately. |
4556 |
</warn> |
4557 |
|
4558 |
</body> |
4559 |
</subsection> |
4560 |
</section> |
4561 |
|
4562 |
<section> |
4563 |
<title>Network Mounts</title> |
4564 |
<subsection> |
4565 |
<title>Optional: Define network mounts</title> |
4566 |
<body> |
4567 |
|
4568 |
<p> |
4569 |
This screen lets you set up and use any existing network mounts during and after |
4570 |
installation. Click <c>New</c> to begin configuration. At this time, only NFS is |
4571 |
supported. |
4572 |
</p> |
4573 |
|
4574 |
</body> |
4575 |
</subsection> |
4576 |
</section> |
4577 |
|
4578 |
<section> |
4579 |
<title>make.conf</title> |
4580 |
<subsection> |
4581 |
<title>USE flags</title> |
4582 |
<body> |
4583 |
|
4584 |
<p> |
4585 |
Since you are performing a GRP/networkless install, you will not be allowed |
4586 |
to select USE flags before installation. However, you are free to set your own |
4587 |
USE flags in <path>/etc/make.conf</path> after you have rebooted into your |
4588 |
finished system. |
4589 |
</p> |
4590 |
|
4591 |
</body> |
4592 |
</subsection> |
4593 |
<subsection> |
4594 |
<title>CFLAGS</title> |
4595 |
<body> |
4596 |
|
4597 |
<p> |
4598 |
You should, however, select your processor type in the <e>CFLAGS</e> section along |
4599 |
with any custom optimizations you may want, such as <c>-O2</c> and |
4600 |
<c>-pipe</c>. |
4601 |
</p> |
4602 |
|
4603 |
</body> |
4604 |
</subsection> |
4605 |
<subsection> |
4606 |
<title>Other</title> |
4607 |
<body> |
4608 |
|
4609 |
<p> |
4610 |
Any other options you wish to set for future use should be selected now. |
4611 |
<e>Build binary packages</e> creates ready-to-install binary tarballs of all |
4612 |
packages you compile on your system. <e>DistCC</e> allows you to share the |
4613 |
burden of compiling with another computer via your network connection. |
4614 |
</p> |
4615 |
|
4616 |
<p> |
4617 |
You will not be allowed to change your <e>CHOST</e>, as this can seriously damage |
4618 |
your installation. In <e>MAKEOPTS</e> you define how many parallel compilations |
4619 |
should occur when you install a package. A good choice is the number of CPUs |
4620 |
in your system plus one, but this guideline isn't always perfect. On a |
4621 |
uniprocessor system, <c>-j2</c> might be used. |
4622 |
</p> |
4623 |
|
4624 |
</body> |
4625 |
</subsection> |
4626 |
</section> |
4627 |
|
4628 |
<section> |
4629 |
<title>Timezone</title> |
4630 |
<subsection> |
4631 |
<title>Choose your timezone</title> |
4632 |
<body> |
4633 |
|
4634 |
<p> |
4635 |
Study the map and select the region closest to your actual location. Later, |
4636 |
you will be asked to select if you want your clock to be set to UTC or local |
4637 |
time. |
4638 |
</p> |
4639 |
|
4640 |
</body> |
4641 |
</subsection> |
4642 |
</section> |
4643 |
|
4644 |
<section> |
4645 |
<title>Kernel Sources</title> |
4646 |
<subsection> |
4647 |
<title>Using the LiveCD kernel</title> |
4648 |
<body> |
4649 |
|
4650 |
<p> |
4651 |
You must use the kernel present on the LiveCD for the GRP/networkless install. |
4652 |
This is merely a <c>gentoo-sources</c> kernel compiled by <c>genkernel</c>, |
4653 |
Gentoo's automated kernel compilation utility and will give you a kernel that |
4654 |
automatically detects and configures your hardware upon boot. |
4655 |
</p> |
4656 |
|
4657 |
</body> |
4658 |
</subsection> |
4659 |
</section> |
4660 |
|
4661 |
<section> |
4662 |
<title>Networking</title> |
4663 |
<subsection> |
4664 |
<title>Device information</title> |
4665 |
<body> |
4666 |
|
4667 |
<p> |
4668 |
On this screen, you will be able to configure the various network interface |
4669 |
devices on your computer. Read the available options carefully. |
4670 |
</p> |
4671 |
|
4672 |
<p> |
4673 |
On the <e>Hostname/Proxy Information/Other</e> tab, you will need to choose a |
4674 |
hostname for your machine. You may also specify proxy server and DNS settings |
4675 |
if needed. |
4676 |
</p> |
4677 |
|
4678 |
</body> |
4679 |
</subsection> |
4680 |
</section> |
4681 |
|
4682 |
<section> |
4683 |
<title>Daemons</title> |
4684 |
<subsection> |
4685 |
<title>Cron daemon</title> |
4686 |
<body> |
4687 |
|
4688 |
<p> |
4689 |
Cron daemons are helpful programs that run tasks at scheduled times. While you |
4690 |
do not <e>need</e> to install one, they can be quite useful. Since this is a |
4691 |
Networkless installation, you are limited to <c>vixie-cron</c> or no cron |
4692 |
daemon. |
4693 |
</p> |
4694 |
|
4695 |
</body> |
4696 |
</subsection> |
4697 |
<subsection> |
4698 |
<title>System logger</title> |
4699 |
<body> |
4700 |
|
4701 |
<p> |
4702 |
A system logger is a necessity for any Linux operating system. Since this is a |
4703 |
Networkless installation, you are limited to <c>syslog-ng</c> or no logger. |
4704 |
</p> |
4705 |
|
4706 |
</body> |
4707 |
</subsection> |
4708 |
</section> |
4709 |
|
4710 |
|
4711 |
<section> |
4712 |
<title>Bootloader</title> |
4713 |
<subsection> |
4714 |
<body> |
4715 |
|
4716 |
<p> |
4717 |
This screen allows to you choose your bootloader and, optionally, specify |
4718 |
additional kernel parameters that will be used at bootup. Since this is a |
4719 |
Networkless installation, you are limited to <c>grub</c> or no bootloader. |
4720 |
</p> |
4721 |
|
4722 |
<p> |
4723 |
You may specify which disk to boot from by choosing the appropriate option |
4724 |
from <e>Boot Drive</e>. In Linux, the first IDE disk in your system is called |
4725 |
<c>hda</c>, the second IDE disk is <c>hdb</c>, and so on. If you have SATA or |
4726 |
SCSI disks, they will be called <c>sda</c>, <c>sdb</c>, etc. Please make the |
4727 |
correct selection for your system. |
4728 |
</p> |
4729 |
<!-- more bootloader inclusions needed about vga, etc. just don't include pure |
4730 |
CLI stuff, but only what can go on the extra kernel params line --> |
4731 |
<p> |
4732 |
If you need to pass any additional options to the kernel, such as video and/or |
4733 |
VGA statements, simply add them to the "Extra kernel parameters" section. |
4734 |
</p> |
4735 |
|
4736 |
<p> |
4737 |
If you jumpered your harddrive because the BIOS can't handle large harddrives |
4738 |
you'll need to append <c>hdx=stroke</c>. If you have SCSI devices, you should |
4739 |
add <c>doscsi</c> as a kernel option. |
4740 |
</p> |
4741 |
|
4742 |
<!-- do we need to cover all the stuff about lilo/grub and kernel parameter |
4743 |
lines and/or block devices here? --> |
4744 |
|
4745 |
</body> |
4746 |
</subsection> |
4747 |
</section> |
4748 |
|
4749 |
<section> |
4750 |
<title>Users</title> |
4751 |
<subsection> |
4752 |
<title>Adding users and groups</title> |
4753 |
<body> |
4754 |
|
4755 |
<p> |
4756 |
First set the root password for the system administrator (the <e>root</e> |
4757 |
user). |
4758 |
</p> |
4759 |
|
4760 |
<p> |
4761 |
We <e>strongly</e> recommend that you create a regular user for daily work. |
4762 |
Working as root all the time is <e>dangerous</e> and should be avoided! Create |
4763 |
your users, add them to the appropriate groups, and set their passwords. You |
4764 |
can optionally change their home directories, select their login shell, and |
4765 |
set helpful comments. |
4766 |
</p> |
4767 |
|
4768 |
</body> |
4769 |
</subsection> |
4770 |
</section> |
4771 |
|
4772 |
<section> |
4773 |
<title>Extra Packages</title> |
4774 |
<subsection> |
4775 |
<title>Optional: installing extra packages</title> |
4776 |
<body> |
4777 |
|
4778 |
<p> |
4779 |
The LiveCD contains a number of available pre-built packages. If you wish to |
4780 |
install any of them, check the appropriate box. |
4781 |
</p> |
4782 |
|
4783 |
</body> |
4784 |
</subsection> |
4785 |
</section> |
4786 |
|
4787 |
<section> |
4788 |
<title>Startup Services</title> |
4789 |
<subsection> |
4790 |
<body> |
4791 |
|
4792 |
<p> |
4793 |
This screen allows you to choose various services to load at system boot. |
4794 |
Study the available options and their descriptions carefully, and then select |
4795 |
your desired services. For example, if you have chosen to install |
4796 |
<c>xorg-x11</c> and want to boot straight into a graphical desktop, then you |
4797 |
would select "xdm" from the list. |
4798 |
</p> |
4799 |
|
4800 |
</body> |
4801 |
</subsection> |
4802 |
</section> |
4803 |
|
4804 |
<section> |
4805 |
<title>Other Settings</title> |
4806 |
<subsection> |
4807 |
<title>Miscellaneous options</title> |
4808 |
<body> |
4809 |
|
4810 |
<p> |
4811 |
Now you will be able to change various settings, including keyboard layout, |
4812 |
graphical display manager, the default editor, and whether to set your |
4813 |
hardware clock to UTC or local time. |
4814 |
</p> |
4815 |
|
4816 |
</body> |
4817 |
</subsection> |
4818 |
</section> |
4819 |
|
4820 |
<section> |
4821 |
<title>Finishing Up</title> |
4822 |
<subsection> |
4823 |
<body> |
4824 |
|
4825 |
<p> |
4826 |
At this point, you're done. You can reboot into your new Gentoo system at any |
4827 |
time. |
4828 |
</p> |
4829 |
|
4830 |
<p> |
4831 |
Congratulations, your system is now fully equipped! Continue with <uri |
4832 |
link="?part=1&chap=5">Where to go from here?</uri> to learn more about |
4833 |
Gentoo. |
4834 |
</p> |
4835 |
|
4836 |
</body> |
4837 |
</subsection> |
4838 |
</section> |
4839 |
</sections> |
4840 |
|
4841 |
|
4842 |
|
4843 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-hppa-bootloader.xml |
4844 |
|
4845 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-hppa-bootloader.xml?rev=1.1&view=markup |
4846 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-hppa-bootloader.xml?rev=1.1&content-type=text/plain |
4847 |
|
4848 |
Index: hb-install-hppa-bootloader.xml |
4849 |
=================================================================== |
4850 |
<?xml version='1.0' encoding='UTF-8'?> |
4851 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
4852 |
|
4853 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
4854 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
4855 |
|
4856 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-hppa-bootloader.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
4857 |
|
4858 |
<sections> |
4859 |
|
4860 |
<version>8.0</version> |
4861 |
<date>2007-05-07</date> |
4862 |
|
4863 |
<section> |
4864 |
<title>Installing PALO</title> |
4865 |
<body> |
4866 |
|
4867 |
<p> |
4868 |
On the PA-RISC platform, the boot loader is called palo. You can find the |
4869 |
configuration file in <path>/etc/palo.conf</path>. Here is a sample |
4870 |
configuration: |
4871 |
</p> |
4872 |
|
4873 |
<pre caption = "/etc/palo.conf example"> |
4874 |
--commandline=2/<keyval id="kernel-name"/> root=/dev/sda4 |
4875 |
--recoverykernel=/vmlinux.old |
4876 |
--init-partitioned=/dev/sda |
4877 |
</pre> |
4878 |
|
4879 |
<p> |
4880 |
The first line tells palo the location of the kernel and which boot parameters |
4881 |
it must use. <c>2/<keyval id="kernel-name"/></c> means the kernel named |
4882 |
<c><keyval id="kernel-name"/></c> resides on the second partition. Beware, the |
4883 |
path to the kernel is relative to the partition, not to the root of your |
4884 |
filesystem. |
4885 |
</p> |
4886 |
|
4887 |
<p> |
4888 |
The second line indicates which recovery kernel to use. If it is your |
4889 |
first install and you do not have a recovery kernel, please comment this |
4890 |
out. The third line indicates on which disk palo will reside. |
4891 |
</p> |
4892 |
|
4893 |
<p> |
4894 |
When configuration is done, just run <c>palo</c>. |
4895 |
</p> |
4896 |
|
4897 |
<pre caption = "Applying the PALO configuration"> |
4898 |
# <i>palo</i> |
4899 |
</pre> |
4900 |
|
4901 |
<p> |
4902 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
4903 |
</p> |
4904 |
|
4905 |
</body> |
4906 |
</section> |
4907 |
<section id="reboot"> |
4908 |
<title>Rebooting the System</title> |
4909 |
<subsection> |
4910 |
<body> |
4911 |
|
4912 |
<p> |
4913 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
4914 |
that one magical command you have been waiting for: <c>reboot</c>. |
4915 |
</p> |
4916 |
|
4917 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
4918 |
# <i>exit</i> |
4919 |
cdimage ~# <i>cd</i> |
4920 |
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
4921 |
cdimage ~# <i>reboot</i> |
4922 |
</pre> |
4923 |
|
4924 |
<p> |
4925 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
4926 |
booted again instead of your new Gentoo system. |
4927 |
</p> |
4928 |
|
4929 |
<p> |
4930 |
Once rebooted in your Gentoo installation, finish up with <uri |
4931 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
4932 |
</p> |
4933 |
|
4934 |
</body> |
4935 |
</subsection> |
4936 |
</section> |
4937 |
</sections> |
4938 |
|
4939 |
|
4940 |
|
4941 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-hppa-disk.xml |
4942 |
|
4943 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-hppa-disk.xml?rev=1.1&view=markup |
4944 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-hppa-disk.xml?rev=1.1&content-type=text/plain |
4945 |
|
4946 |
Index: hb-install-hppa-disk.xml |
4947 |
=================================================================== |
4948 |
<?xml version='1.0' encoding='UTF-8'?> |
4949 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
4950 |
|
4951 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
4952 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
4953 |
|
4954 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-hppa-disk.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
4955 |
|
4956 |
<sections> |
4957 |
|
4958 |
<version>8.1</version> |
4959 |
<date>2007-06-26</date> |
4960 |
|
4961 |
<section> |
4962 |
<title>Introduction to Block Devices</title> |
4963 |
<subsection> |
4964 |
<title>Block Devices</title> |
4965 |
<body> |
4966 |
|
4967 |
<p> |
4968 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
4969 |
and Linux in general, including Linux filesystems, partitions and block devices. |
4970 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
4971 |
you'll be guided through the process of setting up partitions and filesystems |
4972 |
for your Gentoo Linux installation. |
4973 |
</p> |
4974 |
|
4975 |
<p> |
4976 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
4977 |
probably the one that represents the first SCSI HD in a Linux system, namely |
4978 |
<path>/dev/sda</path>. |
4979 |
</p> |
4980 |
|
4981 |
<p> |
4982 |
The block devices above represent an abstract interface to the disk. User |
4983 |
programs can use these block devices to interact with your disk without worrying |
4984 |
about whether your drives are IDE, SCSI or something else. The program can |
4985 |
simply address the storage on the disk as a bunch of contiguous, |
4986 |
randomly-accessible 512-byte blocks. |
4987 |
</p> |
4988 |
|
4989 |
</body> |
4990 |
</subsection> |
4991 |
<subsection> |
4992 |
<title>Partitions and Slices</title> |
4993 |
<body> |
4994 |
|
4995 |
<p> |
4996 |
Although it is theoretically possible to use a full disk to house your Linux |
4997 |
system, this is almost never done in practice. Instead, full disk block devices |
4998 |
are split up in smaller, more manageable block devices. On most systems, |
4999 |
these are called <e>partitions</e>. Other architectures use a similar technique, |
5000 |
called <e>slices</e>. |
5001 |
</p> |
5002 |
|
5003 |
</body> |
5004 |
</subsection> |
5005 |
</section> |
5006 |
<section> |
5007 |
<title>Designing a Partitioning Scheme</title> |
5008 |
<subsection> |
5009 |
<title>How Many and How Big?</title> |
5010 |
<body> |
5011 |
|
5012 |
<p> |
5013 |
The number of partitions is highly dependent on your environment. For instance, |
5014 |
if you have lots of users, you will most likely want to have your |
5015 |
<path>/home</path> separate as it increases security and makes backups easier. |
5016 |
If you are installing Gentoo to perform as a mailserver, your |
5017 |
<path>/var</path> should be separate as all mails are stored inside |
5018 |
<path>/var</path>. A good choice of filesystem will then maximise your |
5019 |
performance. Gameservers will have a separate <path>/opt</path> as most gaming |
5020 |
servers are installed there. The reason is similar for <path>/home</path>: |
5021 |
security and backups. You will definitely want to keep <path>/usr</path> big: |
5022 |
not only will it contain the majority of applications, the Portage tree alone |
5023 |
takes around 500 Mbyte excluding the various sources that are stored in it. |
5024 |
</p> |
5025 |
|
5026 |
<p> |
5027 |
As you can see, it very much depends on what you want to achieve. Separate |
5028 |
partitions or volumes have the following advantages: |
5029 |
</p> |
5030 |
|
5031 |
<ul> |
5032 |
<li> |
5033 |
You can choose the best performing filesystem for each partition or volume |
5034 |
</li> |
5035 |
<li> |
5036 |
Your entire system cannot run out of free space if one defunct tool is |
5037 |
continuously writing files to a partition or volume |
5038 |
</li> |
5039 |
<li> |
5040 |
If necessary, file system checks are reduced in time, as multiple checks can |
5041 |
be done in parallel (although this advantage is more with multiple disks than |
5042 |
it is with multiple partitions) |
5043 |
</li> |
5044 |
<li> |
5045 |
Security can be enhanced by mounting some partitions or volumes read-only, |
5046 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
5047 |
</li> |
5048 |
</ul> |
5049 |
|
5050 |
<p> |
5051 |
However, multiple partitions have one big disadvantage: if not configured |
5052 |
properly, you might result in having a system with lots of free space on one |
5053 |
partition and none on another. There is also a 15-partition limit for SCSI and |
5054 |
SATA. |
5055 |
</p> |
5056 |
|
5057 |
</body> |
5058 |
</subsection> |
5059 |
</section> |
5060 |
<section> |
5061 |
<title>Using fdisk on HPPA to Partition your Disk</title> |
5062 |
<body> |
5063 |
|
5064 |
<p> |
5065 |
Use <c>fdisk</c> to create the partitions you want: |
5066 |
</p> |
5067 |
|
5068 |
<pre caption="Partitioning the disk"> |
5069 |
# <i>fdisk /dev/sda</i> |
5070 |
</pre> |
5071 |
|
5072 |
<p> |
5073 |
HPPA machines use the PC standard DOS partition tables. To create a new |
5074 |
DOS partition table, simply use the <c>o</c> command. |
5075 |
</p> |
5076 |
|
5077 |
<pre caption="Creating a DOS partition table"> |
5078 |
# <i>fdisk /dev/sda</i> |
5079 |
|
5080 |
Command (m for help): <i>o</i> |
5081 |
Building a new DOS disklabel. |
5082 |
</pre> |
5083 |
|
5084 |
<p> |
5085 |
PALO (the HPPA bootloader) needs a special partition to work. You have |
5086 |
to create a partition of at least 16MB at the beginning of your disk. |
5087 |
The partition type must be of type <e>f0</e> (Linux/PA-RISC boot). |
5088 |
</p> |
5089 |
|
5090 |
<impo> |
5091 |
If you ignore this and continue without a special PALO partition, your system |
5092 |
will stop loving you and fail to start. Also, if your disk is larger than 2GB, |
5093 |
make sure that the boot partition is in the first 2GB of your disk. PALO is |
5094 |
unable to read a kernel after the 2GB limit. |
5095 |
</impo> |
5096 |
|
5097 |
<pre caption="A simple default partition schema"> |
5098 |
# <i>cat /etc/fstab</i> |
5099 |
/dev/sda2 /boot ext3 noauto,noatime 1 1 |
5100 |
/dev/sda3 none swap sw 0 0 |
5101 |
/dev/sda4 / ext3 noatime 0 0 |
5102 |
|
5103 |
# <i>fdisk /dev/sda</i> |
5104 |
|
5105 |
Command (m for help): <i>p</i> |
5106 |
|
5107 |
Disk /dev/sda: 4294 MB, 4294816768 bytes |
5108 |
133 heads, 62 sectors/track, 1017 cylinders |
5109 |
Units = cylinders of 8246 * 512 = 4221952 bytes |
5110 |
|
5111 |
Device Boot Start End Blocks Id System |
5112 |
/dev/sda1 1 8 32953 f0 Linux/PA-RISC boot |
5113 |
/dev/sda2 9 20 49476 83 Linux |
5114 |
/dev/sda3 21 70 206150 82 Linux swap |
5115 |
/dev/sda4 71 1017 3904481 83 Linux |
5116 |
</pre> |
5117 |
|
5118 |
<p> |
5119 |
Now that your partitions are created, you can now continue with <uri |
5120 |
link="#filesystems">Creating Filesystems</uri>. |
5121 |
</p> |
5122 |
|
5123 |
</body> |
5124 |
</section> |
5125 |
<section id="filesystems"> |
5126 |
<title>Creating Filesystems</title> |
5127 |
<subsection> |
5128 |
<title>Introduction</title> |
5129 |
<body> |
5130 |
|
5131 |
<p> |
5132 |
Now that your partitions are created, it is time to place a filesystem on them. |
5133 |
If you don't care about what filesystem to choose and are happy with what we use |
5134 |
as default in this handbook, continue with <uri |
5135 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
5136 |
Otherwise read on to learn about the available filesystems... |
5137 |
</p> |
5138 |
|
5139 |
</body> |
5140 |
</subsection> |
5141 |
<subsection> |
5142 |
<title>Filesystems?</title> |
5143 |
<body> |
5144 |
|
5145 |
<p> |
5146 |
Several filesystems are available. Ext2, ext3, XFS and reiserfs are found stable |
5147 |
on the HPPA architecture. The others are very experimental. |
5148 |
</p> |
5149 |
|
5150 |
<p> |
5151 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
5152 |
journaling, which means that routine ext2 filesystem checks at startup time can |
5153 |
be quite time-consuming. There is now quite a selection of newer-generation |
5154 |
journaled filesystems that can be checked for consistency very quickly and are |
5155 |
thus generally preferred over their non-journaled counterparts. Journaled |
5156 |
filesystems prevent long delays when you boot your system and your filesystem |
5157 |
happens to be in an inconsistent state. |
5158 |
</p> |
5159 |
|
5160 |
<p> |
5161 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
5162 |
journaling for fast recovery in addition to other enhanced journaling modes like |
5163 |
full data and ordered data journaling. It uses an HTree index that enables high |
5164 |
performance in almost all situations. In short, ext3 is a very good and reliable |
5165 |
filesystem. |
5166 |
</p> |
5167 |
|
5168 |
<p> |
5169 |
<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall |
5170 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
5171 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
5172 |
extremely well and has metadata journaling. ReiserFS is solid and usable as |
5173 |
both general-purpose filesystem and for extreme cases such as the creation of |
5174 |
large filesystems, very large files and directories containing tens of |
5175 |
thousands of small files. |
5176 |
</p> |
5177 |
|
5178 |
<p> |
5179 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
5180 |
feature-set and is optimized for scalability. We only recommend using this |
5181 |
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
5182 |
an uninterruptible power supply. Because XFS aggressively caches in-transit data |
5183 |
in RAM, improperly designed programs (those that don't take proper precautions |
5184 |
when writing files to disk and there are quite a few of them) can lose a good |
5185 |
deal of data if the system goes down unexpectedly. |
5186 |
</p> |
5187 |
|
5188 |
<p> |
5189 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
5190 |
become production-ready and there hasn't been a sufficient track record to |
5191 |
comment positively nor negatively on its general stability at this point. |
5192 |
</p> |
5193 |
|
5194 |
</body> |
5195 |
</subsection> |
5196 |
<subsection id="filesystems-apply"> |
5197 |
<title>Applying a Filesystem to a Partition</title> |
5198 |
<body> |
5199 |
|
5200 |
<p> |
5201 |
To create a filesystem on a partition or volume, there are tools available for |
5202 |
each possible filesystem: |
5203 |
</p> |
5204 |
|
5205 |
<table> |
5206 |
<tr> |
5207 |
<th>Filesystem</th> |
5208 |
<th>Creation Command</th> |
5209 |
</tr> |
5210 |
<tr> |
5211 |
<ti>ext2</ti> |
5212 |
<ti><c>mke2fs</c></ti> |
5213 |
</tr> |
5214 |
<tr> |
5215 |
<ti>ext3</ti> |
5216 |
<ti><c>mke2fs -j</c></ti> |
5217 |
</tr> |
5218 |
<tr> |
5219 |
<ti>reiserfs</ti> |
5220 |
<ti><c>mkreiserfs</c></ti> |
5221 |
</tr> |
5222 |
<tr> |
5223 |
<ti>xfs</ti> |
5224 |
<ti><c>mkfs.xfs</c></ti> |
5225 |
</tr> |
5226 |
<tr> |
5227 |
<ti>jfs</ti> |
5228 |
<ti><c>mkfs.jfs</c></ti> |
5229 |
</tr> |
5230 |
</table> |
5231 |
|
5232 |
<p> |
5233 |
For instance, to have the boot partition (<path>/dev/sda2</path> in our |
5234 |
example) in ext2 and the root partition (<path>/dev/sda4</path> in our example) |
5235 |
in ext3 (as in our example), you would use: |
5236 |
</p> |
5237 |
|
5238 |
<pre caption="Applying a filesystem on a partition"> |
5239 |
# <i>mke2fs /dev/sda2</i> |
5240 |
# <i>mke2fs -j /dev/sda4</i> |
5241 |
</pre> |
5242 |
|
5243 |
<p> |
5244 |
Now create the filesystems on your newly created partitions (or logical |
5245 |
volumes). |
5246 |
</p> |
5247 |
|
5248 |
</body> |
5249 |
</subsection> |
5250 |
<subsection> |
5251 |
<title>Activating the Swap Partition</title> |
5252 |
<body> |
5253 |
|
5254 |
<p> |
5255 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
5256 |
</p> |
5257 |
|
5258 |
<pre caption="Creating a Swap signature"> |
5259 |
# <i>mkswap /dev/sda3</i> |
5260 |
</pre> |
5261 |
|
5262 |
<p> |
5263 |
To activate the swap partition, use <c>swapon</c>: |
5264 |
</p> |
5265 |
|
5266 |
<pre caption="Activating the swap partition"> |
5267 |
# <i>swapon /dev/sda3</i> |
5268 |
</pre> |
5269 |
|
5270 |
<p> |
5271 |
Create and activate the swap now. |
5272 |
</p> |
5273 |
|
5274 |
</body> |
5275 |
</subsection> |
5276 |
</section> |
5277 |
<section> |
5278 |
<title>Mounting</title> |
5279 |
<subsection> |
5280 |
<body> |
5281 |
|
5282 |
<p> |
5283 |
Now that your partitions are initialized and are housing a filesystem, it is |
5284 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
5285 |
create the necessary mount directories for every partition you created. As an |
5286 |
example we mount the root and boot partition: |
5287 |
</p> |
5288 |
|
5289 |
<pre caption="Mounting partitions"> |
5290 |
# <i>mount /dev/sda4 /mnt/gentoo</i> |
5291 |
# <i>mkdir /mnt/gentoo/boot</i> |
5292 |
# <i>mount /dev/sda2 /mnt/gentoo/boot</i> |
5293 |
</pre> |
5294 |
|
5295 |
<note> |
5296 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
5297 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
5298 |
also holds for <path>/var/tmp</path>. |
5299 |
</note> |
5300 |
|
5301 |
<p> |
5302 |
We will also have to mount the proc filesystem (a virtual interface with the |
5303 |
kernel) on <path>/proc</path>. But first we will need to place our files on the |
5304 |
partitions. |
5305 |
</p> |
5306 |
|
5307 |
<p> |
5308 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
5309 |
Installation Files</uri>. |
5310 |
</p> |
5311 |
|
5312 |
</body> |
5313 |
</subsection> |
5314 |
</section> |
5315 |
</sections> |
5316 |
|
5317 |
|
5318 |
|
5319 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-hppa-kernel.xml |
5320 |
|
5321 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-hppa-kernel.xml?rev=1.1&view=markup |
5322 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-hppa-kernel.xml?rev=1.1&content-type=text/plain |
5323 |
|
5324 |
Index: hb-install-hppa-kernel.xml |
5325 |
=================================================================== |
5326 |
<?xml version='1.0' encoding='UTF-8'?> |
5327 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
5328 |
|
5329 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
5330 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
5331 |
|
5332 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-hppa-kernel.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
5333 |
|
5334 |
<sections> |
5335 |
|
5336 |
<version>8.2</version> |
5337 |
<date>2007-07-29</date> |
5338 |
|
5339 |
<section> |
5340 |
<title>Timezone</title> |
5341 |
<body> |
5342 |
|
5343 |
<p> |
5344 |
You first need to select your timezone so that your system knows where it is |
5345 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
5346 |
it to <path>/etc/localtime</path>. Please avoid the |
5347 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
5348 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact |
5349 |
GMT+8. |
5350 |
</p> |
5351 |
|
5352 |
<pre caption="Setting the timezone information"> |
5353 |
# <i>ls /usr/share/zoneinfo</i> |
5354 |
<comment>(Suppose you want to use GMT)</comment> |
5355 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
5356 |
</pre> |
5357 |
|
5358 |
</body> |
5359 |
</section> |
5360 |
<section> |
5361 |
<title>Installing the Sources</title> |
5362 |
<subsection> |
5363 |
<title>Choosing a Kernel</title> |
5364 |
<body> |
5365 |
|
5366 |
<p> |
5367 |
The core around which all distributions are built is the Linux kernel. It is the |
5368 |
layer between the user programs and your system hardware. Gentoo provides its |
5369 |
users several possible kernel sources. A full listing with description is |
5370 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
5371 |
Guide</uri>. |
5372 |
</p> |
5373 |
|
5374 |
<p> |
5375 |
For HPPA we have <c>hppa-sources</c>. By default these sources are based on the |
5376 |
2.6 kernel sources. |
5377 |
</p> |
5378 |
|
5379 |
<pre caption="Installing a kernel source"> |
5380 |
# <i>emerge hppa-sources</i> |
5381 |
</pre> |
5382 |
|
5383 |
<p> |
5384 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
5385 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
5386 |
kernel source points to <c>hppa-sources-<keyval id="kernel-version"/></c>. Your |
5387 |
version may be different, so keep this in mind. |
5388 |
</p> |
5389 |
|
5390 |
<pre caption="Viewing the kernel source symlink"> |
5391 |
# <i>ls -l /usr/src/linux</i> |
5392 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-<keyval id="kernel-version"/> |
5393 |
</pre> |
5394 |
|
5395 |
<p> |
5396 |
Now it is time to configure and compile your kernel source. All architectures |
5397 |
can use <c>genkernel</c> for this, which will build a generic kernel as used |
5398 |
by the Installation CD. We explain the "manual" configuration first though, as |
5399 |
it is the best way to optimize your environment. |
5400 |
</p> |
5401 |
|
5402 |
<p> |
5403 |
If you want to manually configure your kernel, continue now with <uri |
5404 |
link="#manual">Default: Manual Configuration</uri>. If you want to use |
5405 |
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
5406 |
genkernel</uri> instead. |
5407 |
</p> |
5408 |
|
5409 |
</body> |
5410 |
</subsection> |
5411 |
</section> |
5412 |
<section id="manual"> |
5413 |
<title>Default: Manual Configuration</title> |
5414 |
<subsection> |
5415 |
<title>Introduction</title> |
5416 |
<body> |
5417 |
|
5418 |
<p> |
5419 |
Manually configuring a kernel is often seen as the most difficult procedure a |
5420 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
5421 |
couple of kernels you don't even remember that it was difficult ;) |
5422 |
</p> |
5423 |
|
5424 |
<p> |
5425 |
However, one thing <e>is</e> true: you must know your system when you start |
5426 |
configuring a kernel manually. Most information can be gathered by emerging |
5427 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
5428 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
5429 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
5430 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
5431 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
5432 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
5433 |
uses (it might provide you with a nice hint on what to enable). |
5434 |
</p> |
5435 |
|
5436 |
<p> |
5437 |
Now go to your kernel source directory and execute <c>make menuconfig</c>. This |
5438 |
will fire up an ncurses-based configuration menu. |
5439 |
</p> |
5440 |
|
5441 |
<pre caption="Invoking menuconfig"> |
5442 |
# <i>cd /usr/src/linux</i> |
5443 |
# <i>make menuconfig</i> |
5444 |
</pre> |
5445 |
|
5446 |
<p> |
5447 |
You will be greeted with several configuration sections. We'll first list some |
5448 |
options you must activate (otherwise Gentoo will not function, or not function |
5449 |
properly without additional tweaks). |
5450 |
</p> |
5451 |
|
5452 |
</body> |
5453 |
</subsection> |
5454 |
<subsection> |
5455 |
<title>Activating Required Options</title> |
5456 |
<body> |
5457 |
|
5458 |
<p> |
5459 |
First of all, activate the use of development and experimental code/drivers. |
5460 |
You need this, otherwise some very important code/drivers won't show up: |
5461 |
</p> |
5462 |
|
5463 |
<pre caption="Selecting experimental code/drivers"> |
5464 |
Code maturity level options ---> |
5465 |
[*] Prompt for development and/or incomplete code/drivers |
5466 |
General setup ---> |
5467 |
[*] Support for hot-pluggable devices |
5468 |
</pre> |
5469 |
|
5470 |
<p> |
5471 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
5472 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
5473 |
able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc |
5474 |
file system</c>. |
5475 |
</p> |
5476 |
|
5477 |
<pre caption="Selecting necessary file systems"> |
5478 |
File systems ---> |
5479 |
Pseudo Filesystems ---> |
5480 |
[*] /proc file system support |
5481 |
[*] Virtual memory file system support (former shm fs) |
5482 |
|
5483 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
5484 |
<*> Reiserfs support |
5485 |
<*> Ext3 journalling file system support |
5486 |
<*> JFS filesystem support |
5487 |
<*> Second extended fs support |
5488 |
<*> XFS filesystem support |
5489 |
</pre> |
5490 |
|
5491 |
<p> |
5492 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
5493 |
modem, you will need the following options in the kernel: |
5494 |
</p> |
5495 |
|
5496 |
<pre caption="Selecting PPPoE necessary drivers"> |
5497 |
Device Drivers ---> |
5498 |
Networking support ---> |
5499 |
<*> PPP (point-to-point protocol) support |
5500 |
<*> PPP support for async serial ports |
5501 |
<*> PPP support for sync tty ports |
5502 |
</pre> |
5503 |
|
5504 |
<p> |
5505 |
The two compression options won't harm but are not definitely needed, neither |
5506 |
does the <c>PPP over Ethernet</c> option, that might only be used by <c>ppp</c> |
5507 |
when configured to do kernel mode PPPoE. |
5508 |
</p> |
5509 |
|
5510 |
<p> |
5511 |
If you require it, don't forget to include support in the kernel for your |
5512 |
ethernet card. |
5513 |
</p> |
5514 |
|
5515 |
<p> |
5516 |
If you have a HIL mouse or keyboard, do not forget to compile in support for |
5517 |
them. |
5518 |
</p> |
5519 |
|
5520 |
<pre caption="Activating HIL support"> |
5521 |
Input core support ---> |
5522 |
[*] Keyboard support |
5523 |
[*] Mouse support |
5524 |
[*] Event interface support |
5525 |
</pre> |
5526 |
|
5527 |
<p> |
5528 |
If you have no mouse on your HIL port, only use the basic support: |
5529 |
</p> |
5530 |
|
5531 |
<pre caption="Basic HIL support"> |
5532 |
HIL support ---> |
5533 |
[*] HIL Keyboard (basic) support |
5534 |
</pre> |
5535 |
|
5536 |
<p> |
5537 |
If you however want <e>full</e> HIL support, select the following options: |
5538 |
</p> |
5539 |
|
5540 |
<pre caption="Full HIL support"> |
5541 |
HIL support ---> |
5542 |
[*] HP System Device Controller i8042 Support |
5543 |
[*] HIL MLC Support |
5544 |
[*] HIL Keyboard (full) support |
5545 |
[*] HIL Mouse & Pointer support |
5546 |
</pre> |
5547 |
|
5548 |
<p> |
5549 |
Also include display driver support: |
5550 |
</p> |
5551 |
|
5552 |
<pre caption="Display Driver support"> |
5553 |
Graphics support ---> |
5554 |
[*] Support for frame buffer devices |
5555 |
[*] HP STI frame buffer device support |
5556 |
Console display driver support ---> |
5557 |
[*] STI text console |
5558 |
</pre> |
5559 |
|
5560 |
<p> |
5561 |
When you're done configuring your kernel, continue with <uri |
5562 |
link="#compiling">Compiling and Installing</uri>. |
5563 |
</p> |
5564 |
|
5565 |
</body> |
5566 |
</subsection> |
5567 |
<subsection id="compiling"> |
5568 |
<title>Compiling and Installing</title> |
5569 |
<body> |
5570 |
|
5571 |
<impo> |
5572 |
If you want to compile a 64-bit kernel, you'll need to emerge <c>kgcc64</c> |
5573 |
<e>after</e> you've finished installing Gentoo and rebooted. However, running a |
5574 |
64-bit kernel is discouraged. You should only run a 64-bit kernel if you have |
5575 |
more than 4GB of RAM or if your server requires it, i.e. on the A500. |
5576 |
</impo> |
5577 |
|
5578 |
<p> |
5579 |
Now that your kernel is configured, it is time to compile and install it. Exit |
5580 |
the configuration and start the compilation process: |
5581 |
</p> |
5582 |
|
5583 |
<pre caption="Compiling the kernel"> |
5584 |
# <i>make && make modules_install</i> |
5585 |
</pre> |
5586 |
|
5587 |
<p> |
5588 |
When the kernel has finished compiling, copy the kernel image to |
5589 |
<path>/boot</path>. Use whatever name you feel is appropriate for your kernel |
5590 |
choice and remember it as you will need it later on when you configure your |
5591 |
bootloader. Remember to replace <path><kernel-version></path> with the |
5592 |
name and version of your kernel. |
5593 |
</p> |
5594 |
|
5595 |
<pre caption="Installing the kernel"> |
5596 |
# <i>cp vmlinux /boot/<kernel-version></i> |
5597 |
</pre> |
5598 |
|
5599 |
<p> |
5600 |
Now continue with <uri link="#kernel_modules">Configuring Kernel |
5601 |
Modules</uri>. |
5602 |
</p> |
5603 |
|
5604 |
</body> |
5605 |
</subsection> |
5606 |
</section> |
5607 |
<section id="genkernel"> |
5608 |
<title>Alternative: Using genkernel</title> |
5609 |
<body> |
5610 |
|
5611 |
<p> |
5612 |
If you are reading this section, you have chosen to use our <c>genkernel</c> |
5613 |
script to configure your kernel for you. |
5614 |
</p> |
5615 |
|
5616 |
<p> |
5617 |
Now that your kernel source tree is installed, it's now time to compile your |
5618 |
kernel by using our <c>genkernel</c> script to automatically build a kernel for |
5619 |
you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
5620 |
way our Installation CD kernel is configured. This means that when you use |
5621 |
<c>genkernel</c> to build your kernel, your system will generally detect all |
5622 |
your hardware at boot-time, just like our Installation CD does. Because |
5623 |
genkernel doesn't require any manual kernel configuration, it is an ideal |
5624 |
solution for those users who may not be comfortable compiling their own |
5625 |
kernels. |
5626 |
</p> |
5627 |
|
5628 |
<p> |
5629 |
Now, let's see how to use genkernel. First, emerge the genkernel ebuild: |
5630 |
</p> |
5631 |
|
5632 |
<pre caption="Emerging genkernel"> |
5633 |
# <i>emerge genkernel</i> |
5634 |
</pre> |
5635 |
|
5636 |
<p> |
5637 |
Now, compile your kernel sources by running <c>genkernel all</c>. |
5638 |
Be aware though, as <c>genkernel</c> compiles a kernel that supports almost all |
5639 |
hardware, this compilation will take quite a while to finish! |
5640 |
</p> |
5641 |
|
5642 |
<p> |
5643 |
Note that, if your boot partition doesn't use ext2 or ext3 as filesystem you |
5644 |
need to manually configure your kernel using <c>genkernel --menuconfig all</c> |
5645 |
and add support for your filesystem <e>in</e> the kernel (i.e. <e>not</e> as a |
5646 |
module). |
5647 |
</p> |
5648 |
|
5649 |
<pre caption="Running genkernel"> |
5650 |
# <i>genkernel all</i> |
5651 |
</pre> |
5652 |
|
5653 |
<p> |
5654 |
Once <c>genkernel</c> completes, a kernel, full set of modules and |
5655 |
<e>initial root disk</e> (initrd) will be created. We will use the kernel |
5656 |
and initrd when configuring a boot loader later in this document. Write |
5657 |
down the names of the kernel and initrd as you will need it when writing |
5658 |
the bootloader configuration file. The initrd will be started immediately after |
5659 |
booting to perform hardware autodetection (just like on the Installation CD) |
5660 |
before your "real" system starts up. |
5661 |
</p> |
5662 |
|
5663 |
<pre caption="Checking the created kernel image name and initrd"> |
5664 |
# <i>ls /boot/kernel* /boot/initramfs*</i> |
5665 |
</pre> |
5666 |
|
5667 |
</body> |
5668 |
</section> |
5669 |
<section id="kernel_modules"> |
5670 |
<title>Configuring Kernel Modules</title> |
5671 |
<subsection> |
5672 |
<title>Configuring the Modules</title> |
5673 |
<body> |
5674 |
|
5675 |
<p> |
5676 |
You should list the modules you want automatically loaded in |
5677 |
<path>/etc/modules.autoload.d/kernel-2.6</path>. |
5678 |
You can add extra options to the modules too if you want. |
5679 |
</p> |
5680 |
|
5681 |
<p> |
5682 |
To view all available modules, run the following command: |
5683 |
</p> |
5684 |
|
5685 |
<pre caption="Viewing all available modules"> |
5686 |
# <i>modprobe -l</i> |
5687 |
</pre> |
5688 |
|
5689 |
<p> |
5690 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
5691 |
<path>kernel-2.6</path> file and enter the module |
5692 |
name in it. |
5693 |
</p> |
5694 |
|
5695 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
5696 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
5697 |
</pre> |
5698 |
|
5699 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
5700 |
3c59x |
5701 |
</pre> |
5702 |
|
5703 |
<p> |
5704 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
5705 |
your System</uri>. |
5706 |
</p> |
5707 |
|
5708 |
</body> |
5709 |
</subsection> |
5710 |
</section> |
5711 |
</sections> |
5712 |
|
5713 |
|
5714 |
|
5715 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-hppa-medium.xml |
5716 |
|
5717 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-hppa-medium.xml?rev=1.1&view=markup |
5718 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-hppa-medium.xml?rev=1.1&content-type=text/plain |
5719 |
|
5720 |
Index: hb-install-hppa-medium.xml |
5721 |
=================================================================== |
5722 |
<?xml version='1.0' encoding='UTF-8'?> |
5723 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
5724 |
|
5725 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
5726 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
5727 |
|
5728 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-hppa-medium.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
5729 |
|
5730 |
<sections> |
5731 |
|
5732 |
<version>8.2</version> |
5733 |
<date>2007-06-29</date> |
5734 |
|
5735 |
<section> |
5736 |
<title>Hardware Requirements</title> |
5737 |
<subsection> |
5738 |
<title>Introduction</title> |
5739 |
<body> |
5740 |
|
5741 |
<p> |
5742 |
Before we start, we first list what hardware requirements you need to |
5743 |
successfully install Gentoo on your box. |
5744 |
</p> |
5745 |
|
5746 |
</body> |
5747 |
</subsection> |
5748 |
<subsection> |
5749 |
<title>Hardware Requirements</title> |
5750 |
<body> |
5751 |
|
5752 |
<p> |
5753 |
A list of supported hardware can be found on the <uri |
5754 |
link="http://www.pateam.org/list.html">PA Team website</uri>. You may find |
5755 |
additional information about your box in the <uri |
5756 |
link="http://hwdb.parisc-linux.org">Parisc-Linux Hardware Database</uri> and |
5757 |
the <uri link="http://www.openpa.net/cpu.html">processor list</uri> on |
5758 |
<uri link="http://www.openpa.net">www.openpa.net</uri>. |
5759 |
</p> |
5760 |
|
5761 |
<p> |
5762 |
If you don't know which version of PA-RISC your box is using, please check the |
5763 |
links above to find out whether you're using version 1.1 or 2.0. You will need |
5764 |
this information later on. |
5765 |
</p> |
5766 |
|
5767 |
<table> |
5768 |
<tr> |
5769 |
<th>Memory</th> |
5770 |
<ti>64 MB</ti> |
5771 |
</tr> |
5772 |
<tr> |
5773 |
<th>Diskspace</th> |
5774 |
<ti>1.5 GB (excluding swap space)</ti> |
5775 |
</tr> |
5776 |
<tr> |
5777 |
<th>Swap space</th> |
5778 |
<ti>At least 256 MB</ti> |
5779 |
</tr> |
5780 |
</table> |
5781 |
|
5782 |
</body> |
5783 |
</subsection> |
5784 |
</section> |
5785 |
<!-- Copy/paste from hb-install-x86-medium.xml --> |
5786 |
<!-- START --> |
5787 |
<section> |
5788 |
<title>The Gentoo Universal Installation CD</title> |
5789 |
<subsection> |
5790 |
<title>Introduction</title> |
5791 |
<body> |
5792 |
|
5793 |
<p> |
5794 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
5795 |
Such a tarball is an archive that contains a minimal environment from |
5796 |
which you can succesfully install Gentoo Linux onto your system. |
5797 |
</p> |
5798 |
|
5799 |
<p> |
5800 |
Installations using a stage1 or stage2 tarball file are not documented in the |
5801 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
5802 |
FAQ</uri> on these matters. |
5803 |
</p> |
5804 |
|
5805 |
</body> |
5806 |
</subsection> |
5807 |
<subsection> |
5808 |
<title>Gentoo Universal Installation CD</title> |
5809 |
<body> |
5810 |
|
5811 |
<p> |
5812 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
5813 |
environment. It allows you to boot Linux from the CD. During the boot process |
5814 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
5815 |
Installation CDs are maintained by Gentoo developers. |
5816 |
</p> |
5817 |
|
5818 |
<p> |
5819 |
There currently are two Installation CDs available: |
5820 |
</p> |
5821 |
|
5822 |
<ul> |
5823 |
<li> |
5824 |
The Universal Installation CD contains everything you need to install |
5825 |
Gentoo. It provides stage3 files for common architectures, source code |
5826 |
for the extra applications you need to choose from and, of course, the |
5827 |
installation instructions for your architecture. |
5828 |
</li> |
5829 |
<li> |
5830 |
The Minimal Installation CD contains only a minimal environment that allows |
5831 |
you to boot up and configure your network so you can connect to the |
5832 |
Internet. It does not contain any additional files and cannot be used |
5833 |
during the current installation approach. |
5834 |
</li> |
5835 |
</ul> |
5836 |
|
5837 |
</body> |
5838 |
</subsection> |
5839 |
</section> |
5840 |
<!-- STOP --> |
5841 |
<section> |
5842 |
<title>Download, Burn and Boot the Gentoo Universal Installation CD</title> |
5843 |
<subsection> |
5844 |
<title>Downloading and Burning the Installation CD</title> |
5845 |
<body> |
5846 |
|
5847 |
<p> |
5848 |
You can download the Universal Installation CD from one of our <uri |
5849 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CD is located in |
5850 |
the <path><keyval id="release-dir"/>installcd</path> directory. |
5851 |
</p> |
5852 |
|
5853 |
<p> |
5854 |
Inside those directories you'll find ISO-files. Those are full CD images which |
5855 |
you can write on a CD-R. |
5856 |
</p> |
5857 |
|
5858 |
<p> |
5859 |
After downloading the file, you can verify its integrity to see if it is |
5860 |
corrupted or not: |
5861 |
</p> |
5862 |
|
5863 |
<ul> |
5864 |
<li> |
5865 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
5866 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
5867 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows) |
5868 |
</li> |
5869 |
<li> |
5870 |
You can verify the cryptographic signature that we provide. You need to |
5871 |
obtain the public key we use (17072058) before you proceed though. |
5872 |
</li> |
5873 |
</ul> |
5874 |
|
5875 |
<p> |
5876 |
To fetch our public key using the GnuPG application, run the following command: |
5877 |
</p> |
5878 |
|
5879 |
<pre caption="Obtaining the public key"> |
5880 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
5881 |
</pre> |
5882 |
|
5883 |
<p> |
5884 |
Now verify the signature: |
5885 |
</p> |
5886 |
|
5887 |
<pre caption="Verify the cryptographic signature"> |
5888 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
5889 |
</pre> |
5890 |
|
5891 |
<p> |
5892 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
5893 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
5894 |
<c>K3B</c> here; more information can be found in our <uri |
5895 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
5896 |
</p> |
5897 |
|
5898 |
<ul> |
5899 |
<li> |
5900 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
5901 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
5902 |
path). |
5903 |
</li> |
5904 |
<li> |
5905 |
With K3B, select <c>Tools</c> > <c>Burn CD Image</c>. Then you can locate |
5906 |
your ISO file within the 'Image to Burn' area. Finally click <c>Start</c>. |
5907 |
</li> |
5908 |
</ul> |
5909 |
|
5910 |
</body> |
5911 |
</subsection> |
5912 |
<subsection> |
5913 |
<title>Booting the Universal Installation CD</title> |
5914 |
<body> |
5915 |
|
5916 |
<note> |
5917 |
If you have problems booting the Installation CD or any other media, please |
5918 |
read the <uri |
5919 |
link="http://www.tldp.org/HOWTO/PA-RISC-Linux-Boot-HOWTO/index.html"> |
5920 |
PA-RISC Linux Boot HOWTO</uri>. |
5921 |
</note> |
5922 |
|
5923 |
<p> |
5924 |
Boot your HPPA system. During the boot process, you will see a message similar |
5925 |
to the following: |
5926 |
</p> |
5927 |
|
5928 |
<pre caption="HPPA boot message"> |
5929 |
Searching for Potential Boot Devices. |
5930 |
To terminate search, press and hold the ESCAPE key. |
5931 |
</pre> |
5932 |
|
5933 |
<p> |
5934 |
When this message appears, press and hold the Esc-key until an option menu |
5935 |
appears. This can take a while, be patient. By default, you should enter the |
5936 |
BOOT_ADMIN console. If you receive an option menu, choose <c>Enter Boot |
5937 |
Administration mode</c> to enter the BOOT_ADMIN console. You should now have an |
5938 |
'>' prompt. |
5939 |
</p> |
5940 |
|
5941 |
<p> |
5942 |
Put the Gentoo Installation CD in the CD-ROM. If you do not know the SCSI ID of |
5943 |
your CD-ROM drive, your PA-RISC station will search for it when you issue the |
5944 |
<c>search</c> command. |
5945 |
</p> |
5946 |
|
5947 |
<pre caption="Searching for SCSI ID"> |
5948 |
> <i>search</i> |
5949 |
Searching for Devices with Bootable Media. |
5950 |
To terminate search, please press and hold the ESCAPE key. |
5951 |
</pre> |
5952 |
|
5953 |
<p> |
5954 |
Your PA-RISC station will now display all the available boot media. This is an |
5955 |
example result of this command: |
5956 |
</p> |
5957 |
|
5958 |
<pre caption="Available boot media"> |
5959 |
Device Selection Device Path Device Type and Utilities |
5960 |
--------------------------------------------------------------------------- |
5961 |
|
5962 |
P0 scsi.5.0 TOSHIBA CD-ROM XM-3301TA |
5963 |
IPL |
5964 |
P1 scsi.2.0 COMPAQ ST32550N |
5965 |
IPL |
5966 |
P2 lan.0010a7-06d1b6.3.6 server |
5967 |
IPL |
5968 |
</pre> |
5969 |
|
5970 |
<p> |
5971 |
To boot from a CD-ROM you need the accompanying Device Path. For instance, if we |
5972 |
want to boot from the TOSHIBA CD-ROM in the above example, we would need to type |
5973 |
the following command: |
5974 |
</p> |
5975 |
|
5976 |
<pre caption="Booting from a CD-ROM"> |
5977 |
> <i>boot scsi.5.0 ipl</i> |
5978 |
|
5979 |
Trying scsi.5.0 |
5980 |
</pre> |
5981 |
|
5982 |
<p> |
5983 |
The <c>ipl</c> keyword (Initial Program Loader) tells palo (the PA-RISC boot |
5984 |
LOader) to enter interactive mode. This will allow you to change, for example, |
5985 |
the kernel boot parameters. |
5986 |
</p> |
5987 |
|
5988 |
<p> |
5989 |
When the boot is successful, palo will start in interactive mode: |
5990 |
</p> |
5991 |
|
5992 |
<pre caption="PALO Interactive Mode"> |
5993 |
Boot path initialized. |
5994 |
Attempting to load IPL. |
5995 |
|
5996 |
|
5997 |
HARD Booted. |
5998 |
palo ipl 1.5 root@hope Sat Apr 23 18:06:47 CEST 2005 |
5999 |
|
6000 |
Boot image contains: |
6001 |
0/vmlinux32 6241293 bytes @ 0x3904000 |
6002 |
0/vmlinux64 8352719 bytes @ 0x3ef8000 |
6003 |
0/ramdisk 1007589 bytes @ 0x105800 |
6004 |
|
6005 |
Information: No console specified on kernel command line. This is normal. |
6006 |
PALO will choose the console currently used by firmware (serial).Current command line: |
6007 |
0/vmlinux initrd=initrd TERM=linux root=/dev/ram0 init=/linuxrc cdroot looptype=squashfs loop=/livecd.squashfs hda=scsi console=ttyS0 |
6008 |
0: 0/vmlinux |
6009 |
1: initrd=initrd |
6010 |
2: TERM=linux |
6011 |
3: root=/dev/ram0 |
6012 |
4: init=/linuxrc |
6013 |
5: cdroot |
6014 |
6: looptype=squashfs |
6015 |
7: loop=/livecd.squashfs |
6016 |
8: hda=scsi |
6017 |
9: console=ttyS0 |
6018 |
|
6019 |
<#> edit the numbered field |
6020 |
'b' boot with this command line |
6021 |
'r' restore command line |
6022 |
'l' list dir |
6023 |
</pre> |
6024 |
|
6025 |
<p> |
6026 |
These parameters are suitable for most situations. |
6027 |
</p> |
6028 |
|
6029 |
<p> |
6030 |
If you need extra features you must add the appropriate keyword(s) to the end of |
6031 |
the command line. To add a keyword, edit the last field, add a space and type |
6032 |
your keyword. The only implemented keywords as of now are <c>cdcache</c> which |
6033 |
tells the Installation CD to load itself into RAM, allowing you to unmount the |
6034 |
CD, and <c>noload=module1[,module2[,...]]</c> which allows you to explicitly |
6035 |
disable loading of particular modules. |
6036 |
</p> |
6037 |
|
6038 |
<pre caption="Adding hdb=scsi as boot option"> |
6039 |
(or 'b' to boot with this command line)? <i>9</i> |
6040 |
console=ttyS0 <i>hdb=scsi</i> |
6041 |
</pre> |
6042 |
|
6043 |
<p> |
6044 |
Now that you have tweaked your kernel boot params, boot it. |
6045 |
</p> |
6046 |
|
6047 |
<pre caption="Booting the kernel"> |
6048 |
(or 'b' to boot with this command line)? <i>b</i> |
6049 |
</pre> |
6050 |
|
6051 |
<p> |
6052 |
You should have a root ("#") prompt on the current console and can also switch |
6053 |
to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get back to the one you |
6054 |
started on by pressing Alt-F1. |
6055 |
</p> |
6056 |
|
6057 |
<p> |
6058 |
Now continue with <uri link="#hardware">Extra Hardware |
6059 |
Configuration</uri>. |
6060 |
</p> |
6061 |
|
6062 |
</body> |
6063 |
</subsection> |
6064 |
<subsection id="hardware"> |
6065 |
<title>Extra Hardware Configuration</title> |
6066 |
<body> |
6067 |
|
6068 |
<p> |
6069 |
Most hppa machines have an onboard ethernet card. Old ones use the lasi driver |
6070 |
which is compiled in the kernel. Newer ones need the tulip driver which is |
6071 |
compiled as a module. To use the latter, you need to load its driver. |
6072 |
</p> |
6073 |
|
6074 |
<p> |
6075 |
In the next example, we try to load the <c>tulip</c> module (support for |
6076 |
certain kinds of network interfaces): |
6077 |
</p> |
6078 |
|
6079 |
<pre caption="Loading kernel modules"> |
6080 |
# <i>modprobe tulip</i> |
6081 |
</pre> |
6082 |
|
6083 |
</body> |
6084 |
</subsection> |
6085 |
|
6086 |
<subsection id="useraccounts"> |
6087 |
<title>Optional: User Accounts</title> |
6088 |
<body> |
6089 |
|
6090 |
<p> |
6091 |
If you plan on giving other people access to your installation |
6092 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
6093 |
security reasons), you need to create the necessary user accounts and change |
6094 |
the root password. |
6095 |
</p> |
6096 |
|
6097 |
<p> |
6098 |
To change the root password, use the <c>passwd</c> utility: |
6099 |
</p> |
6100 |
|
6101 |
<pre caption="Changing the root password"> |
6102 |
# <i>passwd</i> |
6103 |
New password: <comment>(Enter your new password)</comment> |
6104 |
Re-enter password: <comment>(Re-enter your password)</comment> |
6105 |
</pre> |
6106 |
|
6107 |
<p> |
6108 |
To create a user account, we first enter their credentials, followed by |
6109 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
6110 |
In the next example, we create a user called "john". |
6111 |
</p> |
6112 |
|
6113 |
<pre caption="Creating a user account"> |
6114 |
# <i>useradd -m -G users john</i> |
6115 |
# <i>passwd john</i> |
6116 |
New password: <comment>(Enter john's password)</comment> |
6117 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
6118 |
</pre> |
6119 |
|
6120 |
<p> |
6121 |
You can change your user id from root to the newly created user by using |
6122 |
<c>su</c>: |
6123 |
</p> |
6124 |
|
6125 |
<pre caption="Changing user id"> |
6126 |
# <i>su - john</i> |
6127 |
</pre> |
6128 |
|
6129 |
</body> |
6130 |
</subsection> |
6131 |
<subsection> |
6132 |
<title>Optional: Viewing Documentation while Installing</title> |
6133 |
<body> |
6134 |
|
6135 |
<p> |
6136 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
6137 |
installation, make sure you have created a user account (see <uri |
6138 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
6139 |
go to a new terminal and log in. |
6140 |
</p> |
6141 |
|
6142 |
<p> |
6143 |
If you want to view the documentation on the CD you can immediately run |
6144 |
<c>links</c> to read it: |
6145 |
</p> |
6146 |
|
6147 |
<pre caption="Viewing the on-CD documentation"> |
6148 |
# <i>links /mnt/cdrom/docs/handbook/html/index.html</i> |
6149 |
</pre> |
6150 |
|
6151 |
<p> |
6152 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
6153 |
more recent than the one provided on the CD. You can view it using <c>links</c> |
6154 |
as well, but only after having completed the <e>Configuring your Network</e> |
6155 |
chapter (otherwise you won't be able to go on the Internet to view the |
6156 |
document): |
6157 |
</p> |
6158 |
|
6159 |
<pre caption="Viewing the Online Documentation"> |
6160 |
# <i>links http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i> |
6161 |
</pre> |
6162 |
|
6163 |
<p> |
6164 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
6165 |
</p> |
6166 |
|
6167 |
</body> |
6168 |
</subsection> |
6169 |
<subsection> |
6170 |
<title>Optional: Starting the SSH Daemon</title> |
6171 |
<body> |
6172 |
|
6173 |
<p> |
6174 |
If you want to allow other users to access your computer during the |
6175 |
Gentoo installation (perhaps because those users are going to help you |
6176 |
install Gentoo, or even do it for you), you need to create a user |
6177 |
account for them and perhaps even provide them with your root password |
6178 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
6179 |
</p> |
6180 |
|
6181 |
<p> |
6182 |
To fire up the SSH daemon, execute the following command: |
6183 |
</p> |
6184 |
|
6185 |
<pre caption="Starting the SSH daemon"> |
6186 |
# <i>/etc/init.d/sshd start</i> |
6187 |
</pre> |
6188 |
|
6189 |
<p> |
6190 |
To be able to use sshd, you first need to set up your networking. Continue with |
6191 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
6192 |
</p> |
6193 |
|
6194 |
</body> |
6195 |
</subsection> |
6196 |
</section> |
6197 |
</sections> |
6198 |
|
6199 |
|
6200 |
|
6201 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-network.xml |
6202 |
|
6203 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-network.xml?rev=1.1&view=markup |
6204 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-network.xml?rev=1.1&content-type=text/plain |
6205 |
|
6206 |
Index: hb-install-network.xml |
6207 |
=================================================================== |
6208 |
<?xml version='1.0' encoding='UTF-8'?> |
6209 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
6210 |
|
6211 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
6212 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
6213 |
|
6214 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-network.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
6215 |
|
6216 |
<sections> |
6217 |
|
6218 |
<version>8.0</version> |
6219 |
<date>2007-05-07</date> |
6220 |
|
6221 |
<section> |
6222 |
<title>Do you need Networking?</title> |
6223 |
<subsection> |
6224 |
<title>Who can do without?</title> |
6225 |
<body> |
6226 |
|
6227 |
<p> |
6228 |
Generally, you don't need a working network connection to install Gentoo using |
6229 |
either the Universal InstallCD or the Installer LiveCD. However, there are some |
6230 |
circumstances where you do want to have a working Internet connection: |
6231 |
</p> |
6232 |
|
6233 |
<ul> |
6234 |
<li> |
6235 |
The stage3 files that are stored in the Universal InstallCD do not |
6236 |
match your architecture and you need to download the correct stage3 file |
6237 |
</li> |
6238 |
<li> |
6239 |
The stage3 file that is generated by the Installer LiveCD does not |
6240 |
match your architecture and you need to download the correct stage3 file |
6241 |
</li> |
6242 |
<li> |
6243 |
You need to install a specific networking application that will allow you to |
6244 |
connect to the Internet which isn't available on the Universal InstallCD or |
6245 |
the Installer LiveCD, but is supported by the CD (i.e. you can connect to |
6246 |
the Internet using the CD but the necessary sources are not available on |
6247 |
the CD) |
6248 |
</li> |
6249 |
<li> |
6250 |
You want remote assistance during the installation (using SSH or through |
6251 |
direct conversations using IRC) |
6252 |
</li> |
6253 |
</ul> |
6254 |
|
6255 |
</body> |
6256 |
</subsection> |
6257 |
<subsection> |
6258 |
<title>Do I need Networking?</title> |
6259 |
<body> |
6260 |
|
6261 |
<p> |
6262 |
To find out if the stage3 file for your architecture is available and you are |
6263 |
using a Universal InstallCD, take a look inside <path>/mnt/cdrom/stages</path> |
6264 |
and check if one of the available stages matches your architecture. If not, you |
6265 |
can still opt for a stage3 file of an architecture compatible with yours. |
6266 |
</p> |
6267 |
|
6268 |
<p> |
6269 |
The stage3 file built by the x86 Installer LiveCD is optimized for i686 or |
6270 |
better and uses NPTL. The stage3 file built by the amd64 Installer LiveCD is |
6271 |
optimized for generic amd64 usage and uses NPTL. |
6272 |
</p> |
6273 |
|
6274 |
<p> |
6275 |
If you, on the other hand, want to use a stage3 file optimized for your |
6276 |
architecture and the stage3 file of your choice is not available, then you will |
6277 |
need networking to download the appropriate stage3 file. |
6278 |
</p> |
6279 |
|
6280 |
<p> |
6281 |
So, if you don't need networking, you can skip the rest of this chapter and |
6282 |
continue with <uri link="?part=1&chap=4">Preparing the Disks</uri>. |
6283 |
Otherwise, continue with the networking configuration sections below. |
6284 |
</p> |
6285 |
|
6286 |
</body> |
6287 |
</subsection> |
6288 |
</section> |
6289 |
<section> |
6290 |
<title>Automatic Network Detection</title> |
6291 |
<subsection> |
6292 |
<title>Maybe it just works?</title> |
6293 |
<body> |
6294 |
|
6295 |
<p> |
6296 |
If your system is plugged into an Ethernet network with a DHCP server, it is |
6297 |
very likely that your networking configuration has already been set up |
6298 |
automatically for you. If so, you should be able to take advantage of the many |
6299 |
included network-aware commands on the Installation CD such as <c>ssh</c>, |
6300 |
<c>scp</c>, <c>ping</c>, <c>irssi</c>, <c>wget</c> and <c>links</c>, among |
6301 |
others. |
6302 |
</p> |
6303 |
|
6304 |
<p> |
6305 |
If networking has been configured for you, the <c>/sbin/ifconfig</c> command |
6306 |
should list some network interfaces besides lo, such as eth0: |
6307 |
</p> |
6308 |
|
6309 |
<pre caption="/sbin/ifconfig for a working network configuration"> |
6310 |
# <i>/sbin/ifconfig</i> |
6311 |
<comment>(...)</comment> |
6312 |
eth0 Link encap:Ethernet HWaddr 00:50:BA:8F:61:7A |
6313 |
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 |
6314 |
inet6 addr: fe80::50:ba8f:617a/10 Scope:Link |
6315 |
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 |
6316 |
RX packets:1498792 errors:0 dropped:0 overruns:0 frame:0 |
6317 |
TX packets:1284980 errors:0 dropped:0 overruns:0 carrier:0 |
6318 |
collisions:1984 txqueuelen:100 |
6319 |
RX bytes:485691215 (463.1 Mb) TX bytes:123951388 (118.2 Mb) |
6320 |
Interrupt:11 Base address:0xe800 |
6321 |
</pre> |
6322 |
|
6323 |
</body> |
6324 |
</subsection> |
6325 |
<subsection> |
6326 |
<title>Optional: Configure any Proxies</title> |
6327 |
<body> |
6328 |
|
6329 |
<p> |
6330 |
If you access the Internet through a proxy, you might need to set up proxy |
6331 |
information during the installation. It is very easy to define a proxy: you just |
6332 |
need to define a variable which contains the proxy server information. |
6333 |
</p> |
6334 |
|
6335 |
<p> |
6336 |
In most cases, you can just define the variables using the server hostname. As |
6337 |
an example, we assume the proxy is called <c>proxy.gentoo.org</c> and the port |
6338 |
is <c>8080</c>. |
6339 |
</p> |
6340 |
|
6341 |
<pre caption="Defining proxy servers"> |
6342 |
<comment>(If the proxy filters HTTP traffic)</comment> |
6343 |
# <i>export http_proxy="http://proxy.gentoo.org:8080"</i> |
6344 |
<comment>(If the proxy filters FTP traffic)</comment> |
6345 |
# <i>export ftp_proxy="ftp://proxy.gentoo.org:8080"</i> |
6346 |
<comment>(If the proxy filters RSYNC traffic)</comment> |
6347 |
# <i>export RSYNC_PROXY="proxy.gentoo.org:8080"</i> |
6348 |
</pre> |
6349 |
|
6350 |
<p> |
6351 |
If your proxy requires a username and password, you should use the following |
6352 |
syntax for the variable: |
6353 |
</p> |
6354 |
|
6355 |
<pre caption="Adding username/password to the proxy variable"> |
6356 |
http://<i>username</i>:<i>password</i>@proxy.gentoo.org:8080 |
6357 |
</pre> |
6358 |
|
6359 |
</body> |
6360 |
</subsection> |
6361 |
<subsection> |
6362 |
<title>Testing the Network</title> |
6363 |
<body> |
6364 |
|
6365 |
<p> |
6366 |
You may want to try pinging your ISP's DNS server (found in |
6367 |
<path>/etc/resolv.conf</path>) and a Web site of your choice, just to make sure |
6368 |
that your packets are reaching the net, DNS name resolution is working |
6369 |
correctly, etc. |
6370 |
</p> |
6371 |
|
6372 |
<pre caption="Further network testing"> |
6373 |
# <i>ping -c 3 www.gentoo.org</i> |
6374 |
</pre> |
6375 |
|
6376 |
<p> |
6377 |
If you are now able to use your network, you can skip the rest of this |
6378 |
section and continue with <uri link="?part=1&chap=4">Preparing the |
6379 |
Disks</uri>. If not, read on. |
6380 |
</p> |
6381 |
|
6382 |
</body> |
6383 |
</subsection> |
6384 |
</section> |
6385 |
<section> |
6386 |
<title>Automatic Network Configuration</title> |
6387 |
<subsection> |
6388 |
<body> |
6389 |
|
6390 |
<p> |
6391 |
If the network doesn't work immediately, some installation media allow you to |
6392 |
use <c>net-setup</c> (for regular or wireless networks), <c>pppoe-setup</c> |
6393 |
(for ADSL-users) or <c>pptp</c> (for PPTP-users - only available on x86). |
6394 |
</p> |
6395 |
|
6396 |
<p> |
6397 |
If your installation medium does not contain any of these tools or your network |
6398 |
doesn't function yet, continue with <uri link="#doc_chap3">Manual Network |
6399 |
Configuration</uri>. |
6400 |
</p> |
6401 |
|
6402 |
<ul> |
6403 |
<li> |
6404 |
Regular Ethernet users should continue with <uri |
6405 |
link="#net-setup">Default: Using net-setup</uri> |
6406 |
</li> |
6407 |
<li> |
6408 |
ADSL users should continue with <uri link="#ppp">Alternative: Using |
6409 |
PPP</uri> |
6410 |
</li> |
6411 |
<li> |
6412 |
PPTP users should continue with <uri link="#pptp">Alternative: |
6413 |
Using PPTP</uri> |
6414 |
</li> |
6415 |
</ul> |
6416 |
|
6417 |
</body> |
6418 |
</subsection> |
6419 |
<subsection id="net-setup"> |
6420 |
<title>Default: Using net-setup</title> |
6421 |
<body> |
6422 |
|
6423 |
<p> |
6424 |
The simplest way to set up networking if it didn't get configured |
6425 |
automatically is to run the <c>net-setup</c> script: |
6426 |
</p> |
6427 |
|
6428 |
<pre caption="Running the net-setup script"> |
6429 |
# <i>net-setup eth0</i> |
6430 |
</pre> |
6431 |
|
6432 |
<p> |
6433 |
<c>net-setup</c> will ask you some questions about your network |
6434 |
environment. When all is done, you should have a working network |
6435 |
connection. Test your network connection as stated before. If the tests |
6436 |
are positive, congratulations! You are now ready to install Gentoo. Skip |
6437 |
the rest of this section and continue with <uri |
6438 |
link="?part=1&chap=4">Preparing the Disks</uri>. |
6439 |
</p> |
6440 |
|
6441 |
<p> |
6442 |
If your network still doesn't work, continue with <uri link="#doc_chap3">Manual |
6443 |
Network Configuration</uri>. |
6444 |
</p> |
6445 |
|
6446 |
|
6447 |
</body> |
6448 |
</subsection> |
6449 |
<subsection id="ppp"> |
6450 |
<title>Alternative: Using PPP</title> |
6451 |
<body> |
6452 |
|
6453 |
<p> |
6454 |
Assuming you need PPPoE to connect to the internet, the Installation CD (any |
6455 |
version) has made things easy for you by including <c>ppp</c>. Use the provided |
6456 |
<c>pppoe-setup</c> script to configure your connection. You will be prompted for |
6457 |
the ethernet device that is connected to your adsl modem, your username and |
6458 |
password, the IPs of your DNS servers and if you need a basic firewall or not. |
6459 |
</p> |
6460 |
|
6461 |
<pre caption="Using ppp"> |
6462 |
# <i>pppoe-setup</i> |
6463 |
# <i>pppoe-start</i> |
6464 |
</pre> |
6465 |
|
6466 |
<p> |
6467 |
If something goes wrong, double-check that you correctly typed your username and |
6468 |
password by looking at <path>/etc/ppp/pap-secrets</path> or |
6469 |
<path>/etc/ppp/chap-secrets</path> and make sure you are using the right |
6470 |
ethernet device. If your ethernet device doesn't exist, you will have to load |
6471 |
the appropriate network modules. In that case you should continue with |
6472 |
<uri link="#doc_chap3">Manual Network Configuration</uri> as we explain how to |
6473 |
load the appropriate network modules there. |
6474 |
</p> |
6475 |
|
6476 |
<p> |
6477 |
If everything worked, continue with <uri link="?part=1&chap=4">Preparing the |
6478 |
Disks</uri>. |
6479 |
</p> |
6480 |
|
6481 |
</body> |
6482 |
</subsection> |
6483 |
<subsection id="pptp"> |
6484 |
<title>Alternative: Using PPTP</title> |
6485 |
<body> |
6486 |
|
6487 |
<note> |
6488 |
PPTP support is only available for x86 |
6489 |
</note> |
6490 |
|
6491 |
<p> |
6492 |
If you need PPTP support, you can use <c>pptpclient</c> which is provided by our |
6493 |
Installation CDs. But first you need to make sure that your configuration is |
6494 |
correct. Edit <path>/etc/ppp/pap-secrets</path> or |
6495 |
<path>/etc/ppp/chap-secrets</path> so it contains the correct username/password |
6496 |
combination: |
6497 |
</p> |
6498 |
|
6499 |
<pre caption="Editing /etc/ppp/chap-secrets"> |
6500 |
# <i>nano -w /etc/ppp/chap-secrets</i> |
6501 |
</pre> |
6502 |
|
6503 |
<p> |
6504 |
Then adjust <path>/etc/ppp/options.pptp</path> if necessary: |
6505 |
</p> |
6506 |
|
6507 |
<pre caption="Editing /etc/ppp/options.pptp"> |
6508 |
# <i>nano -w /etc/ppp/options.pptp</i> |
6509 |
</pre> |
6510 |
|
6511 |
<p> |
6512 |
When all that is done, just run <c>pptp</c> (along with the options you couldn't |
6513 |
set in <path>options.pptp</path>) to connect the server: |
6514 |
</p> |
6515 |
|
6516 |
<pre caption="Connection to a dial-in server"> |
6517 |
# <i>pptp <server ip></i> |
6518 |
</pre> |
6519 |
|
6520 |
<p> |
6521 |
Now continue with <uri link="?part=1&chap=4">Preparing the Disks</uri>. |
6522 |
</p> |
6523 |
|
6524 |
</body> |
6525 |
</subsection> |
6526 |
</section> |
6527 |
<section> |
6528 |
<title>Manual Network Configuration</title> |
6529 |
<subsection> |
6530 |
<title>Loading the Appropriate Network Modules</title> |
6531 |
<body> |
6532 |
|
6533 |
<p> |
6534 |
When the Installation CD boots, it tries to detect all your hardware devices and |
6535 |
loads the appropriate kernel modules (drivers) to support your hardware. In the |
6536 |
vast majority of cases, it does a very good job. However, in some cases, |
6537 |
it may not auto-load the kernel modules you need. |
6538 |
</p> |
6539 |
|
6540 |
<p> |
6541 |
If <c>net-setup</c> or <c>pppoe-setup</c> failed, then it is possible that |
6542 |
your network card wasn't found immediately. This means you may have to load |
6543 |
the appropriate kernel modules manually. |
6544 |
</p> |
6545 |
|
6546 |
<p> |
6547 |
To find out what kernel modules we provide for networking, use |
6548 |
<c>ls</c>: |
6549 |
</p> |
6550 |
|
6551 |
<pre caption="Searching for provided modules"> |
6552 |
# <i>ls /lib/modules/`uname -r`/kernel/drivers/net</i> |
6553 |
</pre> |
6554 |
|
6555 |
<p> |
6556 |
If you find a driver for your network card, use <c>modprobe</c> to load |
6557 |
the kernel module: |
6558 |
</p> |
6559 |
|
6560 |
<pre caption="Using modprobe to load a kernel module"> |
6561 |
<comment>(As an example, we load the pcnet32 module)</comment> |
6562 |
# <i>modprobe pcnet32</i> |
6563 |
</pre> |
6564 |
|
6565 |
<p> |
6566 |
To check if your network card is now detected, use <c>ifconfig</c>. A |
6567 |
detected network card would result in something like this: |
6568 |
</p> |
6569 |
|
6570 |
<pre caption="Testing availability of your network card, successful"> |
6571 |
# <i>ifconfig eth0</i> |
6572 |
eth0 Link encap:Ethernet HWaddr FE:FD:00:00:00:00 |
6573 |
BROADCAST NOARP MULTICAST MTU:1500 Metric:1 |
6574 |
RX packets:0 errors:0 dropped:0 overruns:0 frame:0 |
6575 |
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 |
6576 |
collisions:0 txqueuelen:0 |
6577 |
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) |
6578 |
</pre> |
6579 |
|
6580 |
<p> |
6581 |
If however you receive the following error, the network card is not |
6582 |
detected: |
6583 |
</p> |
6584 |
|
6585 |
<pre caption="Testing availability of your network card, failed"> |
6586 |
# <i>ifconfig eth0</i> |
6587 |
eth0: error fetching interface information: Device not found |
6588 |
</pre> |
6589 |
|
6590 |
<p> |
6591 |
If you have multiple network cards in your system they are named <e>eth0</e>, |
6592 |
<e>eth1</e>, etc. Make sure that the network card you want to use works well and |
6593 |
remember to use the correct naming throughout this document. We will assume that |
6594 |
the network card <e>eth0</e> is used. |
6595 |
</p> |
6596 |
|
6597 |
<p> |
6598 |
Assuming that you now have a detected network card, you can |
6599 |
retry <c>net-setup</c> or <c>pppoe-setup</c> again (which should work |
6600 |
now), but for the hardcore people amongst you we explain how to configure your |
6601 |
network manually. |
6602 |
</p> |
6603 |
|
6604 |
<p> |
6605 |
Select one of the following sections based on your network setup: |
6606 |
</p> |
6607 |
|
6608 |
<ul> |
6609 |
<li><uri link="#install-dhcp">Using DHCP</uri> for automatic IP retrieval</li> |
6610 |
<li> |
6611 |
<uri link="#wireless">Preparing for Wireless Access</uri> if you have a |
6612 |
wireless card |
6613 |
</li> |
6614 |
<li> |
6615 |
<uri link="#network_term">Understanding Network Terminology</uri> explains |
6616 |
what you need to know about networking |
6617 |
</li> |
6618 |
<li> |
6619 |
<uri link="#ifconfig_route">Using ifconfig and route</uri> explains how to |
6620 |
set up your networking manually |
6621 |
</li> |
6622 |
</ul> |
6623 |
|
6624 |
</body> |
6625 |
</subsection> |
6626 |
<subsection id="install-dhcp"> |
6627 |
<title>Using DHCP</title> |
6628 |
<body> |
6629 |
|
6630 |
<p> |
6631 |
DHCP (Dynamic Host Configuration Protocol) makes it possible to |
6632 |
automatically receive networking information (IP address, netmask, |
6633 |
broadcast address, gateway, nameservers etc.). This only works if you |
6634 |
have a DHCP server in your network (or if your provider provides a DHCP |
6635 |
service). To have a network interface receive this information automatically, |
6636 |
use <c>dhcpcd</c>: |
6637 |
</p> |
6638 |
|
6639 |
<pre caption="Using dhcpcd"> |
6640 |
# <i>dhcpcd eth0</i> |
6641 |
<comment>Some network admins require that you use the</comment> |
6642 |
<comment>hostname and domainname provided by the DHCP server.</comment> |
6643 |
<comment>In that case, use</comment> |
6644 |
# <i>dhcpcd -HD eth0</i> |
6645 |
</pre> |
6646 |
|
6647 |
<p> |
6648 |
If this works (try pinging some internet server, like <uri |
6649 |
link="http://www.google.com">Google</uri>), then you are all set and |
6650 |
ready to continue. Skip the rest of this section and continue with <uri |
6651 |
link="?part=1&chap=4">Preparing the Disks</uri>. |
6652 |
</p> |
6653 |
|
6654 |
</body> |
6655 |
</subsection> |
6656 |
<subsection id="wireless"> |
6657 |
<title>Preparing for Wireless Access</title> |
6658 |
<body> |
6659 |
|
6660 |
<note> |
6661 |
Support for the <c>iwconfig</c> command is only available on x86, amd64 and ppc |
6662 |
Installation CDs. You can still get the extensions working otherwise |
6663 |
by following the instructions of the |
6664 |
<uri link="ftp://ftp.linux-wlan.org/pub/linux-wlan-ng/README">linux-wlan-ng |
6665 |
project</uri>. |
6666 |
</note> |
6667 |
|
6668 |
<p> |
6669 |
If you are using a wireless (802.11) card, you may need to configure your |
6670 |
wireless settings before going any further. To see the current wireless settings |
6671 |
on your card, you can use <c>iwconfig</c>. Running <c>iwconfig</c> might show |
6672 |
something like: |
6673 |
</p> |
6674 |
|
6675 |
<pre caption="Showing the current wireless settings"> |
6676 |
# <i>iwconfig eth0</i> |
6677 |
eth0 IEEE 802.11-DS ESSID:"GentooNode" |
6678 |
Mode:Managed Frequency:2.442GHz Access Point: 00:09:5B:11:CC:F2 |
6679 |
Bit Rate:11Mb/s Tx-Power=20 dBm Sensitivity=0/65535 |
6680 |
Retry limit:16 RTS thr:off Fragment thr:off |
6681 |
Power Management:off |
6682 |
Link Quality:25/10 Signal level:-51 dBm Noise level:-102 dBm |
6683 |
Rx invalid nwid:5901 Rx invalid crypt:0 Rx invalid frag:0 Tx |
6684 |
excessive retries:237 Invalid misc:350282 Missed beacon:84 |
6685 |
</pre> |
6686 |
|
6687 |
<note> |
6688 |
Some wireless cards may have a device name of <c>wlan0</c> or <c>ra0</c> instead |
6689 |
of <c>eth0</c>. Run <c>iwconfig</c> without any command-line parameters to |
6690 |
determine the correct device name. |
6691 |
</note> |
6692 |
|
6693 |
<p> |
6694 |
For most users, there are only two settings that might be important to change, |
6695 |
the ESSID (aka wireless network name) or the WEP key. If the ESSID and Access |
6696 |
Point address listed are already that of your access point and you are not using |
6697 |
WEP, then your wireless is working. If you need to change your ESSID, or add a |
6698 |
WEP key, you can issue the following commands: |
6699 |
</p> |
6700 |
|
6701 |
<pre caption="Changing ESSID and/or adding WEP key"> |
6702 |
<comment>(This sets the network name to "GentooNode")</comment> |
6703 |
# <i>iwconfig eth0 essid GentooNode</i> |
6704 |
|
6705 |
<comment>(This sets a hex WEP key)</comment> |
6706 |
# <i>iwconfig eth0 key 1234123412341234abcd</i> |
6707 |
|
6708 |
<comment>(This sets an ASCII key - prefix it with "s:")</comment> |
6709 |
# <i>iwconfig eth0 key s:some-password</i> |
6710 |
</pre> |
6711 |
|
6712 |
<p> |
6713 |
You can then confirm your wireless settings again by using <c>iwconfig</c>. |
6714 |
Once you have wireless working, you can continue configuring the IP level |
6715 |
networking options as described in the next section (<uri |
6716 |
link="#network_term">Understanding Network Terminology</uri>) or use the |
6717 |
<c>net-setup</c> tool as described previously. |
6718 |
</p> |
6719 |
|
6720 |
</body> |
6721 |
</subsection> |
6722 |
<subsection id="network_term"> |
6723 |
<title>Understanding Network Terminology</title> |
6724 |
<body> |
6725 |
|
6726 |
<note> |
6727 |
If you know your IP address, broadcast address, netmask and nameservers, |
6728 |
then you can skip this subsection and continue with <uri |
6729 |
link="#ifconfig_route">Using ifconfig and route</uri>. |
6730 |
</note> |
6731 |
|
6732 |
<p> |
6733 |
If all of the above fails, you will have to configure your network manually. |
6734 |
This is not difficult at all. However, you need to be familiar with some |
6735 |
network terminology, as you will need it to be able to |
6736 |
configure your network to your satisfaction. After reading this, you |
6737 |
will know what a <e>gateway</e> is, what a <e>netmask</e> serves for, |
6738 |
how a <e>broadcast</e> address is formed and why you need |
6739 |
<e>nameservers</e>. |
6740 |
</p> |
6741 |
|
6742 |
<p> |
6743 |
In a network, hosts are identified by their <e>IP address</e> (Internet |
6744 |
Protocol address). Such an address is a combination of four numbers |
6745 |
between 0 and 255. Well, at least that is how we perceive it. In |
6746 |
reality, such an IP address consists of 32 bits (ones and zeros). Let's |
6747 |
view an example: |
6748 |
</p> |
6749 |
|
6750 |
<pre caption="Example of an IP address"> |
6751 |
IP Address (numbers): 192.168.0.2 |
6752 |
IP Address (bits): 11000000 10101000 00000000 00000010 |
6753 |
-------- -------- -------- -------- |
6754 |
192 168 0 2 |
6755 |
</pre> |
6756 |
|
6757 |
<p> |
6758 |
Such an IP address is unique to a host as far as all accessible networks are |
6759 |
concerned (i.e. every host that you are able to reach must have a unique IP |
6760 |
address). In order to distinguish between hosts inside and outside a |
6761 |
network, the IP address is divided in two parts: the |
6762 |
<e>network</e> part and the <e>host</e> part. |
6763 |
</p> |
6764 |
|
6765 |
<p> |
6766 |
The separation is written down with the <e>netmask</e>, a collection of |
6767 |
ones followed by a collection of zeros. The part of the IP that can be |
6768 |
mapped on the ones is the network-part, the other one is the host-part. |
6769 |
As usual, the netmask can be written down as an IP-address. |
6770 |
</p> |
6771 |
|
6772 |
<pre caption="Example of network/host separation"> |
6773 |
IP-address: 192 168 0 2 |
6774 |
11000000 10101000 00000000 00000010 |
6775 |
Netmask: 11111111 11111111 11111111 00000000 |
6776 |
255 255 255 0 |
6777 |
+--------------------------+--------+ |
6778 |
Network Host |
6779 |
</pre> |
6780 |
|
6781 |
<p> |
6782 |
In other words, 192.168.0.14 is still part of our example network, but |
6783 |
192.168.1.2 is not. |
6784 |
</p> |
6785 |
|
6786 |
<p> |
6787 |
The <e>broadcast</e> address is an IP-address with the same network-part |
6788 |
as your network, but with only ones as host-part. Every host on your |
6789 |
network listens to this IP address. It is truly meant for broadcasting |
6790 |
packets. |
6791 |
</p> |
6792 |
|
6793 |
<pre caption="Broadcast address"> |
6794 |
IP-address: 192 168 0 2 |
6795 |
11000000 10101000 00000000 00000010 |
6796 |
Broadcast: 11000000 10101000 00000000 11111111 |
6797 |
192 168 0 255 |
6798 |
+--------------------------+--------+ |
6799 |
Network Host |
6800 |
</pre> |
6801 |
|
6802 |
<p> |
6803 |
To be able to surf on the internet, you must know which host shares the |
6804 |
Internet connection. This host is called the <e>gateway</e>. Since it is |
6805 |
a regular host, it has a regular IP address (for instance 192.168.0.1). |
6806 |
</p> |
6807 |
|
6808 |
<p> |
6809 |
We previously stated that every host has its own IP address. To be able |
6810 |
to reach this host by a name (instead of an IP address) you need a |
6811 |
service that translates a name (such as <e>dev.gentoo.org</e>) to an IP |
6812 |
address (such as <e>64.5.62.82</e>). Such a service is called a name |
6813 |
service. To use such a service, you must define the necessary <e>name |
6814 |
servers</e> in <path>/etc/resolv.conf</path>. |
6815 |
</p> |
6816 |
|
6817 |
<p> |
6818 |
In some cases, your gateway also serves as nameserver. Otherwise you |
6819 |
will have to enter the nameservers provided by your ISP. |
6820 |
</p> |
6821 |
|
6822 |
<p> |
6823 |
To summarise, you will need the following information before continuing: |
6824 |
</p> |
6825 |
|
6826 |
<table> |
6827 |
<tr> |
6828 |
<th>Network Item</th> |
6829 |
<th>Example</th> |
6830 |
</tr> |
6831 |
<tr> |
6832 |
<ti>Your IP address</ti> |
6833 |
<ti>192.168.0.2</ti> |
6834 |
</tr> |
6835 |
<tr> |
6836 |
<ti>Netmask</ti> |
6837 |
<ti>255.255.255.0</ti> |
6838 |
</tr> |
6839 |
<tr> |
6840 |
<ti>Broadcast</ti> |
6841 |
<ti>192.168.0.255</ti> |
6842 |
</tr> |
6843 |
<tr> |
6844 |
<ti>Gateway</ti> |
6845 |
<ti>192.168.0.1</ti> |
6846 |
</tr> |
6847 |
<tr> |
6848 |
<ti>Nameserver(s)</ti> |
6849 |
<ti>195.130.130.5, 195.130.130.133</ti> |
6850 |
</tr> |
6851 |
</table> |
6852 |
|
6853 |
</body> |
6854 |
</subsection> |
6855 |
<subsection id="ifconfig_route"> |
6856 |
<title>Using ifconfig and route</title> |
6857 |
<body> |
6858 |
|
6859 |
<p> |
6860 |
Setting up your network consists of three steps. First we assign |
6861 |
ourselves an IP address using <c>ifconfig</c>. Then we set up routing to |
6862 |
the gateway using <c>route</c>. Then we finish up by placing the |
6863 |
nameserver IPs in <path>/etc/resolv.conf</path>. |
6864 |
</p> |
6865 |
|
6866 |
<p> |
6867 |
To assign an IP address, you will need your IP address, broadcast |
6868 |
address and netmask. Then execute the following command, substituting |
6869 |
<c>${IP_ADDR}</c> with your IP address, <c>${BROADCAST}</c> with your |
6870 |
broadcast address and <c>${NETMASK}</c> with your netmask: |
6871 |
</p> |
6872 |
|
6873 |
<pre caption="Using ifconfig"> |
6874 |
# <i>ifconfig eth0 ${IP_ADDR} broadcast ${BROADCAST} netmask ${NETMASK} up</i> |
6875 |
</pre> |
6876 |
|
6877 |
<p> |
6878 |
Now set up routing using <c>route</c>. Substitute <c>${GATEWAY}</c> with |
6879 |
your gateway IP address: |
6880 |
</p> |
6881 |
|
6882 |
<pre caption="Using route"> |
6883 |
# <i>route add default gw ${GATEWAY}</i> |
6884 |
</pre> |
6885 |
|
6886 |
<p> |
6887 |
Now open <path>/etc/resolv.conf</path> with your favorite editor (in our |
6888 |
example, we use <c>nano</c>): |
6889 |
</p> |
6890 |
|
6891 |
<pre caption="Creating /etc/resolv.conf"> |
6892 |
# <i>nano -w /etc/resolv.conf</i> |
6893 |
</pre> |
6894 |
|
6895 |
<p> |
6896 |
Now fill in your nameserver(s) using the following as a template. Make |
6897 |
sure you substitute <c>${NAMESERVER1}</c> and <c>${NAMESERVER2}</c> with |
6898 |
the appropriate nameserver addresses: |
6899 |
</p> |
6900 |
|
6901 |
<pre caption="/etc/resolv.conf template"> |
6902 |
nameserver ${NAMESERVER1} |
6903 |
nameserver ${NAMESERVER2} |
6904 |
</pre> |
6905 |
|
6906 |
<p> |
6907 |
That's it. Now test your network by pinging some Internet server (like |
6908 |
<uri link="http://www.google.com">Google</uri>). If this works, |
6909 |
congratulations then. You are now ready to install Gentoo. Continue with <uri |
6910 |
link="?part=1&chap=4">Preparing the Disks</uri>. |
6911 |
</p> |
6912 |
|
6913 |
</body> |
6914 |
</subsection> |
6915 |
</section> |
6916 |
</sections> |
6917 |
|
6918 |
|
6919 |
|
6920 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-next.xml |
6921 |
|
6922 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-next.xml?rev=1.1&view=markup |
6923 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-next.xml?rev=1.1&content-type=text/plain |
6924 |
|
6925 |
Index: hb-install-next.xml |
6926 |
=================================================================== |
6927 |
<?xml version='1.0' encoding='UTF-8'?> |
6928 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
6929 |
|
6930 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
6931 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
6932 |
|
6933 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-next.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
6934 |
|
6935 |
<sections> |
6936 |
|
6937 |
<version>8.0</version> |
6938 |
<date>2007-05-07</date> |
6939 |
|
6940 |
<section> |
6941 |
<title>Documentation</title> |
6942 |
<subsection> |
6943 |
<body> |
6944 |
|
6945 |
<p> |
6946 |
Congratulations! You now have a working Gentoo system. But where to go from |
6947 |
here? What are your options now? What to explore first? Gentoo provides its |
6948 |
users with lots of possibilities, and therefore lots of documented (and less |
6949 |
documented) features. |
6950 |
</p> |
6951 |
|
6952 |
<p> |
6953 |
You should definitely take a look at the next part of the Gentoo Handbook |
6954 |
entitled <uri link="?part=2">Working with Gentoo</uri> which explains |
6955 |
how to keep your software up to date, how to install more software, what USE |
6956 |
flags are, how the Gentoo Init system works, etc. |
6957 |
</p> |
6958 |
|
6959 |
<p> |
6960 |
If you are interested in optimizing your system for desktop use, or you want to |
6961 |
learn how to configure your system to be a full working desktop system, consult |
6962 |
our extensive <uri link="/doc/en/index.xml?catid=desktop">Gentoo Desktop |
6963 |
Documentation Resources</uri>. Besides, you might want to use our <uri |
6964 |
link="/doc/en/guide-localization.xml">localization guide</uri> to make your |
6965 |
system feel more at home. |
6966 |
</p> |
6967 |
|
6968 |
<p> |
6969 |
We also have a <uri link="/doc/en/security/">Gentoo Security Handbook</uri> |
6970 |
which is worth reading. |
6971 |
</p> |
6972 |
|
6973 |
<p> |
6974 |
For a full listing of all our available documentation check out our <uri |
6975 |
link="/doc/en/index.xml">Documentation Resources</uri> page. |
6976 |
</p> |
6977 |
|
6978 |
</body> |
6979 |
</subsection> |
6980 |
</section> |
6981 |
<section> |
6982 |
<title>Gentoo Online</title> |
6983 |
<body> |
6984 |
|
6985 |
<p> |
6986 |
You are of course always welcome on our <uri |
6987 |
link="http://forums.gentoo.org">Gentoo Forums</uri> or on one of our many |
6988 |
<uri link="/main/en/irc.xml">Gentoo IRC channels</uri>. |
6989 |
</p> |
6990 |
|
6991 |
<p> |
6992 |
We also have several <uri |
6993 |
link="/main/en/lists.xml">mailinglists</uri> open to all |
6994 |
our users. Information on how to join is contained in that page. |
6995 |
</p> |
6996 |
|
6997 |
<p> |
6998 |
We'll shut up now and let you enjoy your installation :) |
6999 |
</p> |
7000 |
|
7001 |
</body> |
7002 |
</section> |
7003 |
<section> |
7004 |
<title>Gentoo Changes since 2007.0</title> |
7005 |
<subsection> |
7006 |
<title>Changes?</title> |
7007 |
<body> |
7008 |
|
7009 |
<p> |
7010 |
Gentoo is a fast-moving target. The following sections describe important |
7011 |
changes that affect a Gentoo installation. We only list those that have anything |
7012 |
in common with the installation, not with package changes that did not occur |
7013 |
during the installation. |
7014 |
</p> |
7015 |
|
7016 |
<p> |
7017 |
There have been no significant changes since. |
7018 |
</p> |
7019 |
|
7020 |
</body> |
7021 |
</subsection> |
7022 |
</section> |
7023 |
</sections> |
7024 |
|
7025 |
|
7026 |
|
7027 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc64-bootloader.xml |
7028 |
|
7029 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc64-bootloader.xml?rev=1.1&view=markup |
7030 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc64-bootloader.xml?rev=1.1&content-type=text/plain |
7031 |
|
7032 |
Index: hb-install-ppc64-bootloader.xml |
7033 |
=================================================================== |
7034 |
<?xml version='1.0' encoding='UTF-8'?> |
7035 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
7036 |
|
7037 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
7038 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
7039 |
|
7040 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc64-bootloader.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
7041 |
|
7042 |
<sections> |
7043 |
|
7044 |
<version>8.0</version> |
7045 |
<date>2007-05-07</date> |
7046 |
|
7047 |
<section> |
7048 |
<title>Making your Choice</title> |
7049 |
<subsection> |
7050 |
<title>Introduction</title> |
7051 |
<body> |
7052 |
|
7053 |
<p> |
7054 |
Now that your kernel is configured and compiled and the necessary system |
7055 |
configuration files are filled in correctly, it is time to install a |
7056 |
program that will fire up your kernel when you start the system. Such a |
7057 |
program is called a <e>bootloader</e>. |
7058 |
</p> |
7059 |
|
7060 |
<p> |
7061 |
On Linux/PPC64 we have only yaBoot as a bootloader until grub2 is |
7062 |
finished. |
7063 |
</p> |
7064 |
|
7065 |
</body> |
7066 |
</subsection> |
7067 |
</section> |
7068 |
<section id="yaboot"> |
7069 |
<title>Using yaBoot</title> |
7070 |
<subsection> |
7071 |
<title>Introduction</title> |
7072 |
<body> |
7073 |
|
7074 |
<impo> |
7075 |
For a 64bit userland use yaboot-static instead of yaboot, because yaboot won't |
7076 |
compile on 64bit userland systems. For a 32bit userland use yaboot as you |
7077 |
normally would. |
7078 |
</impo> |
7079 |
|
7080 |
<p> |
7081 |
There are two ways to configure yaBoot for your system. You can use the new and |
7082 |
improved <c>yabootconfig</c> included with <path>yaboot-1.3.8-r1</path> and |
7083 |
later to automatically set up yaboot. If for some reason you do not want to run |
7084 |
<c>yabootconfig</c> to automatically set up <path>/etc/yaboot.conf</path> or you |
7085 |
are installing Gentoo on a G5 (on which <c>yabootconfig</c> does not always |
7086 |
work), you can just edit the sample file already installed on your system. |
7087 |
</p> |
7088 |
|
7089 |
<pre caption="Installing Necessary File System Tools"> |
7090 |
# <i>emerge hfsutils hfsplusutils</i> |
7091 |
</pre> |
7092 |
|
7093 |
<pre caption="Installing the bootloader"> |
7094 |
<comment>(64bit userland)</comment> |
7095 |
# <i>emerge --update yaboot-static</i> |
7096 |
<comment>(32bit userland)</comment> |
7097 |
# <i>emerge --update yaboot</i> |
7098 |
</pre> |
7099 |
|
7100 |
<impo> |
7101 |
yabootconfig/ybin won't work on IBM. You have to install yaboot another way: |
7102 |
<uri link="#yaboot-ibm">Using yaboot on IBM hardware</uri> |
7103 |
</impo> |
7104 |
|
7105 |
<note> |
7106 |
If your root filesystem uses the JFS filesystem, be sure to add <c>ro</c> as a |
7107 |
kernel parameter. JFS must be able to replay its log in read-only mode before it |
7108 |
gets mounted read-write. |
7109 |
</note> |
7110 |
|
7111 |
<ul> |
7112 |
<li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li> |
7113 |
<li> |
7114 |
<uri link="#manual_yaboot">Alternative: Manual yaBoot Configuration</uri> |
7115 |
</li> |
7116 |
</ul> |
7117 |
|
7118 |
</body> |
7119 |
</subsection> |
7120 |
<subsection id="yabootconfig"> |
7121 |
<title>Default: Using yabootconfig</title> |
7122 |
<body> |
7123 |
|
7124 |
<p> |
7125 |
<c>yabootconfig</c> will auto-detect the partitions on your machine and will |
7126 |
set up dual and triple boot combinations with Linux, Mac OS, and Mac OS |
7127 |
X. |
7128 |
</p> |
7129 |
|
7130 |
<p> |
7131 |
To use <c>yabootconfig</c>, your drive must have a bootstrap partition, and |
7132 |
<path>/etc/fstab</path> must be configured with your Linux partitions. Both of |
7133 |
these should have been done already in the steps above. To start, ensure that |
7134 |
you have the latest version of yaboot installed by running <c>emerge --update |
7135 |
yaboot-static</c>. This is necessary as the latest version will be available via |
7136 |
Portage, but it may not have made it into the stage files. |
7137 |
</p> |
7138 |
|
7139 |
<p> |
7140 |
Now run <c>yabootconfig</c>. The program will run and it will confirm the |
7141 |
location of the bootstrap partition. Type <c>Y</c> if it is correct. If not, |
7142 |
double check <path>/etc/fstab</path>. yabootconfig will then scan your system |
7143 |
setup, create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you. |
7144 |
<c>mkofboot</c> is used to format the bootstrap partition, and install the |
7145 |
yaboot configuration file into it. |
7146 |
</p> |
7147 |
|
7148 |
<p> |
7149 |
You might want to verify the contents of <path>/etc/yaboot.conf</path>. If |
7150 |
you make changes to <path>/etc/yaboot.conf</path> (like setting the |
7151 |
default/boot OS), make sure to rerun <c>ybin -v</c> to apply changes to the |
7152 |
bootstrap partition. |
7153 |
</p> |
7154 |
|
7155 |
<p> |
7156 |
Now continue with <uri link="#reboot">Rebooting your System</uri>. |
7157 |
</p> |
7158 |
|
7159 |
</body> |
7160 |
</subsection> |
7161 |
<subsection id="manual_yaboot"> |
7162 |
<title>Alternative: Manual yaBoot Configuration</title> |
7163 |
<body> |
7164 |
|
7165 |
<p> |
7166 |
Below you find a completed <path>yaboot.conf</path> file. Alter it at |
7167 |
will. |
7168 |
</p> |
7169 |
|
7170 |
<pre caption="/etc/yaboot.conf"> |
7171 |
<comment>## /etc/yaboot.conf |
7172 |
## |
7173 |
## run: "man yaboot.conf" for details. Do not make changes until you have!! |
7174 |
## see also: /usr/share/doc/yaboot/examples for example configurations. |
7175 |
## |
7176 |
## For a dual-boot menu, add one or more of: |
7177 |
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ |
7178 |
|
7179 |
## our bootstrap partition:</comment> |
7180 |
|
7181 |
boot=/dev/hda2 |
7182 |
|
7183 |
<comment>## ofboot is the Open Firmware way to specify the bootstrap partition. |
7184 |
## If this isn't defined, yaboot fails on the G5 and some G4s (unless |
7185 |
## you pass the necessary arguments to the mkofboot/ybin program). |
7186 |
## hd:X means /dev/sdaX (or /dev/hdaX).</comment> |
7187 |
|
7188 |
ofboot=hd:2 |
7189 |
|
7190 |
<comment>## hd: is open firmware speak for hda</comment> |
7191 |
device=hd: |
7192 |
|
7193 |
delay=5 |
7194 |
defaultos=macosx |
7195 |
timeout=30 |
7196 |
install=/usr/lib/yaboot/yaboot |
7197 |
magicboot=/usr/lib/yaboot/ofboot |
7198 |
|
7199 |
<comment>################# |
7200 |
## This section can be duplicated if you have more than one kernel or set of |
7201 |
## boot options - replace <keyval id="kernel-name"/> with your kernel-version |
7202 |
#################</comment> |
7203 |
image=/boot/<keyval id="kernel-name"/> |
7204 |
label=Linux |
7205 |
root=/dev/hda3 |
7206 |
partition=3 |
7207 |
read-only |
7208 |
|
7209 |
macos=hd:13 |
7210 |
macosx=hd:12 |
7211 |
enablecdboot |
7212 |
enableofboot |
7213 |
</pre> |
7214 |
|
7215 |
<p> |
7216 |
Once <path>yaboot.conf</path> is set up the way you want it, you run <c>mkofboot |
7217 |
-v</c> to install the settings in the bootstrap partition. <e>Don't forget |
7218 |
this!</e> Confirm when <c>mkofboot</c> asks you to create a new filesystem. |
7219 |
</p> |
7220 |
|
7221 |
<p> |
7222 |
If all goes well, and you have the same options as the sample above, your next |
7223 |
reboot will give you a simple, five-entry boot menu. If you update your yaboot |
7224 |
config later on, you'll just need to run <c>ybin -v</c> to update the bootstrap |
7225 |
partition - <c>mkofboot</c> is for initial setup only. |
7226 |
</p> |
7227 |
|
7228 |
<p> |
7229 |
For more information on yaboot, take a look at the <uri |
7230 |
link="http://penguinppc.org/projects/yaboot">yaboot project</uri>. For now, |
7231 |
continue the installation with <uri link="#reboot">Rebooting your System</uri>. |
7232 |
</p> |
7233 |
|
7234 |
</body> |
7235 |
</subsection> |
7236 |
</section> |
7237 |
<section id="yaboot-ibm"> |
7238 |
<title>Using yaboot on IBM hardware</title> |
7239 |
<body> |
7240 |
|
7241 |
<p> |
7242 |
On IBM hardware you cannot run yabootconfig or ybin. You must proceed with the |
7243 |
following steps: |
7244 |
</p> |
7245 |
|
7246 |
<ul> |
7247 |
<li>Install yaboot-static</li> |
7248 |
<li> |
7249 |
Run <c>dd if=/usr/lib/yaboot/yaboot.chrp of=/dev/sdXX</c> (fill in XX with |
7250 |
your disk and partition for the PReP partition; this was in our example |
7251 |
<path>/dev/sda1</path>) |
7252 |
</li> |
7253 |
<li> |
7254 |
Next construct your own <path>yaboot.conf</path> file and place into |
7255 |
<path>/etc</path>. (Take a look at the config above, look into the man page |
7256 |
of <path>yaboot.conf</path> or look at the below <path>yaboot.conf</path> |
7257 |
example.) |
7258 |
</li> |
7259 |
<li> |
7260 |
Assuming your boot device in OF is pointing to the harddrive you prep boot |
7261 |
partition is on then it'll just work, otherwise at IPL time, go into the |
7262 |
multiboot menu and set the boot device to the one with your prep boot |
7263 |
partition |
7264 |
</li> |
7265 |
<li>That's it!</li> |
7266 |
</ul> |
7267 |
|
7268 |
<pre caption="yaboot.conf for IBM hardware"> |
7269 |
device=disk: |
7270 |
partition=2 |
7271 |
root=/dev/sda2 |
7272 |
default=linux |
7273 |
timeout=50 |
7274 |
|
7275 |
image=/boot/<keyval id="kernel-name"/> |
7276 |
label=linux |
7277 |
append="console=ttyS0,9600" |
7278 |
read-only |
7279 |
</pre> |
7280 |
|
7281 |
<p> |
7282 |
For POWER4, POWER5, and blade-based hardware where the PReP disk partition and |
7283 |
the disk partition that contains your kernel are on the same physical disk, you |
7284 |
can use a simplified <path>yaboot.conf</path>. The following should be |
7285 |
sufficient: |
7286 |
</p> |
7287 |
|
7288 |
<pre caption="yaboot.conf for PReP hardware"> |
7289 |
default = linux |
7290 |
timeout = 100 |
7291 |
image=/boot/<keyval id="kernel-name"/> |
7292 |
label=linux |
7293 |
read-only |
7294 |
root = /dev/sda2 |
7295 |
append="root=/dev/sda2" |
7296 |
</pre> |
7297 |
|
7298 |
<p> |
7299 |
To verify that yaboot has been copied to the PReP partition: |
7300 |
</p> |
7301 |
|
7302 |
<pre caption="Verifying the yaboot install on PReP"> |
7303 |
# <i>dd if=/dev/sda1 count=10 | grep ELF</i> |
7304 |
Binary file (standard input) matches |
7305 |
10+0 records in |
7306 |
10+0 records out |
7307 |
</pre> |
7308 |
|
7309 |
<p> |
7310 |
A match signifies that yaboot was installed correctly. |
7311 |
</p> |
7312 |
|
7313 |
</body> |
7314 |
</section> |
7315 |
<section id="reboot"> |
7316 |
<title>Rebooting the System</title> |
7317 |
<subsection> |
7318 |
<body> |
7319 |
|
7320 |
<p> |
7321 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
7322 |
that one magical command you have been waiting for: <c>reboot</c>. |
7323 |
</p> |
7324 |
|
7325 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
7326 |
# <i>exit</i> |
7327 |
~# <i>cd</i> |
7328 |
~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
7329 |
~# <i>reboot</i> |
7330 |
</pre> |
7331 |
|
7332 |
<p> |
7333 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
7334 |
booted again instead of your new Gentoo system. |
7335 |
</p> |
7336 |
|
7337 |
<p> |
7338 |
Once rebooted in your Gentoo installation, finish up with <uri |
7339 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
7340 |
</p> |
7341 |
|
7342 |
</body> |
7343 |
</subsection> |
7344 |
</section> |
7345 |
|
7346 |
</sections> |
7347 |
|
7348 |
|
7349 |
|
7350 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc64-disk.xml |
7351 |
|
7352 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc64-disk.xml?rev=1.1&view=markup |
7353 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc64-disk.xml?rev=1.1&content-type=text/plain |
7354 |
|
7355 |
Index: hb-install-ppc64-disk.xml |
7356 |
=================================================================== |
7357 |
<?xml version='1.0' encoding='UTF-8'?> |
7358 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
7359 |
|
7360 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
7361 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
7362 |
|
7363 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc64-disk.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
7364 |
|
7365 |
<sections> |
7366 |
|
7367 |
<version>8.2</version> |
7368 |
<date>2007-06-26</date> |
7369 |
|
7370 |
<section> |
7371 |
<title>Introduction to Block Devices</title> |
7372 |
<subsection> |
7373 |
<title>Block Devices</title> |
7374 |
<body> |
7375 |
|
7376 |
<p> |
7377 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
7378 |
and Linux in general, including Linux filesystems, partitions and block devices. |
7379 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
7380 |
you'll be guided through the process of setting up partitions and filesystems |
7381 |
for your Gentoo Linux installation. |
7382 |
</p> |
7383 |
|
7384 |
<p> |
7385 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
7386 |
probably the one that represents the first IDE drive in a Linux system, namely |
7387 |
<path>/dev/hda</path>. If your system uses SCSI drives, then your first hard |
7388 |
drive would be <path>/dev/sda</path>. Serial ATA drives are also |
7389 |
<path>/dev/sda</path> even if they are IDE drives. |
7390 |
</p> |
7391 |
|
7392 |
<p> |
7393 |
The block devices above represent an abstract interface to the disk. User |
7394 |
programs can use these block devices to interact with your disk without worrying |
7395 |
about whether your drives are IDE, SCSI or something else. The program can |
7396 |
simply address the storage on the disk as a bunch of contiguous, |
7397 |
randomly-accessible 512-byte blocks. |
7398 |
</p> |
7399 |
|
7400 |
</body> |
7401 |
</subsection> |
7402 |
<subsection> |
7403 |
<title>Partitions and Slices</title> |
7404 |
<body> |
7405 |
|
7406 |
<p> |
7407 |
Although it is theoretically possible to use a full disk to house your Linux |
7408 |
system, this is almost never done in practice. Instead, full disk block devices |
7409 |
are split up in smaller, more manageable block devices. On most systems, |
7410 |
these are called <e>partitions</e>. Other architectures use a similar technique, |
7411 |
called <e>slices</e>. |
7412 |
</p> |
7413 |
|
7414 |
</body> |
7415 |
</subsection> |
7416 |
</section> |
7417 |
<section> |
7418 |
<title>Designing a Partitioning Scheme</title> |
7419 |
<subsection> |
7420 |
<title>Default Partitioning Scheme</title> |
7421 |
<body> |
7422 |
|
7423 |
<p> |
7424 |
If you are not interested in drawing up a partitioning scheme for your system, |
7425 |
you can use the partitioning scheme we use throughout this book: |
7426 |
</p> |
7427 |
|
7428 |
<table> |
7429 |
<tr> |
7430 |
<th>Partition</th> |
7431 |
<th>Filesystem</th> |
7432 |
<th>Size</th> |
7433 |
<th>Description</th> |
7434 |
</tr> |
7435 |
<tr> |
7436 |
<ti><path>/dev/sda1</path></ti> |
7437 |
<ti>Partition map</ti> |
7438 |
<ti>31.5k</ti> |
7439 |
<ti>Partition map</ti> |
7440 |
</tr> |
7441 |
<tr> |
7442 |
<ti><path>/dev/sda2</path></ti> |
7443 |
<ti>(bootstrap)</ti> |
7444 |
<ti>800k</ti> |
7445 |
<ti>Apple_Bootstrap</ti> |
7446 |
</tr> |
7447 |
<tr> |
7448 |
<ti><path>/dev/sda3</path></ti> |
7449 |
<ti>(swap)</ti> |
7450 |
<ti>512M</ti> |
7451 |
<ti>Swap partition</ti> |
7452 |
</tr> |
7453 |
<tr> |
7454 |
<ti><path>/dev/sda4</path></ti> |
7455 |
<ti>ext3</ti> |
7456 |
<ti>Rest of the disk</ti> |
7457 |
<ti>Root partition</ti> |
7458 |
</tr> |
7459 |
</table> |
7460 |
|
7461 |
<note> |
7462 |
There are some partitions named like this: <path>Apple_Driver43</path>, |
7463 |
<path>Apple_Driver_ATA</path>, <path>Apple_FWDriver</path>, |
7464 |
<path>Apple_Driver_IOKit</path>, and <path>Apple_Patches</path>. If you are not |
7465 |
planning to use MacOS 9 you can delete them, because MacOS X and Linux don't |
7466 |
need them. You might have to use parted in order to delete them, as mac-fdisk |
7467 |
can't delete them yet. |
7468 |
</note> |
7469 |
|
7470 |
<p> |
7471 |
If you are interested in knowing how big a partition should be, or even how |
7472 |
many partitions you need, read on. Otherwise continue now with |
7473 |
<uri link="#mac-fdisk">Apple G5: Using mac-fdisk to Partition your |
7474 |
Disk</uri> or <uri link="#fdisk">IBM pSeries: using fdisk to Partition |
7475 |
your Disk</uri> |
7476 |
</p> |
7477 |
|
7478 |
</body> |
7479 |
</subsection> |
7480 |
<subsection> |
7481 |
<title>How Many and How Big?</title> |
7482 |
<body> |
7483 |
|
7484 |
<p> |
7485 |
The number of partitions is highly dependent on your environment. For instance, |
7486 |
if you have lots of users, you will most likely want to have your |
7487 |
<path>/home</path> separate as it increases security and makes backups easier. |
7488 |
If you are installing Gentoo to perform as a mailserver, your <path>/var</path> |
7489 |
should be separate as all mails are stored inside <path>/var</path>. A good |
7490 |
choice of filesystem will then maximise your performance. Gameservers will have |
7491 |
a separate <path>/opt</path> as most gaming servers are installed there. The |
7492 |
reason is similar for <path>/home</path>: security and backups. You will |
7493 |
definitely want to keep <path>/usr</path> big: not only will it contain the |
7494 |
majority of applications, the Portage tree alone takes around 500 Mbyte |
7495 |
excluding the various sources that are stored in it. |
7496 |
</p> |
7497 |
|
7498 |
<p> |
7499 |
As you can see, it very much depends on what you want to achieve. Separate |
7500 |
partitions or volumes have the following advantages: |
7501 |
</p> |
7502 |
|
7503 |
<ul> |
7504 |
<li> |
7505 |
You can choose the best performing filesystem for each partition or volume |
7506 |
</li> |
7507 |
<li> |
7508 |
Your entire system cannot run out of free space if one defunct tool is |
7509 |
continuously writing files to a partition or volume |
7510 |
</li> |
7511 |
<li> |
7512 |
If necessary, file system checks are reduced in time, as multiple checks can |
7513 |
be done in parallel (although this advantage is more with multiple disks than |
7514 |
it is with multiple partitions) |
7515 |
</li> |
7516 |
<li> |
7517 |
Security can be enhanced by mounting some partitions or volumes read-only, |
7518 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
7519 |
</li> |
7520 |
</ul> |
7521 |
|
7522 |
<p> |
7523 |
However, multiple partitions have one big disadvantage: if not configured |
7524 |
properly, you might result in having a system with lots of free space on one |
7525 |
partition and none on another. There is also a 15-partition limit for SCSI and |
7526 |
SATA. |
7527 |
</p> |
7528 |
|
7529 |
</body> |
7530 |
</subsection> |
7531 |
</section> |
7532 |
<section id="mac-fdisk"> |
7533 |
<title>Default: Using mac-fdisk (Apple G5) to Partition your Disk</title> |
7534 |
<body> |
7535 |
|
7536 |
<p> |
7537 |
At this point, create your partitions using <c>mac-fdisk</c>: |
7538 |
</p> |
7539 |
|
7540 |
<pre caption="Starting mac-fdisk"> |
7541 |
# <i>mac-fdisk /dev/sda</i> |
7542 |
</pre> |
7543 |
|
7544 |
<p> |
7545 |
First delete the partitions you have cleared previously to make room for your |
7546 |
Linux partitions. Use <c>d</c> in <c>mac-fdisk</c> to delete those partition(s). |
7547 |
It will ask for the partition number to delete. |
7548 |
</p> |
7549 |
|
7550 |
<p> |
7551 |
Second, create an <e>Apple_Bootstrap</e> partition by using <c>b</c>. It will |
7552 |
ask for what block you want to start. Enter the number of your first free |
7553 |
partition, followed by a <c>p</c>. For instance this is <c>2p</c>. |
7554 |
</p> |
7555 |
|
7556 |
<note> |
7557 |
This partition is <e>not</e> a "boot" partition. It is not used by Linux at all; |
7558 |
you don't have to place any filesystem on it and you should never mount it. PPC |
7559 |
users don't need an extra partition for <path>/boot</path>. |
7560 |
</note> |
7561 |
|
7562 |
<p> |
7563 |
Now create a swap partition by pressing <c>c</c>. Again <c>mac-fdisk</c> will |
7564 |
ask for what block you want to start this partition from. As we used <c>2</c> |
7565 |
before to create the Apple_Bootstrap partition, you now have to enter |
7566 |
<c>3p</c>. When you're asked for the size, enter <c>512M</c> (or whatever size |
7567 |
you want). When asked for a name, enter <c>swap</c> (mandatory). |
7568 |
</p> |
7569 |
|
7570 |
<p> |
7571 |
To create the root partition, enter <c>c</c>, followed by <c>4p</c> to select |
7572 |
from what block the root partition should start. When asked for the size, enter |
7573 |
<c>4p</c> again. <c>mac-fdisk</c> will interpret this as "Use all available |
7574 |
space". When asked for the name, enter <c>root</c> (mandatory). |
7575 |
</p> |
7576 |
|
7577 |
<p> |
7578 |
To finish up, write the partition to the disk using <c>w</c> and <c>q</c> to |
7579 |
quit <c>mac-fdisk</c>. |
7580 |
</p> |
7581 |
|
7582 |
<note> |
7583 |
To make sure everything is ok, you should run mac-fdisk once more and check |
7584 |
whether all the partitions are there. If you don't see any of the partitions you |
7585 |
created, or the changes you made, you should reinitialize your partitions by |
7586 |
pressing <c>i</c> in mac-fdisk. Note that this will recreate the partition map |
7587 |
and thus remove all your partitions. |
7588 |
</note> |
7589 |
|
7590 |
<p> |
7591 |
Now that your partitions are created, you can now continue with <uri |
7592 |
link="#filesystems">Creating Filesystems</uri>. |
7593 |
</p> |
7594 |
|
7595 |
</body> |
7596 |
</section> |
7597 |
<section id="fdisk"> |
7598 |
<title>IBM pSeries, iSeries and OpenPower: using fdisk to Partition your Disk</title> |
7599 |
<subsection> |
7600 |
<body> |
7601 |
|
7602 |
<note> |
7603 |
If you are planning to use a RAID disk array for your Gentoo installation and |
7604 |
you are using POWER5-based hardware, you should now run <c>iprconfig</c> to |
7605 |
format the disks to Advanced Function format and create the disk array. You |
7606 |
should emerge <c>iprutils</c> after your install is complete. |
7607 |
</note> |
7608 |
|
7609 |
<p> |
7610 |
If you have an ipr-based SCSI adapter, you should start the ipr utilities now. |
7611 |
</p> |
7612 |
|
7613 |
<pre caption="Starting ipr utilities"> |
7614 |
# <i>/etc/init.d/iprinit start</i> |
7615 |
</pre> |
7616 |
|
7617 |
<p> |
7618 |
The following parts explain how to create the example partition layout |
7619 |
described previously, namely: |
7620 |
</p> |
7621 |
|
7622 |
<table> |
7623 |
<tr> |
7624 |
<th>Partition</th> |
7625 |
<th>Description</th> |
7626 |
</tr> |
7627 |
<tr> |
7628 |
<ti><path>/dev/sda1</path></ti> |
7629 |
<ti>PPC PReP Boot partition</ti> |
7630 |
</tr> |
7631 |
<tr> |
7632 |
<ti><path>/dev/sda2</path></ti> |
7633 |
<ti>Swap partition</ti> |
7634 |
</tr> |
7635 |
<tr> |
7636 |
<ti><path>/dev/sda3</path></ti> |
7637 |
<ti>Root partition</ti> |
7638 |
</tr> |
7639 |
</table> |
7640 |
|
7641 |
<p> |
7642 |
Change your partition layout according to your own preference. |
7643 |
</p> |
7644 |
|
7645 |
</body> |
7646 |
</subsection> |
7647 |
<subsection> |
7648 |
<title>Viewing the Current Partition Layout</title> |
7649 |
<body> |
7650 |
|
7651 |
<p> |
7652 |
<c>fdisk</c> is a popular and powerful tool to split your disk into |
7653 |
partitions. Fire up <c>fdisk</c> on your disk (in our example, we |
7654 |
use <path>/dev/sda</path>): |
7655 |
</p> |
7656 |
|
7657 |
<pre caption="Starting fdisk"> |
7658 |
# <i>fdisk /dev/sda</i> |
7659 |
</pre> |
7660 |
|
7661 |
<p> |
7662 |
Once in <c>fdisk</c>, you'll be greeted with a prompt that looks like |
7663 |
this: |
7664 |
</p> |
7665 |
|
7666 |
<pre caption="fdisk prompt"> |
7667 |
Command (m for help): |
7668 |
</pre> |
7669 |
|
7670 |
<p> |
7671 |
Type <c>p</c> to display your disk's current partition configuration: |
7672 |
</p> |
7673 |
|
7674 |
<pre caption="An example partition configuration"> |
7675 |
Command (m for help): p |
7676 |
|
7677 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
7678 |
141 heads, 63 sectors/track, 6761 cylinders |
7679 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
7680 |
|
7681 |
Device Boot Start End Blocks Id System |
7682 |
/dev/sda1 1 12 53266+ 83 Linux |
7683 |
/dev/sda2 13 233 981571+ 82 Linux swap |
7684 |
/dev/sda3 234 674 1958701+ 83 Linux |
7685 |
/dev/sda4 675 6761 27035410+ 5 Extended |
7686 |
/dev/sda5 675 2874 9771268+ 83 Linux |
7687 |
/dev/sda6 2875 2919 199836 83 Linux |
7688 |
/dev/sda7 2920 3008 395262 83 Linux |
7689 |
/dev/sda8 3009 6761 16668918 83 Linux |
7690 |
|
7691 |
Command (m for help): |
7692 |
</pre> |
7693 |
|
7694 |
<p> |
7695 |
This particular disk is configured to house six Linux filesystems |
7696 |
(each with a corresponding partition listed as "Linux") as well as a |
7697 |
swap partition (listed as "Linux swap"). |
7698 |
</p> |
7699 |
|
7700 |
</body> |
7701 |
</subsection> |
7702 |
<subsection> |
7703 |
<title>Removing all Partitions</title> |
7704 |
<body> |
7705 |
|
7706 |
<p> |
7707 |
We will first remove all existing partitions from the disk. Type |
7708 |
<c>d</c> to delete a partition. For instance, to delete an existing |
7709 |
<path>/dev/sda1</path>: |
7710 |
</p> |
7711 |
|
7712 |
<note> |
7713 |
If you don't want to delete all partitions just delete those you |
7714 |
want to delete. At this point the author recommends a backup of your |
7715 |
data to avoid the lose of it. |
7716 |
</note> |
7717 |
|
7718 |
<pre caption="Deleting a partition"> |
7719 |
Command (m for help): <i>d</i> |
7720 |
Partition number (1-4): <i>1</i> |
7721 |
</pre> |
7722 |
|
7723 |
<p> |
7724 |
The partition has been scheduled for deletion. It will no longer show up |
7725 |
if you type <c>p</c>, but it will not be erased until your changes have |
7726 |
been saved. If you made a mistake and want to abort without saving your |
7727 |
changes, type <c>q</c> immediately and hit enter and your partition will |
7728 |
not be deleted. |
7729 |
</p> |
7730 |
|
7731 |
<p> |
7732 |
Now, assuming that you do indeed want to wipe out all the partitions on |
7733 |
your system, repeatedly type <c>p</c> to print out a partition listing |
7734 |
and then type <c>d</c> and the number of the partition to delete it. |
7735 |
Eventually, you'll end up with a partition table with nothing in it: |
7736 |
</p> |
7737 |
|
7738 |
<pre caption="An empty partition table"> |
7739 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
7740 |
141 heads, 63 sectors/track, 6761 cylinders |
7741 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
7742 |
|
7743 |
Device Boot Start End Blocks Id System |
7744 |
|
7745 |
Command (m for help): |
7746 |
</pre> |
7747 |
|
7748 |
<p> |
7749 |
Now that the in-memory partition table is empty, we're ready to create |
7750 |
the partitions. We will use a default partitioning scheme as discussed |
7751 |
previously. Of course, don't follow these instructions to the letter if |
7752 |
you don't want the same partitioning scheme! |
7753 |
</p> |
7754 |
|
7755 |
</body> |
7756 |
</subsection> |
7757 |
<subsection> |
7758 |
<title>Creating the PPC PReP boot partition</title> |
7759 |
<body> |
7760 |
|
7761 |
<p> |
7762 |
We first create a small PReP boot partition. Type <c>n</c> to create a new |
7763 |
partition, then <c>p</c> to select a primary partition, followed by |
7764 |
<c>1</c> to select the first primary partition. When prompted for the |
7765 |
first cylinder, hit enter. When prompted for the last cylinder, type |
7766 |
<c>+7M</c> to create a partition 7 Mbyte in size. After you've done |
7767 |
this, type <c>t</c> to set the partition type, <c>1</c> to select the |
7768 |
partition you just created and then type in <c>41</c> to set the |
7769 |
partition type to "PPC PReP Boot". Finally, you'll need to mark the PReP |
7770 |
partition as bootable. |
7771 |
</p> |
7772 |
|
7773 |
<note> |
7774 |
The PReP partition has to be smaller than 8 MByte! |
7775 |
</note> |
7776 |
|
7777 |
<pre caption="Creating the PReP boot partition"> |
7778 |
Command (m for help): <i>p</i> |
7779 |
|
7780 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
7781 |
141 heads, 63 sectors/track, 6761 cylinders |
7782 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
7783 |
|
7784 |
Device Boot Start End Blocks Id System |
7785 |
|
7786 |
Command (m for help): <i>n</i> |
7787 |
Command action |
7788 |
e extended |
7789 |
p primary partition (1-4) |
7790 |
<i>p</i> |
7791 |
Partition number (1-4): <i>1</i> |
7792 |
First cylinder (1-6761, default 1): |
7793 |
Using default value 1 |
7794 |
Last cylinder or +size or +sizeM or +sizeK (1-6761, default |
7795 |
6761): <i>+8M</i> |
7796 |
|
7797 |
Command (m for help): <i>t</i> |
7798 |
Selected partition 1 |
7799 |
Hex code (type L to list codes): <i>41</i> |
7800 |
Changed system type of partition 1 to 41 (PPC PReP Boot) |
7801 |
|
7802 |
Command (m for help): <i>a</i> |
7803 |
Partition number (1-4): <i>1</i> |
7804 |
Command (m for help): |
7805 |
</pre> |
7806 |
|
7807 |
<p> |
7808 |
Now, when you type <c>p</c>, you should see the following partition information: |
7809 |
</p> |
7810 |
|
7811 |
<pre caption="Created boot partition"> |
7812 |
Command (m for help): <i>p</i> |
7813 |
|
7814 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
7815 |
141 heads, 63 sectors/track, 6761 cylinders |
7816 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
7817 |
|
7818 |
Device Boot Start End Blocks Id System |
7819 |
/dev/sda1 * 1 3 13293 41 PPC PReP Boot |
7820 |
|
7821 |
Command (m for help): |
7822 |
</pre> |
7823 |
</body> |
7824 |
</subsection> |
7825 |
<subsection> |
7826 |
<title>Creating the Swap Partition</title> |
7827 |
<body> |
7828 |
|
7829 |
<p> |
7830 |
Let's now create the swap partition. To do this, type <c>n</c> to create |
7831 |
a new partition, then <c>p</c> to tell fdisk that you want a primary |
7832 |
partition. Then type <c>2</c> to create the second primary partition, |
7833 |
<path>/dev/sda2</path> in our case. When prompted for the first |
7834 |
cylinder, hit enter. When prompted for the last cylinder, type |
7835 |
<c>+512M</c> to create a partition 512MB in size. After you've done |
7836 |
this, type <c>t</c> to set the partition type, <c>2</c> to select the |
7837 |
partition you just created and then type in <c>82</c> to set the |
7838 |
partition type to "Linux Swap". After completing these steps, typing |
7839 |
<c>p</c> should display a partition table that looks similar to this: |
7840 |
</p> |
7841 |
|
7842 |
<pre caption="Partition listing after creating a swap partition"> |
7843 |
Command (m for help): <i>p</i> |
7844 |
|
7845 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
7846 |
141 heads, 63 sectors/track, 6761 cylinders |
7847 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
7848 |
|
7849 |
Device Boot Start End Blocks Id System |
7850 |
/dev/sda1 1 3 13293 41 PPC PReP Boot |
7851 |
/dev/sda2 4 117 506331 82 Linux swap |
7852 |
|
7853 |
Command (m for help): |
7854 |
</pre> |
7855 |
|
7856 |
</body> |
7857 |
</subsection> |
7858 |
<subsection> |
7859 |
<title>Creating the Root Partition</title> |
7860 |
<body> |
7861 |
|
7862 |
<p> |
7863 |
Finally, let's create the root partition. To do this, type <c>n</c> to |
7864 |
create a new partition, then <c>p</c> to tell fdisk that you want a |
7865 |
primary partition. Then type <c>3</c> to create the third primary |
7866 |
partition, <path>/dev/sda3</path> in our case. When prompted for the |
7867 |
first cylinder, hit enter. When prompted for the last cylinder, hit |
7868 |
enter to create a partition that takes up the rest of the remaining |
7869 |
space on your disk. After completing these steps, typing <c>p</c> should |
7870 |
display a partition table that looks similar to this: |
7871 |
</p> |
7872 |
|
7873 |
<pre caption="Partition listing after creating the root partition"> |
7874 |
Command (m for help): p |
7875 |
|
7876 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
7877 |
141 heads, 63 sectors/track, 6761 cylinders |
7878 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
7879 |
|
7880 |
Device Boot Start End Blocks Id System |
7881 |
/dev/sda1 1 3 13293 41 PPC PReP Boot |
7882 |
/dev/sda2 4 117 506331 82 Linux swap |
7883 |
/dev/sda3 118 6761 29509326 83 Linux |
7884 |
|
7885 |
Command (m for help): |
7886 |
</pre> |
7887 |
</body> |
7888 |
</subsection> |
7889 |
<subsection> |
7890 |
<title>Saving the Partition Layout</title> |
7891 |
<body> |
7892 |
|
7893 |
<p> |
7894 |
To save the partition layout and exit <c>fdisk</c>, type <c>w</c>. |
7895 |
</p> |
7896 |
|
7897 |
<pre caption="Save and exit fdisk"> |
7898 |
Command (m for help): <i>w</i> |
7899 |
</pre> |
7900 |
|
7901 |
<p> |
7902 |
Now that your partitions are created, you can now continue with <uri |
7903 |
link="#filesystems">Creating Filesystems</uri>. |
7904 |
</p> |
7905 |
|
7906 |
</body> |
7907 |
</subsection> |
7908 |
</section> |
7909 |
<section id="filesystems"> |
7910 |
<title>Creating Filesystems</title> |
7911 |
<subsection> |
7912 |
<title>Introduction</title> |
7913 |
<body> |
7914 |
|
7915 |
<p> |
7916 |
Now that your partitions are created, it is time to place a filesystem on them. |
7917 |
If you don't care about what filesystem to choose and are happy with what we use |
7918 |
as default in this handbook, continue with <uri |
7919 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
7920 |
Otherwise read on to learn about the available filesystems... |
7921 |
</p> |
7922 |
|
7923 |
</body> |
7924 |
</subsection> |
7925 |
<subsection> |
7926 |
<title>Filesystems?</title> |
7927 |
<body> |
7928 |
|
7929 |
<note> |
7930 |
Several filesystems are available. ext2, ext3 and ReiserFS support is built in |
7931 |
the Installation CD kernels. JFS and XFS support is available through kernel |
7932 |
modules. |
7933 |
</note> |
7934 |
|
7935 |
<p> |
7936 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
7937 |
journaling, which means that routine ext2 filesystem checks at startup time can |
7938 |
be quite time-consuming. There is now quite a selection of newer-generation |
7939 |
journaled filesystems that can be checked for consistency very quickly and are |
7940 |
thus generally preferred over their non-journaled counterparts. Journaled |
7941 |
filesystems prevent long delays when you boot your system and your filesystem |
7942 |
happens to be in an inconsistent state. |
7943 |
</p> |
7944 |
|
7945 |
<p> |
7946 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
7947 |
journaling for fast recovery in addition to other enhanced journaling modes like |
7948 |
full data and ordered data journaling. It uses an HTree index that enables high |
7949 |
performance in almost all situations. In short, ext3 is a very good and reliable |
7950 |
filesystem. |
7951 |
</p> |
7952 |
|
7953 |
<p> |
7954 |
<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall |
7955 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
7956 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
7957 |
extremely well and has metadata journaling. ReiserFS is solid and usable as |
7958 |
both general-purpose filesystem and for extreme cases such as the creation of |
7959 |
large filesystems, very large files and directories containing tens of |
7960 |
thousands of small files. |
7961 |
</p> |
7962 |
|
7963 |
<p> |
7964 |
<b>XFS</b> is a filesystem with metadata journaling that is fully supported |
7965 |
under Gentoo Linux's xfs-sources kernel. It comes with a robust feature-set and |
7966 |
is optimized for scalability. We only recommend using this filesystem on Linux |
7967 |
systems with high-end SCSI and/or fibre channel storage and a uninterruptible |
7968 |
power supply. Because XFS aggressively caches in-transit data in RAM, improperly |
7969 |
designed programs (those that don't take proper precautions when writing files |
7970 |
to disk and there are quite a few of them) can lose a good deal of data if the |
7971 |
system goes down unexpectedly. |
7972 |
</p> |
7973 |
|
7974 |
<p> |
7975 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
7976 |
become production-ready. |
7977 |
</p> |
7978 |
|
7979 |
</body> |
7980 |
</subsection> |
7981 |
<subsection id="filesystems-apply"> |
7982 |
<title>Applying a Filesystem to a Partition</title> |
7983 |
<body> |
7984 |
|
7985 |
<p> |
7986 |
To create a filesystem on a partition or volume, there are tools available for |
7987 |
each possible filesystem: |
7988 |
</p> |
7989 |
|
7990 |
<table> |
7991 |
<tr> |
7992 |
<th>Filesystem</th> |
7993 |
<th>Creation Command</th> |
7994 |
</tr> |
7995 |
<tr> |
7996 |
<ti>ext2</ti> |
7997 |
<ti><c>mke2fs</c></ti> |
7998 |
</tr> |
7999 |
<tr> |
8000 |
<ti>ext3</ti> |
8001 |
<ti><c>mke2fs -j</c></ti> |
8002 |
</tr> |
8003 |
<tr> |
8004 |
<ti>reiserfs</ti> |
8005 |
<ti><c>mkreiserfs</c></ti> |
8006 |
</tr> |
8007 |
<tr> |
8008 |
<ti>xfs</ti> |
8009 |
<ti><c>mkfs.xfs</c></ti> |
8010 |
</tr> |
8011 |
<tr> |
8012 |
<ti>jfs</ti> |
8013 |
<ti><c>mkfs.jfs</c></ti> |
8014 |
</tr> |
8015 |
</table> |
8016 |
|
8017 |
<p> |
8018 |
For instance, to have the root partition (<path>/dev/sda4</path> in our example) |
8019 |
in ext3 (as in our example), you would use: |
8020 |
</p> |
8021 |
|
8022 |
<pre caption="Applying a filesystem on a partition"> |
8023 |
# <i>mke2fs -j /dev/sda4</i> |
8024 |
</pre> |
8025 |
|
8026 |
<p> |
8027 |
Now create the filesystems on your newly created partitions (or logical |
8028 |
volumes). |
8029 |
</p> |
8030 |
|
8031 |
<impo> |
8032 |
If you choose to use ReiserFS for <path>/</path>, do not change its default |
8033 |
block size if you will also be using <c>yaboot</c> as your bootloader, as |
8034 |
explained in <uri link="?part=1&chap=10">Configuring the Bootloader</uri>. |
8035 |
</impo> |
8036 |
|
8037 |
</body> |
8038 |
</subsection> |
8039 |
<subsection> |
8040 |
<title>Activating the Swap Partition</title> |
8041 |
<body> |
8042 |
|
8043 |
<p> |
8044 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
8045 |
</p> |
8046 |
|
8047 |
<pre caption="Creating a Swap signature"> |
8048 |
# <i>mkswap /dev/sda3</i> |
8049 |
</pre> |
8050 |
|
8051 |
<p> |
8052 |
To activate the swap partition, use <c>swapon</c>: |
8053 |
</p> |
8054 |
|
8055 |
<pre caption="Activating the swap partition"> |
8056 |
# <i>swapon /dev/sda3</i> |
8057 |
</pre> |
8058 |
|
8059 |
<p> |
8060 |
Create and activate the swap with the commands mentioned above. |
8061 |
</p> |
8062 |
|
8063 |
</body> |
8064 |
</subsection> |
8065 |
</section> |
8066 |
<section> |
8067 |
<title>Mounting</title> |
8068 |
<body> |
8069 |
|
8070 |
<p> |
8071 |
Now that your partitions are initialized and are housing a filesystem, it is |
8072 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
8073 |
create the necessary mount directories for every partition you created. As an |
8074 |
example we create a mount point and mount the root partition: |
8075 |
</p> |
8076 |
|
8077 |
<pre caption="Mounting partitions"> |
8078 |
# <i>mkdir /mnt/gentoo</i> |
8079 |
# <i>mount /dev/sda4 /mnt/gentoo</i> |
8080 |
</pre> |
8081 |
|
8082 |
<note> |
8083 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
8084 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
8085 |
also holds for <path>/var/tmp</path>. |
8086 |
</note> |
8087 |
|
8088 |
<p> |
8089 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
8090 |
Installation Files</uri>. |
8091 |
</p> |
8092 |
|
8093 |
</body> |
8094 |
</section> |
8095 |
</sections> |
8096 |
|
8097 |
|
8098 |
|
8099 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc64-kernel.xml |
8100 |
|
8101 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc64-kernel.xml?rev=1.1&view=markup |
8102 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc64-kernel.xml?rev=1.1&content-type=text/plain |
8103 |
|
8104 |
Index: hb-install-ppc64-kernel.xml |
8105 |
=================================================================== |
8106 |
<?xml version='1.0' encoding='UTF-8'?> |
8107 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
8108 |
|
8109 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
8110 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
8111 |
|
8112 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc64-kernel.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
8113 |
|
8114 |
<sections> |
8115 |
|
8116 |
<version>8.3</version> |
8117 |
<date>2007-07-29</date> |
8118 |
|
8119 |
<section> |
8120 |
<title>Timezone</title> |
8121 |
<body> |
8122 |
|
8123 |
<p> |
8124 |
You first need to select your timezone so that your system knows where it is |
8125 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
8126 |
it to <path>/etc/localtime</path>. Please avoid the |
8127 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
8128 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact |
8129 |
GMT+8. |
8130 |
</p> |
8131 |
|
8132 |
<pre caption="Setting the timezone information"> |
8133 |
# <i>ls /usr/share/zoneinfo</i> |
8134 |
<comment>(Suppose you want to use GMT)</comment> |
8135 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
8136 |
</pre> |
8137 |
|
8138 |
</body> |
8139 |
</section> |
8140 |
<section> |
8141 |
<title>Installing the Sources</title> |
8142 |
<subsection> |
8143 |
<title>Choosing a Kernel</title> |
8144 |
<body> |
8145 |
|
8146 |
<p> |
8147 |
The core around which all distributions are built is the Linux kernel. |
8148 |
It is the layer between the user programs and your system hardware. |
8149 |
Gentoo provides its users several possible kernel sources. A full |
8150 |
listing with description is available at the <uri |
8151 |
link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>. |
8152 |
</p> |
8153 |
|
8154 |
<p> |
8155 |
For PPC64 you should use <c>gentoo-sources</c>. |
8156 |
</p> |
8157 |
|
8158 |
<pre caption="Installing a kernel source"> |
8159 |
# <i>emerge gentoo-sources</i> |
8160 |
</pre> |
8161 |
|
8162 |
<p> |
8163 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
8164 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
8165 |
kernel source points to <c>gentoo-sources-<keyval id="kernel-version"/></c>. |
8166 |
Your version may be different, so keep this in mind. |
8167 |
</p> |
8168 |
|
8169 |
<pre caption="Viewing the kernel source symlink"> |
8170 |
# <i>ls -l /usr/src/linux</i> |
8171 |
lrwxrwxrwx 1 root root 12 Aug 10 11:04 /usr/src/linux -> linux-<keyval id="kernel-version"/> |
8172 |
</pre> |
8173 |
|
8174 |
<p> |
8175 |
Now it is time to configure and compile your kernel source. There is the |
8176 |
ability to use "genkernel" which would create a generic kernel like the |
8177 |
ones used on the installation CDs, but it is not fully functional for PPC64 at |
8178 |
the moment. |
8179 |
</p> |
8180 |
|
8181 |
<p> |
8182 |
Continue now with <uri link="#manual">Manual Configuration</uri>. |
8183 |
</p> |
8184 |
|
8185 |
</body> |
8186 |
</subsection> |
8187 |
</section> |
8188 |
<section id="manual"> |
8189 |
<title>Manual Configuration</title> |
8190 |
<subsection> |
8191 |
<title>Introduction</title> |
8192 |
<body> |
8193 |
|
8194 |
<p> |
8195 |
Manually configuring a kernel is often seen as the most difficult procedure a |
8196 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
8197 |
couple of kernels you don't even remember that it was difficult ;) |
8198 |
</p> |
8199 |
|
8200 |
<p> |
8201 |
However, one thing <e>is</e> true: you must know your system when you |
8202 |
configuring a kernel manually. Most information can be gathered by emerging |
8203 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
8204 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
8205 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
8206 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
8207 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
8208 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
8209 |
uses (it might provide you with a nice hint on what to enable). |
8210 |
</p> |
8211 |
|
8212 |
<pre caption="Invoking menuconfig"> |
8213 |
# <i>cd /usr/src/linux</i> |
8214 |
<comment>Important: In case you are in 32-bit userland, you must edit the top |
8215 |
level Makefile in /usr/src/linux and change the CROSS_COMPILE option to |
8216 |
CROSS_COMPILE ?= powerpc64-unknown-linux-gnu-. You must do this before you run |
8217 |
make menuconfig or it may result in kernel compilation problems.</comment> |
8218 |
# <i>make menuconfig</i> |
8219 |
</pre> |
8220 |
|
8221 |
<p> |
8222 |
You will be greeted with several configuration sections. We'll first |
8223 |
list some options you must activate (otherwise Gentoo will not function, |
8224 |
or not function properly without additional tweaks). |
8225 |
</p> |
8226 |
|
8227 |
</body> |
8228 |
</subsection> |
8229 |
<subsection> |
8230 |
<title>Activating Required Options</title> |
8231 |
<body> |
8232 |
|
8233 |
<p> |
8234 |
First of all, activate the use of development and experimental |
8235 |
code/drivers. You need this, otherwise some very important code/drivers |
8236 |
won't show up: |
8237 |
</p> |
8238 |
|
8239 |
<pre caption="Selecting experimental code/drivers"> |
8240 |
Code maturity level options ---> |
8241 |
[*] Prompt for development and/or incomplete code/drivers |
8242 |
</pre> |
8243 |
|
8244 |
<p> |
8245 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
8246 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
8247 |
able to mount your partitions. Also select <c>Virtual memory</c>, <c>/proc file |
8248 |
system</c>, and <c>/dev/pts file system for Unix98 PTYs</c>: |
8249 |
</p> |
8250 |
|
8251 |
<pre caption="Selecting necessary file systems"> |
8252 |
File systems ---> |
8253 |
[*] Virtual memory file system support (former shm fs) |
8254 |
[*] /proc file system support |
8255 |
[*] /dev/pts file system for Unix98 PTYs |
8256 |
|
8257 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
8258 |
<*> Reiserfs support |
8259 |
<*> Ext3 journalling file system support |
8260 |
<*> JFS filesystem support |
8261 |
<*> Second extended fs support |
8262 |
<*> XFS filesystem support |
8263 |
</pre> |
8264 |
|
8265 |
<note> |
8266 |
You will find some of the mentioned options under <c>Pseudo |
8267 |
filesystems</c> which is a subpart of <c>File systems</c>. |
8268 |
</note> |
8269 |
|
8270 |
<p> |
8271 |
If you are using PPPoE to connect to the Internet or you are using a |
8272 |
dial-up modem, you will need the following options in the kernel (you |
8273 |
will find the mentioned options under <c>Networking support</c> which is |
8274 |
a subpart of <c>Device Drivers</c>): |
8275 |
</p> |
8276 |
|
8277 |
<pre caption="Selecting PPPoE necessary drivers"> |
8278 |
Network device support ---> |
8279 |
<*> PPP (point-to-point protocol) support |
8280 |
<*> PPP support for async serial ports |
8281 |
<*> PPP support for sync tty ports |
8282 |
</pre> |
8283 |
|
8284 |
<p> |
8285 |
The two compression options won't harm but are not definitely needed, neither |
8286 |
does the <c>PPP over Ethernet</c> option, that might only be used by <c>ppp</c> |
8287 |
when configured to do kernel mode PPPoE. |
8288 |
</p> |
8289 |
|
8290 |
<p> |
8291 |
If you require it, don't forget to include support in the kernel for your |
8292 |
ethernet card. |
8293 |
</p> |
8294 |
|
8295 |
<p> |
8296 |
Disable ADB raw keycodes: |
8297 |
</p> |
8298 |
|
8299 |
<pre caption="Disabling ADB raw keycodes"> |
8300 |
Macintosh Device Drivers ---> |
8301 |
[ ] Support for ADB raw keycodes |
8302 |
</pre> |
8303 |
|
8304 |
<p> |
8305 |
When you're done configuring your kernel, continue with <uri |
8306 |
link="#compiling">Compiling and Installing</uri>. |
8307 |
</p> |
8308 |
|
8309 |
</body> |
8310 |
</subsection> |
8311 |
<subsection id="compiling"> |
8312 |
<title>Compiling and Installing</title> |
8313 |
<body> |
8314 |
|
8315 |
<p> |
8316 |
Now that your kernel is configured, it is time to compile and install it. Exit |
8317 |
the configuration and start the compilation process: |
8318 |
</p> |
8319 |
|
8320 |
<pre caption="Compiling the kernel"> |
8321 |
# <i>make && make modules_install</i> |
8322 |
</pre> |
8323 |
|
8324 |
<p> |
8325 |
When the kernel has finished compiling, copy the kernel image to |
8326 |
<path>/boot</path>. Remember to replace <path><kernel-version></path> |
8327 |
with your actual kernel version: |
8328 |
</p> |
8329 |
|
8330 |
<pre caption="Installing the kernel"> |
8331 |
# <i>cp vmlinux /boot/<kernel-version></i> |
8332 |
</pre> |
8333 |
|
8334 |
<p> |
8335 |
Now continue with <uri link="#kernel_modules">Configuring the Modules</uri>. |
8336 |
</p> |
8337 |
|
8338 |
</body> |
8339 |
</subsection> |
8340 |
</section> |
8341 |
<section id="kernel_modules"> |
8342 |
<title>Configuring the Modules</title> |
8343 |
<body> |
8344 |
|
8345 |
<p> |
8346 |
You should list the modules you want automatically loaded in |
8347 |
<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra |
8348 |
options to the modules too if you want. |
8349 |
</p> |
8350 |
|
8351 |
<p> |
8352 |
To view all available modules, run the following command: |
8353 |
</p> |
8354 |
|
8355 |
<pre caption="Viewing all available modules"> |
8356 |
# <i>modprobe -l</i> |
8357 |
</pre> |
8358 |
|
8359 |
<p> |
8360 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
8361 |
<path>kernel-2.6</path> file and enter the module name in it. |
8362 |
</p> |
8363 |
|
8364 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
8365 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
8366 |
</pre> |
8367 |
|
8368 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
8369 |
3c59x |
8370 |
</pre> |
8371 |
|
8372 |
<p> |
8373 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
8374 |
your System</uri>. |
8375 |
</p> |
8376 |
|
8377 |
</body> |
8378 |
</section> |
8379 |
</sections> |
8380 |
|
8381 |
|
8382 |
|
8383 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc64-medium.xml |
8384 |
|
8385 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc64-medium.xml?rev=1.1&view=markup |
8386 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc64-medium.xml?rev=1.1&content-type=text/plain |
8387 |
|
8388 |
Index: hb-install-ppc64-medium.xml |
8389 |
=================================================================== |
8390 |
<?xml version='1.0' encoding='UTF-8'?> |
8391 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
8392 |
|
8393 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
8394 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
8395 |
|
8396 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc64-medium.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
8397 |
|
8398 |
<sections> |
8399 |
|
8400 |
<version>8.1</version> |
8401 |
<date>2007-06-29</date> |
8402 |
|
8403 |
<section> |
8404 |
<title>Hardware Requirements</title> |
8405 |
<subsection> |
8406 |
<title>Introduction</title> |
8407 |
<body> |
8408 |
|
8409 |
<p> |
8410 |
Before we start, we first list what hardware requirements you need to |
8411 |
successfully install Gentoo on your box. |
8412 |
</p> |
8413 |
|
8414 |
</body> |
8415 |
</subsection> |
8416 |
<subsection> |
8417 |
<title>Hardware Requirements</title> |
8418 |
<body> |
8419 |
|
8420 |
<table> |
8421 |
<tr> |
8422 |
<th>CPU</th> |
8423 |
<ti>Any PowerPC64 CPU</ti> |
8424 |
</tr> |
8425 |
<tr> |
8426 |
<th>Systems</th> |
8427 |
<ti> |
8428 |
IBM RS/6000s, Power Macintosh G5, iMac G5, IBP pSeries and IBM OpenPower |
8429 |
</ti> |
8430 |
</tr> |
8431 |
<tr> |
8432 |
<th>Memory</th> |
8433 |
<ti>64 MB</ti> |
8434 |
</tr> |
8435 |
<tr> |
8436 |
<th>Diskspace</th> |
8437 |
<ti>1.5 GB (excluding swap space)</ti> |
8438 |
</tr> |
8439 |
<tr> |
8440 |
<th>Swap space</th> |
8441 |
<ti>At least 256 MB</ti> |
8442 |
</tr> |
8443 |
</table> |
8444 |
|
8445 |
<p> |
8446 |
For a full list of supported systems, please go to |
8447 |
<uri>http://www.linuxppc64.org/hardware.shtml</uri>. |
8448 |
</p> |
8449 |
|
8450 |
</body> |
8451 |
</subsection> |
8452 |
</section> |
8453 |
<!-- Copy/paste from hb-install-x86-medium.xml, with s/x86/ppc64/ --> |
8454 |
<!-- START --> |
8455 |
<section> |
8456 |
<title>The Gentoo Universal Installation CD</title> |
8457 |
<subsection> |
8458 |
<title>Introduction</title> |
8459 |
<body> |
8460 |
|
8461 |
<p> |
8462 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
8463 |
Such a tarball is an archive that contains a minimal environment from |
8464 |
which you can succesfully install Gentoo Linux onto your system. |
8465 |
</p> |
8466 |
|
8467 |
<p> |
8468 |
Installations using a stage1 or stage2 tarball file are not documented in the |
8469 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
8470 |
FAQ</uri> on these matters. |
8471 |
</p> |
8472 |
|
8473 |
</body> |
8474 |
</subsection> |
8475 |
<subsection> |
8476 |
<title>Gentoo Universal Installation CD</title> |
8477 |
<body> |
8478 |
|
8479 |
<p> |
8480 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
8481 |
environment. It allows you to boot Linux from the CD. During the boot process |
8482 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
8483 |
Installation CDs are maintained by Gentoo developers. |
8484 |
</p> |
8485 |
|
8486 |
<p> |
8487 |
There currently are two Installation CDs available: |
8488 |
</p> |
8489 |
|
8490 |
<ul> |
8491 |
<li> |
8492 |
The Universal Installation CD contains everything you need to install |
8493 |
Gentoo. It provides stage3 files for common architectures, source code |
8494 |
for the extra applications you need to choose from and, of course, the |
8495 |
installation instructions for your architecture. |
8496 |
</li> |
8497 |
<li> |
8498 |
The Minimal Installation CD contains only a minimal environment that allows |
8499 |
you to boot up and configure your network so you can connect to the |
8500 |
Internet. It does not contain any additional files and cannot be used |
8501 |
during the current installation approach. |
8502 |
</li> |
8503 |
</ul> |
8504 |
|
8505 |
<p> |
8506 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
8507 |
additional resource that you can exploit during the installation of your Gentoo |
8508 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
8509 |
you to easily and quickly install additional applications immediately after the |
8510 |
Gentoo installation and right before you update your Portage tree. |
8511 |
</p> |
8512 |
|
8513 |
<p> |
8514 |
The use of the Package CD is covered later in this document. |
8515 |
</p> |
8516 |
|
8517 |
</body> |
8518 |
</subsection> |
8519 |
<subsection> |
8520 |
<title>Choosing a userland</title> |
8521 |
<body> |
8522 |
|
8523 |
<p> |
8524 |
On PPC64, the kernel is 64-bit and the <e>userland</e> can be 32-bit or 64-bit. The |
8525 |
userland is basically the applications you are running, such as |
8526 |
<c>bash</c> or <c>mozilla-firefox</c>. They can be compiled and run in either |
8527 |
64-bit or 32-bit modes. The Gentoo/PPC64 team provides both 32-bit and 64-bit |
8528 |
userlands, so which one should you use? |
8529 |
</p> |
8530 |
|
8531 |
<p> |
8532 |
You may have heard that 64-bit applications are better, but in fact, 32-bit |
8533 |
applications take up slightly less memory and often run a little bit faster than |
8534 |
64-bit applications. |
8535 |
</p> |
8536 |
|
8537 |
<p> |
8538 |
You really only need 64-bit applications when you need more memory than a 32-bit |
8539 |
userland allows, or if you do a lot of 64-bit number crunching. If you run |
8540 |
applications that require more than 4GB of memory or you run scientific |
8541 |
applications, you should choose the 64-bit userland. Otherwise, choose the |
8542 |
32-bit userland, as it is recommended by the Gentoo/PPC64 developers. |
8543 |
</p> |
8544 |
|
8545 |
<p> |
8546 |
Additionally, the 32-bit userland has been available in Portage longer than the |
8547 |
64-bit userland has. This means that there are more applications tested in the |
8548 |
32-bit userland that just work "out of the box." Many applications compiled for |
8549 |
the 64-bit userland may be just as stable as the 32-bit version, but they |
8550 |
haven't been tested yet. Though testing isn't difficult to do, it can be |
8551 |
annoying and time consuming if you want to use many untested 64-bit |
8552 |
applications. Also, some programs just won't run in the 64-bit userland until |
8553 |
their code is fixed, such as OpenOffice. |
8554 |
</p> |
8555 |
|
8556 |
<p> |
8557 |
The Gentoo/PPC64 team provides stages and Package CDs for both 32-bit and 64-bit |
8558 |
userlands, so no matter which one you choose, you'll be able to successfully |
8559 |
install Gentoo and get a full system up and running with minimal fuss. |
8560 |
</p> |
8561 |
|
8562 |
</body> |
8563 |
</subsection> |
8564 |
</section> |
8565 |
<!-- STOP --> |
8566 |
<section> |
8567 |
<title>Download, Burn and Boot a Gentoo Installation CD</title> |
8568 |
<subsection> |
8569 |
<title>Downloading and Burning the Installation CDs</title> |
8570 |
<body> |
8571 |
|
8572 |
<p> |
8573 |
You can download the Universal Installation CD (and, if you want to, the |
8574 |
Packages CD as well) from one of our <uri |
8575 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located in |
8576 |
the <path><keyval id="release-dir"/>installcd</path> directory; the Package CDs |
8577 |
are located in the <path><keyval id="release-dir"/>packagecd</path> directory. |
8578 |
</p> |
8579 |
|
8580 |
<p> |
8581 |
Inside those directories you'll find ISO-files. Those are full CD images which |
8582 |
you can write on a CD-R. |
8583 |
</p> |
8584 |
|
8585 |
<p> |
8586 |
After downloading the file, you can verify its integrity to see if it is |
8587 |
corrupted or not: |
8588 |
</p> |
8589 |
|
8590 |
<ul> |
8591 |
<li> |
8592 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
8593 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
8594 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows). How |
8595 |
to verify MD5 checksums with Mac OS X is described in the <uri |
8596 |
link="/doc/en/gentoo-ppc-faq.xml#doc_chap1">Gentoo PPC FAQ</uri>. |
8597 |
</li> |
8598 |
<li> |
8599 |
You can verify the cryptographic signature that we provide. You need to |
8600 |
obtain the public key we use (0x17072058) before you proceed though. |
8601 |
</li> |
8602 |
</ul> |
8603 |
|
8604 |
<p> |
8605 |
To fetch our public key using the GnuPG application, run the following command: |
8606 |
</p> |
8607 |
|
8608 |
<pre caption="Obtaining the public key"> |
8609 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 0x17072058</i> |
8610 |
</pre> |
8611 |
|
8612 |
<p> |
8613 |
Now verify the signature: |
8614 |
</p> |
8615 |
|
8616 |
<pre caption="Verify the cryptographic signature"> |
8617 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
8618 |
</pre> |
8619 |
|
8620 |
<p> |
8621 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
8622 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
8623 |
<c>K3B</c> here; more information can be found in our <uri |
8624 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
8625 |
</p> |
8626 |
|
8627 |
<ul> |
8628 |
<li> |
8629 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
8630 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
8631 |
path). |
8632 |
</li> |
8633 |
<li> |
8634 |
With K3B, select <c>Tools</c> > <c>Burn CD Image</c>. Then you can locate |
8635 |
your ISO file within the 'Image to Burn' area. Finally click <c>Start</c>. |
8636 |
</li> |
8637 |
</ul> |
8638 |
|
8639 |
</body> |
8640 |
</subsection> |
8641 |
<subsection> |
8642 |
<title>Booting the Installation CD on an Apple</title> |
8643 |
<body> |
8644 |
|
8645 |
<p> |
8646 |
Please check the <path>README.kernel</path> on the Installation CD for the |
8647 |
latest information on how to boot various kernels and getting hardware support. |
8648 |
</p> |
8649 |
|
8650 |
<p> |
8651 |
Place the Installation CD in the CD-ROM and reboot the system. Hold down the |
8652 |
'C' key at bootup. You will be greeted by a friendly welcome message and a |
8653 |
<e>boot:</e> prompt at the bottom of the screen. |
8654 |
</p> |
8655 |
|
8656 |
<p> |
8657 |
You are also able to tweak some kernel options at this prompt. The following |
8658 |
table lists the available boot options you can add: |
8659 |
</p> |
8660 |
|
8661 |
<table> |
8662 |
<tr> |
8663 |
<th>Boot Option</th> |
8664 |
<th>Description</th> |
8665 |
</tr> |
8666 |
<tr> |
8667 |
<ti><c>video</c></ti> |
8668 |
<ti> |
8669 |
This option takes one of the following vendor-specific tags: |
8670 |
<c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, <c>aty128</c>, <c>nvidiafb</c> |
8671 |
or <c>ofonly</c>. You can follow this tag with the resolution and |
8672 |
refreshrate you want to use. For instance |
8673 |
<c>video=radeonfb:1280x1024@75</c>. If you are uncertain what to choose, |
8674 |
<c>ofonly</c> will most certainly work. |
8675 |
</ti> |
8676 |
</tr> |
8677 |
<tr> |
8678 |
<ti><c>nol3</c></ti> |
8679 |
<ti> |
8680 |
Disables level 3 cache on some powerbooks (needed for at least the 17") |
8681 |
</ti> |
8682 |
</tr> |
8683 |
<tr> |
8684 |
<ti><c>debug</c></ti> |
8685 |
<ti> |
8686 |
Enables verbose booting, spawns an initrd shell that can be used to debug |
8687 |
the Installation CD |
8688 |
</ti> |
8689 |
</tr> |
8690 |
<tr> |
8691 |
<ti><c>sleep=X</c></ti> |
8692 |
<ti> |
8693 |
Wait X seconds before continuing; this can be needed by some very old SCSI |
8694 |
CD-ROMs which don't speed up the CD quick enough |
8695 |
</ti> |
8696 |
</tr> |
8697 |
<tr> |
8698 |
<ti><c>bootfrom=X</c></ti> |
8699 |
<ti> |
8700 |
Boot from a different device |
8701 |
</ti> |
8702 |
</tr> |
8703 |
</table> |
8704 |
|
8705 |
<p> |
8706 |
At this prompt, hit enter, and a complete Gentoo Linux environment will be |
8707 |
loaded from the CD. Continue with <uri link="#booted">And When You're |
8708 |
Booted...</uri>. |
8709 |
</p> |
8710 |
|
8711 |
</body> |
8712 |
</subsection> |
8713 |
<subsection> |
8714 |
<title>Booting the Installation CD on an IBM pSeries, OpenPower and Power5 |
8715 |
iSeries servers</title> |
8716 |
<body> |
8717 |
|
8718 |
<p> |
8719 |
Please check the <path>README.kernel</path> on the Installation CD for the |
8720 |
latest information on how to boot various kernels and getting hardware support. |
8721 |
</p> |
8722 |
|
8723 |
<p> |
8724 |
Most modern pSeries servers can boot from the CDROM drive through SMS ('1' when |
8725 |
the “IBM IBM IBM” messages flash across the console). On some older pSeries |
8726 |
boxes, sometimes the cds might not autoboot. You might have to set up your |
8727 |
cdrom as a bootable device in the multi-boot menu. (F1 at startup) The other |
8728 |
option is to jump into OF and do it from there: |
8729 |
</p> |
8730 |
|
8731 |
<ol> |
8732 |
<li> |
8733 |
Boot into OF (this is 8 from the serial cons or F8 from a graphics |
8734 |
cons, start hitting the key when you see the keyboard mouse etc etc |
8735 |
messages. |
8736 |
</li> |
8737 |
<li>Run the command 0> boot cdrom:1,yaboot</li> |
8738 |
<li>Stand back and enjoy!</li> |
8739 |
</ol> |
8740 |
|
8741 |
</body> |
8742 |
</subsection> |
8743 |
<subsection id="booted"> |
8744 |
<title>And When You're Booted...</title> |
8745 |
<body> |
8746 |
|
8747 |
<p> |
8748 |
You will be greeted by a root ("#") prompt on the current console. You can also |
8749 |
switch to other consoles by pressing Alt-fn-F2, Alt-fn-F3 and Alt-fn-F4. Get |
8750 |
back to the one you started on by pressing Alt-fn-F1. |
8751 |
</p> |
8752 |
|
8753 |
<p> |
8754 |
If you are installing Gentoo on a system with a non-US keyboard, use |
8755 |
<c>loadkeys</c> to load the keymap for your keyboard. To list the available |
8756 |
keymaps, execute <c>ls /usr/share/keymaps/i386</c>. |
8757 |
</p> |
8758 |
|
8759 |
<pre caption="Listing available keymaps"> |
8760 |
<comment>(PPC uses x86 keymaps on most systems. The mac/ppc keymaps provided |
8761 |
on the Installation CD are ADB keymaps and unusable with the |
8762 |
Installation CD kernel)</comment> |
8763 |
# <i>ls /usr/share/keymaps/i386</i> |
8764 |
</pre> |
8765 |
|
8766 |
<p> |
8767 |
Now load the keymap of your choice: |
8768 |
</p> |
8769 |
|
8770 |
<pre caption="Loading a keymap"> |
8771 |
# <i>loadkeys be-latin1</i> |
8772 |
</pre> |
8773 |
|
8774 |
<p> |
8775 |
Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
8776 |
</p> |
8777 |
|
8778 |
</body> |
8779 |
</subsection> |
8780 |
<subsection id="hardware"> |
8781 |
<title>Extra Hardware Configuration</title> |
8782 |
<body> |
8783 |
|
8784 |
<p> |
8785 |
When the Installation CD boots, it tries to detect all your hardware devices and |
8786 |
loads the appropriate kernel modules to support your hardware. In the vast |
8787 |
majority of cases, it does a very good job. However, in some cases it may not |
8788 |
auto-load the kernel modules you need. If the PCI auto-detection missed some of |
8789 |
your system's hardware, you will have to load the appropriate kernel modules |
8790 |
manually. |
8791 |
</p> |
8792 |
|
8793 |
<p> |
8794 |
In the next example we try to load the <c>8139too</c> module (support for |
8795 |
certain kinds of network interfaces): |
8796 |
</p> |
8797 |
|
8798 |
<pre caption="Loading kernel modules"> |
8799 |
# <i>modprobe 8139too</i> |
8800 |
</pre> |
8801 |
|
8802 |
</body> |
8803 |
</subsection> |
8804 |
<subsection> |
8805 |
<title>Optional: Tweaking Hard Disk Performance</title> |
8806 |
<body> |
8807 |
|
8808 |
<p> |
8809 |
If you are an advanced user, you might want to tweak the IDE hard disk |
8810 |
performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
8811 |
test the performance of your disk (execute it several times to get a |
8812 |
more precise impression): |
8813 |
</p> |
8814 |
|
8815 |
<pre caption="Testing disk performance"> |
8816 |
# <i>hdparm -tT /dev/hda</i> |
8817 |
</pre> |
8818 |
|
8819 |
<p> |
8820 |
To tweak, you can use any of the following examples (or experiment |
8821 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
8822 |
disk): |
8823 |
</p> |
8824 |
|
8825 |
<pre caption="Tweaking hard disk performance"> |
8826 |
<comment>Activate DMA:</comment> |
8827 |
# <i>hdparm -d 1 /dev/hda</i> |
8828 |
<comment>Activate DMA + Safe Performance-enhancing Options:</comment> |
8829 |
# <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
8830 |
</pre> |
8831 |
|
8832 |
</body> |
8833 |
</subsection> |
8834 |
<subsection id="useraccounts"> |
8835 |
<title>Optional: User Accounts</title> |
8836 |
<body> |
8837 |
|
8838 |
<p> |
8839 |
If you plan on giving other people access to your installation |
8840 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
8841 |
security reasons), you need to create the necessary user accounts and change |
8842 |
the root password. |
8843 |
</p> |
8844 |
|
8845 |
<p> |
8846 |
To change the root password, use the <c>passwd</c> utility: |
8847 |
</p> |
8848 |
|
8849 |
<pre caption="Changing the root password"> |
8850 |
# <i>passwd</i> |
8851 |
New password: <comment>(Enter your new password)</comment> |
8852 |
Re-enter password: <comment>(Re-enter your password)</comment> |
8853 |
</pre> |
8854 |
|
8855 |
<p> |
8856 |
To create a user account, we first enter their credentials, followed by |
8857 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
8858 |
In the next example, we create a user called "john". |
8859 |
</p> |
8860 |
|
8861 |
<pre caption="Creating a user account"> |
8862 |
# <i>useradd -m -G users john</i> |
8863 |
# <i>passwd john</i> |
8864 |
New password: <comment>(Enter john's password)</comment> |
8865 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
8866 |
</pre> |
8867 |
|
8868 |
<p> |
8869 |
You can change your user id from root to the newly created user by using |
8870 |
<c>su</c>: |
8871 |
</p> |
8872 |
|
8873 |
<pre caption="Changing user id"> |
8874 |
# <i>su - john</i> |
8875 |
</pre> |
8876 |
|
8877 |
</body> |
8878 |
</subsection> |
8879 |
<subsection> |
8880 |
<title>Optional: Viewing Documentation while Installing</title> |
8881 |
<body> |
8882 |
|
8883 |
<p> |
8884 |
If you want to view the Gentoo Handbook during the installation, make sure you |
8885 |
have created a user account (see <uri link="#useraccounts">Optional: User |
8886 |
Accounts</uri>). Then press <c>Alt-F2</c> to go to a new terminal and log in. |
8887 |
</p> |
8888 |
|
8889 |
<p> |
8890 |
If you want to view the documentation on the CD you can immediately run |
8891 |
<c>links</c> to read it: |
8892 |
</p> |
8893 |
|
8894 |
<pre caption="Viewing the on-CD documentation"> |
8895 |
# <i>links /mnt/cdrom/docs/handbook/html/index.html</i> |
8896 |
</pre> |
8897 |
|
8898 |
<p> |
8899 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
8900 |
more recent than the one provided on the CD. |
8901 |
</p> |
8902 |
|
8903 |
<pre caption="Viewing the Online Documentation"> |
8904 |
# <i>links http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i> |
8905 |
</pre> |
8906 |
|
8907 |
<p> |
8908 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
8909 |
</p> |
8910 |
|
8911 |
</body> |
8912 |
</subsection> |
8913 |
<subsection> |
8914 |
<title>Optional: Starting the SSH Daemon</title> |
8915 |
<body> |
8916 |
|
8917 |
<p> |
8918 |
If you want to allow other users to access your computer during the |
8919 |
Gentoo installation (perhaps because those users are going to help you |
8920 |
install Gentoo, or even do it for you), you need to create a user |
8921 |
account for them and perhaps even provide them with your root password |
8922 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
8923 |
</p> |
8924 |
|
8925 |
<p> |
8926 |
To fire up the SSH daemon, execute the following command: |
8927 |
</p> |
8928 |
|
8929 |
<pre caption="Starting the SSH daemon"> |
8930 |
# <i>/etc/init.d/sshd start</i> |
8931 |
</pre> |
8932 |
|
8933 |
<p> |
8934 |
To be able to use sshd, you first need to set up your networking. Continue with |
8935 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
8936 |
</p> |
8937 |
|
8938 |
</body> |
8939 |
</subsection> |
8940 |
</section> |
8941 |
</sections> |
8942 |
|
8943 |
|
8944 |
|
8945 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc-bootloader.xml |
8946 |
|
8947 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc-bootloader.xml?rev=1.1&view=markup |
8948 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc-bootloader.xml?rev=1.1&content-type=text/plain |
8949 |
|
8950 |
Index: hb-install-ppc-bootloader.xml |
8951 |
=================================================================== |
8952 |
<?xml version='1.0' encoding='UTF-8'?> |
8953 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
8954 |
|
8955 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
8956 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
8957 |
|
8958 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc-bootloader.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
8959 |
|
8960 |
<sections> |
8961 |
|
8962 |
<version>8.0</version> |
8963 |
<date>2007-05-07</date> |
8964 |
|
8965 |
<section> |
8966 |
<title>Choosing a Bootloader</title> |
8967 |
<subsection> |
8968 |
<title>Introduction</title> |
8969 |
<body> |
8970 |
|
8971 |
<p> |
8972 |
Now that the kernel is configured and compiled, you'll need a <e>bootloader</e> |
8973 |
to start your new linux installation. The <e>bootloader</e> that you use will |
8974 |
depend upon the type of PPC machine you have. |
8975 |
</p> |
8976 |
|
8977 |
<p> |
8978 |
If you are using a NewWorld Apple or IBM machine, you need to use |
8979 |
<uri link="#yaboot">yaboot</uri>. OldWorld Apple machines have two options, |
8980 |
<uri link="#bootx">BootX</uri> (recommended) and <uri link="#quik">quik</uri>. |
8981 |
The Pegasos does not require a bootloader, but you will need to emerge |
8982 |
<uri link="#bootcreator">bootcreator</uri> to create SmartFirmware boot menus. |
8983 |
</p> |
8984 |
|
8985 |
</body> |
8986 |
</subsection> |
8987 |
</section> |
8988 |
<section id="yaboot"> |
8989 |
<title>Default: Using yaboot</title> |
8990 |
<subsection> |
8991 |
<title>Introduction</title> |
8992 |
<body> |
8993 |
|
8994 |
<impo> |
8995 |
yaboot can only be used on NewWorld Apple and IBM systems! |
8996 |
</impo> |
8997 |
|
8998 |
<p> |
8999 |
In order to find the boot devices, yaboot needs access to the device nodes |
9000 |
created by udev on startup and the sysfs filesystem. These two filesystems |
9001 |
are found at <path>/dev</path> and <path>sys</path> respectively. To do this, |
9002 |
you will need to "bind mount" these filesystems from the Installation CD's root |
9003 |
to the <path>/dev</path> and <path>/sys</path> mount points inside the chroot. |
9004 |
If you have already bind mounted these filesystems, there is no need to do it |
9005 |
again. |
9006 |
</p> |
9007 |
|
9008 |
<pre caption="Bind-mounting the device and sysfs filesystems"> |
9009 |
# <i>exit </i> # this will exit the chroot |
9010 |
# <i>mount -o bind /dev /mnt/gentoo/dev</i> |
9011 |
# <i>mount -o bind /sys /mnt/gentoo/sys</i> |
9012 |
# <i>chroot /mnt/gentoo /bin/bash</i> |
9013 |
# <i>/usr/sbin/env-update && source /etc/profile </i> |
9014 |
</pre> |
9015 |
|
9016 |
<p> |
9017 |
To set up yaboot, you can use <c>yabootconfig</c> to automatically create a |
9018 |
configuration file for you. If you are installing Gentoo on a G5 (where |
9019 |
<c>yabootconfig</c> does not always work), or you plan to boot from firewire |
9020 |
or USB, you will need to manually configure yaboot. |
9021 |
</p> |
9022 |
|
9023 |
<note> |
9024 |
You will need to manually edit the yaboot.conf when using genkernel, even if |
9025 |
yabootconfig is used. The kernel image section of yaboot.conf should be |
9026 |
modified as follows (using vmlinux and initrd as the name of kernel and |
9027 |
initrd image): |
9028 |
</note> |
9029 |
|
9030 |
<pre caption="Adding genkernel boot arguments to yaboot.conf"> |
9031 |
<comment>########################################################### |
9032 |
## This section can be duplicated if you have more than one |
9033 |
## kernel or set of boot options - replace the image and initrd |
9034 |
## with the exact filename of your kernel and initrd image. |
9035 |
###########################################################</comment> |
9036 |
image=/boot/kernel-genkernel-ppc-<keyval id="kernel-gentoo"/> |
9037 |
label=Linux |
9038 |
root=/dev/ram0 |
9039 |
partition=3 |
9040 |
initrd=/boot/initramfs-genkernel-ppc-<keyval id="kernel-gentoo"/> |
9041 |
<comment># You can add additional kernel arguments to append such as |
9042 |
# rootdelay=10 for a USB/Firewire Boot</comment> |
9043 |
append="real_root=/dev/hda3 init=/linuxrc" |
9044 |
read-only |
9045 |
<comment>##########################################################</comment> |
9046 |
</pre> |
9047 |
|
9048 |
<ul> |
9049 |
<li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li> |
9050 |
<li> |
9051 |
<uri link="#manual_yaboot">Alternative: Manual yaboot Configuration</uri> |
9052 |
</li> |
9053 |
</ul> |
9054 |
|
9055 |
</body> |
9056 |
</subsection> |
9057 |
<subsection id="yabootconfig"> |
9058 |
<title>Default: Using yabootconfig</title> |
9059 |
<body> |
9060 |
|
9061 |
<p> |
9062 |
<c>yabootconfig</c> will auto-detect the partitions on your machine and will |
9063 |
set up dual and triple boot combinations with Linux, Mac OS, and Mac OS X. |
9064 |
</p> |
9065 |
|
9066 |
<p> |
9067 |
To use <c>yabootconfig</c>, your drive must have an Apple_Bootstrap partition, |
9068 |
and <path>/etc/fstab</path> must be configured to reflect your Linux |
9069 |
partitions (note that the Bootstrap partition should <e>not</e> be in your |
9070 |
fstab). These steps should have already been completed before, but check |
9071 |
<path>/etc/fstab</path> before proceeding. Now, install <c>yaboot</c>. |
9072 |
</p> |
9073 |
|
9074 |
<pre caption = "Installing yaboot from GRP"> |
9075 |
# <i>emerge --usepkg yaboot</i> |
9076 |
</pre> |
9077 |
|
9078 |
<p> |
9079 |
Now exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</c>. First, |
9080 |
the program will confirm the location of the bootstrap partition. If you are |
9081 |
using the suggested disk partitioning scheme, your bootstrap partition should |
9082 |
be /dev/hda2. Type <c>Y</c> if the output is correct. If not, double check your |
9083 |
<path>/etc/fstab</path>. <c>yabootconfig</c> will then scan your system setup, |
9084 |
create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you. |
9085 |
<c>mkofboot</c> is used to format the Apple_Bootstrap partition, and install |
9086 |
the yaboot configuration file into it. After this enter the chroot again. |
9087 |
</p> |
9088 |
|
9089 |
<pre caption="Re-enter the chroot"> |
9090 |
# <i>chroot /mnt/gentoo /bin/bash</i> |
9091 |
# <i>/usr/sbin/env-update && source /etc/profile</i> |
9092 |
</pre> |
9093 |
|
9094 |
<p> |
9095 |
You should verify the contents of <path>/etc/yaboot.conf</path>. If you make |
9096 |
changes to <path>/etc/yaboot.conf</path> (like setting the default/boot OS), |
9097 |
make sure to rerun <c>ybin -v</c> to apply changes to the Apple_Bootstrap |
9098 |
partition. Whenever you make a change to yaboot.conf, like when testing a new |
9099 |
kernel, always remember to run <c>ybin -v</c> to update the bootstrap |
9100 |
partition. |
9101 |
</p> |
9102 |
|
9103 |
<p> |
9104 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
9105 |
</p> |
9106 |
|
9107 |
</body> |
9108 |
</subsection> |
9109 |
<subsection id="manual_yaboot"> |
9110 |
<title>Alternative: Manual yaboot Configuration</title> |
9111 |
<body> |
9112 |
|
9113 |
<p> |
9114 |
First, install <c>yaboot</c> on your system: |
9115 |
</p> |
9116 |
|
9117 |
<pre caption="Installing yaboot from GRP"> |
9118 |
# <i>emerge --usepkg yaboot</i> |
9119 |
</pre> |
9120 |
|
9121 |
<p> |
9122 |
An example <path>yaboot.conf</path> file is given below, but you will need to |
9123 |
alter it to fit your needs. G5 users and users booting from firewire and USB |
9124 |
should be aware that their disks are seen as SCSI disks by the Linux kernel, so |
9125 |
you will need to substitute <path>/dev/hda</path> with <path>/dev/sda</path>). |
9126 |
</p> |
9127 |
|
9128 |
<pre caption = "/etc/yaboot.conf"> |
9129 |
<comment>## /etc/yaboot.conf |
9130 |
## |
9131 |
## run: "man yaboot.conf" for details. Do not make changes until you have!! |
9132 |
## see also: /usr/share/doc/yaboot/examples for example configurations. |
9133 |
## |
9134 |
## For a dual-boot menu, add one or more of: |
9135 |
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ |
9136 |
|
9137 |
## The bootstrap partition:</comment> |
9138 |
|
9139 |
boot=/dev/hda2 |
9140 |
|
9141 |
<comment>## ofboot is the Open Firmware way to specify the bootstrap partition. |
9142 |
## If this isn't defined, yaboot fails on the G5 and some G4s (unless |
9143 |
## you pass the necessary arguments to the mkofboot/ybin program). |
9144 |
## hd:X means /dev/sdaX (or /dev/hdaX). |
9145 |
## |
9146 |
## G5 users should uncomment this line!! |
9147 |
|
9148 |
#ofboot=hd:2 |
9149 |
|
9150 |
## Users booting from firewire should use something like this line: |
9151 |
# ofboot=fw/node/sbp-2/disk@0: |
9152 |
|
9153 |
## Users booting from USB should use something like this line: |
9154 |
# ofboot=usb/disk@0: |
9155 |
|
9156 |
## hd: is shorthand for the first hard drive Open Firmware sees</comment> |
9157 |
device=hd: |
9158 |
|
9159 |
<comment>## Firewire and USB users will need to specify the whole OF device name |
9160 |
## This can be found using ofpath, which is included with yaboot. |
9161 |
|
9162 |
# device=fw/node@0001d200e00d0207/sbp-2@c000/disk@0: |
9163 |
</comment> |
9164 |
|
9165 |
delay=5 |
9166 |
defaultos=macosx |
9167 |
timeout=30 |
9168 |
install=/usr/lib/yaboot/yaboot |
9169 |
magicboot=/usr/lib/yaboot/ofboot |
9170 |
|
9171 |
<comment>########################################################### |
9172 |
## This section can be duplicated if you have more than one |
9173 |
## kernel or set of boot options - replace the image variable |
9174 |
## with the exact filename of your kernel. |
9175 |
###########################################################</comment> |
9176 |
image=/boot/<keyval id="kernel-name"/> |
9177 |
label=Linux |
9178 |
root=/dev/hda3 |
9179 |
partition=3 |
9180 |
<comment># append="rootdelay=10" # Required for booting USB/Firewire</comment> |
9181 |
read-only |
9182 |
<comment>################## |
9183 |
|
9184 |
## G5 users and some G4 users should set |
9185 |
## macos=hd:13 |
9186 |
## macosx=hd:12 |
9187 |
## instead of the example values.</comment> |
9188 |
macos=/dev/hda13 |
9189 |
macosx=/dev/hda12 |
9190 |
enablecdboot |
9191 |
enableofboot |
9192 |
</pre> |
9193 |
|
9194 |
<p> |
9195 |
Once <path>yaboot.conf</path> is configured, run <c>mkofboot -v</c> to format |
9196 |
the Apple_bootstrap partition and install the settings. If you change |
9197 |
yaboot.conf after the Apple_bootstrap partition has been created, you can |
9198 |
update the settings by running <c>ybin -v</c> |
9199 |
</p> |
9200 |
|
9201 |
<pre caption="Setting up the bootstrap partition"> |
9202 |
# <i>mkofboot -v</i> |
9203 |
</pre> |
9204 |
|
9205 |
<p> |
9206 |
For more information on yaboot, take a look at the <uri |
9207 |
link="http://penguinppc.org/bootloaders/yaboot">yaboot project</uri>. For |
9208 |
now, continue the installation with <uri link="#reboot">Rebooting the |
9209 |
System</uri>. |
9210 |
</p> |
9211 |
|
9212 |
</body> |
9213 |
</subsection> |
9214 |
</section> |
9215 |
<section id="bootx"> |
9216 |
<title>Alternative: BootX</title> |
9217 |
<body> |
9218 |
|
9219 |
<impo> |
9220 |
BootX can only be used on OldWorld Apple systems with MacOS 9 or earlier! |
9221 |
</impo> |
9222 |
|
9223 |
<p> |
9224 |
Since BootX boots Linux from within MacOS, the kernel will need to be copied |
9225 |
from the Linux Partition to the MacOS partition. First, mount the MacOS |
9226 |
partition from outside of the chroot. Use <c>mac-fdisk -l</c> to find the |
9227 |
MacOS partition number, sda6 is used as an example here. Once the partition is |
9228 |
mounted, we'll copy the kernel to the system folder so BootX can find it. |
9229 |
</p> |
9230 |
|
9231 |
<pre caption="Copying the kernel to the MacOS partition"> |
9232 |
# <i>exit</i> |
9233 |
cdimage ~# <i>mkdir /mnt/mac</i> |
9234 |
cdimage ~# <i>mount /dev/sda6 /mnt/mac -t hfs</i> |
9235 |
cdimage ~# <i>cp /mnt/gentoo/usr/src/linux/vmlinux "/mnt/mac/System Folder/Linux Kernels/<keyval id="kernel-name"/>"</i> |
9236 |
</pre> |
9237 |
|
9238 |
<p> |
9239 |
If genkernel is used, both the kernel and initrd will need to be copied to the |
9240 |
MacOS partition. |
9241 |
</p> |
9242 |
|
9243 |
<pre caption="Copying the Genkernel kernel and initrd to the MacOS partition"> |
9244 |
# <i>exit</i> |
9245 |
cdimage ~# <i>mkdir /mnt/mac</i> |
9246 |
cdimage ~# <i>mount /dev/sda6 /mnt/mac -t hfs</i> |
9247 |
cdimage ~# <i>cp /mnt/gentoo/boot/kernel-genkernel-ppc-<keyval id="kernel-gentoo"/> "/mnt/mac/System Folder/Linux Kernels"</i> |
9248 |
cdimage ~# <i>cp /mnt/gentoo/boot/initramfs-genkernel-ppc-<keyval id="kernel-gentoo"/> "/mnt/mac/System Folder"</i> |
9249 |
</pre> |
9250 |
|
9251 |
<p> |
9252 |
Now that the kernel is copied over, we'll need to reboot to set up BootX. |
9253 |
</p> |
9254 |
|
9255 |
<pre caption="Unmounting all partitions and rebooting"> |
9256 |
cdimage ~# <i>cd /</i> |
9257 |
cdimage ~# <i>umount /mnt/gentoo/proc /mnt/gentoo/dev /mnt/gentoo/sys /mnt/gentoo /mnt/mac</i> |
9258 |
cdimage ~# <i>reboot</i> |
9259 |
</pre> |
9260 |
|
9261 |
<p> |
9262 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
9263 |
booted again instead of MacOS. |
9264 |
</p> |
9265 |
|
9266 |
<p> |
9267 |
Once the machine has booted into MacOS, open the BootX control panel. If you're |
9268 |
not using genkernel, select <c>Options</c> and uncheck <c>Use specified RAM |
9269 |
disk</c>. If you are using genkernel, ensure that the genkernel initrd is |
9270 |
selected instead of the Installation CD initrd. If not using genkernel, |
9271 |
there is now an option to specify the machine's Linux root disk and partition. |
9272 |
Fill these in with the appropriate values. Depending upon the kernel |
9273 |
configuration, additional boot arguments may need to be applied. |
9274 |
</p> |
9275 |
|
9276 |
<p> |
9277 |
BootX can be configured to start Linux upon boot. If you do this, you will first |
9278 |
see your machine boot into MacOS then, during startup, BootX will load and start |
9279 |
Linux. See the <uri link="http://penguinppc.org/bootloaders/bootx/">BootX home |
9280 |
page</uri> for more information. |
9281 |
</p> |
9282 |
|
9283 |
<impo> |
9284 |
Make sure that you have support for HFS and HFS+ filesystems in your kernel, |
9285 |
otherwise you will not be able to upgrade or change the kernel on your MacOS |
9286 |
partition. |
9287 |
</impo> |
9288 |
|
9289 |
<p> |
9290 |
Now reboot again and boot into Linux, then continue with <uri |
9291 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
9292 |
</p> |
9293 |
|
9294 |
</body> |
9295 |
</section> |
9296 |
<section id="quik"> |
9297 |
<title>Alternative: quik</title> |
9298 |
<body> |
9299 |
|
9300 |
<p> |
9301 |
quik allows OldWorld Macs to boot without MacOS. However, it isn't well |
9302 |
supported and has a number of quirks. If you have the option, it is recommended |
9303 |
that you use BootX instead since it is much more reliable and easier to set up |
9304 |
than quik. |
9305 |
</p> |
9306 |
|
9307 |
<p> |
9308 |
First, we'll need to install quik: |
9309 |
</p> |
9310 |
|
9311 |
<pre caption="Emerge quik from GRP"> |
9312 |
# <i>emerge --usepkg quik</i> |
9313 |
</pre> |
9314 |
|
9315 |
<p> |
9316 |
Next, we'll need to set it up. Edit <path>/etc/quik.conf</path> and set your |
9317 |
image to the kernel that we copied to your boot partition. |
9318 |
</p> |
9319 |
|
9320 |
<pre caption="Configuring quik.conf"> |
9321 |
# Example of quik.conf |
9322 |
init-message = "Gentoo 2007.0\n" |
9323 |
<comment># This is the boot partition</comment> |
9324 |
partition = 2 |
9325 |
root = /dev/hda4 |
9326 |
timeout = 30 |
9327 |
default = gentoo |
9328 |
<comment># This is your kernel</comment> |
9329 |
image = /<keyval id="kernel-name"/> |
9330 |
label = gentoo |
9331 |
</pre> |
9332 |
|
9333 |
<p> |
9334 |
Your quik.conf file <e>must</e> be on the same disk as the quik boot images, |
9335 |
however it can be on a different partition on the same disk, although it is |
9336 |
recommended to move it to your boot partition. |
9337 |
</p> |
9338 |
|
9339 |
<pre caption="Moving quik.conf to /boot"> |
9340 |
# <i>mv /etc/quik.conf /boot/quik.conf</i> |
9341 |
</pre> |
9342 |
|
9343 |
<p> |
9344 |
We will now set your boot variables so that quik loads on boot. To do this, |
9345 |
we'll use a program called <c>nvsetenv</c>. The variables that you want to |
9346 |
set vary from machine to machine, it's best to find your machine's |
9347 |
<uri link="http://penguinppc.org/bootloaders/quik/quirks.php">quirks</uri> |
9348 |
before attempting this. |
9349 |
</p> |
9350 |
|
9351 |
<pre caption="Setting the boot variables"> |
9352 |
# <i>nvsetenv auto-boot true</i> <comment># Set to false if you want to boot into OF, not all models can display the OF output</comment> |
9353 |
# <i>nvsetenv output-device video</i> <comment># Check the quirks page, there are many variations here</comment> |
9354 |
# <i>nvsetenv input-device kbd</i> |
9355 |
# <i>nvsetenv boot-device scsi/sd@1:0</i> <comment># For SCSI</comment> |
9356 |
# <i>nvsetenv boot-device ata/ata-disk@0:0</i> <comment># For ATA</comment> |
9357 |
# <i>nvsetenv boot-file /boot/<keyval id="kernel-name"/> root=/dev/hda4</i> <comment>First item is the path to the kernel, the second is the root partition. You may append any kernel options to the end of this line.</comment> |
9358 |
# <i>nvsetenv boot-command boot</i> <comment># Set this to bye for MacOS and boot for Linux</comment> |
9359 |
</pre> |
9360 |
|
9361 |
<note> |
9362 |
It is also possible to change your boot variables from MacOS. Depending upon |
9363 |
the model, either <uri |
9364 |
link="http://penguinppc.org/bootloaders/quik/BootVars.sit.hqx">bootvars</uri> or |
9365 |
<uri |
9366 |
link="ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin"> |
9367 |
Apple System Disk</uri> should be used. Please see the quik quirks page above |
9368 |
for more information. |
9369 |
</note> |
9370 |
|
9371 |
<p> |
9372 |
Now that we've set up our machine to boot, we'll need to make sure the boot |
9373 |
images are installed correctly. Run <c>quik -v -C /boot/quik.conf</c>. It |
9374 |
should tell you that it has installed the first stage QUIK boot block. |
9375 |
</p> |
9376 |
|
9377 |
<note> |
9378 |
If something has gone wrong, you can always reset your PRAM back to the default |
9379 |
values by holding down <c>command + option + p + r</c> before powering on your |
9380 |
machine. This will clear the values you set with nvsetenv and should allow you |
9381 |
to boot either a MacOS bootdisk or a Linux bootdisk. |
9382 |
</note> |
9383 |
|
9384 |
<p> |
9385 |
Now, continue the installation with |
9386 |
<uri link="#reboot">Rebooting the System</uri>. |
9387 |
</p> |
9388 |
|
9389 |
</body> |
9390 |
</section> |
9391 |
<section id="bootcreator"> |
9392 |
<title>Alternative: BootCreator</title> |
9393 |
<body> |
9394 |
|
9395 |
<impo> |
9396 |
BootCreator will build a nice SmartFirmware bootmenu written in Forth for the |
9397 |
Pegasos. |
9398 |
</impo> |
9399 |
|
9400 |
<p> |
9401 |
First make sure you have <c>bootcreator</c> installed on your system: |
9402 |
</p> |
9403 |
|
9404 |
<pre caption = "Installing bootcreator from GRP"> |
9405 |
# <i>emerge --usepkg bootcreator</i> |
9406 |
</pre> |
9407 |
|
9408 |
<p> |
9409 |
Now copy the file <path>/etc/bootmenu.example</path> into |
9410 |
<path>/etc/bootmenu</path> and edit it to suit your needs: |
9411 |
</p> |
9412 |
|
9413 |
<pre caption = "Edit the bootcreator config file"> |
9414 |
# <i>cp /etc/bootmenu.example /etc/bootmenu</i> |
9415 |
# <i>nano -w /etc/bootmenu</i> |
9416 |
</pre> |
9417 |
|
9418 |
<p> |
9419 |
Below is a complete <path>/etc/bootmenu</path> config file. vmlinux and |
9420 |
initrd should be replaced by your kernel and initrd image names. |
9421 |
</p> |
9422 |
|
9423 |
<pre caption = "bootcreator config file"> |
9424 |
<comment># |
9425 |
# Example description file for bootcreator 1.1 |
9426 |
#</comment> |
9427 |
|
9428 |
[VERSION] |
9429 |
1 |
9430 |
|
9431 |
[TITLE] |
9432 |
Boot Menu |
9433 |
|
9434 |
[SETTINGS] |
9435 |
AbortOnKey = false |
9436 |
Timeout = 9 |
9437 |
Default = 1 |
9438 |
|
9439 |
[SECTION] |
9440 |
Local HD -> Morphos (Normal) |
9441 |
ide:0 boot2.img ramdebug edebugflags="logkprintf" |
9442 |
|
9443 |
[SECTION] |
9444 |
Local HD -> Linux (Normal) |
9445 |
ide:0 <keyval id="kernel-name"/> video=radeonfb:1024x768@70 root=/dev/hda3 |
9446 |
|
9447 |
[SECTION] |
9448 |
Local HD -> Genkernel (Normal) |
9449 |
ide:0 kernel-genkernel-ppc-<keyval id="kernel-gentoo"/> root=/dev/ram0 real_root=/dev/hda3 init=/linuxrc initrd=initramfs-genkernel-ppc-<keyval id="kernel-gentoo"/> |
9450 |
</pre> |
9451 |
|
9452 |
<p> |
9453 |
Finally the <path>bootmenu</path> must be transferred into Forth and copied to |
9454 |
your boot partition, so that the SmartFirmware can read it. Therefore you have |
9455 |
to call <c>bootcreator</c>: |
9456 |
</p> |
9457 |
|
9458 |
<pre caption = "Install the bootmenu"> |
9459 |
# <i>bootcreator /etc/bootmenu /boot/menu</i> |
9460 |
</pre> |
9461 |
|
9462 |
<note> |
9463 |
Be sure to have a look into the SmartFirmware's settings when you reboot, that |
9464 |
<path>menu</path> is the file that will be loaded by default. |
9465 |
</note> |
9466 |
|
9467 |
<p> |
9468 |
For now, continue the installation with <uri link="#reboot">Rebooting the |
9469 |
System</uri>. |
9470 |
</p> |
9471 |
|
9472 |
</body> |
9473 |
</section> |
9474 |
<section id="reboot"> |
9475 |
<title>Rebooting the System</title> |
9476 |
<subsection> |
9477 |
<body> |
9478 |
|
9479 |
<p> |
9480 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
9481 |
that one magical command you have been waiting for: <c>reboot</c>. |
9482 |
</p> |
9483 |
|
9484 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
9485 |
# <i>exit</i> |
9486 |
livecd ~# <i>umount /mnt/gentoo/proc /mnt/gentoo/dev /mnt/gentoo/sys /mnt/gentoo</i> |
9487 |
livecd ~# <i>reboot</i> |
9488 |
</pre> |
9489 |
|
9490 |
<p> |
9491 |
Once rebooted in your Gentoo installation, finish up with <uri |
9492 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
9493 |
</p> |
9494 |
|
9495 |
</body> |
9496 |
</subsection> |
9497 |
</section> |
9498 |
</sections> |
9499 |
|
9500 |
|
9501 |
|
9502 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc-disk.xml |
9503 |
|
9504 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc-disk.xml?rev=1.1&view=markup |
9505 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc-disk.xml?rev=1.1&content-type=text/plain |
9506 |
|
9507 |
Index: hb-install-ppc-disk.xml |
9508 |
=================================================================== |
9509 |
<?xml version='1.0' encoding='UTF-8'?> |
9510 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
9511 |
|
9512 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
9513 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
9514 |
|
9515 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc-disk.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
9516 |
|
9517 |
<sections> |
9518 |
|
9519 |
<version>8.3</version> |
9520 |
<date>2007-06-26</date> |
9521 |
|
9522 |
<section> |
9523 |
<title>Introduction to Block Devices</title> |
9524 |
<subsection> |
9525 |
<title>Block Devices</title> |
9526 |
<body> |
9527 |
|
9528 |
<p> |
9529 |
We'll start by taking a good look at disk-oriented aspects of Gentoo Linux |
9530 |
and Linux in general, including Linux filesystems, partitions and block devices. |
9531 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
9532 |
you'll be guided through the process of setting up partitions and filesystems |
9533 |
for your Gentoo Linux installation. |
9534 |
</p> |
9535 |
|
9536 |
<p> |
9537 |
To begin, we'll introduce <e>block devices</e>. The most common block device is |
9538 |
the one that represents the first IDE drive in a Linux system, namely |
9539 |
<path>/dev/hda</path>. If you are installing onto SCSI, FireWire, USB or SATA |
9540 |
drives, then your first hard drive would be <path>/dev/sda</path>. Additional |
9541 |
drives are enumerated by the next letter in the alphabet. As an example, the |
9542 |
third IDE disk could be found at <path>/dev/hdc</path>. |
9543 |
</p> |
9544 |
|
9545 |
<p> |
9546 |
The block devices above represent an abstract interface to the disk. User |
9547 |
programs can use these block devices to interact with the disk without worrying |
9548 |
about whether the drives are IDE, SCSI or something else. The program can |
9549 |
simply address the storage on the disk as a bunch of contiguous, |
9550 |
randomly-accessible 512-byte blocks. |
9551 |
</p> |
9552 |
|
9553 |
</body> |
9554 |
</subsection> |
9555 |
<subsection> |
9556 |
<title>Partitions</title> |
9557 |
<body> |
9558 |
|
9559 |
<p> |
9560 |
Although it is theoretically possible to use a full disk to house your Linux |
9561 |
system, this is almost never done in practice. Instead, full disk block devices |
9562 |
are split up in smaller, more manageable block devices. On most systems, |
9563 |
these are called <e>partitions</e>. |
9564 |
</p> |
9565 |
|
9566 |
</body> |
9567 |
</subsection> |
9568 |
</section> |
9569 |
<section> |
9570 |
<title>Designing a Partitioning Scheme</title> |
9571 |
<subsection> |
9572 |
<title>Default Partitioning Scheme</title> |
9573 |
<body> |
9574 |
|
9575 |
<p> |
9576 |
If you are not interested in drawing up a partitioning scheme for your system, |
9577 |
you can use the partitioning scheme we use throughout this book. Choose the |
9578 |
filesystem layout that best matches the type of PowerPC system you are |
9579 |
installing on. |
9580 |
</p> |
9581 |
|
9582 |
</body> |
9583 |
</subsection> |
9584 |
<subsection> |
9585 |
<title>Apple New World</title> |
9586 |
<body> |
9587 |
|
9588 |
<p> |
9589 |
Apple New World machines are fairly straightforward to configure. The first |
9590 |
partition is always an <e>Apple Partition Map</e>. This partition keeps track |
9591 |
of the layout of the disk. You cannot remove this partition. The next |
9592 |
partition should always be a bootstrap partition. This partition contains a |
9593 |
small (800k) HFS filesystem that holds a copy of the bootloader Yaboot and its |
9594 |
configuration file. This partition is <e>not</e> the same as a |
9595 |
<path>/boot</path> partition as found on other architectures. After the boot |
9596 |
partition, the usual Linux filesystems are placed, according to the scheme |
9597 |
below. The swap partition is a temporary storage place for when your system |
9598 |
runs out of physical memory. The root partition will contain the filesystem |
9599 |
that Gentoo is installed on. If you wish to dual boot, the OSX partition |
9600 |
can go anywhere after the bootstrap partition to insure that yaboot starts |
9601 |
first. |
9602 |
</p> |
9603 |
|
9604 |
<note> |
9605 |
There may be "Disk Driver" partitions on your disk such as |
9606 |
<path>Apple_Driver63</path>, <path>Apple_Driver_ATA</path>, |
9607 |
<path>Apple_FWDriver</path>, <path>Apple_Driver_IOKit</path>, and |
9608 |
<path>Apple_Patches</path>. These are used to boot MacOS, so if you have no |
9609 |
need for this, you can remove them by initializing the disk with mac-fdisk's |
9610 |
<c>i</c> option. This will completely erase the disk! If you are in doubt, |
9611 |
just let them be. |
9612 |
</note> |
9613 |
|
9614 |
<note> |
9615 |
If you partitioned this disk with Apple's Disk Utility, there may be |
9616 |
128Mb spaces between partitions which Apple reserves for "future use". You |
9617 |
can safely remove these. |
9618 |
</note> |
9619 |
|
9620 |
<table> |
9621 |
<tr> |
9622 |
<th>Partition</th> |
9623 |
<th>Size</th> |
9624 |
<th>Filesystem</th> |
9625 |
<th>Description</th> |
9626 |
</tr> |
9627 |
<tr> |
9628 |
<ti><path>/dev/hda1</path></ti> |
9629 |
<ti>32k</ti> |
9630 |
<ti>None</ti> |
9631 |
<ti>Apple Partition Map</ti> |
9632 |
</tr> |
9633 |
<tr> |
9634 |
<ti><path>/dev/hda2</path></ti> |
9635 |
<ti>800k</ti> |
9636 |
<ti>HFS</ti> |
9637 |
<ti>Apple Bootstrap</ti> |
9638 |
</tr> |
9639 |
<tr> |
9640 |
<ti><path>/dev/hda3</path></ti> |
9641 |
<ti>512Mb</ti> |
9642 |
<ti>Swap</ti> |
9643 |
<ti>Linux Swap</ti> |
9644 |
</tr> |
9645 |
<tr> |
9646 |
<ti><path>/dev/hda4</path></ti> |
9647 |
<ti>Rest of Disk</ti> |
9648 |
<ti>ext3, reiserfs, xfs</ti> |
9649 |
<ti>Linux Root</ti> |
9650 |
</tr> |
9651 |
</table> |
9652 |
|
9653 |
</body> |
9654 |
</subsection> |
9655 |
<subsection> |
9656 |
<title>Apple Old World</title> |
9657 |
<body> |
9658 |
|
9659 |
<p> |
9660 |
Apple Old World machines are a bit more complicated to configure. The first |
9661 |
partition is always an <e>Apple Partition Map</e>. This partition keeps track |
9662 |
of the layout of the disk. You cannot remove this partition. If you are using |
9663 |
BootX, the configuration below assumes that MacOS is installed on a seperate |
9664 |
disk. If this is not the case, there will be additional partitions for "Apple |
9665 |
Disk Drivers" such as <path>Apple_Driver63, Apple_Driver_ATA, Apple_FWDriver, |
9666 |
Apple_Driver_IOKit, Apple_Patches</path> and the MacOS install. If you are |
9667 |
using Quik, you will need to create a boot partition to hold the kernel, unlike |
9668 |
other Apple boot methods. After the boot partition, the usual Linux filesystems |
9669 |
are placed, according to the scheme below. The swap partition is a temporary |
9670 |
storage place for when your system runs out of physical memory. The root |
9671 |
partition will contain the filesystem that Gentoo is installed on. |
9672 |
</p> |
9673 |
|
9674 |
<note> |
9675 |
If you are using an OldWorld machine, you will need to keep MacOS available. |
9676 |
The layout here assumes MacOS is installed on a separate drive. |
9677 |
</note> |
9678 |
|
9679 |
<table> |
9680 |
<tr> |
9681 |
<th>Partition</th> |
9682 |
<th>Size</th> |
9683 |
<th>Filesystem</th> |
9684 |
<th>Description</th> |
9685 |
</tr> |
9686 |
<tr> |
9687 |
<ti><path>/dev/hda1</path></ti> |
9688 |
<ti>32k</ti> |
9689 |
<ti>None</ti> |
9690 |
<ti>Apple Partition Map</ti> |
9691 |
</tr> |
9692 |
<tr> |
9693 |
<ti><path>/dev/hda2</path></ti> |
9694 |
<ti>32Mb</ti> |
9695 |
<ti>ext2</ti> |
9696 |
<ti>Quik Boot Partition (quik only)</ti> |
9697 |
</tr> |
9698 |
<tr> |
9699 |
<ti><path>/dev/hda3</path></ti> |
9700 |
<ti>512Mb</ti> |
9701 |
<ti>Swap</ti> |
9702 |
<ti>Linux Swap</ti> |
9703 |
</tr> |
9704 |
<tr> |
9705 |
<ti><path>/dev/hda4</path></ti> |
9706 |
<ti>Rest of Disk</ti> |
9707 |
<ti>ext3, reiserfs, xfs</ti> |
9708 |
<ti>Linux Root</ti> |
9709 |
</tr> |
9710 |
</table> |
9711 |
|
9712 |
</body> |
9713 |
</subsection> |
9714 |
<subsection> |
9715 |
<title>Pegasos</title> |
9716 |
<body> |
9717 |
|
9718 |
<p> |
9719 |
The Pegasos partition layout is quite simple compared to the Apple layouts. |
9720 |
The first partition is a Boot Partition, which contains kernels to be booted, |
9721 |
along with an Open Firmware script that presents a menu on boot. After the boot |
9722 |
partition, the usual Linux filesystems are placed, according to the scheme |
9723 |
below. The swap partition is a temporary storage place for when your system |
9724 |
runs out of physical memory. The root partition will contain the filesystem |
9725 |
that Gentoo is installed on. |
9726 |
</p> |
9727 |
|
9728 |
<table> |
9729 |
<tr> |
9730 |
<th>Partition</th> |
9731 |
<th>Size</th> |
9732 |
<th>Filesystem</th> |
9733 |
<th>Description</th> |
9734 |
</tr> |
9735 |
<tr> |
9736 |
<ti><path>/dev/hda1</path></ti> |
9737 |
<ti>32Mb</ti> |
9738 |
<ti>affs1 or ext2</ti> |
9739 |
<ti>Boot Partition</ti> |
9740 |
</tr> |
9741 |
<tr> |
9742 |
<ti><path>/dev/hda2</path></ti> |
9743 |
<ti>512Mb</ti> |
9744 |
<ti>Swap</ti> |
9745 |
<ti>Linux Swap</ti> |
9746 |
</tr> |
9747 |
<tr> |
9748 |
<ti><path>/dev/hda3</path></ti> |
9749 |
<ti>Rest of Disk</ti> |
9750 |
<ti>ext3, reiserfs, xfs</ti> |
9751 |
<ti>Linux Root</ti> |
9752 |
</tr> |
9753 |
</table> |
9754 |
|
9755 |
</body> |
9756 |
</subsection> |
9757 |
<subsection> |
9758 |
<title>IBM PReP (RS/6000)</title> |
9759 |
<body> |
9760 |
|
9761 |
<p> |
9762 |
The IBM PowerPC Reference Platform (PReP) requires a small PReP boot partition |
9763 |
on the disk's first partition, followed by the swap and root partitions. |
9764 |
</p> |
9765 |
|
9766 |
<table> |
9767 |
<tr> |
9768 |
<th>Partition</th> |
9769 |
<th>Size</th> |
9770 |
<th>Filesystem</th> |
9771 |
<th>Description</th> |
9772 |
</tr> |
9773 |
<tr> |
9774 |
<ti><path>/dev/hda1</path></ti> |
9775 |
<ti>800k</ti> |
9776 |
<ti>None</ti> |
9777 |
<ti>PReP Boot Partition (Type 0x41)</ti> |
9778 |
</tr> |
9779 |
<tr> |
9780 |
<ti><path>/dev/hda2</path></ti> |
9781 |
<ti>512Mb</ti> |
9782 |
<ti>Swap</ti> |
9783 |
<ti>Linux Swap (Type 0x82)</ti> |
9784 |
</tr> |
9785 |
<tr> |
9786 |
<ti><path>/dev/hda3</path></ti> |
9787 |
<ti>Rest of Disk</ti> |
9788 |
<ti>ext3, reiserfs, xfs</ti> |
9789 |
<ti>Linux Root (Type 0x83)</ti> |
9790 |
</tr> |
9791 |
</table> |
9792 |
|
9793 |
<warn> |
9794 |
<c>parted</c> is able to resize partitions including HFS+. Unfortunately there |
9795 |
may be issues with resizing HFS+ journaled filesystems, so, for the best |
9796 |
results, switch off journaling in Mac OS X before resizing. Remember that any |
9797 |
resizing operation is dangerous, so attempt at your own risk! Be sure to always |
9798 |
have a backup of your data before resizing! |
9799 |
</warn> |
9800 |
|
9801 |
<p> |
9802 |
If you are interested in knowing how big a partition should be, or even how many |
9803 |
partitions you need, read on. Otherwise continue now with |
9804 |
<uri link="#mac-fdisk"> Default: Using mac-fdisk (Apple) to Partition your Disk |
9805 |
</uri> or <uri link="#parted">Alternative: Using parted (IBM/Pegasos) to |
9806 |
Partition your Disk</uri>. |
9807 |
</p> |
9808 |
|
9809 |
</body> |
9810 |
</subsection> |
9811 |
<subsection> |
9812 |
<title>How Many and How Big?</title> |
9813 |
<body> |
9814 |
|
9815 |
<p> |
9816 |
The number of partitions is highly dependent on your environment. For instance, |
9817 |
if you have lots of users, you will most likely want to have your |
9818 |
<path>/home</path> separate as it increases security and makes backups easier. |
9819 |
If you are installing Gentoo to perform as a mailserver, your <path>/var</path> |
9820 |
should be separate as all received mail is stored in <path>/var</path>. A good |
9821 |
choice of filesystem will then maximise your performance. Game servers should |
9822 |
have a separate <path>/opt</path> as most game servers are installed there. The |
9823 |
reason is similar for <path>/home</path>: security and backups. Whatever layout |
9824 |
you chose, you will definitely want to keep <path>/usr</path> large: not only |
9825 |
will it contain the majority of applications, the Portage tree alone takes |
9826 |
more than 500Mb excluding the various sources that are stored in it. |
9827 |
</p> |
9828 |
|
9829 |
<p> |
9830 |
As you can see, it very much depends on what you want to achieve. Separate |
9831 |
partitions or volumes have the following advantages: |
9832 |
</p> |
9833 |
|
9834 |
<ul> |
9835 |
<li> |
9836 |
You can choose the best performing filesystem for each partition or volume |
9837 |
</li> |
9838 |
<li> |
9839 |
Your entire system cannot run out of free space if one defunct tool is |
9840 |
continuously writing files to a partition or volume |
9841 |
</li> |
9842 |
<li> |
9843 |
If necessary, file system checks are reduced in time, as multiple checks can |
9844 |
be done in parallel (although this advantage is more with multiple disks than |
9845 |
it is with multiple partitions) |
9846 |
</li> |
9847 |
<li> |
9848 |
Security can be enhanced by mounting some partitions or volumes read-only, |
9849 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
9850 |
</li> |
9851 |
</ul> |
9852 |
|
9853 |
<p> |
9854 |
However, multiple partitions have one big disadvantage: if not configured |
9855 |
properly, you might result in having a system with lots of free space on one |
9856 |
partition and none on another. There is also a 15-partition limit for SCSI and |
9857 |
SATA. |
9858 |
</p> |
9859 |
|
9860 |
</body> |
9861 |
</subsection> |
9862 |
</section> |
9863 |
<section id="mac-fdisk"> |
9864 |
<title>Default: Using mac-fdisk (Apple) Partition your Disk</title> |
9865 |
<body> |
9866 |
|
9867 |
<p> |
9868 |
At this point, create your partitions using <c>mac-fdisk</c>: |
9869 |
</p> |
9870 |
|
9871 |
<pre caption="Starting mac-fdisk"> |
9872 |
# <i>mac-fdisk /dev/hda</i> |
9873 |
</pre> |
9874 |
|
9875 |
<p> |
9876 |
If you used Apple's Disk Utility to leave space for Linux, first delete the |
9877 |
partitions you have created previously to make room for your new install. Use |
9878 |
<c>d</c> in <c>mac-fdisk</c> to delete those partition(s). It will ask for the |
9879 |
partition number to delete. Usually the first partition on NewWorld machines |
9880 |
(Apple_partition_map) could not be deleted. If you would like to start with a |
9881 |
clean disk, you can simply initialize the disk by pressing <c>i</c>. This |
9882 |
will completely erase the disk, so use this with caution. |
9883 |
</p> |
9884 |
|
9885 |
<p> |
9886 |
Second, create an <e>Apple_Bootstrap</e> partition by using <c>b</c>. It will |
9887 |
ask for what block you want to start. Enter the number of your first free |
9888 |
partition, followed by a <c>p</c>. For instance this is <c>2p</c>. |
9889 |
</p> |
9890 |
|
9891 |
<note> |
9892 |
This partition is <e>not</e> a <path>/boot</path> partition. It is not used by |
9893 |
Linux at all; you don't have to place any filesystem on it and you should never |
9894 |
mount it. Apple users don't need an extra partition for <path>/boot</path>. |
9895 |
</note> |
9896 |
|
9897 |
<p> |
9898 |
Now create a swap partition by pressing <c>c</c>. Again <c>mac-fdisk</c> will |
9899 |
ask for what block you want to start this partition from. As we used <c>2</c> |
9900 |
before to create the Apple_Bootstrap partition, you now have to enter |
9901 |
<c>3p</c>. When you're asked for the size, enter <c>512M</c> (or whatever size |
9902 |
you want -- a minimum of 512MB is recommended, but 2 times your physical memory |
9903 |
is the generally accepted size). When asked for a name, enter <c>swap</c>. |
9904 |
</p> |
9905 |
|
9906 |
<p> |
9907 |
To create the root partition, enter <c>c</c>, followed by <c>4p</c> to select |
9908 |
from what block the root partition should start. When asked for the size, enter |
9909 |
<c>4p</c> again. <c>mac-fdisk</c> will interpret this as "Use all available |
9910 |
space". When asked for the name, enter <c>root</c>. |
9911 |
</p> |
9912 |
|
9913 |
<p> |
9914 |
To finish up, write the partition to the disk using <c>w</c> and <c>q</c> to |
9915 |
quit <c>mac-fdisk</c>. |
9916 |
</p> |
9917 |
|
9918 |
<note> |
9919 |
To make sure everything is ok, you should run <c>mac-fdisk -l</c> and check |
9920 |
whether all the partitions are there. If you don't see any of the partitions |
9921 |
you created, or the changes you made, you should reinitialize your partitions |
9922 |
by pressing "i" in mac-fdisk. Note that this will recreate the partition map |
9923 |
and thus remove all your partitions. |
9924 |
</note> |
9925 |
|
9926 |
<p> |
9927 |
Now that your partitions are created, you can continue with |
9928 |
<uri link="#filesystems">Creating Filesystems</uri>. |
9929 |
</p> |
9930 |
|
9931 |
</body> |
9932 |
</section> |
9933 |
<section id="parted"> |
9934 |
<title>Using parted to Partition your Disk (Pegasos and RS/6000)</title> |
9935 |
<body> |
9936 |
|
9937 |
<p> |
9938 |
<c>parted</c>, the Partition Editor, can now handle HFS+ partitions used by |
9939 |
Mac OS and Mac OS X. With this tool you can resize your Mac-partitions and |
9940 |
create space for your Linux partitions. Nevertheless, the example below |
9941 |
describes partitioning for Pegasos machines only. |
9942 |
</p> |
9943 |
|
9944 |
<p> |
9945 |
To begin let's fire up <c>parted</c>: |
9946 |
</p> |
9947 |
|
9948 |
<pre caption="Starting parted"> |
9949 |
# <i>parted /dev/hda</i> |
9950 |
</pre> |
9951 |
|
9952 |
<p> |
9953 |
If the drive is unpartitioned, run <c>mklabel amiga</c> to create a new |
9954 |
disklabel for the drive. |
9955 |
</p> |
9956 |
|
9957 |
<p> |
9958 |
You can type <c>print</c> at any time in parted to display the current partition |
9959 |
table. If at any time you change your mind or made a mistake you can press |
9960 |
<c>Ctrl-c</c> to abort parted. |
9961 |
</p> |
9962 |
|
9963 |
<p> |
9964 |
If you intend to also install MorphOS on your Pegasos create an affs1 filesystem |
9965 |
at the start of the drive. 32MB should be more than enough to store the MorphOS |
9966 |
kernel. If you have a Pegasos I or intend to use any filesystem besides ext2 or |
9967 |
ext3, you will also have to store your Linux kernel on this partition (the |
9968 |
Pegasos II can only boot from ext2/ext3 or affs1 partitions). To create the |
9969 |
partition run <c>mkpart primary affs1 START END</c> where <c>START</c> and |
9970 |
<c>END</c> should be replaced with the megabyte range (e.g. <c>0 32</c>) which |
9971 |
creates a 32 MB partition starting at 0MB and ending at 32MB. If you chose to |
9972 |
create an ext2 or ext3 partition instead, substitute ext2 or ext3 for affs1 in |
9973 |
the mkpart command. |
9974 |
</p> |
9975 |
|
9976 |
<p> |
9977 |
You will need to create two partitions for Linux, one root filesystem and one |
9978 |
swap partition. Run <c>mkpart primary START END</c> to create each partition, |
9979 |
replacing <c>START</c> and <c>END</c> with the desired megabyte boundries. |
9980 |
</p> |
9981 |
|
9982 |
<p> |
9983 |
It is generally recommended that you create a swap partition that is two times |
9984 |
bigger than the amount of RAM in your computer, but at least 512Mb is |
9985 |
recommended. To create the swap partition, run |
9986 |
<c>mkpart primary linux-swap START END</c> with START and END again denoting |
9987 |
the partition boundries. |
9988 |
</p> |
9989 |
|
9990 |
<p> |
9991 |
When you are done in parted simply type <c>quit</c>. |
9992 |
</p> |
9993 |
|
9994 |
</body> |
9995 |
</section> |
9996 |
<section id="filesystems"> |
9997 |
<title>Creating Filesystems</title> |
9998 |
<subsection> |
9999 |
<title>Introduction</title> |
10000 |
<body> |
10001 |
|
10002 |
<p> |
10003 |
Now that your partitions are created, it is time to place a filesystem on them. |
10004 |
If you're not sure which filesystems to choose and are happy with our defaults, |
10005 |
continue with |
10006 |
<uri link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
10007 |
Otherwise, read on to learn about the available filesystems. |
10008 |
</p> |
10009 |
|
10010 |
</body> |
10011 |
</subsection> |
10012 |
<subsection> |
10013 |
<title>Filesystems?</title> |
10014 |
<body> |
10015 |
|
10016 |
<p> |
10017 |
Several filesystems are available for use on the PowerPC architecture including |
10018 |
ext2, ext3, ReiserFS and XFS, each with their strengths and faults. |
10019 |
</p> |
10020 |
|
10021 |
<p> |
10022 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
10023 |
journaling, which means that routine ext2 filesystem checks at startup time can |
10024 |
be quite time-consuming. There is now quite a selection of journaled |
10025 |
filesystems that can be checked for consistency very quickly and are thus |
10026 |
generally preferred over their non-journaled counterparts. |
10027 |
</p> |
10028 |
|
10029 |
<p> |
10030 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
10031 |
journaling for fast recovery in addition to other enhanced journaling modes like |
10032 |
full data and ordered data journaling. It uses an HTree index that enables high |
10033 |
performance in almost all situations. In short, ext3 is a very good and reliable |
10034 |
filesystem. |
10035 |
</p> |
10036 |
|
10037 |
<p> |
10038 |
<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall |
10039 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
10040 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
10041 |
extremely well and has metadata journaling. ReiserFS is solid and usable as |
10042 |
both general-purpose filesystem and for extreme cases such as the creation of |
10043 |
large filesystems, very large files and directories containing tens of |
10044 |
thousands of small files. |
10045 |
</p> |
10046 |
|
10047 |
<p> |
10048 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
10049 |
feature-set and is optimized for scalability. We only recommend using this |
10050 |
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
10051 |
an uninterruptible power supply. Because XFS aggressively caches in-transit data |
10052 |
in RAM, improperly designed programs (those that don't take proper precautions |
10053 |
when writing files to disk and there are quite a few of them) can lose a good |
10054 |
deal of data if the system goes down unexpectedly. |
10055 |
</p> |
10056 |
|
10057 |
</body> |
10058 |
</subsection> |
10059 |
<subsection> |
10060 |
<title>Activating the Swap Partition</title> |
10061 |
<body> |
10062 |
|
10063 |
<p> |
10064 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
10065 |
</p> |
10066 |
|
10067 |
<pre caption="Creating a swap signature"> |
10068 |
# <i>mkswap /dev/hda3</i> |
10069 |
</pre> |
10070 |
|
10071 |
<p> |
10072 |
To activate the swap partition, use <c>swapon</c>: |
10073 |
</p> |
10074 |
|
10075 |
<pre caption="Activating the swap partition"> |
10076 |
# <i>swapon /dev/hda3</i> |
10077 |
</pre> |
10078 |
|
10079 |
<p> |
10080 |
Create and activate the swap now before creating other filesystems. |
10081 |
</p> |
10082 |
|
10083 |
</body> |
10084 |
</subsection> |
10085 |
<subsection id="filesystems-apply"> |
10086 |
<title>Applying a Filesystem to a Partition</title> |
10087 |
<body> |
10088 |
|
10089 |
<p> |
10090 |
To create a filesystem on a partition or volume, there are tools available for |
10091 |
each possible filesystem: |
10092 |
</p> |
10093 |
|
10094 |
<table> |
10095 |
<tr> |
10096 |
<th>Filesystem</th> |
10097 |
<th>Creation Command</th> |
10098 |
</tr> |
10099 |
<tr> |
10100 |
<ti>ext2</ti> |
10101 |
<ti><c>mke2fs</c></ti> |
10102 |
</tr> |
10103 |
<tr> |
10104 |
<ti>ext3</ti> |
10105 |
<ti><c>mke2fs -j</c></ti> |
10106 |
</tr> |
10107 |
<tr> |
10108 |
<ti>reiserfs</ti> |
10109 |
<ti><c>mkreiserfs</c></ti> |
10110 |
</tr> |
10111 |
<tr> |
10112 |
<ti>xfs</ti> |
10113 |
<ti><c>mkfs.xfs</c></ti> |
10114 |
</tr> |
10115 |
</table> |
10116 |
|
10117 |
<p> |
10118 |
For instance, to make an ext3 filesystem on the root partition |
10119 |
(<path>/dev/hda4</path> in our example), you would use: |
10120 |
</p> |
10121 |
|
10122 |
<pre caption="Applying a filesystem on a partition"> |
10123 |
# <i>mke2fs -j /dev/hda4</i> |
10124 |
</pre> |
10125 |
|
10126 |
<p> |
10127 |
Now create the filesystems on your newly created partitions (or logical |
10128 |
volumes). |
10129 |
</p> |
10130 |
|
10131 |
<impo> |
10132 |
If you choose to use ReiserFS for <path>/</path>, do not change its default |
10133 |
block size if you will also be using <c>yaboot</c> as your bootloader, as |
10134 |
explained in <uri link="?part=1&chap=10">Configuring the Bootloader</uri>. |
10135 |
</impo> |
10136 |
|
10137 |
<note> |
10138 |
On the PegasosII your partition which holds the kernel must be ext2, ext3 or |
10139 |
affs1. NewWorld machines can boot from any of ext2, ext3, XFS, ReiserFS or |
10140 |
even HFS/HFS+ filesystems. On OldWorld machines booting with BootX, the kernel |
10141 |
must be placed on an HFS partition, but this will be completed when you |
10142 |
configure your bootloader. |
10143 |
</note> |
10144 |
|
10145 |
</body> |
10146 |
</subsection> |
10147 |
</section> |
10148 |
<section> |
10149 |
<title>Mounting</title> |
10150 |
<body> |
10151 |
|
10152 |
<p> |
10153 |
Now that your partitions are initialized and are housing a filesystem, it is |
10154 |
time to mount those partitions. Use the <c>mount</c> command. As an example we |
10155 |
mount the root partition: |
10156 |
</p> |
10157 |
|
10158 |
<pre caption="Mounting partitions"> |
10159 |
# <i>mount /dev/hda4 /mnt/gentoo</i> |
10160 |
</pre> |
10161 |
|
10162 |
<note> |
10163 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
10164 |
change its permissions after mounting and unpacking with |
10165 |
<c>chmod 1777 /mnt/gentoo/tmp</c>. This is also true for <path>/var/tmp</path>. |
10166 |
</note> |
10167 |
|
10168 |
<p> |
10169 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
10170 |
Installation Files</uri>. |
10171 |
</p> |
10172 |
|
10173 |
</body> |
10174 |
</section> |
10175 |
</sections> |
10176 |
|
10177 |
|
10178 |
|
10179 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc-kernel.xml |
10180 |
|
10181 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc-kernel.xml?rev=1.1&view=markup |
10182 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc-kernel.xml?rev=1.1&content-type=text/plain |
10183 |
|
10184 |
Index: hb-install-ppc-kernel.xml |
10185 |
=================================================================== |
10186 |
<?xml version='1.0' encoding='UTF-8'?> |
10187 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
10188 |
|
10189 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
10190 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
10191 |
|
10192 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc-kernel.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
10193 |
|
10194 |
<sections> |
10195 |
|
10196 |
<version>8.3</version> |
10197 |
<date>2007-07-29</date> |
10198 |
|
10199 |
<section> |
10200 |
<title>Timezone</title> |
10201 |
<body> |
10202 |
|
10203 |
<p> |
10204 |
You first need to select your timezone so that your system knows where it is |
10205 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
10206 |
it to <path>/etc/localtime</path>. Please avoid the |
10207 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
10208 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact |
10209 |
GMT+8. |
10210 |
</p> |
10211 |
|
10212 |
<pre caption="Setting the timezone information"> |
10213 |
# <i>ls /usr/share/zoneinfo</i> |
10214 |
<comment>(Suppose you want to use GMT)</comment> |
10215 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
10216 |
</pre> |
10217 |
|
10218 |
</body> |
10219 |
</section> |
10220 |
<section> |
10221 |
<title>Installing the Kernel Sources</title> |
10222 |
<subsection> |
10223 |
<title>Choosing a Kernel</title> |
10224 |
<body> |
10225 |
|
10226 |
<p> |
10227 |
The core around which all distributions are built is the Linux kernel. It is the |
10228 |
layer between the user programs and your system hardware. Gentoo provides its |
10229 |
users several possible kernels to choose from. A full listing with description |
10230 |
is available at the |
10231 |
<uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>. |
10232 |
</p> |
10233 |
|
10234 |
<p> |
10235 |
We suggest using <c>gentoo-sources</c> on PPC, which is a recent 2.6 kernel. |
10236 |
</p> |
10237 |
|
10238 |
<pre caption="Installing a kernel source"> |
10239 |
# <i>emerge --usepkg gentoo-sources</i> |
10240 |
</pre> |
10241 |
|
10242 |
<p> |
10243 |
If you take a look in <path>/usr/src</path> you should see a symlink named |
10244 |
<path>linux</path> pointing to your current kernel source. In this case, the |
10245 |
installed kernel source points to <c>gentoo-sources-<keyval |
10246 |
id="kernel-version"/></c>. Your version may be different, so keep this in mind. |
10247 |
</p> |
10248 |
|
10249 |
<pre caption="Viewing the kernel source symlink"> |
10250 |
# <i>ls -l /usr/src/linux</i> |
10251 |
lrwxrwxrwx 1 root root 22 Mar 18 16:23 /usr/src/linux -> linux-<keyval id="kernel-gentoo"/> |
10252 |
</pre> |
10253 |
|
10254 |
<p> |
10255 |
Now it is time to configure and compile your kernel source. You can use |
10256 |
<c>genkernel</c> for this, which will build a generic kernel as used by the |
10257 |
Installation CD. We explain the "manual" configuration first though, as it is |
10258 |
a more efficient configuration. |
10259 |
</p> |
10260 |
|
10261 |
<p> |
10262 |
If you want to manually configure your kernel, continue now with <uri |
10263 |
link="#manual">Default: Manual Configuration</uri>. If you want to use |
10264 |
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
10265 |
genkernel</uri> instead. |
10266 |
</p> |
10267 |
|
10268 |
</body> |
10269 |
</subsection> |
10270 |
</section> |
10271 |
<section id="manual"> |
10272 |
<title>Default: Manual Configuration</title> |
10273 |
<subsection> |
10274 |
<title>Introduction</title> |
10275 |
<body> |
10276 |
|
10277 |
<p> |
10278 |
Manually configuring a kernel is often seen as the most difficult procedure a |
10279 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
10280 |
few kernels you won't even remember that it was difficult ;) |
10281 |
</p> |
10282 |
|
10283 |
<p> |
10284 |
However, one thing <e>is</e> true: you must know your system when you start |
10285 |
configuring a kernel manually. Most information can be gathered by emerging |
10286 |
pciutils (<c>emerge --usepkg pciutils</c>) which contains the program |
10287 |
<c>lspci</c>. You will now be able to use <c>lspci</c> within the chrooted |
10288 |
environment. You may safely ignore any <e>pcilib</e> warnings (such as pcilib: |
10289 |
cannot open /sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, |
10290 |
you can run <c>lspci</c> from a <e>non-chrooted</e> environment. The results |
10291 |
are the same. You can also run <c>lsmod</c> to see what kernel modules the |
10292 |
Installation CD uses (it might provide you with a nice hint on what to enable). |
10293 |
Another place to look for clues as to what components to enable is to check the |
10294 |
kernel message logs from the successful boot that got you this far. Type |
10295 |
<c>dmesg</c> to see these kernel messages. |
10296 |
</p> |
10297 |
|
10298 |
<p> |
10299 |
Now, go to your kernel source directory, it's time to configure your kernel. |
10300 |
Start by configuring a kernel that will boot on most 32 Bit PowerPC machines |
10301 |
by first running <c>make pmac32_defconfig</c>. After the default configuration |
10302 |
has been generated, run <c>make menuconfig</c> to start an ncurses-based |
10303 |
configuration menu. |
10304 |
</p> |
10305 |
|
10306 |
<pre caption="Invoking menuconfig"> |
10307 |
# <i>cd /usr/src/linux</i> |
10308 |
# <i>make pmac32_defconfig</i> |
10309 |
# <i>make menuconfig</i> |
10310 |
</pre> |
10311 |
|
10312 |
<p> |
10313 |
You will be greeted with several configuration sections. We'll first list some |
10314 |
options you must activate (otherwise Gentoo will not function, or not function |
10315 |
properly without additional tweaks). |
10316 |
</p> |
10317 |
|
10318 |
</body> |
10319 |
</subsection> |
10320 |
<subsection> |
10321 |
<title>Activating Required Options</title> |
10322 |
<body> |
10323 |
|
10324 |
<p> |
10325 |
First of all, activate the use of development and experimental code/drivers. |
10326 |
You need this, otherwise some very important code/drivers won't show up: |
10327 |
</p> |
10328 |
|
10329 |
<pre caption="Selecting experimental code/drivers"> |
10330 |
Code maturity level options ---> |
10331 |
[*] Prompt for development and/or incomplete code/drivers |
10332 |
</pre> |
10333 |
|
10334 |
<p> |
10335 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
10336 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
10337 |
able to mount your partitions. Also select the <c>/proc file system</c> and |
10338 |
<c>Virtual memory</c>. Make sure that you also enable support for Amiga |
10339 |
partitions if you are using a Pegasos, or Macintosh partitions if you are using |
10340 |
an Apple computer. |
10341 |
</p> |
10342 |
|
10343 |
<pre caption="Selecting necessary file systems"> |
10344 |
File systems ---> |
10345 |
Pseudo Filesystems ---> |
10346 |
<comment>(/proc may already be forced on by your configuration, if so, you'll see --- instead)</comment> |
10347 |
[*] /proc file system support |
10348 |
[*] Virtual memory file system support (former shm fs) |
10349 |
Partition Types ---> |
10350 |
[*] Advanced partition support |
10351 |
[*] Amiga partition table support |
10352 |
[*] Macintosh partition map support |
10353 |
|
10354 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
10355 |
<*> Reiserfs support |
10356 |
<*> Ext3 journalling file system support |
10357 |
<*> Second extended fs support |
10358 |
<*> XFS filesystem support |
10359 |
</pre> |
10360 |
|
10361 |
<p> |
10362 |
Users of NewWorld and OldWorld machines will want HFS support as well. OldWorld |
10363 |
users require it for copying compiled kernels to the MacOS partition. NewWorld |
10364 |
users require it for configuring the special Apple_Bootstrap partition: |
10365 |
</p> |
10366 |
|
10367 |
<pre caption="Activating HFS support"> |
10368 |
File Systems ---> |
10369 |
Miscellaneous filesystems ---> |
10370 |
<M> Apple Macintosh file system support |
10371 |
<M> Apple Extended HFS file system support |
10372 |
</pre> |
10373 |
|
10374 |
<p> |
10375 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
10376 |
modem, you will need the following options in the kernel: |
10377 |
</p> |
10378 |
|
10379 |
<pre caption="Selecting PPPoE necessary drivers"> |
10380 |
Device Drivers ---> |
10381 |
Network device support ---> |
10382 |
<*> PPP (point-to-point protocol) support |
10383 |
<*> PPP support for async serial ports |
10384 |
<*> PPP support for sync tty ports |
10385 |
</pre> |
10386 |
|
10387 |
<p> |
10388 |
The two compression options won't harm but are not always needed. The <c>PPP |
10389 |
over Ethernet</c> option might only be used by <c>ppp</c> when configured to |
10390 |
perform kernel mode PPPoE. |
10391 |
</p> |
10392 |
|
10393 |
<p> |
10394 |
Don't forget to include support in the kernel for your ethernet card! Most |
10395 |
newer Apple computers use the SunGEM ethernet driver. Older iMacs commonly use |
10396 |
the BMAC driver. |
10397 |
</p> |
10398 |
|
10399 |
<pre caption="Selecting the network driver"> |
10400 |
Device Drivers ---> |
10401 |
Network device support ---> |
10402 |
Ethernet (10 or 100Mbit) ---> |
10403 |
[*] Ethernet (10 or 100Mbit) |
10404 |
<*> Generic Media Independent Interface device support |
10405 |
<*> MACE (Power Mac ethernet) support |
10406 |
<*> BMAC (G3 ethernet) support |
10407 |
<*> Sun GEM support |
10408 |
</pre> |
10409 |
|
10410 |
<p> |
10411 |
At this time, full kernel preemption may still be unstable on PPC and may cause |
10412 |
compilation failures and random segfaults. It is <e>strongly</e> suggested |
10413 |
that you do not use this feature. Both <e>Voluntary Preemption</e> and |
10414 |
<e>No Forced Preemption</e> should be safe. |
10415 |
</p> |
10416 |
|
10417 |
<pre caption="Ensure the Preemptible Kernel Option is Off"> |
10418 |
Kernel options ---> |
10419 |
<comment>(Select One)</comment> |
10420 |
Preemption Model |
10421 |
(X) No Forced Preemption (Server) |
10422 |
(X) Voluntary Kernel Preemption (Desktop) |
10423 |
</pre> |
10424 |
|
10425 |
<p> |
10426 |
If you're booting from Firewire, you'll need to enable these options. If you do |
10427 |
not want to compile in support, you'll need to include these modules and their |
10428 |
dependencies in an initrd. |
10429 |
</p> |
10430 |
|
10431 |
<pre caption="Enable support for firewire devices on boot"> |
10432 |
Device Drivers ---> |
10433 |
IEEE 1394 (FireWire) support ---> |
10434 |
<*> IEEE 1394 (FireWire) support |
10435 |
<*> OHCI-1394 support |
10436 |
<*> SBP-2 support (Harddisks etc.) |
10437 |
</pre> |
10438 |
|
10439 |
<p> |
10440 |
If you're booting from USB, you'll need to enable these options. If you do not |
10441 |
want to compile in support, you'll need to include these modules and their |
10442 |
dependencies in an initrd. |
10443 |
</p> |
10444 |
|
10445 |
<pre caption="Enable support for USB devices on boot"> |
10446 |
Device Drivers ---> |
10447 |
USB support ---> |
10448 |
<*> Support for Host-side USB |
10449 |
<*> OHCI HCD support |
10450 |
<*> USB Mass Storage support |
10451 |
</pre> |
10452 |
|
10453 |
<p> |
10454 |
Do not turn off kernel framebuffer support as it is required for a successful |
10455 |
boot. If you are using an NVIDIA based chipset, you should use the Open Firmware |
10456 |
framebuffer. If you are using an ATI based chipset, you should select the |
10457 |
framebuffer driver based upon your chipset (Mach64, Rage128 or Radeon). |
10458 |
</p> |
10459 |
|
10460 |
<pre caption="Choosing a Framebuffer Driver"> |
10461 |
Device Drivers ---> |
10462 |
Graphics support ---> |
10463 |
<*> Support for frame buffer devices |
10464 |
[*] Open Firmware frame buffer device support |
10465 |
<*> ATI Radeon display support |
10466 |
<*> ATI Rage128 display support |
10467 |
<*> ATI Mach64 display support |
10468 |
Console display driver support ---> |
10469 |
<*> Framebuffer Console support |
10470 |
</pre> |
10471 |
|
10472 |
<note> |
10473 |
If you select more than one framebuffer device, it may default to a less than |
10474 |
optimal driver. Either use only one framebuffer device or specify which |
10475 |
to use by passing the driver to use to the kernel on boot by appending a video |
10476 |
line such as: <c>video=radeonfb</c>. |
10477 |
</note> |
10478 |
|
10479 |
<p> |
10480 |
When you're done configuring your kernel, continue with <uri |
10481 |
link="#compiling">Compiling and Installing</uri>. |
10482 |
</p> |
10483 |
|
10484 |
</body> |
10485 |
</subsection> |
10486 |
<subsection id="compiling"> |
10487 |
<title>Compiling and Installing</title> |
10488 |
<body> |
10489 |
|
10490 |
<p> |
10491 |
Now that your kernel is configured, it is time to compile and install it. Exit |
10492 |
the configuration menu and run the following commands: |
10493 |
</p> |
10494 |
|
10495 |
<pre caption="Compiling the kernel"> |
10496 |
# <i>make && make modules_install</i> |
10497 |
</pre> |
10498 |
|
10499 |
<p> |
10500 |
When the kernel has finished compiling, copy the kernel image to |
10501 |
<path>/boot</path> as shown below. If you have a separate boot partition, as |
10502 |
on Pegasos computers, be sure that it is mounted properly. If you are using |
10503 |
BootX to boot, we'll copy the kernel later. |
10504 |
</p> |
10505 |
|
10506 |
<p> |
10507 |
Yaboot and BootX expect to use an uncompressed kernel unlike many other |
10508 |
bootloaders. The uncompressed kernel is called vmlinux and it is placed in |
10509 |
<path>/usr/src/linux</path> after the kernel has finished compiling. If you are |
10510 |
using a Pegasos machine, the Pegasos firmware requires a compressed kernel |
10511 |
called zImage which can be found in |
10512 |
<path>/usr/src/linux/arch/powerpc/boot/images</path>. |
10513 |
</p> |
10514 |
|
10515 |
<pre caption="Installing the kernel"> |
10516 |
# <i>cd /usr/src/linux</i> |
10517 |
<comment>Note, your kernel version might be different</comment> |
10518 |
<comment>(Apple/IBM)</comment> |
10519 |
# <i>cp vmlinux /boot/<keyval id="kernel-name"/></i> |
10520 |
<comment>(Pegasos)</comment> |
10521 |
# <i>cp arch/powerpc/boot/images/zImage /boot/<keyval id="kernel-name"/></i> |
10522 |
</pre> |
10523 |
|
10524 |
<p> |
10525 |
Now continue with <uri link="#kernel_modules">Installing Separate Kernel |
10526 |
Modules</uri>. |
10527 |
</p> |
10528 |
|
10529 |
</body> |
10530 |
</subsection> |
10531 |
</section> |
10532 |
<section id="kernel_modules"> |
10533 |
<title>Installing Separate Kernel Modules</title> |
10534 |
<subsection> |
10535 |
<title>Configuring the Modules</title> |
10536 |
<body> |
10537 |
|
10538 |
<p> |
10539 |
You should list the modules you want automatically loaded in |
10540 |
<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra options to |
10541 |
the modules if required. |
10542 |
</p> |
10543 |
|
10544 |
<p> |
10545 |
To view all available modules, run the following command: |
10546 |
</p> |
10547 |
|
10548 |
<pre caption="Viewing all available modules"> |
10549 |
# <i>modprobe -l</i> |
10550 |
</pre> |
10551 |
|
10552 |
<p> |
10553 |
For instance, to automatically load the <c>3c59x</c> module, edit the |
10554 |
<path>kernel-2.6</path> file and add the module to it, one module on a line. |
10555 |
</p> |
10556 |
|
10557 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
10558 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
10559 |
</pre> |
10560 |
|
10561 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
10562 |
3c59x |
10563 |
</pre> |
10564 |
|
10565 |
<p> |
10566 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
10567 |
your System</uri>. |
10568 |
</p> |
10569 |
|
10570 |
</body> |
10571 |
</subsection> |
10572 |
</section> |
10573 |
<section id="genkernel"> |
10574 |
<title>Alternative: Using genkernel</title> |
10575 |
<body> |
10576 |
|
10577 |
<p> |
10578 |
Now that your kernel source tree is installed, it's now time to compile your |
10579 |
kernel by using our <c>genkernel</c> script to automatically build a kernel for |
10580 |
you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
10581 |
way our Installation CD kernel is configured. This means that when you use |
10582 |
<c>genkernel</c> to build your kernel, your system will generally detect all |
10583 |
your hardware at boot-time, just like our Installation CD does. Because |
10584 |
genkernel doesn't require any manual kernel configuration, it is an ideal |
10585 |
solution for those users who may not be comfortable compiling their own |
10586 |
kernels. |
10587 |
</p> |
10588 |
|
10589 |
<p> |
10590 |
Now, let's see how to use genkernel. First, emerge the genkernel ebuild: |
10591 |
</p> |
10592 |
|
10593 |
<pre caption="Emerging genkernel"> |
10594 |
# <i>emerge --usepkg genkernel</i> |
10595 |
</pre> |
10596 |
|
10597 |
<p> |
10598 |
Next, copy over the kernel configuration used by the Installation CD to the |
10599 |
location where genkernel looks for the default kernel configuration: |
10600 |
</p> |
10601 |
|
10602 |
<pre caption="Copying over the Installation CD kernel config"> |
10603 |
# <i>zcat /proc/config.gz > /usr/share/genkernel/ppc/kernel-config-2.6</i> |
10604 |
</pre> |
10605 |
|
10606 |
<p> |
10607 |
If you are using firewire or USB to boot, you'll need to add modules to the |
10608 |
initrd. Edit <path>/usr/share/genkernel/ppc/modules_load</path> and change |
10609 |
<c>MODULES_FIREWIRE="ieee1394 ohci1394 sbp2"</c> for firewire support or |
10610 |
<c>MODULES_USB="usbcore ohci-hcd ehci-hcd usb-storage"</c> for USB support. |
10611 |
</p> |
10612 |
|
10613 |
<p> |
10614 |
Before compiling your sources, the fstab needs a slight adjustment. The rest of |
10615 |
the fstab will be completed during a later step, so don't worry about the |
10616 |
details now. If you did not create a separate boot partition (NOT bootstrap, |
10617 |
that's different), remove the line referencing <path>/boot</path> from |
10618 |
<path>/etc/fstab</path>. This will need to be done on most Apple computers. |
10619 |
</p> |
10620 |
|
10621 |
<pre caption="Removing /boot from /etc/fstab on machines without a boot partition"> |
10622 |
# <i>nano -w /etc/fstab</i> |
10623 |
<comment>Remove this line</comment> |
10624 |
/dev/BOOT /boot ext2 noauto,noatime 1 2 |
10625 |
</pre> |
10626 |
|
10627 |
<p> |
10628 |
Now, compile your kernel sources by running <c>genkernel --genzimage all</c>. |
10629 |
For Pegasos, we will need to use a different config and create a zImage instead |
10630 |
of the vmlinux kernel used on Apple machines. Be aware, as <c>genkernel</c> |
10631 |
compiles a kernel that supports almost all hardware, this compilation can take |
10632 |
quite a while to finish! |
10633 |
</p> |
10634 |
|
10635 |
<p> |
10636 |
Note that, if your partition where the kernel should be located doesn't use ext2 |
10637 |
or ext3 as filesystem you might need to manually configure your kernel using |
10638 |
<c>genkernel --menuconfig all</c> and add support for your |
10639 |
filesystem <e>in</e> the kernel (i.e. <e>not</e> as a module). Users of EVMS2 or |
10640 |
LVM2 will probably want to add <c>--evms2</c> or <c>--lvm2</c> as an argument as |
10641 |
well. |
10642 |
</p> |
10643 |
|
10644 |
<pre caption="Running genkernel"> |
10645 |
# <i>genkernel all</i> |
10646 |
</pre> |
10647 |
|
10648 |
<pre caption="Running genkernel on the Pegasos"> |
10649 |
# <i>genkernel --genzimage --kernel-config=/usr/share/genkernel/ppc/Pegasos all</i> |
10650 |
</pre> |
10651 |
|
10652 |
<p> |
10653 |
Once <c>genkernel</c> completes, a kernel, full set of modules and |
10654 |
<e>initial root disk</e> (initrd) will be created. We will use the kernel |
10655 |
and initrd when configuring a boot loader later in this document. Write |
10656 |
down the names of the kernel and initrd as you will need them when writing |
10657 |
the bootloader configuration file. The initrd will be started immediately after |
10658 |
booting to perform hardware autodetection (just like on the Installation CD) |
10659 |
before your "real" system starts up. Be sure to also copy down the required |
10660 |
boot arguments, these are required for a successful boot with genkernel. |
10661 |
</p> |
10662 |
|
10663 |
<pre caption="Checking the created kernel image name and initrd"> |
10664 |
<comment>Note, your kernel version might be different</comment> |
10665 |
# <i>ls /boot/kernel-genkernel-ppc-<keyval id="kernel-gentoo"/> /boot/initramfs-genkernel-ppc-<keyval id="kernel-gentoo"/></i> |
10666 |
</pre> |
10667 |
|
10668 |
<p> |
10669 |
Now continue with <uri link="?part=1&chap=8">Configuring your System</uri>. |
10670 |
</p> |
10671 |
|
10672 |
</body> |
10673 |
</section> |
10674 |
</sections> |
10675 |
|
10676 |
|
10677 |
|
10678 |
|
10679 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc-medium.xml |
10680 |
|
10681 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc-medium.xml?rev=1.1&view=markup |
10682 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc-medium.xml?rev=1.1&content-type=text/plain |
10683 |
|
10684 |
Index: hb-install-ppc-medium.xml |
10685 |
=================================================================== |
10686 |
<?xml version='1.0' encoding='UTF-8'?> |
10687 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
10688 |
|
10689 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
10690 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
10691 |
|
10692 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-ppc-medium.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
10693 |
|
10694 |
<sections> |
10695 |
|
10696 |
<version>8.1</version> |
10697 |
<date>2007-06-29</date> |
10698 |
|
10699 |
<section> |
10700 |
<title>Hardware Requirements</title> |
10701 |
<subsection> |
10702 |
<title>Introduction</title> |
10703 |
<body> |
10704 |
|
10705 |
<p> |
10706 |
Before we start, we first list what hardware requirements you need to |
10707 |
successfully install Gentoo on your box. |
10708 |
</p> |
10709 |
|
10710 |
</body> |
10711 |
</subsection> |
10712 |
<subsection> |
10713 |
<title>Hardware Requirements</title> |
10714 |
<body> |
10715 |
|
10716 |
<table> |
10717 |
<tr> |
10718 |
<th>Apple NewWorld Machines</th> |
10719 |
<ti> |
10720 |
Power/PowerPC microprocessors (G3, G4, G5) such as iMac, eMac, iBook |
10721 |
PowerBook, Xserver, PowerMac |
10722 |
</ti> |
10723 |
</tr> |
10724 |
<tr> |
10725 |
<th>Apple OldWorld machines</th> |
10726 |
<ti> |
10727 |
Apple Machines with an Open Firmware revision less than 3, such as the Beige |
10728 |
G3s, PCI PowerMacs and PCI PowerBooks. PCI based Apple Clones should also |
10729 |
be supported. |
10730 |
</ti> |
10731 |
</tr> |
10732 |
<tr> |
10733 |
<th>Genesi</th> |
10734 |
<ti> |
10735 |
Pegasos I/II, Open Desktop Workstation, Efika |
10736 |
</ti> |
10737 |
</tr> |
10738 |
<tr> |
10739 |
<th>IBM</th> |
10740 |
<ti> |
10741 |
RS/6000, iSeries, pSeries |
10742 |
</ti> |
10743 |
</tr> |
10744 |
<tr> |
10745 |
<th>Memory</th> |
10746 |
<ti>At least 64 MB</ti> |
10747 |
</tr> |
10748 |
<tr> |
10749 |
<th>Diskspace</th> |
10750 |
<ti>1.5 GB (excluding swap space)</ti> |
10751 |
</tr> |
10752 |
<tr> |
10753 |
<th>Swap space</th> |
10754 |
<ti>At least 256 MB</ti> |
10755 |
</tr> |
10756 |
</table> |
10757 |
|
10758 |
<p> |
10759 |
Be sure to read the <uri link="/doc/en/gentoo-ppc-faq.xml">Gentoo PPC FAQ</uri> |
10760 |
for help with some common installation related issues or if you're unsure as to |
10761 |
just what's in that PowerPC machine you've got sitting on your desk right now. |
10762 |
</p> |
10763 |
|
10764 |
</body> |
10765 |
</subsection> |
10766 |
</section> |
10767 |
<!-- Copy/paste of hb-install-x86-medium.xml, with s/x86/ppc/ --> |
10768 |
<!-- START --> |
10769 |
<section> |
10770 |
<title>The Gentoo Universal Installation CD</title> |
10771 |
<subsection> |
10772 |
<title>Introduction</title> |
10773 |
<body> |
10774 |
|
10775 |
<p> |
10776 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
10777 |
Such a tarball is an archive that contains a minimal environment from |
10778 |
which you can succesfully install Gentoo Linux onto your system. |
10779 |
</p> |
10780 |
|
10781 |
<p> |
10782 |
Installations using a stage1 or stage2 tarball file are not documented in the |
10783 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
10784 |
FAQ</uri> on these matters. |
10785 |
</p> |
10786 |
|
10787 |
</body> |
10788 |
</subsection> |
10789 |
<subsection> |
10790 |
<title>Gentoo Universal Installation CD</title> |
10791 |
<body> |
10792 |
|
10793 |
<p> |
10794 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
10795 |
environment. It allows you to boot Linux from the CD. During the boot process |
10796 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
10797 |
Installation CDs are maintained by Gentoo developers. |
10798 |
</p> |
10799 |
|
10800 |
<p> |
10801 |
There currently are two Installation CDs available: |
10802 |
</p> |
10803 |
|
10804 |
<ul> |
10805 |
<li> |
10806 |
The Universal Installation CD contains everything you need to install |
10807 |
Gentoo. It provides stage3 files for common architectures, source code |
10808 |
for the extra applications you need to choose from and, of course, the |
10809 |
installation instructions for your architecture. |
10810 |
</li> |
10811 |
<li> |
10812 |
The Minimal Installation CD contains only a minimal environment that allows |
10813 |
you to boot up and configure your network so you can connect to the |
10814 |
Internet. It does not contain any additional files and cannot be used |
10815 |
during the current installation approach. |
10816 |
</li> |
10817 |
</ul> |
10818 |
|
10819 |
<p> |
10820 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
10821 |
additional resource that you can exploit during the installation of your Gentoo |
10822 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
10823 |
you to easily and quickly install additional applications (such as |
10824 |
OpenOffice.org, KDE, GNOME, ...) immediately after the Gentoo installation and |
10825 |
right before you update your Portage tree. |
10826 |
</p> |
10827 |
|
10828 |
<p> |
10829 |
The use of the Package CD is covered later in this document. |
10830 |
</p> |
10831 |
|
10832 |
</body> |
10833 |
</subsection> |
10834 |
</section> |
10835 |
<!-- STOP --> |
10836 |
<section> |
10837 |
<title>Download, Burn and Boot the Gentoo Universal Installation CD</title> |
10838 |
<subsection> |
10839 |
<title>Downloading and Burning the Installation CD</title> |
10840 |
<body> |
10841 |
|
10842 |
<p> |
10843 |
You can download the Universal Installation CD (and, if you want to, the |
10844 |
Packages CD as well) from one of our <uri |
10845 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located in |
10846 |
the <path><keyval id="release-dir"/>installcd</path> directory; the Package CDs |
10847 |
are located in the <path><keyval id="release-dir"/>packagecd</path> directory. |
10848 |
</p> |
10849 |
|
10850 |
<p> |
10851 |
Inside those directories you'll find ISO-files. Those are full CD images which |
10852 |
you can write on a CD-R. |
10853 |
</p> |
10854 |
|
10855 |
<p> |
10856 |
After downloading the file, you can verify its integrity to see if it is |
10857 |
corrupted or not: |
10858 |
</p> |
10859 |
|
10860 |
<ul> |
10861 |
<li> |
10862 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
10863 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
10864 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows). |
10865 |
Verifying MD5 checksums with Mac OS X is described in the <uri |
10866 |
link="/doc/en/gentoo-ppc-faq.xml#doc_chap1">Gentoo PPC FAQ</uri>. |
10867 |
</li> |
10868 |
<li> |
10869 |
You can verify the cryptographic signature that we provide. You need to |
10870 |
obtain the public key we use (0x17072058) before you proceed though. |
10871 |
</li> |
10872 |
</ul> |
10873 |
|
10874 |
<p> |
10875 |
To fetch our public key using the GnuPG application, run the following command: |
10876 |
</p> |
10877 |
|
10878 |
<pre caption="Obtaining the public key"> |
10879 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 0x17072058</i> |
10880 |
</pre> |
10881 |
|
10882 |
<p> |
10883 |
Now verify the signature: |
10884 |
</p> |
10885 |
|
10886 |
<pre caption="Verify the cryptographic signature"> |
10887 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
10888 |
</pre> |
10889 |
|
10890 |
<p> |
10891 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
10892 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
10893 |
<c>K3B</c> here; more information can be found in our <uri |
10894 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
10895 |
</p> |
10896 |
|
10897 |
<ul> |
10898 |
<li> |
10899 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
10900 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
10901 |
path). |
10902 |
</li> |
10903 |
<li> |
10904 |
With K3B, select <c>Tools</c> > <c>Burn CD Image</c>. Then you can locate |
10905 |
your ISO file within the 'Image to Burn' area. Finally click <c>Start</c>. |
10906 |
</li> |
10907 |
</ul> |
10908 |
|
10909 |
</body> |
10910 |
</subsection> |
10911 |
<subsection> |
10912 |
<title>Default: Booting the Installation CD with Yaboot</title> |
10913 |
<body> |
10914 |
|
10915 |
<p> |
10916 |
On NewWorld machines place the Installation CD in the CD-ROM and reboot the |
10917 |
system. When the system-start-bell sounds, simply hold down the 'C' until the |
10918 |
CD loads. |
10919 |
</p> |
10920 |
|
10921 |
<p> |
10922 |
After the Installation CD loaded, you will be greeted by a friendly welcome |
10923 |
message and a <e>boot:</e> prompt at the bottom of the screen. |
10924 |
</p> |
10925 |
|
10926 |
<p> |
10927 |
We provide one generic kernel, <e>apple</e>. This kernel is built with support |
10928 |
for multiple CPUs, but it will boot on single processor machines as well. |
10929 |
</p> |
10930 |
|
10931 |
<p> |
10932 |
You can tweak some kernel options at this prompt. The following table lists |
10933 |
some of the available boot options you can add: |
10934 |
</p> |
10935 |
|
10936 |
<table> |
10937 |
<tr> |
10938 |
<th>Boot Option</th> |
10939 |
<th>Description</th> |
10940 |
</tr> |
10941 |
<tr> |
10942 |
<ti><c>video</c></ti> |
10943 |
<ti> |
10944 |
This option takes one of the following vendor-specific tags: |
10945 |
<c>nvidiafb</c>, <c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, |
10946 |
<c>aty128</c> or <c>ofonly</c>. You can follow this tag with the resolution |
10947 |
refresh rate and color depth you want to use. For instance, |
10948 |
<c>video=radeonfb:1280x1024@75-32</c> will select the ATI Radeon frame buffer |
10949 |
at a resolution of 1280x1024 with a refresh rate of 75Hz and a color depth of |
10950 |
32 bits. If you are uncertain what to choose, and the default doesn't work, |
10951 |
<c>video=ofonly</c> will most certainly work. |
10952 |
</ti> |
10953 |
</tr> |
10954 |
<tr> |
10955 |
<ti><c>nol3</c></ti> |
10956 |
<ti> |
10957 |
Disables level 3 cache on some PowerBooks (needed for at least the 17") |
10958 |
</ti> |
10959 |
</tr> |
10960 |
<tr> |
10961 |
<ti><c>dofirewire</c></ti> |
10962 |
<ti> |
10963 |
Enables support for IEEE1394 (FireWire) devices, like external harddisks. |
10964 |
</ti> |
10965 |
</tr> |
10966 |
<tr> |
10967 |
<ti><c>dopcmcia</c></ti> |
10968 |
<ti> |
10969 |
If you want to use PCMCIA devices during your installation (like PCMCIA |
10970 |
network cards) you have to enable this option. |
10971 |
</ti> |
10972 |
</tr> |
10973 |
</table> |
10974 |
|
10975 |
<p> |
10976 |
To use the above options, at the <e>boot:</e> prompt, type <e>apple</e> followed |
10977 |
by the desired option. In the example below, we'll force the kernel to use the |
10978 |
Open Firmware framebuffer instead of the device specific driver. |
10979 |
</p> |
10980 |
|
10981 |
<pre caption="Force the use of the Open Firmware framebuffer"> |
10982 |
boot: <i>apple video=ofonly</i> |
10983 |
</pre> |
10984 |
|
10985 |
<p> |
10986 |
If you don't need to add any options, just hit enter at this prompt, and a |
10987 |
complete Gentoo Linux environment will be loaded from the CD. Continue with |
10988 |
<uri link="#booted">And When You're Booted...</uri>. |
10989 |
</p> |
10990 |
|
10991 |
</body> |
10992 |
</subsection> |
10993 |
<subsection> |
10994 |
<title>Alternative: Booting the Installation CD on a Pegasos</title> |
10995 |
<body> |
10996 |
|
10997 |
<p> |
10998 |
On the Pegasos simply insert the CD and at the SmartFirmware boot-prompt type |
10999 |
<c>boot cd /boot/menu</c>. This will open a small bootmenu where you can choose |
11000 |
between several preconfigured video configs. If you need any special boot |
11001 |
options you can append them to the command-line just like with Yaboot above. |
11002 |
For example: <c>boot cd /boot/pegasos video=radeonfb:1280x1024@75 mem=256M</c>. |
11003 |
The default kernel options (in case something goes wrong and you need it) are |
11004 |
preconfigured with <c>console=ttyS0,115200 console=tty0 init=/linuxrc |
11005 |
looptype=squashfs loop=/image.squashfs cdroot root=/dev/ram0</c>. |
11006 |
</p> |
11007 |
|
11008 |
</body> |
11009 |
</subsection> |
11010 |
|
11011 |
<subsection> |
11012 |
<title>Alternative: Booting the Installation CD with BootX</title> |
11013 |
<body> |
11014 |
|
11015 |
<p> |
11016 |
If you have an OldWorld Mac the bootable portion of the livecd can't be used. |
11017 |
The most simple solution is to use MacOS 9 or earlier to bootstrap into a Linux |
11018 |
environment with a tool called BootX. |
11019 |
</p> |
11020 |
|
11021 |
<p> |
11022 |
First, download <uri link="http://penguinppc.org/projects/bootx/">BootX</uri> |
11023 |
and unpack the archive. Copy the the <c>BootX Extension</c> from the unpacked |
11024 |
archive into <c>Extensions Folder</c> and the BootX App Control Panel into |
11025 |
<c>Control Panels</c>, both of which are located in your MacOS System Folder. |
11026 |
Next, create a folder called "Linux Kernels" in your System folder and copy the |
11027 |
<c>apple</c> kernel from the CD to this folder. Finally, copy <c>apple.igz</c> |
11028 |
from the Installation CD <path>boot</path> folder into the MacOS |
11029 |
<c>System Folder</c>. |
11030 |
</p> |
11031 |
|
11032 |
<p> |
11033 |
To prepare BootX, start the BootX App Control Panel. First select the Options |
11034 |
dialog and check <c>Use Specified RAM Disk</c> and select <c>apple.igz</c> from |
11035 |
your System Folder. Continue back to the initial screen and ensure that the |
11036 |
ramdisk size is at least <c>32000</c>. Finally, set the kernel arguments as |
11037 |
shown below: |
11038 |
</p> |
11039 |
|
11040 |
<pre caption="BootX kernel arguments"> |
11041 |
cdroot root=/dev/ram0 init=linuxrc loop=image.squashfs looptype=squashfs console=tty0 |
11042 |
</pre> |
11043 |
|
11044 |
<note> |
11045 |
The kernel parameters in the yaboot section above are also applicable here. You |
11046 |
can append any of those options to the kernel arguments above. |
11047 |
</note> |
11048 |
|
11049 |
<p> |
11050 |
Check once more to make sure the settings are correct and then save the |
11051 |
configuration. This saves typing just in case it doesn't boot or something is |
11052 |
missing. Press the Linux button at the top of the window. If everything goes |
11053 |
correctly, it should boot into the Installation CD. Continue with |
11054 |
<uri link="#booted">And When You're Booted...</uri> |
11055 |
</p> |
11056 |
|
11057 |
</body> |
11058 |
</subsection> |
11059 |
|
11060 |
<subsection id="booted"> |
11061 |
<title>And When You're Booted...</title> |
11062 |
<body> |
11063 |
|
11064 |
<p> |
11065 |
You will be greeted by a root ("#") prompt on the current console. You can also |
11066 |
switch to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get |
11067 |
back to the one you started on by pressing Alt-F1. Due to the keyboard layout, |
11068 |
you may need to press Alt-fn-Fx on Apple machines. |
11069 |
</p> |
11070 |
|
11071 |
<p> |
11072 |
If you are installing Gentoo on a system with a non-US keyboard, use |
11073 |
<c>loadkeys</c> to load the keymap for your keyboard. To list the available |
11074 |
keymaps, execute <c>ls /usr/share/keymaps/i386</c>. On NewWorld machines or the |
11075 |
Pegasos do not use the keymaps in <path>ppc</path> or <path>mac</path> as they |
11076 |
are for ADB-based OldWorld machines. |
11077 |
</p> |
11078 |
|
11079 |
<pre caption="Listing available keymaps"> |
11080 |
<comment>(PPC uses x86 keymaps on most systems. The mac/ppc keymaps provided |
11081 |
on the Installation CD are ADB keymaps and unusable with the Installation CD |
11082 |
kernel)</comment> |
11083 |
# <i>ls /usr/share/keymaps/i386</i> |
11084 |
</pre> |
11085 |
|
11086 |
<p> |
11087 |
Now load the keymap of your choice: |
11088 |
</p> |
11089 |
|
11090 |
<pre caption="Loading a keymap"> |
11091 |
# <i>loadkeys be-latin1</i> |
11092 |
</pre> |
11093 |
|
11094 |
<p> |
11095 |
Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
11096 |
</p> |
11097 |
|
11098 |
</body> |
11099 |
</subsection> |
11100 |
<subsection id="hardware"> |
11101 |
<title>Extra Hardware Configuration</title> |
11102 |
<body> |
11103 |
|
11104 |
<p> |
11105 |
When the Installation CD boots, it tries to detect all your hardware devices and |
11106 |
loads the appropriate kernel modules to support your hardware. In the |
11107 |
vast majority of cases, it does a very good job. However, in some cases, it may |
11108 |
not auto-load the kernel modules you need. If the PCI auto-detection missed some |
11109 |
of your system's hardware, you will have to load the appropriate kernel modules |
11110 |
manually. |
11111 |
</p> |
11112 |
|
11113 |
<p> |
11114 |
In the next example we try to load the <c>airport</c> module. This module |
11115 |
supports only the old Airport cards (802.11b). Airport Extreme (802.11g) is not |
11116 |
supported on the InstallCD due to restrictions on firmware distribution. |
11117 |
</p> |
11118 |
|
11119 |
<pre caption="Loading the airport module"> |
11120 |
# <i>modprobe airport</i> |
11121 |
</pre> |
11122 |
|
11123 |
<p> |
11124 |
On older iMacs, sometimes the network card is not detected properly. These use |
11125 |
the BMAC driver: |
11126 |
</p> |
11127 |
|
11128 |
<pre caption="Loading the bmac module"> |
11129 |
# <i>modprobe bmac</i> |
11130 |
</pre> |
11131 |
|
11132 |
</body> |
11133 |
</subsection> |
11134 |
<subsection> |
11135 |
<title>Optional: Tweaking Hard Disk Performance</title> |
11136 |
<body> |
11137 |
|
11138 |
<p> |
11139 |
If you are an advanced user, you might want to tweak the IDE hard disk |
11140 |
performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
11141 |
test the performance of your disk (execute it several times to get a |
11142 |
more precise impression): |
11143 |
</p> |
11144 |
|
11145 |
<pre caption="Testing disk performance"> |
11146 |
# <i>hdparm -tT /dev/hda</i> |
11147 |
</pre> |
11148 |
|
11149 |
<p> |
11150 |
To tweak, you can use any of the following examples (or experiment |
11151 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
11152 |
disk): |
11153 |
</p> |
11154 |
|
11155 |
<pre caption="Tweaking hard disk performance"> |
11156 |
<comment>Activate DMA:</comment> |
11157 |
# <i>hdparm -d 1 /dev/hda</i> |
11158 |
<comment>Activate DMA + Safe Performance-enhancing Options:</comment> |
11159 |
# <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
11160 |
</pre> |
11161 |
|
11162 |
</body> |
11163 |
</subsection> |
11164 |
<subsection id="useraccounts"> |
11165 |
<title>Optional: User Accounts</title> |
11166 |
<body> |
11167 |
|
11168 |
<p> |
11169 |
If you plan on giving other people access to your installation |
11170 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
11171 |
security reasons), you need to create the necessary user accounts and change |
11172 |
the root password. |
11173 |
</p> |
11174 |
|
11175 |
<p> |
11176 |
To change the root password, use the <c>passwd</c> utility: |
11177 |
</p> |
11178 |
|
11179 |
<pre caption="Changing the root password"> |
11180 |
# <i>passwd</i> |
11181 |
New password: <comment>(Enter your new password)</comment> |
11182 |
Re-enter password: <comment>(Re-enter your password)</comment> |
11183 |
</pre> |
11184 |
|
11185 |
<p> |
11186 |
To create a user account, we first enter their credentials, followed by |
11187 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
11188 |
In the next example, we create a user called "john". |
11189 |
</p> |
11190 |
|
11191 |
<pre caption="Creating a user account"> |
11192 |
# <i>useradd -m -G users john</i> |
11193 |
# <i>passwd john</i> |
11194 |
New password: <comment>(Enter john's password)</comment> |
11195 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
11196 |
</pre> |
11197 |
|
11198 |
<p> |
11199 |
You can change your user id from root to the newly created user by using |
11200 |
<c>su</c>: |
11201 |
</p> |
11202 |
|
11203 |
<pre caption="Changing user id"> |
11204 |
# <i>su - john</i> |
11205 |
</pre> |
11206 |
|
11207 |
</body> |
11208 |
</subsection> |
11209 |
<subsection> |
11210 |
<title>Optional: Viewing Documentation while Installing</title> |
11211 |
<body> |
11212 |
|
11213 |
<p> |
11214 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
11215 |
installation, make sure you have created a user account (see <uri |
11216 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
11217 |
go to a new terminal and log in. |
11218 |
</p> |
11219 |
|
11220 |
<p> |
11221 |
If you want to view the documentation on the CD you can immediately run |
11222 |
<c>links</c> or even <c>links -g</c> for a graphical framebuffer browser to |
11223 |
read it: |
11224 |
</p> |
11225 |
|
11226 |
<pre caption="Viewing the on-CD documentation"> |
11227 |
# <i>links /mnt/cdrom/docs/html/index.html</i> |
11228 |
</pre> |
11229 |
|
11230 |
<p> |
11231 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
11232 |
more recent than the one provided on the CD. You can view it using <c>links</c> |
11233 |
as well, but only after having completed the <e>Configuring your Network</e> |
11234 |
chapter (otherwise you won't be able to go on the Internet to view the |
11235 |
document): |
11236 |
</p> |
11237 |
|
11238 |
<pre caption="Viewing the Online Documentation"> |
11239 |
# <i>links http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i> |
11240 |
</pre> |
11241 |
|
11242 |
<p> |
11243 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
11244 |
</p> |
11245 |
|
11246 |
</body> |
11247 |
</subsection> |
11248 |
<subsection> |
11249 |
<title>Optional: Starting the SSH Daemon</title> |
11250 |
<body> |
11251 |
|
11252 |
<p> |
11253 |
If you want to allow other users to access your computer during the |
11254 |
Gentoo installation (perhaps because those users are going to help you |
11255 |
install Gentoo, or even do it for you), you need to create a user |
11256 |
account for them and perhaps even provide them with your root password |
11257 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
11258 |
</p> |
11259 |
|
11260 |
<p> |
11261 |
To fire up the SSH daemon, execute the following command: |
11262 |
</p> |
11263 |
|
11264 |
<pre caption="Starting the SSH daemon"> |
11265 |
# <i>/etc/init.d/sshd start</i> |
11266 |
</pre> |
11267 |
|
11268 |
<p> |
11269 |
To be able to use sshd, you first need to set up your networking. Continue with |
11270 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
11271 |
</p> |
11272 |
|
11273 |
</body> |
11274 |
</subsection> |
11275 |
</section> |
11276 |
</sections> |
11277 |
|
11278 |
|
11279 |
|
11280 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-sparc-bootloader.xml |
11281 |
|
11282 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-sparc-bootloader.xml?rev=1.1&view=markup |
11283 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-sparc-bootloader.xml?rev=1.1&content-type=text/plain |
11284 |
|
11285 |
Index: hb-install-sparc-bootloader.xml |
11286 |
=================================================================== |
11287 |
<?xml version='1.0' encoding='UTF-8'?> |
11288 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
11289 |
|
11290 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
11291 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
11292 |
|
11293 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-sparc-bootloader.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
11294 |
|
11295 |
<sections> |
11296 |
|
11297 |
<version>8.0</version> |
11298 |
<date>2007-05-07</date> |
11299 |
|
11300 |
<section> |
11301 |
<title>Making your Choice</title> |
11302 |
<subsection> |
11303 |
<title>Introduction</title> |
11304 |
<body> |
11305 |
|
11306 |
<p> |
11307 |
Now that your kernel is configured and compiled and the necessary system |
11308 |
configuration files are filled in correctly, it is time to install a |
11309 |
program that will fire up your kernel when you start the system. Such a |
11310 |
program is called a <e>bootloader</e>. |
11311 |
</p> |
11312 |
|
11313 |
</body> |
11314 |
</subsection> |
11315 |
</section> |
11316 |
<section> |
11317 |
<title>Installing the SPARC Bootloader: SILO</title> |
11318 |
<body> |
11319 |
|
11320 |
<p> |
11321 |
It is now time to install and configure <uri |
11322 |
link="http://www.sparc-boot.org">SILO</uri>, the Sparc Improved boot |
11323 |
LOader. |
11324 |
</p> |
11325 |
|
11326 |
<pre caption = "Installing SILO"> |
11327 |
# <i>emerge silo</i> |
11328 |
</pre> |
11329 |
|
11330 |
<p> |
11331 |
Now open up your favorite editor (we use <c>nano</c> as an example) and |
11332 |
create <path>/etc/silo.conf</path>. |
11333 |
</p> |
11334 |
|
11335 |
<pre caption = "Creating /etc/silo.conf"> |
11336 |
# <i>nano -w /etc/silo.conf</i> |
11337 |
</pre> |
11338 |
|
11339 |
<p> |
11340 |
Below you'll find an example <path>silo.conf</path> file. It uses the |
11341 |
partitioning scheme we use throughout this book and |
11342 |
<path>kernel-<keyval id="kernel-version"/></path> as kernelimage. |
11343 |
</p> |
11344 |
|
11345 |
<pre caption = "Example /etc/silo.conf"> |
11346 |
partition = 1 <comment># Boot partition (= root partition)</comment> |
11347 |
root = /dev/sda1 <comment># Root partition</comment> |
11348 |
timeout = 150 <comment># Wait 15 seconds before booting the default section</comment> |
11349 |
|
11350 |
image = /boot/kernel-<keyval id="kernel-version"/> |
11351 |
label = linux |
11352 |
</pre> |
11353 |
|
11354 |
<p> |
11355 |
If you use the example <path>silo.conf</path> delivered by Portage, be |
11356 |
sure to comment out <e>all</e> lines that you do not need. |
11357 |
</p> |
11358 |
|
11359 |
<p> |
11360 |
If the physical disk on which you want to install SILO (as bootloader) differs |
11361 |
from the physical disk on which <path>/etc/silo.conf</path> resides, you must |
11362 |
copy over <path>/etc/silo.conf</path> to a partition on that disk. Assuming that |
11363 |
<path>/boot</path> is a separate partition on that disk, copy over the |
11364 |
configuration file to <path>/boot</path> and run <c>/sbin/silo -f</c>: |
11365 |
</p> |
11366 |
|
11367 |
<pre caption = "Only if /boot and the SILO destination are not on the same disk"> |
11368 |
# <i>cp /etc/silo.conf /boot</i> |
11369 |
# <i>/sbin/silo -f -C /boot/silo.conf</i> |
11370 |
/boot/silo.conf appears to be valid |
11371 |
</pre> |
11372 |
|
11373 |
<p> |
11374 |
Otherwise just run <c>/sbin/silo -f</c>: |
11375 |
</p> |
11376 |
|
11377 |
<pre caption = "Run silo"> |
11378 |
# <i>/sbin/silo -f</i> |
11379 |
/etc/silo.conf appears to be valid |
11380 |
</pre> |
11381 |
|
11382 |
<note> |
11383 |
You have to run <c>silo</c> (with parameters) again each time you update or |
11384 |
reinstall the <c>sys-boot/silo</c> package. |
11385 |
</note> |
11386 |
|
11387 |
<p> |
11388 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
11389 |
</p> |
11390 |
|
11391 |
</body> |
11392 |
</section> |
11393 |
<section id="reboot"> |
11394 |
<title>Rebooting the System</title> |
11395 |
<subsection> |
11396 |
<body> |
11397 |
|
11398 |
<p> |
11399 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
11400 |
that one magical command you have been waiting for: <c>reboot</c>. |
11401 |
</p> |
11402 |
|
11403 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
11404 |
# <i>exit</i> |
11405 |
cdimage ~# <i>cd</i> |
11406 |
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
11407 |
cdimage ~# <i>reboot</i> |
11408 |
</pre> |
11409 |
|
11410 |
<p> |
11411 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
11412 |
booted again instead of your new Gentoo system. |
11413 |
</p> |
11414 |
|
11415 |
<p> |
11416 |
Once rebooted in your Gentoo installation, finish up with <uri |
11417 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
11418 |
</p> |
11419 |
|
11420 |
</body> |
11421 |
</subsection> |
11422 |
</section> |
11423 |
</sections> |
11424 |
|
11425 |
|
11426 |
|
11427 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-sparc-disk.xml |
11428 |
|
11429 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-sparc-disk.xml?rev=1.1&view=markup |
11430 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-sparc-disk.xml?rev=1.1&content-type=text/plain |
11431 |
|
11432 |
Index: hb-install-sparc-disk.xml |
11433 |
=================================================================== |
11434 |
<?xml version='1.0' encoding='UTF-8'?> |
11435 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
11436 |
|
11437 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
11438 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
11439 |
|
11440 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-sparc-disk.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
11441 |
|
11442 |
<sections> |
11443 |
|
11444 |
<version>8.1</version> |
11445 |
<date>2007-06-26</date> |
11446 |
|
11447 |
<section> |
11448 |
<title>Introduction to Block Devices</title> |
11449 |
<subsection> |
11450 |
<title>Block Devices</title> |
11451 |
<body> |
11452 |
|
11453 |
<p> |
11454 |
We'll take a good look at some of the disk-oriented aspects of Gentoo Linux |
11455 |
and Linux in general, including Linux filesystems, partitions, and block |
11456 |
devices. Then, once you're familiar with the ins and outs of disks and |
11457 |
filesystems, you'll be guided through the process of setting up partitions |
11458 |
and filesystems for your Gentoo Linux installation. |
11459 |
</p> |
11460 |
|
11461 |
<p> |
11462 |
To begin, we introduce <e>block devices</e>. The most typical block device is |
11463 |
probably the one that represents the first SCSI hard disk in a Linux system, |
11464 |
namely <path>/dev/sda</path>. |
11465 |
</p> |
11466 |
|
11467 |
<p> |
11468 |
Block devices represent an abstract interface to the disk. User programs can |
11469 |
use these block devices to interact with your disk without worrying about |
11470 |
whether your drives are IDE, SCSI, or something else. The program can simply |
11471 |
address the storage on the disk as a bunch of contiguous, randomly-accessible |
11472 |
512-byte blocks. |
11473 |
</p> |
11474 |
|
11475 |
<p> |
11476 |
Block devices show up as entries in <path>/dev/</path>. Typically, the first |
11477 |
SCSI drive is named <path>/dev/sda</path>, the second <path>/dev/sdb</path>, |
11478 |
and so on. IDE drives are named similarly, however, they are prefixed by hd- |
11479 |
instead of sd-. If you are using IDE drives, the first one will be named |
11480 |
<path>/dev/hda</path>, the second <path>/dev/hdb</path>, and so on. |
11481 |
</p> |
11482 |
|
11483 |
</body> |
11484 |
</subsection> |
11485 |
<subsection> |
11486 |
<title>Partitions</title> |
11487 |
<body> |
11488 |
|
11489 |
<p> |
11490 |
Although it is theoretically possible to use the entire disk to house your Linux |
11491 |
system, this is almost never done in practice. Instead, full disk block devices |
11492 |
are split up in smaller, more manageable block devices. These are known as |
11493 |
<e>partitions</e> or <e>slices</e>. |
11494 |
</p> |
11495 |
|
11496 |
<p> |
11497 |
The first partition on the first SCSI disk is <path>/dev/sda1</path>, the second |
11498 |
<path>/dev/sda2</path> and so on. Similarly, the first two partitions on the |
11499 |
first IDE disk are <path>/dev/hda1</path> and <path>/dev/hda2</path>. |
11500 |
</p> |
11501 |
|
11502 |
<p> |
11503 |
The third partition on Sun systems is set aside as a special "whole disk" |
11504 |
slice. This partition must not contain a file system. |
11505 |
</p> |
11506 |
|
11507 |
<p> |
11508 |
Users who are used to the DOS partitioning scheme should note that Sun |
11509 |
disklabels do not have "primary" and "extended" partitions. Instead, up to |
11510 |
eight partitions are available per drive, with the third of these being |
11511 |
reserved. |
11512 |
</p> |
11513 |
|
11514 |
</body> |
11515 |
</subsection> |
11516 |
</section> |
11517 |
<section> |
11518 |
<title>Designing a Partitioning Scheme</title> |
11519 |
<subsection> |
11520 |
<title>Default Partitioning Scheme</title> |
11521 |
<body> |
11522 |
|
11523 |
<p> |
11524 |
If you are not interested in drawing up a partitioning scheme, |
11525 |
the table below suggests a suitable starting point for most systems. For |
11526 |
IDE-based systems, substitute <c>hda</c> for <c>sda</c> in the following. |
11527 |
</p> |
11528 |
|
11529 |
<p> |
11530 |
Note that a separate <path>/boot</path> partition is generally <e>not</e> |
11531 |
recommended on SPARC, as it complicates the bootloader configuration. |
11532 |
</p> |
11533 |
|
11534 |
<table> |
11535 |
<tr> |
11536 |
<th>Partition</th> |
11537 |
<th>Filesystem</th> |
11538 |
<th>Size</th> |
11539 |
<th>Mount Point</th> |
11540 |
<th>Description</th> |
11541 |
</tr> |
11542 |
<tr> |
11543 |
<ti>/dev/sda1</ti> |
11544 |
<ti>ext3</ti> |
11545 |
<ti><2 GByte</ti> |
11546 |
<ti>/</ti> |
11547 |
<ti> |
11548 |
Root partition. For sparc64 systems with older OBP versions, this |
11549 |
<e>must</e> be less than 2 GBytes in size, and the first partition on the |
11550 |
disk. |
11551 |
</ti> |
11552 |
</tr> |
11553 |
<tr> |
11554 |
<ti>/dev/sda2</ti> |
11555 |
<ti>swap</ti> |
11556 |
<ti>512 MBytes</ti> |
11557 |
<ti>none</ti> |
11558 |
<ti> |
11559 |
Swap partition. For bootstrap and certain larger compiles, at least 512 |
11560 |
MBytes of RAM (including swap) is required. |
11561 |
</ti> |
11562 |
</tr> |
11563 |
<tr> |
11564 |
<ti>/dev/sda3</ti> |
11565 |
<ti>none</ti> |
11566 |
<ti>Whole disk</ti> |
11567 |
<ti>none</ti> |
11568 |
<ti>Whole disk partition. This is required on SPARC systems.</ti> |
11569 |
</tr> |
11570 |
<tr> |
11571 |
<ti>/dev/sda4</ti> |
11572 |
<ti>ext3</ti> |
11573 |
<ti>at least 2 GBytes</ti> |
11574 |
<ti>/usr</ti> |
11575 |
<ti> |
11576 |
/usr partition. Applications are installed here. By default this partition |
11577 |
is also used for Portage data (which takes around 500 Mbyte excluding |
11578 |
source code). |
11579 |
</ti> |
11580 |
</tr> |
11581 |
<tr> |
11582 |
<ti>/dev/sda5</ti> |
11583 |
<ti>ext3</ti> |
11584 |
<ti>at least 1GByte</ti> |
11585 |
<ti>/var</ti> |
11586 |
<ti> |
11587 |
/var partition. Used for program-generated data. By default Portage uses |
11588 |
this partition for temporary space whilst compiling. Certain larger |
11589 |
applications such as Mozilla and OpenOffice.org can require over 1 GByte |
11590 |
of temporary space here when building. |
11591 |
</ti> |
11592 |
</tr> |
11593 |
<tr> |
11594 |
<ti>/dev/sda6</ti> |
11595 |
<ti>ext3</ti> |
11596 |
<ti>remaining space</ti> |
11597 |
<ti>/home</ti> |
11598 |
<ti>/home partition. Used for users' home directories.</ti> |
11599 |
</tr> |
11600 |
</table> |
11601 |
|
11602 |
</body> |
11603 |
</subsection> |
11604 |
</section> |
11605 |
|
11606 |
<section id="fdisk"> |
11607 |
<title>Using fdisk to Partition your Disk</title> |
11608 |
<subsection> |
11609 |
<body> |
11610 |
|
11611 |
<p> |
11612 |
The following parts explain how to create the example partition layout described |
11613 |
previously, namely: |
11614 |
</p> |
11615 |
|
11616 |
<table> |
11617 |
<tr> |
11618 |
<th>Partition</th> |
11619 |
<th>Description</th> |
11620 |
</tr> |
11621 |
<tr> |
11622 |
<ti>/dev/sda1</ti> |
11623 |
<ti>/</ti> |
11624 |
</tr> |
11625 |
<tr> |
11626 |
<ti>/dev/sda2</ti> |
11627 |
<ti>swap</ti> |
11628 |
</tr> |
11629 |
<tr> |
11630 |
<ti>/dev/sda3</ti> |
11631 |
<ti>whole disk slice</ti> |
11632 |
</tr> |
11633 |
<tr> |
11634 |
<ti>/dev/sda4</ti> |
11635 |
<ti>/usr</ti> |
11636 |
</tr> |
11637 |
<tr> |
11638 |
<ti>/dev/sda5</ti> |
11639 |
<ti>/var</ti> |
11640 |
</tr> |
11641 |
<tr> |
11642 |
<ti>/dev/sda6</ti> |
11643 |
<ti>/home</ti> |
11644 |
</tr> |
11645 |
</table> |
11646 |
|
11647 |
<p> |
11648 |
Change the partition layout as required. Remember to keep the root partition |
11649 |
entirely within the first 2 GBytes of the disk for older systems. There is also |
11650 |
a 15-partition limit for SCSI and SATA. |
11651 |
</p> |
11652 |
|
11653 |
</body> |
11654 |
</subsection> |
11655 |
<subsection> |
11656 |
<title>Firing up fdisk</title> |
11657 |
<body> |
11658 |
|
11659 |
<p> |
11660 |
Start <c>fdisk</c> with your disk as argument: |
11661 |
</p> |
11662 |
|
11663 |
<pre caption="Starting fdisk"> |
11664 |
# <i>fdisk /dev/sda</i> |
11665 |
</pre> |
11666 |
|
11667 |
<p> |
11668 |
You should be greeted with the fdisk prompt: |
11669 |
</p> |
11670 |
|
11671 |
<pre caption="The fdisk prompt"> |
11672 |
Command (m for help): |
11673 |
</pre> |
11674 |
|
11675 |
<p> |
11676 |
To view the available partitions, type in <c>p</c>: |
11677 |
</p> |
11678 |
|
11679 |
<pre caption="Listing available partitions"> |
11680 |
Command (m for help): <i>p</i> |
11681 |
|
11682 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
11683 |
Units = cylinders of 2048 * 512 bytes |
11684 |
|
11685 |
Device Flag Start End Blocks Id System |
11686 |
/dev/sda1 0 488 499712 83 Linux native |
11687 |
/dev/sda2 488 976 499712 82 Linux swap |
11688 |
/dev/sda3 0 8635 8842240 5 Whole disk |
11689 |
/dev/sda4 976 1953 1000448 83 Linux native |
11690 |
/dev/sda5 1953 2144 195584 83 Linux native |
11691 |
/dev/sda6 2144 8635 6646784 83 Linux native |
11692 |
</pre> |
11693 |
|
11694 |
<p> |
11695 |
Note the <c>Sun disk label</c> in the output. If this is missing, the disk is |
11696 |
using the DOS-partitioning, not the Sun partitioning. In this case, use <c>s</c> |
11697 |
to ensure that the disk has a sun partition table: |
11698 |
</p> |
11699 |
|
11700 |
<pre caption="Creating a Sun Disklabel"> |
11701 |
Command (m for help): s |
11702 |
Building a new sun disklabel. Changes will remain in memory only, |
11703 |
until you decide to write them. After that, of course, the previous |
11704 |
content won't be recoverable. |
11705 |
|
11706 |
Drive type |
11707 |
? auto configure |
11708 |
0 custom (with hardware detected defaults) |
11709 |
a Quantum ProDrive 80S |
11710 |
b Quantum ProDrive 105S |
11711 |
c CDC Wren IV 94171-344 |
11712 |
d IBM DPES-31080 |
11713 |
e IBM DORS-32160 |
11714 |
f IBM DNES-318350 |
11715 |
g SEAGATE ST34371 |
11716 |
h SUN0104 |
11717 |
i SUN0207 |
11718 |
j SUN0327 |
11719 |
k SUN0340 |
11720 |
l SUN0424 |
11721 |
m SUN0535 |
11722 |
n SUN0669 |
11723 |
o SUN1.0G |
11724 |
p SUN1.05 |
11725 |
q SUN1.3G |
11726 |
r SUN2.1G |
11727 |
s IOMEGA Jaz |
11728 |
Select type (? for auto, 0 for custom): <i>0</i> |
11729 |
Heads (1-1024, default 64): |
11730 |
Using default value 64 |
11731 |
Sectors/track (1-1024, default 32): |
11732 |
Using default value 32 |
11733 |
Cylinders (1-65535, default 8635): |
11734 |
Using default value 8635 |
11735 |
Alternate cylinders (0-65535, default 2): |
11736 |
Using default value 2 |
11737 |
Physical cylinders (0-65535, default 8637): |
11738 |
Using default value 8637 |
11739 |
Rotation speed (rpm) (1-100000, default 5400): <i>10000</i> |
11740 |
Interleave factor (1-32, default 1): |
11741 |
Using default value 1 |
11742 |
Extra sectors per cylinder (0-32, default 0): |
11743 |
Using default value 0 |
11744 |
</pre> |
11745 |
|
11746 |
<p> |
11747 |
You can find the correct values in your disk's documentation. The |
11748 |
'auto configure' option does not usually work. |
11749 |
</p> |
11750 |
|
11751 |
</body> |
11752 |
</subsection> |
11753 |
<subsection> |
11754 |
<title>Deleting Existing Partitions</title> |
11755 |
<body> |
11756 |
|
11757 |
<p> |
11758 |
It's time to delete any existing partitions. To do this, type <c>d</c> and hit |
11759 |
Enter. You will then be prompted for the partition number you would like to |
11760 |
delete. To delete a pre-existing <path>/dev/sda1</path>, you would type: |
11761 |
</p> |
11762 |
|
11763 |
<pre caption="Deleting a partition"> |
11764 |
Command (m for help): <i>d</i> |
11765 |
Partition number (1-4): <i>1</i> |
11766 |
</pre> |
11767 |
|
11768 |
<p> |
11769 |
<e>You should not delete partition 3 (whole disk).</e> This is required. If |
11770 |
this partition does not exist, follow the "Creating a Sun Disklabel" |
11771 |
instructions above. |
11772 |
</p> |
11773 |
|
11774 |
<p> |
11775 |
After deleting all partitions except the Whole disk slice, you should have a |
11776 |
partition layout similar to the following: |
11777 |
</p> |
11778 |
|
11779 |
<pre caption="View an empty partition scheme"> |
11780 |
Command (m for help): <i>p</i> |
11781 |
|
11782 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
11783 |
Units = cylinders of 2048 * 512 bytes |
11784 |
|
11785 |
Device Flag Start End Blocks Id System |
11786 |
/dev/sda3 0 8635 8842240 5 Whole disk |
11787 |
</pre> |
11788 |
|
11789 |
|
11790 |
</body> |
11791 |
</subsection> |
11792 |
|
11793 |
<subsection> |
11794 |
<title>Creating the Root Partition</title> |
11795 |
<body> |
11796 |
|
11797 |
<p> |
11798 |
We're ready to create the root partition. To do this, type <c>n</c> to create a |
11799 |
new partition, then type <c>1</c> to create the partition. When prompted for |
11800 |
the first cylinder, hit enter. When prompted for the last cylinder, type |
11801 |
<c>+512M</c> to create a partition <c>512MBytes</c> in size. Make sure that the |
11802 |
entire root partition fits within the first 2GBytes of the disk. You can see |
11803 |
output from these steps below: |
11804 |
</p> |
11805 |
|
11806 |
<pre caption="Creating a root partition"> |
11807 |
Command (m for help): <i>n</i> |
11808 |
Partition number (1-8): <i>1</i> |
11809 |
First cylinder (0-8635): <i>(press Enter)</i> |
11810 |
Last cylinder or +size or +sizeM or +sizeK (0-8635, default 8635): <i>+512M</i> |
11811 |
</pre> |
11812 |
|
11813 |
<p> |
11814 |
Now, when you type <c>p</c>, you should see the following partition printout: |
11815 |
</p> |
11816 |
|
11817 |
<pre caption="Listing the partition layout"> |
11818 |
Command (m for help): <i>p</i> |
11819 |
|
11820 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
11821 |
Units = cylinders of 2048 * 512 bytes |
11822 |
|
11823 |
Device Flag Start End Blocks Id System |
11824 |
/dev/sda1 0 488 499712 83 Linux native |
11825 |
/dev/sda3 0 8635 8842240 5 Whole disk |
11826 |
</pre> |
11827 |
|
11828 |
</body> |
11829 |
</subsection> |
11830 |
<subsection> |
11831 |
<title>Creating a swap partition</title> |
11832 |
<body> |
11833 |
|
11834 |
<p> |
11835 |
Next, let's create the swap partition. To do this, type <c>n</c> to create a new |
11836 |
partition, then <c>2</c> to create the second partition, <path>/dev/sda2</path> |
11837 |
in our case. When prompted for the first cylinder, hit enter. When prompted for |
11838 |
the last cylinder, type <c>+512M</c> to create a partition 512MB in size. After |
11839 |
you've done this, type <c>t</c> to set the partition type, and then type in |
11840 |
<c>82</c> to set the partition type to "Linux Swap". After completing these |
11841 |
steps, typing <c>p</c> should display a partition table that looks similar to |
11842 |
this: |
11843 |
</p> |
11844 |
|
11845 |
<pre caption="Listing of available partitions"> |
11846 |
Command (m for help): <i>p</i> |
11847 |
|
11848 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
11849 |
Units = cylinders of 2048 * 512 bytes |
11850 |
|
11851 |
Device Flag Start End Blocks Id System |
11852 |
/dev/sda1 0 488 499712 83 Linux native |
11853 |
/dev/sda2 488 976 499712 82 Linux swap |
11854 |
/dev/sda3 0 8635 8842240 5 Whole disk |
11855 |
</pre> |
11856 |
|
11857 |
</body> |
11858 |
</subsection> |
11859 |
<subsection> |
11860 |
<title>Creating the /usr, /var and /home partitions</title> |
11861 |
<body> |
11862 |
|
11863 |
<p> |
11864 |
Finally, let's create the /usr, /var and /home partitions. As before, |
11865 |
type <c>n</c> to create a new partition, then type <c>4</c> to create the |
11866 |
third partition, <path>/dev/sda4</path> in our case. When prompted for the |
11867 |
first cylinder, hit enter. When prompted for the last cylinder, enter |
11868 |
<c>+2048M</c> to create a partition 2 GBytes in size. Repeat this process |
11869 |
for <path>sda5</path> and <path>sda6</path>, using the desired sizes. Once |
11870 |
you're done, you should see something like this: |
11871 |
</p> |
11872 |
|
11873 |
<pre caption="Listing complete partition table"> |
11874 |
Command (m for help): <i>p</i> |
11875 |
|
11876 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
11877 |
Units = cylinders of 2048 * 512 bytes |
11878 |
|
11879 |
Device Flag Start End Blocks Id System |
11880 |
/dev/sda1 0 488 499712 83 Linux native |
11881 |
/dev/sda2 488 976 499712 82 Linux swap |
11882 |
/dev/sda3 0 8635 8842240 5 Whole disk |
11883 |
/dev/sda4 976 1953 1000448 83 Linux native |
11884 |
/dev/sda5 1953 2144 195584 83 Linux native |
11885 |
/dev/sda6 2144 8635 6646784 83 Linux native |
11886 |
</pre> |
11887 |
|
11888 |
</body> |
11889 |
</subsection> |
11890 |
<subsection> |
11891 |
<title>Save and Exit</title> |
11892 |
<body> |
11893 |
|
11894 |
<p> |
11895 |
To save your partition layout and exit <c>fdisk</c>, type <c>w</c>: |
11896 |
</p> |
11897 |
|
11898 |
<pre caption="Save and exit fdisk"> |
11899 |
Command (m for help): <i>w</i> |
11900 |
</pre> |
11901 |
|
11902 |
<p> |
11903 |
Now that your partitions are created, you can now continue with <uri |
11904 |
link="#filesystems">Creating Filesystems</uri>. |
11905 |
</p> |
11906 |
|
11907 |
</body> |
11908 |
</subsection> |
11909 |
</section> |
11910 |
<section id="filesystems"> |
11911 |
<title>Creating Filesystems</title> |
11912 |
<subsection> |
11913 |
<title>Introduction</title> |
11914 |
<body> |
11915 |
|
11916 |
<p> |
11917 |
Now that your partitions are created, it is time to place a filesystem on them. |
11918 |
If you don't care about what filesystem to choose and are happy with what is |
11919 |
used as default in this handbook, continue with <uri |
11920 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
11921 |
Otherwise, read on to learn about the available filesystems... |
11922 |
</p> |
11923 |
|
11924 |
</body> |
11925 |
</subsection> |
11926 |
<subsection> |
11927 |
<title>Filesystems?</title> |
11928 |
<body> |
11929 |
|
11930 |
<p> |
11931 |
Several filesystems are available, some are known to be stable on the |
11932 |
SPARC architecture. Ext2 and ext3, for example, are known to work well. |
11933 |
Alternate filesystems may not function correctly. |
11934 |
</p> |
11935 |
|
11936 |
<p> |
11937 |
<b>ext2</b> is the tried-and-true Linux filesystem. It does not support |
11938 |
journaling, which means that periodic checks of ext2 filesystems at startup |
11939 |
can be quite time-consuming. There is quite a selection of newer-generation |
11940 |
journaled filesystems that can be checked for consistency very quickly at |
11941 |
startup, and are therefore generally preferred over their non-journaled |
11942 |
counterparts. In general, journaled filesystems prevent long delays when a |
11943 |
system is booted and the filesystem is in an inconsistent state. |
11944 |
</p> |
11945 |
|
11946 |
<p> |
11947 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
11948 |
journaling for fast recovery in addition to other enhanced journaling modes like |
11949 |
full data and ordered data journaling. It uses an HTree index that enables high |
11950 |
performance in almost all situations. In short, ext3 is a very good and reliable |
11951 |
filesystem. |
11952 |
</p> |
11953 |
|
11954 |
</body> |
11955 |
</subsection> |
11956 |
<subsection id="filesystems-apply"> |
11957 |
<title>Applying a Filesystem to a Partition</title> |
11958 |
<body> |
11959 |
|
11960 |
<p> |
11961 |
To create a filesystem on a partition or volume, tools specific to the chosen |
11962 |
filesystem are available: |
11963 |
</p> |
11964 |
|
11965 |
<table> |
11966 |
<tr> |
11967 |
<th>Filesystem</th> |
11968 |
<th>Creation Command</th> |
11969 |
</tr> |
11970 |
<tr> |
11971 |
<ti>ext2</ti> |
11972 |
<ti><c>mke2fs</c></ti> |
11973 |
</tr> |
11974 |
<tr> |
11975 |
<ti>ext3</ti> |
11976 |
<ti><c>mke2fs -j</c></ti> |
11977 |
</tr> |
11978 |
</table> |
11979 |
|
11980 |
<p> |
11981 |
For instance, to create the root partition (<path>/dev/sda1</path> in our |
11982 |
example) as ext2, and the <path>/usr</path>, <path>/var</path>, and |
11983 |
<path>/home</path> partitions (<path>/dev/sda4</path>, <path>5</path> |
11984 |
and <path>6</path> in our example, respectively) as ext3, you would use: |
11985 |
</p> |
11986 |
|
11987 |
<pre caption="Applying a filesystem on a partition"> |
11988 |
# <i>mke2fs /dev/sda1</i> |
11989 |
# <i>mke2fs -j /dev/sda4</i> |
11990 |
# <i>mke2fs -j /dev/sda5</i> |
11991 |
# <i>mke2fs -j /dev/sda6</i> |
11992 |
</pre> |
11993 |
|
11994 |
</body> |
11995 |
</subsection> |
11996 |
<subsection> |
11997 |
<title>Activating the Swap Partition</title> |
11998 |
<body> |
11999 |
|
12000 |
<p> |
12001 |
<c>mkswap</c> is the command used to initialize swap partitions: |
12002 |
</p> |
12003 |
|
12004 |
<pre caption="Creating a Swap signature"> |
12005 |
# <i>mkswap /dev/sda2</i> |
12006 |
</pre> |
12007 |
|
12008 |
<p> |
12009 |
To activate the swap partition, use <c>swapon</c>: |
12010 |
</p> |
12011 |
|
12012 |
<pre caption="Activating the swap partition"> |
12013 |
# <i>swapon /dev/sda2</i> |
12014 |
</pre> |
12015 |
|
12016 |
<p> |
12017 |
Create and activate the swap with the commands mentioned above. |
12018 |
</p> |
12019 |
|
12020 |
</body> |
12021 |
</subsection> |
12022 |
</section> |
12023 |
<section> |
12024 |
<title>Mounting</title> |
12025 |
<body> |
12026 |
|
12027 |
<p> |
12028 |
Now that your partitions are initialized and are housing a filesystem, it is |
12029 |
time to mount them using the <c>mount</c> command. Don't forget to first |
12030 |
create the necessary mount directories for every partition you created. For |
12031 |
example: |
12032 |
</p> |
12033 |
|
12034 |
<pre caption="Mounting partitions"> |
12035 |
# <i>mount /dev/sda1 /mnt/gentoo</i> |
12036 |
# <i>mkdir /mnt/gentoo/usr</i> |
12037 |
# <i>mount /dev/sda4 /mnt/gentoo/usr</i> |
12038 |
# <i>mkdir /mnt/gentoo/var</i> |
12039 |
# <i>mount /dev/sda5 /mnt/gentoo/var</i> |
12040 |
# <i>mkdir /mnt/gentoo/home</i> |
12041 |
# <i>mount /dev/sda6 /mnt/gentoo/home</i> |
12042 |
</pre> |
12043 |
|
12044 |
<note> |
12045 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure |
12046 |
to change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. |
12047 |
This also holds for <path>/var/tmp</path>. |
12048 |
</note> |
12049 |
|
12050 |
<p> |
12051 |
We will also have to mount the proc filesystem (a virtual interface with the |
12052 |
kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. |
12053 |
</p> |
12054 |
|
12055 |
<p> |
12056 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
12057 |
Installation Files</uri>. |
12058 |
</p> |
12059 |
|
12060 |
</body> |
12061 |
</section> |
12062 |
</sections> |
12063 |
|
12064 |
|
12065 |
|
12066 |
|
12067 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-sparc-kernel.xml |
12068 |
|
12069 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-sparc-kernel.xml?rev=1.1&view=markup |
12070 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-sparc-kernel.xml?rev=1.1&content-type=text/plain |
12071 |
|
12072 |
Index: hb-install-sparc-kernel.xml |
12073 |
=================================================================== |
12074 |
<?xml version='1.0' encoding='UTF-8'?> |
12075 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
12076 |
|
12077 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
12078 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
12079 |
|
12080 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-sparc-kernel.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
12081 |
|
12082 |
<sections> |
12083 |
|
12084 |
<version>8.2</version> |
12085 |
<date>2007-07-29</date> |
12086 |
|
12087 |
<section> |
12088 |
<title>Timezone</title> |
12089 |
<body> |
12090 |
|
12091 |
<p> |
12092 |
You first need to select your timezone so that your system knows where it is |
12093 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
12094 |
it to <path>/etc/localtime</path>. Please avoid the |
12095 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
12096 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact |
12097 |
GMT+8. |
12098 |
</p> |
12099 |
|
12100 |
<pre caption="Setting the timezone information"> |
12101 |
# <i>ls /usr/share/zoneinfo</i> |
12102 |
<comment>(Suppose you want to use GMT)</comment> |
12103 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
12104 |
</pre> |
12105 |
|
12106 |
</body> |
12107 |
</section> |
12108 |
<section> |
12109 |
<title>Installing the Sources</title> |
12110 |
<subsection> |
12111 |
<title>Choosing a Kernel</title> |
12112 |
<body> |
12113 |
|
12114 |
<p> |
12115 |
The core around which all distributions are built is the Linux kernel. It is the |
12116 |
layer between the user programs and your system hardware. Gentoo provides its |
12117 |
users several possible kernel sources. A full listing with description is |
12118 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
12119 |
Guide</uri>. |
12120 |
</p> |
12121 |
|
12122 |
<p> |
12123 |
For sparc-based systems we have <c>gentoo-sources</c> (recommended 2.6 kernel |
12124 |
sources). |
12125 |
</p> |
12126 |
|
12127 |
<p> |
12128 |
In the next example we install <c>gentoo-sources</c>. |
12129 |
</p> |
12130 |
|
12131 |
<pre caption="Installing a kernel source"> |
12132 |
# <i>emerge gentoo-sources</i> |
12133 |
</pre> |
12134 |
|
12135 |
<p> |
12136 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
12137 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
12138 |
kernel source points to <c>linux-<keyval id="kernel-version"/></c>. Your version |
12139 |
may be different, so keep this in mind. |
12140 |
</p> |
12141 |
|
12142 |
<pre caption="Viewing the kernel source symlink"> |
12143 |
# <i>ls -l /usr/src/linux</i> |
12144 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-<keyval id="kernel-version"/> |
12145 |
</pre> |
12146 |
|
12147 |
<p> |
12148 |
Now it is time to configure and compile your kernel source. |
12149 |
</p> |
12150 |
|
12151 |
</body> |
12152 |
</subsection> |
12153 |
</section> |
12154 |
<section> |
12155 |
<title>Manual Configuration</title> |
12156 |
<subsection> |
12157 |
<title>Introduction</title> |
12158 |
<body> |
12159 |
|
12160 |
<p> |
12161 |
Manually configuring a kernel is often seen as the most difficult procedure a |
12162 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
12163 |
couple of kernels you don't even remember that it was difficult ;) |
12164 |
</p> |
12165 |
|
12166 |
<p> |
12167 |
However, one thing <e>is</e> true: you must know your system when you start |
12168 |
configuring a kernel manually. Most information can be gathered by emerging |
12169 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
12170 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
12171 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
12172 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
12173 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
12174 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
12175 |
uses (it might provide you with a nice hint on what to enable). |
12176 |
</p> |
12177 |
|
12178 |
<p> |
12179 |
Now go to your kernel source directory and execute <c>make menuconfig</c>. This |
12180 |
will fire up an ncurses-based configuration menu. |
12181 |
</p> |
12182 |
|
12183 |
<pre caption="Invoking menuconfig"> |
12184 |
# <i>cd /usr/src/linux</i> |
12185 |
# <i>make menuconfig</i> |
12186 |
</pre> |
12187 |
|
12188 |
<p> |
12189 |
You will be greeted with several configuration sections. We'll first list some |
12190 |
options you must activate (otherwise Gentoo will not function, or not function |
12191 |
properly without additional tweaks). |
12192 |
</p> |
12193 |
|
12194 |
</body> |
12195 |
</subsection> |
12196 |
<subsection> |
12197 |
<title>Activating Required Options</title> |
12198 |
<body> |
12199 |
|
12200 |
<p> |
12201 |
First of all, activate the use of development and experimental code/drivers. |
12202 |
You need this, otherwise some very important code/drivers won't show up: |
12203 |
</p> |
12204 |
|
12205 |
<pre caption="Selecting experimental code/drivers"> |
12206 |
Code maturity level options ---> |
12207 |
[*] Prompt for development and/or incomplete code/drivers |
12208 |
</pre> |
12209 |
|
12210 |
<p> |
12211 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
12212 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
12213 |
able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc |
12214 |
file system</c>: |
12215 |
</p> |
12216 |
|
12217 |
<pre caption="Selecting necessary file systems"> |
12218 |
File systems ---> |
12219 |
Pseudo Filesystems ---> |
12220 |
[*] /proc file system support |
12221 |
[*] Virtual memory file system support (former shm fs) |
12222 |
|
12223 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
12224 |
<*> Ext3 journalling file system support |
12225 |
<*> Second extended fs support |
12226 |
</pre> |
12227 |
|
12228 |
<p> |
12229 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
12230 |
modem, you will need the following options in the kernel: |
12231 |
</p> |
12232 |
|
12233 |
<pre caption="Selecting PPPoE necessary drivers"> |
12234 |
Device Drivers ---> |
12235 |
Networking support ---> |
12236 |
<*> PPP (point-to-point protocol) support |
12237 |
<*> PPP support for async serial ports |
12238 |
<*> PPP support for sync tty ports |
12239 |
</pre> |
12240 |
|
12241 |
<p> |
12242 |
The two compression options won't harm but are not definitely needed, neither |
12243 |
does the <c>PPP over Ethernet</c> option, that might only be used by <c>ppp</c> |
12244 |
when configured to do kernel mode PPPoE. |
12245 |
</p> |
12246 |
|
12247 |
<p> |
12248 |
Now activate the correct bus-support: |
12249 |
</p> |
12250 |
|
12251 |
<pre caption="Activating SBUS/UPA"> |
12252 |
Console drivers ---> |
12253 |
Frame-buffer support ---> |
12254 |
[*] SBUS and UPA framebuffers |
12255 |
[*] Creator/Creator3D support <comment>(Only for UPA slot adapter used in many Ultras)</comment> |
12256 |
[*] CGsix (GX,TurboGX) support <comment>(Only for SBUS slot adapter used in many SPARCStations)</comment> |
12257 |
</pre> |
12258 |
|
12259 |
<p> |
12260 |
Of course you want support for the OBP: |
12261 |
</p> |
12262 |
|
12263 |
<pre caption="Activating OBP Support"> |
12264 |
Misc Linux/SPARC drivers ---> |
12265 |
[*] /dev/openprom device support |
12266 |
</pre> |
12267 |
|
12268 |
<p> |
12269 |
You will also need SCSI-specific support: |
12270 |
</p> |
12271 |
|
12272 |
<pre caption="Activating SCSI-specific support"> |
12273 |
SCSI support ---> |
12274 |
SCSI low-level drivers ---> |
12275 |
<*> Sparc ESP Scsi Driver <comment>(Only for SPARC ESP on-board SCSI adapter)</comment> |
12276 |
<*> PTI Qlogic, ISP Driver <comment>(Only for SBUS SCSI controllers from PTI or QLogic)</comment> |
12277 |
<*> SYM53C8XX Version 2 SCSI support <comment>(Only for Ultra 60 on-board SCSI adapter)</comment> |
12278 |
</pre> |
12279 |
|
12280 |
<p> |
12281 |
To support your network card, select one of the following: |
12282 |
</p> |
12283 |
|
12284 |
<pre caption="Activating networking support"> |
12285 |
Network device support ---> |
12286 |
Ethernet (10 or 100Mbit) ---> |
12287 |
<*> Sun LANCE support <comment>(Only for SPARCStation, older Ultra systems, and as Sbus option)</comment> |
12288 |
<*> Sun Happy Meal 10/100baseT support <comment>(Only for Ultra; also supports "qfe" quad-ethernet on PCI and Sbus)</comment> |
12289 |
<*> DECchip Tulip (dc21x4x) PCI support <comment>(For some Netras, like N1)</comment> |
12290 |
Ethernet (1000Mbit) ---> |
12291 |
<*> Broadcom Tigon3 support <comment>(Modern Netra, Sun Fire machines)</comment> |
12292 |
</pre> |
12293 |
|
12294 |
<p> |
12295 |
When you have a 4-port Ethernet machine (10/100 or 10/100/1000) the port order |
12296 |
is different from the one used by Solaris. You can use <c>sys-apps/ethtool</c> |
12297 |
to check the port link status. |
12298 |
</p> |
12299 |
|
12300 |
<p> |
12301 |
When you're done configuring your kernel, continue with <uri |
12302 |
link="#compiling">Compiling and Installing</uri>. However, after having |
12303 |
compiled the kernel, check its size: |
12304 |
</p> |
12305 |
|
12306 |
<pre caption="Check kernel size"> |
12307 |
# <i>ls -lh vmlinux</i> |
12308 |
-rw-r--r-- 1 root root 2.4M Oct 25 14:38 vmlinux |
12309 |
</pre> |
12310 |
|
12311 |
<p> |
12312 |
If the (uncompressed) size is bigger than 7.5 MB, reconfigure your kernel until |
12313 |
it doesn't exceed these limits. One way of accomplishing this is by having most |
12314 |
kernel drivers compiled as modules. Ignoring this can lead to a non-booting |
12315 |
kernel. |
12316 |
</p> |
12317 |
|
12318 |
<p> |
12319 |
Also, if your kernel is just a tad too big, you can try stripping it using the |
12320 |
<c>strip</c> command: |
12321 |
</p> |
12322 |
|
12323 |
<pre caption="Stripping the kernel"> |
12324 |
# <i>strip -R .comment -R .note vmlinux</i> |
12325 |
</pre> |
12326 |
|
12327 |
</body> |
12328 |
</subsection> |
12329 |
<subsection id="compiling"> |
12330 |
<title>Compiling and Installing</title> |
12331 |
<body> |
12332 |
|
12333 |
<p> |
12334 |
Now that your kernel is configured, it is time to compile and install it. Exit |
12335 |
the configuration and start the compilation process: |
12336 |
</p> |
12337 |
|
12338 |
<pre caption="Compiling the kernel"> |
12339 |
# <i>make && make image modules_install</i> |
12340 |
</pre> |
12341 |
|
12342 |
<p> |
12343 |
When the kernel has finished compiling, copy the kernel image to |
12344 |
<path>/boot</path>. Remember to replace <path><kernel-version></path> |
12345 |
with your actual kernel version. |
12346 |
</p> |
12347 |
|
12348 |
<pre caption="Installing the kernel"> |
12349 |
# <i>cp arch/sparc64/boot/image /boot/<kernel-version></i> |
12350 |
</pre> |
12351 |
|
12352 |
<p> |
12353 |
Now continue with <uri link="#kernel_modules">Installing Separate Kernel |
12354 |
Modules</uri>. |
12355 |
</p> |
12356 |
|
12357 |
</body> |
12358 |
</subsection> |
12359 |
</section> |
12360 |
<section id="kernel_modules"> |
12361 |
<title>Installing Separate Kernel Modules</title> |
12362 |
<subsection> |
12363 |
<title>Configuring the Modules</title> |
12364 |
<body> |
12365 |
|
12366 |
<p> |
12367 |
You should list the modules you want automatically loaded in |
12368 |
<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra options to |
12369 |
the modules too if you want. |
12370 |
</p> |
12371 |
|
12372 |
<p> |
12373 |
To view all available modules, run the following command: |
12374 |
</p> |
12375 |
|
12376 |
<pre caption="Viewing all available modules"> |
12377 |
# <i>modprobe -l</i> |
12378 |
</pre> |
12379 |
|
12380 |
<p> |
12381 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
12382 |
<path>kernel-2.6</path> file and enter the module name in it. |
12383 |
</p> |
12384 |
|
12385 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
12386 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
12387 |
</pre> |
12388 |
|
12389 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
12390 |
3c59x |
12391 |
</pre> |
12392 |
|
12393 |
<p> |
12394 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
12395 |
your System</uri>. |
12396 |
</p> |
12397 |
|
12398 |
</body> |
12399 |
</subsection> |
12400 |
</section> |
12401 |
</sections> |
12402 |
|
12403 |
|
12404 |
|
12405 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-sparc-medium.xml |
12406 |
|
12407 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-sparc-medium.xml?rev=1.1&view=markup |
12408 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-sparc-medium.xml?rev=1.1&content-type=text/plain |
12409 |
|
12410 |
Index: hb-install-sparc-medium.xml |
12411 |
=================================================================== |
12412 |
<?xml version='1.0' encoding='UTF-8'?> |
12413 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
12414 |
|
12415 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
12416 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
12417 |
|
12418 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-sparc-medium.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
12419 |
|
12420 |
<sections> |
12421 |
|
12422 |
<version>8.1</version> |
12423 |
<date>2007-06-29</date> |
12424 |
|
12425 |
<section> |
12426 |
<title>Hardware Requirements</title> |
12427 |
<subsection> |
12428 |
<title>Introduction</title> |
12429 |
<body> |
12430 |
|
12431 |
<p> |
12432 |
Before we start, we first list what hardware requirements you need to |
12433 |
successfully install Gentoo on your box. |
12434 |
</p> |
12435 |
|
12436 |
</body> |
12437 |
</subsection> |
12438 |
<subsection> |
12439 |
<title>Hardware Requirements</title> |
12440 |
<body> |
12441 |
|
12442 |
<table> |
12443 |
<tr> |
12444 |
<th>Sparc System</th> |
12445 |
<ti> |
12446 |
Please check the <uri link="/proj/en/base/sparc/sunhw.xml">Gentoo |
12447 |
Linux/SPARC64 Compatibility list</uri> or the <uri |
12448 |
link="http://www.ultralinux.org/faq.html#s_2">UltraLinux FAQ</uri> |
12449 |
</ti> |
12450 |
</tr> |
12451 |
<tr> |
12452 |
<th>CPU</th> |
12453 |
<ti> |
12454 |
We currently only support sparc64 CPUs |
12455 |
</ti> |
12456 |
</tr> |
12457 |
<tr> |
12458 |
<th>Memory</th> |
12459 |
<ti>64 MB</ti> |
12460 |
</tr> |
12461 |
<tr> |
12462 |
<th>Diskspace</th> |
12463 |
<ti>1.5 GB (excluding swap space)</ti> |
12464 |
</tr> |
12465 |
<tr> |
12466 |
<th>Swap space</th> |
12467 |
<ti>At least 256 MB</ti> |
12468 |
</tr> |
12469 |
</table> |
12470 |
|
12471 |
</body> |
12472 |
</subsection> |
12473 |
</section> |
12474 |
<!-- Copy/Paste from hb-install-x86-medium.xml --> |
12475 |
<!-- START --> |
12476 |
<section> |
12477 |
<title>The Gentoo Universal Installation CD</title> |
12478 |
<subsection> |
12479 |
<title>Introduction</title> |
12480 |
<body> |
12481 |
|
12482 |
<p> |
12483 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
12484 |
Such a tarball is an archive that contains a minimal environment from |
12485 |
which you can succesfully install Gentoo Linux onto your system. |
12486 |
</p> |
12487 |
|
12488 |
<p> |
12489 |
Installations using a stage1 or stage2 tarball file are not documented in the |
12490 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
12491 |
FAQ</uri> on these matters. |
12492 |
</p> |
12493 |
|
12494 |
</body> |
12495 |
</subsection> |
12496 |
<subsection> |
12497 |
<title>Gentoo Universal Installation CD</title> |
12498 |
<body> |
12499 |
|
12500 |
<p> |
12501 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
12502 |
environment. It allows you to boot Linux from the CD. During the boot process |
12503 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
12504 |
Installation CDs are maintained by Gentoo developers. |
12505 |
</p> |
12506 |
|
12507 |
<p> |
12508 |
There currently are two Installation CDs available: |
12509 |
</p> |
12510 |
|
12511 |
<ul> |
12512 |
<li> |
12513 |
The Universal Installation CD contains everything you need to install |
12514 |
Gentoo. It provides stage3 files for common architectures, source code |
12515 |
for the extra applications you need to choose from and, of course, the |
12516 |
installation instructions for your architecture. |
12517 |
</li> |
12518 |
<li> |
12519 |
The Minimal Installation CD contains only a minimal environment that allows |
12520 |
you to boot up and configure your network so you can connect to the |
12521 |
Internet. It does not contain any additional files and cannot be used |
12522 |
during the current installation approach. |
12523 |
</li> |
12524 |
</ul> |
12525 |
|
12526 |
<p> |
12527 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
12528 |
additional resource that you can exploit during the installation of your Gentoo |
12529 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
12530 |
you to easily and quickly install additional applications (such as |
12531 |
OpenOffice.org, KDE, GNOME, ...) immediately after the Gentoo installation and |
12532 |
right before you update your Portage tree. |
12533 |
</p> |
12534 |
|
12535 |
<p> |
12536 |
The use of the Package CD is covered later in this document. |
12537 |
</p> |
12538 |
|
12539 |
</body> |
12540 |
</subsection> |
12541 |
</section> |
12542 |
<!-- STOP --> |
12543 |
<section> |
12544 |
<title>Download, Burn and Boot a Gentoo Installation CD</title> |
12545 |
<subsection> |
12546 |
<title>Downloading and Burning the Installation CDs</title> |
12547 |
<body> |
12548 |
|
12549 |
<p> |
12550 |
You can download the Universal Installation CD (and, if you want to, the |
12551 |
Packages CD as well) from one of our <uri |
12552 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located in |
12553 |
the <path><keyval id="release-dir"/>installcd</path> directory; the Package CDs |
12554 |
are located in the <path><keyval id="release-dir"/>packagecd</path> directory. |
12555 |
</p> |
12556 |
|
12557 |
<p> |
12558 |
Inside those directories you'll find ISO-files. Those are full CD images which |
12559 |
you can write on a CD-R. |
12560 |
</p> |
12561 |
|
12562 |
<p> |
12563 |
In case you wonder if your downloaded file is corrupted or not, you can check its |
12564 |
MD5 checksum and compare it with the MD5 checksum we provide (such as |
12565 |
<path>install-sparc64-minimal-2007.0.iso.DIGESTS</path>). You can check the MD5 |
12566 |
checksum with the <c>md5sum</c> tool under Linux/Unix or <uri |
12567 |
link="http://www.etree.org/md5com.html">md5sum</uri> for Windows. |
12568 |
</p> |
12569 |
|
12570 |
<p> |
12571 |
Another way to check the validity of the downloaded file is to use GnuPG to |
12572 |
verify the cryptographic signature that we provide (the file ending with |
12573 |
<path>.asc</path>). Download the signature file and obtain the public key: |
12574 |
</p> |
12575 |
|
12576 |
<pre caption="Obtaining the public key"> |
12577 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
12578 |
</pre> |
12579 |
|
12580 |
<p> |
12581 |
Now verify the signature: |
12582 |
</p> |
12583 |
|
12584 |
<pre caption="Verify the cryptographic signature"> |
12585 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
12586 |
</pre> |
12587 |
|
12588 |
<p> |
12589 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
12590 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
12591 |
<c>K3B</c> here; more information can be found in our <uri |
12592 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
12593 |
</p> |
12594 |
|
12595 |
<ul> |
12596 |
<li> |
12597 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded |
12598 |
iso></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
12599 |
path). |
12600 |
</li> |
12601 |
<li> |
12602 |
With K3B, select <c>Tools</c> > <c>Burn CD Image</c>. Then you can locate |
12603 |
your ISO file within the 'Image to Burn' area. Finally click <c>Start</c>. |
12604 |
</li> |
12605 |
</ul> |
12606 |
|
12607 |
</body> |
12608 |
</subsection> |
12609 |
<subsection> |
12610 |
<title>Booting the Universal Installation CD</title> |
12611 |
<body> |
12612 |
|
12613 |
<p> |
12614 |
Insert the Gentoo Installation CD in the CD-ROM and boot your system. During |
12615 |
startup, press Stop-A to enter OpenBootPROM (OBP). Once you are in the OBP, |
12616 |
boot from the CD-ROM: |
12617 |
</p> |
12618 |
|
12619 |
<pre caption="Booting the Installation CD"> |
12620 |
ok <i>boot cdrom</i> |
12621 |
</pre> |
12622 |
|
12623 |
<p> |
12624 |
You will be greeted by the SILO boot manager (on the Installation CD). You can |
12625 |
hit Enter for more help if you want. Type in <c>2617</c> (if you have an FC-AL |
12626 |
machine; check the <uri |
12627 |
link="http://www.gentoo.org/proj/en/base/sparc/sunhw.xml">Hardware Compatibility |
12628 |
List</uri>) or <c>2620</c> (for everyone else) and press enter to continue |
12629 |
booting the system: |
12630 |
</p> |
12631 |
|
12632 |
<pre caption="Continue booting from the Installation CD"> |
12633 |
boot: <i>2620</i> |
12634 |
</pre> |
12635 |
|
12636 |
<p> |
12637 |
Once the Installation CD is booted, you will be automatically logged on to the |
12638 |
system. |
12639 |
</p> |
12640 |
|
12641 |
<p> |
12642 |
You should have a root ("#") prompt on the current console. You will also find a |
12643 |
root prompt on the serial console (<path>ttyS0</path>). |
12644 |
</p> |
12645 |
|
12646 |
<p> |
12647 |
Continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
12648 |
</p> |
12649 |
|
12650 |
</body> |
12651 |
</subsection> |
12652 |
<subsection id="hardware"> |
12653 |
<title>Extra Hardware Configuration</title> |
12654 |
<body> |
12655 |
|
12656 |
<p> |
12657 |
If not all hardware is supported out-of-the-box, you will need to load the |
12658 |
appropriate kernel modules. |
12659 |
</p> |
12660 |
|
12661 |
<p> |
12662 |
In the next example we try to load the <c>8139too</c> module (support for |
12663 |
certain kinds of network interfaces): |
12664 |
</p> |
12665 |
|
12666 |
<pre caption="Loading kernel modules"> |
12667 |
# <i>modprobe 8139too</i> |
12668 |
</pre> |
12669 |
|
12670 |
</body> |
12671 |
</subsection> |
12672 |
<subsection id="useraccounts"> |
12673 |
<title>Optional: User Accounts</title> |
12674 |
<body> |
12675 |
|
12676 |
<p> |
12677 |
If you plan on giving other people access to your installation |
12678 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
12679 |
security reasons), you need to create the necessary user accounts and change |
12680 |
the root password. |
12681 |
</p> |
12682 |
|
12683 |
<p> |
12684 |
To change the root password, use the <c>passwd</c> utility: |
12685 |
</p> |
12686 |
|
12687 |
<pre caption="Changing the root password"> |
12688 |
# <i>passwd</i> |
12689 |
New password: <comment>(Enter your new password)</comment> |
12690 |
Re-enter password: <comment>(Re-enter your password)</comment> |
12691 |
</pre> |
12692 |
|
12693 |
<p> |
12694 |
To create a user account, we first enter their credentials, followed by |
12695 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
12696 |
In the next example, we create a user called "john". |
12697 |
</p> |
12698 |
|
12699 |
<pre caption="Creating a user account"> |
12700 |
# <i>useradd -m -G users john</i> |
12701 |
# <i>passwd john</i> |
12702 |
New password: <comment>(Enter john's password)</comment> |
12703 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
12704 |
</pre> |
12705 |
|
12706 |
<p> |
12707 |
You can change your user id from root to the newly created user by using |
12708 |
<c>su</c>: |
12709 |
</p> |
12710 |
|
12711 |
<pre caption="Changing user id"> |
12712 |
# <i>su - john</i> |
12713 |
</pre> |
12714 |
|
12715 |
</body> |
12716 |
</subsection> |
12717 |
<subsection> |
12718 |
<title>Optional: Viewing Documentation while Installing</title> |
12719 |
<body> |
12720 |
|
12721 |
<p> |
12722 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
12723 |
installation, make sure you have created a user account (see <uri |
12724 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
12725 |
go to a new terminal and log in. |
12726 |
</p> |
12727 |
|
12728 |
<p> |
12729 |
If you want to view the documentation on the CD you can immediately run |
12730 |
<c>links</c> to read it: |
12731 |
</p> |
12732 |
|
12733 |
<pre caption="Viewing the on-CD documentation"> |
12734 |
# <i>links /mnt/cdrom/docs/handbook/html/index.html</i> |
12735 |
</pre> |
12736 |
|
12737 |
<p> |
12738 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
12739 |
more recent than the one provided on the CD. You can view it using <c>links</c> |
12740 |
as well, but only after having completed the <e>Configuring your Network</e> |
12741 |
chapter (otherwise you won't be able to go on the Internet to view the |
12742 |
document): |
12743 |
</p> |
12744 |
|
12745 |
<pre caption="Viewing the Online Documentation"> |
12746 |
# <i>links http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i> |
12747 |
</pre> |
12748 |
|
12749 |
<p> |
12750 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
12751 |
</p> |
12752 |
|
12753 |
</body> |
12754 |
</subsection> |
12755 |
<subsection> |
12756 |
<title>Optional: Starting the SSH Daemon</title> |
12757 |
<body> |
12758 |
|
12759 |
<p> |
12760 |
If you want to allow other users to access your computer during the |
12761 |
Gentoo installation (perhaps because those users are going to help you |
12762 |
install Gentoo, or even do it for you), you need to create a user |
12763 |
account for them and perhaps even provide them with your root password |
12764 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
12765 |
</p> |
12766 |
|
12767 |
<p> |
12768 |
To fire up the SSH daemon, execute the following command: |
12769 |
</p> |
12770 |
|
12771 |
<pre caption="Starting the SSH daemon"> |
12772 |
# <i>/etc/init.d/sshd start</i> |
12773 |
</pre> |
12774 |
|
12775 |
<p> |
12776 |
To be able to use sshd, you first need to set up your networking. Continue with |
12777 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
12778 |
</p> |
12779 |
|
12780 |
</body> |
12781 |
</subsection> |
12782 |
</section> |
12783 |
</sections> |
12784 |
|
12785 |
|
12786 |
|
12787 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-stage.xml |
12788 |
|
12789 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-stage.xml?rev=1.1&view=markup |
12790 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-stage.xml?rev=1.1&content-type=text/plain |
12791 |
|
12792 |
Index: hb-install-stage.xml |
12793 |
=================================================================== |
12794 |
<?xml version='1.0' encoding='UTF-8'?> |
12795 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
12796 |
|
12797 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
12798 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
12799 |
|
12800 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-stage.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
12801 |
|
12802 |
<sections> |
12803 |
|
12804 |
<version>8.0</version> |
12805 |
<date>2007-05-07</date> |
12806 |
|
12807 |
<section> |
12808 |
<title>Installing a Stage Tarball</title> |
12809 |
<subsection> |
12810 |
<title>Setting the Date/Time Right</title> |
12811 |
<body> |
12812 |
|
12813 |
<p> |
12814 |
Before you continue you need to check your date/time and update it. A |
12815 |
misconfigured clock may lead to strange results in the future! |
12816 |
</p> |
12817 |
|
12818 |
<p> |
12819 |
To verify the current date/time, run <c>date</c>: |
12820 |
</p> |
12821 |
|
12822 |
<pre caption="Verifying the date/time"> |
12823 |
# <i>date</i> |
12824 |
Fri Mar 29 16:21:18 UTC 2005 |
12825 |
</pre> |
12826 |
|
12827 |
<p> |
12828 |
If the date/time displayed is wrong, update it using the <c>date |
12829 |
MMDDhhmmYYYY</c> syntax (<b>M</b>onth, <b>D</b>ay, <b>h</b>our, <b>m</b>inute |
12830 |
and <b>Y</b>ear). At this stage, you should use UTC time. You will be able to |
12831 |
define your timezone later on. For instance, to set the date to March 29th, |
12832 |
16:21 in the year 2005: |
12833 |
</p> |
12834 |
|
12835 |
<pre caption="Setting the UTC date/time"> |
12836 |
# <i>date 032916212005</i> |
12837 |
</pre> |
12838 |
|
12839 |
</body> |
12840 |
</subsection> |
12841 |
</section> |
12842 |
<section id="available"> |
12843 |
<title>Default: Using a Stage from the Installation CD</title> |
12844 |
<subsection> |
12845 |
<title>Extracting the Stage Tarball</title> |
12846 |
<body> |
12847 |
|
12848 |
<p> |
12849 |
The stages on the CD reside in the <path>/mnt/cdrom/stages</path> directory. To |
12850 |
see a listing of available stages, use <c>ls</c>: |
12851 |
</p> |
12852 |
|
12853 |
<pre caption="List all available stages"> |
12854 |
# <i>ls /mnt/cdrom/stages</i> |
12855 |
</pre> |
12856 |
|
12857 |
<p> |
12858 |
If the system replies with an error, you may need to mount the CD-ROM first: |
12859 |
</p> |
12860 |
|
12861 |
<pre caption="Mounting the CD-ROM"> |
12862 |
# <i>ls /mnt/cdrom/stages</i> |
12863 |
ls: /mnt/cdrom/stages: No such file or directory |
12864 |
# <i>mount /dev/cdroms/cdrom0 /mnt/cdrom</i> |
12865 |
# <i>ls /mnt/cdrom/stages</i> |
12866 |
</pre> |
12867 |
|
12868 |
<p> |
12869 |
Now go into your Gentoo mountpoint (usually <path>/mnt/gentoo</path>): |
12870 |
</p> |
12871 |
|
12872 |
<pre caption="Changing directory to /mnt/gentoo"> |
12873 |
# <i>cd /mnt/gentoo</i> |
12874 |
</pre> |
12875 |
|
12876 |
<p> |
12877 |
We will now extract the stage tarball of your choice. We will do this with the |
12878 |
<c>tar</c> tool. Make sure you use the same options (<c>xvjpf</c>)! The <c>x</c> |
12879 |
stands for <e>Extract</e>, the <c>v</c> for <e>Verbose</e> to see what happens |
12880 |
during the extraction process (this one is optional), the <c>j</c> for |
12881 |
<e>Decompress with bzip2</e>, the <c>p</c> for <e>Preserve permissions</e> and |
12882 |
the <c>f</c> to denote that we want to extract a file, not standard input. In |
12883 |
the next example, we extract the stage tarball <path><keyval |
12884 |
id="stage3"/></path>. Be sure to substitute the tarball filename with your |
12885 |
stage. |
12886 |
</p> |
12887 |
|
12888 |
<pre caption="Extracting the stage tarball"> |
12889 |
# <i>tar xvjpf /mnt/cdrom/stages/<keyval id="stage3"/></i> |
12890 |
</pre> |
12891 |
|
12892 |
<p> |
12893 |
Now that the stage is installed, continue with <uri |
12894 |
link="#installing_portage">Installing Portage</uri>. |
12895 |
</p> |
12896 |
|
12897 |
</body> |
12898 |
</subsection> |
12899 |
<subsection> |
12900 |
<title>Unpacking the Stage Tarball</title> |
12901 |
<body> |
12902 |
|
12903 |
<p> |
12904 |
Now unpack your downloaded stage onto your system. We use <c>tar</c> to proceed |
12905 |
as it is the easiest method: |
12906 |
</p> |
12907 |
|
12908 |
<pre caption="Unpacking the stage"> |
12909 |
# <i>tar xvjpf stage3-*.tar.bz2</i> |
12910 |
</pre> |
12911 |
|
12912 |
<p> |
12913 |
Make sure that you use the same options (<c>xvjpf</c>). The <c>x</c> stands |
12914 |
for <e>Extract</e>, the <c>v</c> for <e>Verbose</e> to see what happens during |
12915 |
the extraction process (this one is optional), the <c>j</c> for <e>Decompress |
12916 |
with bzip2</e>, the <c>p</c> for <e>Preserve permissions</e> and the <c>f</c> |
12917 |
to denote that we want to extract a file, not standard input. |
12918 |
</p> |
12919 |
|
12920 |
<p> |
12921 |
Now that the stage is installed, continue with <uri |
12922 |
link="#installing_portage">Installing Portage</uri>. |
12923 |
</p> |
12924 |
|
12925 |
</body> |
12926 |
</subsection> |
12927 |
</section> |
12928 |
<section id="installing_portage"> |
12929 |
<title>Installing Portage</title> |
12930 |
<subsection> |
12931 |
<title>Unpacking a Portage Snapshot</title> |
12932 |
<body> |
12933 |
|
12934 |
<p> |
12935 |
You now have to install a Portage snapshot, a collection of files that inform |
12936 |
Portage what software titles you can install, which profiles are available, etc. |
12937 |
</p> |
12938 |
|
12939 |
</body> |
12940 |
</subsection> |
12941 |
<subsection id="installing_from_InstallCD"> |
12942 |
<title>Unpack the Snapshot from the Installation CD</title> |
12943 |
<body> |
12944 |
|
12945 |
<p> |
12946 |
To install the snapshot, take a look inside <path>/mnt/cdrom/snapshots/</path> |
12947 |
to see what snapshot is available: |
12948 |
</p> |
12949 |
|
12950 |
<pre caption="Checking the /mnt/cdrom/snapshots content"> |
12951 |
# <i>ls /mnt/cdrom/snapshots</i> |
12952 |
</pre> |
12953 |
|
12954 |
<p> |
12955 |
Now extract the snapshot using the following construct. Again, make sure you |
12956 |
use the correct options with <c>tar</c>. Also, the <c>-C</c> is with a capital |
12957 |
<c>C</c>, not <c>c</c>. In the next example we use |
12958 |
<path>portage-<date>.tar.bz2</path> as the snapshot filename. Be sure to |
12959 |
substitute with the name of the snapshot that is on your Installation CD. |
12960 |
</p> |
12961 |
|
12962 |
<pre caption="Extracting a Portage snapshot"> |
12963 |
# <i>tar xvjf /mnt/cdrom/snapshots/portage-<date>.tar.bz2 -C /mnt/gentoo/usr</i> |
12964 |
</pre> |
12965 |
|
12966 |
</body> |
12967 |
</subsection> |
12968 |
<subsection id="copysources"> |
12969 |
<title>Copy Source Code Archives</title> |
12970 |
<body> |
12971 |
|
12972 |
<p> |
12973 |
You also need to copy over all source code from the Universal Installation CD. |
12974 |
</p> |
12975 |
|
12976 |
<pre caption="Copy over source code"> |
12977 |
# <i>mkdir /mnt/gentoo/usr/portage/distfiles</i> |
12978 |
# <i>cp /mnt/cdrom/distfiles/* /mnt/gentoo/usr/portage/distfiles/</i> |
12979 |
</pre> |
12980 |
|
12981 |
</body> |
12982 |
</subsection> |
12983 |
</section> |
12984 |
<section id="compile_options"> |
12985 |
<title>Configuring the Compile Options</title> |
12986 |
<subsection> |
12987 |
<title>Introduction</title> |
12988 |
<body> |
12989 |
|
12990 |
<p> |
12991 |
To optimize Gentoo, you can set a couple of variables which impact Portage |
12992 |
behaviour. All those variables can be set as environment variables (using |
12993 |
<c>export</c>) but that isn't permanent. To keep your settings, Portage provides |
12994 |
you with <path>/etc/make.conf</path>, a configuration file for Portage. It is |
12995 |
this file we will edit now. |
12996 |
</p> |
12997 |
|
12998 |
<note> |
12999 |
A commented listing of all possible variables can be found in |
13000 |
<path>/mnt/gentoo/etc/make.conf.example</path>. For a successful Gentoo |
13001 |
installation you'll only need to set the variables which are mentioned beneath. |
13002 |
</note> |
13003 |
|
13004 |
<p> |
13005 |
Fire up your favorite editor (in this guide we use <c>nano</c>) so we can alter |
13006 |
the optimization variables we will discuss hereafter. |
13007 |
</p> |
13008 |
|
13009 |
<pre caption="Opening /etc/make.conf"> |
13010 |
# <i>nano -w /mnt/gentoo/etc/make.conf</i> |
13011 |
</pre> |
13012 |
|
13013 |
<p> |
13014 |
As you probably noticed, the <path>make.conf.example</path> file is |
13015 |
structured in a generic way: commented lines start with "#", other lines define |
13016 |
variables using the <c>VARIABLE="content"</c> syntax. The <path>make.conf</path> |
13017 |
file uses the same syntax. Several of those variables are discussed next. |
13018 |
</p> |
13019 |
|
13020 |
<warn> |
13021 |
Do not make any modifications to the USE variable if you are performing a stage3 |
13022 |
with GRP installation. You can alter the USE variable after having installed the |
13023 |
packages you want. Gremlins are known to attack your system if you ignore this |
13024 |
warning! |
13025 |
</warn> |
13026 |
|
13027 |
</body> |
13028 |
</subsection> |
13029 |
<subsection> |
13030 |
<title>CHOST</title> |
13031 |
<body> |
13032 |
|
13033 |
<p> |
13034 |
The <c>CHOST</c> variable declares the target build host for your system. This |
13035 |
variable should already be set to the correct value. <brite>Do not edit |
13036 |
it</brite> as that might break your system. If the <c>CHOST</c> variable does |
13037 |
not look correct to you, you might be using the wrong stage3 tarball. |
13038 |
</p> |
13039 |
|
13040 |
</body> |
13041 |
</subsection> |
13042 |
<subsection> |
13043 |
<title>CFLAGS and CXXFLAGS</title> |
13044 |
<body> |
13045 |
|
13046 |
<p> |
13047 |
The <c>CFLAGS</c> and <c>CXXFLAGS</c> variables define the optimization flags |
13048 |
for the <c>gcc</c> C and C++ compiler respectively. Although we define those |
13049 |
generally here, you will only have maximum performance if you optimize these |
13050 |
flags for each program separately. The reason for this is because every program |
13051 |
is different. |
13052 |
</p> |
13053 |
|
13054 |
<p> |
13055 |
In <path>make.conf</path> you should define the optimization flags you think |
13056 |
will make your system the most responsive <e>generally</e>. Don't place |
13057 |
experimental settings in this variable; too much optimization can make |
13058 |
programs behave bad (crash, or even worse, malfunction). |
13059 |
</p> |
13060 |
|
13061 |
<p> |
13062 |
We cannot explain all possible optimization options here, but if you want to |
13063 |
investigate them all, read the <uri link="http://gcc.gnu.org/onlinedocs/">GNU |
13064 |
Online Manual(s)</uri> or the <c>gcc</c> info page (<c>info gcc</c> -- only |
13065 |
works on a working Linux system). For common optimizations and architecture |
13066 |
specific settings, please read <path>/etc/make.conf.example</path>. This |
13067 |
file also contains lots of examples and information; don't forget to read it |
13068 |
too. |
13069 |
</p> |
13070 |
|
13071 |
<p> |
13072 |
A first setting is the <c>-march=</c> or <c>-mcpu=</c> flag, which specifies |
13073 |
the name of the target architecture. Possible options are described in the |
13074 |
<path>make.conf.example</path> file (as comments). |
13075 |
</p> |
13076 |
|
13077 |
<p> |
13078 |
A second one is the <c>-O</c> flag (that is a capital O, not a zero), |
13079 |
which specifies the <c>gcc</c> optimization |
13080 |
class flag. Possible classes are <c>s</c> (for size-optimized), |
13081 |
<c>0</c> (zero - for no optimizations), <c>1</c>, <c>2</c> or <c>3</c> for more |
13082 |
speed-optimization flags (every class has the same flags as the one before, plus |
13083 |
some extras). <c>-O2</c> is the recommended default. |
13084 |
</p> |
13085 |
|
13086 |
<p> |
13087 |
Another popular optimization flag is <c>-pipe</c> (use pipes rather than |
13088 |
temporary files for communication between the various stages of compilation). |
13089 |
It has no impact on the generated code. |
13090 |
</p> |
13091 |
|
13092 |
<p> |
13093 |
Using <c>-fomit-frame-pointer</c> (which doesn't keep the frame pointer in a |
13094 |
register for functions that don't need one) might have serious repercussions on |
13095 |
the debugging of applications. |
13096 |
</p> |
13097 |
|
13098 |
<p> |
13099 |
When you define the <c>CFLAGS</c> and <c>CXXFLAGS</c>, you should combine |
13100 |
several optimization flags. The default values contained in the stage3 archive |
13101 |
you unpacked should be good enough. The following example is just an example: |
13102 |
</p> |
13103 |
|
13104 |
<pre caption="Defining the CFLAGS and CXXFLAGS variable"> |
13105 |
CFLAGS="<keyval id="CFLAGS"/>" |
13106 |
<comment># Use the same settings for both variables</comment> |
13107 |
CXXFLAGS="${CFLAGS}" |
13108 |
</pre> |
13109 |
|
13110 |
</body> |
13111 |
</subsection> |
13112 |
<subsection> |
13113 |
<title>MAKEOPTS</title> |
13114 |
<body> |
13115 |
|
13116 |
<p> |
13117 |
With <c>MAKEOPTS</c> you define how many parallel compilations should occur when |
13118 |
you install a package. A good choice is the number of CPUs in your system plus |
13119 |
one, but this guideline isn't always perfect. |
13120 |
</p> |
13121 |
|
13122 |
<pre caption="MAKEOPTS for a regular, 1-CPU system"> |
13123 |
MAKEOPTS="-j2" |
13124 |
</pre> |
13125 |
|
13126 |
</body> |
13127 |
</subsection> |
13128 |
<subsection> |
13129 |
<title>Ready, Set, Go!</title> |
13130 |
<body> |
13131 |
|
13132 |
<p> |
13133 |
Update your <path>/mnt/gentoo/etc/make.conf</path> to your own preference and |
13134 |
save (<c>nano</c> users would hit <c>Ctrl-X</c>). You are now ready to continue |
13135 |
with <uri link="?part=1&chap=6">Chrooting into the Gentoo Base System</uri>. |
13136 |
</p> |
13137 |
|
13138 |
</body> |
13139 |
</subsection> |
13140 |
</section> |
13141 |
</sections> |
13142 |
|
13143 |
|
13144 |
|
13145 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-system.xml |
13146 |
|
13147 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-system.xml?rev=1.1&view=markup |
13148 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-system.xml?rev=1.1&content-type=text/plain |
13149 |
|
13150 |
Index: hb-install-system.xml |
13151 |
=================================================================== |
13152 |
<?xml version='1.0' encoding='UTF-8'?> |
13153 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
13154 |
|
13155 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
13156 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
13157 |
|
13158 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-system.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
13159 |
|
13160 |
<sections> |
13161 |
|
13162 |
<version>8.0</version> |
13163 |
<date>2007-05-07</date> |
13164 |
|
13165 |
<section> |
13166 |
<title>Chrooting</title> |
13167 |
<subsection> |
13168 |
<title>Mounting the /proc and /dev Filesystems</title> |
13169 |
<body> |
13170 |
|
13171 |
<p> |
13172 |
Mount the <path>/proc</path> filesystem on <path>/mnt/gentoo/proc</path> to |
13173 |
allow the installation to use the kernel-provided information within the |
13174 |
chrooted environment, and then mount-bind the <path>/dev</path> filesystem. |
13175 |
</p> |
13176 |
|
13177 |
<pre caption="Mounting /proc and /dev"> |
13178 |
# <i>mount -t proc none /mnt/gentoo/proc</i> |
13179 |
# <i>mount -o bind /dev /mnt/gentoo/dev</i> |
13180 |
</pre> |
13181 |
|
13182 |
</body> |
13183 |
</subsection> |
13184 |
<subsection> |
13185 |
<title>Entering the new Environment</title> |
13186 |
<body> |
13187 |
|
13188 |
<p> |
13189 |
Now that all partitions are initialized and the base environment |
13190 |
installed, it is time to enter our new installation environment by |
13191 |
<e>chrooting</e> into it. This means that we change from the current |
13192 |
installation environment to your installation system (namely the |
13193 |
initialized partitions). |
13194 |
</p> |
13195 |
|
13196 |
<p> |
13197 |
This chrooting is done in three steps. First we will change the root |
13198 |
from <path>/</path> (on the installation medium) to <path>/mnt/gentoo</path> |
13199 |
(on your partitions) using <c>chroot</c>. Then we will create a new environment |
13200 |
using <c>env-update</c>, which essentially creates environment variables. |
13201 |
Finally, we load those variables into memory using <c>source</c>. |
13202 |
</p> |
13203 |
|
13204 |
<pre caption="Chrooting into the new environment"> |
13205 |
# <i>chroot /mnt/gentoo /bin/bash</i> |
13206 |
# <i>env-update</i> |
13207 |
>>> Regenerating /etc/ld.so.cache... |
13208 |
# <i>source /etc/profile</i> |
13209 |
# <i>export PS1="(chroot) $PS1"</i> |
13210 |
</pre> |
13211 |
|
13212 |
<p> |
13213 |
Congratulations! You are now inside your own Gentoo Linux environment. |
13214 |
Of course it is far from finished, which is why the installation still |
13215 |
has some sections left :-) |
13216 |
</p> |
13217 |
|
13218 |
</body> |
13219 |
</subsection> |
13220 |
<subsection> |
13221 |
<title>Creating the Portage cache</title> |
13222 |
<body> |
13223 |
|
13224 |
<p> |
13225 |
You have already installed the Portage tree, but you should now build the |
13226 |
Portage cache to speed up future emerges. <c>emerge --metadata</c> does this |
13227 |
for you. |
13228 |
</p> |
13229 |
|
13230 |
<pre caption="Creating the Portage cache"> |
13231 |
# <i>emerge --metadata</i> |
13232 |
</pre> |
13233 |
|
13234 |
</body> |
13235 |
</subsection> |
13236 |
</section> |
13237 |
|
13238 |
<section id="configure_USE"> |
13239 |
<title>Configuring the USE Variable</title> |
13240 |
<subsection> |
13241 |
<title>What is the USE Variable?</title> |
13242 |
<body> |
13243 |
|
13244 |
<p> |
13245 |
<c>USE</c> is one of the most powerful variables Gentoo provides to its users. |
13246 |
Several programs can be compiled with or without optional support for certain |
13247 |
items. For instance, some programs can be compiled with gtk-support, or with |
13248 |
qt-support. Others can be compiled with or without SSL support. Some programs |
13249 |
can even be compiled with framebuffer support (svgalib) instead of X11 support |
13250 |
(X-server). |
13251 |
</p> |
13252 |
|
13253 |
<p> |
13254 |
Most distributions compile their packages with support for as much as possible, |
13255 |
increasing the size of the programs and startup time, not to mention an enormous |
13256 |
amount of dependencies. With Gentoo you can define what options a package |
13257 |
should be compiled with. This is where <c>USE</c> comes into play. |
13258 |
</p> |
13259 |
|
13260 |
<p> |
13261 |
In the <c>USE</c> variable you define keywords which are mapped onto |
13262 |
compile-options. For instance, <e>ssl</e> will compile ssl-support in the |
13263 |
programs that support it. <e>-X</e> will remove X-server support (note the |
13264 |
minus sign in front). <e>gnome gtk -kde -qt3 -qt4</e> will compile your |
13265 |
programs with gnome (and gtk) support, and not with kde (and qt) support, |
13266 |
making your system fully tweaked for GNOME. |
13267 |
</p> |
13268 |
|
13269 |
</body> |
13270 |
</subsection> |
13271 |
<subsection> |
13272 |
<title>Modifying the USE Variable</title> |
13273 |
<body> |
13274 |
|
13275 |
<warn> |
13276 |
Do not make any modifications to the USE variable yet if you plan to use our |
13277 |
prebuilt packages (GRP set). You can alter the USE variable after having |
13278 |
installed the packages you want. Gremlins are known to attack your system |
13279 |
if you ignore this warning! |
13280 |
</warn> |
13281 |
|
13282 |
<p> |
13283 |
The default <c>USE</c> settings are placed in |
13284 |
<path>/etc/make.profile/make.defaults</path>. What you place in |
13285 |
<path>/etc/make.conf</path> is calculated against these defaults settings. If |
13286 |
you add something to the <c>USE</c> setting, it is added to the default list. If |
13287 |
you remove something from the <c>USE</c> setting (by placing a minus sign in |
13288 |
front of it) it is removed from the default list (if it was in the default list |
13289 |
at all). <e>Never</e> alter anything inside the <path>/etc/make.profile</path> |
13290 |
directory; it gets overwritten when you update Portage! |
13291 |
</p> |
13292 |
|
13293 |
<p> |
13294 |
A full description on <c>USE</c> can be found in the second part of the Gentoo |
13295 |
Handbook, <uri link="?part=2&chap=2">USE flags</uri>. A full description on |
13296 |
the available USE flags can be found on your system in |
13297 |
<path>/usr/portage/profiles/use.desc</path>. |
13298 |
</p> |
13299 |
|
13300 |
<pre caption="Viewing available USE flags"> |
13301 |
# <i>less /usr/portage/profiles/use.desc</i> |
13302 |
<comment>(You can scroll using your arrow keys, exit by pressing 'q')</comment> |
13303 |
</pre> |
13304 |
|
13305 |
<p> |
13306 |
As an example we show a <c>USE</c> setting for a KDE-based system with DVD, ALSA |
13307 |
and CD Recording support: |
13308 |
</p> |
13309 |
|
13310 |
<pre caption="Opening /etc/make.conf"> |
13311 |
# <i>nano -w /etc/make.conf</i> |
13312 |
</pre> |
13313 |
|
13314 |
<pre caption="USE setting"> |
13315 |
USE="-gtk -gnome qt3 qt4 kde dvd alsa cdr" |
13316 |
</pre> |
13317 |
|
13318 |
</body> |
13319 |
</subsection> |
13320 |
</section> |
13321 |
</sections> |
13322 |
|
13323 |
|
13324 |
|
13325 |
1.1 xml/htdocs/doc/en/handbook/2007.1/hb-install-tools.xml |
13326 |
|
13327 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-tools.xml?rev=1.1&view=markup |
13328 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-tools.xml?rev=1.1&content-type=text/plain |
13329 |
|
13330 |
Index: hb-install-tools.xml |
13331 |
=================================================================== |
13332 |
<?xml version='1.0' encoding='UTF-8'?> |
13333 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
13334 |
|
13335 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
13336 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
13337 |
|
13338 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/hb-install-tools.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
13339 |
|
13340 |
<sections> |
13341 |
|
13342 |
<version>8.0</version> |
13343 |
<date>2007-05-07</date> |
13344 |
|
13345 |
<section> |
13346 |
<title>System Logger</title> |
13347 |
<body> |
13348 |
|
13349 |
<p> |
13350 |
Some tools are missing from the <e>stage3</e> archive because several packages |
13351 |
provide the same functionality. It is now up to you to choose which ones you |
13352 |
want to install. |
13353 |
</p> |
13354 |
|
13355 |
<p> |
13356 |
The first tool you need to decide on has to provide logging facilities for your |
13357 |
system. Unix and Linux have an excellent history of logging capabilities -- if |
13358 |
you want you can log everything that happens on your system in logfiles. This |
13359 |
happens through the <e>system logger</e>. |
13360 |
</p> |
13361 |
|
13362 |
<p> |
13363 |
Gentoo offers several system loggers to choose from. There are <c>sysklogd</c>, |
13364 |
which is the traditional set of system logging daemons, <c>syslog-ng</c>, an |
13365 |
advanced system logger, and <c>metalog</c> which is a highly-configurable |
13366 |
system logger. Others might be available through Portage as well - our number of |
13367 |
available packages increases on a daily basis. |
13368 |
</p> |
13369 |
|
13370 |
<p> |
13371 |
If you plan on using <c>sysklogd</c> or <c>syslog-ng</c> you might want to |
13372 |
install <c>logrotate</c> afterwards as those system loggers don't provide any |
13373 |
rotation mechanism for the log files. |
13374 |
</p> |
13375 |
|
13376 |
<!-- |
13377 |
Even though syslog-ng does not rotate the logs, it does conform to the syslog |
13378 |
RFC (http://www.faqs.org/rfcs/rfc3164.html) and is far more powerful than most other system loggers. That and some architectures really prefer syslog-ng |
13379 |
above others (metalog for instance doesn't work nicely with sparc all the |
13380 |
time). |
13381 |
--> |
13382 |
|
13383 |
<p> |
13384 |
To install the system logger of your choice, <c>emerge</c> it and have it added |
13385 |
to the default runlevel using <c>rc-update</c>. The following example installs |
13386 |
<c>syslog-ng</c>. Of course substitute with your system logger: |
13387 |
</p> |
13388 |
|
13389 |
<pre caption="Installing a system logger"> |
13390 |
# <i>emerge syslog-ng</i> |
13391 |
# <i>rc-update add syslog-ng default</i> |
13392 |
</pre> |
13393 |
|
13394 |
</body> |
13395 |
</section> |
13396 |
<section> |
13397 |
<title>Optional: Cron Daemon</title> |
13398 |
<body> |
13399 |
|
13400 |
<p> |
13401 |
Next is the cron daemon. Although it is optional and not required for your |
13402 |
system, it is wise to install one. But what is a cron daemon? A cron daemon |
13403 |
executes scheduled commands. It is very handy if you need to execute some |
13404 |
command regularly (for instance daily, weekly or monthly). |
13405 |
</p> |
13406 |
|
13407 |
<p> |
13408 |
We only provide <c>vixie-cron</c> for networkless installations. If you want |
13409 |
another cron daemon you can wait and install it later on. |
13410 |
</p> |
13411 |
|
13412 |
<pre caption="Installing a cron daemon"> |
13413 |
# <i>emerge vixie-cron</i> |
13414 |
# <i>rc-update add vixie-cron default</i> |
13415 |
</pre> |
13416 |
|
13417 |
</body> |
13418 |
</section> |
13419 |
<section> |
13420 |
<title>Optional: File Indexing</title> |
13421 |
<body> |
13422 |
|
13423 |
<p> |
13424 |
If you want to index your system's files so you are able to quickly |
13425 |
locate them using the <c>locate</c> tool, you need to install |
13426 |
<c>sys-apps/slocate</c>. |
13427 |
</p> |
13428 |
|
13429 |
<pre caption="Installing slocate"> |
13430 |
# <i>emerge slocate</i> |
13431 |
</pre> |
13432 |
|
13433 |
</body> |
13434 |
</section> |
13435 |
<section> |
13436 |
<title>File System Tools</title> |
13437 |
<subsection> |
13438 |
<body> |
13439 |
|
13440 |
<p> |
13441 |
Depending on what file systems you are using, you need to install the necessary |
13442 |
file system utilities (for checking the filesystem integrity, creating |
13443 |
additional file systems etc.). |
13444 |
</p> |
13445 |
|
13446 |
<p> |
13447 |
The following table lists the tools you need to install if you use a certain |
13448 |
file system. Not all filesystems are available for each and every architecture |
13449 |
though. |
13450 |
</p> |
13451 |
|
13452 |
<table> |
13453 |
<tr> |
13454 |
<th>File System</th> |
13455 |
<th>Tool</th> |
13456 |
<th>Install Command</th> |
13457 |
</tr> |
13458 |
<tr> |
13459 |
<ti>XFS</ti> |
13460 |
<ti>xfsprogs</ti> |
13461 |
<ti><c>emerge xfsprogs</c></ti> |
13462 |
</tr> |
13463 |
<tr> |
13464 |
<ti>ReiserFS</ti> |
13465 |
<ti>reiserfsprogs</ti> |
13466 |
<ti><c>emerge reiserfsprogs</c></ti> |
13467 |
</tr> |
13468 |
<tr> |
13469 |
<ti>JFS</ti> |
13470 |
<ti>jfsutils</ti> |
13471 |
<ti><c>emerge jfsutils</c></ti> |
13472 |
</tr> |
13473 |
</table> |
13474 |
|
13475 |
<p> |
13476 |
If you are an EVMS user, you need to install <c>emvs</c>: |
13477 |
</p> |
13478 |
|
13479 |
<pre caption="Installing EVMS utilities"> |
13480 |
# <i>USE="-gtk" emerge evms</i> |
13481 |
</pre> |
13482 |
|
13483 |
<p> |
13484 |
The <c>USE="-gtk"</c> will prevent the installation of dependencies. If you |
13485 |
want to enable the <c>evms</c> graphical tools, you can recompile <c>evms</c> |
13486 |
later on. |
13487 |
</p> |
13488 |
|
13489 |
</body> |
13490 |
</subsection> |
13491 |
<subsection test="contains('PPC PPC64', func:keyval('arch'))"> |
13492 |
<title>Optional: RAID utilities for IBM hardware</title> |
13493 |
<body> |
13494 |
|
13495 |
<p> |
13496 |
If you are using SCSI RAID on a POWER5-based system, you should consider |
13497 |
installing the <c>iprutils</c> which will allow you to work with the RAID disk |
13498 |
array, get status on the disks in the arrays, and update microcode among other |
13499 |
functions. |
13500 |
</p> |
13501 |
|
13502 |
<pre caption="Installing iprutils"> |
13503 |
# <i>emerge iprutils</i> |
13504 |
</pre> |
13505 |
|
13506 |
</body> |
13507 |
</subsection> |
13508 |
</section> |
13509 |
<section> |
13510 |
<title>Networking Tools</title> |
13511 |
<subsection> |
13512 |
<body> |
13513 |
|
13514 |
<p> |
13515 |
If you don't require any additional networking-related tools (such as <c>ppp</c> |
13516 |
or a dhcp client) continue with <uri link="?part=1&chap=10">Configuring the |
13517 |
Bootloader</uri>. |
13518 |
</p> |
13519 |
|
13520 |
</body> |
13521 |
</subsection> |
13522 |
<subsection> |
13523 |
<title>Optional: Installing a DHCP Client</title> |
13524 |
<body> |
13525 |
|
13526 |
<p> |
13527 |
If you require Gentoo to automatically obtain an IP address for your network |
13528 |
interface(s), you need to install <c>dhcpcd</c> (or any other DHCP Client) |
13529 |
on your system. If you don't do this now, you might not be able to connect |
13530 |
to the internet after the installation! |
13531 |
</p> |
13532 |
|
13533 |
<pre caption="Installing dhcpcd"> |
13534 |
# <i>emerge dhcpcd</i> |
13535 |
</pre> |
13536 |
|
13537 |
</body> |
13538 |
</subsection> |
13539 |
<subsection> |
13540 |
<title>Optional: Installing a PPPoE Client</title> |
13541 |
<body> |
13542 |
|
13543 |
<p> |
13544 |
If you need <c>ppp</c> to connect to the net, you need to install it. |
13545 |
</p> |
13546 |
|
13547 |
<pre caption="Installing ppp"> |
13548 |
# <i>emerge ppp</i> |
13549 |
</pre> |
13550 |
|
13551 |
<p> |
13552 |
Now continue with <uri link="?part=1&chap=10">Configuring the |
13553 |
Bootloader</uri>. |
13554 |
</p> |
13555 |
|
13556 |
</body> |
13557 |
</subsection> |
13558 |
</section> |
13559 |
</sections> |
13560 |
|
13561 |
|
13562 |
|
13563 |
1.1 xml/htdocs/doc/en/handbook/2007.1/index.xml |
13564 |
|
13565 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/index.xml?rev=1.1&view=markup |
13566 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.1/index.xml?rev=1.1&content-type=text/plain |
13567 |
|
13568 |
Index: index.xml |
13569 |
=================================================================== |
13570 |
<?xml version='1.0' encoding="UTF-8"?> |
13571 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
13572 |
|
13573 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.1/index.xml,v 1.1 2007/08/01 18:25:54 swift Exp $ --> |
13574 |
|
13575 |
<guide link="/doc/en/handbook/2007.0/index.xml"> |
13576 |
<title>Gentoo 2007.0 Networkless Handbook</title> |
13577 |
|
13578 |
<author title="Author"> |
13579 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
13580 |
</author> |
13581 |
|
13582 |
<abstract> |
13583 |
The Gentoo 2007.0 Networkless Handbook is an effort to centralize documentation |
13584 |
into a coherent handbook. It contains the networkless installation instructions |
13585 |
for the 2007.0 release and parts on working with Gentoo and Portage. |
13586 |
</abstract> |
13587 |
|
13588 |
<license/> |
13589 |
|
13590 |
<version>8.6</version> |
13591 |
<date>2007-06-06</date> |
13592 |
|
13593 |
<chapter> |
13594 |
<title>The Gentoo Linux 2007.0 Networkless Handbooks</title> |
13595 |
|
13596 |
<section> |
13597 |
<title>Available languages</title> |
13598 |
<body> |
13599 |
|
13600 |
<p> |
13601 |
The Gentoo Linux 2007.0 Networkless Handbook is available in the following |
13602 |
languages: |
13603 |
</p> |
13604 |
|
13605 |
<p> |
13606 |
<uri link="/doc/en/handbook/2007.0/">English</uri> | |
13607 |
<uri link="/doc/id/handbook/2007.0/">Indonesian</uri> | |
13608 |
<uri link="/doc/it/handbook/2007.0/">Italian</uri> | |
13609 |
<uri link="/doc/pl/handbook/2007.0/">Polish</uri> |
13610 |
</p> |
13611 |
|
13612 |
</body> |
13613 |
</section> |
13614 |
<section> |
13615 |
<title>Introduction</title> |
13616 |
<body> |
13617 |
|
13618 |
<p> |
13619 |
Welcome to the Gentoo Linux 2007.0 Networkless Handbooks. These handbooks are |
13620 |
released together with the Gentoo Linux releases and contain the necessary |
13621 |
installation instructions to install Gentoo Linux 2007.0 <brite>without an |
13622 |
internet connection.</brite> |
13623 |
</p> |
13624 |
|
13625 |
<p> |
13626 |
However, if you want to install Gentoo Linux using the latest versions of all |
13627 |
available packages, please use the Installation Instructions in the <uri |
13628 |
link="/doc/en/handbook/">Gentoo Linux Handbook</uri> for your architecture. |
13629 |
</p> |
13630 |
|
13631 |
</body> |
13632 |
</section> |
13633 |
</chapter> |
13634 |
<chapter> |
13635 |
<title>View the Handbook</title> |
13636 |
<section> |
13637 |
<body> |
13638 |
|
13639 |
<table> |
13640 |
<tr> |
13641 |
<th>Format</th> |
13642 |
<th>Description</th> |
13643 |
<th>Links</th> |
13644 |
</tr> |
13645 |
<tr> |
13646 |
<ti>HTML</ti> |
13647 |
<ti>One page per chapter, perfect for online viewing</ti> |
13648 |
<ti> |
13649 |
<uri link="handbook-x86.xml">x86</uri>, |
13650 |
<uri link="handbook-sparc.xml">sparc</uri>, |
13651 |
<uri link="handbook-amd64.xml">amd64</uri>, |
13652 |
<uri link="handbook-ppc.xml">ppc</uri>, |
13653 |
<uri link="handbook-ppc64.xml">ppc64</uri>, |
13654 |
<uri link="handbook-hppa.xml">hppa</uri> |
13655 |
</ti> |
13656 |
</tr> |
13657 |
<tr> |
13658 |
<ti>HTML</ti> |
13659 |
<ti>All in one page</ti> |
13660 |
<ti> |
13661 |
<uri link="handbook-x86.xml?full=1">x86</uri>, |
13662 |
<uri link="handbook-sparc.xml?full=1">sparc</uri>, |
13663 |
<uri link="handbook-amd64.xml?full=1">amd64</uri>, |
13664 |
<uri link="handbook-ppc.xml?full=1">ppc</uri>, |
13665 |
<uri link="handbook-ppc64.xml?full=1">ppc64</uri>, |
13666 |
<uri link="handbook-hppa.xml?full=1">hppa</uri> |
13667 |
</ti> |
13668 |
</tr> |
13669 |
<tr> |
13670 |
<ti>HTML</ti> |
13671 |
<ti>All in one page, printable version</ti> |
13672 |
<ti> |
13673 |
<uri link="handbook-x86.xml?style=printable&full=1">x86</uri>, |
13674 |
<uri link="handbook-sparc.xml?style=printable&full=1">sparc</uri>, |
13675 |
<uri link="handbook-amd64.xml?style=printable&full=1">amd64</uri>, |
13676 |
<uri link="handbook-ppc.xml?style=printable&full=1">ppc</uri>, |
13677 |
<uri link="handbook-ppc64.xml?style=printable&full=1">ppc64</uri>, |
13678 |
<uri link="handbook-hppa.xml?style=printable&full=1">hppa</uri> |
13679 |
</ti> |
13680 |
</tr> |
13681 |
</table> |
13682 |
|
13683 |
</body> |
13684 |
</section> |
13685 |
</chapter> |
13686 |
</guide> |
13687 |
|
13688 |
|
13689 |
|
13690 |
-- |
13691 |
gentoo-doc-cvs@g.o mailing list |