1 |
nightmorph 07/03/19 20:37:28 |
2 |
|
3 |
Added: handbook-alpha.xml handbook-amd64.xml |
4 |
handbook-hppa.xml handbook-ppc64.xml |
5 |
handbook-ppc.xml handbook-sparc.xml |
6 |
handbook-x86.xml hb-install-about.xml |
7 |
hb-install-alpha-bootloader.xml |
8 |
hb-install-alpha-disk.xml |
9 |
hb-install-alpha-kernel.xml |
10 |
hb-install-alpha-medium.xml hb-install-config.xml |
11 |
hb-installer-about.xml hb-install-finalise.xml |
12 |
hb-install-gli-dialog.xml hb-install-gli-medium.xml |
13 |
hb-install-gtkfe.xml hb-install-hppa-bootloader.xml |
14 |
hb-install-hppa-disk.xml hb-install-hppa-kernel.xml |
15 |
hb-install-hppa-medium.xml hb-install-network.xml |
16 |
hb-install-next.xml hb-install-ppc64-bootloader.xml |
17 |
hb-install-ppc64-disk.xml |
18 |
hb-install-ppc64-kernel.xml |
19 |
hb-install-ppc64-medium.xml |
20 |
hb-install-ppc-bootloader.xml |
21 |
hb-install-ppc-disk.xml hb-install-ppc-kernel.xml |
22 |
hb-install-ppc-medium.xml |
23 |
hb-install-sparc-bootloader.xml |
24 |
hb-install-sparc-disk.xml |
25 |
hb-install-sparc-kernel.xml |
26 |
hb-install-sparc-medium.xml hb-install-stage.xml |
27 |
hb-install-system.xml hb-install-tools.xml |
28 |
index.xml |
29 |
Log: |
30 |
initial import |
31 |
|
32 |
Revision Changes Path |
33 |
1.1 xml/htdocs/doc/en/handbook/2007.0/handbook-alpha.xml |
34 |
|
35 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-alpha.xml?rev=1.1&view=markup |
36 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-alpha.xml?rev=1.1&content-type=text/plain |
37 |
|
38 |
Index: handbook-alpha.xml |
39 |
=================================================================== |
40 |
<?xml version='1.0' encoding='UTF-8'?> |
41 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
42 |
|
43 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-alpha.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
44 |
|
45 |
<book link="/doc/en/handbook/2006.1/handbook-alpha.xml"> |
46 |
<title>Gentoo Linux 2006.1 Alpha Handbook</title> |
47 |
|
48 |
<author title="Author"> |
49 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
50 |
</author> |
51 |
<author title="Author"> |
52 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
53 |
</author> |
54 |
<author title="Author"> |
55 |
<mail link="uberlord@g.o">Roy Marples</mail> |
56 |
</author> |
57 |
<author title="Author"> |
58 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
59 |
</author> |
60 |
<author title="Author"> |
61 |
<mail link="chouser@g.o">Chris Houser</mail> |
62 |
</author> |
63 |
<author title="Author"> |
64 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
65 |
</author> |
66 |
<author title="Gentoo x86 Developer"> |
67 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
68 |
</author> |
69 |
<author title="Gentoo Alpha Developer"> |
70 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
71 |
</author><!-- Does not want to be listed on the rendered page |
72 |
<author title="Gentoo Developer"> |
73 |
Aron Griffis |
74 |
</author> |
75 |
--> |
76 |
<author title="Gentoo AMD64 Developer"> |
77 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
78 |
</author> |
79 |
<author title="Gentoo HPPA developer"> |
80 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
81 |
</author> |
82 |
<author title="Gentoo PPC developer"> |
83 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
84 |
</author> |
85 |
<author title="Gentoo SPARC developer"> |
86 |
<mail link="blademan@g.o">Joe Kallar</mail> |
87 |
</author> |
88 |
<author title="Editor"> |
89 |
<mail link="zhen@g.o">John P. Davis</mail> |
90 |
</author> |
91 |
<author title="Editor">Pierre-Henri Jondot</author> |
92 |
<author title="Editor"> |
93 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
94 |
</author> |
95 |
<author title="Editor"> |
96 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
97 |
</author> |
98 |
<author title="Editor"> |
99 |
<mail link="seo@g.o">Jungmin Seo</mail> |
100 |
</author> |
101 |
<author title="Editor"> |
102 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
103 |
</author> |
104 |
<author title="Editor"> |
105 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
106 |
</author> |
107 |
<author title="Editor"> |
108 |
<mail link="peitolm@g.o">Colin Morey</mail> |
109 |
</author> |
110 |
<author title="Editor"> |
111 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
112 |
</author> |
113 |
<author title="Editor"> |
114 |
<mail link="carl@g.o">Carl Anderson</mail> |
115 |
</author> |
116 |
<author title="Editor"> |
117 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
118 |
</author> |
119 |
<author title="Editor"> |
120 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
121 |
</author> |
122 |
<author title="Editor"> |
123 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
124 |
</author> |
125 |
<author title="Editor"> |
126 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
127 |
</author> |
128 |
<author title="Editor"> |
129 |
<mail link="erwin@g.o">Erwin</mail> |
130 |
</author> |
131 |
<author title="Editor"> |
132 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
133 |
</author> |
134 |
<author title="Editor"> |
135 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
136 |
</author> |
137 |
<author title="Editor"> |
138 |
<mail link="neysx@g.o">Xavier Neys</mail> |
139 |
</author> |
140 |
<author title="Reviewer"> |
141 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
142 |
</author> |
143 |
<author title="Reviewer"> |
144 |
<mail link="dberkholz@g.o">Donnie Berkholz</mail> |
145 |
</author> |
146 |
<author title="Reviewer"> |
147 |
<mail link="antifa@g.o">Ken Nowack</mail> |
148 |
</author> |
149 |
<author title="Contributor"> |
150 |
<mail link="pylon@g.o">Lars Weiler</mail> |
151 |
</author> |
152 |
|
153 |
<abstract> |
154 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
155 |
This handbook contains the installation instructions for a networkless |
156 |
installation on Alpha systems and parts about working with Gentoo and Portage. |
157 |
</abstract> |
158 |
|
159 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
160 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
161 |
<license/> |
162 |
|
163 |
<version>7.1</version> |
164 |
<date>2006-08-30</date> |
165 |
|
166 |
<part> |
167 |
<title>Installing Gentoo</title> |
168 |
<abstract> |
169 |
In this part you learn how to install Gentoo on your system. |
170 |
</abstract> |
171 |
|
172 |
<chapter> |
173 |
<title>About the Gentoo Linux Installation</title> |
174 |
<abstract> |
175 |
Users not familiar with Gentoo do not always know that choice is what |
176 |
Gentoo is all about. |
177 |
</abstract> |
178 |
<include href="hb-install-about.xml"/> |
179 |
</chapter> |
180 |
|
181 |
<chapter> |
182 |
<title>Booting the Universal Installation CD</title> |
183 |
<abstract> |
184 |
Using our Universal Installation CD you can boot up your system into a running |
185 |
environment that allows you to install Gentoo. |
186 |
</abstract> |
187 |
<include href="hb-install-alpha-medium.xml"/> |
188 |
</chapter> |
189 |
|
190 |
<chapter> |
191 |
<title>Configuring your Network</title> |
192 |
<abstract> |
193 |
If you need networking, this is the place where the network (and Internet |
194 |
connection) is configured. |
195 |
</abstract> |
196 |
<include href="hb-install-network.xml"/> |
197 |
</chapter> |
198 |
|
199 |
<chapter> |
200 |
<title>Preparing the Disks</title> |
201 |
<abstract> |
202 |
To be able to install Gentoo, you must create the necessary partitions. |
203 |
This chapter describes how to partition a disk for future usage. |
204 |
</abstract> |
205 |
<include href="hb-install-alpha-disk.xml"/> |
206 |
</chapter> |
207 |
|
208 |
<chapter> |
209 |
<title>Installing the Gentoo Installation Files</title> |
210 |
<abstract> |
211 |
In this chapter we describe how you extract a stage3 file and how to configure |
212 |
Portage. |
213 |
</abstract> |
214 |
<include href="hb-install-stage.xml"/> |
215 |
</chapter> |
216 |
|
217 |
<chapter> |
218 |
<title>Chrooting into the Gentoo Base System</title> |
219 |
<abstract> |
220 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
221 |
the USE variable. |
222 |
</abstract> |
223 |
<include href="hb-install-system.xml"/> |
224 |
</chapter> |
225 |
|
226 |
<chapter> |
227 |
<title>Configuring the Kernel</title> |
228 |
<abstract> |
229 |
The Linux kernel is the core of every distribution. This chapter |
230 |
explains how to configure your kernel. |
231 |
</abstract> |
232 |
<include href="hb-install-alpha-kernel.xml"/> |
233 |
</chapter> |
234 |
|
235 |
<chapter> |
236 |
<title>Configuring your System</title> |
237 |
<abstract> |
238 |
You need to edit some important configuration files. In this chapter |
239 |
you receive an overview of these files and an explanation on how to |
240 |
proceed. |
241 |
</abstract> |
242 |
<include href="hb-install-config.xml"/> |
243 |
</chapter> |
244 |
|
245 |
<chapter> |
246 |
<title>Installing Necessary System Tools</title> |
247 |
<abstract> |
248 |
As mentioned before, Gentoo is about customization. In this chapter we help you |
249 |
choose and install some important tools. |
250 |
</abstract> |
251 |
<include href="hb-install-tools.xml"/> |
252 |
</chapter> |
253 |
|
254 |
<chapter> |
255 |
<title>Configuring the Bootloader</title> |
256 |
<abstract> |
257 |
Several bootloaders exist. Each one of them has its own way of |
258 |
configuration. In this chapter we'll describe all possibilities for you |
259 |
and step you through the process of configuring a bootloader to your |
260 |
needs. |
261 |
</abstract> |
262 |
<include href="hb-install-alpha-bootloader.xml"/> |
263 |
</chapter> |
264 |
|
265 |
<chapter> |
266 |
<title>Finalizing your Gentoo Installation</title> |
267 |
<abstract> |
268 |
You're almost done. We'll just create one (or more) users for your |
269 |
system and (optionally) install the prebuild packages. |
270 |
</abstract> |
271 |
<include href="hb-install-finalise.xml"/> |
272 |
</chapter> |
273 |
|
274 |
<chapter> |
275 |
<title>Where to go from here?</title> |
276 |
<abstract> |
277 |
Now you have your Gentoo system, but what's next? |
278 |
</abstract> |
279 |
<include href="hb-install-next.xml"/> |
280 |
</chapter> |
281 |
</part> |
282 |
|
283 |
<part> |
284 |
<title>Working with Gentoo</title> |
285 |
<abstract> |
286 |
Learn how to work with Gentoo: installing software, altering variables, changing |
287 |
Portage behaviour etc. |
288 |
</abstract> |
289 |
|
290 |
<chapter> |
291 |
<title>A Portage Introduction</title> |
292 |
<abstract> |
293 |
This chapter explains the "simple" steps a user definitely needs to know to |
294 |
maintain the software on his system. |
295 |
</abstract> |
296 |
<include href="../hb-working-portage.xml"/> |
297 |
</chapter> |
298 |
|
299 |
<chapter> |
300 |
<title>USE flags</title> |
301 |
<abstract> |
302 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
303 |
work with USE-flags and understand how USE-flags interact with your system. |
304 |
</abstract> |
305 |
<include href="../hb-working-use.xml"/> |
306 |
</chapter> |
307 |
|
308 |
<chapter> |
309 |
<title>Portage Features</title> |
310 |
<abstract> |
311 |
Discover the features Portage has, such as support for distributed compiling, |
312 |
ccache and more. |
313 |
</abstract> |
314 |
<include href="../hb-working-features.xml"/> |
315 |
</chapter> |
316 |
|
317 |
<chapter> |
318 |
<title>Initscripts</title> |
319 |
<abstract> |
320 |
Gentoo uses a special initscript format which, amongst other features, allows |
321 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
322 |
these aspects and explains how to deal with these scripts. |
323 |
</abstract> |
324 |
<include href="../hb-working-rcscripts.xml"/> |
325 |
</chapter> |
326 |
|
327 |
<chapter> |
328 |
<title>Environment Variables</title> |
329 |
<abstract> |
330 |
With Gentoo you can easily manage the environment variables for your system. |
331 |
This chapter explains how you do that, and also describes frequently used |
332 |
variables. |
333 |
</abstract> |
334 |
<include href="../hb-working-variables.xml"/> |
335 |
</chapter> |
336 |
</part> |
337 |
|
338 |
<part> |
339 |
<title>Working with Portage</title> |
340 |
<abstract> |
341 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
342 |
Software Management Tool. |
343 |
</abstract> |
344 |
|
345 |
<chapter> |
346 |
<title>Files and Directories</title> |
347 |
<abstract> |
348 |
Once you want to know Portage in-depth you need to know where it stores its |
349 |
files and data. |
350 |
</abstract> |
351 |
<include href="../hb-portage-files.xml"/> |
352 |
</chapter> |
353 |
|
354 |
<chapter> |
355 |
<title>Configuring through Variables</title> |
356 |
<abstract> |
357 |
Portage is completely configurable through various variables you can set in the |
358 |
configuration file or as environment variable. |
359 |
</abstract> |
360 |
<include href="../hb-portage-configuration.xml"/> |
361 |
</chapter> |
362 |
|
363 |
<chapter> |
364 |
<title>Mixing Software Branches</title> |
365 |
<abstract> |
366 |
Gentoo provides software separated in several branches, depending on stability |
367 |
and architectural support. "Mixing Software Branches" inform you how these |
368 |
branches can be configured and how you can override this separation |
369 |
individually. |
370 |
</abstract> |
371 |
<include href="../hb-portage-branches.xml"/> |
372 |
</chapter> |
373 |
|
374 |
<chapter> |
375 |
<title>Additional Portage Tools</title> |
376 |
<abstract> |
377 |
Portage comes with a few extra tools that might make your Gentoo experience even |
378 |
better. Read on to discover how to use dispatch-conf and other tools. |
379 |
</abstract> |
380 |
<include href="../hb-portage-tools.xml"/> |
381 |
</chapter> |
382 |
|
383 |
<chapter> |
384 |
<title>Diverting from the Official Tree</title> |
385 |
<abstract> |
386 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
387 |
your own Portage tree, how to synchronise only the categories you want, inject |
388 |
packages and more. |
389 |
</abstract> |
390 |
<include href="../hb-portage-diverttree.xml"/> |
391 |
</chapter> |
392 |
</part> |
393 |
|
394 |
<part> |
395 |
<title>Gentoo Network Configuration</title> |
396 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
397 |
|
398 |
<chapter> |
399 |
<title>Getting Started</title> |
400 |
<abstract> |
401 |
A guide to quickly get your network interface up and running in most common |
402 |
environments. |
403 |
</abstract> |
404 |
<include href="../hb-net-start.xml"/> |
405 |
</chapter> |
406 |
|
407 |
<chapter> |
408 |
<title>Advanced Configuration</title> |
409 |
<abstract> |
410 |
Here we learn about how the configuration works - you need to know this |
411 |
before we learn about modular networking. |
412 |
</abstract> |
413 |
<include href="../hb-net-advanced.xml"/> |
414 |
</chapter> |
415 |
|
416 |
<chapter> |
417 |
<title>Modular Networking</title> |
418 |
<abstract> |
419 |
Gentoo provides you flexible networking - here you are told about choosing |
420 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
421 |
</abstract> |
422 |
<include href="../hb-net-modules.xml"/> |
423 |
</chapter> |
424 |
|
425 |
<chapter> |
426 |
<title>Wireless Networking</title> |
427 |
<abstract> |
428 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
429 |
</abstract> |
430 |
<include href="../hb-net-wireless.xml"/> |
431 |
</chapter> |
432 |
|
433 |
<chapter> |
434 |
<title>Adding Functionality</title> |
435 |
<abstract> |
436 |
If you're feeling adventurous, you can add your own functions to networking. |
437 |
</abstract> |
438 |
<include href="../hb-net-functions.xml"/> |
439 |
</chapter> |
440 |
|
441 |
<chapter> |
442 |
<title>Network Management</title> |
443 |
<abstract> |
444 |
For laptop users or people who move their computer around different networks. |
445 |
</abstract> |
446 |
<include href="../hb-net-management.xml"/> |
447 |
</chapter> |
448 |
</part> |
449 |
|
450 |
</book> |
451 |
|
452 |
|
453 |
|
454 |
1.1 xml/htdocs/doc/en/handbook/2007.0/handbook-amd64.xml |
455 |
|
456 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-amd64.xml?rev=1.1&view=markup |
457 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-amd64.xml?rev=1.1&content-type=text/plain |
458 |
|
459 |
Index: handbook-amd64.xml |
460 |
=================================================================== |
461 |
<?xml version='1.0' encoding='UTF-8'?> |
462 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
463 |
|
464 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-amd64.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
465 |
|
466 |
<book link="/doc/en/handbook/2006.1/handbook-amd64.xml"> |
467 |
<title>Gentoo Linux 2006.1 AMD64 Handbook</title> |
468 |
|
469 |
<values> |
470 |
<key id="arch">AMD64</key> |
471 |
<key id="release-dir">releases/amd64/2006.1/</key> |
472 |
<key id="online-book">2006.1/handbook-amd64.xml</key> |
473 |
</values> |
474 |
|
475 |
<author title="Author"> |
476 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
477 |
</author> |
478 |
<author title="Author"> |
479 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
480 |
</author> |
481 |
<author title="Author"> |
482 |
<mail link="uberlord@g.o">Roy Marples</mail> |
483 |
</author> |
484 |
<author title="Author"> |
485 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
486 |
</author> |
487 |
<author title="Author"> |
488 |
<mail link="chouser@g.o">Chris Houser</mail> |
489 |
</author> |
490 |
<author title="Author"> |
491 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
492 |
</author> |
493 |
<author title="Author"> |
494 |
<mail link="nightmorph@g.o">Joshua Saddler</mail> |
495 |
</author> |
496 |
<author title="Gentoo x86 Developer"> |
497 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
498 |
</author> |
499 |
<author title="Gentoo Alpha Developer"> |
500 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
501 |
</author> |
502 |
<!-- Does not want to be listed on the rendered page |
503 |
<author title="Gentoo Developer"> |
504 |
Aron Griffis |
505 |
</author> |
506 |
--> |
507 |
<author title="Gentoo AMD64 Developer"> |
508 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
509 |
</author> |
510 |
<author title="Gentoo HPPA developer"> |
511 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
512 |
</author> |
513 |
<author title="Gentoo PPC developer"> |
514 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
515 |
</author> |
516 |
<author title="Gentoo SPARC developer"> |
517 |
<mail link="blademan@g.o">Joe Kallar</mail> |
518 |
</author> |
519 |
<author title="Editor"> |
520 |
<mail link="zhen@g.o">John P. Davis</mail> |
521 |
</author> |
522 |
<author title="Editor">Pierre-Henri Jondot</author> |
523 |
<author title="Editor"> |
524 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
525 |
</author> |
526 |
<author title="Editor"> |
527 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
528 |
</author> |
529 |
<author title="Editor"> |
530 |
<mail link="seo@g.o">Jungmin Seo</mail> |
531 |
</author> |
532 |
<author title="Editor"> |
533 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
534 |
</author> |
535 |
<author title="Editor"> |
536 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
537 |
</author> |
538 |
<author title="Editor"> |
539 |
<mail link="peitolm@g.o">Colin Morey</mail> |
540 |
</author> |
541 |
<author title="Editor"> |
542 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
543 |
</author> |
544 |
<author title="Editor"> |
545 |
<mail link="carl@g.o">Carl Anderson</mail> |
546 |
</author> |
547 |
<author title="Editor"> |
548 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
549 |
</author> |
550 |
<author title="Editor"> |
551 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
552 |
</author> |
553 |
<author title="Editor"> |
554 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
555 |
</author> |
556 |
<author title="Editor"> |
557 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
558 |
</author> |
559 |
<author title="Editor"> |
560 |
<mail link="erwin@g.o">Erwin</mail> |
561 |
</author> |
562 |
<author title="Editor"> |
563 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
564 |
</author> |
565 |
<author title="Editor"> |
566 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
567 |
</author> |
568 |
<author title="Editor"> |
569 |
<mail link="neysx@g.o">Xavier Neys</mail> |
570 |
</author> |
571 |
<author title="Editor"> |
572 |
<mail link="fox2mike@g.o">Shyam Mani</mail> |
573 |
</author> |
574 |
<author title="Reviewer"> |
575 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
576 |
</author> |
577 |
<author title="Reviewer"> |
578 |
<mail link="dberkholz@g.o">Donnie Berkholz</mail> |
579 |
</author> |
580 |
<author title="Reviewer"> |
581 |
<mail link="antifa@g.o">Ken Nowack</mail> |
582 |
</author> |
583 |
<author title="Contributor"> |
584 |
<mail link="pylon@g.o">Lars Weiler</mail> |
585 |
</author> |
586 |
|
587 |
<abstract> |
588 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
589 |
This handbook contains the installation instructions for a networkless |
590 |
installation on AMD64 & EM64T systems and parts about working with Gentoo |
591 |
and Portage. |
592 |
</abstract> |
593 |
|
594 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
595 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
596 |
<license/> |
597 |
|
598 |
<version>7.1</version> |
599 |
<date>2006-08-30</date> |
600 |
|
601 |
<part> |
602 |
<title>Installing Gentoo</title> |
603 |
<abstract> |
604 |
In this part you learn how to install Gentoo on your system. |
605 |
</abstract> |
606 |
|
607 |
<chapter> |
608 |
<title>About the Gentoo Linux Installation</title> |
609 |
<abstract> |
610 |
Users not familiar with Gentoo do not always know that choice is what |
611 |
Gentoo is all about. |
612 |
</abstract> |
613 |
<include href="hb-installer-about.xml"/> |
614 |
</chapter> |
615 |
|
616 |
<chapter> |
617 |
<title>Booting the Installer LiveCD</title> |
618 |
<abstract> |
619 |
Using our Installer LiveCD you can boot up your system into a running |
620 |
environment that allows you to install Gentoo. |
621 |
</abstract> |
622 |
<include href="hb-install-gli-medium.xml"/> |
623 |
</chapter> |
624 |
|
625 |
<chapter> |
626 |
<title>Using the GTK+ based Gentoo Linux Installer</title> |
627 |
<abstract> |
628 |
You now have an option of using our graphical installer to install Gentoo. |
629 |
Configure the options you need through an easy to use GUI and you're ready to |
630 |
go. |
631 |
</abstract> |
632 |
<include href="hb-install-gtkfe.xml" /> |
633 |
</chapter> |
634 |
|
635 |
<chapter> |
636 |
<title>Using the Dialog based Gentoo Linux Installer</title> |
637 |
<abstract> |
638 |
You also have an option of using our text based installer to install Gentoo. |
639 |
Configure the options you need through an easy to use set of menus and you're |
640 |
ready to go. |
641 |
</abstract> |
642 |
<include href="hb-install-gli-dialog.xml" /> |
643 |
</chapter> |
644 |
|
645 |
<chapter> |
646 |
<title>Where to go from here?</title> |
647 |
<abstract> |
648 |
Now you have your Gentoo system, but what's next? |
649 |
</abstract> |
650 |
<include href="hb-install-next.xml"/> |
651 |
</chapter> |
652 |
</part> |
653 |
|
654 |
<part> |
655 |
<title>Working with Gentoo</title> |
656 |
<abstract> |
657 |
Learn how to work with Gentoo: installing software, altering variables, |
658 |
changing Portage behaviour etc. |
659 |
</abstract> |
660 |
|
661 |
<chapter> |
662 |
<title>A Portage Introduction</title> |
663 |
<abstract> |
664 |
This chapter explains the "simple" steps a user definitely needs to know to |
665 |
maintain the software on his system. |
666 |
</abstract> |
667 |
<include href="../hb-working-portage.xml"/> |
668 |
</chapter> |
669 |
|
670 |
<chapter> |
671 |
<title>USE flags</title> |
672 |
<abstract> |
673 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
674 |
work with USE-flags and understand how USE-flags interact with your system. |
675 |
</abstract> |
676 |
<include href="../hb-working-use.xml"/> |
677 |
</chapter> |
678 |
|
679 |
<chapter> |
680 |
<title>Portage Features</title> |
681 |
<abstract> |
682 |
Discover the features Portage has, such as support for distributed compiling, |
683 |
ccache and more. |
684 |
</abstract> |
685 |
<include href="../hb-working-features.xml"/> |
686 |
</chapter> |
687 |
|
688 |
<chapter> |
689 |
<title>Initscripts</title> |
690 |
<abstract> |
691 |
Gentoo uses a special initscript format which, amongst other features, allows |
692 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
693 |
these aspects and explains how to deal with these scripts. |
694 |
</abstract> |
695 |
<include href="../hb-working-rcscripts.xml"/> |
696 |
</chapter> |
697 |
|
698 |
<chapter> |
699 |
<title>Environment Variables</title> |
700 |
<abstract> |
701 |
With Gentoo you can easily manage the environment variables for your system. |
702 |
This chapter explains how you do that, and also describes frequently used |
703 |
variables. |
704 |
</abstract> |
705 |
<include href="../hb-working-variables.xml"/> |
706 |
</chapter> |
707 |
</part> |
708 |
|
709 |
<part> |
710 |
<title>Working with Portage</title> |
711 |
<abstract> |
712 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
713 |
Software Management Tool. |
714 |
</abstract> |
715 |
|
716 |
<chapter> |
717 |
<title>Files and Directories</title> |
718 |
<abstract> |
719 |
Once you want to know Portage in-depth you need to know where it stores its |
720 |
files and data. |
721 |
</abstract> |
722 |
<include href="../hb-portage-files.xml"/> |
723 |
</chapter> |
724 |
|
725 |
<chapter> |
726 |
<title>Configuring through Variables</title> |
727 |
<abstract> |
728 |
Portage is completely configurable through various variables you can set in the |
729 |
configuration file or as environment variable. |
730 |
</abstract> |
731 |
<include href="../hb-portage-configuration.xml"/> |
732 |
</chapter> |
733 |
|
734 |
<chapter> |
735 |
<title>Mixing Software Branches</title> |
736 |
<abstract> |
737 |
Gentoo provides software separated in several branches, depending on stability |
738 |
and architectural support. "Mixing Software Branches" inform you how these |
739 |
branches can be configured and how you can override this separation |
740 |
individually. |
741 |
</abstract> |
742 |
<include href="../hb-portage-branches.xml"/> |
743 |
</chapter> |
744 |
|
745 |
<chapter> |
746 |
<title>Additional Portage Tools</title> |
747 |
<abstract> |
748 |
Portage comes with a few extra tools that might make your Gentoo experience even |
749 |
better. Read on to discover how to use dispatch-conf and other tools. |
750 |
</abstract> |
751 |
<include href="../hb-portage-tools.xml"/> |
752 |
</chapter> |
753 |
|
754 |
<chapter> |
755 |
<title>Diverting from the Official Tree</title> |
756 |
<abstract> |
757 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
758 |
your own Portage tree, how to synchronise only the categories you want, inject |
759 |
packages and more. |
760 |
</abstract> |
761 |
<include href="../hb-portage-diverttree.xml"/> |
762 |
</chapter> |
763 |
</part> |
764 |
|
765 |
<part> |
766 |
<title>Gentoo Network Configuration</title> |
767 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
768 |
|
769 |
<chapter> |
770 |
<title>Getting Started</title> |
771 |
<abstract> |
772 |
A guide to quickly get your network interface up and running in most common |
773 |
environments. |
774 |
</abstract> |
775 |
<include href="../hb-net-start.xml"/> |
776 |
</chapter> |
777 |
|
778 |
<chapter> |
779 |
<title>Advanced Configuration</title> |
780 |
<abstract> |
781 |
Here we learn about how the configuration works - you need to know this |
782 |
before we learn about modular networking. |
783 |
</abstract> |
784 |
<include href="../hb-net-advanced.xml"/> |
785 |
</chapter> |
786 |
|
787 |
<chapter> |
788 |
<title>Modular Networking</title> |
789 |
<abstract> |
790 |
Gentoo provides you flexible networking - here you are told about choosing |
791 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
792 |
</abstract> |
793 |
<include href="../hb-net-modules.xml"/> |
794 |
</chapter> |
795 |
|
796 |
<chapter> |
797 |
<title>Wireless Networking</title> |
798 |
<abstract> |
799 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
800 |
</abstract> |
801 |
<include href="../hb-net-wireless.xml"/> |
802 |
</chapter> |
803 |
|
804 |
<chapter> |
805 |
<title>Adding Functionality</title> |
806 |
<abstract> |
807 |
If you're feeling adventurous, you can add your own functions to networking. |
808 |
</abstract> |
809 |
<include href="../hb-net-functions.xml"/> |
810 |
</chapter> |
811 |
|
812 |
<chapter> |
813 |
<title>Network Management</title> |
814 |
<abstract> |
815 |
For laptop users or people who move their computer around different networks. |
816 |
</abstract> |
817 |
<include href="../hb-net-management.xml"/> |
818 |
</chapter> |
819 |
</part> |
820 |
|
821 |
</book> |
822 |
|
823 |
|
824 |
|
825 |
1.1 xml/htdocs/doc/en/handbook/2007.0/handbook-hppa.xml |
826 |
|
827 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-hppa.xml?rev=1.1&view=markup |
828 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-hppa.xml?rev=1.1&content-type=text/plain |
829 |
|
830 |
Index: handbook-hppa.xml |
831 |
=================================================================== |
832 |
<?xml version='1.0' encoding='UTF-8'?> |
833 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
834 |
|
835 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-hppa.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
836 |
|
837 |
<book link="/doc/en/handbook/2006.1/handbook-hppa.xml"> |
838 |
<title>Gentoo Linux 2006.1 HPPA Handbook</title> |
839 |
|
840 |
<author title="Author"> |
841 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
842 |
</author> |
843 |
<author title="Author"> |
844 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
845 |
</author> |
846 |
<author title="Author"> |
847 |
<mail link="uberlord@g.o">Roy Marples</mail> |
848 |
</author> |
849 |
<author title="Author"> |
850 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
851 |
</author> |
852 |
<author title="Author"> |
853 |
<mail link="chouser@g.o">Chris Houser</mail> |
854 |
</author> |
855 |
<author title="Author"> |
856 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
857 |
</author> |
858 |
<author title="Gentoo x86 Developer"> |
859 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
860 |
</author> |
861 |
<author title="Gentoo Alpha Developer"> |
862 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
863 |
</author><!-- Does not want to be listed on the rendered page |
864 |
<author title="Gentoo Developer"> |
865 |
Aron Griffis |
866 |
</author> |
867 |
--> |
868 |
<author title="Gentoo AMD64 Developer"> |
869 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
870 |
</author> |
871 |
<author title="Gentoo HPPA developer"> |
872 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
873 |
</author> |
874 |
<author title="Gentoo PPC developer"> |
875 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
876 |
</author> |
877 |
<author title="Gentoo SPARC developer"> |
878 |
<mail link="blademan@g.o">Joe Kallar</mail> |
879 |
</author> |
880 |
<author title="Editor"> |
881 |
<mail link="zhen@g.o">John P. Davis</mail> |
882 |
</author> |
883 |
<author title="Editor">Pierre-Henri Jondot</author> |
884 |
<author title="Editor"> |
885 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
886 |
</author> |
887 |
<author title="Editor"> |
888 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
889 |
</author> |
890 |
<author title="Editor"> |
891 |
<mail link="seo@g.o">Jungmin Seo</mail> |
892 |
</author> |
893 |
<author title="Editor"> |
894 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
895 |
</author> |
896 |
<author title="Editor"> |
897 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
898 |
</author> |
899 |
<author title="Editor"> |
900 |
<mail link="peitolm@g.o">Colin Morey</mail> |
901 |
</author> |
902 |
<author title="Editor"> |
903 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
904 |
</author> |
905 |
<author title="Editor"> |
906 |
<mail link="carl@g.o">Carl Anderson</mail> |
907 |
</author> |
908 |
<author title="Editor"> |
909 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
910 |
</author> |
911 |
<author title="Editor"> |
912 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
913 |
</author> |
914 |
<author title="Editor"> |
915 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
916 |
</author> |
917 |
<author title="Editor"> |
918 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
919 |
</author> |
920 |
<author title="Editor"> |
921 |
<mail link="erwin@g.o">Erwin</mail> |
922 |
</author> |
923 |
<author title="Editor"> |
924 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
925 |
</author> |
926 |
<author title="Editor"> |
927 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
928 |
</author> |
929 |
<author title="Editor"> |
930 |
<mail link="neysx@g.o">Xavier Neys</mail> |
931 |
</author> |
932 |
<author title="Reviewer"> |
933 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
934 |
</author> |
935 |
<author title="Reviewer"> |
936 |
<mail link="dberkholz@g.o">Donnie Berkholz</mail> |
937 |
</author> |
938 |
<author title="Reviewer"> |
939 |
<mail link="antifa@g.o">Ken Nowack</mail> |
940 |
</author> |
941 |
<author title="Contributor"> |
942 |
<mail link="pylon@g.o">Lars Weiler</mail> |
943 |
</author> |
944 |
|
945 |
<abstract> |
946 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
947 |
This handbook contains the installation instructions for a networkless |
948 |
installation on HPPA systems and parts about working with Gentoo and Portage. |
949 |
</abstract> |
950 |
|
951 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
952 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
953 |
<license/> |
954 |
|
955 |
<version>7.1</version> |
956 |
<date>2006-08-30</date> |
957 |
|
958 |
<part> |
959 |
<title>Installing Gentoo</title> |
960 |
<abstract> |
961 |
In this part you learn how to install Gentoo on your system. |
962 |
</abstract> |
963 |
|
964 |
<chapter> |
965 |
<title>About the Gentoo Linux Installation</title> |
966 |
<abstract> |
967 |
Users not familiar with Gentoo do not always know that choice is what |
968 |
Gentoo is all about. |
969 |
</abstract> |
970 |
<include href="hb-install-about.xml"/> |
971 |
</chapter> |
972 |
|
973 |
<chapter> |
974 |
<title>Booting the Universal Installation CD</title> |
975 |
<abstract> |
976 |
Using our Universal Installation CD you can boot up your system into a running |
977 |
environment that allows you to install Gentoo. |
978 |
</abstract> |
979 |
<include href="hb-install-hppa-medium.xml"/> |
980 |
</chapter> |
981 |
|
982 |
<chapter> |
983 |
<title>Configuring your Network</title> |
984 |
<abstract> |
985 |
If you need networking, this is the place where the network (and Internet |
986 |
connection) is configured. |
987 |
</abstract> |
988 |
<include href="hb-install-network.xml"/> |
989 |
</chapter> |
990 |
|
991 |
<chapter> |
992 |
<title>Preparing the Disks</title> |
993 |
<abstract> |
994 |
To be able to install Gentoo, you must create the necessary partitions. |
995 |
This chapter describes how to partition a disk for future usage. |
996 |
</abstract> |
997 |
<include href="hb-install-hppa-disk.xml"/> |
998 |
</chapter> |
999 |
|
1000 |
<chapter> |
1001 |
<title>Installing the Gentoo Installation Files</title> |
1002 |
<abstract> |
1003 |
Gentoo installs work through so-called stage-files. In this chapter we |
1004 |
describe how you extract a stage-file and configure Portage. |
1005 |
</abstract> |
1006 |
<include href="hb-install-stage.xml"/> |
1007 |
</chapter> |
1008 |
|
1009 |
<chapter> |
1010 |
<title>Chrooting into the Gentoo Base System</title> |
1011 |
<abstract> |
1012 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
1013 |
the USE variable. |
1014 |
</abstract> |
1015 |
<include href="hb-install-system.xml"/> |
1016 |
</chapter> |
1017 |
|
1018 |
<chapter> |
1019 |
<title>Configuring the Kernel</title> |
1020 |
<abstract> |
1021 |
The Linux kernel is the core of every distribution. This chapter |
1022 |
explains how to configure your kernel. |
1023 |
</abstract> |
1024 |
<include href="hb-install-hppa-kernel.xml"/> |
1025 |
</chapter> |
1026 |
|
1027 |
<chapter> |
1028 |
<title>Configuring your System</title> |
1029 |
<abstract> |
1030 |
You need to edit some important configuration files. In this chapter |
1031 |
you receive an overview of these files and an explanation on how to |
1032 |
proceed. |
1033 |
</abstract> |
1034 |
<include href="hb-install-config.xml"/> |
1035 |
</chapter> |
1036 |
|
1037 |
<chapter> |
1038 |
<title>Installing Necessary System Tools</title> |
1039 |
<abstract> |
1040 |
As mentioned before, Gentoo is about customization. In this chapter we help you |
1041 |
choose and install some important tools. |
1042 |
</abstract> |
1043 |
<include href="hb-install-tools.xml"/> |
1044 |
</chapter> |
1045 |
|
1046 |
<chapter> |
1047 |
<title>Configuring the Bootloader</title> |
1048 |
<abstract> |
1049 |
In this chapter we'll describe the PALO bootloader |
1050 |
and step you through the process of configuring PALO to your |
1051 |
needs. |
1052 |
</abstract> |
1053 |
<include href="hb-install-hppa-bootloader.xml"/> |
1054 |
</chapter> |
1055 |
|
1056 |
<chapter> |
1057 |
<title>Finalizing your Gentoo Installation</title> |
1058 |
<abstract> |
1059 |
You're almost done. We'll just create one (or more) users for your |
1060 |
system and (optionally) install prebuilt packages. |
1061 |
</abstract> |
1062 |
<include href="hb-install-finalise.xml"/> |
1063 |
</chapter> |
1064 |
|
1065 |
<chapter> |
1066 |
<title>Where to go from here?</title> |
1067 |
<abstract> |
1068 |
Now you have your Gentoo system, but what's next? |
1069 |
</abstract> |
1070 |
<include href="hb-install-next.xml"/> |
1071 |
</chapter> |
1072 |
</part> |
1073 |
|
1074 |
<part> |
1075 |
<title>Working with Gentoo</title> |
1076 |
<abstract> |
1077 |
Learn how to work with Gentoo: installing software, altering variables, changing |
1078 |
Portage behaviour etc. |
1079 |
</abstract> |
1080 |
|
1081 |
<chapter> |
1082 |
<title>A Portage Introduction</title> |
1083 |
<abstract> |
1084 |
This chapter explains the "simple" steps a user definitely needs to know to |
1085 |
maintain the software on his system. |
1086 |
</abstract> |
1087 |
<include href="../hb-working-portage.xml"/> |
1088 |
</chapter> |
1089 |
|
1090 |
<chapter> |
1091 |
<title>USE flags</title> |
1092 |
<abstract> |
1093 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
1094 |
work with USE-flags and understand how USE-flags interact with your system. |
1095 |
</abstract> |
1096 |
<include href="../hb-working-use.xml"/> |
1097 |
</chapter> |
1098 |
|
1099 |
<chapter> |
1100 |
<title>Portage Features</title> |
1101 |
<abstract> |
1102 |
Discover the features Portage has, such as support for distributed compiling, |
1103 |
ccache and more. |
1104 |
</abstract> |
1105 |
<include href="../hb-working-features.xml"/> |
1106 |
</chapter> |
1107 |
|
1108 |
<chapter> |
1109 |
<title>Initscripts</title> |
1110 |
<abstract> |
1111 |
Gentoo uses a special initscript format which, amongst other features, allows |
1112 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
1113 |
these aspects and explains how to deal with these scripts. |
1114 |
</abstract> |
1115 |
<include href="../hb-working-rcscripts.xml"/> |
1116 |
</chapter> |
1117 |
|
1118 |
<chapter> |
1119 |
<title>Environment Variables</title> |
1120 |
<abstract> |
1121 |
With Gentoo you can easily manage the environment variables for your system. |
1122 |
This chapter explains how you do that, and also describes frequently used |
1123 |
variables. |
1124 |
</abstract> |
1125 |
<include href="../hb-working-variables.xml"/> |
1126 |
</chapter> |
1127 |
</part> |
1128 |
|
1129 |
<part> |
1130 |
<title>Working with Portage</title> |
1131 |
<abstract> |
1132 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
1133 |
Software Management Tool. |
1134 |
</abstract> |
1135 |
|
1136 |
<chapter> |
1137 |
<title>Files and Directories</title> |
1138 |
<abstract> |
1139 |
Once you want to know Portage in-depth you need to know where it stores its |
1140 |
files and data. |
1141 |
</abstract> |
1142 |
<include href="../hb-portage-files.xml"/> |
1143 |
</chapter> |
1144 |
|
1145 |
<chapter> |
1146 |
<title>Configuring through Variables</title> |
1147 |
<abstract> |
1148 |
Portage is completely configurable through various variables you can set in the |
1149 |
configuration file or as environment variable. |
1150 |
</abstract> |
1151 |
<include href="../hb-portage-configuration.xml"/> |
1152 |
</chapter> |
1153 |
|
1154 |
<chapter> |
1155 |
<title>Mixing Software Branches</title> |
1156 |
<abstract> |
1157 |
Gentoo provides software separated in several branches, depending on stability |
1158 |
and architectural support. "Mixing Software Branches" inform you how these |
1159 |
branches can be configured and how you can override this separation |
1160 |
individually. |
1161 |
</abstract> |
1162 |
<include href="../hb-portage-branches.xml"/> |
1163 |
</chapter> |
1164 |
|
1165 |
<chapter> |
1166 |
<title>Additional Portage Tools</title> |
1167 |
<abstract> |
1168 |
Portage comes with a few extra tools that might make your Gentoo experience even |
1169 |
better. Read on to discover how to use dispatch-conf and other tools. |
1170 |
</abstract> |
1171 |
<include href="../hb-portage-tools.xml"/> |
1172 |
</chapter> |
1173 |
|
1174 |
<chapter> |
1175 |
<title>Diverting from the Official Tree</title> |
1176 |
<abstract> |
1177 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
1178 |
your own Portage tree, how to synchronise only the categories you want, inject |
1179 |
packages and more. |
1180 |
</abstract> |
1181 |
<include href="../hb-portage-diverttree.xml"/> |
1182 |
</chapter> |
1183 |
</part> |
1184 |
|
1185 |
<part> |
1186 |
<title>Gentoo Network Configuration</title> |
1187 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
1188 |
|
1189 |
<chapter> |
1190 |
<title>Getting Started</title> |
1191 |
<abstract> |
1192 |
A guide to quickly get your network interface up and running in most common |
1193 |
environments. |
1194 |
</abstract> |
1195 |
<include href="../hb-net-start.xml"/> |
1196 |
</chapter> |
1197 |
|
1198 |
<chapter> |
1199 |
<title>Advanced Configuration</title> |
1200 |
<abstract> |
1201 |
Here we learn about how the configuration works - you need to know this |
1202 |
before we learn about modular networking. |
1203 |
</abstract> |
1204 |
<include href="../hb-net-advanced.xml"/> |
1205 |
</chapter> |
1206 |
|
1207 |
<chapter> |
1208 |
<title>Modular Networking</title> |
1209 |
<abstract> |
1210 |
Gentoo provides you flexible networking - here you are told about choosing |
1211 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
1212 |
</abstract> |
1213 |
<include href="../hb-net-modules.xml"/> |
1214 |
</chapter> |
1215 |
|
1216 |
<chapter> |
1217 |
<title>Wireless Networking</title> |
1218 |
<abstract> |
1219 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
1220 |
</abstract> |
1221 |
<include href="../hb-net-wireless.xml"/> |
1222 |
</chapter> |
1223 |
|
1224 |
<chapter> |
1225 |
<title>Adding Functionality</title> |
1226 |
<abstract> |
1227 |
If you're feeling adventurous, you can add your own functions to networking. |
1228 |
</abstract> |
1229 |
<include href="../hb-net-functions.xml"/> |
1230 |
</chapter> |
1231 |
|
1232 |
<chapter> |
1233 |
<title>Network Management</title> |
1234 |
<abstract> |
1235 |
For laptop users or people who move their computer around different networks. |
1236 |
</abstract> |
1237 |
<include href="../hb-net-management.xml"/> |
1238 |
</chapter> |
1239 |
</part> |
1240 |
|
1241 |
</book> |
1242 |
|
1243 |
|
1244 |
|
1245 |
1.1 xml/htdocs/doc/en/handbook/2007.0/handbook-ppc64.xml |
1246 |
|
1247 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-ppc64.xml?rev=1.1&view=markup |
1248 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-ppc64.xml?rev=1.1&content-type=text/plain |
1249 |
|
1250 |
Index: handbook-ppc64.xml |
1251 |
=================================================================== |
1252 |
<?xml version='1.0' encoding='UTF-8'?> |
1253 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
1254 |
|
1255 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-ppc64.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
1256 |
|
1257 |
<book link="/doc/en/handbook/2006.1/handbook-ppc64.xml"> |
1258 |
<title>Gentoo Linux 2006.1 PPC64 Handbook</title> |
1259 |
|
1260 |
<author title="Author"> |
1261 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
1262 |
</author> |
1263 |
<author title="Author"> |
1264 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
1265 |
</author> |
1266 |
<author title="Author"> |
1267 |
<mail link="uberlord@g.o">Roy Marples</mail> |
1268 |
</author> |
1269 |
<author title="Author"> |
1270 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
1271 |
</author> |
1272 |
<author title="Author"> |
1273 |
<mail link="chouser@g.o">Chris Houser</mail> |
1274 |
</author> |
1275 |
<author title="Author"> |
1276 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
1277 |
</author> |
1278 |
<author title="Gentoo x86 Developer"> |
1279 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
1280 |
</author> |
1281 |
<author title="Gentoo Alpha Developer"> |
1282 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
1283 |
</author><!-- Does not want to be listed on the rendered page |
1284 |
<author title="Gentoo Developer"> |
1285 |
Aron Griffis |
1286 |
</author> |
1287 |
--> |
1288 |
<author title="Gentoo AMD64 Developer"> |
1289 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
1290 |
</author> |
1291 |
<author title="Gentoo HPPA developer"> |
1292 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
1293 |
</author> |
1294 |
<author title="Gentoo PPC developer"> |
1295 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
1296 |
</author> |
1297 |
<author title="Gentoo SPARC developer"> |
1298 |
<mail link="blademan@g.o">Joe Kallar</mail> |
1299 |
</author> |
1300 |
<author title="Editor"> |
1301 |
<mail link="zhen@g.o">John P. Davis</mail> |
1302 |
</author> |
1303 |
<author title="Editor">Pierre-Henri Jondot</author> |
1304 |
<author title="Editor"> |
1305 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
1306 |
</author> |
1307 |
<author title="Editor"> |
1308 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
1309 |
</author> |
1310 |
<author title="Editor"> |
1311 |
<mail link="seo@g.o">Jungmin Seo</mail> |
1312 |
</author> |
1313 |
<author title="Editor"> |
1314 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
1315 |
</author> |
1316 |
<author title="Editor"> |
1317 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
1318 |
</author> |
1319 |
<author title="Editor"> |
1320 |
<mail link="peitolm@g.o">Colin Morey</mail> |
1321 |
</author> |
1322 |
<author title="Editor"> |
1323 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
1324 |
</author> |
1325 |
<author title="Editor"> |
1326 |
<mail link="carl@g.o">Carl Anderson</mail> |
1327 |
</author> |
1328 |
<author title="Editor"> |
1329 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
1330 |
</author> |
1331 |
<author title="Editor"> |
1332 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
1333 |
</author> |
1334 |
<author title="Editor"> |
1335 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
1336 |
</author> |
1337 |
<author title="Editor"> |
1338 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
1339 |
</author> |
1340 |
<author title="Editor"> |
1341 |
<mail link="erwin@g.o">Erwin</mail> |
1342 |
</author> |
1343 |
<author title="Editor"> |
1344 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
1345 |
</author> |
1346 |
<author title="Editor"> |
1347 |
<mail link="neysx@g.o">Xavier Neys</mail> |
1348 |
</author> |
1349 |
<author title="Reviewer"> |
1350 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
1351 |
</author> |
1352 |
<author title="Reviewer"> |
1353 |
<mail link="dberkholz@g.o">Donnie Berkholz</mail> |
1354 |
</author> |
1355 |
<author title="Reviewer"> |
1356 |
<mail link="antifa@g.o">Ken Nowack</mail> |
1357 |
</author> |
1358 |
<author title="Contributor"> |
1359 |
<mail link="pylon@g.o">Lars Weiler</mail> |
1360 |
</author> |
1361 |
<author title="Editor"> |
1362 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
1363 |
</author> |
1364 |
|
1365 |
<abstract> |
1366 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
1367 |
This handbook contains the installation instructions for a networkless |
1368 |
installation on PPC64 systems and parts about working with Gentoo and Portage. |
1369 |
</abstract> |
1370 |
|
1371 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
1372 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
1373 |
<license/> |
1374 |
|
1375 |
<version>7.1</version> |
1376 |
<date>2006-08-30</date> |
1377 |
|
1378 |
<part> |
1379 |
<title>Installing Gentoo</title> |
1380 |
<abstract> |
1381 |
In this part you learn how to install Gentoo on your system. |
1382 |
</abstract> |
1383 |
|
1384 |
<chapter> |
1385 |
<title>About the Gentoo Linux Installation</title> |
1386 |
<abstract> |
1387 |
Users not familiar with Gentoo do not always know that choice is what |
1388 |
Gentoo is all about. |
1389 |
</abstract> |
1390 |
<include href="hb-install-about.xml"/> |
1391 |
</chapter> |
1392 |
|
1393 |
<chapter> |
1394 |
<title>Booting the Universal Installation CD</title> |
1395 |
<abstract> |
1396 |
Using our Universal Installation CD you can boot up your system into a running |
1397 |
environment that allows you to install Gentoo. |
1398 |
</abstract> |
1399 |
<include href="hb-install-ppc64-medium.xml"/> |
1400 |
</chapter> |
1401 |
|
1402 |
<chapter> |
1403 |
<title>Configuring your Network</title> |
1404 |
<abstract> |
1405 |
If you need networking, this is the place where the network (and Internet |
1406 |
connection) is configured. |
1407 |
</abstract> |
1408 |
<include href="hb-install-network.xml"/> |
1409 |
</chapter> |
1410 |
|
1411 |
<chapter> |
1412 |
<title>Preparing the Disks</title> |
1413 |
<abstract> |
1414 |
To be able to install Gentoo, you must create the necessary partitions. |
1415 |
This chapter describes how to partition a disk for future usage. |
1416 |
</abstract> |
1417 |
<include href="hb-install-ppc64-disk.xml"/> |
1418 |
</chapter> |
1419 |
|
1420 |
<chapter> |
1421 |
<title>Installing the Gentoo Installation Files</title> |
1422 |
<abstract> |
1423 |
In this chapter we describe how you extract a stage3 file and how to configure |
1424 |
Portage. |
1425 |
</abstract> |
1426 |
<include href="hb-install-stage.xml"/> |
1427 |
</chapter> |
1428 |
|
1429 |
<chapter> |
1430 |
<title>Chrooting into the Gentoo Base System</title> |
1431 |
<abstract> |
1432 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
1433 |
the USE variable. |
1434 |
</abstract> |
1435 |
<include href="hb-install-system.xml"/> |
1436 |
</chapter> |
1437 |
|
1438 |
<chapter> |
1439 |
<title>Configuring the Kernel</title> |
1440 |
<abstract> |
1441 |
The Linux kernel is the core of every distribution. This chapter |
1442 |
explains how to configure your kernel. |
1443 |
</abstract> |
1444 |
<include href="hb-install-ppc64-kernel.xml"/> |
1445 |
</chapter> |
1446 |
|
1447 |
<chapter> |
1448 |
<title>Configuring your System</title> |
1449 |
<abstract> |
1450 |
You need to edit some important configuration files. In this chapter |
1451 |
you receive an overview of these files and an explanation on how to |
1452 |
proceed. |
1453 |
</abstract> |
1454 |
<include href="hb-install-config.xml"/> |
1455 |
</chapter> |
1456 |
|
1457 |
<chapter> |
1458 |
<title>Installing Necessary System Tools</title> |
1459 |
<abstract> |
1460 |
As mentioned before, Gentoo is about customization. In this chapter we help you |
1461 |
choose and install some important tools. |
1462 |
</abstract> |
1463 |
<include href="hb-install-tools.xml"/> |
1464 |
</chapter> |
1465 |
|
1466 |
<chapter> |
1467 |
<title>Configuring the Bootloader</title> |
1468 |
<abstract> |
1469 |
Several bootloaders exist. Each one of them has its own way of |
1470 |
configuration. In this chapter we'll describe all possibilities for you |
1471 |
and step you through the process of configuring a bootloader to your |
1472 |
needs. |
1473 |
</abstract> |
1474 |
<include href="hb-install-ppc64-bootloader.xml"/> |
1475 |
</chapter> |
1476 |
|
1477 |
|
1478 |
<chapter> |
1479 |
<title>Finalizing your Gentoo Installation</title> |
1480 |
<abstract> |
1481 |
You're almost done. We'll just create one (or more) users for your |
1482 |
system and (optionally) install prebuilt packages. |
1483 |
</abstract> |
1484 |
<include href="hb-install-finalise.xml"/> |
1485 |
</chapter> |
1486 |
|
1487 |
<chapter> |
1488 |
<title>Where to go from here?</title> |
1489 |
<abstract> |
1490 |
Now you have your Gentoo system, but what's next? |
1491 |
</abstract> |
1492 |
<include href="hb-install-next.xml"/> |
1493 |
</chapter> |
1494 |
</part> |
1495 |
|
1496 |
<part> |
1497 |
<title>Working with Gentoo</title> |
1498 |
<abstract> |
1499 |
Learn how to work with Gentoo: installing software, altering variables, changing |
1500 |
Portage behaviour etc. |
1501 |
</abstract> |
1502 |
|
1503 |
<chapter> |
1504 |
<title>A Portage Introduction</title> |
1505 |
<abstract> |
1506 |
This chapter explains the "simple" steps a user definitely needs to know to |
1507 |
maintain the software on his system. |
1508 |
</abstract> |
1509 |
<include href="../hb-working-portage.xml"/> |
1510 |
</chapter> |
1511 |
|
1512 |
<chapter> |
1513 |
<title>USE flags</title> |
1514 |
<abstract> |
1515 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
1516 |
work with USE-flags and understand how USE-flags interact with your system. |
1517 |
</abstract> |
1518 |
<include href="../hb-working-use.xml"/> |
1519 |
</chapter> |
1520 |
|
1521 |
<chapter> |
1522 |
<title>Portage Features</title> |
1523 |
<abstract> |
1524 |
Discover the features Portage has, such as support for distributed compiling, |
1525 |
ccache and more. |
1526 |
</abstract> |
1527 |
<include href="../hb-working-features.xml"/> |
1528 |
</chapter> |
1529 |
|
1530 |
<chapter> |
1531 |
<title>Initscripts</title> |
1532 |
<abstract> |
1533 |
Gentoo uses a special initscript format which, amongst other features, allows |
1534 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
1535 |
these aspects and explains how to deal with these scripts. |
1536 |
</abstract> |
1537 |
<include href="../hb-working-rcscripts.xml"/> |
1538 |
</chapter> |
1539 |
|
1540 |
<chapter> |
1541 |
<title>Environment Variables</title> |
1542 |
<abstract> |
1543 |
With Gentoo you can easily manage the environment variables for your system. |
1544 |
This chapter explains how you do that, and also describes frequently used |
1545 |
variables. |
1546 |
</abstract> |
1547 |
<include href="../hb-working-variables.xml"/> |
1548 |
</chapter> |
1549 |
</part> |
1550 |
|
1551 |
<part> |
1552 |
<title>Working with Portage</title> |
1553 |
<abstract> |
1554 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
1555 |
Software Management Tool. |
1556 |
</abstract> |
1557 |
|
1558 |
<chapter> |
1559 |
<title>Files and Directories</title> |
1560 |
<abstract> |
1561 |
Once you want to know Portage in-depth you need to know where it stores its |
1562 |
files and data. |
1563 |
</abstract> |
1564 |
<include href="../hb-portage-files.xml"/> |
1565 |
</chapter> |
1566 |
|
1567 |
<chapter> |
1568 |
<title>Configuring through Variables</title> |
1569 |
<abstract> |
1570 |
Portage is completely configurable through various variables you can set in the |
1571 |
configuration file or as environment variable. |
1572 |
</abstract> |
1573 |
<include href="../hb-portage-configuration.xml"/> |
1574 |
</chapter> |
1575 |
|
1576 |
<chapter> |
1577 |
<title>Mixing Software Branches</title> |
1578 |
<abstract> |
1579 |
Gentoo provides software separated in several branches, depending on stability |
1580 |
and architectural support. "Mixing Software Branches" inform you how these |
1581 |
branches can be configured and how you can override this separation |
1582 |
individually. |
1583 |
</abstract> |
1584 |
<include href="../hb-portage-branches.xml"/> |
1585 |
</chapter> |
1586 |
|
1587 |
<chapter> |
1588 |
<title>Additional Portage Tools</title> |
1589 |
<abstract> |
1590 |
Portage comes with a few extra tools that might make your Gentoo experience even |
1591 |
better. Read on to discover how to use dispatch-conf and other tools. |
1592 |
</abstract> |
1593 |
<include href="../hb-portage-tools.xml"/> |
1594 |
</chapter> |
1595 |
|
1596 |
<chapter> |
1597 |
<title>Diverting from the Official Tree</title> |
1598 |
<abstract> |
1599 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
1600 |
your own Portage tree, how to synchronise only the categories you want, inject |
1601 |
packages and more. |
1602 |
</abstract> |
1603 |
<include href="../hb-portage-diverttree.xml"/> |
1604 |
</chapter> |
1605 |
</part> |
1606 |
|
1607 |
<part> |
1608 |
<title>Gentoo Network Configuration</title> |
1609 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
1610 |
|
1611 |
<chapter> |
1612 |
<title>Getting Started</title> |
1613 |
<abstract> |
1614 |
A guide to quickly get your network interface up and running in most common |
1615 |
environments. |
1616 |
</abstract> |
1617 |
<include href="../hb-net-start.xml"/> |
1618 |
</chapter> |
1619 |
|
1620 |
<chapter> |
1621 |
<title>Advanced Configuration</title> |
1622 |
<abstract> |
1623 |
Here we learn about how the configuration works - you need to know this |
1624 |
before we learn about modular networking. |
1625 |
</abstract> |
1626 |
<include href="../hb-net-advanced.xml"/> |
1627 |
</chapter> |
1628 |
|
1629 |
<chapter> |
1630 |
<title>Modular Networking</title> |
1631 |
<abstract> |
1632 |
Gentoo provides you flexible networking - here you are told about choosing |
1633 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
1634 |
</abstract> |
1635 |
<include href="../hb-net-modules.xml"/> |
1636 |
</chapter> |
1637 |
|
1638 |
<chapter> |
1639 |
<title>Wireless Networking</title> |
1640 |
<abstract> |
1641 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
1642 |
</abstract> |
1643 |
<include href="../hb-net-wireless.xml"/> |
1644 |
</chapter> |
1645 |
|
1646 |
<chapter> |
1647 |
<title>Adding Functionality</title> |
1648 |
<abstract> |
1649 |
If you're feeling adventurous, you can add your own functions to networking. |
1650 |
</abstract> |
1651 |
<include href="../hb-net-functions.xml"/> |
1652 |
</chapter> |
1653 |
|
1654 |
<chapter> |
1655 |
<title>Network Management</title> |
1656 |
<abstract> |
1657 |
For laptop users or people who move their computer around different networks. |
1658 |
</abstract> |
1659 |
<include href="../hb-net-management.xml"/> |
1660 |
</chapter> |
1661 |
</part> |
1662 |
|
1663 |
</book> |
1664 |
|
1665 |
|
1666 |
|
1667 |
1.1 xml/htdocs/doc/en/handbook/2007.0/handbook-ppc.xml |
1668 |
|
1669 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-ppc.xml?rev=1.1&view=markup |
1670 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-ppc.xml?rev=1.1&content-type=text/plain |
1671 |
|
1672 |
Index: handbook-ppc.xml |
1673 |
=================================================================== |
1674 |
<?xml version='1.0' encoding='UTF-8'?> |
1675 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
1676 |
|
1677 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-ppc.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
1678 |
|
1679 |
<book link="/doc/en/handbook/2006.1/handbook-ppc.xml"> |
1680 |
<title>Gentoo Linux 2006.1 PPC Handbook</title> |
1681 |
|
1682 |
<author title="Author"> |
1683 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
1684 |
</author> |
1685 |
<author title="Author"> |
1686 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
1687 |
</author> |
1688 |
<author title="Author"> |
1689 |
<mail link="uberlord@g.o">Roy Marples</mail> |
1690 |
</author> |
1691 |
<author title="Author"> |
1692 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
1693 |
</author> |
1694 |
<author title="Author"> |
1695 |
<mail link="chouser@g.o">Chris Houser</mail> |
1696 |
</author> |
1697 |
<author title="Author"> |
1698 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
1699 |
</author> |
1700 |
<author title="Gentoo x86 Developer"> |
1701 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
1702 |
</author> |
1703 |
<author title="Gentoo Alpha Developer"> |
1704 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
1705 |
</author><!-- Does not want to be listed on the rendered page |
1706 |
<author title="Gentoo Developer"> |
1707 |
Aron Griffis |
1708 |
</author> |
1709 |
--> |
1710 |
<author title="Gentoo AMD64 Developer"> |
1711 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
1712 |
</author> |
1713 |
<author title="Gentoo HPPA developer"> |
1714 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
1715 |
</author> |
1716 |
<author title="Gentoo PPC developer"> |
1717 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
1718 |
</author> |
1719 |
<author title="Gentoo SPARC developer"> |
1720 |
<mail link="blademan@g.o">Joe Kallar</mail> |
1721 |
</author> |
1722 |
<author title="Editor"> |
1723 |
<mail link="zhen@g.o">John P. Davis</mail> |
1724 |
</author> |
1725 |
<author title="Editor">Pierre-Henri Jondot</author> |
1726 |
<author title="Editor"> |
1727 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
1728 |
</author> |
1729 |
<author title="Editor"> |
1730 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
1731 |
</author> |
1732 |
<author title="Editor"> |
1733 |
<mail link="seo@g.o">Jungmin Seo</mail> |
1734 |
</author> |
1735 |
<author title="Editor"> |
1736 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
1737 |
</author> |
1738 |
<author title="Editor"> |
1739 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
1740 |
</author> |
1741 |
<author title="Editor"> |
1742 |
<mail link="peitolm@g.o">Colin Morey</mail> |
1743 |
</author> |
1744 |
<author title="Editor"> |
1745 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
1746 |
</author> |
1747 |
<author title="Editor"> |
1748 |
<mail link="carl@g.o">Carl Anderson</mail> |
1749 |
</author> |
1750 |
<author title="Editor"> |
1751 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
1752 |
</author> |
1753 |
<author title="Editor"> |
1754 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
1755 |
</author> |
1756 |
<author title="Editor"> |
1757 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
1758 |
</author> |
1759 |
<author title="Editor"> |
1760 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
1761 |
</author> |
1762 |
<author title="Editor"> |
1763 |
<mail link="erwin@g.o">Erwin</mail> |
1764 |
</author> |
1765 |
<author title="Editor"> |
1766 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
1767 |
</author> |
1768 |
<author title="Editor"> |
1769 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
1770 |
</author> |
1771 |
<author title="Editor"> |
1772 |
<mail link="pylon@g.o">Lars Weiler</mail> |
1773 |
</author> |
1774 |
<author title="Editor"> |
1775 |
<mail link="sejo@g.o">Jochen Maes </mail> |
1776 |
</author> |
1777 |
<author title="Editor"> |
1778 |
<mail link="neysx@g.o">Xavier Neys</mail> |
1779 |
</author> |
1780 |
<author title="Editor"> |
1781 |
<mail link="josejx@g.o">Joseph Jezak</mail> |
1782 |
</author> |
1783 |
<author title="Reviewer"> |
1784 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
1785 |
</author> |
1786 |
<author title="Reviewer"> |
1787 |
<mail link="dberkholz@g.o">Donnie Berkholz</mail> |
1788 |
</author> |
1789 |
<author title="Reviewer"> |
1790 |
<mail link="antifa@g.o">Ken Nowack</mail> |
1791 |
</author> |
1792 |
|
1793 |
<abstract> |
1794 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
1795 |
This handbook contains the installation instructions for a networkless |
1796 |
installation on PPC systems and parts about working with Gentoo and Portage. |
1797 |
</abstract> |
1798 |
|
1799 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
1800 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
1801 |
<license/> |
1802 |
|
1803 |
<version>7.1</version> |
1804 |
<date>2006-08-30</date> |
1805 |
|
1806 |
<part> |
1807 |
<title>Installing Gentoo</title> |
1808 |
<abstract> |
1809 |
In this part you learn how to install Gentoo on your system. |
1810 |
</abstract> |
1811 |
|
1812 |
<chapter> |
1813 |
<title>About the Gentoo Linux Installation</title> |
1814 |
<abstract> |
1815 |
Users not familiar with Gentoo do not always know that choice is what |
1816 |
Gentoo is all about. |
1817 |
</abstract> |
1818 |
<include href="hb-install-about.xml"/> |
1819 |
</chapter> |
1820 |
|
1821 |
<chapter> |
1822 |
<title>Booting the Universal Installation CD</title> |
1823 |
<abstract> |
1824 |
Using our Universal Installation CD you can boot up your system into a running |
1825 |
environment that allows you to install Gentoo. |
1826 |
</abstract> |
1827 |
<include href="hb-install-ppc-medium.xml"/> |
1828 |
</chapter> |
1829 |
|
1830 |
<chapter> |
1831 |
<title>Configuring your Network</title> |
1832 |
<abstract> |
1833 |
If you need networking, this is the place where the network (and Internet |
1834 |
connection) is configured. |
1835 |
</abstract> |
1836 |
<include href="hb-install-network.xml"/> |
1837 |
</chapter> |
1838 |
|
1839 |
<chapter> |
1840 |
<title>Preparing the Disks</title> |
1841 |
<abstract> |
1842 |
To be able to install Gentoo, you must create the necessary partitions. |
1843 |
This chapter describes how to partition a disk for future usage. |
1844 |
</abstract> |
1845 |
<include href="hb-install-ppc-disk.xml"/> |
1846 |
</chapter> |
1847 |
|
1848 |
<chapter> |
1849 |
<title>Installing the Gentoo Installation Files</title> |
1850 |
<abstract> |
1851 |
In this chapter we describe how you extract a stage3 file and how to configure |
1852 |
Portage. |
1853 |
</abstract> |
1854 |
<include href="hb-install-stage.xml"/> |
1855 |
</chapter> |
1856 |
|
1857 |
<chapter> |
1858 |
<title>Chrooting into the Gentoo Base System</title> |
1859 |
<abstract> |
1860 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
1861 |
the USE variable. |
1862 |
</abstract> |
1863 |
<include href="hb-install-system.xml"/> |
1864 |
</chapter> |
1865 |
|
1866 |
<chapter> |
1867 |
<title>Configuring the Kernel</title> |
1868 |
<abstract> |
1869 |
The Linux kernel is the core of every distribution. This chapter |
1870 |
explains how to configure your kernel. |
1871 |
</abstract> |
1872 |
<include href="hb-install-ppc-kernel.xml"/> |
1873 |
</chapter> |
1874 |
|
1875 |
<chapter> |
1876 |
<title>Configuring your System</title> |
1877 |
<abstract> |
1878 |
You need to edit some important configuration files. In this chapter |
1879 |
you receive an overview of these files and an explanation on how to |
1880 |
proceed. |
1881 |
</abstract> |
1882 |
<include href="hb-install-config.xml"/> |
1883 |
</chapter> |
1884 |
|
1885 |
<chapter> |
1886 |
<title>Installing Necessary System Tools</title> |
1887 |
<abstract> |
1888 |
As mentioned before, Gentoo is about customization. In this chapter we help you |
1889 |
choose and install some important tools. |
1890 |
</abstract> |
1891 |
<include href="hb-install-tools.xml"/> |
1892 |
</chapter> |
1893 |
|
1894 |
<chapter> |
1895 |
<title>Configuring the Bootloader</title> |
1896 |
<abstract> |
1897 |
Several bootloaders exist. Each one of them has its own way of |
1898 |
configuration. In this chapter we'll describe all possibilities for you |
1899 |
and step you through the process of configuring a bootloader to your |
1900 |
needs. |
1901 |
</abstract> |
1902 |
<include href="hb-install-ppc-bootloader.xml"/> |
1903 |
</chapter> |
1904 |
|
1905 |
<chapter> |
1906 |
<title>Finalizing your Gentoo Installation</title> |
1907 |
<abstract> |
1908 |
You're almost done. We'll just create one (or more) users for your |
1909 |
system and (optionally) install prebuilt packages. |
1910 |
</abstract> |
1911 |
<include href="hb-install-finalise.xml"/> |
1912 |
</chapter> |
1913 |
|
1914 |
<chapter> |
1915 |
<title>Where to go from here?</title> |
1916 |
<abstract> |
1917 |
Now you have your Gentoo system, but what's next? |
1918 |
</abstract> |
1919 |
<include href="hb-install-next.xml"/> |
1920 |
</chapter> |
1921 |
</part> |
1922 |
|
1923 |
<part> |
1924 |
<title>Working with Gentoo</title> |
1925 |
<abstract> |
1926 |
Learn how to work with Gentoo: installing software, altering variables, changing |
1927 |
Portage behaviour etc. |
1928 |
</abstract> |
1929 |
|
1930 |
<chapter> |
1931 |
<title>A Portage Introduction</title> |
1932 |
<abstract> |
1933 |
This chapter explains the "simple" steps a user definitely needs to know to |
1934 |
maintain the software on his system. |
1935 |
</abstract> |
1936 |
<include href="../hb-working-portage.xml"/> |
1937 |
</chapter> |
1938 |
|
1939 |
<chapter> |
1940 |
<title>USE flags</title> |
1941 |
<abstract> |
1942 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
1943 |
work with USE-flags and understand how USE-flags interact with your system. |
1944 |
</abstract> |
1945 |
<include href="../hb-working-use.xml"/> |
1946 |
</chapter> |
1947 |
|
1948 |
<chapter> |
1949 |
<title>Portage Features</title> |
1950 |
<abstract> |
1951 |
Discover the features Portage has, such as support for distributed compiling, |
1952 |
ccache and more. |
1953 |
</abstract> |
1954 |
<include href="../hb-working-features.xml"/> |
1955 |
</chapter> |
1956 |
|
1957 |
<chapter> |
1958 |
<title>Initscripts</title> |
1959 |
<abstract> |
1960 |
Gentoo uses a special initscript format which, amongst other features, allows |
1961 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
1962 |
these aspects and explains how to deal with these scripts. |
1963 |
</abstract> |
1964 |
<include href="../hb-working-rcscripts.xml"/> |
1965 |
</chapter> |
1966 |
|
1967 |
<chapter> |
1968 |
<title>Environment Variables</title> |
1969 |
<abstract> |
1970 |
With Gentoo you can easily manage the environment variables for your system. |
1971 |
This chapter explains how you do that, and also describes frequently used |
1972 |
variables. |
1973 |
</abstract> |
1974 |
<include href="../hb-working-variables.xml"/> |
1975 |
</chapter> |
1976 |
</part> |
1977 |
|
1978 |
<part> |
1979 |
<title>Working with Portage</title> |
1980 |
<abstract> |
1981 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
1982 |
Software Management Tool. |
1983 |
</abstract> |
1984 |
|
1985 |
<chapter> |
1986 |
<title>Files and Directories</title> |
1987 |
<abstract> |
1988 |
Once you want to know Portage in-depth you need to know where it stores its |
1989 |
files and data. |
1990 |
</abstract> |
1991 |
<include href="../hb-portage-files.xml"/> |
1992 |
</chapter> |
1993 |
|
1994 |
<chapter> |
1995 |
<title>Configuring through Variables</title> |
1996 |
<abstract> |
1997 |
Portage is completely configurable through various variables you can set in the |
1998 |
configuration file or as environment variable. |
1999 |
</abstract> |
2000 |
<include href="../hb-portage-configuration.xml"/> |
2001 |
</chapter> |
2002 |
|
2003 |
<chapter> |
2004 |
<title>Mixing Software Branches</title> |
2005 |
<abstract> |
2006 |
Gentoo provides software separated in several branches, depending on stability |
2007 |
and architectural support. "Mixing Software Branches" inform you how these |
2008 |
branches can be configured and how you can override this separation |
2009 |
individually. |
2010 |
</abstract> |
2011 |
<include href="../hb-portage-branches.xml"/> |
2012 |
</chapter> |
2013 |
|
2014 |
<chapter> |
2015 |
<title>Additional Portage Tools</title> |
2016 |
<abstract> |
2017 |
Portage comes with a few extra tools that might make your Gentoo experience even |
2018 |
better. Read on to discover how to use dispatch-conf and other tools. |
2019 |
</abstract> |
2020 |
<include href="../hb-portage-tools.xml"/> |
2021 |
</chapter> |
2022 |
|
2023 |
<chapter> |
2024 |
<title>Diverting from the Official Tree</title> |
2025 |
<abstract> |
2026 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
2027 |
your own Portage tree, how to synchronise only the categories you want, inject |
2028 |
packages and more. |
2029 |
</abstract> |
2030 |
<include href="../hb-portage-diverttree.xml"/> |
2031 |
</chapter> |
2032 |
</part> |
2033 |
|
2034 |
<part> |
2035 |
<title>Gentoo Network Configuration</title> |
2036 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
2037 |
|
2038 |
<chapter> |
2039 |
<title>Getting Started</title> |
2040 |
<abstract> |
2041 |
A guide to quickly get your network interface up and running in most common |
2042 |
environments. |
2043 |
</abstract> |
2044 |
<include href="../hb-net-start.xml"/> |
2045 |
</chapter> |
2046 |
|
2047 |
<chapter> |
2048 |
<title>Advanced Configuration</title> |
2049 |
<abstract> |
2050 |
Here we learn about how the configuration works - you need to know this |
2051 |
before we learn about modular networking. |
2052 |
</abstract> |
2053 |
<include href="../hb-net-advanced.xml"/> |
2054 |
</chapter> |
2055 |
|
2056 |
<chapter> |
2057 |
<title>Modular Networking</title> |
2058 |
<abstract> |
2059 |
Gentoo provides you flexible networking - here you are told about choosing |
2060 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
2061 |
</abstract> |
2062 |
<include href="../hb-net-modules.xml"/> |
2063 |
</chapter> |
2064 |
|
2065 |
<chapter> |
2066 |
<title>Wireless Networking</title> |
2067 |
<abstract> |
2068 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
2069 |
</abstract> |
2070 |
<include href="../hb-net-wireless.xml"/> |
2071 |
</chapter> |
2072 |
|
2073 |
<chapter> |
2074 |
<title>Adding Functionality</title> |
2075 |
<abstract> |
2076 |
If you're feeling adventurous, you can add your own functions to networking. |
2077 |
</abstract> |
2078 |
<include href="../hb-net-functions.xml"/> |
2079 |
</chapter> |
2080 |
|
2081 |
<chapter> |
2082 |
<title>Network Management</title> |
2083 |
<abstract> |
2084 |
For laptop users or people who move their computer around different networks. |
2085 |
</abstract> |
2086 |
<include href="../hb-net-management.xml"/> |
2087 |
</chapter> |
2088 |
</part> |
2089 |
|
2090 |
</book> |
2091 |
|
2092 |
|
2093 |
|
2094 |
1.1 xml/htdocs/doc/en/handbook/2007.0/handbook-sparc.xml |
2095 |
|
2096 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-sparc.xml?rev=1.1&view=markup |
2097 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-sparc.xml?rev=1.1&content-type=text/plain |
2098 |
|
2099 |
Index: handbook-sparc.xml |
2100 |
=================================================================== |
2101 |
<?xml version='1.0' encoding='UTF-8'?> |
2102 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
2103 |
|
2104 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-sparc.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
2105 |
|
2106 |
<book link="/doc/en/handbook/2006.1/handbook-sparc.xml"> |
2107 |
<title>Gentoo Linux 2006.1 SPARC Handbook</title> |
2108 |
|
2109 |
<author title="Author"> |
2110 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
2111 |
</author> |
2112 |
<author title="Author"> |
2113 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
2114 |
</author> |
2115 |
<author title="Author"> |
2116 |
<mail link="uberlord@g.o">Roy Marples</mail> |
2117 |
</author> |
2118 |
<author title="Author"> |
2119 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
2120 |
</author> |
2121 |
<author title="Author"> |
2122 |
<mail link="chouser@g.o">Chris Houser</mail> |
2123 |
</author> |
2124 |
<author title="Author"> |
2125 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
2126 |
</author> |
2127 |
<author title="Gentoo x86 Developer"> |
2128 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
2129 |
</author> |
2130 |
<author title="Gentoo Alpha Developer"> |
2131 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
2132 |
</author><!-- Does not want to be listed on the rendered page |
2133 |
<author title="Gentoo Developer"> |
2134 |
Aron Griffis |
2135 |
</author> |
2136 |
--> |
2137 |
<author title="Gentoo AMD64 Developer"> |
2138 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
2139 |
</author> |
2140 |
<author title="Gentoo HPPA developer"> |
2141 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
2142 |
</author> |
2143 |
<author title="Gentoo PPC developer"> |
2144 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
2145 |
</author> |
2146 |
<author title="Gentoo SPARC developer"> |
2147 |
<mail link="blademan@g.o">Joe Kallar</mail> |
2148 |
</author> |
2149 |
<author title="Editor"> |
2150 |
<mail link="zhen@g.o">John P. Davis</mail> |
2151 |
</author> |
2152 |
<author title="Editor">Pierre-Henri Jondot</author> |
2153 |
<author title="Editor"> |
2154 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
2155 |
</author> |
2156 |
<author title="Editor"> |
2157 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
2158 |
</author> |
2159 |
<author title="Editor"> |
2160 |
<mail link="seo@g.o">Jungmin Seo</mail> |
2161 |
</author> |
2162 |
<author title="Editor"> |
2163 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
2164 |
</author> |
2165 |
<author title="Editor"> |
2166 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
2167 |
</author> |
2168 |
<author title="Editor"> |
2169 |
<mail link="peitolm@g.o">Colin Morey</mail> |
2170 |
</author> |
2171 |
<author title="Editor"> |
2172 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
2173 |
</author> |
2174 |
<author title="Editor"> |
2175 |
<mail link="carl@g.o">Carl Anderson</mail> |
2176 |
</author> |
2177 |
<author title="Editor"> |
2178 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
2179 |
</author> |
2180 |
<author title="Editor"> |
2181 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
2182 |
</author> |
2183 |
<author title="Editor"> |
2184 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
2185 |
</author> |
2186 |
<author title="Editor"> |
2187 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
2188 |
</author> |
2189 |
<author title="Editor"> |
2190 |
<mail link="erwin@g.o">Erwin</mail> |
2191 |
</author> |
2192 |
<author title="Editor"> |
2193 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
2194 |
</author> |
2195 |
<author title="Editor"> |
2196 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
2197 |
</author> |
2198 |
<author title="Editor"> |
2199 |
<mail link="neysx@g.o">Xavier Neys</mail> |
2200 |
</author> |
2201 |
<author title="Reviewer"> |
2202 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
2203 |
</author> |
2204 |
<author title="Reviewer"> |
2205 |
<mail link="dberkholz@g.o">Donnie Berkholz</mail> |
2206 |
</author> |
2207 |
<author title="Reviewer"> |
2208 |
<mail link="antifa@g.o">Ken Nowack</mail> |
2209 |
</author> |
2210 |
<author title="Contributor"> |
2211 |
<mail link="pylon@g.o">Lars Weiler</mail> |
2212 |
</author> |
2213 |
|
2214 |
<abstract> |
2215 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
2216 |
This handbook contains the installation instructions for a networkless |
2217 |
installation on Sparc systems and parts about working with Gentoo and Portage. |
2218 |
</abstract> |
2219 |
|
2220 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
2221 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
2222 |
<license/> |
2223 |
|
2224 |
<version>7.1</version> |
2225 |
<date>2006-08-30</date> |
2226 |
|
2227 |
<part> |
2228 |
<title>Installing Gentoo</title> |
2229 |
<abstract> |
2230 |
In this part you learn how to install Gentoo on your system. |
2231 |
</abstract> |
2232 |
|
2233 |
<chapter> |
2234 |
<title>About the Gentoo Linux Installation</title> |
2235 |
<abstract> |
2236 |
Users not familiar with Gentoo do not always know that choice is what |
2237 |
Gentoo is all about. |
2238 |
</abstract> |
2239 |
<include href="hb-install-about.xml"/> |
2240 |
</chapter> |
2241 |
|
2242 |
<chapter> |
2243 |
<title>Booting the Universal Installation CD</title> |
2244 |
<abstract> |
2245 |
Using our Universal Installation CD you can boot up your system into a running |
2246 |
environment that allows you to install Gentoo. |
2247 |
</abstract> |
2248 |
<include href="hb-install-sparc-medium.xml"/> |
2249 |
</chapter> |
2250 |
|
2251 |
<chapter> |
2252 |
<title>Configuring your Network</title> |
2253 |
<abstract> |
2254 |
If you need networking, this is the place where the network (and Internet |
2255 |
connection) is configured. |
2256 |
</abstract> |
2257 |
<include href="hb-install-network.xml"/> |
2258 |
</chapter> |
2259 |
|
2260 |
<chapter> |
2261 |
<title>Preparing the Disks</title> |
2262 |
<abstract> |
2263 |
To be able to install Gentoo, you must create the necessary partitions. |
2264 |
This chapter describes how to partition a disk for future usage. |
2265 |
</abstract> |
2266 |
<include href="hb-install-sparc-disk.xml"/> |
2267 |
</chapter> |
2268 |
|
2269 |
<chapter> |
2270 |
<title>Installing the Gentoo Installation Files</title> |
2271 |
<abstract> |
2272 |
In this chapter we describe how you extract a stage3 file and how to configure |
2273 |
Portage. |
2274 |
</abstract> |
2275 |
<include href="hb-install-stage.xml"/> |
2276 |
</chapter> |
2277 |
|
2278 |
<chapter> |
2279 |
<title>Chrooting into the Gentoo Base System</title> |
2280 |
<abstract> |
2281 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
2282 |
the USE variable. |
2283 |
</abstract> |
2284 |
<include href="hb-install-system.xml"/> |
2285 |
</chapter> |
2286 |
|
2287 |
<chapter> |
2288 |
<title>Configuring the Kernel</title> |
2289 |
<abstract> |
2290 |
The Linux kernel is the core of every distribution. This chapter |
2291 |
explains how to configure your kernel. |
2292 |
</abstract> |
2293 |
<include href="hb-install-sparc-kernel.xml"/> |
2294 |
</chapter> |
2295 |
|
2296 |
<chapter> |
2297 |
<title>Configuring your System</title> |
2298 |
<abstract> |
2299 |
You need to edit some important configuration files. In this chapter |
2300 |
you receive an overview of these files and an explanation on how to |
2301 |
proceed. |
2302 |
</abstract> |
2303 |
<include href="hb-install-config.xml"/> |
2304 |
</chapter> |
2305 |
|
2306 |
<chapter> |
2307 |
<title>Installing Necessary System Tools</title> |
2308 |
<abstract> |
2309 |
As mentioned before, Gentoo is about customization. In this chapter we help you |
2310 |
choose and install some important tools. |
2311 |
</abstract> |
2312 |
<include href="hb-install-tools.xml"/> |
2313 |
</chapter> |
2314 |
|
2315 |
<chapter> |
2316 |
<title>Configuring the Bootloader</title> |
2317 |
<abstract> |
2318 |
The SPARC architecture uses the SILO bootloader to fire up your Linux system. In |
2319 |
this chapter we step you through the process of configuring this bootloader to |
2320 |
your needs. |
2321 |
</abstract> |
2322 |
<include href="hb-install-sparc-bootloader.xml"/> |
2323 |
</chapter> |
2324 |
|
2325 |
<chapter> |
2326 |
<title>Finalizing your Gentoo Installation</title> |
2327 |
<abstract> |
2328 |
You're almost done. We'll just create one (or more) users for your |
2329 |
system and (optionally) install prebuilt packages. |
2330 |
</abstract> |
2331 |
<include href="hb-install-finalise.xml"/> |
2332 |
</chapter> |
2333 |
|
2334 |
<chapter> |
2335 |
<title>Where to go from here?</title> |
2336 |
<abstract> |
2337 |
Now you have your Gentoo system, but what's next? |
2338 |
</abstract> |
2339 |
<include href="hb-install-next.xml"/> |
2340 |
</chapter> |
2341 |
</part> |
2342 |
|
2343 |
<part> |
2344 |
<title>Working with Gentoo</title> |
2345 |
<abstract> |
2346 |
Learn how to work with Gentoo: installing software, altering variables, changing |
2347 |
Portage behaviour etc. |
2348 |
</abstract> |
2349 |
|
2350 |
<chapter> |
2351 |
<title>A Portage Introduction</title> |
2352 |
<abstract> |
2353 |
This chapter explains the "simple" steps a user definitely needs to know to |
2354 |
maintain the software on his system. |
2355 |
</abstract> |
2356 |
<include href="../hb-working-portage.xml"/> |
2357 |
</chapter> |
2358 |
|
2359 |
<chapter> |
2360 |
<title>USE flags</title> |
2361 |
<abstract> |
2362 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
2363 |
work with USE-flags and understand how USE-flags interact with your system. |
2364 |
</abstract> |
2365 |
<include href="../hb-working-use.xml"/> |
2366 |
</chapter> |
2367 |
|
2368 |
<chapter> |
2369 |
<title>Portage Features</title> |
2370 |
<abstract> |
2371 |
Discover the features Portage has, such as support for distributed compiling, |
2372 |
ccache and more. |
2373 |
</abstract> |
2374 |
<include href="../hb-working-features.xml"/> |
2375 |
</chapter> |
2376 |
|
2377 |
<chapter> |
2378 |
<title>Initscripts</title> |
2379 |
<abstract> |
2380 |
Gentoo uses a special initscript format which, amongst other features, allows |
2381 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
2382 |
these aspects and explains how to deal with these scripts. |
2383 |
</abstract> |
2384 |
<include href="../hb-working-rcscripts.xml"/> |
2385 |
</chapter> |
2386 |
|
2387 |
<chapter> |
2388 |
<title>Environment Variables</title> |
2389 |
<abstract> |
2390 |
With Gentoo you can easily manage the environment variables for your system. |
2391 |
This chapter explains how you do that, and also describes frequently used |
2392 |
variables. |
2393 |
</abstract> |
2394 |
<include href="../hb-working-variables.xml"/> |
2395 |
</chapter> |
2396 |
</part> |
2397 |
|
2398 |
<part> |
2399 |
<title>Working with Portage</title> |
2400 |
<abstract> |
2401 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
2402 |
Software Management Tool. |
2403 |
</abstract> |
2404 |
|
2405 |
<chapter> |
2406 |
<title>Files and Directories</title> |
2407 |
<abstract> |
2408 |
Once you want to know Portage in-depth you need to know where it stores its |
2409 |
files and data. |
2410 |
</abstract> |
2411 |
<include href="../hb-portage-files.xml"/> |
2412 |
</chapter> |
2413 |
|
2414 |
<chapter> |
2415 |
<title>Configuring through Variables</title> |
2416 |
<abstract> |
2417 |
Portage is completely configurable through various variables you can set in the |
2418 |
configuration file or as environment variable. |
2419 |
</abstract> |
2420 |
<include href="../hb-portage-configuration.xml"/> |
2421 |
</chapter> |
2422 |
|
2423 |
<chapter> |
2424 |
<title>Mixing Software Branches</title> |
2425 |
<abstract> |
2426 |
Gentoo provides software separated in several branches, depending on stability |
2427 |
and architectural support. "Mixing Software Branches" inform you how these |
2428 |
branches can be configured and how you can override this separation |
2429 |
individually. |
2430 |
</abstract> |
2431 |
<include href="../hb-portage-branches.xml"/> |
2432 |
</chapter> |
2433 |
|
2434 |
<chapter> |
2435 |
<title>Additional Portage Tools</title> |
2436 |
<abstract> |
2437 |
Portage comes with a few extra tools that might make your Gentoo experience even |
2438 |
better. Read on to discover how to use dispatch-conf and other tools. |
2439 |
</abstract> |
2440 |
<include href="../hb-portage-tools.xml"/> |
2441 |
</chapter> |
2442 |
|
2443 |
<chapter> |
2444 |
<title>Diverting from the Official Tree</title> |
2445 |
<abstract> |
2446 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
2447 |
your own Portage tree, how to synchronise only the categories you want, inject |
2448 |
packages and more. |
2449 |
</abstract> |
2450 |
<include href="../hb-portage-diverttree.xml"/> |
2451 |
</chapter> |
2452 |
</part> |
2453 |
|
2454 |
<part> |
2455 |
<title>Gentoo Network Configuration</title> |
2456 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
2457 |
|
2458 |
<chapter> |
2459 |
<title>Getting Started</title> |
2460 |
<abstract> |
2461 |
A guide to quickly get your network interface up and running in most common |
2462 |
environments. |
2463 |
</abstract> |
2464 |
<include href="../hb-net-start.xml"/> |
2465 |
</chapter> |
2466 |
|
2467 |
<chapter> |
2468 |
<title>Advanced Configuration</title> |
2469 |
<abstract> |
2470 |
Here we learn about how the configuration works - you need to know this |
2471 |
before we learn about modular networking. |
2472 |
</abstract> |
2473 |
<include href="../hb-net-advanced.xml"/> |
2474 |
</chapter> |
2475 |
|
2476 |
<chapter> |
2477 |
<title>Modular Networking</title> |
2478 |
<abstract> |
2479 |
Gentoo provides you flexible networking - here you are told about choosing |
2480 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
2481 |
</abstract> |
2482 |
<include href="../hb-net-modules.xml"/> |
2483 |
</chapter> |
2484 |
|
2485 |
<chapter> |
2486 |
<title>Wireless Networking</title> |
2487 |
<abstract> |
2488 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
2489 |
</abstract> |
2490 |
<include href="../hb-net-wireless.xml"/> |
2491 |
</chapter> |
2492 |
|
2493 |
<chapter> |
2494 |
<title>Adding Functionality</title> |
2495 |
<abstract> |
2496 |
If you're feeling adventurous, you can add your own functions to networking. |
2497 |
</abstract> |
2498 |
<include href="../hb-net-functions.xml"/> |
2499 |
</chapter> |
2500 |
|
2501 |
<chapter> |
2502 |
<title>Network Management</title> |
2503 |
<abstract> |
2504 |
For laptop users or people who move their computer around different networks. |
2505 |
</abstract> |
2506 |
<include href="../hb-net-management.xml"/> |
2507 |
</chapter> |
2508 |
</part> |
2509 |
|
2510 |
</book> |
2511 |
|
2512 |
|
2513 |
|
2514 |
1.1 xml/htdocs/doc/en/handbook/2007.0/handbook-x86.xml |
2515 |
|
2516 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-x86.xml?rev=1.1&view=markup |
2517 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-x86.xml?rev=1.1&content-type=text/plain |
2518 |
|
2519 |
Index: handbook-x86.xml |
2520 |
=================================================================== |
2521 |
<?xml version='1.0' encoding='UTF-8'?> |
2522 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
2523 |
|
2524 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/handbook-x86.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
2525 |
|
2526 |
<book link="/doc/en/handbook/2006.1/handbook-x86.xml"> |
2527 |
<title>Gentoo Linux 2006.1 x86 Handbook</title> |
2528 |
|
2529 |
<values> |
2530 |
<key id="arch">x86</key> |
2531 |
<key id="release-dir">releases/x86/2006.1/</key> |
2532 |
<key id="online-book">2006.1/handbook-x86.xml</key> |
2533 |
</values> |
2534 |
|
2535 |
<author title="Author"> |
2536 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
2537 |
</author> |
2538 |
<author title="Author"> |
2539 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
2540 |
</author> |
2541 |
<author title="Author"> |
2542 |
<mail link="uberlord@g.o">Roy Marples</mail> |
2543 |
</author> |
2544 |
<author title="Author"> |
2545 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
2546 |
</author> |
2547 |
<author title="Author"> |
2548 |
<mail link="chouser@g.o">Chris Houser</mail> |
2549 |
</author> |
2550 |
<author title="Author"> |
2551 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
2552 |
</author> |
2553 |
<author title="Author"> |
2554 |
<mail link="nightmorph@g.o">Joshua Saddler</mail> |
2555 |
</author> |
2556 |
<author title="Gentoo x86 Developer"> |
2557 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
2558 |
</author> |
2559 |
<author title="Gentoo Alpha Developer"> |
2560 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
2561 |
</author><!-- Does not want to be listed on the rendered page |
2562 |
<author title="Gentoo Developer"> |
2563 |
Aron Griffis |
2564 |
</author> |
2565 |
--> |
2566 |
<author title="Gentoo AMD64 Developer"> |
2567 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
2568 |
</author> |
2569 |
<author title="Gentoo HPPA developer"> |
2570 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
2571 |
</author> |
2572 |
<author title="Gentoo PPC developer"> |
2573 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
2574 |
</author> |
2575 |
<author title="Gentoo SPARC developer"> |
2576 |
<mail link="blademan@g.o">Joe Kallar</mail> |
2577 |
</author> |
2578 |
<author title="Editor"> |
2579 |
<mail link="zhen@g.o">John P. Davis</mail> |
2580 |
</author> |
2581 |
<author title="Editor">Pierre-Henri Jondot</author> |
2582 |
<author title="Editor"> |
2583 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
2584 |
</author> |
2585 |
<author title="Editor"> |
2586 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
2587 |
</author> |
2588 |
<author title="Editor"> |
2589 |
<mail link="seo@g.o">Jungmin Seo</mail> |
2590 |
</author> |
2591 |
<author title="Editor"> |
2592 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
2593 |
</author> |
2594 |
<author title="Editor"> |
2595 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
2596 |
</author> |
2597 |
<author title="Editor"> |
2598 |
<mail link="peitolm@g.o">Colin Morey</mail> |
2599 |
</author> |
2600 |
<author title="Editor"> |
2601 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
2602 |
</author> |
2603 |
<author title="Editor"> |
2604 |
<mail link="carl@g.o">Carl Anderson</mail> |
2605 |
</author> |
2606 |
<author title="Editor"> |
2607 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
2608 |
</author> |
2609 |
<author title="Editor"> |
2610 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
2611 |
</author> |
2612 |
<author title="Editor"> |
2613 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
2614 |
</author> |
2615 |
<author title="Editor"> |
2616 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
2617 |
</author> |
2618 |
<author title="Editor"> |
2619 |
<mail link="erwin@g.o">Erwin</mail> |
2620 |
</author> |
2621 |
<author title="Editor"> |
2622 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
2623 |
</author> |
2624 |
<author title="Editor"> |
2625 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
2626 |
</author> |
2627 |
<author title="Editor"> |
2628 |
<mail link="neysx@g.o">Xavier Neys</mail> |
2629 |
</author> |
2630 |
<author title="Editor"> |
2631 |
<mail link="fox2mike@g.o">Shyam Mani</mail> |
2632 |
</author> |
2633 |
<author title="Reviewer"> |
2634 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
2635 |
</author> |
2636 |
<author title="Reviewer"> |
2637 |
<mail link="dberkholz@g.o">Donnie Berkholz</mail> |
2638 |
</author> |
2639 |
<author title="Reviewer"> |
2640 |
<mail link="antifa@g.o">Ken Nowack</mail> |
2641 |
</author> |
2642 |
<author title="Contributor"> |
2643 |
<mail link="pylon@g.o">Lars Weiler</mail> |
2644 |
</author> |
2645 |
|
2646 |
<abstract> |
2647 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
2648 |
This handbook contains the installation instructions for a networkless |
2649 |
installation on x86 systems and parts about working with Gentoo and Portage. |
2650 |
</abstract> |
2651 |
|
2652 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
2653 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
2654 |
<license/> |
2655 |
|
2656 |
<version>7.1</version> |
2657 |
<date>2006-08-30</date> |
2658 |
|
2659 |
<part> |
2660 |
<title>Installing Gentoo</title> |
2661 |
<abstract> |
2662 |
In this part you learn how to install Gentoo on your system. |
2663 |
</abstract> |
2664 |
|
2665 |
<chapter> |
2666 |
<title>About the Gentoo Linux Installation</title> |
2667 |
<abstract> |
2668 |
Users not familiar with Gentoo do not always know that choice is what |
2669 |
Gentoo is all about. |
2670 |
</abstract> |
2671 |
<include href="hb-installer-about.xml"/> |
2672 |
</chapter> |
2673 |
|
2674 |
<chapter> |
2675 |
<title>Booting the Installer LiveCD</title> |
2676 |
<abstract> |
2677 |
Using our Installer LiveCD you can boot up your system into a running |
2678 |
environment that allows you to install Gentoo. |
2679 |
</abstract> |
2680 |
<include href="hb-install-gli-medium.xml"/> |
2681 |
</chapter> |
2682 |
|
2683 |
<chapter> |
2684 |
<title>Using the GTK+ based Gentoo Linux Installer</title> |
2685 |
<abstract> |
2686 |
You now have an option of using our graphical installer to install Gentoo. |
2687 |
Configure the options you need through an easy to use GUI and you're ready to |
2688 |
go. |
2689 |
</abstract> |
2690 |
<include href="hb-install-gtkfe.xml" /> |
2691 |
</chapter> |
2692 |
|
2693 |
<chapter> |
2694 |
<title>Using the Dialog based Gentoo Linux Installer</title> |
2695 |
<abstract> |
2696 |
You also have an option of using our text based installer to install Gentoo. |
2697 |
Configure the options you need through an easy to use set of menus and you're |
2698 |
ready to go. |
2699 |
</abstract> |
2700 |
<include href="hb-install-gli-dialog.xml" /> |
2701 |
</chapter> |
2702 |
|
2703 |
<chapter> |
2704 |
<title>Where to go from here?</title> |
2705 |
<abstract> |
2706 |
Now you have your Gentoo system, but what's next? |
2707 |
</abstract> |
2708 |
<include href="hb-install-next.xml"/> |
2709 |
</chapter> |
2710 |
</part> |
2711 |
|
2712 |
<part> |
2713 |
<title>Working with Gentoo</title> |
2714 |
<abstract> |
2715 |
Learn how to work with Gentoo: installing software, altering variables, |
2716 |
changing Portage behaviour etc. |
2717 |
</abstract> |
2718 |
|
2719 |
<chapter> |
2720 |
<title>A Portage Introduction</title> |
2721 |
<abstract> |
2722 |
This chapter explains the "simple" steps a user definitely needs to know to |
2723 |
maintain the software on his system. |
2724 |
</abstract> |
2725 |
<include href="../hb-working-portage.xml"/> |
2726 |
</chapter> |
2727 |
|
2728 |
<chapter> |
2729 |
<title>USE flags</title> |
2730 |
<abstract> |
2731 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
2732 |
work with USE-flags and understand how USE-flags interact with your system. |
2733 |
</abstract> |
2734 |
<include href="../hb-working-use.xml"/> |
2735 |
</chapter> |
2736 |
|
2737 |
<chapter> |
2738 |
<title>Portage Features</title> |
2739 |
<abstract> |
2740 |
Discover the features Portage has, such as support for distributed compiling, |
2741 |
ccache and more. |
2742 |
</abstract> |
2743 |
<include href="../hb-working-features.xml"/> |
2744 |
</chapter> |
2745 |
|
2746 |
<chapter> |
2747 |
<title>Initscripts</title> |
2748 |
<abstract> |
2749 |
Gentoo uses a special initscript format which, amongst other features, allows |
2750 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
2751 |
these aspects and explains how to deal with these scripts. |
2752 |
</abstract> |
2753 |
<include href="../hb-working-rcscripts.xml"/> |
2754 |
</chapter> |
2755 |
|
2756 |
<chapter> |
2757 |
<title>Environment Variables</title> |
2758 |
<abstract> |
2759 |
With Gentoo you can easily manage the environment variables for your system. |
2760 |
This chapter explains how you do that, and also describes frequently used |
2761 |
variables. |
2762 |
</abstract> |
2763 |
<include href="../hb-working-variables.xml"/> |
2764 |
</chapter> |
2765 |
</part> |
2766 |
|
2767 |
<part> |
2768 |
<title>Working with Portage</title> |
2769 |
<abstract> |
2770 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
2771 |
Software Management Tool. |
2772 |
</abstract> |
2773 |
|
2774 |
<chapter> |
2775 |
<title>Files and Directories</title> |
2776 |
<abstract> |
2777 |
Once you want to know Portage in-depth you need to know where it stores its |
2778 |
files and data. |
2779 |
</abstract> |
2780 |
<include href="../hb-portage-files.xml"/> |
2781 |
</chapter> |
2782 |
|
2783 |
<chapter> |
2784 |
<title>Configuring through Variables</title> |
2785 |
<abstract> |
2786 |
Portage is completely configurable through various variables you can set in the |
2787 |
configuration file or as environment variable. |
2788 |
</abstract> |
2789 |
<include href="../hb-portage-configuration.xml"/> |
2790 |
</chapter> |
2791 |
|
2792 |
<chapter> |
2793 |
<title>Mixing Software Branches</title> |
2794 |
<abstract> |
2795 |
Gentoo provides software separated in several branches, depending on stability |
2796 |
and architectural support. "Mixing Software Branches" inform you how these |
2797 |
branches can be configured and how you can override this separation |
2798 |
individually. |
2799 |
</abstract> |
2800 |
<include href="../hb-portage-branches.xml"/> |
2801 |
</chapter> |
2802 |
|
2803 |
<chapter> |
2804 |
<title>Additional Portage Tools</title> |
2805 |
<abstract> |
2806 |
Portage comes with a few extra tools that might make your Gentoo experience even |
2807 |
better. Read on to discover how to use dispatch-conf and other tools. |
2808 |
</abstract> |
2809 |
<include href="../hb-portage-tools.xml"/> |
2810 |
</chapter> |
2811 |
|
2812 |
<chapter> |
2813 |
<title>Diverting from the Official Tree</title> |
2814 |
<abstract> |
2815 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
2816 |
your own Portage tree, how to synchronise only the categories you want, inject |
2817 |
packages and more. |
2818 |
</abstract> |
2819 |
<include href="../hb-portage-diverttree.xml"/> |
2820 |
</chapter> |
2821 |
</part> |
2822 |
|
2823 |
<part> |
2824 |
<title>Gentoo Network Configuration</title> |
2825 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
2826 |
|
2827 |
<chapter> |
2828 |
<title>Getting Started</title> |
2829 |
<abstract> |
2830 |
A guide to quickly get your network interface up and running in most common |
2831 |
environments. |
2832 |
</abstract> |
2833 |
<include href="../hb-net-start.xml"/> |
2834 |
</chapter> |
2835 |
|
2836 |
<chapter> |
2837 |
<title>Advanced Configuration</title> |
2838 |
<abstract> |
2839 |
Here we learn about how the configuration works - you need to know this |
2840 |
before we learn about modular networking. |
2841 |
</abstract> |
2842 |
<include href="../hb-net-advanced.xml"/> |
2843 |
</chapter> |
2844 |
|
2845 |
<chapter> |
2846 |
<title>Modular Networking</title> |
2847 |
<abstract> |
2848 |
Gentoo provides you flexible networking - here you are told about choosing |
2849 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
2850 |
</abstract> |
2851 |
<include href="../hb-net-modules.xml"/> |
2852 |
</chapter> |
2853 |
|
2854 |
<chapter> |
2855 |
<title>Wireless Networking</title> |
2856 |
<abstract> |
2857 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
2858 |
</abstract> |
2859 |
<include href="../hb-net-wireless.xml"/> |
2860 |
</chapter> |
2861 |
|
2862 |
<chapter> |
2863 |
<title>Adding Functionality</title> |
2864 |
<abstract> |
2865 |
If you're feeling adventurous, you can add your own functions to networking. |
2866 |
</abstract> |
2867 |
<include href="../hb-net-functions.xml"/> |
2868 |
</chapter> |
2869 |
|
2870 |
<chapter> |
2871 |
<title>Network Management</title> |
2872 |
<abstract> |
2873 |
For laptop users or people who move their computer around different networks. |
2874 |
</abstract> |
2875 |
<include href="../hb-net-management.xml"/> |
2876 |
</chapter> |
2877 |
</part> |
2878 |
|
2879 |
</book> |
2880 |
|
2881 |
|
2882 |
|
2883 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-about.xml |
2884 |
|
2885 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-about.xml?rev=1.1&view=markup |
2886 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-about.xml?rev=1.1&content-type=text/plain |
2887 |
|
2888 |
Index: hb-install-about.xml |
2889 |
=================================================================== |
2890 |
<?xml version='1.0' encoding='UTF-8'?> |
2891 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
2892 |
|
2893 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
2894 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
2895 |
|
2896 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-about.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
2897 |
|
2898 |
<sections> |
2899 |
|
2900 |
<version>7.0</version> |
2901 |
<date>2006-08-30</date> |
2902 |
|
2903 |
<section> |
2904 |
<title>Introduction</title> |
2905 |
<subsection> |
2906 |
<title>Welcome!</title> |
2907 |
<body> |
2908 |
|
2909 |
<p> |
2910 |
First of all, <e>welcome</e> to Gentoo. You are about to enter the world |
2911 |
of customization and performance. When installing Gentoo, this is made clear to |
2912 |
you several times -- you can choose how much you want to compile yourself, how |
2913 |
to install Gentoo, what system logger you want, etc. |
2914 |
</p> |
2915 |
|
2916 |
<p> |
2917 |
Gentoo is a fast, modern meta-distribution with a clean and flexible |
2918 |
design. Gentoo is built around free software and doesn't hide from its |
2919 |
users what is beneath the hood. Portage, the package maintenance system |
2920 |
which Gentoo uses, is written in Python, meaning you can easily view and |
2921 |
modify the source code. Gentoo's packaging system uses source code |
2922 |
(although support for precompiled packages is included too) and |
2923 |
configuring Gentoo happens through regular text files. In other words, |
2924 |
openness everywhere. |
2925 |
</p> |
2926 |
|
2927 |
<p> |
2928 |
It is very important that you understand that <e>empowerment</e> is what makes |
2929 |
Gentoo run. We try not to force anything on our users and try our best to |
2930 |
empower you to make the choices you wish. If you feel a change should be made, |
2931 |
please file a <uri link="http://bugs.gentoo.org">bug report</uri> about it. |
2932 |
</p> |
2933 |
|
2934 |
</body> |
2935 |
</subsection> |
2936 |
<subsection> |
2937 |
<title>How is the Installation Structured?</title> |
2938 |
<body> |
2939 |
|
2940 |
<p> |
2941 |
The Gentoo Installation can be seen as a 10-step procedure, |
2942 |
corresponding to chapters 2 - 11. Every step results in |
2943 |
a certain state: |
2944 |
</p> |
2945 |
|
2946 |
<ul> |
2947 |
<li> |
2948 |
After step 1, you are in a working environment ready to install Gentoo |
2949 |
</li> |
2950 |
<li> |
2951 |
After step 2, your internet connection is prepared in case you need it (this |
2952 |
is however optional) |
2953 |
</li> |
2954 |
<li> |
2955 |
After step 3, your hard disks are initialized to house your Gentoo |
2956 |
installation |
2957 |
</li> |
2958 |
<li> |
2959 |
After step 4, your installation environment is prepared and you are |
2960 |
ready to chroot into the new environment |
2961 |
</li> |
2962 |
<li> |
2963 |
After step 5, core packages, which are the same on all Gentoo |
2964 |
installations, are installed |
2965 |
</li> |
2966 |
<li> |
2967 |
After step 6, you have compiled your Linux kernel |
2968 |
</li> |
2969 |
<li> |
2970 |
After step 7, you have written most of your Gentoo system |
2971 |
configuration files |
2972 |
</li> |
2973 |
<li> |
2974 |
After step 8, necessary system tools (which you can choose from a nice |
2975 |
list) are installed |
2976 |
</li> |
2977 |
<li> |
2978 |
After step 9, your choice of bootloader has been installed and |
2979 |
configured and you are logged in into your new Gentoo installation |
2980 |
</li> |
2981 |
<li> |
2982 |
After step 10, your Gentoo Linux environment is ready to be explored |
2983 |
</li> |
2984 |
</ul> |
2985 |
|
2986 |
<p> |
2987 |
When you are given a certain choice, we try our best to explain what the pros |
2988 |
and cons are. We will continue then with a default |
2989 |
choice, identified by "Default: " in the title. The other |
2990 |
possibilities are marked by "Alternative: ". Do <e>not</e> |
2991 |
think that the default is what we recommend. It is however what we |
2992 |
believe most users will use. |
2993 |
</p> |
2994 |
|
2995 |
<p> |
2996 |
Sometimes you can pursue an optional step. Such steps are marked as |
2997 |
"Optional: " and are therefore not needed to install Gentoo. |
2998 |
However, some optional steps are dependant on a previous decision you |
2999 |
made. We will inform you when this happens, both when you make the |
3000 |
decision, and right before the optional step is described. |
3001 |
</p> |
3002 |
|
3003 |
</body> |
3004 |
</subsection> |
3005 |
<subsection> |
3006 |
<title>What are my Options?</title> |
3007 |
<body> |
3008 |
|
3009 |
<p> |
3010 |
You can install Gentoo in many different ways. You can download and install from |
3011 |
one of our Installation CDs, from an existing distribution, |
3012 |
from a bootable CD (such as Knoppix), from a netbooted environment, from a |
3013 |
rescue floppy, etc. |
3014 |
</p> |
3015 |
|
3016 |
<p> |
3017 |
This document covers the installation using a Gentoo Linux Installation CD, a |
3018 |
bootable CD that contains everything you need to get Gentoo Linux up and |
3019 |
running. There are two types of Installation CDs, the InstallCD and the |
3020 |
Installer LiveCD. The InstallCD is a minimal environment which contains only |
3021 |
those packages necessary for installing Gentoo Linux. The LiveCD is a complete |
3022 |
Gentoo Linux environment and can be used for multiple tasks, one of which is |
3023 |
installing Gentoo Linux. The LiveCD is not available on all architectures at |
3024 |
this time. If your architecture does not have a LiveCD, then this document will |
3025 |
refer to the Universal InstallCD for you. |
3026 |
</p> |
3027 |
|
3028 |
<p> |
3029 |
This installation approach however does not immediately use the latest version |
3030 |
of the available packages; if you want this you should check out the |
3031 |
Installation Instructions inside our <uri |
3032 |
link="/doc/en/handbook/index.xml">Gentoo Linux Handbooks</uri>. |
3033 |
</p> |
3034 |
|
3035 |
<p> |
3036 |
For help on the other installation approaches, |
3037 |
please read our <uri link="/doc/en/altinstall.xml">Alternative Installation |
3038 |
Guide</uri>. We also provide a <uri |
3039 |
link="/doc/en/gentoo-x86-tipsntricks.xml">Gentoo Installation Tips & |
3040 |
Tricks</uri> document that might be useful to read as well. If you feel that |
3041 |
the current installation instructions are too elaborate, feel free to use our |
3042 |
Quick Installation Guide available from our <uri |
3043 |
link="/doc/en/index.xml">Documentation Resources</uri> if your architecture |
3044 |
has such a document available. |
3045 |
</p> |
3046 |
|
3047 |
</body> |
3048 |
</subsection> |
3049 |
<subsection> |
3050 |
<title>Troubles?</title> |
3051 |
<body> |
3052 |
|
3053 |
<p> |
3054 |
If you find a problem in the installation (or in the installation |
3055 |
documentation), please check the errata from our <uri |
3056 |
link="/proj/en/releng/">Gentoo Release Engineering Project</uri>, |
3057 |
visit our <uri link="http://bugs.gentoo.org">bug tracking |
3058 |
system</uri> and check if the bug is known. If not, please create a bug report |
3059 |
for it so we can take care of it. Do not be afraid of the developers who are |
3060 |
assigned to (your) bugs -- they generally don't eat people. |
3061 |
</p> |
3062 |
|
3063 |
<p> |
3064 |
Note though that, although the document you are now reading is |
3065 |
architecture-specific, it will contain references to other architectures as |
3066 |
well. This is due to the fact that large parts of the Gentoo Handbook use source |
3067 |
code that is common for all architectures (to avoid duplication of efforts and |
3068 |
starvation of development resources). We will try to keep this to a minimum |
3069 |
to avoid confusion. |
3070 |
</p> |
3071 |
|
3072 |
<p> |
3073 |
If you are uncertain if the problem is a user-problem (some error you |
3074 |
made despite having read the documentation carefully) or a |
3075 |
software-problem (some error we made despite having tested the |
3076 |
installation/documentation carefully) you are free to join #gentoo on |
3077 |
irc.freenode.net. Of course, you are welcome otherwise too :) |
3078 |
</p> |
3079 |
|
3080 |
<p> |
3081 |
If you have a question regarding Gentoo, check out our <uri |
3082 |
link="/doc/en/faq.xml">Frequently Asked |
3083 |
Questions</uri>, available from the <uri |
3084 |
link="/doc/en/">Gentoo Documentation</uri>. You can |
3085 |
also view the <uri |
3086 |
link="http://forums.gentoo.org/viewforum.php?f=40">FAQs</uri> on our |
3087 |
<uri link="http://forums.gentoo.org">forums</uri>. If you can't find the answer |
3088 |
there ask on #gentoo, our IRC-channel on irc.freenode.net. Yes, several of |
3089 |
us are freaks who sit on IRC :-) |
3090 |
</p> |
3091 |
|
3092 |
</body> |
3093 |
</subsection> |
3094 |
</section> |
3095 |
<section> |
3096 |
<title>Fast Installation using the Gentoo Reference Platform</title> |
3097 |
<subsection> |
3098 |
<title>What is the Gentoo Reference Platform?</title> |
3099 |
<body> |
3100 |
|
3101 |
<p> |
3102 |
The Gentoo Reference Platform, from now on abbreviated to GRP, is a snapshot of |
3103 |
prebuilt packages users (that means you!) can install during the installation |
3104 |
of Gentoo to speed up the installation process. The GRP consists of all |
3105 |
packages required to have a fully functional Gentoo installation. They are not |
3106 |
just the ones you need to have a base installation up to speed in no time, but |
3107 |
all lengthier builds (such as xorg-x11, GNOME, OpenOffice, Mozilla, ...) |
3108 |
are available as GRP packages too. |
3109 |
</p> |
3110 |
|
3111 |
<p> |
3112 |
However, these prebuilt packages aren't maintained during the lifetime of the |
3113 |
Gentoo distribution. They are snapshots released at every Gentoo release and |
3114 |
make it possible to have a functional environment in a short amount of time. You |
3115 |
can then upgrade your system in the background while working in your Gentoo |
3116 |
environment. |
3117 |
</p> |
3118 |
|
3119 |
</body> |
3120 |
</subsection> |
3121 |
<subsection> |
3122 |
<title>How Portage Handles GRP Packages</title> |
3123 |
<body> |
3124 |
|
3125 |
<p> |
3126 |
Your Portage tree - the collection of <e>ebuilds</e> (files that contain all |
3127 |
information about a package, such as its description, homepage, sourcecode URLs, |
3128 |
compilation instructions, dependencies, etc.) - must be synchronised with the |
3129 |
GRP set: the versions of the available ebuilds and their accompanying GRP |
3130 |
packages must match. |
3131 |
</p> |
3132 |
|
3133 |
<p> |
3134 |
For this reason you can only benefit from the GRP packages Gentoo provides while |
3135 |
performing the current installation approach. GRP is not available for those |
3136 |
interested in performing an installation using the latest versions of all |
3137 |
available packages. |
3138 |
</p> |
3139 |
|
3140 |
</body> |
3141 |
</subsection> |
3142 |
<subsection> |
3143 |
<title>Is GRP Available?</title> |
3144 |
<body> |
3145 |
|
3146 |
<p> |
3147 |
Not all architectures provide GRP packages. That doesn't mean GRP isn't |
3148 |
supported on the other architectures, but it means that we don't have the |
3149 |
resources to build and test the GRP packages. |
3150 |
</p> |
3151 |
|
3152 |
<p> |
3153 |
At present we provide GRP packages for the following architectures: |
3154 |
</p> |
3155 |
|
3156 |
<ul> |
3157 |
<li> |
3158 |
The <b>amd64</b> architecture (amd64). Note: The packages are now available |
3159 |
on the Installer LiveCD. |
3160 |
</li> |
3161 |
<li> |
3162 |
The <b>ppc</b> architecture (ppc32, ppc64) |
3163 |
</li> |
3164 |
<li> |
3165 |
The <b>sparc</b> architecture (sparc64) |
3166 |
</li> |
3167 |
<li> |
3168 |
The <b>x86</b> architecture (athlon, athlon-xp, athlon-mp, pentium-pro, |
3169 |
pentium2, pentium3, pentium4 and pentium-m) Note: The packages are for i686 |
3170 |
and are available on the Installer LiveCD. |
3171 |
</li> |
3172 |
</ul> |
3173 |
|
3174 |
<p> |
3175 |
If your architecture (or subarchitecture) isn't on this list, you are not |
3176 |
able to opt for a GRP installation. |
3177 |
</p> |
3178 |
|
3179 |
<p> |
3180 |
Now that this introduction is over, let's continue with <uri |
3181 |
link="?part=1&chap=2">Booting the Universal InstallCD/Installer |
3182 |
LiveCD</uri>. |
3183 |
</p> |
3184 |
|
3185 |
</body> |
3186 |
</subsection> |
3187 |
</section> |
3188 |
</sections> |
3189 |
|
3190 |
|
3191 |
|
3192 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-bootloader.xml |
3193 |
|
3194 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-bootloader.xml?rev=1.1&view=markup |
3195 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-bootloader.xml?rev=1.1&content-type=text/plain |
3196 |
|
3197 |
Index: hb-install-alpha-bootloader.xml |
3198 |
=================================================================== |
3199 |
<?xml version='1.0' encoding='UTF-8'?> |
3200 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
3201 |
|
3202 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
3203 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
3204 |
|
3205 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-bootloader.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
3206 |
|
3207 |
<sections> |
3208 |
|
3209 |
<version>7.0</version> |
3210 |
<date>2006-08-30</date> |
3211 |
|
3212 |
<section> |
3213 |
<title>Making your Choice</title> |
3214 |
<subsection> |
3215 |
<title>Introduction</title> |
3216 |
<body> |
3217 |
|
3218 |
<p> |
3219 |
Now that your kernel is configured and compiled and the necessary system |
3220 |
configuration files are filled in correctly, it is time to install a |
3221 |
program that will fire up your kernel when you start the system. Such a |
3222 |
program is called a <e>bootloader</e>. |
3223 |
</p> |
3224 |
|
3225 |
<p> |
3226 |
Several bootloaders exist for Linux/Alpha. You must choose one of the supported |
3227 |
bootloaders, not all. You have the choice between <uri link="#aboot">aBoot</uri> |
3228 |
and <uri link="#milo">MILO</uri>. |
3229 |
</p> |
3230 |
|
3231 |
</body> |
3232 |
</subsection> |
3233 |
</section> |
3234 |
<section id="aboot"> |
3235 |
<title>Default: Using aboot</title> |
3236 |
<body> |
3237 |
|
3238 |
<note> |
3239 |
<c>aboot</c> only supports booting from <b>ext2</b> and <b>ext3</b> |
3240 |
partitions. |
3241 |
</note> |
3242 |
|
3243 |
<p> |
3244 |
We first install aboot on our system. Of course we use <c>emerge</c> to |
3245 |
do so: |
3246 |
</p> |
3247 |
|
3248 |
<pre caption="Installing aboot"> |
3249 |
# <i>emerge aboot</i> |
3250 |
</pre> |
3251 |
|
3252 |
<p> |
3253 |
The next step is to make our bootdisk bootable. This will start |
3254 |
<c>aboot</c> when you boot your system. We make our bootdisk bootable by |
3255 |
writing the <c>aboot</c> bootloader to the start of the disk. |
3256 |
</p> |
3257 |
|
3258 |
<pre caption = "Making your bootdisk bootable"> |
3259 |
# <i>swriteboot -f3 /dev/sda /boot/bootlx</i> |
3260 |
# <i>abootconf /dev/sda 2</i> |
3261 |
</pre> |
3262 |
|
3263 |
<note> |
3264 |
If you use a different partitioning scheme than the one we use |
3265 |
throughout this chapter, you have to change the commands accordingly. |
3266 |
Please read the appropriate manual pages (<c>man 8 swriteboot</c> and |
3267 |
<c>man 8 abootconf</c>). Also, if your root filesystem uses the JFS filesystem, |
3268 |
make sure to pass the <c>ro</c> kernel option so that it can replay its log |
3269 |
before it gets mounted read-write. |
3270 |
</note> |
3271 |
|
3272 |
<p> |
3273 |
Additionally, you can make Gentoo boot automatically by setting up the |
3274 |
aboot configuration file and some SRM variables. You can try setting |
3275 |
these variables from Linux, but it may be easier to do so from the SRM |
3276 |
console itself. |
3277 |
</p> |
3278 |
|
3279 |
<pre caption = "Automatically booting Gentoo"> |
3280 |
# <i>echo '0:2/boot/vmlinux.gz root=/dev/sda2' > /etc/aboot.conf</i> |
3281 |
# <i>cd /proc/srm_environment/named_variables</i> |
3282 |
# <i>echo -n 0 > boot_osflags</i> |
3283 |
# <i>echo -n '' > boot_file</i> |
3284 |
# <i>echo -n 'BOOT' > auto_action</i> |
3285 |
# <i>echo -n 'dkc100' > bootdef_dev</i> |
3286 |
<comment>(Substitute dkc100 with whatever your boot device is)</comment> |
3287 |
</pre> |
3288 |
|
3289 |
<p> |
3290 |
If you need to get into the SRM console again in the future (to recover |
3291 |
your Gentoo install, play with some variables, or whatever), just hit |
3292 |
CTRL+C to abort the automatic loading process. |
3293 |
</p> |
3294 |
|
3295 |
<p> |
3296 |
If you're installing using a serial console, don't forget to include |
3297 |
the serial console boot flag in <path>aboot.conf</path>. See |
3298 |
<path>/etc/aboot.conf.example</path> for some further information. |
3299 |
</p> |
3300 |
|
3301 |
<p> |
3302 |
Aboot is now configured and ready to use. Continue with <uri |
3303 |
link="#reboot">Rebooting the System</uri>. |
3304 |
</p> |
3305 |
|
3306 |
</body> |
3307 |
</section> |
3308 |
<section id="milo"> |
3309 |
<title>Alternative: Using MILO</title> |
3310 |
<body> |
3311 |
|
3312 |
<p> |
3313 |
Before continuing, you should decide on how to use MILO. In this |
3314 |
section, we will assume that you want to make a MILO boot floppy. If you |
3315 |
are going to boot from an MS-DOS partition on your hard disk, you should |
3316 |
amend the commands appropriately. |
3317 |
</p> |
3318 |
|
3319 |
<p> |
3320 |
To install MILO, we use <c>emerge</c>. |
3321 |
</p> |
3322 |
|
3323 |
<pre caption = "Installing MILO"> |
3324 |
# <i>emerge --usepkg milo</i> |
3325 |
</pre> |
3326 |
|
3327 |
<p> |
3328 |
After MILO has been installed, the MILO images should be in |
3329 |
<path>/opt/milo</path>. The commands below make a bootfloppy for use |
3330 |
with MILO. Remember to use the correct image for your Alpha-system. |
3331 |
</p> |
3332 |
|
3333 |
<pre caption = "Installing MILO on a floppy"> |
3334 |
<comment>(First insert a blank floppy)</comment> |
3335 |
# <i>fdformat /dev/fd0</i> |
3336 |
# <i>mformat a:</i> |
3337 |
# <i>mcopy /opt/milo/milo-2.2-18-gentoo-ruffian a:\milo</i> |
3338 |
# <i>mcopy /opt/milo/linload.exe a:\lilnload.exe</i> |
3339 |
<comment>(Only if you have a Ruffian:</comment> |
3340 |
# <i>mcopy /opt/milo/ldmilo.exe a:\ldmilo.exe</i> |
3341 |
<comment>)</comment> |
3342 |
# <i>echo -ne '\125\252' | dd of=/dev/fd0 bs=1 seek=510 count=2</i> |
3343 |
</pre> |
3344 |
|
3345 |
<p> |
3346 |
Your MILO boot floppy is now ready to boot Gentoo Linux. You may need to |
3347 |
set environment variables in your ARCS Firmware to get MILO to start; |
3348 |
this is all explained in the <uri |
3349 |
link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri> with some examples |
3350 |
on common systems, and examples of the commands to use in interactive mode. |
3351 |
</p> |
3352 |
|
3353 |
<p> |
3354 |
Not reading the <uri link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri> |
3355 |
is a <e>bad</e> idea. |
3356 |
</p> |
3357 |
|
3358 |
<p> |
3359 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
3360 |
</p> |
3361 |
|
3362 |
</body> |
3363 |
</section> |
3364 |
<section id="reboot"> |
3365 |
<title>Rebooting the System</title> |
3366 |
<subsection> |
3367 |
<body> |
3368 |
|
3369 |
<p> |
3370 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
3371 |
that one magical command you have been waiting for: <c>reboot</c>. |
3372 |
</p> |
3373 |
|
3374 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
3375 |
# <i>exit</i> |
3376 |
cdimage ~# <i>cd</i> |
3377 |
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
3378 |
cdimage ~# <i>reboot</i> |
3379 |
</pre> |
3380 |
|
3381 |
<p> |
3382 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
3383 |
booted again instead of your new Gentoo system. |
3384 |
</p> |
3385 |
|
3386 |
<p> |
3387 |
Once rebooted in your Gentoo installation, finish up with <uri |
3388 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
3389 |
</p> |
3390 |
|
3391 |
</body> |
3392 |
</subsection> |
3393 |
</section> |
3394 |
|
3395 |
</sections> |
3396 |
|
3397 |
|
3398 |
|
3399 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-disk.xml |
3400 |
|
3401 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-disk.xml?rev=1.1&view=markup |
3402 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-disk.xml?rev=1.1&content-type=text/plain |
3403 |
|
3404 |
Index: hb-install-alpha-disk.xml |
3405 |
=================================================================== |
3406 |
<?xml version='1.0' encoding='UTF-8'?> |
3407 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
3408 |
|
3409 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
3410 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
3411 |
|
3412 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-disk.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
3413 |
|
3414 |
<sections> |
3415 |
|
3416 |
<version>7.1</version> |
3417 |
<date>2006-11-02</date> |
3418 |
|
3419 |
<section> |
3420 |
<title>Introduction to Block Devices</title> |
3421 |
<subsection> |
3422 |
<title>Block Devices</title> |
3423 |
<body> |
3424 |
|
3425 |
<p> |
3426 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
3427 |
and Linux in general, including Linux filesystems, partitions and block devices. |
3428 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
3429 |
you'll be guided through the process of setting up partitions and filesystems |
3430 |
for your Gentoo Linux installation. |
3431 |
</p> |
3432 |
|
3433 |
<p> |
3434 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
3435 |
probably the one that represents the first SCSI HD in a Linux system, namely |
3436 |
<path>/dev/sda</path>. |
3437 |
</p> |
3438 |
|
3439 |
<p> |
3440 |
The block devices above represent an abstract interface to the disk. User |
3441 |
programs can use these block devices to interact with your disk without worrying |
3442 |
about whether your drives are IDE, SCSI or something else. The program can |
3443 |
simply address the storage on the disk as a bunch of contiguous, |
3444 |
randomly-accessible 512-byte blocks. |
3445 |
</p> |
3446 |
|
3447 |
</body> |
3448 |
</subsection> |
3449 |
<subsection> |
3450 |
<title>Slices</title> |
3451 |
<body> |
3452 |
|
3453 |
<p> |
3454 |
Although it is theoretically possible to use a full disk to house your Linux |
3455 |
system, this is almost never done in practice. Instead, full disk block devices |
3456 |
are split up in smaller, more manageable block devices. On Alpha systems, |
3457 |
these are called <e>slices</e>. |
3458 |
</p> |
3459 |
|
3460 |
</body> |
3461 |
</subsection> |
3462 |
</section> |
3463 |
<section> |
3464 |
<title>Designing a Partitioning Scheme</title> |
3465 |
<subsection> |
3466 |
<title>Default Partitioning Scheme</title> |
3467 |
<body> |
3468 |
|
3469 |
<p> |
3470 |
As an example we use the following slice layout: |
3471 |
</p> |
3472 |
|
3473 |
<table> |
3474 |
<tr> |
3475 |
<th>Slice</th> |
3476 |
<th>Description</th> |
3477 |
</tr> |
3478 |
<tr> |
3479 |
<ti><path>/dev/sda1</path></ti> |
3480 |
<ti>Swap slice</ti> |
3481 |
</tr> |
3482 |
<tr> |
3483 |
<ti><path>/dev/sda2</path></ti> |
3484 |
<ti>Root slice</ti> |
3485 |
</tr> |
3486 |
<tr> |
3487 |
<ti><path>/dev/sda3</path></ti> |
3488 |
<ti>Full disk (required)</ti> |
3489 |
</tr> |
3490 |
</table> |
3491 |
|
3492 |
|
3493 |
<p> |
3494 |
If you are interested in knowing how big a partition should be, or even how |
3495 |
many partitions (or volumes) you need, read on. Otherwise continue now with |
3496 |
<uri link="#fdisk_SRM">Using fdisk to Partition your Disk (SRM only)</uri> |
3497 |
or <uri link="#fdisk_ARC">Using fdisk to Partition your Disk (ARC/AlphaBIOS |
3498 |
only)</uri>. |
3499 |
</p> |
3500 |
|
3501 |
</body> |
3502 |
</subsection> |
3503 |
<subsection> |
3504 |
<title>How Many and How Big?</title> |
3505 |
<body> |
3506 |
|
3507 |
<p> |
3508 |
The number of partitions is highly dependent on your environment. For instance, |
3509 |
if you have lots of users, you will most likely want to have your |
3510 |
<path>/home</path> separate as it increases security and makes backups easier. |
3511 |
If you are installing Gentoo to perform as a mailserver, your |
3512 |
<path>/var</path> should be separate as all mails are stored inside |
3513 |
<path>/var</path>. A good choice of filesystem will then maximise your |
3514 |
performance. Gameservers will have a separate <path>/opt</path> as most gaming |
3515 |
servers are installed there. The reason is similar for <path>/home</path>: |
3516 |
security and backups. You will definitely want to keep <path>/usr</path> big: |
3517 |
not only will it contain the majority of applications, the Portage tree alone |
3518 |
takes around 500 Mbyte excluding the various sources that are stored in it. |
3519 |
</p> |
3520 |
|
3521 |
<p> |
3522 |
As you can see, it very much depends on what you want to achieve. Separate |
3523 |
partitions or volumes have the following advantages: |
3524 |
</p> |
3525 |
|
3526 |
<ul> |
3527 |
<li> |
3528 |
You can choose the best performing filesystem for each partition or volume |
3529 |
</li> |
3530 |
<li> |
3531 |
Your entire system cannot run out of free space if one defunct tool is |
3532 |
continuously writing files to a partition or volume |
3533 |
</li> |
3534 |
<li> |
3535 |
If necessary, file system checks are reduced in time, as multiple checks can |
3536 |
be done in parallel (although this advantage is more with multiple disks than |
3537 |
it is with multiple partitions) |
3538 |
</li> |
3539 |
<li> |
3540 |
Security can be enhanced by mounting some partitions or volumes read-only, |
3541 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
3542 |
</li> |
3543 |
</ul> |
3544 |
|
3545 |
<p> |
3546 |
However, multiple partitions have one big disadvantage: if not configured |
3547 |
properly, you might result in having a system with lots |
3548 |
of free space on one partition and none on another. |
3549 |
</p> |
3550 |
|
3551 |
</body> |
3552 |
</subsection> |
3553 |
</section> |
3554 |
<section id="fdisk_SRM"> |
3555 |
<title>Using fdisk to Partition your Disk (SRM only)</title> |
3556 |
<subsection> |
3557 |
<body> |
3558 |
|
3559 |
<p> |
3560 |
The following parts explain how to create the example slice layout described |
3561 |
previously, namely: |
3562 |
</p> |
3563 |
|
3564 |
<table> |
3565 |
<tr> |
3566 |
<th>Slice</th> |
3567 |
<th>Description</th> |
3568 |
</tr> |
3569 |
<tr> |
3570 |
<ti><path>/dev/sda1</path></ti> |
3571 |
<ti>Swap slice</ti> |
3572 |
</tr> |
3573 |
<tr> |
3574 |
<ti><path>/dev/sda2</path></ti> |
3575 |
<ti>Root slice</ti> |
3576 |
</tr> |
3577 |
<tr> |
3578 |
<ti><path>/dev/sda3</path></ti> |
3579 |
<ti>Full disk (required)</ti> |
3580 |
</tr> |
3581 |
</table> |
3582 |
|
3583 |
<p> |
3584 |
Change your slice layout according to your own preference. |
3585 |
</p> |
3586 |
|
3587 |
|
3588 |
</body> |
3589 |
</subsection> |
3590 |
<subsection> |
3591 |
<title>Identifying Available Disks</title> |
3592 |
<body> |
3593 |
|
3594 |
<p> |
3595 |
To figure out what disks you have running, use the following commands: |
3596 |
</p> |
3597 |
|
3598 |
<pre caption="Identifying available disks"> |
3599 |
# <i>dmesg | grep 'drive$'</i> <comment>(For IDE disks)</comment> |
3600 |
# <i>dmesg | grep 'scsi'</i> <comment>(For SCSI disks)</comment> |
3601 |
</pre> |
3602 |
|
3603 |
<p> |
3604 |
>From this output you should be able to see what disks were detected and their |
3605 |
respective <path>/dev</path> entry. In the following parts we assume that the |
3606 |
disk is a SCSI disk on <path>/dev/sda</path>. |
3607 |
</p> |
3608 |
|
3609 |
<p> |
3610 |
Now fire up <c>fdisk</c>: |
3611 |
</p> |
3612 |
|
3613 |
<pre caption="Starting fdisk"> |
3614 |
# <i>fdisk /dev/sda</i> |
3615 |
</pre> |
3616 |
|
3617 |
</body> |
3618 |
</subsection> |
3619 |
<subsection> |
3620 |
<title>Deleting All Slices</title> |
3621 |
<body> |
3622 |
|
3623 |
<p> |
3624 |
If your hard drive is completely blank, then you'll have to first create |
3625 |
a BSD disklabel. |
3626 |
</p> |
3627 |
|
3628 |
<pre caption="Creating a BSD disklabel"> |
3629 |
Command (m for help): <i>b</i> |
3630 |
/dev/sda contains no disklabel. |
3631 |
Do you want to create a disklabel? (y/n) <i>y</i> |
3632 |
<comment>A bunch of drive-specific info will show here</comment> |
3633 |
3 partitions: |
3634 |
# start end size fstype [fsize bsize cpg] |
3635 |
c: 1 5290* 5289* unused 0 0 |
3636 |
</pre> |
3637 |
|
3638 |
<p> |
3639 |
We start with deleting all slices <e>except</e> the 'c'-slice (a requirement |
3640 |
for using BSD disklabels). The following shows how to delete a slice (in |
3641 |
the example we use 'a'). Repeat the process to delete all other slices |
3642 |
(again, except the 'c'-slice). |
3643 |
</p> |
3644 |
|
3645 |
<p> |
3646 |
Use <c>p</c> to view all existing slices. <c>d</c> is used to delete a slice. |
3647 |
</p> |
3648 |
|
3649 |
<pre caption="Deleting a slice"> |
3650 |
BSD disklabel command (m for help): <i>p</i> |
3651 |
|
3652 |
8 partitions: |
3653 |
# start end size fstype [fsize bsize cpg] |
3654 |
a: 1 235* 234* 4.2BSD 1024 8192 16 |
3655 |
b: 235* 469* 234* swap |
3656 |
c: 1 5290* 5289* unused 0 0 |
3657 |
d: 469* 2076* 1607* unused 0 0 |
3658 |
e: 2076* 3683* 1607* unused 0 0 |
3659 |
f: 3683* 5290* 1607* unused 0 0 |
3660 |
g: 469* 1749* 1280 4.2BSD 1024 8192 16 |
3661 |
h: 1749* 5290* 3541* unused 0 0 |
3662 |
|
3663 |
BSD disklabel command (m for help): <i>d</i> |
3664 |
Partition (a-h): <i>a</i> |
3665 |
</pre> |
3666 |
|
3667 |
<p> |
3668 |
After repeating this process for all slices, a listing should show you something |
3669 |
similar to this: |
3670 |
</p> |
3671 |
|
3672 |
<pre caption="Viewing an empty scheme"> |
3673 |
BSD disklabel command (m for help): <i>p</i> |
3674 |
|
3675 |
3 partitions: |
3676 |
# start end size fstype [fsize bsize cpg] |
3677 |
c: 1 5290* 5289* unused 0 0 |
3678 |
</pre> |
3679 |
|
3680 |
</body> |
3681 |
</subsection> |
3682 |
<subsection> |
3683 |
<title>Creating the Swap Slice</title> |
3684 |
<body> |
3685 |
|
3686 |
<p> |
3687 |
On Alpha based systems you don't need a separate boot partition. However, the |
3688 |
first cylinder cannot be used as the <c>aboot</c> image will be placed there. |
3689 |
</p> |
3690 |
|
3691 |
<p> |
3692 |
We will create a swap slice starting at the third cylinder, with a total |
3693 |
size of 1 GB. Use <c>n</c> to create a new slice. After creating the slice, |
3694 |
we will change its type to <c>1</c> (one), meaning <e>swap</e>. |
3695 |
</p> |
3696 |
|
3697 |
<pre caption="Creating the swap slice"> |
3698 |
BSD disklabel command (m for help): <i>n</i> |
3699 |
Partition (a-p): <i>a</i> |
3700 |
First cylinder (1-5290, default 1): <i>3</i> |
3701 |
Last cylinder or +size or +sizeM or +sizeK (3-5290, default 5290): <i>+1024M</i> |
3702 |
|
3703 |
BSD disklabel command (m for help): <i>t</i> |
3704 |
Partition (a-c): <i>a</i> |
3705 |
Hex code (type L to list codes): <i>1</i> |
3706 |
</pre> |
3707 |
|
3708 |
<p> |
3709 |
After these steps you should see a layout similar to the following: |
3710 |
</p> |
3711 |
|
3712 |
<pre caption="Slice layout after creating the swap slice"> |
3713 |
BSD disklabel command (m for help): <i>p</i> |
3714 |
|
3715 |
3 partitions: |
3716 |
# start end size fstype [fsize bsize cpg] |
3717 |
a: 3 1003 1001 swap |
3718 |
c: 1 5290* 5289* unused 0 0 |
3719 |
</pre> |
3720 |
|
3721 |
</body> |
3722 |
</subsection> |
3723 |
<subsection> |
3724 |
<title>Create the Root Slice</title> |
3725 |
<body> |
3726 |
|
3727 |
<p> |
3728 |
We will now create the root slice, starting from the first cylinder <e>after</e> |
3729 |
the swap slice. Use the <c>p</c> command to view where the swap slice ends. In |
3730 |
our example, this is at 1003, making the root partition start at 1004. |
3731 |
</p> |
3732 |
|
3733 |
<p> |
3734 |
Another problem is that there is currently a bug in <c>fdisk</c> making it think |
3735 |
the number of available cylinders is one above the real number of cylinders. In |
3736 |
other words, when you are asked for the last cylinder, decrease the cylinder |
3737 |
number (in this example: 5290) with one. |
3738 |
</p> |
3739 |
|
3740 |
<p> |
3741 |
When the partition is created, we change the type to <c>8</c>, for <e>ext2</e>. |
3742 |
</p> |
3743 |
|
3744 |
<pre caption="Creating the root slice"> |
3745 |
D disklabel command (m for help): <i>n</i> |
3746 |
Partition (a-p): <i>b</i> |
3747 |
First cylinder (1-5290, default 1): <i>1004</i> |
3748 |
Last cylinder or +size or +sizeM or +sizeK (1004-5290, default 5290): <i>5289</i> |
3749 |
|
3750 |
BSD disklabel command (m for help): <i>t</i> |
3751 |
Partition (a-c): <i>b</i> |
3752 |
Hex code (type L to list codes): <i>8</i> |
3753 |
</pre> |
3754 |
|
3755 |
<p> |
3756 |
Your slice layout should now be similar to this: |
3757 |
</p> |
3758 |
|
3759 |
<pre caption="Viewing the slice layout"> |
3760 |
BSD disklabel command (m for help): <i>p</i> |
3761 |
|
3762 |
3 partitions: |
3763 |
# start end size fstype [fsize bsize cpg] |
3764 |
a: 3 1003 1001 swap |
3765 |
b: 1004 5289 4286 ext2 |
3766 |
c: 1 5290* 5289* unused 0 0 |
3767 |
</pre> |
3768 |
|
3769 |
</body> |
3770 |
</subsection> |
3771 |
<subsection> |
3772 |
<title>Save the Slice Layout and Exit</title> |
3773 |
<body> |
3774 |
|
3775 |
<p> |
3776 |
Save <c>fdisk</c> by typing <c>w</c>. This will also save your slice layout. |
3777 |
</p> |
3778 |
|
3779 |
<pre caption="Save and exit fdisk"> |
3780 |
Command (m for help): <i>w</i> |
3781 |
</pre> |
3782 |
|
3783 |
<p> |
3784 |
Now that your slices are created, you can now continue with <uri |
3785 |
link="#filesystems">Creating Filesystems</uri>. |
3786 |
</p> |
3787 |
|
3788 |
</body> |
3789 |
</subsection> |
3790 |
</section> |
3791 |
<section id="fdisk_ARC"> |
3792 |
<title>Using fdisk to Partition your Disk (ARC/AlphaBIOS only)</title> |
3793 |
<subsection> |
3794 |
<body> |
3795 |
|
3796 |
<p> |
3797 |
The following parts explain how to partition the disk with a layout |
3798 |
similar to the one described previously, namely: |
3799 |
</p> |
3800 |
|
3801 |
<table> |
3802 |
<tr> |
3803 |
<th>Partition</th> |
3804 |
<th>Description</th> |
3805 |
</tr> |
3806 |
<tr> |
3807 |
<ti><path>/dev/sda1</path></ti> |
3808 |
<ti>Boot partition</ti> |
3809 |
</tr> |
3810 |
<tr> |
3811 |
<ti><path>/dev/sda2</path></ti> |
3812 |
<ti>Swap partition</ti> |
3813 |
</tr> |
3814 |
<tr> |
3815 |
<ti><path>/dev/sda3</path></ti> |
3816 |
<ti>Root partition</ti> |
3817 |
</tr> |
3818 |
</table> |
3819 |
|
3820 |
<p> |
3821 |
Change your partition layout according to your own preference. |
3822 |
</p> |
3823 |
|
3824 |
</body> |
3825 |
</subsection> |
3826 |
<subsection> |
3827 |
<title>Identifying Available Disks</title> |
3828 |
<body> |
3829 |
|
3830 |
<p> |
3831 |
To figure out what disks you have running, use the following commands: |
3832 |
</p> |
3833 |
|
3834 |
<pre caption="Identifying available disks"> |
3835 |
# <i>dmesg | grep 'drive$'</i> <comment>(For IDE disks)</comment> |
3836 |
# <i>dmesg | grep 'scsi'</i> <comment>(For SCSI disks)</comment> |
3837 |
</pre> |
3838 |
|
3839 |
<p> |
3840 |
>From this output you should be able to see what disks were detected and their |
3841 |
respective <path>/dev</path> entry. In the following parts we assume that the |
3842 |
disk is a SCSI disk on <path>/dev/sda</path>. |
3843 |
</p> |
3844 |
|
3845 |
<p> |
3846 |
Now fire up <c>fdisk</c>: |
3847 |
</p> |
3848 |
|
3849 |
<pre caption="Starting fdisk"> |
3850 |
# <i>fdisk /dev/sda</i> |
3851 |
</pre> |
3852 |
|
3853 |
</body> |
3854 |
</subsection> |
3855 |
<subsection> |
3856 |
<title>Deleting All Partitions</title> |
3857 |
<body> |
3858 |
|
3859 |
<p> |
3860 |
If your hard drive is completely blank, then you'll have to first create |
3861 |
a DOS disklabel. |
3862 |
</p> |
3863 |
|
3864 |
<pre caption="Creating a DOS disklabel"> |
3865 |
Command (m for help): <i>o</i> |
3866 |
Building a new DOS disklabel. |
3867 |
</pre> |
3868 |
|
3869 |
<p> |
3870 |
We start with deleting all partitions. The following shows how to delete |
3871 |
a partition (in the example we use '1'). Repeat the process to delete all |
3872 |
other partitions. |
3873 |
</p> |
3874 |
|
3875 |
<p> |
3876 |
Use <c>p</c> to view all existing partitions. <c>d</c> is used to delete a |
3877 |
partition. |
3878 |
</p> |
3879 |
|
3880 |
<pre caption="Deleting a partition"> |
3881 |
command (m for help): <i>p</i> |
3882 |
|
3883 |
Disk /dev/sda: 9150 MB, 9150996480 bytes |
3884 |
64 heads, 32 sectors/track, 8727 cylinders |
3885 |
Units = cylinders of 2048 * 512 = 1048576 bytes |
3886 |
|
3887 |
Device Boot Start End Blocks Id System |
3888 |
/dev/sda1 1 478 489456 83 Linux |
3889 |
/dev/sda2 479 8727 8446976 5 Extended |
3890 |
/dev/sda5 479 1433 977904 83 Linux Swap |
3891 |
/dev/sda6 1434 8727 7469040 83 Linux |
3892 |
|
3893 |
command (m for help): <i>d</i> |
3894 |
Partition number (1-6): <i>1</i> |
3895 |
</pre> |
3896 |
|
3897 |
|
3898 |
</body> |
3899 |
</subsection> |
3900 |
<subsection> |
3901 |
<title>Creating the Boot Partition</title> |
3902 |
<body> |
3903 |
|
3904 |
<p> |
3905 |
On Alpha systems which use MILO to boot, we have to create a small vfat |
3906 |
boot partition. |
3907 |
</p> |
3908 |
|
3909 |
<pre caption="Creating the boot partition"> |
3910 |
Command (m for help): <i>n</i> |
3911 |
Command action |
3912 |
e extended |
3913 |
p primary partition (1-4) |
3914 |
<i>p</i> |
3915 |
Partition number (1-4): <i>1</i> |
3916 |
First cylinder (1-8727, default 1): <i>1</i> |
3917 |
Last cylinder or +size or +sizeM or +sizeK (1-8727, default 8727): <i>+16M</i> |
3918 |
|
3919 |
Command (m for help): <i>t</i> |
3920 |
Selected partition 1 |
3921 |
Hex code (type L to list codes): <i>6</i> |
3922 |
Changed system type of partition 1 to 6 (FAT16) |
3923 |
</pre> |
3924 |
|
3925 |
</body> |
3926 |
</subsection> |
3927 |
<subsection> |
3928 |
<title>Creating the Swap Partition</title> |
3929 |
<body> |
3930 |
|
3931 |
<p> |
3932 |
We will create a swap partition starting at the third cylinder, with a total |
3933 |
size of 1 GB. Use <c>n</c> to create a new partition. |
3934 |
</p> |
3935 |
|
3936 |
<pre caption="Creating the swap partition"> |
3937 |
Command (m for help): <i>n</i> |
3938 |
Command action |
3939 |
e extended |
3940 |
p primary partition (1-4) |
3941 |
<i>p</i> |
3942 |
Partition number (1-4): <i>2</i> |
3943 |
First cylinder (17-8727, default 17): <i>17</i> |
3944 |
Last cylinder or +size or +sizeM or +sizeK (17-8727, default 8727): <i>+1000M</i> |
3945 |
|
3946 |
Command (m for help): <i>t</i> |
3947 |
Partition number (1-4): <i>1</i> |
3948 |
Hex code (type L to list codes): <i>82</i> |
3949 |
Changed system type of partition 2 to 82 (Linux swap) |
3950 |
</pre> |
3951 |
|
3952 |
<p> |
3953 |
After these steps you should see a layout similar to the following: |
3954 |
</p> |
3955 |
|
3956 |
<pre caption="Partition listing after creating a swap partition"> |
3957 |
Command (m for help): <i>p</i> |
3958 |
|
3959 |
Disk /dev/sda: 9150 MB, 9150996480 bytes |
3960 |
64 heads, 32 sectors/track, 8727 cylinders |
3961 |
Units = cylinders of 2048 * 512 = 1048576 bytes |
3962 |
|
3963 |
Device Boot Start End Blocks Id System |
3964 |
/dev/sda1 1 16 16368 6 FAT16 |
3965 |
/dev/sda2 17 971 977920 82 Linux swap |
3966 |
</pre> |
3967 |
|
3968 |
</body> |
3969 |
</subsection> |
3970 |
<subsection> |
3971 |
<title>Creating the Root Partition</title> |
3972 |
<body> |
3973 |
|
3974 |
<p> |
3975 |
We will now create the root partition. Again, just use the <c>n</c> command. |
3976 |
</p> |
3977 |
|
3978 |
<pre caption="Creating the root partition"> |
3979 |
Command (m for help): <i>n</i> |
3980 |
Command action |
3981 |
e extended |
3982 |
p primary partition (1-4) |
3983 |
<i>p</i> |
3984 |
Partition number (1-4): <i>3</i> |
3985 |
First cylinder (972-8727, default 972): <i>972</i> |
3986 |
Last cylinder or +size or +sizeM or +sizeK (972-8727, default 8727): <i>8727</i> |
3987 |
</pre> |
3988 |
|
3989 |
<p> |
3990 |
After these steps you should see a layout similar to the following: |
3991 |
</p> |
3992 |
|
3993 |
<pre caption="Partition listing after creating the root partition"> |
3994 |
Command (m for help): <i>p</i> |
3995 |
|
3996 |
Disk /dev/sda: 9150 MB, 9150996480 bytes |
3997 |
64 heads, 32 sectors/track, 8727 cylinders |
3998 |
Units = cylinders of 2048 * 512 = 1048576 bytes |
3999 |
|
4000 |
Device Boot Start End Blocks Id System |
4001 |
/dev/sda1 1 16 16368 6 FAT16 |
4002 |
/dev/sda2 17 971 977920 82 Linux swap |
4003 |
/dev/sda3 972 8727 7942144 83 Linux |
4004 |
</pre> |
4005 |
|
4006 |
</body> |
4007 |
</subsection> |
4008 |
<subsection> |
4009 |
<title>Save the Partition Layout and Exit</title> |
4010 |
<body> |
4011 |
|
4012 |
<p> |
4013 |
Save <c>fdisk</c> by typing <c>w</c>. This will also save your partition layout. |
4014 |
</p> |
4015 |
|
4016 |
<pre caption="Save and exit fdisk"> |
4017 |
Command (m for help): <i>w</i> |
4018 |
</pre> |
4019 |
|
4020 |
<p> |
4021 |
Now that your partitions are created, you can now continue with <uri |
4022 |
link="#filesystems">Creating Filesystems</uri>. |
4023 |
</p> |
4024 |
|
4025 |
</body> |
4026 |
</subsection> |
4027 |
</section> |
4028 |
<section id="filesystems"> |
4029 |
<title>Creating Filesystems</title> |
4030 |
<subsection> |
4031 |
<title>Introduction</title> |
4032 |
<body> |
4033 |
|
4034 |
<p> |
4035 |
Now that your partitions are created, it is time to place a filesystem on them. |
4036 |
If you don't care about what filesystem to choose and are happy with what we use |
4037 |
as default in this handbook, continue with <uri |
4038 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
4039 |
Otherwise read on to learn about the available filesystems... |
4040 |
</p> |
4041 |
|
4042 |
</body> |
4043 |
</subsection> |
4044 |
<subsection> |
4045 |
<title>Filesystems?</title> |
4046 |
<body> |
4047 |
|
4048 |
<p> |
4049 |
Several filesystems are available. Most of them are found stable on the |
4050 |
Alpha architecture. |
4051 |
</p> |
4052 |
|
4053 |
<note> |
4054 |
<c>aboot</c> only supports booting from <b>ext2</b> and <b>ext3</b> |
4055 |
partitions. |
4056 |
</note> |
4057 |
|
4058 |
<p> |
4059 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
4060 |
journaling, which means that routine ext2 filesystem checks at startup time can |
4061 |
be quite time-consuming. There is now quite a selection of newer-generation |
4062 |
journaled filesystems that can be checked for consistency very quickly and are |
4063 |
thus generally preferred over their non-journaled counterparts. Journaled |
4064 |
filesystems prevent long delays when you boot your system and your filesystem |
4065 |
happens to be in an inconsistent state. |
4066 |
</p> |
4067 |
|
4068 |
<p> |
4069 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
4070 |
journaling for fast recovery in addition to other enhanced journaling modes |
4071 |
like full data and ordered data journaling. It uses a hashed B*-tree index that |
4072 |
enables high performance in almost all situations. In short, ext3 is a very |
4073 |
good and reliable filesystem. |
4074 |
</p> |
4075 |
|
4076 |
<p> |
4077 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
4078 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
4079 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
4080 |
extremely well and has metadata journaling. ReiserFS is solid and usable as |
4081 |
both general-purpose filesystem and for extreme cases such as the creation of |
4082 |
large filesystems, very large files and directories containing tens of |
4083 |
thousands of small files. |
4084 |
</p> |
4085 |
|
4086 |
<p> |
4087 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
4088 |
feature-set and is optimized for scalability. We only recommend using this |
4089 |
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
4090 |
an uninterruptible power supply. Because XFS aggressively caches in-transit data |
4091 |
in RAM, improperly designed programs (those that don't take proper precautions |
4092 |
when writing files to disk and there are quite a few of them) can lose a good |
4093 |
deal of data if the system goes down unexpectedly. |
4094 |
</p> |
4095 |
|
4096 |
<p> |
4097 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
4098 |
become production-ready and there hasn't been a sufficient track record to |
4099 |
comment positively nor negatively on its general stability at this point. |
4100 |
</p> |
4101 |
|
4102 |
</body> |
4103 |
</subsection> |
4104 |
<subsection id="filesystems-apply"> |
4105 |
<title>Applying a Filesystem to a Partition</title> |
4106 |
<body> |
4107 |
|
4108 |
<p> |
4109 |
To create a filesystem on a partition or volume, there are tools available for |
4110 |
each possible filesystem: |
4111 |
</p> |
4112 |
|
4113 |
<table> |
4114 |
<tr> |
4115 |
<th>Filesystem</th> |
4116 |
<th>Creation Command</th> |
4117 |
</tr> |
4118 |
<tr> |
4119 |
<ti>ext2</ti> |
4120 |
<ti><c>mke2fs</c></ti> |
4121 |
</tr> |
4122 |
<tr> |
4123 |
<ti>ext3</ti> |
4124 |
<ti><c>mke2fs -j</c></ti> |
4125 |
</tr> |
4126 |
<tr> |
4127 |
<ti>reiserfs</ti> |
4128 |
<ti><c>mkreiserfs</c></ti> |
4129 |
</tr> |
4130 |
<tr> |
4131 |
<ti>xfs</ti> |
4132 |
<ti><c>mkfs.xfs</c></ti> |
4133 |
</tr> |
4134 |
<tr> |
4135 |
<ti>jfs</ti> |
4136 |
<ti><c>mkfs.jfs</c></ti> |
4137 |
</tr> |
4138 |
</table> |
4139 |
|
4140 |
<p> |
4141 |
For instance, to have the root partition (<path>/dev/sda2</path> in our example) |
4142 |
in ext3, you would use: |
4143 |
</p> |
4144 |
|
4145 |
<pre caption="Applying a filesystem on a partition"> |
4146 |
# <i>mke2fs -j /dev/sda2</i> |
4147 |
</pre> |
4148 |
|
4149 |
<p> |
4150 |
Now create the filesystems on your newly created partitions (or logical |
4151 |
volumes). |
4152 |
</p> |
4153 |
|
4154 |
</body> |
4155 |
</subsection> |
4156 |
<subsection> |
4157 |
<title>Activating the Swap Partition</title> |
4158 |
<body> |
4159 |
|
4160 |
<p> |
4161 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
4162 |
</p> |
4163 |
|
4164 |
<pre caption="Creating a Swap signature"> |
4165 |
# <i>mkswap /dev/sda1</i> |
4166 |
</pre> |
4167 |
|
4168 |
<p> |
4169 |
To activate the swap partition, use <c>swapon</c>: |
4170 |
</p> |
4171 |
|
4172 |
<pre caption="Activating the swap partition"> |
4173 |
# <i>swapon /dev/sda1</i> |
4174 |
</pre> |
4175 |
|
4176 |
<p> |
4177 |
Create and activate the swap with the commands mentioned above. |
4178 |
</p> |
4179 |
|
4180 |
</body> |
4181 |
</subsection> |
4182 |
</section> |
4183 |
<section> |
4184 |
<title>Mounting</title> |
4185 |
<body> |
4186 |
|
4187 |
<p> |
4188 |
Now that your partitions are initialized and are housing a filesystem, it is |
4189 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
4190 |
create the necessary mount directories for every partition you created. As an |
4191 |
example we mount the root and boot partition: |
4192 |
</p> |
4193 |
|
4194 |
<pre caption="Mounting partitions"> |
4195 |
# <i>mount /dev/sda2 /mnt/gentoo</i> |
4196 |
</pre> |
4197 |
|
4198 |
<note> |
4199 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
4200 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
4201 |
also holds for <path>/var/tmp</path>. |
4202 |
</note> |
4203 |
|
4204 |
<p> |
4205 |
We will also have to mount the proc filesystem (a virtual interface with the |
4206 |
kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. |
4207 |
</p> |
4208 |
|
4209 |
<p> |
4210 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
4211 |
Installation Files</uri>. |
4212 |
</p> |
4213 |
|
4214 |
</body> |
4215 |
</section> |
4216 |
</sections> |
4217 |
|
4218 |
|
4219 |
|
4220 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-kernel.xml |
4221 |
|
4222 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-kernel.xml?rev=1.1&view=markup |
4223 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-kernel.xml?rev=1.1&content-type=text/plain |
4224 |
|
4225 |
Index: hb-install-alpha-kernel.xml |
4226 |
=================================================================== |
4227 |
<?xml version='1.0' encoding='UTF-8'?> |
4228 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
4229 |
|
4230 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
4231 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
4232 |
|
4233 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-kernel.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
4234 |
|
4235 |
<sections> |
4236 |
|
4237 |
<version>7.2</version> |
4238 |
<date>2007-03-12</date> |
4239 |
|
4240 |
<section> |
4241 |
<title>Timezone</title> |
4242 |
<body> |
4243 |
|
4244 |
<p> |
4245 |
You first need to select your timezone so that your system knows where it is |
4246 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
4247 |
it to <path>/etc/localtime</path>. Please avoid the |
4248 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
4249 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
4250 |
</p> |
4251 |
|
4252 |
<pre caption="Setting the timezone information"> |
4253 |
# <i>ls /usr/share/zoneinfo</i> |
4254 |
<comment>(Suppose you want to use GMT)</comment> |
4255 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
4256 |
</pre> |
4257 |
|
4258 |
</body> |
4259 |
</section> |
4260 |
<section> |
4261 |
<title>Installing the Sources</title> |
4262 |
<subsection> |
4263 |
<title>Choosing a Kernel</title> |
4264 |
<body> |
4265 |
|
4266 |
<p> |
4267 |
The core around which all distributions are built is the Linux kernel. It is the |
4268 |
layer between the user programs and your system hardware. Gentoo provides its |
4269 |
users several possible kernel sources. A full listing with description is |
4270 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
4271 |
Guide</uri>. |
4272 |
</p> |
4273 |
|
4274 |
<p> |
4275 |
For alpha-based systems we have <c>vanilla-sources</c> (the default 2.6 kernel source). |
4276 |
</p> |
4277 |
|
4278 |
<pre caption="Installing a kernel source"> |
4279 |
# <i>emerge vanilla-sources</i> |
4280 |
</pre> |
4281 |
|
4282 |
<p> |
4283 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
4284 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
4285 |
kernel source points to <c>vanilla-sources-2.6.16.19</c>. Your version may be |
4286 |
different, so keep this in mind. |
4287 |
</p> |
4288 |
|
4289 |
<pre caption="Viewing the kernel source symlink"> |
4290 |
# <i>ls -l /usr/src/linux</i> |
4291 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-2.6.16.19 |
4292 |
</pre> |
4293 |
|
4294 |
<p> |
4295 |
Now it is time to configure and compile your kernel source. You |
4296 |
can use <c>genkernel</c> for this, which will build a generic kernel as used |
4297 |
by the Installation CD. We explain the "manual" configuration first though, as it is |
4298 |
the best way to optimize your environment. |
4299 |
</p> |
4300 |
|
4301 |
<p> |
4302 |
If you want to manually configure your kernel, continue now with <uri |
4303 |
link="#manual">Default: Manual Configuration</uri>. If you want to use |
4304 |
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
4305 |
genkernel</uri> instead. |
4306 |
</p> |
4307 |
|
4308 |
</body> |
4309 |
</subsection> |
4310 |
</section> |
4311 |
<section id="manual"> |
4312 |
<title>Default: Manual Configuration</title> |
4313 |
<subsection> |
4314 |
<title>Introduction</title> |
4315 |
<body> |
4316 |
|
4317 |
<p> |
4318 |
Manually configuring a kernel is often seen as the most difficult procedure a |
4319 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
4320 |
couple of kernels you don't even remember that it was difficult ;) |
4321 |
</p> |
4322 |
|
4323 |
<p> |
4324 |
However, one thing <e>is</e> true: you must know your system when you start |
4325 |
configuring a kernel manually. You can run <c>lsmod</c> to see what kernel |
4326 |
modules the Installation CD uses (it might provide you with a nice hint on |
4327 |
what to enable). |
4328 |
</p> |
4329 |
|
4330 |
<p> |
4331 |
Now go to your kernel source directory and execute <c>make menuconfig</c>. This |
4332 |
will fire up an ncurses-based configuration menu. |
4333 |
</p> |
4334 |
|
4335 |
<pre caption="Invoking menuconfig"> |
4336 |
# <i>cd /usr/src/linux</i> |
4337 |
# <i>make menuconfig</i> |
4338 |
</pre> |
4339 |
|
4340 |
<p> |
4341 |
You will be greeted with several configuration sections. We'll first list some |
4342 |
options you must activate (otherwise Gentoo will not function, or not function |
4343 |
properly without additional tweaks). |
4344 |
</p> |
4345 |
|
4346 |
</body> |
4347 |
</subsection> |
4348 |
<subsection> |
4349 |
<title>Activating Required Options</title> |
4350 |
<body> |
4351 |
|
4352 |
<p> |
4353 |
First of all, activate the use of development and experimental code/drivers. |
4354 |
You need this, otherwise some very important code/drivers won't show up: |
4355 |
</p> |
4356 |
|
4357 |
<pre caption="Selecting experimental code/drivers"> |
4358 |
Code maturity level options ---> |
4359 |
[*] Prompt for development and/or incomplete code/drivers |
4360 |
</pre> |
4361 |
|
4362 |
<p> |
4363 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
4364 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
4365 |
able to mount your partitions. Also select <c>Virtual memory</c>, <c>/proc |
4366 |
file system</c>, (<c>/dev file system</c> + <c>Automatically mount at boot</c> only for 2.4 kernel): |
4367 |
</p> |
4368 |
|
4369 |
<pre caption="Selecting necessary file systems"> |
4370 |
<comment>(With a 2.4.x kernel)</comment> |
4371 |
File systems ---> |
4372 |
[*] Virtual memory file system support (former shm fs) |
4373 |
[*] /proc file system support |
4374 |
[*] /dev file system support (EXPERIMENTAL) |
4375 |
[*] Automatically mount at boot |
4376 |
[ ] /dev/pts file system for Unix98 PTYs |
4377 |
|
4378 |
<comment>(With a 2.6.x kernel)</comment> |
4379 |
File systems ---> |
4380 |
Pseudo Filesystems ---> |
4381 |
[*] /proc file system support |
4382 |
[*] Virtual memory file system support (former shm fs) |
4383 |
|
4384 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
4385 |
<*> Reiserfs support |
4386 |
<*> Ext3 journalling file system support |
4387 |
<*> JFS filesystem support |
4388 |
<*> Second extended fs support |
4389 |
<*> XFS filesystem support |
4390 |
</pre> |
4391 |
|
4392 |
<p> |
4393 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
4394 |
modem, you will need the following options in the kernel: |
4395 |
</p> |
4396 |
|
4397 |
<pre caption="Selecting PPPoE necessary drivers"> |
4398 |
<comment>(With a 2.4.x kernel)</comment> |
4399 |
Network device support ---> |
4400 |
<*> PPP (point-to-point protocol) support |
4401 |
<*> PPP support for async serial ports |
4402 |
<*> PPP support for sync tty ports |
4403 |
|
4404 |
<comment>(With a 2.6.x kernel)</comment> |
4405 |
Device Drivers ---> |
4406 |
Networking support ---> |
4407 |
<*> PPP (point-to-point protocol) support |
4408 |
<*> PPP support for async serial ports |
4409 |
<*> PPP support for sync tty ports |
4410 |
</pre> |
4411 |
|
4412 |
<p> |
4413 |
The two compression options won't harm but are not definitely needed, neither |
4414 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
4415 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
4416 |
</p> |
4417 |
|
4418 |
<p> |
4419 |
If you require it, don't forget to include support in the kernel for your |
4420 |
ethernet card. |
4421 |
</p> |
4422 |
|
4423 |
<p> |
4424 |
The following options are recommended as well: |
4425 |
</p> |
4426 |
|
4427 |
<pre caption="Recommended Alpha options"> |
4428 |
General setup ---> |
4429 |
<*> SRM environment through procfs |
4430 |
<*> Configure uac policy via sysctl |
4431 |
|
4432 |
Plug and Play configuration ---> |
4433 |
<*> Plug and Play support |
4434 |
<M> ISA Plug and Play support |
4435 |
|
4436 |
SCSI support ---> |
4437 |
SCSI low-level drivers ---> |
4438 |
<*> SYM53C8XX Version 2 SCSI support (NEW) |
4439 |
<*> Qlogic ISP SCSI support |
4440 |
|
4441 |
Network device support ---> |
4442 |
Ethernet (10 or 100 Mbit) ---> |
4443 |
<M> DECchip Tulip (dc21x4x) PCI support |
4444 |
<M> Generic DECchip & DIGITAL EtherWORKS PCI/EISA |
4445 |
<M> EtherExpressPro/100 support (eepro100) |
4446 |
<M> EtherExpressPro/100 support (e100) |
4447 |
Ethernet (1000 Mbit) ---> |
4448 |
<M> Alteon AceNIC |
4449 |
[*] Omit support for old Tigon I |
4450 |
<M> Broadcom Tigon3 |
4451 |
[*] FDDI driver support |
4452 |
<M> Digital DEFEA and DEFPA |
4453 |
<*> PPP support |
4454 |
<*> PPP Deflate compression |
4455 |
|
4456 |
Character devices ---> |
4457 |
[*] Support for console on serial port |
4458 |
[*] Direct Rendering Manager |
4459 |
|
4460 |
File systems ---> |
4461 |
<*> Kernel automounter version 4 support |
4462 |
Network File Systems ---> |
4463 |
<*> NFS |
4464 |
[*] NFSv3 client |
4465 |
<*> NFS server |
4466 |
[*] NFSv3 server |
4467 |
Partition Types ---> |
4468 |
[*] Advanced partition selection |
4469 |
[*] Alpha OSF partition support |
4470 |
Native Language Support |
4471 |
<*> NLS ISO 8859-1 |
4472 |
|
4473 |
Sound ---> |
4474 |
<M> Sound card support |
4475 |
<M> OSS sound modules |
4476 |
[*] Verbose initialisation |
4477 |
[*] Persistent DMA buffers |
4478 |
<M> 100% Sound Blaster compatibles |
4479 |
</pre> |
4480 |
|
4481 |
<p> |
4482 |
When you've finished configuring the kernel, continue with <uri |
4483 |
link="#compiling">Compiling and Installing</uri>. |
4484 |
</p> |
4485 |
|
4486 |
</body> |
4487 |
</subsection> |
4488 |
<subsection id="compiling"> |
4489 |
<title>Compiling and Installing</title> |
4490 |
<body> |
4491 |
|
4492 |
<p> |
4493 |
Now that your kernel is configured, it is time to compile and install it. Exit |
4494 |
the configuration and start the compilation process: |
4495 |
</p> |
4496 |
|
4497 |
<pre caption="Compiling the kernel"> |
4498 |
<comment>(For 2.4 kernel)</comment> |
4499 |
# <i>make dep && make vmlinux modules modules_install</i> |
4500 |
|
4501 |
<comment>(For 2.6 kernel)</comment> |
4502 |
# <i>make && make modules_install</i> |
4503 |
|
4504 |
<comment>(For all kernels)</comment> |
4505 |
# <i>make boot</i> |
4506 |
</pre> |
4507 |
|
4508 |
<p> |
4509 |
When the kernel has finished compiling, copy the kernel image to |
4510 |
<path>/boot</path>. Recent kernels might create <path>vmlinux</path> instead of |
4511 |
<path>vmlinux.gz</path>. Keep this in mind when you copy your kernel image. |
4512 |
</p> |
4513 |
|
4514 |
<pre caption="Installing the kernel"> |
4515 |
# <i>cp arch/alpha/boot/vmlinux.gz /boot/</i> |
4516 |
</pre> |
4517 |
|
4518 |
<p> |
4519 |
Now continue with <uri link="#kernel_modules">Installing Separate Kernel |
4520 |
Modules</uri>. |
4521 |
</p> |
4522 |
|
4523 |
</body> |
4524 |
</subsection> |
4525 |
</section> |
4526 |
<section id="genkernel"> |
4527 |
<title>Alternative: Using genkernel</title> |
4528 |
<body> |
4529 |
|
4530 |
<p> |
4531 |
If you are reading this section, you have chosen to use our <c>genkernel</c> |
4532 |
script to configure your kernel for you. |
4533 |
</p> |
4534 |
|
4535 |
<p> |
4536 |
Now that your kernel source tree is installed, it's now time to compile your |
4537 |
kernel by using our <c>genkernel</c> script to automatically build a kernel for |
4538 |
you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
4539 |
way our Installation CD kernel is configured. This means that when you use |
4540 |
<c>genkernel</c> to build your kernel, your system will generally detect all |
4541 |
your hardware at boot-time, just like our Installation CD does. Because genkernel |
4542 |
doesn't require any manual kernel configuration, it is an ideal solution for |
4543 |
those users who may not be comfortable compiling their own kernels. |
4544 |
</p> |
4545 |
|
4546 |
<p> |
4547 |
Now, let's see how to use genkernel. First, emerge the genkernel ebuild: |
4548 |
</p> |
4549 |
|
4550 |
<pre caption="Emerging genkernel"> |
4551 |
# <i>emerge genkernel</i> |
4552 |
</pre> |
4553 |
|
4554 |
<p> |
4555 |
Now, compile your kernel sources by running <c>genkernel all</c>. |
4556 |
Be aware though, as <c>genkernel</c> compiles a kernel that supports almost all |
4557 |
hardware, this compilation will take quite a while to finish! |
4558 |
</p> |
4559 |
|
4560 |
<p> |
4561 |
Note that, if your boot partition doesn't use ext2 or ext3 as filesystem you |
4562 |
need to manually configure your kernel using <c>genkernel --menuconfig all</c> |
4563 |
and add support for your filesystem <e>in</e> the kernel (i.e. <e>not</e> as a |
4564 |
module). |
4565 |
</p> |
4566 |
|
4567 |
<pre caption="Running genkernel"> |
4568 |
* Gentoo Linux Genkernel; Version 3.4.0 |
4569 |
* Running with options: all |
4570 |
|
4571 |
* Linux Kernel 2.6.16.19 for alpha... |
4572 |
* kernel: >> Running mrproper... |
4573 |
# <i>genkernel all</i> |
4574 |
<comment>(Output removed to increase readability)</comment> |
4575 |
* Kernel compiled successfully! |
4576 |
* |
4577 |
* Required Kernel Parameters: |
4578 |
* real_root=/dev/$ROOT |
4579 |
* |
4580 |
* Where $ROOT is the device node for your root partition as the |
4581 |
* one specified in /etc/fstab |
4582 |
* |
4583 |
* If you require Genkernel's hardware detection features; you MUST |
4584 |
* tell your bootloader to use the provided INITRAMFS file. Otherwise; |
4585 |
* substitute the root argument for the real_root argument if you are |
4586 |
* not planning to use the initrd... |
4587 |
|
4588 |
* WARNING... WARNING... WARNING... |
4589 |
* Additional kernel cmdline arguments that *may* be required to boot properly... |
4590 |
* Do NOT report kernel bugs as genkernel bugs unless your bug |
4591 |
* is about the default genkernel configuration... |
4592 |
* |
4593 |
* Make sure you have the latest genkernel before reporting bugs. |
4594 |
</pre> |
4595 |
|
4596 |
<p> |
4597 |
Once <c>genkernel</c> completes, a kernel, full set of modules and |
4598 |
<e>initial root disk</e> (initrd) will be created. We will use the kernel |
4599 |
and initrd when configuring a boot loader later in this document. Write |
4600 |
down the names of the kernel and initrd as you will need it when writing |
4601 |
the bootloader configuration file. The initrd will be started immediately after |
4602 |
booting to perform hardware autodetection (just like on the Installation CD) before |
4603 |
your "real" system starts up. |
4604 |
</p> |
4605 |
|
4606 |
<pre caption="Checking the created kernel image name and initrd"> |
4607 |
# <i>ls /boot/kernel* /boot/initramfs*</i> |
4608 |
</pre> |
4609 |
|
4610 |
</body> |
4611 |
</section> |
4612 |
<section id="kernel_modules"> |
4613 |
<title>Installing Separate Kernel Modules</title> |
4614 |
<subsection> |
4615 |
<title>Installing Extra Modules</title> |
4616 |
<body> |
4617 |
|
4618 |
<p> |
4619 |
If appropriate, you should emerge ebuilds for any additional hardware that is |
4620 |
on your system. Here is a list of kernel-related ebuilds that you could emerge: |
4621 |
</p> |
4622 |
|
4623 |
<table> |
4624 |
<tcolumn width="1in"/> |
4625 |
<tcolumn width="4in"/> |
4626 |
<tcolumn width="2in"/> |
4627 |
<tr> |
4628 |
<th>Ebuild</th> |
4629 |
<th>Purpose</th> |
4630 |
<th>Command</th> |
4631 |
</tr> |
4632 |
<tr> |
4633 |
<ti>x11-drm</ti> |
4634 |
<ti> |
4635 |
Accelerated graphics for ATI Radeon up to 9200, Rage128, Matrox, Voodoo and |
4636 |
other cards for xorg-x11. Please check the <c>IUSE_VIDEO_CARDS</c> variable |
4637 |
in the <path>/usr/portage/x11-base/x11-drm</path> ebuilds to see what you |
4638 |
need to fill in as <c>yourcard</c>. |
4639 |
</ti> |
4640 |
<ti><c>VIDEO_CARDS="yourcard" emerge x11-drm</c></ti> |
4641 |
</tr> |
4642 |
</table> |
4643 |
|
4644 |
<p> |
4645 |
Beware though, some of these ebuilds might deal with big dependencies. To verify |
4646 |
what packages will be installed by emerging an ebuild, use <c>emerge |
4647 |
--pretend</c>. For instance, for the <c>x11-drm</c> package: |
4648 |
</p> |
4649 |
|
4650 |
<pre caption="View full installation package listing"> |
4651 |
# <i>emerge --pretend x11-drm</i> |
4652 |
</pre> |
4653 |
|
4654 |
</body> |
4655 |
</subsection> |
4656 |
<subsection> |
4657 |
<title>Configuring the Modules</title> |
4658 |
<body> |
4659 |
|
4660 |
<p> |
4661 |
You should list the modules you want automatically loaded in |
4662 |
<path>/etc/modules.autoload.d/kernel-2.4</path> (or <path>kernel-2.6</path>). |
4663 |
You can add extra options to the modules too if you want. |
4664 |
</p> |
4665 |
|
4666 |
<p> |
4667 |
To view all available modules, run the following <c>find</c> command. Don't |
4668 |
forget to substitute "<kernel version>" with the version of the kernel you |
4669 |
just compiled: |
4670 |
</p> |
4671 |
|
4672 |
<pre caption="Viewing all available modules"> |
4673 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
4674 |
</pre> |
4675 |
|
4676 |
<p> |
4677 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
4678 |
<path>kernel-2.4</path> or <path>kernel-2.6</path> file and enter the module |
4679 |
name in it. |
4680 |
</p> |
4681 |
|
4682 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.4"> |
4683 |
<comment>(Example for 2.4 kernels)</comment> |
4684 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.4</i> |
4685 |
</pre> |
4686 |
|
4687 |
<pre caption="/etc/modules.autoload.d/kernel-2.4 or kernel-2.6"> |
4688 |
3c59x |
4689 |
</pre> |
4690 |
|
4691 |
<p> |
4692 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
4693 |
your System</uri>. |
4694 |
</p> |
4695 |
|
4696 |
</body> |
4697 |
</subsection> |
4698 |
</section> |
4699 |
</sections> |
4700 |
|
4701 |
|
4702 |
|
4703 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-medium.xml |
4704 |
|
4705 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-medium.xml?rev=1.1&view=markup |
4706 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-medium.xml?rev=1.1&content-type=text/plain |
4707 |
|
4708 |
Index: hb-install-alpha-medium.xml |
4709 |
=================================================================== |
4710 |
<?xml version='1.0' encoding='UTF-8'?> |
4711 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
4712 |
|
4713 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
4714 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
4715 |
|
4716 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-alpha-medium.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
4717 |
|
4718 |
<sections> |
4719 |
|
4720 |
<version>7.0</version> |
4721 |
<date>2006-08-30</date> |
4722 |
|
4723 |
<section> |
4724 |
<title>Hardware Requirements</title> |
4725 |
<subsection> |
4726 |
<title>Introduction</title> |
4727 |
<body> |
4728 |
|
4729 |
<p> |
4730 |
Before we start, we first list what hardware requirements you need to |
4731 |
successfully install Gentoo on your box. |
4732 |
</p> |
4733 |
|
4734 |
</body> |
4735 |
</subsection> |
4736 |
<subsection> |
4737 |
<title>Hardware Requirements</title> |
4738 |
<body> |
4739 |
|
4740 |
<table> |
4741 |
<tr> |
4742 |
<th>CPU</th> |
4743 |
<ti> |
4744 |
Please check with the <uri |
4745 |
link="http://www.alphalinux.org/faq/FAQ-5.html">Alpha/Linux FAQ</uri> |
4746 |
</ti> |
4747 |
</tr> |
4748 |
<tr> |
4749 |
<th>Memory</th> |
4750 |
<ti>64 MB</ti> |
4751 |
</tr> |
4752 |
<tr> |
4753 |
<th>Diskspace</th> |
4754 |
<ti>1.5 GB (excluding swap space)</ti> |
4755 |
</tr> |
4756 |
<tr> |
4757 |
<th>Swap space</th> |
4758 |
<ti>At least 256 MB</ti> |
4759 |
</tr> |
4760 |
</table> |
4761 |
|
4762 |
</body> |
4763 |
</subsection> |
4764 |
</section> |
4765 |
<!-- Copy/paste from the hb-install-x86-medium.xml file but no Universal |
4766 |
Installation CD. |
4767 |
Also s/x86/alpha --> |
4768 |
<!-- START --> |
4769 |
<section> |
4770 |
<title>The Gentoo Universal Installation CD</title> |
4771 |
<subsection> |
4772 |
<title>Introduction</title> |
4773 |
<body> |
4774 |
|
4775 |
<p> |
4776 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
4777 |
Such a tarball is an archive that contains a minimal environment from |
4778 |
which you can succesfully install Gentoo Linux onto your system. |
4779 |
</p> |
4780 |
|
4781 |
<p> |
4782 |
Installations using a stage1 or stage2 tarball file are not documented in the |
4783 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
4784 |
FAQ</uri> on these matters. |
4785 |
</p> |
4786 |
|
4787 |
</body> |
4788 |
</subsection> |
4789 |
<subsection> |
4790 |
<title>Gentoo Universal Installation CD</title> |
4791 |
<body> |
4792 |
|
4793 |
<p> |
4794 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
4795 |
environment. It allows you to boot Linux from the CD. During the boot process |
4796 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
4797 |
Installation CDs are maintained by Gentoo developers. |
4798 |
</p> |
4799 |
|
4800 |
<p> |
4801 |
There currently are two Installation CDs available: |
4802 |
</p> |
4803 |
|
4804 |
<ul> |
4805 |
<li> |
4806 |
The Universal Installation CD contains everything you need to install |
4807 |
Gentoo. It provides stage3 files for common architectures, source code |
4808 |
for the extra applications you need to choose from and, of course, the |
4809 |
installation instructions for your architecture. |
4810 |
</li> |
4811 |
<li> |
4812 |
The Minimal Installation CD contains only a minimal environment that allows |
4813 |
you to boot up and configure your network so you can connect to the |
4814 |
Internet. It does not contain any additional files and cannot be used |
4815 |
during the current installation approach. |
4816 |
</li> |
4817 |
</ul> |
4818 |
|
4819 |
</body> |
4820 |
</subsection> |
4821 |
</section> |
4822 |
<!-- STOP --> |
4823 |
<section> |
4824 |
<title>Download, Burn and Boot the Gentoo Universal Installation CD</title> |
4825 |
<subsection> |
4826 |
<title>Downloading and Burning the Installation CD</title> |
4827 |
<body> |
4828 |
|
4829 |
<p> |
4830 |
You can download the Universal Installation CD from one of our <uri |
4831 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CD is located in |
4832 |
the <path>releases/alpha/2006.1/installcd</path> directory. |
4833 |
</p> |
4834 |
|
4835 |
<p> |
4836 |
Inside those directories you'll find ISO-files. Those are full CD images which |
4837 |
you can write on a CD-R. |
4838 |
</p> |
4839 |
|
4840 |
<p> |
4841 |
After downloading the file, you can verify its integrity to see if it is |
4842 |
corrupted or not: |
4843 |
</p> |
4844 |
|
4845 |
<ul> |
4846 |
<li> |
4847 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
4848 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
4849 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows) |
4850 |
</li> |
4851 |
<li> |
4852 |
You can verify the cryptographic signature that we provide. You need to |
4853 |
obtain the public key we use (17072058) before you proceed though. |
4854 |
</li> |
4855 |
</ul> |
4856 |
|
4857 |
<p> |
4858 |
To fetch our public key using the GnuPG application, run the following command: |
4859 |
</p> |
4860 |
|
4861 |
<pre caption="Obtaining the public key"> |
4862 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
4863 |
</pre> |
4864 |
|
4865 |
<p> |
4866 |
Now verify the signature: |
4867 |
</p> |
4868 |
|
4869 |
<pre caption="Verify the cryptographic signature"> |
4870 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
4871 |
</pre> |
4872 |
|
4873 |
<p> |
4874 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
4875 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
4876 |
<c>K3B</c> here; more information can be found in our <uri |
4877 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
4878 |
</p> |
4879 |
|
4880 |
<ul> |
4881 |
<li> |
4882 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
4883 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
4884 |
path). |
4885 |
</li> |
4886 |
<li> |
4887 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
4888 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
4889 |
<c>Start</c>. |
4890 |
</li> |
4891 |
</ul> |
4892 |
|
4893 |
</body> |
4894 |
</subsection> |
4895 |
<subsection> |
4896 |
<title>Booting the Universal Installation CD</title> |
4897 |
<body> |
4898 |
|
4899 |
<p> |
4900 |
When your Alpha is powered on, the first thing that gets started is the |
4901 |
firmware. It is loosely synonymous with the BIOS software on PC systems. There |
4902 |
are two types of firmware on Alpha systems: SRM (<e>Systems Reference |
4903 |
Manual</e>) and ARC (<e>Advanced Risc Console</e>). |
4904 |
</p> |
4905 |
|
4906 |
<p> |
4907 |
SRM is based on the Alpha Console Subsystem specification, which provides an |
4908 |
operating environment for OpenVMS, Tru64 UNIX, and Linux operating systems. ARC |
4909 |
is based on the Advanced RISC Computing (ARC) specification, which provides |
4910 |
an operating environment for Windows NT. You can find a |
4911 |
<uri link="http://www.alphalinux.org/faq/SRM-HOWTO/">detailed guide</uri> on |
4912 |
using SRM over at the Alpha Linux website. |
4913 |
</p> |
4914 |
|
4915 |
<p> |
4916 |
If your Alpha system supports both SRC and ARCs (ARC, AlphaBIOS, ARCSBIOS) you |
4917 |
should follow <uri link="http://www.alphalinux.org/faq/x31.html">these |
4918 |
instructions</uri> for switching to SRM. If your system already uses SRM, you |
4919 |
are all set. If your system can only use ARCs (Ruffian, nautilus, xl, etc.) you |
4920 |
will need to choose <c>MILO</c> later on when we are talking about bootloaders. |
4921 |
</p> |
4922 |
|
4923 |
<p> |
4924 |
Now to boot an Alpha Installation CD, put the CD-ROM in the tray and reboot the system. |
4925 |
You can use SRM to boot the Installation CD. If you cannot do that, you will have to use |
4926 |
<c>MILO</c>. If you don't have <c>MILO</c> installed already, use one of the |
4927 |
precompiled <c>MILO</c> images available on <uri |
4928 |
link="http://dev.gentoo.org/~taviso/milo/">taviso's homepage</uri>. |
4929 |
</p> |
4930 |
|
4931 |
<p> |
4932 |
This release also includes two entries for people who want to use a serial |
4933 |
console during the installation, possibly boxes with no keyboard and screen |
4934 |
attached. One allows you to boot 2.6 using the serial console and the other will |
4935 |
do the same with our 2.4 kernel. |
4936 |
</p> |
4937 |
|
4938 |
<pre caption="Booting a CD-ROM using SRM"> |
4939 |
<comment>(List available hardware drives)</comment> |
4940 |
>>> <i>show device</i> |
4941 |
dkb0.0.1.4.0 DKB0 TOSHIBA CDROM |
4942 |
<comment>(...)</comment> |
4943 |
<comment>(Substitute dkb0 with your CD-ROM drive device)</comment> |
4944 |
>>> <i>boot dkb0 -flags 0</i> |
4945 |
<comment>(To boot the 2.4 kernel instead of the default 2.6 kernel use:)</comment> |
4946 |
>>> <i>boot dkb -flags 1</i> |
4947 |
<comment>(If you need serial console support)</comment> |
4948 |
<comment>(To boot the 2.6 kernel with serial console support use:)</comment> |
4949 |
>>> <i>boot dkb0 -flags 2</i> |
4950 |
<comment>(To boot the 2.4 kernel with serial console support use:)</comment> |
4951 |
>>> <i>boot dkb0 -flags 3</i> |
4952 |
</pre> |
4953 |
|
4954 |
<pre caption="Booting a CD-ROM using MILO"> |
4955 |
<comment>(Substitute hdb with your CD-ROM drive device)</comment> |
4956 |
MILO> <i>boot hdb:/boot/gentoo_2.6 initrd=/boot/gentoo_2_6.igz root=/dev/ram0 init=/linuxrc looptype=zisofs loop=/zisofs cdroot</i> |
4957 |
<comment>(To boot the 2.4 kernel instead of the default 2.6 kernel use:)</comment> |
4958 |
MILO> <i>boot hdb:/boot/gentoo_2.4 initrd=/boot/gentoo_2_4.igz root=/dev/ram0 init=/linuxrc looptype=zisofs loop=/zisofs cdroot</i> |
4959 |
<comment>(If you need serial console support)</comment> |
4960 |
<comment>(To boot the 2.6 kernel with serial console support use:)</comment> |
4961 |
MILO> <i>boot hdb:/boot/gentoo_2.6 initrd=/boot/gentoo_2_6.igz root=/dev/ram0 init=/linuxrc looptype=zisofs loop=/zisofs console=ttyS0</i> |
4962 |
<comment>(To boot the 2.4 kernel with serial console support use:)</comment> |
4963 |
MILO> <i>boot hdb:/boot/gentoo_2.4 initrd=/boot/gentoo_2_4.igz root=/dev/ram0 init=/linuxrc looptype=zisofs loop=/zisofs console=ttyS0 cdroot</i> |
4964 |
</pre> |
4965 |
|
4966 |
<p> |
4967 |
You should have a root ("#") prompt on the current console and can also switch |
4968 |
to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get back to the one you |
4969 |
started on by pressing Alt-F1. |
4970 |
</p> |
4971 |
|
4972 |
<p> |
4973 |
Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
4974 |
</p> |
4975 |
|
4976 |
</body> |
4977 |
</subsection> |
4978 |
<subsection id="hardware"> |
4979 |
<title>Extra Hardware Configuration</title> |
4980 |
<body> |
4981 |
|
4982 |
<p> |
4983 |
When the Installation CD boots, it tries to detect all your hardware devices and |
4984 |
loads the appropriate kernel modules to support your hardware. In the |
4985 |
vast majority of cases, it does a very good job. However, in some cases (the |
4986 |
SPARC Installation CDs don't even do autodetection), it may not auto-load the kernel |
4987 |
modules you need. If the PCI auto-detection missed some of your system's |
4988 |
hardware, you will have to load the appropriate kernel modules manually. |
4989 |
</p> |
4990 |
|
4991 |
<p> |
4992 |
In the next example we try to load the <c>8139too</c> module (support for |
4993 |
certain kinds of network interfaces): |
4994 |
</p> |
4995 |
|
4996 |
<pre caption="Loading kernel modules"> |
4997 |
# <i>modprobe 8139too</i> |
4998 |
</pre> |
4999 |
|
5000 |
<p> |
5001 |
If you need PCMCIA support, you should start the <c>pcmcia</c> init script: |
5002 |
</p> |
5003 |
|
5004 |
<pre caption="Starting the PCMCIA init script"> |
5005 |
# <i>/etc/init.d/pcmcia start</i> |
5006 |
</pre> |
5007 |
|
5008 |
</body> |
5009 |
</subsection> |
5010 |
<subsection> |
5011 |
<title>Optional: Tweaking Hard Disk Performance</title> |
5012 |
<body> |
5013 |
|
5014 |
<p> |
5015 |
If you are an advanced user, you might want to tweak the IDE hard disk |
5016 |
performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
5017 |
test the performance of your disk (execute it several times to get a |
5018 |
more precise impression): |
5019 |
</p> |
5020 |
|
5021 |
<pre caption="Testing disk performance"> |
5022 |
# <i>hdparm -tT /dev/hda</i> |
5023 |
</pre> |
5024 |
|
5025 |
<p> |
5026 |
To tweak, you can use any of the following examples (or experiment |
5027 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
5028 |
disk): |
5029 |
</p> |
5030 |
|
5031 |
<pre caption="Tweaking hard disk performance"> |
5032 |
<comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i> |
5033 |
<comment>Activate DMA + Safe Performance-enhancing Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
5034 |
</pre> |
5035 |
|
5036 |
</body> |
5037 |
</subsection> |
5038 |
<subsection id="useraccounts"> |
5039 |
<title>Optional: User Accounts</title> |
5040 |
<body> |
5041 |
|
5042 |
<p> |
5043 |
If you plan on giving other people access to your installation |
5044 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
5045 |
security reasons), you need to create the necessary user accounts and change |
5046 |
the root password. |
5047 |
</p> |
5048 |
|
5049 |
<p> |
5050 |
To change the root password, use the <c>passwd</c> utility: |
5051 |
</p> |
5052 |
|
5053 |
<pre caption="Changing the root password"> |
5054 |
# <i>passwd</i> |
5055 |
New password: <comment>(Enter your new password)</comment> |
5056 |
Re-enter password: <comment>(Re-enter your password)</comment> |
5057 |
</pre> |
5058 |
|
5059 |
<p> |
5060 |
To create a user account, we first enter their credentials, followed by |
5061 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
5062 |
In the next example, we create a user called "john". |
5063 |
</p> |
5064 |
|
5065 |
<pre caption="Creating a user account"> |
5066 |
# <i>useradd -m -G users john</i> |
5067 |
# <i>passwd john</i> |
5068 |
New password: <comment>(Enter john's password)</comment> |
5069 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
5070 |
</pre> |
5071 |
|
5072 |
<p> |
5073 |
You can change your user id from root to the newly created user by using |
5074 |
<c>su</c>: |
5075 |
</p> |
5076 |
|
5077 |
<pre caption="Changing user id"> |
5078 |
# <i>su - john</i> |
5079 |
</pre> |
5080 |
|
5081 |
</body> |
5082 |
</subsection> |
5083 |
<subsection> |
5084 |
<title>Optional: Viewing Documentation while Installing</title> |
5085 |
<body> |
5086 |
|
5087 |
<p> |
5088 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
5089 |
installation, make sure you have created a user account (see <uri |
5090 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
5091 |
go to a new terminal and log in. |
5092 |
</p> |
5093 |
|
5094 |
<p> |
5095 |
If you want to view the documentation on the CD you can immediately run |
5096 |
<c>lynx</c> to read it: |
5097 |
</p> |
5098 |
|
5099 |
<pre caption="Viewing the on-CD documentation"> |
5100 |
# <i>lynx /mnt/cdrom/docs/html/index.html</i> |
5101 |
</pre> |
5102 |
|
5103 |
<p> |
5104 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
5105 |
more recent than the one provided on the CD. You can view it using <c>lynx</c> |
5106 |
as well, but only after having completed the <e>Configuring your Network</e> |
5107 |
chapter (otherwise you won't be able to go on the Internet to view the |
5108 |
document): |
5109 |
</p> |
5110 |
|
5111 |
<pre caption="Viewing the Online Documentation"> |
5112 |
# <i>lynx http://www.gentoo.org/doc/en/handbook/handbook-alpha.xml</i> |
5113 |
</pre> |
5114 |
|
5115 |
<p> |
5116 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
5117 |
</p> |
5118 |
|
5119 |
</body> |
5120 |
</subsection> |
5121 |
<subsection> |
5122 |
<title>Optional: Starting the SSH Daemon</title> |
5123 |
<body> |
5124 |
|
5125 |
<p> |
5126 |
If you want to allow other users to access your computer during the |
5127 |
Gentoo installation (perhaps because those users are going to help you |
5128 |
install Gentoo, or even do it for you), you need to create a user |
5129 |
account for them and perhaps even provide them with your root password |
5130 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
5131 |
</p> |
5132 |
|
5133 |
<p> |
5134 |
To fire up the SSH daemon, execute the following command: |
5135 |
</p> |
5136 |
|
5137 |
<pre caption="Starting the SSH daemon"> |
5138 |
# <i>/etc/init.d/sshd start</i> |
5139 |
</pre> |
5140 |
|
5141 |
<p> |
5142 |
To be able to use sshd, you first need to set up your networking. Continue with |
5143 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
5144 |
</p> |
5145 |
|
5146 |
</body> |
5147 |
</subsection> |
5148 |
</section> |
5149 |
</sections> |
5150 |
|
5151 |
|
5152 |
|
5153 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-config.xml |
5154 |
|
5155 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-config.xml?rev=1.1&view=markup |
5156 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-config.xml?rev=1.1&content-type=text/plain |
5157 |
|
5158 |
Index: hb-install-config.xml |
5159 |
=================================================================== |
5160 |
<?xml version='1.0' encoding='UTF-8'?> |
5161 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
5162 |
|
5163 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
5164 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
5165 |
|
5166 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-config.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
5167 |
|
5168 |
<sections> |
5169 |
|
5170 |
<version>7.5</version> |
5171 |
<date>2007-03-12</date> |
5172 |
|
5173 |
<section> |
5174 |
<title>Filesystem Information</title> |
5175 |
<subsection> |
5176 |
<title>What is fstab?</title> |
5177 |
<body> |
5178 |
|
5179 |
<p> |
5180 |
Under Linux, all partitions used by the system must be listed in |
5181 |
<path>/etc/fstab</path>. This file contains the mountpoints of those partitions |
5182 |
(where they are seen in the file system structure), how they should be mounted |
5183 |
and with what special options (automatically or not, whether users can mount |
5184 |
them or not, etc.) |
5185 |
</p> |
5186 |
|
5187 |
</body> |
5188 |
</subsection> |
5189 |
<subsection> |
5190 |
<title>Creating /etc/fstab</title> |
5191 |
<body> |
5192 |
|
5193 |
<p> |
5194 |
<path>/etc/fstab</path> uses a special syntax. Every line consists of six |
5195 |
fields, separated by whitespace (space(s), tabs or a mixture). Each field has |
5196 |
its own meaning: |
5197 |
</p> |
5198 |
|
5199 |
<ul> |
5200 |
<li> |
5201 |
The first field shows the <b>partition</b> described (the path to the device |
5202 |
file) |
5203 |
</li> |
5204 |
<li> |
5205 |
The second field shows the <b>mountpoint</b> at which the partition should be |
5206 |
mounted |
5207 |
</li> |
5208 |
<li> |
5209 |
The third field shows the <b>filesystem</b> used by the partition |
5210 |
</li> |
5211 |
<li> |
5212 |
The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it |
5213 |
wants to mount the partition. As every filesystem has its own mountoptions, |
5214 |
you are encouraged to read the mount man page (<c>man mount</c>) for a full |
5215 |
listing. Multiple mountoptions are comma-separated. |
5216 |
</li> |
5217 |
<li> |
5218 |
The fifth field is used by <c>dump</c> to determine if the partition needs to |
5219 |
be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero). |
5220 |
</li> |
5221 |
<li> |
5222 |
The sixth field is used by <c>fsck</c> to determine the order in which |
5223 |
filesystems should be <b>check</b>ed if the system wasn't shut down properly. |
5224 |
The root filesystem should have <c>1</c> while the rest should have <c>2</c> |
5225 |
(or <c>0</c> if a filesystem check isn't necessary). |
5226 |
</li> |
5227 |
</ul> |
5228 |
|
5229 |
<p> |
5230 |
The default <path>/etc/fstab</path> file provided by Gentoo <e>is not a valid |
5231 |
fstab file</e>, so start <c>nano</c> (or your favorite editor) to create your |
5232 |
<path>/etc/fstab</path>: |
5233 |
</p> |
5234 |
|
5235 |
<pre caption="Opening /etc/fstab"> |
5236 |
# <i>nano -w /etc/fstab</i> |
5237 |
</pre> |
5238 |
|
5239 |
<p> |
5240 |
Let us take a look at how we write down the options for the <path>/boot</path> |
5241 |
partition. If your architecture doesn't require a seperate <path>/boot</path> |
5242 |
partition (such as Apple PowerPC machines) or you have elected not to create |
5243 |
one, don't include a boot line in your fstab. The Apple Bootstrap partition |
5244 |
is not a <path>/boot</path> partition. |
5245 |
</p> |
5246 |
|
5247 |
<p> |
5248 |
In our default x86 partitioning example <path>/boot</path> is the |
5249 |
<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. |
5250 |
It needs to be checked during boot, so we would write down: |
5251 |
</p> |
5252 |
|
5253 |
<pre caption="An example /boot line for /etc/fstab"> |
5254 |
/dev/hda1 /boot ext2 defaults 1 2 |
5255 |
</pre> |
5256 |
|
5257 |
<p> |
5258 |
Some users don't want their <path>/boot</path> partition to be mounted |
5259 |
automatically to improve their system's security. Those people should |
5260 |
substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to |
5261 |
manually mount this partition every time you want to use it. |
5262 |
</p> |
5263 |
|
5264 |
<p> |
5265 |
Now, to improve performance, most users would want to add the <c>noatime</c> |
5266 |
option as mountoption, which results in a faster system since access times |
5267 |
aren't registered (you don't need those generally anyway): |
5268 |
</p> |
5269 |
|
5270 |
<pre caption="An improved /boot line for /etc/fstab"> |
5271 |
/dev/hda1 /boot ext2 defaults,noatime 1 2 |
5272 |
</pre> |
5273 |
|
5274 |
<p> |
5275 |
If we continue with this, we would end up with the following three lines (for |
5276 |
<path>/boot</path>, <path>/</path> and the swap partition): |
5277 |
</p> |
5278 |
|
5279 |
<pre caption="Three /etc/fstab lines"> |
5280 |
/dev/hda1 /boot ext2 defaults,noatime 1 2 |
5281 |
/dev/hda2 none swap sw 0 0 |
5282 |
/dev/hda3 / ext3 noatime 0 1 |
5283 |
</pre> |
5284 |
|
5285 |
<p> |
5286 |
To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c> |
5287 |
(required) and for your CD-ROM drive (and of course, if you have other |
5288 |
partitions or drives, for those too): |
5289 |
</p> |
5290 |
|
5291 |
<pre caption="A full /etc/fstab example"> |
5292 |
/dev/hda1 /boot ext2 defaults,noatime 1 2 |
5293 |
/dev/hda2 none swap sw 0 0 |
5294 |
/dev/hda3 / ext3 noatime 0 1 |
5295 |
|
5296 |
proc /proc proc defaults 0 0 |
5297 |
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
5298 |
|
5299 |
/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 |
5300 |
</pre> |
5301 |
|
5302 |
<p> |
5303 |
<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for |
5304 |
removable media as they can be created with one of many filesystems) and |
5305 |
<c>user</c> makes it possible for non-root users to mount the CD. |
5306 |
</p> |
5307 |
|
5308 |
<p> |
5309 |
Now use the above example to create your <path>/etc/fstab</path>. If you are a |
5310 |
<b>SPARC</b>-user, you should add the following line to your |
5311 |
<path>/etc/fstab</path> |
5312 |
too: |
5313 |
</p> |
5314 |
|
5315 |
<pre caption="Adding openprom filesystem to /etc/fstab"> |
5316 |
openprom /proc/openprom openpromfs defaults 0 0 |
5317 |
</pre> |
5318 |
|
5319 |
<p> |
5320 |
Double-check your <path>/etc/fstab</path>, save and quit to continue. |
5321 |
</p> |
5322 |
|
5323 |
</body> |
5324 |
</subsection> |
5325 |
</section> |
5326 |
<section> |
5327 |
<title>Networking Information</title> |
5328 |
<subsection> |
5329 |
<title>Hostname, Domainname etc.</title> |
5330 |
<body> |
5331 |
|
5332 |
<p> |
5333 |
One of the choices the user has to make is name his/her PC. This seems to be |
5334 |
quite easy, but <e>lots</e> of users are having difficulties finding the |
5335 |
appropriate name for their Linux-pc. To speed things up, know that any name you |
5336 |
choose can be changed afterwards. For all we care, you can just call your system |
5337 |
<c>tux</c> and domain <c>homenetwork</c>. |
5338 |
</p> |
5339 |
|
5340 |
<p> |
5341 |
We use these values in the next examples. First we set the hostname: |
5342 |
</p> |
5343 |
|
5344 |
<pre caption="Setting the hostname"> |
5345 |
# <i>nano -w /etc/conf.d/hostname</i> |
5346 |
|
5347 |
<comment>(Set the HOSTNAME variable to your hostname)</comment> |
5348 |
HOSTNAME="<i>tux</i>" |
5349 |
</pre> |
5350 |
|
5351 |
<p> |
5352 |
Second, <e>if</e> you need a domainname, set it in <path>/etc/conf.d/net</path>. |
5353 |
You only need a domain if your ISP or network administrator says so, or if you |
5354 |
have a DNS server but not a DHCP server. You don't need to worry about DNS or |
5355 |
domainnames if your networking is setup for DHCP. |
5356 |
</p> |
5357 |
|
5358 |
<pre caption="Setting the domainname"> |
5359 |
# <i>nano -w /etc/conf.d/net</i> |
5360 |
|
5361 |
<comment>(Set the dns_domain variable to your domain name)</comment> |
5362 |
dns_domain_lo="<i>homenetwork</i>" |
5363 |
</pre> |
5364 |
|
5365 |
<p> |
5366 |
If you have a NIS domain (if you don't know what that is, then you don't have |
5367 |
one), you need to define that one too: |
5368 |
</p> |
5369 |
|
5370 |
<pre caption="Setting the NIS domainname"> |
5371 |
# <i>nano -w /etc/conf.d/net</i> |
5372 |
|
5373 |
<comment>(Set the nis_domain variable to your NIS domain name)</comment> |
5374 |
nis_domain_lo="<i>my-nisdomain</i>" |
5375 |
</pre> |
5376 |
|
5377 |
<note> |
5378 |
For more information on configuring DNS and NIS, please read the examples |
5379 |
provided in <path>/etc/conf.d/net.example</path>. Also, you may want to emerge |
5380 |
<c>resolvconf-gentoo</c> to help manage your DNS/NIS setup. |
5381 |
</note> |
5382 |
|
5383 |
</body> |
5384 |
</subsection> |
5385 |
<subsection> |
5386 |
<title>Configuring your Network</title> |
5387 |
<body> |
5388 |
|
5389 |
<p> |
5390 |
Before you get that "Hey, we've had that already"-feeling, you should remember |
5391 |
that the networking you set up in the beginning of the Gentoo installation was |
5392 |
just for the installation. Right now you are going to configure networking for |
5393 |
your Gentoo system permanently. |
5394 |
</p> |
5395 |
|
5396 |
<note> |
5397 |
More detailed information about networking, including advanced topics like |
5398 |
bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri |
5399 |
link="?part=4">Gentoo Network Configuration</uri> section. |
5400 |
</note> |
5401 |
|
5402 |
<p> |
5403 |
All networking information is gathered in <path>/etc/conf.d/net</path>. It uses |
5404 |
a straightforward yet not intuitive syntax if you don't know how to set up |
5405 |
networking manually. But don't fear, we'll explain everything. A fully |
5406 |
commented example that covers many different configurations is available in |
5407 |
<path>/etc/conf.d/net.example</path>. |
5408 |
</p> |
5409 |
|
5410 |
<p> |
5411 |
DHCP is used by default and does not require any further configuration. |
5412 |
</p> |
5413 |
|
5414 |
<p> |
5415 |
If you need to configure your network connection either because you need |
5416 |
specific DHCP options or because you do not use DHCP at all, open |
5417 |
<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in |
5418 |
this example): |
5419 |
</p> |
5420 |
|
5421 |
<pre caption="Opening /etc/conf.d/net for editing"> |
5422 |
# <i>nano -w /etc/conf.d/net</i> |
5423 |
</pre> |
5424 |
|
5425 |
<p> |
5426 |
You will see the following file: |
5427 |
</p> |
5428 |
|
5429 |
<pre caption="Default /etc/conf.d/net"> |
5430 |
# This blank configuration will automatically use DHCP for any net.* |
5431 |
# scripts in /etc/init.d. To create a more complete configuration, |
5432 |
# please review /etc/conf.d/net.example and save your configuration |
5433 |
# in /etc/conf.d/net (this file :]!). |
5434 |
</pre> |
5435 |
|
5436 |
<p> |
5437 |
To enter your own IP address, netmask and gateway, you need |
5438 |
to set both <c>config_eth0</c> and <c>routes_eth0</c>: |
5439 |
</p> |
5440 |
|
5441 |
<pre caption="Manually setting IP information for eth0"> |
5442 |
config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" ) |
5443 |
routes_eth0=( "default gw 192.168.0.1" ) |
5444 |
</pre> |
5445 |
|
5446 |
<p> |
5447 |
To use DHCP and add specific DHCP options, define <c>config_eth0</c> and |
5448 |
<c>dhcp_eth0</c>: |
5449 |
</p> |
5450 |
|
5451 |
<pre caption="Automatically obtaining an IP address for eth0"> |
5452 |
config_eth0=( "dhcp" ) |
5453 |
dhcp_eth0="nodns nontp nonis" |
5454 |
</pre> |
5455 |
|
5456 |
<p> |
5457 |
Please read <path>/etc/conf.d/net.example</path> for a list of all available |
5458 |
options. |
5459 |
</p> |
5460 |
|
5461 |
<p> |
5462 |
If you have several network interfaces repeat the above steps for |
5463 |
<c>config_eth1</c>, <c>config_eth2</c>, etc. |
5464 |
</p> |
5465 |
|
5466 |
<p> |
5467 |
Now save the configuration and exit to continue. |
5468 |
</p> |
5469 |
|
5470 |
</body> |
5471 |
</subsection> |
5472 |
<subsection> |
5473 |
<title>Automatically Start Networking at Boot</title> |
5474 |
<body> |
5475 |
|
5476 |
<p> |
5477 |
To have your network interfaces activated at boot, you need to add them to the |
5478 |
default runlevel. If you have PCMCIA interfaces you should skip this action as |
5479 |
the PCMCIA interfaces are started by the PCMCIA init script. |
5480 |
</p> |
5481 |
|
5482 |
<pre caption="Adding net.eth0 to the default runlevel"> |
5483 |
# <i>rc-update add net.eth0 default</i> |
5484 |
</pre> |
5485 |
|
5486 |
<p> |
5487 |
If you have several network interfaces, you need to create the appropriate |
5488 |
<path>net.eth1</path>, <path>net.eth2</path> etc. initscripts for those. You can |
5489 |
use <c>ln</c> to do this: |
5490 |
</p> |
5491 |
|
5492 |
<pre caption="Creating extra initscripts"> |
5493 |
# <i>cd /etc/init.d</i> |
5494 |
# <i>ln -s net.lo net.eth1</i> |
5495 |
# <i>rc-update add net.eth1 default</i> |
5496 |
</pre> |
5497 |
|
5498 |
</body> |
5499 |
</subsection> |
5500 |
<subsection> |
5501 |
<title>Writing Down Network Information</title> |
5502 |
<body> |
5503 |
|
5504 |
<p> |
5505 |
You now need to inform Linux about your network. This is defined in |
5506 |
<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses for |
5507 |
hosts that aren't resolved by your nameserver. You need to define your system. |
5508 |
You may also want to define other systems on your network if you don't want to |
5509 |
set up your own internal DNS system. |
5510 |
</p> |
5511 |
|
5512 |
<pre caption="Opening /etc/hosts"> |
5513 |
# <i>nano -w /etc/hosts</i> |
5514 |
</pre> |
5515 |
|
5516 |
<pre caption="Filling in the networking information"> |
5517 |
<comment>(This defines the current system)</comment> |
5518 |
127.0.0.1 tux.homenetwork tux localhost |
5519 |
|
5520 |
<comment>(Define extra systems on your network, |
5521 |
they need to have a static IP to be defined this way.)</comment> |
5522 |
192.168.0.5 jenny.homenetwork jenny |
5523 |
192.168.0.6 benny.homenetwork benny |
5524 |
</pre> |
5525 |
|
5526 |
<p> |
5527 |
Save and exit the editor to continue. |
5528 |
</p> |
5529 |
|
5530 |
<p> |
5531 |
If you don't have PCMCIA, you can now continue with <uri |
5532 |
link="#doc_chap3">System Information</uri>. PCMCIA-users should read the |
5533 |
following topic on PCMCIA. |
5534 |
</p> |
5535 |
|
5536 |
</body> |
5537 |
</subsection> |
5538 |
<subsection> |
5539 |
<title>Optional: Get PCMCIA Working</title> |
5540 |
<body> |
5541 |
|
5542 |
<note> |
5543 |
pcmcia-cs is only available for x86, amd64 and ppc platforms. |
5544 |
</note> |
5545 |
|
5546 |
<p> |
5547 |
PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also |
5548 |
includes users who will be working with a 2.6 kernel (even though they won't be |
5549 |
using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary |
5550 |
to avoid installing xorg-x11 at this moment: |
5551 |
</p> |
5552 |
|
5553 |
<pre caption="Installing pcmcia-cs"> |
5554 |
# <i>USE="-X" emerge pcmcia-cs</i> |
5555 |
</pre> |
5556 |
|
5557 |
<p> |
5558 |
When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e> |
5559 |
runlevel: |
5560 |
</p> |
5561 |
|
5562 |
<pre caption="Adding pcmcia to the default runlevel"> |
5563 |
# <i>rc-update add pcmcia default</i> |
5564 |
</pre> |
5565 |
|
5566 |
</body> |
5567 |
</subsection> |
5568 |
</section> |
5569 |
<section> |
5570 |
<title>System Information</title> |
5571 |
<subsection> |
5572 |
<title>Root Password</title> |
5573 |
<body> |
5574 |
|
5575 |
<p> |
5576 |
First we set the root password by typing: |
5577 |
</p> |
5578 |
|
5579 |
<pre caption="Setting the root password"> |
5580 |
# <i>passwd</i> |
5581 |
</pre> |
5582 |
|
5583 |
<p> |
5584 |
If you want root to be able to log on through the serial console, add |
5585 |
<c>tts/0</c> to <path>/etc/securetty</path>: |
5586 |
</p> |
5587 |
|
5588 |
<pre caption="Adding tts/0 to /etc/securetty"> |
5589 |
# <i>echo "tts/0" >> /etc/securetty</i> |
5590 |
</pre> |
5591 |
|
5592 |
</body> |
5593 |
</subsection> |
5594 |
<subsection> |
5595 |
<title>System Information</title> |
5596 |
<body> |
5597 |
|
5598 |
<p> |
5599 |
Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. |
5600 |
Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :) |
5601 |
</p> |
5602 |
|
5603 |
<pre caption="Opening /etc/rc.conf"> |
5604 |
# <i>nano -w /etc/rc.conf</i> |
5605 |
</pre> |
5606 |
|
5607 |
<p> |
5608 |
When you're finished configuring <path>/etc/rc.conf</path>, save and exit. |
5609 |
</p> |
5610 |
|
5611 |
<p> |
5612 |
As you can see, this file is well commented to help you set up the necessary |
5613 |
configuration variables. You can configure your system to use unicode and |
5614 |
define your default editor and your display manager (like gdm or kdm). |
5615 |
</p> |
5616 |
|
5617 |
<p> |
5618 |
Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration. |
5619 |
Edit it to configure your keyboard. |
5620 |
</p> |
5621 |
|
5622 |
<pre caption="Opening /etc/conf.d/keymaps"> |
5623 |
# <i>nano -w /etc/conf.d/keymaps</i> |
5624 |
</pre> |
5625 |
|
5626 |
<p> |
5627 |
Take special care with the <c>KEYMAP</c> variable. If you select the wrong |
5628 |
<c>KEYMAP</c>, you will get weird results when typing on your keyboard. |
5629 |
</p> |
5630 |
|
5631 |
<note> |
5632 |
Users of <b>SPARC</b> systems and <b>SPARC</b> clones should choose old-style, |
5633 |
sparc-specific keymaps if they have 2.4 kernel. But if you go for 2.6 kernel |
5634 |
(which is default), you should rather choose pc-style i386 keymaps (like "us"). |
5635 |
<b>PPC</b> uses x86 keymaps on most systems. Users who want to be able to use |
5636 |
ADB keymaps on boot have to enable ADB keycode sendings in their kernel and |
5637 |
have to set a mac/ppc keymap in <path>/etc/conf.d/keymaps</path>. |
5638 |
</note> |
5639 |
|
5640 |
<p> |
5641 |
When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and |
5642 |
exit. |
5643 |
</p> |
5644 |
|
5645 |
<p> |
5646 |
Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it |
5647 |
according to your needs. |
5648 |
</p> |
5649 |
|
5650 |
<pre caption="Opening /etc/conf.d/clock"> |
5651 |
# <i>nano -w /etc/conf.d/clock</i> |
5652 |
</pre> |
5653 |
|
5654 |
<p> |
5655 |
If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to |
5656 |
the file. Otherwise you will notice some clock skew. |
5657 |
</p> |
5658 |
|
5659 |
<p> |
5660 |
When you're finished configuring <path>/etc/conf.d/clock</path>, save and |
5661 |
exit. |
5662 |
</p> |
5663 |
|
5664 |
<p> |
5665 |
If you are not installing Gentoo on IBM PPC64 hardware, continue with |
5666 |
<uri link="?part=1&chap=9">Installing Necessary System Tools</uri>. |
5667 |
</p> |
5668 |
|
5669 |
</body> |
5670 |
</subsection> |
5671 |
<subsection> |
5672 |
<title>Configuring the Console</title> |
5673 |
<body> |
5674 |
|
5675 |
<note> |
5676 |
The following section applies to the IBM PPC64 hardware platforms. |
5677 |
</note> |
5678 |
|
5679 |
<p> |
5680 |
If you are running Gentoo on IBM PPC64 hardware and using a virtual console |
5681 |
you must uncomment the appropriate line in <path>/etc/inittab</path> for the |
5682 |
virtual console to spawn a login prompt. |
5683 |
</p> |
5684 |
|
5685 |
<pre caption="Enabling hvc or hvsi support in /etc/inittab"> |
5686 |
hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0 |
5687 |
hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0 |
5688 |
</pre> |
5689 |
|
5690 |
<p> |
5691 |
You should also take this time to verify that the appropriate console is |
5692 |
listed in <path>/etc/securetty</path>. |
5693 |
</p> |
5694 |
|
5695 |
<p> |
5696 |
You may now continue with <uri link="?part=1&chap=9">Installing Necessary |
5697 |
System Tools</uri>. |
5698 |
</p> |
5699 |
|
5700 |
</body> |
5701 |
</subsection> |
5702 |
</section> |
5703 |
</sections> |
5704 |
|
5705 |
|
5706 |
|
5707 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-installer-about.xml |
5708 |
|
5709 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-installer-about.xml?rev=1.1&view=markup |
5710 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-installer-about.xml?rev=1.1&content-type=text/plain |
5711 |
|
5712 |
Index: hb-installer-about.xml |
5713 |
=================================================================== |
5714 |
<?xml version='1.0' encoding='UTF-8'?> |
5715 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
5716 |
|
5717 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
5718 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
5719 |
|
5720 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-installer-about.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
5721 |
|
5722 |
<sections> |
5723 |
|
5724 |
<version>2.0</version> |
5725 |
<date>2006-08-30</date> |
5726 |
|
5727 |
<section> |
5728 |
<title>Introduction</title> |
5729 |
<subsection> |
5730 |
<title>Welcome!</title> |
5731 |
<body> |
5732 |
|
5733 |
<p> |
5734 |
First of all, <e>welcome</e> to Gentoo. You are about to enter the world |
5735 |
of customization and performance. When installing Gentoo, this is made clear to |
5736 |
you several times -- you can choose how much you want to compile yourself, how |
5737 |
to install Gentoo, what system logger you want, etc. |
5738 |
</p> |
5739 |
|
5740 |
<p> |
5741 |
Gentoo is a fast, modern meta-distribution with a clean and flexible |
5742 |
design. Gentoo is built around free software and doesn't hide from its |
5743 |
users what is beneath the hood. Portage, the package maintenance system |
5744 |
which Gentoo uses, is written in Python, meaning you can easily view and |
5745 |
modify the source code. Gentoo's packaging system uses source code |
5746 |
(although support for precompiled packages is included too) and |
5747 |
configuring Gentoo happens through regular text files. In other words, |
5748 |
openness everywhere. |
5749 |
</p> |
5750 |
|
5751 |
<p> |
5752 |
It is very important that you understand that <e>empowerment</e> is what makes |
5753 |
Gentoo run. We try not to force anything on our users and try our best to |
5754 |
empower you to make the choices you wish. If you feel a change should be made, |
5755 |
please file a <uri link="http://bugs.gentoo.org">bug report</uri> about it. |
5756 |
</p> |
5757 |
|
5758 |
</body> |
5759 |
</subsection> |
5760 |
<subsection> |
5761 |
<title>How do I go about Installing Gentoo?</title> |
5762 |
<body> |
5763 |
|
5764 |
<p> |
5765 |
Gentoo Linux comes with two versions of an easy to use Installer. A GTK+ based |
5766 |
installer (for use with an X based environment) and a Dialog based installer for |
5767 |
use on the console. Chapter 3 of the handbook deals with the GTK+ based |
5768 |
installer while Chapter 4 is for the Dialog based one. |
5769 |
</p> |
5770 |
|
5771 |
<p> |
5772 |
Sometimes, you are given a certain choice in the handbook. We try our best to |
5773 |
explain what the pros and cons are. We will continue then with a default choice, |
5774 |
identified by "Default: " in the title. The other possibilities are |
5775 |
marked by "Alternative: ". Do <e>not</e> think that the default is |
5776 |
what we recommend. It is however what we believe most users will use. |
5777 |
</p> |
5778 |
|
5779 |
<p> |
5780 |
Sometimes you can pursue an optional step. Such steps are marked as |
5781 |
"Optional: " and are therefore not needed to install Gentoo. |
5782 |
However, some optional steps are dependant on a previous decision you |
5783 |
made. We will inform you when this happens, both when you make the |
5784 |
decision, and right before the optional step is described. |
5785 |
</p> |
5786 |
|
5787 |
</body> |
5788 |
</subsection> |
5789 |
<subsection> |
5790 |
<title>What are my Options?</title> |
5791 |
<body> |
5792 |
|
5793 |
<p> |
5794 |
You can install Gentoo in many different ways. You can download and install from |
5795 |
one of our Installation CDs, from an existing distribution, from a bootable CD |
5796 |
(such as Knoppix), from a netbooted environment, from a rescue floppy, etc. |
5797 |
</p> |
5798 |
|
5799 |
<p> |
5800 |
This document covers the installation using a Gentoo Linux Installation CD, a |
5801 |
bootable CD that contains everything you need to get Gentoo Linux up and |
5802 |
running. There are two types of Installation CDs, the InstallCD and the |
5803 |
Installer LiveCD. The InstallCD is a minimal environment which contains only |
5804 |
those packages necessary for installing Gentoo Linux. The LiveCD is a complete |
5805 |
Gentoo Linux environment and can be used for multiple tasks, one of which is |
5806 |
installing Gentoo Linux. The LiveCD is not available on all architectures at |
5807 |
this time. If your architecture does not have a LiveCD, then this document will |
5808 |
refer to the Universal InstallCD for you. |
5809 |
</p> |
5810 |
|
5811 |
<p> |
5812 |
This installation approach however does not immediately use the latest version |
5813 |
of the available packages; if you want this you should check out the |
5814 |
Installation Instructions inside our <uri |
5815 |
link="/doc/en/handbook/index.xml">Gentoo Linux Handbooks</uri>. |
5816 |
</p> |
5817 |
|
5818 |
<p> |
5819 |
For help on the other installation approaches, |
5820 |
please read our <uri link="/doc/en/altinstall.xml">Alternative Installation |
5821 |
Guide</uri>. We also provide a <uri |
5822 |
link="/doc/en/gentoo-x86-tipsntricks.xml">Gentoo Installation Tips & |
5823 |
Tricks</uri> document that might be useful to read as well. If you feel that |
5824 |
the current installation instructions are too elaborate, feel free to use our |
5825 |
Quick Installation Guide available from our <uri |
5826 |
link="/doc/en/index.xml">Documentation Resources</uri> if your architecture |
5827 |
has such a document available. |
5828 |
</p> |
5829 |
|
5830 |
</body> |
5831 |
</subsection> |
5832 |
<subsection> |
5833 |
<title>Troubles?</title> |
5834 |
<body> |
5835 |
|
5836 |
<p> |
5837 |
If you find a problem in the installation (or in the installation |
5838 |
documentation), please check the errata from our <uri |
5839 |
link="/proj/en/releng/">Gentoo Release Engineering Project</uri>, |
5840 |
visit our <uri link="http://bugs.gentoo.org">bug tracking |
5841 |
system</uri> and check if the bug is known. If not, please create a bug report |
5842 |
for it so we can take care of it. Do not be afraid of the developers who are |
5843 |
assigned to (your) bugs -- they generally don't eat people. |
5844 |
</p> |
5845 |
|
5846 |
<p> |
5847 |
Note though that, although the document you are now reading is |
5848 |
architecture-specific, it will contain references to other architectures as |
5849 |
well. This is due to the fact that large parts of the Gentoo Handbook use source |
5850 |
code that is common for all architectures (to avoid duplication of efforts and |
5851 |
starvation of development resources). We will try to keep this to a minimum |
5852 |
to avoid confusion. |
5853 |
</p> |
5854 |
|
5855 |
<p> |
5856 |
If you are uncertain if the problem is a user-problem (some error you |
5857 |
made despite having read the documentation carefully) or a |
5858 |
software-problem (some error we made despite having tested the |
5859 |
installation/documentation carefully) you are free to join #gentoo on |
5860 |
irc.freenode.net. Of course, you are welcome otherwise too :) |
5861 |
</p> |
5862 |
|
5863 |
<p> |
5864 |
If you have a question regarding Gentoo, check out our <uri |
5865 |
link="/doc/en/faq.xml">Frequently Asked |
5866 |
Questions</uri>, available from the <uri |
5867 |
link="/doc/en/">Gentoo Documentation</uri>. You can |
5868 |
also view the <uri |
5869 |
link="http://forums.gentoo.org/viewforum.php?f=40">FAQs</uri> on our |
5870 |
<uri link="http://forums.gentoo.org">forums</uri>. If you can't find the answer |
5871 |
there ask on #gentoo, our IRC-channel on irc.freenode.net. Yes, several of |
5872 |
us are freaks who sit on IRC :-) |
5873 |
</p> |
5874 |
|
5875 |
</body> |
5876 |
</subsection> |
5877 |
</section> |
5878 |
<section> |
5879 |
<title>Fast Installation using the Gentoo Reference Platform</title> |
5880 |
<subsection> |
5881 |
<title>What is the Gentoo Reference Platform?</title> |
5882 |
<body> |
5883 |
|
5884 |
<p> |
5885 |
The Gentoo Reference Platform, from now on abbreviated to GRP, is a snapshot of |
5886 |
prebuilt packages users (that means you!) can install during the installation |
5887 |
of Gentoo to speed up the installation process. The GRP consists of all |
5888 |
packages required to have a fully functional Gentoo installation. They are not |
5889 |
just the ones you need to have a base installation up to speed in no time, but |
5890 |
all lengthier builds (such as xorg-x11, GNOME, OpenOffice, Mozilla, ...) |
5891 |
are available as GRP packages too. |
5892 |
</p> |
5893 |
|
5894 |
<p> |
5895 |
However, these prebuilt packages aren't maintained during the lifetime of the |
5896 |
Gentoo distribution. They are snapshots released at every Gentoo release and |
5897 |
make it possible to have a functional environment in a short amount of time. You |
5898 |
can then upgrade your system in the background while working in your Gentoo |
5899 |
environment. |
5900 |
</p> |
5901 |
|
5902 |
</body> |
5903 |
</subsection> |
5904 |
<subsection> |
5905 |
<title>How Portage Handles GRP Packages</title> |
5906 |
<body> |
5907 |
|
5908 |
<p> |
5909 |
Your Portage tree - the collection of <e>ebuilds</e> (files that contain all |
5910 |
information about a package, such as its description, homepage, sourcecode URLs, |
5911 |
compilation instructions, dependencies, etc.) - must be synchronised with the |
5912 |
GRP set: the versions of the available ebuilds and their accompanying GRP |
5913 |
packages must match. |
5914 |
</p> |
5915 |
|
5916 |
<p> |
5917 |
For this reason you can only benefit from the GRP packages Gentoo provides while |
5918 |
performing the current installation approach. GRP is not available for those |
5919 |
interested in performing an installation using the latest versions of all |
5920 |
available packages. |
5921 |
</p> |
5922 |
|
5923 |
</body> |
5924 |
</subsection> |
5925 |
<subsection> |
5926 |
<title>Is GRP Available?</title> |
5927 |
<body> |
5928 |
|
5929 |
<p> |
5930 |
Not all architectures provide GRP packages. That doesn't mean GRP isn't |
5931 |
supported on the other architectures, but it means that we don't have the |
5932 |
resources to build and test the GRP packages. |
5933 |
</p> |
5934 |
|
5935 |
<p> |
5936 |
At present we provide GRP packages for the following architectures: |
5937 |
</p> |
5938 |
|
5939 |
<ul> |
5940 |
<li> |
5941 |
The <b>amd64</b> architecture (amd64) |
5942 |
</li> |
5943 |
<li> |
5944 |
The <b>ppc</b> architecture (ppc32, ppc64) |
5945 |
</li> |
5946 |
<li> |
5947 |
The <b>sparc</b> architecture (sparc64) |
5948 |
</li> |
5949 |
<li> |
5950 |
The <b>x86</b> architecture (athlon, athlon-xp, athlon-mp, pentium-pro, |
5951 |
pentium2, pentium3, pentium4 and pentium-m) Note: The packages are for i686 |
5952 |
and are available on the Installer LiveCD. |
5953 |
</li> |
5954 |
</ul> |
5955 |
|
5956 |
<p> |
5957 |
If your architecture (or subarchitecture) isn't on this list, you are not |
5958 |
able to opt for a GRP installation. |
5959 |
</p> |
5960 |
|
5961 |
<p> |
5962 |
Now that this introduction is over, let's continue with <uri |
5963 |
link="?part=1&chap=2">Booting the Universal InstallCD/Installer |
5964 |
LiveCD</uri>. |
5965 |
</p> |
5966 |
|
5967 |
</body> |
5968 |
</subsection> |
5969 |
</section> |
5970 |
</sections> |
5971 |
|
5972 |
|
5973 |
|
5974 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-finalise.xml |
5975 |
|
5976 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-finalise.xml?rev=1.1&view=markup |
5977 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-finalise.xml?rev=1.1&content-type=text/plain |
5978 |
|
5979 |
Index: hb-install-finalise.xml |
5980 |
=================================================================== |
5981 |
<?xml version='1.0' encoding='UTF-8'?> |
5982 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
5983 |
|
5984 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
5985 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
5986 |
|
5987 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-finalise.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
5988 |
|
5989 |
<sections> |
5990 |
|
5991 |
<version>7.0</version> |
5992 |
<date>2006-08-30</date> |
5993 |
|
5994 |
<section> |
5995 |
<title>User Administration</title> |
5996 |
<subsection> |
5997 |
<title>Adding a User for Daily Use</title> |
5998 |
<body> |
5999 |
|
6000 |
<p> |
6001 |
Working as root on a Unix/Linux system is <e>dangerous</e> and should be avoided |
6002 |
as much as possible. Therefore it is <e>strongly</e> recommended to add a user |
6003 |
for day-to-day use. |
6004 |
</p> |
6005 |
|
6006 |
<p> |
6007 |
The groups the user is member of define what activities the user can perform. |
6008 |
The following table lists a number of important groups you might wish to use: |
6009 |
</p> |
6010 |
|
6011 |
<table> |
6012 |
<tr> |
6013 |
<th>Group</th> |
6014 |
<th>Description</th> |
6015 |
</tr> |
6016 |
<tr> |
6017 |
<ti>audio</ti> |
6018 |
<ti>be able to access the audio devices</ti> |
6019 |
</tr> |
6020 |
<tr> |
6021 |
<ti>cdrom</ti> |
6022 |
<ti>be able to directly access optical devices</ti> |
6023 |
</tr> |
6024 |
<tr> |
6025 |
<ti>floppy</ti> |
6026 |
<ti>be able to directly access floppy devices</ti> |
6027 |
</tr> |
6028 |
<tr> |
6029 |
<ti>games</ti> |
6030 |
<ti>be able to play games</ti> |
6031 |
</tr> |
6032 |
<tr> |
6033 |
<ti>portage</ti> |
6034 |
<ti>be able to use <c>emerge --pretend</c> as a normal user</ti> |
6035 |
</tr> |
6036 |
<tr> |
6037 |
<ti>usb</ti> |
6038 |
<ti>be able to access USB devices</ti> |
6039 |
</tr> |
6040 |
<tr> |
6041 |
<ti>plugdev</ti> |
6042 |
<ti> |
6043 |
Be able to mount and use pluggable devices such as cameras and USB sticks |
6044 |
</ti> |
6045 |
</tr> |
6046 |
<tr> |
6047 |
<ti>video</ti> |
6048 |
<ti> |
6049 |
be able to access video capturing hardware and doing hardware |
6050 |
acceleration |
6051 |
</ti> |
6052 |
</tr> |
6053 |
<tr> |
6054 |
<ti>wheel</ti> |
6055 |
<ti>be able to use <c>su</c></ti> |
6056 |
</tr> |
6057 |
</table> |
6058 |
|
6059 |
<p> |
6060 |
For instance, to create a user called <c>john</c> who is member of the |
6061 |
<c>wheel</c>, <c>users</c> and <c>audio</c> groups, log in as root first |
6062 |
(only root can create users) and run <c>useradd</c>: |
6063 |
</p> |
6064 |
|
6065 |
<pre caption="Adding a user for day-to-day use"> |
6066 |
Login: <i>root</i> |
6067 |
Password: <comment>(Your root password)</comment> |
6068 |
|
6069 |
# <i>useradd -m -G users,wheel,audio -s /bin/bash john</i> |
6070 |
# <i>passwd john</i> |
6071 |
Password: <comment>(Enter the password for john)</comment> |
6072 |
Re-enter password: <comment>(Re-enter the password to verify)</comment> |
6073 |
</pre> |
6074 |
|
6075 |
<p> |
6076 |
If a user ever needs to perform some task as root, they can use <c>su -</c> |
6077 |
to temporarily receive root privileges. Another way is to use the <c>sudo</c> |
6078 |
package which is, if correctly configured, very secure. |
6079 |
</p> |
6080 |
|
6081 |
</body> |
6082 |
</subsection> |
6083 |
</section> |
6084 |
<section> |
6085 |
<title>Optional: Install GRP Packages</title> |
6086 |
<body> |
6087 |
|
6088 |
<impo> |
6089 |
This part is for GRP users only. Other users should skip this part and continue |
6090 |
with <uri link="?part=1&chap=12">Where to go from here?</uri>. |
6091 |
</impo> |
6092 |
|
6093 |
<p> |
6094 |
Now that your system is booted, log on as the user you created (for instance, |
6095 |
<c>john</c>) and use <c>su -</c> to gain root privileges: |
6096 |
</p> |
6097 |
|
6098 |
<pre caption="Gaining root privileges"> |
6099 |
$ <i>su -</i> |
6100 |
Password: <comment>(Enter your root password)</comment> |
6101 |
</pre> |
6102 |
|
6103 |
<p> |
6104 |
Now we need to change the Portage configuration to look for the prebuilt |
6105 |
binaries from the second CD (Gentoo Packages CD). First mount this CD: |
6106 |
</p> |
6107 |
|
6108 |
<pre caption="Mount the Packages CD"> |
6109 |
<comment>(Put the Gentoo Packages CD in the CD tray)</comment> |
6110 |
# <i>mount /mnt/cdrom</i> |
6111 |
</pre> |
6112 |
|
6113 |
<p> |
6114 |
Now configure Portage to use <path>/mnt/cdrom</path> for its prebuilt packages: |
6115 |
</p> |
6116 |
|
6117 |
<pre caption="Configuring Portage to use /mnt/cdrom"> |
6118 |
# <i>ls /mnt/cdrom</i> |
6119 |
|
6120 |
<comment>(If there is a /mnt/cdrom/packages directory:)</comment> |
6121 |
# <i>export PKGDIR="/mnt/cdrom/packages"</i> |
6122 |
|
6123 |
<comment>(Otherwise:)</comment> |
6124 |
# <i>export PKGDIR="/mnt/cdrom"</i> |
6125 |
</pre> |
6126 |
|
6127 |
<p> |
6128 |
Now install the packages you want. The Packages CD contains several prebuilt |
6129 |
binaries, for instance KDE and GNOME. |
6130 |
</p> |
6131 |
|
6132 |
<pre caption="Installing GNOME"> |
6133 |
# <i>emerge --usepkg gnome</i> |
6134 |
</pre> |
6135 |
|
6136 |
<p> |
6137 |
To find out what prebuilt packages are available, do a quick listing of all |
6138 |
the files in <path>/mnt/cdrom/All</path>. For instance, to find out if KDE is |
6139 |
emergeable: |
6140 |
</p> |
6141 |
|
6142 |
<pre caption="Finding out if KDE is installable"> |
6143 |
# <i>ls /mnt/cdrom/All/kde*</i> |
6144 |
</pre> |
6145 |
|
6146 |
<p> |
6147 |
Be sure to install the binaries now. When you do an <c>emerge --sync</c> to |
6148 |
update Portage (as you will learn later), the prebuilt binaries might not match |
6149 |
against the ebuilds in your updated Portage. You can try to circumvent this by |
6150 |
using <c>emerge --usepkgonly</c> instead of <c>emerge --usepkg</c>. |
6151 |
</p> |
6152 |
|
6153 |
<p> |
6154 |
Congratulations, your system is now fully equipped! Continue with <uri |
6155 |
link="?part=1&chap=12">Where to go from here?</uri> to learn more about |
6156 |
Gentoo. |
6157 |
</p> |
6158 |
|
6159 |
</body> |
6160 |
</section> |
6161 |
</sections> |
6162 |
|
6163 |
|
6164 |
|
6165 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-gli-dialog.xml |
6166 |
|
6167 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-gli-dialog.xml?rev=1.1&view=markup |
6168 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-gli-dialog.xml?rev=1.1&content-type=text/plain |
6169 |
|
6170 |
Index: hb-install-gli-dialog.xml |
6171 |
=================================================================== |
6172 |
<?xml version='1.0' encoding='UTF-8'?> |
6173 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
6174 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-gli-dialog.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
6175 |
|
6176 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
6177 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
6178 |
|
6179 |
<sections> |
6180 |
|
6181 |
<version>2.1</version> |
6182 |
<date>2006-11-01</date> |
6183 |
|
6184 |
<section> |
6185 |
<title>Welcome</title> |
6186 |
<subsection> |
6187 |
<title>Before you begin</title> |
6188 |
<body> |
6189 |
|
6190 |
<p> |
6191 |
After you boot the Gentoo Linux Installer LiveCD, it will attempt to load a |
6192 |
graphical desktop. If it is unable to do so, it will instead display a command |
6193 |
line prompt. To launch the installer, simply type: |
6194 |
</p> |
6195 |
|
6196 |
<pre caption="Start the installer"> |
6197 |
# <i>installer</i> |
6198 |
</pre> |
6199 |
|
6200 |
<p> |
6201 |
Once the installer has finished loading, you will be greeted by the welcome |
6202 |
screen. It provides a friendly introduction to the process of installing Gentoo |
6203 |
on your computer. Remember to read each option carefully. There is detailed |
6204 |
help available for each step of installation at the top of the screen. We |
6205 |
recommend that you always read the help provided before making your choices. |
6206 |
Note that at any time during the installation process, you can save your |
6207 |
configuration progress in case you need to resume your installation at a later |
6208 |
time. Use the <c>Tab</c> key (on your keyboard) to move around the menus within |
6209 |
a screen and the <c>Enter</c> key to confirm an action. |
6210 |
</p> |
6211 |
|
6212 |
<p> |
6213 |
There are two types of installation modes available. Choose <c>Networkless</c> |
6214 |
to begin installing Gentoo Linux. |
6215 |
</p> |
6216 |
|
6217 |
<note> |
6218 |
Selecting <c>Networkless</c> will make some later configuration options |
6219 |
unavailable. Simply proceed to the next screen. |
6220 |
</note> |
6221 |
|
6222 |
</body> |
6223 |
</subsection> |
6224 |
</section> |
6225 |
|
6226 |
<section> |
6227 |
<title>Preinstallation Configuration</title> |
6228 |
<subsection> |
6229 |
<title>Optional: Manual Network Configuration</title> |
6230 |
<body> |
6231 |
|
6232 |
<p> |
6233 |
Even though you will be installing without a connection to the internet, you |
6234 |
can manually set up connections to your local area network (LAN), in case you |
6235 |
want to install Gentoo from another machine on your LAN. |
6236 |
</p> |
6237 |
|
6238 |
<p> |
6239 |
If you wish to enable SSH access to the machine (for remote installation), you |
6240 |
can start <c>sshd</c> and specify a root password. |
6241 |
</p> |
6242 |
|
6243 |
</body> |
6244 |
</subsection> |
6245 |
<subsection> |
6246 |
<title>Optional: Load Additional Kernel Modules</title> |
6247 |
<body> |
6248 |
|
6249 |
<p> |
6250 |
If you need to load more kernel modules to support your hardware, enter their |
6251 |
names, each separated by a space. |
6252 |
</p> |
6253 |
|
6254 |
</body> |
6255 |
</subsection> |
6256 |
</section> |
6257 |
|
6258 |
<section> |
6259 |
<title>Partitioning</title> |
6260 |
<subsection> |
6261 |
<title>Preparing the disks</title> |
6262 |
<body> |
6263 |
|
6264 |
<p> |
6265 |
In order to install Gentoo on your machine, you will need to prepare your |
6266 |
disks. The <c>Partitioning</c> screen will show you a list of detected disks and |
6267 |
allow you to specify the filesystems you would like to have on your |
6268 |
partitions. Selecting <c>Clear partitions</c> will erase all previous partitions on |
6269 |
your disk, so be careful with this option! It is also possible to resize |
6270 |
certain partition types. |
6271 |
</p> |
6272 |
|
6273 |
<p> |
6274 |
If you choose to go with the <c>Recommended layout</c>, the installer will |
6275 |
create three partitions: 100MB for <path>/boot</path>, a <path>/swap</path> |
6276 |
partition up to 512MB in size, and the rest of the available space on the disk |
6277 |
is used for <path>/</path>, the root partition. If you have more than 4GB of |
6278 |
unpartitioned space, using the "Recommended layout" will automatically configure |
6279 |
your partitions without destroying any data on any existing partitions. |
6280 |
</p> |
6281 |
|
6282 |
<warn> |
6283 |
As with any partitioning application, you should backup your system before |
6284 |
making changes to your partition table, as any possible bugs could cause data |
6285 |
loss. |
6286 |
</warn> |
6287 |
|
6288 |
</body> |
6289 |
</subsection> |
6290 |
</section> |
6291 |
|
6292 |
<section> |
6293 |
<title>Network Mounts</title> |
6294 |
<subsection> |
6295 |
<title>Optional: Define network mounts</title> |
6296 |
<body> |
6297 |
|
6298 |
<p> |
6299 |
This screen lets you set up and use any existing network mounts during and |
6300 |
after installation. At this time, only NFS is supported. |
6301 |
</p> |
6302 |
|
6303 |
</body> |
6304 |
</subsection> |
6305 |
</section> |
6306 |
|
6307 |
<!-- removed per codeman's suggestion on IRC; selecting "Networkless at |
6308 |
beginning makes these options unavailable |
6309 |
|
6310 |
<section> |
6311 |
<title>Stage Selection</title> |
6312 |
<subsection> |
6313 |
<title>Dynamic stage generation</title> |
6314 |
<body> |
6315 |
|
6316 |
<p> |
6317 |
Since you are performing an installation <e>without</e> an internet connection, |
6318 |
you <e>must</e> select <c>3+GRP</c> from the stage options present. Then, on the next |
6319 |
screen, select <c>Create from CD</c>. Everything you need to build your system will |
6320 |
then be generated from the files on the LiveCD. |
6321 |
</p> |
6322 |
|
6323 |
<warn> |
6324 |
Do <e>not</e> select any options other than those specified above when you are |
6325 |
installing without an internet connection. |
6326 |
</warn> |
6327 |
|
6328 |
</body> |
6329 |
</subsection> |
6330 |
</section> |
6331 |
|
6332 |
<section> |
6333 |
<title>Portage Tree</title> |
6334 |
<subsection> |
6335 |
<title>Obtaining a Portage tree</title> |
6336 |
<body> |
6337 |
|
6338 |
<p> |
6339 |
You must choose <c>Snapshot</c> on this screen. The installer will automatically |
6340 |
install a Portage tree from the LiveCD once you select Snapshot; you do not |
6341 |
need to specify a snapshot URI. |
6342 |
</p> |
6343 |
|
6344 |
</body> |
6345 |
</subsection> |
6346 |
</section> |
6347 |
|
6348 |
--> |
6349 |
|
6350 |
<section> |
6351 |
<title>make.conf</title> |
6352 |
<subsection> |
6353 |
<title>USE flags</title> |
6354 |
<body> |
6355 |
|
6356 |
<p> |
6357 |
Since you are performing a GRP/networkless install, you will not be allowed to |
6358 |
select USE flags before installation. However, you are free to set your own USE |
6359 |
flags in <path>/etc/make.conf</path> after you have rebooted into your finished |
6360 |
system. |
6361 |
</p> |
6362 |
|
6363 |
</body> |
6364 |
</subsection> |
6365 |
<subsection> |
6366 |
<title>CFLAGS</title> |
6367 |
<body> |
6368 |
|
6369 |
<p> |
6370 |
Select your processor type in the CFLAGS section along with any custom |
6371 |
optimizations you may want, such as <c>-O2</c> and <c>-pipe</c>. |
6372 |
</p> |
6373 |
|
6374 |
</body> |
6375 |
</subsection> |
6376 |
<subsection> |
6377 |
<title>Features</title> |
6378 |
<body> |
6379 |
|
6380 |
<p> |
6381 |
Any other options you wish to set for future use should be selected now. Read |
6382 |
through the available FEATURES and make your choices. |
6383 |
</p> |
6384 |
|
6385 |
</body> |
6386 |
</subsection> |
6387 |
</section> |
6388 |
|
6389 |
<section> |
6390 |
<title>Kernel Sources</title> |
6391 |
<subsection> |
6392 |
<title>Using the LiveCD kernel</title> |
6393 |
<body> |
6394 |
|
6395 |
<p> |
6396 |
You must use the kernel present on the LiveCD for the GRP/networkless |
6397 |
install. This is merely a <c>gentoo-sources</c> kernel compiled by |
6398 |
<c>genkernel</c>, Gentoo's automated compilation utility, and will give you a |
6399 |
kernel that automatically detects and configures your hardware upon boot. |
6400 |
</p> |
6401 |
|
6402 |
</body> |
6403 |
</subsection> |
6404 |
</section> |
6405 |
|
6406 |
<section> |
6407 |
<title>Bootloader</title> |
6408 |
<subsection> |
6409 |
<title>Making your choice</title> |
6410 |
<body> |
6411 |
|
6412 |
<p> |
6413 |
This screen allows to you choose your bootloader. Next, select your boot device |
6414 |
and (optionally) specify any additional boot options. |
6415 |
</p> |
6416 |
|
6417 |
</body> |
6418 |
</subsection> |
6419 |
</section> |
6420 |
|
6421 |
<section> |
6422 |
<title>Timezone</title> |
6423 |
<subsection> |
6424 |
<title>Choose your timezone</title> |
6425 |
<body> |
6426 |
|
6427 |
<p> |
6428 |
Study the list and select the region closest to your actual location. |
6429 |
</p> |
6430 |
|
6431 |
</body> |
6432 |
</subsection> |
6433 |
</section> |
6434 |
|
6435 |
<section> |
6436 |
<title>Networking</title> |
6437 |
<subsection> |
6438 |
<title>Add network device</title> |
6439 |
<body> |
6440 |
|
6441 |
<p> |
6442 |
On this screen, you will be able to configure the various network interface |
6443 |
devices detected on your computer. Read the available options carefully. |
6444 |
</p> |
6445 |
|
6446 |
<p> |
6447 |
The next screen gives you a choice between DHCP and manual IP address |
6448 |
configuration. Once your network interface is properly configured, you will |
6449 |
need to create a hostname for your system. Optionally, you may specify a |
6450 |
domainname and any DNS server information needed. |
6451 |
</p> |
6452 |
|
6453 |
</body> |
6454 |
</subsection> |
6455 |
</section> |
6456 |
|
6457 |
<section> |
6458 |
<title>Extra Packages</title> |
6459 |
<subsection> |
6460 |
<title>Optional: installing extra packages</title> |
6461 |
<body> |
6462 |
|
6463 |
<p> |
6464 |
The LiveCD contains a number of available pre-built packages. If you wish to |
6465 |
install any of them, check the appropriate box. |
6466 |
</p> |
6467 |
|
6468 |
</body> |
6469 |
</subsection> |
6470 |
</section> |
6471 |
|
6472 |
<section> |
6473 |
<title>Startup Services</title> |
6474 |
<subsection> |
6475 |
<body> |
6476 |
|
6477 |
<p> |
6478 |
This screen allows you to choose various services to load at system boot. Study |
6479 |
the available options and their descriptions carefully, and then select your |
6480 |
desired services. For example, if you have chosen to install <c>xorg-x11</c> |
6481 |
and want to boot straight into a graphical desktop, then you would select |
6482 |
"xdm" from the list. |
6483 |
</p> |
6484 |
|
6485 |
</body> |
6486 |
</subsection> |
6487 |
</section> |
6488 |
|
6489 |
<section> |
6490 |
<title>Other Settings</title> |
6491 |
<subsection> |
6492 |
<title>Miscellaneous options</title> |
6493 |
<body> |
6494 |
|
6495 |
<p> |
6496 |
Now you will be able to change various settings, including keyboard layout, |
6497 |
graphical display manager, the default editor, and whether to set your hardware |
6498 |
clock to UTC or local time. |
6499 |
</p> |
6500 |
|
6501 |
</body> |
6502 |
</subsection> |
6503 |
</section> |
6504 |
|
6505 |
<section> |
6506 |
<title>Users</title> |
6507 |
<subsection> |
6508 |
<title>Adding users and groups</title> |
6509 |
<body> |
6510 |
|
6511 |
<p> |
6512 |
First set the root password for the system administrator (the <e>root</e> |
6513 |
user). |
6514 |
</p> |
6515 |
|
6516 |
<p> |
6517 |
We <e>strongly</e> recommend that you create a regular user for daily work. |
6518 |
Working as root all the time is <e>dangerous</e> and should be avoided! Create |
6519 |
your users, set their passwords, and add them to the appropriate groups. You |
6520 |
can optionally change their home directories, select their login shell, and set |
6521 |
helpful comments. |
6522 |
</p> |
6523 |
|
6524 |
</body> |
6525 |
</subsection> |
6526 |
</section> |
6527 |
|
6528 |
<section> |
6529 |
<title>Review</title> |
6530 |
<subsection> |
6531 |
<title>Finishing up</title> |
6532 |
<body> |
6533 |
|
6534 |
<p> |
6535 |
Please take the time to double-check each step of the installation process, |
6536 |
ensuring that your system is properly configured. When you have finished |
6537 |
reviewing, you may save your progress and exit, or select <c>Install</c> to |
6538 |
begin automatically installing Gentoo. |
6539 |
</p> |
6540 |
|
6541 |
<p> |
6542 |
The installer will alert you when it has finished. It will then return you to |
6543 |
the command prompt. All you need to do to reboot is type: |
6544 |
</p> |
6545 |
|
6546 |
<pre caption="Rebooting"> |
6547 |
# <i>shutdown -r now</i> |
6548 |
</pre> |
6549 |
|
6550 |
<p> |
6551 |
Congratulations, your system is now fully equipped! Continue with <uri |
6552 |
link="?part=1&chap=5">Where to go from here?</uri> to learn more about |
6553 |
Gentoo. |
6554 |
</p> |
6555 |
|
6556 |
</body> |
6557 |
</subsection> |
6558 |
</section> |
6559 |
</sections> |
6560 |
|
6561 |
<!-- |
6562 |
Steps of the dialog: |
6563 |
(pre): type installer at the prompt to begin the dialog |
6564 |
1. Partitioning |
6565 |
(note: we absolutely must include partitioning info here; gli-dialog refers |
6566 |
users to the partitioning info in the gentoo handbook! note that the gtkfe |
6567 |
installer already has this partition info in its graphical help screens) |
6568 |
|
6569 |
2. Network mounts |
6570 |
3. Stage Selection |
6571 |
4. kernel sources |
6572 |
5. bootloader |
6573 |
6. timezone |
6574 |
7. network interface selection/configuration (inc. dhcp/static-manual) |
6575 |
8. hostname/domainname/dns |
6576 |
9. Optional: install additional packages |
6577 |
10. set root password |
6578 |
11. add user, set passwords/groups |
6579 |
12. review |
6580 |
(post) finishes, drops to prompt: shutdown -r now |
6581 |
--> |
6582 |
|
6583 |
|
6584 |
|
6585 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-gli-medium.xml |
6586 |
|
6587 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-gli-medium.xml?rev=1.1&view=markup |
6588 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-gli-medium.xml?rev=1.1&content-type=text/plain |
6589 |
|
6590 |
Index: hb-install-gli-medium.xml |
6591 |
=================================================================== |
6592 |
<?xml version='1.0' encoding='UTF-8'?> |
6593 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
6594 |
|
6595 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
6596 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
6597 |
|
6598 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-gli-medium.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
6599 |
|
6600 |
<sections> |
6601 |
|
6602 |
<version>7.3</version> |
6603 |
<date>2007-02-26</date> |
6604 |
|
6605 |
<section> |
6606 |
<title>Hardware Requirements</title> |
6607 |
<subsection> |
6608 |
<title>Introduction</title> |
6609 |
<body> |
6610 |
|
6611 |
<p> |
6612 |
Before we start, we first list what hardware requirements you need to |
6613 |
successfully install Gentoo on your box using the Installer LiveCD. |
6614 |
</p> |
6615 |
|
6616 |
</body> |
6617 |
</subsection> |
6618 |
<subsection> |
6619 |
<title>Hardware Requirements</title> |
6620 |
<body> |
6621 |
|
6622 |
<table> |
6623 |
<tr test="func:keyval('arch')='x86'"> |
6624 |
<th>CPU</th> |
6625 |
<ti>i686 or later</ti> |
6626 |
</tr> |
6627 |
<tr test="func:keyval('arch')='AMD64'"> |
6628 |
<th>CPU</th> |
6629 |
<ti>Any AMD64 or EM64T CPU</ti> |
6630 |
</tr> |
6631 |
<tr> |
6632 |
<th>Memory</th> |
6633 |
<ti>128 MB</ti> |
6634 |
</tr> |
6635 |
<tr> |
6636 |
<th>Diskspace</th> |
6637 |
<ti>1.5 GB (excluding swap space)</ti> |
6638 |
</tr> |
6639 |
<tr> |
6640 |
<th>Swap space</th> |
6641 |
<ti>At least 256 MB</ti> |
6642 |
</tr> |
6643 |
</table> |
6644 |
|
6645 |
|
6646 |
</body> |
6647 |
</subsection> |
6648 |
</section> |
6649 |
<!-- General description, propagated to other architectures as well --> |
6650 |
<!-- START --> |
6651 |
<section> |
6652 |
<title>The Gentoo Linux Installer LiveCD</title> |
6653 |
<subsection> |
6654 |
<title>Introduction</title> |
6655 |
<body> |
6656 |
|
6657 |
<p> |
6658 |
A LiveCD is a bootable medium which contains a self-sustained Gentoo |
6659 |
environment. It allows you to boot Linux from the CD. During the boot process |
6660 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
6661 |
Installation CDs are maintained by Gentoo developers. |
6662 |
</p> |
6663 |
|
6664 |
<p> |
6665 |
There currently are two Installation CDs available: |
6666 |
</p> |
6667 |
|
6668 |
<ul> |
6669 |
<li> |
6670 |
The Installer LiveCD contains everything you need to install Gentoo. It |
6671 |
provides a graphical environment, a graphical as well as console based |
6672 |
installer which automatically carries out the installation for you, and of |
6673 |
course, the installation instructions for your architecture. |
6674 |
</li> |
6675 |
<li> |
6676 |
The Minimal Installation CD contains only a minimal environment that allows |
6677 |
you to boot up and configure your network so you can connect to the |
6678 |
Internet. It does not contain any additional files and cannot be used |
6679 |
during the current installation approach. |
6680 |
</li> |
6681 |
</ul> |
6682 |
|
6683 |
</body> |
6684 |
</subsection> |
6685 |
</section> |
6686 |
<!-- STOP --> |
6687 |
<section> |
6688 |
<title>Download, Burn and Boot the Gentoo Linux Installer LiveCD</title> |
6689 |
<subsection> |
6690 |
<title>Downloading and Burning the Installer LiveCD</title> |
6691 |
<body> |
6692 |
|
6693 |
<p> |
6694 |
You can download the Installer LiveCDs from one of our <uri |
6695 |
link="/main/en/mirrors.xml">mirrors</uri>. They are located in the |
6696 |
<path><keyval id="release-dir"/>livecd/</path> directory. |
6697 |
</p> |
6698 |
|
6699 |
<p> |
6700 |
Inside that directory you'll find an ISO-file. That is a full CD image which |
6701 |
you can write on a CD-R. |
6702 |
</p> |
6703 |
|
6704 |
<p> |
6705 |
After downloading the file, you can verify its integrity to see if it is |
6706 |
corrupted or not: |
6707 |
</p> |
6708 |
|
6709 |
<ul> |
6710 |
<li> |
6711 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
6712 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or <uri |
6713 |
link="http://www.etree.org/md5com.html">md5sum</uri> for Windows) |
6714 |
</li> |
6715 |
<li> |
6716 |
You can verify the cryptographic signature that we provide. You need to |
6717 |
obtain the public key we use (17072058) before you proceed though. |
6718 |
</li> |
6719 |
</ul> |
6720 |
|
6721 |
<p> |
6722 |
To fetch our public key using the GnuPG application, run the following command: |
6723 |
</p> |
6724 |
|
6725 |
<pre caption="Obtaining the public key"> |
6726 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
6727 |
</pre> |
6728 |
|
6729 |
<p> |
6730 |
Now verify the signature: |
6731 |
</p> |
6732 |
|
6733 |
<pre caption="Verify the cryptographic signature"> |
6734 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
6735 |
</pre> |
6736 |
|
6737 |
<p> |
6738 |
To burn the downloaded ISO(s), you have to select raw-burning. How you do this |
6739 |
is highly program-dependent. We will discuss <c>cdrecord</c> and <c>K3B</c> |
6740 |
here; more information can be found in our <uri |
6741 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
6742 |
</p> |
6743 |
|
6744 |
<ul> |
6745 |
<li> |
6746 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
6747 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
6748 |
path). |
6749 |
</li> |
6750 |
<li> |
6751 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
6752 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
6753 |
<c>Start</c>. |
6754 |
</li> |
6755 |
</ul> |
6756 |
|
6757 |
</body> |
6758 |
</subsection> |
6759 |
<subsection> |
6760 |
<title>Booting the Installer LiveCD</title> |
6761 |
<body> |
6762 |
|
6763 |
<impo> |
6764 |
Read this whole subsection before continuing, as you will probably not have the |
6765 |
opportunity to read it before doing things later. |
6766 |
</impo> |
6767 |
|
6768 |
<p> |
6769 |
Once you have burned your LiveCD, it is time to boot it. Remove all CDs from |
6770 |
your CD drives, reboot your system and enter the BIOS. This is usually done by |
6771 |
hitting DEL, F1 or ESC, depending on your BIOS. Inside the BIOS, change the |
6772 |
boot order so that the CD-ROM is tried before the hard disk. This is often |
6773 |
found under "CMOS Setup". If you don't do this, your system will just reboot |
6774 |
from the hard disk, ignoring the CD-ROM. |
6775 |
</p> |
6776 |
|
6777 |
<p> |
6778 |
Now place the LiveCD in the CD-ROM drive and reboot. You should see a boot |
6779 |
prompt. At this screen, you can hit Enter to begin the boot process with the |
6780 |
default boot options, or boot the LiveCD with custom boot options by specifying |
6781 |
a kernel followed by boot options and then hitting Enter. |
6782 |
</p> |
6783 |
|
6784 |
<p> |
6785 |
Specifying a kernel? Yes, we provide several kernels on our LiveCD. The default |
6786 |
one is <c>gentoo</c>. Other kernels are for specific hardware needs and the |
6787 |
<c>-nofb</c> variants which disable framebuffer. |
6788 |
</p> |
6789 |
|
6790 |
<p> |
6791 |
Below you'll find a short overview on the available kernels: |
6792 |
</p> |
6793 |
|
6794 |
<table> |
6795 |
<tr> |
6796 |
<th>Kernel</th> |
6797 |
<th>Description</th> |
6798 |
</tr> |
6799 |
<tr test="func:keyval('arch')='x86'"> |
6800 |
<ti>gentoo</ti> |
6801 |
<ti>Default 2.6 kernel with support for multiple CPUs</ti> |
6802 |
</tr> |
6803 |
<tr test="func:keyval('arch')='x86'"> |
6804 |
<ti>gentoo-nofb</ti> |
6805 |
<ti>Same as <c>gentoo</c> but without framebuffer support</ti> |
6806 |
</tr> |
6807 |
<tr test="func:keyval('arch')='AMD64'"> |
6808 |
<ti>gentoo</ti> |
6809 |
<ti> |
6810 |
Default kernel with support for K8 CPUS (including NUMA support) and EM64T |
6811 |
CPUs |
6812 |
</ti> |
6813 |
</tr> |
6814 |
<tr> |
6815 |
<ti>memtest86</ti> |
6816 |
<ti>Test your local RAM for errors</ti> |
6817 |
</tr> |
6818 |
</table> |
6819 |
|
6820 |
<p> |
6821 |
You can also provide kernel options. They represent optional settings you can |
6822 |
(de)activate at will. The following list is the same as the one you receive |
6823 |
when you press F2 through F7 at the bootscreen. |
6824 |
</p> |
6825 |
|
6826 |
<pre caption="Options available to pass to your kernel of choice"> |
6827 |
<comment>Hardware options:</comment> |
6828 |
|
6829 |
acpi=on This loads support for ACPI and also causes the acpid daemon to |
6830 |
be started by the CD on boot. This is only needed if your |
6831 |
system requires ACPI to function properly. This is not |
6832 |
required for Hyperthreading support. |
6833 |
|
6834 |
acpi=off Completely disables ACPI. This is useful on some older |
6835 |
systems, and is also a requirement for using APM. This will |
6836 |
disable any Hyperthreading support of your processor. |
6837 |
|
6838 |
console=X This sets up serial console access for the CD. The first |
6839 |
option is the device, usually ttyS0 on x86, followed by any |
6840 |
connection options, which are comma separated. The default |
6841 |
options are 9600,8,n,1. |
6842 |
|
6843 |
dmraid=X This allows for passing options to the device-mapper RAID |
6844 |
subsystem. Options should be encapsulated in quotes. |
6845 |
|
6846 |
doapm This loads APM driver support. This requires you to also use |
6847 |
acpi=off. |
6848 |
|
6849 |
doslowusb This adds some extra pauses into the boot process for the slow |
6850 |
USB CDROM of the IBM BladeCenter. |
6851 |
|
6852 |
dopcmcia This loads support for PCMCIA and Cardbus hardware and also |
6853 |
causes the pcmcia cardmgr to be started by the CD on boot. |
6854 |
This is only required when booting from a PCMCIA/Cardbus device. |
6855 |
|
6856 |
doscsi This loads support for most SCSI controllers. This is also a |
6857 |
requirement for booting most USB devices, as they use the SCSI |
6858 |
subsystem of the kernel. |
6859 |
|
6860 |
hda=stroke This allows you to partition the whole hard disk even when your |
6861 |
BIOS is unable to handle large disks. This option is only used |
6862 |
on machines with an older BIOS. Replace hda with the device |
6863 |
that is requiring this option. |
6864 |
|
6865 |
ide=nodma This forces the disabling of DMA in the kernel and is required |
6866 |
by some IDE chipsets and also by some CDROM drives. If your |
6867 |
system is having trouble reading from your IDE CDROM, try this |
6868 |
option. This also disables the default hdparm settings from |
6869 |
being executed. |
6870 |
|
6871 |
noapic This disables the Advanced Programmable Interrupt Controller |
6872 |
that is present on newer motherboards. It has been known to |
6873 |
cause some problems on older hardware. |
6874 |
|
6875 |
nodetect This disables all of the autodetection done by the CD, |
6876 |
including device autodetection and DHCP probing. This is |
6877 |
useful for doing debugging of a failing CD or driver. |
6878 |
|
6879 |
nodhcp This disables DHCP probing on detected network cards. This is |
6880 |
useful on networks with only static addresses. |
6881 |
|
6882 |
nodmraid Disables support for device-mapper RAID, such as that used for |
6883 |
on-board IDE/SATA RAID controllers. |
6884 |
|
6885 |
nofirewire This disables the loading of Firewire modules. This should only |
6886 |
be necessary if your Firewire hardware is causing a problem |
6887 |
with booting the CD. |
6888 |
|
6889 |
nogpm This disables gpm console mouse support. |
6890 |
|
6891 |
nohotplug This disables the loading of the hotplug and coldplug init |
6892 |
scripts at boot. This is useful for doing debugging of a |
6893 |
failing CD or driver. |
6894 |
|
6895 |
nokeymap This disables the keymap selection used to select non-US |
6896 |
keyboard layouts. |
6897 |
|
6898 |
nolapic This disables the local APIC on Uniprocessor kernels. |
6899 |
|
6900 |
nosata This disables the loading of Serial ATA modules. This is |
6901 |
useful if your system is having problems with the SATA subsystem. |
6902 |
|
6903 |
nosmp This disables SMP, or Symmetric Multiprocessing, on SMP-enabled |
6904 |
kernels. This is useful for debugging SMP-related issues with |
6905 |
certain drivers and motherboards. |
6906 |
|
6907 |
nosound This disables sound support and volume setting. This is useful |
6908 |
for systems where sound support causes problems. |
6909 |
|
6910 |
nousb This disables the autoloading of USB modules. This is useful |
6911 |
for debugging USB issues. |
6912 |
|
6913 |
<comment>Volume/Device Management:</comment> |
6914 |
|
6915 |
dodevfs This enables the deprecated device filesystem on 2.6 systems. |
6916 |
You will also need to use noudev for this to take effect. |
6917 |
Since devfs is the only option with a 2.4 kernel, this option |
6918 |
has no effect if booting a 2.4 kernel. |
6919 |
|
6920 |
doevms2 This enables support for IBM's pluggable EVMS, or Enterprise |
6921 |
Volume Management System. This is not safe to use with lvm2. |
6922 |
|
6923 |
dolvm2 This enables support for Linux's Logical Volume Management. |
6924 |
This is not safe to use with evms2. |
6925 |
|
6926 |
noudev This disables udev support on 2.6 kernels. This option |
6927 |
requires that dodevfs is used. Since udev is not an option for |
6928 |
2.4 kernels, this options has no effect if booting a 2.4 |
6929 |
kernel. |
6930 |
|
6931 |
unionfs Enables support for Unionfs on supported CD images. This will |
6932 |
create a writable Unionfs overlay in a tmpfs, allowing you to |
6933 |
change any file on the CD. |
6934 |
|
6935 |
unionfs=X Enables support for Unionfs on supported CD images. This will |
6936 |
create a writable Unionfs overlay on the device you specify. |
6937 |
The device must be formatted with a filesystem recognized and |
6938 |
writable by the kernel. |
6939 |
|
6940 |
<comment>Other options:</comment> |
6941 |
|
6942 |
debug Enables debugging code. This might get messy, as it displays |
6943 |
a lot of data to the screen. |
6944 |
|
6945 |
docache This caches the entire runtime portion of the CD into RAM, |
6946 |
which allows you to umount /mnt/cdrom and mount another CDROM. |
6947 |
This option requires that you have at least twice as much |
6948 |
available RAM as the size of the CD. |
6949 |
|
6950 |
doload=X This causes the initial ramdisk to load any module listed, as |
6951 |
well as dependencies. Replace X with the module name. Multiple |
6952 |
modules can be specified by a comma-separated list. |
6953 |
|
6954 |
noload=X This causes the initial ramdisk to skip the loading of a |
6955 |
specific module that may be causing a problem. Syntax matches |
6956 |
that of doload. |
6957 |
|
6958 |
nox This causes an X-enabled LiveCD to not automatically start X, |
6959 |
but rather, to drop to the command line instead. |
6960 |
|
6961 |
scandelay This causes the CD to pause for 10 seconds during certain |
6962 |
portions the boot process to allow for devices that are slow to |
6963 |
initialize to be ready for use. |
6964 |
|
6965 |
scandelay=X This allows you to specify a given delay, in seconds, to be |
6966 |
added to certain portions of the boot process to allow for |
6967 |
devices that are slow to initialize to be ready for use. |
6968 |
Replace X with the number of seconds to pause. |
6969 |
</pre> |
6970 |
|
6971 |
<p> |
6972 |
Now boot your CD, select a kernel (if you are not happy with the default |
6973 |
<c>gentoo</c> kernel) and boot options. As an example, we show you how |
6974 |
to boot the <c>gentoo</c> kernel, with <c>dopcmcia</c> as kernel |
6975 |
parameters: |
6976 |
</p> |
6977 |
|
6978 |
<pre caption="Booting an Installation CD"> |
6979 |
boot: <i>gentoo dopcmcia</i> |
6980 |
</pre> |
6981 |
|
6982 |
<p> |
6983 |
You will then be greeted with a boot screen and progress bar. If you are |
6984 |
installing Gentoo on a system with a non-US keyboard, make sure you |
6985 |
immediately press Alt-F1 to switch to verbose mode and follow the prompt. If no |
6986 |
selection is made in 10 seconds the default (US keyboard) will be accepted and |
6987 |
the boot process will continue. Once the boot process completes, Gnome will |
6988 |
start up and you will be automatically logged in to the "Live" Gentoo Linux |
6989 |
system as "gentoo" in graphical mode. You will be logged in as "root", the |
6990 |
superuser on the other consoles and should have a root ("#") prompt there. You |
6991 |
can switch to those consoles by pressing Alt-F2, Alt-F3, Alt-F4 Alt-F5, Alt-F6. |
6992 |
Get back to the graphical desktop you started on by pressing Alt-F7. To switch |
6993 |
to other consoles from within X, you must prefix the above with Ctrl. You are |
6994 |
able to run commands as root from any terminal within the graphical environment |
6995 |
by using the <c>sudo</c> application. You can even become root within a |
6996 |
terminal to perform multiple tasks. |
6997 |
</p> |
6998 |
|
6999 |
<pre caption="Using sudo to run applications"> |
7000 |
<comment>(Example only)</comment> |
7001 |
<comment>(Editing the group file)</comment> |
7002 |
# <i>sudo vi /etc/group</i> |
7003 |
<comment>(Becoming root for a session)</comment> |
7004 |
# <i>sudo su -</i> |
7005 |
</pre> |
7006 |
|
7007 |
</body> |
7008 |
</subsection> |
7009 |
<subsection id="hardware"> |
7010 |
<title>Extra Hardware Configuration</title> |
7011 |
<body> |
7012 |
|
7013 |
<p> |
7014 |
When the LiveCD boots, it tries to detect all your hardware devices and loads |
7015 |
the appropriate kernel modules to support your hardware. In the vast majority |
7016 |
of cases, it does a very good job. However, in some cases, it may not auto-load |
7017 |
the kernel modules you need. If the PCI auto-detection missed some of your |
7018 |
system's hardware, you will have to load the appropriate kernel modules |
7019 |
manually. These tasks require root access. |
7020 |
</p> |
7021 |
|
7022 |
<p> |
7023 |
In the next example we try to load the <c>8139too</c> module (support for |
7024 |
certain kinds of network interfaces): |
7025 |
</p> |
7026 |
|
7027 |
<pre caption="Loading kernel modules"> |
7028 |
# <i>modprobe 8139too</i> |
7029 |
</pre> |
7030 |
|
7031 |
<p> |
7032 |
If you need PCMCIA support, you should start the <c>pcmcia</c> init script: |
7033 |
</p> |
7034 |
|
7035 |
<pre caption="Starting the PCMCIA init script"> |
7036 |
# <i>/etc/init.d/pcmcia start</i> |
7037 |
</pre> |
7038 |
|
7039 |
</body> |
7040 |
</subsection> |
7041 |
<subsection> |
7042 |
<title>Optional: Tweaking Hard Disk Performance</title> |
7043 |
<body> |
7044 |
|
7045 |
<p> |
7046 |
If you are an advanced user, you might want to tweak the IDE hard disk |
7047 |
performance using <c>hdparm</c>. You will need root access to use <c>hdparm</c>. |
7048 |
With the <c>-tT</c> options you can test the performance of your disk (execute |
7049 |
it several times to get a more precise impression): |
7050 |
</p> |
7051 |
|
7052 |
<pre caption="Testing disk performance"> |
7053 |
# <i>hdparm -tT /dev/hda</i> |
7054 |
</pre> |
7055 |
|
7056 |
<p> |
7057 |
To tweak, you can use any of the following examples (or experiment |
7058 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
7059 |
disk): |
7060 |
</p> |
7061 |
|
7062 |
<pre caption="Tweaking hard disk performance"> |
7063 |
<comment>(Activate DMA:)</comment> |
7064 |
# <i>hdparm -d 1 /dev/hda</i> |
7065 |
|
7066 |
<comment>(Or with Safe Performance Options:)</comment> |
7067 |
# <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
7068 |
</pre> |
7069 |
|
7070 |
</body> |
7071 |
</subsection> |
7072 |
<subsection id="useraccounts"> |
7073 |
<title>Optional: User Accounts</title> |
7074 |
<body> |
7075 |
|
7076 |
<p> |
7077 |
If you plan on giving other people access to your installation environment or |
7078 |
you want to chat using <c>irssi</c> without root privileges (for security |
7079 |
reasons), you need to create the necessary user accounts and change the root |
7080 |
password. You need root access to change the root password and add new users. |
7081 |
</p> |
7082 |
|
7083 |
<p> |
7084 |
To change the root password, use the <c>passwd</c> utility: |
7085 |
</p> |
7086 |
|
7087 |
<pre caption="Changing the root password"> |
7088 |
$ <i>sudo su -</i> |
7089 |
# <i>passwd</i> |
7090 |
New password: <comment>(Enter your new password)</comment> |
7091 |
Re-enter password: <comment>(Re-enter your password)</comment> |
7092 |
</pre> |
7093 |
|
7094 |
<p> |
7095 |
To create a user account, we first enter their credentials, followed by its |
7096 |
password. We use <c>useradd</c> and <c>passwd</c> for these tasks. In the next |
7097 |
example, we create a user called "john". |
7098 |
</p> |
7099 |
|
7100 |
<pre caption="Creating a user account"> |
7101 |
# <i>useradd -m -G users john</i> |
7102 |
# <i>passwd john</i> |
7103 |
New password: <comment>(Enter john's password)</comment> |
7104 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
7105 |
</pre> |
7106 |
|
7107 |
<p> |
7108 |
You can change your user id from root to the newly created user by using |
7109 |
<c>su</c>: |
7110 |
</p> |
7111 |
|
7112 |
<pre caption="Changing user id"> |
7113 |
# <i>su - john</i> |
7114 |
</pre> |
7115 |
|
7116 |
<p> |
7117 |
You can also change the password for the "gentoo" user in the graphical |
7118 |
environment. This account is already suitable for use on the Internet. |
7119 |
</p> |
7120 |
|
7121 |
<pre caption="Changing the gentoo password"> |
7122 |
$ <i>passwd</i> |
7123 |
New password: <comment>(Enter your new password)</comment> |
7124 |
Re-enter password: <comment>(Re-enter your password)</comment> |
7125 |
</pre> |
7126 |
|
7127 |
</body> |
7128 |
</subsection> |
7129 |
<subsection> |
7130 |
<title>Optional: Viewing Documentation while Installing</title> |
7131 |
<body> |
7132 |
|
7133 |
<p> |
7134 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
7135 |
installation, you can view it with Mozilla Firefox (from the graphical |
7136 |
environment) or with <c>links</c> (from a terminal environment). |
7137 |
</p> |
7138 |
|
7139 |
<pre caption="Viewing the on-CD documentation with Firefox"> |
7140 |
# <i>firefox /mnt/cdrom/docs/handbook/html/index.html</i> |
7141 |
</pre> |
7142 |
|
7143 |
<p> |
7144 |
If you would prefer to use <c>links</c> to see a text-only version of the |
7145 |
handbook, make sure you have created a user account (see <uri |
7146 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> |
7147 |
to go to a new terminal and log in. |
7148 |
</p> |
7149 |
|
7150 |
<pre caption="Viewing the on-CD documentation with links"> |
7151 |
# <i>links /mnt/cdrom/docs/handbook/html/index.html</i> |
7152 |
</pre> |
7153 |
|
7154 |
<p> |
7155 |
You can go back to your original window by pressing <c>Alt-F7</c>. |
7156 |
</p> |
7157 |
|
7158 |
<p> |
7159 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
7160 |
more recent than the one provided on the CD. You can view it using Firefox or |
7161 |
<c>links</c> as well, but only after having completed the <e>Configuring your |
7162 |
Network</e> chapter (otherwise you won't be able to go on the Internet to view |
7163 |
the document): |
7164 |
</p> |
7165 |
|
7166 |
<pre caption="Viewing the online documentation with Firefox"> |
7167 |
# <i>firefox http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i> |
7168 |
</pre> |
7169 |
|
7170 |
<pre caption="Viewing the online documentation with links"> |
7171 |
# <i>links http://www.gentoo.org/doc/en/handbook/<keyval id="online-book"/></i> |
7172 |
</pre> |
7173 |
|
7174 |
<p> |
7175 |
You can now choose to proceed by using the <uri link="?part=1&chap=3">GTK+ |
7176 |
based installer</uri> (which needs X) or the <uri |
7177 |
link="?part=1&chap=4">Dialog based installer</uri> that can be run on a |
7178 |
console. |
7179 |
</p> |
7180 |
|
7181 |
</body> |
7182 |
</subsection> |
7183 |
</section> |
7184 |
</sections> |
7185 |
|
7186 |
|
7187 |
|
7188 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-gtkfe.xml |
7189 |
|
7190 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-gtkfe.xml?rev=1.1&view=markup |
7191 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-gtkfe.xml?rev=1.1&content-type=text/plain |
7192 |
|
7193 |
Index: hb-install-gtkfe.xml |
7194 |
=================================================================== |
7195 |
<?xml version='1.0' encoding='UTF-8'?> |
7196 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
7197 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-gtkfe.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
7198 |
|
7199 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
7200 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
7201 |
|
7202 |
<sections> |
7203 |
|
7204 |
<version>2.1</version> |
7205 |
<date>2006-11-01</date> |
7206 |
|
7207 |
<section> |
7208 |
<title>Welcome</title> |
7209 |
<subsection> |
7210 |
<title>Before you begin</title> |
7211 |
<body> |
7212 |
|
7213 |
<p> |
7214 |
Once the Gentoo Linux Installer (GLI) has finished loading, you will be |
7215 |
greeted by the welcome screen. It provides a friendly introduction to the |
7216 |
process of installing Gentoo on your computer. Remember to read each option |
7217 |
carefully. There is detailed help available for each step of installation; |
7218 |
just click <c>Help</c> in the lower left corner of the installer. We recommend that |
7219 |
you always read the help pages before making your choices. Note that at any |
7220 |
time during the installation process, you can save your configuration |
7221 |
progress in case you need to resume your installation at a later time. |
7222 |
</p> |
7223 |
|
7224 |
<p> |
7225 |
There are two types of installation modes available. Choose <c>Networkless</c> |
7226 |
to begin installing Gentoo Linux. |
7227 |
</p> |
7228 |
|
7229 |
<note> |
7230 |
Selecting <c>Networkless</c> will make some later configuration options |
7231 |
unavailable. Simply proceed to the next screen. |
7232 |
</note> |
7233 |
|
7234 |
</body> |
7235 |
</subsection> |
7236 |
</section> |
7237 |
|
7238 |
<section> |
7239 |
<title>Pre-installation Configuration</title> |
7240 |
<subsection> |
7241 |
<title>Optional: Manual Network Configuration</title> |
7242 |
<body> |
7243 |
|
7244 |
<p> |
7245 |
In the next section, you are required to configure your network. The Installer |
7246 |
should have already detected and set up your network for you, but if it didn't, |
7247 |
you can manually configure your network. On the <e>Misc.</e> tab, you can |
7248 |
specify a location of your choice or keep the default of |
7249 |
<path>/var/log/installer.log</path> where the Installer will store its logs. |
7250 |
</p> |
7251 |
|
7252 |
</body> |
7253 |
</subsection> |
7254 |
<subsection> |
7255 |
<title>Optional: Remote Installation</title> |
7256 |
<body> |
7257 |
|
7258 |
<p> |
7259 |
If you wish to enable SSH access to the machine, you can start <c>sshd</c> and |
7260 |
specify a root password. |
7261 |
</p> |
7262 |
|
7263 |
</body> |
7264 |
</subsection> |
7265 |
<subsection> |
7266 |
<title>Optional: Load Additional Kernel Modules</title> |
7267 |
<body> |
7268 |
|
7269 |
<p> |
7270 |
If you need to load more kernel modules to support your hardware, enter their |
7271 |
names into the appropriate line, each separated by a space. |
7272 |
</p> |
7273 |
|
7274 |
<warn> |
7275 |
Do not change the <e>Install mode</e> selection to anything besides |
7276 |
<b>Normal</b>. This feature is still experimental and changing it will leave you |
7277 |
with an unbootable system! |
7278 |
</warn> |
7279 |
<!-- still experimental for 2006.1? --> |
7280 |
|
7281 |
</body> |
7282 |
</subsection> |
7283 |
</section> |
7284 |
|
7285 |
<section> |
7286 |
<title>Partitioning</title> |
7287 |
<subsection> |
7288 |
<title>Preparing the disks</title> |
7289 |
<body> |
7290 |
|
7291 |
<p> |
7292 |
In order to install Gentoo on your machine, you will need to prepare your |
7293 |
disks. The <e>Partitioning</e> screen will show you a list of detected disks and |
7294 |
allow you to specify the filesystems you would like to have on your |
7295 |
partitions. Clicking <c>Clear partitions</c> will erase all previous partitions on |
7296 |
your disk, so be careful with this option! It is also possible to resize |
7297 |
certain partition types. |
7298 |
</p> |
7299 |
|
7300 |
<p> |
7301 |
If you choose to go with the <c>Recommended layout</c>, the installer will |
7302 |
create three partitions: 100MB for <path>/boot</path>, a <path>/swap</path> |
7303 |
partition up to 512MB in size, and the rest of the available space on the disk |
7304 |
is used for <path>/</path>, the root partition. If you have more than 4GB of |
7305 |
unpartitioned space, using the "Recommended layout" will automatically configure |
7306 |
your partitions without destroying any data on any existing partitions. |
7307 |
</p> |
7308 |
|
7309 |
<warn> |
7310 |
As with any partitioning application, you should backup your system before |
7311 |
making changes to your partition table, as any possible bugs could cause data |
7312 |
loss. |
7313 |
</warn> |
7314 |
|
7315 |
</body> |
7316 |
</subsection> |
7317 |
</section> |
7318 |
|
7319 |
<section> |
7320 |
<title>Network Mounts</title> |
7321 |
<subsection> |
7322 |
<title>Optional: Define network mounts</title> |
7323 |
<body> |
7324 |
|
7325 |
<p> |
7326 |
This screen lets you set up and use any existing network mounts during and after |
7327 |
installation. Click <c>New</c> to begin configuration. At this time, only NFS is |
7328 |
supported. |
7329 |
</p> |
7330 |
|
7331 |
</body> |
7332 |
</subsection> |
7333 |
</section> |
7334 |
|
7335 |
<section> |
7336 |
<title>make.conf</title> |
7337 |
<subsection> |
7338 |
<title>USE flags</title> |
7339 |
<body> |
7340 |
|
7341 |
<p> |
7342 |
Since you are performing a GRP/networkless install, you will not be allowed |
7343 |
to select USE flags before installation. However, you are free to set your own |
7344 |
USE flags in <path>/etc/make.conf</path> after you have rebooted into your |
7345 |
finished system. |
7346 |
</p> |
7347 |
|
7348 |
</body> |
7349 |
</subsection> |
7350 |
<subsection> |
7351 |
<title>CFLAGS</title> |
7352 |
<body> |
7353 |
|
7354 |
<p> |
7355 |
You should, however, select your processor type in the <e>CFLAGS</e> section along |
7356 |
with any custom optimizations you may want, such as <c>-O2</c> and |
7357 |
<c>-pipe</c>. |
7358 |
</p> |
7359 |
|
7360 |
</body> |
7361 |
</subsection> |
7362 |
<subsection> |
7363 |
<title>Other</title> |
7364 |
<body> |
7365 |
|
7366 |
<p> |
7367 |
Any other options you wish to set for future use should be selected now. |
7368 |
<e>Build binary packages</e> creates ready-to-install binary tarballs of all |
7369 |
packages you compile on your system. <e>DistCC</e> allows you to share the |
7370 |
burden of compiling with another computer via your network connection. |
7371 |
<e>ccache</e> saves compiled code for later use, and thus can greatly speed up |
7372 |
compilation time if you re-install the same package. |
7373 |
</p> |
7374 |
|
7375 |
<p> |
7376 |
You will not be allowed to change your <e>CHOST</e>, as this can seriously damage |
7377 |
your installation. In <e>MAKEOPTS</e> you define how many parallel compilations |
7378 |
should occur when you install a package. A good choice is the number of CPUs |
7379 |
in your system plus one, but this guideline isn't always perfect. On a |
7380 |
uniprocessor system, <c>-j2</c> might be used. |
7381 |
</p> |
7382 |
|
7383 |
</body> |
7384 |
</subsection> |
7385 |
</section> |
7386 |
|
7387 |
<section> |
7388 |
<title>Kernel Sources</title> |
7389 |
<subsection> |
7390 |
<title>Using the LiveCD kernel</title> |
7391 |
<body> |
7392 |
|
7393 |
<p> |
7394 |
You must use the kernel present on the LiveCD for the GRP/networkless install. |
7395 |
This is merely a <c>gentoo-sources</c> kernel compiled by <c>genkernel</c>, |
7396 |
Gentoo's automated kernel compilation utility and will give you a kernel that |
7397 |
automatically detects and configures your hardware upon boot. |
7398 |
</p> |
7399 |
|
7400 |
<p> |
7401 |
If you want to have a nifty background image during system boot, select the |
7402 |
<c>Enable bootsplash</c> option. |
7403 |
</p> |
7404 |
|
7405 |
</body> |
7406 |
</subsection> |
7407 |
</section> |
7408 |
|
7409 |
<section> |
7410 |
<title>Bootloader</title> |
7411 |
<subsection> |
7412 |
<title>Making your choice</title> |
7413 |
<body> |
7414 |
|
7415 |
<p> |
7416 |
This screen allows to you choose your bootloader and, optionally, specify |
7417 |
additional kernel parameters that will be used at bootup. |
7418 |
</p> |
7419 |
|
7420 |
<p> |
7421 |
You may specify which disk to boot from by choosing the appropriate option |
7422 |
from <e>Boot Drive</e>. In Linux, the first IDE disk in your system is called |
7423 |
<c>hda</c>, the second IDE disk is <c>hdb</c>, and so on. If you have SATA or |
7424 |
SCSI disks, they will be called <c>sda</c>, <c>sdb</c>, etc. Please make the |
7425 |
correct selection for your system. |
7426 |
</p> |
7427 |
<!-- more bootloader inclusions needed about vga, etc. just don't include pure |
7428 |
CLI stuff, but only what can go on the extra kernel params line --> |
7429 |
<p> |
7430 |
If you need to pass any additional options to the kernel, such as video and/or |
7431 |
VGA statements, simply add them to the "Extra kernel parameters" section. |
7432 |
</p> |
7433 |
|
7434 |
<p> |
7435 |
If you jumpered your harddrive because the BIOS can't handle large harddrives |
7436 |
you'll need to append <c>hdx=stroke</c>. If you have SCSI devices, you should |
7437 |
add <c>doscsi</c> as a kernel option. |
7438 |
</p> |
7439 |
|
7440 |
<!-- do we need to cover all the stuff about lilo/grub and kernel parameter |
7441 |
lines and/or block devices here? --> |
7442 |
|
7443 |
</body> |
7444 |
</subsection> |
7445 |
</section> |
7446 |
|
7447 |
<section> |
7448 |
<title>Timezone</title> |
7449 |
<subsection> |
7450 |
<title>Choose your timezone</title> |
7451 |
<body> |
7452 |
|
7453 |
<p> |
7454 |
Study the map and select the region closest to your actual location. Later, |
7455 |
you will be asked to select if you want your clock to be set to UTC or local |
7456 |
time. |
7457 |
</p> |
7458 |
|
7459 |
</body> |
7460 |
</subsection> |
7461 |
</section> |
7462 |
|
7463 |
<section> |
7464 |
<title>Networking</title> |
7465 |
<subsection> |
7466 |
<title>Device information</title> |
7467 |
<body> |
7468 |
|
7469 |
<p> |
7470 |
On this screen, you will be able to configure the various network interface |
7471 |
devices on your computer. Read the available options carefully. |
7472 |
</p> |
7473 |
|
7474 |
<p> |
7475 |
On the <e>Hostname/Proxy Information/Other</e> tab, you will need to choose a |
7476 |
hostname for your machine. You may also specify proxy server and DNS settings |
7477 |
if needed. |
7478 |
</p> |
7479 |
|
7480 |
</body> |
7481 |
</subsection> |
7482 |
</section> |
7483 |
|
7484 |
<section> |
7485 |
<title>Daemons</title> |
7486 |
<subsection> |
7487 |
<title>Cron daemon</title> |
7488 |
<body> |
7489 |
|
7490 |
<p> |
7491 |
Cron daemons are helpful programs that run tasks at scheduled times. While you |
7492 |
do not <e>need</e> to install one, they can be quite useful. |
7493 |
</p> |
7494 |
|
7495 |
</body> |
7496 |
</subsection> |
7497 |
<subsection> |
7498 |
<title>System logger</title> |
7499 |
<body> |
7500 |
|
7501 |
<p> |
7502 |
A system logger is a necessity for any Linux operating system. Make your |
7503 |
selection from the available choices. |
7504 |
</p> |
7505 |
|
7506 |
</body> |
7507 |
</subsection> |
7508 |
</section> |
7509 |
|
7510 |
<section> |
7511 |
<title>Extra Packages</title> |
7512 |
<subsection> |
7513 |
<title>Optional: installing extra packages</title> |
7514 |
<body> |
7515 |
|
7516 |
<p> |
7517 |
The LiveCD contains a number of available pre-built packages. If you wish to |
7518 |
install any of them, check the appropriate box. |
7519 |
</p> |
7520 |
|
7521 |
</body> |
7522 |
</subsection> |
7523 |
</section> |
7524 |
|
7525 |
<section> |
7526 |
<title>Startup Services</title> |
7527 |
<subsection> |
7528 |
<body> |
7529 |
|
7530 |
<p> |
7531 |
This screen allows you to choose various services to load at system boot. |
7532 |
Study the available options and their descriptions carefully, and then select |
7533 |
your desired services. For example, if you have chosen to install |
7534 |
<c>xorg-x11</c> and want to boot straight into a graphical desktop, then you |
7535 |
would select "xdm" from the list. |
7536 |
</p> |
7537 |
|
7538 |
</body> |
7539 |
</subsection> |
7540 |
</section> |
7541 |
|
7542 |
<section> |
7543 |
<title>Other Settings</title> |
7544 |
<subsection> |
7545 |
<title>Miscellaneous options</title> |
7546 |
<body> |
7547 |
|
7548 |
<p> |
7549 |
Now you will be able to change various settings, including keyboard layout, |
7550 |
graphical display manager, the default editor, and whether to set your |
7551 |
hardware clock to UTC or local time. |
7552 |
</p> |
7553 |
|
7554 |
</body> |
7555 |
</subsection> |
7556 |
</section> |
7557 |
|
7558 |
<section> |
7559 |
<title>Users</title> |
7560 |
<subsection> |
7561 |
<title>Adding users and groups</title> |
7562 |
<body> |
7563 |
|
7564 |
<p> |
7565 |
First set the root password for the system administrator (the <e>root</e> |
7566 |
user). |
7567 |
</p> |
7568 |
|
7569 |
<p> |
7570 |
We <e>strongly</e> recommend that you create a regular user for daily work. |
7571 |
Working as root all the time is <e>dangerous</e> and should be avoided! Create |
7572 |
your users, add them to the appropriate groups, and set their passwords. You |
7573 |
can optionally change their home directories, select their login shell, and |
7574 |
set helpful comments. |
7575 |
</p> |
7576 |
|
7577 |
</body> |
7578 |
</subsection> |
7579 |
</section> |
7580 |
|
7581 |
<section> |
7582 |
<title>Review</title> |
7583 |
<subsection> |
7584 |
<title>Finishing up</title> |
7585 |
<body> |
7586 |
|
7587 |
<p> |
7588 |
Please take the time to double-check each step of the installation process, |
7589 |
ensuring that your system is properly configured. When you have finished |
7590 |
reviewing, you may save your progress and exit, or click <c>Install</c> to begin |
7591 |
automatically installing Gentoo. |
7592 |
</p> |
7593 |
|
7594 |
<p> |
7595 |
You are free to browse around on the LiveCD while the installation proceeds. |
7596 |
The installer window will alert you when it has finished. At that point, can |
7597 |
close the window by clicking the <c>x</c> in the top right corner. When you are |
7598 |
ready, you may log out and reboot. Make sure you remove the LiveCD during the |
7599 |
reboot. |
7600 |
</p> |
7601 |
|
7602 |
<p> |
7603 |
Congratulations, your system is now fully equipped! Continue with <uri |
7604 |
link="?part=1&chap=5">Where to go from here?</uri> to learn more about |
7605 |
Gentoo. |
7606 |
</p> |
7607 |
|
7608 |
</body> |
7609 |
</subsection> |
7610 |
</section> |
7611 |
</sections> |
7612 |
|
7613 |
|
7614 |
|
7615 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-hppa-bootloader.xml |
7616 |
|
7617 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-hppa-bootloader.xml?rev=1.1&view=markup |
7618 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-hppa-bootloader.xml?rev=1.1&content-type=text/plain |
7619 |
|
7620 |
Index: hb-install-hppa-bootloader.xml |
7621 |
=================================================================== |
7622 |
<?xml version='1.0' encoding='UTF-8'?> |
7623 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
7624 |
|
7625 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
7626 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
7627 |
|
7628 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-hppa-bootloader.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
7629 |
|
7630 |
<sections> |
7631 |
|
7632 |
<version>7.0</version> |
7633 |
<date>2006-08-30</date> |
7634 |
|
7635 |
<section> |
7636 |
<title>Installing PALO</title> |
7637 |
<body> |
7638 |
|
7639 |
<p> |
7640 |
On the PA-RISC platform, the boot loader is called palo. You can find |
7641 |
the configuration file in <path>/etc/palo.conf</path>. Here is a sample |
7642 |
configuration: |
7643 |
</p> |
7644 |
|
7645 |
<pre caption = "/etc/palo.conf example"> |
7646 |
--commandline=2/kernel-2.6.16.18-pa11 root=/dev/sda4 |
7647 |
--recoverykernel=/vmlinux.old |
7648 |
--init-partitioned=/dev/sda |
7649 |
</pre> |
7650 |
|
7651 |
<p> |
7652 |
The first line tells palo the location of the kernel and which boot parameters |
7653 |
it must use. <c>2/kernel-2.6.16.18-pa11</c> means the kernel named |
7654 |
<c>kernel-2.6.16.18-pa11</c> resides on the second partition. Beware, the path |
7655 |
to the kernel is relative to the partition, not to the root of your filesystem. |
7656 |
</p> |
7657 |
|
7658 |
<p> |
7659 |
The second line indicates which recovery kernel to use. If it is your |
7660 |
first install and you do not have a recovery kernel, please comment this |
7661 |
out. The third line indicates on which disk palo will reside. |
7662 |
</p> |
7663 |
|
7664 |
<p> |
7665 |
When configuration is done, just run <c>palo</c>. |
7666 |
</p> |
7667 |
|
7668 |
<pre caption = "Applying the PALO configuration"> |
7669 |
# <i>palo</i> |
7670 |
</pre> |
7671 |
|
7672 |
<p> |
7673 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
7674 |
</p> |
7675 |
|
7676 |
</body> |
7677 |
</section> |
7678 |
<section id="reboot"> |
7679 |
<title>Rebooting the System</title> |
7680 |
<subsection> |
7681 |
<body> |
7682 |
|
7683 |
<p> |
7684 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
7685 |
that one magical command you have been waiting for: <c>reboot</c>. |
7686 |
</p> |
7687 |
|
7688 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
7689 |
# <i>exit</i> |
7690 |
cdimage ~# <i>cd</i> |
7691 |
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
7692 |
cdimage ~# <i>reboot</i> |
7693 |
</pre> |
7694 |
|
7695 |
<p> |
7696 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
7697 |
booted again instead of your new Gentoo system. |
7698 |
</p> |
7699 |
|
7700 |
<p> |
7701 |
Once rebooted in your Gentoo installation, finish up with <uri |
7702 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
7703 |
</p> |
7704 |
|
7705 |
</body> |
7706 |
</subsection> |
7707 |
</section> |
7708 |
</sections> |
7709 |
|
7710 |
|
7711 |
|
7712 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-hppa-disk.xml |
7713 |
|
7714 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-hppa-disk.xml?rev=1.1&view=markup |
7715 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-hppa-disk.xml?rev=1.1&content-type=text/plain |
7716 |
|
7717 |
Index: hb-install-hppa-disk.xml |
7718 |
=================================================================== |
7719 |
<?xml version='1.0' encoding='UTF-8'?> |
7720 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
7721 |
|
7722 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
7723 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
7724 |
|
7725 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-hppa-disk.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
7726 |
|
7727 |
<sections> |
7728 |
|
7729 |
<version>7.1</version> |
7730 |
<date>2006-11-02</date> |
7731 |
|
7732 |
<section> |
7733 |
<title>Introduction to Block Devices</title> |
7734 |
<subsection> |
7735 |
<title>Block Devices</title> |
7736 |
<body> |
7737 |
|
7738 |
<p> |
7739 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
7740 |
and Linux in general, including Linux filesystems, partitions and block devices. |
7741 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
7742 |
you'll be guided through the process of setting up partitions and filesystems |
7743 |
for your Gentoo Linux installation. |
7744 |
</p> |
7745 |
|
7746 |
<p> |
7747 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
7748 |
probably the one that represents the first SCSI HD in a Linux system, namely |
7749 |
<path>/dev/sda</path>. |
7750 |
</p> |
7751 |
|
7752 |
<p> |
7753 |
The block devices above represent an abstract interface to the disk. User |
7754 |
programs can use these block devices to interact with your disk without worrying |
7755 |
about whether your drives are IDE, SCSI or something else. The program can |
7756 |
simply address the storage on the disk as a bunch of contiguous, |
7757 |
randomly-accessible 512-byte blocks. |
7758 |
</p> |
7759 |
|
7760 |
</body> |
7761 |
</subsection> |
7762 |
<subsection> |
7763 |
<title>Partitions and Slices</title> |
7764 |
<body> |
7765 |
|
7766 |
<p> |
7767 |
Although it is theoretically possible to use a full disk to house your Linux |
7768 |
system, this is almost never done in practice. Instead, full disk block devices |
7769 |
are split up in smaller, more manageable block devices. On most systems, |
7770 |
these are called <e>partitions</e>. Other architectures use a similar technique, |
7771 |
called <e>slices</e>. |
7772 |
</p> |
7773 |
|
7774 |
</body> |
7775 |
</subsection> |
7776 |
</section> |
7777 |
<section> |
7778 |
<title>Designing a Partitioning Scheme</title> |
7779 |
<subsection> |
7780 |
<title>How Many and How Big?</title> |
7781 |
<body> |
7782 |
|
7783 |
<p> |
7784 |
The number of partitions is highly dependent on your environment. For instance, |
7785 |
if you have lots of users, you will most likely want to have your |
7786 |
<path>/home</path> separate as it increases security and makes backups easier. |
7787 |
If you are installing Gentoo to perform as a mailserver, your |
7788 |
<path>/var</path> should be separate as all mails are stored inside |
7789 |
<path>/var</path>. A good choice of filesystem will then maximise your |
7790 |
performance. Gameservers will have a separate <path>/opt</path> as most gaming |
7791 |
servers are installed there. The reason is similar for <path>/home</path>: |
7792 |
security and backups. You will definitely want to keep <path>/usr</path> big: |
7793 |
not only will it contain the majority of applications, the Portage tree alone |
7794 |
takes around 500 Mbyte excluding the various sources that are stored in it. |
7795 |
</p> |
7796 |
|
7797 |
<p> |
7798 |
As you can see, it very much depends on what you want to achieve. Separate |
7799 |
partitions or volumes have the following advantages: |
7800 |
</p> |
7801 |
|
7802 |
<ul> |
7803 |
<li> |
7804 |
You can choose the best performing filesystem for each partition or volume |
7805 |
</li> |
7806 |
<li> |
7807 |
Your entire system cannot run out of free space if one defunct tool is |
7808 |
continuously writing files to a partition or volume |
7809 |
</li> |
7810 |
<li> |
7811 |
If necessary, file system checks are reduced in time, as multiple checks can |
7812 |
be done in parallel (although this advantage is more with multiple disks than |
7813 |
it is with multiple partitions) |
7814 |
</li> |
7815 |
<li> |
7816 |
Security can be enhanced by mounting some partitions or volumes read-only, |
7817 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
7818 |
</li> |
7819 |
</ul> |
7820 |
|
7821 |
<p> |
7822 |
However, multiple partitions have one big disadvantage: if not configured |
7823 |
properly, you might result in having a system with lots |
7824 |
of free space on one partition and none on another. There is also a 15-partition |
7825 |
limit for SCSI and SATA. |
7826 |
</p> |
7827 |
|
7828 |
</body> |
7829 |
</subsection> |
7830 |
</section> |
7831 |
<section> |
7832 |
<title>Using fdisk on HPPA to Partition your Disk</title> |
7833 |
<body> |
7834 |
|
7835 |
<p> |
7836 |
Use <c>fdisk</c> to create the partitions you want: |
7837 |
</p> |
7838 |
|
7839 |
<pre caption="Partitioning the disk"> |
7840 |
# <i>fdisk /dev/sda</i> |
7841 |
</pre> |
7842 |
|
7843 |
<p> |
7844 |
HPPA machines use the PC standard DOS partition tables. To create a new |
7845 |
DOS partition table, simply use the <c>o</c> command. |
7846 |
</p> |
7847 |
|
7848 |
<pre caption="Creating a DOS partition table"> |
7849 |
# <i>fdisk /dev/sda</i> |
7850 |
|
7851 |
Command (m for help): <i>o</i> |
7852 |
Building a new DOS disklabel. |
7853 |
</pre> |
7854 |
|
7855 |
<p> |
7856 |
PALO (the HPPA bootloader) needs a special partition to work. You have |
7857 |
to create a partition of at least 16MB at the beginning of your disk. |
7858 |
The partition type must be of type <e>f0</e> (Linux/PA-RISC boot). |
7859 |
</p> |
7860 |
|
7861 |
<impo> |
7862 |
If you ignore this and continue without a special PALO partition, your system |
7863 |
will stop loving you and fail to start. Also, if your disk is larger than 2GB, |
7864 |
make sure that the boot partition is in the first 2GB of your disk. PALO is |
7865 |
unable to read a kernel after the 2GB limit. |
7866 |
</impo> |
7867 |
|
7868 |
<pre caption="A simple default partition schema"> |
7869 |
# <i>cat /etc/fstab</i> |
7870 |
/dev/sda2 /boot ext3 noauto,noatime 1 1 |
7871 |
/dev/sda3 none swap sw 0 0 |
7872 |
/dev/sda4 / ext3 noatime 0 0 |
7873 |
|
7874 |
# <i>fdisk /dev/sda</i> |
7875 |
|
7876 |
Command (m for help): <i>p</i> |
7877 |
|
7878 |
Disk /dev/sda: 4294 MB, 4294816768 bytes |
7879 |
133 heads, 62 sectors/track, 1017 cylinders |
7880 |
Units = cylinders of 8246 * 512 = 4221952 bytes |
7881 |
|
7882 |
Device Boot Start End Blocks Id System |
7883 |
/dev/sda1 1 8 32953 f0 Linux/PA-RISC boot |
7884 |
/dev/sda2 9 20 49476 83 Linux |
7885 |
/dev/sda3 21 70 206150 82 Linux swap |
7886 |
/dev/sda4 71 1017 3904481 83 Linux |
7887 |
</pre> |
7888 |
|
7889 |
<p> |
7890 |
Now that your partitions are created, you can now continue with <uri |
7891 |
link="#filesystems">Creating Filesystems</uri>. |
7892 |
</p> |
7893 |
|
7894 |
</body> |
7895 |
</section> |
7896 |
<section id="filesystems"> |
7897 |
<title>Creating Filesystems</title> |
7898 |
<subsection> |
7899 |
<title>Introduction</title> |
7900 |
<body> |
7901 |
|
7902 |
<p> |
7903 |
Now that your partitions are created, it is time to place a filesystem on them. |
7904 |
If you don't care about what filesystem to choose and are happy with what we use |
7905 |
as default in this handbook, continue with <uri |
7906 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
7907 |
Otherwise read on to learn about the available filesystems... |
7908 |
</p> |
7909 |
|
7910 |
</body> |
7911 |
</subsection> |
7912 |
<subsection> |
7913 |
<title>Filesystems?</title> |
7914 |
<body> |
7915 |
|
7916 |
<p> |
7917 |
Several filesystems are available. Ext2, ext3, XFS and reiserfs are found stable on |
7918 |
the HPPA architecture. The others are very experimental. |
7919 |
</p> |
7920 |
|
7921 |
<p> |
7922 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
7923 |
journaling, which means that routine ext2 filesystem checks at startup time can |
7924 |
be quite time-consuming. There is now quite a selection of newer-generation |
7925 |
journaled filesystems that can be checked for consistency very quickly and are |
7926 |
thus generally preferred over their non-journaled counterparts. Journaled |
7927 |
filesystems prevent long delays when you boot your system and your filesystem |
7928 |
happens to be in an inconsistent state. |
7929 |
</p> |
7930 |
|
7931 |
<p> |
7932 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
7933 |
journaling for fast recovery in addition to other enhanced journaling modes |
7934 |
like full data and ordered data journaling. It uses a hashed B*-tree index that |
7935 |
enables high performance in almost all situations. In short, ext3 is a very |
7936 |
good and reliable filesystem. |
7937 |
</p> |
7938 |
|
7939 |
<p> |
7940 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
7941 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
7942 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
7943 |
extremely well and has metadata journaling. ReiserFS is solid and usable as |
7944 |
both general-purpose filesystem and for extreme cases such as the creation of |
7945 |
large filesystems, very large files and directories containing tens of |
7946 |
thousands of small files. |
7947 |
</p> |
7948 |
|
7949 |
<p> |
7950 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
7951 |
feature-set and is optimized for scalability. We only recommend using this |
7952 |
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
7953 |
an uninterruptible power supply. Because XFS aggressively caches in-transit data |
7954 |
in RAM, improperly designed programs (those that don't take proper precautions |
7955 |
when writing files to disk and there are quite a few of them) can lose a good |
7956 |
deal of data if the system goes down unexpectedly. |
7957 |
</p> |
7958 |
|
7959 |
<p> |
7960 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
7961 |
become production-ready and there hasn't been a sufficient track record to |
7962 |
comment positively nor negatively on its general stability at this point. |
7963 |
</p> |
7964 |
|
7965 |
</body> |
7966 |
</subsection> |
7967 |
<subsection id="filesystems-apply"> |
7968 |
<title>Applying a Filesystem to a Partition</title> |
7969 |
<body> |
7970 |
|
7971 |
<p> |
7972 |
To create a filesystem on a partition or volume, there are tools available for |
7973 |
each possible filesystem: |
7974 |
</p> |
7975 |
|
7976 |
<table> |
7977 |
<tr> |
7978 |
<th>Filesystem</th> |
7979 |
<th>Creation Command</th> |
7980 |
</tr> |
7981 |
<tr> |
7982 |
<ti>ext2</ti> |
7983 |
<ti><c>mke2fs</c></ti> |
7984 |
</tr> |
7985 |
<tr> |
7986 |
<ti>ext3</ti> |
7987 |
<ti><c>mke2fs -j</c></ti> |
7988 |
</tr> |
7989 |
<tr> |
7990 |
<ti>reiserfs</ti> |
7991 |
<ti><c>mkreiserfs</c></ti> |
7992 |
</tr> |
7993 |
<tr> |
7994 |
<ti>xfs</ti> |
7995 |
<ti><c>mkfs.xfs</c></ti> |
7996 |
</tr> |
7997 |
<tr> |
7998 |
<ti>jfs</ti> |
7999 |
<ti><c>mkfs.jfs</c></ti> |
8000 |
</tr> |
8001 |
</table> |
8002 |
|
8003 |
<p> |
8004 |
For instance, to have the boot partition (<path>/dev/sda2</path> in our |
8005 |
example) in ext2 and the root partition (<path>/dev/sda4</path> in our example) |
8006 |
in ext3 (as in our example), you would use: |
8007 |
</p> |
8008 |
|
8009 |
<pre caption="Applying a filesystem on a partition"> |
8010 |
# <i>mke2fs /dev/sda2</i> |
8011 |
# <i>mke2fs -j /dev/sda4</i> |
8012 |
</pre> |
8013 |
|
8014 |
<p> |
8015 |
Now create the filesystems on your newly created partitions (or logical |
8016 |
volumes). |
8017 |
</p> |
8018 |
|
8019 |
</body> |
8020 |
</subsection> |
8021 |
<subsection> |
8022 |
<title>Activating the Swap Partition</title> |
8023 |
<body> |
8024 |
|
8025 |
<p> |
8026 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
8027 |
</p> |
8028 |
|
8029 |
<pre caption="Creating a Swap signature"> |
8030 |
# <i>mkswap /dev/sda3</i> |
8031 |
</pre> |
8032 |
|
8033 |
<p> |
8034 |
To activate the swap partition, use <c>swapon</c>: |
8035 |
</p> |
8036 |
|
8037 |
<pre caption="Activating the swap partition"> |
8038 |
# <i>swapon /dev/sda3</i> |
8039 |
</pre> |
8040 |
|
8041 |
<p> |
8042 |
Create and activate the swap now. |
8043 |
</p> |
8044 |
|
8045 |
</body> |
8046 |
</subsection> |
8047 |
</section> |
8048 |
<section> |
8049 |
<title>Mounting</title> |
8050 |
<body> |
8051 |
|
8052 |
<p> |
8053 |
Now that your partitions are initialized and are housing a filesystem, it is |
8054 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
8055 |
create the necessary mount directories for every partition you created. As an |
8056 |
example we mount the root and boot partition: |
8057 |
</p> |
8058 |
|
8059 |
<pre caption="Mounting partitions"> |
8060 |
# <i>mount /dev/sda4 /mnt/gentoo</i> |
8061 |
# <i>mkdir /mnt/gentoo/boot</i> |
8062 |
# <i>mount /dev/sda2 /mnt/gentoo/boot</i> |
8063 |
</pre> |
8064 |
|
8065 |
<note> |
8066 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
8067 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
8068 |
also holds for <path>/var/tmp</path>. |
8069 |
</note> |
8070 |
|
8071 |
<p> |
8072 |
We will also have to mount the proc filesystem (a virtual interface with the |
8073 |
kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. |
8074 |
</p> |
8075 |
|
8076 |
<p> |
8077 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
8078 |
Installation Files</uri>. |
8079 |
</p> |
8080 |
|
8081 |
</body> |
8082 |
</section> |
8083 |
</sections> |
8084 |
|
8085 |
|
8086 |
|
8087 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-hppa-kernel.xml |
8088 |
|
8089 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-hppa-kernel.xml?rev=1.1&view=markup |
8090 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-hppa-kernel.xml?rev=1.1&content-type=text/plain |
8091 |
|
8092 |
Index: hb-install-hppa-kernel.xml |
8093 |
=================================================================== |
8094 |
<?xml version='1.0' encoding='UTF-8'?> |
8095 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
8096 |
|
8097 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
8098 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
8099 |
|
8100 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-hppa-kernel.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
8101 |
|
8102 |
<sections> |
8103 |
|
8104 |
<version>7.3</version> |
8105 |
<date>2007-03-12</date> |
8106 |
|
8107 |
<section> |
8108 |
<title>Timezone</title> |
8109 |
<body> |
8110 |
|
8111 |
<p> |
8112 |
You first need to select your timezone so that your system knows where it is |
8113 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
8114 |
it to <path>/etc/localtime</path>. Please avoid the |
8115 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
8116 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
8117 |
</p> |
8118 |
|
8119 |
<pre caption="Setting the timezone information"> |
8120 |
# <i>ls /usr/share/zoneinfo</i> |
8121 |
<comment>(Suppose you want to use GMT)</comment> |
8122 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
8123 |
</pre> |
8124 |
|
8125 |
</body> |
8126 |
</section> |
8127 |
<section> |
8128 |
<title>Installing the Sources</title> |
8129 |
<subsection> |
8130 |
<title>Choosing a Kernel</title> |
8131 |
<body> |
8132 |
|
8133 |
<p> |
8134 |
The core around which all distributions are built is the Linux kernel. It is the |
8135 |
layer between the user programs and your system hardware. Gentoo provides its |
8136 |
users several possible kernel sources. A full listing with description is |
8137 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
8138 |
Guide</uri>. |
8139 |
</p> |
8140 |
|
8141 |
<p> |
8142 |
For HPPA we have <c>hppa-sources</c>. By default these sources are based on the |
8143 |
2.6 kernel sources. If you want to install a 2.4 kernel, you will need to |
8144 |
install Gentoo from a working Internet connection as we do not supply those |
8145 |
sources on our Installation CD. Continue by installing the kernel source. |
8146 |
</p> |
8147 |
|
8148 |
<pre caption="Installing a kernel source"> |
8149 |
# <i>emerge hppa-sources</i> |
8150 |
</pre> |
8151 |
|
8152 |
<p> |
8153 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
8154 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
8155 |
kernel source points to <c>hppa-sources-2.6.16.18-pa11</c>. Your version may be |
8156 |
different, so keep this in mind. |
8157 |
</p> |
8158 |
|
8159 |
<pre caption="Viewing the kernel source symlink"> |
8160 |
# <i>ls -l /usr/src/linux</i> |
8161 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> hppa-sources-2.6.16.18-pa11 |
8162 |
</pre> |
8163 |
|
8164 |
<p> |
8165 |
Now it is time to configure and compile your kernel source. All architectures |
8166 |
can use <c>genkernel</c> for this, which will build a generic kernel as used |
8167 |
by the Installation CD. We explain the "manual" configuration first though, as |
8168 |
it is the best way to optimize your environment. |
8169 |
</p> |
8170 |
|
8171 |
<p> |
8172 |
If you want to manually configure your kernel, continue now with <uri |
8173 |
link="#manual">Default: Manual Configuration</uri>. If you want to use |
8174 |
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
8175 |
genkernel</uri> instead. |
8176 |
</p> |
8177 |
|
8178 |
</body> |
8179 |
</subsection> |
8180 |
</section> |
8181 |
<section id="manual"> |
8182 |
<title>Default: Manual Configuration</title> |
8183 |
<subsection> |
8184 |
<title>Introduction</title> |
8185 |
<body> |
8186 |
|
8187 |
<p> |
8188 |
Manually configuring a kernel is often seen as the most difficult procedure a |
8189 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
8190 |
couple of kernels you don't even remember that it was difficult ;) |
8191 |
</p> |
8192 |
|
8193 |
<p> |
8194 |
However, one thing <e>is</e> true: you must know your system when you start |
8195 |
configuring a kernel manually. Most information can be gathered by emerging |
8196 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
8197 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
8198 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
8199 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
8200 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
8201 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
8202 |
uses (it might provide you with a nice hint on what to enable). |
8203 |
</p> |
8204 |
|
8205 |
<p> |
8206 |
Now go to your kernel source directory and execute <c>make menuconfig</c>. This |
8207 |
will fire up an ncurses-based configuration menu. |
8208 |
</p> |
8209 |
|
8210 |
<pre caption="Invoking menuconfig"> |
8211 |
# <i>cd /usr/src/linux</i> |
8212 |
# <i>make menuconfig</i> |
8213 |
</pre> |
8214 |
|
8215 |
<p> |
8216 |
You will be greeted with several configuration sections. We'll first list some |
8217 |
options you must activate (otherwise Gentoo will not function, or not function |
8218 |
properly without additional tweaks). |
8219 |
</p> |
8220 |
|
8221 |
</body> |
8222 |
</subsection> |
8223 |
<subsection> |
8224 |
<title>Activating Required Options</title> |
8225 |
<body> |
8226 |
|
8227 |
<p> |
8228 |
First of all, activate the use of development and experimental code/drivers. |
8229 |
You need this, otherwise some very important code/drivers won't show up: |
8230 |
</p> |
8231 |
|
8232 |
<pre caption="Selecting experimental code/drivers"> |
8233 |
Code maturity level options ---> |
8234 |
[*] Prompt for development and/or incomplete code/drivers |
8235 |
</pre> |
8236 |
|
8237 |
<p> |
8238 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
8239 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
8240 |
able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc |
8241 |
file system</c>. |
8242 |
</p> |
8243 |
|
8244 |
<pre caption="Selecting necessary file systems"> |
8245 |
File systems ---> |
8246 |
Pseudo Filesystems ---> |
8247 |
[*] /proc file system support |
8248 |
[*] Virtual memory file system support (former shm fs) |
8249 |
|
8250 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
8251 |
<*> Reiserfs support |
8252 |
<*> Ext3 journalling file system support |
8253 |
<*> JFS filesystem support |
8254 |
<*> Second extended fs support |
8255 |
<*> XFS filesystem support |
8256 |
</pre> |
8257 |
|
8258 |
<p> |
8259 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
8260 |
modem, you will need the following options in the kernel: |
8261 |
</p> |
8262 |
|
8263 |
<pre caption="Selecting PPPoE necessary drivers"> |
8264 |
Device Drivers ---> |
8265 |
Networking support ---> |
8266 |
<*> PPP (point-to-point protocol) support |
8267 |
<*> PPP support for async serial ports |
8268 |
<*> PPP support for sync tty ports |
8269 |
</pre> |
8270 |
|
8271 |
<p> |
8272 |
The two compression options won't harm but are not definitely needed, neither |
8273 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
8274 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
8275 |
</p> |
8276 |
|
8277 |
<p> |
8278 |
If you require it, don't forget to include support in the kernel for your |
8279 |
ethernet card. |
8280 |
</p> |
8281 |
|
8282 |
<p> |
8283 |
If you have a HIL mouse or keyboard, do not forget to compile in support for |
8284 |
them. |
8285 |
</p> |
8286 |
|
8287 |
<pre caption="Activating HIL support"> |
8288 |
Input core support ---> |
8289 |
[*] Keyboard support |
8290 |
[*] Mouse support |
8291 |
[*] Event interface support |
8292 |
</pre> |
8293 |
|
8294 |
<p> |
8295 |
If you have no mouse on your HIL port, only use the basic support: |
8296 |
</p> |
8297 |
|
8298 |
<pre caption="Basic HIL support"> |
8299 |
HIL support ---> |
8300 |
[*] HIL Keyboard (basic) support |
8301 |
</pre> |
8302 |
|
8303 |
<p> |
8304 |
If you however want <e>full</e> HIL support, select the following options: |
8305 |
</p> |
8306 |
|
8307 |
<pre caption="Full HIL support"> |
8308 |
HIL support ---> |
8309 |
[*] HP System Device Controller i8042 Support |
8310 |
[*] HIL MLC Support |
8311 |
[*] HIL Keyboard (full) support |
8312 |
[*] HIL Mouse & Pointer support |
8313 |
</pre> |
8314 |
|
8315 |
<p> |
8316 |
Also include display driver support: |
8317 |
</p> |
8318 |
|
8319 |
<pre caption="Display Driver support"> |
8320 |
Graphics support ---> |
8321 |
[*] Support for frame buffer devices |
8322 |
[*] HP STI frame buffer device support |
8323 |
Console display driver support ---> |
8324 |
[*] STI text console |
8325 |
</pre> |
8326 |
|
8327 |
<p> |
8328 |
When you're done configuring your kernel, continue with <uri |
8329 |
link="#compiling">Compiling and Installing</uri>. |
8330 |
</p> |
8331 |
|
8332 |
</body> |
8333 |
</subsection> |
8334 |
<subsection id="compiling"> |
8335 |
<title>Compiling and Installing</title> |
8336 |
<body> |
8337 |
|
8338 |
<impo> |
8339 |
If you want to compile a 64-bit kernel, you'll need to emerge <c>kgcc64</c> |
8340 |
<e>after</e> you've finished installing Gentoo and rebooted. However, running a |
8341 |
64-bit kernel is discouraged. You should only run a 64-bit kernel if you have |
8342 |
more than 4GB of RAM or if your server requires it, i.e. on the A500. |
8343 |
</impo> |
8344 |
|
8345 |
<p> |
8346 |
Now that your kernel is configured, it is time to compile and install it. Exit |
8347 |
the configuration and start the compilation process: |
8348 |
</p> |
8349 |
|
8350 |
<pre caption="Compiling the kernel"> |
8351 |
# <i>make && make modules_install</i> |
8352 |
</pre> |
8353 |
|
8354 |
<p> |
8355 |
When the kernel has finished compiling, copy the kernel image to |
8356 |
<path>/boot</path>. Use whatever name you feel is appropriate for your kernel |
8357 |
choice and remember it as you will need it later on when you configure your |
8358 |
bootloader. Remember to replace <path><kernel-version></path> with the |
8359 |
name and version of your kernel. |
8360 |
</p> |
8361 |
|
8362 |
<pre caption="Installing the kernel"> |
8363 |
# <i>cp vmlinux /boot/<kernel-version></i> |
8364 |
</pre> |
8365 |
|
8366 |
<p> |
8367 |
Now continue with <uri link="#kernel_modules">Configuring Kernel |
8368 |
Modules</uri>. |
8369 |
</p> |
8370 |
|
8371 |
</body> |
8372 |
</subsection> |
8373 |
</section> |
8374 |
<section id="genkernel"> |
8375 |
<title>Alternative: Using genkernel</title> |
8376 |
<body> |
8377 |
|
8378 |
<p> |
8379 |
If you are reading this section, you have chosen to use our <c>genkernel</c> |
8380 |
script to configure your kernel for you. |
8381 |
</p> |
8382 |
|
8383 |
<p> |
8384 |
Now that your kernel source tree is installed, it's now time to compile your |
8385 |
kernel by using our <c>genkernel</c> script to automatically build a kernel for |
8386 |
you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
8387 |
way our Installation CD kernel is configured. This means that when you use |
8388 |
<c>genkernel</c> to build your kernel, your system will generally detect all |
8389 |
your hardware at boot-time, just like our Installation CD does. Because genkernel |
8390 |
doesn't require any manual kernel configuration, it is an ideal solution for |
8391 |
those users who may not be comfortable compiling their own kernels. |
8392 |
</p> |
8393 |
|
8394 |
<p> |
8395 |
Now, let's see how to use genkernel. First, emerge the genkernel ebuild: |
8396 |
</p> |
8397 |
|
8398 |
<pre caption="Emerging genkernel"> |
8399 |
# <i>emerge genkernel</i> |
8400 |
</pre> |
8401 |
|
8402 |
<p> |
8403 |
Now, compile your kernel sources by running <c>genkernel all</c>. |
8404 |
Be aware though, as <c>genkernel</c> compiles a kernel that supports almost all |
8405 |
hardware, this compilation will take quite a while to finish! |
8406 |
</p> |
8407 |
|
8408 |
<p> |
8409 |
Note that, if your boot partition doesn't use ext2 or ext3 as filesystem you |
8410 |
need to manually configure your kernel using <c>genkernel --menuconfig all</c> |
8411 |
and add support for your filesystem <e>in</e> the kernel (i.e. <e>not</e> as a |
8412 |
module). |
8413 |
</p> |
8414 |
|
8415 |
<pre caption="Running genkernel"> |
8416 |
# <i>genkernel all</i> |
8417 |
<comment>(Output removed to increase readability)</comment> |
8418 |
* Kernel compiled successfully! |
8419 |
* Required Kernel Params: |
8420 |
* : root=/dev/ram0 init=/linuxrc real_root=/dev/$ROOT |
8421 |
* where $ROOT is the devicenode for your root partition as |
8422 |
* you should have specified in /etc/fstab |
8423 |
* |
8424 |
* You MUST tell your bootloader to use the generated initrd |
8425 |
* |
8426 |
* Recommended Kernel Params: |
8427 |
* : vga=0x317 splash=verbose |
8428 |
* |
8429 |
* Do NOT report kernel bugs (configs included) as genkernel bugs. |
8430 |
* Make sure you have the latest genkernel before reporting bugs |
8431 |
* |
8432 |
* For more info see /usr/share/genkernel/README |
8433 |
</pre> |
8434 |
|
8435 |
<p> |
8436 |
Once <c>genkernel</c> completes, a kernel, full set of modules and |
8437 |
<e>initial root disk</e> (initrd) will be created. We will use the kernel |
8438 |
and initrd when configuring a boot loader later in this document. Write |
8439 |
down the names of the kernel and initrd as you will need it when writing |
8440 |
the bootloader configuration file. The initrd will be started immediately after |
8441 |
booting to perform hardware autodetection (just like on the Installation CD) |
8442 |
before your "real" system starts up. |
8443 |
</p> |
8444 |
|
8445 |
<pre caption="Checking the created kernel image name and initrd"> |
8446 |
# <i>ls /boot/kernel* /boot/initramfs*</i> |
8447 |
</pre> |
8448 |
|
8449 |
</body> |
8450 |
</section> |
8451 |
<section id="kernel_modules"> |
8452 |
<title>Configuring Kernel Modules</title> |
8453 |
<subsection> |
8454 |
<title>Configuring the Modules</title> |
8455 |
<body> |
8456 |
|
8457 |
<p> |
8458 |
You should list the modules you want automatically loaded in |
8459 |
<path>/etc/modules.autoload.d/kernel-2.6</path>. |
8460 |
You can add extra options to the modules too if you want. |
8461 |
</p> |
8462 |
|
8463 |
<p> |
8464 |
To view all available modules, run the following <c>find</c> command. Don't |
8465 |
forget to substitute "<kernel version>" with the version of the kernel you |
8466 |
just compiled: |
8467 |
</p> |
8468 |
|
8469 |
<pre caption="Viewing all available modules"> |
8470 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
8471 |
</pre> |
8472 |
|
8473 |
<p> |
8474 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
8475 |
<path>kernel-2.6</path> file and enter the module |
8476 |
name in it. |
8477 |
</p> |
8478 |
|
8479 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
8480 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
8481 |
</pre> |
8482 |
|
8483 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
8484 |
3c59x |
8485 |
</pre> |
8486 |
|
8487 |
<p> |
8488 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
8489 |
your System</uri>. |
8490 |
</p> |
8491 |
|
8492 |
</body> |
8493 |
</subsection> |
8494 |
</section> |
8495 |
</sections> |
8496 |
|
8497 |
|
8498 |
|
8499 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-hppa-medium.xml |
8500 |
|
8501 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-hppa-medium.xml?rev=1.1&view=markup |
8502 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-hppa-medium.xml?rev=1.1&content-type=text/plain |
8503 |
|
8504 |
Index: hb-install-hppa-medium.xml |
8505 |
=================================================================== |
8506 |
<?xml version='1.0' encoding='UTF-8'?> |
8507 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
8508 |
|
8509 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
8510 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
8511 |
|
8512 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-hppa-medium.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
8513 |
|
8514 |
<sections> |
8515 |
|
8516 |
<version>7.0</version> |
8517 |
<date>2006-08-30</date> |
8518 |
|
8519 |
<section> |
8520 |
<title>Hardware Requirements</title> |
8521 |
<subsection> |
8522 |
<title>Introduction</title> |
8523 |
<body> |
8524 |
|
8525 |
<p> |
8526 |
Before we start, we first list what hardware requirements you need to |
8527 |
successfully install Gentoo on your box. |
8528 |
</p> |
8529 |
|
8530 |
</body> |
8531 |
</subsection> |
8532 |
<subsection> |
8533 |
<title>Hardware Requirements</title> |
8534 |
<body> |
8535 |
|
8536 |
<p> |
8537 |
A list of supported hardware can be found on the <uri |
8538 |
link="http://www.pateam.org/list.html">PA Team website</uri>. You may find |
8539 |
additional information about your box in the <uri |
8540 |
link="http://hwdb.parisc-linux.org">Parisc-Linux Hardware Database</uri> and |
8541 |
the <uri link="http://www.openpa.net/cpu.html">processor list</uri> on |
8542 |
<uri>www.openpa.net</uri>. |
8543 |
</p> |
8544 |
|
8545 |
<p> |
8546 |
If you don't know which version of PA-RISC your box is using, please check the |
8547 |
links above to find out whether you're using version 1.1 or 2.0. You will need |
8548 |
this information later on. |
8549 |
</p> |
8550 |
|
8551 |
<table> |
8552 |
<tr> |
8553 |
<th>Memory</th> |
8554 |
<ti>64 MB</ti> |
8555 |
</tr> |
8556 |
<tr> |
8557 |
<th>Diskspace</th> |
8558 |
<ti>1.5 GB (excluding swap space)</ti> |
8559 |
</tr> |
8560 |
<tr> |
8561 |
<th>Swap space</th> |
8562 |
<ti>At least 256 MB</ti> |
8563 |
</tr> |
8564 |
</table> |
8565 |
|
8566 |
</body> |
8567 |
</subsection> |
8568 |
</section> |
8569 |
<!-- Copy/paste from hb-install-x86-medium.xml --> |
8570 |
<!-- START --> |
8571 |
<section> |
8572 |
<title>The Gentoo Universal Installation CD</title> |
8573 |
<subsection> |
8574 |
<title>Introduction</title> |
8575 |
<body> |
8576 |
|
8577 |
<p> |
8578 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
8579 |
Such a tarball is an archive that contains a minimal environment from |
8580 |
which you can succesfully install Gentoo Linux onto your system. |
8581 |
</p> |
8582 |
|
8583 |
<p> |
8584 |
Installations using a stage1 or stage2 tarball file are not documented in the |
8585 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
8586 |
FAQ</uri> on these matters. |
8587 |
</p> |
8588 |
|
8589 |
</body> |
8590 |
</subsection> |
8591 |
<subsection> |
8592 |
<title>Gentoo Universal Installation CD</title> |
8593 |
<body> |
8594 |
|
8595 |
<p> |
8596 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
8597 |
environment. It allows you to boot Linux from the CD. During the boot process |
8598 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
8599 |
Installation CDs are maintained by Gentoo developers. |
8600 |
</p> |
8601 |
|
8602 |
<p> |
8603 |
There currently are two Installation CDs available: |
8604 |
</p> |
8605 |
|
8606 |
<ul> |
8607 |
<li> |
8608 |
The Universal Installation CD contains everything you need to install |
8609 |
Gentoo. It provides stage3 files for common architectures, source code |
8610 |
for the extra applications you need to choose from and, of course, the |
8611 |
installation instructions for your architecture. |
8612 |
</li> |
8613 |
<li> |
8614 |
The Minimal Installation CD contains only a minimal environment that allows |
8615 |
you to boot up and configure your network so you can connect to the |
8616 |
Internet. It does not contain any additional files and cannot be used |
8617 |
during the current installation approach. |
8618 |
</li> |
8619 |
</ul> |
8620 |
|
8621 |
</body> |
8622 |
</subsection> |
8623 |
</section> |
8624 |
<!-- STOP --> |
8625 |
<section> |
8626 |
<title>Download, Burn and Boot the Gentoo Universal Installation CD</title> |
8627 |
<subsection> |
8628 |
<title>Downloading and Burning the Installation CD</title> |
8629 |
<body> |
8630 |
|
8631 |
<p> |
8632 |
You can download the Universal Installation CD from one of our <uri |
8633 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CD is located in |
8634 |
the <path>releases/hppa/2006.1/installcd</path> directory. |
8635 |
</p> |
8636 |
|
8637 |
<p> |
8638 |
Inside those directories you'll find ISO-files. Those are full CD images which |
8639 |
you can write on a CD-R. |
8640 |
</p> |
8641 |
|
8642 |
<p> |
8643 |
After downloading the file, you can verify its integrity to see if it is |
8644 |
corrupted or not: |
8645 |
</p> |
8646 |
|
8647 |
<ul> |
8648 |
<li> |
8649 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
8650 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
8651 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows) |
8652 |
</li> |
8653 |
<li> |
8654 |
You can verify the cryptographic signature that we provide. You need to |
8655 |
obtain the public key we use (17072058) before you proceed though. |
8656 |
</li> |
8657 |
</ul> |
8658 |
|
8659 |
<p> |
8660 |
To fetch our public key using the GnuPG application, run the following command: |
8661 |
</p> |
8662 |
|
8663 |
<pre caption="Obtaining the public key"> |
8664 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
8665 |
</pre> |
8666 |
|
8667 |
<p> |
8668 |
Now verify the signature: |
8669 |
</p> |
8670 |
|
8671 |
<pre caption="Verify the cryptographic signature"> |
8672 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
8673 |
</pre> |
8674 |
|
8675 |
<p> |
8676 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
8677 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
8678 |
<c>K3B</c> here; more information can be found in our <uri |
8679 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
8680 |
</p> |
8681 |
|
8682 |
<ul> |
8683 |
<li> |
8684 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
8685 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
8686 |
path). |
8687 |
</li> |
8688 |
<li> |
8689 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
8690 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
8691 |
<c>Start</c>. |
8692 |
</li> |
8693 |
</ul> |
8694 |
|
8695 |
</body> |
8696 |
</subsection> |
8697 |
<subsection> |
8698 |
<title>Booting the Universal Installation CD</title> |
8699 |
<body> |
8700 |
|
8701 |
<note> |
8702 |
If you have problems booting the Installation CD or any other media, please |
8703 |
read the <uri |
8704 |
link="http://www.tldp.org/HOWTO/PA-RISC-Linux-Boot-HOWTO/index.html"> |
8705 |
PA-RISC Linux Boot HOWTO</uri>. |
8706 |
</note> |
8707 |
|
8708 |
<p> |
8709 |
Boot your HPPA system. During the boot process, you will see a message similar |
8710 |
to the following: |
8711 |
</p> |
8712 |
|
8713 |
<pre caption="HPPA boot message"> |
8714 |
Searching for Potential Boot Devices. |
8715 |
To terminate search, press and hold the ESCAPE key. |
8716 |
</pre> |
8717 |
|
8718 |
<p> |
8719 |
When this message appears, press and hold the Esc-key until an option menu |
8720 |
appears. This can take a while, be patient. By default, you should enter the |
8721 |
BOOT_ADMIN console. If you receive an option menu, choose <c>Enter Boot |
8722 |
Administration mode</c> to enter the BOOT_ADMIN console. You should now have an |
8723 |
'>' prompt. |
8724 |
</p> |
8725 |
|
8726 |
<p> |
8727 |
Put the Gentoo Installation CD in the CD-ROM. If you do not know the SCSI ID of |
8728 |
your CD-ROM drive, your PA-RISC station will search for it when you issue the |
8729 |
<c>search</c> command. |
8730 |
</p> |
8731 |
|
8732 |
<pre caption="Searching for SCSI ID"> |
8733 |
> <i>search</i> |
8734 |
Searching for Devices with Bootable Media. |
8735 |
To terminate search, please press and hold the ESCAPE key. |
8736 |
</pre> |
8737 |
|
8738 |
<p> |
8739 |
Your PA-RISC station will now display all the available boot media. This is an |
8740 |
example result of this command: |
8741 |
</p> |
8742 |
|
8743 |
<pre caption="Available boot media"> |
8744 |
Device Selection Device Path Device Type and Utilities |
8745 |
--------------------------------------------------------------------------- |
8746 |
|
8747 |
P0 scsi.5.0 TOSHIBA CD-ROM XM-3301TA |
8748 |
IPL |
8749 |
P1 scsi.2.0 COMPAQ ST32550N |
8750 |
IPL |
8751 |
P2 lan.0010a7-06d1b6.3.6 server |
8752 |
IPL |
8753 |
</pre> |
8754 |
|
8755 |
<p> |
8756 |
To boot from a CD-ROM you need the accompanying Device Path. For instance, if we |
8757 |
want to boot from the TOSHIBA CD-ROM in the above example, we would need to type |
8758 |
the following command: |
8759 |
</p> |
8760 |
|
8761 |
<pre caption="Booting from a CD-ROM"> |
8762 |
> <i>boot scsi.5.0 ipl</i> |
8763 |
|
8764 |
Trying scsi.5.0 |
8765 |
</pre> |
8766 |
|
8767 |
<p> |
8768 |
The <c>ipl</c> keyword (Initial Program Loader) tells palo (the PA-RISC boot |
8769 |
LOader) to enter interactive mode. This will allow you to change, for example, |
8770 |
the kernel boot parameters. |
8771 |
</p> |
8772 |
|
8773 |
<p> |
8774 |
When the boot is successful, palo will start in interactive mode: |
8775 |
</p> |
8776 |
|
8777 |
<pre caption="PALO Interactive Mode"> |
8778 |
Boot path initialized. |
8779 |
Attempting to load IPL. |
8780 |
|
8781 |
|
8782 |
HARD Booted. |
8783 |
palo ipl 1.5 root@hope Sat Apr 23 18:06:47 CEST 2005 |
8784 |
|
8785 |
Boot image contains: |
8786 |
0/vmlinux32 6241293 bytes @ 0x3904000 |
8787 |
0/vmlinux64 8352719 bytes @ 0x3ef8000 |
8788 |
0/ramdisk 1007589 bytes @ 0x105800 |
8789 |
|
8790 |
Information: No console specified on kernel command line. This is normal. |
8791 |
PALO will choose the console currently used by firmware (serial).Current command line: |
8792 |
0/vmlinux initrd=initrd TERM=linux root=/dev/ram0 init=/linuxrc cdroot looptype=squashfs loop=/livecd.squashfs hda=scsi console=ttyS0 |
8793 |
0: 0/vmlinux |
8794 |
1: initrd=initrd |
8795 |
2: TERM=linux |
8796 |
3: root=/dev/ram0 |
8797 |
4: init=/linuxrc |
8798 |
5: cdroot |
8799 |
6: looptype=squashfs |
8800 |
7: loop=/livecd.squashfs |
8801 |
8: hda=scsi |
8802 |
9: console=ttyS0 |
8803 |
|
8804 |
<#> edit the numbered field |
8805 |
'b' boot with this command line |
8806 |
'r' restore command line |
8807 |
'l' list dir |
8808 |
</pre> |
8809 |
|
8810 |
<p> |
8811 |
These parameters are suitable for most situations. |
8812 |
</p> |
8813 |
|
8814 |
<p> |
8815 |
If you need extra features you must add the appropriate keyword(s) to the end of |
8816 |
the command line. To add a keyword, edit the last field, add a space and type |
8817 |
your keyword. The only implemented keywords as of now are <c>cdcache</c> which |
8818 |
tells the Installation CD to load itself into RAM, allowing you to unmount the |
8819 |
CD, and <c>noload=module1[,module2[,...]]</c> which allows you to explicitly |
8820 |
disable loading of particular modules. |
8821 |
</p> |
8822 |
|
8823 |
<pre caption="Adding hdb=scsi as boot option"> |
8824 |
(or 'b' to boot with this command line)? <i>9</i> |
8825 |
console=ttyS0 <i>hdb=scsi</i> |
8826 |
</pre> |
8827 |
|
8828 |
<p> |
8829 |
Now that you have tweaked your kernel boot params, boot it. |
8830 |
</p> |
8831 |
|
8832 |
<pre caption="Booting the kernel"> |
8833 |
(or 'b' to boot with this command line)? <i>b</i> |
8834 |
</pre> |
8835 |
|
8836 |
<p> |
8837 |
You should have a root ("#") prompt on the current console and can also switch |
8838 |
to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get back to the one you |
8839 |
started on by pressing Alt-F1. |
8840 |
</p> |
8841 |
|
8842 |
<p> |
8843 |
Now continue with <uri link="#hardware">Extra Hardware |
8844 |
Configuration</uri>. |
8845 |
</p> |
8846 |
|
8847 |
</body> |
8848 |
</subsection> |
8849 |
<subsection id="hardware"> |
8850 |
<title>Extra Hardware Configuration</title> |
8851 |
<body> |
8852 |
|
8853 |
<p> |
8854 |
Most hppa machines have an onboard ethernet card. Old ones use the lasi driver |
8855 |
which is compiled in the kernel. Newer ones need the tulip driver which is |
8856 |
compiled as a module. To use the latter, you need to load its driver. |
8857 |
</p> |
8858 |
|
8859 |
<p> |
8860 |
In the next example, we try to load the <c>tulip</c> module (support for |
8861 |
certain kinds of network interfaces): |
8862 |
</p> |
8863 |
|
8864 |
<pre caption="Loading kernel modules"> |
8865 |
# <i>modprobe tulip</i> |
8866 |
</pre> |
8867 |
|
8868 |
</body> |
8869 |
</subsection> |
8870 |
|
8871 |
<subsection id="useraccounts"> |
8872 |
<title>Optional: User Accounts</title> |
8873 |
<body> |
8874 |
|
8875 |
<p> |
8876 |
If you plan on giving other people access to your installation |
8877 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
8878 |
security reasons), you need to create the necessary user accounts and change |
8879 |
the root password. |
8880 |
</p> |
8881 |
|
8882 |
<p> |
8883 |
To change the root password, use the <c>passwd</c> utility: |
8884 |
</p> |
8885 |
|
8886 |
<pre caption="Changing the root password"> |
8887 |
# <i>passwd</i> |
8888 |
New password: <comment>(Enter your new password)</comment> |
8889 |
Re-enter password: <comment>(Re-enter your password)</comment> |
8890 |
</pre> |
8891 |
|
8892 |
<p> |
8893 |
To create a user account, we first enter their credentials, followed by |
8894 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
8895 |
In the next example, we create a user called "john". |
8896 |
</p> |
8897 |
|
8898 |
<pre caption="Creating a user account"> |
8899 |
# <i>useradd -m -G users john</i> |
8900 |
# <i>passwd john</i> |
8901 |
New password: <comment>(Enter john's password)</comment> |
8902 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
8903 |
</pre> |
8904 |
|
8905 |
<p> |
8906 |
You can change your user id from root to the newly created user by using |
8907 |
<c>su</c>: |
8908 |
</p> |
8909 |
|
8910 |
<pre caption="Changing user id"> |
8911 |
# <i>su - john</i> |
8912 |
</pre> |
8913 |
|
8914 |
</body> |
8915 |
</subsection> |
8916 |
<subsection> |
8917 |
<title>Optional: Viewing Documentation while Installing</title> |
8918 |
<body> |
8919 |
|
8920 |
<p> |
8921 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
8922 |
installation, make sure you have created a user account (see <uri |
8923 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
8924 |
go to a new terminal and log in. |
8925 |
</p> |
8926 |
|
8927 |
<p> |
8928 |
If you want to view the documentation on the CD you can immediately run |
8929 |
<c>links</c> to read it: |
8930 |
</p> |
8931 |
|
8932 |
<pre caption="Viewing the on-CD documentation"> |
8933 |
# <i>links /mnt/cdrom/docs/handbook/html/index.html</i> |
8934 |
</pre> |
8935 |
|
8936 |
<p> |
8937 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
8938 |
more recent than the one provided on the CD. You can view it using <c>links</c> |
8939 |
as well, but only after having completed the <e>Configuring your Network</e> |
8940 |
chapter (otherwise you won't be able to go on the Internet to view the |
8941 |
document): |
8942 |
</p> |
8943 |
|
8944 |
<pre caption="Viewing the Online Documentation"> |
8945 |
# <i>links http://www.gentoo.org/doc/en/handbook/handbook-hppa.xml</i> |
8946 |
</pre> |
8947 |
|
8948 |
<p> |
8949 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
8950 |
</p> |
8951 |
|
8952 |
</body> |
8953 |
</subsection> |
8954 |
<subsection> |
8955 |
<title>Optional: Starting the SSH Daemon</title> |
8956 |
<body> |
8957 |
|
8958 |
<p> |
8959 |
If you want to allow other users to access your computer during the |
8960 |
Gentoo installation (perhaps because those users are going to help you |
8961 |
install Gentoo, or even do it for you), you need to create a user |
8962 |
account for them and perhaps even provide them with your root password |
8963 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
8964 |
</p> |
8965 |
|
8966 |
<p> |
8967 |
To fire up the SSH daemon, execute the following command: |
8968 |
</p> |
8969 |
|
8970 |
<pre caption="Starting the SSH daemon"> |
8971 |
# <i>/etc/init.d/sshd start</i> |
8972 |
</pre> |
8973 |
|
8974 |
<p> |
8975 |
To be able to use sshd, you first need to set up your networking. Continue with |
8976 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
8977 |
</p> |
8978 |
|
8979 |
</body> |
8980 |
</subsection> |
8981 |
</section> |
8982 |
</sections> |
8983 |
|
8984 |
|
8985 |
|
8986 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-network.xml |
8987 |
|
8988 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-network.xml?rev=1.1&view=markup |
8989 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-network.xml?rev=1.1&content-type=text/plain |
8990 |
|
8991 |
Index: hb-install-network.xml |
8992 |
=================================================================== |
8993 |
<?xml version='1.0' encoding='UTF-8'?> |
8994 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
8995 |
|
8996 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
8997 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
8998 |
|
8999 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-network.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
9000 |
|
9001 |
<sections> |
9002 |
|
9003 |
<version>7.1</version> |
9004 |
<date>2006-11-10</date> |
9005 |
|
9006 |
<section> |
9007 |
<title>Do you need Networking?</title> |
9008 |
<subsection> |
9009 |
<title>Who can do without?</title> |
9010 |
<body> |
9011 |
|
9012 |
<p> |
9013 |
Generally, you don't need a working network connection to install Gentoo using |
9014 |
either the Universal InstallCD or the Installer LiveCD. However, there are some |
9015 |
circumstances where you do want to have a working Internet connection: |
9016 |
</p> |
9017 |
|
9018 |
<ul> |
9019 |
<li> |
9020 |
The stage3 files that are stored in the Universal InstallCD do not |
9021 |
match your architecture and you need to download the correct stage3 file |
9022 |
</li> |
9023 |
<li> |
9024 |
The stage3 file that is generated by the Installer LiveCD does not |
9025 |
match your architecture and you need to download the correct stage3 file |
9026 |
</li> |
9027 |
<li> |
9028 |
You need to install a specific networking application that will allow you to |
9029 |
connect to the Internet which isn't available on the Universal InstallCD or |
9030 |
the Installer LiveCD, but is supported by the CD (i.e. you can connect to |
9031 |
the Internet using the CD but the necessary sources are not available on |
9032 |
the CD) |
9033 |
</li> |
9034 |
<li> |
9035 |
You want remote assistance during the installation (using SSH or through |
9036 |
direct conversations using IRC) |
9037 |
</li> |
9038 |
</ul> |
9039 |
|
9040 |
</body> |
9041 |
</subsection> |
9042 |
<subsection> |
9043 |
<title>Do I need Networking?</title> |
9044 |
<body> |
9045 |
|
9046 |
<p> |
9047 |
To find out if the stage3 file for your architecture is available and you are |
9048 |
using a Universal InstallCD, take a look inside <path>/mnt/cdrom/stages</path> |
9049 |
and check if one of the available stages matches your architecture. If not, you |
9050 |
can still opt for a stage3 file of an architecture compatible with yours. |
9051 |
</p> |
9052 |
|
9053 |
<p> |
9054 |
The stage3 file built by the x86 Installer LiveCD is optimized for i686 or |
9055 |
better and uses NPTL. The stage3 file built by the amd64 Installer LiveCD is |
9056 |
optimized for generic amd64 usage and uses NPTL. |
9057 |
</p> |
9058 |
|
9059 |
<p> |
9060 |
If you, on the other hand, want to use a stage3 file optimized for your |
9061 |
architecture and the stage3 file of your choice is not available, then you will |
9062 |
need networking to download the appropriate stage3 file. |
9063 |
</p> |
9064 |
|
9065 |
<p> |
9066 |
So, if you don't need networking, you can skip the rest of this chapter and |
9067 |
continue with <uri link="?part=1&chap=4">Preparing the Disks</uri>. |
9068 |
Otherwise, continue with the networking configuration sections below. |
9069 |
</p> |
9070 |
|
9071 |
</body> |
9072 |
</subsection> |
9073 |
</section> |
9074 |
<section> |
9075 |
<title>Automatic Network Detection</title> |
9076 |
<subsection> |
9077 |
<title>Maybe it just works?</title> |
9078 |
<body> |
9079 |
|
9080 |
<p> |
9081 |
If your system is plugged into an Ethernet network with a DHCP server, it is |
9082 |
very likely that your networking configuration has already been set up |
9083 |
automatically for you. If so, you should be able to take advantage of the many |
9084 |
included network-aware commands on the Installation CD such as <c>ssh</c>, |
9085 |
<c>scp</c>, <c>ping</c>, <c>irssi</c>, <c>wget</c> and <c>links</c>, among |
9086 |
others. |
9087 |
</p> |
9088 |
|
9089 |
<p> |
9090 |
If networking has been configured for you, the <c>/sbin/ifconfig</c> command |
9091 |
should list some network interfaces besides lo, such as eth0: |
9092 |
</p> |
9093 |
|
9094 |
<pre caption="/sbin/ifconfig for a working network configuration"> |
9095 |
# <i>/sbin/ifconfig</i> |
9096 |
<comment>(...)</comment> |
9097 |
eth0 Link encap:Ethernet HWaddr 00:50:BA:8F:61:7A |
9098 |
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 |
9099 |
inet6 addr: fe80::50:ba8f:617a/10 Scope:Link |
9100 |
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 |
9101 |
RX packets:1498792 errors:0 dropped:0 overruns:0 frame:0 |
9102 |
TX packets:1284980 errors:0 dropped:0 overruns:0 carrier:0 |
9103 |
collisions:1984 txqueuelen:100 |
9104 |
RX bytes:485691215 (463.1 Mb) TX bytes:123951388 (118.2 Mb) |
9105 |
Interrupt:11 Base address:0xe800 |
9106 |
</pre> |
9107 |
|
9108 |
</body> |
9109 |
</subsection> |
9110 |
<subsection> |
9111 |
<title>Optional: Configure any Proxies</title> |
9112 |
<body> |
9113 |
|
9114 |
<p> |
9115 |
If you access the Internet through a proxy, you might need to set up proxy |
9116 |
information during the installation. It is very easy to define a proxy: you just |
9117 |
need to define a variable which contains the proxy server information. |
9118 |
</p> |
9119 |
|
9120 |
<p> |
9121 |
In most cases, you can just define the variables using the server hostname. As |
9122 |
an example, we assume the proxy is called <c>proxy.gentoo.org</c> and the port |
9123 |
is <c>8080</c>. |
9124 |
</p> |
9125 |
|
9126 |
<pre caption="Defining proxy servers"> |
9127 |
<comment>(If the proxy filters HTTP traffic)</comment> |
9128 |
# <i>export http_proxy="http://proxy.gentoo.org:8080"</i> |
9129 |
<comment>(If the proxy filters FTP traffic)</comment> |
9130 |
# <i>export ftp_proxy="ftp://proxy.gentoo.org:8080"</i> |
9131 |
<comment>(If the proxy filters RSYNC traffic)</comment> |
9132 |
# <i>export RSYNC_PROXY="proxy.gentoo.org:8080"</i> |
9133 |
</pre> |
9134 |
|
9135 |
<p> |
9136 |
If your proxy requires a username and password, you should use the following |
9137 |
syntax for the variable: |
9138 |
</p> |
9139 |
|
9140 |
<pre caption="Adding username/password to the proxy variable"> |
9141 |
http://<i>username</i>:<i>password</i>@proxy.gentoo.org:8080 |
9142 |
</pre> |
9143 |
|
9144 |
</body> |
9145 |
</subsection> |
9146 |
<subsection> |
9147 |
<title>Testing the Network</title> |
9148 |
<body> |
9149 |
|
9150 |
<p> |
9151 |
You may want to try pinging your ISP's DNS server (found in |
9152 |
<path>/etc/resolv.conf</path>) and a Web site of your choice, just to make sure |
9153 |
that your packets are reaching the net, DNS name resolution is working |
9154 |
correctly, etc. |
9155 |
</p> |
9156 |
|
9157 |
<pre caption="Further network testing"> |
9158 |
# <i>ping -c 3 www.gentoo.org</i> |
9159 |
</pre> |
9160 |
|
9161 |
<p> |
9162 |
If you are now able to use your network, you can skip the rest of this |
9163 |
section and continue with <uri link="?part=1&chap=4">Preparing the |
9164 |
Disks</uri>. If not, read on. |
9165 |
</p> |
9166 |
|
9167 |
</body> |
9168 |
</subsection> |
9169 |
</section> |
9170 |
<section> |
9171 |
<title>Automatic Network Configuration</title> |
9172 |
<subsection> |
9173 |
<body> |
9174 |
|
9175 |
<p> |
9176 |
If the network doesn't work immediately, some installation media allow you to |
9177 |
use <c>net-setup</c> (for regular or wireless networks), <c>pppoe-setup</c> |
9178 |
(for ADSL-users) or <c>pptp</c> (for PPTP-users - only available on x86). |
9179 |
</p> |
9180 |
|
9181 |
<p> |
9182 |
If your installation medium does not contain any of these tools or your network |
9183 |
doesn't function yet, continue with <uri link="#doc_chap3">Manual Network |
9184 |
Configuration</uri>. |
9185 |
</p> |
9186 |
|
9187 |
<ul> |
9188 |
<li> |
9189 |
Regular Ethernet users should continue with <uri |
9190 |
link="#net-setup">Default: Using net-setup</uri> |
9191 |
</li> |
9192 |
<li> |
9193 |
ADSL users should continue with <uri link="#rp-pppoe">Alternative: |
9194 |
Using RP-PPPoE</uri> |
9195 |
</li> |
9196 |
<li> |
9197 |
PPTP users should continue with <uri link="#pptp">Alternative: |
9198 |
Using PPTP</uri> |
9199 |
</li> |
9200 |
</ul> |
9201 |
|
9202 |
</body> |
9203 |
</subsection> |
9204 |
<subsection id="net-setup"> |
9205 |
<title>Default: Using net-setup</title> |
9206 |
<body> |
9207 |
|
9208 |
<p> |
9209 |
The simplest way to set up networking if it didn't get configured |
9210 |
automatically is to run the <c>net-setup</c> script: |
9211 |
</p> |
9212 |
|
9213 |
<pre caption="Running the net-setup script"> |
9214 |
# <i>net-setup eth0</i> |
9215 |
</pre> |
9216 |
|
9217 |
<p> |
9218 |
<c>net-setup</c> will ask you some questions about your network |
9219 |
environment. When all is done, you should have a working network |
9220 |
connection. Test your network connection as stated before. If the tests |
9221 |
are positive, congratulations! You are now ready to install Gentoo. Skip |
9222 |
the rest of this section and continue with <uri |
9223 |
link="?part=1&chap=4">Preparing the Disks</uri>. |
9224 |
</p> |
9225 |
|
9226 |
<p> |
9227 |
If your network still doesn't work, continue with <uri link="#doc_chap3">Manual |
9228 |
Network Configuration</uri>. |
9229 |
</p> |
9230 |
|
9231 |
|
9232 |
</body> |
9233 |
</subsection> |
9234 |
<subsection id="rp-pppoe"> |
9235 |
<title>Alternative: Using RP-PPPoE</title> |
9236 |
<body> |
9237 |
|
9238 |
<p> |
9239 |
Assuming you need PPPoE to connect to the internet, the Installation CD (any |
9240 |
version) has made things easy for you by including <c>rp-pppoe</c>. Use the |
9241 |
provided <c>pppoe-setup</c> script to configure your connection. You will be |
9242 |
prompted for the ethernet device that is connected to your adsl modem, your |
9243 |
username and password, the IPs of your DNS servers and if you need a basic |
9244 |
firewall or not. |
9245 |
</p> |
9246 |
|
9247 |
<pre caption="Using rp-pppoe"> |
9248 |
# <i>pppoe-setup</i> |
9249 |
# <i>pppoe-start</i> |
9250 |
</pre> |
9251 |
|
9252 |
<p> |
9253 |
If something goes wrong, double-check that you correctly typed your username and |
9254 |
password by looking at <path>/etc/ppp/pap-secrets</path> or |
9255 |
<path>/etc/ppp/chap-secrets</path> and make sure you are using the right |
9256 |
ethernet device. If your ethernet device doesn't exist, you will have to load |
9257 |
the appropriate network modules. In that case you should continue with |
9258 |
<uri link="#doc_chap3">Manual Network Configuration</uri> as we explain how to |
9259 |
load the appropriate network modules there. |
9260 |
</p> |
9261 |
|
9262 |
<p> |
9263 |
If everything worked, continue with <uri link="?part=1&chap=4">Preparing the |
9264 |
Disks</uri>. |
9265 |
</p> |
9266 |
|
9267 |
</body> |
9268 |
</subsection> |
9269 |
<subsection id="pptp"> |
9270 |
<title>Alternative: Using PPTP</title> |
9271 |
<body> |
9272 |
|
9273 |
<note> |
9274 |
PPTP support is only available for x86 |
9275 |
</note> |
9276 |
|
9277 |
<p> |
9278 |
If you need PPTP support, you can use <c>pptpclient</c> which is provided by our |
9279 |
Installation CDs. But first you need to make sure that your configuration is |
9280 |
correct. Edit <path>/etc/ppp/pap-secrets</path> or |
9281 |
<path>/etc/ppp/chap-secrets</path> so it contains the correct username/password |
9282 |
combination: |
9283 |
</p> |
9284 |
|
9285 |
<pre caption="Editing /etc/ppp/chap-secrets"> |
9286 |
# <i>nano -w /etc/ppp/chap-secrets</i> |
9287 |
</pre> |
9288 |
|
9289 |
<p> |
9290 |
Then adjust <path>/etc/ppp/options.pptp</path> if necessary: |
9291 |
</p> |
9292 |
|
9293 |
<pre caption="Editing /etc/ppp/options.pptp"> |
9294 |
# <i>nano -w /etc/ppp/options.pptp</i> |
9295 |
</pre> |
9296 |
|
9297 |
<p> |
9298 |
When all that is done, just run <c>pptp</c> (along with the options you couldn't |
9299 |
set in <path>options.pptp</path>) to connect the server: |
9300 |
</p> |
9301 |
|
9302 |
<pre caption="Connection to a dial-in server"> |
9303 |
# <i>pptp <server ip></i> |
9304 |
</pre> |
9305 |
|
9306 |
<p> |
9307 |
Now continue with <uri link="?part=1&chap=4">Preparing the Disks</uri>. |
9308 |
</p> |
9309 |
|
9310 |
</body> |
9311 |
</subsection> |
9312 |
</section> |
9313 |
<section> |
9314 |
<title>Manual Network Configuration</title> |
9315 |
<subsection> |
9316 |
<title>Loading the Appropriate Network Modules</title> |
9317 |
<body> |
9318 |
|
9319 |
<p> |
9320 |
When the Installation CD boots, it tries to detect all your hardware devices and |
9321 |
loads the appropriate kernel modules (drivers) to support your hardware. In the |
9322 |
vast majority of cases, it does a very good job. However, in some cases, |
9323 |
it may not auto-load the kernel modules you need. |
9324 |
</p> |
9325 |
|
9326 |
<p> |
9327 |
If <c>net-setup</c> or <c>pppoe-setup</c> failed, then it is possible that |
9328 |
your network card wasn't found immediately. This means you may have to load |
9329 |
the appropriate kernel modules manually. |
9330 |
</p> |
9331 |
|
9332 |
<p> |
9333 |
To find out what kernel modules we provide for networking, use |
9334 |
<c>ls</c>: |
9335 |
</p> |
9336 |
|
9337 |
<pre caption="Searching for provided modules"> |
9338 |
# <i>ls /lib/modules/`uname -r`/kernel/drivers/net</i> |
9339 |
</pre> |
9340 |
|
9341 |
<p> |
9342 |
If you find a driver for your network card, use <c>modprobe</c> to load |
9343 |
the kernel module: |
9344 |
</p> |
9345 |
|
9346 |
<pre caption="Using modprobe to load a kernel module"> |
9347 |
<comment>(As an example, we load the pcnet32 module)</comment> |
9348 |
# <i>modprobe pcnet32</i> |
9349 |
</pre> |
9350 |
|
9351 |
<p> |
9352 |
To check if your network card is now detected, use <c>ifconfig</c>. A |
9353 |
detected network card would result in something like this: |
9354 |
</p> |
9355 |
|
9356 |
<pre caption="Testing availability of your network card, successful"> |
9357 |
# <i>ifconfig eth0</i> |
9358 |
eth0 Link encap:Ethernet HWaddr FE:FD:00:00:00:00 |
9359 |
BROADCAST NOARP MULTICAST MTU:1500 Metric:1 |
9360 |
RX packets:0 errors:0 dropped:0 overruns:0 frame:0 |
9361 |
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 |
9362 |
collisions:0 txqueuelen:0 |
9363 |
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) |
9364 |
</pre> |
9365 |
|
9366 |
<p> |
9367 |
If however you receive the following error, the network card is not |
9368 |
detected: |
9369 |
</p> |
9370 |
|
9371 |
<pre caption="Testing availability of your network card, failed"> |
9372 |
# <i>ifconfig eth0</i> |
9373 |
eth0: error fetching interface information: Device not found |
9374 |
</pre> |
9375 |
|
9376 |
<p> |
9377 |
If you have multiple network cards in your system they are named <e>eth0</e>, |
9378 |
<e>eth1</e>, etc. Make sure that the network card you want to use works well and |
9379 |
remember to use the correct naming throughout this document. We will assume that |
9380 |
the network card <e>eth0</e> is used. |
9381 |
</p> |
9382 |
|
9383 |
<p> |
9384 |
Assuming that you now have a detected network card, you can |
9385 |
retry <c>net-setup</c> or <c>pppoe-setup</c> again (which should work |
9386 |
now), but for the hardcore people amongst you we explain how to configure your |
9387 |
network manually. |
9388 |
</p> |
9389 |
|
9390 |
<p> |
9391 |
Select one of the following sections based on your network setup: |
9392 |
</p> |
9393 |
|
9394 |
<ul> |
9395 |
<li><uri link="#install-dhcp">Using DHCP</uri> for automatic IP retrieval</li> |
9396 |
<li> |
9397 |
<uri link="#wireless">Preparing for Wireless Access</uri> if you have a |
9398 |
wireless card |
9399 |
</li> |
9400 |
<li> |
9401 |
<uri link="#network_term">Understanding Network Terminology</uri> explains |
9402 |
what you need to know about networking |
9403 |
</li> |
9404 |
<li> |
9405 |
<uri link="#ifconfig_route">Using ifconfig and route</uri> explains how to |
9406 |
set up your networking manually |
9407 |
</li> |
9408 |
</ul> |
9409 |
|
9410 |
</body> |
9411 |
</subsection> |
9412 |
<subsection id="install-dhcp"> |
9413 |
<title>Using DHCP</title> |
9414 |
<body> |
9415 |
|
9416 |
<p> |
9417 |
DHCP (Dynamic Host Configuration Protocol) makes it possible to |
9418 |
automatically receive networking information (IP address, netmask, |
9419 |
broadcast address, gateway, nameservers etc.). This only works if you |
9420 |
have a DHCP server in your network (or if your provider provides a DHCP |
9421 |
service). To have a network interface receive this information automatically, |
9422 |
use <c>dhcpcd</c>: |
9423 |
</p> |
9424 |
|
9425 |
<pre caption="Using dhcpcd"> |
9426 |
# <i>dhcpcd eth0</i> |
9427 |
<comment>Some network admins require that you use the</comment> |
9428 |
<comment>hostname and domainname provided by the DHCP server.</comment> |
9429 |
<comment>In that case, use</comment> |
9430 |
# <i>dhcpcd -HD eth0</i> |
9431 |
</pre> |
9432 |
|
9433 |
<p> |
9434 |
If this works (try pinging some internet server, like <uri |
9435 |
link="http://www.google.com">Google</uri>), then you are all set and |
9436 |
ready to continue. Skip the rest of this section and continue with <uri |
9437 |
link="?part=1&chap=4">Preparing the Disks</uri>. |
9438 |
</p> |
9439 |
|
9440 |
</body> |
9441 |
</subsection> |
9442 |
<subsection id="wireless"> |
9443 |
<title>Preparing for Wireless Access</title> |
9444 |
<body> |
9445 |
|
9446 |
<note> |
9447 |
Support for the <c>iwconfig</c> command is only available on x86, amd64 and ppc |
9448 |
Installation CDs. You can still get the extensions working otherwise |
9449 |
by following the instructions of the |
9450 |
<uri link="ftp://ftp.linux-wlan.org/pub/linux-wlan-ng/README">linux-wlan-ng |
9451 |
project</uri>. |
9452 |
</note> |
9453 |
|
9454 |
<p> |
9455 |
If you are using a wireless (802.11) card, you may need to configure your |
9456 |
wireless settings before going any further. To see the current wireless settings |
9457 |
on your card, you can use <c>iwconfig</c>. Running <c>iwconfig</c> might show |
9458 |
something like: |
9459 |
</p> |
9460 |
|
9461 |
<pre caption="Showing the current wireless settings"> |
9462 |
# <i>iwconfig eth0</i> |
9463 |
eth0 IEEE 802.11-DS ESSID:"GentooNode" |
9464 |
Mode:Managed Frequency:2.442GHz Access Point: 00:09:5B:11:CC:F2 |
9465 |
Bit Rate:11Mb/s Tx-Power=20 dBm Sensitivity=0/65535 |
9466 |
Retry limit:16 RTS thr:off Fragment thr:off |
9467 |
Power Management:off |
9468 |
Link Quality:25/10 Signal level:-51 dBm Noise level:-102 dBm |
9469 |
Rx invalid nwid:5901 Rx invalid crypt:0 Rx invalid frag:0 Tx |
9470 |
excessive retries:237 Invalid misc:350282 Missed beacon:84 |
9471 |
</pre> |
9472 |
|
9473 |
<note> |
9474 |
Some wireless cards may have a device name of <c>wlan0</c> or <c>ra0</c> instead |
9475 |
of <c>eth0</c>. Run <c>iwconfig</c> without any command-line parameters to |
9476 |
determine the correct device name. |
9477 |
</note> |
9478 |
|
9479 |
<p> |
9480 |
For most users, there are only two settings that might be important to change, |
9481 |
the ESSID (aka wireless network name) or the WEP key. If the ESSID and Access |
9482 |
Point address listed are already that of your access point and you are not using |
9483 |
WEP, then your wireless is working. If you need to change your ESSID, or add a |
9484 |
WEP key, you can issue the following commands: |
9485 |
</p> |
9486 |
|
9487 |
<pre caption="Changing ESSID and/or adding WEP key"> |
9488 |
<comment>(This sets the network name to "GentooNode")</comment> |
9489 |
# <i>iwconfig eth0 essid GentooNode</i> |
9490 |
|
9491 |
<comment>(This sets a hex WEP key)</comment> |
9492 |
# <i>iwconfig eth0 key 1234123412341234abcd</i> |
9493 |
|
9494 |
<comment>(This sets an ASCII key - prefix it with "s:")</comment> |
9495 |
# <i>iwconfig eth0 key s:some-password</i> |
9496 |
</pre> |
9497 |
|
9498 |
<p> |
9499 |
You can then confirm your wireless settings again by using <c>iwconfig</c>. |
9500 |
Once you have wireless working, you can continue configuring the IP level |
9501 |
networking options as described in the next section (<uri |
9502 |
link="#network_term">Understanding Network Terminology</uri>) or use the |
9503 |
<c>net-setup</c> tool as described previously. |
9504 |
</p> |
9505 |
|
9506 |
</body> |
9507 |
</subsection> |
9508 |
<subsection id="network_term"> |
9509 |
<title>Understanding Network Terminology</title> |
9510 |
<body> |
9511 |
|
9512 |
<note> |
9513 |
If you know your IP address, broadcast address, netmask and nameservers, |
9514 |
then you can skip this subsection and continue with <uri |
9515 |
link="#ifconfig_route">Using ifconfig and route</uri>. |
9516 |
</note> |
9517 |
|
9518 |
<p> |
9519 |
If all of the above fails, you will have to configure your network manually. |
9520 |
This is not difficult at all. However, you need to be familiar with some |
9521 |
network terminology, as you will need it to be able to |
9522 |
configure your network to your satisfaction. After reading this, you |
9523 |
will know what a <e>gateway</e> is, what a <e>netmask</e> serves for, |
9524 |
how a <e>broadcast</e> address is formed and why you need |
9525 |
<e>nameservers</e>. |
9526 |
</p> |
9527 |
|
9528 |
<p> |
9529 |
In a network, hosts are identified by their <e>IP address</e> (Internet |
9530 |
Protocol address). Such an address is a combination of four numbers |
9531 |
between 0 and 255. Well, at least that is how we perceive it. In |
9532 |
reality, such an IP address consists of 32 bits (ones and zeros). Let's |
9533 |
view an example: |
9534 |
</p> |
9535 |
|
9536 |
<pre caption="Example of an IP address"> |
9537 |
IP Address (numbers): 192.168.0.2 |
9538 |
IP Address (bits): 11000000 10101000 00000000 00000010 |
9539 |
-------- -------- -------- -------- |
9540 |
192 168 0 2 |
9541 |
</pre> |
9542 |
|
9543 |
<p> |
9544 |
Such an IP address is unique to a host as far as all accessible networks are |
9545 |
concerned (i.e. every host that you are able to reach must have a unique IP |
9546 |
address). In order to distinguish between hosts inside and outside a |
9547 |
network, the IP address is divided in two parts: the |
9548 |
<e>network</e> part and the <e>host</e> part. |
9549 |
</p> |
9550 |
|
9551 |
<p> |
9552 |
The separation is written down with the <e>netmask</e>, a collection of |
9553 |
ones followed by a collection of zeros. The part of the IP that can be |
9554 |
mapped on the ones is the network-part, the other one is the host-part. |
9555 |
As usual, the netmask can be written down as an IP-address. |
9556 |
</p> |
9557 |
|
9558 |
<pre caption="Example of network/host separation"> |
9559 |
IP-address: 192 168 0 2 |
9560 |
11000000 10101000 00000000 00000010 |
9561 |
Netmask: 11111111 11111111 11111111 00000000 |
9562 |
255 255 255 0 |
9563 |
+--------------------------+--------+ |
9564 |
Network Host |
9565 |
</pre> |
9566 |
|
9567 |
<p> |
9568 |
In other words, 192.168.0.14 is still part of our example network, but |
9569 |
192.168.1.2 is not. |
9570 |
</p> |
9571 |
|
9572 |
<p> |
9573 |
The <e>broadcast</e> address is an IP-address with the same network-part |
9574 |
as your network, but with only ones as host-part. Every host on your |
9575 |
network listens to this IP address. It is truly meant for broadcasting |
9576 |
packets. |
9577 |
</p> |
9578 |
|
9579 |
<pre caption="Broadcast address"> |
9580 |
IP-address: 192 168 0 2 |
9581 |
11000000 10101000 00000000 00000010 |
9582 |
Broadcast: 11000000 10101000 00000000 11111111 |
9583 |
192 168 0 255 |
9584 |
+--------------------------+--------+ |
9585 |
Network Host |
9586 |
</pre> |
9587 |
|
9588 |
<p> |
9589 |
To be able to surf on the internet, you must know which host shares the |
9590 |
Internet connection. This host is called the <e>gateway</e>. Since it is |
9591 |
a regular host, it has a regular IP address (for instance 192.168.0.1). |
9592 |
</p> |
9593 |
|
9594 |
<p> |
9595 |
We previously stated that every host has its own IP address. To be able |
9596 |
to reach this host by a name (instead of an IP address) you need a |
9597 |
service that translates a name (such as <e>dev.gentoo.org</e>) to an IP |
9598 |
address (such as <e>64.5.62.82</e>). Such a service is called a name |
9599 |
service. To use such a service, you must define the necessary <e>name |
9600 |
servers</e> in <path>/etc/resolv.conf</path>. |
9601 |
</p> |
9602 |
|
9603 |
<p> |
9604 |
In some cases, your gateway also serves as nameserver. Otherwise you |
9605 |
will have to enter the nameservers provided by your ISP. |
9606 |
</p> |
9607 |
|
9608 |
<p> |
9609 |
To summarise, you will need the following information before continuing: |
9610 |
</p> |
9611 |
|
9612 |
<table> |
9613 |
<tr> |
9614 |
<th>Network Item</th> |
9615 |
<th>Example</th> |
9616 |
</tr> |
9617 |
<tr> |
9618 |
<ti>Your IP address</ti> |
9619 |
<ti>192.168.0.2</ti> |
9620 |
</tr> |
9621 |
<tr> |
9622 |
<ti>Netmask</ti> |
9623 |
<ti>255.255.255.0</ti> |
9624 |
</tr> |
9625 |
<tr> |
9626 |
<ti>Broadcast</ti> |
9627 |
<ti>192.168.0.255</ti> |
9628 |
</tr> |
9629 |
<tr> |
9630 |
<ti>Gateway</ti> |
9631 |
<ti>192.168.0.1</ti> |
9632 |
</tr> |
9633 |
<tr> |
9634 |
<ti>Nameserver(s)</ti> |
9635 |
<ti>195.130.130.5, 195.130.130.133</ti> |
9636 |
</tr> |
9637 |
</table> |
9638 |
|
9639 |
</body> |
9640 |
</subsection> |
9641 |
<subsection id="ifconfig_route"> |
9642 |
<title>Using ifconfig and route</title> |
9643 |
<body> |
9644 |
|
9645 |
<p> |
9646 |
Setting up your network consists of three steps. First we assign |
9647 |
ourselves an IP address using <c>ifconfig</c>. Then we set up routing to |
9648 |
the gateway using <c>route</c>. Then we finish up by placing the |
9649 |
nameserver IPs in <path>/etc/resolv.conf</path>. |
9650 |
</p> |
9651 |
|
9652 |
<p> |
9653 |
To assign an IP address, you will need your IP address, broadcast |
9654 |
address and netmask. Then execute the following command, substituting |
9655 |
<c>${IP_ADDR}</c> with your IP address, <c>${BROADCAST}</c> with your |
9656 |
broadcast address and <c>${NETMASK}</c> with your netmask: |
9657 |
</p> |
9658 |
|
9659 |
<pre caption="Using ifconfig"> |
9660 |
# <i>ifconfig eth0 ${IP_ADDR} broadcast ${BROADCAST} netmask ${NETMASK} up</i> |
9661 |
</pre> |
9662 |
|
9663 |
<p> |
9664 |
Now set up routing using <c>route</c>. Substitute <c>${GATEWAY}</c> with |
9665 |
your gateway IP address: |
9666 |
</p> |
9667 |
|
9668 |
<pre caption="Using route"> |
9669 |
# <i>route add default gw ${GATEWAY}</i> |
9670 |
</pre> |
9671 |
|
9672 |
<p> |
9673 |
Now open <path>/etc/resolv.conf</path> with your favorite editor (in our |
9674 |
example, we use <c>nano</c>): |
9675 |
</p> |
9676 |
|
9677 |
<pre caption="Creating /etc/resolv.conf"> |
9678 |
# <i>nano -w /etc/resolv.conf</i> |
9679 |
</pre> |
9680 |
|
9681 |
<p> |
9682 |
Now fill in your nameserver(s) using the following as a template. Make |
9683 |
sure you substitute <c>${NAMESERVER1}</c> and <c>${NAMESERVER2}</c> with |
9684 |
the appropriate nameserver addresses: |
9685 |
</p> |
9686 |
|
9687 |
<pre caption="/etc/resolv.conf template"> |
9688 |
nameserver ${NAMESERVER1} |
9689 |
nameserver ${NAMESERVER2} |
9690 |
</pre> |
9691 |
|
9692 |
<p> |
9693 |
That's it. Now test your network by pinging some Internet server (like |
9694 |
<uri link="http://www.google.com">Google</uri>). If this works, |
9695 |
congratulations then. You are now ready to install Gentoo. Continue with <uri |
9696 |
link="?part=1&chap=4">Preparing the Disks</uri>. |
9697 |
</p> |
9698 |
|
9699 |
</body> |
9700 |
</subsection> |
9701 |
</section> |
9702 |
</sections> |
9703 |
|
9704 |
|
9705 |
|
9706 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-next.xml |
9707 |
|
9708 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-next.xml?rev=1.1&view=markup |
9709 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-next.xml?rev=1.1&content-type=text/plain |
9710 |
|
9711 |
Index: hb-install-next.xml |
9712 |
=================================================================== |
9713 |
<?xml version='1.0' encoding='UTF-8'?> |
9714 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
9715 |
|
9716 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
9717 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
9718 |
|
9719 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-next.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
9720 |
|
9721 |
<sections> |
9722 |
|
9723 |
<version>7.0</version> |
9724 |
<date>2006-08-30</date> |
9725 |
|
9726 |
<section> |
9727 |
<title>Documentation</title> |
9728 |
<subsection> |
9729 |
<body> |
9730 |
|
9731 |
<p> |
9732 |
Congratulations! You now have a working Gentoo system. But where to go from |
9733 |
here? What are your options now? What to explore first? Gentoo provides its |
9734 |
users with lots of possibilities, and therefore lots of documented (and less |
9735 |
documented) features. |
9736 |
</p> |
9737 |
|
9738 |
<p> |
9739 |
You should definitely take a look at the next part of the Gentoo Handbook |
9740 |
entitled <uri link="?part=2">Working with Gentoo</uri> which explains |
9741 |
how to keep your software up to date, how to install more software, what USE |
9742 |
flags are, how the Gentoo Init system works, etc. |
9743 |
</p> |
9744 |
|
9745 |
<p> |
9746 |
If you are interested in optimizing your system for desktop use, or you want to |
9747 |
learn how to configure your system to be a full working desktop system, consult |
9748 |
our extensive <uri link="/doc/en/index.xml?catid=desktop">Gentoo Desktop |
9749 |
Documentation Resources</uri>. Besides, you might want to use our <uri |
9750 |
link="/doc/en/guide-localization.xml">localization guide</uri> to make your |
9751 |
system feel more at home. |
9752 |
</p> |
9753 |
|
9754 |
<p> |
9755 |
We also have a <uri link="/doc/en/security/">Gentoo Security Handbook</uri> |
9756 |
which is worth reading. |
9757 |
</p> |
9758 |
|
9759 |
<p> |
9760 |
For a full listing of all our available documentation check out our <uri |
9761 |
link="/doc/en/index.xml">Documentation Resources</uri> page. |
9762 |
</p> |
9763 |
|
9764 |
</body> |
9765 |
</subsection> |
9766 |
</section> |
9767 |
<section> |
9768 |
<title>Gentoo Online</title> |
9769 |
<body> |
9770 |
|
9771 |
<p> |
9772 |
You are of course always welcome on our <uri |
9773 |
link="http://forums.gentoo.org">Gentoo Forums</uri> or on one of our many |
9774 |
<uri link="/main/en/irc.xml">Gentoo IRC channels</uri>. |
9775 |
</p> |
9776 |
|
9777 |
<p> |
9778 |
We also have several <uri |
9779 |
link="/main/en/lists.xml">mailinglists</uri> open to all |
9780 |
our users. Information on how to join is contained in that page. |
9781 |
</p> |
9782 |
|
9783 |
<p> |
9784 |
We'll shut up now and let you enjoy your installation :) |
9785 |
</p> |
9786 |
|
9787 |
</body> |
9788 |
</section> |
9789 |
<section> |
9790 |
<title>Gentoo Changes since 2006.1</title> |
9791 |
<subsection> |
9792 |
<title>Changes?</title> |
9793 |
<body> |
9794 |
|
9795 |
<p> |
9796 |
Gentoo is a fast-moving target. The following sections describe important |
9797 |
changes that affect a Gentoo installation. We only list those that have anything |
9798 |
in common with the installation, not with package changes that did not occur |
9799 |
during the installation. |
9800 |
</p> |
9801 |
|
9802 |
<p> |
9803 |
There have been no significant changes since. |
9804 |
</p> |
9805 |
|
9806 |
</body> |
9807 |
</subsection> |
9808 |
</section> |
9809 |
</sections> |
9810 |
|
9811 |
|
9812 |
|
9813 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-bootloader.xml |
9814 |
|
9815 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-bootloader.xml?rev=1.1&view=markup |
9816 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-bootloader.xml?rev=1.1&content-type=text/plain |
9817 |
|
9818 |
Index: hb-install-ppc64-bootloader.xml |
9819 |
=================================================================== |
9820 |
<?xml version='1.0' encoding='UTF-8'?> |
9821 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
9822 |
|
9823 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
9824 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
9825 |
|
9826 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-bootloader.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
9827 |
|
9828 |
<sections> |
9829 |
|
9830 |
<version>7.0</version> |
9831 |
<date>2006-08-30</date> |
9832 |
|
9833 |
<section> |
9834 |
<title>Making your Choice</title> |
9835 |
<subsection> |
9836 |
<title>Introduction</title> |
9837 |
<body> |
9838 |
|
9839 |
<p> |
9840 |
Now that your kernel is configured and compiled and the necessary system |
9841 |
configuration files are filled in correctly, it is time to install a |
9842 |
program that will fire up your kernel when you start the system. Such a |
9843 |
program is called a <e>bootloader</e>. |
9844 |
</p> |
9845 |
|
9846 |
<p> |
9847 |
On Linux/PPC64 we have only yaBoot as a bootloader until grub2 is |
9848 |
finished. |
9849 |
</p> |
9850 |
|
9851 |
</body> |
9852 |
</subsection> |
9853 |
</section> |
9854 |
<section id="yaboot"> |
9855 |
<title>Using yaBoot</title> |
9856 |
<subsection> |
9857 |
<title>Introduction</title> |
9858 |
<body> |
9859 |
|
9860 |
<impo> |
9861 |
For a 64bit userland use yaboot-static instead of yaboot, because yaboot won't |
9862 |
compile on 64bit userland systems. For a 32bit userland use yaboot as you |
9863 |
normally would. |
9864 |
</impo> |
9865 |
|
9866 |
<p> |
9867 |
There are two ways to configure yaBoot for your system. You can use the |
9868 |
new and improved <c>yabootconfig</c> included with |
9869 |
<path>yaboot-1.3.8-r1</path> and later to automatically set up yaboot. If |
9870 |
for some reason you do not want to run <c>yabootconfig</c> to |
9871 |
automatically set up <path>/etc/yaboot.conf</path> or you are installing Gentoo |
9872 |
on a G5 (on which <c>yabootconfig</c> does not always work), you can just edit |
9873 |
the sample file already installed on your system. |
9874 |
</p> |
9875 |
|
9876 |
<impo> |
9877 |
If you are installing on a G5 using an online install and have not used the |
9878 |
G5 optimized stages you must change what profile you are linked to now. If you |
9879 |
do not you will not get dependencies necessary for yaboot to run on Apple |
9880 |
equipment. In the command below replace <c>(userland)</c> with your chosen |
9881 |
userland bit level. If you are installing on a G5 using an offline install |
9882 |
you have to install these packages by hand. |
9883 |
</impo> |
9884 |
|
9885 |
<pre caption = "(ONLINE INSTALL FOR G5 USERS ONLY) Changing your profile"> |
9886 |
# <i>rm /etc/make.profile</i> |
9887 |
# <i>ln -sf /usr/portage/profiles/default-linux/ppc/2006.1/ppc64/(userland)/970/pmac /etc/make.profile</i> |
9888 |
</pre> |
9889 |
|
9890 |
<pre caption = "(OFFLINE INSTALL FOR G5 USERS ONLY) Installing Necessary File System Tools"> |
9891 |
# <i>emerge hfsutils hfsplusutils</i> |
9892 |
</pre> |
9893 |
|
9894 |
<pre caption = "Installing the bootloader"> |
9895 |
<comment>(64bit userland)</comment> |
9896 |
# <i>emerge --update yaboot-static</i> |
9897 |
<comment>(32bit userland)</comment> |
9898 |
# <i>emerge --update yaboot</i> |
9899 |
</pre> |
9900 |
|
9901 |
<impo> |
9902 |
yabootconfig/ybin won't work on IBM. You have to install yaboot another way: |
9903 |
<uri link="#yaboot-ibm">Using yaboot on IBM hardware</uri> |
9904 |
</impo> |
9905 |
|
9906 |
<note> |
9907 |
If your root filesystem uses the JFS filesystem, be sure to add <c>ro</c> as a |
9908 |
kernel parameter. JFS must be able to replay its log in read-only mode before it |
9909 |
gets mounted read-write. |
9910 |
</note> |
9911 |
|
9912 |
<ul> |
9913 |
<li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li> |
9914 |
<li> |
9915 |
<uri link="#manual_yaboot">Alternative: Manual yaBoot Configuration</uri> |
9916 |
</li> |
9917 |
</ul> |
9918 |
|
9919 |
</body> |
9920 |
</subsection> |
9921 |
<subsection id="yabootconfig"> |
9922 |
<title>Default: Using yabootconfig</title> |
9923 |
<body> |
9924 |
|
9925 |
<p> |
9926 |
<c>yabootconfig</c> will auto-detect the partitions on your machine and will |
9927 |
set up dual and triple boot combinations with Linux, Mac OS, and Mac OS |
9928 |
X. |
9929 |
</p> |
9930 |
|
9931 |
<p> |
9932 |
To use <c>yabootconfig</c>, your drive must have a bootstrap partition, and |
9933 |
<path>/etc/fstab</path> must be configured with your Linux partitions. Both of |
9934 |
these should have been done already in the steps above. To start, ensure that |
9935 |
you have the latest version of yaboot installed by running <c>emerge --update |
9936 |
yaboot-static</c>. This is necessary as the latest version will be available via |
9937 |
Portage, but it may not have made it into the stage files. |
9938 |
</p> |
9939 |
|
9940 |
<p> |
9941 |
Now run <c>yabootconfig</c>. The program will run and it will confirm |
9942 |
the location of the bootstrap partition. Type <c>Y</c> if it is correct. If |
9943 |
not, double check <path>/etc/fstab</path>. yabootconfig will then scan your |
9944 |
system setup, create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for |
9945 |
you. <c>mkofboot</c> is used to format the bootstrap partition, and install |
9946 |
the yaboot configuration file into it. |
9947 |
</p> |
9948 |
|
9949 |
<p> |
9950 |
You might want to verify the contents of <path>/etc/yaboot.conf</path>. If |
9951 |
you make changes to <path>/etc/yaboot.conf</path> (like setting the |
9952 |
default/boot OS), make sure to rerun <c>ybin -v</c> to apply changes to the |
9953 |
bootstrap partition. |
9954 |
</p> |
9955 |
|
9956 |
<p> |
9957 |
Now continue with <uri link="#reboot">Rebooting your System</uri>. |
9958 |
</p> |
9959 |
|
9960 |
</body> |
9961 |
</subsection> |
9962 |
<subsection id="manual_yaboot"> |
9963 |
<title>Alternative: Manual yaBoot Configuration</title> |
9964 |
<body> |
9965 |
|
9966 |
<p> |
9967 |
Below you find a completed <path>yaboot.conf</path> file. Alter it at |
9968 |
will. |
9969 |
</p> |
9970 |
|
9971 |
<pre caption = "/etc/yaboot.conf"> |
9972 |
<comment>## /etc/yaboot.conf |
9973 |
## |
9974 |
## run: "man yaboot.conf" for details. Do not make changes until you have!! |
9975 |
## see also: /usr/share/doc/yaboot/examples for example configurations. |
9976 |
## |
9977 |
## For a dual-boot menu, add one or more of: |
9978 |
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ |
9979 |
|
9980 |
## our bootstrap partition:</comment> |
9981 |
|
9982 |
boot=/dev/hda2 |
9983 |
|
9984 |
<comment>## ofboot is the openfirmware way to specify the bootstrap partition. |
9985 |
## If this isn't defined, yaboot fails on the G5 and some G4s (unless |
9986 |
## you pass the necessary arguments to the mkofboot/ybin program). |
9987 |
## hd:X means /dev/sdaX (or /dev/hdaX).</comment> |
9988 |
|
9989 |
ofboot=hd:2 |
9990 |
|
9991 |
<comment>## hd: is open firmware speak for hda</comment> |
9992 |
device=hd: |
9993 |
|
9994 |
delay=5 |
9995 |
defaultos=macosx |
9996 |
timeout=30 |
9997 |
install=/usr/lib/yaboot/yaboot |
9998 |
magicboot=/usr/lib/yaboot/ofboot |
9999 |
|
10000 |
<comment>################# |
10001 |
## This section can be duplicated if you have more than one kernel or set of |
10002 |
## boot options - replace 2.6.17-gentoo-r5 with your kernel-version |
10003 |
#################</comment> |
10004 |
image=/boot/kernel-2.6.17-gentoo-r5 |
10005 |
label=Linux |
10006 |
root=/dev/hda3 |
10007 |
partition=3 |
10008 |
read-only |
10009 |
|
10010 |
macos=hd:13 |
10011 |
macosx=hd:12 |
10012 |
enablecdboot |
10013 |
enableofboot |
10014 |
</pre> |
10015 |
|
10016 |
<p> |
10017 |
Once <path>yaboot.conf</path> is set up the way you want it, you run |
10018 |
<c>mkofboot -v</c> to install the settings in the bootstrap partition. |
10019 |
<e>Don't forget this!</e> Confirm when <c>mkofboot</c> asks you to create a new |
10020 |
filesystem. |
10021 |
</p> |
10022 |
|
10023 |
<p> |
10024 |
If all goes well, and you have the same |
10025 |
options as the sample above, your next reboot will give you a simple, |
10026 |
five-entry boot menu. If you update your yaboot config later on, you'll |
10027 |
just need to run <c>ybin -v</c> to update the bootstrap partition - |
10028 |
<c>mkofboot</c> is for initial setup only. |
10029 |
</p> |
10030 |
|
10031 |
<p> |
10032 |
For more information on yaboot, take a look at the <uri |
10033 |
link="http://penguinppc.org/projects/yaboot">yaboot project</uri>. For |
10034 |
now, continue the installation with <uri link="#reboot">Rebooting your |
10035 |
System</uri>. |
10036 |
</p> |
10037 |
|
10038 |
</body> |
10039 |
</subsection> |
10040 |
</section> |
10041 |
<section id="yaboot-ibm"> |
10042 |
<title>Using yaboot on IBM hardware</title> |
10043 |
<body> |
10044 |
|
10045 |
<p> |
10046 |
On IBM hardware you cannot run yabootconfig or ybin. You must proceed with the |
10047 |
following steps: |
10048 |
</p> |
10049 |
|
10050 |
<ul> |
10051 |
<li>Install yaboot-static</li> |
10052 |
<li>Run 'dd if=/usr/lib/yaboot/yaboot.chrp of=/dev/sdXX' (fill in XX |
10053 |
with your disk and partition for the PReP partition; this was in our |
10054 |
example /dev/sda1)</li> |
10055 |
<li>Next construct your own yaboot.conf file and place into /etc. |
10056 |
(Take a look at the config above, look into the man page of |
10057 |
yaboot.conf or look at the below yaboot.conf example)</li> |
10058 |
<li>Assuming your boot device in OF is pointing to the harddrive you |
10059 |
prep boot partition is on then it'll just work, otherwise at IPL time, |
10060 |
go into the multiboot menu and set the boot device to the one with |
10061 |
your prep boot partition.</li> |
10062 |
<li>That's it!</li> |
10063 |
</ul> |
10064 |
|
10065 |
<pre caption = "yaboot.conf for IBM hardware"> |
10066 |
device=disk: |
10067 |
partition=2 |
10068 |
root=/dev/sda2 |
10069 |
default=2.6.17-gentoo-r5 |
10070 |
timeout=50 |
10071 |
|
10072 |
image=/boot/kernel-2.6.17-gentoo-r5 |
10073 |
label=Linux |
10074 |
append="console=ttyS0,9600" |
10075 |
read-only |
10076 |
</pre> |
10077 |
|
10078 |
<p> |
10079 |
For POWER4, POWER5, and blade-based hardware where the PReP disk partition |
10080 |
and the disk partition that contains your kernel are on the same physical disk, |
10081 |
you can use a simplified yaboot.conf. The following should be sufficient: |
10082 |
</p> |
10083 |
|
10084 |
<pre caption="yaboot.conf for PReP hardware"> |
10085 |
default = linux |
10086 |
timeout = 100 |
10087 |
image=/boot/kernel-2.6.17-gentoo-r5 |
10088 |
label=linux |
10089 |
read-only |
10090 |
root = /dev/sda2 |
10091 |
append="root=/dev/sda2" |
10092 |
</pre> |
10093 |
|
10094 |
<p> |
10095 |
To verify that yaboot has been copied to the PReP partition: |
10096 |
</p> |
10097 |
|
10098 |
<pre caption="Verifying the yaboot install on PReP"> |
10099 |
# <i>dd if=/dev/sda1 count=10 | grep ELF</i> |
10100 |
Binary file (standard input) matches |
10101 |
10+0 records in |
10102 |
10+0 records out |
10103 |
</pre> |
10104 |
|
10105 |
<p> |
10106 |
A match signifies that yaboot was installed correctly. |
10107 |
</p> |
10108 |
|
10109 |
</body> |
10110 |
</section> |
10111 |
<section id="reboot"> |
10112 |
<title>Rebooting the System</title> |
10113 |
<subsection> |
10114 |
<body> |
10115 |
|
10116 |
<p> |
10117 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
10118 |
that one magical command you have been waiting for: <c>reboot</c>. |
10119 |
</p> |
10120 |
|
10121 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
10122 |
# <i>exit</i> |
10123 |
~# <i>cd</i> |
10124 |
~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
10125 |
~# <i>reboot</i> |
10126 |
</pre> |
10127 |
|
10128 |
<p> |
10129 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
10130 |
booted again instead of your new Gentoo system. |
10131 |
</p> |
10132 |
|
10133 |
<p> |
10134 |
Once rebooted in your Gentoo installation, finish up with <uri |
10135 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
10136 |
</p> |
10137 |
|
10138 |
</body> |
10139 |
</subsection> |
10140 |
</section> |
10141 |
|
10142 |
</sections> |
10143 |
|
10144 |
|
10145 |
|
10146 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-disk.xml |
10147 |
|
10148 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-disk.xml?rev=1.1&view=markup |
10149 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-disk.xml?rev=1.1&content-type=text/plain |
10150 |
|
10151 |
Index: hb-install-ppc64-disk.xml |
10152 |
=================================================================== |
10153 |
<?xml version='1.0' encoding='UTF-8'?> |
10154 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
10155 |
|
10156 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
10157 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
10158 |
|
10159 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-disk.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
10160 |
|
10161 |
<sections> |
10162 |
|
10163 |
<version>7.1</version> |
10164 |
<date>2006-11-02</date> |
10165 |
|
10166 |
<section> |
10167 |
<title>Introduction to Block Devices</title> |
10168 |
<subsection> |
10169 |
<title>Block Devices</title> |
10170 |
<body> |
10171 |
|
10172 |
<p> |
10173 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
10174 |
and Linux in general, including Linux filesystems, partitions and block devices. |
10175 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
10176 |
you'll be guided through the process of setting up partitions and filesystems |
10177 |
for your Gentoo Linux installation. |
10178 |
</p> |
10179 |
|
10180 |
<p> |
10181 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
10182 |
probably the one that represents the first IDE drive in a Linux system, namely |
10183 |
<path>/dev/hda</path>. If your system uses SCSI drives, then your first hard |
10184 |
drive would be <path>/dev/sda</path>. Serial ATA drives are also |
10185 |
<path>/dev/sda</path> even if they are IDE drives. |
10186 |
</p> |
10187 |
|
10188 |
<p> |
10189 |
The block devices above represent an abstract interface to the disk. User |
10190 |
programs can use these block devices to interact with your disk without worrying |
10191 |
about whether your drives are IDE, SCSI or something else. The program can |
10192 |
simply address the storage on the disk as a bunch of contiguous, |
10193 |
randomly-accessible 512-byte blocks. |
10194 |
</p> |
10195 |
|
10196 |
</body> |
10197 |
</subsection> |
10198 |
<subsection> |
10199 |
<title>Partitions and Slices</title> |
10200 |
<body> |
10201 |
|
10202 |
<p> |
10203 |
Although it is theoretically possible to use a full disk to house your Linux |
10204 |
system, this is almost never done in practice. Instead, full disk block devices |
10205 |
are split up in smaller, more manageable block devices. On most systems, |
10206 |
these are called <e>partitions</e>. Other architectures use a similar technique, |
10207 |
called <e>slices</e>. |
10208 |
</p> |
10209 |
|
10210 |
</body> |
10211 |
</subsection> |
10212 |
</section> |
10213 |
<section> |
10214 |
<title>Designing a Partitioning Scheme</title> |
10215 |
<subsection> |
10216 |
<title>Default Partitioning Scheme</title> |
10217 |
<body> |
10218 |
|
10219 |
<p> |
10220 |
If you are not interested in drawing up a partitioning scheme for your system, |
10221 |
you can use the partitioning scheme we use throughout this book: |
10222 |
</p> |
10223 |
|
10224 |
<table> |
10225 |
<tr> |
10226 |
<th>Partition</th> |
10227 |
<th>Filesystem</th> |
10228 |
<th>Size</th> |
10229 |
<th>Description</th> |
10230 |
</tr> |
10231 |
<tr> |
10232 |
<ti><path>/dev/sda1</path></ti> |
10233 |
<ti>Partition map</ti> |
10234 |
<ti>31.5k</ti> |
10235 |
<ti>Partition map</ti> |
10236 |
</tr> |
10237 |
<tr> |
10238 |
<ti><path>/dev/sda2</path></ti> |
10239 |
<ti>(bootstrap)</ti> |
10240 |
<ti>800k</ti> |
10241 |
<ti>Apple_Bootstrap</ti> |
10242 |
</tr> |
10243 |
<tr> |
10244 |
<ti><path>/dev/sda3</path></ti> |
10245 |
<ti>(swap)</ti> |
10246 |
<ti>512M</ti> |
10247 |
<ti>Swap partition</ti> |
10248 |
</tr> |
10249 |
<tr> |
10250 |
<ti><path>/dev/sda4</path></ti> |
10251 |
<ti>ext3</ti> |
10252 |
<ti>Rest of the disk</ti> |
10253 |
<ti>Root partition</ti> |
10254 |
</tr> |
10255 |
</table> |
10256 |
|
10257 |
<note> |
10258 |
There are some partitions named like this: <path>Apple_Driver43, |
10259 |
Apple_Driver_ATA, Apple_FWDriver, Apple_Driver_IOKit, |
10260 |
Apple_Patches</path>. If you are not planning to use MacOS 9 you can |
10261 |
delete them, because MacOS X and Linux don't need them. |
10262 |
You might have to use parted in order to delete them, as mac-fdisk can't delete them yet. |
10263 |
</note> |
10264 |
|
10265 |
<p> |
10266 |
If you are interested in knowing how big a partition should be, or even how |
10267 |
many partitions you need, read on. Otherwise continue now with |
10268 |
<uri link="#mac-fdisk">Apple G5: Using mac-fdisk to Partition your |
10269 |
Disk</uri> or <uri link="#fdisk">IBM pSeries: using fdisk to Partition |
10270 |
your Disk</uri> |
10271 |
</p> |
10272 |
|
10273 |
</body> |
10274 |
</subsection> |
10275 |
<subsection> |
10276 |
<title>How Many and How Big?</title> |
10277 |
<body> |
10278 |
|
10279 |
<p> |
10280 |
The number of partitions is highly dependent on your environment. For instance, |
10281 |
if you have lots of users, you will most likely want to have your |
10282 |
<path>/home</path> separate as it increases security and makes backups easier. |
10283 |
If you are installing Gentoo to perform as a mailserver, your |
10284 |
<path>/var</path> should be separate as all mails are stored inside |
10285 |
<path>/var</path>. A good choice of filesystem will then maximise your |
10286 |
performance. Gameservers will have a separate <path>/opt</path> as most gaming |
10287 |
servers are installed there. The reason is similar for <path>/home</path>: |
10288 |
security and backups. You will definitely want to keep <path>/usr</path> big: |
10289 |
not only will it contain the majority of applications, the Portage tree alone |
10290 |
takes around 500 Mbyte excluding the various sources that are stored in it. |
10291 |
</p> |
10292 |
|
10293 |
<p> |
10294 |
As you can see, it very much depends on what you want to achieve. Separate |
10295 |
partitions or volumes have the following advantages: |
10296 |
</p> |
10297 |
|
10298 |
<ul> |
10299 |
<li> |
10300 |
You can choose the best performing filesystem for each partition or volume |
10301 |
</li> |
10302 |
<li> |
10303 |
Your entire system cannot run out of free space if one defunct tool is |
10304 |
continuously writing files to a partition or volume |
10305 |
</li> |
10306 |
<li> |
10307 |
If necessary, file system checks are reduced in time, as multiple checks can |
10308 |
be done in parallel (although this advantage is more with multiple disks than |
10309 |
it is with multiple partitions) |
10310 |
</li> |
10311 |
<li> |
10312 |
Security can be enhanced by mounting some partitions or volumes read-only, |
10313 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
10314 |
</li> |
10315 |
</ul> |
10316 |
|
10317 |
<p> |
10318 |
However, multiple partitions have one big disadvantage: if not configured |
10319 |
properly, you might result in having a system with lots |
10320 |
of free space on one partition and none on another. There is also a 15-partition |
10321 |
limit for SCSI and SATA. |
10322 |
</p> |
10323 |
|
10324 |
</body> |
10325 |
</subsection> |
10326 |
</section> |
10327 |
<section id="mac-fdisk"> |
10328 |
<title>Default: Using mac-fdisk (Apple G5) Partition your Disk</title> |
10329 |
<body> |
10330 |
|
10331 |
<p> |
10332 |
At this point, create your partitions using <c>mac-fdisk</c>: |
10333 |
</p> |
10334 |
|
10335 |
<pre caption="Starting mac-fdisk"> |
10336 |
# <i>mac-fdisk /dev/sda</i> |
10337 |
</pre> |
10338 |
|
10339 |
<p> |
10340 |
First delete the partitions you have cleared previously to make room for your |
10341 |
Linux partitions. Use <c>d</c> in <c>mac-fdisk</c> to delete those partition(s). |
10342 |
It will ask for the partition number to delete. |
10343 |
</p> |
10344 |
|
10345 |
<p> |
10346 |
Second, create an <e>Apple_Bootstrap</e> partition by using <c>b</c>. It will |
10347 |
ask for what block you want to start. Enter the number of your first free |
10348 |
partition, followed by a <c>p</c>. For instance this is <c>2p</c>. |
10349 |
</p> |
10350 |
|
10351 |
<note> |
10352 |
This partition is <e>not</e> a "boot" partition. It is not used by Linux at all; |
10353 |
you don't have to place any filesystem on it and you should never mount it. PPC |
10354 |
users don't need an extra partition for <path>/boot</path>. |
10355 |
</note> |
10356 |
|
10357 |
<p> |
10358 |
Now create a swap partition by pressing <c>c</c>. Again <c>mac-fdisk</c> will |
10359 |
ask for what block you want to start this partition from. As we used <c>2</c> |
10360 |
before to create the Apple_Bootstrap partition, you now have to enter |
10361 |
<c>3p</c>. When you're asked for the size, enter <c>512M</c> (or whatever size |
10362 |
you want). When asked for a name, enter <c>swap</c> (mandatory). |
10363 |
</p> |
10364 |
|
10365 |
<p> |
10366 |
To create the root partition, enter <c>c</c>, followed by <c>4p</c> to select |
10367 |
from what block the root partition should start. When asked for the size, enter |
10368 |
<c>4p</c> again. <c>mac-fdisk</c> will interpret this as "Use all available |
10369 |
space". When asked for the name, enter <c>root</c> (mandatory). |
10370 |
</p> |
10371 |
|
10372 |
<p> |
10373 |
To finish up, write the partition to the disk using <c>w</c> and <c>q</c> to |
10374 |
quit <c>mac-fdisk</c>. |
10375 |
</p> |
10376 |
|
10377 |
<note> |
10378 |
To make sure everything is ok, you should run mac-fdisk once more and check whether all the partitions are there. |
10379 |
If you don't see any of the partitions you created, or the changes you made, you should reinitialize your partitions by pressing "i" in mac-fdisk. |
10380 |
Note that this will recreate the partition map and thus remove all your partitions. |
10381 |
</note> |
10382 |
|
10383 |
<p> |
10384 |
Now that your partitions are created, you can now continue with <uri |
10385 |
link="#filesystems">Creating Filesystems</uri>. |
10386 |
</p> |
10387 |
|
10388 |
</body> |
10389 |
</section> |
10390 |
<section id="fdisk"> |
10391 |
<title>IBM pSeries, iSeries and OpenPower: using fdisk to Partition your Disk</title> |
10392 |
<subsection> |
10393 |
<body> |
10394 |
|
10395 |
<note> |
10396 |
If you are planning to use a RAID disk array for your gentoo installation and |
10397 |
you are using POWER5-based hardware, you should now run <c>iprconfig</c> to |
10398 |
format the disks to Advanced Function format and create the disk array. You |
10399 |
should emerge <c>iprutils</c> after your install is complete. |
10400 |
</note> |
10401 |
|
10402 |
<p> |
10403 |
If you have an ipr based SCSI adapter, you should start the ipr utilities now. |
10404 |
</p> |
10405 |
|
10406 |
<pre caption="Starting ipr utilities"> |
10407 |
# <i>/etc/init.d/iprinit start</i> |
10408 |
</pre> |
10409 |
|
10410 |
<p> |
10411 |
The following parts explain how to create the example partition layout |
10412 |
described previously, namely: |
10413 |
</p> |
10414 |
|
10415 |
<table> |
10416 |
<tr> |
10417 |
<th>Partition</th> |
10418 |
<th>Description</th> |
10419 |
</tr> |
10420 |
<tr> |
10421 |
<ti><path>/dev/sda1</path></ti> |
10422 |
<ti>PPC PReP Boot partition</ti> |
10423 |
</tr> |
10424 |
<tr> |
10425 |
<ti><path>/dev/sda2</path></ti> |
10426 |
<ti>Swap partition</ti> |
10427 |
</tr> |
10428 |
<tr> |
10429 |
<ti><path>/dev/sda3</path></ti> |
10430 |
<ti>Root partition</ti> |
10431 |
</tr> |
10432 |
</table> |
10433 |
|
10434 |
<p> |
10435 |
Change your partition layout according to your own preference. |
10436 |
</p> |
10437 |
|
10438 |
</body> |
10439 |
</subsection> |
10440 |
<subsection> |
10441 |
<title>Viewing the Current Partition Layout</title> |
10442 |
<body> |
10443 |
|
10444 |
<p> |
10445 |
<c>fdisk</c> is a popular and powerful tool to split your disk into |
10446 |
partitions. Fire up <c>fdisk</c> on your disk (in our example, we |
10447 |
use <path>/dev/sda</path>): |
10448 |
</p> |
10449 |
|
10450 |
<pre caption="Starting fdisk"> |
10451 |
# <i>fdisk /dev/sda</i> |
10452 |
</pre> |
10453 |
|
10454 |
<p> |
10455 |
Once in <c>fdisk</c>, you'll be greeted with a prompt that looks like |
10456 |
this: |
10457 |
</p> |
10458 |
|
10459 |
<pre caption="fdisk prompt"> |
10460 |
Command (m for help): |
10461 |
</pre> |
10462 |
|
10463 |
<p> |
10464 |
Type <c>p</c> to display your disk's current partition configuration: |
10465 |
</p> |
10466 |
|
10467 |
<pre caption="An example partition configuration"> |
10468 |
Command (m for help): p |
10469 |
|
10470 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
10471 |
141 heads, 63 sectors/track, 6761 cylinders |
10472 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
10473 |
|
10474 |
Device Boot Start End Blocks Id System |
10475 |
/dev/sda1 1 12 53266+ 83 Linux |
10476 |
/dev/sda2 13 233 981571+ 82 Linux swap |
10477 |
/dev/sda3 234 674 1958701+ 83 Linux |
10478 |
/dev/sda4 675 6761 27035410+ 5 Extended |
10479 |
/dev/sda5 675 2874 9771268+ 83 Linux |
10480 |
/dev/sda6 2875 2919 199836 83 Linux |
10481 |
/dev/sda7 2920 3008 395262 83 Linux |
10482 |
/dev/sda8 3009 6761 16668918 83 Linux |
10483 |
|
10484 |
Command (m for help): |
10485 |
</pre> |
10486 |
|
10487 |
<p> |
10488 |
This particular disk is configured to house six Linux filesystems |
10489 |
(each with a corresponding partition listed as "Linux") as well as a |
10490 |
swap partition (listed as "Linux swap"). |
10491 |
</p> |
10492 |
|
10493 |
</body> |
10494 |
</subsection> |
10495 |
<subsection> |
10496 |
<title>Removing all Partitions</title> |
10497 |
<body> |
10498 |
|
10499 |
<p> |
10500 |
We will first remove all existing partitions from the disk. Type |
10501 |
<c>d</c> to delete a partition. For instance, to delete an existing |
10502 |
<path>/dev/sda1</path>: |
10503 |
</p> |
10504 |
|
10505 |
<note> |
10506 |
If you don't want to delete all partitions just delete those you |
10507 |
want to delete. At this point the author recommends a backup of your |
10508 |
data to avoid the lose of it. |
10509 |
</note> |
10510 |
|
10511 |
<pre caption="Deleting a partition"> |
10512 |
Command (m for help): <i>d</i> |
10513 |
Partition number (1-4): <i>1</i> |
10514 |
</pre> |
10515 |
|
10516 |
<p> |
10517 |
The partition has been scheduled for deletion. It will no longer show up |
10518 |
if you type <c>p</c>, but it will not be erased until your changes have |
10519 |
been saved. If you made a mistake and want to abort without saving your |
10520 |
changes, type <c>q</c> immediately and hit enter and your partition will |
10521 |
not be deleted. |
10522 |
</p> |
10523 |
|
10524 |
<p> |
10525 |
Now, assuming that you do indeed want to wipe out all the partitions on |
10526 |
your system, repeatedly type <c>p</c> to print out a partition listing |
10527 |
and then type <c>d</c> and the number of the partition to delete it. |
10528 |
Eventually, you'll end up with a partition table with nothing in it: |
10529 |
</p> |
10530 |
|
10531 |
<pre caption="An empty partition table"> |
10532 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
10533 |
141 heads, 63 sectors/track, 6761 cylinders |
10534 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
10535 |
|
10536 |
Device Boot Start End Blocks Id System |
10537 |
|
10538 |
Command (m for help): |
10539 |
</pre> |
10540 |
|
10541 |
<p> |
10542 |
Now that the in-memory partition table is empty, we're ready to create |
10543 |
the partitions. We will use a default partitioning scheme as discussed |
10544 |
previously. Of course, don't follow these instructions to the letter if |
10545 |
you don't want the same partitioning scheme! |
10546 |
</p> |
10547 |
|
10548 |
</body> |
10549 |
</subsection> |
10550 |
<subsection> |
10551 |
<title>Creating the PPC PReP boot partition</title> |
10552 |
<body> |
10553 |
|
10554 |
<p> |
10555 |
We first create a small PReP boot partition. Type <c>n</c> to create a new |
10556 |
partition, then <c>p</c> to select a primary partition, followed by |
10557 |
<c>1</c> to select the first primary partition. When prompted for the |
10558 |
first cylinder, hit enter. When prompted for the last cylinder, type |
10559 |
<c>+7M</c> to create a partition 7 Mbyte in size. After you've done |
10560 |
this, type <c>t</c> to set the partition type, <c>1</c> to select the |
10561 |
partition you just created and then type in <c>41</c> to set the |
10562 |
partition type to "PPC PReP Boot". Finally, you'll need to mark the PReP |
10563 |
partition as bootable. |
10564 |
</p> |
10565 |
|
10566 |
<note> |
10567 |
The PReP partition has to be smaller than 8 MByte! |
10568 |
</note> |
10569 |
|
10570 |
<pre caption="Creating the PReP boot partition"> |
10571 |
Command (m for help): <i>p</i> |
10572 |
|
10573 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
10574 |
141 heads, 63 sectors/track, 6761 cylinders |
10575 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
10576 |
|
10577 |
Device Boot Start End Blocks Id System |
10578 |
|
10579 |
Command (m for help): <i>n</i> |
10580 |
Command action |
10581 |
e extended |
10582 |
p primary partition (1-4) |
10583 |
<i>p</i> |
10584 |
Partition number (1-4): <i>1</i> |
10585 |
First cylinder (1-6761, default 1): |
10586 |
Using default value 1 |
10587 |
Last cylinder or +size or +sizeM or +sizeK (1-6761, default |
10588 |
6761): <i>+8M</i> |
10589 |
|
10590 |
Command (m for help): <i>t</i> |
10591 |
Selected partition 1 |
10592 |
Hex code (type L to list codes): <i>41</i> |
10593 |
Changed system type of partition 1 to 41 (PPC PReP Boot) |
10594 |
|
10595 |
Command (m for help): <i>a</i> |
10596 |
Partition number (1-4): <i>1</i> |
10597 |
Command (m for help): |
10598 |
</pre> |
10599 |
|
10600 |
<p> |
10601 |
Now, when you type <c>p</c>, you should see the following partition information: |
10602 |
</p> |
10603 |
|
10604 |
<pre caption="Created boot partition"> |
10605 |
Command (m for help): <i>p</i> |
10606 |
|
10607 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
10608 |
141 heads, 63 sectors/track, 6761 cylinders |
10609 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
10610 |
|
10611 |
Device Boot Start End Blocks Id System |
10612 |
/dev/sda1 * 1 3 13293 41 PPC PReP Boot |
10613 |
|
10614 |
Command (m for help): |
10615 |
</pre> |
10616 |
</body> |
10617 |
</subsection> |
10618 |
<subsection> |
10619 |
<title>Creating the Swap Partition</title> |
10620 |
<body> |
10621 |
|
10622 |
<p> |
10623 |
Let's now create the swap partition. To do this, type <c>n</c> to create |
10624 |
a new partition, then <c>p</c> to tell fdisk that you want a primary |
10625 |
partition. Then type <c>2</c> to create the second primary partition, |
10626 |
<path>/dev/sda2</path> in our case. When prompted for the first |
10627 |
cylinder, hit enter. When prompted for the last cylinder, type |
10628 |
<c>+512M</c> to create a partition 512MB in size. After you've done |
10629 |
this, type <c>t</c> to set the partition type, <c>2</c> to select the |
10630 |
partition you just created and then type in <c>82</c> to set the |
10631 |
partition type to "Linux Swap". After completing these steps, typing |
10632 |
<c>p</c> should display a partition table that looks similar to this: |
10633 |
</p> |
10634 |
|
10635 |
<pre caption="Partition listing after creating a swap partition"> |
10636 |
Command (m for help): <i>p</i> |
10637 |
|
10638 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
10639 |
141 heads, 63 sectors/track, 6761 cylinders |
10640 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
10641 |
|
10642 |
Device Boot Start End Blocks Id System |
10643 |
/dev/sda1 1 3 13293 41 PPC PReP Boot |
10644 |
/dev/sda2 4 117 506331 82 Linux swap |
10645 |
|
10646 |
Command (m for help): |
10647 |
</pre> |
10648 |
|
10649 |
</body> |
10650 |
</subsection> |
10651 |
<subsection> |
10652 |
<title>Creating the Root Partition</title> |
10653 |
<body> |
10654 |
|
10655 |
<p> |
10656 |
Finally, let's create the root partition. To do this, type <c>n</c> to |
10657 |
create a new partition, then <c>p</c> to tell fdisk that you want a |
10658 |
primary partition. Then type <c>3</c> to create the third primary |
10659 |
partition, <path>/dev/sda3</path> in our case. When prompted for the |
10660 |
first cylinder, hit enter. When prompted for the last cylinder, hit |
10661 |
enter to create a partition that takes up the rest of the remaining |
10662 |
space on your disk. After completing these steps, typing <c>p</c> should |
10663 |
display a partition table that looks similar to this: |
10664 |
</p> |
10665 |
|
10666 |
<pre caption="Partition listing after creating the root partition"> |
10667 |
Command (m for help): p |
10668 |
|
10669 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
10670 |
141 heads, 63 sectors/track, 6761 cylinders |
10671 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
10672 |
|
10673 |
Device Boot Start End Blocks Id System |
10674 |
/dev/sda1 1 3 13293 41 PPC PReP Boot |
10675 |
/dev/sda2 4 117 506331 82 Linux swap |
10676 |
/dev/sda3 118 6761 29509326 83 Linux |
10677 |
|
10678 |
Command (m for help): |
10679 |
</pre> |
10680 |
</body> |
10681 |
</subsection> |
10682 |
<subsection> |
10683 |
<title>Saving the Partition Layout</title> |
10684 |
<body> |
10685 |
|
10686 |
<p> |
10687 |
To save the partition layout and exit <c>fdisk</c>, type <c>w</c>. |
10688 |
</p> |
10689 |
|
10690 |
<pre caption="Save and exit fdisk"> |
10691 |
Command (m for help): <i>w</i> |
10692 |
</pre> |
10693 |
|
10694 |
<p> |
10695 |
Now that your partitions are created, you can now continue with <uri |
10696 |
link="#filesystems">Creating Filesystems</uri>. |
10697 |
</p> |
10698 |
|
10699 |
</body> |
10700 |
</subsection> |
10701 |
</section> |
10702 |
<section id="filesystems"> |
10703 |
<title>Creating Filesystems</title> |
10704 |
<subsection> |
10705 |
<title>Introduction</title> |
10706 |
<body> |
10707 |
|
10708 |
<p> |
10709 |
Now that your partitions are created, it is time to place a filesystem on them. |
10710 |
If you don't care about what filesystem to choose and are happy with what we use |
10711 |
as default in this handbook, continue with <uri |
10712 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
10713 |
Otherwise read on to learn about the available filesystems... |
10714 |
</p> |
10715 |
|
10716 |
</body> |
10717 |
</subsection> |
10718 |
<subsection> |
10719 |
<title>Filesystems?</title> |
10720 |
<body> |
10721 |
|
10722 |
<note> |
10723 |
Several filesystems are available. ext2, ext3 and ReiserFS support is built in |
10724 |
the Installation CD kernels. JFS and XFS support is available through kernel |
10725 |
modules. |
10726 |
</note> |
10727 |
|
10728 |
<p> |
10729 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
10730 |
journaling, which means that routine ext2 filesystem checks at startup time can |
10731 |
be quite time-consuming. There is now quite a selection of newer-generation |
10732 |
journaled filesystems that can be checked for consistency very quickly and are |
10733 |
thus generally preferred over their non-journaled counterparts. Journaled |
10734 |
filesystems prevent long delays when you boot your system and your filesystem |
10735 |
happens to be in an inconsistent state. |
10736 |
</p> |
10737 |
|
10738 |
<p> |
10739 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
10740 |
journaling for fast recovery in addition to other enhanced journaling modes |
10741 |
like full data and ordered data journaling. It uses a hashed B*-tree index that |
10742 |
enables high performance in almost all situations. In short, ext3 is a very |
10743 |
good and reliable filesystem. |
10744 |
</p> |
10745 |
|
10746 |
<p> |
10747 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
10748 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
10749 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
10750 |
extremely well and has metadata journaling. ReiserFS is solid and usable as |
10751 |
both general-purpose filesystem and for extreme cases such as the creation of |
10752 |
large filesystems, very large files and directories containing tens of |
10753 |
thousands of small files. |
10754 |
</p> |
10755 |
|
10756 |
<p> |
10757 |
<b>XFS</b> is a filesystem with metadata journaling that is fully supported |
10758 |
under Gentoo Linux's xfs-sources kernel. It comes with a robust feature-set and |
10759 |
is optimized for scalability. We only recommend using this filesystem on Linux |
10760 |
systems with high-end SCSI and/or fibre channel storage and a uninterruptible |
10761 |
power supply. Because XFS aggressively caches in-transit data in RAM, improperly |
10762 |
designed programs (those that don't take proper precautions when writing files |
10763 |
to disk and there are quite a few of them) can lose a good deal of data if the |
10764 |
system goes down unexpectedly. |
10765 |
</p> |
10766 |
|
10767 |
<p> |
10768 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
10769 |
become production-ready. |
10770 |
</p> |
10771 |
|
10772 |
</body> |
10773 |
</subsection> |
10774 |
<subsection id="filesystems-apply"> |
10775 |
<title>Applying a Filesystem to a Partition</title> |
10776 |
<body> |
10777 |
|
10778 |
<p> |
10779 |
To create a filesystem on a partition or volume, there are tools available for |
10780 |
each possible filesystem: |
10781 |
</p> |
10782 |
|
10783 |
<table> |
10784 |
<tr> |
10785 |
<th>Filesystem</th> |
10786 |
<th>Creation Command</th> |
10787 |
</tr> |
10788 |
<tr> |
10789 |
<ti>ext2</ti> |
10790 |
<ti><c>mke2fs</c></ti> |
10791 |
</tr> |
10792 |
<tr> |
10793 |
<ti>ext3</ti> |
10794 |
<ti><c>mke2fs -j</c></ti> |
10795 |
</tr> |
10796 |
<tr> |
10797 |
<ti>reiserfs</ti> |
10798 |
<ti><c>mkreiserfs</c></ti> |
10799 |
</tr> |
10800 |
<tr> |
10801 |
<ti>xfs</ti> |
10802 |
<ti><c>mkfs.xfs</c></ti> |
10803 |
</tr> |
10804 |
<tr> |
10805 |
<ti>jfs</ti> |
10806 |
<ti><c>mkfs.jfs</c></ti> |
10807 |
</tr> |
10808 |
</table> |
10809 |
|
10810 |
<p> |
10811 |
For instance, to have the root partition (<path>/dev/sda4</path> in our example) |
10812 |
in ext3 (as in our example), you would use: |
10813 |
</p> |
10814 |
|
10815 |
<pre caption="Applying a filesystem on a partition"> |
10816 |
# <i>mke2fs -j /dev/sda4</i> |
10817 |
</pre> |
10818 |
|
10819 |
<p> |
10820 |
Now create the filesystems on your newly created partitions (or logical |
10821 |
volumes). |
10822 |
</p> |
10823 |
|
10824 |
</body> |
10825 |
</subsection> |
10826 |
<subsection> |
10827 |
<title>Activating the Swap Partition</title> |
10828 |
<body> |
10829 |
|
10830 |
<p> |
10831 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
10832 |
</p> |
10833 |
|
10834 |
<pre caption="Creating a Swap signature"> |
10835 |
# <i>mkswap /dev/sda3</i> |
10836 |
</pre> |
10837 |
|
10838 |
<p> |
10839 |
To activate the swap partition, use <c>swapon</c>: |
10840 |
</p> |
10841 |
|
10842 |
<pre caption="Activating the swap partition"> |
10843 |
# <i>swapon /dev/sda3</i> |
10844 |
</pre> |
10845 |
|
10846 |
<p> |
10847 |
Create and activate the swap with the commands mentioned above. |
10848 |
</p> |
10849 |
|
10850 |
</body> |
10851 |
</subsection> |
10852 |
</section> |
10853 |
<section> |
10854 |
<title>Mounting</title> |
10855 |
<body> |
10856 |
|
10857 |
<p> |
10858 |
Now that your partitions are initialized and are housing a filesystem, it is |
10859 |
time to mount those partitions. Use the <c>mount</c> command. As an example we |
10860 |
mount the root partition: |
10861 |
</p> |
10862 |
|
10863 |
<pre caption="Mounting partitions"> |
10864 |
# <i>mount /dev/sda4 /mnt/gentoo</i> |
10865 |
</pre> |
10866 |
|
10867 |
<note> |
10868 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
10869 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
10870 |
also holds for <path>/var/tmp</path>. |
10871 |
</note> |
10872 |
|
10873 |
<p> |
10874 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
10875 |
Installation Files</uri>. |
10876 |
</p> |
10877 |
|
10878 |
</body> |
10879 |
</section> |
10880 |
</sections> |
10881 |
|
10882 |
|
10883 |
|
10884 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-kernel.xml |
10885 |
|
10886 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-kernel.xml?rev=1.1&view=markup |
10887 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-kernel.xml?rev=1.1&content-type=text/plain |
10888 |
|
10889 |
Index: hb-install-ppc64-kernel.xml |
10890 |
=================================================================== |
10891 |
<?xml version='1.0' encoding='UTF-8'?> |
10892 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
10893 |
|
10894 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
10895 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
10896 |
|
10897 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-kernel.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
10898 |
|
10899 |
<sections> |
10900 |
|
10901 |
<version>7.1</version> |
10902 |
<date>2007-02-26</date> |
10903 |
|
10904 |
<section> |
10905 |
<title>Timezone</title> |
10906 |
<body> |
10907 |
|
10908 |
<p> |
10909 |
You first need to select your timezone so that your system knows where it is |
10910 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
10911 |
it to <path>/etc/localtime</path>. Please avoid the |
10912 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
10913 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
10914 |
</p> |
10915 |
|
10916 |
<pre caption="Setting the timezone information"> |
10917 |
# <i>ls /usr/share/zoneinfo</i> |
10918 |
<comment>(Suppose you want to use GMT)</comment> |
10919 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
10920 |
</pre> |
10921 |
|
10922 |
</body> |
10923 |
</section> |
10924 |
<section> |
10925 |
<title>Installing the Sources</title> |
10926 |
<subsection> |
10927 |
<title>Choosing a Kernel</title> |
10928 |
<body> |
10929 |
|
10930 |
<p> |
10931 |
The core around which all distributions are built is the Linux kernel. |
10932 |
It is the layer between the user programs and your system hardware. |
10933 |
Gentoo provides its users several possible kernel sources. A full |
10934 |
listing with description is available at the <uri |
10935 |
link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>. |
10936 |
</p> |
10937 |
|
10938 |
<p> |
10939 |
For PPC64 you should use <c>gentoo-sources</c>. |
10940 |
</p> |
10941 |
|
10942 |
<pre caption="Installing a kernel source"> |
10943 |
# <i>emerge gentoo-sources</i> |
10944 |
</pre> |
10945 |
|
10946 |
<p> |
10947 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
10948 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
10949 |
kernel source points to <c>gentoo-sources-2.6.17-r5</c>. Your version may be |
10950 |
different, so keep this in mind. |
10951 |
</p> |
10952 |
|
10953 |
<pre caption="Viewing the kernel source symlink"> |
10954 |
# <i>ls -l /usr/src/linux</i> |
10955 |
lrwxrwxrwx 1 root root 12 Aug 10 11:04 /usr/src/linux -> linux-2.6.17-gentoo-r5 |
10956 |
</pre> |
10957 |
|
10958 |
<p> |
10959 |
Now it is time to configure and compile your kernel source. There is the |
10960 |
ability to use "genkernel" which would create a generic kernel like the |
10961 |
ones used on the installation CDs, but it is not fully functional for PPC64 at |
10962 |
the moment. |
10963 |
</p> |
10964 |
|
10965 |
<p> |
10966 |
Continue now with <uri link="#manual">Manual Configuration</uri>. |
10967 |
</p> |
10968 |
|
10969 |
</body> |
10970 |
</subsection> |
10971 |
</section> |
10972 |
<section id="manual"> |
10973 |
<title>Manual Configuration</title> |
10974 |
<subsection> |
10975 |
<title>Introduction</title> |
10976 |
<body> |
10977 |
|
10978 |
<p> |
10979 |
Manually configuring a kernel is often seen as the most difficult procedure a |
10980 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
10981 |
couple of kernels you don't even remember that it was difficult ;) |
10982 |
</p> |
10983 |
|
10984 |
<p> |
10985 |
However, one thing <e>is</e> true: you must know your system when you |
10986 |
configuring a kernel manually. Most information can be gathered by emerging |
10987 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
10988 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
10989 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
10990 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
10991 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
10992 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
10993 |
uses (it might provide you with a nice hint on what to enable). |
10994 |
</p> |
10995 |
|
10996 |
<pre caption="Invoking menuconfig"> |
10997 |
# <i>cd /usr/src/linux</i> |
10998 |
<comment>Important: In case you are in 32-bit userland, you must edit the top |
10999 |
level Makefile in /usr/src/linux and change the CROSS_COMPILE option to |
11000 |
CROSS_COMPILE ?= powerpc64-unknown-linux-gnu-. You must do this before you run |
11001 |
make menuconfig or it may result in kernel compilation problems.</comment> |
11002 |
# <i>make menuconfig</i> |
11003 |
</pre> |
11004 |
|
11005 |
<p> |
11006 |
You will be greeted with several configuration sections. We'll first |
11007 |
list some options you must activate (otherwise Gentoo will not function, |
11008 |
or not function properly without additional tweaks). |
11009 |
</p> |
11010 |
|
11011 |
</body> |
11012 |
</subsection> |
11013 |
<subsection> |
11014 |
<title>Activating Required Options</title> |
11015 |
<body> |
11016 |
|
11017 |
<p> |
11018 |
First of all, activate the use of development and experimental |
11019 |
code/drivers. You need this, otherwise some very important code/drivers |
11020 |
won't show up: |
11021 |
</p> |
11022 |
|
11023 |
<pre caption="Selecting experimental code/drivers"> |
11024 |
Code maturity level options ---> |
11025 |
[*] Prompt for development and/or incomplete code/drivers |
11026 |
</pre> |
11027 |
|
11028 |
<p> |
11029 |
Now go to <c>File Systems</c> and select support for the filesystems you |
11030 |
use. <e>Don't</e> compile them as modules, otherwise your Gentoo system |
11031 |
will not be able to mount your partitions. Also select <c>Virtual |
11032 |
memory</c>, <c>/proc file system</c>, and <c>/dev/pts file system for |
11033 |
Unix98 PTYs</c>: |
11034 |
</p> |
11035 |
|
11036 |
<pre caption="Selecting necessary file systems"> |
11037 |
File systems ---> |
11038 |
[*] Virtual memory file system support (former shm fs) |
11039 |
[*] /proc file system support |
11040 |
[*] /dev/pts file system for Unix98 PTYs |
11041 |
|
11042 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
11043 |
<*> Reiserfs support |
11044 |
<*> Ext3 journalling file system support |
11045 |
<*> JFS filesystem support |
11046 |
<*> Second extended fs support |
11047 |
<*> XFS filesystem support |
11048 |
</pre> |
11049 |
|
11050 |
<note> |
11051 |
You will find some of the mentioned options under <c>Pseudo |
11052 |
filesystems</c> which is a subpart of <c>File systems</c>. |
11053 |
</note> |
11054 |
|
11055 |
<p> |
11056 |
If you are using PPPoE to connect to the Internet or you are using a |
11057 |
dial-up modem, you will need the following options in the kernel (you |
11058 |
will find the mentioned options under <c>Networking support</c> which is |
11059 |
a subpart of <c>Device Drivers</c>): |
11060 |
</p> |
11061 |
|
11062 |
<pre caption="Selecting PPPoE necessary drivers"> |
11063 |
Network device support ---> |
11064 |
<*> PPP (point-to-point protocol) support |
11065 |
<*> PPP support for async serial ports |
11066 |
<*> PPP support for sync tty ports |
11067 |
</pre> |
11068 |
|
11069 |
<p> |
11070 |
The two compression options won't harm but are not definitely needed, neither |
11071 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
11072 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
11073 |
</p> |
11074 |
|
11075 |
<p> |
11076 |
If you require it, don't forget to include support in the kernel for your |
11077 |
ethernet card. |
11078 |
</p> |
11079 |
|
11080 |
<p> |
11081 |
Disable ADB raw keycodes: |
11082 |
</p> |
11083 |
|
11084 |
<pre caption="Disabling ADB raw keycodes"> |
11085 |
Macintosh Device Drivers ---> |
11086 |
[ ] Support for ADB raw keycodes |
11087 |
</pre> |
11088 |
|
11089 |
<p> |
11090 |
When you're done configuring your kernel, continue with <uri |
11091 |
link="#compiling">Compiling and Installing</uri>. |
11092 |
</p> |
11093 |
|
11094 |
</body> |
11095 |
</subsection> |
11096 |
<subsection id="compiling"> |
11097 |
<title>Compiling and Installing</title> |
11098 |
<body> |
11099 |
|
11100 |
<p> |
11101 |
Now that your kernel is configured, it is time to compile and install it. Exit |
11102 |
the configuration and start the compilation process: |
11103 |
</p> |
11104 |
|
11105 |
<pre caption="Compiling the kernel"> |
11106 |
# <i>make vmlinux && make modules_install</i> |
11107 |
</pre> |
11108 |
|
11109 |
<p> |
11110 |
When the kernel has finished compiling, copy the kernel image to |
11111 |
<path>/boot</path>. Remember to replace <path><kernel-version></path> |
11112 |
with your actual kernel version: |
11113 |
</p> |
11114 |
|
11115 |
<pre caption="Installing the kernel"> |
11116 |
# <i>cp vmlinux /boot/<kernel-version></i> |
11117 |
</pre> |
11118 |
|
11119 |
<p> |
11120 |
Now continue with <uri link="#kernel_modules">Configuring the Modules</uri>. |
11121 |
</p> |
11122 |
|
11123 |
</body> |
11124 |
</subsection> |
11125 |
</section> |
11126 |
<section id="kernel_modules"> |
11127 |
<title>Configuring the Modules</title> |
11128 |
<body> |
11129 |
|
11130 |
<p> |
11131 |
You should list the modules you want automatically loaded in |
11132 |
<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra |
11133 |
options to the modules too if you want. |
11134 |
</p> |
11135 |
|
11136 |
<p> |
11137 |
To view all available modules, run the following <c>find</c> command. Don't |
11138 |
forget to substitute "<kernel version>" with the version of the kernel you |
11139 |
just compiled: |
11140 |
</p> |
11141 |
|
11142 |
<pre caption="Viewing all available modules"> |
11143 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
11144 |
</pre> |
11145 |
|
11146 |
<p> |
11147 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
11148 |
<path>kernel-2.6</path> file and enter the module name in it. |
11149 |
</p> |
11150 |
|
11151 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
11152 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
11153 |
</pre> |
11154 |
|
11155 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
11156 |
3c59x |
11157 |
</pre> |
11158 |
|
11159 |
<p> |
11160 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
11161 |
your System</uri>. |
11162 |
</p> |
11163 |
|
11164 |
</body> |
11165 |
</section> |
11166 |
</sections> |
11167 |
|
11168 |
|
11169 |
|
11170 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-medium.xml |
11171 |
|
11172 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-medium.xml?rev=1.1&view=markup |
11173 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-medium.xml?rev=1.1&content-type=text/plain |
11174 |
|
11175 |
Index: hb-install-ppc64-medium.xml |
11176 |
=================================================================== |
11177 |
<?xml version='1.0' encoding='UTF-8'?> |
11178 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
11179 |
|
11180 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
11181 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
11182 |
|
11183 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc64-medium.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
11184 |
|
11185 |
<sections> |
11186 |
|
11187 |
<version>7.0</version> |
11188 |
<date>2006-08-30</date> |
11189 |
|
11190 |
<section> |
11191 |
<title>Hardware Requirements</title> |
11192 |
<subsection> |
11193 |
<title>Introduction</title> |
11194 |
<body> |
11195 |
|
11196 |
<p> |
11197 |
Before we start, we first list what hardware requirements you need to |
11198 |
successfully install Gentoo on your box. |
11199 |
</p> |
11200 |
|
11201 |
</body> |
11202 |
</subsection> |
11203 |
<subsection> |
11204 |
<title>Hardware Requirements</title> |
11205 |
<body> |
11206 |
|
11207 |
<table> |
11208 |
<tr> |
11209 |
<th>CPU</th> |
11210 |
<ti>Any PowerPC64 CPU</ti> |
11211 |
</tr> |
11212 |
<tr> |
11213 |
<th>Systems</th> |
11214 |
<ti> |
11215 |
IBM RS/6000s, Power Macintosh G5, iMac G5, IBP pSeries and IBM OpenPower |
11216 |
</ti> |
11217 |
</tr> |
11218 |
<tr> |
11219 |
<th>Memory</th> |
11220 |
<ti>64 MB</ti> |
11221 |
</tr> |
11222 |
<tr> |
11223 |
<th>Diskspace</th> |
11224 |
<ti>1.5 GB (excluding swap space)</ti> |
11225 |
</tr> |
11226 |
<tr> |
11227 |
<th>Swap space</th> |
11228 |
<ti>At least 256 MB</ti> |
11229 |
</tr> |
11230 |
</table> |
11231 |
|
11232 |
<p> |
11233 |
For a full list of supported systems, please go to |
11234 |
<uri>http://www.linuxppc64.org/hardware.shtml</uri>. |
11235 |
</p> |
11236 |
|
11237 |
</body> |
11238 |
</subsection> |
11239 |
</section> |
11240 |
<!-- Copy/paste from hb-install-x86-medium.xml, with s/x86/ppc64/ --> |
11241 |
<!-- START --> |
11242 |
<section> |
11243 |
<title>The Gentoo Universal Installation CD</title> |
11244 |
<subsection> |
11245 |
<title>Introduction</title> |
11246 |
<body> |
11247 |
|
11248 |
<p> |
11249 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
11250 |
Such a tarball is an archive that contains a minimal environment from |
11251 |
which you can succesfully install Gentoo Linux onto your system. |
11252 |
</p> |
11253 |
|
11254 |
<p> |
11255 |
Installations using a stage1 or stage2 tarball file are not documented in the |
11256 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
11257 |
FAQ</uri> on these matters. |
11258 |
</p> |
11259 |
|
11260 |
</body> |
11261 |
</subsection> |
11262 |
<subsection> |
11263 |
<title>Gentoo Universal Installation CD</title> |
11264 |
<body> |
11265 |
|
11266 |
<p> |
11267 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
11268 |
environment. It allows you to boot Linux from the CD. During the boot process |
11269 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
11270 |
Installation CDs are maintained by Gentoo developers. |
11271 |
</p> |
11272 |
|
11273 |
<p> |
11274 |
There currently are two Installation CDs available: |
11275 |
</p> |
11276 |
|
11277 |
<ul> |
11278 |
<li> |
11279 |
The Universal Installation CD contains everything you need to install |
11280 |
Gentoo. It provides stage3 files for common architectures, source code |
11281 |
for the extra applications you need to choose from and, of course, the |
11282 |
installation instructions for your architecture. |
11283 |
</li> |
11284 |
<li> |
11285 |
The Minimal Installation CD contains only a minimal environment that allows |
11286 |
you to boot up and configure your network so you can connect to the |
11287 |
Internet. It does not contain any additional files and cannot be used |
11288 |
during the current installation approach. |
11289 |
</li> |
11290 |
</ul> |
11291 |
|
11292 |
<p> |
11293 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
11294 |
additional resource that you can exploit during the installation of your Gentoo |
11295 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
11296 |
you to easily and quickly install additional applications immediately after the |
11297 |
Gentoo installation and right before you update your Portage tree. |
11298 |
</p> |
11299 |
|
11300 |
<p> |
11301 |
The use of the Package CD is covered later in this document. |
11302 |
</p> |
11303 |
|
11304 |
</body> |
11305 |
</subsection> |
11306 |
</section> |
11307 |
<!-- STOP --> |
11308 |
<section> |
11309 |
<title>Download, Burn and Boot a Gentoo Installation CD</title> |
11310 |
<subsection> |
11311 |
<title>Downloading and Burning the Installation CDs</title> |
11312 |
<body> |
11313 |
|
11314 |
<p> |
11315 |
You can download the Universal Installation CD (and, if you want to, the |
11316 |
Packages CD as well) from one of our <uri |
11317 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located |
11318 |
in the <path>releases/ppc/2006.1/ppc64/installcd</path> directory; the Package |
11319 |
CDs are located in the <path>releases/ppc/2006.1/ppc64/packagecd</path> |
11320 |
directory. |
11321 |
</p> |
11322 |
|
11323 |
<p> |
11324 |
Inside those directories you'll find ISO-files. Those are full CD images which |
11325 |
you can write on a CD-R. |
11326 |
</p> |
11327 |
|
11328 |
<p> |
11329 |
After downloading the file, you can verify its integrity to see if it is |
11330 |
corrupted or not: |
11331 |
</p> |
11332 |
|
11333 |
<ul> |
11334 |
<li> |
11335 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
11336 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
11337 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows). How |
11338 |
to verify MD5 checksums with Mac OS X is described in the <uri |
11339 |
link="/doc/en/gentoo-ppc-faq.xml#doc_chap1">Gentoo PPC FAQ</uri>. |
11340 |
</li> |
11341 |
<li> |
11342 |
You can verify the cryptographic signature that we provide. You need to |
11343 |
obtain the public key we use (0x17072058) before you proceed though. |
11344 |
</li> |
11345 |
</ul> |
11346 |
|
11347 |
<p> |
11348 |
To fetch our public key using the GnuPG application, run the following command: |
11349 |
</p> |
11350 |
|
11351 |
<pre caption="Obtaining the public key"> |
11352 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 0x17072058</i> |
11353 |
</pre> |
11354 |
|
11355 |
<p> |
11356 |
Now verify the signature: |
11357 |
</p> |
11358 |
|
11359 |
<pre caption="Verify the cryptographic signature"> |
11360 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
11361 |
</pre> |
11362 |
|
11363 |
<p> |
11364 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
11365 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
11366 |
<c>K3B</c> here; more information can be found in our <uri |
11367 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
11368 |
</p> |
11369 |
|
11370 |
<ul> |
11371 |
<li> |
11372 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
11373 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
11374 |
path). |
11375 |
</li> |
11376 |
<li> |
11377 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
11378 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
11379 |
<c>Start</c>. |
11380 |
</li> |
11381 |
</ul> |
11382 |
|
11383 |
</body> |
11384 |
</subsection> |
11385 |
<subsection> |
11386 |
<title>Booting the Installation CD on an Apple</title> |
11387 |
<body> |
11388 |
|
11389 |
<p> |
11390 |
Please check the <path>README.kernel</path> on the Installation CD for the |
11391 |
latest information on how to boot various kernels and getting hardware support. |
11392 |
</p> |
11393 |
|
11394 |
<p> |
11395 |
Place the Installation CD in the CD-ROM and reboot the system. Hold down the |
11396 |
'C' key at bootup. You will be greeted by a friendly welcome message and a |
11397 |
<e>boot:</e> prompt at the bottom of the screen. |
11398 |
</p> |
11399 |
|
11400 |
<p> |
11401 |
You are also able to tweak some kernel options at this prompt. The following |
11402 |
table lists the available boot options you can add: |
11403 |
</p> |
11404 |
|
11405 |
<table> |
11406 |
<tr> |
11407 |
<th>Boot Option</th> |
11408 |
<th>Description</th> |
11409 |
</tr> |
11410 |
<tr> |
11411 |
<ti><c>video</c></ti> |
11412 |
<ti> |
11413 |
This option takes one of the following vendor-specific tags: |
11414 |
<c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, <c>aty128</c>, <c>nvidiafb</c> |
11415 |
or <c>ofonly</c>. You can follow this tag with the resolution and |
11416 |
refreshrate you want to use. For instance <c>video=radeonfb:1280x1024@75</c> |
11417 |
. If you are uncertain what to choose, <c>ofonly</c> will most certainly |
11418 |
work. |
11419 |
</ti> |
11420 |
</tr> |
11421 |
<tr> |
11422 |
<ti><c>nol3</c></ti> |
11423 |
<ti> |
11424 |
Disables level 3 cache on some powerbooks (needed for at least the 17'') |
11425 |
</ti> |
11426 |
</tr> |
11427 |
<tr> |
11428 |
<ti><c>debug</c></ti> |
11429 |
<ti> |
11430 |
Enables verbose booting, spawns an initrd shell that can be used to debug |
11431 |
the Installation CD |
11432 |
</ti> |
11433 |
</tr> |
11434 |
<tr> |
11435 |
<ti><c>sleep=X</c></ti> |
11436 |
<ti> |
11437 |
Wait X seconds before continuing; this can be needed by some very old SCSI |
11438 |
CD-ROMs which don't speed up the CD quick enough |
11439 |
</ti> |
11440 |
</tr> |
11441 |
<tr> |
11442 |
<ti><c>bootfrom=X</c></ti> |
11443 |
<ti> |
11444 |
Boot from a different device |
11445 |
</ti> |
11446 |
</tr> |
11447 |
</table> |
11448 |
|
11449 |
<p> |
11450 |
At this prompt, hit enter, and a complete Gentoo Linux environment will be |
11451 |
loaded from the CD. Continue with <uri link="#booted">And When You're |
11452 |
Booted...</uri>. |
11453 |
</p> |
11454 |
|
11455 |
</body> |
11456 |
</subsection> |
11457 |
<subsection> |
11458 |
<title>Booting the Installation CD on an IBM pSeries, OpenPower and Power5 |
11459 |
iSeries servers</title> |
11460 |
<body> |
11461 |
|
11462 |
<p> |
11463 |
Please check the <path>README.kernel</path> on the Installation CD for the |
11464 |
latest information on how to boot various kernels and getting hardware support. |
11465 |
</p> |
11466 |
|
11467 |
<p> |
11468 |
Most modern pSeries servers can boot from the CDROM drive through SMS ('1' when |
11469 |
the “IBM IBM IBM” messages flash across the console). On some older pSeries |
11470 |
boxes, sometimes the cds might not autoboot. You might have to set up your |
11471 |
cdrom as a bootable device in the multi-boot menu. (F1 at startup) The other |
11472 |
option is to jump into OF and do it from there: |
11473 |
</p> |
11474 |
|
11475 |
<ol> |
11476 |
<li> |
11477 |
Boot into OF (this is 8 from the serial cons or F8 from a graphics |
11478 |
cons, start hitting the key when you see the keyboard mouse etc etc |
11479 |
messages. |
11480 |
</li> |
11481 |
<li>Run the command 0> boot cdrom:1,yaboot</li> |
11482 |
<li>Stand back and enjoy!</li> |
11483 |
</ol> |
11484 |
|
11485 |
</body> |
11486 |
</subsection> |
11487 |
<subsection id="booted"> |
11488 |
<title>And When You're Booted...</title> |
11489 |
<body> |
11490 |
|
11491 |
<p> |
11492 |
You will be greeted by a root ("#") prompt on the current console. You can also |
11493 |
switch to other consoles by pressing Alt-fn-F2, Alt-fn-F3 and Alt-fn-F4. Get |
11494 |
back to the one you started on by pressing Alt-fn-F1. |
11495 |
</p> |
11496 |
|
11497 |
<p> |
11498 |
If you are installing Gentoo on a system with a non-US keyboard, use |
11499 |
<c>loadkeys</c> to load the keymap for your keyboard. To list the available |
11500 |
keymaps, execute <c>ls /usr/share/keymaps/i386</c>. |
11501 |
</p> |
11502 |
|
11503 |
<pre caption="Listing available keymaps"> |
11504 |
<comment>(PPC uses x86 keymaps on most systems. The mac/ppc keymaps provided |
11505 |
on the Installation CD are ADB keymaps and unusable with the |
11506 |
Installation CD kernel)</comment> |
11507 |
# <i>ls /usr/share/keymaps/i386</i> |
11508 |
</pre> |
11509 |
|
11510 |
<p> |
11511 |
Now load the keymap of your choice: |
11512 |
</p> |
11513 |
|
11514 |
<pre caption="Loading a keymap"> |
11515 |
# <i>loadkeys be-latin1</i> |
11516 |
</pre> |
11517 |
|
11518 |
<p> |
11519 |
Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
11520 |
</p> |
11521 |
|
11522 |
</body> |
11523 |
</subsection> |
11524 |
<subsection id="hardware"> |
11525 |
<title>Extra Hardware Configuration</title> |
11526 |
<body> |
11527 |
|
11528 |
<p> |
11529 |
When the Installation CD boots, it tries to detect all your hardware devices and |
11530 |
loads the appropriate kernel modules to support your hardware. In the |
11531 |
vast majority of cases, it does a very good job. However, in some cases it may |
11532 |
not auto-load the kernel |
11533 |
modules you need. If the PCI auto-detection missed some of your system's |
11534 |
hardware, you will have to load the appropriate kernel modules manually. |
11535 |
</p> |
11536 |
|
11537 |
<p> |
11538 |
In the next example we try to load the <c>8139too</c> module (support for |
11539 |
certain kinds of network interfaces): |
11540 |
</p> |
11541 |
|
11542 |
<pre caption="Loading kernel modules"> |
11543 |
# <i>modprobe 8139too</i> |
11544 |
</pre> |
11545 |
|
11546 |
</body> |
11547 |
</subsection> |
11548 |
<subsection> |
11549 |
<title>Optional: Tweaking Hard Disk Performance</title> |
11550 |
<body> |
11551 |
|
11552 |
<p> |
11553 |
If you are an advanced user, you might want to tweak the IDE hard disk |
11554 |
performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
11555 |
test the performance of your disk (execute it several times to get a |
11556 |
more precise impression): |
11557 |
</p> |
11558 |
|
11559 |
<pre caption="Testing disk performance"> |
11560 |
# <i>hdparm -tT /dev/hda</i> |
11561 |
</pre> |
11562 |
|
11563 |
<p> |
11564 |
To tweak, you can use any of the following examples (or experiment |
11565 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
11566 |
disk): |
11567 |
</p> |
11568 |
|
11569 |
<pre caption="Tweaking hard disk performance"> |
11570 |
<comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i> |
11571 |
<comment>Activate DMA + Safe Performance-enhancing Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
11572 |
</pre> |
11573 |
|
11574 |
</body> |
11575 |
</subsection> |
11576 |
<subsection id="useraccounts"> |
11577 |
<title>Optional: User Accounts</title> |
11578 |
<body> |
11579 |
|
11580 |
<p> |
11581 |
If you plan on giving other people access to your installation |
11582 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
11583 |
security reasons), you need to create the necessary user accounts and change |
11584 |
the root password. |
11585 |
</p> |
11586 |
|
11587 |
<p> |
11588 |
To change the root password, use the <c>passwd</c> utility: |
11589 |
</p> |
11590 |
|
11591 |
<pre caption="Changing the root password"> |
11592 |
# <i>passwd</i> |
11593 |
New password: <comment>(Enter your new password)</comment> |
11594 |
Re-enter password: <comment>(Re-enter your password)</comment> |
11595 |
</pre> |
11596 |
|
11597 |
<p> |
11598 |
To create a user account, we first enter their credentials, followed by |
11599 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
11600 |
In the next example, we create a user called "john". |
11601 |
</p> |
11602 |
|
11603 |
<pre caption="Creating a user account"> |
11604 |
# <i>useradd -m -G users john</i> |
11605 |
# <i>passwd john</i> |
11606 |
New password: <comment>(Enter john's password)</comment> |
11607 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
11608 |
</pre> |
11609 |
|
11610 |
<p> |
11611 |
You can change your user id from root to the newly created user by using |
11612 |
<c>su</c>: |
11613 |
</p> |
11614 |
|
11615 |
<pre caption="Changing user id"> |
11616 |
# <i>su - john</i> |
11617 |
</pre> |
11618 |
|
11619 |
</body> |
11620 |
</subsection> |
11621 |
<subsection> |
11622 |
<title>Optional: Viewing Documentation while Installing</title> |
11623 |
<body> |
11624 |
|
11625 |
<p> |
11626 |
If you want to view the Gentoo Handbook during the installation, make sure you |
11627 |
have created a user account (see <uri link="#useraccounts">Optional: User |
11628 |
Accounts</uri>). Then press <c>Alt-F2</c> to go to a new terminal and log in. |
11629 |
</p> |
11630 |
|
11631 |
<p> |
11632 |
If you want to view the documentation on the CD you can immediately run |
11633 |
<c>links</c> to read it: |
11634 |
</p> |
11635 |
|
11636 |
<pre caption="Viewing the on-CD documentation"> |
11637 |
# <i>links /mnt/cdrom/docs/handbook/html/index.html</i> |
11638 |
</pre> |
11639 |
|
11640 |
<p> |
11641 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
11642 |
more recent than the one provided on the CD. |
11643 |
</p> |
11644 |
|
11645 |
<pre caption="Viewing the Online Documentation"> |
11646 |
# <i>links http://www.gentoo.org/doc/en/handbook/handbook-ppc64.xml</i> |
11647 |
</pre> |
11648 |
|
11649 |
<p> |
11650 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
11651 |
</p> |
11652 |
|
11653 |
</body> |
11654 |
</subsection> |
11655 |
<subsection> |
11656 |
<title>Optional: Starting the SSH Daemon</title> |
11657 |
<body> |
11658 |
|
11659 |
<p> |
11660 |
If you want to allow other users to access your computer during the |
11661 |
Gentoo installation (perhaps because those users are going to help you |
11662 |
install Gentoo, or even do it for you), you need to create a user |
11663 |
account for them and perhaps even provide them with your root password |
11664 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
11665 |
</p> |
11666 |
|
11667 |
<p> |
11668 |
To fire up the SSH daemon, execute the following command: |
11669 |
</p> |
11670 |
|
11671 |
<pre caption="Starting the SSH daemon"> |
11672 |
# <i>/etc/init.d/sshd start</i> |
11673 |
</pre> |
11674 |
|
11675 |
<p> |
11676 |
To be able to use sshd, you first need to set up your networking. Continue with |
11677 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
11678 |
</p> |
11679 |
|
11680 |
</body> |
11681 |
</subsection> |
11682 |
</section> |
11683 |
</sections> |
11684 |
|
11685 |
|
11686 |
|
11687 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-bootloader.xml |
11688 |
|
11689 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-bootloader.xml?rev=1.1&view=markup |
11690 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-bootloader.xml?rev=1.1&content-type=text/plain |
11691 |
|
11692 |
Index: hb-install-ppc-bootloader.xml |
11693 |
=================================================================== |
11694 |
<?xml version='1.0' encoding='UTF-8'?> |
11695 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
11696 |
|
11697 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
11698 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
11699 |
|
11700 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-bootloader.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
11701 |
|
11702 |
<sections> |
11703 |
|
11704 |
<version>7.1</version> |
11705 |
<date>2006-11-13</date> |
11706 |
|
11707 |
<section> |
11708 |
<title>Choosing a Bootloader</title> |
11709 |
<subsection> |
11710 |
<title>Introduction</title> |
11711 |
<body> |
11712 |
|
11713 |
<p> |
11714 |
Now that the kernel is configured and compiled, you'll need a <e>bootloader</e> |
11715 |
to start your new linux installation. The <e>bootloader</e> that you use will |
11716 |
depend upon the type of PPC machine you have. |
11717 |
</p> |
11718 |
|
11719 |
<p> |
11720 |
If you are using a NewWorld Apple or IBM machine, you need to use |
11721 |
<uri link="#yaboot">yaboot</uri>. OldWorld Apple machines have two options, |
11722 |
<uri link="#bootx">BootX</uri> (recommended) and <uri link="#quik">quik</uri>. |
11723 |
The Pegasos does not require a bootloader, but you will need to emerge |
11724 |
<uri link="#bootcreator">BootCreator</uri> to create SmartFirmware bootmenus. |
11725 |
</p> |
11726 |
|
11727 |
</body> |
11728 |
</subsection> |
11729 |
</section> |
11730 |
<section id="yaboot"> |
11731 |
<title>Default: Using yaboot</title> |
11732 |
<subsection> |
11733 |
<title>Introduction</title> |
11734 |
<body> |
11735 |
|
11736 |
<impo> |
11737 |
yaboot can only be used on NewWorld Apple and IBM systems! |
11738 |
</impo> |
11739 |
|
11740 |
<p> |
11741 |
In order to find the boot devices, yaboot needs access to the device nodes |
11742 |
created by udev on startup and the sysfs filesystem. These two filesystems |
11743 |
are found at <path>/dev</path> and <path>sys</path> respectively. To do this, |
11744 |
you will need to "bind mount" these filesystems from the Installation CD's root |
11745 |
to the <path>/dev</path> and <path>/sys</path> mount points inside the chroot. |
11746 |
If you have already bind mounted these filesystems, there is no need to do it |
11747 |
again. |
11748 |
</p> |
11749 |
|
11750 |
<pre caption="Bind-mounting the device and sysfs filesystems"> |
11751 |
# <i>exit </i> # this will exit the chroot |
11752 |
# <i>mount -o bind /dev /mnt/gentoo/dev</i> |
11753 |
# <i>mount -o bind /sys /mnt/gentoo/sys</i> |
11754 |
# <i>chroot /mnt/gentoo /bin/bash</i> |
11755 |
# <i>/usr/sbin/env-update && source /etc/profile </i> |
11756 |
</pre> |
11757 |
|
11758 |
<p> |
11759 |
To set up yaboot, you can use <c>yabootconfig</c> to automatically create a |
11760 |
configuration file for you. If you are installing Gentoo on a G5 (where |
11761 |
<c>yabootconfig</c> does not always work), or you plan to boot from firewire |
11762 |
or USB, you will need to manually configure yaboot. |
11763 |
</p> |
11764 |
|
11765 |
<note> |
11766 |
You will need to manually edit the yaboot.conf when using genkernel, even if |
11767 |
yabootconfig is used. The kernel image section of yaboot.conf should be |
11768 |
modified as follows: |
11769 |
</note> |
11770 |
|
11771 |
<pre caption="Adding genkernel boot arguments to yaboot.conf"> |
11772 |
<comment>########################################################### |
11773 |
## This section can be duplicated if you have more than one |
11774 |
## kernel or set of boot options - replace kernel-name |
11775 |
## and initrd-name with the exact filename of your kernel |
11776 |
## and initrd image. |
11777 |
###########################################################</comment> |
11778 |
image=/boot/kernel-name |
11779 |
label=Linux |
11780 |
root=/dev/ram0 |
11781 |
partition=3 |
11782 |
initrd=/boot/initrd-name |
11783 |
append="real_root=/dev/hda3 init=/linuxrc" |
11784 |
<comment># You can add additional kernel arguments to append such as |
11785 |
# rootdelay=10 for a USB/Firewire Boot</comment> |
11786 |
read-only |
11787 |
<comment>##########################################################</comment> |
11788 |
</pre> |
11789 |
|
11790 |
<ul> |
11791 |
<li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li> |
11792 |
<li> |
11793 |
<uri link="#manual_yaboot">Alternative: Manual yaboot Configuration</uri> |
11794 |
</li> |
11795 |
</ul> |
11796 |
|
11797 |
</body> |
11798 |
</subsection> |
11799 |
<subsection id="yabootconfig"> |
11800 |
<title>Default: Using yabootconfig</title> |
11801 |
<body> |
11802 |
|
11803 |
<p> |
11804 |
<c>yabootconfig</c> will auto-detect the partitions on your machine and will |
11805 |
set up dual and triple boot combinations with Linux, Mac OS, and Mac OS X. |
11806 |
</p> |
11807 |
|
11808 |
<p> |
11809 |
To use <c>yabootconfig</c>, your drive must have an Apple_Bootstrap partition, |
11810 |
and <path>/etc/fstab</path> must be configured to reflect your Linux |
11811 |
partitions. These steps should have already been completed before, but check |
11812 |
<path>/etc/fstab</path> before proceeding. Now, ensure that you have |
11813 |
<c>yaboot</c> installed. |
11814 |
</p> |
11815 |
|
11816 |
<pre caption = "Installing yaboot with GRP"> |
11817 |
# <i>emerge --usepkg yaboot</i> |
11818 |
</pre> |
11819 |
|
11820 |
<p> |
11821 |
Now exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</c>. First, |
11822 |
the program will confirm the location of the bootstrap partition. If you are |
11823 |
using the suggested disk partitioning scheme, your bootstrap partition should |
11824 |
be /dev/hda2. Type <c>Y</c> if the output is correct. If not, double check your |
11825 |
<path>/etc/fstab</path>. <c>yabootconfig</c> will then scan your system setup, |
11826 |
create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you. |
11827 |
<c>mkofboot</c> is used to format the Apple_Bootstrap partition, and install |
11828 |
the yaboot configuration file into it. After this enter the chroot again. |
11829 |
</p> |
11830 |
|
11831 |
<pre caption="Re-enter the chroot"> |
11832 |
# <i>chroot /mnt/gentoo /bin/bash</i> |
11833 |
# <i>/usr/sbin/env-update && source /etc/profile</i> |
11834 |
</pre> |
11835 |
|
11836 |
<p> |
11837 |
You might want to verify the contents of <path>/etc/yaboot.conf</path>. If you |
11838 |
make changes to <path>/etc/yaboot.conf</path> (like setting the default/boot |
11839 |
OS), make sure to rerun <c>ybin -v</c> to apply changes to the Apple_Bootstrap |
11840 |
partition. |
11841 |
</p> |
11842 |
|
11843 |
<p> |
11844 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
11845 |
</p> |
11846 |
|
11847 |
</body> |
11848 |
</subsection> |
11849 |
<subsection id="manual_yaboot"> |
11850 |
<title>Alternative: Manual yaboot Configuration</title> |
11851 |
<body> |
11852 |
|
11853 |
<p> |
11854 |
First make sure you have <c>yaboot</c> installed on your system: |
11855 |
</p> |
11856 |
|
11857 |
<pre caption = "Installing yaboot with GRP"> |
11858 |
# <i>emerge --usepkg yaboot</i> |
11859 |
</pre> |
11860 |
|
11861 |
<p> |
11862 |
An example <path>yaboot.conf</path> file is given below, but you will need to |
11863 |
alter it to fit your needs. G5 users and users booting from firewire and USB |
11864 |
should be aware that their disks are seen as SCSI disks by the Linux kernel, so |
11865 |
you will need to substitute <path>/dev/hda</path> with <path>/dev/sda</path>). |
11866 |
</p> |
11867 |
|
11868 |
<pre caption = "/etc/yaboot.conf"> |
11869 |
<comment>## /etc/yaboot.conf |
11870 |
## |
11871 |
## run: "man yaboot.conf" for details. Do not make changes until you have!! |
11872 |
## see also: /usr/share/doc/yaboot/examples for example configurations. |
11873 |
## |
11874 |
## For a dual-boot menu, add one or more of: |
11875 |
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ |
11876 |
|
11877 |
## The bootstrap partition:</comment> |
11878 |
|
11879 |
boot=/dev/hda2 |
11880 |
|
11881 |
<comment>## ofboot is the openfirmware way to specify the bootstrap partition. |
11882 |
## If this isn't defined, yaboot fails on the G5 and some G4s (unless |
11883 |
## you pass the necessary arguments to the mkofboot/ybin program). |
11884 |
## hd:X means /dev/sdaX (or /dev/hdaX). |
11885 |
## |
11886 |
## G5 users should uncomment this line!! |
11887 |
|
11888 |
#ofboot=hd:2 |
11889 |
|
11890 |
## Users booting from firewire should use something like this line: |
11891 |
# ofboot=fw/node/sbp-2/disk@0: |
11892 |
|
11893 |
## Users booting from USB should use something like this line: |
11894 |
# ofboot=usb/disk@0: |
11895 |
|
11896 |
## hd: is shorthand for the first hard drive OpenFirmware sees</comment> |
11897 |
device=hd: |
11898 |
|
11899 |
<comment>## Firewire and USB users will need to specify the whole OF device name |
11900 |
## This can be found using ofpath, which is included with yaboot. |
11901 |
|
11902 |
# device=fw/node@0001d200e00d0207/sbp-2@c000/disk@0: |
11903 |
</comment> |
11904 |
|
11905 |
delay=5 |
11906 |
defaultos=macosx |
11907 |
timeout=30 |
11908 |
install=/usr/lib/yaboot/yaboot |
11909 |
magicboot=/usr/lib/yaboot/ofboot |
11910 |
|
11911 |
<comment>################# |
11912 |
## This section can be duplicated if you have more than one kernel or set of |
11913 |
## boot options - replace kernel-name with your kernel-version |
11914 |
#################</comment> |
11915 |
image=/boot/kernel-name |
11916 |
label=Linux |
11917 |
root=/dev/hda3 |
11918 |
partition=3 |
11919 |
<comment># append="rootdelay=10" # Required for booting USB/Firewire</comment> |
11920 |
read-only |
11921 |
<comment>################## |
11922 |
|
11923 |
## G5 users and some G4 users should set |
11924 |
## macos=hd:13 |
11925 |
## macosx=hd:12 |
11926 |
## instead of the example values.</comment> |
11927 |
macos=/dev/hda13 |
11928 |
macosx=/dev/hda12 |
11929 |
enablecdboot |
11930 |
enableofboot |
11931 |
</pre> |
11932 |
|
11933 |
<p> |
11934 |
Once <path>yaboot.conf</path> is configured, run <c>mkofboot -v</c> to format |
11935 |
the Apple_bootstrap partition and install the settings. If you change |
11936 |
yaboot.conf after the Apple_bootstrap partition has been created, you can |
11937 |
update the settings by running <c>ybin -v</c> |
11938 |
</p> |
11939 |
|
11940 |
<pre caption="Setting up the bootstrap partition"> |
11941 |
# <i>mkofboot -v</i> |
11942 |
</pre> |
11943 |
|
11944 |
<p> |
11945 |
For more information on yaboot, take a look at the <uri |
11946 |
link="http://penguinppc.org/bootloaders/yaboot">yaboot project</uri>. For |
11947 |
now, continue the installation with <uri link="#reboot">Rebooting the |
11948 |
System</uri>. |
11949 |
</p> |
11950 |
|
11951 |
</body> |
11952 |
</subsection> |
11953 |
</section> |
11954 |
<section id="bootx"> |
11955 |
<title>Alternative: BootX</title> |
11956 |
<body> |
11957 |
|
11958 |
<impo> |
11959 |
BootX can only be used on OldWorld Apple systems with MacOS 9 or earlier! |
11960 |
</impo> |
11961 |
|
11962 |
<p> |
11963 |
Since BootX boots Linux from within MacOS, the kernel will need to be copied |
11964 |
from the Linux Partition to the MacOS partition. First, mount the MacOS |
11965 |
partition from outside of the chroot. Use <c>mac-fdisk -l</c> to find the |
11966 |
MacOS partition number, sda6 is used as an example here. Once the partition is |
11967 |
mounted, we'll copy the kernel to the system folder so BootX can find it. |
11968 |
</p> |
11969 |
|
11970 |
<pre caption="Copying the kernel to the MacOS partition"> |
11971 |
# <i>exit</i> |
11972 |
cdimage ~# <i>mkdir /mnt/mac</i> |
11973 |
cdimage ~# <i>mount /dev/sda6 /mnt/mac -t hfs</i> |
11974 |
cdimage ~# <i>cp /mnt/gentoo/usr/src/linux/vmlinux "/mnt/mac/System Folder/Linux Kernels"</i> |
11975 |
</pre> |
11976 |
|
11977 |
<p> |
11978 |
If genkernel is used, both the kernel and initrd will need to be copied to the |
11979 |
MacOS partition. |
11980 |
</p> |
11981 |
|
11982 |
<pre caption="Copying the Genkernel kernel and initrd to the MacOS partition"> |
11983 |
# <i>exit</i> |
11984 |
cdimage ~# <i>mkdir /mnt/mac</i> |
11985 |
cdimage ~# <i>mount /dev/sda6 /mnt/mac -t hfs</i> |
11986 |
cdimage ~# <i>cp /mnt/gentoo/boot/kernel-* "/mnt/mac/System Folder/Linux Kernels"</i> |
11987 |
cdimage ~# <i>cp /mnt/gentoo/boot/initramfs-* "/mnt/mac/System Folder"</i> |
11988 |
</pre> |
11989 |
|
11990 |
<p> |
11991 |
Now that the kernel is copied over, we'll need to reboot to set up BootX. |
11992 |
</p> |
11993 |
|
11994 |
<pre caption="Unmounting all partitions and rebooting"> |
11995 |
cdimage ~# <i>cd /</i> |
11996 |
cdimage ~# <i>umount /mnt/gentoo/proc /mnt/gentoo/dev /mnt/gentoo/sys /mnt/gentoo /mnt/mac</i> |
11997 |
cdimage ~# <i>reboot</i> |
11998 |
</pre> |
11999 |
|
12000 |
<p> |
12001 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
12002 |
booted again instead of MacOS. |
12003 |
</p> |
12004 |
|
12005 |
<p> |
12006 |
Once the machine has booted into MacOS, open the BootX control panel. If you're |
12007 |
not using genkernel, select <c>Options</c> and uncheck <c>Use specified RAM |
12008 |
disk</c>. If you are using genkernel, ensure that the genkernel initrd is |
12009 |
selected instead of the Installation CD initrd. If not using genkernel, |
12010 |
there is now an option to specify the machine's Linux root disk and partition. |
12011 |
Fill these in with the appropriate values. Depending upon the kernel |
12012 |
configuration, additional boot arguments may need to be applied. |
12013 |
</p> |
12014 |
|
12015 |
<p> |
12016 |
BootX can be configured to start Linux upon boot. If you do this, you will first |
12017 |
see your machine boot into MacOS then, during startup, BootX will load and start |
12018 |
Linux. See the <uri link="http://penguinppc.org/bootloaders/bootx/">BootX home |
12019 |
page</uri> for more information. |
12020 |
</p> |
12021 |
|
12022 |
<impo> |
12023 |
Make sure that you have support for HFS and HFS+ filesystems in your kernel, |
12024 |
otherwise you will not be able to upgrade or change the kernel on your MacOS |
12025 |
partition. |
12026 |
</impo> |
12027 |
|
12028 |
<p> |
12029 |
Now reboot again and boot into Linux, then continue with <uri |
12030 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
12031 |
</p> |
12032 |
|
12033 |
</body> |
12034 |
</section> |
12035 |
<section id="quik"> |
12036 |
<title>Alternative: quik</title> |
12037 |
<body> |
12038 |
|
12039 |
<p> |
12040 |
quik allows OldWorld Macs to boot without MacOS. However, it isn't well |
12041 |
supported and has a number of quirks. If you have the option, it is recommended |
12042 |
that you use BootX instead since it is much more reliable and easier to set up |
12043 |
than quik. |
12044 |
</p> |
12045 |
|
12046 |
<p> |
12047 |
First, we'll need to install quik: |
12048 |
</p> |
12049 |
|
12050 |
<pre caption="Emerge quik"> |
12051 |
# <i>emerge quik</i> |
12052 |
</pre> |
12053 |
|
12054 |
<p> |
12055 |
Next, we'll need to set it up. Edit /etc/quik.conf and set your image to the |
12056 |
kernel that we copied to your boot partition. |
12057 |
</p> |
12058 |
|
12059 |
<pre caption="Configuring quik.conf"> |
12060 |
# Example of quik.conf |
12061 |
init-message = "Gentoo 2006.1\n" |
12062 |
partition = 2 <comment># This is the boot partition</comment> |
12063 |
root = /dev/hda4 |
12064 |
timeout = 30 |
12065 |
default = gentoo |
12066 |
image = /vmlinux <comment># This is your kernel</comment> |
12067 |
label = gentoo |
12068 |
</pre> |
12069 |
|
12070 |
<p> |
12071 |
Your quik.conf file <e>must</e> be on the same disk as the quik boot images, |
12072 |
however it can be on a different partition on the same disk, although it is |
12073 |
recommended to move it to your boot partition. |
12074 |
</p> |
12075 |
|
12076 |
<pre caption="Moving quik.conf to /boot"> |
12077 |
# <i>mv /etc/quik.conf /boot/quik.conf</i> |
12078 |
</pre> |
12079 |
|
12080 |
<p> |
12081 |
We will now set your boot variables so that quik loads on boot. To do this, |
12082 |
we'll use a program called <c>nvsetenv</c>. The variables that you want to |
12083 |
set vary from machine to machine, it's best to find your machine's |
12084 |
<uri link="http://penguinppc.org/bootloaders/quik/quirks.php">quirks</uri> |
12085 |
before attempting this. |
12086 |
</p> |
12087 |
|
12088 |
<pre caption="Setting the boot variables"> |
12089 |
# <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> |
12090 |
# <i>nvsetenv output-device video</i> <comment># Check the quirks page, there are many variations here</comment> |
12091 |
# <i>nvsetenv input-device kbd</i> |
12092 |
# <i>nvsetenv boot-device scsi/sd@1:0</i> <comment># For SCSI</comment> |
12093 |
# <i>nvsetenv boot-device ata/ata-disk@0:0</i> <comment># For ATA</comment> |
12094 |
# <i>nvsetenv boot-file /boot/vmlinux-2.6.17 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> |
12095 |
# <i>nvsetenv boot-command boot</i> <comment># Set this to bye for MacOS and boot for Linux</comment> |
12096 |
</pre> |
12097 |
|
12098 |
<note> |
12099 |
It is also possible to change your boot variables from MacOS. Depending |
12100 |
upon the model, either |
12101 |
<uri link="http://penguinppc.org/bootloaders/quik/BootVars.sit.hqx">bootvars</uri> or |
12102 |
<uri link="ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin"> |
12103 |
Apple System Disk</uri> should be used. Please see the quik quirks page |
12104 |
above for more information. |
12105 |
</note> |
12106 |
|
12107 |
<p> |
12108 |
Now that we've set up our machine to boot, we'll need to make sure the boot |
12109 |
images are installed correctly. Run <c>quik -v -C /boot/quik.conf</c>. It |
12110 |
should tell you that it has installed the first stage QUIK boot block. |
12111 |
</p> |
12112 |
|
12113 |
<note> |
12114 |
If something has gone wrong, you can always reset your PRAM back to the default |
12115 |
values by holding down <c>command + option + p + r</c> before powering on your |
12116 |
machine. This will clear the values you set with nvsetenv and should allow you |
12117 |
to boot either a MacOS bootdisk or a Linux bootdisk. |
12118 |
</note> |
12119 |
|
12120 |
<p> |
12121 |
Now, continue the installation with |
12122 |
<uri link="#reboot">Rebooting the System</uri>. |
12123 |
</p> |
12124 |
|
12125 |
</body> |
12126 |
</section> |
12127 |
<section id="bootcreator"> |
12128 |
<title>Alternative: BootCreator</title> |
12129 |
<body> |
12130 |
|
12131 |
<impo> |
12132 |
BootCreator will build a nice SmartFirmware bootmenu written in Forth for the |
12133 |
Pegasos. |
12134 |
</impo> |
12135 |
|
12136 |
<p> |
12137 |
First make sure you have <c>bootcreator</c> installed on your system: |
12138 |
</p> |
12139 |
|
12140 |
<pre caption = "Installing bootcreator"> |
12141 |
# <i>emerge --usepkg bootcreator</i> |
12142 |
</pre> |
12143 |
|
12144 |
<p> |
12145 |
Now copy the file <path>/etc/bootmenu.example</path> into |
12146 |
<path>/etc/bootmenu</path> and edit it to your needs: |
12147 |
</p> |
12148 |
|
12149 |
<pre caption = "Edit the bootcreator config file"> |
12150 |
# <i>cp /etc/bootmenu.example /etc/bootmenu</i> |
12151 |
# <i>nano -w /etc/bootmenu</i> |
12152 |
</pre> |
12153 |
|
12154 |
<p> |
12155 |
Below is a complete <path>/etc/bootmenu</path> config file. The kernel-name |
12156 |
and initrd-name should be replaced by your kernel and initrd image names. |
12157 |
</p> |
12158 |
|
12159 |
<pre caption = "bootcreator config file"> |
12160 |
<comment># |
12161 |
# Example description file for bootcreator 1.1 |
12162 |
#</comment> |
12163 |
|
12164 |
[VERSION] |
12165 |
1 |
12166 |
|
12167 |
[TITLE] |
12168 |
Boot Menu |
12169 |
|
12170 |
[SETTINGS] |
12171 |
AbortOnKey = false |
12172 |
Timeout = 9 |
12173 |
Default = 1 |
12174 |
|
12175 |
[SECTION] |
12176 |
Local HD -> Morphos (Normal) |
12177 |
ide:0 boot2.img ramdebug edebugflags="logkprintf" |
12178 |
|
12179 |
[SECTION] |
12180 |
Local HD -> Linux (Normal) |
12181 |
ide:0 kernel-name video=radeonfb:1024x768@70 root=/dev/hda3 |
12182 |
|
12183 |
[SECTION] |
12184 |
Local HD -> Genkernel (Normal) |
12185 |
ide:0 kernel-name root=/dev/ram0 real_root=/dev/hda3 init=/linuxrc initrd=initrd-name |
12186 |
</pre> |
12187 |
|
12188 |
<p> |
12189 |
Finally the <path>bootmenu</path> must be transfered into Forth and copied to |
12190 |
your boot partition, so that the SmartFirmware can read it. Therefore you have |
12191 |
to call <c>bootcreator</c>: |
12192 |
</p> |
12193 |
|
12194 |
<pre caption = "Install the bootmenu"> |
12195 |
# <i>bootcreator /etc/bootmenu /boot/menu</i> |
12196 |
</pre> |
12197 |
|
12198 |
<note> |
12199 |
Be sure to have a look into the SmartFirmware's settings when you reboot, that |
12200 |
<path>menu</path> is the file that will be loaded by default. |
12201 |
</note> |
12202 |
|
12203 |
<p> |
12204 |
For now, continue the installation with <uri link="#reboot">Rebooting the |
12205 |
System</uri>. |
12206 |
</p> |
12207 |
|
12208 |
</body> |
12209 |
</section> |
12210 |
<section id="reboot"> |
12211 |
<title>Rebooting the System</title> |
12212 |
<subsection> |
12213 |
<body> |
12214 |
|
12215 |
<p> |
12216 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
12217 |
that one magical command you have been waiting for: <c>reboot</c>. |
12218 |
</p> |
12219 |
|
12220 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
12221 |
# <i>exit</i> |
12222 |
livecd ~# <i>umount /mnt/gentoo/proc /mnt/gentoo/dev /mnt/gentoo/sys /mnt/gentoo</i> |
12223 |
livecd ~# <i>reboot</i> |
12224 |
</pre> |
12225 |
|
12226 |
<p> |
12227 |
Once rebooted in your Gentoo installation, finish up with <uri |
12228 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
12229 |
</p> |
12230 |
|
12231 |
</body> |
12232 |
</subsection> |
12233 |
</section> |
12234 |
</sections> |
12235 |
|
12236 |
|
12237 |
|
12238 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-disk.xml |
12239 |
|
12240 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-disk.xml?rev=1.1&view=markup |
12241 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-disk.xml?rev=1.1&content-type=text/plain |
12242 |
|
12243 |
Index: hb-install-ppc-disk.xml |
12244 |
=================================================================== |
12245 |
<?xml version='1.0' encoding='UTF-8'?> |
12246 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
12247 |
|
12248 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
12249 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
12250 |
|
12251 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-disk.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
12252 |
|
12253 |
<sections> |
12254 |
|
12255 |
<version>7.1</version> |
12256 |
<date>2006-11-02</date> |
12257 |
|
12258 |
<section> |
12259 |
<title>Introduction to Block Devices</title> |
12260 |
<subsection> |
12261 |
<title>Block Devices</title> |
12262 |
<body> |
12263 |
|
12264 |
<p> |
12265 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
12266 |
and Linux in general, including Linux filesystems, partitions and block devices. |
12267 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
12268 |
you'll be guided through the process of setting up partitions and filesystems |
12269 |
for your Gentoo Linux installation. |
12270 |
</p> |
12271 |
|
12272 |
<p> |
12273 |
To begin, we'll introduce <e>block devices</e>. The most common block device is |
12274 |
the one that represents the first IDE drive in a Linux system, namely |
12275 |
<path>/dev/hda</path>. If you are installing onto SCSI, FireWire, USB or SATA |
12276 |
drives, then your first hard drive would be <path>/dev/sda</path>. |
12277 |
</p> |
12278 |
|
12279 |
<p> |
12280 |
The block devices above represent an abstract interface to the disk. User |
12281 |
programs can use these block devices to interact with your disk without worrying |
12282 |
about whether your drives are IDE, SCSI or something else. The program can |
12283 |
simply address the storage on the disk as a bunch of contiguous, |
12284 |
randomly-accessible 512-byte blocks. |
12285 |
</p> |
12286 |
|
12287 |
</body> |
12288 |
</subsection> |
12289 |
<subsection> |
12290 |
<title>Partitions</title> |
12291 |
<body> |
12292 |
|
12293 |
<p> |
12294 |
Although it is theoretically possible to use a full disk to house your Linux |
12295 |
system, this is almost never done in practice. Instead, full disk block devices |
12296 |
are split up in smaller, more manageable block devices. On most systems, |
12297 |
these are called <e>partitions</e>. |
12298 |
</p> |
12299 |
|
12300 |
</body> |
12301 |
</subsection> |
12302 |
</section> |
12303 |
<section> |
12304 |
<title>Designing a Partitioning Scheme</title> |
12305 |
<subsection> |
12306 |
<title>Default Partitioning Scheme</title> |
12307 |
<body> |
12308 |
|
12309 |
<p> |
12310 |
If you are not interested in drawing up a partitioning scheme for your system, |
12311 |
you can use the partitioning scheme we use throughout this book: |
12312 |
</p> |
12313 |
|
12314 |
<note> |
12315 |
If you are using an OldWorld machine, you will need to keep MacOS available. |
12316 |
The layout here assumes MacOS is installed on a separate drive. |
12317 |
</note> |
12318 |
|
12319 |
<table> |
12320 |
<tr> |
12321 |
<th>Partition NewWorld</th> |
12322 |
<th>Partition OldWorld</th> |
12323 |
<th>Partition Pegasos</th> |
12324 |
<th>Partition RS/6000</th> |
12325 |
<th>Filesystem</th> |
12326 |
<th>Size</th> |
12327 |
<th>Description</th> |
12328 |
</tr> |
12329 |
<tr> |
12330 |
<ti><path>/dev/hda1</path></ti> |
12331 |
<ti><path>/dev/hda1</path></ti> |
12332 |
<ti>(Not applicable)</ti> |
12333 |
<ti>(Not applicable)</ti> |
12334 |
<ti>(Partition Map)</ti> |
12335 |
<ti>32k</ti> |
12336 |
<ti>Apple_partition_map</ti> |
12337 |
</tr> |
12338 |
<tr> |
12339 |
<ti><path>/dev/hda2</path></ti> |
12340 |
<ti>(Not needed)</ti> |
12341 |
<ti>(Not applicable)</ti> |
12342 |
<ti>(Not applicable)</ti> |
12343 |
<ti>(bootstrap)</ti> |
12344 |
<ti>800k</ti> |
12345 |
<ti>Apple_Bootstrap</ti> |
12346 |
</tr> |
12347 |
<tr> |
12348 |
<ti>(Not applicable)</ti> |
12349 |
<ti>(Not applicable)</ti> |
12350 |
<ti>(Not applicable)</ti> |
12351 |
<ti><path>/dev/sda1</path></ti> |
12352 |
<ti>(PReP Boot)</ti> |
12353 |
<ti>800k</ti> |
12354 |
<ti>Type 0x41</ti> |
12355 |
</tr> |
12356 |
<tr> |
12357 |
<ti>(Not applicable)</ti> |
12358 |
<ti><path>/dev/hda2</path> (If using quik)</ti> |
12359 |
<ti><path>/dev/hda1</path></ti> |
12360 |
<ti>(Not applicable)</ti> |
12361 |
<ti>ext2</ti> |
12362 |
<ti>32MB</ti> |
12363 |
<ti>Boot partition</ti> |
12364 |
</tr> |
12365 |
<tr> |
12366 |
<ti><path>/dev/hda3</path></ti> |
12367 |
<ti><path>/dev/hda2</path> (<path>/dev/hda3</path> if using quik)</ti> |
12368 |
<ti><path>/dev/hda2</path></ti> |
12369 |
<ti><path>/dev/sda2</path></ti> |
12370 |
<ti>(swap)</ti> |
12371 |
<ti>512M</ti> |
12372 |
<ti>Swap partition, Type 0x82</ti> |
12373 |
</tr> |
12374 |
<tr> |
12375 |
<ti><path>/dev/hda4</path></ti> |
12376 |
<ti><path>/dev/hda3</path> (<path>/dev/hda4</path> if using quik)</ti> |
12377 |
<ti><path>/dev/hda3</path></ti> |
12378 |
<ti><path>/dev/sda3</path></ti> |
12379 |
<ti>ext3, xfs</ti> |
12380 |
<ti>Rest of the disk</ti> |
12381 |
<ti>Root partition, Type 0x83</ti> |
12382 |
</tr> |
12383 |
</table> |
12384 |
|
12385 |
<note> |
12386 |
There are some partitions named: <path>Apple_Driver63, Apple_Driver_ATA, |
12387 |
Apple_FWDriver, Apple_Driver_IOKit, Apple_Patches</path>. If you are not |
12388 |
planning to use MacOS 9 you can delete them, because MacOS X and Linux don't |
12389 |
need them. To delete them, either use parted or erase the whole disk by |
12390 |
initializing the partition map. |
12391 |
</note> |
12392 |
|
12393 |
<warn> |
12394 |
<c>parted</c> is able to resize partitions including HFS+. Unfortunately it is |
12395 |
not possible to resize HFS+ journaled filesystems, so switch off journaling in |
12396 |
Mac OS X before resizing. Remember that any resizing operation is dangerous, |
12397 |
so attempt at your own risk! Be sure to always have a backup of your data |
12398 |
before resizing! |
12399 |
</warn> |
12400 |
|
12401 |
<p> |
12402 |
If you are interested in knowing how big a partition should be, or even how many |
12403 |
partitions you need, read on. Otherwise continue now with |
12404 |
<uri link="#mac-fdisk"> Default: Using mac-fdisk (Apple) to Partition your Disk |
12405 |
</uri> or <uri link="#parted">Alternative: Using parted (IBM/Pegasos) to |
12406 |
Partition your Disk</uri>. |
12407 |
</p> |
12408 |
|
12409 |
</body> |
12410 |
</subsection> |
12411 |
<subsection> |
12412 |
<title>How Many and How Big?</title> |
12413 |
<body> |
12414 |
|
12415 |
<p> |
12416 |
The number of partitions is highly dependent on your environment. For instance, |
12417 |
if you have lots of users, you will most likely want to have your |
12418 |
<path>/home</path> separate as it increases security and makes backups easier. |
12419 |
If you are installing Gentoo to perform as a mailserver, your <path>/var</path> |
12420 |
should be separate as all mails are stored inside <path>/var</path>. A good |
12421 |
choice of filesystem will then maximise your performance. Gameservers will have |
12422 |
a separate <path>/opt</path> as most gaming servers are installed there. The |
12423 |
reason is similar for <path>/home</path>: security and backups. You will |
12424 |
definitely want to keep <path>/usr</path> big: not only will it contain the |
12425 |
majority of applications, the Portage tree alone takes around 500 Mbyte |
12426 |
excluding the various sources that are stored in it. |
12427 |
</p> |
12428 |
|
12429 |
<p> |
12430 |
As you can see, it very much depends on what you want to achieve. Separate |
12431 |
partitions or volumes have the following advantages: |
12432 |
</p> |
12433 |
|
12434 |
<ul> |
12435 |
<li> |
12436 |
You can choose the best performing filesystem for each partition or volume |
12437 |
</li> |
12438 |
<li> |
12439 |
Your entire system cannot run out of free space if one defunct tool is |
12440 |
continuously writing files to a partition or volume |
12441 |
</li> |
12442 |
<li> |
12443 |
If necessary, file system checks are reduced in time, as multiple checks can |
12444 |
be done in parallel (although this advantage is more with multiple disks than |
12445 |
it is with multiple partitions) |
12446 |
</li> |
12447 |
<li> |
12448 |
Security can be enhanced by mounting some partitions or volumes read-only, |
12449 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
12450 |
</li> |
12451 |
</ul> |
12452 |
|
12453 |
<p> |
12454 |
However, multiple partitions have one big disadvantage: if not configured |
12455 |
properly, you might result in having a system with lots of free space on one |
12456 |
partition and none on another. There is also a 15-partition limit for SCSI and |
12457 |
SATA. |
12458 |
</p> |
12459 |
|
12460 |
</body> |
12461 |
</subsection> |
12462 |
</section> |
12463 |
<section id="mac-fdisk"> |
12464 |
<title>Default: Using mac-fdisk (Apple) Partition your Disk</title> |
12465 |
<body> |
12466 |
|
12467 |
<p> |
12468 |
At this point, create your partitions using <c>mac-fdisk</c>: |
12469 |
</p> |
12470 |
|
12471 |
<pre caption="Starting mac-fdisk"> |
12472 |
# <i>mac-fdisk /dev/hda</i> |
12473 |
</pre> |
12474 |
|
12475 |
<p> |
12476 |
First delete the partitions you have cleared previously to make room for your |
12477 |
Linux partitions. Use <c>d</c> in <c>mac-fdisk</c> to delete those partition(s). |
12478 |
It will ask for the partition number to delete. Usually the first partition on |
12479 |
NewWorld machines (Apple_partition_map) could not be deleted. |
12480 |
</p> |
12481 |
|
12482 |
<p> |
12483 |
Second, create an <e>Apple_Bootstrap</e> partition by using <c>b</c>. It will |
12484 |
ask for what block you want to start. Enter the number of your first free |
12485 |
partition, followed by a <c>p</c>. For instance this is <c>2p</c>. |
12486 |
</p> |
12487 |
|
12488 |
<note> |
12489 |
This partition is <e>not</e> a <path>/boot</path> partition. It is not used by |
12490 |
Linux at all; you don't have to place any filesystem on it and you should never |
12491 |
mount it. Apple users don't need an extra partition for <path>/boot</path>. |
12492 |
</note> |
12493 |
|
12494 |
<p> |
12495 |
Now create a swap partition by pressing <c>c</c>. Again <c>mac-fdisk</c> will |
12496 |
ask for what block you want to start this partition from. As we used <c>2</c> |
12497 |
before to create the Apple_Bootstrap partition, you now have to enter |
12498 |
<c>3p</c>. When you're asked for the size, enter <c>512M</c> (or whatever size |
12499 |
you want -- 512MB is recommended though). When asked for a name, enter <c>swap</c> |
12500 |
(mandatory). |
12501 |
</p> |
12502 |
|
12503 |
<p> |
12504 |
To create the root partition, enter <c>c</c>, followed by <c>4p</c> to select |
12505 |
from what block the root partition should start. When asked for the size, enter |
12506 |
<c>4p</c> again. <c>mac-fdisk</c> will interpret this as "Use all available |
12507 |
space". When asked for the name, enter <c>root</c> (mandatory). |
12508 |
</p> |
12509 |
|
12510 |
<p> |
12511 |
To finish up, write the partition to the disk using <c>w</c> and <c>q</c> to |
12512 |
quit <c>mac-fdisk</c>. |
12513 |
</p> |
12514 |
|
12515 |
<note> |
12516 |
To make sure everything is ok, you should run mac-fdisk once more and check |
12517 |
whether all the partitions are there. If you don't see any of the partitions |
12518 |
you created, or the changes you made, you should reinitialize your partitions |
12519 |
by pressing "i" in mac-fdisk. Note that this will recreate the partition map |
12520 |
and thus remove all your partitions. |
12521 |
</note> |
12522 |
|
12523 |
<p> |
12524 |
Now that your partitions are created, you can continue with <uri |
12525 |
link="#filesystems">Creating Filesystems</uri>. |
12526 |
</p> |
12527 |
|
12528 |
</body> |
12529 |
</section> |
12530 |
<section id="parted"> |
12531 |
<title>Using parted (especially Pegasos) to Partition your Disk</title> |
12532 |
<body> |
12533 |
|
12534 |
<p> |
12535 |
<c>parted</c>, the Partition Editor, can now handle HFS+ partitions used by |
12536 |
Mac OS and Mac OS X. With this tool you can resize your Mac-partitions and |
12537 |
create space for your Linux partitions. Nevertheless, the example below |
12538 |
describes partitioning for Pegasos machines only. |
12539 |
</p> |
12540 |
|
12541 |
<p> |
12542 |
To begin let's fire up <c>parted</c>: |
12543 |
</p> |
12544 |
|
12545 |
<pre caption="Starting parted"> |
12546 |
# <i>parted /dev/hda</i> |
12547 |
</pre> |
12548 |
|
12549 |
<p> |
12550 |
If the drive is unpartitioned, run <c>mklabel amiga</c> to create a new |
12551 |
disklabel for the drive. |
12552 |
</p> |
12553 |
|
12554 |
<p> |
12555 |
You can type <c>print</c> at any time in parted to display the current partition |
12556 |
table. If at any time you change your mind or made a mistake you can press |
12557 |
<c>Ctrl-c</c> to abort parted. |
12558 |
</p> |
12559 |
|
12560 |
<p> |
12561 |
If you intend to also install MorphOS on your Pegasos create an affs1 filesystem |
12562 |
named "BI0" (BI zero) at the start of the drive. 32MB should be more than enough |
12563 |
to store the MorphOS kernel. If you have a Pegasos I or intend to use reiserfs or |
12564 |
xfs, you will also have to store your Linux kernel on this partition (the |
12565 |
Pegasos II can only boot from ext2/ext3 or affs1 partitions). To create the partition run |
12566 |
<c>mkpart primary affs1 START END</c> where <c>START</c> and <c>END</c> should |
12567 |
be replaced with the megabyte range (e.g. <c>0 32</c> creates a 32 MB partition |
12568 |
starting at 0MB and ending at 32MB. |
12569 |
</p> |
12570 |
|
12571 |
<p> |
12572 |
You need to create two partitions for Linux, one root filesystem for all your |
12573 |
program files etc, and one swap partition. To create the root filesystem you |
12574 |
must first decide which filesystem to use. Possible options are ext2, ext3, |
12575 |
reiserfs and xfs. Unless you know what you are doing, use ext3. Run |
12576 |
<c>mkpart primary ext3 START END</c> to create an ext3 partition. Again, replace |
12577 |
<c>START</c> and <c>END</c> with the megabyte start and stop marks for the |
12578 |
partition. |
12579 |
</p> |
12580 |
|
12581 |
<p> |
12582 |
It is generally recommended that you create a swap partition the same size as |
12583 |
the amount of RAM in your computer times two. You will probably get away with a |
12584 |
smaller swap partition unless you intend to run a lot of applications at the |
12585 |
same time (although at least 512MB is recommended). To create the swap |
12586 |
partition, run <c>mkpart primary linux-swap START END</c>. |
12587 |
</p> |
12588 |
|
12589 |
<p> |
12590 |
Write down the partition minor numbers as they are required during the |
12591 |
installation process. To display the minor numbers run <c>print</c>. Your drives |
12592 |
are accessed as <path>/dev/hdaX</path> where X is replaced with the minor number |
12593 |
of the partition. |
12594 |
</p> |
12595 |
|
12596 |
<p> |
12597 |
When you are done in parted simply run <c>quit</c>. |
12598 |
</p> |
12599 |
|
12600 |
</body> |
12601 |
</section> |
12602 |
<section id="filesystems"> |
12603 |
<title>Creating Filesystems</title> |
12604 |
<subsection> |
12605 |
<title>Introduction</title> |
12606 |
<body> |
12607 |
|
12608 |
<p> |
12609 |
Now that your partitions are created, it is time to place a filesystem on them. |
12610 |
If you don't care about what filesystem to choose and are happy with what we use |
12611 |
as default in this handbook, continue with <uri |
12612 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
12613 |
Otherwise read on to learn about the available filesystems... |
12614 |
</p> |
12615 |
|
12616 |
</body> |
12617 |
</subsection> |
12618 |
<subsection> |
12619 |
<title>Filesystems?</title> |
12620 |
<body> |
12621 |
|
12622 |
<p> |
12623 |
Several filesystems are available. ext2, ext3, ReiserFS and XFS have been found |
12624 |
stable on the PPC architecture. |
12625 |
</p> |
12626 |
|
12627 |
<p> |
12628 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
12629 |
journaling, which means that routine ext2 filesystem checks at startup time can |
12630 |
be quite time-consuming. There is now quite a selection of newer-generation |
12631 |
journaled filesystems that can be checked for consistency very quickly and are |
12632 |
thus generally preferred over their non-journaled counterparts. Journaled |
12633 |
filesystems prevent long delays when you boot your system and your filesystem |
12634 |
happens to be in an inconsistent state. |
12635 |
</p> |
12636 |
|
12637 |
<p> |
12638 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
12639 |
journaling for fast recovery in addition to other enhanced journaling modes |
12640 |
like full data and ordered data journaling. It uses a hashed B*-tree index that |
12641 |
enables high performance in almost all situations. In short, ext3 is a very |
12642 |
good and reliable filesystem. |
12643 |
</p> |
12644 |
|
12645 |
<p> |
12646 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
12647 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
12648 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
12649 |
extremely well and has metadata journaling. ReiserFS is solid and usable as |
12650 |
both general-purpose filesystem and for extreme cases such as the creation of |
12651 |
large filesystems, very large files and directories containing tens of |
12652 |
thousands of small files. |
12653 |
</p> |
12654 |
|
12655 |
<p> |
12656 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
12657 |
feature-set and is optimized for scalability. We only recommend using this |
12658 |
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
12659 |
an uninterruptible power supply. Because XFS aggressively caches in-transit data |
12660 |
in RAM, improperly designed programs (those that don't take proper precautions |
12661 |
when writing files to disk and there are quite a few of them) can lose a good |
12662 |
deal of data if the system goes down unexpectedly. |
12663 |
</p> |
12664 |
|
12665 |
</body> |
12666 |
</subsection> |
12667 |
<subsection id="filesystems-apply"> |
12668 |
<title>Applying a Filesystem to a Partition</title> |
12669 |
<body> |
12670 |
|
12671 |
<p> |
12672 |
To create a filesystem on a partition or volume, there are tools available for |
12673 |
each possible filesystem: |
12674 |
</p> |
12675 |
|
12676 |
<table> |
12677 |
<tr> |
12678 |
<th>Filesystem</th> |
12679 |
<th>Creation Command</th> |
12680 |
</tr> |
12681 |
<tr> |
12682 |
<ti>ext2</ti> |
12683 |
<ti><c>mkfs.ext2</c></ti> |
12684 |
</tr> |
12685 |
<tr> |
12686 |
<ti>ext3</ti> |
12687 |
<ti><c>mkfs.ext3</c></ti> |
12688 |
</tr> |
12689 |
<tr> |
12690 |
<ti>reiserfs</ti> |
12691 |
<ti><c>mkfs.reiserfs</c></ti> |
12692 |
</tr> |
12693 |
<tr> |
12694 |
<ti>xfs</ti> |
12695 |
<ti><c>mkfs.xfs</c></ti> |
12696 |
</tr> |
12697 |
</table> |
12698 |
|
12699 |
<p> |
12700 |
For instance, to have the root partition (<path>/dev/hda4</path> in our example) |
12701 |
in ext3 (as in our example), you would use: |
12702 |
</p> |
12703 |
|
12704 |
<pre caption="Applying a filesystem on a partition"> |
12705 |
# <i>mkfs.ext3 /dev/hda4</i> |
12706 |
</pre> |
12707 |
|
12708 |
<p> |
12709 |
Now create the filesystems on your newly created partitions (or logical |
12710 |
volumes). |
12711 |
</p> |
12712 |
|
12713 |
<note> |
12714 |
On the PegasosII your partition which holds the kernel must be ext2/ext3 or |
12715 |
affs1. NewWorld machines can boot from any of ext2, ext3, XFS, ReiserFS or |
12716 |
even HFS/HFS+ filesystems. On OldWorld machines booting with BootX, the kernel |
12717 |
must be placed on an HFS partition, but this will be completed when you |
12718 |
configure your bootloader. |
12719 |
</note> |
12720 |
|
12721 |
</body> |
12722 |
</subsection> |
12723 |
<subsection> |
12724 |
<title>Activating the Swap Partition</title> |
12725 |
<body> |
12726 |
|
12727 |
<p> |
12728 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
12729 |
</p> |
12730 |
|
12731 |
<pre caption="Creating a Swap signature"> |
12732 |
# <i>mkswap /dev/hda3</i> |
12733 |
</pre> |
12734 |
|
12735 |
<p> |
12736 |
To activate the swap partition, use <c>swapon</c>: |
12737 |
</p> |
12738 |
|
12739 |
<pre caption="Activating the swap partition"> |
12740 |
# <i>swapon /dev/hda3</i> |
12741 |
</pre> |
12742 |
|
12743 |
<p> |
12744 |
Create and activate the swap now. |
12745 |
</p> |
12746 |
|
12747 |
</body> |
12748 |
</subsection> |
12749 |
</section> |
12750 |
<section> |
12751 |
<title>Mounting</title> |
12752 |
<body> |
12753 |
|
12754 |
<p> |
12755 |
Now that your partitions are initialized and are housing a filesystem, it is |
12756 |
time to mount those partitions. Use the <c>mount</c> command. As an example we |
12757 |
mount the root partition: |
12758 |
</p> |
12759 |
|
12760 |
<pre caption="Mounting partitions"> |
12761 |
# <i>mount /dev/hda4 /mnt/gentoo</i> |
12762 |
</pre> |
12763 |
|
12764 |
<note> |
12765 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
12766 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
12767 |
also holds for <path>/var/tmp</path>. |
12768 |
</note> |
12769 |
|
12770 |
<p> |
12771 |
We will have to mount the proc filesystem (a virtual interface with the |
12772 |
kernel) on <path>/proc</path>. But first we will need to place our files on the |
12773 |
partitions. |
12774 |
</p> |
12775 |
|
12776 |
<p> |
12777 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
12778 |
Installation Files</uri>. |
12779 |
</p> |
12780 |
|
12781 |
</body> |
12782 |
</section> |
12783 |
</sections> |
12784 |
|
12785 |
|
12786 |
|
12787 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-kernel.xml |
12788 |
|
12789 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-kernel.xml?rev=1.1&view=markup |
12790 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-kernel.xml?rev=1.1&content-type=text/plain |
12791 |
|
12792 |
Index: hb-install-ppc-kernel.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.0/hb-install-ppc-kernel.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
12801 |
|
12802 |
<sections> |
12803 |
|
12804 |
<version>7.5</version> |
12805 |
<date>2007-03-12</date> |
12806 |
|
12807 |
<section> |
12808 |
<title>Timezone</title> |
12809 |
<body> |
12810 |
|
12811 |
<p> |
12812 |
You first need to select your timezone so that your system knows where it is |
12813 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
12814 |
it to <path>/etc/localtime</path>. Please avoid the |
12815 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
12816 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
12817 |
</p> |
12818 |
|
12819 |
<pre caption="Setting the timezone information"> |
12820 |
# <i>ls /usr/share/zoneinfo</i> |
12821 |
<comment>(Suppose you want to use GMT)</comment> |
12822 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
12823 |
</pre> |
12824 |
|
12825 |
</body> |
12826 |
</section> |
12827 |
<section> |
12828 |
<title>Installing the Sources</title> |
12829 |
<subsection> |
12830 |
<title>Choosing a Kernel</title> |
12831 |
<body> |
12832 |
|
12833 |
<p> |
12834 |
The core around which all distributions are built is the Linux kernel. It is the |
12835 |
layer between the user programs and your system hardware. Gentoo provides its |
12836 |
users several possible kernel sources. A full listing with description is |
12837 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
12838 |
Guide</uri>. |
12839 |
</p> |
12840 |
|
12841 |
<p> |
12842 |
We suggest using <c>gentoo-sources</c> on PPC, which is a 2.6 kernel. |
12843 |
</p> |
12844 |
|
12845 |
<pre caption="Installing a kernel source"> |
12846 |
# <i>emerge gentoo-sources</i> |
12847 |
</pre> |
12848 |
|
12849 |
<p> |
12850 |
If you take a look in <path>/usr/src</path> you should see a symlink named |
12851 |
<path>linux</path> pointing to your current kernel source. In this case, the |
12852 |
installed kernel source points to <c>gentoo-sources-2.6.15</c>. Your version |
12853 |
may be different, so keep this in mind. |
12854 |
</p> |
12855 |
|
12856 |
<pre caption="Viewing the kernel source symlink"> |
12857 |
# <i>ls -l /usr/src/linux</i> |
12858 |
lrwxrwxrwx 1 root root 22 Mar 18 16:23 /usr/src/linux -> linux-2.6.15 |
12859 |
</pre> |
12860 |
|
12861 |
<p> |
12862 |
Now it is time to configure and compile your kernel source. You |
12863 |
can use <c>genkernel</c> for this, which will build a generic kernel as used |
12864 |
by the Installation CD. We explain the "manual" configuration first though, as |
12865 |
it is the best way to optimize your environment. |
12866 |
</p> |
12867 |
|
12868 |
<p> |
12869 |
If you want to manually configure your kernel, continue now with <uri |
12870 |
link="#manual">Default: Manual Configuration</uri>. If you want to use |
12871 |
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
12872 |
genkernel</uri> instead. |
12873 |
</p> |
12874 |
|
12875 |
</body> |
12876 |
</subsection> |
12877 |
</section> |
12878 |
<section id="manual"> |
12879 |
<title>Default: Manual Configuration</title> |
12880 |
<subsection> |
12881 |
<title>Introduction</title> |
12882 |
<body> |
12883 |
|
12884 |
<p> |
12885 |
Manually configuring a kernel is often seen as the most difficult procedure a |
12886 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
12887 |
couple of kernels you don't even remember that it was difficult ;) |
12888 |
</p> |
12889 |
|
12890 |
<p> |
12891 |
However, one thing <e>is</e> true: you must know your system when you start |
12892 |
configuring a kernel manually. Most information can be gathered by emerging |
12893 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
12894 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
12895 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
12896 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
12897 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
12898 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
12899 |
uses (it might provide you with a nice hint on what to enable). Another place |
12900 |
to look for clues as to what components to enable is to check the kernel |
12901 |
message logs from the successful boot that got you this far. Type <c>dmesg</c> |
12902 |
to see the kernel messages. |
12903 |
</p> |
12904 |
|
12905 |
<p> |
12906 |
Now, go to your kernel source directory, it's time to configure your kernel. |
12907 |
It is recommended that you add the default settings to your configuration by |
12908 |
first running <c>make pmac32_defconfig</c>. After the default configuration has |
12909 |
been generated, run <c>make menuconfig</c> which will fire up an ncurses-based |
12910 |
configuration menu. |
12911 |
</p> |
12912 |
|
12913 |
<pre caption="Invoking menuconfig"> |
12914 |
# <i>cd /usr/src/linux</i> |
12915 |
# <i>make pmac32_defconfig</i> |
12916 |
# <i>make menuconfig</i> |
12917 |
</pre> |
12918 |
|
12919 |
<p> |
12920 |
You will be greeted with several configuration sections. We'll first list some |
12921 |
options you must activate (otherwise Gentoo will not function, or not function |
12922 |
properly without additional tweaks). |
12923 |
</p> |
12924 |
|
12925 |
</body> |
12926 |
</subsection> |
12927 |
<subsection> |
12928 |
<title>Activating Required Options</title> |
12929 |
<body> |
12930 |
|
12931 |
<p> |
12932 |
First of all, activate the use of development and experimental code/drivers. |
12933 |
You need this, otherwise some very important code/drivers won't show up: |
12934 |
</p> |
12935 |
|
12936 |
<pre caption="Selecting experimental code/drivers"> |
12937 |
Code maturity level options ---> |
12938 |
[*] Prompt for development and/or incomplete code/drivers |
12939 |
</pre> |
12940 |
|
12941 |
<p> |
12942 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
12943 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
12944 |
able to mount your partitions. Also select the <c>/proc file system</c> and |
12945 |
<c>Virtual memory</c>. Make sure that you also enable support for Amiga |
12946 |
partitions if you are using a Pegasos, or Macintosh partitions if you are using |
12947 |
an Apple computer. |
12948 |
</p> |
12949 |
|
12950 |
<pre caption="Selecting necessary file systems"> |
12951 |
File systems ---> |
12952 |
Pseudo Filesystems ---> |
12953 |
[*] /proc file system support |
12954 |
[*] Virtual memory file system support (former shm fs) |
12955 |
Partition Types ---> |
12956 |
[*] Amiga partition table support |
12957 |
[*] Macintosh partition map support |
12958 |
|
12959 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
12960 |
<*> Reiserfs support |
12961 |
<*> Ext3 journalling file system support |
12962 |
<*> Second extended fs support |
12963 |
<*> XFS filesystem support |
12964 |
</pre> |
12965 |
|
12966 |
<p> |
12967 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
12968 |
modem, you will need the following options in the kernel: |
12969 |
</p> |
12970 |
|
12971 |
<pre caption="Selecting PPPoE necessary drivers"> |
12972 |
Device Drivers ---> |
12973 |
Networking support ---> |
12974 |
<*> PPP (point-to-point protocol) support |
12975 |
<*> PPP support for async serial ports |
12976 |
<*> PPP support for sync tty ports |
12977 |
</pre> |
12978 |
|
12979 |
<p> |
12980 |
The two compression options won't harm but are not definitely needed, neither |
12981 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
12982 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
12983 |
</p> |
12984 |
|
12985 |
<p> |
12986 |
If you require it, don't forget to include support in the kernel for your |
12987 |
ethernet card. |
12988 |
</p> |
12989 |
|
12990 |
<p> |
12991 |
Users of NewWorld and OldWorld machines will want HFS support as well. OldWorld |
12992 |
users require it for copying compiled kernels to the MacOS partition. NewWorld |
12993 |
users require it for configuring the special Apple_Bootstrap partition: |
12994 |
</p> |
12995 |
|
12996 |
<pre caption="Activating HFS support"> |
12997 |
File Systems ---> |
12998 |
[*] HFS Support |
12999 |
</pre> |
13000 |
|
13001 |
<p> |
13002 |
At this time, kernel preemption is still unstable on PPC and may cause |
13003 |
compilation failures and random segfaults. It is <e>strongly</e> suggested |
13004 |
that you do not use this feature. |
13005 |
</p> |
13006 |
|
13007 |
<pre caption="Ensure the Preemptible Kernel Option is Off"> |
13008 |
Kernel options ---> |
13009 |
Preemption Model (No Forced Preemption (Server)) |
13010 |
</pre> |
13011 |
|
13012 |
<p> |
13013 |
If you're booting from Firewire, you'll need to enable these options. If you do |
13014 |
not want to compile in support, you'll need to include these modules and their |
13015 |
dependencies in an initrd. |
13016 |
</p> |
13017 |
|
13018 |
<pre caption="Enable support for firewire devices on boot"> |
13019 |
Device Drivers ---> |
13020 |
IEEE 1394 (FireWire) support ---> |
13021 |
<*> IEEE 1394 (FireWire) support |
13022 |
<*> OHCI-1394 support |
13023 |
<*> SBP-2 support (Harddisks etc.) |
13024 |
</pre> |
13025 |
|
13026 |
<p> |
13027 |
If you're booting from USB, you'll need to enable these options. If you do not |
13028 |
want to compile in support, you'll need to include these modules and their |
13029 |
dependencies in an initrd. |
13030 |
</p> |
13031 |
|
13032 |
<pre caption="Enable support for USB devices on boot"> |
13033 |
Device Drivers ---> |
13034 |
USB support ---> |
13035 |
<*> Support for Host-side USB |
13036 |
<*> OHCI HCD support |
13037 |
<*> USB Mass Storage support |
13038 |
</pre> |
13039 |
|
13040 |
<p> |
13041 |
Do not turn off kernel framebuffer support as it is required for a successful |
13042 |
boot. If you are using an NVIDIA based chipset, you should use the OpenFirmware |
13043 |
framebuffer. If you are using an ATI based chipset, you should select the |
13044 |
framebuffer driver based upon your chipset (Mach64, Rage128 or Radeon). |
13045 |
</p> |
13046 |
|
13047 |
<pre caption="Chosing a Framebuffer Driver"> |
13048 |
Device Drivers ---> |
13049 |
Graphics support ---> |
13050 |
<*> Support for frame buffer devices |
13051 |
[*] Open Firmware frame buffer device support |
13052 |
<*> ATI Radeon display support |
13053 |
<*> ATI Rage128 display support |
13054 |
<*> ATI Mach64 display support |
13055 |
Console display driver support ---> |
13056 |
<*> Framebuffer Console support |
13057 |
</pre> |
13058 |
|
13059 |
<note> |
13060 |
If you select more than one framebuffer device, it may default to a less than |
13061 |
optimal driver. Either use only one framebuffer device or specify which |
13062 |
to use by passing the driver to use to the kernel on boot such as |
13063 |
<c>video=radeonfb</c>. |
13064 |
</note> |
13065 |
|
13066 |
<p> |
13067 |
When you're done configuring your kernel, continue with <uri |
13068 |
link="#compiling">Compiling and Installing</uri>. |
13069 |
</p> |
13070 |
|
13071 |
</body> |
13072 |
</subsection> |
13073 |
<subsection id="compiling"> |
13074 |
<title>Compiling and Installing</title> |
13075 |
<body> |
13076 |
|
13077 |
<p> |
13078 |
Now that your kernel is configured, it is time to compile and install it. Exit |
13079 |
the configuration and run the commands which will compile the kernel: |
13080 |
</p> |
13081 |
|
13082 |
<pre caption="Compiling the kernel"> |
13083 |
# <i>make && make modules_install</i> |
13084 |
</pre> |
13085 |
|
13086 |
<p> |
13087 |
When the kernel has finished compiling, copy the kernel image to |
13088 |
<path>/boot</path> (be sure that it is mounted properly on Pegasos computers). |
13089 |
If you are using BootX to boot, we'll copy the kernel later. |
13090 |
</p> |
13091 |
|
13092 |
<p> |
13093 |
Yaboot and BootX expect to use an uncompressed kernel unlike many other |
13094 |
bootloaders. The uncompressed kernel is called vmlinux and it is placed in |
13095 |
<path>/usr/src/linux</path> after the kernel has finished compiling. If you |
13096 |
are using a Pegasos machine, the Pegasos firmware requires a compressed |
13097 |
kernel called zImage.chrp which can be found in |
13098 |
<path>/usr/src/linux/arch/ppc/boot/images</path>. |
13099 |
</p> |
13100 |
|
13101 |
<pre caption="Installing the kernel"> |
13102 |
# <i>cd /usr/src/linux</i> |
13103 |
<comment>replace <kernel-version> with your kernel version</comment> |
13104 |
<comment>(Apple/IBM)</comment> |
13105 |
# <i>cp vmlinux /boot/<kernel-version></i> |
13106 |
<comment>(Pegasos)</comment> |
13107 |
# <i>cp arch/ppc/boot/images/zImage.chrp /boot/<kernel-version></i> |
13108 |
</pre> |
13109 |
|
13110 |
<p> |
13111 |
Now continue with <uri link="#kernel_modules">Installing Separate Kernel |
13112 |
Modules</uri>. |
13113 |
</p> |
13114 |
|
13115 |
</body> |
13116 |
</subsection> |
13117 |
</section> |
13118 |
<section id="kernel_modules"> |
13119 |
<title>Installing Separate Kernel Modules</title> |
13120 |
<subsection> |
13121 |
<title>Configuring the Modules</title> |
13122 |
<body> |
13123 |
|
13124 |
<p> |
13125 |
You should list the modules you want automatically loaded in |
13126 |
<path>/etc/modules.autoload.d/kernel-2.6</path>. |
13127 |
You can add extra options to the modules too if you want. |
13128 |
</p> |
13129 |
|
13130 |
<p> |
13131 |
To view all available modules, run the following <c>find</c> command. Don't |
13132 |
forget to substitute "<kernel version>" with the version of the kernel you |
13133 |
just compiled: |
13134 |
</p> |
13135 |
|
13136 |
<pre caption="Viewing all available modules"> |
13137 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
13138 |
</pre> |
13139 |
|
13140 |
<p> |
13141 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
13142 |
<path>kernel-2.6</path> file and enter the module |
13143 |
name in it. |
13144 |
</p> |
13145 |
|
13146 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
13147 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
13148 |
</pre> |
13149 |
|
13150 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
13151 |
3c59x |
13152 |
</pre> |
13153 |
|
13154 |
<p> |
13155 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
13156 |
your System</uri>. |
13157 |
</p> |
13158 |
|
13159 |
</body> |
13160 |
</subsection> |
13161 |
</section> |
13162 |
<section id="genkernel"> |
13163 |
<title>Alternative: Using genkernel</title> |
13164 |
<body> |
13165 |
|
13166 |
<p> |
13167 |
If you are reading this section, you have chosen to use our <c>genkernel</c> |
13168 |
script to configure your kernel for you. |
13169 |
</p> |
13170 |
|
13171 |
<p> |
13172 |
Now that your kernel source tree is installed, it's now time to compile your |
13173 |
kernel by using our <c>genkernel</c> script to automatically build a kernel for |
13174 |
you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
13175 |
way our Installation CD kernel is configured. This means that when you use |
13176 |
<c>genkernel</c> to build your kernel, your system will generally detect all |
13177 |
your hardware at boot-time, just like our Installation CD does. Because genkernel |
13178 |
doesn't require any manual kernel configuration, it is an ideal solution for |
13179 |
those users who may not be comfortable compiling their own kernels. |
13180 |
</p> |
13181 |
|
13182 |
<p> |
13183 |
Now, let's see how to use genkernel. First, emerge the genkernel ebuild: |
13184 |
</p> |
13185 |
|
13186 |
<pre caption="Emerging genkernel"> |
13187 |
# <i>emerge genkernel</i> |
13188 |
</pre> |
13189 |
|
13190 |
<p> |
13191 |
Next, copy over the kernel configuration used by the Installation CD to the |
13192 |
location where genkernel looks for the default kernel configuration: |
13193 |
</p> |
13194 |
|
13195 |
<pre caption="Copying over the Installation CD kernel config"> |
13196 |
# <i>zcat /proc/config.gz > /usr/share/genkernel/ppc/kernel-config-2.6</i> |
13197 |
</pre> |
13198 |
|
13199 |
<p> |
13200 |
If you are using firewire or USB to boot, you'll need to add modules to the |
13201 |
initrd. Edit <path>/usr/share/genkernel/ppc/modules_load</path> and change |
13202 |
<c>MODULES_FIREWIRE="ieee1394 ohci1394 sbp2"</c> for firewire support or |
13203 |
<c>MODULES_USB="usbcore ohci-hcd ehci-hcd usb-storage"</c> for USB support. |
13204 |
</p> |
13205 |
|
13206 |
<p> |
13207 |
Before compiling your sources, the fstab needs a slight adjustment. The rest of |
13208 |
the fstab will be completed during a later step, so don't worry about the |
13209 |
details now. If you did not create a separate boot partition (NOT bootstrap, |
13210 |
that's different), remove the line referencing /boot from |
13211 |
<path>/etc/fstab</path>. This will need to be done on most Apple computers. |
13212 |
</p> |
13213 |
|
13214 |
<pre caption="Removing /boot from /etc/fstab on machines without a boot partition"> |
13215 |
# <i>nano -w /etc/fstab</i> |
13216 |
<comment>Remove this line</comment> |
13217 |
/dev/BOOT /boot ext2 noauto,noatime 1 2 |
13218 |
</pre> |
13219 |
|
13220 |
<p> |
13221 |
Now, compile your kernel sources by running <c>genkernel --genzimage all</c>. |
13222 |
For Pegasos, we will need to use a different config and create a zImage instead |
13223 |
of the vmlinux kernel used on Apple machines. Be aware, as <c>genkernel</c> |
13224 |
compiles a kernel that supports almost all hardware, this compilation can take |
13225 |
quite a while to finish! |
13226 |
</p> |
13227 |
|
13228 |
<p> |
13229 |
Note that, if your partition where the kernel should be located doesn't use ext2 |
13230 |
or ext3 as filesystem you might need to manually configure your kernel using |
13231 |
<c>genkernel --menuconfig all</c> and add support for your |
13232 |
filesystem <e>in</e> the kernel (i.e. <e>not</e> as a module). Users of EVMS2 or |
13233 |
LVM2 will probably want to add <c>--evms2</c> or <c>--lvm2</c> as arguments as |
13234 |
well. |
13235 |
</p> |
13236 |
|
13237 |
<pre caption="Running genkernel"> |
13238 |
# <i>genkernel all</i> |
13239 |
</pre> |
13240 |
|
13241 |
<pre caption="Running genkernel on the Pegasos"> |
13242 |
# <i>genkernel --genzimage --kernel-config=/usr/share/genkernel/ppc/Pegasos all</i> |
13243 |
</pre> |
13244 |
|
13245 |
<p> |
13246 |
Once <c>genkernel</c> completes, a kernel, full set of modules and |
13247 |
<e>initial root disk</e> (initrd) will be created. We will use the kernel |
13248 |
and initrd when configuring a boot loader later in this document. Write |
13249 |
down the names of the kernel and initrd as you will need it when writing |
13250 |
the bootloader configuration file. The initrd will be started immediately after |
13251 |
booting to perform hardware autodetection (just like on the Installation CD) |
13252 |
before your "real" system starts up. Be sure to also copy down the required |
13253 |
boot arguments, these are required for a successful boot with genkernel. |
13254 |
</p> |
13255 |
|
13256 |
<pre caption="Checking the created kernel image name and initrd"> |
13257 |
# <i>ls /boot/kernel* /boot/initramfs*</i> |
13258 |
</pre> |
13259 |
|
13260 |
<p> |
13261 |
If you want your system to react to hotplugging events, you will need to install |
13262 |
and setup <c>hotplug</c>: |
13263 |
</p> |
13264 |
|
13265 |
<pre caption="Emerging and enabling hotplug"> |
13266 |
# <i>emerge hotplug</i> |
13267 |
# <i>rc-update add hotplug default</i> |
13268 |
</pre> |
13269 |
|
13270 |
<p> |
13271 |
Now continue with <uri link="?part=1&chap=8">Configuring your System</uri>. |
13272 |
</p> |
13273 |
|
13274 |
</body> |
13275 |
</section> |
13276 |
|
13277 |
</sections> |
13278 |
|
13279 |
|
13280 |
|
13281 |
|
13282 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-medium.xml |
13283 |
|
13284 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-medium.xml?rev=1.1&view=markup |
13285 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-medium.xml?rev=1.1&content-type=text/plain |
13286 |
|
13287 |
Index: hb-install-ppc-medium.xml |
13288 |
=================================================================== |
13289 |
<?xml version='1.0' encoding='UTF-8'?> |
13290 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
13291 |
|
13292 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
13293 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
13294 |
|
13295 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-medium.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
13296 |
|
13297 |
<sections> |
13298 |
|
13299 |
<version>7.0</version> |
13300 |
<date>2006-08-30</date> |
13301 |
|
13302 |
<section> |
13303 |
<title>Hardware Requirements</title> |
13304 |
<subsection> |
13305 |
<title>Introduction</title> |
13306 |
<body> |
13307 |
|
13308 |
<p> |
13309 |
Before we start, we first list what hardware requirements you need to |
13310 |
successfully install Gentoo on your box. |
13311 |
</p> |
13312 |
|
13313 |
</body> |
13314 |
</subsection> |
13315 |
<subsection> |
13316 |
<title>Hardware Requirements</title> |
13317 |
<body> |
13318 |
|
13319 |
<table> |
13320 |
<tr> |
13321 |
<th>Apple NewWorld Machines</th> |
13322 |
<ti> |
13323 |
Power/PowerPC microprocessors (G3, G4, G5) such as iMac, eMac, iBook |
13324 |
PowerBook, Xserver, PowerMac |
13325 |
</ti> |
13326 |
</tr> |
13327 |
<tr> |
13328 |
<th>Apple OldWorld machines</th> |
13329 |
<ti> |
13330 |
Apple Machines with an OpenFirmware revision less than 3, such as the Beige |
13331 |
G3s, PCI PowerMacs and PCI PowerBooks. PCI based Apple Clones should also |
13332 |
be supported. |
13333 |
</ti> |
13334 |
</tr> |
13335 |
<tr> |
13336 |
<th>Genesi's Pegasos</th> |
13337 |
<ti> |
13338 |
Pegasos I/II, Open Desktop Workstation |
13339 |
</ti> |
13340 |
</tr> |
13341 |
<tr> |
13342 |
<th>IBM</th> |
13343 |
<ti> |
13344 |
RS/6000, iSeries, pSeries |
13345 |
</ti> |
13346 |
</tr> |
13347 |
<tr> |
13348 |
<th>Memory</th> |
13349 |
<ti>At least 64 MB</ti> |
13350 |
</tr> |
13351 |
<tr> |
13352 |
<th>Diskspace</th> |
13353 |
<ti>1.5 GB (excluding swap space)</ti> |
13354 |
</tr> |
13355 |
<tr> |
13356 |
<th>Swap space</th> |
13357 |
<ti>At least 256 MB</ti> |
13358 |
</tr> |
13359 |
</table> |
13360 |
|
13361 |
<p> |
13362 |
Be sure to read the <uri link="/doc/en/gentoo-ppc-faq.xml">Gentoo PPC FAQ</uri> |
13363 |
for help with some common installation related issues or if you're unsure as to |
13364 |
just what's in that PowerPC machine you've got sitting on your desk right now. |
13365 |
</p> |
13366 |
|
13367 |
</body> |
13368 |
</subsection> |
13369 |
</section> |
13370 |
<!-- Copy/paste of hb-install-x86-medium.xml, with s/x86/ppc/ --> |
13371 |
<!-- START --> |
13372 |
<section> |
13373 |
<title>The Gentoo Universal Installation CD</title> |
13374 |
<subsection> |
13375 |
<title>Introduction</title> |
13376 |
<body> |
13377 |
|
13378 |
<p> |
13379 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
13380 |
Such a tarball is an archive that contains a minimal environment from |
13381 |
which you can succesfully install Gentoo Linux onto your system. |
13382 |
</p> |
13383 |
|
13384 |
<p> |
13385 |
Installations using a stage1 or stage2 tarball file are not documented in the |
13386 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
13387 |
FAQ</uri> on these matters. |
13388 |
</p> |
13389 |
|
13390 |
</body> |
13391 |
</subsection> |
13392 |
<subsection> |
13393 |
<title>Gentoo Universal Installation CD</title> |
13394 |
<body> |
13395 |
|
13396 |
<p> |
13397 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
13398 |
environment. It allows you to boot Linux from the CD. During the boot process |
13399 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
13400 |
Installation CDs are maintained by Gentoo developers. |
13401 |
</p> |
13402 |
|
13403 |
<p> |
13404 |
There currently are two Installation CDs available: |
13405 |
</p> |
13406 |
|
13407 |
<ul> |
13408 |
<li> |
13409 |
The Universal Installation CD contains everything you need to install |
13410 |
Gentoo. It provides stage3 files for common architectures, source code |
13411 |
for the extra applications you need to choose from and, of course, the |
13412 |
installation instructions for your architecture. |
13413 |
</li> |
13414 |
<li> |
13415 |
The Minimal Installation CD contains only a minimal environment that allows |
13416 |
you to boot up and configure your network so you can connect to the |
13417 |
Internet. It does not contain any additional files and cannot be used |
13418 |
during the current installation approach. |
13419 |
</li> |
13420 |
</ul> |
13421 |
|
13422 |
<p> |
13423 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
13424 |
additional resource that you can exploit during the installation of your Gentoo |
13425 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
13426 |
you to easily and quickly install additional applications (such as |
13427 |
OpenOffice.org, KDE, GNOME, ...) immediately after the Gentoo installation and |
13428 |
right before you update your Portage tree. |
13429 |
</p> |
13430 |
|
13431 |
<p> |
13432 |
The use of the Package CD is covered later in this document. |
13433 |
</p> |
13434 |
|
13435 |
</body> |
13436 |
</subsection> |
13437 |
</section> |
13438 |
<!-- STOP --> |
13439 |
<section> |
13440 |
<title>Download, Burn and Boot the Gentoo Universal Installation CD</title> |
13441 |
<subsection> |
13442 |
<title>Downloading and Burning the Installation CD</title> |
13443 |
<body> |
13444 |
|
13445 |
<p> |
13446 |
You can download the Universal Installation CD (and, if you want to, the |
13447 |
Packages CD as well) from one of our <uri |
13448 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located |
13449 |
in the <path>releases/ppc/2006.1/ppc32/installcd</path> directory; |
13450 |
the Package CDs are located in the |
13451 |
<path>releases/ppc/2006.1/ppc32/packagecd</path> directory. |
13452 |
</p> |
13453 |
|
13454 |
<p> |
13455 |
Inside those directories you'll find ISO-files. Those are full CD images which |
13456 |
you can write on a CD-R. |
13457 |
</p> |
13458 |
|
13459 |
<p> |
13460 |
After downloading the file, you can verify its integrity to see if it is |
13461 |
corrupted or not: |
13462 |
</p> |
13463 |
|
13464 |
<ul> |
13465 |
<li> |
13466 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
13467 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
13468 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows). |
13469 |
Verifying MD5 checksums with Mac OS X is described in the <uri |
13470 |
link="/doc/en/gentoo-ppc-faq.xml#doc_chap1">Gentoo PPC FAQ</uri>. |
13471 |
</li> |
13472 |
<li> |
13473 |
You can verify the cryptographic signature that we provide. You need to |
13474 |
obtain the public key we use (0x17072058) before you proceed though. |
13475 |
</li> |
13476 |
</ul> |
13477 |
|
13478 |
<p> |
13479 |
To fetch our public key using the GnuPG application, run the following command: |
13480 |
</p> |
13481 |
|
13482 |
<pre caption="Obtaining the public key"> |
13483 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 0x17072058</i> |
13484 |
</pre> |
13485 |
|
13486 |
<p> |
13487 |
Now verify the signature: |
13488 |
</p> |
13489 |
|
13490 |
<pre caption="Verify the cryptographic signature"> |
13491 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
13492 |
</pre> |
13493 |
|
13494 |
<p> |
13495 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
13496 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
13497 |
<c>K3B</c> here; more information can be found in our <uri |
13498 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
13499 |
</p> |
13500 |
|
13501 |
<ul> |
13502 |
<li> |
13503 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
13504 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
13505 |
path). |
13506 |
</li> |
13507 |
<li> |
13508 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
13509 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
13510 |
<c>Start</c>. |
13511 |
</li> |
13512 |
</ul> |
13513 |
|
13514 |
</body> |
13515 |
</subsection> |
13516 |
<subsection> |
13517 |
<title>Default: Booting the Installation CD with Yaboot</title> |
13518 |
<body> |
13519 |
|
13520 |
<p> |
13521 |
On NewWorld machines place the Installation CD in the CD-ROM and reboot the |
13522 |
system. When the system-start-bell sounds, simply hold down the 'C' until the |
13523 |
CD loads. |
13524 |
</p> |
13525 |
|
13526 |
<p> |
13527 |
After the Installation CD loaded, you will be greeted by a friendly welcome |
13528 |
message and a <e>boot:</e> prompt at the bottom of the screen. |
13529 |
</p> |
13530 |
|
13531 |
<p> |
13532 |
We provide one generic kernel, <e>apple</e>. This kernel is built with support |
13533 |
for multiple CPUs, but it will boot on single processor machines as well. |
13534 |
</p> |
13535 |
|
13536 |
<p> |
13537 |
You can tweak some kernel options at this prompt. The following table lists |
13538 |
some of the available boot options you can add: |
13539 |
</p> |
13540 |
|
13541 |
<table> |
13542 |
<tr> |
13543 |
<th>Boot Option</th> |
13544 |
<th>Description</th> |
13545 |
</tr> |
13546 |
<tr> |
13547 |
<ti><c>video</c></ti> |
13548 |
<ti> |
13549 |
This option takes one of the following vendor-specific tags: |
13550 |
<c>nvidiafb</c>, <c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, |
13551 |
<c>aty128</c> or <c>ofonly</c>. You can follow this tag with the resolution |
13552 |
refresh rate and color depth you want to use. For instance, |
13553 |
<c>video=radeonfb:1280x1024@75-32</c> will select the ATI Radeon frame buffer |
13554 |
at a resolution of 1280x1024 with a refresh rate of 75Hz and a color depth of |
13555 |
32 bits. If you are uncertain what to choose, and the default doesn't work, |
13556 |
<c>video=ofonly</c> will most certainly work. |
13557 |
</ti> |
13558 |
</tr> |
13559 |
<tr> |
13560 |
<ti><c>nol3</c></ti> |
13561 |
<ti> |
13562 |
Disables level 3 cache on some PowerBooks (needed for at least the 17") |
13563 |
</ti> |
13564 |
</tr> |
13565 |
<tr> |
13566 |
<ti><c>dofirewire</c></ti> |
13567 |
<ti> |
13568 |
Enables support for IEEE1394 (FireWire) devices, like external harddisks. |
13569 |
</ti> |
13570 |
</tr> |
13571 |
<tr> |
13572 |
<ti><c>dopcmcia</c></ti> |
13573 |
<ti> |
13574 |
If you want to use PCMCIA devices during your installation (like PCMCIA |
13575 |
network cards) you have to enable this option. |
13576 |
</ti> |
13577 |
</tr> |
13578 |
</table> |
13579 |
|
13580 |
<p> |
13581 |
To use the above options, at the <e>boot:</e> prompt, type <e>apple</e> followed |
13582 |
by the desired option. In the example below, we'll force the kernel to use the |
13583 |
OpenFirmware framebuffer instead of the device specific driver. |
13584 |
</p> |
13585 |
|
13586 |
<pre caption="Force the use of the OpenFirmware framebuffer"> |
13587 |
boot: <i>apple video=ofonly</i> |
13588 |
</pre> |
13589 |
|
13590 |
<p> |
13591 |
If you don't need to add any options, just hit enter at this prompt, and a |
13592 |
complete Gentoo Linux environment will be loaded from the CD. Continue with |
13593 |
<uri link="#booted">And When You're Booted...</uri>. |
13594 |
</p> |
13595 |
|
13596 |
</body> |
13597 |
</subsection> |
13598 |
<subsection> |
13599 |
<title>Alternative: Booting the Installation CD on a Pegasos</title> |
13600 |
<body> |
13601 |
|
13602 |
<p> |
13603 |
On the Pegasos simply insert the CD and at the SmartFirmware boot-prompt type |
13604 |
<c>boot cd /boot/menu</c>. This will open a small bootmenu where you can choose |
13605 |
between several preconfigured video configs. If you need any special boot |
13606 |
options you can append them to the command-line just like with Yaboot above. |
13607 |
For example: <c>boot cd /boot/pegasos video=radeonfb:1280x1024@75 mem=256M</c>. |
13608 |
The default kernel options (in case something goes wrong and you need it) are |
13609 |
preconfigured with <c>console=ttyS0,115200 console=tty0 init=/linuxrc |
13610 |
looptype=squashfs loop=/image.squashfs cdroot root=/dev/ram0</c>. |
13611 |
</p> |
13612 |
|
13613 |
</body> |
13614 |
</subsection> |
13615 |
|
13616 |
<subsection> |
13617 |
<title>Alternative: Booting the Installation CD with BootX</title> |
13618 |
<body> |
13619 |
|
13620 |
<p> |
13621 |
If you have an OldWorld Mac the bootable portion of the livecd can't be used. |
13622 |
The most simple solution is to use MacOS 9 or earlier to bootstrap into a Linux |
13623 |
environment with a tool called BootX. |
13624 |
</p> |
13625 |
|
13626 |
<p> |
13627 |
First, download <uri link="http://penguinppc.org/projects/bootx/">BootX</uri> |
13628 |
and unpack the archive. Copy the the <c>BootX Extension</c> from the unpacked |
13629 |
archive into <c>Extensions Folder</c> and the BootX App Control Panel into |
13630 |
<c>Control Panels</c>, both of which are located in your MacOS System Folder. |
13631 |
Next, create a folder called "Linux Kernels" in your System folder and copy the |
13632 |
<c>apple</c> kernel from the CD to this folder. Finally, copy <c>apple.igz</c> |
13633 |
from the Installation CD <path>boot</path> folder into the MacOS |
13634 |
<c>System Folder</c>. |
13635 |
</p> |
13636 |
|
13637 |
<p> |
13638 |
To prepare BootX, start the BootX App Control Panel. First select the Options |
13639 |
dialog and check <c>Use Specified RAM Disk</c> and select <c>apple.igz</c> from |
13640 |
your System Folder. Continue back to the initial screen and ensure that the |
13641 |
ramdisk size is at least <c>32000</c>. Finally, set the kernel arguments as |
13642 |
shown below: |
13643 |
</p> |
13644 |
|
13645 |
<pre caption="BootX kernel arguments"> |
13646 |
cdroot root=/dev/ram0 init=linuxrc loop=image.squashfs looptype=squashfs console=tty0 |
13647 |
</pre> |
13648 |
|
13649 |
<note> |
13650 |
The kernel parameters in the yaboot section above are also applicable here. You |
13651 |
can append any of those options to the kernel arguments above. |
13652 |
</note> |
13653 |
|
13654 |
<p> |
13655 |
Check once more to make sure the settings are correct and then save the |
13656 |
configuration. This saves typing just in case it doesn't boot or something is |
13657 |
missing. Press the Linux button at the top of the window. If everything goes |
13658 |
correctly, it should boot into the Installation CD. Continue with |
13659 |
<uri link="#booted">And When You're Booted...</uri> |
13660 |
</p> |
13661 |
|
13662 |
</body> |
13663 |
</subsection> |
13664 |
|
13665 |
<subsection id="booted"> |
13666 |
<title>And When You're Booted...</title> |
13667 |
<body> |
13668 |
|
13669 |
<p> |
13670 |
You will be greeted by a root ("#") prompt on the current console. You can also |
13671 |
switch to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get |
13672 |
back to the one you started on by pressing Alt-F1. Due to the keyboard layout, |
13673 |
you may need to press Alt-fn-Fx on Apple machines. |
13674 |
</p> |
13675 |
|
13676 |
<p> |
13677 |
If you are installing Gentoo on a system with a non-US keyboard, use |
13678 |
<c>loadkeys</c> to load the keymap for your keyboard. To list the available |
13679 |
keymaps, execute <c>ls /usr/share/keymaps/i386</c>. On NewWorld machines or the |
13680 |
Pegasos do not use the keymaps in <path>ppc</path> or <path>mac</path> as they |
13681 |
are for ADB-based OldWorld machines. |
13682 |
</p> |
13683 |
|
13684 |
<pre caption="Listing available keymaps"> |
13685 |
<comment>(PPC uses x86 keymaps on most systems. The mac/ppc keymaps provided |
13686 |
on the Installation CD are ADB keymaps and unusable with the Installation CD |
13687 |
kernel)</comment> |
13688 |
# <i>ls /usr/share/keymaps/i386</i> |
13689 |
</pre> |
13690 |
|
13691 |
<p> |
13692 |
Now load the keymap of your choice: |
13693 |
</p> |
13694 |
|
13695 |
<pre caption="Loading a keymap"> |
13696 |
# <i>loadkeys be-latin1</i> |
13697 |
</pre> |
13698 |
|
13699 |
<p> |
13700 |
Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
13701 |
</p> |
13702 |
|
13703 |
</body> |
13704 |
</subsection> |
13705 |
<subsection id="hardware"> |
13706 |
<title>Extra Hardware Configuration</title> |
13707 |
<body> |
13708 |
|
13709 |
<p> |
13710 |
When the Installation CD boots, it tries to detect all your hardware devices and |
13711 |
loads the appropriate kernel modules to support your hardware. In the |
13712 |
vast majority of cases, it does a very good job. However, in some cases, it may |
13713 |
not auto-load the kernel modules you need. If the PCI auto-detection missed some |
13714 |
of your system's hardware, you will have to load the appropriate kernel modules |
13715 |
manually. |
13716 |
</p> |
13717 |
|
13718 |
<p> |
13719 |
In the next example we try to load the <c>airport</c> module. This module |
13720 |
supports only the old Airport cards (802.11b). Airport Extreme (802.11g) is not |
13721 |
supported on the InstallCD due to restrictions on firmware distribution. |
13722 |
</p> |
13723 |
|
13724 |
<pre caption="Loading the airport module"> |
13725 |
# <i>modprobe airport</i> |
13726 |
</pre> |
13727 |
|
13728 |
<p> |
13729 |
On older iMacs, sometimes the network card is not detected properly. These use |
13730 |
the BMAC driver: |
13731 |
</p> |
13732 |
|
13733 |
<pre caption="Loading the bmac module"> |
13734 |
# <i>modprobe bmac</i> |
13735 |
</pre> |
13736 |
|
13737 |
</body> |
13738 |
</subsection> |
13739 |
<subsection> |
13740 |
<title>Optional: Tweaking Hard Disk Performance</title> |
13741 |
<body> |
13742 |
|
13743 |
<p> |
13744 |
If you are an advanced user, you might want to tweak the IDE hard disk |
13745 |
performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
13746 |
test the performance of your disk (execute it several times to get a |
13747 |
more precise impression): |
13748 |
</p> |
13749 |
|
13750 |
<pre caption="Testing disk performance"> |
13751 |
# <i>hdparm -tT /dev/hda</i> |
13752 |
</pre> |
13753 |
|
13754 |
<p> |
13755 |
To tweak, you can use any of the following examples (or experiment |
13756 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
13757 |
disk): |
13758 |
</p> |
13759 |
|
13760 |
<pre caption="Tweaking hard disk performance"> |
13761 |
<comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i> |
13762 |
<comment>Activate DMA + Safe Performance-enhancing Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
13763 |
</pre> |
13764 |
|
13765 |
</body> |
13766 |
</subsection> |
13767 |
<subsection id="useraccounts"> |
13768 |
<title>Optional: User Accounts</title> |
13769 |
<body> |
13770 |
|
13771 |
<p> |
13772 |
If you plan on giving other people access to your installation |
13773 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
13774 |
security reasons), you need to create the necessary user accounts and change |
13775 |
the root password. |
13776 |
</p> |
13777 |
|
13778 |
<p> |
13779 |
To change the root password, use the <c>passwd</c> utility: |
13780 |
</p> |
13781 |
|
13782 |
<pre caption="Changing the root password"> |
13783 |
# <i>passwd</i> |
13784 |
New password: <comment>(Enter your new password)</comment> |
13785 |
Re-enter password: <comment>(Re-enter your password)</comment> |
13786 |
</pre> |
13787 |
|
13788 |
<p> |
13789 |
To create a user account, we first enter their credentials, followed by |
13790 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
13791 |
In the next example, we create a user called "john". |
13792 |
</p> |
13793 |
|
13794 |
<pre caption="Creating a user account"> |
13795 |
# <i>useradd -m -G users john</i> |
13796 |
# <i>passwd john</i> |
13797 |
New password: <comment>(Enter john's password)</comment> |
13798 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
13799 |
</pre> |
13800 |
|
13801 |
<p> |
13802 |
You can change your user id from root to the newly created user by using |
13803 |
<c>su</c>: |
13804 |
</p> |
13805 |
|
13806 |
<pre caption="Changing user id"> |
13807 |
# <i>su - john</i> |
13808 |
</pre> |
13809 |
|
13810 |
</body> |
13811 |
</subsection> |
13812 |
<subsection> |
13813 |
<title>Optional: Viewing Documentation while Installing</title> |
13814 |
<body> |
13815 |
|
13816 |
<p> |
13817 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
13818 |
installation, make sure you have created a user account (see <uri |
13819 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
13820 |
go to a new terminal and log in. |
13821 |
</p> |
13822 |
|
13823 |
<p> |
13824 |
If you want to view the documentation on the CD you can immediately run |
13825 |
<c>links</c> or even <c>links -g</c> for a graphical framebuffer browser to |
13826 |
read it: |
13827 |
</p> |
13828 |
|
13829 |
<pre caption="Viewing the on-CD documentation"> |
13830 |
# <i>links /mnt/cdrom/docs/html/index.html</i> |
13831 |
</pre> |
13832 |
|
13833 |
<p> |
13834 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
13835 |
more recent than the one provided on the CD. You can view it using <c>links</c> |
13836 |
as well, but only after having completed the <e>Configuring your Network</e> |
13837 |
chapter (otherwise you won't be able to go on the Internet to view the |
13838 |
document): |
13839 |
</p> |
13840 |
|
13841 |
<pre caption="Viewing the Online Documentation"> |
13842 |
# <i>links http://www.gentoo.org/doc/en/handbook/handbook-ppc.xml</i> |
13843 |
</pre> |
13844 |
|
13845 |
<p> |
13846 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
13847 |
</p> |
13848 |
|
13849 |
</body> |
13850 |
</subsection> |
13851 |
<subsection> |
13852 |
<title>Optional: Starting the SSH Daemon</title> |
13853 |
<body> |
13854 |
|
13855 |
<p> |
13856 |
If you want to allow other users to access your computer during the |
13857 |
Gentoo installation (perhaps because those users are going to help you |
13858 |
install Gentoo, or even do it for you), you need to create a user |
13859 |
account for them and perhaps even provide them with your root password |
13860 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
13861 |
</p> |
13862 |
|
13863 |
<p> |
13864 |
To fire up the SSH daemon, execute the following command: |
13865 |
</p> |
13866 |
|
13867 |
<pre caption="Starting the SSH daemon"> |
13868 |
# <i>/etc/init.d/sshd start</i> |
13869 |
</pre> |
13870 |
|
13871 |
<p> |
13872 |
To be able to use sshd, you first need to set up your networking. Continue with |
13873 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
13874 |
</p> |
13875 |
|
13876 |
</body> |
13877 |
</subsection> |
13878 |
</section> |
13879 |
</sections> |
13880 |
|
13881 |
|
13882 |
|
13883 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-sparc-bootloader.xml |
13884 |
|
13885 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-sparc-bootloader.xml?rev=1.1&view=markup |
13886 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-sparc-bootloader.xml?rev=1.1&content-type=text/plain |
13887 |
|
13888 |
Index: hb-install-sparc-bootloader.xml |
13889 |
=================================================================== |
13890 |
<?xml version='1.0' encoding='UTF-8'?> |
13891 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
13892 |
|
13893 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
13894 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
13895 |
|
13896 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-sparc-bootloader.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
13897 |
|
13898 |
<sections> |
13899 |
|
13900 |
<version>7.0</version> |
13901 |
<date>2006-08-30</date> |
13902 |
|
13903 |
<section> |
13904 |
<title>Making your Choice</title> |
13905 |
<subsection> |
13906 |
<title>Introduction</title> |
13907 |
<body> |
13908 |
|
13909 |
<p> |
13910 |
Now that your kernel is configured and compiled and the necessary system |
13911 |
configuration files are filled in correctly, it is time to install a |
13912 |
program that will fire up your kernel when you start the system. Such a |
13913 |
program is called a <e>bootloader</e>. |
13914 |
</p> |
13915 |
|
13916 |
</body> |
13917 |
</subsection> |
13918 |
</section> |
13919 |
<section> |
13920 |
<title>Installing the SPARC Bootloader: SILO</title> |
13921 |
<body> |
13922 |
|
13923 |
<p> |
13924 |
It is now time to install and configure <uri |
13925 |
link="http://www.sparc-boot.org">SILO</uri>, the Sparc Improved boot |
13926 |
LOader. |
13927 |
</p> |
13928 |
|
13929 |
<pre caption = "Installing SILO"> |
13930 |
# <i>emerge silo</i> |
13931 |
</pre> |
13932 |
|
13933 |
<p> |
13934 |
Now open up your favorite editor (we use <c>nano</c> as an example) and |
13935 |
create <path>/etc/silo.conf</path>. |
13936 |
</p> |
13937 |
|
13938 |
<pre caption = "Creating /etc/silo.conf"> |
13939 |
# <i>nano -w /etc/silo.conf</i> |
13940 |
</pre> |
13941 |
|
13942 |
<p> |
13943 |
Below you'll find an example <path>silo.conf</path> file. It uses the |
13944 |
partitioning scheme we use throughout this book and |
13945 |
<path>kernel-2.4.31</path> as kernelimage. |
13946 |
</p> |
13947 |
|
13948 |
<pre caption = "Example /etc/silo.conf"> |
13949 |
partition = 1 <comment># Boot partition (= root partition)</comment> |
13950 |
root = /dev/sda1 <comment># Root partition</comment> |
13951 |
timeout = 150 <comment># Wait 15 seconds before booting the default section</comment> |
13952 |
|
13953 |
image = /boot/kernel-2.4.31 |
13954 |
label = linux |
13955 |
</pre> |
13956 |
|
13957 |
<p> |
13958 |
If you use the example <path>silo.conf</path> delivered by Portage, be |
13959 |
sure to comment out <e>all</e> lines that you do not need. |
13960 |
</p> |
13961 |
|
13962 |
<p> |
13963 |
If the physical disk on which you want to install SILO (as bootloader) differs |
13964 |
from the physical disk on which <path>/etc/silo.conf</path> resides, you must |
13965 |
copy over <path>/etc/silo.conf</path> to a partition on that disk. Assuming that |
13966 |
<path>/boot</path> is a separate partition on that disk, copy over the |
13967 |
configuration file to <path>/boot</path> and run <c>/sbin/silo -f</c>: |
13968 |
</p> |
13969 |
|
13970 |
<pre caption = "Only if /boot and the SILO destination are not on the same disk"> |
13971 |
# <i>cp /etc/silo.conf /boot</i> |
13972 |
# <i>/sbin/silo -f -C /boot/silo.conf</i> |
13973 |
/boot/silo.conf appears to be valid |
13974 |
</pre> |
13975 |
|
13976 |
<p> |
13977 |
Otherwise just run <c>/sbin/silo -f</c>: |
13978 |
</p> |
13979 |
|
13980 |
<pre caption = "Run silo"> |
13981 |
# <i>/sbin/silo -f</i> |
13982 |
/etc/silo.conf appears to be valid |
13983 |
</pre> |
13984 |
|
13985 |
<note> |
13986 |
You have to run <c>silo</c> (with parameters) again each time you update or |
13987 |
reinstall the <c>sys-boot/silo</c> package. |
13988 |
</note> |
13989 |
|
13990 |
<p> |
13991 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
13992 |
</p> |
13993 |
|
13994 |
</body> |
13995 |
</section> |
13996 |
<section id="reboot"> |
13997 |
<title>Rebooting the System</title> |
13998 |
<subsection> |
13999 |
<body> |
14000 |
|
14001 |
<p> |
14002 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
14003 |
that one magical command you have been waiting for: <c>reboot</c>. |
14004 |
</p> |
14005 |
|
14006 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
14007 |
# <i>exit</i> |
14008 |
cdimage ~# <i>cd</i> |
14009 |
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
14010 |
cdimage ~# <i>reboot</i> |
14011 |
</pre> |
14012 |
|
14013 |
<p> |
14014 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
14015 |
booted again instead of your new Gentoo system. |
14016 |
</p> |
14017 |
|
14018 |
<p> |
14019 |
Once rebooted in your Gentoo installation, finish up with <uri |
14020 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
14021 |
</p> |
14022 |
|
14023 |
</body> |
14024 |
</subsection> |
14025 |
</section> |
14026 |
</sections> |
14027 |
|
14028 |
|
14029 |
|
14030 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-sparc-disk.xml |
14031 |
|
14032 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-sparc-disk.xml?rev=1.1&view=markup |
14033 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-sparc-disk.xml?rev=1.1&content-type=text/plain |
14034 |
|
14035 |
Index: hb-install-sparc-disk.xml |
14036 |
=================================================================== |
14037 |
<?xml version='1.0' encoding='UTF-8'?> |
14038 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
14039 |
|
14040 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
14041 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
14042 |
|
14043 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-sparc-disk.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
14044 |
|
14045 |
<sections> |
14046 |
|
14047 |
<version>7.2</version> |
14048 |
<date>2006-11-02</date> |
14049 |
|
14050 |
<section> |
14051 |
<title>Introduction to Block Devices</title> |
14052 |
<subsection> |
14053 |
<title>Block Devices</title> |
14054 |
<body> |
14055 |
|
14056 |
<p> |
14057 |
We'll take a good look at some of the disk-oriented aspects of Gentoo Linux |
14058 |
and Linux in general, including Linux filesystems, partitions, and block |
14059 |
devices. Then, once you're familiar with the ins and outs of disks and |
14060 |
filesystems, you'll be guided through the process of setting up partitions |
14061 |
and filesystems for your Gentoo Linux installation. |
14062 |
</p> |
14063 |
|
14064 |
<p> |
14065 |
To begin, we introduce <e>block devices</e>. The most typical block device is |
14066 |
probably the one that represents the first SCSI hard disk in a Linux system, |
14067 |
namely <path>/dev/sda</path>. |
14068 |
</p> |
14069 |
|
14070 |
<p> |
14071 |
Block devices represent an abstract interface to the disk. User programs can |
14072 |
use these block devices to interact with your disk without worrying about |
14073 |
whether your drives are IDE, SCSI, or something else. The program can simply |
14074 |
address the storage on the disk as a bunch of contiguous, randomly-accessible |
14075 |
512-byte blocks. |
14076 |
</p> |
14077 |
|
14078 |
<p> |
14079 |
Block devices show up as entries in <path>/dev/</path>. Typically, the first |
14080 |
SCSI drive is named <path>/dev/sda</path>, the second <path>/dev/sdb</path>, |
14081 |
and so on. IDE drives are named similarly, however, they are prefixed by hd- |
14082 |
instead of sd-. If you are using IDE drives, the first one will be named |
14083 |
<path>/dev/hda</path>, the second <path>/dev/hdb</path>, and so on. |
14084 |
</p> |
14085 |
|
14086 |
</body> |
14087 |
</subsection> |
14088 |
<subsection> |
14089 |
<title>Partitions</title> |
14090 |
<body> |
14091 |
|
14092 |
<p> |
14093 |
Although it is theoretically possible to use the entire disk to house your Linux |
14094 |
system, this is almost never done in practice. Instead, full disk block devices |
14095 |
are split up in smaller, more manageable block devices. These are known as |
14096 |
<e>partitions</e> or <e>slices</e>. |
14097 |
</p> |
14098 |
|
14099 |
<p> |
14100 |
The first partition on the first SCSI disk is <path>/dev/sda1</path>, the second |
14101 |
<path>/dev/sda2</path> and so on. Similarly, the first two partitions on the |
14102 |
first IDE disk are <path>/dev/hda1</path> and <path>/dev/hda2</path>. |
14103 |
</p> |
14104 |
|
14105 |
<p> |
14106 |
The third partition on Sun systems is set aside as a special "whole disk" |
14107 |
slice. This partition must not contain a file system. |
14108 |
</p> |
14109 |
|
14110 |
<p> |
14111 |
Users who are used to the DOS partitioning scheme should note that Sun |
14112 |
disklabels do not have "primary" and "extended" partitions. Instead, up to |
14113 |
eight partitions are available per drive, with the third of these being |
14114 |
reserved. |
14115 |
</p> |
14116 |
|
14117 |
</body> |
14118 |
</subsection> |
14119 |
</section> |
14120 |
<section> |
14121 |
<title>Designing a Partitioning Scheme</title> |
14122 |
<subsection> |
14123 |
<title>Default Partitioning Scheme</title> |
14124 |
<body> |
14125 |
|
14126 |
<p> |
14127 |
If you are not interested in drawing up a partitioning scheme, |
14128 |
the table below suggests a suitable starting point for most systems. For |
14129 |
IDE-based systems, substitute <c>hda</c> for <c>sda</c> in the following. |
14130 |
</p> |
14131 |
|
14132 |
<p> |
14133 |
Note that a separate <path>/boot</path> partition is generally <e>not</e> |
14134 |
recommended on SPARC, as it complicates the bootloader configuration. |
14135 |
</p> |
14136 |
|
14137 |
<table> |
14138 |
<tr> |
14139 |
<th>Partition</th> |
14140 |
<th>Filesystem</th> |
14141 |
<th>Size</th> |
14142 |
<th>Mount Point</th> |
14143 |
<th>Description</th> |
14144 |
</tr> |
14145 |
<tr> |
14146 |
<ti>/dev/sda1</ti> |
14147 |
<ti>ext3</ti> |
14148 |
<ti><2 GByte</ti> |
14149 |
<ti>/</ti> |
14150 |
<ti> |
14151 |
Root partition. For all sparc32 systems, and sparc64 systems with older |
14152 |
OBP versions, this <e>must</e> be less than 2 GBytes in size, and the first |
14153 |
partition on the disk. |
14154 |
</ti> |
14155 |
</tr> |
14156 |
<tr> |
14157 |
<ti>/dev/sda2</ti> |
14158 |
<ti>swap</ti> |
14159 |
<ti>512 MBytes</ti> |
14160 |
<ti>none</ti> |
14161 |
<ti> |
14162 |
Swap partition. For bootstrap and certain larger compiles, at least 512 |
14163 |
MBytes of RAM (including swap) is required. |
14164 |
</ti> |
14165 |
</tr> |
14166 |
<tr> |
14167 |
<ti>/dev/sda3</ti> |
14168 |
<ti>none</ti> |
14169 |
<ti>Whole disk</ti> |
14170 |
<ti>none</ti> |
14171 |
<ti>Whole disk partition. This is required on SPARC systems.</ti> |
14172 |
</tr> |
14173 |
<tr> |
14174 |
<ti>/dev/sda4</ti> |
14175 |
<ti>ext3</ti> |
14176 |
<ti>at least 2 GBytes</ti> |
14177 |
<ti>/usr</ti> |
14178 |
<ti> |
14179 |
/usr partition. Applications are installed here. By default this partition |
14180 |
is also used for Portage data (which takes around 500 Mbyte excluding |
14181 |
source code). |
14182 |
</ti> |
14183 |
</tr> |
14184 |
<tr> |
14185 |
<ti>/dev/sda5</ti> |
14186 |
<ti>ext3</ti> |
14187 |
<ti>at least 1GByte</ti> |
14188 |
<ti>/var</ti> |
14189 |
<ti> |
14190 |
/var partition. Used for program-generated data. By default Portage uses |
14191 |
this partition for temporary space whilst compiling. Certain larger |
14192 |
applications such as Mozilla and OpenOffice.org can require over 1 GByte |
14193 |
of temporary space here when building. |
14194 |
</ti> |
14195 |
</tr> |
14196 |
<tr> |
14197 |
<ti>/dev/sda6</ti> |
14198 |
<ti>ext3</ti> |
14199 |
<ti>remaining space</ti> |
14200 |
<ti>/home</ti> |
14201 |
<ti>/home partition. Used for users' home directories.</ti> |
14202 |
</tr> |
14203 |
</table> |
14204 |
|
14205 |
</body> |
14206 |
</subsection> |
14207 |
</section> |
14208 |
|
14209 |
<section id="fdisk"> |
14210 |
<title>Using fdisk to Partition your Disk</title> |
14211 |
<subsection> |
14212 |
<body> |
14213 |
|
14214 |
<p> |
14215 |
The following parts explain how to create the example partition layout described |
14216 |
previously, namely: |
14217 |
</p> |
14218 |
|
14219 |
<table> |
14220 |
<tr> |
14221 |
<th>Partition</th> |
14222 |
<th>Description</th> |
14223 |
</tr> |
14224 |
<tr> |
14225 |
<ti>/dev/sda1</ti> |
14226 |
<ti>/</ti> |
14227 |
</tr> |
14228 |
<tr> |
14229 |
<ti>/dev/sda2</ti> |
14230 |
<ti>swap</ti> |
14231 |
</tr> |
14232 |
<tr> |
14233 |
<ti>/dev/sda3</ti> |
14234 |
<ti>whole disk slice</ti> |
14235 |
</tr> |
14236 |
<tr> |
14237 |
<ti>/dev/sda4</ti> |
14238 |
<ti>/usr</ti> |
14239 |
</tr> |
14240 |
<tr> |
14241 |
<ti>/dev/sda5</ti> |
14242 |
<ti>/var</ti> |
14243 |
</tr> |
14244 |
<tr> |
14245 |
<ti>/dev/sda6</ti> |
14246 |
<ti>/home</ti> |
14247 |
</tr> |
14248 |
</table> |
14249 |
|
14250 |
<p> |
14251 |
Change the partition layout as required. Remember to keep the root partition |
14252 |
entirely within the first 2 GBytes of the disk for older systems. There is also |
14253 |
a 15-partition limit for SCSI and SATA. |
14254 |
</p> |
14255 |
|
14256 |
</body> |
14257 |
</subsection> |
14258 |
<subsection> |
14259 |
<title>Firing up fdisk</title> |
14260 |
<body> |
14261 |
|
14262 |
<p> |
14263 |
Start <c>fdisk</c> with your disk as argument: |
14264 |
</p> |
14265 |
|
14266 |
<pre caption="Starting fdisk"> |
14267 |
# <i>fdisk /dev/sda</i> |
14268 |
</pre> |
14269 |
|
14270 |
<p> |
14271 |
You should be greeted with the fdisk prompt: |
14272 |
</p> |
14273 |
|
14274 |
<pre caption="The fdisk prompt"> |
14275 |
Command (m for help): |
14276 |
</pre> |
14277 |
|
14278 |
<p> |
14279 |
To view the available partitions, type in <c>p</c>: |
14280 |
</p> |
14281 |
|
14282 |
<pre caption="Listing available partitions"> |
14283 |
Command (m for help): <i>p</i> |
14284 |
|
14285 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
14286 |
Units = cylinders of 2048 * 512 bytes |
14287 |
|
14288 |
Device Flag Start End Blocks Id System |
14289 |
/dev/sda1 0 488 499712 83 Linux native |
14290 |
/dev/sda2 488 976 499712 82 Linux swap |
14291 |
/dev/sda3 0 8635 8842240 5 Whole disk |
14292 |
/dev/sda4 976 1953 1000448 83 Linux native |
14293 |
/dev/sda5 1953 2144 195584 83 Linux native |
14294 |
/dev/sda6 2144 8635 6646784 83 Linux native |
14295 |
</pre> |
14296 |
|
14297 |
<p> |
14298 |
Note the <c>Sun disk label</c> in the output. If this is missing, the disk is |
14299 |
using the DOS-partitioning, not the Sun partitioning. In this case, use <c>s</c> |
14300 |
to ensure that the disk has a sun partition table: |
14301 |
</p> |
14302 |
|
14303 |
<pre caption="Creating a Sun Disklabel"> |
14304 |
Command (m for help): s |
14305 |
Building a new sun disklabel. Changes will remain in memory only, |
14306 |
until you decide to write them. After that, of course, the previous |
14307 |
content won't be recoverable. |
14308 |
|
14309 |
Drive type |
14310 |
? auto configure |
14311 |
0 custom (with hardware detected defaults) |
14312 |
a Quantum ProDrive 80S |
14313 |
b Quantum ProDrive 105S |
14314 |
c CDC Wren IV 94171-344 |
14315 |
d IBM DPES-31080 |
14316 |
e IBM DORS-32160 |
14317 |
f IBM DNES-318350 |
14318 |
g SEAGATE ST34371 |
14319 |
h SUN0104 |
14320 |
i SUN0207 |
14321 |
j SUN0327 |
14322 |
k SUN0340 |
14323 |
l SUN0424 |
14324 |
m SUN0535 |
14325 |
n SUN0669 |
14326 |
o SUN1.0G |
14327 |
p SUN1.05 |
14328 |
q SUN1.3G |
14329 |
r SUN2.1G |
14330 |
s IOMEGA Jaz |
14331 |
Select type (? for auto, 0 for custom): <i>0</i> |
14332 |
Heads (1-1024, default 64): |
14333 |
Using default value 64 |
14334 |
Sectors/track (1-1024, default 32): |
14335 |
Using default value 32 |
14336 |
Cylinders (1-65535, default 8635): |
14337 |
Using default value 8635 |
14338 |
Alternate cylinders (0-65535, default 2): |
14339 |
Using default value 2 |
14340 |
Physical cylinders (0-65535, default 8637): |
14341 |
Using default value 8637 |
14342 |
Rotation speed (rpm) (1-100000, default 5400): <i>10000</i> |
14343 |
Interleave factor (1-32, default 1): |
14344 |
Using default value 1 |
14345 |
Extra sectors per cylinder (0-32, default 0): |
14346 |
Using default value 0 |
14347 |
</pre> |
14348 |
|
14349 |
<p> |
14350 |
You can find the correct values in your disk's documentation. The |
14351 |
'auto configure' option does not usually work. |
14352 |
</p> |
14353 |
|
14354 |
</body> |
14355 |
</subsection> |
14356 |
<subsection> |
14357 |
<title>Deleting Existing Partitions</title> |
14358 |
<body> |
14359 |
|
14360 |
<p> |
14361 |
It's time to delete any existing partitions. To do this, type <c>d</c> and hit |
14362 |
Enter. You will then be prompted for the partition number you would like to |
14363 |
delete. To delete a pre-existing <path>/dev/sda1</path>, you would type: |
14364 |
</p> |
14365 |
|
14366 |
<pre caption="Deleting a partition"> |
14367 |
Command (m for help): <i>d</i> |
14368 |
Partition number (1-4): <i>1</i> |
14369 |
</pre> |
14370 |
|
14371 |
<p> |
14372 |
<e>You should not delete partition 3 (whole disk).</e> This is required. If |
14373 |
this partition does not exist, follow the "Creating a Sun Disklabel" |
14374 |
instructions above. |
14375 |
</p> |
14376 |
|
14377 |
<p> |
14378 |
After deleting all partitions except the Whole disk slice, you should have a |
14379 |
partition layout similar to the following: |
14380 |
</p> |
14381 |
|
14382 |
<pre caption="View an empty partition scheme"> |
14383 |
Command (m for help): <i>p</i> |
14384 |
|
14385 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
14386 |
Units = cylinders of 2048 * 512 bytes |
14387 |
|
14388 |
Device Flag Start End Blocks Id System |
14389 |
/dev/sda3 0 8635 8842240 5 Whole disk |
14390 |
</pre> |
14391 |
|
14392 |
|
14393 |
</body> |
14394 |
</subsection> |
14395 |
|
14396 |
<subsection> |
14397 |
<title>Creating the Root Partition</title> |
14398 |
<body> |
14399 |
|
14400 |
<p> |
14401 |
We're ready to create the root partition. To do this, type <c>n</c> to create a |
14402 |
new partition, then type <c>1</c> to create the partition. When prompted for |
14403 |
the first cylinder, hit enter. When prompted for the last cylinder, type |
14404 |
<c>+512M</c> to create a partition <c>512MBytes</c> in size. Make sure that the |
14405 |
entire root partition fits within the first 2GBytes of the disk. You can see |
14406 |
output from these steps below: |
14407 |
</p> |
14408 |
|
14409 |
<pre caption="Creating a root partition"> |
14410 |
Command (m for help): <i>n</i> |
14411 |
Partition number (1-8): <i>1</i> |
14412 |
First cylinder (0-8635): <i>(press Enter)</i> |
14413 |
Last cylinder or +size or +sizeM or +sizeK (0-8635, default 8635): <i>+512M</i> |
14414 |
</pre> |
14415 |
|
14416 |
<p> |
14417 |
Now, when you type <c>p</c>, you should see the following partition printout: |
14418 |
</p> |
14419 |
|
14420 |
<pre caption="Listing the partition layout"> |
14421 |
Command (m for help): <i>p</i> |
14422 |
|
14423 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
14424 |
Units = cylinders of 2048 * 512 bytes |
14425 |
|
14426 |
Device Flag Start End Blocks Id System |
14427 |
/dev/sda1 0 488 499712 83 Linux native |
14428 |
/dev/sda3 0 8635 8842240 5 Whole disk |
14429 |
</pre> |
14430 |
|
14431 |
</body> |
14432 |
</subsection> |
14433 |
<subsection> |
14434 |
<title>Creating a swap partition</title> |
14435 |
<body> |
14436 |
|
14437 |
<p> |
14438 |
Next, let's create the swap partition. To do this, type <c>n</c> to create a new |
14439 |
partition, then <c>2</c> to create the second partition, <path>/dev/sda2</path> |
14440 |
in our case. When prompted for the first cylinder, hit enter. When prompted for |
14441 |
the last cylinder, type <c>+512M</c> to create a partition 512MB in size. After |
14442 |
you've done this, type <c>t</c> to set the partition type, and then type in |
14443 |
<c>82</c> to set the partition type to "Linux Swap". After completing these |
14444 |
steps, typing <c>p</c> should display a partition table that looks similar to |
14445 |
this: |
14446 |
</p> |
14447 |
|
14448 |
<pre caption="Listing of available partitions"> |
14449 |
Command (m for help): <i>p</i> |
14450 |
|
14451 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
14452 |
Units = cylinders of 2048 * 512 bytes |
14453 |
|
14454 |
Device Flag Start End Blocks Id System |
14455 |
/dev/sda1 0 488 499712 83 Linux native |
14456 |
/dev/sda2 488 976 499712 82 Linux swap |
14457 |
/dev/sda3 0 8635 8842240 5 Whole disk |
14458 |
</pre> |
14459 |
|
14460 |
</body> |
14461 |
</subsection> |
14462 |
<subsection> |
14463 |
<title>Creating the /usr, /var and /home partitions</title> |
14464 |
<body> |
14465 |
|
14466 |
<p> |
14467 |
Finally, let's create the /usr, /var and /home partitions. As before, |
14468 |
type <c>n</c> to create a new partition, then type <c>4</c> to create the |
14469 |
third partition, <path>/dev/sda4</path> in our case. When prompted for the |
14470 |
first cylinder, hit enter. When prompted for the last cylinder, enter |
14471 |
<c>+2048M</c> to create a partition 2 GBytes in size. Repeat this process |
14472 |
for <path>sda5</path> and <path>sda6</path>, using the desired sizes. Once |
14473 |
you're done, you should see something like this: |
14474 |
</p> |
14475 |
|
14476 |
<pre caption="Listing complete partition table"> |
14477 |
Command (m for help): <i>p</i> |
14478 |
|
14479 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
14480 |
Units = cylinders of 2048 * 512 bytes |
14481 |
|
14482 |
Device Flag Start End Blocks Id System |
14483 |
/dev/sda1 0 488 499712 83 Linux native |
14484 |
/dev/sda2 488 976 499712 82 Linux swap |
14485 |
/dev/sda3 0 8635 8842240 5 Whole disk |
14486 |
/dev/sda4 976 1953 1000448 83 Linux native |
14487 |
/dev/sda5 1953 2144 195584 83 Linux native |
14488 |
/dev/sda6 2144 8635 6646784 83 Linux native |
14489 |
</pre> |
14490 |
|
14491 |
</body> |
14492 |
</subsection> |
14493 |
<subsection> |
14494 |
<title>Save and Exit</title> |
14495 |
<body> |
14496 |
|
14497 |
<p> |
14498 |
To save your partition layout and exit <c>fdisk</c>, type <c>w</c>: |
14499 |
</p> |
14500 |
|
14501 |
<pre caption="Save and exit fdisk"> |
14502 |
Command (m for help): <i>w</i> |
14503 |
</pre> |
14504 |
|
14505 |
<p> |
14506 |
Now that your partitions are created, you can now continue with <uri |
14507 |
link="#filesystems">Creating Filesystems</uri>. |
14508 |
</p> |
14509 |
|
14510 |
</body> |
14511 |
</subsection> |
14512 |
</section> |
14513 |
<section id="filesystems"> |
14514 |
<title>Creating Filesystems</title> |
14515 |
<subsection> |
14516 |
<title>Introduction</title> |
14517 |
<body> |
14518 |
|
14519 |
<p> |
14520 |
Now that your partitions are created, it is time to place a filesystem on them. |
14521 |
If you don't care about what filesystem to choose and are happy with what is |
14522 |
used as default in this handbook, continue with <uri |
14523 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
14524 |
Otherwise, read on to learn about the available filesystems... |
14525 |
</p> |
14526 |
|
14527 |
</body> |
14528 |
</subsection> |
14529 |
<subsection> |
14530 |
<title>Filesystems?</title> |
14531 |
<body> |
14532 |
|
14533 |
<p> |
14534 |
Several filesystems are available, some are known to be stable on the |
14535 |
SPARC architecture. Ext2 and ext3, for example, are known to work well. |
14536 |
Alternate filesystems may not function correctly. |
14537 |
</p> |
14538 |
|
14539 |
<p> |
14540 |
<b>ext2</b> is the tried-and-true Linux filesystem. It does not support |
14541 |
journaling, which means that periodic checks of ext2 filesystems at startup |
14542 |
can be quite time-consuming. There is quite a selection of newer-generation |
14543 |
journaled filesystems that can be checked for consistency very quickly at |
14544 |
startup, and are therefore generally preferred over their non-journaled |
14545 |
counterparts. In general, journaled filesystems prevent long delays when a |
14546 |
system is booted and the filesystem is in an inconsistent state. |
14547 |
</p> |
14548 |
|
14549 |
<p> |
14550 |
<b>ext3</b> is the journaled version of the ext2 filesystem. It provides |
14551 |
metadata journaling for fast recovery as well as other enhanced journaling |
14552 |
modes like full-data and ordered-data journaling. It uses a hashed B*-tree |
14553 |
index that enables high performance in almost all situations. Ext3 makes an |
14554 |
excellent and reliable alternative to ext2. |
14555 |
</p> |
14556 |
|
14557 |
</body> |
14558 |
</subsection> |
14559 |
<subsection id="filesystems-apply"> |
14560 |
<title>Applying a Filesystem to a Partition</title> |
14561 |
<body> |
14562 |
|
14563 |
<p> |
14564 |
To create a filesystem on a partition or volume, tools specific to the chosen |
14565 |
filesystem are available: |
14566 |
</p> |
14567 |
|
14568 |
<table> |
14569 |
<tr> |
14570 |
<th>Filesystem</th> |
14571 |
<th>Creation Command</th> |
14572 |
</tr> |
14573 |
<tr> |
14574 |
<ti>ext2</ti> |
14575 |
<ti><c>mke2fs</c></ti> |
14576 |
</tr> |
14577 |
<tr> |
14578 |
<ti>ext3</ti> |
14579 |
<ti><c>mke2fs -j</c></ti> |
14580 |
</tr> |
14581 |
</table> |
14582 |
|
14583 |
<p> |
14584 |
For instance, to create the root partition (<path>/dev/sda1</path> in our |
14585 |
example) as ext2, and the <path>/usr</path>, <path>/var</path>, and |
14586 |
<path>/home</path> partitions (<path>/dev/sda4</path>, <path>5</path> |
14587 |
and <path>6</path> in our example, respectively) as ext3, you would use: |
14588 |
</p> |
14589 |
|
14590 |
<pre caption="Applying a filesystem on a partition"> |
14591 |
# <i>mke2fs /dev/sda1</i> |
14592 |
# <i>mke2fs -j /dev/sda4</i> |
14593 |
# <i>mke2fs -j /dev/sda5</i> |
14594 |
# <i>mke2fs -j /dev/sda6</i> |
14595 |
</pre> |
14596 |
|
14597 |
</body> |
14598 |
</subsection> |
14599 |
<subsection> |
14600 |
<title>Activating the Swap Partition</title> |
14601 |
<body> |
14602 |
|
14603 |
<p> |
14604 |
<c>mkswap</c> is the command used to initialize swap partitions: |
14605 |
</p> |
14606 |
|
14607 |
<pre caption="Creating a Swap signature"> |
14608 |
# <i>mkswap /dev/sda2</i> |
14609 |
</pre> |
14610 |
|
14611 |
<p> |
14612 |
To activate the swap partition, use <c>swapon</c>: |
14613 |
</p> |
14614 |
|
14615 |
<pre caption="Activating the swap partition"> |
14616 |
# <i>swapon /dev/sda2</i> |
14617 |
</pre> |
14618 |
|
14619 |
<p> |
14620 |
Create and activate the swap now. |
14621 |
</p> |
14622 |
|
14623 |
</body> |
14624 |
</subsection> |
14625 |
</section> |
14626 |
<section> |
14627 |
<title>Mounting</title> |
14628 |
<body> |
14629 |
|
14630 |
<p> |
14631 |
Now that your partitions are initialized and are housing a filesystem, it is |
14632 |
time to mount them using the <c>mount</c> command. Don't forget to first |
14633 |
create the necessary mount directories for every partition you created. For |
14634 |
example: |
14635 |
</p> |
14636 |
|
14637 |
<pre caption="Mounting partitions"> |
14638 |
# <i>mount /dev/sda1 /mnt/gentoo</i> |
14639 |
# <i>mkdir /mnt/gentoo/usr</i> |
14640 |
# <i>mount /dev/sda4 /mnt/gentoo/usr</i> |
14641 |
# <i>mkdir /mnt/gentoo/var</i> |
14642 |
# <i>mount /dev/sda5 /mnt/gentoo/var</i> |
14643 |
# <i>mkdir /mnt/gentoo/home</i> |
14644 |
# <i>mount /dev/sda6 /mnt/gentoo/home</i> |
14645 |
</pre> |
14646 |
|
14647 |
<note> |
14648 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure |
14649 |
to change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. |
14650 |
This also holds for <path>/var/tmp</path>. |
14651 |
</note> |
14652 |
|
14653 |
<p> |
14654 |
We will also have to mount the proc filesystem (a virtual interface with the |
14655 |
kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. |
14656 |
</p> |
14657 |
|
14658 |
<p> |
14659 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
14660 |
Installation Files</uri>. |
14661 |
</p> |
14662 |
|
14663 |
</body> |
14664 |
</section> |
14665 |
</sections> |
14666 |
|
14667 |
|
14668 |
|
14669 |
|
14670 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-sparc-kernel.xml |
14671 |
|
14672 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-sparc-kernel.xml?rev=1.1&view=markup |
14673 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-sparc-kernel.xml?rev=1.1&content-type=text/plain |
14674 |
|
14675 |
Index: hb-install-sparc-kernel.xml |
14676 |
=================================================================== |
14677 |
<?xml version='1.0' encoding='UTF-8'?> |
14678 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
14679 |
|
14680 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
14681 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
14682 |
|
14683 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-sparc-kernel.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
14684 |
|
14685 |
<sections> |
14686 |
|
14687 |
<version>7.2</version> |
14688 |
<date>2007-03-06</date> |
14689 |
|
14690 |
<section> |
14691 |
<title>Timezone</title> |
14692 |
<body> |
14693 |
|
14694 |
<p> |
14695 |
You first need to select your timezone so that your system knows where it is |
14696 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
14697 |
it to <path>/etc/localtime</path>. Please avoid the |
14698 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
14699 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
14700 |
</p> |
14701 |
|
14702 |
<pre caption="Setting the timezone information"> |
14703 |
# <i>ls /usr/share/zoneinfo</i> |
14704 |
<comment>(Suppose you want to use GMT)</comment> |
14705 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
14706 |
</pre> |
14707 |
|
14708 |
</body> |
14709 |
</section> |
14710 |
<section> |
14711 |
<title>Installing the Sources</title> |
14712 |
<subsection> |
14713 |
<title>Choosing a Kernel</title> |
14714 |
<body> |
14715 |
|
14716 |
<p> |
14717 |
The core around which all distributions are built is the Linux kernel. It is the |
14718 |
layer between the user programs and your system hardware. Gentoo provides its |
14719 |
users several possible kernel sources. A full listing with description is |
14720 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
14721 |
Guide</uri>. |
14722 |
</p> |
14723 |
|
14724 |
<p> |
14725 |
For sparc-based systems we have <c>sparc-sources</c> (2.4 kernel sources |
14726 |
optimized for SPARC users) and <c>gentoo-sources</c> (recommended 2.6 kernel |
14727 |
sources). |
14728 |
</p> |
14729 |
|
14730 |
<p> |
14731 |
In the next example we install the <c>gentoo-sources</c>. Of course substitute |
14732 |
with your choice of sources, this is merely an example. |
14733 |
</p> |
14734 |
|
14735 |
<pre caption="Installing a kernel source"> |
14736 |
# <i>emerge gentoo-sources</i> |
14737 |
</pre> |
14738 |
|
14739 |
<p> |
14740 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
14741 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
14742 |
kernel source points to <c>linux-2.6.17-gentoo-r5</c>. Your version may be |
14743 |
different, so keep this in mind. |
14744 |
</p> |
14745 |
|
14746 |
<pre caption="Viewing the kernel source symlink"> |
14747 |
# <i>ls -l /usr/src/linux</i> |
14748 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-2.6.17-gentoo-r5 |
14749 |
</pre> |
14750 |
|
14751 |
<p> |
14752 |
Now it is time to configure and compile your kernel source. |
14753 |
</p> |
14754 |
|
14755 |
</body> |
14756 |
</subsection> |
14757 |
</section> |
14758 |
<section> |
14759 |
<title>Manual Configuration</title> |
14760 |
<subsection> |
14761 |
<title>Introduction</title> |
14762 |
<body> |
14763 |
|
14764 |
<p> |
14765 |
Manually configuring a kernel is often seen as the most difficult procedure a |
14766 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
14767 |
couple of kernels you don't even remember that it was difficult ;) |
14768 |
</p> |
14769 |
|
14770 |
<p> |
14771 |
However, one thing <e>is</e> true: you must know your system when you start |
14772 |
configuring a kernel manually. Most information can be gathered by emerging |
14773 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
14774 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
14775 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
14776 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
14777 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
14778 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
14779 |
uses (it might provide you with a nice hint on what to enable). |
14780 |
</p> |
14781 |
|
14782 |
<p> |
14783 |
Now go to your kernel source directory and execute <c>make menuconfig</c>. This |
14784 |
will fire up an ncurses-based configuration menu. |
14785 |
</p> |
14786 |
|
14787 |
<pre caption="Invoking menuconfig"> |
14788 |
# <i>cd /usr/src/linux</i> |
14789 |
# <i>make menuconfig</i> |
14790 |
</pre> |
14791 |
|
14792 |
<p> |
14793 |
You will be greeted with several configuration sections. We'll first list some |
14794 |
options you must activate (otherwise Gentoo will not function, or not function |
14795 |
properly without additional tweaks). |
14796 |
</p> |
14797 |
|
14798 |
</body> |
14799 |
</subsection> |
14800 |
<subsection> |
14801 |
<title>Activating Required Options</title> |
14802 |
<body> |
14803 |
|
14804 |
<p> |
14805 |
First of all, activate the use of development and experimental code/drivers. |
14806 |
You need this, otherwise some very important code/drivers won't show up: |
14807 |
</p> |
14808 |
|
14809 |
<pre caption="Selecting experimental code/drivers"> |
14810 |
Code maturity level options ---> |
14811 |
[*] Prompt for development and/or incomplete code/drivers |
14812 |
</pre> |
14813 |
|
14814 |
<p> |
14815 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
14816 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
14817 |
able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc |
14818 |
file system</c>. If you are running a 2.4 kernel, you should also select |
14819 |
<c>/dev file system</c> + <c>Automatically mount at boot</c>: |
14820 |
</p> |
14821 |
|
14822 |
<pre caption="Selecting necessary file systems"> |
14823 |
File systems ---> |
14824 |
[*] Virtual memory file system support (former shm fs) |
14825 |
[*] /proc file system support |
14826 |
[ ] /dev/pts file system for Unix98 PTYs |
14827 |
|
14828 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
14829 |
<*> Ext3 journalling file system support |
14830 |
<*> Second extended fs support |
14831 |
</pre> |
14832 |
|
14833 |
<p> |
14834 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
14835 |
modem, you will need the following options in the kernel: |
14836 |
</p> |
14837 |
|
14838 |
<pre caption="Selecting PPPoE necessary drivers"> |
14839 |
Network device support ---> |
14840 |
<*> PPP (point-to-point protocol) support |
14841 |
<*> PPP support for async serial ports |
14842 |
<*> PPP support for sync tty ports |
14843 |
</pre> |
14844 |
|
14845 |
<p> |
14846 |
The two compression options won't harm but are not definitely needed, neither |
14847 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
14848 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
14849 |
</p> |
14850 |
|
14851 |
<p> |
14852 |
Now activate the correct bus-support: |
14853 |
</p> |
14854 |
|
14855 |
<pre caption="Activating SBUS/UPA"> |
14856 |
Console drivers ---> |
14857 |
Frame-buffer support ---> |
14858 |
[*] SBUS and UPA framebuffers |
14859 |
[*] Creator/Creator3D support <comment>(Only for UPA slot adapter used in many Ultras)</comment> |
14860 |
[*] CGsix (GX,TurboGX) support <comment>(Only for SBUS slot adapter used in many SPARCStations)</comment> |
14861 |
</pre> |
14862 |
|
14863 |
<p> |
14864 |
Of course you want support for the OBP: |
14865 |
</p> |
14866 |
|
14867 |
<pre caption="Activating OBP Support"> |
14868 |
Misc Linux/SPARC drivers ---> |
14869 |
[*] /dev/openprom device support |
14870 |
</pre> |
14871 |
|
14872 |
<p> |
14873 |
You will also need SCSI-specific support: |
14874 |
</p> |
14875 |
|
14876 |
<pre caption="Activating SCSI-specific support"> |
14877 |
SCSI support ---> |
14878 |
SCSI low-level drivers ---> |
14879 |
<*> Sparc ESP Scsi Driver <comment>(Only for SPARC ESP on-board SCSI adapter)</comment> |
14880 |
<*> PTI Qlogic, ISP Driver <comment>(Only for SBUS SCSI controllers from PTI or QLogic)</comment> |
14881 |
<*> SYM53C8XX Version 2 SCSI support <comment>(Only for Ultra 60 on-board SCSI adapter)</comment> |
14882 |
</pre> |
14883 |
|
14884 |
<p> |
14885 |
To support your network card, select one of the following: |
14886 |
</p> |
14887 |
|
14888 |
<pre caption="Activating networking support"> |
14889 |
Network device support ---> |
14890 |
Ethernet (10 or 100Mbit) ---> |
14891 |
<*> Sun LANCE support <comment>(Only for SPARCStation, older Ultra systems, and as Sbus option)</comment> |
14892 |
<*> Sun Happy Meal 10/100baseT support <comment>(Only for Ultra; also supports "qfe" quad-ethernet on PCI and Sbus)</comment> |
14893 |
<*> DECchip Tulip (dc21x4x) PCI support <comment>(For some Netras, like N1)</comment> |
14894 |
Ethernet (1000Mbit) ---> |
14895 |
<*> Broadcom Tigon3 support <comment>(Modern Netra, Sun Fire machines)</comment> |
14896 |
</pre> |
14897 |
|
14898 |
<p> |
14899 |
When you have a 4-port Ethernet machine (10/100 or 10/100/1000) the port order |
14900 |
is different from the one used by Solaris. You can use <c>sys-apps/ethtool</c> |
14901 |
to check the port link status. |
14902 |
</p> |
14903 |
|
14904 |
<p> |
14905 |
When you're done configuring your kernel, continue with <uri |
14906 |
link="#compiling">Compiling and Installing</uri>. However, after having |
14907 |
compiled the kernel, check its size: |
14908 |
</p> |
14909 |
|
14910 |
<pre caption="Check kernel size"> |
14911 |
# <i>ls -lh vmlinux</i> |
14912 |
-rw-r--r-- 1 root root 2.4M Oct 25 14:38 vmlinux |
14913 |
</pre> |
14914 |
|
14915 |
<p> |
14916 |
If the (uncompressed) size is bigger than 2.5 MB (for Sparc32) or 3.5 MB (for |
14917 |
Sparc64), reconfigure your kernel until it doesn't exceed these limits. One way |
14918 |
of accomplishing this is by having most kernel drivers compiled as modules. |
14919 |
Ignoring this can lead to a non-booting kernel. |
14920 |
</p> |
14921 |
|
14922 |
<p> |
14923 |
Also, if your kernel is just a tad too big, you can try stripping it using the |
14924 |
<c>strip</c> command: |
14925 |
</p> |
14926 |
|
14927 |
<pre caption="Stripping the kernel"> |
14928 |
# <i>strip -R .comment -R .note vmlinux</i> |
14929 |
</pre> |
14930 |
|
14931 |
</body> |
14932 |
</subsection> |
14933 |
<subsection id="compiling"> |
14934 |
<title>Compiling and Installing</title> |
14935 |
<body> |
14936 |
|
14937 |
<p> |
14938 |
Now that your kernel is configured, it is time to compile and install it. Exit |
14939 |
the configuration and start the compilation process: |
14940 |
</p> |
14941 |
|
14942 |
<pre caption="Compiling the kernel"> |
14943 |
<comment>(sparc32)</comment> |
14944 |
# <i>make dep && make clean vmlinux modules modules_install</i> |
14945 |
|
14946 |
<comment>(sparc64)</comment> |
14947 |
# <i>make dep && make clean vmlinux image modules modules_install</i> |
14948 |
</pre> |
14949 |
|
14950 |
<p> |
14951 |
When the kernel has finished compiling, copy the kernel image to |
14952 |
<path>/boot</path>. Remember to replace <path><kernel-version></path> |
14953 |
with your actual kernel version. |
14954 |
</p> |
14955 |
|
14956 |
<pre caption="Installing the kernel"> |
14957 |
<comment>(sparc32)</comment> |
14958 |
# <i>cp vmlinux /boot/<kernel-version></i> |
14959 |
|
14960 |
<comment>(sparc64)</comment> |
14961 |
# <i>cp arch/sparc64/boot/image /boot/<kernel-version></i> |
14962 |
</pre> |
14963 |
|
14964 |
<p> |
14965 |
Now continue with <uri link="#kernel_modules">Installing Separate Kernel |
14966 |
Modules</uri>. |
14967 |
</p> |
14968 |
|
14969 |
</body> |
14970 |
</subsection> |
14971 |
</section> |
14972 |
<section id="kernel_modules"> |
14973 |
<title>Installing Separate Kernel Modules</title> |
14974 |
<subsection> |
14975 |
<title>Configuring the Modules</title> |
14976 |
<body> |
14977 |
|
14978 |
<p> |
14979 |
You should list the modules you want automatically loaded in |
14980 |
<path>/etc/modules.autoload.d/kernel-2.6</path>. |
14981 |
You can add extra options to the modules too if you want. |
14982 |
</p> |
14983 |
|
14984 |
<p> |
14985 |
To view all available modules, run the following <c>find</c> command. Don't |
14986 |
forget to substitute "<kernel version>" with the version of the kernel you |
14987 |
just compiled: |
14988 |
</p> |
14989 |
|
14990 |
<pre caption="Viewing all available modules"> |
14991 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
14992 |
</pre> |
14993 |
|
14994 |
<p> |
14995 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
14996 |
<path>kernel-2.6</path> file and enter the module name in it. |
14997 |
</p> |
14998 |
|
14999 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
15000 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
15001 |
</pre> |
15002 |
|
15003 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
15004 |
3c59x |
15005 |
</pre> |
15006 |
|
15007 |
<p> |
15008 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
15009 |
your System</uri>. |
15010 |
</p> |
15011 |
|
15012 |
</body> |
15013 |
</subsection> |
15014 |
</section> |
15015 |
</sections> |
15016 |
|
15017 |
|
15018 |
|
15019 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-sparc-medium.xml |
15020 |
|
15021 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-sparc-medium.xml?rev=1.1&view=markup |
15022 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-sparc-medium.xml?rev=1.1&content-type=text/plain |
15023 |
|
15024 |
Index: hb-install-sparc-medium.xml |
15025 |
=================================================================== |
15026 |
<?xml version='1.0' encoding='UTF-8'?> |
15027 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
15028 |
|
15029 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
15030 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
15031 |
|
15032 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-sparc-medium.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
15033 |
|
15034 |
<sections> |
15035 |
|
15036 |
<version>7.0</version> |
15037 |
<date>2006-08-30</date> |
15038 |
|
15039 |
<section> |
15040 |
<title>Hardware Requirements</title> |
15041 |
<subsection> |
15042 |
<title>Introduction</title> |
15043 |
<body> |
15044 |
|
15045 |
<p> |
15046 |
Before we start, we first list what hardware requirements you need to |
15047 |
successfully install Gentoo on your box. |
15048 |
</p> |
15049 |
|
15050 |
</body> |
15051 |
</subsection> |
15052 |
<subsection> |
15053 |
<title>Hardware Requirements</title> |
15054 |
<body> |
15055 |
|
15056 |
<table> |
15057 |
<tr> |
15058 |
<th>Sparc System</th> |
15059 |
<ti> |
15060 |
Please check the <uri link="/proj/en/base/sparc/sunhw.xml">Gentoo |
15061 |
Linux/SPARC64 Compatibility list</uri> or the <uri |
15062 |
link="http://www.ultralinux.org/faq.html#s_2">UltraLinux FAQ</uri> |
15063 |
</ti> |
15064 |
</tr> |
15065 |
<tr> |
15066 |
<th>CPU</th> |
15067 |
<ti> |
15068 |
Although sparc64 is the only officially supported platform, experimental |
15069 |
support for sparc32 is available as well |
15070 |
</ti> |
15071 |
</tr> |
15072 |
<tr> |
15073 |
<th>Memory</th> |
15074 |
<ti>64 MB</ti> |
15075 |
</tr> |
15076 |
<tr> |
15077 |
<th>Diskspace</th> |
15078 |
<ti>1.5 GB (excluding swap space)</ti> |
15079 |
</tr> |
15080 |
<tr> |
15081 |
<th>Swap space</th> |
15082 |
<ti>At least 256 MB</ti> |
15083 |
</tr> |
15084 |
</table> |
15085 |
|
15086 |
<p> |
15087 |
We currently only provide Installation CDs for the sparc64 architecture. Users |
15088 |
of sparc32 can use the experimental netboot images to install Gentoo from. |
15089 |
More information about netbooting can be found in our <uri |
15090 |
link="/doc/en/gentoo-sparc-netboot-howto.xml">Gentoo Linux based Netboot |
15091 |
HOWTO</uri>. |
15092 |
</p> |
15093 |
|
15094 |
</body> |
15095 |
</subsection> |
15096 |
</section> |
15097 |
<!-- Copy/Paste from hb-install-x86-medium.xml --> |
15098 |
<!-- START --> |
15099 |
<section> |
15100 |
<title>The Gentoo Universal Installation CD</title> |
15101 |
<subsection> |
15102 |
<title>Introduction</title> |
15103 |
<body> |
15104 |
|
15105 |
<p> |
15106 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
15107 |
Such a tarball is an archive that contains a minimal environment from |
15108 |
which you can succesfully install Gentoo Linux onto your system. |
15109 |
</p> |
15110 |
|
15111 |
<p> |
15112 |
Installations using a stage1 or stage2 tarball file are not documented in the |
15113 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
15114 |
FAQ</uri> on these matters. |
15115 |
</p> |
15116 |
|
15117 |
</body> |
15118 |
</subsection> |
15119 |
<subsection> |
15120 |
<title>Gentoo Universal Installation CD</title> |
15121 |
<body> |
15122 |
|
15123 |
<p> |
15124 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
15125 |
environment. It allows you to boot Linux from the CD. During the boot process |
15126 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
15127 |
Installation CDs are maintained by Gentoo developers. |
15128 |
</p> |
15129 |
|
15130 |
<p> |
15131 |
There currently are two Installation CDs available: |
15132 |
</p> |
15133 |
|
15134 |
<ul> |
15135 |
<li> |
15136 |
The Universal Installation CD contains everything you need to install |
15137 |
Gentoo. It provides stage3 files for common architectures, source code |
15138 |
for the extra applications you need to choose from and, of course, the |
15139 |
installation instructions for your architecture. |
15140 |
</li> |
15141 |
<li> |
15142 |
The Minimal Installation CD contains only a minimal environment that allows |
15143 |
you to boot up and configure your network so you can connect to the |
15144 |
Internet. It does not contain any additional files and cannot be used |
15145 |
during the current installation approach. |
15146 |
</li> |
15147 |
</ul> |
15148 |
|
15149 |
<p> |
15150 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
15151 |
additional resource that you can exploit during the installation of your Gentoo |
15152 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
15153 |
you to easily and quickly install additional applications (such as |
15154 |
OpenOffice.org, KDE, GNOME, ...) immediately after the Gentoo installation and |
15155 |
right before you update your Portage tree. |
15156 |
</p> |
15157 |
|
15158 |
<p> |
15159 |
The use of the Package CD is covered later in this document. |
15160 |
</p> |
15161 |
|
15162 |
</body> |
15163 |
</subsection> |
15164 |
</section> |
15165 |
<!-- STOP --> |
15166 |
<section> |
15167 |
<title>Download, Burn and Boot a Gentoo Installation CD</title> |
15168 |
<subsection> |
15169 |
<title>Downloading and Burning the Installation CDs</title> |
15170 |
<body> |
15171 |
|
15172 |
<p> |
15173 |
You can download the Universal Installation CD (and, if you want to, the |
15174 |
Packages CD as well) from one of our <uri |
15175 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located in |
15176 |
the <path>releases/sparc/2006.1/sparc64/installcd</path> |
15177 |
directory; the Package CDs are located in the |
15178 |
<path>releases/sparc/2006.1/sparc64/packagecd</path> directory. |
15179 |
</p> |
15180 |
|
15181 |
<p> |
15182 |
Inside those directories you'll find ISO-files. Those are full CD images which |
15183 |
you can write on a CD-R. |
15184 |
</p> |
15185 |
|
15186 |
<p> |
15187 |
After downloading the file, you can verify its integrity to see if it is |
15188 |
corrupted or not: |
15189 |
</p> |
15190 |
|
15191 |
<ul> |
15192 |
<li> |
15193 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
15194 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
15195 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows) |
15196 |
</li> |
15197 |
<li> |
15198 |
You can verify the cryptographic signature that we provide. You need to |
15199 |
obtain the public key we use (17072058) before you proceed though. |
15200 |
</li> |
15201 |
</ul> |
15202 |
|
15203 |
<p> |
15204 |
To fetch our public key using the GnuPG application, run the following command: |
15205 |
</p> |
15206 |
|
15207 |
<pre caption="Obtaining the public key"> |
15208 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
15209 |
</pre> |
15210 |
|
15211 |
<p> |
15212 |
Now verify the signature: |
15213 |
</p> |
15214 |
|
15215 |
<pre caption="Verify the cryptographic signature"> |
15216 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
15217 |
</pre> |
15218 |
|
15219 |
<p> |
15220 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
15221 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
15222 |
<c>K3B</c> here; more information can be found in our <uri |
15223 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
15224 |
</p> |
15225 |
|
15226 |
<ul> |
15227 |
<li> |
15228 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded |
15229 |
iso></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
15230 |
path). |
15231 |
</li> |
15232 |
<li> |
15233 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
15234 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
15235 |
<c>Start</c>. |
15236 |
</li> |
15237 |
</ul> |
15238 |
|
15239 |
</body> |
15240 |
</subsection> |
15241 |
<subsection> |
15242 |
<title>Booting the Universal Installation CD</title> |
15243 |
<body> |
15244 |
|
15245 |
<p> |
15246 |
Insert the Gentoo Installation CD in the CD-ROM and boot your system. During |
15247 |
startup, press Stop-A to enter OpenBootPROM (OBP). Once you are in the OBP, |
15248 |
boot from the CD-ROM: |
15249 |
</p> |
15250 |
|
15251 |
<pre caption="Booting the Installation CD"> |
15252 |
ok <i>boot cdrom</i> |
15253 |
</pre> |
15254 |
|
15255 |
<p> |
15256 |
You will be greeted by the SILO boot manager (on the Installation CD). Type in |
15257 |
<c>2616</c> to use 2.6.16 kernel or <c>2617</c> to use 2.6.17 kernel and press |
15258 |
enter to continue booting the system. <c>2616</c> was tested more extensively |
15259 |
so it's the option you should choose if default <c>2617</c> doesn't work for |
15260 |
you. If you want to have support for the newer Sun boxes (Niagara, UltraSPARC, |
15261 |
T1), you should choose default <c>2617</c>. |
15262 |
</p> |
15263 |
|
15264 |
<pre caption="Continue booting from the Installation CD"> |
15265 |
boot: <i>2617</i> |
15266 |
</pre> |
15267 |
|
15268 |
<p> |
15269 |
Once the Installation CD is booted, you will be automatically logged on to the |
15270 |
system. |
15271 |
</p> |
15272 |
|
15273 |
<p> |
15274 |
You should have a root ("#") prompt on the current console and can also switch |
15275 |
to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get back to the one you |
15276 |
started on by pressing Alt-F1. You will also find a root prompt on the serial |
15277 |
console (<path>ttyS0</path>). |
15278 |
</p> |
15279 |
|
15280 |
<p> |
15281 |
Continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
15282 |
</p> |
15283 |
|
15284 |
</body> |
15285 |
</subsection> |
15286 |
<subsection id="hardware"> |
15287 |
<title>Extra Hardware Configuration</title> |
15288 |
<body> |
15289 |
|
15290 |
<p> |
15291 |
If not all hardware is supported out-of-the-box, you will need to load the |
15292 |
appropriate kernel modules. |
15293 |
</p> |
15294 |
|
15295 |
<p> |
15296 |
In the next example we try to load the <c>8139too</c> module (support for |
15297 |
certain kinds of network interfaces): |
15298 |
</p> |
15299 |
|
15300 |
<pre caption="Loading kernel modules"> |
15301 |
# <i>modprobe 8139too</i> |
15302 |
</pre> |
15303 |
|
15304 |
</body> |
15305 |
</subsection> |
15306 |
<subsection id="useraccounts"> |
15307 |
<title>Optional: User Accounts</title> |
15308 |
<body> |
15309 |
|
15310 |
<p> |
15311 |
If you plan on giving other people access to your installation |
15312 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
15313 |
security reasons), you need to create the necessary user accounts and change |
15314 |
the root password. |
15315 |
</p> |
15316 |
|
15317 |
<p> |
15318 |
To change the root password, use the <c>passwd</c> utility: |
15319 |
</p> |
15320 |
|
15321 |
<pre caption="Changing the root password"> |
15322 |
# <i>passwd</i> |
15323 |
New password: <comment>(Enter your new password)</comment> |
15324 |
Re-enter password: <comment>(Re-enter your password)</comment> |
15325 |
</pre> |
15326 |
|
15327 |
<p> |
15328 |
To create a user account, we first enter their credentials, followed by |
15329 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
15330 |
In the next example, we create a user called "john". |
15331 |
</p> |
15332 |
|
15333 |
<pre caption="Creating a user account"> |
15334 |
# <i>useradd -m -G users john</i> |
15335 |
# <i>passwd john</i> |
15336 |
New password: <comment>(Enter john's password)</comment> |
15337 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
15338 |
</pre> |
15339 |
|
15340 |
<p> |
15341 |
You can change your user id from root to the newly created user by using |
15342 |
<c>su</c>: |
15343 |
</p> |
15344 |
|
15345 |
<pre caption="Changing user id"> |
15346 |
# <i>su - john</i> |
15347 |
</pre> |
15348 |
|
15349 |
</body> |
15350 |
</subsection> |
15351 |
<subsection> |
15352 |
<title>Optional: Viewing Documentation while Installing</title> |
15353 |
<body> |
15354 |
|
15355 |
<p> |
15356 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
15357 |
installation, make sure you have created a user account (see <uri |
15358 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
15359 |
go to a new terminal and log in. |
15360 |
</p> |
15361 |
|
15362 |
<p> |
15363 |
If you want to view the documentation on the CD you can immediately run |
15364 |
<c>links</c> to read it: |
15365 |
</p> |
15366 |
|
15367 |
<pre caption="Viewing the on-CD documentation"> |
15368 |
# <i>links /mnt/cdrom/docs/handbook/html/index.html</i> |
15369 |
</pre> |
15370 |
|
15371 |
<p> |
15372 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
15373 |
more recent than the one provided on the CD. You can view it using <c>links</c> |
15374 |
as well, but only after having completed the <e>Configuring your Network</e> |
15375 |
chapter (otherwise you won't be able to go on the Internet to view the |
15376 |
document): |
15377 |
</p> |
15378 |
|
15379 |
<pre caption="Viewing the Online Documentation"> |
15380 |
# <i>links http://www.gentoo.org/doc/en/handbook/handbook-sparc.xml</i> |
15381 |
</pre> |
15382 |
|
15383 |
<p> |
15384 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
15385 |
</p> |
15386 |
|
15387 |
</body> |
15388 |
</subsection> |
15389 |
<subsection> |
15390 |
<title>Optional: Starting the SSH Daemon</title> |
15391 |
<body> |
15392 |
|
15393 |
<p> |
15394 |
If you want to allow other users to access your computer during the |
15395 |
Gentoo installation (perhaps because those users are going to help you |
15396 |
install Gentoo, or even do it for you), you need to create a user |
15397 |
account for them and perhaps even provide them with your root password |
15398 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
15399 |
</p> |
15400 |
|
15401 |
<p> |
15402 |
To fire up the SSH daemon, execute the following command: |
15403 |
</p> |
15404 |
|
15405 |
<pre caption="Starting the SSH daemon"> |
15406 |
# <i>/etc/init.d/sshd start</i> |
15407 |
</pre> |
15408 |
|
15409 |
<p> |
15410 |
To be able to use sshd, you first need to set up your networking. Continue with |
15411 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
15412 |
</p> |
15413 |
|
15414 |
</body> |
15415 |
</subsection> |
15416 |
</section> |
15417 |
</sections> |
15418 |
|
15419 |
|
15420 |
|
15421 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-stage.xml |
15422 |
|
15423 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-stage.xml?rev=1.1&view=markup |
15424 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-stage.xml?rev=1.1&content-type=text/plain |
15425 |
|
15426 |
Index: hb-install-stage.xml |
15427 |
=================================================================== |
15428 |
<?xml version='1.0' encoding='UTF-8'?> |
15429 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
15430 |
|
15431 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
15432 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
15433 |
|
15434 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-stage.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
15435 |
|
15436 |
<sections> |
15437 |
|
15438 |
<version>7.1</version> |
15439 |
<date>2006-10-31</date> |
15440 |
|
15441 |
<section> |
15442 |
<title>Installing a Stage Tarball</title> |
15443 |
<subsection> |
15444 |
<title>Setting the Date/Time Right</title> |
15445 |
<body> |
15446 |
|
15447 |
<p> |
15448 |
Before you continue you need to check your date/time and update it. A |
15449 |
misconfigured clock may lead to strange results in the future! |
15450 |
</p> |
15451 |
|
15452 |
<p> |
15453 |
To verify the current date/time, run <c>date</c>: |
15454 |
</p> |
15455 |
|
15456 |
<pre caption="Verifying the date/time"> |
15457 |
# <i>date</i> |
15458 |
Fri Mar 29 16:21:18 UTC 2005 |
15459 |
</pre> |
15460 |
|
15461 |
<p> |
15462 |
If the date/time displayed is wrong, update it using the <c>date |
15463 |
MMDDhhmmYYYY</c> syntax (<b>M</b>onth, <b>D</b>ay, <b>h</b>our, <b>m</b>inute |
15464 |
and <b>Y</b>ear). At this stage, you should use UTC time. You will be able to |
15465 |
define your timezone later on. For instance, to set the date to March 29th, |
15466 |
16:21 in the year 2005: |
15467 |
</p> |
15468 |
|
15469 |
<pre caption="Setting the UTC date/time"> |
15470 |
# <i>date 032916212005</i> |
15471 |
</pre> |
15472 |
|
15473 |
</body> |
15474 |
</subsection> |
15475 |
<subsection> |
15476 |
<title>Locating the Stage3 File</title> |
15477 |
<body> |
15478 |
|
15479 |
<p> |
15480 |
If you have configured networking because you need to download a stage3 file for |
15481 |
your architecture, continue with <uri link="#download">Alternative: Using a |
15482 |
Stage3 from the Internet</uri>. Otherwise read <uri link="#available">Default: |
15483 |
Using a Stage3 from the Installation CD</uri>. |
15484 |
</p> |
15485 |
|
15486 |
</body> |
15487 |
</subsection> |
15488 |
</section> |
15489 |
<section id="available"> |
15490 |
<title>Default: Using a Stage from the Installation CD</title> |
15491 |
<subsection> |
15492 |
<title>Extracting the Stage Tarball</title> |
15493 |
<body> |
15494 |
|
15495 |
<p> |
15496 |
The stages on the CD reside in the <path>/mnt/cdrom/stages</path> directory. To |
15497 |
see a listing of available stages, use <c>ls</c>: |
15498 |
</p> |
15499 |
|
15500 |
<pre caption="List all available stages"> |
15501 |
# <i>ls /mnt/cdrom/stages</i> |
15502 |
</pre> |
15503 |
|
15504 |
<p> |
15505 |
If the system replies with an error, you may need to mount the CD-ROM first: |
15506 |
</p> |
15507 |
|
15508 |
<pre caption="Mounting the CD-ROM"> |
15509 |
# <i>ls /mnt/cdrom/stages</i> |
15510 |
ls: /mnt/cdrom/stages: No such file or directory |
15511 |
# <i>mount /dev/cdroms/cdrom0 /mnt/cdrom</i> |
15512 |
# <i>ls /mnt/cdrom/stages</i> |
15513 |
</pre> |
15514 |
|
15515 |
<p> |
15516 |
Now go into your Gentoo mountpoint (usually <path>/mnt/gentoo</path>): |
15517 |
</p> |
15518 |
|
15519 |
<pre caption="Changing directory to /mnt/gentoo"> |
15520 |
# <i>cd /mnt/gentoo</i> |
15521 |
</pre> |
15522 |
|
15523 |
<p> |
15524 |
We will now extract the stage tarball of your choice. We will do this with the |
15525 |
<c>tar</c> tool. Make sure you use the same options (<c>xvjpf</c>)! The |
15526 |
<c>x</c> stands for <e>Extract</e>, the <c>v</c> for <e>Verbose</e> to see what |
15527 |
happens during the extraction process (this one is optional), the <c>j</c> for |
15528 |
<e>Decompress with bzip2</e>, the <c>p</c> for <e>Preserve permissions</e> and |
15529 |
the <c>f</c> to denote that we want to extract a file, not standard input. In |
15530 |
the next example, we extract the stage tarball |
15531 |
<path>stage3-<subarch>-2006.1.tar.bz2</path>. Be sure to substitute |
15532 |
the tarball filename with your stage. |
15533 |
</p> |
15534 |
|
15535 |
<pre caption="Extracting the stage tarball"> |
15536 |
# <i>tar xvjpf /mnt/cdrom/stages/stage3-<subarch>-2006.1.tar.bz2</i> |
15537 |
</pre> |
15538 |
|
15539 |
<p> |
15540 |
Now that the stage is installed, continue with <uri |
15541 |
link="#installing_portage">Installing Portage</uri>. |
15542 |
</p> |
15543 |
|
15544 |
</body> |
15545 |
</subsection> |
15546 |
</section> |
15547 |
<section id="download"> |
15548 |
<title>Alternative: Using a Stage from the Internet</title> |
15549 |
<subsection> |
15550 |
<title>Downloading the Stage Tarball</title> |
15551 |
<body> |
15552 |
|
15553 |
<p> |
15554 |
Go to the Gentoo mountpoint at which you mounted your filesystems |
15555 |
(most likely <path>/mnt/gentoo</path>): |
15556 |
</p> |
15557 |
|
15558 |
<pre caption="Going to the Gentoo mountpoint"> |
15559 |
# <i>cd /mnt/gentoo</i> |
15560 |
</pre> |
15561 |
|
15562 |
<p> |
15563 |
Depending on your installation medium, you have a couple of tools available to |
15564 |
download a stage. If you have <c>links</c> available, then you can immediately |
15565 |
surf to <uri link="/main/en/mirrors.xml">the Gentoo mirrorlist</uri> and |
15566 |
choose a mirror close to you. |
15567 |
</p> |
15568 |
|
15569 |
<p> |
15570 |
If you don't have <c>links</c> available you should have <c>lynx</c> at your |
15571 |
disposal. If you need to go through a proxy, export the <c>http_proxy</c> and |
15572 |
<c>ftp_proxy</c> variables: |
15573 |
</p> |
15574 |
|
15575 |
<pre caption="Setting proxy information for lynx"> |
15576 |
# <i>export http_proxy="http://proxy.server.com:port"</i> |
15577 |
# <i>export ftp_proxy="http://proxy.server.com:port"</i> |
15578 |
</pre> |
15579 |
|
15580 |
<p> |
15581 |
We will now assume that you have <c>links</c> at your disposal. |
15582 |
</p> |
15583 |
|
15584 |
<p> |
15585 |
Pick the <path>releases/</path> directory, followed by your architecture (for |
15586 |
instance <path>x86/</path>) and the Gentoo version (<path>2006.1/</path>) to |
15587 |
finish up with the <path>stages/</path> directory. There you should see all |
15588 |
available stage files for your architecture (they might be stored within |
15589 |
subdirectories named to the individual subarchitectures). Select one and press |
15590 |
<c>D</c> to download. When you're finished, press <c>Q</c> to quit the browser. |
15591 |
</p> |
15592 |
|
15593 |
<pre caption="Surfing to the mirror listing with links"> |
15594 |
# <i>links http://www.gentoo.org/main/en/mirrors.xml</i> |
15595 |
|
15596 |
<comment>(If you need proxy support with links:)</comment> |
15597 |
# <i>links -http-proxy proxy.server.com:8080 http://www.gentoo.org/main/en/mirrors.xml</i> |
15598 |
</pre> |
15599 |
|
15600 |
<p> |
15601 |
Make sure you download a stage3 tarball - installations using a stage1 or stage2 |
15602 |
tarball are not supported anymore. |
15603 |
</p> |
15604 |
|
15605 |
<p> |
15606 |
If you want to check the integrity of the downloaded stage tarball, use |
15607 |
<c>md5sum</c> and compare the output with the MD5 checksum provided on the |
15608 |
mirror. For instance, to check the validity of the x86 stage tarball: |
15609 |
</p> |
15610 |
|
15611 |
<pre caption="Example checking integrity of a stage tarball"> |
15612 |
# <i>md5sum -c stage3-x86-2006.1.tar.bz2.DIGESTS</i> |
15613 |
stage3-x86-2006.1.tar.bz2: OK |
15614 |
</pre> |
15615 |
|
15616 |
</body> |
15617 |
</subsection> |
15618 |
<subsection> |
15619 |
<title>Unpacking the Stage Tarball</title> |
15620 |
<body> |
15621 |
|
15622 |
<p> |
15623 |
Now unpack your downloaded stage onto your system. We use <c>tar</c> to proceed |
15624 |
as it is the easiest method: |
15625 |
</p> |
15626 |
|
15627 |
<pre caption="Unpacking the stage"> |
15628 |
# <i>tar xvjpf stage3-*.tar.bz2</i> |
15629 |
</pre> |
15630 |
|
15631 |
<p> |
15632 |
Make sure that you use the same options (<c>xvjpf</c>). The <c>x</c> stands |
15633 |
for <e>Extract</e>, the <c>v</c> for <e>Verbose</e> to see what happens during |
15634 |
the extraction process (this one is optional), the <c>j</c> for <e>Decompress |
15635 |
with bzip2</e>, the <c>p</c> for <e>Preserve permissions</e> and the <c>f</c> |
15636 |
to denote that we want to extract a file, not standard input. |
15637 |
</p> |
15638 |
|
15639 |
<p> |
15640 |
Now that the stage is installed, continue with <uri |
15641 |
link="#installing_portage">Installing Portage</uri>. |
15642 |
</p> |
15643 |
|
15644 |
</body> |
15645 |
</subsection> |
15646 |
</section> |
15647 |
<section id="installing_portage"> |
15648 |
<title>Installing Portage</title> |
15649 |
<subsection> |
15650 |
<title>Unpacking a Portage Snapshot</title> |
15651 |
<body> |
15652 |
|
15653 |
<p> |
15654 |
You now have to install a Portage snapshot, a collection of files that inform |
15655 |
Portage what software titles you can install, which profiles are available, etc. |
15656 |
</p> |
15657 |
|
15658 |
</body> |
15659 |
</subsection> |
15660 |
<subsection id="installing_from_InstallCD"> |
15661 |
<title>Unpack the Snapshot from the Installation CD</title> |
15662 |
<body> |
15663 |
|
15664 |
<p> |
15665 |
To install the snapshot, take a look inside <path>/mnt/cdrom/snapshots/</path> |
15666 |
to see what snapshot is available: |
15667 |
</p> |
15668 |
|
15669 |
<pre caption="Checking the /mnt/cdrom/snapshots content"> |
15670 |
# <i>ls /mnt/cdrom/snapshots</i> |
15671 |
</pre> |
15672 |
|
15673 |
<p> |
15674 |
Now extract the snapshot using the following construct. Again, make sure you |
15675 |
use the correct options with <c>tar</c>. Also, the <c>-C</c> is with a capital |
15676 |
<c>C</c>, not <c>c</c>. In the next example we use |
15677 |
<path>portage-<date>.tar.bz2</path> as the snapshot filename. Be sure to |
15678 |
substitute with the name of the snapshot that is on your Installation CD. |
15679 |
</p> |
15680 |
|
15681 |
<pre caption="Extracting a Portage snapshot"> |
15682 |
# <i>tar xvjf /mnt/cdrom/snapshots/portage-<date>.tar.bz2 -C /mnt/gentoo/usr</i> |
15683 |
</pre> |
15684 |
|
15685 |
</body> |
15686 |
</subsection> |
15687 |
<subsection id="copysources"> |
15688 |
<title>Copy Source Code Archives</title> |
15689 |
<body> |
15690 |
|
15691 |
<p> |
15692 |
You also need to copy over all source code from the Universal Installation CD. |
15693 |
</p> |
15694 |
|
15695 |
<pre caption="Copy over source code"> |
15696 |
# <i>mkdir /mnt/gentoo/usr/portage/distfiles</i> |
15697 |
# <i>cp /mnt/cdrom/distfiles/* /mnt/gentoo/usr/portage/distfiles/</i> |
15698 |
</pre> |
15699 |
|
15700 |
</body> |
15701 |
</subsection> |
15702 |
</section> |
15703 |
<section id="compile_options"> |
15704 |
<title>Configuring the Compile Options</title> |
15705 |
<subsection> |
15706 |
<title>Introduction</title> |
15707 |
<body> |
15708 |
|
15709 |
<p> |
15710 |
To optimize Gentoo, you can set a couple of variables which impact Portage |
15711 |
behaviour. All those variables can be set as environment variables (using |
15712 |
<c>export</c>) but that isn't permanent. To keep your settings, Portage provides |
15713 |
you with <path>/etc/make.conf</path>, a configuration file for Portage. It is |
15714 |
this file we will edit now. |
15715 |
</p> |
15716 |
|
15717 |
<note> |
15718 |
A commented listing of all possible variables can be found in |
15719 |
<path>/mnt/gentoo/etc/make.conf.example</path>. For a successful Gentoo |
15720 |
installation you'll only need to set the variables which are mentioned beneath. |
15721 |
</note> |
15722 |
|
15723 |
<p> |
15724 |
Fire up your favorite editor (in this guide we use <c>nano</c>) so we can alter |
15725 |
the optimization variables we will discuss hereafter. |
15726 |
</p> |
15727 |
|
15728 |
<pre caption="Opening /etc/make.conf"> |
15729 |
# <i>nano -w /mnt/gentoo/etc/make.conf</i> |
15730 |
</pre> |
15731 |
|
15732 |
<p> |
15733 |
As you probably noticed, the <path>make.conf.example</path> file is |
15734 |
structured in a generic way: commented lines start with "#", other lines define |
15735 |
variables using the <c>VARIABLE="content"</c> syntax. The <path>make.conf</path> |
15736 |
file uses the same syntax. Several of those variables are discussed next. |
15737 |
</p> |
15738 |
|
15739 |
<warn> |
15740 |
Do not make any modifications to the USE variable if you are performing a stage3 |
15741 |
with GRP installation. You can alter the USE variable after having installed the |
15742 |
packages you want. Gremlins are known to attack your system if you ignore this |
15743 |
warning! |
15744 |
</warn> |
15745 |
|
15746 |
</body> |
15747 |
</subsection> |
15748 |
<subsection> |
15749 |
<title>CHOST</title> |
15750 |
<body> |
15751 |
|
15752 |
<p> |
15753 |
The <c>CHOST</c> variable declares the target build host for your system. This |
15754 |
variable should already be set to the correct value. <brite>Do not edit |
15755 |
it</brite> as that might break your system. If the <c>CHOST</c> variable does |
15756 |
not look correct to you, you might be using the wrong stage3 tarball. |
15757 |
</p> |
15758 |
|
15759 |
</body> |
15760 |
</subsection> |
15761 |
<subsection> |
15762 |
<title>CFLAGS and CXXFLAGS</title> |
15763 |
<body> |
15764 |
|
15765 |
<p> |
15766 |
The <c>CFLAGS</c> and <c>CXXFLAGS</c> variables define the optimization flags |
15767 |
for the <c>gcc</c> C and C++ compiler respectively. Although we define those |
15768 |
generally here, you will only have maximum performance if you optimize these |
15769 |
flags for each program separately. The reason for this is because every program |
15770 |
is different. |
15771 |
</p> |
15772 |
|
15773 |
<p> |
15774 |
In <path>make.conf</path> you should define the optimization flags you think |
15775 |
will make your system the most responsive <e>generally</e>. Don't place |
15776 |
experimental settings in this variable; too much optimization can make |
15777 |
programs behave bad (crash, or even worse, malfunction). |
15778 |
</p> |
15779 |
|
15780 |
<p> |
15781 |
We cannot explain all possible optimization options here, but if you want to |
15782 |
investigate them all, read the <uri link="http://gcc.gnu.org/onlinedocs/">GNU |
15783 |
Online Manual(s)</uri> or the <c>gcc</c> info page (<c>info gcc</c> -- only |
15784 |
works on a working Linux system). For common optimizations and architecture |
15785 |
specific settings, please read <path>/etc/make.conf.example</path>. This |
15786 |
file also contains lots of examples and information; don't forget to read it |
15787 |
too. |
15788 |
</p> |
15789 |
|
15790 |
<p> |
15791 |
As an example, on the x86 architecture, you will want to set the -march= flag |
15792 |
as shown below (for an Athlon XP machine): |
15793 |
</p> |
15794 |
|
15795 |
<pre caption="The GCC march setting"> |
15796 |
-march=athlon-xp |
15797 |
</pre> |
15798 |
|
15799 |
<p> |
15800 |
A second one is the <c>-O</c> flag (that is a capital O, not a zero), |
15801 |
which specifies the <c>gcc</c> optimization |
15802 |
class flag. Possible classes are <c>s</c> (for size-optimized), |
15803 |
<c>0</c> (zero - for no optimizations), <c>1</c>, <c>2</c> or <c>3</c> for more |
15804 |
speed-optimization flags (every class has the same flags as the one before, plus |
15805 |
some extras). For instance, for a class-2 optimization: |
15806 |
</p> |
15807 |
|
15808 |
<pre caption="The GCC O setting"> |
15809 |
-O2 |
15810 |
</pre> |
15811 |
|
15812 |
<p> |
15813 |
Another popular optimization flag is <c>-pipe</c> (use pipes rather than |
15814 |
temporary files for communication between the various stages of compilation). |
15815 |
</p> |
15816 |
|
15817 |
<p> |
15818 |
Mind you that using <c>-fomit-frame-pointer</c> (which doesn't keep the frame |
15819 |
pointer in a register for functions that don't need one) might have serious |
15820 |
repercussions on the debugging of applications! |
15821 |
</p> |
15822 |
|
15823 |
<p> |
15824 |
When you define the <c>CFLAGS</c> and <c>CXXFLAGS</c>, you should combine |
15825 |
several optimization flags, like in the following example: |
15826 |
</p> |
15827 |
|
15828 |
<pre caption="Defining the CFLAGS and CXXFLAGS variable"> |
15829 |
CFLAGS="-march=athlon-xp -pipe -O2" |
15830 |
CXXFLAGS="${CFLAGS}" <comment># Use the same settings for both variables</comment> |
15831 |
</pre> |
15832 |
|
15833 |
</body> |
15834 |
</subsection> |
15835 |
<subsection> |
15836 |
<title>MAKEOPTS</title> |
15837 |
<body> |
15838 |
|
15839 |
<p> |
15840 |
With <c>MAKEOPTS</c> you define how many parallel compilations should occur when |
15841 |
you install a package. A good choice is the number of CPUs in your system plus |
15842 |
one, but this guideline isn't always perfect. |
15843 |
</p> |
15844 |
|
15845 |
<pre caption="MAKEOPTS for a regular, 1-CPU system"> |
15846 |
MAKEOPTS="-j2" |
15847 |
</pre> |
15848 |
|
15849 |
</body> |
15850 |
</subsection> |
15851 |
<subsection> |
15852 |
<title>Ready, Set, Go!</title> |
15853 |
<body> |
15854 |
|
15855 |
<p> |
15856 |
Update your <path>/mnt/gentoo/etc/make.conf</path> to your own preference and |
15857 |
save (<c>nano</c> users would hit <c>Ctrl-X</c>). You are now ready to continue |
15858 |
with <uri link="?part=1&chap=6">Chrooting into the Gentoo Base System</uri>. |
15859 |
</p> |
15860 |
|
15861 |
</body> |
15862 |
</subsection> |
15863 |
</section> |
15864 |
</sections> |
15865 |
|
15866 |
|
15867 |
|
15868 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-system.xml |
15869 |
|
15870 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-system.xml?rev=1.1&view=markup |
15871 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-system.xml?rev=1.1&content-type=text/plain |
15872 |
|
15873 |
Index: hb-install-system.xml |
15874 |
=================================================================== |
15875 |
<?xml version='1.0' encoding='UTF-8'?> |
15876 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
15877 |
|
15878 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
15879 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
15880 |
|
15881 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-system.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
15882 |
|
15883 |
<sections> |
15884 |
|
15885 |
<version>7.1</version> |
15886 |
<date>2006-10-08</date> |
15887 |
|
15888 |
<section> |
15889 |
<title>Chrooting</title> |
15890 |
<subsection> |
15891 |
<title>Mounting the /proc and /dev Filesystems</title> |
15892 |
<body> |
15893 |
|
15894 |
<p> |
15895 |
Mount the <path>/proc</path> filesystem on <path>/mnt/gentoo/proc</path> to |
15896 |
allow the installation to use the kernel-provided information within the |
15897 |
chrooted environment, and then mount-bind the <path>/dev</path> filesystem. |
15898 |
</p> |
15899 |
|
15900 |
<pre caption="Mounting /proc and /dev"> |
15901 |
# <i>mount -t proc none /mnt/gentoo/proc</i> |
15902 |
# <i>mount -o bind /dev /mnt/gentoo/dev</i> |
15903 |
</pre> |
15904 |
|
15905 |
</body> |
15906 |
</subsection> |
15907 |
<subsection> |
15908 |
<title>Optional: Copy over DNS Information</title> |
15909 |
<body> |
15910 |
|
15911 |
<p> |
15912 |
If you configured your network to fetch the appropriate stage file later on from |
15913 |
the Internet, you need to copy over the DNS information stored in |
15914 |
<path>/etc/resolv.conf</path> to <path>/mnt/gentoo/etc/resolv.conf</path>. This |
15915 |
file contains the nameservers your system will use to resolve names to IP |
15916 |
addresses. |
15917 |
</p> |
15918 |
|
15919 |
<pre caption="Copy over DNS Information"> |
15920 |
# <i>cp -L /etc/resolv.conf /mnt/gentoo/etc/resolv.conf</i> |
15921 |
</pre> |
15922 |
|
15923 |
</body> |
15924 |
</subsection> |
15925 |
<subsection> |
15926 |
<title>Entering the new Environment</title> |
15927 |
<body> |
15928 |
|
15929 |
<p> |
15930 |
Now that all partitions are initialized and the base environment |
15931 |
installed, it is time to enter our new installation environment by |
15932 |
<e>chrooting</e> into it. This means that we change from the current |
15933 |
installation environment to your installation system (namely the |
15934 |
initialized partitions). |
15935 |
</p> |
15936 |
|
15937 |
<p> |
15938 |
This chrooting is done in three steps. First we will change the root |
15939 |
from <path>/</path> (on the installation medium) to <path>/mnt/gentoo</path> |
15940 |
(on your partitions) using <c>chroot</c>. Then we will create a new environment |
15941 |
using <c>env-update</c>, which essentially creates environment variables. |
15942 |
Finally, we load those variables into memory using <c>source</c>. |
15943 |
</p> |
15944 |
|
15945 |
<pre caption="Chrooting into the new environment"> |
15946 |
# <i>chroot /mnt/gentoo /bin/bash</i> |
15947 |
# <i>env-update</i> |
15948 |
>>> Regenerating /etc/ld.so.cache... |
15949 |
# <i>source /etc/profile</i> |
15950 |
# <i>export PS1="(chroot) $PS1"</i> |
15951 |
</pre> |
15952 |
|
15953 |
<p> |
15954 |
Congratulations! You are now inside your own Gentoo Linux environment. |
15955 |
Of course it is far from finished, which is why the installation still |
15956 |
has some sections left :-) |
15957 |
</p> |
15958 |
|
15959 |
</body> |
15960 |
</subsection> |
15961 |
<subsection> |
15962 |
<title>Creating the Portage cache</title> |
15963 |
<body> |
15964 |
|
15965 |
<p> |
15966 |
You have already installed the Portage tree, but you should now build the |
15967 |
Portage cache to speed up future emerges. <c>emerge --metadata</c> does this |
15968 |
for you. |
15969 |
</p> |
15970 |
|
15971 |
<pre caption="Creating the Portage cache"> |
15972 |
# <i>emerge --metadata</i> |
15973 |
</pre> |
15974 |
|
15975 |
</body> |
15976 |
</subsection> |
15977 |
</section> |
15978 |
|
15979 |
<section id="configure_USE"> |
15980 |
<title>Configuring the USE Variable</title> |
15981 |
<subsection> |
15982 |
<title>What is the USE Variable?</title> |
15983 |
<body> |
15984 |
|
15985 |
<p> |
15986 |
<c>USE</c> is one of the most powerful variables Gentoo provides to its users. |
15987 |
Several programs can be compiled with or without optional support for certain |
15988 |
items. For instance, some programs can be compiled with gtk-support, or with |
15989 |
qt-support. Others can be compiled with or without SSL support. Some programs |
15990 |
can even be compiled with framebuffer support (svgalib) instead of X11 support |
15991 |
(X-server). |
15992 |
</p> |
15993 |
|
15994 |
<p> |
15995 |
Most distributions compile their packages with support for as much as possible, |
15996 |
increasing the size of the programs and startup time, not to mention an enormous |
15997 |
amount of dependencies. With Gentoo you can define what options a package |
15998 |
should be compiled with. This is where <c>USE</c> comes into play. |
15999 |
</p> |
16000 |
|
16001 |
<p> |
16002 |
In the <c>USE</c> variable you define keywords which are mapped onto |
16003 |
compile-options. For instance, <e>ssl</e> will compile ssl-support in the |
16004 |
programs that support it. <e>-X</e> will remove X-server support (note the |
16005 |
minus sign in front). <e>gnome gtk -kde -qt3 -qt4</e> will compile your |
16006 |
programs with gnome (and gtk) support, and not with kde (and qt) support, |
16007 |
making your system fully tweaked for GNOME. |
16008 |
</p> |
16009 |
|
16010 |
</body> |
16011 |
</subsection> |
16012 |
<subsection> |
16013 |
<title>Modifying the USE Variable</title> |
16014 |
<body> |
16015 |
|
16016 |
<warn> |
16017 |
Do not make any modifications to the USE variable yet if you plan to use our |
16018 |
prebuilt packages (GRP set). You can alter the USE variable after having |
16019 |
installed the packages you want. Gremlins are known to attack your system |
16020 |
if you ignore this warning! |
16021 |
</warn> |
16022 |
|
16023 |
<p> |
16024 |
The default <c>USE</c> settings are placed in |
16025 |
<path>/etc/make.profile/make.defaults</path>. What you place in |
16026 |
<path>/etc/make.conf</path> is calculated against these defaults settings. If |
16027 |
you add something to the <c>USE</c> setting, it is added to the default list. If |
16028 |
you remove something from the <c>USE</c> setting (by placing a minus sign in |
16029 |
front of it) it is removed from the default list (if it was in the default list |
16030 |
at all). <e>Never</e> alter anything inside the <path>/etc/make.profile</path> |
16031 |
directory; it gets overwritten when you update Portage! |
16032 |
</p> |
16033 |
|
16034 |
<p> |
16035 |
A full description on <c>USE</c> can be found in the second part of the Gentoo |
16036 |
Handbook, <uri link="?part=2&chap=2">USE flags</uri>. A full description on |
16037 |
the available USE flags can be found on your system in |
16038 |
<path>/usr/portage/profiles/use.desc</path>. |
16039 |
</p> |
16040 |
|
16041 |
<pre caption="Viewing available USE flags"> |
16042 |
# <i>less /usr/portage/profiles/use.desc</i> |
16043 |
<comment>(You can scroll using your arrow keys, exit by pressing 'q')</comment> |
16044 |
</pre> |
16045 |
|
16046 |
<p> |
16047 |
As an example we show a <c>USE</c> setting for a KDE-based system with DVD, ALSA |
16048 |
and CD Recording support: |
16049 |
</p> |
16050 |
|
16051 |
<pre caption="Opening /etc/make.conf"> |
16052 |
# <i>nano -w /etc/make.conf</i> |
16053 |
</pre> |
16054 |
|
16055 |
<pre caption="USE setting"> |
16056 |
USE="-gtk -gnome qt3 qt4 kde dvd alsa cdr" |
16057 |
</pre> |
16058 |
|
16059 |
</body> |
16060 |
</subsection> |
16061 |
</section> |
16062 |
</sections> |
16063 |
|
16064 |
|
16065 |
|
16066 |
1.1 xml/htdocs/doc/en/handbook/2007.0/hb-install-tools.xml |
16067 |
|
16068 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-tools.xml?rev=1.1&view=markup |
16069 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-tools.xml?rev=1.1&content-type=text/plain |
16070 |
|
16071 |
Index: hb-install-tools.xml |
16072 |
=================================================================== |
16073 |
<?xml version='1.0' encoding='UTF-8'?> |
16074 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
16075 |
|
16076 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
16077 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
16078 |
|
16079 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-tools.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
16080 |
|
16081 |
<sections> |
16082 |
|
16083 |
<version>7.1</version> |
16084 |
<date>2006-12-30</date> |
16085 |
|
16086 |
<section> |
16087 |
<title>System Logger</title> |
16088 |
<body> |
16089 |
|
16090 |
<p> |
16091 |
Some tools are missing from the <e>stage3</e> archive because several packages |
16092 |
provide the same functionality. It is now up to you to choose which ones you |
16093 |
want to install. |
16094 |
</p> |
16095 |
|
16096 |
<p> |
16097 |
The first tool you need to decide on has to provide logging facilities for your |
16098 |
system. Unix and Linux have an excellent history of logging capabilities -- if |
16099 |
you want you can log everything that happens on your system in logfiles. This |
16100 |
happens through the <e>system logger</e>. |
16101 |
</p> |
16102 |
|
16103 |
<p> |
16104 |
Gentoo offers several system loggers to choose from. There are <c>sysklogd</c>, |
16105 |
which is the traditional set of system logging daemons, <c>syslog-ng</c>, an |
16106 |
advanced system logger, and <c>metalog</c> which is a highly-configurable |
16107 |
system logger. Others might be available through Portage as well - our number of |
16108 |
available packages increases on a daily basis. |
16109 |
</p> |
16110 |
|
16111 |
<p> |
16112 |
If you plan on using <c>sysklogd</c> or <c>syslog-ng</c> you might want to |
16113 |
install <c>logrotate</c> afterwards as those system loggers don't provide any |
16114 |
rotation mechanism for the log files. |
16115 |
</p> |
16116 |
|
16117 |
<!-- |
16118 |
Even though syslog-ng does not rotate the logs, it does conform to the syslog |
16119 |
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 |
16120 |
above others (metalog for instance doesn't work nicely with sparc all the |
16121 |
time). |
16122 |
--> |
16123 |
|
16124 |
<p> |
16125 |
To install the system logger of your choice, <c>emerge</c> it and have it added |
16126 |
to the default runlevel using <c>rc-update</c>. The following example installs |
16127 |
<c>syslog-ng</c>. Of course substitute with your system logger: |
16128 |
</p> |
16129 |
|
16130 |
<pre caption="Installing a system logger"> |
16131 |
# <i>emerge syslog-ng</i> |
16132 |
# <i>rc-update add syslog-ng default</i> |
16133 |
</pre> |
16134 |
|
16135 |
</body> |
16136 |
</section> |
16137 |
<section> |
16138 |
<title>Optional: Cron Daemon</title> |
16139 |
<body> |
16140 |
|
16141 |
<p> |
16142 |
Next is the cron daemon. Although it is optional and not required for your |
16143 |
system, it is wise to install one. But what is a cron daemon? A cron daemon |
16144 |
executes scheduled commands. It is very handy if you need to execute some |
16145 |
command regularly (for instance daily, weekly or monthly). |
16146 |
</p> |
16147 |
|
16148 |
<p> |
16149 |
We only provide <c>vixie-cron</c> for networkless installations. If you want |
16150 |
another cron daemon you can wait and install it later on. |
16151 |
</p> |
16152 |
|
16153 |
<pre caption="Installing a cron daemon"> |
16154 |
# <i>emerge vixie-cron</i> |
16155 |
# <i>rc-update add vixie-cron default</i> |
16156 |
</pre> |
16157 |
|
16158 |
</body> |
16159 |
</section> |
16160 |
<section> |
16161 |
<title>Optional: File Indexing</title> |
16162 |
<body> |
16163 |
|
16164 |
<p> |
16165 |
If you want to index your system's files so you are able to quickly |
16166 |
locate them using the <c>locate</c> tool, you need to install |
16167 |
<c>sys-apps/slocate</c>. |
16168 |
</p> |
16169 |
|
16170 |
<pre caption="Installing slocate"> |
16171 |
# <i>emerge slocate</i> |
16172 |
</pre> |
16173 |
|
16174 |
</body> |
16175 |
</section> |
16176 |
<section> |
16177 |
<title>File System Tools</title> |
16178 |
<subsection> |
16179 |
<body> |
16180 |
|
16181 |
<p> |
16182 |
Depending on what file systems you are using, you need to install the necessary |
16183 |
file system utilities (for checking the filesystem integrity, creating |
16184 |
additional file systems etc.). |
16185 |
</p> |
16186 |
|
16187 |
<p> |
16188 |
The following table lists the tools you need to install if you use a certain |
16189 |
file system. Not all filesystems are available for each and every architecture |
16190 |
though. |
16191 |
</p> |
16192 |
|
16193 |
<table> |
16194 |
<tr> |
16195 |
<th>File System</th> |
16196 |
<th>Tool</th> |
16197 |
<th>Install Command</th> |
16198 |
</tr> |
16199 |
<tr> |
16200 |
<ti>XFS</ti> |
16201 |
<ti>xfsprogs</ti> |
16202 |
<ti><c>emerge xfsprogs</c></ti> |
16203 |
</tr> |
16204 |
<tr> |
16205 |
<ti>ReiserFS</ti> |
16206 |
<ti>reiserfsprogs</ti> |
16207 |
<ti><c>emerge reiserfsprogs</c></ti> |
16208 |
</tr> |
16209 |
<tr> |
16210 |
<ti>JFS</ti> |
16211 |
<ti>jfsutils</ti> |
16212 |
<ti><c>emerge jfsutils</c></ti> |
16213 |
</tr> |
16214 |
</table> |
16215 |
|
16216 |
<p> |
16217 |
If you are an EVMS user, you need to install <c>emvs</c>: |
16218 |
</p> |
16219 |
|
16220 |
<pre caption="Installing EVMS utilities"> |
16221 |
# <i>USE="-gtk" emerge evms</i> |
16222 |
</pre> |
16223 |
|
16224 |
<p> |
16225 |
The <c>USE="-gtk"</c> will prevent the installation of dependencies. If you |
16226 |
want to enable the <c>evms</c> graphical tools, you can recompile <c>evms</c> |
16227 |
later on. |
16228 |
</p> |
16229 |
|
16230 |
</body> |
16231 |
</subsection> |
16232 |
<subsection test="contains('PPC PPC64', func:keyval('arch'))"> |
16233 |
<title>Optional: RAID utilities for IBM hardware</title> |
16234 |
<body> |
16235 |
|
16236 |
<p> |
16237 |
If you are using SCSI RAID on a POWER5-based system, you should consider |
16238 |
installing the <c>iprutils</c> which will allow you to work with the RAID disk |
16239 |
array, get status on the disks in the arrays, and update microcode among other |
16240 |
functions. |
16241 |
</p> |
16242 |
|
16243 |
<pre caption="Installing iprutils"> |
16244 |
# <i>emerge iprutils</i> |
16245 |
</pre> |
16246 |
|
16247 |
</body> |
16248 |
</subsection> |
16249 |
</section> |
16250 |
<section> |
16251 |
<title>Networking Tools</title> |
16252 |
<subsection> |
16253 |
<body> |
16254 |
|
16255 |
<p> |
16256 |
If you don't require any additional networking-related tools (such as rp-pppoe |
16257 |
or a dhcp client) continue with <uri link="?part=1&chap=10">Configuring the |
16258 |
Bootloader</uri>. |
16259 |
</p> |
16260 |
|
16261 |
</body> |
16262 |
</subsection> |
16263 |
<subsection> |
16264 |
<title>Optional: Installing a DHCP Client</title> |
16265 |
<body> |
16266 |
|
16267 |
<p> |
16268 |
If you require Gentoo to automatically obtain an IP address for your network |
16269 |
interface(s), you need to install <c>dhcpcd</c> (or any other DHCP Client) |
16270 |
on your system. If you don't do this now, you might not be able to connect |
16271 |
to the internet after the installation! |
16272 |
</p> |
16273 |
|
16274 |
<pre caption="Installing dhcpcd"> |
16275 |
# <i>emerge dhcpcd</i> |
16276 |
</pre> |
16277 |
|
16278 |
</body> |
16279 |
</subsection> |
16280 |
<subsection> |
16281 |
<title>Optional: Installing a PPPoE Client</title> |
16282 |
<body> |
16283 |
|
16284 |
<p> |
16285 |
If you need <c>rp-pppoe</c> to connect to the net, you need to install it. |
16286 |
</p> |
16287 |
|
16288 |
<pre caption="Installing rp-pppoe"> |
16289 |
# <i>USE="-X" emerge rp-pppoe</i> |
16290 |
</pre> |
16291 |
|
16292 |
<p> |
16293 |
The <c>USE="-X"</c> will prohibit xorg-x11 to be installed as a dependency |
16294 |
(<c>rp-pppoe</c> has graphical tools; if you want those enabled, you can |
16295 |
recompile <c>rp-pppoe</c> later on or have xorg-x11 installed now -- which takes a |
16296 |
long time to compile). |
16297 |
</p> |
16298 |
|
16299 |
<p> |
16300 |
Now continue with <uri link="?part=1&chap=10">Configuring the |
16301 |
Bootloader</uri>. |
16302 |
</p> |
16303 |
|
16304 |
</body> |
16305 |
</subsection> |
16306 |
</section> |
16307 |
</sections> |
16308 |
|
16309 |
|
16310 |
|
16311 |
1.1 xml/htdocs/doc/en/handbook/2007.0/index.xml |
16312 |
|
16313 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/index.xml?rev=1.1&view=markup |
16314 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/index.xml?rev=1.1&content-type=text/plain |
16315 |
|
16316 |
Index: index.xml |
16317 |
=================================================================== |
16318 |
<?xml version='1.0' encoding="UTF-8"?> |
16319 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
16320 |
|
16321 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/index.xml,v 1.1 2007/03/19 20:37:28 nightmorph Exp $ --> |
16322 |
|
16323 |
<guide link="/doc/en/handbook/2006.1/index.xml"> |
16324 |
<title>Gentoo 2006.1 Handbook</title> |
16325 |
|
16326 |
<author title="Author"> |
16327 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
16328 |
</author> |
16329 |
|
16330 |
<abstract> |
16331 |
The Gentoo 2006.1 Handbook is an effort to centralize documentation into a |
16332 |
coherent handbook. It contains the networkless installation instructions for the |
16333 |
2006.1 release and parts on working with Gentoo and Portage. |
16334 |
</abstract> |
16335 |
|
16336 |
<license/> |
16337 |
|
16338 |
<version>7.0</version> |
16339 |
<date>2006-08-30</date> |
16340 |
|
16341 |
<chapter> |
16342 |
<title>The Gentoo Linux 2006.1 Handbooks</title> |
16343 |
<!-- Uncomment when needed, probably for the 2006.1 versions --> |
16344 |
<!-- |
16345 |
<section> |
16346 |
<title>Available languages</title> |
16347 |
<body> |
16348 |
|
16349 |
<p> |
16350 |
The Gentoo Linux 2006.1 Handbook is available in the following languages: |
16351 |
</p> |
16352 |
|
16353 |
<p> |
16354 |
<uri link="/doc/da/handbook">Danish</uri> | |
16355 |
<uri link="/doc/de/handbook">German</uri> | |
16356 |
<uri link="/doc/en/handbook">English</uri> | |
16357 |
<uri link="/doc/fr/handbook">French</uri> | |
16358 |
<uri link="/doc/id/handbook">Indonesian</uri> | |
16359 |
<uri link="/doc/it/handbook">Italian</uri> | |
16360 |
<uri link="/doc/ja/handbook">Japanese</uri> | |
16361 |
<uri link="/doc/pl/handbook">Polish</uri> | |
16362 |
<uri link="/doc/ro/handbook">Romanian</uri> | |
16363 |
<uri link="/doc/es/handbook">Spanish</uri> | |
16364 |
<uri link="/doc/zh_tw/handbook">Traditional Chinese</uri> |
16365 |
</p> |
16366 |
|
16367 |
</body> |
16368 |
</section> |
16369 |
--> |
16370 |
<section> |
16371 |
<title>Introduction</title> |
16372 |
<body> |
16373 |
|
16374 |
<p> |
16375 |
Welcome to the Gentoo Linux 2006.1 Handbooks. These handbooks are released |
16376 |
together with the Gentoo Linux releases and contain the necessary installation |
16377 |
instructions to install Gentoo Linux 2006.1 <brite>without an internet |
16378 |
connection.</brite> |
16379 |
</p> |
16380 |
|
16381 |
<p> |
16382 |
However, if you want to install Gentoo Linux using the latest versions of all |
16383 |
available packages, please use the Installation Instructions in the <uri |
16384 |
link="/doc/en/handbook/">Gentoo Linux Handbook</uri> for your architecture. |
16385 |
</p> |
16386 |
|
16387 |
</body> |
16388 |
</section> |
16389 |
</chapter> |
16390 |
<chapter> |
16391 |
<title>View the Handbook</title> |
16392 |
<section> |
16393 |
<body> |
16394 |
|
16395 |
<table> |
16396 |
<tr> |
16397 |
<th>Format</th> |
16398 |
<th>Description</th> |
16399 |
<th>Links</th> |
16400 |
</tr> |
16401 |
<tr> |
16402 |
<ti>HTML</ti> |
16403 |
<ti>One page per chapter, perfect for online viewing</ti> |
16404 |
<ti> |
16405 |
<uri link="handbook-x86.xml">x86</uri>, |
16406 |
<uri link="handbook-sparc.xml">sparc</uri>, |
16407 |
<uri link="handbook-alpha.xml">alpha</uri>, |
16408 |
<uri link="handbook-amd64.xml">amd64</uri>, |
16409 |
<uri link="handbook-ppc.xml">ppc</uri>, |
16410 |
<uri link="handbook-ppc64.xml">ppc64</uri>, |
16411 |
<uri link="handbook-hppa.xml">hppa</uri> |
16412 |
</ti> |
16413 |
</tr> |
16414 |
<tr> |
16415 |
<ti>HTML</ti> |
16416 |
<ti>All in one page</ti> |
16417 |
<ti> |
16418 |
<uri link="handbook-x86.xml?full=1">x86</uri>, |
16419 |
<uri link="handbook-sparc.xml?full=1">sparc</uri>, |
16420 |
<uri link="handbook-alpha.xml?full=1">alpha</uri>, |
16421 |
<uri link="handbook-amd64.xml?full=1">amd64</uri>, |
16422 |
<uri link="handbook-ppc.xml?full=1">ppc</uri>, |
16423 |
<uri link="handbook-ppc64.xml?full=1">ppc64</uri>, |
16424 |
<uri link="handbook-hppa.xml?full=1">hppa</uri> |
16425 |
</ti> |
16426 |
</tr> |
16427 |
<tr> |
16428 |
<ti>HTML</ti> |
16429 |
<ti>All in one page, printable version</ti> |
16430 |
<ti> |
16431 |
<uri link="handbook-x86.xml?style=printable&full=1">x86</uri>, |
16432 |
<uri link="handbook-sparc.xml?style=printable&full=1">sparc</uri>, |
16433 |
<uri link="handbook-alpha.xml?style=printable&full=1">alpha</uri>, |
16434 |
<uri link="handbook-amd64.xml?style=printable&full=1">amd64</uri>, |
16435 |
<uri link="handbook-ppc.xml?style=printable&full=1">ppc</uri>, |
16436 |
<uri link="handbook-ppc64.xml?style=printable&full=1">ppc64</uri>, |
16437 |
<uri link="handbook-hppa.xml?style=printable&full=1">hppa</uri> |
16438 |
</ti> |
16439 |
</tr> |
16440 |
</table> |
16441 |
|
16442 |
</body> |
16443 |
</section> |
16444 |
</chapter> |
16445 |
</guide> |
16446 |
|
16447 |
|
16448 |
|
16449 |
-- |
16450 |
gentoo-doc-cvs@g.o mailing list |