1 |
fox2mike 06/02/27 00:11:36 |
2 |
|
3 |
Added: xml/htdocs/doc/en/handbook/2006.0 handbook-alpha.xml |
4 |
handbook-amd64.xml handbook-hppa.xml |
5 |
handbook-ppc.xml handbook-ppc64.xml |
6 |
handbook-sparc.xml handbook-x86.xml |
7 |
hb-install-about.xml |
8 |
hb-install-alpha-bootloader.xml |
9 |
hb-install-alpha-disk.xml |
10 |
hb-install-alpha-kernel.xml |
11 |
hb-install-alpha-medium.xml |
12 |
hb-install-amd64-bootloader.xml |
13 |
hb-install-amd64-disk.xml |
14 |
hb-install-amd64-kernel.xml |
15 |
hb-install-amd64-medium.xml hb-install-config.xml |
16 |
hb-install-finalise.xml |
17 |
hb-install-hppa-bootloader.xml |
18 |
hb-install-hppa-disk.xml hb-install-hppa-kernel.xml |
19 |
hb-install-hppa-medium.xml hb-install-network.xml |
20 |
hb-install-next.xml 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-ppc64-bootloader.xml |
24 |
hb-install-ppc64-disk.xml |
25 |
hb-install-ppc64-kernel.xml |
26 |
hb-install-ppc64-medium.xml |
27 |
hb-install-sparc-bootloader.xml |
28 |
hb-install-sparc-disk.xml |
29 |
hb-install-sparc-kernel.xml |
30 |
hb-install-sparc-medium.xml hb-install-stage.xml |
31 |
hb-install-system.xml hb-install-tools.xml |
32 |
hb-install-x86-bootloader.xml |
33 |
hb-install-x86-disk.xml hb-install-x86-kernel.xml |
34 |
hb-install-x86-medium.xml |
35 |
Log: |
36 |
Prep for 2006.0 |
37 |
|
38 |
Revision Changes Path |
39 |
1.1 xml/htdocs/doc/en/handbook/2006.0/handbook-alpha.xml |
40 |
|
41 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/handbook-alpha.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
42 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/handbook-alpha.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
43 |
|
44 |
Index: handbook-alpha.xml |
45 |
=================================================================== |
46 |
<?xml version='1.0' encoding='UTF-8'?> |
47 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
48 |
|
49 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/handbook-alpha.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
50 |
|
51 |
<book link="handbook-alpha.xml"> |
52 |
<title>Gentoo Linux 2005.1 Alpha Handbook</title> |
53 |
|
54 |
<author title="Author"> |
55 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
56 |
</author> |
57 |
<author title="Author"> |
58 |
<mail link="uberlord@g.o">Roy Marples</mail> |
59 |
</author> |
60 |
<author title="Author"> |
61 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
62 |
</author> |
63 |
<author title="Author"> |
64 |
<mail link="chouser@g.o">Chris Houser</mail> |
65 |
</author> |
66 |
<author title="Author"> |
67 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
68 |
</author> |
69 |
<author title="Gentoo x86 Developer"> |
70 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
71 |
</author> |
72 |
<author title="Gentoo Alpha Developer"> |
73 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
74 |
</author><!-- Does not want to be listed on the rendered page |
75 |
<author title="Gentoo Developer"> |
76 |
Aron Griffis |
77 |
</author> |
78 |
--> |
79 |
<author title="Gentoo AMD64 Developer"> |
80 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
81 |
</author> |
82 |
<author title="Gentoo HPPA developer"> |
83 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
84 |
</author> |
85 |
<author title="Gentoo PPC developer"> |
86 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
87 |
</author> |
88 |
<author title="Gentoo SPARC developer"> |
89 |
<mail link="blademan@g.o">Joe Kallar</mail> |
90 |
</author> |
91 |
<author title="Editor"> |
92 |
<mail link="zhen@g.o">John P. Davis</mail> |
93 |
</author> |
94 |
<author title="Editor">Pierre-Henri Jondot</author> |
95 |
<author title="Editor"> |
96 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
97 |
</author> |
98 |
<author title="Editor"> |
99 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
100 |
</author> |
101 |
<author title="Editor"> |
102 |
<mail link="seo@g.o">Jungmin Seo</mail> |
103 |
</author> |
104 |
<author title="Editor"> |
105 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
106 |
</author> |
107 |
<author title="Editor"> |
108 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
109 |
</author> |
110 |
<author title="Editor"> |
111 |
<mail link="peitolm@g.o">Colin Morey</mail> |
112 |
</author> |
113 |
<author title="Editor"> |
114 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
115 |
</author> |
116 |
<author title="Editor"> |
117 |
<mail link="carl@g.o">Carl Anderson</mail> |
118 |
</author> |
119 |
<author title="Editor"> |
120 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
121 |
</author> |
122 |
<author title="Editor"> |
123 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
124 |
</author> |
125 |
<author title="Editor"> |
126 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
127 |
</author> |
128 |
<author title="Editor"> |
129 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
130 |
</author> |
131 |
<author title="Editor"> |
132 |
<mail link="erwin@g.o">Erwin</mail> |
133 |
</author> |
134 |
<author title="Editor"> |
135 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
136 |
</author> |
137 |
<author title="Editor"> |
138 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
139 |
</author> |
140 |
<author title="Editor"> |
141 |
<mail link="neysx@g.o">Xavier Neys</mail> |
142 |
</author> |
143 |
<author title="Reviewer"> |
144 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
145 |
</author> |
146 |
<author title="Reviewer"> |
147 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
148 |
</author> |
149 |
<author title="Reviewer"> |
150 |
<mail link="spyderous@g.o">Donnie Berkholz</mail> |
151 |
</author> |
152 |
<author title="Reviewer"> |
153 |
<mail link="antifa@g.o">Ken Nowack</mail> |
154 |
</author> |
155 |
<author title="Contributor"> |
156 |
<mail link="pylon@g.o">Lars Weiler</mail> |
157 |
</author> |
158 |
|
159 |
<abstract> |
160 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
161 |
This handbook contains the installation instructions for a networkless |
162 |
installation on Alpha systems and parts about working with Gentoo and Portage. |
163 |
</abstract> |
164 |
|
165 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
166 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
167 |
<license/> |
168 |
|
169 |
<version>5.2</version> |
170 |
<date>2005-10-13</date> |
171 |
|
172 |
<part> |
173 |
<title>Installing Gentoo</title> |
174 |
<abstract> |
175 |
In this part you learn how to install Gentoo on your system. |
176 |
</abstract> |
177 |
|
178 |
<chapter> |
179 |
<title>About the Gentoo Linux Installation</title> |
180 |
<abstract> |
181 |
Users not familiar with Gentoo do not always know that choice is what |
182 |
Gentoo is all about. |
183 |
</abstract> |
184 |
<include href="hb-install-about.xml"/> |
185 |
</chapter> |
186 |
|
187 |
<chapter> |
188 |
<title>Booting the Universal Installation CD</title> |
189 |
<abstract> |
190 |
Using our Universal Installation CD you can boot up your system into a running |
191 |
environment that allows you to install Gentoo. |
192 |
</abstract> |
193 |
<include href="hb-install-alpha-medium.xml"/> |
194 |
</chapter> |
195 |
|
196 |
<chapter> |
197 |
<title>Configuring your Network</title> |
198 |
<abstract> |
199 |
If you need networking, this is the place where the network (and Internet |
200 |
connection) is configured. |
201 |
</abstract> |
202 |
<include href="hb-install-network.xml"/> |
203 |
</chapter> |
204 |
|
205 |
<chapter> |
206 |
<title>Preparing the Disks</title> |
207 |
<abstract> |
208 |
To be able to install Gentoo, you must create the necessary partitions. |
209 |
This chapter describes how to partition a disk for future usage. |
210 |
</abstract> |
211 |
<include href="hb-install-alpha-disk.xml"/> |
212 |
</chapter> |
213 |
|
214 |
<chapter> |
215 |
<title>Installing the Gentoo Installation Files</title> |
216 |
<abstract> |
217 |
In this chapter we describe how you extract a stage3 file and how to configure |
218 |
Portage. |
219 |
</abstract> |
220 |
<include href="hb-install-stage.xml"/> |
221 |
</chapter> |
222 |
|
223 |
<chapter> |
224 |
<title>Chrooting into the Gentoo Base System</title> |
225 |
<abstract> |
226 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
227 |
the USE variable. |
228 |
</abstract> |
229 |
<include href="hb-install-system.xml"/> |
230 |
</chapter> |
231 |
|
232 |
<chapter> |
233 |
<title>Configuring the Kernel</title> |
234 |
<abstract> |
235 |
The Linux kernel is the core of every distribution. This chapter |
236 |
explains how to configure your kernel. |
237 |
</abstract> |
238 |
<include href="hb-install-alpha-kernel.xml"/> |
239 |
</chapter> |
240 |
|
241 |
<chapter> |
242 |
<title>Configuring your System</title> |
243 |
<abstract> |
244 |
You need to edit some important configuration files. In this chapter |
245 |
you receive an overview of these files and an explanation on how to |
246 |
proceed. |
247 |
</abstract> |
248 |
<include href="hb-install-config.xml"/> |
249 |
</chapter> |
250 |
|
251 |
<chapter> |
252 |
<title>Installing Necessary System Tools</title> |
253 |
<abstract> |
254 |
As mentioned before, Gentoo is about choices. In this chapter we help you |
255 |
choose and install some important tools. |
256 |
</abstract> |
257 |
<include href="hb-install-tools.xml"/> |
258 |
</chapter> |
259 |
|
260 |
<chapter> |
261 |
<title>Configuring the Bootloader</title> |
262 |
<abstract> |
263 |
Several bootloaders exist. Each one of them has its own way of |
264 |
configuration. In this chapter we'll describe all possibilities for you |
265 |
and step you through the process of configuring a bootloader to your |
266 |
needs. |
267 |
</abstract> |
268 |
<include href="hb-install-alpha-bootloader.xml"/> |
269 |
</chapter> |
270 |
|
271 |
<chapter> |
272 |
<title>Finalizing your Gentoo Installation</title> |
273 |
<abstract> |
274 |
You're almost done. We'll just create one (or more) users for your |
275 |
system and (optionally) install the prebuilt packages. |
276 |
</abstract> |
277 |
<include href="hb-install-finalise.xml"/> |
278 |
</chapter> |
279 |
|
280 |
<chapter> |
281 |
<title>Where to go from here?</title> |
282 |
<abstract> |
283 |
Now you have your Gentoo system, but what's next? |
284 |
</abstract> |
285 |
<include href="hb-install-next.xml"/> |
286 |
</chapter> |
287 |
</part> |
288 |
|
289 |
<part> |
290 |
<title>Working with Gentoo</title> |
291 |
<abstract> |
292 |
Learn how to work with Gentoo: installing software, altering variables, changing |
293 |
Portage behaviour etc. |
294 |
</abstract> |
295 |
|
296 |
<chapter> |
297 |
<title>A Portage Introduction</title> |
298 |
<abstract> |
299 |
This chapter explains the "simple" steps a user definitely needs to know to |
300 |
maintain the software on his system. |
301 |
</abstract> |
302 |
<include href="../hb-working-portage.xml"/> |
303 |
</chapter> |
304 |
|
305 |
<chapter> |
306 |
<title>USE flags</title> |
307 |
<abstract> |
308 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
309 |
work with USE-flags and understand how USE-flags interact with your system. |
310 |
</abstract> |
311 |
<include href="../hb-working-use.xml"/> |
312 |
</chapter> |
313 |
|
314 |
<chapter> |
315 |
<title>Portage Features</title> |
316 |
<abstract> |
317 |
Discover the features Portage has, such as support for distributed compiling, |
318 |
ccache and more. |
319 |
</abstract> |
320 |
<include href="../hb-working-features.xml"/> |
321 |
</chapter> |
322 |
|
323 |
<chapter> |
324 |
<title>Initscripts</title> |
325 |
<abstract> |
326 |
Gentoo uses a special initscript format which, amongst other features, allows |
327 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
328 |
these aspects and explains how to deal with these scripts. |
329 |
</abstract> |
330 |
<include href="../hb-working-rcscripts.xml"/> |
331 |
</chapter> |
332 |
|
333 |
<chapter> |
334 |
<title>Environment Variables</title> |
335 |
<abstract> |
336 |
With Gentoo you can easily manage the environment variables for your system. |
337 |
This chapter explains how you do that, and also describes frequently used |
338 |
variables. |
339 |
</abstract> |
340 |
<include href="../hb-working-variables.xml"/> |
341 |
</chapter> |
342 |
</part> |
343 |
|
344 |
<part> |
345 |
<title>Working with Portage</title> |
346 |
<abstract> |
347 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
348 |
Software Management Tool. |
349 |
</abstract> |
350 |
|
351 |
<chapter> |
352 |
<title>Files and Directories</title> |
353 |
<abstract> |
354 |
Once you want to know Portage in-depth you need to know where it stores its |
355 |
files and data. |
356 |
</abstract> |
357 |
<include href="../hb-portage-files.xml"/> |
358 |
</chapter> |
359 |
|
360 |
<chapter> |
361 |
<title>Configuring through Variables</title> |
362 |
<abstract> |
363 |
Portage is completely configurable through various variables you can set in the |
364 |
configuration file or as environment variable. |
365 |
</abstract> |
366 |
<include href="../hb-portage-configuration.xml"/> |
367 |
</chapter> |
368 |
|
369 |
<chapter> |
370 |
<title>Mixing Software Branches</title> |
371 |
<abstract> |
372 |
Gentoo provides software separated in several branches, depending on stability |
373 |
and architectural support. "Mixing Software Branches" inform you how these |
374 |
branches can be configured and how you can override this separation |
375 |
individually. |
376 |
</abstract> |
377 |
<include href="../hb-portage-branches.xml"/> |
378 |
</chapter> |
379 |
|
380 |
<chapter> |
381 |
<title>Additional Portage Tools</title> |
382 |
<abstract> |
383 |
Portage comes with a few extra tools that might make your Gentoo experience even |
384 |
better. Read on to discover how to use dispatch-conf and other tools. |
385 |
</abstract> |
386 |
<include href="../hb-portage-tools.xml"/> |
387 |
</chapter> |
388 |
|
389 |
<chapter> |
390 |
<title>Diverting from the Official Tree</title> |
391 |
<abstract> |
392 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
393 |
your own Portage tree, how to synchronise only the categories you want, inject |
394 |
packages and more. |
395 |
</abstract> |
396 |
<include href="../hb-portage-diverttree.xml"/> |
397 |
</chapter> |
398 |
|
399 |
<chapter> |
400 |
<title>The Ebuild Application</title> |
401 |
<abstract> |
402 |
In "The Ebuild Application" you are informed about the steps Portage takes while |
403 |
installing software and how you can do this yourself using the ebuild |
404 |
application. |
405 |
</abstract> |
406 |
<include href="../hb-portage-ebuild.xml"/> |
407 |
</chapter> |
408 |
</part> |
409 |
|
410 |
<part> |
411 |
<title>Gentoo Network Configuration</title> |
412 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
413 |
|
414 |
<chapter> |
415 |
<title>Getting Started</title> |
416 |
<abstract> |
417 |
A guide to quickly get your network interface up and running in most common |
418 |
environments. |
419 |
</abstract> |
420 |
<include href="../hb-net-start.xml"/> |
421 |
</chapter> |
422 |
|
423 |
<chapter> |
424 |
<title>Advanced Configuration</title> |
425 |
<abstract> |
426 |
Here we learn about how the configuration works - you need to know this |
427 |
before we learn about modular networking. |
428 |
</abstract> |
429 |
<include href="../hb-net-advanced.xml"/> |
430 |
</chapter> |
431 |
|
432 |
<chapter> |
433 |
<title>Modular Networking</title> |
434 |
<abstract> |
435 |
Gentoo provides you flexible networking - here you are told about choosing |
436 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
437 |
</abstract> |
438 |
<include href="../hb-net-modules.xml"/> |
439 |
</chapter> |
440 |
|
441 |
<chapter> |
442 |
<title>Wireless Networking</title> |
443 |
<abstract> |
444 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
445 |
</abstract> |
446 |
<include href="../hb-net-wireless.xml"/> |
447 |
</chapter> |
448 |
|
449 |
<chapter> |
450 |
<title>Adding Functionality</title> |
451 |
<abstract> |
452 |
If you're feeling adventurous, you can add your own functions to networking. |
453 |
</abstract> |
454 |
<include href="../hb-net-functions.xml"/> |
455 |
</chapter> |
456 |
|
457 |
<chapter> |
458 |
<title>Network Management</title> |
459 |
<abstract> |
460 |
For laptop users or people who move their computer around different networks. |
461 |
</abstract> |
462 |
<include href="../hb-net-management.xml"/> |
463 |
</chapter> |
464 |
</part> |
465 |
|
466 |
</book> |
467 |
|
468 |
|
469 |
|
470 |
1.1 xml/htdocs/doc/en/handbook/2006.0/handbook-amd64.xml |
471 |
|
472 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/handbook-amd64.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
473 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/handbook-amd64.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
474 |
|
475 |
Index: handbook-amd64.xml |
476 |
=================================================================== |
477 |
<?xml version='1.0' encoding='UTF-8'?> |
478 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
479 |
|
480 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/handbook-amd64.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
481 |
|
482 |
<book link="handbook-amd64.xml"> |
483 |
<title>Gentoo Linux 2005.1 AMD64 Handbook</title> |
484 |
|
485 |
<author title="Author"> |
486 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
487 |
</author> |
488 |
<author title="Author"> |
489 |
<mail link="uberlord@g.o">Roy Marples</mail> |
490 |
</author> |
491 |
<author title="Author"> |
492 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
493 |
</author> |
494 |
<author title="Author"> |
495 |
<mail link="chouser@g.o">Chris Houser</mail> |
496 |
</author> |
497 |
<author title="Author"> |
498 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
499 |
</author> |
500 |
<author title="Gentoo x86 Developer"> |
501 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
502 |
</author> |
503 |
<author title="Gentoo Alpha Developer"> |
504 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
505 |
</author><!-- Does not want to be listed on the rendered page |
506 |
<author title="Gentoo Developer"> |
507 |
Aron Griffis |
508 |
</author> |
509 |
--> |
510 |
<author title="Gentoo AMD64 Developer"> |
511 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
512 |
</author> |
513 |
<author title="Gentoo HPPA developer"> |
514 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
515 |
</author> |
516 |
<author title="Gentoo PPC developer"> |
517 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
518 |
</author> |
519 |
<author title="Gentoo SPARC developer"> |
520 |
<mail link="blademan@g.o">Joe Kallar</mail> |
521 |
</author> |
522 |
<author title="Editor"> |
523 |
<mail link="zhen@g.o">John P. Davis</mail> |
524 |
</author> |
525 |
<author title="Editor">Pierre-Henri Jondot</author> |
526 |
<author title="Editor"> |
527 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
528 |
</author> |
529 |
<author title="Editor"> |
530 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
531 |
</author> |
532 |
<author title="Editor"> |
533 |
<mail link="seo@g.o">Jungmin Seo</mail> |
534 |
</author> |
535 |
<author title="Editor"> |
536 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
537 |
</author> |
538 |
<author title="Editor"> |
539 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
540 |
</author> |
541 |
<author title="Editor"> |
542 |
<mail link="peitolm@g.o">Colin Morey</mail> |
543 |
</author> |
544 |
<author title="Editor"> |
545 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
546 |
</author> |
547 |
<author title="Editor"> |
548 |
<mail link="carl@g.o">Carl Anderson</mail> |
549 |
</author> |
550 |
<author title="Editor"> |
551 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
552 |
</author> |
553 |
<author title="Editor"> |
554 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
555 |
</author> |
556 |
<author title="Editor"> |
557 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
558 |
</author> |
559 |
<author title="Editor"> |
560 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
561 |
</author> |
562 |
<author title="Editor"> |
563 |
<mail link="erwin@g.o">Erwin</mail> |
564 |
</author> |
565 |
<author title="Editor"> |
566 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
567 |
</author> |
568 |
<author title="Editor"> |
569 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
570 |
</author> |
571 |
<author title="Editor"> |
572 |
<mail link="neysx@g.o">Xavier Neys</mail> |
573 |
</author> |
574 |
<author title="Reviewer"> |
575 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
576 |
</author> |
577 |
<author title="Reviewer"> |
578 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
579 |
</author> |
580 |
<author title="Reviewer"> |
581 |
<mail link="spyderous@g.o">Donnie Berkholz</mail> |
582 |
</author> |
583 |
<author title="Reviewer"> |
584 |
<mail link="antifa@g.o">Ken Nowack</mail> |
585 |
</author> |
586 |
<author title="Contributor"> |
587 |
<mail link="pylon@g.o">Lars Weiler</mail> |
588 |
</author> |
589 |
|
590 |
<abstract> |
591 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
592 |
This handbook contains the installation instructions for a networkless |
593 |
installation on AMD64 systems and parts about working with Gentoo and Portage. |
594 |
</abstract> |
595 |
|
596 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
597 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
598 |
<license/> |
599 |
|
600 |
<version>5.2</version> |
601 |
<date>2005-10-13</date> |
602 |
|
603 |
<part> |
604 |
<title>Installing Gentoo</title> |
605 |
<abstract> |
606 |
In this part you learn how to install Gentoo on your system. |
607 |
</abstract> |
608 |
|
609 |
<chapter> |
610 |
<title>About the Gentoo Linux Installation</title> |
611 |
<abstract> |
612 |
Users not familiar with Gentoo do not always know that choice is what |
613 |
Gentoo is all about. |
614 |
</abstract> |
615 |
<include href="hb-install-about.xml"/> |
616 |
</chapter> |
617 |
|
618 |
<chapter> |
619 |
<title>Booting the Universal Installation CD</title> |
620 |
<abstract> |
621 |
Using our Universal Installation CD you can boot up your system into a running |
622 |
environment that allows you to install Gentoo. |
623 |
</abstract> |
624 |
<include href="hb-install-amd64-medium.xml"/> |
625 |
</chapter> |
626 |
|
627 |
<chapter> |
628 |
<title>Configuring your Network</title> |
629 |
<abstract> |
630 |
If you need networking, this is the place where the network (and Internet |
631 |
connection) is configured. |
632 |
</abstract> |
633 |
<include href="hb-install-network.xml"/> |
634 |
</chapter> |
635 |
|
636 |
<chapter> |
637 |
<title>Preparing the Disks</title> |
638 |
<abstract> |
639 |
To be able to install Gentoo, you must create the necessary partitions. |
640 |
This chapter describes how to partition a disk for future usage. |
641 |
</abstract> |
642 |
<include href="hb-install-amd64-disk.xml"/> |
643 |
</chapter> |
644 |
|
645 |
<chapter> |
646 |
<title>Installing the Gentoo Installation Files</title> |
647 |
<abstract> |
648 |
In this chapter we describe how you extract a stage3 file and how to configure |
649 |
Portage. |
650 |
</abstract> |
651 |
<include href="hb-install-stage.xml"/> |
652 |
</chapter> |
653 |
|
654 |
<chapter> |
655 |
<title>Chrooting into the Gentoo Base System</title> |
656 |
<abstract> |
657 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
658 |
the USE variable. |
659 |
</abstract> |
660 |
<include href="hb-install-system.xml"/> |
661 |
</chapter> |
662 |
|
663 |
<chapter> |
664 |
<title>Configuring the Kernel</title> |
665 |
<abstract> |
666 |
The Linux kernel is the core of every distribution. This chapter |
667 |
explains how to configure your kernel. |
668 |
</abstract> |
669 |
<include href="hb-install-amd64-kernel.xml"/> |
670 |
</chapter> |
671 |
|
672 |
<chapter> |
673 |
<title>Configuring your System</title> |
674 |
<abstract> |
675 |
You need to edit some important configuration files. In this chapter |
676 |
you receive an overview of these files and an explanation on how to |
677 |
proceed. |
678 |
</abstract> |
679 |
<include href="hb-install-config.xml"/> |
680 |
</chapter> |
681 |
|
682 |
<chapter> |
683 |
<title>Installing Necessary System Tools</title> |
684 |
<abstract> |
685 |
As mentioned before, Gentoo is about choices. In this chapter we help you |
686 |
choose and install some important tools. |
687 |
</abstract> |
688 |
<include href="hb-install-tools.xml"/> |
689 |
</chapter> |
690 |
|
691 |
<chapter> |
692 |
<title>Configuring the Bootloader</title> |
693 |
<abstract> |
694 |
In this chapter we'll describe the GRUB bootloader |
695 |
and step you through the process of configuring GRUB to your |
696 |
needs. |
697 |
</abstract> |
698 |
<include href="hb-install-amd64-bootloader.xml"/> |
699 |
</chapter> |
700 |
|
701 |
<chapter> |
702 |
<title>Finalizing your Gentoo Installation</title> |
703 |
<abstract> |
704 |
You're almost done. We'll just create one (or more) users for your |
705 |
system and (optionally) install the prebuilt packages. |
706 |
</abstract> |
707 |
<include href="hb-install-finalise.xml"/> |
708 |
</chapter> |
709 |
|
710 |
<chapter> |
711 |
<title>Where to go from here?</title> |
712 |
<abstract> |
713 |
Now you have your Gentoo system, but what's next? |
714 |
</abstract> |
715 |
<include href="hb-install-next.xml"/> |
716 |
</chapter> |
717 |
</part> |
718 |
|
719 |
<part> |
720 |
<title>Working with Gentoo</title> |
721 |
<abstract> |
722 |
Learn how to work with Gentoo: installing software, altering variables, changing |
723 |
Portage behaviour etc. |
724 |
</abstract> |
725 |
|
726 |
<chapter> |
727 |
<title>A Portage Introduction</title> |
728 |
<abstract> |
729 |
This chapter explains the "simple" steps a user definitely needs to know to |
730 |
maintain the software on his system. |
731 |
</abstract> |
732 |
<include href="../hb-working-portage.xml"/> |
733 |
</chapter> |
734 |
|
735 |
<chapter> |
736 |
<title>USE flags</title> |
737 |
<abstract> |
738 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
739 |
work with USE-flags and understand how USE-flags interact with your system. |
740 |
</abstract> |
741 |
<include href="../hb-working-use.xml"/> |
742 |
</chapter> |
743 |
|
744 |
<chapter> |
745 |
<title>Portage Features</title> |
746 |
<abstract> |
747 |
Discover the features Portage has, such as support for distributed compiling, |
748 |
ccache and more. |
749 |
</abstract> |
750 |
<include href="../hb-working-features.xml"/> |
751 |
</chapter> |
752 |
|
753 |
<chapter> |
754 |
<title>Initscripts</title> |
755 |
<abstract> |
756 |
Gentoo uses a special initscript format which, amongst other features, allows |
757 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
758 |
these aspects and explains how to deal with these scripts. |
759 |
</abstract> |
760 |
<include href="../hb-working-rcscripts.xml"/> |
761 |
</chapter> |
762 |
|
763 |
<chapter> |
764 |
<title>Environment Variables</title> |
765 |
<abstract> |
766 |
With Gentoo you can easily manage the environment variables for your system. |
767 |
This chapter explains how you do that, and also describes frequently used |
768 |
variables. |
769 |
</abstract> |
770 |
<include href="../hb-working-variables.xml"/> |
771 |
</chapter> |
772 |
</part> |
773 |
|
774 |
<part> |
775 |
<title>Working with Portage</title> |
776 |
<abstract> |
777 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
778 |
Software Management Tool. |
779 |
</abstract> |
780 |
|
781 |
<chapter> |
782 |
<title>Files and Directories</title> |
783 |
<abstract> |
784 |
Once you want to know Portage in-depth you need to know where it stores its |
785 |
files and data. |
786 |
</abstract> |
787 |
<include href="../hb-portage-files.xml"/> |
788 |
</chapter> |
789 |
|
790 |
<chapter> |
791 |
<title>Configuring through Variables</title> |
792 |
<abstract> |
793 |
Portage is completely configurable through various variables you can set in the |
794 |
configuration file or as environment variable. |
795 |
</abstract> |
796 |
<include href="../hb-portage-configuration.xml"/> |
797 |
</chapter> |
798 |
|
799 |
<chapter> |
800 |
<title>Mixing Software Branches</title> |
801 |
<abstract> |
802 |
Gentoo provides software separated in several branches, depending on stability |
803 |
and architectural support. "Mixing Software Branches" inform you how these |
804 |
branches can be configured and how you can override this separation |
805 |
individually. |
806 |
</abstract> |
807 |
<include href="../hb-portage-branches.xml"/> |
808 |
</chapter> |
809 |
|
810 |
<chapter> |
811 |
<title>Additional Portage Tools</title> |
812 |
<abstract> |
813 |
Portage comes with a few extra tools that might make your Gentoo experience even |
814 |
better. Read on to discover how to use dispatch-conf and other tools. |
815 |
</abstract> |
816 |
<include href="../hb-portage-tools.xml"/> |
817 |
</chapter> |
818 |
|
819 |
<chapter> |
820 |
<title>Diverting from the Official Tree</title> |
821 |
<abstract> |
822 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
823 |
your own Portage tree, how to synchronise only the categories you want, inject |
824 |
packages and more. |
825 |
</abstract> |
826 |
<include href="../hb-portage-diverttree.xml"/> |
827 |
</chapter> |
828 |
|
829 |
<chapter> |
830 |
<title>The Ebuild Application</title> |
831 |
<abstract> |
832 |
In "The Ebuild Application" you are informed about the steps Portage takes while |
833 |
installing software and how you can do this yourself using the ebuild |
834 |
application. |
835 |
</abstract> |
836 |
<include href="../hb-portage-ebuild.xml"/> |
837 |
</chapter> |
838 |
</part> |
839 |
|
840 |
<part> |
841 |
<title>Gentoo Network Configuration</title> |
842 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
843 |
|
844 |
<chapter> |
845 |
<title>Getting Started</title> |
846 |
<abstract> |
847 |
A guide to quickly get your network interface up and running in most common |
848 |
environments. |
849 |
</abstract> |
850 |
<include href="../hb-net-start.xml"/> |
851 |
</chapter> |
852 |
|
853 |
<chapter> |
854 |
<title>Advanced Configuration</title> |
855 |
<abstract> |
856 |
Here we learn about how the configuration works - you need to know this |
857 |
before we learn about modular networking. |
858 |
</abstract> |
859 |
<include href="../hb-net-advanced.xml"/> |
860 |
</chapter> |
861 |
|
862 |
<chapter> |
863 |
<title>Modular Networking</title> |
864 |
<abstract> |
865 |
Gentoo provides you flexible networking - here you are told about choosing |
866 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
867 |
</abstract> |
868 |
<include href="../hb-net-modules.xml"/> |
869 |
</chapter> |
870 |
|
871 |
<chapter> |
872 |
<title>Wireless Networking</title> |
873 |
<abstract> |
874 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
875 |
</abstract> |
876 |
<include href="../hb-net-wireless.xml"/> |
877 |
</chapter> |
878 |
|
879 |
<chapter> |
880 |
<title>Adding Functionality</title> |
881 |
<abstract> |
882 |
If you're feeling adventurous, you can add your own functions to networking. |
883 |
</abstract> |
884 |
<include href="../hb-net-functions.xml"/> |
885 |
</chapter> |
886 |
|
887 |
<chapter> |
888 |
<title>Network Management</title> |
889 |
<abstract> |
890 |
For laptop users or people who move their computer around different networks. |
891 |
</abstract> |
892 |
<include href="../hb-net-management.xml"/> |
893 |
</chapter> |
894 |
</part> |
895 |
|
896 |
</book> |
897 |
|
898 |
|
899 |
|
900 |
1.1 xml/htdocs/doc/en/handbook/2006.0/handbook-hppa.xml |
901 |
|
902 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/handbook-hppa.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
903 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/handbook-hppa.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
904 |
|
905 |
Index: handbook-hppa.xml |
906 |
=================================================================== |
907 |
<?xml version='1.0' encoding='UTF-8'?> |
908 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
909 |
|
910 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/handbook-hppa.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
911 |
|
912 |
<book link="handbook-hppa.xml"> |
913 |
<title>Gentoo Linux 2005.1 HPPA Handbook</title> |
914 |
|
915 |
<author title="Author"> |
916 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
917 |
</author> |
918 |
<author title="Author"> |
919 |
<mail link="uberlord@g.o">Roy Marples</mail> |
920 |
</author> |
921 |
<author title="Author"> |
922 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
923 |
</author> |
924 |
<author title="Author"> |
925 |
<mail link="chouser@g.o">Chris Houser</mail> |
926 |
</author> |
927 |
<author title="Author"> |
928 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
929 |
</author> |
930 |
<author title="Gentoo x86 Developer"> |
931 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
932 |
</author> |
933 |
<author title="Gentoo Alpha Developer"> |
934 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
935 |
</author><!-- Does not want to be listed on the rendered page |
936 |
<author title="Gentoo Developer"> |
937 |
Aron Griffis |
938 |
</author> |
939 |
--> |
940 |
<author title="Gentoo AMD64 Developer"> |
941 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
942 |
</author> |
943 |
<author title="Gentoo HPPA developer"> |
944 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
945 |
</author> |
946 |
<author title="Gentoo PPC developer"> |
947 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
948 |
</author> |
949 |
<author title="Gentoo SPARC developer"> |
950 |
<mail link="blademan@g.o">Joe Kallar</mail> |
951 |
</author> |
952 |
<author title="Editor"> |
953 |
<mail link="zhen@g.o">John P. Davis</mail> |
954 |
</author> |
955 |
<author title="Editor">Pierre-Henri Jondot</author> |
956 |
<author title="Editor"> |
957 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
958 |
</author> |
959 |
<author title="Editor"> |
960 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
961 |
</author> |
962 |
<author title="Editor"> |
963 |
<mail link="seo@g.o">Jungmin Seo</mail> |
964 |
</author> |
965 |
<author title="Editor"> |
966 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
967 |
</author> |
968 |
<author title="Editor"> |
969 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
970 |
</author> |
971 |
<author title="Editor"> |
972 |
<mail link="peitolm@g.o">Colin Morey</mail> |
973 |
</author> |
974 |
<author title="Editor"> |
975 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
976 |
</author> |
977 |
<author title="Editor"> |
978 |
<mail link="carl@g.o">Carl Anderson</mail> |
979 |
</author> |
980 |
<author title="Editor"> |
981 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
982 |
</author> |
983 |
<author title="Editor"> |
984 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
985 |
</author> |
986 |
<author title="Editor"> |
987 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
988 |
</author> |
989 |
<author title="Editor"> |
990 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
991 |
</author> |
992 |
<author title="Editor"> |
993 |
<mail link="erwin@g.o">Erwin</mail> |
994 |
</author> |
995 |
<author title="Editor"> |
996 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
997 |
</author> |
998 |
<author title="Editor"> |
999 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
1000 |
</author> |
1001 |
<author title="Editor"> |
1002 |
<mail link="neysx@g.o">Xavier Neys</mail> |
1003 |
</author> |
1004 |
<author title="Reviewer"> |
1005 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
1006 |
</author> |
1007 |
<author title="Reviewer"> |
1008 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
1009 |
</author> |
1010 |
<author title="Reviewer"> |
1011 |
<mail link="spyderous@g.o">Donnie Berkholz</mail> |
1012 |
</author> |
1013 |
<author title="Reviewer"> |
1014 |
<mail link="antifa@g.o">Ken Nowack</mail> |
1015 |
</author> |
1016 |
<author title="Contributor"> |
1017 |
<mail link="pylon@g.o">Lars Weiler</mail> |
1018 |
</author> |
1019 |
|
1020 |
<abstract> |
1021 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
1022 |
This handbook contains the installation instructions for a networkless |
1023 |
installation on HPPA systems and parts about working with Gentoo and Portage. |
1024 |
</abstract> |
1025 |
|
1026 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
1027 |
<!-- See http://creativecommons.org/licenses/by-sa/2.0 --> |
1028 |
<license/> |
1029 |
|
1030 |
<version>5.2</version> |
1031 |
<date>2005-10-13</date> |
1032 |
|
1033 |
<part> |
1034 |
<title>Installing Gentoo</title> |
1035 |
<abstract> |
1036 |
In this part you learn how to install Gentoo on your system. |
1037 |
</abstract> |
1038 |
|
1039 |
<chapter> |
1040 |
<title>About the Gentoo Linux Installation</title> |
1041 |
<abstract> |
1042 |
Users not familiar with Gentoo do not always know that choice is what |
1043 |
Gentoo is all about. |
1044 |
</abstract> |
1045 |
<include href="hb-install-about.xml"/> |
1046 |
</chapter> |
1047 |
|
1048 |
<chapter> |
1049 |
<title>Booting the Universal Installation CD</title> |
1050 |
<abstract> |
1051 |
Using our Universal Installation CD you can boot up your system into a running |
1052 |
environment that allows you to install Gentoo. |
1053 |
</abstract> |
1054 |
<include href="hb-install-hppa-medium.xml"/> |
1055 |
</chapter> |
1056 |
|
1057 |
<chapter> |
1058 |
<title>Configuring your Network</title> |
1059 |
<abstract> |
1060 |
If you need networking, this is the place where the network (and Internet |
1061 |
connection) is configured. |
1062 |
</abstract> |
1063 |
<include href="hb-install-network.xml"/> |
1064 |
</chapter> |
1065 |
|
1066 |
<chapter> |
1067 |
<title>Preparing the Disks</title> |
1068 |
<abstract> |
1069 |
To be able to install Gentoo, you must create the necessary partitions. |
1070 |
This chapter describes how to partition a disk for future usage. |
1071 |
</abstract> |
1072 |
<include href="hb-install-hppa-disk.xml"/> |
1073 |
</chapter> |
1074 |
|
1075 |
<chapter> |
1076 |
<title>Installing the Gentoo Installation Files</title> |
1077 |
<abstract> |
1078 |
Gentoo installs work through so-called stage-files. In this chapter we |
1079 |
describe how you extract a stage-file and configure Portage. |
1080 |
</abstract> |
1081 |
<include href="hb-install-stage.xml"/> |
1082 |
</chapter> |
1083 |
|
1084 |
<chapter> |
1085 |
<title>Chrooting into the Gentoo Base System</title> |
1086 |
<abstract> |
1087 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
1088 |
the USE variable. |
1089 |
</abstract> |
1090 |
<include href="hb-install-system.xml"/> |
1091 |
</chapter> |
1092 |
|
1093 |
<chapter> |
1094 |
<title>Configuring the Kernel</title> |
1095 |
<abstract> |
1096 |
The Linux kernel is the core of every distribution. This chapter |
1097 |
explains how to configure your kernel. |
1098 |
</abstract> |
1099 |
<include href="hb-install-hppa-kernel.xml"/> |
1100 |
</chapter> |
1101 |
|
1102 |
<chapter> |
1103 |
<title>Configuring your System</title> |
1104 |
<abstract> |
1105 |
You need to edit some important configuration files. In this chapter |
1106 |
you receive an overview of these files and an explanation on how to |
1107 |
proceed. |
1108 |
</abstract> |
1109 |
<include href="hb-install-config.xml"/> |
1110 |
</chapter> |
1111 |
|
1112 |
<chapter> |
1113 |
<title>Installing Necessary System Tools</title> |
1114 |
<abstract> |
1115 |
As mentioned before, Gentoo is about choices. In this chapter we help you |
1116 |
choose and install some important tools. |
1117 |
</abstract> |
1118 |
<include href="hb-install-tools.xml"/> |
1119 |
</chapter> |
1120 |
|
1121 |
<chapter> |
1122 |
<title>Configuring the Bootloader</title> |
1123 |
<abstract> |
1124 |
In this chapter we'll describe the PALO bootloader |
1125 |
and step you through the process of configuring PALO to your |
1126 |
needs. |
1127 |
</abstract> |
1128 |
<include href="hb-install-hppa-bootloader.xml"/> |
1129 |
</chapter> |
1130 |
|
1131 |
<chapter> |
1132 |
<title>Finalizing your Gentoo Installation</title> |
1133 |
<abstract> |
1134 |
You're almost done. We'll just create one (or more) users for your |
1135 |
system and (optionally) install prebuilt packages. |
1136 |
</abstract> |
1137 |
<include href="hb-install-finalise.xml"/> |
1138 |
</chapter> |
1139 |
|
1140 |
<chapter> |
1141 |
<title>Where to go from here?</title> |
1142 |
<abstract> |
1143 |
Now you have your Gentoo system, but what's next? |
1144 |
</abstract> |
1145 |
<include href="hb-install-next.xml"/> |
1146 |
</chapter> |
1147 |
</part> |
1148 |
|
1149 |
<part> |
1150 |
<title>Working with Gentoo</title> |
1151 |
<abstract> |
1152 |
Learn how to work with Gentoo: installing software, altering variables, changing |
1153 |
Portage behaviour etc. |
1154 |
</abstract> |
1155 |
|
1156 |
<chapter> |
1157 |
<title>A Portage Introduction</title> |
1158 |
<abstract> |
1159 |
This chapter explains the "simple" steps a user definitely needs to know to |
1160 |
maintain the software on his system. |
1161 |
</abstract> |
1162 |
<include href="../hb-working-portage.xml"/> |
1163 |
</chapter> |
1164 |
|
1165 |
<chapter> |
1166 |
<title>USE flags</title> |
1167 |
<abstract> |
1168 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
1169 |
work with USE-flags and understand how USE-flags interact with your system. |
1170 |
</abstract> |
1171 |
<include href="../hb-working-use.xml"/> |
1172 |
</chapter> |
1173 |
|
1174 |
<chapter> |
1175 |
<title>Portage Features</title> |
1176 |
<abstract> |
1177 |
Discover the features Portage has, such as support for distributed compiling, |
1178 |
ccache and more. |
1179 |
</abstract> |
1180 |
<include href="../hb-working-features.xml"/> |
1181 |
</chapter> |
1182 |
|
1183 |
<chapter> |
1184 |
<title>Initscripts</title> |
1185 |
<abstract> |
1186 |
Gentoo uses a special initscript format which, amongst other features, allows |
1187 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
1188 |
these aspects and explains how to deal with these scripts. |
1189 |
</abstract> |
1190 |
<include href="../hb-working-rcscripts.xml"/> |
1191 |
</chapter> |
1192 |
|
1193 |
<chapter> |
1194 |
<title>Environment Variables</title> |
1195 |
<abstract> |
1196 |
With Gentoo you can easily manage the environment variables for your system. |
1197 |
This chapter explains how you do that, and also describes frequently used |
1198 |
variables. |
1199 |
</abstract> |
1200 |
<include href="../hb-working-variables.xml"/> |
1201 |
</chapter> |
1202 |
</part> |
1203 |
|
1204 |
<part> |
1205 |
<title>Working with Portage</title> |
1206 |
<abstract> |
1207 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
1208 |
Software Management Tool. |
1209 |
</abstract> |
1210 |
|
1211 |
<chapter> |
1212 |
<title>Files and Directories</title> |
1213 |
<abstract> |
1214 |
Once you want to know Portage in-depth you need to know where it stores its |
1215 |
files and data. |
1216 |
</abstract> |
1217 |
<include href="../hb-portage-files.xml"/> |
1218 |
</chapter> |
1219 |
|
1220 |
<chapter> |
1221 |
<title>Configuring through Variables</title> |
1222 |
<abstract> |
1223 |
Portage is completely configurable through various variables you can set in the |
1224 |
configuration file or as environment variable. |
1225 |
</abstract> |
1226 |
<include href="../hb-portage-configuration.xml"/> |
1227 |
</chapter> |
1228 |
|
1229 |
<chapter> |
1230 |
<title>Mixing Software Branches</title> |
1231 |
<abstract> |
1232 |
Gentoo provides software separated in several branches, depending on stability |
1233 |
and architectural support. "Mixing Software Branches" inform you how these |
1234 |
branches can be configured and how you can override this separation |
1235 |
individually. |
1236 |
</abstract> |
1237 |
<include href="../hb-portage-branches.xml"/> |
1238 |
</chapter> |
1239 |
|
1240 |
<chapter> |
1241 |
<title>Additional Portage Tools</title> |
1242 |
<abstract> |
1243 |
Portage comes with a few extra tools that might make your Gentoo experience even |
1244 |
better. Read on to discover how to use dispatch-conf and other tools. |
1245 |
</abstract> |
1246 |
<include href="../hb-portage-tools.xml"/> |
1247 |
</chapter> |
1248 |
|
1249 |
<chapter> |
1250 |
<title>Diverting from the Official Tree</title> |
1251 |
<abstract> |
1252 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
1253 |
your own Portage tree, how to synchronise only the categories you want, inject |
1254 |
packages and more. |
1255 |
</abstract> |
1256 |
<include href="../hb-portage-diverttree.xml"/> |
1257 |
</chapter> |
1258 |
|
1259 |
<chapter> |
1260 |
<title>The Ebuild Application</title> |
1261 |
<abstract> |
1262 |
In "The Ebuild Application" you are informed about the steps Portage takes while |
1263 |
installing software and how you can do this yourself using the ebuild |
1264 |
application. |
1265 |
</abstract> |
1266 |
<include href="../hb-portage-ebuild.xml"/> |
1267 |
</chapter> |
1268 |
</part> |
1269 |
|
1270 |
<part> |
1271 |
<title>Gentoo Network Configuration</title> |
1272 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
1273 |
|
1274 |
<chapter> |
1275 |
<title>Getting Started</title> |
1276 |
<abstract> |
1277 |
A guide to quickly get your network interface up and running in most common |
1278 |
environments. |
1279 |
</abstract> |
1280 |
<include href="../hb-net-start.xml"/> |
1281 |
</chapter> |
1282 |
|
1283 |
<chapter> |
1284 |
<title>Advanced Configuration</title> |
1285 |
<abstract> |
1286 |
Here we learn about how the configuration works - you need to know this |
1287 |
before we learn about modular networking. |
1288 |
</abstract> |
1289 |
<include href="../hb-net-advanced.xml"/> |
1290 |
</chapter> |
1291 |
|
1292 |
<chapter> |
1293 |
<title>Modular Networking</title> |
1294 |
<abstract> |
1295 |
Gentoo provides you flexible networking - here you are told about choosing |
1296 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
1297 |
</abstract> |
1298 |
<include href="../hb-net-modules.xml"/> |
1299 |
</chapter> |
1300 |
|
1301 |
<chapter> |
1302 |
<title>Wireless Networking</title> |
1303 |
<abstract> |
1304 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
1305 |
</abstract> |
1306 |
<include href="../hb-net-wireless.xml"/> |
1307 |
</chapter> |
1308 |
|
1309 |
<chapter> |
1310 |
<title>Adding Functionality</title> |
1311 |
<abstract> |
1312 |
If you're feeling adventurous, you can add your own functions to networking. |
1313 |
</abstract> |
1314 |
<include href="../hb-net-functions.xml"/> |
1315 |
</chapter> |
1316 |
|
1317 |
<chapter> |
1318 |
<title>Network Management</title> |
1319 |
<abstract> |
1320 |
For laptop users or people who move their computer around different networks. |
1321 |
</abstract> |
1322 |
<include href="../hb-net-management.xml"/> |
1323 |
</chapter> |
1324 |
</part> |
1325 |
|
1326 |
</book> |
1327 |
|
1328 |
|
1329 |
|
1330 |
1.1 xml/htdocs/doc/en/handbook/2006.0/handbook-ppc.xml |
1331 |
|
1332 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/handbook-ppc.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
1333 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/handbook-ppc.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
1334 |
|
1335 |
Index: handbook-ppc.xml |
1336 |
=================================================================== |
1337 |
<?xml version='1.0' encoding='UTF-8'?> |
1338 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
1339 |
|
1340 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/handbook-ppc.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
1341 |
|
1342 |
<book link="handbook-ppc.xml"> |
1343 |
<title>Gentoo Linux 2005.1 PPC Handbook</title> |
1344 |
|
1345 |
<author title="Author"> |
1346 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
1347 |
</author> |
1348 |
<author title="Author"> |
1349 |
<mail link="uberlord@g.o">Roy Marples</mail> |
1350 |
</author> |
1351 |
<author title="Author"> |
1352 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
1353 |
</author> |
1354 |
<author title="Author"> |
1355 |
<mail link="chouser@g.o">Chris Houser</mail> |
1356 |
</author> |
1357 |
<author title="Author"> |
1358 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
1359 |
</author> |
1360 |
<author title="Gentoo x86 Developer"> |
1361 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
1362 |
</author> |
1363 |
<author title="Gentoo Alpha Developer"> |
1364 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
1365 |
</author><!-- Does not want to be listed on the rendered page |
1366 |
<author title="Gentoo Developer"> |
1367 |
Aron Griffis |
1368 |
</author> |
1369 |
--> |
1370 |
<author title="Gentoo AMD64 Developer"> |
1371 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
1372 |
</author> |
1373 |
<author title="Gentoo HPPA developer"> |
1374 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
1375 |
</author> |
1376 |
<author title="Gentoo PPC developer"> |
1377 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
1378 |
</author> |
1379 |
<author title="Gentoo SPARC developer"> |
1380 |
<mail link="blademan@g.o">Joe Kallar</mail> |
1381 |
</author> |
1382 |
<author title="Editor"> |
1383 |
<mail link="zhen@g.o">John P. Davis</mail> |
1384 |
</author> |
1385 |
<author title="Editor">Pierre-Henri Jondot</author> |
1386 |
<author title="Editor"> |
1387 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
1388 |
</author> |
1389 |
<author title="Editor"> |
1390 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
1391 |
</author> |
1392 |
<author title="Editor"> |
1393 |
<mail link="seo@g.o">Jungmin Seo</mail> |
1394 |
</author> |
1395 |
<author title="Editor"> |
1396 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
1397 |
</author> |
1398 |
<author title="Editor"> |
1399 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
1400 |
</author> |
1401 |
<author title="Editor"> |
1402 |
<mail link="peitolm@g.o">Colin Morey</mail> |
1403 |
</author> |
1404 |
<author title="Editor"> |
1405 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
1406 |
</author> |
1407 |
<author title="Editor"> |
1408 |
<mail link="carl@g.o">Carl Anderson</mail> |
1409 |
</author> |
1410 |
<author title="Editor"> |
1411 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
1412 |
</author> |
1413 |
<author title="Editor"> |
1414 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
1415 |
</author> |
1416 |
<author title="Editor"> |
1417 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
1418 |
</author> |
1419 |
<author title="Editor"> |
1420 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
1421 |
</author> |
1422 |
<author title="Editor"> |
1423 |
<mail link="erwin@g.o">Erwin</mail> |
1424 |
</author> |
1425 |
<author title="Editor"> |
1426 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
1427 |
</author> |
1428 |
<author title="Editor"> |
1429 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
1430 |
</author> |
1431 |
<author title="Editor"> |
1432 |
<mail link="pylon@g.o">Lars Weiler</mail> |
1433 |
</author> |
1434 |
<author title="Editor"> |
1435 |
<mail link="sejo@g.o">Jochen Maes </mail> |
1436 |
</author> |
1437 |
<author title="Editor"> |
1438 |
<mail link="neysx@g.o">Xavier Neys</mail> |
1439 |
</author> |
1440 |
<author title="Reviewer"> |
1441 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
1442 |
</author> |
1443 |
<author title="Reviewer"> |
1444 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
1445 |
</author> |
1446 |
<author title="Reviewer"> |
1447 |
<mail link="spyderous@g.o">Donnie Berkholz</mail> |
1448 |
</author> |
1449 |
<author title="Reviewer"> |
1450 |
<mail link="antifa@g.o">Ken Nowack</mail> |
1451 |
</author> |
1452 |
|
1453 |
<abstract> |
1454 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
1455 |
This handbook contains the installation instructions for a networkless |
1456 |
installation on PPC systems and parts about working with Gentoo and Portage. |
1457 |
</abstract> |
1458 |
|
1459 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
1460 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
1461 |
<license/> |
1462 |
|
1463 |
<version>5.2</version> |
1464 |
<date>2005-10-13</date> |
1465 |
|
1466 |
<part> |
1467 |
<title>Installing Gentoo</title> |
1468 |
<abstract> |
1469 |
In this part you learn how to install Gentoo on your system. |
1470 |
</abstract> |
1471 |
|
1472 |
<chapter> |
1473 |
<title>About the Gentoo Linux Installation</title> |
1474 |
<abstract> |
1475 |
Users not familiar with Gentoo do not always know that choice is what |
1476 |
Gentoo is all about. |
1477 |
</abstract> |
1478 |
<include href="hb-install-about.xml"/> |
1479 |
</chapter> |
1480 |
|
1481 |
<chapter> |
1482 |
<title>Booting the Universal Installation CD</title> |
1483 |
<abstract> |
1484 |
Using our Universal Installation CD you can boot up your system into a running |
1485 |
environment that allows you to install Gentoo. |
1486 |
</abstract> |
1487 |
<include href="hb-install-ppc-medium.xml"/> |
1488 |
</chapter> |
1489 |
|
1490 |
<chapter> |
1491 |
<title>Configuring your Network</title> |
1492 |
<abstract> |
1493 |
If you need networking, this is the place where the network (and Internet |
1494 |
connection) is configured. |
1495 |
</abstract> |
1496 |
<include href="hb-install-network.xml"/> |
1497 |
</chapter> |
1498 |
|
1499 |
<chapter> |
1500 |
<title>Preparing the Disks</title> |
1501 |
<abstract> |
1502 |
To be able to install Gentoo, you must create the necessary partitions. |
1503 |
This chapter describes how to partition a disk for future usage. |
1504 |
</abstract> |
1505 |
<include href="hb-install-ppc-disk.xml"/> |
1506 |
</chapter> |
1507 |
|
1508 |
<chapter> |
1509 |
<title>Installing the Gentoo Installation Files</title> |
1510 |
<abstract> |
1511 |
In this chapter we describe how you extract a stage3 file and how to configure |
1512 |
Portage. |
1513 |
</abstract> |
1514 |
<include href="hb-install-stage.xml"/> |
1515 |
</chapter> |
1516 |
|
1517 |
<chapter> |
1518 |
<title>Chrooting into the Gentoo Base System</title> |
1519 |
<abstract> |
1520 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
1521 |
the USE variable. |
1522 |
</abstract> |
1523 |
<include href="hb-install-system.xml"/> |
1524 |
</chapter> |
1525 |
|
1526 |
<chapter> |
1527 |
<title>Configuring the Kernel</title> |
1528 |
<abstract> |
1529 |
The Linux kernel is the core of every distribution. This chapter |
1530 |
explains how to configure your kernel. |
1531 |
</abstract> |
1532 |
<include href="hb-install-ppc-kernel.xml"/> |
1533 |
</chapter> |
1534 |
|
1535 |
<chapter> |
1536 |
<title>Configuring your System</title> |
1537 |
<abstract> |
1538 |
You need to edit some important configuration files. In this chapter |
1539 |
you receive an overview of these files and an explanation on how to |
1540 |
proceed. |
1541 |
</abstract> |
1542 |
<include href="hb-install-config.xml"/> |
1543 |
</chapter> |
1544 |
|
1545 |
<chapter> |
1546 |
<title>Installing Necessary System Tools</title> |
1547 |
<abstract> |
1548 |
As mentioned before, Gentoo is about choices. In this chapter we help you |
1549 |
choose and install some important tools. |
1550 |
</abstract> |
1551 |
<include href="hb-install-tools.xml"/> |
1552 |
</chapter> |
1553 |
|
1554 |
<chapter> |
1555 |
<title>Configuring the Bootloader</title> |
1556 |
<abstract> |
1557 |
Several bootloaders exist. Each one of them has its own way of |
1558 |
configuration. In this chapter we'll describe all possibilities for you |
1559 |
and step you through the process of configuring a bootloader to your |
1560 |
needs. |
1561 |
</abstract> |
1562 |
<include href="hb-install-ppc-bootloader.xml"/> |
1563 |
</chapter> |
1564 |
|
1565 |
<chapter> |
1566 |
<title>Finalizing your Gentoo Installation</title> |
1567 |
<abstract> |
1568 |
You're almost done. We'll just create one (or more) users for your |
1569 |
system and (optionally) install prebuilt packages. |
1570 |
</abstract> |
1571 |
<include href="hb-install-finalise.xml"/> |
1572 |
</chapter> |
1573 |
|
1574 |
<chapter> |
1575 |
<title>Where to go from here?</title> |
1576 |
<abstract> |
1577 |
Now you have your Gentoo system, but what's next? |
1578 |
</abstract> |
1579 |
<include href="hb-install-next.xml"/> |
1580 |
</chapter> |
1581 |
</part> |
1582 |
|
1583 |
<part> |
1584 |
<title>Working with Gentoo</title> |
1585 |
<abstract> |
1586 |
Learn how to work with Gentoo: installing software, altering variables, changing |
1587 |
Portage behaviour etc. |
1588 |
</abstract> |
1589 |
|
1590 |
<chapter> |
1591 |
<title>A Portage Introduction</title> |
1592 |
<abstract> |
1593 |
This chapter explains the "simple" steps a user definitely needs to know to |
1594 |
maintain the software on his system. |
1595 |
</abstract> |
1596 |
<include href="../hb-working-portage.xml"/> |
1597 |
</chapter> |
1598 |
|
1599 |
<chapter> |
1600 |
<title>USE flags</title> |
1601 |
<abstract> |
1602 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
1603 |
work with USE-flags and understand how USE-flags interact with your system. |
1604 |
</abstract> |
1605 |
<include href="../hb-working-use.xml"/> |
1606 |
</chapter> |
1607 |
|
1608 |
<chapter> |
1609 |
<title>Portage Features</title> |
1610 |
<abstract> |
1611 |
Discover the features Portage has, such as support for distributed compiling, |
1612 |
ccache and more. |
1613 |
</abstract> |
1614 |
<include href="../hb-working-features.xml"/> |
1615 |
</chapter> |
1616 |
|
1617 |
<chapter> |
1618 |
<title>Initscripts</title> |
1619 |
<abstract> |
1620 |
Gentoo uses a special initscript format which, amongst other features, allows |
1621 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
1622 |
these aspects and explains how to deal with these scripts. |
1623 |
</abstract> |
1624 |
<include href="../hb-working-rcscripts.xml"/> |
1625 |
</chapter> |
1626 |
|
1627 |
<chapter> |
1628 |
<title>Environment Variables</title> |
1629 |
<abstract> |
1630 |
With Gentoo you can easily manage the environment variables for your system. |
1631 |
This chapter explains how you do that, and also describes frequently used |
1632 |
variables. |
1633 |
</abstract> |
1634 |
<include href="../hb-working-variables.xml"/> |
1635 |
</chapter> |
1636 |
</part> |
1637 |
|
1638 |
<part> |
1639 |
<title>Working with Portage</title> |
1640 |
<abstract> |
1641 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
1642 |
Software Management Tool. |
1643 |
</abstract> |
1644 |
|
1645 |
<chapter> |
1646 |
<title>Files and Directories</title> |
1647 |
<abstract> |
1648 |
Once you want to know Portage in-depth you need to know where it stores its |
1649 |
files and data. |
1650 |
</abstract> |
1651 |
<include href="../hb-portage-files.xml"/> |
1652 |
</chapter> |
1653 |
|
1654 |
<chapter> |
1655 |
<title>Configuring through Variables</title> |
1656 |
<abstract> |
1657 |
Portage is completely configurable through various variables you can set in the |
1658 |
configuration file or as environment variable. |
1659 |
</abstract> |
1660 |
<include href="../hb-portage-configuration.xml"/> |
1661 |
</chapter> |
1662 |
|
1663 |
<chapter> |
1664 |
<title>Mixing Software Branches</title> |
1665 |
<abstract> |
1666 |
Gentoo provides software separated in several branches, depending on stability |
1667 |
and architectural support. "Mixing Software Branches" inform you how these |
1668 |
branches can be configured and how you can override this separation |
1669 |
individually. |
1670 |
</abstract> |
1671 |
<include href="../hb-portage-branches.xml"/> |
1672 |
</chapter> |
1673 |
|
1674 |
<chapter> |
1675 |
<title>Additional Portage Tools</title> |
1676 |
<abstract> |
1677 |
Portage comes with a few extra tools that might make your Gentoo experience even |
1678 |
better. Read on to discover how to use dispatch-conf and other tools. |
1679 |
</abstract> |
1680 |
<include href="../hb-portage-tools.xml"/> |
1681 |
</chapter> |
1682 |
|
1683 |
<chapter> |
1684 |
<title>Diverting from the Official Tree</title> |
1685 |
<abstract> |
1686 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
1687 |
your own Portage tree, how to synchronise only the categories you want, inject |
1688 |
packages and more. |
1689 |
</abstract> |
1690 |
<include href="../hb-portage-diverttree.xml"/> |
1691 |
</chapter> |
1692 |
|
1693 |
<chapter> |
1694 |
<title>The Ebuild Application</title> |
1695 |
<abstract> |
1696 |
In "The Ebuild Application" you are informed about the steps Portage takes while |
1697 |
installing software and how you can do this yourself using the ebuild |
1698 |
application. |
1699 |
</abstract> |
1700 |
<include href="../hb-portage-ebuild.xml"/> |
1701 |
</chapter> |
1702 |
</part> |
1703 |
|
1704 |
<part> |
1705 |
<title>Gentoo Network Configuration</title> |
1706 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
1707 |
|
1708 |
<chapter> |
1709 |
<title>Getting Started</title> |
1710 |
<abstract> |
1711 |
A guide to quickly get your network interface up and running in most common |
1712 |
environments. |
1713 |
</abstract> |
1714 |
<include href="../hb-net-start.xml"/> |
1715 |
</chapter> |
1716 |
|
1717 |
<chapter> |
1718 |
<title>Advanced Configuration</title> |
1719 |
<abstract> |
1720 |
Here we learn about how the configuration works - you need to know this |
1721 |
before we learn about modular networking. |
1722 |
</abstract> |
1723 |
<include href="../hb-net-advanced.xml"/> |
1724 |
</chapter> |
1725 |
|
1726 |
<chapter> |
1727 |
<title>Modular Networking</title> |
1728 |
<abstract> |
1729 |
Gentoo provides you flexible networking - here you are told about choosing |
1730 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
1731 |
</abstract> |
1732 |
<include href="../hb-net-modules.xml"/> |
1733 |
</chapter> |
1734 |
|
1735 |
<chapter> |
1736 |
<title>Wireless Networking</title> |
1737 |
<abstract> |
1738 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
1739 |
</abstract> |
1740 |
<include href="../hb-net-wireless.xml"/> |
1741 |
</chapter> |
1742 |
|
1743 |
<chapter> |
1744 |
<title>Adding Functionality</title> |
1745 |
<abstract> |
1746 |
If you're feeling adventurous, you can add your own functions to networking. |
1747 |
</abstract> |
1748 |
<include href="../hb-net-functions.xml"/> |
1749 |
</chapter> |
1750 |
|
1751 |
<chapter> |
1752 |
<title>Network Management</title> |
1753 |
<abstract> |
1754 |
For laptop users or people who move their computer around different networks. |
1755 |
</abstract> |
1756 |
<include href="../hb-net-management.xml"/> |
1757 |
</chapter> |
1758 |
</part> |
1759 |
|
1760 |
</book> |
1761 |
|
1762 |
|
1763 |
|
1764 |
1.1 xml/htdocs/doc/en/handbook/2006.0/handbook-ppc64.xml |
1765 |
|
1766 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/handbook-ppc64.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
1767 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/handbook-ppc64.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
1768 |
|
1769 |
Index: handbook-ppc64.xml |
1770 |
=================================================================== |
1771 |
<?xml version='1.0' encoding='UTF-8'?> |
1772 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
1773 |
|
1774 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/handbook-ppc64.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
1775 |
|
1776 |
<book link="handbook-ppc64.xml"> |
1777 |
<title>Gentoo Linux 2005.1 PPC64 Handbook</title> |
1778 |
|
1779 |
<author title="Author"> |
1780 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
1781 |
</author> |
1782 |
<author title="Author"> |
1783 |
<mail link="uberlord@g.o">Roy Marples</mail> |
1784 |
</author> |
1785 |
<author title="Author"> |
1786 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
1787 |
</author> |
1788 |
<author title="Author"> |
1789 |
<mail link="chouser@g.o">Chris Houser</mail> |
1790 |
</author> |
1791 |
<author title="Author"> |
1792 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
1793 |
</author> |
1794 |
<author title="Gentoo x86 Developer"> |
1795 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
1796 |
</author> |
1797 |
<author title="Gentoo Alpha Developer"> |
1798 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
1799 |
</author><!-- Does not want to be listed on the rendered page |
1800 |
<author title="Gentoo Developer"> |
1801 |
Aron Griffis |
1802 |
</author> |
1803 |
--> |
1804 |
<author title="Gentoo AMD64 Developer"> |
1805 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
1806 |
</author> |
1807 |
<author title="Gentoo HPPA developer"> |
1808 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
1809 |
</author> |
1810 |
<author title="Gentoo PPC developer"> |
1811 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
1812 |
</author> |
1813 |
<author title="Gentoo SPARC developer"> |
1814 |
<mail link="blademan@g.o">Joe Kallar</mail> |
1815 |
</author> |
1816 |
<author title="Editor"> |
1817 |
<mail link="zhen@g.o">John P. Davis</mail> |
1818 |
</author> |
1819 |
<author title="Editor">Pierre-Henri Jondot</author> |
1820 |
<author title="Editor"> |
1821 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
1822 |
</author> |
1823 |
<author title="Editor"> |
1824 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
1825 |
</author> |
1826 |
<author title="Editor"> |
1827 |
<mail link="seo@g.o">Jungmin Seo</mail> |
1828 |
</author> |
1829 |
<author title="Editor"> |
1830 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
1831 |
</author> |
1832 |
<author title="Editor"> |
1833 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
1834 |
</author> |
1835 |
<author title="Editor"> |
1836 |
<mail link="peitolm@g.o">Colin Morey</mail> |
1837 |
</author> |
1838 |
<author title="Editor"> |
1839 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
1840 |
</author> |
1841 |
<author title="Editor"> |
1842 |
<mail link="carl@g.o">Carl Anderson</mail> |
1843 |
</author> |
1844 |
<author title="Editor"> |
1845 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
1846 |
</author> |
1847 |
<author title="Editor"> |
1848 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
1849 |
</author> |
1850 |
<author title="Editor"> |
1851 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
1852 |
</author> |
1853 |
<author title="Editor"> |
1854 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
1855 |
</author> |
1856 |
<author title="Editor"> |
1857 |
<mail link="erwin@g.o">Erwin</mail> |
1858 |
</author> |
1859 |
<author title="Editor"> |
1860 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
1861 |
</author> |
1862 |
<author title="Editor"> |
1863 |
<mail link="neysx@g.o">Xavier Neys</mail> |
1864 |
</author> |
1865 |
<author title="Reviewer"> |
1866 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
1867 |
</author> |
1868 |
<author title="Reviewer"> |
1869 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
1870 |
</author> |
1871 |
<author title="Reviewer"> |
1872 |
<mail link="spyderous@g.o">Donnie Berkholz</mail> |
1873 |
</author> |
1874 |
<author title="Reviewer"> |
1875 |
<mail link="antifa@g.o">Ken Nowack</mail> |
1876 |
</author> |
1877 |
<author title="Contributor"> |
1878 |
<mail link="pylon@g.o">Lars Weiler</mail> |
1879 |
</author> |
1880 |
<author title="Editor"> |
1881 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
1882 |
</author> |
1883 |
|
1884 |
<abstract> |
1885 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
1886 |
This handbook contains the installation instructions for a networkless |
1887 |
installation on PPC64 systems and parts about working with Gentoo and Portage. |
1888 |
</abstract> |
1889 |
|
1890 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
1891 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
1892 |
<license/> |
1893 |
|
1894 |
<version>5.2</version> |
1895 |
<date>2005-10-13</date> |
1896 |
|
1897 |
<part> |
1898 |
<title>Installing Gentoo</title> |
1899 |
<abstract> |
1900 |
In this part you learn how to install Gentoo on your system. |
1901 |
</abstract> |
1902 |
|
1903 |
<chapter> |
1904 |
<title>About the Gentoo Linux Installation</title> |
1905 |
<abstract> |
1906 |
Users not familiar with Gentoo do not always know that choice is what |
1907 |
Gentoo is all about. |
1908 |
</abstract> |
1909 |
<include href="hb-install-about.xml"/> |
1910 |
</chapter> |
1911 |
|
1912 |
<chapter> |
1913 |
<title>Booting the Universal Installation CD</title> |
1914 |
<abstract> |
1915 |
Using our Universal Installation CD you can boot up your system into a running |
1916 |
environment that allows you to install Gentoo. |
1917 |
</abstract> |
1918 |
<include href="hb-install-ppc64-medium.xml"/> |
1919 |
</chapter> |
1920 |
|
1921 |
<chapter> |
1922 |
<title>Configuring your Network</title> |
1923 |
<abstract> |
1924 |
If you need networking, this is the place where the network (and Internet |
1925 |
connection) is configured. |
1926 |
</abstract> |
1927 |
<include href="hb-install-network.xml"/> |
1928 |
</chapter> |
1929 |
|
1930 |
<chapter> |
1931 |
<title>Preparing the Disks</title> |
1932 |
<abstract> |
1933 |
To be able to install Gentoo, you must create the necessary partitions. |
1934 |
This chapter describes how to partition a disk for future usage. |
1935 |
</abstract> |
1936 |
<include href="hb-install-ppc64-disk.xml"/> |
1937 |
</chapter> |
1938 |
|
1939 |
<chapter> |
1940 |
<title>Installing the Gentoo Installation Files</title> |
1941 |
<abstract> |
1942 |
In this chapter we describe how you extract a stage3 file and how to configure |
1943 |
Portage. |
1944 |
</abstract> |
1945 |
<include href="hb-install-stage.xml"/> |
1946 |
</chapter> |
1947 |
|
1948 |
<chapter> |
1949 |
<title>Chrooting into the Gentoo Base System</title> |
1950 |
<abstract> |
1951 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
1952 |
the USE variable. |
1953 |
</abstract> |
1954 |
<include href="hb-install-system.xml"/> |
1955 |
</chapter> |
1956 |
|
1957 |
<chapter> |
1958 |
<title>Configuring the Kernel</title> |
1959 |
<abstract> |
1960 |
The Linux kernel is the core of every distribution. This chapter |
1961 |
explains how to configure your kernel. |
1962 |
</abstract> |
1963 |
<include href="hb-install-ppc64-kernel.xml"/> |
1964 |
</chapter> |
1965 |
|
1966 |
<chapter> |
1967 |
<title>Configuring your System</title> |
1968 |
<abstract> |
1969 |
You need to edit some important configuration files. In this chapter |
1970 |
you receive an overview of these files and an explanation on how to |
1971 |
proceed. |
1972 |
</abstract> |
1973 |
<include href="hb-install-config.xml"/> |
1974 |
</chapter> |
1975 |
|
1976 |
<chapter> |
1977 |
<title>Installing Necessary System Tools</title> |
1978 |
<abstract> |
1979 |
As mentioned before, Gentoo is about choices. In this chapter we help you |
1980 |
choose and install some important tools. |
1981 |
</abstract> |
1982 |
<include href="hb-install-tools.xml"/> |
1983 |
</chapter> |
1984 |
|
1985 |
<chapter> |
1986 |
<title>Configuring the Bootloader</title> |
1987 |
<abstract> |
1988 |
Several bootloaders exist. Each one of them has its own way of |
1989 |
configuration. In this chapter we'll describe all possibilities for you |
1990 |
and step you through the process of configuring a bootloader to your |
1991 |
needs. |
1992 |
</abstract> |
1993 |
<include href="hb-install-ppc64-bootloader.xml"/> |
1994 |
</chapter> |
1995 |
|
1996 |
|
1997 |
<chapter> |
1998 |
<title>Finalizing your Gentoo Installation</title> |
1999 |
<abstract> |
2000 |
You're almost done. We'll just create one (or more) users for your |
2001 |
system and (optionally) install prebuilt packages. |
2002 |
</abstract> |
2003 |
<include href="hb-install-finalise.xml"/> |
2004 |
</chapter> |
2005 |
|
2006 |
<chapter> |
2007 |
<title>Where to go from here?</title> |
2008 |
<abstract> |
2009 |
Now you have your Gentoo system, but what's next? |
2010 |
</abstract> |
2011 |
<include href="hb-install-next.xml"/> |
2012 |
</chapter> |
2013 |
</part> |
2014 |
|
2015 |
<part> |
2016 |
<title>Working with Gentoo</title> |
2017 |
<abstract> |
2018 |
Learn how to work with Gentoo: installing software, altering variables, changing |
2019 |
Portage behaviour etc. |
2020 |
</abstract> |
2021 |
|
2022 |
<chapter> |
2023 |
<title>A Portage Introduction</title> |
2024 |
<abstract> |
2025 |
This chapter explains the "simple" steps a user definitely needs to know to |
2026 |
maintain the software on his system. |
2027 |
</abstract> |
2028 |
<include href="../hb-working-portage.xml"/> |
2029 |
</chapter> |
2030 |
|
2031 |
<chapter> |
2032 |
<title>USE flags</title> |
2033 |
<abstract> |
2034 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
2035 |
work with USE-flags and understand how USE-flags interact with your system. |
2036 |
</abstract> |
2037 |
<include href="../hb-working-use.xml"/> |
2038 |
</chapter> |
2039 |
|
2040 |
<chapter> |
2041 |
<title>Portage Features</title> |
2042 |
<abstract> |
2043 |
Discover the features Portage has, such as support for distributed compiling, |
2044 |
ccache and more. |
2045 |
</abstract> |
2046 |
<include href="../hb-working-features.xml"/> |
2047 |
</chapter> |
2048 |
|
2049 |
<chapter> |
2050 |
<title>Initscripts</title> |
2051 |
<abstract> |
2052 |
Gentoo uses a special initscript format which, amongst other features, allows |
2053 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
2054 |
these aspects and explains how to deal with these scripts. |
2055 |
</abstract> |
2056 |
<include href="../hb-working-rcscripts.xml"/> |
2057 |
</chapter> |
2058 |
|
2059 |
<chapter> |
2060 |
<title>Environment Variables</title> |
2061 |
<abstract> |
2062 |
With Gentoo you can easily manage the environment variables for your system. |
2063 |
This chapter explains how you do that, and also describes frequently used |
2064 |
variables. |
2065 |
</abstract> |
2066 |
<include href="../hb-working-variables.xml"/> |
2067 |
</chapter> |
2068 |
</part> |
2069 |
|
2070 |
<part> |
2071 |
<title>Working with Portage</title> |
2072 |
<abstract> |
2073 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
2074 |
Software Management Tool. |
2075 |
</abstract> |
2076 |
|
2077 |
<chapter> |
2078 |
<title>Files and Directories</title> |
2079 |
<abstract> |
2080 |
Once you want to know Portage in-depth you need to know where it stores its |
2081 |
files and data. |
2082 |
</abstract> |
2083 |
<include href="../hb-portage-files.xml"/> |
2084 |
</chapter> |
2085 |
|
2086 |
<chapter> |
2087 |
<title>Configuring through Variables</title> |
2088 |
<abstract> |
2089 |
Portage is completely configurable through various variables you can set in the |
2090 |
configuration file or as environment variable. |
2091 |
</abstract> |
2092 |
<include href="../hb-portage-configuration.xml"/> |
2093 |
</chapter> |
2094 |
|
2095 |
<chapter> |
2096 |
<title>Mixing Software Branches</title> |
2097 |
<abstract> |
2098 |
Gentoo provides software separated in several branches, depending on stability |
2099 |
and architectural support. "Mixing Software Branches" inform you how these |
2100 |
branches can be configured and how you can override this separation |
2101 |
individually. |
2102 |
</abstract> |
2103 |
<include href="../hb-portage-branches.xml"/> |
2104 |
</chapter> |
2105 |
|
2106 |
<chapter> |
2107 |
<title>Additional Portage Tools</title> |
2108 |
<abstract> |
2109 |
Portage comes with a few extra tools that might make your Gentoo experience even |
2110 |
better. Read on to discover how to use dispatch-conf and other tools. |
2111 |
</abstract> |
2112 |
<include href="../hb-portage-tools.xml"/> |
2113 |
</chapter> |
2114 |
|
2115 |
<chapter> |
2116 |
<title>Diverting from the Official Tree</title> |
2117 |
<abstract> |
2118 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
2119 |
your own Portage tree, how to synchronise only the categories you want, inject |
2120 |
packages and more. |
2121 |
</abstract> |
2122 |
<include href="../hb-portage-diverttree.xml"/> |
2123 |
</chapter> |
2124 |
|
2125 |
<chapter> |
2126 |
<title>The Ebuild Application</title> |
2127 |
<abstract> |
2128 |
In "The Ebuild Application" you are informed about the steps Portage takes while |
2129 |
installing software and how you can do this yourself using the ebuild |
2130 |
application. |
2131 |
</abstract> |
2132 |
<include href="../hb-portage-ebuild.xml"/> |
2133 |
</chapter> |
2134 |
</part> |
2135 |
|
2136 |
<part> |
2137 |
<title>Gentoo Network Configuration</title> |
2138 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
2139 |
|
2140 |
<chapter> |
2141 |
<title>Getting Started</title> |
2142 |
<abstract> |
2143 |
A guide to quickly get your network interface up and running in most common |
2144 |
environments. |
2145 |
</abstract> |
2146 |
<include href="../hb-net-start.xml"/> |
2147 |
</chapter> |
2148 |
|
2149 |
<chapter> |
2150 |
<title>Advanced Configuration</title> |
2151 |
<abstract> |
2152 |
Here we learn about how the configuration works - you need to know this |
2153 |
before we learn about modular networking. |
2154 |
</abstract> |
2155 |
<include href="../hb-net-advanced.xml"/> |
2156 |
</chapter> |
2157 |
|
2158 |
<chapter> |
2159 |
<title>Modular Networking</title> |
2160 |
<abstract> |
2161 |
Gentoo provides you flexible networking - here you are told about choosing |
2162 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
2163 |
</abstract> |
2164 |
<include href="../hb-net-modules.xml"/> |
2165 |
</chapter> |
2166 |
|
2167 |
<chapter> |
2168 |
<title>Wireless Networking</title> |
2169 |
<abstract> |
2170 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
2171 |
</abstract> |
2172 |
<include href="../hb-net-wireless.xml"/> |
2173 |
</chapter> |
2174 |
|
2175 |
<chapter> |
2176 |
<title>Adding Functionality</title> |
2177 |
<abstract> |
2178 |
If you're feeling adventurous, you can add your own functions to networking. |
2179 |
</abstract> |
2180 |
<include href="../hb-net-functions.xml"/> |
2181 |
</chapter> |
2182 |
|
2183 |
<chapter> |
2184 |
<title>Network Management</title> |
2185 |
<abstract> |
2186 |
For laptop users or people who move their computer around different networks. |
2187 |
</abstract> |
2188 |
<include href="../hb-net-management.xml"/> |
2189 |
</chapter> |
2190 |
</part> |
2191 |
|
2192 |
</book> |
2193 |
|
2194 |
|
2195 |
|
2196 |
1.1 xml/htdocs/doc/en/handbook/2006.0/handbook-sparc.xml |
2197 |
|
2198 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/handbook-sparc.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
2199 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/handbook-sparc.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
2200 |
|
2201 |
Index: handbook-sparc.xml |
2202 |
=================================================================== |
2203 |
<?xml version='1.0' encoding='UTF-8'?> |
2204 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
2205 |
|
2206 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/handbook-sparc.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
2207 |
|
2208 |
<book link="handbook-sparc.xml"> |
2209 |
<title>Gentoo Linux 2005.1 SPARC Handbook</title> |
2210 |
|
2211 |
<author title="Author"> |
2212 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
2213 |
</author> |
2214 |
<author title="Author"> |
2215 |
<mail link="uberlord@g.o">Roy Marples</mail> |
2216 |
</author> |
2217 |
<author title="Author"> |
2218 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
2219 |
</author> |
2220 |
<author title="Author"> |
2221 |
<mail link="chouser@g.o">Chris Houser</mail> |
2222 |
</author> |
2223 |
<author title="Author"> |
2224 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
2225 |
</author> |
2226 |
<author title="Gentoo x86 Developer"> |
2227 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
2228 |
</author> |
2229 |
<author title="Gentoo Alpha Developer"> |
2230 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
2231 |
</author><!-- Does not want to be listed on the rendered page |
2232 |
<author title="Gentoo Developer"> |
2233 |
Aron Griffis |
2234 |
</author> |
2235 |
--> |
2236 |
<author title="Gentoo AMD64 Developer"> |
2237 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
2238 |
</author> |
2239 |
<author title="Gentoo HPPA developer"> |
2240 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
2241 |
</author> |
2242 |
<author title="Gentoo PPC developer"> |
2243 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
2244 |
</author> |
2245 |
<author title="Gentoo SPARC developer"> |
2246 |
<mail link="blademan@g.o">Joe Kallar</mail> |
2247 |
</author> |
2248 |
<author title="Editor"> |
2249 |
<mail link="zhen@g.o">John P. Davis</mail> |
2250 |
</author> |
2251 |
<author title="Editor">Pierre-Henri Jondot</author> |
2252 |
<author title="Editor"> |
2253 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
2254 |
</author> |
2255 |
<author title="Editor"> |
2256 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
2257 |
</author> |
2258 |
<author title="Editor"> |
2259 |
<mail link="seo@g.o">Jungmin Seo</mail> |
2260 |
</author> |
2261 |
<author title="Editor"> |
2262 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
2263 |
</author> |
2264 |
<author title="Editor"> |
2265 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
2266 |
</author> |
2267 |
<author title="Editor"> |
2268 |
<mail link="peitolm@g.o">Colin Morey</mail> |
2269 |
</author> |
2270 |
<author title="Editor"> |
2271 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
2272 |
</author> |
2273 |
<author title="Editor"> |
2274 |
<mail link="carl@g.o">Carl Anderson</mail> |
2275 |
</author> |
2276 |
<author title="Editor"> |
2277 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
2278 |
</author> |
2279 |
<author title="Editor"> |
2280 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
2281 |
</author> |
2282 |
<author title="Editor"> |
2283 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
2284 |
</author> |
2285 |
<author title="Editor"> |
2286 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
2287 |
</author> |
2288 |
<author title="Editor"> |
2289 |
<mail link="erwin@g.o">Erwin</mail> |
2290 |
</author> |
2291 |
<author title="Editor"> |
2292 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
2293 |
</author> |
2294 |
<author title="Editor"> |
2295 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
2296 |
</author> |
2297 |
<author title="Editor"> |
2298 |
<mail link="neysx@g.o">Xavier Neys</mail> |
2299 |
</author> |
2300 |
<author title="Reviewer"> |
2301 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
2302 |
</author> |
2303 |
<author title="Reviewer"> |
2304 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
2305 |
</author> |
2306 |
<author title="Reviewer"> |
2307 |
<mail link="spyderous@g.o">Donnie Berkholz</mail> |
2308 |
</author> |
2309 |
<author title="Reviewer"> |
2310 |
<mail link="antifa@g.o">Ken Nowack</mail> |
2311 |
</author> |
2312 |
<author title="Contributor"> |
2313 |
<mail link="pylon@g.o">Lars Weiler</mail> |
2314 |
</author> |
2315 |
|
2316 |
<abstract> |
2317 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
2318 |
This handbook contains the installation instructions for a networkless |
2319 |
installation on Sparc systems and parts about working with Gentoo and Portage. |
2320 |
</abstract> |
2321 |
|
2322 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
2323 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
2324 |
<license/> |
2325 |
|
2326 |
<version>5.2</version> |
2327 |
<date>2005-10-13</date> |
2328 |
|
2329 |
<part> |
2330 |
<title>Installing Gentoo</title> |
2331 |
<abstract> |
2332 |
In this part you learn how to install Gentoo on your system. |
2333 |
</abstract> |
2334 |
|
2335 |
<chapter> |
2336 |
<title>About the Gentoo Linux Installation</title> |
2337 |
<abstract> |
2338 |
Users not familiar with Gentoo do not always know that choice is what |
2339 |
Gentoo is all about. |
2340 |
</abstract> |
2341 |
<include href="hb-install-about.xml"/> |
2342 |
</chapter> |
2343 |
|
2344 |
<chapter> |
2345 |
<title>Booting the Universal Installation CD</title> |
2346 |
<abstract> |
2347 |
Using our Universal Installation CD you can boot up your system into a running |
2348 |
environment that allows you to install Gentoo. |
2349 |
</abstract> |
2350 |
<include href="hb-install-sparc-medium.xml"/> |
2351 |
</chapter> |
2352 |
|
2353 |
<chapter> |
2354 |
<title>Configuring your Network</title> |
2355 |
<abstract> |
2356 |
If you need networking, this is the place where the network (and Internet |
2357 |
connection) is configured. |
2358 |
</abstract> |
2359 |
<include href="hb-install-network.xml"/> |
2360 |
</chapter> |
2361 |
|
2362 |
<chapter> |
2363 |
<title>Preparing the Disks</title> |
2364 |
<abstract> |
2365 |
To be able to install Gentoo, you must create the necessary partitions. |
2366 |
This chapter describes how to partition a disk for future usage. |
2367 |
</abstract> |
2368 |
<include href="hb-install-sparc-disk.xml"/> |
2369 |
</chapter> |
2370 |
|
2371 |
<chapter> |
2372 |
<title>Installing the Gentoo Installation Files</title> |
2373 |
<abstract> |
2374 |
In this chapter we describe how you extract a stage3 file and how to configure |
2375 |
Portage. |
2376 |
</abstract> |
2377 |
<include href="hb-install-stage.xml"/> |
2378 |
</chapter> |
2379 |
|
2380 |
<chapter> |
2381 |
<title>Chrooting into the Gentoo Base System</title> |
2382 |
<abstract> |
2383 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
2384 |
the USE variable. |
2385 |
</abstract> |
2386 |
<include href="hb-install-system.xml"/> |
2387 |
</chapter> |
2388 |
|
2389 |
<chapter> |
2390 |
<title>Configuring the Kernel</title> |
2391 |
<abstract> |
2392 |
The Linux kernel is the core of every distribution. This chapter |
2393 |
explains how to configure your kernel. |
2394 |
</abstract> |
2395 |
<include href="hb-install-sparc-kernel.xml"/> |
2396 |
</chapter> |
2397 |
|
2398 |
<chapter> |
2399 |
<title>Configuring your System</title> |
2400 |
<abstract> |
2401 |
You need to edit some important configuration files. In this chapter |
2402 |
you receive an overview of these files and an explanation on how to |
2403 |
proceed. |
2404 |
</abstract> |
2405 |
<include href="hb-install-config.xml"/> |
2406 |
</chapter> |
2407 |
|
2408 |
<chapter> |
2409 |
<title>Installing Necessary System Tools</title> |
2410 |
<abstract> |
2411 |
As mentioned before, Gentoo is about choices. In this chapter we help you |
2412 |
choose and install some important tools. |
2413 |
</abstract> |
2414 |
<include href="hb-install-tools.xml"/> |
2415 |
</chapter> |
2416 |
|
2417 |
<chapter> |
2418 |
<title>Configuring the Bootloader</title> |
2419 |
<abstract> |
2420 |
The SPARC architecture uses the SILO bootloader to fire up your Linux system. In |
2421 |
this chapter we step you through the process of configuring this bootloader to |
2422 |
your needs. |
2423 |
</abstract> |
2424 |
<include href="hb-install-sparc-bootloader.xml"/> |
2425 |
</chapter> |
2426 |
|
2427 |
<chapter> |
2428 |
<title>Finalizing your Gentoo Installation</title> |
2429 |
<abstract> |
2430 |
You're almost done. We'll just create one (or more) users for your |
2431 |
system and (optionally) install prebuilt packages. |
2432 |
</abstract> |
2433 |
<include href="hb-install-finalise.xml"/> |
2434 |
</chapter> |
2435 |
|
2436 |
<chapter> |
2437 |
<title>Where to go from here?</title> |
2438 |
<abstract> |
2439 |
Now you have your Gentoo system, but what's next? |
2440 |
</abstract> |
2441 |
<include href="hb-install-next.xml"/> |
2442 |
</chapter> |
2443 |
</part> |
2444 |
|
2445 |
<part> |
2446 |
<title>Working with Gentoo</title> |
2447 |
<abstract> |
2448 |
Learn how to work with Gentoo: installing software, altering variables, changing |
2449 |
Portage behaviour etc. |
2450 |
</abstract> |
2451 |
|
2452 |
<chapter> |
2453 |
<title>A Portage Introduction</title> |
2454 |
<abstract> |
2455 |
This chapter explains the "simple" steps a user definitely needs to know to |
2456 |
maintain the software on his system. |
2457 |
</abstract> |
2458 |
<include href="../hb-working-portage.xml"/> |
2459 |
</chapter> |
2460 |
|
2461 |
<chapter> |
2462 |
<title>USE flags</title> |
2463 |
<abstract> |
2464 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
2465 |
work with USE-flags and understand how USE-flags interact with your system. |
2466 |
</abstract> |
2467 |
<include href="../hb-working-use.xml"/> |
2468 |
</chapter> |
2469 |
|
2470 |
<chapter> |
2471 |
<title>Portage Features</title> |
2472 |
<abstract> |
2473 |
Discover the features Portage has, such as support for distributed compiling, |
2474 |
ccache and more. |
2475 |
</abstract> |
2476 |
<include href="../hb-working-features.xml"/> |
2477 |
</chapter> |
2478 |
|
2479 |
<chapter> |
2480 |
<title>Initscripts</title> |
2481 |
<abstract> |
2482 |
Gentoo uses a special initscript format which, amongst other features, allows |
2483 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
2484 |
these aspects and explains how to deal with these scripts. |
2485 |
</abstract> |
2486 |
<include href="../hb-working-rcscripts.xml"/> |
2487 |
</chapter> |
2488 |
|
2489 |
<chapter> |
2490 |
<title>Environment Variables</title> |
2491 |
<abstract> |
2492 |
With Gentoo you can easily manage the environment variables for your system. |
2493 |
This chapter explains how you do that, and also describes frequently used |
2494 |
variables. |
2495 |
</abstract> |
2496 |
<include href="../hb-working-variables.xml"/> |
2497 |
</chapter> |
2498 |
</part> |
2499 |
|
2500 |
<part> |
2501 |
<title>Working with Portage</title> |
2502 |
<abstract> |
2503 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
2504 |
Software Management Tool. |
2505 |
</abstract> |
2506 |
|
2507 |
<chapter> |
2508 |
<title>Files and Directories</title> |
2509 |
<abstract> |
2510 |
Once you want to know Portage in-depth you need to know where it stores its |
2511 |
files and data. |
2512 |
</abstract> |
2513 |
<include href="../hb-portage-files.xml"/> |
2514 |
</chapter> |
2515 |
|
2516 |
<chapter> |
2517 |
<title>Configuring through Variables</title> |
2518 |
<abstract> |
2519 |
Portage is completely configurable through various variables you can set in the |
2520 |
configuration file or as environment variable. |
2521 |
</abstract> |
2522 |
<include href="../hb-portage-configuration.xml"/> |
2523 |
</chapter> |
2524 |
|
2525 |
<chapter> |
2526 |
<title>Mixing Software Branches</title> |
2527 |
<abstract> |
2528 |
Gentoo provides software separated in several branches, depending on stability |
2529 |
and architectural support. "Mixing Software Branches" inform you how these |
2530 |
branches can be configured and how you can override this separation |
2531 |
individually. |
2532 |
</abstract> |
2533 |
<include href="../hb-portage-branches.xml"/> |
2534 |
</chapter> |
2535 |
|
2536 |
<chapter> |
2537 |
<title>Additional Portage Tools</title> |
2538 |
<abstract> |
2539 |
Portage comes with a few extra tools that might make your Gentoo experience even |
2540 |
better. Read on to discover how to use dispatch-conf and other tools. |
2541 |
</abstract> |
2542 |
<include href="../hb-portage-tools.xml"/> |
2543 |
</chapter> |
2544 |
|
2545 |
<chapter> |
2546 |
<title>Diverting from the Official Tree</title> |
2547 |
<abstract> |
2548 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
2549 |
your own Portage tree, how to synchronise only the categories you want, inject |
2550 |
packages and more. |
2551 |
</abstract> |
2552 |
<include href="../hb-portage-diverttree.xml"/> |
2553 |
</chapter> |
2554 |
|
2555 |
<chapter> |
2556 |
<title>The Ebuild Application</title> |
2557 |
<abstract> |
2558 |
In "The Ebuild Application" you are informed about the steps Portage takes while |
2559 |
installing software and how you can do this yourself using the ebuild |
2560 |
application. |
2561 |
</abstract> |
2562 |
<include href="../hb-portage-ebuild.xml"/> |
2563 |
</chapter> |
2564 |
</part> |
2565 |
|
2566 |
<part> |
2567 |
<title>Gentoo Network Configuration</title> |
2568 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
2569 |
|
2570 |
<chapter> |
2571 |
<title>Getting Started</title> |
2572 |
<abstract> |
2573 |
A guide to quickly get your network interface up and running in most common |
2574 |
environments. |
2575 |
</abstract> |
2576 |
<include href="../hb-net-start.xml"/> |
2577 |
</chapter> |
2578 |
|
2579 |
<chapter> |
2580 |
<title>Advanced Configuration</title> |
2581 |
<abstract> |
2582 |
Here we learn about how the configuration works - you need to know this |
2583 |
before we learn about modular networking. |
2584 |
</abstract> |
2585 |
<include href="../hb-net-advanced.xml"/> |
2586 |
</chapter> |
2587 |
|
2588 |
<chapter> |
2589 |
<title>Modular Networking</title> |
2590 |
<abstract> |
2591 |
Gentoo provides you flexible networking - here you are told about choosing |
2592 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
2593 |
</abstract> |
2594 |
<include href="../hb-net-modules.xml"/> |
2595 |
</chapter> |
2596 |
|
2597 |
<chapter> |
2598 |
<title>Wireless Networking</title> |
2599 |
<abstract> |
2600 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
2601 |
</abstract> |
2602 |
<include href="../hb-net-wireless.xml"/> |
2603 |
</chapter> |
2604 |
|
2605 |
<chapter> |
2606 |
<title>Adding Functionality</title> |
2607 |
<abstract> |
2608 |
If you're feeling adventurous, you can add your own functions to networking. |
2609 |
</abstract> |
2610 |
<include href="../hb-net-functions.xml"/> |
2611 |
</chapter> |
2612 |
|
2613 |
<chapter> |
2614 |
<title>Network Management</title> |
2615 |
<abstract> |
2616 |
For laptop users or people who move their computer around different networks. |
2617 |
</abstract> |
2618 |
<include href="../hb-net-management.xml"/> |
2619 |
</chapter> |
2620 |
</part> |
2621 |
|
2622 |
</book> |
2623 |
|
2624 |
|
2625 |
|
2626 |
1.1 xml/htdocs/doc/en/handbook/2006.0/handbook-x86.xml |
2627 |
|
2628 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/handbook-x86.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
2629 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/handbook-x86.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
2630 |
|
2631 |
Index: handbook-x86.xml |
2632 |
=================================================================== |
2633 |
<?xml version='1.0' encoding='UTF-8'?> |
2634 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
2635 |
|
2636 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/handbook-x86.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
2637 |
|
2638 |
<book link="handbook-x86.xml"> |
2639 |
<title>Gentoo Linux 2005.1 x86 Handbook</title> |
2640 |
|
2641 |
<author title="Author"> |
2642 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
2643 |
</author> |
2644 |
<author title="Author"> |
2645 |
<mail link="uberlord@g.o">Roy Marples</mail> |
2646 |
</author> |
2647 |
<author title="Author"> |
2648 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
2649 |
</author> |
2650 |
<author title="Author"> |
2651 |
<mail link="chouser@g.o">Chris Houser</mail> |
2652 |
</author> |
2653 |
<author title="Author"> |
2654 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
2655 |
</author> |
2656 |
<author title="Gentoo x86 Developer"> |
2657 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
2658 |
</author> |
2659 |
<author title="Gentoo Alpha Developer"> |
2660 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
2661 |
</author><!-- Does not want to be listed on the rendered page |
2662 |
<author title="Gentoo Developer"> |
2663 |
Aron Griffis |
2664 |
</author> |
2665 |
--> |
2666 |
<author title="Gentoo AMD64 Developer"> |
2667 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
2668 |
</author> |
2669 |
<author title="Gentoo HPPA developer"> |
2670 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
2671 |
</author> |
2672 |
<author title="Gentoo PPC developer"> |
2673 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
2674 |
</author> |
2675 |
<author title="Gentoo SPARC developer"> |
2676 |
<mail link="blademan@g.o">Joe Kallar</mail> |
2677 |
</author> |
2678 |
<author title="Editor"> |
2679 |
<mail link="zhen@g.o">John P. Davis</mail> |
2680 |
</author> |
2681 |
<author title="Editor">Pierre-Henri Jondot</author> |
2682 |
<author title="Editor"> |
2683 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
2684 |
</author> |
2685 |
<author title="Editor"> |
2686 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
2687 |
</author> |
2688 |
<author title="Editor"> |
2689 |
<mail link="seo@g.o">Jungmin Seo</mail> |
2690 |
</author> |
2691 |
<author title="Editor"> |
2692 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
2693 |
</author> |
2694 |
<author title="Editor"> |
2695 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
2696 |
</author> |
2697 |
<author title="Editor"> |
2698 |
<mail link="peitolm@g.o">Colin Morey</mail> |
2699 |
</author> |
2700 |
<author title="Editor"> |
2701 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
2702 |
</author> |
2703 |
<author title="Editor"> |
2704 |
<mail link="carl@g.o">Carl Anderson</mail> |
2705 |
</author> |
2706 |
<author title="Editor"> |
2707 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
2708 |
</author> |
2709 |
<author title="Editor"> |
2710 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
2711 |
</author> |
2712 |
<author title="Editor"> |
2713 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
2714 |
</author> |
2715 |
<author title="Editor"> |
2716 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
2717 |
</author> |
2718 |
<author title="Editor"> |
2719 |
<mail link="erwin@g.o">Erwin</mail> |
2720 |
</author> |
2721 |
<author title="Editor"> |
2722 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
2723 |
</author> |
2724 |
<author title="Editor"> |
2725 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
2726 |
</author> |
2727 |
<author title="Editor"> |
2728 |
<mail link="neysx@g.o">Xavier Neys</mail> |
2729 |
</author> |
2730 |
<author title="Reviewer"> |
2731 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
2732 |
</author> |
2733 |
<author title="Reviewer"> |
2734 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
2735 |
</author> |
2736 |
<author title="Reviewer"> |
2737 |
<mail link="spyderous@g.o">Donnie Berkholz</mail> |
2738 |
</author> |
2739 |
<author title="Reviewer"> |
2740 |
<mail link="antifa@g.o">Ken Nowack</mail> |
2741 |
</author> |
2742 |
<author title="Contributor"> |
2743 |
<mail link="pylon@g.o">Lars Weiler</mail> |
2744 |
</author> |
2745 |
|
2746 |
<abstract> |
2747 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
2748 |
This handbook contains the installation instructions for a networkless |
2749 |
installation on x86 systems and parts about working with Gentoo and Portage. |
2750 |
</abstract> |
2751 |
|
2752 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
2753 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
2754 |
<license/> |
2755 |
|
2756 |
<version>5.2</version> |
2757 |
<date>2005-10-13</date> |
2758 |
|
2759 |
<part> |
2760 |
<title>Installing Gentoo</title> |
2761 |
<abstract> |
2762 |
In this part you learn how to install Gentoo on your system. |
2763 |
</abstract> |
2764 |
|
2765 |
<chapter> |
2766 |
<title>About the Gentoo Linux Installation</title> |
2767 |
<abstract> |
2768 |
Users not familiar with Gentoo do not always know that choice is what |
2769 |
Gentoo is all about. |
2770 |
</abstract> |
2771 |
<include href="hb-install-about.xml"/> |
2772 |
</chapter> |
2773 |
|
2774 |
<chapter> |
2775 |
<title>Booting the Universal Installation CD</title> |
2776 |
<abstract> |
2777 |
Using our Universal Installation CD you can boot up your system into a running |
2778 |
environment that allows you to install Gentoo. |
2779 |
</abstract> |
2780 |
<include href="hb-install-x86-medium.xml"/> |
2781 |
</chapter> |
2782 |
|
2783 |
<chapter> |
2784 |
<title>Configuring your Network</title> |
2785 |
<abstract> |
2786 |
If you need networking, this is the place where the network (and Internet |
2787 |
connection) is configured. |
2788 |
</abstract> |
2789 |
<include href="hb-install-network.xml"/> |
2790 |
</chapter> |
2791 |
|
2792 |
<chapter> |
2793 |
<title>Preparing the Disks</title> |
2794 |
<abstract> |
2795 |
To be able to install Gentoo, you must create the necessary partitions. |
2796 |
This chapter describes how to partition a disk for future usage. |
2797 |
</abstract> |
2798 |
<include href="hb-install-x86-disk.xml"/> |
2799 |
</chapter> |
2800 |
|
2801 |
<chapter> |
2802 |
<title>Installing the Gentoo Installation Files</title> |
2803 |
<abstract> |
2804 |
In this chapter we describe how you extract a stage3 file and |
2805 |
how to configure Portage. |
2806 |
</abstract> |
2807 |
<include href="hb-install-stage.xml"/> |
2808 |
</chapter> |
2809 |
|
2810 |
<chapter> |
2811 |
<title>Chrooting into the Gentoo Base System</title> |
2812 |
<abstract> |
2813 |
Now that the stage3 file is extracted, we chroot into the new system and |
2814 |
modify the USE variable. |
2815 |
</abstract> |
2816 |
<include href="hb-install-system.xml"/> |
2817 |
</chapter> |
2818 |
|
2819 |
<chapter> |
2820 |
<title>Configuring the Kernel</title> |
2821 |
<abstract> |
2822 |
The Linux kernel is the core of every distribution. This chapter |
2823 |
explains how to configure your kernel. |
2824 |
</abstract> |
2825 |
<include href="hb-install-x86-kernel.xml"/> |
2826 |
</chapter> |
2827 |
|
2828 |
<chapter> |
2829 |
<title>Configuring your System</title> |
2830 |
<abstract> |
2831 |
You need to edit some important configuration files. In this chapter |
2832 |
you receive an overview of these files and an explanation on how to |
2833 |
proceed. |
2834 |
</abstract> |
2835 |
<include href="hb-install-config.xml"/> |
2836 |
</chapter> |
2837 |
|
2838 |
<chapter> |
2839 |
<title>Installing Necessary System Tools</title> |
2840 |
<abstract> |
2841 |
As mentioned before, Gentoo is about choices. In this chapter we help you |
2842 |
choose and install some important tools. |
2843 |
</abstract> |
2844 |
<include href="hb-install-tools.xml"/> |
2845 |
</chapter> |
2846 |
|
2847 |
<chapter> |
2848 |
<title>Configuring the Bootloader</title> |
2849 |
<abstract> |
2850 |
Several bootloaders exist for the x86 architecture. Each one of them has its |
2851 |
own way of configuration. We step you through the process of configuring a |
2852 |
bootloader to your needs. |
2853 |
</abstract> |
2854 |
<include href="hb-install-x86-bootloader.xml"/> |
2855 |
</chapter> |
2856 |
|
2857 |
<chapter> |
2858 |
<title>Finalizing your Gentoo Installation</title> |
2859 |
<abstract> |
2860 |
You're almost done. We'll just create one (or more) users for your |
2861 |
system and (optionally) install prebuilt packages. |
2862 |
</abstract> |
2863 |
<include href="hb-install-finalise.xml"/> |
2864 |
</chapter> |
2865 |
|
2866 |
<chapter> |
2867 |
<title>Where to go from here?</title> |
2868 |
<abstract> |
2869 |
Now you have your Gentoo system, but what's next? |
2870 |
</abstract> |
2871 |
<include href="hb-install-next.xml"/> |
2872 |
</chapter> |
2873 |
</part> |
2874 |
|
2875 |
<part> |
2876 |
<title>Working with Gentoo</title> |
2877 |
<abstract> |
2878 |
Learn how to work with Gentoo: installing software, altering variables, changing |
2879 |
Portage behaviour etc. |
2880 |
</abstract> |
2881 |
|
2882 |
<chapter> |
2883 |
<title>A Portage Introduction</title> |
2884 |
<abstract> |
2885 |
This chapter explains the "simple" steps a user definitely needs to know to |
2886 |
maintain the software on his system. |
2887 |
</abstract> |
2888 |
<include href="../hb-working-portage.xml"/> |
2889 |
</chapter> |
2890 |
|
2891 |
<chapter> |
2892 |
<title>USE flags</title> |
2893 |
<abstract> |
2894 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
2895 |
work with USE-flags and understand how USE-flags interact with your system. |
2896 |
</abstract> |
2897 |
<include href="../hb-working-use.xml"/> |
2898 |
</chapter> |
2899 |
|
2900 |
<chapter> |
2901 |
<title>Portage Features</title> |
2902 |
<abstract> |
2903 |
Discover the features Portage has, such as support for distributed compiling, |
2904 |
ccache and more. |
2905 |
</abstract> |
2906 |
<include href="../hb-working-features.xml"/> |
2907 |
</chapter> |
2908 |
|
2909 |
<chapter> |
2910 |
<title>Initscripts</title> |
2911 |
<abstract> |
2912 |
Gentoo uses a special initscript format which, amongst other features, allows |
2913 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
2914 |
these aspects and explains how to deal with these scripts. |
2915 |
</abstract> |
2916 |
<include href="../hb-working-rcscripts.xml"/> |
2917 |
</chapter> |
2918 |
|
2919 |
<chapter> |
2920 |
<title>Environment Variables</title> |
2921 |
<abstract> |
2922 |
With Gentoo you can easily manage the environment variables for your system. |
2923 |
This chapter explains how you do that, and also describes frequently used |
2924 |
variables. |
2925 |
</abstract> |
2926 |
<include href="../hb-working-variables.xml"/> |
2927 |
</chapter> |
2928 |
</part> |
2929 |
|
2930 |
<part> |
2931 |
<title>Working with Portage</title> |
2932 |
<abstract> |
2933 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
2934 |
Software Management Tool. |
2935 |
</abstract> |
2936 |
|
2937 |
<chapter> |
2938 |
<title>Files and Directories</title> |
2939 |
<abstract> |
2940 |
Once you want to know Portage in-depth you need to know where it stores its |
2941 |
files and data. |
2942 |
</abstract> |
2943 |
<include href="../hb-portage-files.xml"/> |
2944 |
</chapter> |
2945 |
|
2946 |
<chapter> |
2947 |
<title>Configuring through Variables</title> |
2948 |
<abstract> |
2949 |
Portage is completely configurable through various variables you can set in the |
2950 |
configuration file or as environment variable. |
2951 |
</abstract> |
2952 |
<include href="../hb-portage-configuration.xml"/> |
2953 |
</chapter> |
2954 |
|
2955 |
<chapter> |
2956 |
<title>Mixing Software Branches</title> |
2957 |
<abstract> |
2958 |
Gentoo provides software separated in several branches, depending on stability |
2959 |
and architectural support. "Mixing Software Branches" inform you how these |
2960 |
branches can be configured and how you can override this separation |
2961 |
individually. |
2962 |
</abstract> |
2963 |
<include href="../hb-portage-branches.xml"/> |
2964 |
</chapter> |
2965 |
|
2966 |
<chapter> |
2967 |
<title>Additional Portage Tools</title> |
2968 |
<abstract> |
2969 |
Portage comes with a few extra tools that might make your Gentoo experience even |
2970 |
better. Read on to discover how to use dispatch-conf and other tools. |
2971 |
</abstract> |
2972 |
<include href="../hb-portage-tools.xml"/> |
2973 |
</chapter> |
2974 |
|
2975 |
<chapter> |
2976 |
<title>Diverting from the Official Tree</title> |
2977 |
<abstract> |
2978 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
2979 |
your own Portage tree, how to synchronise only the categories you want, inject |
2980 |
packages and more. |
2981 |
</abstract> |
2982 |
<include href="../hb-portage-diverttree.xml"/> |
2983 |
</chapter> |
2984 |
|
2985 |
<chapter> |
2986 |
<title>The Ebuild Application</title> |
2987 |
<abstract> |
2988 |
In "The Ebuild Application" you are informed about the steps Portage takes while |
2989 |
installing software and how you can do this yourself using the ebuild |
2990 |
application. |
2991 |
</abstract> |
2992 |
<include href="../hb-portage-ebuild.xml"/> |
2993 |
</chapter> |
2994 |
</part> |
2995 |
|
2996 |
<part> |
2997 |
<title>Gentoo Network Configuration</title> |
2998 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
2999 |
|
3000 |
<chapter> |
3001 |
<title>Getting Started</title> |
3002 |
<abstract> |
3003 |
A guide to quickly get your network interface up and running in most common |
3004 |
environments. |
3005 |
</abstract> |
3006 |
<include href="../hb-net-start.xml"/> |
3007 |
</chapter> |
3008 |
|
3009 |
<chapter> |
3010 |
<title>Advanced Configuration</title> |
3011 |
<abstract> |
3012 |
Here we learn about how the configuration works - you need to know this |
3013 |
before we learn about modular networking. |
3014 |
</abstract> |
3015 |
<include href="../hb-net-advanced.xml"/> |
3016 |
</chapter> |
3017 |
|
3018 |
<chapter> |
3019 |
<title>Modular Networking</title> |
3020 |
<abstract> |
3021 |
Gentoo provides you flexible networking - here you are told about choosing |
3022 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
3023 |
</abstract> |
3024 |
<include href="../hb-net-modules.xml"/> |
3025 |
</chapter> |
3026 |
|
3027 |
<chapter> |
3028 |
<title>Wireless Networking</title> |
3029 |
<abstract> |
3030 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
3031 |
</abstract> |
3032 |
<include href="../hb-net-wireless.xml"/> |
3033 |
</chapter> |
3034 |
|
3035 |
<chapter> |
3036 |
<title>Adding Functionality</title> |
3037 |
<abstract> |
3038 |
If you're feeling adventurous, you can add your own functions to networking. |
3039 |
</abstract> |
3040 |
<include href="../hb-net-functions.xml"/> |
3041 |
</chapter> |
3042 |
|
3043 |
<chapter> |
3044 |
<title>Network Management</title> |
3045 |
<abstract> |
3046 |
For laptop users or people who move their computer around different networks. |
3047 |
</abstract> |
3048 |
<include href="../hb-net-management.xml"/> |
3049 |
</chapter> |
3050 |
</part> |
3051 |
|
3052 |
</book> |
3053 |
|
3054 |
|
3055 |
|
3056 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-about.xml |
3057 |
|
3058 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-about.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
3059 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-about.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
3060 |
|
3061 |
Index: hb-install-about.xml |
3062 |
=================================================================== |
3063 |
<?xml version='1.0' encoding='UTF-8'?> |
3064 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
3065 |
|
3066 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
3067 |
<!-- See http://creativecommons.org/licenses/by-sa/2.0 --> |
3068 |
|
3069 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-about.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
3070 |
|
3071 |
<sections> |
3072 |
|
3073 |
<version>5.0</version> |
3074 |
<date>2005-08-08</date> |
3075 |
|
3076 |
<section> |
3077 |
<title>Introduction</title> |
3078 |
<subsection> |
3079 |
<title>Welcome!</title> |
3080 |
<body> |
3081 |
|
3082 |
<p> |
3083 |
First of all, <e>welcome</e> to Gentoo. You are about to enter the world |
3084 |
of choices and performance. Gentoo is all about choices. When |
3085 |
installing Gentoo, this is made clear to you several times -- you can |
3086 |
choose how much you want to compile yourself, how to install Gentoo, |
3087 |
what system logger you want, etc. |
3088 |
</p> |
3089 |
|
3090 |
<p> |
3091 |
Gentoo is a fast, modern metadistribution with a clean and flexible |
3092 |
design. Gentoo is built around free software and doesn't hide from its |
3093 |
users what is beneath the hood. Portage, the package maintenance system |
3094 |
which Gentoo uses, is written in Python, meaning you can easily view and |
3095 |
modify the source code. Gentoo's packaging system uses source code |
3096 |
(although support for precompiled packages is included too) and |
3097 |
configuring Gentoo happens through regular textfiles. In other words, |
3098 |
openness everywhere. |
3099 |
</p> |
3100 |
|
3101 |
<p> |
3102 |
It is very important that you understand that <e>choices</e> are what |
3103 |
makes Gentoo run. We try not to force you onto anything you don't like. |
3104 |
If you feel like we do, please <uri |
3105 |
link="http://bugs.gentoo.org">bugreport</uri> it. |
3106 |
</p> |
3107 |
|
3108 |
</body> |
3109 |
</subsection> |
3110 |
<subsection> |
3111 |
<title>How is the Installation Structured?</title> |
3112 |
<body> |
3113 |
|
3114 |
<p> |
3115 |
The Gentoo Installation can be seen as a 10-step procedure, |
3116 |
corresponding to chapters 2 - 11. Every step results in |
3117 |
a certain state: |
3118 |
</p> |
3119 |
|
3120 |
<ul> |
3121 |
<li> |
3122 |
After step 1, you are in a working environment ready to install Gentoo |
3123 |
</li> |
3124 |
<li> |
3125 |
After step 2, your internet connection is prepared in case you need it (this |
3126 |
is however optional) |
3127 |
</li> |
3128 |
<li> |
3129 |
After step 3, your hard disks are initialized to house your Gentoo |
3130 |
installation |
3131 |
</li> |
3132 |
<li> |
3133 |
After step 4, your installation environment is prepared and you are |
3134 |
ready to chroot into the new environment |
3135 |
</li> |
3136 |
<li> |
3137 |
After step 5, core packages, which are the same on all Gentoo |
3138 |
installations, are installed |
3139 |
</li> |
3140 |
<li> |
3141 |
After step 6, you have compiled your Linux kernel |
3142 |
</li> |
3143 |
<li> |
3144 |
After step 7, you have written most of your Gentoo system |
3145 |
configuration files |
3146 |
</li> |
3147 |
<li> |
3148 |
After step 8, necessary system tools (which you can choose from a nice |
3149 |
list) are installed |
3150 |
</li> |
3151 |
<li> |
3152 |
After step 9, your choice of bootloader has been installed and |
3153 |
configured and you are logged in into your new Gentoo installation |
3154 |
</li> |
3155 |
<li> |
3156 |
After step 10, your Gentoo Linux environment is ready to be explored |
3157 |
</li> |
3158 |
</ul> |
3159 |
|
3160 |
<p> |
3161 |
When you are given a certain choice, we try our best to explain what the pros |
3162 |
and cons are. We will continue then with a default |
3163 |
choice, identified by "Default: " in the title. The other |
3164 |
possibilities are marked by "Alternative: ". Do <e>not</e> |
3165 |
think that the default is what we recommend. It is however what we |
3166 |
believe most users will use. |
3167 |
</p> |
3168 |
|
3169 |
<p> |
3170 |
Sometimes you can pursue an optional step. Such steps are marked as |
3171 |
"Optional: " and are therefore not needed to install Gentoo. |
3172 |
However, some optional steps are dependant on a previous decision you |
3173 |
made. We will inform you when this happens, both when you make the |
3174 |
decision, and right before the optional step is described. |
3175 |
</p> |
3176 |
|
3177 |
</body> |
3178 |
</subsection> |
3179 |
<subsection> |
3180 |
<title>What are my Options?</title> |
3181 |
<body> |
3182 |
|
3183 |
<p> |
3184 |
You can install Gentoo in many different ways. You can download and install from |
3185 |
one of our Installation CDs, from an existing distribution, |
3186 |
from a bootable CD (such as Knoppix), from a netbooted environment, from a |
3187 |
rescue floppy, etc. |
3188 |
</p> |
3189 |
|
3190 |
<p> |
3191 |
This document covers the installation using the Universal Installation CD, a |
3192 |
bootable CD that contains everything you need to get Gentoo Linux up and |
3193 |
running. You can optionally use one of our Package CDs as well to install a |
3194 |
complete system in a matter of minutes after having installed the Gentoo base |
3195 |
system. |
3196 |
</p> |
3197 |
|
3198 |
<p> |
3199 |
This installation approach however does not immediately use the latest version |
3200 |
of the available packages; if you want this you should check out the |
3201 |
Installation Instructions inside our <uri |
3202 |
link="/doc/en/handbook/index.xml">Gentoo Linux Handbooks</uri>. |
3203 |
</p> |
3204 |
|
3205 |
<p> |
3206 |
For help on the other installation approaches, |
3207 |
please read our <uri link="/doc/en/altinstall.xml">Alternative Installation |
3208 |
Guide</uri>. We also provide a <uri |
3209 |
link="/doc/en/gentoo-x86-tipsntricks.xml">Gentoo Installation Tips & |
3210 |
Tricks</uri> document that might be useful to read as well. If you feel that |
3211 |
the current installation instructions are too elaborate, feel free to use our |
3212 |
Quick Installation Guide available from our <uri |
3213 |
link="/doc/en/index.xml">Documentation Resources</uri> if your architecture |
3214 |
has such a document available. |
3215 |
</p> |
3216 |
|
3217 |
</body> |
3218 |
</subsection> |
3219 |
<subsection> |
3220 |
<title>Troubles?</title> |
3221 |
<body> |
3222 |
|
3223 |
<p> |
3224 |
If you find a problem in the installation (or in the installation |
3225 |
documentation), please check the errata from our <uri |
3226 |
link="/proj/en/releng/">Gentoo Release Engineering Project</uri>, |
3227 |
visit our <uri link="http://bugs.gentoo.org">bugtracking |
3228 |
system</uri> and check if the bug is known. If not, please create a bugreport |
3229 |
for it so we can take care of it. Do not be afraid of the developers who are |
3230 |
assigned to (your) bugs -- they generally don't eat people. |
3231 |
</p> |
3232 |
|
3233 |
<p> |
3234 |
Note though that, although the document you are now reading is |
3235 |
architecture-specific, it will contain references to other architectures as |
3236 |
well. This is due to the fact that large parts of the Gentoo Handbook use source |
3237 |
code that is common for all architectures (to avoid duplication of efforts and |
3238 |
starvation of development resources). We will try to keep this to a minimum |
3239 |
to avoid confusion. |
3240 |
</p> |
3241 |
|
3242 |
<p> |
3243 |
If you are uncertain if the problem is a user-problem (some error you |
3244 |
made despite having read the documentation carefully) or a |
3245 |
software-problem (some error we made despite having tested the |
3246 |
installation/documentation carefully) you are free to join #gentoo on |
3247 |
irc.freenode.net. Of course, you are welcome otherwise too :) |
3248 |
</p> |
3249 |
|
3250 |
<p> |
3251 |
If you have a question regarding Gentoo, check out our <uri |
3252 |
link="/doc/en/faq.xml">Frequently Asked |
3253 |
Questions</uri>, available from the <uri |
3254 |
link="/doc/en/">Gentoo Documentation</uri>. You can |
3255 |
also view the <uri |
3256 |
link="http://forums.gentoo.org/viewforum.php?f=40">FAQs</uri> on our |
3257 |
<uri link="http://forums.gentoo.org">forums</uri>. If you can't find the answer |
3258 |
there ask on #gentoo, our IRC-channel on irc.freenode.net. Yes, several of |
3259 |
us are freaks who sit on IRC :-) |
3260 |
</p> |
3261 |
|
3262 |
</body> |
3263 |
</subsection> |
3264 |
</section> |
3265 |
<section> |
3266 |
<title>Fast Installation using the Gentoo Reference Platform</title> |
3267 |
<subsection> |
3268 |
<title>What is the Gentoo Reference Platform?</title> |
3269 |
<body> |
3270 |
|
3271 |
<p> |
3272 |
The Gentoo Reference Platform, from now on abbreviated to GRP, is a snapshot of |
3273 |
prebuilt packages users (that means you!) can install during the installation |
3274 |
of Gentoo to speed up the installation process. The GRP consists of all |
3275 |
packages required to have a fully functional Gentoo installation. They are not |
3276 |
just the ones you need to have a base installation up to speed in no time, but |
3277 |
all lengthier builds (such as KDE, xorg-x11, GNOME, OpenOffice, Mozilla, ...) |
3278 |
are available as GRP packages too. |
3279 |
</p> |
3280 |
|
3281 |
<p> |
3282 |
However, these prebuilt packages aren't maintained during the lifetime of the |
3283 |
Gentoo distribution. They are snapshots released at every Gentoo release and |
3284 |
make it possible to have a functional environment in a short amount of time. You |
3285 |
can then upgrade your system in the background while working in your Gentoo |
3286 |
environment. |
3287 |
</p> |
3288 |
|
3289 |
</body> |
3290 |
</subsection> |
3291 |
<subsection> |
3292 |
<title>How Portage Handles GRP Packages</title> |
3293 |
<body> |
3294 |
|
3295 |
<p> |
3296 |
Your Portage tree - the collection of <e>ebuilds</e> (files that contain all |
3297 |
information about a package, such as its description, homepage, sourcecode URLs, |
3298 |
compilation instructions, dependencies, etc.) - must be synchronised with the |
3299 |
GRP set: the versions of the available ebuilds and their accompanying GRP |
3300 |
packages must match. |
3301 |
</p> |
3302 |
|
3303 |
<p> |
3304 |
For this reason you can only benefit from the GRP packages Gentoo provides while |
3305 |
performing the current installation approach. GRP is not available for those |
3306 |
interested in performing an installation using the latest versions of all |
3307 |
available packages. |
3308 |
</p> |
3309 |
|
3310 |
</body> |
3311 |
</subsection> |
3312 |
<subsection> |
3313 |
<title>Is GRP Available?</title> |
3314 |
<body> |
3315 |
|
3316 |
<p> |
3317 |
Not all architectures provide GRP packages. That doesn't mean GRP isn't |
3318 |
supported on the other architectures, but it means that we don't have the |
3319 |
resources to build and test the GRP packages. |
3320 |
</p> |
3321 |
|
3322 |
<p> |
3323 |
At present we provide GRP packages for the following architectures: |
3324 |
</p> |
3325 |
|
3326 |
<ul> |
3327 |
<li> |
3328 |
The <b>x86</b> architecture (x86, athlon-xp, pentium3, pentium4) |
3329 |
Note: The x86 packages (packages-x86-2005.1.iso) are available on |
3330 |
our mirrors, while pentium3, pentium4 and athlon-xp are only available |
3331 |
via bittorrent. |
3332 |
</li> |
3333 |
<li> |
3334 |
The <b>amd64</b> architecture (amd64) |
3335 |
</li> |
3336 |
<li> |
3337 |
The <b>sparc</b> architecture (sparc64) |
3338 |
</li> |
3339 |
<li> |
3340 |
The <b>ppc</b> architecture (G3, G4, G5) |
3341 |
</li> |
3342 |
<li> |
3343 |
The <b>alpha</b> architecture |
3344 |
</li> |
3345 |
</ul> |
3346 |
|
3347 |
<p> |
3348 |
If your architecture (or subarchitecture) isn't on this list, you are not |
3349 |
able to opt for a GRP installation. |
3350 |
</p> |
3351 |
|
3352 |
<p> |
3353 |
Now that this introduction is over, let's continue with <uri |
3354 |
link="?part=1&chap=2">Booting the Universal Installation CD</uri>. |
3355 |
</p> |
3356 |
|
3357 |
</body> |
3358 |
</subsection> |
3359 |
</section> |
3360 |
</sections> |
3361 |
|
3362 |
|
3363 |
|
3364 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-alpha-bootloader.xml |
3365 |
|
3366 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-alpha-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
3367 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-alpha-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
3368 |
|
3369 |
Index: hb-install-alpha-bootloader.xml |
3370 |
=================================================================== |
3371 |
<?xml version='1.0' encoding='UTF-8'?> |
3372 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
3373 |
|
3374 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
3375 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
3376 |
|
3377 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-alpha-bootloader.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
3378 |
|
3379 |
<sections> |
3380 |
|
3381 |
<version>5.1</version> |
3382 |
<date>2006-01-19</date> |
3383 |
|
3384 |
<section> |
3385 |
<title>Making your Choice</title> |
3386 |
<subsection> |
3387 |
<title>Introduction</title> |
3388 |
<body> |
3389 |
|
3390 |
<p> |
3391 |
Now that your kernel is configured and compiled and the necessary system |
3392 |
configuration files are filled in correctly, it is time to install a |
3393 |
program that will fire up your kernel when you start the system. Such a |
3394 |
program is called a <e>bootloader</e>. |
3395 |
</p> |
3396 |
|
3397 |
<p> |
3398 |
Several bootloaders exist for Linux/Alpha. You must choose one of the supported |
3399 |
bootloaders, not all. You have the choice between <uri link="#aboot">aBoot</uri> |
3400 |
and <uri link="#milo">MILO</uri>. |
3401 |
</p> |
3402 |
|
3403 |
</body> |
3404 |
</subsection> |
3405 |
</section> |
3406 |
<section id="aboot"> |
3407 |
<title>Default: Using aboot</title> |
3408 |
<body> |
3409 |
|
3410 |
<p> |
3411 |
We first install aboot on our system. Of course we use <c>emerge</c> to |
3412 |
do so: |
3413 |
</p> |
3414 |
|
3415 |
<pre caption = "Installing aboot"> |
3416 |
# <i>emerge --usepkg aboot</i> |
3417 |
</pre> |
3418 |
|
3419 |
<p> |
3420 |
The next step is to make our bootdisk bootable. This will start |
3421 |
<c>aboot</c> when you boot your system. We make our bootdisk bootable by |
3422 |
writing the <c>aboot</c> bootloader to the start of the disk. |
3423 |
</p> |
3424 |
|
3425 |
<pre caption = "Making your bootdisk bootable"> |
3426 |
# <i>swriteboot -f3 /dev/sda /boot/bootlx</i> |
3427 |
# <i>abootconf /dev/sda 2</i> |
3428 |
</pre> |
3429 |
|
3430 |
<note> |
3431 |
If you use a different partitioning scheme than the one we use |
3432 |
throughout this chapter, you have to change the commands accordingly. |
3433 |
Please read the appropriate manual pages (<c>man 8 swriteboot</c> and |
3434 |
<c>man 8 abootconf</c>). Also, if your root filesystem uses the JFS filesystem, |
3435 |
make sure to pass the <c>ro</c> kernel option so that it can replay its log |
3436 |
before it gets mounted read-write. |
3437 |
</note> |
3438 |
|
3439 |
<p> |
3440 |
Additionally, you can make Gentoo boot automatically by setting up the |
3441 |
aboot configuration file and some SRM variables. You can try setting |
3442 |
these variables from Linux, but it may be easier to do so from the SRM |
3443 |
console itself. |
3444 |
</p> |
3445 |
|
3446 |
<pre caption = "Automatically booting Gentoo"> |
3447 |
# <i>echo '0:2/boot/vmlinux.gz root=/dev/sda2' > /etc/aboot.conf</i> |
3448 |
# <i>cd /proc/srm_environment/named_variables</i> |
3449 |
# <i>echo -n 0 > boot_osflags</i> |
3450 |
# <i>echo -n '' > boot_file</i> |
3451 |
# <i>echo -n 'BOOT' > auto_action</i> |
3452 |
# <i>echo -n 'dkc100' > bootdef_dev</i> |
3453 |
<comment>(Substitute dkc100 with whatever your boot device is)</comment> |
3454 |
</pre> |
3455 |
|
3456 |
<p> |
3457 |
If you need to get into the SRM console again in the future (to recover |
3458 |
your Gentoo install, play with some variables, or whatever), just hit |
3459 |
CTRL+C to abort the automatic loading process. |
3460 |
</p> |
3461 |
|
3462 |
<p> |
3463 |
If you're installing using a serial console, don't forget to include |
3464 |
the serial console boot flag in <path>aboot.conf</path>. See |
3465 |
<path>/etc/aboot.conf.example</path> for some further information. |
3466 |
</p> |
3467 |
|
3468 |
<p> |
3469 |
Aboot is now configured and ready to use. Continue with <uri |
3470 |
link="#reboot">Rebooting the System</uri>. |
3471 |
</p> |
3472 |
|
3473 |
</body> |
3474 |
</section> |
3475 |
<section id="milo"> |
3476 |
<title>Alternative: Using MILO</title> |
3477 |
<body> |
3478 |
|
3479 |
<p> |
3480 |
Before continuing, you should decide on how to use MILO. In this |
3481 |
section, we will assume that you want to make a MILO boot floppy. If you |
3482 |
are going to boot from an MS-DOS partition on your hard disk, you should |
3483 |
amend the commands appropriately. |
3484 |
</p> |
3485 |
|
3486 |
<p> |
3487 |
To install MILO, we use <c>emerge</c>. |
3488 |
</p> |
3489 |
|
3490 |
<pre caption = "Installing MILO"> |
3491 |
# <i>emerge --usepkg milo</i> |
3492 |
</pre> |
3493 |
|
3494 |
<p> |
3495 |
After MILO has been installed, the MILO images should be in |
3496 |
<path>/opt/milo</path>. The commands below make a bootfloppy for use |
3497 |
with MILO. Remember to use the correct image for your Alpha-system. |
3498 |
</p> |
3499 |
|
3500 |
<pre caption = "Installing MILO on a floppy"> |
3501 |
<comment>(First insert a blank floppy)</comment> |
3502 |
# <i>fdformat /dev/fd0</i> |
3503 |
# <i>mformat a:</i> |
3504 |
# <i>mcopy /opt/milo/milo-2.2-18-gentoo-ruffian a:\milo</i> |
3505 |
# <i>mcopy /opt/milo/linload.exe a:\lilnload.exe</i> |
3506 |
<comment>(Only if you have a Ruffian:</comment> |
3507 |
# <i>mcopy /opt/milo/ldmilo.exe a:\ldmilo.exe</i> |
3508 |
<comment>)</comment> |
3509 |
# <i>echo -ne '\125\252' | dd of=/dev/fd0 bs=1 seek=510 count=2</i> |
3510 |
</pre> |
3511 |
|
3512 |
<p> |
3513 |
Your MILO boot floppy is now ready to boot Gentoo Linux. You may need to |
3514 |
set environment variables in your ARCS Firmware to get MILO to start; |
3515 |
this is all explained in the <uri |
3516 |
link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri> with some examples |
3517 |
on common systems, and examples of the commands to use in interactive mode. |
3518 |
</p> |
3519 |
|
3520 |
<p> |
3521 |
Not reading the <uri link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri> |
3522 |
is a <e>bad</e> idea. |
3523 |
</p> |
3524 |
|
3525 |
<p> |
3526 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
3527 |
</p> |
3528 |
|
3529 |
</body> |
3530 |
</section> |
3531 |
<section id="reboot"> |
3532 |
<title>Rebooting the System</title> |
3533 |
<subsection> |
3534 |
<body> |
3535 |
|
3536 |
<p> |
3537 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
3538 |
that one magical command you have been waiting for: <c>reboot</c>. |
3539 |
</p> |
3540 |
|
3541 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
3542 |
# <i>exit</i> |
3543 |
cdimage ~# <i>cd</i> |
3544 |
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
3545 |
cdimage ~# <i>reboot</i> |
3546 |
</pre> |
3547 |
|
3548 |
<p> |
3549 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
3550 |
booted again instead of your new Gentoo system. |
3551 |
</p> |
3552 |
|
3553 |
<p> |
3554 |
Once rebooted in your Gentoo installation, finish up with <uri |
3555 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
3556 |
</p> |
3557 |
|
3558 |
</body> |
3559 |
</subsection> |
3560 |
</section> |
3561 |
|
3562 |
</sections> |
3563 |
|
3564 |
|
3565 |
|
3566 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-alpha-disk.xml |
3567 |
|
3568 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-alpha-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
3569 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-alpha-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
3570 |
|
3571 |
Index: hb-install-alpha-disk.xml |
3572 |
=================================================================== |
3573 |
<?xml version='1.0' encoding='UTF-8'?> |
3574 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
3575 |
|
3576 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
3577 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
3578 |
|
3579 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-alpha-disk.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
3580 |
|
3581 |
<sections> |
3582 |
|
3583 |
<version>5.1</version> |
3584 |
<date>2005-08-25</date> |
3585 |
|
3586 |
<section> |
3587 |
<title>Introduction to Block Devices</title> |
3588 |
<subsection> |
3589 |
<title>Block Devices</title> |
3590 |
<body> |
3591 |
|
3592 |
<p> |
3593 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
3594 |
and Linux in general, including Linux filesystems, partitions and block devices. |
3595 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
3596 |
you'll be guided through the process of setting up partitions and filesystems |
3597 |
for your Gentoo Linux installation. |
3598 |
</p> |
3599 |
|
3600 |
<p> |
3601 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
3602 |
probably the one that represents the first SCSI HD in a Linux system, namely |
3603 |
<path>/dev/sda</path>. |
3604 |
</p> |
3605 |
|
3606 |
<p> |
3607 |
The block devices above represent an abstract interface to the disk. User |
3608 |
programs can use these block devices to interact with your disk without worrying |
3609 |
about whether your drives are IDE, SCSI or something else. The program can |
3610 |
simply address the storage on the disk as a bunch of contiguous, |
3611 |
randomly-accessible 512-byte blocks. |
3612 |
</p> |
3613 |
|
3614 |
</body> |
3615 |
</subsection> |
3616 |
<subsection> |
3617 |
<title>Slices</title> |
3618 |
<body> |
3619 |
|
3620 |
<p> |
3621 |
Although it is theoretically possible to use a full disk to house your Linux |
3622 |
system, this is almost never done in practice. Instead, full disk block devices |
3623 |
are split up in smaller, more manageable block devices. On Alpha systems, |
3624 |
these are called <e>slices</e>. |
3625 |
</p> |
3626 |
|
3627 |
</body> |
3628 |
</subsection> |
3629 |
</section> |
3630 |
<section> |
3631 |
<title>Designing a Partitioning Scheme</title> |
3632 |
<subsection> |
3633 |
<title>Default Partitioning Scheme</title> |
3634 |
<body> |
3635 |
|
3636 |
<p> |
3637 |
As an example we use the following slice layout: |
3638 |
</p> |
3639 |
|
3640 |
<table> |
3641 |
<tr> |
3642 |
<th>Slice</th> |
3643 |
<th>Description</th> |
3644 |
</tr> |
3645 |
<tr> |
3646 |
<ti><path>/dev/sda1</path></ti> |
3647 |
<ti>Swap slice</ti> |
3648 |
</tr> |
3649 |
<tr> |
3650 |
<ti><path>/dev/sda2</path></ti> |
3651 |
<ti>Root slice</ti> |
3652 |
</tr> |
3653 |
<tr> |
3654 |
<ti><path>/dev/sda3</path></ti> |
3655 |
<ti>Full disk (required)</ti> |
3656 |
</tr> |
3657 |
</table> |
3658 |
|
3659 |
|
3660 |
<p> |
3661 |
If you are interested in knowing how big a partition should be, or even how |
3662 |
many partitions (or volumes) you need, read on. Otherwise continue now with |
3663 |
<uri link="#fdisk_SRM">Using fdisk to Partition your Disk (SRM only)</uri> |
3664 |
or <uri link="#fdisk_ARC">Using fdisk to Partition your Disk (ARC/AlphaBIOS |
3665 |
only)</uri>. |
3666 |
</p> |
3667 |
|
3668 |
</body> |
3669 |
</subsection> |
3670 |
<subsection> |
3671 |
<title>How Many and How Big?</title> |
3672 |
<body> |
3673 |
|
3674 |
<p> |
3675 |
The number of partitions is highly dependent on your environment. For instance, |
3676 |
if you have lots of users, you will most likely want to have your |
3677 |
<path>/home</path> separate as it increases security and makes backups easier. |
3678 |
If you are installing Gentoo to perform as a mailserver, your |
3679 |
<path>/var</path> should be separate as all mails are stored inside |
3680 |
<path>/var</path>. A good choice of filesystem will then maximise your |
3681 |
performance. Gameservers will have a separate <path>/opt</path> as most gaming |
3682 |
servers are installed there. The reason is similar for <path>/home</path>: |
3683 |
security and backups. You will definitely want to keep <path>/usr</path> big: |
3684 |
not only will it contain the majority of applications, the Portage tree alone |
3685 |
takes around 500 Mbyte excluding the various sources that are stored in it. |
3686 |
</p> |
3687 |
|
3688 |
<p> |
3689 |
As you can see, it very much depends on what you want to achieve. Separate |
3690 |
partitions or volumes have the following advantages: |
3691 |
</p> |
3692 |
|
3693 |
<ul> |
3694 |
<li> |
3695 |
You can choose the best performing filesystem for each partition or volume |
3696 |
</li> |
3697 |
<li> |
3698 |
Your entire system cannot run out of free space if one defunct tool is |
3699 |
continuously writing files to a partition or volume |
3700 |
</li> |
3701 |
<li> |
3702 |
If necessary, file system checks are reduced in time, as multiple checks can |
3703 |
be done in parallel (although this advantage is more with multiple disks than |
3704 |
it is with multiple partitions) |
3705 |
</li> |
3706 |
<li> |
3707 |
Security can be enhanced by mounting some partitions or volumes read-only, |
3708 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
3709 |
</li> |
3710 |
</ul> |
3711 |
|
3712 |
<p> |
3713 |
However, multiple partitions have one big disadvantage: if not configured |
3714 |
properly, you might result in having a system with lots |
3715 |
of free space on one partition and none on another. |
3716 |
</p> |
3717 |
|
3718 |
</body> |
3719 |
</subsection> |
3720 |
</section> |
3721 |
<section id="fdisk_SRM"> |
3722 |
<title>Using fdisk to Partition your Disk (SRM only)</title> |
3723 |
<subsection> |
3724 |
<body> |
3725 |
|
3726 |
<p> |
3727 |
The following parts explain how to create the example slice layout described |
3728 |
previously, namely: |
3729 |
</p> |
3730 |
|
3731 |
<table> |
3732 |
<tr> |
3733 |
<th>Slice</th> |
3734 |
<th>Description</th> |
3735 |
</tr> |
3736 |
<tr> |
3737 |
<ti><path>/dev/sda1</path></ti> |
3738 |
<ti>Swap slice</ti> |
3739 |
</tr> |
3740 |
<tr> |
3741 |
<ti><path>/dev/sda2</path></ti> |
3742 |
<ti>Root slice</ti> |
3743 |
</tr> |
3744 |
<tr> |
3745 |
<ti><path>/dev/sda3</path></ti> |
3746 |
<ti>Full disk (required)</ti> |
3747 |
</tr> |
3748 |
</table> |
3749 |
|
3750 |
<p> |
3751 |
Change your slice layout according to your own preference. |
3752 |
</p> |
3753 |
|
3754 |
|
3755 |
</body> |
3756 |
</subsection> |
3757 |
<subsection> |
3758 |
<title>Identifying Available Disks</title> |
3759 |
<body> |
3760 |
|
3761 |
<p> |
3762 |
To figure out what disks you have running, use the following commands: |
3763 |
</p> |
3764 |
|
3765 |
<pre caption="Identifying available disks"> |
3766 |
# <i>dmesg | grep 'drive$'</i> <comment>(For IDE disks)</comment> |
3767 |
# <i>dmesg | grep 'scsi'</i> <comment>(For SCSI disks)</comment> |
3768 |
</pre> |
3769 |
|
3770 |
<p> |
3771 |
>From this output you should be able to see what disks were detected and their |
3772 |
respective <path>/dev</path> entry. In the following parts we assume that the |
3773 |
disk is a SCSI disk on <path>/dev/sda</path>. |
3774 |
</p> |
3775 |
|
3776 |
<p> |
3777 |
Now fire up <c>fdisk</c>: |
3778 |
</p> |
3779 |
|
3780 |
<pre caption="Starting fdisk"> |
3781 |
# <i>fdisk /dev/sda</i> |
3782 |
</pre> |
3783 |
|
3784 |
</body> |
3785 |
</subsection> |
3786 |
<subsection> |
3787 |
<title>Deleting All Slices</title> |
3788 |
<body> |
3789 |
|
3790 |
<p> |
3791 |
If your hard drive is completely blank, then you'll have to first create |
3792 |
a BSD disklabel. |
3793 |
</p> |
3794 |
|
3795 |
<pre caption="Creating a BSD disklabel"> |
3796 |
Command (m for help): <i>b</i> |
3797 |
/dev/sda contains no disklabel. |
3798 |
Do you want to create a disklabel? (y/n) <i>y</i> |
3799 |
<comment>A bunch of drive-specific info will show here</comment> |
3800 |
3 partitions: |
3801 |
# start end size fstype [fsize bsize cpg] |
3802 |
c: 1 5290* 5289* unused 0 0 |
3803 |
</pre> |
3804 |
|
3805 |
<p> |
3806 |
We start with deleting all slices <e>except</e> the 'c'-slice (a requirement |
3807 |
for using BSD disklabels). The following shows how to delete a slice (in |
3808 |
the example we use 'a'). Repeat the process to delete all other slices |
3809 |
(again, except the 'c'-slice). |
3810 |
</p> |
3811 |
|
3812 |
<p> |
3813 |
Use <c>p</c> to view all existing slices. <c>d</c> is used to delete a slice. |
3814 |
</p> |
3815 |
|
3816 |
<pre caption="Deleting a slice"> |
3817 |
BSD disklabel command (m for help): <i>p</i> |
3818 |
|
3819 |
8 partitions: |
3820 |
# start end size fstype [fsize bsize cpg] |
3821 |
a: 1 235* 234* 4.2BSD 1024 8192 16 |
3822 |
b: 235* 469* 234* swap |
3823 |
c: 1 5290* 5289* unused 0 0 |
3824 |
d: 469* 2076* 1607* unused 0 0 |
3825 |
e: 2076* 3683* 1607* unused 0 0 |
3826 |
f: 3683* 5290* 1607* unused 0 0 |
3827 |
g: 469* 1749* 1280 4.2BSD 1024 8192 16 |
3828 |
h: 1749* 5290* 3541* unused 0 0 |
3829 |
|
3830 |
BSD disklabel command (m for help): <i>d</i> |
3831 |
Partition (a-h): <i>a</i> |
3832 |
</pre> |
3833 |
|
3834 |
<p> |
3835 |
After repeating this process for all slices, a listing should show you something |
3836 |
similar to this: |
3837 |
</p> |
3838 |
|
3839 |
<pre caption="Viewing an empty scheme"> |
3840 |
BSD disklabel command (m for help): <i>p</i> |
3841 |
|
3842 |
3 partitions: |
3843 |
# start end size fstype [fsize bsize cpg] |
3844 |
c: 1 5290* 5289* unused 0 0 |
3845 |
</pre> |
3846 |
|
3847 |
</body> |
3848 |
</subsection> |
3849 |
<subsection> |
3850 |
<title>Creating the Swap Slice</title> |
3851 |
<body> |
3852 |
|
3853 |
<p> |
3854 |
On Alpha based systems you don't need a separate boot partition. However, the |
3855 |
first cylinder cannot be used as the <c>aboot</c> image will be placed there. |
3856 |
</p> |
3857 |
|
3858 |
<p> |
3859 |
We will create a swap slice starting at the third cylinder, with a total |
3860 |
size of 1 GB. Use <c>n</c> to create a new slice. After creating the slice, |
3861 |
we will change its type to <c>1</c> (one), meaning <e>swap</e>. |
3862 |
</p> |
3863 |
|
3864 |
<pre caption="Creating the swap slice"> |
3865 |
BSD disklabel command (m for help): <i>n</i> |
3866 |
Partition (a-p): <i>a</i> |
3867 |
First cylinder (1-5290, default 1): <i>3</i> |
3868 |
Last cylinder or +size or +sizeM or +sizeK (3-5290, default 5290): <i>+1024M</i> |
3869 |
|
3870 |
BSD disklabel command (m for help): <i>t</i> |
3871 |
Partition (a-c): <i>a</i> |
3872 |
Hex code (type L to list codes): <i>1</i> |
3873 |
</pre> |
3874 |
|
3875 |
<p> |
3876 |
After these steps you should see a layout similar to the following: |
3877 |
</p> |
3878 |
|
3879 |
<pre caption="Slice layout after creating the swap slice"> |
3880 |
BSD disklabel command (m for help): <i>p</i> |
3881 |
|
3882 |
3 partitions: |
3883 |
# start end size fstype [fsize bsize cpg] |
3884 |
a: 3 1003 1001 swap |
3885 |
c: 1 5290* 5289* unused 0 0 |
3886 |
</pre> |
3887 |
|
3888 |
</body> |
3889 |
</subsection> |
3890 |
<subsection> |
3891 |
<title>Create the Root Slice</title> |
3892 |
<body> |
3893 |
|
3894 |
<p> |
3895 |
We will now create the root slice, starting from the first cylinder <e>after</e> |
3896 |
the swap slice. Use the <c>p</c> command to view where the swap slice ends. In |
3897 |
our example, this is at 1003, making the root partition start at 1004. |
3898 |
</p> |
3899 |
|
3900 |
<p> |
3901 |
Another problem is that there is currently a bug in <c>fdisk</c> making it think |
3902 |
the number of available cylinders is one above the real number of cylinders. In |
3903 |
other words, when you are asked for the last cylinder, decrease the cylinder |
3904 |
number (in this example: 5290) with one. |
3905 |
</p> |
3906 |
|
3907 |
<p> |
3908 |
When the partition is created, we change the type to <c>8</c>, for <e>ext2</e>. |
3909 |
</p> |
3910 |
|
3911 |
<pre caption="Creating the root slice"> |
3912 |
D disklabel command (m for help): <i>n</i> |
3913 |
Partition (a-p): <i>b</i> |
3914 |
First cylinder (1-5290, default 1): <i>1004</i> |
3915 |
Last cylinder or +size or +sizeM or +sizeK (1004-5290, default 5290): <i>5289</i> |
3916 |
|
3917 |
BSD disklabel command (m for help): <i>t</i> |
3918 |
Partition (a-c): <i>b</i> |
3919 |
Hex code (type L to list codes): <i>8</i> |
3920 |
</pre> |
3921 |
|
3922 |
<p> |
3923 |
Your slice layout should now be similar to this: |
3924 |
</p> |
3925 |
|
3926 |
<pre caption="Viewing the slice layout"> |
3927 |
BSD disklabel command (m for help): <i>p</i> |
3928 |
|
3929 |
3 partitions: |
3930 |
# start end size fstype [fsize bsize cpg] |
3931 |
a: 3 1003 1001 swap |
3932 |
b: 1004 5289 4286 ext2 |
3933 |
c: 1 5290* 5289* unused 0 0 |
3934 |
</pre> |
3935 |
|
3936 |
</body> |
3937 |
</subsection> |
3938 |
<subsection> |
3939 |
<title>Save the Slice Layout and Exit</title> |
3940 |
<body> |
3941 |
|
3942 |
<p> |
3943 |
Save <c>fdisk</c> by typing <c>w</c>. This will also save your slice layout. |
3944 |
</p> |
3945 |
|
3946 |
<pre caption="Save and exit fdisk"> |
3947 |
Command (m for help): <i>w</i> |
3948 |
</pre> |
3949 |
|
3950 |
<p> |
3951 |
Now that your slices are created, you can now continue with <uri |
3952 |
link="#filesystems">Creating Filesystems</uri>. |
3953 |
</p> |
3954 |
|
3955 |
</body> |
3956 |
</subsection> |
3957 |
</section> |
3958 |
<section id="fdisk_ARC"> |
3959 |
<title>Using fdisk to Partition your Disk (ARC/AlphaBIOS only)</title> |
3960 |
<subsection> |
3961 |
<body> |
3962 |
|
3963 |
<p> |
3964 |
The following parts explain how to partition the disk with a layout |
3965 |
similar to the one described previously, namely: |
3966 |
</p> |
3967 |
|
3968 |
<table> |
3969 |
<tr> |
3970 |
<th>Partition</th> |
3971 |
<th>Description</th> |
3972 |
</tr> |
3973 |
<tr> |
3974 |
<ti><path>/dev/sda1</path></ti> |
3975 |
<ti>Boot partition</ti> |
3976 |
</tr> |
3977 |
<tr> |
3978 |
<ti><path>/dev/sda2</path></ti> |
3979 |
<ti>Swap partition</ti> |
3980 |
</tr> |
3981 |
<tr> |
3982 |
<ti><path>/dev/sda3</path></ti> |
3983 |
<ti>Root partition</ti> |
3984 |
</tr> |
3985 |
</table> |
3986 |
|
3987 |
<p> |
3988 |
Change your partition layout according to your own preference. |
3989 |
</p> |
3990 |
|
3991 |
</body> |
3992 |
</subsection> |
3993 |
<subsection> |
3994 |
<title>Identifying Available Disks</title> |
3995 |
<body> |
3996 |
|
3997 |
<p> |
3998 |
To figure out what disks you have running, use the following commands: |
3999 |
</p> |
4000 |
|
4001 |
<pre caption="Identifying available disks"> |
4002 |
# <i>dmesg | grep 'drive$'</i> <comment>(For IDE disks)</comment> |
4003 |
# <i>dmesg | grep 'scsi'</i> <comment>(For SCSI disks)</comment> |
4004 |
</pre> |
4005 |
|
4006 |
<p> |
4007 |
>From this output you should be able to see what disks were detected and their |
4008 |
respective <path>/dev</path> entry. In the following parts we assume that the |
4009 |
disk is a SCSI disk on <path>/dev/sda</path>. |
4010 |
</p> |
4011 |
|
4012 |
<p> |
4013 |
Now fire up <c>fdisk</c>: |
4014 |
</p> |
4015 |
|
4016 |
<pre caption="Starting fdisk"> |
4017 |
# <i>fdisk /dev/sda</i> |
4018 |
</pre> |
4019 |
|
4020 |
</body> |
4021 |
</subsection> |
4022 |
<subsection> |
4023 |
<title>Deleting All Partitions</title> |
4024 |
<body> |
4025 |
|
4026 |
<p> |
4027 |
If your hard drive is completely blank, then you'll have to first create |
4028 |
a DOS disklabel. |
4029 |
</p> |
4030 |
|
4031 |
<pre caption="Creating a DOS disklabel"> |
4032 |
Command (m for help): <i>o</i> |
4033 |
Building a new DOS disklabel. |
4034 |
</pre> |
4035 |
|
4036 |
<p> |
4037 |
We start with deleting all partitions. The following shows how to delete |
4038 |
a partition (in the example we use '1'). Repeat the process to delete all |
4039 |
other partitions. |
4040 |
</p> |
4041 |
|
4042 |
<p> |
4043 |
Use <c>p</c> to view all existing partitions. <c>d</c> is used to delete a |
4044 |
partition. |
4045 |
</p> |
4046 |
|
4047 |
<pre caption="Deleting a partition"> |
4048 |
command (m for help): <i>p</i> |
4049 |
|
4050 |
Disk /dev/sda: 9150 MB, 9150996480 bytes |
4051 |
64 heads, 32 sectors/track, 8727 cylinders |
4052 |
Units = cylinders of 2048 * 512 = 1048576 bytes |
4053 |
|
4054 |
Device Boot Start End Blocks Id System |
4055 |
/dev/sda1 1 478 489456 83 Linux |
4056 |
/dev/sda2 479 8727 8446976 5 Extended |
4057 |
/dev/sda5 479 1433 977904 83 Linux Swap |
4058 |
/dev/sda6 1434 8727 7469040 83 Linux |
4059 |
|
4060 |
command (m for help): <i>d</i> |
4061 |
Partition number (1-6): <i>1</i> |
4062 |
</pre> |
4063 |
|
4064 |
|
4065 |
</body> |
4066 |
</subsection> |
4067 |
<subsection> |
4068 |
<title>Creating the Boot Partition</title> |
4069 |
<body> |
4070 |
|
4071 |
<p> |
4072 |
On Alpha systems which use MILO to boot, we have to create a small vfat |
4073 |
boot partition. |
4074 |
</p> |
4075 |
|
4076 |
<pre caption="Creating the boot partition"> |
4077 |
Command (m for help): <i>n</i> |
4078 |
Command action |
4079 |
e extended |
4080 |
p primary partition (1-4) |
4081 |
<i>p</i> |
4082 |
Partition number (1-4): <i>1</i> |
4083 |
First cylinder (1-8727, default 1): <i>1</i> |
4084 |
Last cylinder or +size or +sizeM or +sizeK (1-8727, default 8727): <i>+16M</i> |
4085 |
|
4086 |
Command (m for help): <i>t</i> |
4087 |
Selected partition 1 |
4088 |
Hex code (type L to list codes): <i>6</i> |
4089 |
Changed system type of partition 1 to 6 (FAT16) |
4090 |
</pre> |
4091 |
|
4092 |
</body> |
4093 |
</subsection> |
4094 |
<subsection> |
4095 |
<title>Creating the Swap Partition</title> |
4096 |
<body> |
4097 |
|
4098 |
<p> |
4099 |
We will create a swap partition starting at the third cylinder, with a total |
4100 |
size of 1 GB. Use <c>n</c> to create a new partition. |
4101 |
</p> |
4102 |
|
4103 |
<pre caption="Creating the swap partition"> |
4104 |
Command (m for help): <i>n</i> |
4105 |
Command action |
4106 |
e extended |
4107 |
p primary partition (1-4) |
4108 |
<i>p</i> |
4109 |
Partition number (1-4): <i>2</i> |
4110 |
First cylinder (17-8727, default 17): <i>17</i> |
4111 |
Last cylinder or +size or +sizeM or +sizeK (17-8727, default 8727): <i>+1000M</i> |
4112 |
|
4113 |
Command (m for help): <i>t</i> |
4114 |
Partition number (1-4): <i>1</i> |
4115 |
Hex code (type L to list codes): <i>82</i> |
4116 |
Changed system type of partition 2 to 82 (Linux swap) |
4117 |
</pre> |
4118 |
|
4119 |
<p> |
4120 |
After these steps you should see a layout similar to the following: |
4121 |
</p> |
4122 |
|
4123 |
<pre caption="Partition listing after creating a swap partition"> |
4124 |
Command (m for help): <i>p</i> |
4125 |
|
4126 |
Disk /dev/sda: 9150 MB, 9150996480 bytes |
4127 |
64 heads, 32 sectors/track, 8727 cylinders |
4128 |
Units = cylinders of 2048 * 512 = 1048576 bytes |
4129 |
|
4130 |
Device Boot Start End Blocks Id System |
4131 |
/dev/sda1 1 16 16368 6 FAT16 |
4132 |
/dev/sda2 17 971 977920 82 Linux swap |
4133 |
</pre> |
4134 |
|
4135 |
</body> |
4136 |
</subsection> |
4137 |
<subsection> |
4138 |
<title>Creating the Root Partition</title> |
4139 |
<body> |
4140 |
|
4141 |
<p> |
4142 |
We will now create the root partition. Again, just use the <c>n</c> command. |
4143 |
</p> |
4144 |
|
4145 |
<pre caption="Creating the root partition"> |
4146 |
Command (m for help): <i>n</i> |
4147 |
Command action |
4148 |
e extended |
4149 |
p primary partition (1-4) |
4150 |
<i>p</i> |
4151 |
Partition number (1-4): <i>3</i> |
4152 |
First cylinder (972-8727, default 972): <i>972</i> |
4153 |
Last cylinder or +size or +sizeM or +sizeK (972-8727, default 8727): <i>8727</i> |
4154 |
</pre> |
4155 |
|
4156 |
<p> |
4157 |
After these steps you should see a layout similar to the following: |
4158 |
</p> |
4159 |
|
4160 |
<pre caption="Partition listing after creating the root partition"> |
4161 |
Command (m for help): <i>p</i> |
4162 |
|
4163 |
Disk /dev/sda: 9150 MB, 9150996480 bytes |
4164 |
64 heads, 32 sectors/track, 8727 cylinders |
4165 |
Units = cylinders of 2048 * 512 = 1048576 bytes |
4166 |
|
4167 |
Device Boot Start End Blocks Id System |
4168 |
/dev/sda1 1 16 16368 6 FAT16 |
4169 |
/dev/sda2 17 971 977920 82 Linux swap |
4170 |
/dev/sda3 972 8727 7942144 83 Linux |
4171 |
</pre> |
4172 |
|
4173 |
</body> |
4174 |
</subsection> |
4175 |
<subsection> |
4176 |
<title>Save the Partition Layout and Exit</title> |
4177 |
<body> |
4178 |
|
4179 |
<p> |
4180 |
Save <c>fdisk</c> by typing <c>w</c>. This will also save your partition layout. |
4181 |
</p> |
4182 |
|
4183 |
<pre caption="Save and exit fdisk"> |
4184 |
Command (m for help): <i>w</i> |
4185 |
</pre> |
4186 |
|
4187 |
<p> |
4188 |
Now that your partitions are created, you can now continue with <uri |
4189 |
link="#filesystems">Creating Filesystems</uri>. |
4190 |
</p> |
4191 |
|
4192 |
</body> |
4193 |
</subsection> |
4194 |
</section> |
4195 |
<section id="filesystems"> |
4196 |
<title>Creating Filesystems</title> |
4197 |
<subsection> |
4198 |
<title>Introduction</title> |
4199 |
<body> |
4200 |
|
4201 |
<p> |
4202 |
Now that your partitions are created, it is time to place a filesystem on them. |
4203 |
If you don't care about what filesystem to choose and are happy with what we use |
4204 |
as default in this handbook, continue with <uri |
4205 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
4206 |
Otherwise read on to learn about the available filesystems... |
4207 |
</p> |
4208 |
|
4209 |
</body> |
4210 |
</subsection> |
4211 |
<subsection> |
4212 |
<title>Filesystems?</title> |
4213 |
<body> |
4214 |
|
4215 |
<p> |
4216 |
Several filesystems are available. Most of them are found stable on the |
4217 |
Alpha architecture. |
4218 |
</p> |
4219 |
|
4220 |
<p> |
4221 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
4222 |
journaling, which means that routine ext2 filesystem checks at startup time can |
4223 |
be quite time-consuming. There is now quite a selection of newer-generation |
4224 |
journaled filesystems that can be checked for consistency very quickly and are |
4225 |
thus generally preferred over their non-journaled counterparts. Journaled |
4226 |
filesystems prevent long delays when you boot your system and your filesystem |
4227 |
happens to be in an inconsistent state. |
4228 |
</p> |
4229 |
|
4230 |
<p> |
4231 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
4232 |
journaling for fast recovery in addition to other enhanced journaling modes like |
4233 |
full data and ordered data journaling. ext3 is a very good and reliable |
4234 |
filesystem. It has an additional hashed b-tree indexing option that enables |
4235 |
high performance in almost all situations. You can enable this indexing by |
4236 |
adding <c>-O dir_index</c> to the <c>mke2fs</c> command. In short, ext3 is an |
4237 |
excellent filesystem. |
4238 |
</p> |
4239 |
|
4240 |
<p> |
4241 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
4242 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
4243 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
4244 |
extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is |
4245 |
solid and usable as both general-purpose filesystem and for extreme cases such |
4246 |
as the creation of large filesystems, the use of many small files, very large |
4247 |
files and directories containing tens of thousands of files. |
4248 |
</p> |
4249 |
|
4250 |
<p> |
4251 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
4252 |
feature-set and is optimized for scalability. We only recommend using this |
4253 |
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
4254 |
an uninterruptible power supply. Because XFS aggressively caches in-transit data |
4255 |
in RAM, improperly designed programs (those that don't take proper precautions |
4256 |
when writing files to disk and there are quite a few of them) can lose a good |
4257 |
deal of data if the system goes down unexpectedly. |
4258 |
</p> |
4259 |
|
4260 |
<p> |
4261 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
4262 |
become production-ready and there hasn't been a sufficient track record to |
4263 |
comment positively nor negatively on its general stability at this point. |
4264 |
</p> |
4265 |
|
4266 |
</body> |
4267 |
</subsection> |
4268 |
<subsection id="filesystems-apply"> |
4269 |
<title>Applying a Filesystem to a Partition</title> |
4270 |
<body> |
4271 |
|
4272 |
<p> |
4273 |
To create a filesystem on a partition or volume, there are tools available for |
4274 |
each possible filesystem: |
4275 |
</p> |
4276 |
|
4277 |
<table> |
4278 |
<tr> |
4279 |
<th>Filesystem</th> |
4280 |
<th>Creation Command</th> |
4281 |
</tr> |
4282 |
<tr> |
4283 |
<ti>ext2</ti> |
4284 |
<ti><c>mke2fs</c></ti> |
4285 |
</tr> |
4286 |
<tr> |
4287 |
<ti>ext3</ti> |
4288 |
<ti><c>mke2fs -j</c></ti> |
4289 |
</tr> |
4290 |
<tr> |
4291 |
<ti>reiserfs</ti> |
4292 |
<ti><c>mkreiserfs</c></ti> |
4293 |
</tr> |
4294 |
<tr> |
4295 |
<ti>xfs</ti> |
4296 |
<ti><c>mkfs.xfs</c></ti> |
4297 |
</tr> |
4298 |
<tr> |
4299 |
<ti>jfs</ti> |
4300 |
<ti><c>mkfs.jfs</c></ti> |
4301 |
</tr> |
4302 |
</table> |
4303 |
|
4304 |
<p> |
4305 |
For instance, to have the root partition (<path>/dev/sda2</path> in our example) |
4306 |
in ext3, you would use: |
4307 |
</p> |
4308 |
|
4309 |
<pre caption="Applying a filesystem on a partition"> |
4310 |
# <i>mke2fs -j /dev/sda2</i> |
4311 |
</pre> |
4312 |
|
4313 |
<p> |
4314 |
Now create the filesystems on your newly created partitions (or logical |
4315 |
volumes). |
4316 |
</p> |
4317 |
|
4318 |
</body> |
4319 |
</subsection> |
4320 |
<subsection> |
4321 |
<title>Activating the Swap Partition</title> |
4322 |
<body> |
4323 |
|
4324 |
<p> |
4325 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
4326 |
</p> |
4327 |
|
4328 |
<pre caption="Creating a Swap signature"> |
4329 |
# <i>mkswap /dev/sda1</i> |
4330 |
</pre> |
4331 |
|
4332 |
<p> |
4333 |
To activate the swap partition, use <c>swapon</c>: |
4334 |
</p> |
4335 |
|
4336 |
<pre caption="Activating the swap partition"> |
4337 |
# <i>swapon /dev/sda1</i> |
4338 |
</pre> |
4339 |
|
4340 |
<p> |
4341 |
Create and activate the swap with the commands mentioned above. |
4342 |
</p> |
4343 |
|
4344 |
</body> |
4345 |
</subsection> |
4346 |
</section> |
4347 |
<section> |
4348 |
<title>Mounting</title> |
4349 |
<body> |
4350 |
|
4351 |
<p> |
4352 |
Now that your partitions are initialized and are housing a filesystem, it is |
4353 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
4354 |
create the necessary mount directories for every partition you created. As an |
4355 |
example we mount the root and boot partition: |
4356 |
</p> |
4357 |
|
4358 |
<pre caption="Mounting partitions"> |
4359 |
# <i>mount /dev/sda2 /mnt/gentoo</i> |
4360 |
</pre> |
4361 |
|
4362 |
<note> |
4363 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
4364 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
4365 |
also holds for <path>/var/tmp</path>. |
4366 |
</note> |
4367 |
|
4368 |
<p> |
4369 |
We will also have to mount the proc filesystem (a virtual interface with the |
4370 |
kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. |
4371 |
</p> |
4372 |
|
4373 |
<p> |
4374 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
4375 |
Installation Files</uri>. |
4376 |
</p> |
4377 |
|
4378 |
</body> |
4379 |
</section> |
4380 |
</sections> |
4381 |
|
4382 |
|
4383 |
|
4384 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-alpha-kernel.xml |
4385 |
|
4386 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-alpha-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
4387 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-alpha-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
4388 |
|
4389 |
Index: hb-install-alpha-kernel.xml |
4390 |
=================================================================== |
4391 |
<?xml version='1.0' encoding='UTF-8'?> |
4392 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
4393 |
|
4394 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
4395 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
4396 |
|
4397 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-alpha-kernel.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
4398 |
|
4399 |
<sections> |
4400 |
|
4401 |
<version>5.5</version> |
4402 |
<date>2006-01-06</date> |
4403 |
|
4404 |
<section> |
4405 |
<title>Timezone</title> |
4406 |
<body> |
4407 |
|
4408 |
<p> |
4409 |
You first need to select your timezone so that your system knows where it is |
4410 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
4411 |
it to <path>/etc/localtime</path>. Please avoid the |
4412 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
4413 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
4414 |
</p> |
4415 |
|
4416 |
<pre caption="Setting the timezone information"> |
4417 |
# <i>ls /usr/share/zoneinfo</i> |
4418 |
<comment>(Suppose you want to use GMT)</comment> |
4419 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
4420 |
</pre> |
4421 |
|
4422 |
</body> |
4423 |
</section> |
4424 |
<section> |
4425 |
<title>Installing the Sources</title> |
4426 |
<subsection> |
4427 |
<title>Choosing a Kernel</title> |
4428 |
<body> |
4429 |
|
4430 |
<p> |
4431 |
The core around which all distributions are built is the Linux kernel. It is the |
4432 |
layer between the user programs and your system hardware. Gentoo provides its |
4433 |
users several possible kernel sources. A full listing with description is |
4434 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
4435 |
Guide</uri>. |
4436 |
</p> |
4437 |
|
4438 |
<p> |
4439 |
For alpha-based systems we have <c>vanilla-sources</c> (the default 2.6 kernel source). |
4440 |
</p> |
4441 |
|
4442 |
<p> |
4443 |
Choose your kernel source and install it using <c>emerge</c>. The |
4444 |
<c>USE="-doc"</c> is necessary to avoid installing xorg-x11 or other |
4445 |
dependencies at this point. <c>USE="symlink"</c> is not necessary for a new |
4446 |
install, but ensures proper creation of the <path>/usr/src/linux</path> |
4447 |
symlink. |
4448 |
</p> |
4449 |
|
4450 |
<p> |
4451 |
In the next example we install the <c>vanilla-sources</c>. |
4452 |
Of course substitute with your choice of sources, this is merely an example: |
4453 |
</p> |
4454 |
|
4455 |
<pre caption="Installing a kernel source"> |
4456 |
# <i>USE="-doc symlink" emerge vanilla-sources</i> |
4457 |
</pre> |
4458 |
|
4459 |
<p> |
4460 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
4461 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
4462 |
kernel source points to <c>vanilla-sources-2.6.11.2</c>. Your version may be |
4463 |
different, so keep this in mind. |
4464 |
</p> |
4465 |
|
4466 |
<pre caption="Viewing the kernel source symlink"> |
4467 |
# <i>ls -l /usr/src/linux</i> |
4468 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-2.6.11.2 |
4469 |
</pre> |
4470 |
|
4471 |
<p> |
4472 |
Now it is time to configure and compile your kernel source. You |
4473 |
can use <c>genkernel</c> for this, which will build a generic kernel as used |
4474 |
by the Installation CD. We explain the "manual" configuration first though, as it is |
4475 |
the best way to optimize your environment. |
4476 |
</p> |
4477 |
|
4478 |
<p> |
4479 |
If you want to manually configure your kernel, continue now with <uri |
4480 |
link="#manual">Default: Manual Configuration</uri>. If you want to use |
4481 |
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
4482 |
genkernel</uri> instead. |
4483 |
</p> |
4484 |
|
4485 |
</body> |
4486 |
</subsection> |
4487 |
</section> |
4488 |
<section id="manual"> |
4489 |
<title>Default: Manual Configuration</title> |
4490 |
<subsection> |
4491 |
<title>Introduction</title> |
4492 |
<body> |
4493 |
|
4494 |
<p> |
4495 |
Manually configuring a kernel is often seen as the most difficult procedure a |
4496 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
4497 |
couple of kernels you don't even remember that it was difficult ;) |
4498 |
</p> |
4499 |
|
4500 |
<p> |
4501 |
However, one thing <e>is</e> true: you must know your system when you start |
4502 |
configuring a kernel manually. You can run <c>lsmod</c> to see what kernel |
4503 |
modules the Installation CD uses (it might provide you with a nice hint on |
4504 |
what to enable). |
4505 |
</p> |
4506 |
|
4507 |
<p> |
4508 |
Now go to your kernel source directory and execute <c>make menuconfig</c>. This |
4509 |
will fire up an ncurses-based configuration menu. |
4510 |
</p> |
4511 |
|
4512 |
<pre caption="Invoking menuconfig"> |
4513 |
# <i>cd /usr/src/linux</i> |
4514 |
# <i>make menuconfig</i> |
4515 |
</pre> |
4516 |
|
4517 |
<p> |
4518 |
You will be greeted with several configuration sections. We'll first list some |
4519 |
options you must activate (otherwise Gentoo will not function, or not function |
4520 |
properly without additional tweaks). |
4521 |
</p> |
4522 |
|
4523 |
</body> |
4524 |
</subsection> |
4525 |
<subsection> |
4526 |
<title>Activating Required Options</title> |
4527 |
<body> |
4528 |
|
4529 |
<p> |
4530 |
First of all, activate the use of development and experimental code/drivers. |
4531 |
You need this, otherwise some very important code/drivers won't show up: |
4532 |
</p> |
4533 |
|
4534 |
<pre caption="Selecting experimental code/drivers, General setup"> |
4535 |
Code maturity level options ---> |
4536 |
[*] Prompt for development and/or incomplete code/drivers |
4537 |
General setup ---> |
4538 |
[*] Support for hot-pluggable devices |
4539 |
</pre> |
4540 |
|
4541 |
<p> |
4542 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
4543 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
4544 |
able to mount your partitions. Also select <c>Virtual memory</c>, <c>/proc |
4545 |
file system</c>, (<c>/dev file system</c> + <c>Automatically mount at boot</c> only for 2.4 kernel): |
4546 |
</p> |
4547 |
|
4548 |
<pre caption="Selecting necessary file systems"> |
4549 |
<comment>(With a 2.4.x kernel)</comment> |
4550 |
File systems ---> |
4551 |
[*] Virtual memory file system support (former shm fs) |
4552 |
[*] /proc file system support |
4553 |
[*] /dev file system support (EXPERIMENTAL) |
4554 |
[*] Automatically mount at boot |
4555 |
[ ] /dev/pts file system for Unix98 PTYs |
4556 |
|
4557 |
<comment>(With a 2.6.x kernel)</comment> |
4558 |
File systems ---> |
4559 |
Pseudo Filesystems ---> |
4560 |
[*] /proc file system support |
4561 |
[*] Virtual memory file system support (former shm fs) |
4562 |
|
4563 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
4564 |
<*> Reiserfs support |
4565 |
<*> Ext3 journalling file system support |
4566 |
<*> JFS filesystem support |
4567 |
<*> Second extended fs support |
4568 |
<*> XFS filesystem support |
4569 |
</pre> |
4570 |
|
4571 |
<p> |
4572 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
4573 |
modem, you will need the following options in the kernel: |
4574 |
</p> |
4575 |
|
4576 |
<pre caption="Selecting PPPoE necessary drivers"> |
4577 |
<comment>(With a 2.4.x kernel)</comment> |
4578 |
Network device support ---> |
4579 |
<*> PPP (point-to-point protocol) support |
4580 |
<*> PPP support for async serial ports |
4581 |
<*> PPP support for sync tty ports |
4582 |
|
4583 |
<comment>(With a 2.6.x kernel)</comment> |
4584 |
Device Drivers ---> |
4585 |
Networking support ---> |
4586 |
<*> PPP (point-to-point protocol) support |
4587 |
<*> PPP support for async serial ports |
4588 |
<*> PPP support for sync tty ports |
4589 |
</pre> |
4590 |
|
4591 |
<p> |
4592 |
The two compression options won't harm but are not definitely needed, neither |
4593 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
4594 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
4595 |
</p> |
4596 |
|
4597 |
<p> |
4598 |
If you require it, don't forget to include support in the kernel for your |
4599 |
ethernet card. |
4600 |
</p> |
4601 |
|
4602 |
<p> |
4603 |
The following options are recommended as well: |
4604 |
</p> |
4605 |
|
4606 |
<pre caption="Recommended Alpha options"> |
4607 |
General setup ---> |
4608 |
<*> SRM environment through procfs |
4609 |
<*> Configure uac policy via sysctl |
4610 |
|
4611 |
Plug and Play configuration ---> |
4612 |
<*> Plug and Play support |
4613 |
<M> ISA Plug and Play support |
4614 |
|
4615 |
SCSI support ---> |
4616 |
SCSI low-level drivers ---> |
4617 |
<*> SYM53C8XX Version 2 SCSI support (NEW) |
4618 |
<*> Qlogic ISP SCSI support |
4619 |
|
4620 |
Network device support ---> |
4621 |
Ethernet (10 or 100 Mbit) ---> |
4622 |
<M> DECchip Tulip (dc21x4x) PCI support |
4623 |
<M> Generic DECchip & DIGITAL EtherWORKS PCI/EISA |
4624 |
<M> EtherExpressPro/100 support (eepro100) |
4625 |
<M> EtherExpressPro/100 support (e100) |
4626 |
Ethernet (1000 Mbit) ---> |
4627 |
<M> Alteon AceNIC |
4628 |
[*] Omit support for old Tigon I |
4629 |
<M> Broadcom Tigon3 |
4630 |
[*] FDDI driver support |
4631 |
<M> Digital DEFEA and DEFPA |
4632 |
<*> PPP support |
4633 |
<*> PPP Deflate compression |
4634 |
|
4635 |
Character devices ---> |
4636 |
[*] Support for console on serial port |
4637 |
[*] Direct Rendering Manager |
4638 |
|
4639 |
File systems ---> |
4640 |
<*> Kernel automounter version 4 support |
4641 |
Network File Systems ---> |
4642 |
<*> NFS |
4643 |
[*] NFSv3 client |
4644 |
<*> NFS server |
4645 |
[*] NFSv3 server |
4646 |
Partition Types ---> |
4647 |
[*] Advanced partition selection |
4648 |
[*] Alpha OSF partition support |
4649 |
Native Language Support |
4650 |
<*> NLS ISO 8859-1 |
4651 |
|
4652 |
Sound ---> |
4653 |
<M> Sound card support |
4654 |
<M> OSS sound modules |
4655 |
[*] Verbose initialisation |
4656 |
[*] Persistent DMA buffers |
4657 |
<M> 100% Sound Blaster compatibles |
4658 |
</pre> |
4659 |
|
4660 |
<p> |
4661 |
When you've finished configuring the kernel, continue with <uri |
4662 |
link="#compiling">Compiling and Installing</uri>. |
4663 |
</p> |
4664 |
|
4665 |
</body> |
4666 |
</subsection> |
4667 |
<subsection id="compiling"> |
4668 |
<title>Compiling and Installing</title> |
4669 |
<body> |
4670 |
|
4671 |
<p> |
4672 |
Now that your kernel is configured, it is time to compile and install it. Exit |
4673 |
the configuration and start the compilation process: |
4674 |
</p> |
4675 |
|
4676 |
<pre caption="Compiling the kernel"> |
4677 |
<comment>(For 2.4 kernel)</comment> |
4678 |
# <i>make dep && make vmlinux modules modules_install</i> |
4679 |
|
4680 |
<comment>(For 2.6 kernel)</comment> |
4681 |
# <i>make && make modules_install</i> |
4682 |
|
4683 |
<comment>(For all kernels)</comment> |
4684 |
# <i>make boot</i> |
4685 |
</pre> |
4686 |
|
4687 |
<p> |
4688 |
When the kernel has finished compiling, copy the kernel image to |
4689 |
<path>/boot</path>. Recent kernels might create <path>vmlinux</path> instead of |
4690 |
<path>vmlinux.gz</path>. Keep this in mind when you copy your kernel image. |
4691 |
</p> |
4692 |
|
4693 |
<pre caption="Installing the kernel"> |
4694 |
# <i>cp arch/alpha/boot/vmlinux.gz /boot/</i> |
4695 |
</pre> |
4696 |
|
4697 |
<p> |
4698 |
Now continue with <uri link="#kernel_modules">Installing Separate Kernel |
4699 |
Modules</uri>. |
4700 |
</p> |
4701 |
|
4702 |
</body> |
4703 |
</subsection> |
4704 |
</section> |
4705 |
<section id="genkernel"> |
4706 |
<title>Alternative: Using genkernel</title> |
4707 |
<body> |
4708 |
|
4709 |
<p> |
4710 |
If you are reading this section, you have chosen to use our <c>genkernel</c> |
4711 |
script to configure your kernel for you. |
4712 |
</p> |
4713 |
|
4714 |
<p> |
4715 |
Now that your kernel source tree is installed, it's now time to compile your |
4716 |
kernel by using our <c>genkernel</c> script to automatically build a kernel for |
4717 |
you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
4718 |
way our Installation CD kernel is configured. This means that when you use |
4719 |
<c>genkernel</c> to build your kernel, your system will generally detect all |
4720 |
your hardware at boot-time, just like our Installation CD does. Because genkernel |
4721 |
doesn't require any manual kernel configuration, it is an ideal solution for |
4722 |
those users who may not be comfortable compiling their own kernels. |
4723 |
</p> |
4724 |
|
4725 |
<p> |
4726 |
Now, let's see how to use genkernel. First, emerge the genkernel ebuild: |
4727 |
</p> |
4728 |
|
4729 |
<pre caption="Emerging genkernel"> |
4730 |
# <i>emerge genkernel</i> |
4731 |
</pre> |
4732 |
|
4733 |
<p> |
4734 |
Now, compile your kernel sources by running <c>genkernel all</c>. |
4735 |
Be aware though, as <c>genkernel</c> compiles a kernel that supports almost all |
4736 |
hardware, this compilation will take quite a while to finish! |
4737 |
</p> |
4738 |
|
4739 |
<p> |
4740 |
Note that, if your boot partition doesn't use ext2 or ext3 as filesystem you |
4741 |
need to manually configure your kernel using <c>genkernel --menuconfig all</c> |
4742 |
and add support for your filesystem <e>in</e> the kernel (i.e. <e>not</e> as a |
4743 |
module). |
4744 |
</p> |
4745 |
|
4746 |
<pre caption="Running genkernel"> |
4747 |
# <i>genkernel all</i> |
4748 |
GenKernel v3.0.1_beta10 |
4749 |
* ARCH: Alpha |
4750 |
* KERNEL VER: 2.6.11.2 |
4751 |
* kernel: configuring source |
4752 |
* kernel: running mrproper |
4753 |
<comment>(Output removed to increase readability)</comment> |
4754 |
* Kernel compiled successfully! |
4755 |
* Required Kernel Params: |
4756 |
* : root=/dev/ram0 init=/linuxrc real_root=/dev/$ROOT |
4757 |
* where $ROOT is the devicenode for your root partition as |
4758 |
* you should have specified in /etc/fstab |
4759 |
* |
4760 |
* You MUST tell your bootloader to use the generated initrd |
4761 |
* |
4762 |
* Recommended Kernel Params: |
4763 |
* : vga=0x317 splash=verbose |
4764 |
* |
4765 |
* Do NOT report kernel bugs (configs included) as genkernel bugs. |
4766 |
* Make sure you have the latest genkernel before reporting bugs |
4767 |
* |
4768 |
* For more info see /usr/share/genkernel/README |
4769 |
</pre> |
4770 |
|
4771 |
<p> |
4772 |
Once <c>genkernel</c> completes, a kernel, full set of modules and |
4773 |
<e>initial root disk</e> (initrd) will be created. We will use the kernel |
4774 |
and initrd when configuring a boot loader later in this document. Write |
4775 |
down the names of the kernel and initrd as you will need it when writing |
4776 |
the bootloader configuration file. The initrd will be started immediately after |
4777 |
booting to perform hardware autodetection (just like on the Installation CD) before |
4778 |
your "real" system starts up. |
4779 |
</p> |
4780 |
|
4781 |
<pre caption="Checking the created kernel image name and initrd"> |
4782 |
# <i>ls /boot/kernel* /boot/initramfs*</i> |
4783 |
</pre> |
4784 |
|
4785 |
<p> |
4786 |
Now, let's perform one more step to get our system to be more like the Installation CD -- let's emerge <c>coldplug</c>. While the initrd autodetects hardware that |
4787 |
is needed to boot your system, <c>coldplug</c> autodetects everything else. |
4788 |
To emerge and enable <c>coldplug</c>, type the following: |
4789 |
</p> |
4790 |
|
4791 |
<pre caption="Emerging and enabling coldplug"> |
4792 |
# <i>emerge coldplug</i> |
4793 |
# <i>rc-update add coldplug boot</i> |
4794 |
</pre> |
4795 |
|
4796 |
</body> |
4797 |
</section> |
4798 |
<section id="kernel_modules"> |
4799 |
<title>Installing Separate Kernel Modules</title> |
4800 |
<subsection> |
4801 |
<title>Installing Extra Modules</title> |
4802 |
<body> |
4803 |
|
4804 |
<p> |
4805 |
If appropriate, you should emerge ebuilds for any additional hardware that is |
4806 |
on your system. Here is a list of kernel-related ebuilds that you could emerge: |
4807 |
</p> |
4808 |
|
4809 |
<table> |
4810 |
<tcolumn width="1in"/> |
4811 |
<tcolumn width="4in"/> |
4812 |
<tcolumn width="2in"/> |
4813 |
<tr> |
4814 |
<th>Ebuild</th> |
4815 |
<th>Purpose</th> |
4816 |
<th>Command</th> |
4817 |
</tr> |
4818 |
<tr> |
4819 |
<ti>x11-drm</ti> |
4820 |
<ti> |
4821 |
Accelerated graphics for ATI Radeon up to 9200, Rage128, Matrox, Voodoo and |
4822 |
other cards for xorg-x11. Please check the <c>IUSE_VIDEO_CARDS</c> variable |
4823 |
in the <path>/usr/portage/x11-base/x11-drm</path> ebuilds to see what you |
4824 |
need to fill in as <c>yourcard</c>. |
4825 |
</ti> |
4826 |
<ti><c>VIDEO_CARDS="yourcard" emerge x11-drm</c></ti> |
4827 |
</tr> |
4828 |
</table> |
4829 |
|
4830 |
<p> |
4831 |
Beware though, some of these ebuilds might deal with big dependencies. To verify |
4832 |
what packages will be installed by emerging an ebuild, use <c>emerge |
4833 |
--pretend</c>. For instance, for the <c>x11-drm</c> package: |
4834 |
</p> |
4835 |
|
4836 |
<pre caption="View full installation package listing"> |
4837 |
# <i>emerge --pretend x11-drm</i> |
4838 |
</pre> |
4839 |
|
4840 |
</body> |
4841 |
</subsection> |
4842 |
<subsection> |
4843 |
<title>Configuring the Modules</title> |
4844 |
<body> |
4845 |
|
4846 |
<p> |
4847 |
You should list the modules you want automatically loaded in |
4848 |
<path>/etc/modules.autoload.d/kernel-2.4</path> (or <path>kernel-2.6</path>). |
4849 |
You can add extra options to the modules too if you want. |
4850 |
</p> |
4851 |
|
4852 |
<p> |
4853 |
To view all available modules, run the following <c>find</c> command. Don't |
4854 |
forget to substitute "<kernel version>" with the version of the kernel you |
4855 |
just compiled: |
4856 |
</p> |
4857 |
|
4858 |
<pre caption="Viewing all available modules"> |
4859 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
4860 |
</pre> |
4861 |
|
4862 |
<p> |
4863 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
4864 |
<path>kernel-2.4</path> or <path>kernel-2.6</path> file and enter the module |
4865 |
name in it. |
4866 |
</p> |
4867 |
|
4868 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.4"> |
4869 |
<comment>(Example for 2.4 kernels)</comment> |
4870 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.4</i> |
4871 |
</pre> |
4872 |
|
4873 |
<pre caption="/etc/modules.autoload.d/kernel-2.4 or kernel-2.6"> |
4874 |
3c59x |
4875 |
</pre> |
4876 |
|
4877 |
<p> |
4878 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
4879 |
your System</uri>. |
4880 |
</p> |
4881 |
|
4882 |
</body> |
4883 |
</subsection> |
4884 |
</section> |
4885 |
</sections> |
4886 |
|
4887 |
|
4888 |
|
4889 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-alpha-medium.xml |
4890 |
|
4891 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-alpha-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
4892 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-alpha-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
4893 |
|
4894 |
Index: hb-install-alpha-medium.xml |
4895 |
=================================================================== |
4896 |
<?xml version='1.0' encoding='UTF-8'?> |
4897 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
4898 |
|
4899 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
4900 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
4901 |
|
4902 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-alpha-medium.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
4903 |
|
4904 |
<sections> |
4905 |
|
4906 |
<version>5.3</version> |
4907 |
<date>2005-11-29</date> |
4908 |
|
4909 |
<section> |
4910 |
<title>Hardware Requirements</title> |
4911 |
<subsection> |
4912 |
<title>Introduction</title> |
4913 |
<body> |
4914 |
|
4915 |
<p> |
4916 |
Before we start, we first list what hardware requirements you need to |
4917 |
successfully install Gentoo on your box. |
4918 |
</p> |
4919 |
|
4920 |
</body> |
4921 |
</subsection> |
4922 |
<subsection> |
4923 |
<title>Hardware Requirements</title> |
4924 |
<body> |
4925 |
|
4926 |
<table> |
4927 |
<tr> |
4928 |
<th>CPU</th> |
4929 |
<ti> |
4930 |
Please check with the <uri |
4931 |
link="http://www.alphalinux.org/faq/FAQ-5.html">Alpha/Linux FAQ</uri> |
4932 |
</ti> |
4933 |
</tr> |
4934 |
<tr> |
4935 |
<th>Memory</th> |
4936 |
<ti>64 MB</ti> |
4937 |
</tr> |
4938 |
<tr> |
4939 |
<th>Diskspace</th> |
4940 |
<ti>1.5 GB (excluding swap space)</ti> |
4941 |
</tr> |
4942 |
<tr> |
4943 |
<th>Swap space</th> |
4944 |
<ti>At least 256 MB</ti> |
4945 |
</tr> |
4946 |
</table> |
4947 |
|
4948 |
</body> |
4949 |
</subsection> |
4950 |
</section> |
4951 |
<!-- Copy/paste from the hb-install-x86-medium.xml file but no Universal |
4952 |
Installation CD. |
4953 |
Also s/x86/alpha --> |
4954 |
<!-- START --> |
4955 |
<section> |
4956 |
<title>The Gentoo Universal Installation CD</title> |
4957 |
<subsection> |
4958 |
<title>Introduction</title> |
4959 |
<body> |
4960 |
|
4961 |
<p> |
4962 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
4963 |
Such a tarball is an archive that contains a minimal environment from |
4964 |
which you can successfully install Gentoo Linux onto your system. |
4965 |
</p> |
4966 |
|
4967 |
<p> |
4968 |
Installations using a stage1 or stage2 tarball file are not documented in the |
4969 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
4970 |
FAQ</uri> on these matters. |
4971 |
</p> |
4972 |
|
4973 |
</body> |
4974 |
</subsection> |
4975 |
<subsection> |
4976 |
<title>Gentoo Universal Installation CD</title> |
4977 |
<body> |
4978 |
|
4979 |
<p> |
4980 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
4981 |
environment. It allows you to boot Linux from the CD. During the boot process |
4982 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
4983 |
Installation CDs are maintained by Gentoo developers. |
4984 |
</p> |
4985 |
|
4986 |
<p> |
4987 |
There currently are two Installation CDs available: |
4988 |
</p> |
4989 |
|
4990 |
<ul> |
4991 |
<li> |
4992 |
The Universal Installation CD contains everything you need to install |
4993 |
Gentoo. It provides stage3 files for common architectures, source code |
4994 |
for the extra applications you need to choose from and, of course, the |
4995 |
installation instructions for your architecture. |
4996 |
</li> |
4997 |
<li> |
4998 |
The Minimal Installation CD contains only a minimal environment that allows |
4999 |
you to boot up and configure your network so you can connect to the |
5000 |
Internet. It does not contain any additional files and cannot be used |
5001 |
during the current installation approach. |
5002 |
</li> |
5003 |
</ul> |
5004 |
|
5005 |
<p> |
5006 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
5007 |
additional resource that you can exploit during the installation of your Gentoo |
5008 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
5009 |
you to easily and quickly install additional applications (such as |
5010 |
OpenOffice.org, KDE, GNOME, ...) immediately after the Gentoo installation and |
5011 |
right before you update your Portage tree. |
5012 |
</p> |
5013 |
|
5014 |
<p> |
5015 |
The use of the Package CD is covered later in this document. |
5016 |
</p> |
5017 |
|
5018 |
</body> |
5019 |
</subsection> |
5020 |
</section> |
5021 |
<!-- STOP --> |
5022 |
<section> |
5023 |
<title>Download, Burn and Boot the Gentoo Universal Installation CD</title> |
5024 |
<subsection> |
5025 |
<title>Downloading and Burning the Installation CD</title> |
5026 |
<body> |
5027 |
|
5028 |
<p> |
5029 |
You can download the Universal Installation CD (and, if you want to, the |
5030 |
Packages CD as well) from one of our <uri |
5031 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CD is located in |
5032 |
the <path>releases/alpha/2005.1/installcd</path> directory; |
5033 |
the Package CD is located in the <path>releases/alpha/2005.1/packagecd</path> |
5034 |
directory. |
5035 |
</p> |
5036 |
|
5037 |
<p> |
5038 |
Inside those directories you'll find ISO-files. Those are full CD images which |
5039 |
you can write on a CD-R. |
5040 |
</p> |
5041 |
|
5042 |
<p> |
5043 |
After downloading the file, you can verify its integrity to see if it is |
5044 |
corrupted or not: |
5045 |
</p> |
5046 |
|
5047 |
<ul> |
5048 |
<li> |
5049 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
5050 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
5051 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows) |
5052 |
</li> |
5053 |
<li> |
5054 |
You can verify the cryptographic signature that we provide. You need to |
5055 |
obtain the public key we use (17072058) before you proceed though. |
5056 |
</li> |
5057 |
</ul> |
5058 |
|
5059 |
<p> |
5060 |
To fetch our public key using the GnuPG application, run the following command: |
5061 |
</p> |
5062 |
|
5063 |
<pre caption="Obtaining the public key"> |
5064 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
5065 |
</pre> |
5066 |
|
5067 |
<p> |
5068 |
Now verify the signature: |
5069 |
</p> |
5070 |
|
5071 |
<pre caption="Verify the cryptographic signature"> |
5072 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
5073 |
</pre> |
5074 |
|
5075 |
<p> |
5076 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
5077 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
5078 |
<c>K3B</c> here; more information can be found in our <uri |
5079 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
5080 |
</p> |
5081 |
|
5082 |
<ul> |
5083 |
<li> |
5084 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
5085 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
5086 |
path). |
5087 |
</li> |
5088 |
<li> |
5089 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
5090 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
5091 |
<c>Start</c>. |
5092 |
</li> |
5093 |
</ul> |
5094 |
|
5095 |
</body> |
5096 |
</subsection> |
5097 |
<subsection> |
5098 |
<title>Booting the Universal Installation CD</title> |
5099 |
<body> |
5100 |
|
5101 |
<p> |
5102 |
When your Alpha is powered on, the first thing that gets started is the |
5103 |
firmware. It is loosely synonymous with the BIOS software on PC systems. There |
5104 |
are two types of firmware on Alpha systems: SRM (<e>Systems Reference |
5105 |
Manual</e>) and ARC (<e>Advanced Risc Console</e>). |
5106 |
</p> |
5107 |
|
5108 |
<p> |
5109 |
SRM is based on the Alpha Console Subsystem specification, which provides an |
5110 |
operating environment for OpenVMS, Tru64 UNIX, and Linux operating systems. ARC |
5111 |
is based on the Advanced RISC Computing (ARC) specification, which provides |
5112 |
an operating environment for Windows NT. You can find a |
5113 |
<uri link="http://www.alphalinux.org/faq/SRM-HOWTO/">detailed guide</uri> on |
5114 |
using SRM over at the Alpha Linux website. |
5115 |
</p> |
5116 |
|
5117 |
<p> |
5118 |
If your Alpha system supports both SRC and ARCs (ARC, AlphaBIOS, ARCSBIOS) you |
5119 |
should follow <uri link="http://www.alphalinux.org/faq/x31.html">these |
5120 |
instructions</uri> for switching to SRM. If your system already uses SRM, you |
5121 |
are all set. If your system can only use ARCs (Ruffian, nautilus, xl, etc.) you |
5122 |
will need to choose <c>MILO</c> later on when we are talking about bootloaders. |
5123 |
</p> |
5124 |
|
5125 |
<p> |
5126 |
Now to boot an Alpha Installation CD, put the CD-ROM in the tray and reboot the system. |
5127 |
You can use SRM to boot the Installation CD. If you cannot do that, you will have to use |
5128 |
<c>MILO</c>. If you don't have <c>MILO</c> installed already, use one of the |
5129 |
precompiled <c>MILO</c> images available on <uri |
5130 |
link="http://dev.gentoo.org/~taviso/milo/">taviso's homepage</uri>. |
5131 |
</p> |
5132 |
|
5133 |
<pre caption="Booting a CD-ROM using SRM"> |
5134 |
<comment>(List available hardware drives)</comment> |
5135 |
>>> <i>show device</i> |
5136 |
dkb0.0.1.4.0 DKB0 TOSHIBA CDROM |
5137 |
<comment>(...)</comment> |
5138 |
<comment>(Substitute dkb0 with your CD-ROM drive device)</comment> |
5139 |
>>> <i>boot dkb0 -flags 0</i> |
5140 |
<comment>To boot the 2.4 kernel instead of the default 2.6 kernel use:</comment> |
5141 |
>>> <i>boot dkb -flags 1</i> |
5142 |
</pre> |
5143 |
|
5144 |
<pre caption="Booting a CD-ROM using MILO"> |
5145 |
<comment>(Substitute hdb with your CD-ROM drive device)</comment> |
5146 |
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> |
5147 |
<comment>To boot the 2.4 kernel instead of the default 2.6 kernel use:</comment> |
5148 |
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> |
5149 |
</pre> |
5150 |
|
5151 |
<p> |
5152 |
You should have a root ("#") prompt on the current console and can also switch |
5153 |
to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get back to the one you |
5154 |
started on by pressing Alt-F1. |
5155 |
</p> |
5156 |
|
5157 |
<p> |
5158 |
Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
5159 |
</p> |
5160 |
|
5161 |
</body> |
5162 |
</subsection> |
5163 |
<subsection id="hardware"> |
5164 |
<title>Extra Hardware Configuration</title> |
5165 |
<body> |
5166 |
|
5167 |
<p> |
5168 |
When the Installation CD boots, it tries to detect all your hardware devices and |
5169 |
loads the appropriate kernel modules to support your hardware. In the |
5170 |
vast majority of cases, it does a very good job. However, in some cases (the |
5171 |
SPARC Installation CDs don't even do autodetection), it may not auto-load the kernel |
5172 |
modules you need. If the PCI auto-detection missed some of your system's |
5173 |
hardware, you will have to load the appropriate kernel modules manually. |
5174 |
</p> |
5175 |
|
5176 |
<p> |
5177 |
In the next example we try to load the <c>8139too</c> module (support for |
5178 |
certain kinds of network interfaces): |
5179 |
</p> |
5180 |
|
5181 |
<pre caption="Loading kernel modules"> |
5182 |
# <i>modprobe 8139too</i> |
5183 |
</pre> |
5184 |
|
5185 |
<p> |
5186 |
If you need PCMCIA support, you should start the <c>pcmcia</c> init script: |
5187 |
</p> |
5188 |
|
5189 |
<pre caption="Starting the PCMCIA init script"> |
5190 |
# <i>/etc/init.d/pcmcia start</i> |
5191 |
</pre> |
5192 |
|
5193 |
</body> |
5194 |
</subsection> |
5195 |
<subsection> |
5196 |
<title>Optional: Tweaking Hard Disk Performance</title> |
5197 |
<body> |
5198 |
|
5199 |
<p> |
5200 |
If you are an advanced user, you might want to tweak the IDE hard disk |
5201 |
performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
5202 |
test the performance of your disk (execute it several times to get a |
5203 |
more precise impression): |
5204 |
</p> |
5205 |
|
5206 |
<pre caption="Testing disk performance"> |
5207 |
# <i>hdparm -tT /dev/hda</i> |
5208 |
</pre> |
5209 |
|
5210 |
<p> |
5211 |
To tweak, you can use any of the following examples (or experiment |
5212 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
5213 |
disk): |
5214 |
</p> |
5215 |
|
5216 |
<pre caption="Tweaking hard disk performance"> |
5217 |
<comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i> |
5218 |
<comment>Activate DMA + Safe Performance-enhancing Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
5219 |
</pre> |
5220 |
|
5221 |
</body> |
5222 |
</subsection> |
5223 |
<subsection id="useraccounts"> |
5224 |
<title>Optional: User Accounts</title> |
5225 |
<body> |
5226 |
|
5227 |
<p> |
5228 |
If you plan on giving other people access to your installation |
5229 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
5230 |
security reasons), you need to create the necessary user accounts and change |
5231 |
the root password. |
5232 |
</p> |
5233 |
|
5234 |
<p> |
5235 |
To change the root password, use the <c>passwd</c> utility: |
5236 |
</p> |
5237 |
|
5238 |
<pre caption="Changing the root password"> |
5239 |
# <i>passwd</i> |
5240 |
New password: <comment>(Enter your new password)</comment> |
5241 |
Re-enter password: <comment>(Re-enter your password)</comment> |
5242 |
</pre> |
5243 |
|
5244 |
<p> |
5245 |
To create a user account, we first enter their credentials, followed by |
5246 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
5247 |
In the next example, we create a user called "john". |
5248 |
</p> |
5249 |
|
5250 |
<pre caption="Creating a user account"> |
5251 |
# <i>useradd -m -G users john</i> |
5252 |
# <i>passwd john</i> |
5253 |
New password: <comment>(Enter john's password)</comment> |
5254 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
5255 |
</pre> |
5256 |
|
5257 |
<p> |
5258 |
You can change your user id from root to the newly created user by using |
5259 |
<c>su</c>: |
5260 |
</p> |
5261 |
|
5262 |
<pre caption="Changing user id"> |
5263 |
# <i>su - john</i> |
5264 |
</pre> |
5265 |
|
5266 |
</body> |
5267 |
</subsection> |
5268 |
<subsection> |
5269 |
<title>Optional: Viewing Documentation while Installing</title> |
5270 |
<body> |
5271 |
|
5272 |
<p> |
5273 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
5274 |
installation, make sure you have created a user account (see <uri |
5275 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
5276 |
go to a new terminal and log in. |
5277 |
</p> |
5278 |
|
5279 |
<p> |
5280 |
If you want to view the documentation on the CD you can immediately run |
5281 |
<c>lynx</c> to read it: |
5282 |
</p> |
5283 |
|
5284 |
<pre caption="Viewing the on-CD documentation"> |
5285 |
# <i>lynx /mnt/cdrom/docs/html/index.html</i> |
5286 |
</pre> |
5287 |
|
5288 |
<p> |
5289 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
5290 |
more recent than the one provided on the CD. You can view it using <c>lynx</c> |
5291 |
as well, but only after having completed the <e>Configuring your Network</e> |
5292 |
chapter (otherwise you won't be able to go on the Internet to view the |
5293 |
document): |
5294 |
</p> |
5295 |
|
5296 |
<pre caption="Viewing the Online Documentation"> |
5297 |
# <i>lynx http://www.gentoo.org/doc/en/handbook/handbook-alpha.xml</i> |
5298 |
</pre> |
5299 |
|
5300 |
<p> |
5301 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
5302 |
</p> |
5303 |
|
5304 |
</body> |
5305 |
</subsection> |
5306 |
<subsection> |
5307 |
<title>Optional: Starting the SSH Daemon</title> |
5308 |
<body> |
5309 |
|
5310 |
<p> |
5311 |
If you want to allow other users to access your computer during the |
5312 |
Gentoo installation (perhaps because those users are going to help you |
5313 |
install Gentoo, or even do it for you), you need to create a user |
5314 |
account for them and perhaps even provide them with your root password |
5315 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
5316 |
</p> |
5317 |
|
5318 |
<p> |
5319 |
To fire up the SSH daemon, execute the following command: |
5320 |
</p> |
5321 |
|
5322 |
<pre caption="Starting the SSH daemon"> |
5323 |
# <i>/etc/init.d/sshd start</i> |
5324 |
</pre> |
5325 |
|
5326 |
<p> |
5327 |
To be able to use sshd, you first need to set up your networking. Continue with |
5328 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
5329 |
</p> |
5330 |
|
5331 |
</body> |
5332 |
</subsection> |
5333 |
</section> |
5334 |
</sections> |
5335 |
|
5336 |
|
5337 |
|
5338 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-amd64-bootloader.xml |
5339 |
|
5340 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-amd64-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
5341 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-amd64-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
5342 |
|
5343 |
Index: hb-install-amd64-bootloader.xml |
5344 |
=================================================================== |
5345 |
<?xml version='1.0' encoding='UTF-8'?> |
5346 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
5347 |
|
5348 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
5349 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
5350 |
|
5351 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-amd64-bootloader.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
5352 |
|
5353 |
<sections> |
5354 |
|
5355 |
<version>5.9</version> |
5356 |
<date>2006-02-02</date> |
5357 |
|
5358 |
<section> |
5359 |
<title>Making your Choice</title> |
5360 |
<subsection> |
5361 |
<title>Introduction</title> |
5362 |
<body> |
5363 |
|
5364 |
<p> |
5365 |
Now that your kernel is configured and compiled and the necessary system |
5366 |
configuration files are filled in correctly, it is time to install a |
5367 |
program that will fire up your kernel when you start the system. Such a |
5368 |
program is called a <e>bootloader</e>. |
5369 |
</p> |
5370 |
|
5371 |
</body> |
5372 |
</subsection> |
5373 |
<subsection> |
5374 |
<title>Optional: Framebuffer</title> |
5375 |
<body> |
5376 |
|
5377 |
<!-- |
5378 |
Verbatim copy from x86 bootloader framebuffer explanation, minus the section on |
5379 |
vesafb-tng |
5380 |
--> |
5381 |
|
5382 |
<p> |
5383 |
<e>If</e> you have configured your kernel with framebuffer support (or you used |
5384 |
<c>genkernel</c>'s default kernel configuration), you can activate it by adding |
5385 |
a <c>vga</c> and/or a <c>video</c> statement to your bootloader configuration |
5386 |
file. |
5387 |
</p> |
5388 |
|
5389 |
<p> |
5390 |
64-bit systems must use the the <c>vesafb</c> driver, and so will need to set |
5391 |
the <c>vga</c> statement. The <c>vga</c> statement controls the resolution and |
5392 |
color depth of your framebuffer screen for <c>vesafb</c>. As stated in |
5393 |
<path>/usr/src/linux/Documentation/fb/vesafb.txt</path> (which gets installed |
5394 |
when you install a kernel source package), you need to pass the VESA number |
5395 |
corresponding to the requested resolution and color depth to it. |
5396 |
</p> |
5397 |
|
5398 |
<p> |
5399 |
The following table lists the available resolutions and colordepths and matches |
5400 |
those against the value that you need to pass on to the <c>vga</c> statement. |
5401 |
</p> |
5402 |
|
5403 |
<table> |
5404 |
<tr> |
5405 |
<ti></ti> |
5406 |
<th>640x480</th> |
5407 |
<th>800x600</th> |
5408 |
<th>1024x768</th> |
5409 |
<th>1280x1024</th> |
5410 |
</tr> |
5411 |
<tr> |
5412 |
<th>256</th> |
5413 |
<ti>0x301</ti> |
5414 |
<ti>0x303</ti> |
5415 |
<ti>0x305</ti> |
5416 |
<ti>0x307</ti> |
5417 |
</tr> |
5418 |
<tr> |
5419 |
<th>32k</th> |
5420 |
<ti>0x310</ti> |
5421 |
<ti>0x313</ti> |
5422 |
<ti>0x316</ti> |
5423 |
<ti>0x319</ti> |
5424 |
</tr> |
5425 |
<tr> |
5426 |
<th>64k</th> |
5427 |
<ti>0x311</ti> |
5428 |
<ti>0x314</ti> |
5429 |
<ti>0x317</ti> |
5430 |
<ti>0x31A</ti> |
5431 |
</tr> |
5432 |
<tr> |
5433 |
<th>16M</th> |
5434 |
<ti>0x312</ti> |
5435 |
<ti>0x315</ti> |
5436 |
<ti>0x318</ti> |
5437 |
<ti>0x31B</ti> |
5438 |
</tr> |
5439 |
</table> |
5440 |
|
5441 |
<p> |
5442 |
The <c>video</c> statement controls framebuffer display options. It needs to be |
5443 |
given the framebuffer driver (<c>vesafb</c> for 2.6 kernels, or <c>vesa</c> for |
5444 |
2.4 kernels) followed by the control statements you wish to enable. All |
5445 |
variables are listed in <path>/usr/src/linux/Documentation/fb/vesafb.txt</path>, |
5446 |
but we'll inform you about three most-used options: |
5447 |
</p> |
5448 |
|
5449 |
<table> |
5450 |
<tr> |
5451 |
<th>Control</th> |
5452 |
<th>Description</th> |
5453 |
</tr> |
5454 |
<tr> |
5455 |
<ti>ywrap</ti> |
5456 |
<ti> |
5457 |
Assume that the graphical card can wrap around its memory (i.e. continue at |
5458 |
the beginning when it has approached the end) |
5459 |
</ti> |
5460 |
</tr> |
5461 |
<tr> |
5462 |
<ti>mtrr</ti> |
5463 |
<ti> |
5464 |
Setup MTRR registers |
5465 |
</ti> |
5466 |
</tr> |
5467 |
</table> |
5468 |
|
5469 |
<p> |
5470 |
The result of those two statements could be something like <c>vga=0x318 |
5471 |
video=vesafb:mtrr,ywrap</c> or <c>video=vesafb:mtrr,ywrap,1024x768-32@85</c>. |
5472 |
Remember (or write down) this setting; you will need it shortly. |
5473 |
</p> |
5474 |
|
5475 |
<p> |
5476 |
While LILO does work on AMD64, Gentoo only supports using GRUB. Now continue by |
5477 |
its installation. |
5478 |
</p> |
5479 |
|
5480 |
</body> |
5481 |
</subsection> |
5482 |
</section> |
5483 |
<section> |
5484 |
<title>Using GRUB</title> |
5485 |
<subsection> |
5486 |
<title>Understanding GRUB's terminology</title> |
5487 |
<body> |
5488 |
|
5489 |
<p> |
5490 |
The most critical part of understanding GRUB is getting comfortable with |
5491 |
how GRUB refers to hard drives and partitions. Your Linux partition |
5492 |
<path>/dev/hda1</path> will most likely be called <path>(hd0,0)</path> under |
5493 |
GRUB. Notice the parenthesis around the <path>hd0,0</path> - they are required. |
5494 |
</p> |
5495 |
|
5496 |
<p> |
5497 |
Hard drives count from zero rather than "a" and partitions start at zero |
5498 |
rather than one. Be aware too that with the hd devices, only hard drives are |
5499 |
counted, not atapi-ide devices such as cdrom players and burners. Also, the |
5500 |
same construct is used with SCSI drives. (Normally they get higher numbers |
5501 |
than IDE drives except when the BIOS is configured to boot from SCSI devices.) |
5502 |
When you ask the BIOS to boot from a different hard disk (for instance your |
5503 |
primary slave), <e>that</e> harddisk is seen as <path>hd0</path>. |
5504 |
</p> |
5505 |
|
5506 |
<p> |
5507 |
Assuming you have a hard drive on <path>/dev/hda</path>, a cdrom player on |
5508 |
<path>/dev/hdb</path>, a burner on <path>/dev/hdc</path>, a second hard drive |
5509 |
on <path>/dev/hdd</path> and no SCSI hard drive, <path>/dev/hdd7</path> gets |
5510 |
translated to <path>(hd1,6)</path>. It might sound tricky and tricky it is |
5511 |
indeed, but as we will see, GRUB offers a tab completion mechanism |
5512 |
that comes handy for those of you having a lot of hard drives and |
5513 |
partitions and who are a little lost in the GRUB numbering scheme. |
5514 |
</p> |
5515 |
|
5516 |
<p> |
5517 |
Having gotten the feel for that, it is time to install GRUB. |
5518 |
</p> |
5519 |
|
5520 |
</body> |
5521 |
</subsection> |
5522 |
<subsection> |
5523 |
<title>Installing GRUB</title> |
5524 |
<body> |
5525 |
|
5526 |
<p> |
5527 |
To install GRUB, let's first emerge it. |
5528 |
</p> |
5529 |
|
5530 |
<pre caption="Installing GRUB"> |
5531 |
# <i>emerge grub</i> |
5532 |
</pre> |
5533 |
|
5534 |
<p> |
5535 |
Although GRUB is now installed, we still need to write up a |
5536 |
configuration file for it and install GRUB in the MBR so that GRUB |
5537 |
automatically boots your newly created kernel. Create |
5538 |
<path>/boot/grub/grub.conf</path> with <c>nano</c> (or, if applicable, another |
5539 |
editor): |
5540 |
</p> |
5541 |
|
5542 |
<pre caption="Creating /boot/grub/grub.conf"> |
5543 |
# <i>nano -w /boot/grub/grub.conf</i> |
5544 |
</pre> |
5545 |
|
5546 |
<p> |
5547 |
Now we are going to write up a <path>grub.conf</path>. Below you'll |
5548 |
find two possible <path>grub.conf</path> for the partitioning example we use |
5549 |
in this guide, with kernel image <path>kernel-2.6.12-gentoo-r10</path>. We've |
5550 |
only extensively commented the first <path>grub.conf</path>. |
5551 |
</p> |
5552 |
|
5553 |
<ul> |
5554 |
<li> |
5555 |
The first <path>grub.conf</path> is for people who have not used |
5556 |
<c>genkernel</c> to build their kernel |
5557 |
</li> |
5558 |
<li> |
5559 |
The second <path>grub.conf</path> is for people who have used |
5560 |
<c>genkernel</c> to build their kernel |
5561 |
</li> |
5562 |
</ul> |
5563 |
|
5564 |
<note> |
5565 |
If your root filesystem is JFS, you <e>must</e> add " ro" to the <c>kernel</c> |
5566 |
line since JFS needs to replay its log before it allows read-write mounting. |
5567 |
</note> |
5568 |
|
5569 |
<pre caption="grub.conf for non-genkernel users"> |
5570 |
<comment># Which listing to boot as default. 0 is the first, 1 the second etc.</comment> |
5571 |
default 0 |
5572 |
<comment># How many seconds to wait before the default listing is booted.</comment> |
5573 |
timeout 30 |
5574 |
<comment># Nice, fat splash-image to spice things up :) |
5575 |
# Comment out if you don't have a graphics card installed</comment> |
5576 |
splashimage=(hd0,0)/boot/grub/splash.xpm.gz |
5577 |
|
5578 |
title=Gentoo Linux 2.6.12 |
5579 |
<comment># Partition where the kernel image (or operating system) is located</comment> |
5580 |
root (hd0,0) |
5581 |
kernel /boot/kernel-2.6.12-gentoo-r10 root=/dev/hda3 |
5582 |
|
5583 |
<comment># The next four lines are only if you dualboot with a Windows system.</comment> |
5584 |
<comment># In this case, Windows is hosted on /dev/hda6.</comment> |
5585 |
title=Windows XP |
5586 |
rootnoverify (hd0,5) |
5587 |
makeactive |
5588 |
chainloader +1 |
5589 |
</pre> |
5590 |
|
5591 |
<pre caption="grub.conf for genkernel users"> |
5592 |
default 0 |
5593 |
timeout 30 |
5594 |
splashimage=(hd0,0)/boot/grub/splash.xpm.gz |
5595 |
|
5596 |
title=Gentoo Linux 2.6.12 |
5597 |
root (hd0,0) |
5598 |
kernel /boot/kernel-2.6.12-gentoo-r10 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 udev |
5599 |
initrd /boot/initramfs-genkernel-amd64-2.6.12-gentoo-r10 |
5600 |
|
5601 |
<comment># Only in case you want to dual-boot</comment> |
5602 |
title=Windows XP |
5603 |
rootnoverify (hd0,5) |
5604 |
makeactive |
5605 |
chainloader +1 |
5606 |
</pre> |
5607 |
|
5608 |
<p> |
5609 |
If you used a different partitioning scheme and/or kernel image, adjust |
5610 |
accordingly. However, make sure that anything that follows a GRUB-device (such |
5611 |
as <path>(hd0,0)</path>) is relative to the mountpoint, not the root. In other |
5612 |
words, <path>(hd0,0)/grub/splash.xpm.gz</path> is in reality |
5613 |
<path>/boot/grub/splash.xpm.gz</path> since <path>(hd0,0)</path> is |
5614 |
<path>/boot</path>. |
5615 |
</p> |
5616 |
|
5617 |
<p> |
5618 |
Besides, if you chose to use a different partitioning scheme and did not put |
5619 |
<path>/boot</path> in a separate partition, the <path>/boot</path> prefix used |
5620 |
in the above code samples is really <e>required</e>. If you followed our |
5621 |
suggested partitioning plan, the <path>/boot</path> prefix it not required, but |
5622 |
a <path>boot</path> symlink makes it work. In short, the above examples should |
5623 |
work whether you defined a separate <path>/boot</path> partition or not. |
5624 |
</p> |
5625 |
|
5626 |
<p> |
5627 |
If you need to pass any additional options to the kernel, simply add |
5628 |
them to the end of the kernel command. We're already passing one option |
5629 |
(<c>root=/dev/hda3</c> or <c>real_root=/dev/hda3</c>), but you can pass others |
5630 |
as well, such as the <c>video</c> statement for framebuffer as we discussed |
5631 |
previously. |
5632 |
</p> |
5633 |
|
5634 |
<p> |
5635 |
<c>genkernel</c> users should know that their kernels use the same boot options |
5636 |
as is used for the Installation CD. For instance, if you have SCSI devices, you |
5637 |
should add <c>doscsi</c> as kernel option. |
5638 |
</p> |
5639 |
|
5640 |
<p> |
5641 |
Now save the <path>grub.conf</path> file and exit. We still need to install GRUB |
5642 |
in the MBR (Master Boot Record) though. |
5643 |
</p> |
5644 |
|
5645 |
<p> |
5646 |
The GRUB developers recommend the use of <c>grub-install</c>. However, if for |
5647 |
some reason <c>grub-install</c> fails to work correctly you still have the |
5648 |
option to manually install GRUB. |
5649 |
</p> |
5650 |
|
5651 |
<p> |
5652 |
Continue with <uri link="#grub-install-auto">Default: Setting up GRUB using |
5653 |
grub-install</uri> or <uri link="#grub-install-manual">Alternative: Setting up |
5654 |
GRUB using manual instructions</uri>. |
5655 |
</p> |
5656 |
|
5657 |
</body> |
5658 |
</subsection> |
5659 |
<subsection id="grub-install-auto"> |
5660 |
<title>Default: Setting up GRUB using grub-install</title> |
5661 |
<body> |
5662 |
|
5663 |
<p> |
5664 |
To install GRUB you will need to issue the <c>grub-install</c> command. |
5665 |
However, <c>grub-install</c> won't work off-the-shelf since we are inside a |
5666 |
chrooted environment. We need to create <path>/etc/mtab</path> which lists all |
5667 |
mounted filesystems. Fortunately, there is an easy way to accomplish this - |
5668 |
just copy over <path>/proc/mounts</path> to <path>/etc/mtab</path>, excluding |
5669 |
the <c>rootfs</c> line if you haven't created a separate boot partition. The |
5670 |
following command will work in both cases: |
5671 |
</p> |
5672 |
|
5673 |
<pre caption="Creating /etc/mtab"> |
5674 |
# <i>grep -v rootfs /proc/mounts > /etc/mtab</i> |
5675 |
</pre> |
5676 |
|
5677 |
<p> |
5678 |
Now we can install GRUB using <c>grub-install</c>: |
5679 |
</p> |
5680 |
|
5681 |
<pre caption="Running grub-install"> |
5682 |
# <i>grub-install /dev/hda</i> |
5683 |
</pre> |
5684 |
|
5685 |
<p> |
5686 |
If you have more questions regarding GRUB, please consult the <uri |
5687 |
link="http://www.gnu.org/software/grub/grub-faq.html">GRUB FAQ</uri> or the <uri |
5688 |
link="http://www.gnu.org/software/grub/manual/">GRUB Manual</uri>. |
5689 |
</p> |
5690 |
|
5691 |
<p> |
5692 |
Continue with <uri link="#reboot">Rebooting the System</uri>. |
5693 |
</p> |
5694 |
|
5695 |
</body> |
5696 |
</subsection> |
5697 |
<subsection id="grub-install-manual"> |
5698 |
<title>Alternative: Setting up GRUB using manual instructions</title> |
5699 |
<body> |
5700 |
|
5701 |
<p> |
5702 |
To start configuring GRUB, you type in <c>grub</c>. You'll be presented |
5703 |
with the <path>grub></path> grub command-line prompt. Now, you need to type |
5704 |
in the right commands to install the GRUB boot record onto your hard drive. |
5705 |
</p> |
5706 |
|
5707 |
<pre caption=" Starting the GRUB shell"> |
5708 |
# <i>grub</i> |
5709 |
</pre> |
5710 |
|
5711 |
<note> |
5712 |
If your system does not have any floppy drives, add the <c>--no-floppy</c> |
5713 |
option to the above command to prevent grub from probing the (non-existing) |
5714 |
floppy drives. |
5715 |
</note> |
5716 |
|
5717 |
<p> |
5718 |
In the example configuration we want to install GRUB so that it reads its |
5719 |
information from the boot-partition <path>/dev/hda1</path>, and installs the |
5720 |
GRUB boot record on the hard drive's MBR (master boot record) so that the first |
5721 |
thing we see when we turn on the computer is the GRUB prompt. Of course, if you |
5722 |
haven't followed the example configuration during the installation, |
5723 |
change the commands accordingly. |
5724 |
</p> |
5725 |
|
5726 |
<p> |
5727 |
The tab completion mechanism of GRUB can be used from within GRUB. |
5728 |
For instance, if you type in "<c>root (</c>" followed by a TAB, you will |
5729 |
be presented with a list of devices (such as <path>hd0</path>). If you |
5730 |
type in "<c>root (hd0,</c>" followed by a TAB, you will receive a list |
5731 |
of available partitions to choose from (such as <path>hd0,0</path>). |
5732 |
</p> |
5733 |
|
5734 |
<p> |
5735 |
By using the tab completion, setting up GRUB should be not that hard. |
5736 |
Now go on, configure GRUB, shall we? :-) |
5737 |
</p> |
5738 |
|
5739 |
<pre caption=" Installing GRUB in the MBR"> |
5740 |
grub> <i>root (hd0,0)</i> <comment>(Specify where your /boot partition resides)</comment> |
5741 |
grub> <i>setup (hd0)</i> <comment>(Install GRUB in the MBR)</comment> |
5742 |
grub> <i>quit</i> <comment>(Exit the GRUB shell)</comment> |
5743 |
</pre> |
5744 |
|
5745 |
<note> |
5746 |
If you want to install GRUB in a certain partition instead of the MBR, |
5747 |
you have to alter the <c>setup</c> command so it points to the right |
5748 |
partition. For instance, if you want GRUB installed in |
5749 |
<path>/dev/hda3</path>, then the command becomes <c>setup (hd0,2)</c>. |
5750 |
Few users however want to do this. |
5751 |
</note> |
5752 |
|
5753 |
<p> |
5754 |
If you have more questions regarding GRUB, please consult the <uri |
5755 |
link="http://www.gnu.org/software/grub/grub-faq.html">GRUB FAQ</uri> or the <uri |
5756 |
link="http://www.gnu.org/software/grub/manual/">GRUB Manual</uri>. |
5757 |
</p> |
5758 |
|
5759 |
<p> |
5760 |
Continue with <uri link="#reboot">Rebooting the System</uri>. |
5761 |
</p> |
5762 |
|
5763 |
</body> |
5764 |
</subsection> |
5765 |
</section> |
5766 |
<section id="reboot"> |
5767 |
<title>Rebooting the System</title> |
5768 |
<subsection> |
5769 |
<body> |
5770 |
|
5771 |
<p> |
5772 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
5773 |
that one magical command you have been waiting for: <c>reboot</c>. |
5774 |
</p> |
5775 |
|
5776 |
<pre caption="Unmounting all partitions and rebooting"> |
5777 |
# <i>exit</i> |
5778 |
# <i>cd</i> |
5779 |
# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
5780 |
# <i>reboot</i> |
5781 |
</pre> |
5782 |
|
5783 |
<p> |
5784 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
5785 |
booted again instead of your new Gentoo system. |
5786 |
</p> |
5787 |
|
5788 |
<p> |
5789 |
Once rebooted in your Gentoo installation, finish up with <uri |
5790 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
5791 |
</p> |
5792 |
|
5793 |
</body> |
5794 |
</subsection> |
5795 |
</section> |
5796 |
</sections> |
5797 |
|
5798 |
|
5799 |
|
5800 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-amd64-disk.xml |
5801 |
|
5802 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-amd64-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
5803 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-amd64-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
5804 |
|
5805 |
Index: hb-install-amd64-disk.xml |
5806 |
=================================================================== |
5807 |
<?xml version='1.0' encoding='UTF-8'?> |
5808 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
5809 |
|
5810 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
5811 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
5812 |
|
5813 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-amd64-disk.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
5814 |
|
5815 |
<sections> |
5816 |
|
5817 |
<version>5.2</version> |
5818 |
<date>2006-01-01</date> |
5819 |
|
5820 |
<section> |
5821 |
<title>Introduction to Block Devices</title> |
5822 |
<subsection> |
5823 |
<title>Block Devices</title> |
5824 |
<body> |
5825 |
|
5826 |
<p> |
5827 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
5828 |
and Linux in general, including Linux filesystems, partitions and block devices. |
5829 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
5830 |
you'll be guided through the process of setting up partitions and filesystems |
5831 |
for your Gentoo Linux installation. |
5832 |
</p> |
5833 |
|
5834 |
<p> |
5835 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
5836 |
probably the one that represents the first IDE drive in a Linux system, namely |
5837 |
<path>/dev/hda</path>. If your system uses SCSI drives, then your first hard |
5838 |
drive would be <path>/dev/sda</path>. |
5839 |
</p> |
5840 |
|
5841 |
<p> |
5842 |
The block devices above represent an abstract interface to the disk. User |
5843 |
programs can use these block devices to interact with your disk without worrying |
5844 |
about whether your drives are IDE, SCSI or something else. The program can |
5845 |
simply address the storage on the disk as a bunch of contiguous, |
5846 |
randomly-accessible 512-byte blocks. |
5847 |
</p> |
5848 |
|
5849 |
</body> |
5850 |
</subsection> |
5851 |
<subsection> |
5852 |
<title>Partitions and Slices</title> |
5853 |
<body> |
5854 |
|
5855 |
<p> |
5856 |
Although it is theoretically possible to use a full disk to house your Linux |
5857 |
system, this is almost never done in practice. Instead, full disk block devices |
5858 |
are split up in smaller, more manageable block devices. On amd64 systems, |
5859 |
these are called <e>partitions</e>. |
5860 |
</p> |
5861 |
|
5862 |
</body> |
5863 |
</subsection> |
5864 |
<subsection> |
5865 |
<title>Partitions</title> |
5866 |
<body> |
5867 |
|
5868 |
<p> |
5869 |
Partitions are divided in three types: |
5870 |
<e>primary</e>, <e>extended</e> and <e>logical</e>. |
5871 |
</p> |
5872 |
|
5873 |
<p> |
5874 |
A <e>primary</e> partition is a partition which has its information stored in |
5875 |
the MBR (master boot record). As an MBR is very small (512 bytes) only four |
5876 |
primary partitions can be defined (for instance, <path>/dev/hda1</path> to |
5877 |
<path>/dev/hda4</path>). |
5878 |
</p> |
5879 |
|
5880 |
<p> |
5881 |
An <e>extended</e> partition is a special primary partition (meaning the |
5882 |
extended partition must be one of the four possible primary partitions) which |
5883 |
contains more partitions. Such a partition didn't exist originally, but as |
5884 |
four partitions were too few, it was brought to life to extend the formatting |
5885 |
scheme without losing backward compatibility. |
5886 |
</p> |
5887 |
|
5888 |
<p> |
5889 |
A <e>logical</e> partition is a partition inside the extended partition. Their |
5890 |
definitions aren't placed inside the MBR, but are declared inside the extended |
5891 |
partition. |
5892 |
</p> |
5893 |
|
5894 |
</body> |
5895 |
</subsection> |
5896 |
</section> |
5897 |
<section> |
5898 |
<title>Designing a Partitioning Scheme</title> |
5899 |
<subsection> |
5900 |
<title>Default Partitioning Scheme</title> |
5901 |
<body> |
5902 |
|
5903 |
<p> |
5904 |
If you are not interested in drawing up a partitioning scheme for your system, |
5905 |
you can use the partitioning scheme we use throughout this book: |
5906 |
</p> |
5907 |
|
5908 |
<table> |
5909 |
<tr> |
5910 |
<th>Partition</th> |
5911 |
<th>Filesystem</th> |
5912 |
<th>Size</th> |
5913 |
<th>Description</th> |
5914 |
</tr> |
5915 |
<tr> |
5916 |
<ti><path>/dev/hda1</path></ti> |
5917 |
<ti>ext2</ti> |
5918 |
<ti>32M</ti> |
5919 |
<ti>Boot partition</ti> |
5920 |
</tr> |
5921 |
<tr> |
5922 |
<ti><path>/dev/hda2</path></ti> |
5923 |
<ti>(swap)</ti> |
5924 |
<ti>512M</ti> |
5925 |
<ti>Swap partition</ti> |
5926 |
</tr> |
5927 |
<tr> |
5928 |
<ti><path>/dev/hda3</path></ti> |
5929 |
<ti>ext3</ti> |
5930 |
<ti>Rest of the disk</ti> |
5931 |
<ti>Root partition</ti> |
5932 |
</tr> |
5933 |
</table> |
5934 |
|
5935 |
<p> |
5936 |
If you are interested in knowing how big a partition (or logical |
5937 |
volume) should be, or even how many partitions (or volumes) you need, read on. |
5938 |
Otherwise continue with <uri link="#fdisk">Using fdisk to Partition your |
5939 |
Disk</uri>. |
5940 |
</p> |
5941 |
|
5942 |
</body> |
5943 |
</subsection> |
5944 |
<subsection> |
5945 |
<title>How Many and How Big?</title> |
5946 |
<body> |
5947 |
|
5948 |
<p> |
5949 |
The number of partitions is highly dependent on your environment. For instance, |
5950 |
if you have lots of users, you will most likely want to have your |
5951 |
<path>/home</path> separate as it increases security and makes backups easier. |
5952 |
If you are installing Gentoo to perform as a mailserver, your |
5953 |
<path>/var</path> should be separate as all mails are stored inside |
5954 |
<path>/var</path>. A good choice of filesystem will then maximise your |
5955 |
performance. Gameservers will have a separate <path>/opt</path> as most gaming |
5956 |
servers are installed there. The reason is similar for <path>/home</path>: |
5957 |
security and backups. You will definitely want to keep <path>/usr</path> big: |
5958 |
not only will it contain the majority of applications, the Portage tree alone |
5959 |
takes around 500 Mbyte excluding the various sources that are stored in it. |
5960 |
</p> |
5961 |
|
5962 |
<p> |
5963 |
As you can see, it very much depends on what you want to achieve. Separate |
5964 |
partitions or volumes have the following advantages: |
5965 |
</p> |
5966 |
|
5967 |
<ul> |
5968 |
<li> |
5969 |
You can choose the best performing filesystem for each partition or volume |
5970 |
</li> |
5971 |
<li> |
5972 |
Your entire system cannot run out of free space if one defunct tool is |
5973 |
continuously writing files to a partition or volume |
5974 |
</li> |
5975 |
<li> |
5976 |
If necessary, file system checks are reduced in time, as multiple checks can |
5977 |
be done in parallel (although this advantage is more with multiple disks than |
5978 |
it is with multiple partitions) |
5979 |
</li> |
5980 |
<li> |
5981 |
Security can be enhanced by mounting some partitions or volumes read-only, |
5982 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
5983 |
</li> |
5984 |
</ul> |
5985 |
|
5986 |
<p> |
5987 |
However, multiple partitions have one big disadvantage: if not configured |
5988 |
properly, you might result in having a system with lots |
5989 |
of free space on one partition and none on another. There is also a 15-partition |
5990 |
limit for SCSI and SATA. |
5991 |
</p> |
5992 |
|
5993 |
<p> |
5994 |
As an example partitioning, we show you one for a 20GB disk, used as a |
5995 |
demonstration laptop (containing webserver, mailserver, gnome, ...): |
5996 |
</p> |
5997 |
|
5998 |
<pre caption="Filesystem usage example"> |
5999 |
Filesystem Type Size Used Avail Use% Mounted on |
6000 |
/dev/hda5 ext3 509M 132M 351M 28% / |
6001 |
/dev/hda2 ext3 5.0G 3.0G 1.8G 63% /home |
6002 |
/dev/hda7 ext3 7.9G 6.2G 1.3G 83% /usr |
6003 |
/dev/hda8 ext3 1011M 483M 477M 51% /opt |
6004 |
/dev/hda9 ext3 2.0G 607M 1.3G 32% /var |
6005 |
/dev/hda1 ext2 51M 17M 31M 36% /boot |
6006 |
/dev/hda6 swap 516M 12M 504M 2% <not mounted> |
6007 |
<comment>(Unpartitioned space for future usage: 2 GB)</comment> |
6008 |
</pre> |
6009 |
|
6010 |
<p> |
6011 |
<path>/usr</path> is rather full (83% used) here, but once |
6012 |
all software is installed, <path>/usr</path> doesn't tend to grow that much. |
6013 |
Although allocating a few gigabytes of disk space for <path>/var</path> may |
6014 |
seem excessive, remember that Portage uses this partition by default for |
6015 |
compiling packages. If you want to keep <path>/var</path> at a more reasonable |
6016 |
size, such as 1GB, you will need to alter your <c>PORTAGE_TMPDIR</c> variable |
6017 |
in <path>/etc/make.conf</path> to point to the partition with enough free space |
6018 |
for compiling extremely large packages such as OpenOffice. |
6019 |
</p> |
6020 |
|
6021 |
</body> |
6022 |
</subsection> |
6023 |
</section> |
6024 |
<section id="fdisk"> |
6025 |
<title>Using fdisk to Partition your Disk</title> |
6026 |
<subsection> |
6027 |
<body> |
6028 |
|
6029 |
<p> |
6030 |
The following parts explain how to create the example partition layout |
6031 |
described previously, namely: |
6032 |
</p> |
6033 |
|
6034 |
<table> |
6035 |
<tr> |
6036 |
<th>Partition</th> |
6037 |
<th>Description</th> |
6038 |
</tr> |
6039 |
<tr> |
6040 |
<ti><path>/dev/hda1</path></ti> |
6041 |
<ti>Boot partition</ti> |
6042 |
</tr> |
6043 |
<tr> |
6044 |
<ti><path>/dev/hda2</path></ti> |
6045 |
<ti>Swap partition</ti> |
6046 |
</tr> |
6047 |
<tr> |
6048 |
<ti><path>/dev/hda3</path></ti> |
6049 |
<ti>Root partition</ti> |
6050 |
</tr> |
6051 |
</table> |
6052 |
|
6053 |
<p> |
6054 |
Change your partition layout according to your own preference. |
6055 |
</p> |
6056 |
|
6057 |
</body> |
6058 |
</subsection> |
6059 |
<subsection> |
6060 |
<title>Viewing the Current Partition Layout</title> |
6061 |
<body> |
6062 |
|
6063 |
<p> |
6064 |
<c>fdisk</c> is a popular and powerful tool to split your disk into partitions. |
6065 |
Fire up <c>fdisk</c> on your disk (in our example, we use |
6066 |
<path>/dev/hda</path>): |
6067 |
</p> |
6068 |
|
6069 |
<pre caption="Starting fdisk"> |
6070 |
# <i>fdisk /dev/hda</i> |
6071 |
</pre> |
6072 |
|
6073 |
<p> |
6074 |
Once in <c>fdisk</c>, you'll be greeted with a prompt that looks like this: |
6075 |
</p> |
6076 |
|
6077 |
<pre caption="fdisk prompt"> |
6078 |
Command (m for help): |
6079 |
</pre> |
6080 |
|
6081 |
<p> |
6082 |
Type <c>p</c> to display your disk's current partition configuration: |
6083 |
</p> |
6084 |
|
6085 |
<pre caption="An example partition configuration"> |
6086 |
Command (m for help): <i>p</i> |
6087 |
|
6088 |
Disk /dev/hda: 240 heads, 63 sectors, 2184 cylinders |
6089 |
Units = cylinders of 15120 * 512 bytes |
6090 |
|
6091 |
Device Boot Start End Blocks Id System |
6092 |
/dev/hda1 1 14 105808+ 83 Linux |
6093 |
/dev/hda2 15 49 264600 82 Linux swap |
6094 |
/dev/hda3 50 70 158760 83 Linux |
6095 |
/dev/hda4 71 2184 15981840 5 Extended |
6096 |
/dev/hda5 71 209 1050808+ 83 Linux |
6097 |
/dev/hda6 210 348 1050808+ 83 Linux |
6098 |
/dev/hda7 349 626 2101648+ 83 Linux |
6099 |
/dev/hda8 627 904 2101648+ 83 Linux |
6100 |
/dev/hda9 905 2184 9676768+ 83 Linux |
6101 |
|
6102 |
Command (m for help): |
6103 |
</pre> |
6104 |
|
6105 |
<p> |
6106 |
This particular disk is configured to house seven Linux filesystems (each with a |
6107 |
corresponding partition listed as "Linux") as well as a swap partition (listed |
6108 |
as "Linux swap"). |
6109 |
</p> |
6110 |
|
6111 |
</body> |
6112 |
</subsection> |
6113 |
<subsection> |
6114 |
<title>Removing all Partitions</title> |
6115 |
<body> |
6116 |
|
6117 |
<p> |
6118 |
We will first remove all existing partitions from the disk. Type <c>d</c> to |
6119 |
delete a partition. For instance, to delete an existing <path>/dev/hda1</path>: |
6120 |
</p> |
6121 |
|
6122 |
<pre caption="Deleting a partition"> |
6123 |
Command (m for help): <i>d</i> |
6124 |
Partition number (1-4): <i>1</i> |
6125 |
</pre> |
6126 |
|
6127 |
<p> |
6128 |
The partition has been scheduled for deletion. It will no longer show up if you |
6129 |
type <c>p</c>, but it will not be erased until your changes have been saved. If |
6130 |
you made a mistake and want to abort without saving your changes, type <c>q</c> |
6131 |
immediately and hit enter and your partition will not be deleted. |
6132 |
</p> |
6133 |
|
6134 |
<p> |
6135 |
Now, assuming that you do indeed want to wipe out all the partitions on your |
6136 |
system, repeatedly type <c>p</c> to print out a partition listing and then type |
6137 |
<c>d</c> and the number of the partition to delete it. Eventually, you'll end |
6138 |
up with a partition table with nothing in it: |
6139 |
</p> |
6140 |
|
6141 |
<pre caption="An empty partition table"> |
6142 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
6143 |
240 heads, 63 sectors/track, 3876 cylinders |
6144 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
6145 |
|
6146 |
Device Boot Start End Blocks Id System |
6147 |
|
6148 |
Command (m for help): |
6149 |
</pre> |
6150 |
|
6151 |
<p> |
6152 |
Now that the in-memory partition table is empty, we're ready to create the |
6153 |
partitions. We will use a default partitioning scheme as discussed previously. |
6154 |
Of course, don't follow these instructions to the letter if you don't want the |
6155 |
same partitioning scheme! |
6156 |
</p> |
6157 |
|
6158 |
</body> |
6159 |
</subsection> |
6160 |
<subsection> |
6161 |
<title>Creating the Boot Partition</title> |
6162 |
<body> |
6163 |
|
6164 |
<p> |
6165 |
We first create a small boot partition. Type <c>n</c> to create a new partition, |
6166 |
then <c>p</c> to select a primary partition, followed by <c>1</c> to select the |
6167 |
first primary partition. When prompted for the first cylinder, hit enter. When |
6168 |
prompted for the last cylinder, type <c>+32M</c> to create a partition 32 Mbyte |
6169 |
in size: |
6170 |
</p> |
6171 |
|
6172 |
<pre caption="Creating the boot partition"> |
6173 |
Command (m for help): <i>n</i> |
6174 |
Command action |
6175 |
e extended |
6176 |
p primary partition (1-4) |
6177 |
<i>p</i> |
6178 |
Partition number (1-4): <i>1</i> |
6179 |
First cylinder (1-3876, default 1): <comment>(Hit Enter)</comment> |
6180 |
Using default value 1 |
6181 |
Last cylinder or +size or +sizeM or +sizeK (1-3876, default 3876): <i>+32M</i> |
6182 |
</pre> |
6183 |
|
6184 |
<p> |
6185 |
Now, when you type <c>p</c>, you should see the following partition printout: |
6186 |
</p> |
6187 |
|
6188 |
<pre caption="Created boot partition"> |
6189 |
Command (m for help): <i>p</i> |
6190 |
|
6191 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
6192 |
240 heads, 63 sectors/track, 3876 cylinders |
6193 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
6194 |
|
6195 |
Device Boot Start End Blocks Id System |
6196 |
/dev/hda1 1 14 105808+ 83 Linux |
6197 |
</pre> |
6198 |
|
6199 |
<p> |
6200 |
We need to make this partition bootable. Type <c>a</c> to toggle the bootable |
6201 |
flag on a partition and select <c>1</c>. If you press <c>p</c> again, you will |
6202 |
notice that an <path>*</path> is placed in the "Boot" column. |
6203 |
</p> |
6204 |
|
6205 |
</body> |
6206 |
</subsection> |
6207 |
<subsection> |
6208 |
<title>Creating the Swap Partition</title> |
6209 |
<body> |
6210 |
|
6211 |
<p> |
6212 |
Let's now create the swap partition. To do this, type <c>n</c> to create a new |
6213 |
partition, then <c>p</c> to tell fdisk that you want a primary partition. Then |
6214 |
type <c>2</c> to create the second primary partition, <path>/dev/hda2</path> in |
6215 |
our case. When prompted for the first cylinder, hit enter. When prompted for |
6216 |
the last cylinder, type <c>+512M</c> to create a partition 512MB in size. After |
6217 |
you've done this, type <c>t</c> to set the partition type, <c>2</c> to select |
6218 |
the partition you just created and then type in <c>82</c> to set the partition |
6219 |
type to "Linux Swap". After completing these steps, typing <c>p</c> should |
6220 |
display a partition table that looks similar to this: |
6221 |
</p> |
6222 |
|
6223 |
<pre caption="Partition listing after creating a swap partition"> |
6224 |
Command (m for help): <i>p</i> |
6225 |
|
6226 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
6227 |
240 heads, 63 sectors/track, 3876 cylinders |
6228 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
6229 |
|
6230 |
Device Boot Start End Blocks Id System |
6231 |
/dev/hda1 * 1 14 105808+ 83 Linux |
6232 |
/dev/hda2 15 81 506520 82 Linux swap |
6233 |
</pre> |
6234 |
|
6235 |
</body> |
6236 |
</subsection> |
6237 |
<subsection> |
6238 |
<title>Creating the Root Partition</title> |
6239 |
<body> |
6240 |
|
6241 |
<p> |
6242 |
Finally, let's create the root partition. To do this, type <c>n</c> to create a |
6243 |
new partition, then <c>p</c> to tell fdisk that you want a primary partition. |
6244 |
Then type <c>3</c> to create the third primary partition, <path>/dev/hda3</path> |
6245 |
in our case. When prompted for the first cylinder, hit enter. When prompted for |
6246 |
the last cylinder, hit enter to create a partition that takes up the rest of the |
6247 |
remaining space on your disk. After completing these steps, typing <c>p</c> |
6248 |
should display a partition table that looks similar to this: |
6249 |
</p> |
6250 |
|
6251 |
<pre caption="Partition listing after creating the root partition"> |
6252 |
Command (m for help): <i>p</i> |
6253 |
|
6254 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
6255 |
240 heads, 63 sectors/track, 3876 cylinders |
6256 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
6257 |
|
6258 |
Device Boot Start End Blocks Id System |
6259 |
/dev/hda1 * 1 14 105808+ 83 Linux |
6260 |
/dev/hda2 15 81 506520 82 Linux swap |
6261 |
/dev/hda3 82 3876 28690200 83 Linux |
6262 |
</pre> |
6263 |
|
6264 |
|
6265 |
</body> |
6266 |
</subsection> |
6267 |
<subsection> |
6268 |
<title>Saving the Partition Layout</title> |
6269 |
<body> |
6270 |
|
6271 |
<p> |
6272 |
To save the partition layout and exit <c>fdisk</c>, type <c>w</c>. |
6273 |
</p> |
6274 |
|
6275 |
<pre caption="Save and exit fdisk"> |
6276 |
Command (m for help): <i>w</i> |
6277 |
</pre> |
6278 |
|
6279 |
<p> |
6280 |
Now that your partitions are created, you can now continue with <uri |
6281 |
link="#filesystems">Creating Filesystems</uri>. |
6282 |
</p> |
6283 |
|
6284 |
</body> |
6285 |
</subsection> |
6286 |
</section> |
6287 |
<section id="filesystems"> |
6288 |
<title>Creating Filesystems</title> |
6289 |
<subsection> |
6290 |
<title>Introduction</title> |
6291 |
<body> |
6292 |
|
6293 |
<p> |
6294 |
Now that your partitions are created, it is time to place a filesystem on them. |
6295 |
If you don't care about what filesystem to choose and are happy with what we use |
6296 |
as default in this handbook, continue with <uri |
6297 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
6298 |
Otherwise read on to learn about the available filesystems... |
6299 |
</p> |
6300 |
|
6301 |
</body> |
6302 |
</subsection> |
6303 |
<subsection> |
6304 |
<title>Filesystems?</title> |
6305 |
<body> |
6306 |
|
6307 |
<p> |
6308 |
Several filesystems are available. Some of them are found stable on the amd64 |
6309 |
architecture, others aren't. The following filesystems are found to be stable: |
6310 |
ext2 and ext3. jfs and reiserfs may work but need more testing. If you're really |
6311 |
adventurous you can try the unsupported filesystems. |
6312 |
</p> |
6313 |
|
6314 |
<p> |
6315 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
6316 |
journaling, which means that routine ext2 filesystem checks at startup time can |
6317 |
be quite time-consuming. There is now quite a selection of newer-generation |
6318 |
journaled filesystems that can be checked for consistency very quickly and are |
6319 |
thus generally preferred over their non-journaled counterparts. Journaled |
6320 |
filesystems prevent long delays when you boot your system and your filesystem |
6321 |
happens to be in an inconsistent state. |
6322 |
</p> |
6323 |
|
6324 |
<p> |
6325 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
6326 |
journaling for fast recovery in addition to other enhanced journaling modes like |
6327 |
full data and ordered data journaling. ext3 is a very good and reliable |
6328 |
filesystem. It has an additional hashed b-tree indexing option that enables |
6329 |
high performance in almost all situations. You can enable this indexing by |
6330 |
adding <c>-O dir_index</c> to the <c>mke2fs</c> command. In short, ext3 is an |
6331 |
excellent filesystem. |
6332 |
</p> |
6333 |
|
6334 |
<p> |
6335 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
6336 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
6337 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
6338 |
extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is |
6339 |
solid and usable as both general-purpose filesystem and for extreme cases such |
6340 |
as the creation of large filesystems, the use of many small files, very large |
6341 |
files and directories containing tens of thousands of files. |
6342 |
</p> |
6343 |
|
6344 |
<p> |
6345 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
6346 |
feature-set and is optimized for scalability. We only recommend using this |
6347 |
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
6348 |
an uninterruptible power supply. Because XFS aggressively caches in-transit data |
6349 |
in RAM, improperly designed programs (those that don't take proper precautions |
6350 |
when writing files to disk and there are quite a few of them) can lose a good |
6351 |
deal of data if the system goes down unexpectedly. |
6352 |
</p> |
6353 |
|
6354 |
<p> |
6355 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
6356 |
become production-ready and there hasn't been a sufficient track record to |
6357 |
comment positively nor negatively on its general stability at this point. |
6358 |
</p> |
6359 |
|
6360 |
</body> |
6361 |
</subsection> |
6362 |
<subsection id="filesystems-apply"> |
6363 |
<title>Applying a Filesystem to a Partition</title> |
6364 |
<body> |
6365 |
|
6366 |
<p> |
6367 |
To create a filesystem on a partition or volume, there are tools available for |
6368 |
each possible filesystem: |
6369 |
</p> |
6370 |
|
6371 |
<table> |
6372 |
<tr> |
6373 |
<th>Filesystem</th> |
6374 |
<th>Creation Command</th> |
6375 |
</tr> |
6376 |
<tr> |
6377 |
<ti>ext2</ti> |
6378 |
<ti><c>mke2fs</c></ti> |
6379 |
</tr> |
6380 |
<tr> |
6381 |
<ti>ext3</ti> |
6382 |
<ti><c>mke2fs -j</c></ti> |
6383 |
</tr> |
6384 |
<tr> |
6385 |
<ti>reiserfs</ti> |
6386 |
<ti><c>mkreiserfs</c></ti> |
6387 |
</tr> |
6388 |
<tr> |
6389 |
<ti>xfs</ti> |
6390 |
<ti><c>mkfs.xfs</c></ti> |
6391 |
</tr> |
6392 |
<tr> |
6393 |
<ti>jfs</ti> |
6394 |
<ti><c>mkfs.jfs</c></ti> |
6395 |
</tr> |
6396 |
</table> |
6397 |
|
6398 |
<p> |
6399 |
For instance, to have the boot partition (<path>/dev/hda1</path> in our |
6400 |
example) in ext2 and the root partition (<path>/dev/hda3</path> in our example) |
6401 |
in ext3 (as in our example), you would use: |
6402 |
</p> |
6403 |
|
6404 |
<pre caption="Applying a filesystem on a partition"> |
6405 |
# <i>mke2fs /dev/hda1</i> |
6406 |
# <i>mke2fs -j /dev/hda3</i> |
6407 |
</pre> |
6408 |
|
6409 |
<p> |
6410 |
Now create the filesystems on your newly created partitions. |
6411 |
</p> |
6412 |
|
6413 |
</body> |
6414 |
</subsection> |
6415 |
<subsection> |
6416 |
<title>Activating the Swap Partition</title> |
6417 |
<body> |
6418 |
|
6419 |
<p> |
6420 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
6421 |
</p> |
6422 |
|
6423 |
<pre caption="Creating a Swap signature"> |
6424 |
# <i>mkswap /dev/hda2</i> |
6425 |
</pre> |
6426 |
|
6427 |
<p> |
6428 |
To activate the swap partition, use <c>swapon</c>: |
6429 |
</p> |
6430 |
|
6431 |
<pre caption="Activating the swap partition"> |
6432 |
# <i>swapon /dev/hda2</i> |
6433 |
</pre> |
6434 |
|
6435 |
<p> |
6436 |
Create and activate the swap now. |
6437 |
</p> |
6438 |
|
6439 |
</body> |
6440 |
</subsection> |
6441 |
</section> |
6442 |
<section> |
6443 |
<title>Mounting</title> |
6444 |
<body> |
6445 |
|
6446 |
<p> |
6447 |
Now that your partitions are initialized and are housing a filesystem, it is |
6448 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
6449 |
create the necessary mount directories for every partition you created. As an |
6450 |
example we mount the root and boot partition: |
6451 |
</p> |
6452 |
|
6453 |
<pre caption="Mounting partitions"> |
6454 |
# <i>mount /dev/hda3 /mnt/gentoo</i> |
6455 |
# <i>mkdir /mnt/gentoo/boot</i> |
6456 |
# <i>mount /dev/hda1 /mnt/gentoo/boot</i> |
6457 |
</pre> |
6458 |
|
6459 |
<note> |
6460 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
6461 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
6462 |
also holds for <path>/var/tmp</path>. |
6463 |
</note> |
6464 |
|
6465 |
<p> |
6466 |
We will also have to mount the proc filesystem (a virtual interface with the |
6467 |
kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. |
6468 |
</p> |
6469 |
|
6470 |
<p> |
6471 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
6472 |
Installation Files</uri>. |
6473 |
</p> |
6474 |
|
6475 |
</body> |
6476 |
</section> |
6477 |
</sections> |
6478 |
|
6479 |
|
6480 |
|
6481 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-amd64-kernel.xml |
6482 |
|
6483 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-amd64-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
6484 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-amd64-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
6485 |
|
6486 |
Index: hb-install-amd64-kernel.xml |
6487 |
=================================================================== |
6488 |
<?xml version='1.0' encoding='UTF-8'?> |
6489 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
6490 |
|
6491 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
6492 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
6493 |
|
6494 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-amd64-kernel.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
6495 |
|
6496 |
<sections> |
6497 |
|
6498 |
<version>5.6</version> |
6499 |
<date>2006-02-15</date> |
6500 |
|
6501 |
<section> |
6502 |
<title>Timezone</title> |
6503 |
<body> |
6504 |
|
6505 |
<p> |
6506 |
You first need to select your timezone so that your system knows where it is |
6507 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
6508 |
it to <path>/etc/localtime</path>. Please avoid the |
6509 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
6510 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
6511 |
</p> |
6512 |
|
6513 |
<pre caption="Setting the timezone information"> |
6514 |
# <i>ls /usr/share/zoneinfo</i> |
6515 |
<comment>(Suppose you want to use GMT)</comment> |
6516 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
6517 |
</pre> |
6518 |
|
6519 |
</body> |
6520 |
</section> |
6521 |
<section> |
6522 |
<title>Installing the Sources</title> |
6523 |
<subsection> |
6524 |
<title>Choosing a Kernel</title> |
6525 |
<body> |
6526 |
|
6527 |
<p> |
6528 |
The core around which all distributions are built is the Linux kernel. It is the |
6529 |
layer between the user programs and your system hardware. Gentoo provides its |
6530 |
users several possible kernel sources. A full listing with description is |
6531 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
6532 |
Guide</uri>. |
6533 |
</p> |
6534 |
|
6535 |
<p> |
6536 |
For AMD64-based systems we have <c>gentoo-sources</c> (kernel v2.6 source |
6537 |
patched with amd64 specific fixes for stability, performance and hardware |
6538 |
support). |
6539 |
</p> |
6540 |
|
6541 |
<p> |
6542 |
Choose your kernel source and install it using <c>emerge</c>. The |
6543 |
<c>USE="-doc"</c> is necessary to avoid installing xorg-x11 or other |
6544 |
dependencies at this point. <c>USE="symlink"</c> is not necessary for a new |
6545 |
install, but ensures proper creation of the <path>/usr/src/linux</path> |
6546 |
symlink. |
6547 |
</p> |
6548 |
|
6549 |
<pre caption="Installing a kernel source"> |
6550 |
# <i>USE="-doc symlink" emerge gentoo-sources</i> |
6551 |
</pre> |
6552 |
|
6553 |
<p> |
6554 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
6555 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
6556 |
kernel source points to <c>gentoo-sources-2.6.12-r10</c>. Your version may be |
6557 |
different, so keep this in mind. |
6558 |
</p> |
6559 |
|
6560 |
<pre caption="Viewing the kernel source symlink"> |
6561 |
# <i>ls -l /usr/src/linux</i> |
6562 |
lrwxrwxrwx 1 root root 12 Jul 28 11:04 /usr/src/linux -> linux-2.6.12-gentoo-r10 |
6563 |
</pre> |
6564 |
|
6565 |
<p> |
6566 |
Now it is time to configure and compile your kernel source. |
6567 |
You can use <c>genkernel</c> for this, which will build a generic kernel as used |
6568 |
by the Installation CD. We explain the "manual" configuration first though, as |
6569 |
it is the best way to optimize your environment. |
6570 |
</p> |
6571 |
|
6572 |
<p> |
6573 |
If you want to manually configure your kernel, continue now with <uri |
6574 |
link="#manual">Default: Manual Configuration</uri>. If you want to use |
6575 |
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
6576 |
genkernel</uri> instead. |
6577 |
</p> |
6578 |
|
6579 |
</body> |
6580 |
</subsection> |
6581 |
</section> |
6582 |
<section id="manual"> |
6583 |
<title>Default: Manual Configuration</title> |
6584 |
<subsection> |
6585 |
<title>Introduction</title> |
6586 |
<body> |
6587 |
|
6588 |
<p> |
6589 |
Manually configuring a kernel is often seen as the most difficult procedure a |
6590 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
6591 |
couple of kernels you don't even remember that it was difficult ;) |
6592 |
</p> |
6593 |
|
6594 |
<p> |
6595 |
However, one thing <e>is</e> true: you must know your system when you start |
6596 |
configuring a kernel manually. Most information can be gathered by emerging |
6597 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
6598 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
6599 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
6600 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
6601 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
6602 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
6603 |
uses (it might provide you with a nice hint on what to enable). |
6604 |
</p> |
6605 |
|
6606 |
<p> |
6607 |
Now go to your kernel source directory and execute <c>make menuconfig</c>. This |
6608 |
will fire up an ncurses-based configuration menu. |
6609 |
</p> |
6610 |
|
6611 |
<pre caption="Invoking menuconfig"> |
6612 |
# <i>cd /usr/src/linux</i> |
6613 |
# <i>make menuconfig</i> |
6614 |
</pre> |
6615 |
|
6616 |
<p> |
6617 |
You will be greeted with several configuration sections. We'll first list some |
6618 |
options you must activate (otherwise Gentoo will not function, or not function |
6619 |
properly without additional tweaks). |
6620 |
</p> |
6621 |
|
6622 |
</body> |
6623 |
</subsection> |
6624 |
<subsection> |
6625 |
<title>Activating Required Options</title> |
6626 |
<body> |
6627 |
|
6628 |
<p> |
6629 |
First of all, activate the use of development and experimental code/drivers. |
6630 |
You need this, otherwise some very important code/drivers won't show up: |
6631 |
</p> |
6632 |
|
6633 |
<pre caption="Selecting experimental code/drivers, General setup"> |
6634 |
Code maturity level options ---> |
6635 |
[*] Prompt for development and/or incomplete code/drivers |
6636 |
General setup ---> |
6637 |
[*] Support for hot-pluggable devices |
6638 |
</pre> |
6639 |
|
6640 |
<p> |
6641 |
Then we select the exact processor type. |
6642 |
</p> |
6643 |
|
6644 |
<pre caption="Selecting processor type and features"> |
6645 |
Processor type and features ---> |
6646 |
Processor family (AMD-Opteron/Athlon64) ---> |
6647 |
( ) AMD-Opteron/Athlon64 |
6648 |
( ) Intel EM64T |
6649 |
( ) Generic-x86-64" |
6650 |
</pre> |
6651 |
|
6652 |
<p> |
6653 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
6654 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
6655 |
able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc |
6656 |
file system</c>. |
6657 |
</p> |
6658 |
|
6659 |
<pre caption="Selecting necessary file systems"> |
6660 |
File systems ---> |
6661 |
Pseudo Filesystems ---> |
6662 |
<*> /proc file system support |
6663 |
<*> Virtual memory file system support (former shm fs) |
6664 |
|
6665 |
|
6666 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
6667 |
<*> Reiserfs support |
6668 |
<*> Ext3 journalling file system support |
6669 |
<*> JFS filesystem support |
6670 |
<*> Second extended fs support |
6671 |
<*> XFS filesystem support |
6672 |
</pre> |
6673 |
|
6674 |
<p> |
6675 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
6676 |
modem, you will need the following options in the kernel: |
6677 |
</p> |
6678 |
|
6679 |
<pre caption="Selecting PPPoE necessary drivers"> |
6680 |
Device Drivers ---> |
6681 |
Networking Support ---> |
6682 |
<*> PPP (point-to-point protocol) support |
6683 |
<*> PPP support for async serial ports |
6684 |
<*> PPP support for sync tty ports |
6685 |
</pre> |
6686 |
|
6687 |
<p> |
6688 |
The two compression options won't harm but are not definitely needed, neither |
6689 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
6690 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
6691 |
</p> |
6692 |
|
6693 |
<p> |
6694 |
If you require it, don't forget to include support in the kernel for your |
6695 |
ethernet card. |
6696 |
</p> |
6697 |
|
6698 |
<p> |
6699 |
If you have a multi-CPU Opteron or a multi-core (e.g. AMD64 X2) system, you |
6700 |
should activate "Symmetric multi-processing support": |
6701 |
</p> |
6702 |
|
6703 |
<pre caption="Activating SMP support"> |
6704 |
Processor type and features ---> |
6705 |
[*] Symmetric multi-processing support |
6706 |
</pre> |
6707 |
|
6708 |
<p> |
6709 |
If you use USB Input Devices (like Keyboard or Mouse) don't forget to enable |
6710 |
those as well: |
6711 |
</p> |
6712 |
|
6713 |
<pre caption="Activating USB Support for Input Devices"> |
6714 |
Device Drivers ---> |
6715 |
USB Support ---> |
6716 |
<*> USB Human Interface Device (full HID) support |
6717 |
[*] HID input layer support |
6718 |
</pre> |
6719 |
|
6720 |
<p> |
6721 |
When you've finished configuring the kernel, continue with <uri |
6722 |
link="#compiling">Compiling and Installing</uri>. |
6723 |
</p> |
6724 |
|
6725 |
</body> |
6726 |
</subsection> |
6727 |
<subsection id="compiling"> |
6728 |
<title>Compiling and Installing</title> |
6729 |
<body> |
6730 |
|
6731 |
<p> |
6732 |
Now that your kernel is configured, it is time to compile and install it. Exit |
6733 |
the configuration and start the compilation process: |
6734 |
</p> |
6735 |
|
6736 |
<pre caption="Compiling the kernel"> |
6737 |
# <i>make && make modules_install</i> |
6738 |
</pre> |
6739 |
|
6740 |
<p> |
6741 |
When the kernel has finished compiling, copy the kernel image to |
6742 |
<path>/boot</path>. Use whatever name you feel is appropriate for your kernel |
6743 |
choice and remember it as you will need it later on when you configure your |
6744 |
bootloader. Remember to replace <path><kernel-version></path> with the |
6745 |
name and version of your kernel. |
6746 |
</p> |
6747 |
|
6748 |
<pre caption="Installing the kernel"> |
6749 |
# <i>cp arch/x86_64/boot/bzImage /boot/<kernel-version></i> |
6750 |
</pre> |
6751 |
|
6752 |
<p> |
6753 |
Now continue with <uri link="#kernel_modules">Configuring Kernel |
6754 |
Modules</uri>. |
6755 |
</p> |
6756 |
|
6757 |
</body> |
6758 |
</subsection> |
6759 |
</section> |
6760 |
<section id="genkernel"> |
6761 |
<title>Alternative: Using genkernel</title> |
6762 |
<body> |
6763 |
|
6764 |
<p> |
6765 |
If you are reading this section, you have chosen to use our <c>genkernel</c> |
6766 |
script to configure your kernel for you. |
6767 |
</p> |
6768 |
|
6769 |
<p> |
6770 |
Now that your kernel source tree is installed, it's now time to compile your |
6771 |
kernel by using our <c>genkernel</c> script to automatically build a kernel for |
6772 |
you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
6773 |
way our Installation CD kernel is configured. This means that when you use |
6774 |
<c>genkernel</c> to build your kernel, your system will generally detect all |
6775 |
your hardware at boot-time, just like our Installation CD does. Because |
6776 |
genkernel doesn't require any manual kernel configuration, it is an ideal |
6777 |
solution for those users who may not be comfortable compiling their own kernels. |
6778 |
</p> |
6779 |
|
6780 |
<p> |
6781 |
Now, let's see how to use genkernel. First, emerge the genkernel ebuild: |
6782 |
</p> |
6783 |
|
6784 |
<pre caption="Emerging genkernel"> |
6785 |
# <i>emerge genkernel</i> |
6786 |
</pre> |
6787 |
|
6788 |
<p> |
6789 |
Now, compile your kernel sources by running <c>genkernel all</c>. |
6790 |
Be aware though, as <c>genkernel</c> compiles a kernel that supports almost all |
6791 |
hardware, this compilation will take quite a while to finish! |
6792 |
</p> |
6793 |
|
6794 |
<p> |
6795 |
Note that, if your boot partition doesn't use ext2 or ext3 as filesystem you |
6796 |
need to manually configure your kernel using <c>genkernel --menuconfig all</c> |
6797 |
and add support for your filesystem <e>in</e> the kernel (i.e. <e>not</e> as a |
6798 |
module). |
6799 |
</p> |
6800 |
|
6801 |
<pre caption="Running genkernel"> |
6802 |
# <i>genkernel all</i> |
6803 |
</pre> |
6804 |
|
6805 |
<p> |
6806 |
Once <c>genkernel</c> completes, a kernel, full set of modules and |
6807 |
<e>initial root disk</e> (initrd) will be created. We will use the kernel |
6808 |
and initrd when configuring a boot loader later in this document. Write |
6809 |
down the names of the kernel and initrd as you will need it when writing |
6810 |
the bootloader configuration file. The initrd will be started immediately after |
6811 |
booting to perform hardware autodetection (just like on the Installation CD) |
6812 |
before your "real" system starts up. |
6813 |
</p> |
6814 |
|
6815 |
<pre caption="Checking the created kernel image name and initrd"> |
6816 |
# <i>ls /boot/kernel* /boot/initramfs*</i> |
6817 |
</pre> |
6818 |
|
6819 |
<p> |
6820 |
Now, let's perform one more step to get our system to be more like the |
6821 |
Installation CD -- let's emerge <c>coldplug</c>. While the initrd autodetects |
6822 |
hardware that is needed to boot your system, <c>coldplug</c> autodetects |
6823 |
everything else. To emerge and enable <c>coldplug</c>, type the following: |
6824 |
</p> |
6825 |
|
6826 |
<pre caption="Emerging and enabling coldplug"> |
6827 |
# <i>emerge coldplug</i> |
6828 |
# <i>rc-update add coldplug boot</i> |
6829 |
</pre> |
6830 |
|
6831 |
</body> |
6832 |
</section> |
6833 |
|
6834 |
<section id="kernel_modules"> |
6835 |
<title>Configuring Kernel Modules</title> |
6836 |
<subsection> |
6837 |
<title>Configuring the Modules</title> |
6838 |
<body> |
6839 |
|
6840 |
<p> |
6841 |
You should list the modules you want automatically loaded in |
6842 |
<path>/etc/modules.autoload.d/kernel-2.4</path> (or <path>kernel-2.6</path>). |
6843 |
You can add extra options to the modules too if you want. |
6844 |
</p> |
6845 |
|
6846 |
<p> |
6847 |
To view all available modules, run the following <c>find</c> command. Don't |
6848 |
forget to substitute "<kernel version>" with the version of the kernel you |
6849 |
just compiled: |
6850 |
</p> |
6851 |
|
6852 |
<pre caption="Viewing all available modules"> |
6853 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
6854 |
</pre> |
6855 |
|
6856 |
<p> |
6857 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
6858 |
<path>kernel-2.6</path> file and enter the module name in it. |
6859 |
</p> |
6860 |
|
6861 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
6862 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
6863 |
</pre> |
6864 |
|
6865 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
6866 |
3c59x |
6867 |
</pre> |
6868 |
|
6869 |
<p> |
6870 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
6871 |
your System</uri>. |
6872 |
</p> |
6873 |
|
6874 |
</body> |
6875 |
</subsection> |
6876 |
</section> |
6877 |
</sections> |
6878 |
|
6879 |
|
6880 |
|
6881 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-amd64-medium.xml |
6882 |
|
6883 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-amd64-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
6884 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-amd64-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
6885 |
|
6886 |
Index: hb-install-amd64-medium.xml |
6887 |
=================================================================== |
6888 |
<?xml version='1.0' encoding='UTF-8'?> |
6889 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
6890 |
|
6891 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
6892 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
6893 |
|
6894 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-amd64-medium.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
6895 |
|
6896 |
<sections> |
6897 |
|
6898 |
<version>5.3</version> |
6899 |
<date>2005-11-29</date> |
6900 |
|
6901 |
<section> |
6902 |
<title>Hardware Requirements</title> |
6903 |
<subsection> |
6904 |
<title>Introduction</title> |
6905 |
<body> |
6906 |
|
6907 |
<p> |
6908 |
Before we start, we first list what hardware requirements you need to |
6909 |
successfully install Gentoo on your box. |
6910 |
</p> |
6911 |
|
6912 |
</body> |
6913 |
</subsection> |
6914 |
<subsection> |
6915 |
<title>Hardware Requirements</title> |
6916 |
<body> |
6917 |
|
6918 |
<table> |
6919 |
<tr> |
6920 |
<th>CPU</th> |
6921 |
<ti>Any AMD64 CPU *</ti> |
6922 |
</tr> |
6923 |
<tr> |
6924 |
<th>Memory</th> |
6925 |
<ti>64 MB</ti> |
6926 |
</tr> |
6927 |
<tr> |
6928 |
<th>Diskspace</th> |
6929 |
<ti>1.5 GB (excluding swap space)</ti> |
6930 |
</tr> |
6931 |
<tr> |
6932 |
<th>Swap space</th> |
6933 |
<ti>At least 256 MB</ti> |
6934 |
</tr> |
6935 |
</table> |
6936 |
|
6937 |
<p> |
6938 |
You should check the <uri link="http://amd64.gentoo.org">Gentoo |
6939 |
AMD64 Project Page</uri> before proceeding. |
6940 |
</p> |
6941 |
|
6942 |
</body> |
6943 |
</subsection> |
6944 |
</section> |
6945 |
<!-- Copy/paste from hb-install-x86-medium.xml (with s/x86/amd64/) --> |
6946 |
<!-- START --> |
6947 |
<section> |
6948 |
<title>The Gentoo Universal Installation CD</title> |
6949 |
<subsection> |
6950 |
<title>Introduction</title> |
6951 |
<body> |
6952 |
|
6953 |
<p> |
6954 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
6955 |
Such a tarball is an archive that contains a minimal environment from |
6956 |
which you can successfully install Gentoo Linux onto your system. |
6957 |
</p> |
6958 |
|
6959 |
<p> |
6960 |
Installations using a stage1 or stage2 tarball file are not documented in the |
6961 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
6962 |
FAQ</uri> on these matters. |
6963 |
</p> |
6964 |
|
6965 |
</body> |
6966 |
</subsection> |
6967 |
<subsection> |
6968 |
<title>Gentoo Universal Installation CD</title> |
6969 |
<body> |
6970 |
|
6971 |
<p> |
6972 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
6973 |
environment. It allows you to boot Linux from the CD. During the boot process |
6974 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
6975 |
Installation CDs are maintained by Gentoo developers. |
6976 |
</p> |
6977 |
|
6978 |
<p> |
6979 |
There currently are two Installation CDs available: |
6980 |
</p> |
6981 |
|
6982 |
<ul> |
6983 |
<li> |
6984 |
The Universal Installation CD contains everything you need to install |
6985 |
Gentoo. It provides stage3 files for common architectures, source code |
6986 |
for the extra applications you need to choose from and, of course, the |
6987 |
installation instructions for your architecture. |
6988 |
</li> |
6989 |
<li> |
6990 |
The Minimal Installation CD contains only a minimal environment that allows |
6991 |
you to boot up and configure your network so you can connect to the |
6992 |
Internet. It does not contain any additional files and cannot be used |
6993 |
during the current installation approach. |
6994 |
</li> |
6995 |
</ul> |
6996 |
|
6997 |
<p> |
6998 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
6999 |
additional resource that you can exploit during the installation of your Gentoo |
7000 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
7001 |
you to easily and quickly install additional applications (such as |
7002 |
OpenOffice.org, KDE, GNOME, ...) immediately after the Gentoo installation and |
7003 |
right before you update your Portage tree. |
7004 |
</p> |
7005 |
|
7006 |
<p> |
7007 |
The use of the Package CD is covered later in this document. |
7008 |
</p> |
7009 |
|
7010 |
</body> |
7011 |
</subsection> |
7012 |
</section> |
7013 |
<!-- STOP --> |
7014 |
<section> |
7015 |
<title>Download, Burn and Boot the Gentoo Universal Installation CD</title> |
7016 |
<subsection> |
7017 |
<title>Downloading and Burning the Installation CD</title> |
7018 |
<body> |
7019 |
|
7020 |
<p> |
7021 |
You can download the Universal Installation CD (and, if you want to, the |
7022 |
Packages CD as well) from one of our <uri |
7023 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CD is located in |
7024 |
the <path>releases/amd64/2005.1-r1/installcd</path> directory; |
7025 |
the Package CD is located in the <path>releases/amd64/2005.1/packagecd</path> |
7026 |
directory. |
7027 |
</p> |
7028 |
|
7029 |
<p> |
7030 |
Inside those directories you'll find ISO-files. Those are full CD images which |
7031 |
you can write on a CD-R. |
7032 |
</p> |
7033 |
|
7034 |
<p> |
7035 |
After downloading the file, you can verify its integrity to see if it is |
7036 |
corrupted or not: |
7037 |
</p> |
7038 |
|
7039 |
<ul> |
7040 |
<li> |
7041 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
7042 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
7043 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows) |
7044 |
</li> |
7045 |
<li> |
7046 |
You can verify the cryptographic signature that we provide. You need to |
7047 |
obtain the public key we use (17072058) before you proceed though. |
7048 |
</li> |
7049 |
</ul> |
7050 |
|
7051 |
<p> |
7052 |
To fetch our public key using the GnuPG application, run the following command: |
7053 |
</p> |
7054 |
|
7055 |
<pre caption="Obtaining the public key"> |
7056 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
7057 |
</pre> |
7058 |
|
7059 |
<p> |
7060 |
Now verify the signature: |
7061 |
</p> |
7062 |
|
7063 |
<pre caption="Verify the cryptographic signature"> |
7064 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
7065 |
</pre> |
7066 |
|
7067 |
<p> |
7068 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
7069 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
7070 |
<c>K3B</c> here; more information can be found in our <uri |
7071 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
7072 |
</p> |
7073 |
|
7074 |
<ul> |
7075 |
<li> |
7076 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
7077 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
7078 |
path). |
7079 |
</li> |
7080 |
<li> |
7081 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
7082 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
7083 |
<c>Start</c>. |
7084 |
</li> |
7085 |
</ul> |
7086 |
|
7087 |
</body> |
7088 |
</subsection> |
7089 |
<subsection> |
7090 |
<title>Booting the Universal Installation CD</title> |
7091 |
<body> |
7092 |
|
7093 |
<p> |
7094 |
Once you have burned your installation CDs, it is time to boot them. |
7095 |
Remove all CDs from the CD drives, reboot your system and enter the BIOS. |
7096 |
This is usually done by hitting DEL, F1 |
7097 |
or ESC, depending on your BIOS. Inside the BIOS, change the boot |
7098 |
order so that the CD-ROM is tried before the hard disk. This is often found |
7099 |
under "CMOS Setup". If you don't do this, your system will just reboot from the |
7100 |
hard disk, ignoring the CD-ROM. |
7101 |
</p> |
7102 |
|
7103 |
<p> |
7104 |
Now place the installation CD in the CD-ROM drive and reboot. You |
7105 |
should see a boot prompt. At this |
7106 |
screen, you can hit Enter to begin the boot process with the default |
7107 |
boot options, or boot the Installation CD with custom boot options by specifying |
7108 |
a kernel followed by boot options and then hitting Enter. |
7109 |
</p> |
7110 |
|
7111 |
<p> |
7112 |
Specifying a kernel? Yes, we provide several kernels on our Installation CD. The |
7113 |
default one is <c>gentoo</c>. Other kernels are for specific hardware needs and |
7114 |
the <c>-nofb</c> variants which disable framebuffer. |
7115 |
</p> |
7116 |
|
7117 |
<p> |
7118 |
Below you'll find a short overview on the available kernels: |
7119 |
</p> |
7120 |
|
7121 |
<table> |
7122 |
<tr> |
7123 |
<th>Kernel</th> |
7124 |
<th>Description</th> |
7125 |
</tr> |
7126 |
<tr> |
7127 |
<ti>gentoo</ti> |
7128 |
<ti>Default kernel with support for K8 CPUs with NUMA</ti> |
7129 |
</tr> |
7130 |
</table> |
7131 |
|
7132 |
<p> |
7133 |
You can also provide kernel options. They represent optional settings |
7134 |
you can (de)activate at will. The following code listing explains all available |
7135 |
kernel options. |
7136 |
</p> |
7137 |
|
7138 |
<pre caption="Available boot options"> |
7139 |
- agpgart loads agpgart (use if you have graphic problems,lockups) |
7140 |
- acpi=on loads support for ACPI firmware |
7141 |
- ide=nodma force disabling of DMA for malfunctioning IDE devices |
7142 |
- doscsi scan for scsi devices (breaks some ethernet cards) |
7143 |
- dopcmcia starts pcmcia service for PCMCIA cdroms |
7144 |
- nofirewire disables firewire modules in initrd (for firewire cdroms,etc) |
7145 |
- nokeymap disables keymap selection for non-us keyboard layouts |
7146 |
- docache cache the entire runtime portion of cd in RAM, allows you |
7147 |
to umount /mnt/cdrom to mount another cdrom. |
7148 |
- nodetect causes hwsetup/kudzu and hotplug not to run |
7149 |
- nousb disables usb module load from initrd, disables hotplug |
7150 |
- nodhcp dhcp does not automatically start if nic detected |
7151 |
- nohotplug disables loading hotplug service |
7152 |
- noapic disable apic (try if having hardware problems nics,scsi,etc) |
7153 |
- noevms2 disable loading of EVMS2 modules |
7154 |
- nolvm2 disable loading of LVM2 modules |
7155 |
- hdx=stroke allows you to partition the whole harddrive even when your BIOS |
7156 |
can't handle large harddrives |
7157 |
- noload=module1[,module2[,...]] |
7158 |
disable loading of specific kernel modules |
7159 |
</pre> |
7160 |
|
7161 |
<p> |
7162 |
Now boot your CD, select a kernel (if you are not happy with the default |
7163 |
<c>gentoo</c> kernel) and boot options. As an example, we show you how |
7164 |
to boot the <c>gentoo</c> kernel, with <c>dopcmcia</c> as kernel |
7165 |
parameters: |
7166 |
</p> |
7167 |
|
7168 |
<pre caption="Booting an Installation CD"> |
7169 |
boot: <i>gentoo dopcmcia</i> |
7170 |
</pre> |
7171 |
|
7172 |
<p> |
7173 |
You will then be greeted with a boot screen and progress bar. If you are |
7174 |
installing Gentoo on a system with a non-US keyboard, make sure you |
7175 |
immediately press Alt-F1 to switch to verbose mode and follow the prompt. If no |
7176 |
selection is made in 10 seconds, the default (US keyboard) will be accepted and |
7177 |
the boot process will continue. Once the boot process completes, you will be |
7178 |
automatically logged in to the "Live" Gentoo Linux as |
7179 |
"root", the super user. You should have a root ("#") prompt |
7180 |
on the current console and can also switch to other consoles by pressing Alt-F2, |
7181 |
Alt-F3 and Alt-F4. Get back to the one you started on by pressing Alt-F1. |
7182 |
</p> |
7183 |
|
7184 |
<p> |
7185 |
Now continue with <uri link="#hardware">Extra Hardware |
7186 |
Configuration</uri>. |
7187 |
</p> |
7188 |
|
7189 |
</body> |
7190 |
</subsection> |
7191 |
<subsection id="hardware"> |
7192 |
<title>Extra Hardware Configuration</title> |
7193 |
<body> |
7194 |
|
7195 |
<p> |
7196 |
When the Installation CD boots, it tries to detect all your hardware devices and |
7197 |
loads the appropriate kernel modules to support your hardware. In the |
7198 |
vast majority of cases, it does a very good job. However, in some cases it may |
7199 |
not auto-load the kernel modules you need. If the PCI auto-detection missed |
7200 |
some of your system's hardware, you will have to load the appropriate kernel |
7201 |
modules manually. |
7202 |
</p> |
7203 |
|
7204 |
<p> |
7205 |
In the next example we try to load the <c>8139too</c> module (support for |
7206 |
certain kinds of network interfaces): |
7207 |
</p> |
7208 |
|
7209 |
<pre caption="Loading kernel modules"> |
7210 |
# <i>modprobe 8139too</i> |
7211 |
</pre> |
7212 |
|
7213 |
<p> |
7214 |
If you need PCMCIA support, you should start the <c>pcmcia</c> init script: |
7215 |
</p> |
7216 |
|
7217 |
<pre caption="Starting the PCMCIA init script"> |
7218 |
# <i>/etc/init.d/pcmcia start</i> |
7219 |
</pre> |
7220 |
|
7221 |
</body> |
7222 |
</subsection> |
7223 |
<subsection> |
7224 |
<title>Optional: Tweaking Hard Disk Performance</title> |
7225 |
<body> |
7226 |
|
7227 |
<p> |
7228 |
If you are an advanced user, you might want to tweak the IDE hard disk |
7229 |
performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
7230 |
test the performance of your disk (execute it several times to get a |
7231 |
more precise impression): |
7232 |
</p> |
7233 |
|
7234 |
<pre caption="Testing disk performance"> |
7235 |
# <i>hdparm -tT /dev/hda</i> |
7236 |
</pre> |
7237 |
|
7238 |
<p> |
7239 |
To tweak, you can use any of the following examples (or experiment |
7240 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
7241 |
disk): |
7242 |
</p> |
7243 |
|
7244 |
<pre caption="Tweaking hard disk performance"> |
7245 |
<comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i> |
7246 |
<comment>Activate DMA + Safe Performance-enhancing Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
7247 |
</pre> |
7248 |
|
7249 |
</body> |
7250 |
</subsection> |
7251 |
<subsection id="useraccounts"> |
7252 |
<title>Optional: User Accounts</title> |
7253 |
<body> |
7254 |
|
7255 |
<p> |
7256 |
If you plan on giving other people access to your installation |
7257 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
7258 |
security reasons), you need to create the necessary user accounts and change |
7259 |
the root password. |
7260 |
</p> |
7261 |
|
7262 |
<p> |
7263 |
To change the root password, use the <c>passwd</c> utility: |
7264 |
</p> |
7265 |
|
7266 |
<pre caption="Changing the root password"> |
7267 |
# <i>passwd</i> |
7268 |
New password: <comment>(Enter your new password)</comment> |
7269 |
Re-enter password: <comment>(Re-enter your password)</comment> |
7270 |
</pre> |
7271 |
|
7272 |
<p> |
7273 |
To create a user account, we first enter their credentials, followed by |
7274 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
7275 |
In the next example, we create a user called "john". |
7276 |
</p> |
7277 |
|
7278 |
<pre caption="Creating a user account"> |
7279 |
# <i>useradd -m -G users john</i> |
7280 |
# <i>passwd john</i> |
7281 |
New password: <comment>(Enter john's password)</comment> |
7282 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
7283 |
</pre> |
7284 |
|
7285 |
<p> |
7286 |
You can change your user id from root to the newly created user by using |
7287 |
<c>su</c>: |
7288 |
</p> |
7289 |
|
7290 |
<pre caption="Changing user id"> |
7291 |
# <i>su - john</i> |
7292 |
</pre> |
7293 |
|
7294 |
</body> |
7295 |
</subsection> |
7296 |
<subsection> |
7297 |
<title>Optional: Viewing Documentation while Installing</title> |
7298 |
<body> |
7299 |
|
7300 |
<p> |
7301 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
7302 |
installation, make sure you have created a user account (see <uri |
7303 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
7304 |
go to a new terminal and log in. |
7305 |
</p> |
7306 |
|
7307 |
<p> |
7308 |
If you want to view the documentation on the CD you can immediately run |
7309 |
<c>links2</c> to read it: |
7310 |
</p> |
7311 |
|
7312 |
<pre caption="Viewing the on-CD documentation"> |
7313 |
# <i>links2 /mnt/cdrom/docs/handbook/html/index.html</i> |
7314 |
</pre> |
7315 |
|
7316 |
<p> |
7317 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
7318 |
more recent than the one provided on the CD. You can view it using <c>links2</c> |
7319 |
as well, but only after having completed the <e>Configuring your Network</e> |
7320 |
chapter (otherwise you won't be able to go on the Internet to view the |
7321 |
document): |
7322 |
</p> |
7323 |
|
7324 |
<pre caption="Viewing the Online Documentation"> |
7325 |
# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml</i> |
7326 |
</pre> |
7327 |
|
7328 |
<p> |
7329 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
7330 |
</p> |
7331 |
|
7332 |
</body> |
7333 |
</subsection> |
7334 |
<subsection> |
7335 |
<title>Optional: Starting the SSH Daemon</title> |
7336 |
<body> |
7337 |
|
7338 |
<p> |
7339 |
If you want to allow other users to access your computer during the |
7340 |
Gentoo installation (perhaps because those users are going to help you |
7341 |
install Gentoo, or even do it for you), you need to create a user |
7342 |
account for them and perhaps even provide them with your root password |
7343 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
7344 |
</p> |
7345 |
|
7346 |
<p> |
7347 |
To fire up the SSH daemon, execute the following command: |
7348 |
</p> |
7349 |
|
7350 |
<pre caption="Starting the SSH daemon"> |
7351 |
# <i>/etc/init.d/sshd start</i> |
7352 |
</pre> |
7353 |
|
7354 |
<p> |
7355 |
To be able to use sshd, you first need to set up your networking. Continue with |
7356 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
7357 |
</p> |
7358 |
|
7359 |
</body> |
7360 |
</subsection> |
7361 |
</section> |
7362 |
</sections> |
7363 |
|
7364 |
|
7365 |
|
7366 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-config.xml |
7367 |
|
7368 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-config.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
7369 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-config.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
7370 |
|
7371 |
Index: hb-install-config.xml |
7372 |
=================================================================== |
7373 |
<?xml version='1.0' encoding='UTF-8'?> |
7374 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
7375 |
|
7376 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
7377 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
7378 |
|
7379 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-config.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
7380 |
|
7381 |
<sections> |
7382 |
|
7383 |
<version>5.3</version> |
7384 |
<date>2005-11-19</date> |
7385 |
|
7386 |
<section> |
7387 |
<title>Filesystem Information</title> |
7388 |
<subsection> |
7389 |
<title>What is fstab?</title> |
7390 |
<body> |
7391 |
|
7392 |
<p> |
7393 |
Under Linux, all partitions used by the system must be listed in |
7394 |
<path>/etc/fstab</path>. This file contains the mountpoints of those partitions |
7395 |
(where they are seen in the file system structure), how they should be mounted |
7396 |
and with what special options (automatically or not, whether users can mount |
7397 |
them or not, etc.) |
7398 |
</p> |
7399 |
|
7400 |
</body> |
7401 |
</subsection> |
7402 |
<subsection> |
7403 |
<title>Creating /etc/fstab</title> |
7404 |
<body> |
7405 |
|
7406 |
<p> |
7407 |
<path>/etc/fstab</path> uses a special syntax. Every line consists of six |
7408 |
fields, separated by whitespace (space(s), tabs or a mixture). Each field has |
7409 |
its own meaning: |
7410 |
</p> |
7411 |
|
7412 |
<ul> |
7413 |
<li> |
7414 |
The first field shows the <b>partition</b> described (the path to the device |
7415 |
file) |
7416 |
</li> |
7417 |
<li> |
7418 |
The second field shows the <b>mountpoint</b> at which the partition should be |
7419 |
mounted |
7420 |
</li> |
7421 |
<li> |
7422 |
The third field shows the <b>filesystem</b> used by the partition |
7423 |
</li> |
7424 |
<li> |
7425 |
The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it |
7426 |
wants to mount the partition. As every filesystem has its own mountoptions, |
7427 |
you are encouraged to read the mount man page (<c>man mount</c>) for a full |
7428 |
listing. Multiple mountoptions are comma-separated. |
7429 |
</li> |
7430 |
<li> |
7431 |
The fifth field is used by <c>dump</c> to determine if the partition needs to |
7432 |
be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero). |
7433 |
</li> |
7434 |
<li> |
7435 |
The sixth field is used by <c>fsck</c> to determine the order in which |
7436 |
filesystems should be <b>check</b>ed if the system wasn't shut down properly. |
7437 |
The root filesystem should have <c>1</c> while the rest should have <c>2</c> |
7438 |
(or <c>0</c> if a filesystem check isn't necessary). |
7439 |
</li> |
7440 |
</ul> |
7441 |
|
7442 |
<p> |
7443 |
The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab |
7444 |
file</e>, so start <c>nano</c> (or your favorite editor) to create your |
7445 |
<path>/etc/fstab</path>: |
7446 |
</p> |
7447 |
|
7448 |
<pre caption="Opening /etc/fstab"> |
7449 |
# <i>nano -w /etc/fstab</i> |
7450 |
</pre> |
7451 |
|
7452 |
<p> |
7453 |
Let us take a look at how we write down the options for the <path>/boot</path> |
7454 |
partition. This is just an example, so if your architecture doesn't require a |
7455 |
<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim. |
7456 |
</p> |
7457 |
|
7458 |
<p> |
7459 |
In our default x86 partitioning example <path>/boot</path> is the |
7460 |
<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. |
7461 |
It needs to be checked during boot, so we would write down: |
7462 |
</p> |
7463 |
|
7464 |
<pre caption="An example /boot line for /etc/fstab"> |
7465 |
/dev/hda1 /boot ext2 defaults 1 2 |
7466 |
</pre> |
7467 |
|
7468 |
<p> |
7469 |
Some users don't want their <path>/boot</path> partition to be mounted |
7470 |
automatically to improve their system's security. Those people should |
7471 |
substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to |
7472 |
manually mount this partition every time you want to use it. |
7473 |
</p> |
7474 |
|
7475 |
<p> |
7476 |
Now, to improve performance, most users would want to add the <c>noatime</c> |
7477 |
option as mountoption, which results in a faster system since access times |
7478 |
aren't registered (you don't need those generally anyway): |
7479 |
</p> |
7480 |
|
7481 |
<pre caption="An improved /boot line for /etc/fstab"> |
7482 |
/dev/hda1 /boot ext2 defaults,noatime 1 2 |
7483 |
</pre> |
7484 |
|
7485 |
<p> |
7486 |
If we continue with this, we would end up with the following three lines (for |
7487 |
<path>/boot</path>, <path>/</path> and the swap partition): |
7488 |
</p> |
7489 |
|
7490 |
<pre caption="Three /etc/fstab lines"> |
7491 |
/dev/hda1 /boot ext2 defaults,noatime 1 2 |
7492 |
/dev/hda2 none swap sw 0 0 |
7493 |
/dev/hda3 / ext3 noatime 0 1 |
7494 |
</pre> |
7495 |
|
7496 |
<p> |
7497 |
To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c> |
7498 |
(required) and for your CD-ROM drive (and of course, if you have other |
7499 |
partitions or drives, for those too): |
7500 |
</p> |
7501 |
|
7502 |
<pre caption="A full /etc/fstab example"> |
7503 |
/dev/hda1 /boot ext2 defaults,noatime 1 2 |
7504 |
/dev/hda2 none swap sw 0 0 |
7505 |
/dev/hda3 / ext3 noatime 0 1 |
7506 |
|
7507 |
none /proc proc defaults 0 0 |
7508 |
none /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
7509 |
|
7510 |
/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 |
7511 |
</pre> |
7512 |
|
7513 |
<p> |
7514 |
<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for |
7515 |
removable media as they can be created with one of many filesystems) and |
7516 |
<c>user</c> makes it possible for non-root users to mount the CD. |
7517 |
</p> |
7518 |
|
7519 |
<p> |
7520 |
Now use the above example to create your <path>/etc/fstab</path>. If you are a |
7521 |
<b>SPARC</b>-user, you should add the following line to your |
7522 |
<path>/etc/fstab</path> |
7523 |
too: |
7524 |
</p> |
7525 |
|
7526 |
<pre caption="Adding openprom filesystem to /etc/fstab"> |
7527 |
none /proc/openprom openpromfs defaults 0 0 |
7528 |
</pre> |
7529 |
|
7530 |
<p> |
7531 |
Double-check your <path>/etc/fstab</path>, save and quit to continue. |
7532 |
</p> |
7533 |
|
7534 |
</body> |
7535 |
</subsection> |
7536 |
</section> |
7537 |
<section> |
7538 |
<title>Networking Information</title> |
7539 |
<subsection> |
7540 |
<title>Hostname, Domainname etc.</title> |
7541 |
<body> |
7542 |
|
7543 |
<p> |
7544 |
One of the choices the user has to make is name his/her PC. This seems to be |
7545 |
quite easy, but <e>lots</e> of users are having difficulties finding the |
7546 |
appropriate name for their Linux-pc. To speed things up, know that any name you |
7547 |
choose can be changed afterwards. For all we care, you can just call your system |
7548 |
<c>tux</c> and domain <c>homenetwork</c>. |
7549 |
</p> |
7550 |
|
7551 |
<p> |
7552 |
We use these values in the next examples. First we set the hostname: |
7553 |
</p> |
7554 |
|
7555 |
<pre caption="Setting the hostname"> |
7556 |
# <i>nano -w /etc/conf.d/hostname</i> |
7557 |
|
7558 |
<comment>(Set the HOSTNAME variable to your hostname)</comment> |
7559 |
HOSTNAME="<i>tux</i>" |
7560 |
</pre> |
7561 |
|
7562 |
<p> |
7563 |
Second we set the domainname: |
7564 |
</p> |
7565 |
|
7566 |
<pre caption="Setting the domainname"> |
7567 |
# <i>nano -w /etc/conf.d/domainname</i> |
7568 |
|
7569 |
<comment>(Set the DNSDOMAIN variable to your domain name)</comment> |
7570 |
DNSDOMAIN="<i>homenetwork</i>" |
7571 |
</pre> |
7572 |
|
7573 |
<p> |
7574 |
If you have a NIS domain (if you don't know what that is, then you don't have |
7575 |
one), you need to define that one too: |
7576 |
</p> |
7577 |
|
7578 |
<pre caption="Setting the NIS domainname"> |
7579 |
# <i>nano -w /etc/conf.d/domainname</i> |
7580 |
|
7581 |
<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment> |
7582 |
NISDOMAIN="<i>my-nisdomain</i>" |
7583 |
</pre> |
7584 |
|
7585 |
<p> |
7586 |
Now add the <c>domainname</c> script to the default runlevel: |
7587 |
</p> |
7588 |
|
7589 |
<pre caption="Adding domainname to the default runlevel"> |
7590 |
# <i>rc-update add domainname default</i> |
7591 |
</pre> |
7592 |
|
7593 |
</body> |
7594 |
</subsection> |
7595 |
<subsection> |
7596 |
<title>Configuring your Network</title> |
7597 |
<body> |
7598 |
|
7599 |
<p> |
7600 |
Before you get that "Hey, we've had that already"-feeling, you should remember |
7601 |
that the networking you set up in the beginning of the Gentoo installation was |
7602 |
just for the installation. Right now you are going to configure networking for |
7603 |
your Gentoo system permanently. |
7604 |
</p> |
7605 |
|
7606 |
<note> |
7607 |
More detailed information about networking, including advanced topics like |
7608 |
bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri |
7609 |
link="?part=4">Gentoo Network Configuration</uri> section. |
7610 |
</note> |
7611 |
|
7612 |
<p> |
7613 |
All networking information is gathered in <path>/etc/conf.d/net</path>. It uses |
7614 |
a straightforward yet not intuitive syntax if you don't know how to set up |
7615 |
networking manually. But don't fear, we'll explain everything. A fully |
7616 |
commented example that covers many different configurations is available in |
7617 |
<path>/etc/conf.d/net.example</path>. |
7618 |
</p> |
7619 |
|
7620 |
<p> |
7621 |
DHCP is used by default and does not require any further configuration. |
7622 |
</p> |
7623 |
|
7624 |
<p> |
7625 |
If you need to configure your network connection either because you need |
7626 |
specific DHCP options or because you do not use DHCP at all, open |
7627 |
<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in |
7628 |
this example): |
7629 |
</p> |
7630 |
|
7631 |
<pre caption="Opening /etc/conf.d/net for editing"> |
7632 |
# <i>nano -w /etc/conf.d/net</i> |
7633 |
</pre> |
7634 |
|
7635 |
<p> |
7636 |
You will see the following file: |
7637 |
</p> |
7638 |
|
7639 |
<pre caption="Default /etc/conf.d/net"> |
7640 |
# This blank configuration will automatically use DHCP for any net.* |
7641 |
# scripts in /etc/init.d. To create a more complete configuration, |
7642 |
# please review /etc/conf.d/net.example and save your configuration |
7643 |
# in /etc/conf.d/net (this file :]!). |
7644 |
</pre> |
7645 |
|
7646 |
<p> |
7647 |
To enter your own IP address, netmask and gateway, you need |
7648 |
to set both <c>config_eth0</c> and <c>routes_eth0</c>: |
7649 |
</p> |
7650 |
|
7651 |
<pre caption="Manually setting IP information for eth0"> |
7652 |
config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" ) |
7653 |
routes_eth0=( "default gw 192.168.0.1" ) |
7654 |
</pre> |
7655 |
|
7656 |
<p> |
7657 |
To use DHCP and add specific DHCP options, define <c>config_eth0</c> and |
7658 |
<c>dhcp_eth0</c>: |
7659 |
</p> |
7660 |
|
7661 |
<pre caption="Automatically obtaining an IP address for eth0"> |
7662 |
config_eth0=( "dhcp" ) |
7663 |
dhcp_eth0="nodns nontp nonis" |
7664 |
</pre> |
7665 |
|
7666 |
<p> |
7667 |
Please read <path>/etc/conf.d/net.example</path> for a list of all available |
7668 |
options. |
7669 |
</p> |
7670 |
|
7671 |
<p> |
7672 |
If you have several network interfaces repeat the above steps for |
7673 |
<c>config_eth1</c>, <c>config_eth2</c>, etc. |
7674 |
</p> |
7675 |
|
7676 |
<p> |
7677 |
Now save the configuration and exit to continue. |
7678 |
</p> |
7679 |
|
7680 |
</body> |
7681 |
</subsection> |
7682 |
<subsection> |
7683 |
<title>Automatically Start Networking at Boot</title> |
7684 |
<body> |
7685 |
|
7686 |
<p> |
7687 |
To have your network interfaces activated at boot, you need to add them to the |
7688 |
default runlevel. If you have PCMCIA interfaces you should skip this action as |
7689 |
the PCMCIA interfaces are started by the PCMCIA init script. |
7690 |
</p> |
7691 |
|
7692 |
<pre caption="Adding net.eth0 to the default runlevel"> |
7693 |
# <i>rc-update add net.eth0 default</i> |
7694 |
</pre> |
7695 |
|
7696 |
<p> |
7697 |
If you have several network interfaces, you need to create the appropriate |
7698 |
<path>net.eth1</path>, <path>net.eth2</path> etc. initscripts for those. You can |
7699 |
use <c>ln</c> to do this: |
7700 |
</p> |
7701 |
|
7702 |
<pre caption="Creating extra initscripts"> |
7703 |
# <i>cd /etc/init.d</i> |
7704 |
# <i>ln -s net.eth0 net.eth1</i> |
7705 |
# <i>rc-update add net.eth1 default</i> |
7706 |
</pre> |
7707 |
|
7708 |
</body> |
7709 |
</subsection> |
7710 |
<subsection> |
7711 |
<title>Writing Down Network Information</title> |
7712 |
<body> |
7713 |
|
7714 |
<p> |
7715 |
You now need to inform Linux about your network. This is defined in |
7716 |
<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses |
7717 |
for hosts that aren't resolved by your nameserver. For instance, if your |
7718 |
internal network consists of three PCs called <c>jenny</c> (192.168.0.5), |
7719 |
<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would |
7720 |
open <path>/etc/hosts</path> and fill in the values: |
7721 |
</p> |
7722 |
|
7723 |
<pre caption="Opening /etc/hosts"> |
7724 |
# <i>nano -w /etc/hosts</i> |
7725 |
</pre> |
7726 |
|
7727 |
<pre caption="Filling in the networking information"> |
7728 |
127.0.0.1 localhost |
7729 |
192.168.0.5 jenny.homenetwork jenny |
7730 |
192.168.0.6 benny.homenetwork benny |
7731 |
192.168.0.7 tux.homenetwork tux |
7732 |
</pre> |
7733 |
|
7734 |
<p> |
7735 |
If your system is the only system (or the nameservers handle all name |
7736 |
resolution) a single line is sufficient. For instance, if you want to call your |
7737 |
system <c>tux</c>: |
7738 |
</p> |
7739 |
|
7740 |
<pre caption="/etc/hosts for lonely or fully integrated PCs"> |
7741 |
127.0.0.1 localhost tux |
7742 |
</pre> |
7743 |
|
7744 |
<p> |
7745 |
Save and exit the editor to continue. |
7746 |
</p> |
7747 |
|
7748 |
<p> |
7749 |
If you don't have PCMCIA, you can now continue with <uri |
7750 |
link="#doc_chap3">System Information</uri>. PCMCIA-users should read the |
7751 |
following topic on PCMCIA. |
7752 |
</p> |
7753 |
|
7754 |
</body> |
7755 |
</subsection> |
7756 |
<subsection> |
7757 |
<title>Optional: Get PCMCIA Working</title> |
7758 |
<body> |
7759 |
|
7760 |
<note> |
7761 |
pcmcia-cs is only available for x86, amd64 and ppc platforms. |
7762 |
</note> |
7763 |
|
7764 |
<p> |
7765 |
PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also |
7766 |
includes users who will be working with a 2.6 kernel (even though they won't be |
7767 |
using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary |
7768 |
to avoid installing xorg-x11 at this moment: |
7769 |
</p> |
7770 |
|
7771 |
<pre caption="Installing pcmcia-cs"> |
7772 |
# <i>USE="-X" emerge pcmcia-cs</i> |
7773 |
</pre> |
7774 |
|
7775 |
<p> |
7776 |
When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e> |
7777 |
runlevel: |
7778 |
</p> |
7779 |
|
7780 |
<pre caption="Adding pcmcia to the default runlevel"> |
7781 |
# <i>rc-update add pcmcia default</i> |
7782 |
</pre> |
7783 |
|
7784 |
</body> |
7785 |
</subsection> |
7786 |
</section> |
7787 |
<section> |
7788 |
<title>System Information</title> |
7789 |
<subsection> |
7790 |
<title>Root Password</title> |
7791 |
<body> |
7792 |
|
7793 |
<p> |
7794 |
First we set the root password by typing: |
7795 |
</p> |
7796 |
|
7797 |
<pre caption="Setting the root password"> |
7798 |
# <i>passwd</i> |
7799 |
</pre> |
7800 |
|
7801 |
<p> |
7802 |
If you want root to be able to log on through the serial console, add |
7803 |
<c>tts/0</c> to <path>/etc/securetty</path>: |
7804 |
</p> |
7805 |
|
7806 |
<pre caption="Adding tts/0 to /etc/securetty"> |
7807 |
# <i>echo "tts/0" >> /etc/securetty</i> |
7808 |
</pre> |
7809 |
|
7810 |
</body> |
7811 |
</subsection> |
7812 |
<subsection> |
7813 |
<title>System Information</title> |
7814 |
<body> |
7815 |
|
7816 |
<p> |
7817 |
Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. |
7818 |
Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :) |
7819 |
</p> |
7820 |
|
7821 |
<pre caption="Opening /etc/rc.conf"> |
7822 |
# <i>nano -w /etc/rc.conf</i> |
7823 |
</pre> |
7824 |
|
7825 |
<p> |
7826 |
When you're finished configuring <path>/etc/rc.conf</path>, save and exit. |
7827 |
</p> |
7828 |
|
7829 |
<p> |
7830 |
As you can see, this file is well commented to help you set up the necessary |
7831 |
configuration variables. You can configure your system to use unicode and |
7832 |
define your default editor and your display manager (like gdm or kdm). |
7833 |
</p> |
7834 |
|
7835 |
<p> |
7836 |
Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration. |
7837 |
Edit it to configure your keyboard. |
7838 |
</p> |
7839 |
|
7840 |
<pre caption="Opening /etc/conf.d/keymaps"> |
7841 |
# <i>nano -w /etc/conf.d/keymaps</i> |
7842 |
</pre> |
7843 |
|
7844 |
<p> |
7845 |
Take special care with the <c>KEYMAP</c> variable. If you select the wrong |
7846 |
<c>KEYMAP</c>, you will get weird results when typing on your keyboard. |
7847 |
</p> |
7848 |
|
7849 |
<note> |
7850 |
Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to |
7851 |
select an i386 keymap (such as "us") instead of "sunkeymap". <b>PPC</b> uses x86 |
7852 |
keymaps on most systems. Users who want to be able to use ADB keymaps on boot |
7853 |
have to enable ADB keycode sendings in their kernel and have to set a mac/ppc |
7854 |
keymap in <path>/etc/conf.d/keymaps</path>. |
7855 |
</note> |
7856 |
|
7857 |
<p> |
7858 |
When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and |
7859 |
exit. |
7860 |
</p> |
7861 |
|
7862 |
<p> |
7863 |
Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it |
7864 |
according to your needs. |
7865 |
</p> |
7866 |
|
7867 |
<pre caption="Opening /etc/conf.d/clock"> |
7868 |
# <i>nano -w /etc/conf.d/clock</i> |
7869 |
</pre> |
7870 |
|
7871 |
<p> |
7872 |
If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to |
7873 |
the file. Otherwise you will notice some clock skew. |
7874 |
</p> |
7875 |
|
7876 |
<p> |
7877 |
When you're finished configuring <path>/etc/conf.d/clock</path>, save and |
7878 |
exit. |
7879 |
</p> |
7880 |
|
7881 |
<p> |
7882 |
If you are not installing Gentoo on IBM PPC64 hardware, continue with |
7883 |
<uri link="?part=1&chap=9">Installing Necessary System Tools</uri>. |
7884 |
</p> |
7885 |
|
7886 |
</body> |
7887 |
</subsection> |
7888 |
<subsection> |
7889 |
<title>Configuring the Console</title> |
7890 |
<body> |
7891 |
|
7892 |
<note> |
7893 |
The following section applies to the IBM PPC64 hardware platforms. |
7894 |
</note> |
7895 |
|
7896 |
<p> |
7897 |
If you are running Gentoo on IBM PPC64 hardware and using a virtual console |
7898 |
you must uncomment the appropriate line in <path>/etc/inittab</path> for the |
7899 |
virtual console to spawn a login prompt. |
7900 |
</p> |
7901 |
|
7902 |
<pre caption="Enabling hvc or hvsi support in /etc/inittab"> |
7903 |
hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0 |
7904 |
hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0 |
7905 |
</pre> |
7906 |
|
7907 |
<p> |
7908 |
You should also take this time to verify that the appropriate console is |
7909 |
listed in <path>/etc/securetty</path>. |
7910 |
</p> |
7911 |
|
7912 |
<p> |
7913 |
You may now continue with <uri link="?part=1&chap=9">Installing Necessary |
7914 |
System Tools</uri>. |
7915 |
</p> |
7916 |
|
7917 |
</body> |
7918 |
</subsection> |
7919 |
</section> |
7920 |
</sections> |
7921 |
|
7922 |
|
7923 |
|
7924 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-finalise.xml |
7925 |
|
7926 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-finalise.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
7927 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-finalise.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
7928 |
|
7929 |
Index: hb-install-finalise.xml |
7930 |
=================================================================== |
7931 |
<?xml version='1.0' encoding='UTF-8'?> |
7932 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
7933 |
|
7934 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
7935 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
7936 |
|
7937 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-finalise.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
7938 |
|
7939 |
<sections> |
7940 |
|
7941 |
<version>5.3</version> |
7942 |
<date>2006-01-23</date> |
7943 |
|
7944 |
<section> |
7945 |
<title>User Administration</title> |
7946 |
<subsection> |
7947 |
<title>Adding a User for Daily Use</title> |
7948 |
<body> |
7949 |
|
7950 |
<p> |
7951 |
Working as root on a Unix/Linux system is <e>dangerous</e> and should be avoided |
7952 |
as much as possible. Therefore it is <e>strongly</e> recommended to add a user |
7953 |
for day-to-day use. |
7954 |
</p> |
7955 |
|
7956 |
<p> |
7957 |
The groups the user is member of define what activities the user can perform. |
7958 |
The following table lists a number of important groups you might wish to use: |
7959 |
</p> |
7960 |
|
7961 |
<table> |
7962 |
<tr> |
7963 |
<th>Group</th> |
7964 |
<th>Description</th> |
7965 |
</tr> |
7966 |
<tr> |
7967 |
<ti>audio</ti> |
7968 |
<ti>be able to access the audio devices</ti> |
7969 |
</tr> |
7970 |
<tr> |
7971 |
<ti>cdrom</ti> |
7972 |
<ti>be able to directly access optical devices</ti> |
7973 |
</tr> |
7974 |
<tr> |
7975 |
<ti>floppy</ti> |
7976 |
<ti>be able to directly access floppy devices</ti> |
7977 |
</tr> |
7978 |
<tr> |
7979 |
<ti>games</ti> |
7980 |
<ti>be able to play games</ti> |
7981 |
</tr> |
7982 |
<tr> |
7983 |
<ti>portage</ti> |
7984 |
<ti>be able to use <c>emerge --pretend</c> as a normal user</ti> |
7985 |
</tr> |
7986 |
<tr> |
7987 |
<ti>usb</ti> |
7988 |
<ti>be able to access USB devices</ti> |
7989 |
</tr> |
7990 |
<tr> |
7991 |
<ti>plugdev</ti> |
7992 |
<ti> |
7993 |
Be able to mount and use pluggable devices such as cameras and USB sticks |
7994 |
</ti> |
7995 |
</tr> |
7996 |
<tr> |
7997 |
<ti>video</ti> |
7998 |
<ti> |
7999 |
be able to access video capturing hardware and doing hardware |
8000 |
acceleration |
8001 |
</ti> |
8002 |
</tr> |
8003 |
<tr> |
8004 |
<ti>wheel</ti> |
8005 |
<ti>be able to use <c>su</c></ti> |
8006 |
</tr> |
8007 |
</table> |
8008 |
|
8009 |
<p> |
8010 |
For instance, to create a user called <c>john</c> who is member of the |
8011 |
<c>wheel</c>, <c>users</c> and <c>audio</c> groups, log in as root first |
8012 |
(only root can create users) and run <c>useradd</c>: |
8013 |
</p> |
8014 |
|
8015 |
<pre caption="Adding a user for day-to-day use"> |
8016 |
Login: <i>root</i> |
8017 |
Password: <comment>(Your root password)</comment> |
8018 |
|
8019 |
# <i>useradd -m -G users,wheel,audio -s /bin/bash john</i> |
8020 |
# <i>passwd john</i> |
8021 |
Password: <comment>(Enter the password for john)</comment> |
8022 |
Re-enter password: <comment>(Re-enter the password to verify)</comment> |
8023 |
</pre> |
8024 |
|
8025 |
<p> |
8026 |
If a user ever needs to perform some task as root, they can use <c>su -</c> |
8027 |
to temporarily receive root privileges. Another way is to use the <c>sudo</c> |
8028 |
package which is, if correctly configured, very secure. |
8029 |
</p> |
8030 |
|
8031 |
</body> |
8032 |
</subsection> |
8033 |
</section> |
8034 |
<section> |
8035 |
<title>Optional: Install GRP Packages</title> |
8036 |
<body> |
8037 |
|
8038 |
<impo> |
8039 |
This part is for GRP users only. Other users should skip this part and continue |
8040 |
with <uri link="?part=1&chap=12">Where to go from here?</uri>. |
8041 |
</impo> |
8042 |
|
8043 |
<p> |
8044 |
Now that your system is booted, log on as the user you created (for instance, |
8045 |
<c>john</c>) and use <c>su -</c> to gain root privileges: |
8046 |
</p> |
8047 |
|
8048 |
<pre caption="Gaining root privileges"> |
8049 |
$ <i>su -</i> |
8050 |
Password: <comment>(Enter your root password)</comment> |
8051 |
</pre> |
8052 |
|
8053 |
<p> |
8054 |
Now we need to change the Portage configuration to look for the prebuilt |
8055 |
binaries from the second CD (Gentoo Packages CD). First mount this CD: |
8056 |
</p> |
8057 |
|
8058 |
<pre caption="Mount the Packages CD"> |
8059 |
<comment>(Put the Gentoo Packages CD in the CD tray)</comment> |
8060 |
# <i>mount /mnt/cdrom</i> |
8061 |
</pre> |
8062 |
|
8063 |
<p> |
8064 |
Now configure Portage to use <path>/mnt/cdrom</path> for its prebuilt packages: |
8065 |
</p> |
8066 |
|
8067 |
<pre caption="Configuring Portage to use /mnt/cdrom"> |
8068 |
# <i>ls /mnt/cdrom</i> |
8069 |
|
8070 |
<comment>(If there is a /mnt/cdrom/packages directory:)</comment> |
8071 |
# <i>export PKGDIR="/mnt/cdrom/packages"</i> |
8072 |
|
8073 |
<comment>(Otherwise:)</comment> |
8074 |
# <i>export PKGDIR="/mnt/cdrom"</i> |
8075 |
</pre> |
8076 |
|
8077 |
<p> |
8078 |
Now install the packages you want. The Packages CD contains several prebuilt |
8079 |
binaries, for instance KDE and GNOME. |
8080 |
</p> |
8081 |
|
8082 |
<pre caption="Installing GNOME"> |
8083 |
# <i>emerge --usepkg gnome</i> |
8084 |
</pre> |
8085 |
|
8086 |
<p> |
8087 |
To find out what prebuilt packages are available, do a quick listing of all |
8088 |
the files in <path>/mnt/cdrom/All</path>. For instance, to find out if KDE is |
8089 |
emergeable: |
8090 |
</p> |
8091 |
|
8092 |
<pre caption="Finding out if KDE is installable"> |
8093 |
# <i>ls /mnt/cdrom/All/kde*</i> |
8094 |
</pre> |
8095 |
|
8096 |
<p> |
8097 |
Be sure to install the binaries now. When you do an <c>emerge --sync</c> to |
8098 |
update Portage (as you will learn later), the prebuilt binaries might not match |
8099 |
against the ebuilds in your updated Portage. You can try to circumvent this by |
8100 |
using <c>emerge --usepkgonly</c> instead of <c>emerge --usepkg</c>. |
8101 |
</p> |
8102 |
|
8103 |
<p> |
8104 |
Congratulations, your system is now fully equipped! Continue with <uri |
8105 |
link="?part=1&chap=12">Where to go from here?</uri> to learn more about |
8106 |
Gentoo. |
8107 |
</p> |
8108 |
|
8109 |
</body> |
8110 |
</section> |
8111 |
</sections> |
8112 |
|
8113 |
|
8114 |
|
8115 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-hppa-bootloader.xml |
8116 |
|
8117 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-hppa-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
8118 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-hppa-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
8119 |
|
8120 |
Index: hb-install-hppa-bootloader.xml |
8121 |
=================================================================== |
8122 |
<?xml version='1.0' encoding='UTF-8'?> |
8123 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
8124 |
|
8125 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
8126 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
8127 |
|
8128 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-hppa-bootloader.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
8129 |
|
8130 |
<sections> |
8131 |
|
8132 |
<version>5.1</version> |
8133 |
<date>2006-01-19</date> |
8134 |
|
8135 |
<section> |
8136 |
<title>Installing PALO</title> |
8137 |
<body> |
8138 |
|
8139 |
<p> |
8140 |
On the PA-RISC platform, the boot loader is called palo. You can find |
8141 |
the configuration file in <path>/etc/palo.conf</path>. Here is a sample |
8142 |
configuration: |
8143 |
</p> |
8144 |
|
8145 |
<pre caption = "/etc/palo.conf example"> |
8146 |
--commandline=2/kernel-2.6.12.2-pa2 root=/dev/sda4 |
8147 |
--recoverykernel=/vmlinux.old |
8148 |
--init-partitioned=/dev/sda |
8149 |
</pre> |
8150 |
|
8151 |
<p> |
8152 |
The first line tells palo the location of the kernel and which boot |
8153 |
parameters it must use. <c>2/kernel-2.6.12.2-pa2</c> means the kernel named |
8154 |
<c>kernel-2.6.12.2-pa2</c> resides on the second partition. Beware, the path |
8155 |
to the kernel is relative to the partition, not to the root of your filesystem. |
8156 |
</p> |
8157 |
|
8158 |
<p> |
8159 |
The second line indicates which recovery kernel to use. If it is your |
8160 |
first install and you do not have a recovery kernel, please comment this |
8161 |
out. The third line indicates on which disk palo will reside. |
8162 |
</p> |
8163 |
|
8164 |
<p> |
8165 |
When configuration is done, just run <c>palo</c>. |
8166 |
</p> |
8167 |
|
8168 |
<pre caption = "Applying the PALO configuration"> |
8169 |
# <i>palo</i> |
8170 |
</pre> |
8171 |
|
8172 |
<p> |
8173 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
8174 |
</p> |
8175 |
|
8176 |
</body> |
8177 |
</section> |
8178 |
<section id="reboot"> |
8179 |
<title>Rebooting the System</title> |
8180 |
<subsection> |
8181 |
<body> |
8182 |
|
8183 |
<p> |
8184 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
8185 |
that one magical command you have been waiting for: <c>reboot</c>. |
8186 |
</p> |
8187 |
|
8188 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
8189 |
# <i>exit</i> |
8190 |
cdimage ~# <i>cd</i> |
8191 |
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
8192 |
cdimage ~# <i>reboot</i> |
8193 |
</pre> |
8194 |
|
8195 |
<p> |
8196 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
8197 |
booted again instead of your new Gentoo system. |
8198 |
</p> |
8199 |
|
8200 |
<p> |
8201 |
Once rebooted in your Gentoo installation, finish up with <uri |
8202 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
8203 |
</p> |
8204 |
|
8205 |
</body> |
8206 |
</subsection> |
8207 |
</section> |
8208 |
</sections> |
8209 |
|
8210 |
|
8211 |
|
8212 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-hppa-disk.xml |
8213 |
|
8214 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-hppa-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
8215 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-hppa-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
8216 |
|
8217 |
Index: hb-install-hppa-disk.xml |
8218 |
=================================================================== |
8219 |
<?xml version='1.0' encoding='UTF-8'?> |
8220 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
8221 |
|
8222 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
8223 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
8224 |
|
8225 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-hppa-disk.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
8226 |
|
8227 |
<sections> |
8228 |
|
8229 |
<version>5.1</version> |
8230 |
<date>2005-08-25</date> |
8231 |
|
8232 |
<section> |
8233 |
<title>Introduction to Block Devices</title> |
8234 |
<subsection> |
8235 |
<title>Block Devices</title> |
8236 |
<body> |
8237 |
|
8238 |
<p> |
8239 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
8240 |
and Linux in general, including Linux filesystems, partitions and block devices. |
8241 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
8242 |
you'll be guided through the process of setting up partitions and filesystems |
8243 |
for your Gentoo Linux installation. |
8244 |
</p> |
8245 |
|
8246 |
<p> |
8247 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
8248 |
probably the one that represents the first SCSI HD in a Linux system, namely |
8249 |
<path>/dev/sda</path>. |
8250 |
</p> |
8251 |
|
8252 |
<p> |
8253 |
The block devices above represent an abstract interface to the disk. User |
8254 |
programs can use these block devices to interact with your disk without worrying |
8255 |
about whether your drives are IDE, SCSI or something else. The program can |
8256 |
simply address the storage on the disk as a bunch of contiguous, |
8257 |
randomly-accessible 512-byte blocks. |
8258 |
</p> |
8259 |
|
8260 |
</body> |
8261 |
</subsection> |
8262 |
<subsection> |
8263 |
<title>Partitions and Slices</title> |
8264 |
<body> |
8265 |
|
8266 |
<p> |
8267 |
Although it is theoretically possible to use a full disk to house your Linux |
8268 |
system, this is almost never done in practice. Instead, full disk block devices |
8269 |
are split up in smaller, more manageable block devices. On most systems, |
8270 |
these are called <e>partitions</e>. Other architectures use a similar technique, |
8271 |
called <e>slices</e>. |
8272 |
</p> |
8273 |
|
8274 |
</body> |
8275 |
</subsection> |
8276 |
</section> |
8277 |
<section> |
8278 |
<title>Designing a Partitioning Scheme</title> |
8279 |
<subsection> |
8280 |
<title>How Many and How Big?</title> |
8281 |
<body> |
8282 |
|
8283 |
<p> |
8284 |
The number of partitions is highly dependent on your environment. For instance, |
8285 |
if you have lots of users, you will most likely want to have your |
8286 |
<path>/home</path> separate as it increases security and makes backups easier. |
8287 |
If you are installing Gentoo to perform as a mailserver, your |
8288 |
<path>/var</path> should be separate as all mails are stored inside |
8289 |
<path>/var</path>. A good choice of filesystem will then maximise your |
8290 |
performance. Gameservers will have a separate <path>/opt</path> as most gaming |
8291 |
servers are installed there. The reason is similar for <path>/home</path>: |
8292 |
security and backups. You will definitely want to keep <path>/usr</path> big: |
8293 |
not only will it contain the majority of applications, the Portage tree alone |
8294 |
takes around 500 Mbyte excluding the various sources that are stored in it. |
8295 |
</p> |
8296 |
|
8297 |
<p> |
8298 |
As you can see, it very much depends on what you want to achieve. Separate |
8299 |
partitions or volumes have the following advantages: |
8300 |
</p> |
8301 |
|
8302 |
<ul> |
8303 |
<li> |
8304 |
You can choose the best performing filesystem for each partition or volume |
8305 |
</li> |
8306 |
<li> |
8307 |
Your entire system cannot run out of free space if one defunct tool is |
8308 |
continuously writing files to a partition or volume |
8309 |
</li> |
8310 |
<li> |
8311 |
If necessary, file system checks are reduced in time, as multiple checks can |
8312 |
be done in parallel (although this advantage is more with multiple disks than |
8313 |
it is with multiple partitions) |
8314 |
</li> |
8315 |
<li> |
8316 |
Security can be enhanced by mounting some partitions or volumes read-only, |
8317 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
8318 |
</li> |
8319 |
</ul> |
8320 |
|
8321 |
<p> |
8322 |
However, multiple partitions have one big disadvantage: if not configured |
8323 |
properly, you might result in having a system with lots |
8324 |
of free space on one partition and none on another. There is also a 15-partition |
8325 |
limit for SCSI and SATA. |
8326 |
</p> |
8327 |
|
8328 |
</body> |
8329 |
</subsection> |
8330 |
</section> |
8331 |
<section> |
8332 |
<title>Using fdisk on HPPA to Partition your Disk</title> |
8333 |
<body> |
8334 |
|
8335 |
<p> |
8336 |
Use <c>fdisk</c> to create the partitions you want: |
8337 |
</p> |
8338 |
|
8339 |
<pre caption="Partitioning the disk"> |
8340 |
# <i>fdisk /dev/sda</i> |
8341 |
</pre> |
8342 |
|
8343 |
<p> |
8344 |
HPPA machines use the PC standard DOS partition tables. To create a new |
8345 |
DOS partition table, simply use the <c>o</c> command. |
8346 |
</p> |
8347 |
|
8348 |
<pre caption="Creating a DOS partition table"> |
8349 |
# <i>fdisk /dev/sda</i> |
8350 |
|
8351 |
Command (m for help): <i>o</i> |
8352 |
Building a new DOS disklabel. |
8353 |
</pre> |
8354 |
|
8355 |
<p> |
8356 |
PALO (the HPPA bootloader) needs a special partition to work. You have |
8357 |
to create a partition of at least 16MB at the beginning of your disk. |
8358 |
The partition type must be of type <e>f0</e> (Linux/PA-RISC boot). |
8359 |
</p> |
8360 |
|
8361 |
<impo> |
8362 |
If you ignore this and continue without a special PALO partition, your system |
8363 |
will stop loving you and fail to start. Also, if your disk is larger than 2GB, |
8364 |
make sure that the boot partition is in the first 2GB of your disk. PALO is |
8365 |
unable to read a kernel after the 2GB limit. |
8366 |
</impo> |
8367 |
|
8368 |
<pre caption="A simple default partition schema"> |
8369 |
# <i>cat /etc/fstab</i> |
8370 |
/dev/sda2 /boot ext3 noauto,noatime 1 1 |
8371 |
/dev/sda3 none swap sw 0 0 |
8372 |
/dev/sda4 / ext3 noatime 0 0 |
8373 |
|
8374 |
# <i>fdisk /dev/sda</i> |
8375 |
|
8376 |
Command (m for help): <i>p</i> |
8377 |
|
8378 |
Disk /dev/sda: 4294 MB, 4294816768 bytes |
8379 |
133 heads, 62 sectors/track, 1017 cylinders |
8380 |
Units = cylinders of 8246 * 512 = 4221952 bytes |
8381 |
|
8382 |
Device Boot Start End Blocks Id System |
8383 |
/dev/sda1 1 8 32953 f0 Linux/PA-RISC boot |
8384 |
/dev/sda2 9 20 49476 83 Linux |
8385 |
/dev/sda3 21 70 206150 82 Linux swap |
8386 |
/dev/sda4 71 1017 3904481 83 Linux |
8387 |
</pre> |
8388 |
|
8389 |
<p> |
8390 |
Now that your partitions are created, you can now continue with <uri |
8391 |
link="#filesystems">Creating Filesystems</uri>. |
8392 |
</p> |
8393 |
|
8394 |
</body> |
8395 |
</section> |
8396 |
<section id="filesystems"> |
8397 |
<title>Creating Filesystems</title> |
8398 |
<subsection> |
8399 |
<title>Introduction</title> |
8400 |
<body> |
8401 |
|
8402 |
<p> |
8403 |
Now that your partitions are created, it is time to place a filesystem on them. |
8404 |
If you don't care about what filesystem to choose and are happy with what we use |
8405 |
as default in this handbook, continue with <uri |
8406 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
8407 |
Otherwise read on to learn about the available filesystems... |
8408 |
</p> |
8409 |
|
8410 |
</body> |
8411 |
</subsection> |
8412 |
<subsection> |
8413 |
<title>Filesystems?</title> |
8414 |
<body> |
8415 |
|
8416 |
<p> |
8417 |
Several filesystems are available. Ext2, ext3, XFS and reiserfs are found stable on |
8418 |
the HPPA architecture. The others are very experimental. |
8419 |
</p> |
8420 |
|
8421 |
<p> |
8422 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
8423 |
journaling, which means that routine ext2 filesystem checks at startup time can |
8424 |
be quite time-consuming. There is now quite a selection of newer-generation |
8425 |
journaled filesystems that can be checked for consistency very quickly and are |
8426 |
thus generally preferred over their non-journaled counterparts. Journaled |
8427 |
filesystems prevent long delays when you boot your system and your filesystem |
8428 |
happens to be in an inconsistent state. |
8429 |
</p> |
8430 |
|
8431 |
<p> |
8432 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
8433 |
journaling for fast recovery in addition to other enhanced journaling modes like |
8434 |
full data and ordered data journaling. ext3 is a very good and reliable |
8435 |
filesystem. It has an additional hashed b-tree indexing option that enables |
8436 |
high performance in almost all situations. You can enable this indexing by |
8437 |
adding <c>-O dir_index</c> to the <c>mke2fs</c> command. In short, ext3 is an |
8438 |
excellent filesystem. |
8439 |
</p> |
8440 |
|
8441 |
<p> |
8442 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
8443 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
8444 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
8445 |
extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is |
8446 |
solid and usable as both general-purpose filesystem and for extreme cases such |
8447 |
as the creation of large filesystems, the use of many small files, very large |
8448 |
files and directories containing tens of thousands of files. |
8449 |
</p> |
8450 |
|
8451 |
<p> |
8452 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
8453 |
feature-set and is optimized for scalability. We only recommend using this |
8454 |
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
8455 |
an uninterruptible power supply. Because XFS aggressively caches in-transit data |
8456 |
in RAM, improperly designed programs (those that don't take proper precautions |
8457 |
when writing files to disk and there are quite a few of them) can lose a good |
8458 |
deal of data if the system goes down unexpectedly. |
8459 |
</p> |
8460 |
|
8461 |
<p> |
8462 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
8463 |
become production-ready and there hasn't been a sufficient track record to |
8464 |
comment positively nor negatively on its general stability at this point. |
8465 |
</p> |
8466 |
|
8467 |
</body> |
8468 |
</subsection> |
8469 |
<subsection id="filesystems-apply"> |
8470 |
<title>Applying a Filesystem to a Partition</title> |
8471 |
<body> |
8472 |
|
8473 |
<p> |
8474 |
To create a filesystem on a partition or volume, there are tools available for |
8475 |
each possible filesystem: |
8476 |
</p> |
8477 |
|
8478 |
<table> |
8479 |
<tr> |
8480 |
<th>Filesystem</th> |
8481 |
<th>Creation Command</th> |
8482 |
</tr> |
8483 |
<tr> |
8484 |
<ti>ext2</ti> |
8485 |
<ti><c>mke2fs</c></ti> |
8486 |
</tr> |
8487 |
<tr> |
8488 |
<ti>ext3</ti> |
8489 |
<ti><c>mke2fs -j</c></ti> |
8490 |
</tr> |
8491 |
<tr> |
8492 |
<ti>reiserfs</ti> |
8493 |
<ti><c>mkreiserfs</c></ti> |
8494 |
</tr> |
8495 |
<tr> |
8496 |
<ti>xfs</ti> |
8497 |
<ti><c>mkfs.xfs</c></ti> |
8498 |
</tr> |
8499 |
<tr> |
8500 |
<ti>jfs</ti> |
8501 |
<ti><c>mkfs.jfs</c></ti> |
8502 |
</tr> |
8503 |
</table> |
8504 |
|
8505 |
<p> |
8506 |
For instance, to have the boot partition (<path>/dev/sda2</path> in our |
8507 |
example) in ext2 and the root partition (<path>/dev/sda4</path> in our example) |
8508 |
in ext3 (as in our example), you would use: |
8509 |
</p> |
8510 |
|
8511 |
<pre caption="Applying a filesystem on a partition"> |
8512 |
# <i>mke2fs /dev/sda2</i> |
8513 |
# <i>mke2fs -j /dev/sda4</i> |
8514 |
</pre> |
8515 |
|
8516 |
<p> |
8517 |
Now create the filesystems on your newly created partitions (or logical |
8518 |
volumes). |
8519 |
</p> |
8520 |
|
8521 |
</body> |
8522 |
</subsection> |
8523 |
<subsection> |
8524 |
<title>Activating the Swap Partition</title> |
8525 |
<body> |
8526 |
|
8527 |
<p> |
8528 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
8529 |
</p> |
8530 |
|
8531 |
<pre caption="Creating a Swap signature"> |
8532 |
# <i>mkswap /dev/sda3</i> |
8533 |
</pre> |
8534 |
|
8535 |
<p> |
8536 |
To activate the swap partition, use <c>swapon</c>: |
8537 |
</p> |
8538 |
|
8539 |
<pre caption="Activating the swap partition"> |
8540 |
# <i>swapon /dev/sda3</i> |
8541 |
</pre> |
8542 |
|
8543 |
<p> |
8544 |
Create and activate the swap now. |
8545 |
</p> |
8546 |
|
8547 |
</body> |
8548 |
</subsection> |
8549 |
</section> |
8550 |
<section> |
8551 |
<title>Mounting</title> |
8552 |
<body> |
8553 |
|
8554 |
<p> |
8555 |
Now that your partitions are initialized and are housing a filesystem, it is |
8556 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
8557 |
create the necessary mount directories for every partition you created. As an |
8558 |
example we mount the root and boot partition: |
8559 |
</p> |
8560 |
|
8561 |
<pre caption="Mounting partitions"> |
8562 |
# <i>mount /dev/sda4 /mnt/gentoo</i> |
8563 |
# <i>mkdir /mnt/gentoo/boot</i> |
8564 |
# <i>mount /dev/sda2 /mnt/gentoo/boot</i> |
8565 |
</pre> |
8566 |
|
8567 |
<note> |
8568 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
8569 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
8570 |
also holds for <path>/var/tmp</path>. |
8571 |
</note> |
8572 |
|
8573 |
<p> |
8574 |
We will also have to mount the proc filesystem (a virtual interface with the |
8575 |
kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. |
8576 |
</p> |
8577 |
|
8578 |
<p> |
8579 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
8580 |
Installation Files</uri>. |
8581 |
</p> |
8582 |
|
8583 |
</body> |
8584 |
</section> |
8585 |
</sections> |
8586 |
|
8587 |
|
8588 |
|
8589 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-hppa-kernel.xml |
8590 |
|
8591 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-hppa-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
8592 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-hppa-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
8593 |
|
8594 |
Index: hb-install-hppa-kernel.xml |
8595 |
=================================================================== |
8596 |
<?xml version='1.0' encoding='UTF-8'?> |
8597 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
8598 |
|
8599 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
8600 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
8601 |
|
8602 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-hppa-kernel.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
8603 |
|
8604 |
<sections> |
8605 |
|
8606 |
<version>5.5</version> |
8607 |
<date>2006-01-06</date> |
8608 |
|
8609 |
<section> |
8610 |
<title>Timezone</title> |
8611 |
<body> |
8612 |
|
8613 |
<p> |
8614 |
You first need to select your timezone so that your system knows where it is |
8615 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
8616 |
it to <path>/etc/localtime</path>. Please avoid the |
8617 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
8618 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
8619 |
</p> |
8620 |
|
8621 |
<pre caption="Setting the timezone information"> |
8622 |
# <i>ls /usr/share/zoneinfo</i> |
8623 |
<comment>(Suppose you want to use GMT)</comment> |
8624 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
8625 |
</pre> |
8626 |
|
8627 |
</body> |
8628 |
</section> |
8629 |
<section> |
8630 |
<title>Installing the Sources</title> |
8631 |
<subsection> |
8632 |
<title>Choosing a Kernel</title> |
8633 |
<body> |
8634 |
|
8635 |
<p> |
8636 |
The core around which all distributions are built is the Linux kernel. It is the |
8637 |
layer between the user programs and your system hardware. Gentoo provides its |
8638 |
users several possible kernel sources. A full listing with description is |
8639 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
8640 |
Guide</uri>. |
8641 |
</p> |
8642 |
|
8643 |
<p> |
8644 |
For HPPA we have <c>hppa-sources</c>. Default these sources are based on the |
8645 |
2.6 kernel sources. If you want to install a 2.4 kernel, you will need to |
8646 |
install Gentoo from a working Internet connection as we do not supply those |
8647 |
sources on our Installation CD. Continue by installing the kernel source. The |
8648 |
<c>USE="-doc"</c> is necessary to avoid installing xorg-x11 or other |
8649 |
dependencies at this point. <c>USE="symlink"</c> is not necessary for a new |
8650 |
install, but ensures proper creation of the <path>/usr/src/linux</path> |
8651 |
symlink. |
8652 |
</p> |
8653 |
|
8654 |
<pre caption="Installing a kernel source"> |
8655 |
# <i>USE="-doc symlink" emerge hppa-sources</i> |
8656 |
</pre> |
8657 |
|
8658 |
<p> |
8659 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
8660 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
8661 |
kernel source points to <c>hppa-sources-2.6.12.2-pa2</c>. Your version may be |
8662 |
different, so keep this in mind. |
8663 |
</p> |
8664 |
|
8665 |
<pre caption="Viewing the kernel source symlink"> |
8666 |
# <i>ls -l /usr/src/linux</i> |
8667 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-2.6.12.2-pa2 |
8668 |
</pre> |
8669 |
|
8670 |
<p> |
8671 |
Now it is time to configure and compile your kernel source. All architectures |
8672 |
can use <c>genkernel</c> for this, which will build a generic kernel as used |
8673 |
by the Installation CD. We explain the "manual" configuration first though, as |
8674 |
it is the best way to optimize your environment. |
8675 |
</p> |
8676 |
|
8677 |
<p> |
8678 |
If you want to manually configure your kernel, continue now with <uri |
8679 |
link="#manual">Default: Manual Configuration</uri>. If you want to use |
8680 |
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
8681 |
genkernel</uri> instead. |
8682 |
</p> |
8683 |
|
8684 |
</body> |
8685 |
</subsection> |
8686 |
</section> |
8687 |
<section id="manual"> |
8688 |
<title>Default: Manual Configuration</title> |
8689 |
<subsection> |
8690 |
<title>Introduction</title> |
8691 |
<body> |
8692 |
|
8693 |
<p> |
8694 |
Manually configuring a kernel is often seen as the most difficult procedure a |
8695 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
8696 |
couple of kernels you don't even remember that it was difficult ;) |
8697 |
</p> |
8698 |
|
8699 |
<p> |
8700 |
However, one thing <e>is</e> true: you must know your system when you start |
8701 |
configuring a kernel manually. Most information can be gathered by emerging |
8702 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
8703 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
8704 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
8705 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
8706 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
8707 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
8708 |
uses (it might provide you with a nice hint on what to enable). |
8709 |
</p> |
8710 |
|
8711 |
<p> |
8712 |
Now go to your kernel source directory and execute <c>make menuconfig</c>. This |
8713 |
will fire up an ncurses-based configuration menu. |
8714 |
</p> |
8715 |
|
8716 |
<pre caption="Invoking menuconfig"> |
8717 |
# <i>cd /usr/src/linux</i> |
8718 |
# <i>make menuconfig</i> |
8719 |
</pre> |
8720 |
|
8721 |
<p> |
8722 |
You will be greeted with several configuration sections. We'll first list some |
8723 |
options you must activate (otherwise Gentoo will not function, or not function |
8724 |
properly without additional tweaks). |
8725 |
</p> |
8726 |
|
8727 |
</body> |
8728 |
</subsection> |
8729 |
<subsection> |
8730 |
<title>Activating Required Options</title> |
8731 |
<body> |
8732 |
|
8733 |
<p> |
8734 |
First of all, activate the use of development and experimental code/drivers. |
8735 |
You need this, otherwise some very important code/drivers won't show up: |
8736 |
</p> |
8737 |
|
8738 |
<pre caption="Selecting experimental code/drivers, General setup"> |
8739 |
Code maturity level options ---> |
8740 |
[*] Prompt for development and/or incomplete code/drivers |
8741 |
General setup ---> |
8742 |
[*] Support for hot-pluggable devices |
8743 |
</pre> |
8744 |
|
8745 |
<p> |
8746 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
8747 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
8748 |
able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc |
8749 |
file system</c>. |
8750 |
</p> |
8751 |
|
8752 |
<pre caption="Selecting necessary file systems"> |
8753 |
File systems ---> |
8754 |
Pseudo Filesystems ---> |
8755 |
[*] /proc file system support |
8756 |
[*] Virtual memory file system support (former shm fs) |
8757 |
|
8758 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
8759 |
<*> Reiserfs support |
8760 |
<*> Ext3 journalling file system support |
8761 |
<*> JFS filesystem support |
8762 |
<*> Second extended fs support |
8763 |
<*> XFS filesystem support |
8764 |
</pre> |
8765 |
|
8766 |
<p> |
8767 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
8768 |
modem, you will need the following options in the kernel: |
8769 |
</p> |
8770 |
|
8771 |
<pre caption="Selecting PPPoE necessary drivers"> |
8772 |
Device Drivers ---> |
8773 |
Networking support ---> |
8774 |
<*> PPP (point-to-point protocol) support |
8775 |
<*> PPP support for async serial ports |
8776 |
<*> PPP support for sync tty ports |
8777 |
</pre> |
8778 |
|
8779 |
<p> |
8780 |
The two compression options won't harm but are not definitely needed, neither |
8781 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
8782 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
8783 |
</p> |
8784 |
|
8785 |
<p> |
8786 |
If you require it, don't forget to include support in the kernel for your |
8787 |
ethernet card. |
8788 |
</p> |
8789 |
|
8790 |
<p> |
8791 |
If you have a HIL mouse or keyboard, do not forget to compile in support for |
8792 |
them. |
8793 |
</p> |
8794 |
|
8795 |
<pre caption="Activating HIL support"> |
8796 |
Input core support ---> |
8797 |
[*] Keyboard support |
8798 |
[*] Mouse support |
8799 |
[*] Event interface support |
8800 |
</pre> |
8801 |
|
8802 |
<p> |
8803 |
If you have no mouse on your HIL port, only use the basic support: |
8804 |
</p> |
8805 |
|
8806 |
<pre caption="Basic HIL support"> |
8807 |
HIL support ---> |
8808 |
[*] HIL Keyboard (basic) support |
8809 |
</pre> |
8810 |
|
8811 |
<p> |
8812 |
If you however want <e>full</e> HIL support, select the following options: |
8813 |
</p> |
8814 |
|
8815 |
<pre caption="Full HIL support"> |
8816 |
HIL support ---> |
8817 |
[*] HP System Device Controller i8042 Support |
8818 |
[*] HIL MLC Support |
8819 |
[*] HIL Keyboard (full) support |
8820 |
[*] HIL Mouse & Pointer support |
8821 |
</pre> |
8822 |
|
8823 |
<p> |
8824 |
Also include display driver support: |
8825 |
</p> |
8826 |
|
8827 |
<pre caption="Display Driver support"> |
8828 |
Graphics support ---> |
8829 |
[*] Support for frame buffer devices |
8830 |
[*] HP STI frame buffer device support |
8831 |
Console display driver support ---> |
8832 |
[*] STI text console |
8833 |
</pre> |
8834 |
|
8835 |
<p> |
8836 |
When you're done configuring your kernel, continue with <uri |
8837 |
link="#compiling">Compiling and Installing</uri>. |
8838 |
</p> |
8839 |
|
8840 |
</body> |
8841 |
</subsection> |
8842 |
<subsection id="compiling"> |
8843 |
<title>Compiling and Installing</title> |
8844 |
<body> |
8845 |
|
8846 |
<p> |
8847 |
Now that your kernel is configured, it is time to compile and install it. Exit |
8848 |
the configuration and start the compilation process: |
8849 |
</p> |
8850 |
|
8851 |
<pre caption="Compiling the kernel"> |
8852 |
# <i>make && make modules_install</i> |
8853 |
</pre> |
8854 |
|
8855 |
<p> |
8856 |
When the kernel has finished compiling, copy the kernel image to |
8857 |
<path>/boot</path>. Use whatever name you feel is appropriate for your kernel |
8858 |
choice and remember it as you will need it later on when you configure your |
8859 |
bootloader. Remember to replace <path><kernel-version></path> with the |
8860 |
name and version of your kernel. |
8861 |
</p> |
8862 |
|
8863 |
<pre caption="Installing the kernel"> |
8864 |
# <i>cp vmlinux /boot/<kernel-version></i> |
8865 |
</pre> |
8866 |
|
8867 |
<p> |
8868 |
Now continue with <uri link="#kernel_modules">Configuring Kernel |
8869 |
Modules</uri>. |
8870 |
</p> |
8871 |
|
8872 |
</body> |
8873 |
</subsection> |
8874 |
</section> |
8875 |
<section id="genkernel"> |
8876 |
<title>Alternative: Using genkernel</title> |
8877 |
<body> |
8878 |
|
8879 |
<p> |
8880 |
If you are reading this section, you have chosen to use our <c>genkernel</c> |
8881 |
script to configure your kernel for you. |
8882 |
</p> |
8883 |
|
8884 |
<p> |
8885 |
Now that your kernel source tree is installed, it's now time to compile your |
8886 |
kernel by using our <c>genkernel</c> script to automatically build a kernel for |
8887 |
you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
8888 |
way our Installation CD kernel is configured. This means that when you use |
8889 |
<c>genkernel</c> to build your kernel, your system will generally detect all |
8890 |
your hardware at boot-time, just like our Installation CD does. Because genkernel |
8891 |
doesn't require any manual kernel configuration, it is an ideal solution for |
8892 |
those users who may not be comfortable compiling their own kernels. |
8893 |
</p> |
8894 |
|
8895 |
<p> |
8896 |
Now, let's see how to use genkernel. First, emerge the genkernel ebuild: |
8897 |
</p> |
8898 |
|
8899 |
<pre caption="Emerging genkernel"> |
8900 |
# <i>emerge genkernel</i> |
8901 |
</pre> |
8902 |
|
8903 |
<p> |
8904 |
Now, compile your kernel sources by running <c>genkernel all</c>. |
8905 |
Be aware though, as <c>genkernel</c> compiles a kernel that supports almost all |
8906 |
hardware, this compilation will take quite a while to finish! |
8907 |
</p> |
8908 |
|
8909 |
<p> |
8910 |
Note that, if your boot partition doesn't use ext2 or ext3 as filesystem you |
8911 |
need to manually configure your kernel using <c>genkernel --menuconfig all</c> |
8912 |
and add support for your filesystem <e>in</e> the kernel (i.e. <e>not</e> as a |
8913 |
module). |
8914 |
</p> |
8915 |
|
8916 |
<pre caption="Running genkernel"> |
8917 |
# <i>genkernel all</i> |
8918 |
<comment>(Output removed to increase readability)</comment> |
8919 |
* Kernel compiled successfully! |
8920 |
* Required Kernel Params: |
8921 |
* : root=/dev/ram0 init=/linuxrc real_root=/dev/$ROOT |
8922 |
* where $ROOT is the devicenode for your root partition as |
8923 |
* you should have specified in /etc/fstab |
8924 |
* |
8925 |
* You MUST tell your bootloader to use the generated initrd |
8926 |
* |
8927 |
* Recommended Kernel Params: |
8928 |
* : vga=0x317 splash=verbose |
8929 |
* |
8930 |
* Do NOT report kernel bugs (configs included) as genkernel bugs. |
8931 |
* Make sure you have the latest genkernel before reporting bugs |
8932 |
* |
8933 |
* For more info see /usr/share/genkernel/README |
8934 |
</pre> |
8935 |
|
8936 |
<p> |
8937 |
Once <c>genkernel</c> completes, a kernel, full set of modules and |
8938 |
<e>initial root disk</e> (initrd) will be created. We will use the kernel |
8939 |
and initrd when configuring a boot loader later in this document. Write |
8940 |
down the names of the kernel and initrd as you will need it when writing |
8941 |
the bootloader configuration file. The initrd will be started immediately after |
8942 |
booting to perform hardware autodetection (just like on the Installation CD) |
8943 |
before your "real" system starts up. |
8944 |
</p> |
8945 |
|
8946 |
<pre caption="Checking the created kernel image name and initrd"> |
8947 |
# <i>ls /boot/kernel* /boot/initramfs*</i> |
8948 |
</pre> |
8949 |
|
8950 |
<p> |
8951 |
Now, let's perform one more step to get our system to be more like the |
8952 |
Installation CD -- let's emerge <c>coldplug</c>. While the initrd autodetects |
8953 |
hardware that is needed to boot your system, <c>coldplug</c> autodetects |
8954 |
everything else. To emerge and enable <c>coldplug</c>, type the following: |
8955 |
</p> |
8956 |
|
8957 |
<pre caption="Emerging and enabling coldplug"> |
8958 |
# <i>emerge coldplug</i> |
8959 |
# <i>rc-update add coldplug default</i> |
8960 |
</pre> |
8961 |
|
8962 |
</body> |
8963 |
</section> |
8964 |
<section id="kernel_modules"> |
8965 |
<title>Configuring Kernel Modules</title> |
8966 |
<subsection> |
8967 |
<title>Configuring the Modules</title> |
8968 |
<body> |
8969 |
|
8970 |
<p> |
8971 |
You should list the modules you want automatically loaded in |
8972 |
<path>/etc/modules.autoload.d/kernel-2.6</path>. |
8973 |
You can add extra options to the modules too if you want. |
8974 |
</p> |
8975 |
|
8976 |
<p> |
8977 |
To view all available modules, run the following <c>find</c> command. Don't |
8978 |
forget to substitute "<kernel version>" with the version of the kernel you |
8979 |
just compiled: |
8980 |
</p> |
8981 |
|
8982 |
<pre caption="Viewing all available modules"> |
8983 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
8984 |
</pre> |
8985 |
|
8986 |
<p> |
8987 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
8988 |
<path>kernel-2.6</path> file and enter the module |
8989 |
name in it. |
8990 |
</p> |
8991 |
|
8992 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
8993 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
8994 |
</pre> |
8995 |
|
8996 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
8997 |
3c59x |
8998 |
</pre> |
8999 |
|
9000 |
<p> |
9001 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
9002 |
your System</uri>. |
9003 |
</p> |
9004 |
|
9005 |
</body> |
9006 |
</subsection> |
9007 |
</section> |
9008 |
</sections> |
9009 |
|
9010 |
|
9011 |
|
9012 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-hppa-medium.xml |
9013 |
|
9014 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-hppa-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
9015 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-hppa-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
9016 |
|
9017 |
Index: hb-install-hppa-medium.xml |
9018 |
=================================================================== |
9019 |
<?xml version='1.0' encoding='UTF-8'?> |
9020 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
9021 |
|
9022 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
9023 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
9024 |
|
9025 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-hppa-medium.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
9026 |
|
9027 |
<sections> |
9028 |
|
9029 |
<version>5.2</version> |
9030 |
<date>2005-11-29</date> |
9031 |
|
9032 |
<section> |
9033 |
<title>Hardware Requirements</title> |
9034 |
<subsection> |
9035 |
<title>Introduction</title> |
9036 |
<body> |
9037 |
|
9038 |
<p> |
9039 |
Before we start, we first list what hardware requirements you need to |
9040 |
successfully install Gentoo on your box. |
9041 |
</p> |
9042 |
|
9043 |
</body> |
9044 |
</subsection> |
9045 |
<subsection> |
9046 |
<title>Hardware Requirements</title> |
9047 |
<body> |
9048 |
|
9049 |
<p> |
9050 |
A list of supported hardware can be found on the |
9051 |
<uri link="http://www.pateam.org/list.html">PA Team website</uri>. |
9052 |
You may find additional information about your box in the <uri |
9053 |
link="http://hwdb.parisc-linux.org">Parisc-Linux Hardware Database</uri>. |
9054 |
</p> |
9055 |
|
9056 |
<table> |
9057 |
<tr> |
9058 |
<th>Memory</th> |
9059 |
<ti>64 MB</ti> |
9060 |
</tr> |
9061 |
<tr> |
9062 |
<th>Diskspace</th> |
9063 |
<ti>1.5 GB (excluding swap space)</ti> |
9064 |
</tr> |
9065 |
<tr> |
9066 |
<th>Swap space</th> |
9067 |
<ti>At least 256 MB</ti> |
9068 |
</tr> |
9069 |
</table> |
9070 |
|
9071 |
</body> |
9072 |
</subsection> |
9073 |
</section> |
9074 |
<!-- Copy/paste from hb-install-x86-medium.xml --> |
9075 |
<!-- START --> |
9076 |
<section> |
9077 |
<title>The Gentoo Universal Installation CD</title> |
9078 |
<subsection> |
9079 |
<title>Introduction</title> |
9080 |
<body> |
9081 |
|
9082 |
<p> |
9083 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
9084 |
Such a tarball is an archive that contains a minimal environment from |
9085 |
which you can successfully install Gentoo Linux onto your system. |
9086 |
</p> |
9087 |
|
9088 |
<p> |
9089 |
Installations using a stage1 or stage2 tarball file are not documented in the |
9090 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
9091 |
FAQ</uri> on these matters. |
9092 |
</p> |
9093 |
|
9094 |
</body> |
9095 |
</subsection> |
9096 |
<subsection> |
9097 |
<title>Gentoo Universal Installation CD</title> |
9098 |
<body> |
9099 |
|
9100 |
<p> |
9101 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
9102 |
environment. It allows you to boot Linux from the CD. During the boot process |
9103 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
9104 |
Installation CDs are maintained by Gentoo developers. |
9105 |
</p> |
9106 |
|
9107 |
<p> |
9108 |
There currently are two Installation CDs available: |
9109 |
</p> |
9110 |
|
9111 |
<ul> |
9112 |
<li> |
9113 |
The Universal Installation CD contains everything you need to install |
9114 |
Gentoo. It provides stage3 files for common architectures, source code |
9115 |
for the extra applications you need to choose from and, of course, the |
9116 |
installation instructions for your architecture. |
9117 |
</li> |
9118 |
<li> |
9119 |
The Minimal Installation CD contains only a minimal environment that allows |
9120 |
you to boot up and configure your network so you can connect to the |
9121 |
Internet. It does not contain any additional files and cannot be used |
9122 |
during the current installation approach. |
9123 |
</li> |
9124 |
</ul> |
9125 |
|
9126 |
</body> |
9127 |
</subsection> |
9128 |
</section> |
9129 |
<!-- STOP --> |
9130 |
<section> |
9131 |
<title>Download, Burn and Boot the Gentoo Universal Installation CD</title> |
9132 |
<subsection> |
9133 |
<title>Downloading and Burning the Installation CD</title> |
9134 |
<body> |
9135 |
|
9136 |
<p> |
9137 |
You can download the Universal Installation CD from one of our <uri |
9138 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CD is located in |
9139 |
the <path>releases/hppa/2005.1/installcd</path> directory. |
9140 |
</p> |
9141 |
|
9142 |
<p> |
9143 |
Inside those directories you'll find ISO-files. Those are full CD images which |
9144 |
you can write on a CD-R. |
9145 |
</p> |
9146 |
|
9147 |
<p> |
9148 |
After downloading the file, you can verify its integrity to see if it is |
9149 |
corrupted or not: |
9150 |
</p> |
9151 |
|
9152 |
<ul> |
9153 |
<li> |
9154 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
9155 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
9156 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows) |
9157 |
</li> |
9158 |
<li> |
9159 |
You can verify the cryptographic signature that we provide. You need to |
9160 |
obtain the public key we use (17072058) before you proceed though. |
9161 |
</li> |
9162 |
</ul> |
9163 |
|
9164 |
<p> |
9165 |
To fetch our public key using the GnuPG application, run the following command: |
9166 |
</p> |
9167 |
|
9168 |
<pre caption="Obtaining the public key"> |
9169 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
9170 |
</pre> |
9171 |
|
9172 |
<p> |
9173 |
Now verify the signature: |
9174 |
</p> |
9175 |
|
9176 |
<pre caption="Verify the cryptographic signature"> |
9177 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
9178 |
</pre> |
9179 |
|
9180 |
<p> |
9181 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
9182 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
9183 |
<c>K3B</c> here; more information can be found in our <uri |
9184 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
9185 |
</p> |
9186 |
|
9187 |
<ul> |
9188 |
<li> |
9189 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
9190 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
9191 |
path). |
9192 |
</li> |
9193 |
<li> |
9194 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
9195 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
9196 |
<c>Start</c>. |
9197 |
</li> |
9198 |
</ul> |
9199 |
|
9200 |
</body> |
9201 |
</subsection> |
9202 |
<subsection> |
9203 |
<title>Booting the Universal Installation CD</title> |
9204 |
<body> |
9205 |
|
9206 |
<note> |
9207 |
If you have problems booting the Installation CD or any other media, please |
9208 |
read the <uri |
9209 |
link="http://www.tldp.org/HOWTO/PA-RISC-Linux-Boot-HOWTO/index.html"> |
9210 |
PA-RISC Linux Boot HOWTO</uri>. |
9211 |
</note> |
9212 |
|
9213 |
<p> |
9214 |
Boot your HPPA system. During the boot process, you will see a message similar |
9215 |
to the following: |
9216 |
</p> |
9217 |
|
9218 |
<pre caption="HPPA boot message"> |
9219 |
Searching for Potential Boot Devices. |
9220 |
To terminate search, press and hold the ESCAPE key. |
9221 |
</pre> |
9222 |
|
9223 |
<p> |
9224 |
When this message appears, press and hold the Esc-key until an option menu |
9225 |
appears. This can take a while, be patient. By default, you should enter the |
9226 |
BOOT_ADMIN console. If you receive an option menu, choose <c>Enter Boot |
9227 |
Administration mode</c> to enter the BOOT_ADMIN console. You should now have an |
9228 |
'>' prompt. |
9229 |
</p> |
9230 |
|
9231 |
<p> |
9232 |
Put the Gentoo Installation CD in the CD-ROM. If you do not know the SCSI ID of |
9233 |
your CD-ROM drive, your PA-RISC station will search for it when you issue the |
9234 |
<c>search</c> command. |
9235 |
</p> |
9236 |
|
9237 |
<pre caption="Searching for SCSI ID"> |
9238 |
> <i>search</i> |
9239 |
Searching for Devices with Bootable Media. |
9240 |
To terminate search, please press and hold the ESCAPE key. |
9241 |
</pre> |
9242 |
|
9243 |
<p> |
9244 |
Your PA-RISC station will now display all the available boot media. This is an |
9245 |
example result of this command: |
9246 |
</p> |
9247 |
|
9248 |
<pre caption="Available boot media"> |
9249 |
Device Selection Device Path Device Type and Utilities |
9250 |
--------------------------------------------------------------------------- |
9251 |
|
9252 |
P0 scsi.5.0 TOSHIBA CD-ROM XM-3301TA |
9253 |
IPL |
9254 |
P1 scsi.2.0 COMPAQ ST32550N |
9255 |
IPL |
9256 |
P2 lan.0010a7-06d1b6.3.6 server |
9257 |
IPL |
9258 |
</pre> |
9259 |
|
9260 |
<p> |
9261 |
To boot from a CD-ROM you need the accompanying Device Path. For instance, if we |
9262 |
want to boot from the TOSHIBA CD-ROM in the above example, we would need to type |
9263 |
the following command: |
9264 |
</p> |
9265 |
|
9266 |
<pre caption="Booting from a CD-ROM"> |
9267 |
> <i>boot scsi.5.0 ipl</i> |
9268 |
|
9269 |
Trying scsi.5.0 |
9270 |
</pre> |
9271 |
|
9272 |
<p> |
9273 |
The <c>ipl</c> keyword (Initial Program Loader) tells palo (the PA-RISC boot |
9274 |
LOader) to enter interactive mode. This will allow you to change, for example, |
9275 |
the kernel boot parameters. |
9276 |
</p> |
9277 |
|
9278 |
<p> |
9279 |
When the boot is successful, palo will start in interactive mode: |
9280 |
</p> |
9281 |
|
9282 |
<pre caption="PALO Interactive Mode"> |
9283 |
Boot path initialized. |
9284 |
Attempting to load IPL. |
9285 |
|
9286 |
|
9287 |
HARD Booted. |
9288 |
palo ipl 1.5 root@hope Sat Apr 23 18:06:47 CEST 2005 |
9289 |
|
9290 |
Boot image contains: |
9291 |
0/vmlinux32 6241293 bytes @ 0x3904000 |
9292 |
0/vmlinux64 8352719 bytes @ 0x3ef8000 |
9293 |
0/ramdisk 1007589 bytes @ 0x105800 |
9294 |
|
9295 |
Information: No console specified on kernel command line. This is normal. |
9296 |
PALO will choose the console currently used by firmware (serial).Current command line: |
9297 |
0/vmlinux initrd=initrd TERM=linux root=/dev/ram0 init=/linuxrc cdroot looptype=squashfs loop=/livecd.squashfs hda=scsi console=ttyS0 |
9298 |
0: 0/vmlinux |
9299 |
1: initrd=initrd |
9300 |
2: TERM=linux |
9301 |
3: root=/dev/ram0 |
9302 |
4: init=/linuxrc |
9303 |
5: cdroot |
9304 |
6: looptype=squashfs |
9305 |
7: loop=/livecd.squashfs |
9306 |
8: hda=scsi |
9307 |
9: console=ttyS0 |
9308 |
|
9309 |
<#> edit the numbered field |
9310 |
'b' boot with this command line |
9311 |
'r' restore command line |
9312 |
'l' list dir |
9313 |
</pre> |
9314 |
|
9315 |
<p> |
9316 |
These parameters are suitable for most situations. |
9317 |
</p> |
9318 |
|
9319 |
<p> |
9320 |
If you need extra features you must add the appropriate keyword(s) to the end of |
9321 |
the command line. To add a keyword, edit the last field, add a space and type |
9322 |
your keyword. The only implemented keywords as of now are <c>cdcache</c> which |
9323 |
tells the Installation CD to load itself into RAM, allowing you to unmount the |
9324 |
CD, and <c>noload=module1[,module2[,...]]</c> which allows you to explicitly |
9325 |
disable loading of particular modules. |
9326 |
</p> |
9327 |
|
9328 |
<pre caption="Adding hdb=scsi as boot option"> |
9329 |
(or 'b' to boot with this command line)? <i>9</i> |
9330 |
console=ttyS0 <i>hdb=scsi</i> |
9331 |
</pre> |
9332 |
|
9333 |
<p> |
9334 |
Now that you have tweaked your kernel boot params, boot it. |
9335 |
</p> |
9336 |
|
9337 |
<pre caption="Booting the kernel"> |
9338 |
(or 'b' to boot with this command line)? <i>b</i> |
9339 |
</pre> |
9340 |
|
9341 |
<p> |
9342 |
You should have a root ("#") prompt on the current console and can also switch |
9343 |
to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get back to the one you |
9344 |
started on by pressing Alt-F1. |
9345 |
</p> |
9346 |
|
9347 |
<p> |
9348 |
Now continue with <uri link="#hardware">Extra Hardware |
9349 |
Configuration</uri>. |
9350 |
</p> |
9351 |
|
9352 |
</body> |
9353 |
</subsection> |
9354 |
<subsection id="hardware"> |
9355 |
<title>Extra Hardware Configuration</title> |
9356 |
<body> |
9357 |
|
9358 |
<p> |
9359 |
Most hppa machines have an onboard ethernet card. Old ones use the lasi driver |
9360 |
which is compiled in the kernel. Newer ones need the tulip driver which is |
9361 |
compiled as a module. To use the latter, you need to load its driver. |
9362 |
</p> |
9363 |
|
9364 |
<p> |
9365 |
In the next example, we try to load the <c>tulip</c> module (support for |
9366 |
certain kinds of network interfaces): |
9367 |
</p> |
9368 |
|
9369 |
<pre caption="Loading kernel modules"> |
9370 |
# <i>modprobe tulip</i> |
9371 |
</pre> |
9372 |
|
9373 |
</body> |
9374 |
</subsection> |
9375 |
|
9376 |
<subsection id="useraccounts"> |
9377 |
<title>Optional: User Accounts</title> |
9378 |
<body> |
9379 |
|
9380 |
<p> |
9381 |
If you plan on giving other people access to your installation |
9382 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
9383 |
security reasons), you need to create the necessary user accounts and change |
9384 |
the root password. |
9385 |
</p> |
9386 |
|
9387 |
<p> |
9388 |
To change the root password, use the <c>passwd</c> utility: |
9389 |
</p> |
9390 |
|
9391 |
<pre caption="Changing the root password"> |
9392 |
# <i>passwd</i> |
9393 |
New password: <comment>(Enter your new password)</comment> |
9394 |
Re-enter password: <comment>(Re-enter your password)</comment> |
9395 |
</pre> |
9396 |
|
9397 |
<p> |
9398 |
To create a user account, we first enter their credentials, followed by |
9399 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
9400 |
In the next example, we create a user called "john". |
9401 |
</p> |
9402 |
|
9403 |
<pre caption="Creating a user account"> |
9404 |
# <i>useradd -m -G users john</i> |
9405 |
# <i>passwd john</i> |
9406 |
New password: <comment>(Enter john's password)</comment> |
9407 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
9408 |
</pre> |
9409 |
|
9410 |
<p> |
9411 |
You can change your user id from root to the newly created user by using |
9412 |
<c>su</c>: |
9413 |
</p> |
9414 |
|
9415 |
<pre caption="Changing user id"> |
9416 |
# <i>su - john</i> |
9417 |
</pre> |
9418 |
|
9419 |
</body> |
9420 |
</subsection> |
9421 |
<subsection> |
9422 |
<title>Optional: Viewing Documentation while Installing</title> |
9423 |
<body> |
9424 |
|
9425 |
<p> |
9426 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
9427 |
installation, make sure you have created a user account (see <uri |
9428 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
9429 |
go to a new terminal and log in. |
9430 |
</p> |
9431 |
|
9432 |
<p> |
9433 |
If you want to view the documentation on the CD you can immediately run |
9434 |
<c>links2</c> to read it: |
9435 |
</p> |
9436 |
|
9437 |
<pre caption="Viewing the on-CD documentation"> |
9438 |
# <i>links2 /mnt/cdrom/docs/handbook/html/index.html</i> |
9439 |
</pre> |
9440 |
|
9441 |
<p> |
9442 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
9443 |
more recent than the one provided on the CD. You can view it using <c>links2</c> |
9444 |
as well, but only after having completed the <e>Configuring your Network</e> |
9445 |
chapter (otherwise you won't be able to go on the Internet to view the |
9446 |
document): |
9447 |
</p> |
9448 |
|
9449 |
<pre caption="Viewing the Online Documentation"> |
9450 |
# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-hppa.xml</i> |
9451 |
</pre> |
9452 |
|
9453 |
<p> |
9454 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
9455 |
</p> |
9456 |
|
9457 |
</body> |
9458 |
</subsection> |
9459 |
<subsection> |
9460 |
<title>Optional: Starting the SSH Daemon</title> |
9461 |
<body> |
9462 |
|
9463 |
<p> |
9464 |
If you want to allow other users to access your computer during the |
9465 |
Gentoo installation (perhaps because those users are going to help you |
9466 |
install Gentoo, or even do it for you), you need to create a user |
9467 |
account for them and perhaps even provide them with your root password |
9468 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
9469 |
</p> |
9470 |
|
9471 |
<p> |
9472 |
To fire up the SSH daemon, execute the following command: |
9473 |
</p> |
9474 |
|
9475 |
<pre caption="Starting the SSH daemon"> |
9476 |
# <i>/etc/init.d/sshd start</i> |
9477 |
</pre> |
9478 |
|
9479 |
<p> |
9480 |
To be able to use sshd, you first need to set up your networking. Continue with |
9481 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
9482 |
</p> |
9483 |
|
9484 |
</body> |
9485 |
</subsection> |
9486 |
</section> |
9487 |
</sections> |
9488 |
|
9489 |
|
9490 |
|
9491 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-network.xml |
9492 |
|
9493 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-network.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
9494 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-network.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
9495 |
|
9496 |
Index: hb-install-network.xml |
9497 |
=================================================================== |
9498 |
<?xml version='1.0' encoding='UTF-8'?> |
9499 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
9500 |
|
9501 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
9502 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
9503 |
|
9504 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-network.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
9505 |
|
9506 |
<sections> |
9507 |
|
9508 |
<version>5.1</version> |
9509 |
<date>2005-08-08</date> |
9510 |
|
9511 |
<section> |
9512 |
<title>Do you need Networking?</title> |
9513 |
<subsection> |
9514 |
<title>Who can do without?</title> |
9515 |
<body> |
9516 |
|
9517 |
<p> |
9518 |
Generally, you don't need a working network connection to install Gentoo using |
9519 |
the Universal Installation CD. However, there are some circumstances where you |
9520 |
do want to have a working Internet connection: |
9521 |
</p> |
9522 |
|
9523 |
<ul> |
9524 |
<li> |
9525 |
The stage3 files that are stored in the Universal Installation CD do not |
9526 |
match your architecture and you need to download the correct stage3 file |
9527 |
</li> |
9528 |
<li> |
9529 |
You need to install a specific networking application that will allow you to |
9530 |
connect to the Internet which isn't available on the Universal Installation |
9531 |
CD but is supported by the Installation CD (i.e. you can connect to the |
9532 |
Internet using the Installation CD but the necessary sources are not |
9533 |
available on the Installation CD) |
9534 |
</li> |
9535 |
<li> |
9536 |
You want remote assistance during the installation (using SSH or through |
9537 |
direct conversations using IRC) |
9538 |
</li> |
9539 |
</ul> |
9540 |
|
9541 |
</body> |
9542 |
</subsection> |
9543 |
<subsection> |
9544 |
<title>Do I need Networking?</title> |
9545 |
<body> |
9546 |
|
9547 |
<p> |
9548 |
To find out if the stage3 file for your architecture is available, take a look |
9549 |
inside <path>/mnt/cdrom/stages</path> and check if one of the available stages |
9550 |
matches your architecture. If not, you can still opt for a stage3 file of an |
9551 |
architecture compatible with yours. |
9552 |
</p> |
9553 |
|
9554 |
<p> |
9555 |
If you on the other hand want to use a stage3 file optimized for your |
9556 |
architecture and the stage3 file of your choice is not available, then you will |
9557 |
need networking to download the appropriate stage3 file. |
9558 |
</p> |
9559 |
|
9560 |
<p> |
9561 |
So, if you don't need networking, you can skip the rest of this chapter and |
9562 |
continue with <uri link="?part=1&chap=4">Preparing the Disks</uri>. |
9563 |
Otherwise, continue with the networking configuration sections below. |
9564 |
</p> |
9565 |
|
9566 |
</body> |
9567 |
</subsection> |
9568 |
</section> |
9569 |
<section> |
9570 |
<title>Automatic Network Detection</title> |
9571 |
<subsection> |
9572 |
<title>Maybe it just works?</title> |
9573 |
<body> |
9574 |
|
9575 |
<p> |
9576 |
If your system is plugged into an Ethernet network with a DHCP server, it is |
9577 |
very likely that your networking configuration has already been set up |
9578 |
automatically for you. If so, you should be able to take advantage of the many |
9579 |
included network-aware commands on the Installation CD such as <c>ssh</c>, |
9580 |
<c>scp</c>, <c>ping</c>, <c>irssi</c>, <c>wget</c> and <c>links</c>, among |
9581 |
others. |
9582 |
</p> |
9583 |
|
9584 |
<p> |
9585 |
If networking has been configured for you, the <c>/sbin/ifconfig</c> command |
9586 |
should list some network interfaces besides lo, such as eth0: |
9587 |
</p> |
9588 |
|
9589 |
<pre caption="/sbin/ifconfig for a working network configuration"> |
9590 |
# <i>/sbin/ifconfig</i> |
9591 |
<comment>(...)</comment> |
9592 |
eth0 Link encap:Ethernet HWaddr 00:50:BA:8F:61:7A |
9593 |
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 |
9594 |
inet6 addr: fe80::50:ba8f:617a/10 Scope:Link |
9595 |
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 |
9596 |
RX packets:1498792 errors:0 dropped:0 overruns:0 frame:0 |
9597 |
TX packets:1284980 errors:0 dropped:0 overruns:0 carrier:0 |
9598 |
collisions:1984 txqueuelen:100 |
9599 |
RX bytes:485691215 (463.1 Mb) TX bytes:123951388 (118.2 Mb) |
9600 |
Interrupt:11 Base address:0xe800 |
9601 |
</pre> |
9602 |
|
9603 |
</body> |
9604 |
</subsection> |
9605 |
<subsection> |
9606 |
<title>Optional: Configure any Proxies</title> |
9607 |
<body> |
9608 |
|
9609 |
<p> |
9610 |
If you access the Internet through a proxy, you might need to set up proxy |
9611 |
information during the installation. It is very easy to define a proxy: you just |
9612 |
need to define a variable which contains the proxy server information. |
9613 |
</p> |
9614 |
|
9615 |
<p> |
9616 |
In most cases, you can just define the variables using the server hostname. As |
9617 |
an example, we assume the proxy is called <c>proxy.gentoo.org</c> and the port |
9618 |
is <c>8080</c>. |
9619 |
</p> |
9620 |
|
9621 |
<pre caption="Defining proxy servers"> |
9622 |
<comment>(If the proxy filters HTTP traffic)</comment> |
9623 |
# <i>export http_proxy="http://proxy.gentoo.org:8080"</i> |
9624 |
<comment>(If the proxy filters FTP traffic)</comment> |
9625 |
# <i>export ftp_proxy="ftp://proxy.gentoo.org:8080"</i> |
9626 |
<comment>(If the proxy filters RSYNC traffic)</comment> |
9627 |
# <i>export RSYNC_PROXY="proxy.gentoo.org:8080"</i> |
9628 |
</pre> |
9629 |
|
9630 |
<p> |
9631 |
If your proxy requires a username and password, you should use the following |
9632 |
syntax for the variable: |
9633 |
</p> |
9634 |
|
9635 |
<pre caption="Adding username/password to the proxy variable"> |
9636 |
http://<i>username</i>:<i>password</i>@proxy.gentoo.org:8080 |
9637 |
</pre> |
9638 |
|
9639 |
</body> |
9640 |
</subsection> |
9641 |
<subsection> |
9642 |
<title>Testing the Network</title> |
9643 |
<body> |
9644 |
|
9645 |
<p> |
9646 |
You may want to try pinging your ISP's DNS server (found in |
9647 |
<path>/etc/resolv.conf</path>) and a Web site of your choice, just to make sure |
9648 |
that your packets are reaching the net, DNS name resolution is working |
9649 |
correctly, etc. |
9650 |
</p> |
9651 |
|
9652 |
<pre caption="Further network testing"> |
9653 |
# <i>ping -c 3 www.yahoo.com</i> |
9654 |
</pre> |
9655 |
|
9656 |
<p> |
9657 |
If you are now able to use your network, you can skip the rest of this |
9658 |
section and continue with <uri link="?part=1&chap=4">Preparing the |
9659 |
Disks</uri>. If not, read on. |
9660 |
</p> |
9661 |
|
9662 |
</body> |
9663 |
</subsection> |
9664 |
</section> |
9665 |
<section> |
9666 |
<title>Automatic Network Configuration</title> |
9667 |
<subsection> |
9668 |
<body> |
9669 |
|
9670 |
<p> |
9671 |
If the network doesn't work immediately, some installation media allow you to |
9672 |
use <c>net-setup</c> (for regular or wireless networks), <c>adsl-setup</c> |
9673 |
(for ADSL-users) or <c>pptp</c> (for PPTP-users - only available on x86). |
9674 |
</p> |
9675 |
|
9676 |
<p> |
9677 |
If your installation medium does not contain any of these tools or your network |
9678 |
doesn't function yet, continue with <uri link="#doc_chap3">Manual Network |
9679 |
Configuration</uri>. |
9680 |
</p> |
9681 |
|
9682 |
<ul> |
9683 |
<li> |
9684 |
Regular Ethernet users should continue with <uri |
9685 |
link="#net-setup">Default: Using net-setup</uri> |
9686 |
</li> |
9687 |
<li> |
9688 |
ADSL users should continue with <uri link="#rp-pppoe">Alternative: |
9689 |
Using RP-PPPoE</uri> |
9690 |
</li> |
9691 |
<li> |
9692 |
PPTP users should continue with <uri link="#pptp">Alternative: |
9693 |
Using PPTP</uri> |
9694 |
</li> |
9695 |
</ul> |
9696 |
|
9697 |
</body> |
9698 |
</subsection> |
9699 |
<subsection id="net-setup"> |
9700 |
<title>Default: Using net-setup</title> |
9701 |
<body> |
9702 |
|
9703 |
<p> |
9704 |
The simplest way to set up networking if it didn't get configured |
9705 |
automatically is to run the <c>net-setup</c> script: |
9706 |
</p> |
9707 |
|
9708 |
<pre caption="Running the net-setup script"> |
9709 |
# <i>net-setup eth0</i> |
9710 |
</pre> |
9711 |
|
9712 |
<p> |
9713 |
<c>net-setup</c> will ask you some questions about your network |
9714 |
environment. When all is done, you should have a working network |
9715 |
connection. Test your network connection as stated before. If the tests |
9716 |
are positive, congratulations! You are now ready to install Gentoo. Skip |
9717 |
the rest of this section and continue with <uri |
9718 |
link="?part=1&chap=4">Preparing the Disks</uri>. |
9719 |
</p> |
9720 |
|
9721 |
<p> |
9722 |
If your network still doesn't work, continue with <uri link="#doc_chap3">Manual |
9723 |
Network Configuration</uri>. |
9724 |
</p> |
9725 |
|
9726 |
|
9727 |
</body> |
9728 |
</subsection> |
9729 |
<subsection id="rp-pppoe"> |
9730 |
<title>Alternative: Using RP-PPPoE</title> |
9731 |
<body> |
9732 |
|
9733 |
<p> |
9734 |
Assuming you need PPPoE to connect to the internet, the Installation CD (any |
9735 |
version) has made things easy for you by including <c>rp-pppoe</c>. Use the |
9736 |
provided <c>adsl-setup</c> script to configure your connection. You will be |
9737 |
prompted for the ethernet device that is connected to your adsl modem, your |
9738 |
username and password, the IPs of your DNS servers and if you need a basic |
9739 |
firewall or not. |
9740 |
</p> |
9741 |
|
9742 |
<pre caption="Using rp-pppoe"> |
9743 |
# <i>adsl-setup</i> |
9744 |
# <i>adsl-start</i> |
9745 |
</pre> |
9746 |
|
9747 |
<p> |
9748 |
If something goes wrong, double-check that you correctly typed your username and |
9749 |
password by looking at <path>/etc/ppp/pap-secrets</path> or |
9750 |
<path>/etc/ppp/chap-secrets</path> and make sure you are using the right |
9751 |
ethernet device. If your ethernet device doesn't exist, you will have to load |
9752 |
the appropriate network modules. In that case you should continue with |
9753 |
<uri link="#doc_chap3">Manual Network Configuration</uri> as we explain how to |
9754 |
load the appropriate network modules there. |
9755 |
</p> |
9756 |
|
9757 |
<p> |
9758 |
If everything worked, continue with <uri link="?part=1&chap=4">Preparing the |
9759 |
Disks</uri>. |
9760 |
</p> |
9761 |
|
9762 |
</body> |
9763 |
</subsection> |
9764 |
<subsection id="pptp"> |
9765 |
<title>Alternative: Using PPTP</title> |
9766 |
<body> |
9767 |
|
9768 |
<note> |
9769 |
PPTP support is only available for x86 |
9770 |
</note> |
9771 |
|
9772 |
<p> |
9773 |
If you need PPTP support, you can use <c>pptpclient</c> which is provided by our |
9774 |
Installation CDs. But first you need to make sure that your configuration is |
9775 |
correct. Edit <path>/etc/ppp/pap-secrets</path> or |
9776 |
<path>/etc/ppp/chap-secrets</path> so it contains the correct username/password |
9777 |
combination: |
9778 |
</p> |
9779 |
|
9780 |
<pre caption="Editing /etc/ppp/chap-secrets"> |
9781 |
# <i>nano -w /etc/ppp/chap-secrets</i> |
9782 |
</pre> |
9783 |
|
9784 |
<p> |
9785 |
Then adjust <path>/etc/ppp/options.pptp</path> if necessary: |
9786 |
</p> |
9787 |
|
9788 |
<pre caption="Editing /etc/ppp/options.pptp"> |
9789 |
# <i>nano -w /etc/ppp/options.pptp</i> |
9790 |
</pre> |
9791 |
|
9792 |
<p> |
9793 |
When all that is done, just run <c>pptp</c> (along with the options you couldn't |
9794 |
set in <path>options.pptp</path>) to connect the server: |
9795 |
</p> |
9796 |
|
9797 |
<pre caption="Connection to a dial-in server"> |
9798 |
# <i>pptp <server ip></i> |
9799 |
</pre> |
9800 |
|
9801 |
<p> |
9802 |
Now continue with <uri link="?part=1&chap=4">Preparing the Disks</uri>. |
9803 |
</p> |
9804 |
|
9805 |
</body> |
9806 |
</subsection> |
9807 |
</section> |
9808 |
<section> |
9809 |
<title>Manual Network Configuration</title> |
9810 |
<subsection> |
9811 |
<title>Loading the Appropriate Network Modules</title> |
9812 |
<body> |
9813 |
|
9814 |
<p> |
9815 |
When the Installation CD boots, it tries to detect all your hardware devices and |
9816 |
loads the appropriate kernel modules (drivers) to support your hardware. In the |
9817 |
vast majority of cases, it does a very good job. However, in some cases, |
9818 |
it may not auto-load the kernel modules you need. |
9819 |
</p> |
9820 |
|
9821 |
<p> |
9822 |
If <c>net-setup</c> or <c>adsl-setup</c> failed, then it is possible that |
9823 |
your network card wasn't found immediately. This means you may have to load |
9824 |
the appropriate kernel modules manually. |
9825 |
</p> |
9826 |
|
9827 |
<p> |
9828 |
To find out what kernel modules we provide for networking, use |
9829 |
<c>ls</c>: |
9830 |
</p> |
9831 |
|
9832 |
<pre caption="Searching for provided modules"> |
9833 |
# <i>ls /lib/modules/`uname -r`/kernel/drivers/net</i> |
9834 |
</pre> |
9835 |
|
9836 |
<p> |
9837 |
If you find a driver for your network card, use <c>modprobe</c> to load |
9838 |
the kernel module: |
9839 |
</p> |
9840 |
|
9841 |
<pre caption="Using modprobe to load a kernel module"> |
9842 |
<comment>(As an example, we load the pcnet32 module)</comment> |
9843 |
# <i>modprobe pcnet32</i> |
9844 |
</pre> |
9845 |
|
9846 |
<p> |
9847 |
To check if your network card is now detected, use <c>ifconfig</c>. A |
9848 |
detected network card would result in something like this: |
9849 |
</p> |
9850 |
|
9851 |
<pre caption="Testing availability of your network card, successful"> |
9852 |
# <i>ifconfig eth0</i> |
9853 |
eth0 Link encap:Ethernet HWaddr FE:FD:00:00:00:00 |
9854 |
BROADCAST NOARP MULTICAST MTU:1500 Metric:1 |
9855 |
RX packets:0 errors:0 dropped:0 overruns:0 frame:0 |
9856 |
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 |
9857 |
collisions:0 txqueuelen:0 |
9858 |
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) |
9859 |
</pre> |
9860 |
|
9861 |
<p> |
9862 |
If however you receive the following error, the network card is not |
9863 |
detected: |
9864 |
</p> |
9865 |
|
9866 |
<pre caption="Testing availability of your network card, failed"> |
9867 |
# <i>ifconfig eth0</i> |
9868 |
eth0: error fetching interface information: Device not found |
9869 |
</pre> |
9870 |
|
9871 |
<p> |
9872 |
If you have multiple network cards in your system they are named <e>eth0</e>, |
9873 |
<e>eth1</e>, etc. Make sure that the network card you want to use works well and |
9874 |
remember to use the correct naming throughout this document. We will assume that |
9875 |
the network card <e>eth0</e> is used. |
9876 |
</p> |
9877 |
|
9878 |
<p> |
9879 |
Assuming that you now have a detected network card, you can |
9880 |
retry <c>net-setup</c> or <c>adsl-setup</c> again (which should work |
9881 |
now), but for the hardcore people amongst you we explain how to configure your |
9882 |
network manually. |
9883 |
</p> |
9884 |
|
9885 |
<p> |
9886 |
Select one of the following sections based on your network setup: |
9887 |
</p> |
9888 |
|
9889 |
<ul> |
9890 |
<li><uri link="#install-dhcp">Using DHCP</uri> for automatic IP retrieval</li> |
9891 |
<li> |
9892 |
<uri link="#wireless">Preparing for Wireless Access</uri> if you have a |
9893 |
wireless card |
9894 |
</li> |
9895 |
<li> |
9896 |
<uri link="#network_term">Understanding Network Terminology</uri> explains |
9897 |
what you need to know about networking |
9898 |
</li> |
9899 |
<li> |
9900 |
<uri link="#ifconfig_route">Using ifconfig and route</uri> explains how to |
9901 |
set up your networking manually |
9902 |
</li> |
9903 |
</ul> |
9904 |
|
9905 |
</body> |
9906 |
</subsection> |
9907 |
<subsection id="install-dhcp"> |
9908 |
<title>Using DHCP</title> |
9909 |
<body> |
9910 |
|
9911 |
<p> |
9912 |
DHCP (Dynamic Host Configuration Protocol) makes it possible to |
9913 |
automatically receive networking information (IP address, netmask, |
9914 |
broadcast address, gateway, nameservers etc.). This only works if you |
9915 |
have a DHCP server in your network (or if your provider provides a DHCP |
9916 |
service). To have a network interface receive this information automatically, |
9917 |
use <c>dhcpcd</c>: |
9918 |
</p> |
9919 |
|
9920 |
<pre caption="Using dhcpcd"> |
9921 |
# <i>dhcpcd eth0</i> |
9922 |
<comment>Some network admins require that you use the</comment> |
9923 |
<comment>hostname and domainname provided by the DHCP server.</comment> |
9924 |
<comment>In that case, use</comment> |
9925 |
# <i>dhcpcd -HD eth0</i> |
9926 |
</pre> |
9927 |
|
9928 |
<p> |
9929 |
If this works (try pinging some internet server, like <uri |
9930 |
link="http://www.google.com">Google</uri>), then you are all set and |
9931 |
ready to continue. Skip the rest of this section and continue with <uri |
9932 |
link="?part=1&chap=4">Preparing the Disks</uri>. |
9933 |
</p> |
9934 |
|
9935 |
</body> |
9936 |
</subsection> |
9937 |
<subsection id="wireless"> |
9938 |
<title>Preparing for Wireless Access</title> |
9939 |
<body> |
9940 |
|
9941 |
<note> |
9942 |
Support for the <c>iwconfig</c> command is only available on x86, amd64 and ppc |
9943 |
Installation CDs. You can still get the extensions working otherwise |
9944 |
by following the instructions of the |
9945 |
<uri link="ftp://ftp.linux-wlan.org/pub/linux-wlan-ng/README">linux-wlan-ng |
9946 |
project</uri>. |
9947 |
</note> |
9948 |
|
9949 |
<p> |
9950 |
If you are using a wireless (802.11) card, you may need to configure your |
9951 |
wireless settings before going any further. To see the current wireless settings |
9952 |
on your card, you can use <c>iwconfig</c>. Running <c>iwconfig</c> might show |
9953 |
something like: |
9954 |
</p> |
9955 |
|
9956 |
<pre caption="Showing the current wireless settings"> |
9957 |
# <i>iwconfig eth0</i> |
9958 |
eth0 IEEE 802.11-DS ESSID:"GentooNode" |
9959 |
Mode:Managed Frequency:2.442GHz Access Point: 00:09:5B:11:CC:F2 |
9960 |
Bit Rate:11Mb/s Tx-Power=20 dBm Sensitivity=0/65535 |
9961 |
Retry limit:16 RTS thr:off Fragment thr:off |
9962 |
Power Management:off |
9963 |
Link Quality:25/10 Signal level:-51 dBm Noise level:-102 dBm |
9964 |
Rx invalid nwid:5901 Rx invalid crypt:0 Rx invalid frag:0 Tx |
9965 |
excessive retries:237 Invalid misc:350282 Missed beacon:84 |
9966 |
</pre> |
9967 |
|
9968 |
<note> |
9969 |
Some wireless cards may have a device name of <c>wlan0</c> or <c>ra0</c> instead |
9970 |
of <c>eth0</c>. Run <c>iwconfig</c> without any command-line parameters to |
9971 |
determine the correct device name. |
9972 |
</note> |
9973 |
|
9974 |
<p> |
9975 |
For most users, there are only two settings that might be important to change, |
9976 |
the ESSID (aka wireless network name) or the WEP key. If the ESSID and Access |
9977 |
Point address listed are already that of your access point and you are not using |
9978 |
WEP, then your wireless is working. If you need to change your ESSID, or add a |
9979 |
WEP key, you can issue the following commands: |
9980 |
</p> |
9981 |
|
9982 |
<pre caption="Changing ESSID and/or adding WEP key"> |
9983 |
<comment>(This sets the network name to "GentooNode")</comment> |
9984 |
# <i>iwconfig eth0 essid GentooNode</i> |
9985 |
|
9986 |
<comment>(This sets a hex WEP key)</comment> |
9987 |
# <i>iwconfig eth0 key 1234123412341234abcd</i> |
9988 |
|
9989 |
<comment>(This sets an ASCII key - prefix it with "s:")</comment> |
9990 |
# <i>iwconfig eth0 key s:some-password</i> |
9991 |
</pre> |
9992 |
|
9993 |
<p> |
9994 |
You can then confirm your wireless settings again by using <c>iwconfig</c>. |
9995 |
Once you have wireless working, you can continue configuring the IP level |
9996 |
networking options as described in the next section (<uri |
9997 |
link="#network_term">Understanding Network Terminology</uri>) or use the |
9998 |
<c>net-setup</c> tool as described previously. |
9999 |
</p> |
10000 |
|
10001 |
</body> |
10002 |
</subsection> |
10003 |
<subsection id="network_term"> |
10004 |
<title>Understanding Network Terminology</title> |
10005 |
<body> |
10006 |
|
10007 |
<note> |
10008 |
If you know your IP address, broadcast address, netmask and nameservers, |
10009 |
then you can skip this subsection and continue with <uri |
10010 |
link="#ifconfig_route">Using ifconfig and route</uri>. |
10011 |
</note> |
10012 |
|
10013 |
<p> |
10014 |
If all of the above fails, you will have to configure your network manually. |
10015 |
This is not difficult at all. However, you need to be familiar with some |
10016 |
network terminology, as you will need it to be able to |
10017 |
configure your network to your satisfaction. After reading this, you |
10018 |
will know what a <e>gateway</e> is, what a <e>netmask</e> serves for, |
10019 |
how a <e>broadcast</e> address is formed and why you need |
10020 |
<e>nameservers</e>. |
10021 |
</p> |
10022 |
|
10023 |
<p> |
10024 |
In a network, hosts are identified by their <e>IP address</e> (Internet |
10025 |
Protocol address). Such an address is a combination of four numbers |
10026 |
between 0 and 255. Well, at least that is how we perceive it. In |
10027 |
reality, such an IP address consists of 32 bits (ones and zeros). Let's |
10028 |
view an example: |
10029 |
</p> |
10030 |
|
10031 |
<pre caption="Example of an IP address"> |
10032 |
IP Address (numbers): 192.168.0.2 |
10033 |
IP Address (bits): 11000000 10101000 00000000 00000010 |
10034 |
-------- -------- -------- -------- |
10035 |
192 168 0 2 |
10036 |
</pre> |
10037 |
|
10038 |
<p> |
10039 |
Such an IP address is unique to a host as far as all accessible networks are |
10040 |
concerned (i.e. every host that you are able to reach must have a unique IP |
10041 |
address). In order to distinguish between hosts inside and outside a |
10042 |
network, the IP address is divided in two parts: the |
10043 |
<e>network</e> part and the <e>host</e> part. |
10044 |
</p> |
10045 |
|
10046 |
<p> |
10047 |
The separation is written down with the <e>netmask</e>, a collection of |
10048 |
ones followed by a collection of zeros. The part of the IP that can be |
10049 |
mapped on the ones is the network-part, the other one is the host-part. |
10050 |
As usual, the netmask can be written down as an IP-address. |
10051 |
</p> |
10052 |
|
10053 |
<pre caption="Example of network/host separation"> |
10054 |
IP-address: 192 168 0 2 |
10055 |
11000000 10101000 00000000 00000010 |
10056 |
Netmask: 11111111 11111111 11111111 00000000 |
10057 |
255 255 255 0 |
10058 |
+--------------------------+--------+ |
10059 |
Network Host |
10060 |
</pre> |
10061 |
|
10062 |
<p> |
10063 |
In other words, 192.168.0.14 is still part of our example network, but |
10064 |
192.168.1.2 is not. |
10065 |
</p> |
10066 |
|
10067 |
<p> |
10068 |
The <e>broadcast</e> address is an IP-address with the same network-part |
10069 |
as your network, but with only ones as host-part. Every host on your |
10070 |
network listens to this IP address. It is truly meant for broadcasting |
10071 |
packets. |
10072 |
</p> |
10073 |
|
10074 |
<pre caption="Broadcast address"> |
10075 |
IP-address: 192 168 0 2 |
10076 |
11000000 10101000 00000000 00000010 |
10077 |
Broadcast: 11000000 10101000 00000000 11111111 |
10078 |
192 168 0 255 |
10079 |
+--------------------------+--------+ |
10080 |
Network Host |
10081 |
</pre> |
10082 |
|
10083 |
<p> |
10084 |
To be able to surf on the internet, you must know which host shares the |
10085 |
Internet connection. This host is called the <e>gateway</e>. Since it is |
10086 |
a regular host, it has a regular IP address (for instance 192.168.0.1). |
10087 |
</p> |
10088 |
|
10089 |
<p> |
10090 |
We previously stated that every host has its own IP address. To be able |
10091 |
to reach this host by a name (instead of an IP address) you need a |
10092 |
service that translates a name (such as <e>dev.gentoo.org</e>) to an IP |
10093 |
address (such as <e>64.5.62.82</e>). Such a service is called a name |
10094 |
service. To use such a service, you must define the necessary <e>name |
10095 |
servers</e> in <path>/etc/resolv.conf</path>. |
10096 |
</p> |
10097 |
|
10098 |
<p> |
10099 |
In some cases, your gateway also serves as nameserver. Otherwise you |
10100 |
will have to enter the nameservers provided by your ISP. |
10101 |
</p> |
10102 |
|
10103 |
<p> |
10104 |
To summarise, you will need the following information before continuing: |
10105 |
</p> |
10106 |
|
10107 |
<table> |
10108 |
<tr> |
10109 |
<th>Network Item</th> |
10110 |
<th>Example</th> |
10111 |
</tr> |
10112 |
<tr> |
10113 |
<ti>Your IP address</ti> |
10114 |
<ti>192.168.0.2</ti> |
10115 |
</tr> |
10116 |
<tr> |
10117 |
<ti>Netmask</ti> |
10118 |
<ti>255.255.255.0</ti> |
10119 |
</tr> |
10120 |
<tr> |
10121 |
<ti>Broadcast</ti> |
10122 |
<ti>192.168.0.255</ti> |
10123 |
</tr> |
10124 |
<tr> |
10125 |
<ti>Gateway</ti> |
10126 |
<ti>192.168.0.1</ti> |
10127 |
</tr> |
10128 |
<tr> |
10129 |
<ti>Nameserver(s)</ti> |
10130 |
<ti>195.130.130.5, 195.130.130.133</ti> |
10131 |
</tr> |
10132 |
</table> |
10133 |
|
10134 |
</body> |
10135 |
</subsection> |
10136 |
<subsection id="ifconfig_route"> |
10137 |
<title>Using ifconfig and route</title> |
10138 |
<body> |
10139 |
|
10140 |
<p> |
10141 |
Setting up your network consists of three steps. First we assign |
10142 |
ourselves an IP address using <c>ifconfig</c>. Then we set up routing to |
10143 |
the gateway using <c>route</c>. Then we finish up by placing the |
10144 |
nameserver IPs in <path>/etc/resolv.conf</path>. |
10145 |
</p> |
10146 |
|
10147 |
<p> |
10148 |
To assign an IP address, you will need your IP address, broadcast |
10149 |
address and netmask. Then execute the following command, substituting |
10150 |
<c>${IP_ADDR}</c> with your IP address, <c>${BROADCAST}</c> with your |
10151 |
broadcast address and <c>${NETMASK}</c> with your netmask: |
10152 |
</p> |
10153 |
|
10154 |
<pre caption="Using ifconfig"> |
10155 |
# <i>ifconfig eth0 ${IP_ADDR} broadcast ${BROADCAST} netmask ${NETMASK} up</i> |
10156 |
</pre> |
10157 |
|
10158 |
<p> |
10159 |
Now set up routing using <c>route</c>. Substitute <c>${GATEWAY}</c> with |
10160 |
your gateway IP address: |
10161 |
</p> |
10162 |
|
10163 |
<pre caption="Using route"> |
10164 |
# <i>route add default gw ${GATEWAY}</i> |
10165 |
</pre> |
10166 |
|
10167 |
<p> |
10168 |
Now open <path>/etc/resolv.conf</path> with your favorite editor (in our |
10169 |
example, we use <c>nano</c>): |
10170 |
</p> |
10171 |
|
10172 |
<pre caption="Creating /etc/resolv.conf"> |
10173 |
# <i>nano -w /etc/resolv.conf</i> |
10174 |
</pre> |
10175 |
|
10176 |
<p> |
10177 |
Now fill in your nameserver(s) using the following as a template. Make |
10178 |
sure you substitute <c>${NAMESERVER1}</c> and <c>${NAMESERVER2}</c> with |
10179 |
the appropriate nameserver addresses: |
10180 |
</p> |
10181 |
|
10182 |
<pre caption="/etc/resolv.conf template"> |
10183 |
nameserver ${NAMESERVER1} |
10184 |
nameserver ${NAMESERVER2} |
10185 |
</pre> |
10186 |
|
10187 |
<p> |
10188 |
That's it. Now test your network by pinging some Internet server (like |
10189 |
<uri link="http://www.google.com">Google</uri>). If this works, |
10190 |
congratulations then. You are now ready to install Gentoo. Continue with <uri |
10191 |
link="?part=1&chap=4">Preparing the Disks</uri>. |
10192 |
</p> |
10193 |
|
10194 |
</body> |
10195 |
</subsection> |
10196 |
</section> |
10197 |
</sections> |
10198 |
|
10199 |
|
10200 |
|
10201 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-next.xml |
10202 |
|
10203 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-next.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
10204 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-next.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
10205 |
|
10206 |
Index: hb-install-next.xml |
10207 |
=================================================================== |
10208 |
<?xml version='1.0' encoding='UTF-8'?> |
10209 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
10210 |
|
10211 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
10212 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
10213 |
|
10214 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-next.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
10215 |
|
10216 |
<sections> |
10217 |
|
10218 |
<version>5.1</version> |
10219 |
<date>2005-08-22</date> |
10220 |
|
10221 |
<section> |
10222 |
<title>Documentation</title> |
10223 |
<subsection> |
10224 |
<body> |
10225 |
|
10226 |
<p> |
10227 |
Congratulations! You now have a working Gentoo system. But where to go from |
10228 |
here? What are your options now? What to explore first? Gentoo provides its |
10229 |
users with lots of possibilities, and therefore lots of documented (and less |
10230 |
documented) features. |
10231 |
</p> |
10232 |
|
10233 |
<p> |
10234 |
You should definitely take a look at the next part of the Gentoo Handbook |
10235 |
entitled <uri link="?part=2">Working with Gentoo</uri> which explains |
10236 |
how to keep your software up to date, how to install more software, what USE |
10237 |
flags are, how the Gentoo Init system works, etc. |
10238 |
</p> |
10239 |
|
10240 |
<p> |
10241 |
If you are interested in optimizing your system for desktop use, or you want to |
10242 |
learn how to configure your system to be a full working desktop system, consult |
10243 |
our extensive <uri link="/doc/en/index.xml?catid=desktop">Gentoo Desktop |
10244 |
Documentation Resources</uri>. Besides, you might want to use our <uri |
10245 |
link="/doc/en/guide-localization.xml">localization guide</uri> to make your |
10246 |
system feel more at home. |
10247 |
</p> |
10248 |
|
10249 |
<p> |
10250 |
We also have a <uri link="/doc/en/security/">Gentoo Security Handbook</uri> |
10251 |
which is worth reading. |
10252 |
</p> |
10253 |
|
10254 |
<p> |
10255 |
For a full listing of all our available documentation check out our <uri |
10256 |
link="/doc/en/index.xml">Documentation Resources</uri> page. |
10257 |
</p> |
10258 |
|
10259 |
</body> |
10260 |
</subsection> |
10261 |
</section> |
10262 |
<section> |
10263 |
<title>Gentoo Online</title> |
10264 |
<body> |
10265 |
|
10266 |
<p> |
10267 |
You are of course always welcome on our <uri |
10268 |
link="http://forums.gentoo.org">Gentoo Forums</uri> or on one of our many |
10269 |
<uri link="/main/en/irc.xml">Gentoo IRC channels</uri>. |
10270 |
</p> |
10271 |
|
10272 |
<p> |
10273 |
We also have several <uri |
10274 |
link="/main/en/lists.xml">mailinglists</uri> open to all |
10275 |
our users. Information on how to join is contained in that page. |
10276 |
</p> |
10277 |
|
10278 |
<p> |
10279 |
We'll shut up now and let you enjoy your installation :) |
10280 |
</p> |
10281 |
|
10282 |
</body> |
10283 |
</section> |
10284 |
<section> |
10285 |
<title>Gentoo Changes since 2005.1</title> |
10286 |
<subsection> |
10287 |
<title>Changes?</title> |
10288 |
<body> |
10289 |
|
10290 |
<p> |
10291 |
Gentoo is a fast-moving target. The following sections describe important |
10292 |
changes that affect a Gentoo installation. We only list those that have anything |
10293 |
in common with the installation, not with package changes that did not occur |
10294 |
during the installation. |
10295 |
</p> |
10296 |
|
10297 |
<p> |
10298 |
There have been no significant changes since. |
10299 |
</p> |
10300 |
|
10301 |
</body> |
10302 |
</subsection> |
10303 |
</section> |
10304 |
</sections> |
10305 |
|
10306 |
|
10307 |
|
10308 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc-bootloader.xml |
10309 |
|
10310 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
10311 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
10312 |
|
10313 |
Index: hb-install-ppc-bootloader.xml |
10314 |
=================================================================== |
10315 |
<?xml version='1.0' encoding='UTF-8'?> |
10316 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
10317 |
|
10318 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
10319 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
10320 |
|
10321 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc-bootloader.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
10322 |
|
10323 |
<sections> |
10324 |
|
10325 |
<version>5.3</version> |
10326 |
<date>2006-01-19</date> |
10327 |
|
10328 |
<section> |
10329 |
<title>Choosing a Bootloader</title> |
10330 |
<subsection> |
10331 |
<title>Introduction</title> |
10332 |
<body> |
10333 |
|
10334 |
<p> |
10335 |
Now that the kernel is configured and compiled, you'll need a <e>bootloader</e> |
10336 |
to start your new linux installation. The <e>bootloader</e> that you use will |
10337 |
depend upon the type of PPC machine you have. |
10338 |
</p> |
10339 |
|
10340 |
<p> |
10341 |
If you are using a NewWorld Apple or IBM machine, you need to use |
10342 |
<uri link="#yaboot">yaboot</uri>. OldWorld Apple machines have two options, |
10343 |
<uri link="#bootx">BootX</uri> (recommended) and <uri link="#quik">quik</uri>. |
10344 |
The Pegasos does not require a bootloader, but you will need to emerge |
10345 |
<uri link="#bootcreator">BootCreator</uri> to create SmartFirmware bootmenus. |
10346 |
</p> |
10347 |
|
10348 |
</body> |
10349 |
</subsection> |
10350 |
</section> |
10351 |
<section id="yaboot"> |
10352 |
<title>Default: Using yaboot</title> |
10353 |
<subsection> |
10354 |
<title>Introduction</title> |
10355 |
<body> |
10356 |
|
10357 |
<impo> |
10358 |
yaboot can only be used on NewWorld Apple and IBM systems! |
10359 |
</impo> |
10360 |
|
10361 |
<p> |
10362 |
In order to find the boot devices, yaboot needs access to the <path>/dev</path> |
10363 |
filesystem. To do this, you will need to "bind-map" the <path>/dev</path> |
10364 |
filesystem from the Installation CD to <path>/dev</path> inside of the chroot. |
10365 |
</p> |
10366 |
|
10367 |
<pre caption="Bind-mounting the /dev-filesystem"> |
10368 |
# <i>exit </i> # this will exit the chroot |
10369 |
# <i>mount -o bind /dev /mnt/gentoo/dev</i> |
10370 |
# <i>chroot /mnt/gentoo /bin/bash</i> |
10371 |
# <i>/usr/sbin/env-update && source /etc/profile </i> |
10372 |
</pre> |
10373 |
|
10374 |
<p> |
10375 |
To set up yaboot, you can use <c>yabootconfig</c> to automatically create a |
10376 |
configuration file for you. If you are installing Gentoo on a G5 (where |
10377 |
<c>yabootconfig</c> does not always work), or you plan to boot from firewire |
10378 |
or USB, you will need to manually configure yaboot. |
10379 |
</p> |
10380 |
|
10381 |
<note> |
10382 |
You will need to manually edit the yaboot.conf when using genkernel, even if |
10383 |
yabootconfig is used. The kernel image section of yaboot.conf should be |
10384 |
modified as follows: |
10385 |
</note> |
10386 |
|
10387 |
<pre caption="Adding genkernel boot arguments to yaboot.conf"> |
10388 |
<comment>########################################################### |
10389 |
## This section can be duplicated if you have more than one |
10390 |
## kernel or set of boot options - replace kernel-2.6.12 |
10391 |
## with the exact filename of your kernel. |
10392 |
###########################################################</comment> |
10393 |
image=/boot/kernel-2.6.12 |
10394 |
label=Linux |
10395 |
root=/dev/ram0 <comment># If using genkernel this is /dev/ram0</comment> |
10396 |
partition=3 |
10397 |
append="real_root=/dev/hda3 init=/linuxrc" |
10398 |
<comment># You can add additional kernel arguments to append such as |
10399 |
# rootdelay=10 for a USB/Firewire Boot</comment> |
10400 |
read-only |
10401 |
<comment>##########################################################</comment> |
10402 |
</pre> |
10403 |
|
10404 |
<ul> |
10405 |
<li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li> |
10406 |
<li> |
10407 |
<uri link="#manual_yaboot">Alternative: Manual yaboot Configuration</uri> |
10408 |
</li> |
10409 |
</ul> |
10410 |
|
10411 |
</body> |
10412 |
</subsection> |
10413 |
<subsection id="yabootconfig"> |
10414 |
<title>Default: Using yabootconfig</title> |
10415 |
<body> |
10416 |
|
10417 |
<p> |
10418 |
<c>yabootconfig</c> will auto-detect the partitions on your machine and will |
10419 |
set up dual and triple boot combinations with Linux, Mac OS, and Mac OS X. |
10420 |
</p> |
10421 |
|
10422 |
<p> |
10423 |
To use <c>yabootconfig</c>, your drive must have an Apple_Bootstrap partition, |
10424 |
and <path>/etc/fstab</path> must be configured with your Linux partitions. Both |
10425 |
of these should have been done already in the steps above. To start, ensure that |
10426 |
you have the latest <c>yaboot</c> installed. |
10427 |
</p> |
10428 |
|
10429 |
<pre caption = "Installing yaboot with GRP"> |
10430 |
# <i>emerge --usepkg --update yaboot</i> |
10431 |
</pre> |
10432 |
|
10433 |
<p> |
10434 |
Now exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</c>. The |
10435 |
program will run and it will confirm the location of the bootstrap partition. |
10436 |
Type <c>Y</c> if it is correct. If not, double check <path>/etc/fstab</path>. |
10437 |
yabootconfig will then scan your system setup, create |
10438 |
<path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you. <c>mkofboot</c> |
10439 |
is used to format the Apple_Bootstrap partition, and install the yaboot |
10440 |
configuration file into it. After this enter the chroot again. |
10441 |
</p> |
10442 |
<pre caption="enter chroot"> |
10443 |
# <i>chroot /mnt/gentoo /bin/bash</i> |
10444 |
# <i>/usr/sbin/env-update && source /etc/profile</i> |
10445 |
</pre> |
10446 |
|
10447 |
<p> |
10448 |
You might want to verify the contents of <path>/etc/yaboot.conf</path>. If you |
10449 |
make changes to <path>/etc/yaboot.conf</path> (like setting the default/boot |
10450 |
OS), make sure to rerun <c>ybin -v</c> to apply changes to the Apple_Bootstrap |
10451 |
partition. |
10452 |
</p> |
10453 |
|
10454 |
<p> |
10455 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
10456 |
</p> |
10457 |
|
10458 |
</body> |
10459 |
</subsection> |
10460 |
<subsection id="manual_yaboot"> |
10461 |
<title>Alternative: Manual yaboot Configuration</title> |
10462 |
<body> |
10463 |
|
10464 |
<p> |
10465 |
First make sure you have the latest <c>yaboot</c> installed on your |
10466 |
system: |
10467 |
</p> |
10468 |
|
10469 |
<pre caption = "Installing yaboot"> |
10470 |
# <i>emerge --usepkg --update yaboot</i> |
10471 |
</pre> |
10472 |
|
10473 |
<p> |
10474 |
An example <path>yaboot.conf</path> file is given below, but you will need to |
10475 |
alter it to fit your needs. G5 users and users booting from firewire and USB |
10476 |
should be aware that their disks are seen as SCSI disks by the Linux kernel, so |
10477 |
you will need to substitute <path>/dev/hda</path> with <path>/dev/sda</path>). |
10478 |
</p> |
10479 |
|
10480 |
<pre caption = "/etc/yaboot.conf"> |
10481 |
<comment>## /etc/yaboot.conf |
10482 |
## |
10483 |
## run: "man yaboot.conf" for details. Do not make changes until you have!! |
10484 |
## see also: /usr/share/doc/yaboot/examples for example configurations. |
10485 |
## |
10486 |
## For a dual-boot menu, add one or more of: |
10487 |
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ |
10488 |
|
10489 |
## our bootstrap partition:</comment> |
10490 |
|
10491 |
boot=/dev/hda2 |
10492 |
|
10493 |
<comment>## ofboot is the openfirmware way to specify the bootstrap partition. |
10494 |
## If this isn't defined, yaboot fails on the G5 and some G4s (unless |
10495 |
## you pass the necessary arguments to the mkofboot/ybin program). |
10496 |
## hd:X means /dev/sdaX (or /dev/hdaX). |
10497 |
## |
10498 |
## G5 users should uncomment this line!! |
10499 |
|
10500 |
#ofboot=hd:2 |
10501 |
|
10502 |
## Users booting from firewire should use something like this line: |
10503 |
# ofboot=fw/node/sbp-2/disk@0: |
10504 |
|
10505 |
## Users booting from USB should use something like this line: |
10506 |
# ofboot=usb/disk@0: |
10507 |
|
10508 |
## hd: is shorthand for the first hard drive OpenFirmware sees</comment> |
10509 |
device=hd: |
10510 |
|
10511 |
<comment>## Firewire and USB users will need to specify the whole OF device name |
10512 |
## This can be found using ofpath, which is included with yaboot. |
10513 |
|
10514 |
# device=fw/node@0001d200e00d0207/sbp-2@c000/disk@0: |
10515 |
</comment> |
10516 |
|
10517 |
delay=5 |
10518 |
defaultos=macosx |
10519 |
timeout=30 |
10520 |
install=/usr/lib/yaboot/yaboot |
10521 |
magicboot=/usr/lib/yaboot/ofboot |
10522 |
|
10523 |
<comment>################# |
10524 |
## This section can be duplicated if you have more than one kernel or set of |
10525 |
## boot options - replace 2.6.9 with your kernel-version |
10526 |
#################</comment> |
10527 |
image=/boot/kernel-2.6.9 |
10528 |
label=Linux |
10529 |
root=/dev/hda3 |
10530 |
partition=3 |
10531 |
<comment># append="rootdelay=10" # Required for booting USB/Firewire</comment> |
10532 |
read-only |
10533 |
<comment>################## |
10534 |
|
10535 |
## G5 users and some G4 users should set |
10536 |
## macos=hd:13 |
10537 |
## macosx=hd:12 |
10538 |
## instead of the example values.</comment> |
10539 |
macos=/dev/hda13 |
10540 |
macosx=/dev/hda12 |
10541 |
enablecdboot |
10542 |
enableofboot |
10543 |
</pre> |
10544 |
|
10545 |
<p> |
10546 |
Once <path>yaboot.conf</path> is configured, run <c>mkofboot -v</c> to format |
10547 |
the Apple_bootstrap partition and install the settings. If you change |
10548 |
yaboot.conf after the Apple_bootstrap partition has been created, you can |
10549 |
update the settings by running <c>ybin -v</c> |
10550 |
</p> |
10551 |
|
10552 |
<p> |
10553 |
For more information on yaboot, take a look at the <uri |
10554 |
link="http://penguinppc.org/bootloaders/yaboot">yaboot project</uri>. For |
10555 |
now, continue the installation with <uri link="#reboot">Rebooting the |
10556 |
System</uri>. |
10557 |
</p> |
10558 |
|
10559 |
</body> |
10560 |
</subsection> |
10561 |
</section> |
10562 |
<section id="bootx"> |
10563 |
<title>Alternative: BootX</title> |
10564 |
<body> |
10565 |
|
10566 |
<impo> |
10567 |
BootX can only be used on OldWorld Apple systems! |
10568 |
</impo> |
10569 |
|
10570 |
<p> |
10571 |
Since BootX boots Linux from within MacOS, the kernel will need to be copied |
10572 |
from the Linux Partition to the MacOS partition. First, mount the MacOS |
10573 |
partition from outside of the chroot. Use <c>mac-fdisk -l</c> to find the |
10574 |
MacOS partition number, sda6 is used as an example here. Once the partition is |
10575 |
mounted, we'll copy the kernel to the system folder so BootX can find it. |
10576 |
</p> |
10577 |
|
10578 |
<pre caption="Copying the kernel to the MacOS partition"> |
10579 |
# <i>exit</i> |
10580 |
cdimage ~# <i>mkdir /mnt/mac</i> |
10581 |
cdimage ~# <i>mount /dev/sda6 /mnt/mac -t hfs</i> |
10582 |
cdimage ~# <i>cp /mnt/gentoo/usr/src/linux/vmlinux "/mnt/mac/System Folder/Linux Kernels"</i> |
10583 |
</pre> |
10584 |
|
10585 |
<p> |
10586 |
If genkernel is used, both the kernel and initrd will need to be copied to the |
10587 |
MacOS partition. |
10588 |
</p> |
10589 |
|
10590 |
<pre caption="Copying the Genkernel kernel and initrd to the MacOS partition"> |
10591 |
# <i>exit</i> |
10592 |
cdimage ~# <i>mkdir /mnt/mac</i> |
10593 |
cdimage ~# <i>mount /dev/sda6 /mnt/mac -t hfs</i> |
10594 |
cdimage ~# <i>cp /mnt/gentoo/boot/kernel-* "/mnt/mac/System Folder/Linux Kernels"</i> |
10595 |
cdimage ~# <i>cp /mnt/gentoo/boot/initramfs-* "/mnt/mac/System Folder"</i> |
10596 |
</pre> |
10597 |
|
10598 |
<p> |
10599 |
Now that the kernel is copied over, we'll need to reboot to set up BootX. |
10600 |
</p> |
10601 |
|
10602 |
<pre caption="Unmounting all partitions and rebooting"> |
10603 |
cdimage ~# <i>cd /</i> |
10604 |
cdimage ~# <i>umount /mnt/gentoo/proc /mnt/gentoo/dev /mnt/gentoo /mnt/mac</i> |
10605 |
cdimage ~# <i>reboot</i> |
10606 |
</pre> |
10607 |
|
10608 |
<p> |
10609 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
10610 |
booted again instead of MacOS. |
10611 |
</p> |
10612 |
|
10613 |
<p> |
10614 |
Once the machine has booted into MacOS, open the BootX control panel. If you're |
10615 |
not using genkernel, select <c>Options</c> and uncheck <c>Use specified RAM |
10616 |
disk</c>. If you are using genkernel, ensure that the genkernel initrd is |
10617 |
selected instead of the Installation CD initrd. If not using genkernel, |
10618 |
there is now an option to specify the machine's Linux root disk and partition. |
10619 |
Fill these in with the appropriate values. Depending upon the kernel |
10620 |
configuration, additional boot arguments may need to be applied. |
10621 |
</p> |
10622 |
|
10623 |
<p> |
10624 |
BootX can be configured to start Linux upon boot. If you do this, you will first |
10625 |
see your machine boot into MacOS then, during startup, BootX will load and start |
10626 |
Linux. See the <uri link="http://penguinppc.org/bootloaders/bootx/">BootX home |
10627 |
page</uri> for more information. |
10628 |
</p> |
10629 |
|
10630 |
<p> |
10631 |
Now reboot again and boot into Linux, then continue with <uri |
10632 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
10633 |
</p> |
10634 |
|
10635 |
</body> |
10636 |
</section> |
10637 |
<section id="quik"> |
10638 |
<title>Alternative: quik</title> |
10639 |
<body> |
10640 |
|
10641 |
<p> |
10642 |
quik allows OldWorld Macs to boot without MacOS. However, it isn't well |
10643 |
supported and has a number of quirks. If you have the option, it is recommended |
10644 |
that you use BootX instead since it is much more reliable and easier to set up |
10645 |
than quik. |
10646 |
</p> |
10647 |
|
10648 |
<p> |
10649 |
First, we'll need to install quik: |
10650 |
</p> |
10651 |
|
10652 |
<pre caption="Emerge quik"> |
10653 |
# <i>emerge quik</i> |
10654 |
</pre> |
10655 |
|
10656 |
<p> |
10657 |
Next, we'll need to set it up. Edit /etc/quik.conf and set your image to the |
10658 |
kernel that we copied to your boot partition. |
10659 |
</p> |
10660 |
|
10661 |
<pre caption="Configuring quik.conf"> |
10662 |
# Example of quik.conf |
10663 |
init-message = "Gentoo 2005.1\n" |
10664 |
partition = 2 <comment># This is the boot partition</comment> |
10665 |
root = /dev/hda4 |
10666 |
timeout = 30 |
10667 |
default = gentoo |
10668 |
image = /vmlinux-2.6.12 |
10669 |
label = gentoo |
10670 |
</pre> |
10671 |
|
10672 |
<p> |
10673 |
Your quik.conf file <e>must</e> be on the same disk as the quik boot images, |
10674 |
however it can be on a different partition on the same disk, although it is |
10675 |
recommended to move it to your boot partition. |
10676 |
</p> |
10677 |
|
10678 |
<pre caption="Moving quik.conf to /boot"> |
10679 |
# <i>mv /etc/quik.conf /boot/quik.conf</i> |
10680 |
</pre> |
10681 |
|
10682 |
<p> |
10683 |
We will now set your boot variables so that quik loads on boot. To do this, |
10684 |
we'll use a program called <c>nvsetenv</c>. The variables that you want to |
10685 |
set vary from machine to machine, it's best to find your machine's |
10686 |
<uri link="http://penguinppc.org/bootloaders/quik/quirks.php">quirks</uri> |
10687 |
before attempting this. |
10688 |
</p> |
10689 |
|
10690 |
<pre caption="Setting the boot variables"> |
10691 |
# <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> |
10692 |
# <i>nvsetenv output-device video</i> <comment># Check the quirks page, there are many variations here</comment> |
10693 |
# <i>nvsetenv input-device kbd</i> |
10694 |
# <i>nvsetenv boot-device scsi/sd@1:0</i> <comment># For SCSI</comment> |
10695 |
# <i>nvsetenv boot-device ata/ata-disk@0:0</i> <comment># For ATA</comment> |
10696 |
# <i>nvsetenv boot-file /boot/vmlinux-2.6.12 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> |
10697 |
# <i>nvsetenv boot-command boot</i> <comment># Set this to bye for MacOS and boot for Linux</comment> |
10698 |
</pre> |
10699 |
|
10700 |
<note> |
10701 |
It is also possible to change your boot variables from MacOS. Depending |
10702 |
upon the model, either |
10703 |
<uri link="http://penguinppc.org/bootloaders/quik/BootVars.sit.hqx">bootvars</uri> or |
10704 |
<uri link="ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin"> |
10705 |
Apple System Disk</uri> should be used. Please see the quik quirks page |
10706 |
above for more information. |
10707 |
</note> |
10708 |
|
10709 |
<p> |
10710 |
Now that we've set up our machine to boot, we'll need to make sure the boot |
10711 |
images are installed correctly. Run <c>quik -v -C /boot/quik.conf</c>. It |
10712 |
should tell you that it has installed the first stage QUIK boot block. |
10713 |
</p> |
10714 |
|
10715 |
<note> |
10716 |
If something has gone wrong, you can always reset your PRAM back to the default |
10717 |
values by holding down <c>command + option + p + r</c> before powering on your |
10718 |
machine. This will clear the values you set with nvsetenv and should allow you |
10719 |
to boot either a MacOS bootdisk or a Linux bootdisk. |
10720 |
</note> |
10721 |
|
10722 |
<p> |
10723 |
Now, continue the installation with |
10724 |
<uri link="#reboot">Rebooting the System</uri>. |
10725 |
</p> |
10726 |
|
10727 |
</body> |
10728 |
</section> |
10729 |
<section id="bootcreator"> |
10730 |
<title>Alternative: BootCreator</title> |
10731 |
<body> |
10732 |
|
10733 |
<impo> |
10734 |
BootCreator will build a nice SmartFirmware bootmenu written in Forth for the |
10735 |
Pegasos. |
10736 |
</impo> |
10737 |
|
10738 |
<p> |
10739 |
First make sure you have the latest <c>bootcreator</c> installed on your |
10740 |
system: |
10741 |
</p> |
10742 |
|
10743 |
<pre caption = "Installing bootcreator"> |
10744 |
# <i>emerge --usepkg --update bootcreator</i> |
10745 |
</pre> |
10746 |
|
10747 |
<p> |
10748 |
Now copy the file <path>/etc/bootmenu.example</path> into |
10749 |
<path>/etc/bootmenu</path> and edit it to your needs: |
10750 |
</p> |
10751 |
|
10752 |
<pre caption = "Edit the bootcreator config file"> |
10753 |
# <i>cp /etc/bootmenu.example /etc/bootmenu</i> |
10754 |
# <i>nano -w /etc/bootmenu</i> |
10755 |
</pre> |
10756 |
|
10757 |
<p> |
10758 |
Below you find a completed <path>/etc/bootmenu</path> config file. Alter it at |
10759 |
will. |
10760 |
</p> |
10761 |
|
10762 |
<pre caption = "bootcreator config file"> |
10763 |
<comment># |
10764 |
# Example description file for bootcreator 1.1 |
10765 |
#</comment> |
10766 |
|
10767 |
[VERSION] |
10768 |
1 |
10769 |
|
10770 |
[TITLE] |
10771 |
Boot Menu |
10772 |
|
10773 |
[SETTINGS] |
10774 |
AbortOnKey = false |
10775 |
Timeout = 9 |
10776 |
Default = 1 |
10777 |
|
10778 |
[SECTION] |
10779 |
Local HD -> Morphos (Normal) |
10780 |
ide:0 boot2.img ramdebug edebugflags="logkprintf" |
10781 |
|
10782 |
[SECTION] |
10783 |
Local HD -> Linux 2.6.12 (Normal) |
10784 |
ide:0 linux-2.6.12 video=radeonfb:1024x768@70 root=/dev/hda3 |
10785 |
|
10786 |
[SECTION] |
10787 |
Local HD -> Genkernel (Normal) |
10788 |
ide:0 kernelz-2.6.12 root=/dev/ram0 real_root=/dev/hda3 init=/linuxrc |
10789 |
</pre> |
10790 |
|
10791 |
<p> |
10792 |
Finally the <path>bootmenu</path> must be transfered into Forth and copied to |
10793 |
your boot partition, so that the SmartFirmware can read it. Therefore you have |
10794 |
to call <c>bootcreator</c>: |
10795 |
</p> |
10796 |
|
10797 |
<pre caption = "Install the bootmenu"> |
10798 |
# <i>bootcreator /etc/bootmenu /boot/menu</i> |
10799 |
</pre> |
10800 |
|
10801 |
<note> |
10802 |
Be sure to have a look into the SmartFirmware's settings when you reboot, that |
10803 |
<path>menu</path> is the file that will be loaded by default. |
10804 |
</note> |
10805 |
|
10806 |
<p> |
10807 |
For now, continue the installation with <uri link="#reboot">Rebooting the |
10808 |
System</uri>. |
10809 |
</p> |
10810 |
|
10811 |
|
10812 |
</body> |
10813 |
</section> |
10814 |
<section id="reboot"> |
10815 |
<title>Rebooting the System</title> |
10816 |
<subsection> |
10817 |
<body> |
10818 |
|
10819 |
<p> |
10820 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
10821 |
that one magical command you have been waiting for: <c>reboot</c>. |
10822 |
</p> |
10823 |
|
10824 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
10825 |
# <i>exit</i> |
10826 |
livecd ~# <i>umount /mnt/gentoo/proc /mnt/gentoo/dev /mnt/gentoo</i> |
10827 |
livecd ~# <i>reboot</i> |
10828 |
</pre> |
10829 |
|
10830 |
<p> |
10831 |
Once rebooted in your Gentoo installation, finish up with <uri |
10832 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
10833 |
</p> |
10834 |
|
10835 |
</body> |
10836 |
</subsection> |
10837 |
</section> |
10838 |
</sections> |
10839 |
|
10840 |
|
10841 |
|
10842 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc-disk.xml |
10843 |
|
10844 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
10845 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
10846 |
|
10847 |
Index: hb-install-ppc-disk.xml |
10848 |
=================================================================== |
10849 |
<?xml version='1.0' encoding='UTF-8'?> |
10850 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
10851 |
|
10852 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
10853 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
10854 |
|
10855 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc-disk.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
10856 |
|
10857 |
<sections> |
10858 |
|
10859 |
<version>5.1</version> |
10860 |
<date>2005-08-25</date> |
10861 |
|
10862 |
<section> |
10863 |
<title>Introduction to Block Devices</title> |
10864 |
<subsection> |
10865 |
<title>Block Devices</title> |
10866 |
<body> |
10867 |
|
10868 |
<p> |
10869 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
10870 |
and Linux in general, including Linux filesystems, partitions and block devices. |
10871 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
10872 |
you'll be guided through the process of setting up partitions and filesystems |
10873 |
for your Gentoo Linux installation. |
10874 |
</p> |
10875 |
|
10876 |
<p> |
10877 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
10878 |
probably the one that represents the first IDE drive in a Linux system, namely |
10879 |
<path>/dev/hda</path>. If your system uses SCSI or SATA drives, then your first |
10880 |
hard drive would be <path>/dev/sda</path>. |
10881 |
</p> |
10882 |
|
10883 |
<p> |
10884 |
The block devices above represent an abstract interface to the disk. User |
10885 |
programs can use these block devices to interact with your disk without worrying |
10886 |
about whether your drives are IDE, SCSI or something else. The program can |
10887 |
simply address the storage on the disk as a bunch of contiguous, |
10888 |
randomly-accessible 512-byte blocks. |
10889 |
</p> |
10890 |
|
10891 |
</body> |
10892 |
</subsection> |
10893 |
<subsection> |
10894 |
<title>Partitions</title> |
10895 |
<body> |
10896 |
|
10897 |
<p> |
10898 |
Although it is theoretically possible to use a full disk to house your Linux |
10899 |
system, this is almost never done in practice. Instead, full disk block devices |
10900 |
are split up in smaller, more manageable block devices. On most systems, |
10901 |
these are called <e>partitions</e>. |
10902 |
</p> |
10903 |
|
10904 |
</body> |
10905 |
</subsection> |
10906 |
</section> |
10907 |
<section> |
10908 |
<title>Designing a Partitioning Scheme</title> |
10909 |
<subsection> |
10910 |
<title>Default Partitioning Scheme</title> |
10911 |
<body> |
10912 |
|
10913 |
<p> |
10914 |
If you are not interested in drawing up a partitioning scheme for your system, |
10915 |
you can use the partitioning scheme we use throughout this book: |
10916 |
</p> |
10917 |
|
10918 |
<table> |
10919 |
<tr> |
10920 |
<th>Partition NewWorld</th> |
10921 |
<th>Partition OldWorld</th> |
10922 |
<th>Partition Pegasos</th> |
10923 |
<th>Partition RS/6000</th> |
10924 |
<th>Filesystem</th> |
10925 |
<th>Size</th> |
10926 |
<th>Description</th> |
10927 |
</tr> |
10928 |
<tr> |
10929 |
<ti><path>/dev/hda1</path></ti> |
10930 |
<ti><path>/dev/hda1</path></ti> |
10931 |
<ti>(Not applicable)</ti> |
10932 |
<ti>(Not applicable)</ti> |
10933 |
<ti>(Partition Map)</ti> |
10934 |
<ti>32k</ti> |
10935 |
<ti>Apple_partition_map</ti> |
10936 |
</tr> |
10937 |
<tr> |
10938 |
<ti><path>/dev/hda2</path></ti> |
10939 |
<ti>(Not needed)</ti> |
10940 |
<ti>(Not applicable)</ti> |
10941 |
<ti>(Not applicable)</ti> |
10942 |
<ti>(bootstrap)</ti> |
10943 |
<ti>800k</ti> |
10944 |
<ti>Apple_Bootstrap</ti> |
10945 |
</tr> |
10946 |
<tr> |
10947 |
<ti>(Not applicable)</ti> |
10948 |
<ti>(Not applicable)</ti> |
10949 |
<ti>(Not applicable)</ti> |
10950 |
<ti><path>/dev/sda1</path></ti> |
10951 |
<ti>(PReP Boot)</ti> |
10952 |
<ti>800k</ti> |
10953 |
<ti>Type 0x41</ti> |
10954 |
</tr> |
10955 |
<tr> |
10956 |
<ti>(Not applicable)</ti> |
10957 |
<ti><path>/dev/hda2</path> (If using quik)</ti> |
10958 |
<ti><path>/dev/hda1</path></ti> |
10959 |
<ti>(Not needed)</ti> |
10960 |
<ti>ext2</ti> |
10961 |
<ti>32MB</ti> |
10962 |
<ti>Boot partition</ti> |
10963 |
</tr> |
10964 |
<tr> |
10965 |
<ti><path>/dev/hda3</path></ti> |
10966 |
<ti><path>/dev/hda2</path> (<path>/dev/hda3</path> if using quik)</ti> |
10967 |
<ti><path>/dev/hda2</path></ti> |
10968 |
<ti><path>/dev/sda2</path></ti> |
10969 |
<ti>(swap)</ti> |
10970 |
<ti>512M</ti> |
10971 |
<ti>Swap partition, Type 0x82</ti> |
10972 |
</tr> |
10973 |
<tr> |
10974 |
<ti><path>/dev/hda4</path></ti> |
10975 |
<ti><path>/dev/hda3</path> (<path>/dev/hda4</path> if using quik)</ti> |
10976 |
<ti><path>/dev/hda3</path></ti> |
10977 |
<ti><path>/dev/sda3</path></ti> |
10978 |
<ti>ext3, xfs</ti> |
10979 |
<ti>Rest of the disk</ti> |
10980 |
<ti>Root partition, Type 0x83</ti> |
10981 |
</tr> |
10982 |
</table> |
10983 |
|
10984 |
<note> |
10985 |
There are some partitions named: <path>Apple_Driver63, Apple_Driver_ATA, |
10986 |
Apple_FWDriver, Apple_Driver_IOKit, Apple_Patches</path>. If you are not |
10987 |
planning to use MacOS 9 you can delete them, because MacOS X and Linux don't |
10988 |
need them. To delete them, either use parted or erase the whole disk by |
10989 |
initialing the partition map. |
10990 |
</note> |
10991 |
|
10992 |
<warn> |
10993 |
<c>parted</c> is able to resize partitions. On the Installation CD there |
10994 |
are patches included to resize HFS+ filesystem. Unfortunately it is not |
10995 |
possible to resize HFS+ journaled filesystems, even if the journaling has been |
10996 |
switchedoff in Mac OS X. Everything you do with resizing in parted you do it |
10997 |
on your own risk! Be sure to have a backup of your data! |
10998 |
</warn> |
10999 |
|
11000 |
<p> |
11001 |
If you are interested in knowing how big a partition should be, or even how many |
11002 |
partitions you need, read on. Otherwise continue now with |
11003 |
<uri link="#mac-fdisk"> Default: Using mac-fdisk (Apple) to Partition your Disk |
11004 |
</uri> or <uri link="#parted">Alternative: Using parted (IBM/Pegasos) to |
11005 |
Partition your Disk</uri>. |
11006 |
</p> |
11007 |
|
11008 |
</body> |
11009 |
</subsection> |
11010 |
<subsection> |
11011 |
<title>How Many and How Big?</title> |
11012 |
<body> |
11013 |
|
11014 |
<p> |
11015 |
The number of partitions is highly dependent on your environment. For instance, |
11016 |
if you have lots of users, you will most likely want to have your |
11017 |
<path>/home</path> separate as it increases security and makes backups easier. |
11018 |
If you are installing Gentoo to perform as a mailserver, your <path>/var</path> |
11019 |
should be separate as all mails are stored inside <path>/var</path>. A good |
11020 |
choice of filesystem will then maximise your performance. Gameservers will have |
11021 |
a separate <path>/opt</path> as most gaming servers are installed there. The |
11022 |
reason is similar for <path>/home</path>: security and backups. You will |
11023 |
definitely want to keep <path>/usr</path> big: not only will it contain the |
11024 |
majority of applications, the Portage tree alone takes around 500 Mbyte |
11025 |
excluding the various sources that are stored in it. |
11026 |
</p> |
11027 |
|
11028 |
<p> |
11029 |
As you can see, it very much depends on what you want to achieve. Separate |
11030 |
partitions or volumes have the following advantages: |
11031 |
</p> |
11032 |
|
11033 |
<ul> |
11034 |
<li> |
11035 |
You can choose the best performing filesystem for each partition or volume |
11036 |
</li> |
11037 |
<li> |
11038 |
Your entire system cannot run out of free space if one defunct tool is |
11039 |
continuously writing files to a partition or volume |
11040 |
</li> |
11041 |
<li> |
11042 |
If necessary, file system checks are reduced in time, as multiple checks can |
11043 |
be done in parallel (although this advantage is more with multiple disks than |
11044 |
it is with multiple partitions) |
11045 |
</li> |
11046 |
<li> |
11047 |
Security can be enhanced by mounting some partitions or volumes read-only, |
11048 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
11049 |
</li> |
11050 |
</ul> |
11051 |
|
11052 |
<p> |
11053 |
However, multiple partitions have one big disadvantage: if not configured |
11054 |
properly, you might result in having a system with lots of free space on one |
11055 |
partition and none on another. There is also a 15-partition limit for SCSI and |
11056 |
SATA. |
11057 |
</p> |
11058 |
|
11059 |
</body> |
11060 |
</subsection> |
11061 |
</section> |
11062 |
<section id="mac-fdisk"> |
11063 |
<title>Default: Using mac-fdisk (Apple) Partition your Disk</title> |
11064 |
<body> |
11065 |
|
11066 |
<p> |
11067 |
At this point, create your partitions using <c>mac-fdisk</c>: |
11068 |
</p> |
11069 |
|
11070 |
<pre caption="Starting mac-fdisk"> |
11071 |
# <i>mac-fdisk /dev/hda</i> |
11072 |
</pre> |
11073 |
|
11074 |
<p> |
11075 |
First delete the partitions you have cleared previously to make room for your |
11076 |
Linux partitions. Use <c>d</c> in <c>mac-fdisk</c> to delete those partition(s). |
11077 |
It will ask for the partition number to delete. Usually the first partition on |
11078 |
NewWorld machines (Apple_partition_map) could not be deleted. |
11079 |
</p> |
11080 |
|
11081 |
<p> |
11082 |
Second, create an <e>Apple_Bootstrap</e> partition by using <c>b</c>. It will |
11083 |
ask for what block you want to start. Enter the number of your first free |
11084 |
partition, followed by a <c>p</c>. For instance this is <c>2p</c>. |
11085 |
</p> |
11086 |
|
11087 |
<note> |
11088 |
This partition is <e>not</e> a <path>/boot</path> partition. It is not used by |
11089 |
Linux at all; you don't have to place any filesystem on it and you should never |
11090 |
mount it. Apple users don't need an extra partition for <path>/boot</path>. |
11091 |
</note> |
11092 |
|
11093 |
<p> |
11094 |
Now create a swap partition by pressing <c>c</c>. Again <c>mac-fdisk</c> will |
11095 |
ask for what block you want to start this partition from. As we used <c>2</c> |
11096 |
before to create the Apple_Bootstrap partition, you now have to enter |
11097 |
<c>3p</c>. When you're asked for the size, enter <c>512M</c> (or whatever size |
11098 |
you want -- 512MB is recommended though). When asked for a name, enter <c>swap</c> |
11099 |
(mandatory). |
11100 |
</p> |
11101 |
|
11102 |
<p> |
11103 |
To create the root partition, enter <c>c</c>, followed by <c>4p</c> to select |
11104 |
from what block the root partition should start. When asked for the size, enter |
11105 |
<c>4p</c> again. <c>mac-fdisk</c> will interpret this as "Use all available |
11106 |
space". When asked for the name, enter <c>root</c> (mandatory). |
11107 |
</p> |
11108 |
|
11109 |
<p> |
11110 |
To finish up, write the partition to the disk using <c>w</c> and <c>q</c> to |
11111 |
quit <c>mac-fdisk</c>. |
11112 |
</p> |
11113 |
|
11114 |
<note> |
11115 |
To make sure everything is ok, you should run mac-fdisk once more and check |
11116 |
whether all the partitions are there. If you don't see any of the partitions |
11117 |
you created, or the changes you made, you should reinitialize your partitions |
11118 |
by pressing "i" in mac-fdisk. Note that this will recreate the partition map |
11119 |
and thus remove all your partitions. |
11120 |
</note> |
11121 |
|
11122 |
<p> |
11123 |
Now that your partitions are created, you can continue with <uri |
11124 |
link="#filesystems">Creating Filesystems</uri>. |
11125 |
</p> |
11126 |
|
11127 |
</body> |
11128 |
</section> |
11129 |
<section id="parted"> |
11130 |
<title>Using parted (especially Pegasos) to Partition your Disk</title> |
11131 |
<body> |
11132 |
|
11133 |
<p> |
11134 |
<c>parted</c>, the Partition Editor, can now handle HFS+ partitions used by |
11135 |
Mac OS and Mac OS X. With this tool you can resize your Mac-partitions and |
11136 |
create space for your Linux partitions. Nevertheless, the example below |
11137 |
describes partitioning for Pegasos machines only. |
11138 |
</p> |
11139 |
|
11140 |
<p> |
11141 |
To begin let's fire up <c>parted</c>: |
11142 |
</p> |
11143 |
|
11144 |
<pre caption="Starting parted"> |
11145 |
# <i>parted /dev/hda</i> |
11146 |
</pre> |
11147 |
|
11148 |
<p> |
11149 |
If the drive is unpartitioned, run <c>mklabel amiga</c> to create a new |
11150 |
disklabel for the drive. |
11151 |
</p> |
11152 |
|
11153 |
<p> |
11154 |
You can type <c>print</c> at any time in parted to display the current partition |
11155 |
table. If at any time you change your mind or made a mistake you can press |
11156 |
<c>Ctrl-c</c> to abort parted. |
11157 |
</p> |
11158 |
|
11159 |
<p> |
11160 |
If you intend to also install MorphOS on your Pegasos create an affs1 filesystem |
11161 |
named "BI0" (BI zero) at the start of the drive. 32MB should be more than enough |
11162 |
to store the MorphOS kernel. If you have a Pegasos I or intend to use reiserfs or |
11163 |
xfs, you will also have to store your Linux kernel on this partition (the |
11164 |
Pegasos II can only boot from ext2/ext3 or affs1 partitions). To create the partition run |
11165 |
<c>mkpart primary affs1 START END</c> where <c>START</c> and <c>END</c> should |
11166 |
be replaced with the megabyte range (e.g. <c>0 32</c> creates a 32 MB partition |
11167 |
starting at 0MB and ending at 32MB. |
11168 |
</p> |
11169 |
|
11170 |
<p> |
11171 |
You need to create two partitions for Linux, one root filesystem for all your |
11172 |
program files etc, and one swap partition. To create the root filesystem you |
11173 |
must first decide which filesystem to use. Possible options are ext2, ext3, |
11174 |
reiserfs and xfs. Unless you know what you are doing, use ext3. Run |
11175 |
<c>mkpart primary ext3 START END</c> to create an ext3 partition. Again, replace |
11176 |
<c>START</c> and <c>END</c> with the megabyte start and stop marks for the |
11177 |
partition. |
11178 |
</p> |
11179 |
|
11180 |
<p> |
11181 |
It is generally recommended that you create a swap partition the same size as |
11182 |
the amount of RAM in your computer times two. You will probably get away with a |
11183 |
smaller swap partition unless you intend to run a lot of applications at the |
11184 |
same time (although at least 512MB is recommended). To create the swap |
11185 |
partition, run <c>mkpart primary linux-swap START END</c>. |
11186 |
</p> |
11187 |
|
11188 |
<p> |
11189 |
Write down the partition minor numbers as they are required during the |
11190 |
installation process. To display the minor numbers run <c>print</c>. Your drives |
11191 |
are accessed as <path>/dev/hdaX</path> where X is replaced with the minor number |
11192 |
of the partition. |
11193 |
</p> |
11194 |
|
11195 |
<p> |
11196 |
When you are done in parted simply run <c>quit</c>. |
11197 |
</p> |
11198 |
|
11199 |
</body> |
11200 |
</section> |
11201 |
<section id="filesystems"> |
11202 |
<title>Creating Filesystems</title> |
11203 |
<subsection> |
11204 |
<title>Introduction</title> |
11205 |
<body> |
11206 |
|
11207 |
<p> |
11208 |
Now that your partitions are created, it is time to place a filesystem on them. |
11209 |
If you don't care about what filesystem to choose and are happy with what we use |
11210 |
as default in this handbook, continue with <uri |
11211 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
11212 |
Otherwise read on to learn about the available filesystems... |
11213 |
</p> |
11214 |
|
11215 |
</body> |
11216 |
</subsection> |
11217 |
<subsection> |
11218 |
<title>Filesystems?</title> |
11219 |
<body> |
11220 |
|
11221 |
<p> |
11222 |
Several filesystems are available. ext2, ext3, ReiserFS and XFS have been found |
11223 |
stable on the PPC architecture. |
11224 |
</p> |
11225 |
|
11226 |
<p> |
11227 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
11228 |
journaling, which means that routine ext2 filesystem checks at startup time can |
11229 |
be quite time-consuming. There is now quite a selection of newer-generation |
11230 |
journaled filesystems that can be checked for consistency very quickly and are |
11231 |
thus generally preferred over their non-journaled counterparts. Journaled |
11232 |
filesystems prevent long delays when you boot your system and your filesystem |
11233 |
happens to be in an inconsistent state. |
11234 |
</p> |
11235 |
|
11236 |
<p> |
11237 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
11238 |
journaling for fast recovery in addition to other enhanced journaling modes like |
11239 |
full data and ordered data journaling. ext3 is a very good and reliable |
11240 |
filesystem. It has an additional hashed b-tree indexing option that enables |
11241 |
high performance in almost all situations. You can enable this indexing by |
11242 |
adding <c>-O dir_index</c> to the <c>mke2fs</c> command. In short, ext3 is an |
11243 |
excellent filesystem. |
11244 |
</p> |
11245 |
|
11246 |
<p> |
11247 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
11248 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
11249 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
11250 |
extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is |
11251 |
solid and usable as both general-purpose filesystem and for extreme cases such |
11252 |
as the creation of large filesystems, the use of many small files, very large |
11253 |
files and directories containing tens of thousands of files. |
11254 |
</p> |
11255 |
|
11256 |
<p> |
11257 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
11258 |
feature-set and is optimized for scalability. We only recommend using this |
11259 |
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
11260 |
an uninterruptible power supply. Because XFS aggressively caches in-transit data |
11261 |
in RAM, improperly designed programs (those that don't take proper precautions |
11262 |
when writing files to disk and there are quite a few of them) can lose a good |
11263 |
deal of data if the system goes down unexpectedly. |
11264 |
</p> |
11265 |
|
11266 |
</body> |
11267 |
</subsection> |
11268 |
<subsection id="filesystems-apply"> |
11269 |
<title>Applying a Filesystem to a Partition</title> |
11270 |
<body> |
11271 |
|
11272 |
<p> |
11273 |
To create a filesystem on a partition or volume, there are tools available for |
11274 |
each possible filesystem: |
11275 |
</p> |
11276 |
|
11277 |
<table> |
11278 |
<tr> |
11279 |
<th>Filesystem</th> |
11280 |
<th>Creation Command</th> |
11281 |
</tr> |
11282 |
<tr> |
11283 |
<ti>ext2</ti> |
11284 |
<ti><c>mkfs.ext2</c></ti> |
11285 |
</tr> |
11286 |
<tr> |
11287 |
<ti>ext3</ti> |
11288 |
<ti><c>mkfs.ext3</c></ti> |
11289 |
</tr> |
11290 |
<tr> |
11291 |
<ti>reiserfs</ti> |
11292 |
<ti><c>mkfs.reiserfs</c></ti> |
11293 |
</tr> |
11294 |
<tr> |
11295 |
<ti>xfs</ti> |
11296 |
<ti><c>mkfs.xfs</c></ti> |
11297 |
</tr> |
11298 |
</table> |
11299 |
|
11300 |
<p> |
11301 |
For instance, to have the root partition (<path>/dev/hda4</path> in our example) |
11302 |
in ext3 (as in our example), you would use: |
11303 |
</p> |
11304 |
|
11305 |
<pre caption="Applying a filesystem on a partition"> |
11306 |
# <i>mkfs.ext3 /dev/hda4</i> |
11307 |
</pre> |
11308 |
|
11309 |
<p> |
11310 |
Now create the filesystems on your newly created partitions (or logical |
11311 |
volumes). |
11312 |
</p> |
11313 |
|
11314 |
<note> |
11315 |
On the PegasosII your partition which holds the kernel must be ext2 or ext3. |
11316 |
NewWorld machines can boot from any of ext2, ext3, XFS, ReiserFS or even |
11317 |
HFS/HFS+ filesystems. On OldWorld machines booting with BootX, the kernel must |
11318 |
be placed on an HFS partition, but this will be completed when you configure |
11319 |
your bootloader. |
11320 |
</note> |
11321 |
|
11322 |
</body> |
11323 |
</subsection> |
11324 |
<subsection> |
11325 |
<title>Activating the Swap Partition</title> |
11326 |
<body> |
11327 |
|
11328 |
<p> |
11329 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
11330 |
</p> |
11331 |
|
11332 |
<pre caption="Creating a Swap signature"> |
11333 |
# <i>mkswap /dev/hda3</i> |
11334 |
</pre> |
11335 |
|
11336 |
<p> |
11337 |
To activate the swap partition, use <c>swapon</c>: |
11338 |
</p> |
11339 |
|
11340 |
<pre caption="Activating the swap partition"> |
11341 |
# <i>swapon /dev/hda3</i> |
11342 |
</pre> |
11343 |
|
11344 |
<p> |
11345 |
Create and activate the swap now. |
11346 |
</p> |
11347 |
|
11348 |
</body> |
11349 |
</subsection> |
11350 |
</section> |
11351 |
<section> |
11352 |
<title>Mounting</title> |
11353 |
<body> |
11354 |
|
11355 |
<p> |
11356 |
Now that your partitions are initialized and are housing a filesystem, it is |
11357 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
11358 |
create the necessary mount directories for every partition you created. As an |
11359 |
example we create a mount-point and mount the root partition: |
11360 |
</p> |
11361 |
|
11362 |
<pre caption="Mounting partitions"> |
11363 |
# <i>mkdir /mnt/gentoo</i> |
11364 |
# <i>mount /dev/hda4 /mnt/gentoo</i> |
11365 |
</pre> |
11366 |
|
11367 |
<note> |
11368 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
11369 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
11370 |
also holds for <path>/var/tmp</path>. |
11371 |
</note> |
11372 |
|
11373 |
|
11374 |
<p> |
11375 |
We will have to mount the proc filesystem (a virtual interface with the |
11376 |
kernel) on <path>/proc</path>. But first we will need to place our files on the |
11377 |
partitions. |
11378 |
</p> |
11379 |
|
11380 |
<p> |
11381 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
11382 |
Installation Files</uri>. |
11383 |
</p> |
11384 |
|
11385 |
</body> |
11386 |
</section> |
11387 |
</sections> |
11388 |
|
11389 |
|
11390 |
|
11391 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc-kernel.xml |
11392 |
|
11393 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
11394 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
11395 |
|
11396 |
Index: hb-install-ppc-kernel.xml |
11397 |
=================================================================== |
11398 |
<?xml version='1.0' encoding='UTF-8'?> |
11399 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
11400 |
|
11401 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
11402 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
11403 |
|
11404 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc-kernel.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
11405 |
|
11406 |
<sections> |
11407 |
|
11408 |
<version>5.4</version> |
11409 |
<date>2006-01-06</date> |
11410 |
|
11411 |
<section> |
11412 |
<title>Timezone</title> |
11413 |
<body> |
11414 |
|
11415 |
<p> |
11416 |
You first need to select your timezone so that your system knows where it is |
11417 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
11418 |
it to <path>/etc/localtime</path>. Please avoid the |
11419 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
11420 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
11421 |
</p> |
11422 |
|
11423 |
<pre caption="Setting the timezone information"> |
11424 |
# <i>ls /usr/share/zoneinfo</i> |
11425 |
<comment>(Suppose you want to use GMT)</comment> |
11426 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
11427 |
</pre> |
11428 |
|
11429 |
</body> |
11430 |
</section> |
11431 |
<section> |
11432 |
<title>Installing the Sources</title> |
11433 |
<subsection> |
11434 |
<title>Choosing a Kernel</title> |
11435 |
<body> |
11436 |
|
11437 |
<p> |
11438 |
The core around which all distributions are built is the Linux kernel. It is the |
11439 |
layer between the user programs and your system hardware. Gentoo provides its |
11440 |
users several possible kernel sources. A full listing with description is |
11441 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
11442 |
Guide</uri>. |
11443 |
</p> |
11444 |
|
11445 |
<p> |
11446 |
We suggest using either <c>vanilla-sources</c> or <c>gentoo-sources</c> on PPC, |
11447 |
which are both 2.6 kernels. The latter is available when you perform a |
11448 |
networkless installation. So let's continue with <c>emerge</c>'ing the kernel |
11449 |
sources. The <c>USE="-doc"</c> is necessary to avoid installing xorg-x11 or |
11450 |
other dependencies at this point. <c>USE="symlink"</c> is not necessary for a |
11451 |
new install, but ensures proper creation of the <path>/usr/src/linux</path> |
11452 |
symlink. |
11453 |
</p> |
11454 |
|
11455 |
<pre caption="Installing a kernel source"> |
11456 |
# <i>USE="-doc symlink" emerge gentoo-sources</i> |
11457 |
</pre> |
11458 |
|
11459 |
<!-- Removed, as we're trying to avoid specific kernel versions to improve HB |
11460 |
maintainability |
11461 |
<note> |
11462 |
The suggested sources at the time of the 2005.1 release are |
11463 |
<c>gentoo-sources-2.6.12-r6</c> and <c>vanilla-sources-2.6.12.2</c>. |
11464 |
</note> |
11465 |
--> |
11466 |
|
11467 |
<p> |
11468 |
If you take a look in <path>/usr/src</path> you should see a symlink named |
11469 |
<path>linux</path> pointing to your current kernel source. In this case, the |
11470 |
installed kernel source points to <c>gentoo-sources-2.6.12-r6</c>. Your version |
11471 |
may be different, so keep this in mind. |
11472 |
</p> |
11473 |
|
11474 |
<pre caption="Viewing the kernel source symlink"> |
11475 |
# <i>ls -l /usr/src/linux</i> |
11476 |
lrwxrwxrwx 1 root root 22 Mar 18 16:23 /usr/src/linux -> linux-2.6.12-gentoo-r6 |
11477 |
</pre> |
11478 |
|
11479 |
<p> |
11480 |
Now it is time to configure and compile your kernel source. You |
11481 |
can use <c>genkernel</c> for this, which will build a generic kernel as used |
11482 |
by the Installation CD. We explain the "manual" configuration first though, as |
11483 |
it is the best way to optimize your environment. |
11484 |
</p> |
11485 |
|
11486 |
<p> |
11487 |
If you want to manually configure your kernel, continue now with <uri |
11488 |
link="#manual">Default: Manual Configuration</uri>. If you want to use |
11489 |
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
11490 |
genkernel</uri> instead. |
11491 |
</p> |
11492 |
|
11493 |
</body> |
11494 |
</subsection> |
11495 |
</section> |
11496 |
<section id="manual"> |
11497 |
<title>Default: Manual Configuration</title> |
11498 |
<subsection> |
11499 |
<title>Introduction</title> |
11500 |
<body> |
11501 |
|
11502 |
<p> |
11503 |
Manually configuring a kernel is often seen as the most difficult procedure a |
11504 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
11505 |
couple of kernels you don't even remember that it was difficult ;) |
11506 |
</p> |
11507 |
|
11508 |
<p> |
11509 |
However, one thing <e>is</e> true: you must know your system when you start |
11510 |
configuring a kernel manually. Most information can be gathered by emerging |
11511 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
11512 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
11513 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
11514 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
11515 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
11516 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
11517 |
uses (it might provide you with a nice hint on what to enable). Another place |
11518 |
to look for clues as to what components to enable is to check the kernel |
11519 |
message logs from the successful boot that got you this far. Type <c>dmesg</c> |
11520 |
to see the kernel messages. |
11521 |
</p> |
11522 |
|
11523 |
<p> |
11524 |
Now, go to your kernel source directory, it's time to configure your kernel. |
11525 |
It is recommended that you add the default settings to your configuration by |
11526 |
first running <c>make defconfig</c>. After the default configuration has been |
11527 |
generated, run <c>make menuconfig</c> which will fire up an ncurses-based |
11528 |
configuration menu. |
11529 |
</p> |
11530 |
|
11531 |
<pre caption="Invoking menuconfig"> |
11532 |
# <i>cd /usr/src/linux</i> |
11533 |
# <i>make defconfig</i> |
11534 |
# <i>make menuconfig</i> |
11535 |
</pre> |
11536 |
|
11537 |
<p> |
11538 |
You will be greeted with several configuration sections. We'll first list some |
11539 |
options you must activate (otherwise Gentoo will not function, or not function |
11540 |
properly without additional tweaks). |
11541 |
</p> |
11542 |
|
11543 |
</body> |
11544 |
</subsection> |
11545 |
<subsection> |
11546 |
<title>Activating Required Options</title> |
11547 |
<body> |
11548 |
|
11549 |
<p> |
11550 |
First of all, activate the use of development and experimental code/drivers. |
11551 |
You need this, otherwise some very important code/drivers won't show up: |
11552 |
</p> |
11553 |
|
11554 |
<pre caption="Selecting experimental code/drivers, General setup"> |
11555 |
Code maturity level options ---> |
11556 |
[*] Prompt for development and/or incomplete code/drivers |
11557 |
General setup ---> |
11558 |
[*] Support for hot-pluggable devices |
11559 |
</pre> |
11560 |
|
11561 |
<p> |
11562 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
11563 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
11564 |
able to mount your partitions. Also select <c>/proc file system</c> and |
11565 |
<c>Virtual memory</c>. |
11566 |
</p> |
11567 |
|
11568 |
<pre caption="Selecting necessary file systems"> |
11569 |
File systems ---> |
11570 |
Pseudo Filesystems ---> |
11571 |
[*] /proc file system support |
11572 |
[*] Virtual memory file system support (former shm fs) |
11573 |
|
11574 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
11575 |
<*> Reiserfs support |
11576 |
<*> Ext3 journalling file system support |
11577 |
<*> Second extended fs support |
11578 |
<*> XFS filesystem support |
11579 |
</pre> |
11580 |
|
11581 |
<p> |
11582 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
11583 |
modem, you will need the following options in the kernel: |
11584 |
</p> |
11585 |
|
11586 |
<pre caption="Selecting PPPoE necessary drivers"> |
11587 |
Device Drivers ---> |
11588 |
Networking support ---> |
11589 |
<*> PPP (point-to-point protocol) support |
11590 |
<*> PPP support for async serial ports |
11591 |
<*> PPP support for sync tty ports |
11592 |
</pre> |
11593 |
|
11594 |
<p> |
11595 |
The two compression options won't harm but are not definitely needed, neither |
11596 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
11597 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
11598 |
</p> |
11599 |
|
11600 |
<p> |
11601 |
If you require it, don't forget to include support in the kernel for your |
11602 |
ethernet card. |
11603 |
</p> |
11604 |
|
11605 |
<p> |
11606 |
Users of NewWorld and OldWorld machines will want HFS support as well. OldWorld |
11607 |
users require it for copying compiled kernels to the MacOS partition. NewWorld |
11608 |
users require it for configuring the special Apple_Bootstrap partition: |
11609 |
</p> |
11610 |
|
11611 |
<pre caption="Activating HFS support"> |
11612 |
File Systems ---> |
11613 |
[*] HFS Support |
11614 |
</pre> |
11615 |
|
11616 |
<p> |
11617 |
At this time, kernel preemption is still unstable on PPC and may cause |
11618 |
compilation failures and random segfaults. It is <e>strongly</e> suggested |
11619 |
that you do not use this feature. |
11620 |
</p> |
11621 |
|
11622 |
<pre caption="Ensure the Preemptible Kernel Option is Off"> |
11623 |
Platform options ---> |
11624 |
[ ] Preemptible Kernel |
11625 |
</pre> |
11626 |
|
11627 |
<p> |
11628 |
If you're booting from Firewire, you'll need to enable these options. If you do |
11629 |
not want to compile in support, you'll need to include these modules and their |
11630 |
dependencies in an initrd. |
11631 |
</p> |
11632 |
|
11633 |
<pre caption="Enable support for firewire devices on boot"> |
11634 |
Device Drivers ---> |
11635 |
IEEE 1394 (FireWire) support ---> |
11636 |
<*> IEEE 1394 (FireWire) support |
11637 |
<*> OHCI-1394 support |
11638 |
<*> SBP-2 support (Harddisks etc.) |
11639 |
</pre> |
11640 |
|
11641 |
<p> |
11642 |
If you're booting from USB, you'll need to enable these options. If you do not |
11643 |
want to compile in support, you'll need to include these modules and their |
11644 |
dependencies in an initrd. |
11645 |
</p> |
11646 |
|
11647 |
<pre caption="Enable support for USB devices on boot"> |
11648 |
Device Drivers ---> |
11649 |
USB support ---> |
11650 |
<*> Support for Host-side USB |
11651 |
<*> OHCI HCD support |
11652 |
<*> USB Mass Storage support |
11653 |
</pre> |
11654 |
|
11655 |
<p> |
11656 |
Do not turn off kernel framebuffer support as it is required for a successful |
11657 |
boot. If you are using an NVIDIA based chipset, you should use the OpenFirmware |
11658 |
framebuffer. If you are using an ATI based chipset, you should select the |
11659 |
framebuffer driver based upon your chipset (Mach64, Rage128 or Radeon). |
11660 |
</p> |
11661 |
|
11662 |
<pre caption="Chosing a Framebuffer Driver"> |
11663 |
Device Drivers ---> |
11664 |
Graphics support ---> |
11665 |
<*> Support for frame buffer devices |
11666 |
[*] Open Firmware frame buffer device support |
11667 |
<*> ATI Radeon display support |
11668 |
<*> ATI Rage128 display support |
11669 |
<*> ATI Mach64 display support |
11670 |
Console display driver support ---> |
11671 |
<*> Framebuffer Console support |
11672 |
</pre> |
11673 |
|
11674 |
<note> |
11675 |
If you select more than one framebuffer device, it may default to a less than |
11676 |
optimal driver. Either use only one framebuffer device or specify which |
11677 |
to use by passing the driver to use to the kernel on boot such as |
11678 |
<c>video=radeonfb</c>. |
11679 |
</note> |
11680 |
|
11681 |
<p> |
11682 |
When you're done configuring your kernel, continue with <uri |
11683 |
link="#compiling">Compiling and Installing</uri>. |
11684 |
</p> |
11685 |
|
11686 |
</body> |
11687 |
</subsection> |
11688 |
<subsection id="compiling"> |
11689 |
<title>Compiling and Installing</title> |
11690 |
<body> |
11691 |
|
11692 |
<p> |
11693 |
Now that your kernel is configured, it is time to compile and install it. Exit |
11694 |
the configuration and run the commands which will compile the kernel: |
11695 |
</p> |
11696 |
|
11697 |
<pre caption="Compiling the kernel"> |
11698 |
# <i>make && make modules_install</i> |
11699 |
</pre> |
11700 |
|
11701 |
<p> |
11702 |
When the kernel has finished compiling, copy the kernel image to |
11703 |
<path>/boot</path> (be sure that it is mounted properly on the Pegasos). |
11704 |
</p> |
11705 |
|
11706 |
<pre caption="Installing the kernel"> |
11707 |
<comment>replace <kernel-version> with your kernel version</comment> |
11708 |
(Apple/IBM) # <i>cp vmlinux /boot/<kernel-version></i> |
11709 |
(Pegasos) # <i>cp arch/ppc/boot/images/zImage.chrp /boot/<kernel-version></i> |
11710 |
</pre> |
11711 |
|
11712 |
<p> |
11713 |
Now continue with <uri link="#kernel_modules">Installing Separate Kernel |
11714 |
Modules</uri>. |
11715 |
</p> |
11716 |
|
11717 |
</body> |
11718 |
</subsection> |
11719 |
</section> |
11720 |
<section id="kernel_modules"> |
11721 |
<title>Installing Separate Kernel Modules</title> |
11722 |
<subsection> |
11723 |
<title>Configuring the Modules</title> |
11724 |
<body> |
11725 |
|
11726 |
<p> |
11727 |
You should list the modules you want automatically loaded in |
11728 |
<path>/etc/modules.autoload.d/kernel-2.6</path>. |
11729 |
You can add extra options to the modules too if you want. |
11730 |
</p> |
11731 |
|
11732 |
<p> |
11733 |
To view all available modules, run the following <c>find</c> command. Don't |
11734 |
forget to substitute "<kernel version>" with the version of the kernel you |
11735 |
just compiled: |
11736 |
</p> |
11737 |
|
11738 |
<pre caption="Viewing all available modules"> |
11739 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
11740 |
</pre> |
11741 |
|
11742 |
<p> |
11743 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
11744 |
<path>kernel-2.6</path> file and enter the module |
11745 |
name in it. |
11746 |
</p> |
11747 |
|
11748 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
11749 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
11750 |
</pre> |
11751 |
|
11752 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
11753 |
3c59x |
11754 |
</pre> |
11755 |
|
11756 |
<p> |
11757 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
11758 |
your System</uri>. |
11759 |
</p> |
11760 |
|
11761 |
</body> |
11762 |
</subsection> |
11763 |
</section> |
11764 |
<section id="genkernel"> |
11765 |
<title>Alternative: Using genkernel</title> |
11766 |
<body> |
11767 |
|
11768 |
<p> |
11769 |
If you are reading this section, you have chosen to use our <c>genkernel</c> |
11770 |
script to configure your kernel for you. |
11771 |
</p> |
11772 |
|
11773 |
<p> |
11774 |
Now that your kernel source tree is installed, it's now time to compile your |
11775 |
kernel by using our <c>genkernel</c> script to automatically build a kernel for |
11776 |
you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
11777 |
way our Installation CD kernel is configured. This means that when you use |
11778 |
<c>genkernel</c> to build your kernel, your system will generally detect all |
11779 |
your hardware at boot-time, just like our Installation CD does. Because genkernel |
11780 |
doesn't require any manual kernel configuration, it is an ideal solution for |
11781 |
those users who may not be comfortable compiling their own kernels. |
11782 |
</p> |
11783 |
|
11784 |
<p> |
11785 |
Now, let's see how to use genkernel. First, emerge the genkernel ebuild: |
11786 |
</p> |
11787 |
|
11788 |
<pre caption="Emerging genkernel"> |
11789 |
# <i>emerge genkernel</i> |
11790 |
</pre> |
11791 |
|
11792 |
<p> |
11793 |
Next, copy over the kernel configuration used by the Installation CD to the |
11794 |
location where genkernel looks for the default kernel configuration: |
11795 |
</p> |
11796 |
|
11797 |
<pre caption="Copying over the Installation CD kernel config"> |
11798 |
# <i>zcat /proc/config.gz > /usr/share/genkernel/ppc/kernel-config-2.6</i> |
11799 |
</pre> |
11800 |
|
11801 |
<p> |
11802 |
If you are using firewire or USB to boot, you'll need to add modules to the |
11803 |
initrd. Edit <path>/usr/share/genkernel/ppc/modules_load</path> and change |
11804 |
<c>MODULES_FIREWIRE="ieee1394 ohci1394 sbp2"</c> for firewire support or |
11805 |
<c>MODULES_USB="usbcore ohci-hcd ehci-hcd usb-storage"</c> for USB support. |
11806 |
</p> |
11807 |
|
11808 |
|
11809 |
<p> |
11810 |
Now, compile your kernel sources by running <c>genkernel --genzimage all</c>. |
11811 |
For Pegasos, we will need to use a different config and create a zImage instead |
11812 |
of the vmlinux kernel used on Apple machines. Be aware, as <c>genkernel</c> |
11813 |
compiles a kernel that supports almost all hardware, this compilation can take |
11814 |
quite a while to finish! |
11815 |
</p> |
11816 |
|
11817 |
<p> |
11818 |
Note that, if your partition where the kernel should be located doesn't use ext2 |
11819 |
or ext3 as filesystem you might need to manually configure your kernel using |
11820 |
<c>genkernel --menuconfig --genzimage all</c> and add support for your |
11821 |
filesystem <e>in</e> the kernel (i.e. <e>not</e> as a module). Users of EVMS2 or |
11822 |
LVM2 will probably want to add <c>--evms2</c> or <c>--lvm2</c> as argument as |
11823 |
well. |
11824 |
</p> |
11825 |
|
11826 |
<pre caption="Running genkernel"> |
11827 |
# <i>genkernel --genzimage all</i> |
11828 |
</pre> |
11829 |
|
11830 |
<pre caption="Running genkernel on the Pegasos"> |
11831 |
# <i>genkernel --genzimage --kernel-config=/usr/share/genkernel/ppc/Pegasos all</i> |
11832 |
</pre> |
11833 |
|
11834 |
<p> |
11835 |
Once <c>genkernel</c> completes, a kernel, full set of modules and |
11836 |
<e>initial root disk</e> (initrd) will be created. We will use the kernel |
11837 |
and initrd when configuring a boot loader later in this document. Write |
11838 |
down the names of the kernel and initrd as you will need it when writing |
11839 |
the bootloader configuration file. The initrd will be started immediately after |
11840 |
booting to perform hardware autodetection (just like on the Installation CD) |
11841 |
before your "real" system starts up. Be sure to also copy down the required |
11842 |
boot arguments, these are required for a sucessful boot with genkernel. |
11843 |
</p> |
11844 |
|
11845 |
<pre caption="Checking the created kernel image name and initrd"> |
11846 |
# <i>ls /boot/kernel* /boot/initramfs*</i> |
11847 |
</pre> |
11848 |
|
11849 |
<p> |
11850 |
If you want your system to be more like the Installation CD you should, |
11851 |
when your Gentoo installation is over, emerge <c>coldplug</c>. While the |
11852 |
initrd autodetects hardware that is needed to boot your system, |
11853 |
<c>coldplug</c> autodetects everything else. <c>coldplug</c> is available as one |
11854 |
of the packages on the Package CD. |
11855 |
</p> |
11856 |
|
11857 |
<pre caption="Emerging and enabling coldplug"> |
11858 |
<comment>(Do this after the installation, during the GRP installation instructions)</comment> |
11859 |
# <i>emerge -k coldplug</i> |
11860 |
# <i>rc-update add coldplug boot</i> |
11861 |
</pre> |
11862 |
|
11863 |
<p> |
11864 |
If you want your system to react to hotplugging events, you will need to install |
11865 |
and setup <c>hotplug</c> as well: |
11866 |
</p> |
11867 |
|
11868 |
<pre caption="Emerging and enabling hotplug"> |
11869 |
# <i>emerge hotplug</i> |
11870 |
# <i>rc-update add hotplug default</i> |
11871 |
</pre> |
11872 |
|
11873 |
<p> |
11874 |
Now continue with <uri link="?part=1&chap=8">Configuring your System</uri>. |
11875 |
</p> |
11876 |
|
11877 |
</body> |
11878 |
</section> |
11879 |
|
11880 |
</sections> |
11881 |
|
11882 |
|
11883 |
|
11884 |
|
11885 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc-medium.xml |
11886 |
|
11887 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
11888 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
11889 |
|
11890 |
Index: hb-install-ppc-medium.xml |
11891 |
=================================================================== |
11892 |
<?xml version='1.0' encoding='UTF-8'?> |
11893 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
11894 |
|
11895 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
11896 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
11897 |
|
11898 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc-medium.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
11899 |
|
11900 |
<sections> |
11901 |
|
11902 |
<version>5.3</version> |
11903 |
<date>2005-11-29</date> |
11904 |
|
11905 |
<section> |
11906 |
<title>Hardware Requirements</title> |
11907 |
<subsection> |
11908 |
<title>Introduction</title> |
11909 |
<body> |
11910 |
|
11911 |
<p> |
11912 |
Before we start, we first list what hardware requirements you need to |
11913 |
successfully install Gentoo on your box. |
11914 |
</p> |
11915 |
|
11916 |
</body> |
11917 |
</subsection> |
11918 |
<subsection> |
11919 |
<title>Hardware Requirements</title> |
11920 |
<body> |
11921 |
|
11922 |
<table> |
11923 |
<tr> |
11924 |
<th>Apple NewWorld Machines</th> |
11925 |
<ti> |
11926 |
Power/PowerPC microprocessors (G3, G4, G5) such as iMac, eMac, iBook |
11927 |
PowerBook, Xserver, PowerMac |
11928 |
</ti> |
11929 |
</tr> |
11930 |
<tr> |
11931 |
<th>Apple OldWorld machines</th> |
11932 |
<ti> |
11933 |
Apple Machines with an OpenFirmware revision less than 3, such as the Beige |
11934 |
G3s, PCI PowerMacs and PCI PowerBooks. PCI based Apple Clones should also |
11935 |
be supported. |
11936 |
</ti> |
11937 |
</tr> |
11938 |
<tr> |
11939 |
<th>Genesi's Pegasos</th> |
11940 |
<ti> |
11941 |
Pegasos I/II, Open Desktop Workstation |
11942 |
</ti> |
11943 |
</tr> |
11944 |
<tr> |
11945 |
<th>IBM</th> |
11946 |
<ti> |
11947 |
RS/6000, iSeries, pSeries |
11948 |
</ti> |
11949 |
</tr> |
11950 |
<tr> |
11951 |
<th>Memory</th> |
11952 |
<ti>At least 64 MB</ti> |
11953 |
</tr> |
11954 |
<tr> |
11955 |
<th>Diskspace</th> |
11956 |
<ti>1.5 GB (excluding swap space)</ti> |
11957 |
</tr> |
11958 |
<tr> |
11959 |
<th>Swap space</th> |
11960 |
<ti>At least 256 MB</ti> |
11961 |
</tr> |
11962 |
</table> |
11963 |
|
11964 |
<p> |
11965 |
Be sure to read up on the <uri link="/doc/en/gentoo-ppc-faq.xml">Gentoo |
11966 |
PPC FAQ</uri> before you begin. |
11967 |
</p> |
11968 |
|
11969 |
</body> |
11970 |
</subsection> |
11971 |
</section> |
11972 |
<!-- Copy/paste of hb-install-x86-medium.xml, with s/x86/ppc/ --> |
11973 |
<!-- START --> |
11974 |
<section> |
11975 |
<title>The Gentoo Universal Installation CD</title> |
11976 |
<subsection> |
11977 |
<title>Introduction</title> |
11978 |
<body> |
11979 |
|
11980 |
<p> |
11981 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
11982 |
Such a tarball is an archive that contains a minimal environment from |
11983 |
which you can successfully install Gentoo Linux onto your system. |
11984 |
</p> |
11985 |
|
11986 |
<p> |
11987 |
Installations using a stage1 or stage2 tarball file are not documented in the |
11988 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
11989 |
FAQ</uri> on these matters. |
11990 |
</p> |
11991 |
|
11992 |
</body> |
11993 |
</subsection> |
11994 |
<subsection> |
11995 |
<title>Gentoo Universal Installation CD</title> |
11996 |
<body> |
11997 |
|
11998 |
<p> |
11999 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
12000 |
environment. It allows you to boot Linux from the CD. During the boot process |
12001 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
12002 |
Installation CDs are maintained by Gentoo developers. |
12003 |
</p> |
12004 |
|
12005 |
<p> |
12006 |
There currently are two Installation CDs available: |
12007 |
</p> |
12008 |
|
12009 |
<ul> |
12010 |
<li> |
12011 |
The Universal Installation CD contains everything you need to install |
12012 |
Gentoo. It provides stage3 files for common architectures, source code |
12013 |
for the extra applications you need to choose from and, of course, the |
12014 |
installation instructions for your architecture. |
12015 |
</li> |
12016 |
<li> |
12017 |
The Minimal Installation CD contains only a minimal environment that allows |
12018 |
you to boot up and configure your network so you can connect to the |
12019 |
Internet. It does not contain any additional files and cannot be used |
12020 |
during the current installation approach. |
12021 |
</li> |
12022 |
</ul> |
12023 |
|
12024 |
<p> |
12025 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
12026 |
additional resource that you can exploit during the installation of your Gentoo |
12027 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
12028 |
you to easily and quickly install additional applications (such as |
12029 |
OpenOffice.org, KDE, GNOME, ...) immediately after the Gentoo installation and |
12030 |
right before you update your Portage tree. |
12031 |
</p> |
12032 |
|
12033 |
<p> |
12034 |
The use of the Package CD is covered later in this document. |
12035 |
</p> |
12036 |
|
12037 |
</body> |
12038 |
</subsection> |
12039 |
</section> |
12040 |
<!-- STOP --> |
12041 |
<section> |
12042 |
<title>Download, Burn and Boot the Gentoo Universal Installation CD</title> |
12043 |
<subsection> |
12044 |
<title>Downloading and Burning the Installation CD</title> |
12045 |
<body> |
12046 |
|
12047 |
<p> |
12048 |
You can download the Universal Installation CD (and, if you want to, the |
12049 |
Packages CD as well) from one of our <uri |
12050 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located |
12051 |
in the <path>releases/ppc/2005.1/installcd</path> directory; |
12052 |
the Package CDs are located in the |
12053 |
<path>releases/ppc/2005.1/packagecd</path> directory. |
12054 |
</p> |
12055 |
|
12056 |
<p> |
12057 |
Inside those directories you'll find ISO-files. Those are full CD images which |
12058 |
you can write on a CD-R. |
12059 |
</p> |
12060 |
|
12061 |
<p> |
12062 |
After downloading the file, you can verify its integrity to see if it is |
12063 |
corrupted or not: |
12064 |
</p> |
12065 |
|
12066 |
<ul> |
12067 |
<li> |
12068 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
12069 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
12070 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows). |
12071 |
Verifying MD5 checksums with Mac OS X is described in the <uri |
12072 |
link="/doc/en/gentoo-ppc-faq.xml#doc_chap1">Gentoo PPC FAQ</uri>. |
12073 |
</li> |
12074 |
<li> |
12075 |
You can verify the cryptographic signature that we provide. You need to |
12076 |
obtain the public key we use (0x17072058) before you proceed though. |
12077 |
</li> |
12078 |
</ul> |
12079 |
|
12080 |
<p> |
12081 |
To fetch our public key using the GnuPG application, run the following command: |
12082 |
</p> |
12083 |
|
12084 |
<pre caption="Obtaining the public key"> |
12085 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 0x17072058</i> |
12086 |
</pre> |
12087 |
|
12088 |
<p> |
12089 |
Now verify the signature: |
12090 |
</p> |
12091 |
|
12092 |
<pre caption="Verify the cryptographic signature"> |
12093 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
12094 |
</pre> |
12095 |
|
12096 |
<p> |
12097 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
12098 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
12099 |
<c>K3B</c> here; more information can be found in our <uri |
12100 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
12101 |
</p> |
12102 |
|
12103 |
<ul> |
12104 |
<li> |
12105 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
12106 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
12107 |
path). |
12108 |
</li> |
12109 |
<li> |
12110 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
12111 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
12112 |
<c>Start</c>. |
12113 |
</li> |
12114 |
</ul> |
12115 |
|
12116 |
</body> |
12117 |
</subsection> |
12118 |
<subsection> |
12119 |
<title>Default: Booting the Installation CD with Yaboot</title> |
12120 |
<body> |
12121 |
|
12122 |
<p> |
12123 |
On NewWorld machines place the Installation CD in the CD-ROM and reboot the |
12124 |
system. When the system-start-bell sounds, simply hold down the 'C' until the |
12125 |
CD loads. |
12126 |
</p> |
12127 |
|
12128 |
<p> |
12129 |
After the Installation CD loaded, you will be greeted by a friendly welcome |
12130 |
message and a <e>boot:</e> prompt at the bottom of the screen. |
12131 |
</p> |
12132 |
|
12133 |
<p> |
12134 |
At this prompt you are able to select a kernel for the subarchitecture you use. |
12135 |
We provide <c>G3</c>, <c>G4</c> and <c>G5</c>. All kernels are built with |
12136 |
support for multiple CPUs, but they will boot on single processor machines as |
12137 |
well. |
12138 |
</p> |
12139 |
|
12140 |
<p> |
12141 |
You are also able to tweak some kernel options at this prompt. The following |
12142 |
table lists some of the available boot options you can add: |
12143 |
</p> |
12144 |
|
12145 |
<table> |
12146 |
<tr> |
12147 |
<th>Boot Option</th> |
12148 |
<th>Description</th> |
12149 |
</tr> |
12150 |
<tr> |
12151 |
<ti><c>video</c></ti> |
12152 |
<ti> |
12153 |
This option takes one of the following vendor-specific tags: |
12154 |
<c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, <c>aty128</c> or |
12155 |
<c>ofonly</c>. You can follow this tag with the resolution and refreshrate |
12156 |
you want to use. For instance <c>video=radeonfb:1280x1024@75</c>. If you are |
12157 |
uncertain what to choose, <c>ofonly</c> will most certainly work. |
12158 |
</ti> |
12159 |
</tr> |
12160 |
<tr> |
12161 |
<ti><c>nol3</c></ti> |
12162 |
<ti> |
12163 |
Disables level 3 cache on some PowerBooks (needed for at least the 17") |
12164 |
</ti> |
12165 |
</tr> |
12166 |
<tr> |
12167 |
<ti><c>dofirewire</c></ti> |
12168 |
<ti> |
12169 |
Enables support for IEEE1394 (FireWire) devices, like external harddisks. |
12170 |
</ti> |
12171 |
</tr> |
12172 |
<tr> |
12173 |
<ti><c>dopcmcia</c></ti> |
12174 |
<ti> |
12175 |
If you want to use PCMCIA devices during your installation (like PCMCIA |
12176 |
network cards) you have to enable this option. |
12177 |
</ti> |
12178 |
</tr> |
12179 |
</table> |
12180 |
|
12181 |
<p> |
12182 |
At this prompt, hit enter, and a complete Gentoo Linux environment will be |
12183 |
loaded from the CD. Continue with <uri link="#booted">And When You're |
12184 |
Booted...</uri>. |
12185 |
</p> |
12186 |
|
12187 |
</body> |
12188 |
</subsection> |
12189 |
<subsection> |
12190 |
<title>Alternative: Booting the Installation CD on a Pegasos</title> |
12191 |
<body> |
12192 |
|
12193 |
<p> |
12194 |
On the Pegasos simply insert the CD and at the SmartFirmware boot-prompt type |
12195 |
<c>boot cd /boot/menu</c>. This will open a small bootmenu where you can choose |
12196 |
between several preconfigured video configs. If you need any special boot |
12197 |
options you can append them to the command-line. For instance <c>boot cd |
12198 |
/boot/pegasos video=radeonfb:1280x1024@75 mem=256M</c>. The complete list of |
12199 |
kernel appends (in case something goes wrong and you need it) is preconfigured |
12200 |
in the kernel with <c>console=ttyS0,115200 console=tty0 init=/linuxrc |
12201 |
looptype=squashfs loop=/livecd.squashfs udev nodevfs cdroot root=/dev/ram0</c>. |
12202 |
</p> |
12203 |
|
12204 |
</body> |
12205 |
</subsection> |
12206 |
|
12207 |
<subsection> |
12208 |
<title>Alternative: Booting the Installation CD with BootX</title> |
12209 |
<body> |
12210 |
|
12211 |
<p> |
12212 |
If you have an OldWorld Mac the bootable portion of the livecd can't be used. |
12213 |
The most simple solution is to use MacOS to bootstrap into a Linux environment |
12214 |
with a tool called BootX. Boot floppies are being prepared for Macs without |
12215 |
MacOS, but they are not available at this time. |
12216 |
</p> |
12217 |
|
12218 |
<p> |
12219 |
First, download <uri link="http://penguinppc.org/projects/bootx/">BootX</uri> |
12220 |
and unpack the archive. Copy the the <c>BootX Extension</c> from the unpacked |
12221 |
archive into <c>Extensions Folder</c> and the BootX App Control Panel into |
12222 |
<c>Control Panels</c>, both of which are located in your MacOS System Folder. |
12223 |
Next, create a folder called "Linux Kernels" in your System folder and copy the |
12224 |
<c>G3G4</c> kernel from the CD to this folder. Finally, copy <c>G3G4.igz</c> |
12225 |
from the Installation CD <path>boot</path> folder into the MacOS |
12226 |
<c>System Folder</c>. |
12227 |
</p> |
12228 |
|
12229 |
<p> |
12230 |
To prepare BootX, start the BootX App Control Panel. First select the Options |
12231 |
dialog and check <c>Use Specified RAM Disk</c> and select <c>G3G4.igz</c> from |
12232 |
your System Folder. Continue back to the initial screen and ensure that the |
12233 |
ramdisk size is at least <c>32000</c>. Finally, set the kernel arguments as |
12234 |
shown below: |
12235 |
</p> |
12236 |
|
12237 |
<pre caption="BootX kernel arguments"> |
12238 |
cdroot root=/dev/ram0 init=linuxrc loop=livecd.squashfs looptype=squashfs console=tty0 nodevfs udev |
12239 |
</pre> |
12240 |
|
12241 |
<note> |
12242 |
The kernel parameters in the yaboot section above are also applicable here. |
12243 |
</note> |
12244 |
|
12245 |
<p> |
12246 |
Check once more to make sure the settings are correct and then save the |
12247 |
configuration. This saves typing just in case it doesn't boot or something is |
12248 |
missing. Press the Linux button at the top of the window to boot into the |
12249 |
Installation CD and continue with <uri link="#booted">And When |
12250 |
You're Booted...</uri> |
12251 |
</p> |
12252 |
|
12253 |
</body> |
12254 |
</subsection> |
12255 |
|
12256 |
<subsection id="booted"> |
12257 |
<title>And When You're Booted...</title> |
12258 |
<body> |
12259 |
|
12260 |
<p> |
12261 |
You will be greeted by a root ("#") prompt on the current console. You can also |
12262 |
switch to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get |
12263 |
back to the one you started on by pressing Alt-F1. Probably you have to hit |
12264 |
Alt-fn-Fx on Apple machines. |
12265 |
</p> |
12266 |
|
12267 |
<p> |
12268 |
If you are installing Gentoo on a system with a non-US keyboard, use |
12269 |
<c>loadkeys</c> to load the keymap for your keyboard. To list the available |
12270 |
keymaps, execute <c>ls /usr/share/keymaps/i386</c>. On NewWorld machines or the |
12271 |
Pegasos do not use the keymaps in <path>ppc</path> or <path>mac</path> as they |
12272 |
are for ADB-based OldWorld machines. |
12273 |
</p> |
12274 |
|
12275 |
<pre caption="Listing available keymaps"> |
12276 |
<comment>(PPC uses x86 keymaps on most systems. The mac/ppc keymaps provided |
12277 |
on the Installation CD are ADB keymaps and unusable with the Installation CD |
12278 |
kernel)</comment> |
12279 |
# <i>ls /usr/share/keymaps/i386</i> |
12280 |
</pre> |
12281 |
|
12282 |
<p> |
12283 |
Now load the keymap of your choice: |
12284 |
</p> |
12285 |
|
12286 |
<pre caption="Loading a keymap"> |
12287 |
# <i>loadkeys be-latin1</i> |
12288 |
</pre> |
12289 |
|
12290 |
<p> |
12291 |
Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
12292 |
</p> |
12293 |
|
12294 |
</body> |
12295 |
</subsection> |
12296 |
<subsection id="hardware"> |
12297 |
<title>Extra Hardware Configuration</title> |
12298 |
<body> |
12299 |
|
12300 |
<p> |
12301 |
When the Installation CD boots, it tries to detect all your hardware devices and |
12302 |
loads the appropriate kernel modules to support your hardware. In the |
12303 |
vast majority of cases, it does a very good job. However, in some cases, it may |
12304 |
not auto-load the kernel modules you need. If the PCI auto-detection missed some |
12305 |
of your system's hardware, you will have to load the appropriate kernel modules |
12306 |
manually. |
12307 |
</p> |
12308 |
|
12309 |
<p> |
12310 |
In the next example we try to load the <c>airport</c> module. This module |
12311 |
supports only the old Airport cards (b-net). AirportExtreme is not supported |
12312 |
under Linux: |
12313 |
</p> |
12314 |
|
12315 |
<pre caption="Loading kernel modules"> |
12316 |
# <i>modprobe airport</i> |
12317 |
</pre> |
12318 |
|
12319 |
</body> |
12320 |
</subsection> |
12321 |
<subsection> |
12322 |
<title>Optional: Tweaking Hard Disk Performance</title> |
12323 |
<body> |
12324 |
|
12325 |
<p> |
12326 |
If you are an advanced user, you might want to tweak the IDE hard disk |
12327 |
performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
12328 |
test the performance of your disk (execute it several times to get a |
12329 |
more precise impression): |
12330 |
</p> |
12331 |
|
12332 |
<pre caption="Testing disk performance"> |
12333 |
# <i>hdparm -tT /dev/hda</i> |
12334 |
</pre> |
12335 |
|
12336 |
<p> |
12337 |
To tweak, you can use any of the following examples (or experiment |
12338 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
12339 |
disk): |
12340 |
</p> |
12341 |
|
12342 |
<pre caption="Tweaking hard disk performance"> |
12343 |
<comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i> |
12344 |
<comment>Activate DMA + Safe Performance-enhancing Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
12345 |
</pre> |
12346 |
|
12347 |
</body> |
12348 |
</subsection> |
12349 |
<subsection id="useraccounts"> |
12350 |
<title>Optional: User Accounts</title> |
12351 |
<body> |
12352 |
|
12353 |
<p> |
12354 |
If you plan on giving other people access to your installation |
12355 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
12356 |
security reasons), you need to create the necessary user accounts and change |
12357 |
the root password. |
12358 |
</p> |
12359 |
|
12360 |
<p> |
12361 |
To change the root password, use the <c>passwd</c> utility: |
12362 |
</p> |
12363 |
|
12364 |
<pre caption="Changing the root password"> |
12365 |
# <i>passwd</i> |
12366 |
New password: <comment>(Enter your new password)</comment> |
12367 |
Re-enter password: <comment>(Re-enter your password)</comment> |
12368 |
</pre> |
12369 |
|
12370 |
<p> |
12371 |
To create a user account, we first enter their credentials, followed by |
12372 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
12373 |
In the next example, we create a user called "john". |
12374 |
</p> |
12375 |
|
12376 |
<pre caption="Creating a user account"> |
12377 |
# <i>useradd -m -G users john</i> |
12378 |
# <i>passwd john</i> |
12379 |
New password: <comment>(Enter john's password)</comment> |
12380 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
12381 |
</pre> |
12382 |
|
12383 |
<p> |
12384 |
You can change your user id from root to the newly created user by using |
12385 |
<c>su</c>: |
12386 |
</p> |
12387 |
|
12388 |
<pre caption="Changing user id"> |
12389 |
# <i>su - john</i> |
12390 |
</pre> |
12391 |
|
12392 |
</body> |
12393 |
</subsection> |
12394 |
<subsection> |
12395 |
<title>Optional: Viewing Documentation while Installing</title> |
12396 |
<body> |
12397 |
|
12398 |
<p> |
12399 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
12400 |
installation, make sure you have created a user account (see <uri |
12401 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
12402 |
go to a new terminal and log in. |
12403 |
</p> |
12404 |
|
12405 |
<p> |
12406 |
If you want to view the documentation on the CD you can immediately run |
12407 |
<c>links2</c> or even <c>links -g</c> for a graphical framebuffer browser to |
12408 |
read it: |
12409 |
</p> |
12410 |
|
12411 |
<pre caption="Viewing the on-CD documentation"> |
12412 |
# <i>links2 /mnt/cdrom/docs/html/index.html</i> |
12413 |
</pre> |
12414 |
|
12415 |
<p> |
12416 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
12417 |
more recent than the one provided on the CD. You can view it using <c>links2</c> |
12418 |
as well, but only after having completed the <e>Configuring your Network</e> |
12419 |
chapter (otherwise you won't be able to go on the Internet to view the |
12420 |
document): |
12421 |
</p> |
12422 |
|
12423 |
<pre caption="Viewing the Online Documentation"> |
12424 |
# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-ppc.xml</i> |
12425 |
</pre> |
12426 |
|
12427 |
<p> |
12428 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
12429 |
</p> |
12430 |
|
12431 |
</body> |
12432 |
</subsection> |
12433 |
<subsection> |
12434 |
<title>Optional: Starting the SSH Daemon</title> |
12435 |
<body> |
12436 |
|
12437 |
<p> |
12438 |
If you want to allow other users to access your computer during the |
12439 |
Gentoo installation (perhaps because those users are going to help you |
12440 |
install Gentoo, or even do it for you), you need to create a user |
12441 |
account for them and perhaps even provide them with your root password |
12442 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
12443 |
</p> |
12444 |
|
12445 |
<p> |
12446 |
To fire up the SSH daemon, execute the following command: |
12447 |
</p> |
12448 |
|
12449 |
<pre caption="Starting the SSH daemon"> |
12450 |
# <i>/etc/init.d/sshd start</i> |
12451 |
</pre> |
12452 |
|
12453 |
<p> |
12454 |
To be able to use sshd, you first need to set up your networking. Continue with |
12455 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
12456 |
</p> |
12457 |
|
12458 |
</body> |
12459 |
</subsection> |
12460 |
</section> |
12461 |
</sections> |
12462 |
|
12463 |
|
12464 |
|
12465 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc64-bootloader.xml |
12466 |
|
12467 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc64-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
12468 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc64-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
12469 |
|
12470 |
Index: hb-install-ppc64-bootloader.xml |
12471 |
=================================================================== |
12472 |
<?xml version='1.0' encoding='UTF-8'?> |
12473 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
12474 |
|
12475 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
12476 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
12477 |
|
12478 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc64-bootloader.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
12479 |
|
12480 |
<sections> |
12481 |
|
12482 |
<version>5.3</version> |
12483 |
<date>2006-01-20</date> |
12484 |
|
12485 |
<section> |
12486 |
<title>Making your Choice</title> |
12487 |
<subsection> |
12488 |
<title>Introduction</title> |
12489 |
<body> |
12490 |
|
12491 |
<p> |
12492 |
Now that your kernel is configured and compiled and the necessary system |
12493 |
configuration files are filled in correctly, it is time to install a |
12494 |
program that will fire up your kernel when you start the system. Such a |
12495 |
program is called a <e>bootloader</e>. |
12496 |
</p> |
12497 |
|
12498 |
<p> |
12499 |
On Linux/PPC64 we have only yaBoot as a bootloader until grub2 is |
12500 |
finished. |
12501 |
</p> |
12502 |
|
12503 |
</body> |
12504 |
</subsection> |
12505 |
</section> |
12506 |
<section id="yaboot"> |
12507 |
<title>Using yaBoot</title> |
12508 |
<subsection> |
12509 |
<title>Introduction</title> |
12510 |
<body> |
12511 |
|
12512 |
<impo> |
12513 |
For a 64bit userland use yaboot-static instead of yaboot, because yaboot won't |
12514 |
compile on 64bit userland systems. For a 32bit userland use yaboot as you |
12515 |
normally would. |
12516 |
</impo> |
12517 |
|
12518 |
<p> |
12519 |
There are two ways to configure yaBoot for your system. You can use the |
12520 |
new and improved <c>yabootconfig</c> included with |
12521 |
<path>yaboot-1.3.8-r1</path> and later to automatically set up yaboot. If |
12522 |
for some reason you do not want to run <c>yabootconfig</c> to |
12523 |
automatically set up <path>/etc/yaboot.conf</path> or you are installing Gentoo |
12524 |
on a G5 (on which <c>yabootconfig</c> does not always work), you can just edit |
12525 |
the sample file already installed on your system. |
12526 |
</p> |
12527 |
|
12528 |
<impo> |
12529 |
If you are installing on a G5 using an online install and have not used the |
12530 |
G5 optimized stages you must change what profile you are linked to now. If you |
12531 |
do not you will not get dependencies necessary for yaboot to run on Apple |
12532 |
equipment. In the command below replace <c>(userland)</c> with your chosen |
12533 |
userland bit level. If you are installing on a G5 using an offline install |
12534 |
you have to install these packages by hand. |
12535 |
</impo> |
12536 |
|
12537 |
<pre caption = "(ONLINE INSTALL FOR G5 USERS ONLY) Changing your profile"> |
12538 |
# <i>rm /etc/make.profile</i> |
12539 |
# <i>ln -sf /usr/portage/profiles/default-linux/ppc/2005.1/ppc64/(userland)/970/pmac /etc/make.profile</i> |
12540 |
</pre> |
12541 |
|
12542 |
<pre caption = "(OFFLINE INSTALL FOR G5 USERS ONLY) Installing Necessary File System Tools"> |
12543 |
# <i>emerge hfsutils hfsplusutils</i> |
12544 |
</pre> |
12545 |
|
12546 |
<pre caption = "Installing the bootloader"> |
12547 |
<comment>(64bit userland)</comment> |
12548 |
# <i>emerge --update yaboot-static</i> |
12549 |
<comment>(32bit userland)</comment> |
12550 |
# <i>emerge --update yaboot</i> |
12551 |
</pre> |
12552 |
|
12553 |
<impo> |
12554 |
yabootconfig/ybin won't work on IBM. You have to install yaboot another way: |
12555 |
<uri link="#yaboot-ibm">Using yaboot on IBM hardware</uri> |
12556 |
</impo> |
12557 |
|
12558 |
<note> |
12559 |
If your root filesystem uses the JFS filesystem, be sure to add <c>ro</c> as a |
12560 |
kernel parameter. JFS must be able to replay its log in read-only mode before it |
12561 |
gets mounted read-write. |
12562 |
</note> |
12563 |
|
12564 |
<ul> |
12565 |
<li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li> |
12566 |
<li> |
12567 |
<uri link="#manual_yaboot">Alternative: Manual yaBoot Configuration</uri> |
12568 |
</li> |
12569 |
</ul> |
12570 |
|
12571 |
</body> |
12572 |
</subsection> |
12573 |
<subsection id="yabootconfig"> |
12574 |
<title>Default: Using yabootconfig</title> |
12575 |
<body> |
12576 |
|
12577 |
<p> |
12578 |
<c>yabootconfig</c> will auto-detect the partitions on your machine and will |
12579 |
set up dual and triple boot combinations with Linux, Mac OS, and Mac OS |
12580 |
X. |
12581 |
</p> |
12582 |
|
12583 |
<p> |
12584 |
To use <c>yabootconfig</c>, your drive must have a bootstrap partition, and |
12585 |
<path>/etc/fstab</path> must be configured with your Linux partitions. Both of |
12586 |
these should have been done already in the steps above. To start, ensure that |
12587 |
you have the latest version of yaboot installed by running <c>emerge --update |
12588 |
yaboot-static</c>. This is necessary as the latest version will be available via |
12589 |
Portage, but it may not have made it into the stage files. |
12590 |
</p> |
12591 |
|
12592 |
<p> |
12593 |
Now run <c>yabootconfig</c>. The program will run and it will confirm |
12594 |
the location of the bootstrap partition. Type <c>Y</c> if it is correct. If |
12595 |
not, double check <path>/etc/fstab</path>. yabootconfig will then scan your |
12596 |
system setup, create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for |
12597 |
you. <c>mkofboot</c> is used to format the bootstrap partition, and install |
12598 |
the yaboot configuration file into it. |
12599 |
</p> |
12600 |
|
12601 |
<p> |
12602 |
You might want to verify the contents of <path>/etc/yaboot.conf</path>. If |
12603 |
you make changes to <path>/etc/yaboot.conf</path> (like setting the |
12604 |
default/boot OS), make sure to rerun <c>ybin -v</c> to apply changes to the |
12605 |
bootstrap partition. |
12606 |
</p> |
12607 |
|
12608 |
<p> |
12609 |
Now continue with <uri link="#reboot">Rebooting your System</uri>. |
12610 |
</p> |
12611 |
|
12612 |
</body> |
12613 |
</subsection> |
12614 |
<subsection id="manual_yaboot"> |
12615 |
<title>Alternative: Manual yaBoot Configuration</title> |
12616 |
<body> |
12617 |
|
12618 |
<p> |
12619 |
Below you find a completed <path>yaboot.conf</path> file. Alter it at |
12620 |
will. |
12621 |
</p> |
12622 |
|
12623 |
<pre caption = "/etc/yaboot.conf"> |
12624 |
<comment>## /etc/yaboot.conf |
12625 |
## |
12626 |
## run: "man yaboot.conf" for details. Do not make changes until you have!! |
12627 |
## see also: /usr/share/doc/yaboot/examples for example configurations. |
12628 |
## |
12629 |
## For a dual-boot menu, add one or more of: |
12630 |
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ |
12631 |
|
12632 |
## our bootstrap partition:</comment> |
12633 |
|
12634 |
boot=/dev/hda2 |
12635 |
|
12636 |
<comment>## ofboot is the openfirmware way to specify the bootstrap partition. |
12637 |
## If this isn't defined, yaboot fails on the G5 and some G4s (unless |
12638 |
## you pass the necessary arguments to the mkofboot/ybin program). |
12639 |
## hd:X means /dev/sdaX (or /dev/hdaX).</comment> |
12640 |
|
12641 |
ofboot=hd:2 |
12642 |
|
12643 |
<comment>## hd: is open firmware speak for hda</comment> |
12644 |
device=hd: |
12645 |
|
12646 |
delay=5 |
12647 |
defaultos=macosx |
12648 |
timeout=30 |
12649 |
install=/usr/lib/yaboot/yaboot |
12650 |
magicboot=/usr/lib/yaboot/ofboot |
12651 |
|
12652 |
<comment>################# |
12653 |
## This section can be duplicated if you have more than one kernel or set of |
12654 |
## boot options - replace 2.6.12-gentoo-r10 with your kernel-version |
12655 |
#################</comment> |
12656 |
image=/boot/kernel-2.6.12-gentoo-r10 |
12657 |
label=Linux |
12658 |
root=/dev/hda3 |
12659 |
partition=3 |
12660 |
read-only |
12661 |
|
12662 |
macos=hd:13 |
12663 |
macosx=hd:12 |
12664 |
enablecdboot |
12665 |
enableofboot |
12666 |
</pre> |
12667 |
|
12668 |
<p> |
12669 |
Once <path>yaboot.conf</path> is set up the way you want it, you run |
12670 |
<c>mkofboot -v</c> to install the settings in the bootstrap partition. |
12671 |
<e>Don't forget this!</e> Confirm when <c>mkofboot</c> asks you to create a new |
12672 |
filesystem. |
12673 |
</p> |
12674 |
|
12675 |
<p> |
12676 |
If all goes well, and you have the same |
12677 |
options as the sample above, your next reboot will give you a simple, |
12678 |
five-entry boot menu. If you update your yaboot config later on, you'll |
12679 |
just need to run <c>ybin -v</c> to update the bootstrap partition - |
12680 |
<c>mkofboot</c> is for initial setup only. |
12681 |
</p> |
12682 |
|
12683 |
<p> |
12684 |
For more information on yaboot, take a look at the <uri |
12685 |
link="http://penguinppc.org/projects/yaboot">yaboot project</uri>. For |
12686 |
now, continue the installation with <uri link="#reboot">Rebooting your |
12687 |
System</uri>. |
12688 |
</p> |
12689 |
|
12690 |
</body> |
12691 |
</subsection> |
12692 |
</section> |
12693 |
<section id="yaboot-ibm"> |
12694 |
<title>Using yaboot on IBM hardware</title> |
12695 |
<body> |
12696 |
|
12697 |
<p> |
12698 |
On IBM hardware you cannot run yabootconfig or ybin. You must proceed with the |
12699 |
following steps: |
12700 |
</p> |
12701 |
|
12702 |
<ul> |
12703 |
<li>Install yaboot-static</li> |
12704 |
<li>Run 'dd if=/usr/lib/yaboot/yaboot.chrp of=/dev/sdXX' (fill in XX |
12705 |
with your disk and partition for the PReP partition; this was in our |
12706 |
example /dev/sda1)</li> |
12707 |
<li>Next construct your own yaboot.conf file and place into /etc. |
12708 |
(Take a look at the config above, look into the man page of |
12709 |
yaboot.conf or look at the below yaboot.conf example)</li> |
12710 |
<li>Assuming your boot device in OF is pointing to the harddrive you |
12711 |
prep boot partition is on then it'll just work, otherwise at IPL time, |
12712 |
go into the multiboot menu and set the boot device to the one with |
12713 |
your prep boot partition.</li> |
12714 |
<li>That's it!</li> |
12715 |
</ul> |
12716 |
|
12717 |
<pre caption = "yaboot.conf for IBM hardware"> |
12718 |
device=disk: |
12719 |
partition=2 |
12720 |
root=/dev/sda2 |
12721 |
default=2.6.12-gentoo-r10 |
12722 |
timeout=50 |
12723 |
|
12724 |
image=/boot/kernel-2.6.12-gentoo-r10 |
12725 |
label=Linux |
12726 |
append="console=ttyS0,9600" |
12727 |
read-only |
12728 |
</pre> |
12729 |
|
12730 |
<p> |
12731 |
For POWER4, POWER5, and blade-based hardware where the PReP disk partition |
12732 |
and the disk partition that contains your kernel are on the same physical disk, |
12733 |
you can use a simplified yaboot.conf. The following should be sufficient: |
12734 |
</p> |
12735 |
|
12736 |
<pre caption="yaboot.conf for PReP hardware"> |
12737 |
default = linux |
12738 |
timeout = 100 |
12739 |
image=/boot/kernel-2.6.12-gentoo-r10 |
12740 |
label=linux |
12741 |
read-only |
12742 |
root = /dev/sda2 |
12743 |
append="root=/dev/sda2" |
12744 |
</pre> |
12745 |
|
12746 |
<p> |
12747 |
To verify that yaboot has been copied to the PReP partition: |
12748 |
</p> |
12749 |
|
12750 |
<pre caption="Verifying the yaboot install on PReP"> |
12751 |
# <i>dd if=/dev/sda1 count=10 | grep ELF</i> |
12752 |
Binary file (standard input) matches |
12753 |
10+0 records in |
12754 |
10+0 records out |
12755 |
</pre> |
12756 |
|
12757 |
<p> |
12758 |
A match signifies that yaboot was installed correctly. |
12759 |
</p> |
12760 |
|
12761 |
</body> |
12762 |
</section> |
12763 |
<section id="reboot"> |
12764 |
<title>Rebooting the System</title> |
12765 |
<subsection> |
12766 |
<body> |
12767 |
|
12768 |
<p> |
12769 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
12770 |
that one magical command you have been waiting for: <c>reboot</c>. |
12771 |
</p> |
12772 |
|
12773 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
12774 |
# <i>exit</i> |
12775 |
~# <i>cd</i> |
12776 |
~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
12777 |
~# <i>reboot</i> |
12778 |
</pre> |
12779 |
|
12780 |
<p> |
12781 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
12782 |
booted again instead of your new Gentoo system. |
12783 |
</p> |
12784 |
|
12785 |
<p> |
12786 |
Once rebooted in your Gentoo installation, finish up with <uri |
12787 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
12788 |
</p> |
12789 |
|
12790 |
</body> |
12791 |
</subsection> |
12792 |
</section> |
12793 |
|
12794 |
</sections> |
12795 |
|
12796 |
|
12797 |
|
12798 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc64-disk.xml |
12799 |
|
12800 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc64-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
12801 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc64-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
12802 |
|
12803 |
Index: hb-install-ppc64-disk.xml |
12804 |
=================================================================== |
12805 |
<?xml version='1.0' encoding='UTF-8'?> |
12806 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
12807 |
|
12808 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
12809 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
12810 |
|
12811 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc64-disk.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
12812 |
|
12813 |
<sections> |
12814 |
|
12815 |
<version>5.2</version> |
12816 |
<date>2006-01-20</date> |
12817 |
|
12818 |
<section> |
12819 |
<title>Introduction to Block Devices</title> |
12820 |
<subsection> |
12821 |
<title>Block Devices</title> |
12822 |
<body> |
12823 |
|
12824 |
<p> |
12825 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
12826 |
and Linux in general, including Linux filesystems, partitions and block devices. |
12827 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
12828 |
you'll be guided through the process of setting up partitions and filesystems |
12829 |
for your Gentoo Linux installation. |
12830 |
</p> |
12831 |
|
12832 |
<p> |
12833 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
12834 |
probably the one that represents the first IDE drive in a Linux system, namely |
12835 |
<path>/dev/hda</path>. If your system uses SCSI drives, then your first hard |
12836 |
drive would be <path>/dev/sda</path>. Serial ATA drives are also |
12837 |
<path>/dev/sda</path> even if they are IDE drives. |
12838 |
</p> |
12839 |
|
12840 |
<p> |
12841 |
The block devices above represent an abstract interface to the disk. User |
12842 |
programs can use these block devices to interact with your disk without worrying |
12843 |
about whether your drives are IDE, SCSI or something else. The program can |
12844 |
simply address the storage on the disk as a bunch of contiguous, |
12845 |
randomly-accessible 512-byte blocks. |
12846 |
</p> |
12847 |
|
12848 |
</body> |
12849 |
</subsection> |
12850 |
<subsection> |
12851 |
<title>Partitions and Slices</title> |
12852 |
<body> |
12853 |
|
12854 |
<p> |
12855 |
Although it is theoretically possible to use a full disk to house your Linux |
12856 |
system, this is almost never done in practice. Instead, full disk block devices |
12857 |
are split up in smaller, more manageable block devices. On most systems, |
12858 |
these are called <e>partitions</e>. Other architectures use a similar technique, |
12859 |
called <e>slices</e>. |
12860 |
</p> |
12861 |
|
12862 |
</body> |
12863 |
</subsection> |
12864 |
</section> |
12865 |
<section> |
12866 |
<title>Designing a Partitioning Scheme</title> |
12867 |
<subsection> |
12868 |
<title>Default Partitioning Scheme</title> |
12869 |
<body> |
12870 |
|
12871 |
<p> |
12872 |
If you are not interested in drawing up a partitioning scheme for your system, |
12873 |
you can use the partitioning scheme we use throughout this book: |
12874 |
</p> |
12875 |
|
12876 |
<table> |
12877 |
<tr> |
12878 |
<th>Partition</th> |
12879 |
<th>Filesystem</th> |
12880 |
<th>Size</th> |
12881 |
<th>Description</th> |
12882 |
</tr> |
12883 |
<tr> |
12884 |
<ti><path>/dev/sda1</path></ti> |
12885 |
<ti>Partition map</ti> |
12886 |
<ti>31.5k</ti> |
12887 |
<ti>Partition map</ti> |
12888 |
</tr> |
12889 |
<tr> |
12890 |
<ti><path>/dev/sda2</path></ti> |
12891 |
<ti>(bootstrap)</ti> |
12892 |
<ti>800k</ti> |
12893 |
<ti>Apple_Bootstrap</ti> |
12894 |
</tr> |
12895 |
<tr> |
12896 |
<ti><path>/dev/sda3</path></ti> |
12897 |
<ti>(swap)</ti> |
12898 |
<ti>512M</ti> |
12899 |
<ti>Swap partition</ti> |
12900 |
</tr> |
12901 |
<tr> |
12902 |
<ti><path>/dev/sda4</path></ti> |
12903 |
<ti>ext3</ti> |
12904 |
<ti>Rest of the disk</ti> |
12905 |
<ti>Root partition</ti> |
12906 |
</tr> |
12907 |
</table> |
12908 |
|
12909 |
<note> |
12910 |
There are some partitions named like this: <path>Apple_Driver43, |
12911 |
Apple_Driver_ATA, Apple_FWDriver, Apple_Driver_IOKit, |
12912 |
Apple_Patches</path>. If you are not planning to use MacOS 9 you can |
12913 |
delete them, because MacOS X and Linux don't need them. |
12914 |
You might have to use parted in order to delete them, as mac-fdisk can't delete them yet. |
12915 |
</note> |
12916 |
|
12917 |
<p> |
12918 |
If you are interested in knowing how big a partition should be, or even how |
12919 |
many partitions you need, read on. Otherwise continue now with |
12920 |
<uri link="#mac-fdisk">Apple G5: Using mac-fdisk to Partition your |
12921 |
Disk</uri> or <uri link="#fdisk">IBM pSeries: using fdisk to Partition |
12922 |
your Disk</uri> |
12923 |
</p> |
12924 |
|
12925 |
</body> |
12926 |
</subsection> |
12927 |
<subsection> |
12928 |
<title>How Many and How Big?</title> |
12929 |
<body> |
12930 |
|
12931 |
<p> |
12932 |
The number of partitions is highly dependent on your environment. For instance, |
12933 |
if you have lots of users, you will most likely want to have your |
12934 |
<path>/home</path> separate as it increases security and makes backups easier. |
12935 |
If you are installing Gentoo to perform as a mailserver, your |
12936 |
<path>/var</path> should be separate as all mails are stored inside |
12937 |
<path>/var</path>. A good choice of filesystem will then maximise your |
12938 |
performance. Gameservers will have a separate <path>/opt</path> as most gaming |
12939 |
servers are installed there. The reason is similar for <path>/home</path>: |
12940 |
security and backups. You will definitely want to keep <path>/usr</path> big: |
12941 |
not only will it contain the majority of applications, the Portage tree alone |
12942 |
takes around 500 Mbyte excluding the various sources that are stored in it. |
12943 |
</p> |
12944 |
|
12945 |
<p> |
12946 |
As you can see, it very much depends on what you want to achieve. Separate |
12947 |
partitions or volumes have the following advantages: |
12948 |
</p> |
12949 |
|
12950 |
<ul> |
12951 |
<li> |
12952 |
You can choose the best performing filesystem for each partition or volume |
12953 |
</li> |
12954 |
<li> |
12955 |
Your entire system cannot run out of free space if one defunct tool is |
12956 |
continuously writing files to a partition or volume |
12957 |
</li> |
12958 |
<li> |
12959 |
If necessary, file system checks are reduced in time, as multiple checks can |
12960 |
be done in parallel (although this advantage is more with multiple disks than |
12961 |
it is with multiple partitions) |
12962 |
</li> |
12963 |
<li> |
12964 |
Security can be enhanced by mounting some partitions or volumes read-only, |
12965 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
12966 |
</li> |
12967 |
</ul> |
12968 |
|
12969 |
<p> |
12970 |
However, multiple partitions have one big disadvantage: if not configured |
12971 |
properly, you might result in having a system with lots |
12972 |
of free space on one partition and none on another. There is also a 15-partition |
12973 |
limit for SCSI and SATA. |
12974 |
</p> |
12975 |
|
12976 |
</body> |
12977 |
</subsection> |
12978 |
</section> |
12979 |
<section id="mac-fdisk"> |
12980 |
<title>Default: Using mac-fdisk (Apple G5) Partition your Disk</title> |
12981 |
<body> |
12982 |
|
12983 |
<p> |
12984 |
At this point, create your partitions using <c>mac-fdisk</c>: |
12985 |
</p> |
12986 |
|
12987 |
<pre caption="Starting mac-fdisk"> |
12988 |
# <i>mac-fdisk /dev/sda</i> |
12989 |
</pre> |
12990 |
|
12991 |
<p> |
12992 |
First delete the partitions you have cleared previously to make room for your |
12993 |
Linux partitions. Use <c>d</c> in <c>mac-fdisk</c> to delete those partition(s). |
12994 |
It will ask for the partition number to delete. |
12995 |
</p> |
12996 |
|
12997 |
<p> |
12998 |
Second, create an <e>Apple_Bootstrap</e> partition by using <c>b</c>. It will |
12999 |
ask for what block you want to start. Enter the number of your first free |
13000 |
partition, followed by a <c>p</c>. For instance this is <c>2p</c>. |
13001 |
</p> |
13002 |
|
13003 |
<note> |
13004 |
This partition is <e>not</e> a "boot" partition. It is not used by Linux at all; |
13005 |
you don't have to place any filesystem on it and you should never mount it. PPC |
13006 |
users don't need an extra partition for <path>/boot</path>. |
13007 |
</note> |
13008 |
|
13009 |
<p> |
13010 |
Now create a swap partition by pressing <c>c</c>. Again <c>mac-fdisk</c> will |
13011 |
ask for what block you want to start this partition from. As we used <c>2</c> |
13012 |
before to create the Apple_Bootstrap partition, you now have to enter |
13013 |
<c>3p</c>. When you're asked for the size, enter <c>512M</c> (or whatever size |
13014 |
you want). When asked for a name, enter <c>swap</c> (mandatory). |
13015 |
</p> |
13016 |
|
13017 |
<p> |
13018 |
To create the root partition, enter <c>c</c>, followed by <c>4p</c> to select |
13019 |
from what block the root partition should start. When asked for the size, enter |
13020 |
<c>4p</c> again. <c>mac-fdisk</c> will interpret this as "Use all available |
13021 |
space". When asked for the name, enter <c>root</c> (mandatory). |
13022 |
</p> |
13023 |
|
13024 |
<p> |
13025 |
To finish up, write the partition to the disk using <c>w</c> and <c>q</c> to |
13026 |
quit <c>mac-fdisk</c>. |
13027 |
</p> |
13028 |
|
13029 |
<note> |
13030 |
To make sure everything is ok, you should run mac-fdisk once more and check whether all the partitions are there. |
13031 |
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. |
13032 |
Note that this will recreate the partition map and thus remove all your partitions. |
13033 |
</note> |
13034 |
|
13035 |
<p> |
13036 |
Now that your partitions are created, you can now continue with <uri |
13037 |
link="#filesystems">Creating Filesystems</uri>. |
13038 |
</p> |
13039 |
|
13040 |
</body> |
13041 |
</section> |
13042 |
<section id="fdisk"> |
13043 |
<title>IBM pSeries, iSeries and OpenPower: using fdisk to Partition your Disk</title> |
13044 |
<subsection> |
13045 |
<body> |
13046 |
|
13047 |
<note> |
13048 |
If you are planning to use a RAID disk array for your gentoo installation and |
13049 |
you are using POWER5-based hardware, you should now run <c>iprutils</c> to |
13050 |
format the disks to Advanced Function format and create the disk array. You |
13051 |
should also consider emerging this package after your install is complete. |
13052 |
</note> |
13053 |
|
13054 |
<p> |
13055 |
The following parts explain how to create the example partition layout |
13056 |
described previously, namely: |
13057 |
</p> |
13058 |
|
13059 |
<table> |
13060 |
<tr> |
13061 |
<th>Partition</th> |
13062 |
<th>Description</th> |
13063 |
</tr> |
13064 |
<tr> |
13065 |
<ti><path>/dev/sda1</path></ti> |
13066 |
<ti>PPC PReP Boot partition</ti> |
13067 |
</tr> |
13068 |
<tr> |
13069 |
<ti><path>/dev/sda2</path></ti> |
13070 |
<ti>Swap partition</ti> |
13071 |
</tr> |
13072 |
<tr> |
13073 |
<ti><path>/dev/sda3</path></ti> |
13074 |
<ti>Root partition</ti> |
13075 |
</tr> |
13076 |
</table> |
13077 |
|
13078 |
<p> |
13079 |
Change your partition layout according to your own preference. |
13080 |
</p> |
13081 |
|
13082 |
</body> |
13083 |
</subsection> |
13084 |
<subsection> |
13085 |
<title>Viewing the Current Partition Layout</title> |
13086 |
<body> |
13087 |
|
13088 |
<p> |
13089 |
<c>fdisk</c> is a popular and powerful tool to split your disk into |
13090 |
partitions. Fire up <c>fdisk</c> on your disk (in our example, we |
13091 |
use <path>/dev/sda</path>): |
13092 |
</p> |
13093 |
|
13094 |
<pre caption="Starting fdisk"> |
13095 |
# <i>fdisk /dev/sda</i> |
13096 |
</pre> |
13097 |
|
13098 |
<p> |
13099 |
Once in <c>fdisk</c>, you'll be greeted with a prompt that looks like |
13100 |
this: |
13101 |
</p> |
13102 |
|
13103 |
<pre caption="fdisk prompt"> |
13104 |
Command (m for help): |
13105 |
</pre> |
13106 |
|
13107 |
<p> |
13108 |
Type <c>p</c> to display your disk's current partition configuration: |
13109 |
</p> |
13110 |
|
13111 |
<pre caption="An example partition configuration"> |
13112 |
Command (m for help): p |
13113 |
|
13114 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
13115 |
141 heads, 63 sectors/track, 6761 cylinders |
13116 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
13117 |
|
13118 |
Device Boot Start End Blocks Id System |
13119 |
/dev/sda1 1 12 53266+ 83 Linux |
13120 |
/dev/sda2 13 233 981571+ 82 Linux swap |
13121 |
/dev/sda3 234 674 1958701+ 83 Linux |
13122 |
/dev/sda4 675 6761 27035410+ 5 Extended |
13123 |
/dev/sda5 675 2874 9771268+ 83 Linux |
13124 |
/dev/sda6 2875 2919 199836 83 Linux |
13125 |
/dev/sda7 2920 3008 395262 83 Linux |
13126 |
/dev/sda8 3009 6761 16668918 83 Linux |
13127 |
|
13128 |
Command (m for help): |
13129 |
</pre> |
13130 |
|
13131 |
<p> |
13132 |
This particular disk is configured to house six Linux filesystems |
13133 |
(each with a corresponding partition listed as "Linux") as well as a |
13134 |
swap partition (listed as "Linux swap"). |
13135 |
</p> |
13136 |
|
13137 |
</body> |
13138 |
</subsection> |
13139 |
<subsection> |
13140 |
<title>Removing all Partitions</title> |
13141 |
<body> |
13142 |
|
13143 |
<p> |
13144 |
We will first remove all existing partitions from the disk. Type |
13145 |
<c>d</c> to delete a partition. For instance, to delete an existing |
13146 |
<path>/dev/sda1</path>: |
13147 |
</p> |
13148 |
|
13149 |
<note> |
13150 |
If you don't want to delete all partitions just delete those you |
13151 |
want to delete. At this point the author recommends a backup of your |
13152 |
data to avoid the lose of it. |
13153 |
</note> |
13154 |
|
13155 |
<pre caption="Deleting a partition"> |
13156 |
Command (m for help): <i>d</i> |
13157 |
Partition number (1-4): <i>1</i> |
13158 |
</pre> |
13159 |
|
13160 |
<p> |
13161 |
The partition has been scheduled for deletion. It will no longer show up |
13162 |
if you type <c>p</c>, but it will not be erased until your changes have |
13163 |
been saved. If you made a mistake and want to abort without saving your |
13164 |
changes, type <c>q</c> immediately and hit enter and your partition will |
13165 |
not be deleted. |
13166 |
</p> |
13167 |
|
13168 |
<p> |
13169 |
Now, assuming that you do indeed want to wipe out all the partitions on |
13170 |
your system, repeatedly type <c>p</c> to print out a partition listing |
13171 |
and then type <c>d</c> and the number of the partition to delete it. |
13172 |
Eventually, you'll end up with a partition table with nothing in it: |
13173 |
</p> |
13174 |
|
13175 |
<pre caption="An empty partition table"> |
13176 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
13177 |
141 heads, 63 sectors/track, 6761 cylinders |
13178 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
13179 |
|
13180 |
Device Boot Start End Blocks Id System |
13181 |
|
13182 |
Command (m for help): |
13183 |
</pre> |
13184 |
|
13185 |
<p> |
13186 |
Now that the in-memory partition table is empty, we're ready to create |
13187 |
the partitions. We will use a default partitioning scheme as discussed |
13188 |
previously. Of course, don't follow these instructions to the letter if |
13189 |
you don't want the same partitioning scheme! |
13190 |
</p> |
13191 |
|
13192 |
</body> |
13193 |
</subsection> |
13194 |
<subsection> |
13195 |
<title>Creating the PPC PReP boot partition</title> |
13196 |
<body> |
13197 |
|
13198 |
<p> |
13199 |
We first create a small PReP boot partition. Type <c>n</c> to create a new |
13200 |
partition, then <c>p</c> to select a primary partition, followed by |
13201 |
<c>1</c> to select the first primary partition. When prompted for the |
13202 |
first cylinder, hit enter. When prompted for the last cylinder, type |
13203 |
<c>+7M</c> to create a partition 7 Mbyte in size. After you've done |
13204 |
this, type <c>t</c> to set the partition type, <c>1</c> to select the |
13205 |
partition you just created and then type in <c>41</c> to set the |
13206 |
partition type to "PPC PReP Boot". Finally, you'll need to mark the PReP |
13207 |
partition as bootable. |
13208 |
</p> |
13209 |
|
13210 |
<note> |
13211 |
The PReP partition has to be smaller than 8 MByte! |
13212 |
</note> |
13213 |
|
13214 |
<pre caption="Creating the PReP boot partition"> |
13215 |
Command (m for help): <i>p</i> |
13216 |
|
13217 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
13218 |
141 heads, 63 sectors/track, 6761 cylinders |
13219 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
13220 |
|
13221 |
Device Boot Start End Blocks Id System |
13222 |
|
13223 |
Command (m for help): <i>n</i> |
13224 |
Command action |
13225 |
e extended |
13226 |
p primary partition (1-4) |
13227 |
<i>p</i> |
13228 |
Partition number (1-4): <i>1</i> |
13229 |
First cylinder (1-6761, default 1): |
13230 |
Using default value 1 |
13231 |
Last cylinder or +size or +sizeM or +sizeK (1-6761, default |
13232 |
6761): <i>+8M</i> |
13233 |
|
13234 |
Command (m for help): <i>t</i> |
13235 |
Selected partition 1 |
13236 |
Hex code (type L to list codes): <i>41</i> |
13237 |
Changed system type of partition 1 to 41 (PPC PReP Boot) |
13238 |
|
13239 |
Command (m for help): <i>a</i> |
13240 |
Partition number (1-4): <i>1</i> |
13241 |
Command (m for help): |
13242 |
</pre> |
13243 |
|
13244 |
<p> |
13245 |
Now, when you type <c>p</c>, you should see the following partition information: |
13246 |
</p> |
13247 |
|
13248 |
<pre caption="Created boot partition"> |
13249 |
Command (m for help): <i>p</i> |
13250 |
|
13251 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
13252 |
141 heads, 63 sectors/track, 6761 cylinders |
13253 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
13254 |
|
13255 |
Device Boot Start End Blocks Id System |
13256 |
/dev/sda1 * 1 3 13293 41 PPC PReP Boot |
13257 |
|
13258 |
Command (m for help): |
13259 |
</pre> |
13260 |
</body> |
13261 |
</subsection> |
13262 |
<subsection> |
13263 |
<title>Creating the Swap Partition</title> |
13264 |
<body> |
13265 |
|
13266 |
<p> |
13267 |
Let's now create the swap partition. To do this, type <c>n</c> to create |
13268 |
a new partition, then <c>p</c> to tell fdisk that you want a primary |
13269 |
partition. Then type <c>2</c> to create the second primary partition, |
13270 |
<path>/dev/sda2</path> in our case. When prompted for the first |
13271 |
cylinder, hit enter. When prompted for the last cylinder, type |
13272 |
<c>+512M</c> to create a partition 512MB in size. After you've done |
13273 |
this, type <c>t</c> to set the partition type, <c>2</c> to select the |
13274 |
partition you just created and then type in <c>82</c> to set the |
13275 |
partition type to "Linux Swap". After completing these steps, typing |
13276 |
<c>p</c> should display a partition table that looks similar to this: |
13277 |
</p> |
13278 |
|
13279 |
<pre caption="Partition listing after creating a swap partition"> |
13280 |
Command (m for help): <i>p</i> |
13281 |
|
13282 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
13283 |
141 heads, 63 sectors/track, 6761 cylinders |
13284 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
13285 |
|
13286 |
Device Boot Start End Blocks Id System |
13287 |
/dev/sda1 1 3 13293 41 PPC PReP Boot |
13288 |
/dev/sda2 4 117 506331 82 Linux swap |
13289 |
|
13290 |
Command (m for help): |
13291 |
</pre> |
13292 |
|
13293 |
</body> |
13294 |
</subsection> |
13295 |
<subsection> |
13296 |
<title>Creating the Root Partition</title> |
13297 |
<body> |
13298 |
|
13299 |
<p> |
13300 |
Finally, let's create the root partition. To do this, type <c>n</c> to |
13301 |
create a new partition, then <c>p</c> to tell fdisk that you want a |
13302 |
primary partition. Then type <c>3</c> to create the third primary |
13303 |
partition, <path>/dev/sda3</path> in our case. When prompted for the |
13304 |
first cylinder, hit enter. When prompted for the last cylinder, hit |
13305 |
enter to create a partition that takes up the rest of the remaining |
13306 |
space on your disk. After completing these steps, typing <c>p</c> should |
13307 |
display a partition table that looks similar to this: |
13308 |
</p> |
13309 |
|
13310 |
<pre caption="Partition listing after creating the root partition"> |
13311 |
Command (m for help): p |
13312 |
|
13313 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
13314 |
141 heads, 63 sectors/track, 6761 cylinders |
13315 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
13316 |
|
13317 |
Device Boot Start End Blocks Id System |
13318 |
/dev/sda1 1 3 13293 41 PPC PReP Boot |
13319 |
/dev/sda2 4 117 506331 82 Linux swap |
13320 |
/dev/sda3 118 6761 29509326 83 Linux |
13321 |
|
13322 |
Command (m for help): |
13323 |
</pre> |
13324 |
</body> |
13325 |
</subsection> |
13326 |
<subsection> |
13327 |
<title>Saving the Partition Layout</title> |
13328 |
<body> |
13329 |
|
13330 |
<p> |
13331 |
To save the partition layout and exit <c>fdisk</c>, type <c>w</c>. |
13332 |
</p> |
13333 |
|
13334 |
<pre caption="Save and exit fdisk"> |
13335 |
Command (m for help): <i>w</i> |
13336 |
</pre> |
13337 |
|
13338 |
<p> |
13339 |
Now that your partitions are created, you can now continue with <uri |
13340 |
link="#filesystems">Creating Filesystems</uri>. |
13341 |
</p> |
13342 |
|
13343 |
</body> |
13344 |
</subsection> |
13345 |
</section> |
13346 |
<section id="filesystems"> |
13347 |
<title>Creating Filesystems</title> |
13348 |
<subsection> |
13349 |
<title>Introduction</title> |
13350 |
<body> |
13351 |
|
13352 |
<p> |
13353 |
Now that your partitions are created, it is time to place a filesystem on them. |
13354 |
If you don't care about what filesystem to choose and are happy with what we use |
13355 |
as default in this handbook, continue with <uri |
13356 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
13357 |
Otherwise read on to learn about the available filesystems... |
13358 |
</p> |
13359 |
|
13360 |
</body> |
13361 |
</subsection> |
13362 |
<subsection> |
13363 |
<title>Filesystems?</title> |
13364 |
<body> |
13365 |
|
13366 |
<note> |
13367 |
Several filesystems are available. |
13368 |
</note> |
13369 |
|
13370 |
<p> |
13371 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
13372 |
journaling, which means that routine ext2 filesystem checks at startup time can |
13373 |
be quite time-consuming. There is now quite a selection of newer-generation |
13374 |
journaled filesystems that can be checked for consistency very quickly and are |
13375 |
thus generally preferred over their non-journaled counterparts. Journaled |
13376 |
filesystems prevent long delays when you boot your system and your filesystem |
13377 |
happens to be in an inconsistent state. |
13378 |
</p> |
13379 |
|
13380 |
<p> |
13381 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
13382 |
journaling for fast recovery in addition to other enhanced journaling modes like |
13383 |
full data and ordered data journaling. ext3 is a very good and reliable |
13384 |
filesystem. It has an additional hashed b-tree indexing option that enables |
13385 |
high performance in almost all situations. You can enable this indexing by |
13386 |
adding <c>-O dir_index</c> to the <c>mke2fs</c> command. In short, ext3 is an |
13387 |
excellent filesystem. |
13388 |
</p> |
13389 |
|
13390 |
<p> |
13391 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
13392 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
13393 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
13394 |
extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is |
13395 |
solid and usable as both general-purpose filesystem and for extreme cases such |
13396 |
as the creation of large filesystems, the use of many small files, very large |
13397 |
files and directories containing tens of thousands of files. |
13398 |
</p> |
13399 |
|
13400 |
<p> |
13401 |
<b>XFS</b> is a filesystem with metadata journaling that is fully supported |
13402 |
under Gentoo Linux's xfs-sources kernel. It comes with a robust feature-set and |
13403 |
is optimized for scalability. We only recommend using this filesystem on Linux |
13404 |
systems with high-end SCSI and/or fibre channel storage and a uninterruptible |
13405 |
power supply. Because XFS aggressively caches in-transit data in RAM, improperly |
13406 |
designed programs (those that don't take proper precautions when writing files |
13407 |
to disk and there are quite a few of them) can lose a good deal of data if the |
13408 |
system goes down unexpectedly. |
13409 |
</p> |
13410 |
|
13411 |
<p> |
13412 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
13413 |
become production-ready. |
13414 |
</p> |
13415 |
|
13416 |
</body> |
13417 |
</subsection> |
13418 |
<subsection id="filesystems-apply"> |
13419 |
<title>Applying a Filesystem to a Partition</title> |
13420 |
<body> |
13421 |
|
13422 |
<p> |
13423 |
To create a filesystem on a partition or volume, there are tools available for |
13424 |
each possible filesystem: |
13425 |
</p> |
13426 |
|
13427 |
<table> |
13428 |
<tr> |
13429 |
<th>Filesystem</th> |
13430 |
<th>Creation Command</th> |
13431 |
</tr> |
13432 |
<tr> |
13433 |
<ti>ext2</ti> |
13434 |
<ti><c>mke2fs</c></ti> |
13435 |
</tr> |
13436 |
<tr> |
13437 |
<ti>ext3</ti> |
13438 |
<ti><c>mke2fs -j</c></ti> |
13439 |
</tr> |
13440 |
<tr> |
13441 |
<ti>reiserfs</ti> |
13442 |
<ti><c>mkreiserfs</c></ti> |
13443 |
</tr> |
13444 |
<tr> |
13445 |
<ti>xfs</ti> |
13446 |
<ti><c>mkfs.xfs</c></ti> |
13447 |
</tr> |
13448 |
<tr> |
13449 |
<ti>jfs</ti> |
13450 |
<ti><c>mkfs.jfs</c></ti> |
13451 |
</tr> |
13452 |
</table> |
13453 |
|
13454 |
<p> |
13455 |
For instance, to have the root partition (<path>/dev/sda4</path> in our example) |
13456 |
in ext3 (as in our example), you would use: |
13457 |
</p> |
13458 |
|
13459 |
<pre caption="Applying a filesystem on a partition"> |
13460 |
# <i>mke2fs -j /dev/sda4</i> |
13461 |
</pre> |
13462 |
|
13463 |
<p> |
13464 |
Now create the filesystems on your newly created partitions (or logical |
13465 |
volumes). |
13466 |
</p> |
13467 |
|
13468 |
</body> |
13469 |
</subsection> |
13470 |
<subsection> |
13471 |
<title>Activating the Swap Partition</title> |
13472 |
<body> |
13473 |
|
13474 |
<p> |
13475 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
13476 |
</p> |
13477 |
|
13478 |
<pre caption="Creating a Swap signature"> |
13479 |
# <i>mkswap /dev/sda3</i> |
13480 |
</pre> |
13481 |
|
13482 |
<p> |
13483 |
To activate the swap partition, use <c>swapon</c>: |
13484 |
</p> |
13485 |
|
13486 |
<pre caption="Activating the swap partition"> |
13487 |
# <i>swapon /dev/sda3</i> |
13488 |
</pre> |
13489 |
|
13490 |
<p> |
13491 |
Create and activate the swap with the commands mentioned above. |
13492 |
</p> |
13493 |
|
13494 |
</body> |
13495 |
</subsection> |
13496 |
</section> |
13497 |
<section> |
13498 |
<title>Mounting</title> |
13499 |
<body> |
13500 |
|
13501 |
<p> |
13502 |
Now that your partitions are initialized and are housing a filesystem, it is |
13503 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
13504 |
create the necessary mount directories for every partition you created. As an |
13505 |
example we create a mount-point and mount the root and boot partition: |
13506 |
</p> |
13507 |
|
13508 |
<pre caption="Mounting partitions"> |
13509 |
# <i>mkdir /mnt/gentoo</i> |
13510 |
# <i>mount /dev/sda4 /mnt/gentoo</i> |
13511 |
</pre> |
13512 |
|
13513 |
<note> |
13514 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
13515 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
13516 |
also holds for <path>/var/tmp</path>. |
13517 |
</note> |
13518 |
|
13519 |
<p> |
13520 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
13521 |
Installation Files</uri>. |
13522 |
</p> |
13523 |
|
13524 |
</body> |
13525 |
</section> |
13526 |
</sections> |
13527 |
|
13528 |
|
13529 |
|
13530 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc64-kernel.xml |
13531 |
|
13532 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc64-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
13533 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc64-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
13534 |
|
13535 |
Index: hb-install-ppc64-kernel.xml |
13536 |
=================================================================== |
13537 |
<?xml version='1.0' encoding='UTF-8'?> |
13538 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
13539 |
|
13540 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
13541 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
13542 |
|
13543 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc64-kernel.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
13544 |
|
13545 |
<sections> |
13546 |
|
13547 |
<version>5.5</version> |
13548 |
<date>2006-01-06</date> |
13549 |
|
13550 |
<section> |
13551 |
<title>Timezone</title> |
13552 |
<body> |
13553 |
|
13554 |
<p> |
13555 |
You first need to select your timezone so that your system knows where it is |
13556 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
13557 |
it to <path>/etc/localtime</path>. Please avoid the |
13558 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
13559 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
13560 |
</p> |
13561 |
|
13562 |
<pre caption="Setting the timezone information"> |
13563 |
# <i>ls /usr/share/zoneinfo</i> |
13564 |
<comment>(Suppose you want to use GMT)</comment> |
13565 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
13566 |
</pre> |
13567 |
|
13568 |
</body> |
13569 |
</section> |
13570 |
<section> |
13571 |
<title>Installing the Sources</title> |
13572 |
<subsection> |
13573 |
<title>Choosing a Kernel</title> |
13574 |
<body> |
13575 |
|
13576 |
<p> |
13577 |
The core around which all distributions are built is the Linux kernel. |
13578 |
It is the layer between the user programs and your system hardware. |
13579 |
Gentoo provides its users several possible kernel sources. A full |
13580 |
listing with description is available at the <uri |
13581 |
link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>. |
13582 |
</p> |
13583 |
|
13584 |
<p> |
13585 |
For PPC64 you should use <c>gentoo-sources</c>. So let's continue with |
13586 |
<c>emerge</c>'ing the kernel sources. The <c>USE="-doc"</c> is necessary to |
13587 |
avoid installing xorg-x11 or other dependencies at this point. |
13588 |
<c>USE="symlink"</c> is not necessary for a new install, but ensures proper |
13589 |
creation of the <path>/usr/src/linux</path> symlink. |
13590 |
</p> |
13591 |
|
13592 |
<pre caption="Installing a kernel source"> |
13593 |
# <i>USE="-doc symlink" emerge gentoo-sources</i> |
13594 |
</pre> |
13595 |
|
13596 |
<p> |
13597 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
13598 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
13599 |
kernel source points to <c>gentoo-sources-2.6.12-r10</c>. Your version may be |
13600 |
different, so keep this in mind. |
13601 |
</p> |
13602 |
|
13603 |
<pre caption="Viewing the kernel source symlink"> |
13604 |
# <i>ls -l /usr/src/linux</i> |
13605 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-2.6.12-gentoo-r10 |
13606 |
</pre> |
13607 |
|
13608 |
<p> |
13609 |
Now it is time to configure and compile your kernel source. There is the |
13610 |
ability to use "genkernel" which would create a generic kernel like the |
13611 |
ones used on the installation CDs, but it is not fully functional for PPC64 at |
13612 |
the moment. |
13613 |
</p> |
13614 |
|
13615 |
<p> |
13616 |
Continue now with <uri link="#manual">Manual Configuration</uri>. |
13617 |
</p> |
13618 |
|
13619 |
</body> |
13620 |
</subsection> |
13621 |
</section> |
13622 |
<section id="manual"> |
13623 |
<title>Manual Configuration</title> |
13624 |
<subsection> |
13625 |
<title>Introduction</title> |
13626 |
<body> |
13627 |
|
13628 |
<p> |
13629 |
Manually configuring a kernel is often seen as the most difficult procedure a |
13630 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
13631 |
couple of kernels you don't even remember that it was difficult ;) |
13632 |
</p> |
13633 |
|
13634 |
<p> |
13635 |
However, one thing <e>is</e> true: you must know your system when you |
13636 |
configuring a kernel manually. Most information can be gathered by emerging |
13637 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
13638 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
13639 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
13640 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
13641 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
13642 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
13643 |
uses (it might provide you with a nice hint on what to enable). |
13644 |
</p> |
13645 |
|
13646 |
<p> |
13647 |
Now go to your kernel source directory and execute <c>make |
13648 |
menuconfig</c>. This will fire up an ncurses-based configuration menu. |
13649 |
</p> |
13650 |
|
13651 |
<p> |
13652 |
When compiling the kernel on a 32bit userland system add the following to |
13653 |
the bottom of /etc/profile: |
13654 |
</p> |
13655 |
|
13656 |
<pre caption="32bit userland make alias"> |
13657 |
# <i>echo 'alias ppc64make="make ARCH=ppc64 CROSS_COMPILE=powerpc64-unknown-linux-gnu-"' >> /etc/profile</i> |
13658 |
# <i>source /etc/profile</i> |
13659 |
</pre> |
13660 |
|
13661 |
<pre caption="Invoking menuconfig"> |
13662 |
# <i>cd /usr/src/linux</i> |
13663 |
(64bit userland) # <i>make menuconfig</i> |
13664 |
(32bit userland) # <i>ppc64make menuconfig</i> |
13665 |
</pre> |
13666 |
|
13667 |
<p> |
13668 |
You will be greeted with several configuration sections. We'll first |
13669 |
list some options you must activate (otherwise Gentoo will not function, |
13670 |
or not function properly without additional tweaks). |
13671 |
</p> |
13672 |
|
13673 |
</body> |
13674 |
</subsection> |
13675 |
<subsection> |
13676 |
<title>Activating Required Options</title> |
13677 |
<body> |
13678 |
|
13679 |
<p> |
13680 |
First of all, activate the use of development and experimental |
13681 |
code/drivers. You need this, otherwise some very important code/drivers |
13682 |
won't show up: |
13683 |
</p> |
13684 |
|
13685 |
<pre caption="Selecting experimental code/drivers, General setup"> |
13686 |
Code maturity level options ---> |
13687 |
[*] Prompt for development and/or incomplete code/drivers |
13688 |
General setup ---> |
13689 |
[*] Support for hot-pluggable devices |
13690 |
</pre> |
13691 |
|
13692 |
<p> |
13693 |
Now go to <c>File Systems</c> and select support for the filesystems you |
13694 |
use. <e>Don't</e> compile them as modules, otherwise your Gentoo system |
13695 |
will not be able to mount your partitions. Also select <c>Virtual |
13696 |
memory</c>, <c>/proc file system</c>, and <c>/dev/pts file system for |
13697 |
Unix98 PTYs</c>: |
13698 |
</p> |
13699 |
|
13700 |
<pre caption="Selecting necessary file systems"> |
13701 |
File systems ---> |
13702 |
[*] Virtual memory file system support (former shm fs) |
13703 |
[*] /proc file system support |
13704 |
[*] /dev/pts file system for Unix98 PTYs |
13705 |
|
13706 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
13707 |
<*> Reiserfs support |
13708 |
<*> Ext3 journalling file system support |
13709 |
<*> JFS filesystem support |
13710 |
<*> Second extended fs support |
13711 |
<*> XFS filesystem support |
13712 |
</pre> |
13713 |
|
13714 |
<note> |
13715 |
You will find some of the mentioned options under <c>Pseudo |
13716 |
filesystems</c> which is a subpart of <c>File systems</c>. |
13717 |
</note> |
13718 |
|
13719 |
<p> |
13720 |
If you are using PPPoE to connect to the Internet or you are using a |
13721 |
dial-up modem, you will need the following options in the kernel (you |
13722 |
will find the mentioned options under <c>Networking support</c> which is |
13723 |
a subpart of <c>Device Drivers</c>): |
13724 |
</p> |
13725 |
|
13726 |
<pre caption="Selecting PPPoE necessary drivers"> |
13727 |
Network device support ---> |
13728 |
<*> PPP (point-to-point protocol) support |
13729 |
<*> PPP support for async serial ports |
13730 |
<*> PPP support for sync tty ports |
13731 |
</pre> |
13732 |
|
13733 |
<p> |
13734 |
The two compression options won't harm but are not definitely needed, neither |
13735 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
13736 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
13737 |
</p> |
13738 |
|
13739 |
<p> |
13740 |
If you require it, don't forget to include support in the kernel for your |
13741 |
ethernet card. |
13742 |
</p> |
13743 |
|
13744 |
<p> |
13745 |
Disable ADB raw keycodes: |
13746 |
</p> |
13747 |
|
13748 |
<pre caption="Disabling ADB raw keycodes"> |
13749 |
Macintosh Device Drivers ---> |
13750 |
[ ] Support for ADB raw keycodes |
13751 |
</pre> |
13752 |
|
13753 |
<p> |
13754 |
When you're done configuring your kernel, continue with <uri |
13755 |
link="#compiling">Compiling and Installing</uri>. |
13756 |
</p> |
13757 |
|
13758 |
</body> |
13759 |
</subsection> |
13760 |
<subsection id="compiling"> |
13761 |
<title>Compiling and Installing</title> |
13762 |
<body> |
13763 |
|
13764 |
<p> |
13765 |
Now that your kernel is configured, it is time to compile and install it. Exit |
13766 |
the configuration and start the compilation process: |
13767 |
</p> |
13768 |
|
13769 |
<pre caption="Compiling the kernel"> |
13770 |
(64bit userland) # <i>make && make modules_install</i> |
13771 |
(32bit userland) # <i>ppc64make && ppc64make modules_install</i> |
13772 |
</pre> |
13773 |
|
13774 |
<p> |
13775 |
When the kernel has finished compiling, copy the kernel image to |
13776 |
<path>/boot</path>. Remember to replace <path><kernel-version<</path> |
13777 |
with your actual kernel version: |
13778 |
</p> |
13779 |
|
13780 |
<pre caption="Installing the kernel"> |
13781 |
# <i>cp vmlinux /boot/<kernel-version<</i> |
13782 |
</pre> |
13783 |
|
13784 |
<p> |
13785 |
Now continue with <uri link="#kernel_modules">Configuring the Modules</uri>. |
13786 |
</p> |
13787 |
|
13788 |
</body> |
13789 |
</subsection> |
13790 |
</section> |
13791 |
<section id="kernel_modules"> |
13792 |
<title>Configuring the Modules</title> |
13793 |
<body> |
13794 |
|
13795 |
<p> |
13796 |
You should list the modules you want automatically loaded in |
13797 |
<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra |
13798 |
options to the modules too if you want. |
13799 |
</p> |
13800 |
|
13801 |
<p> |
13802 |
To view all available modules, run the following <c>find</c> command. Don't |
13803 |
forget to substitute "<kernel version>" with the version of the kernel you |
13804 |
just compiled: |
13805 |
</p> |
13806 |
|
13807 |
<pre caption="Viewing all available modules"> |
13808 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
13809 |
</pre> |
13810 |
|
13811 |
<p> |
13812 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
13813 |
<path>kernel-2.6</path> file and enter the module name in it. |
13814 |
</p> |
13815 |
|
13816 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
13817 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
13818 |
</pre> |
13819 |
|
13820 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
13821 |
3c59x |
13822 |
</pre> |
13823 |
|
13824 |
<p> |
13825 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
13826 |
your System</uri>. |
13827 |
</p> |
13828 |
|
13829 |
</body> |
13830 |
</section> |
13831 |
</sections> |
13832 |
|
13833 |
|
13834 |
|
13835 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc64-medium.xml |
13836 |
|
13837 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc64-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
13838 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc64-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
13839 |
|
13840 |
Index: hb-install-ppc64-medium.xml |
13841 |
=================================================================== |
13842 |
<?xml version='1.0' encoding='UTF-8'?> |
13843 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
13844 |
|
13845 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
13846 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
13847 |
|
13848 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-ppc64-medium.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
13849 |
|
13850 |
<sections> |
13851 |
|
13852 |
<version>5.5</version> |
13853 |
<date>2005-11-29</date> |
13854 |
|
13855 |
<section> |
13856 |
<title>Hardware Requirements</title> |
13857 |
<subsection> |
13858 |
<title>Introduction</title> |
13859 |
<body> |
13860 |
|
13861 |
<p> |
13862 |
Before we start, we first list what hardware requirements you need to |
13863 |
successfully install Gentoo on your box. |
13864 |
</p> |
13865 |
|
13866 |
</body> |
13867 |
</subsection> |
13868 |
<subsection> |
13869 |
<title>Hardware Requirements</title> |
13870 |
<body> |
13871 |
|
13872 |
<table> |
13873 |
<tr> |
13874 |
<th>CPU</th> |
13875 |
<ti>Any PowerPC64 CPU</ti> |
13876 |
</tr> |
13877 |
<tr> |
13878 |
<th>Systems</th> |
13879 |
<ti> |
13880 |
IBM RS/6000s, Power Macintosh G5, iMac G5, IBP pSeries and IBM OpenPower |
13881 |
</ti> |
13882 |
</tr> |
13883 |
<tr> |
13884 |
<th>Memory</th> |
13885 |
<ti>64 MB</ti> |
13886 |
</tr> |
13887 |
<tr> |
13888 |
<th>Diskspace</th> |
13889 |
<ti>1.5 GB (excluding swap space)</ti> |
13890 |
</tr> |
13891 |
<tr> |
13892 |
<th>Swap space</th> |
13893 |
<ti>At least 256 MB</ti> |
13894 |
</tr> |
13895 |
</table> |
13896 |
|
13897 |
<p> |
13898 |
For a full list of supported systems, please go to |
13899 |
<uri>http://www.linuxppc64.org/hardware.shtml</uri>. |
13900 |
</p> |
13901 |
|
13902 |
</body> |
13903 |
</subsection> |
13904 |
</section> |
13905 |
<!-- Copy/paste from hb-install-x86-medium.xml, with s/x86/ppc64/ --> |
13906 |
<!-- START --> |
13907 |
<section> |
13908 |
<title>The Gentoo Universal Installation CD</title> |
13909 |
<subsection> |
13910 |
<title>Introduction</title> |
13911 |
<body> |
13912 |
|
13913 |
<p> |
13914 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
13915 |
Such a tarball is an archive that contains a minimal environment from |
13916 |
which you can successfully install Gentoo Linux onto your system. |
13917 |
</p> |
13918 |
|
13919 |
<p> |
13920 |
Installations using a stage1 or stage2 tarball file are not documented in the |
13921 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
13922 |
FAQ</uri> on these matters. |
13923 |
</p> |
13924 |
|
13925 |
</body> |
13926 |
</subsection> |
13927 |
<subsection> |
13928 |
<title>Gentoo Universal Installation CD</title> |
13929 |
<body> |
13930 |
|
13931 |
<p> |
13932 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
13933 |
environment. It allows you to boot Linux from the CD. During the boot process |
13934 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
13935 |
Installation CDs are maintained by Gentoo developers. |
13936 |
</p> |
13937 |
|
13938 |
<p> |
13939 |
There currently are two Installation CDs available: |
13940 |
</p> |
13941 |
|
13942 |
<ul> |
13943 |
<li> |
13944 |
The Universal Installation CD contains everything you need to install |
13945 |
Gentoo. It provides stage3 files for common architectures, source code |
13946 |
for the extra applications you need to choose from and, of course, the |
13947 |
installation instructions for your architecture. |
13948 |
</li> |
13949 |
<li> |
13950 |
The Minimal Installation CD contains only a minimal environment that allows |
13951 |
you to boot up and configure your network so you can connect to the |
13952 |
Internet. It does not contain any additional files and cannot be used |
13953 |
during the current installation approach. |
13954 |
</li> |
13955 |
</ul> |
13956 |
|
13957 |
<p> |
13958 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
13959 |
additional resource that you can exploit during the installation of your Gentoo |
13960 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
13961 |
you to easily and quickly install additional applications immediately after the |
13962 |
Gentoo installation and right before you update your Portage tree. |
13963 |
</p> |
13964 |
|
13965 |
<p> |
13966 |
The use of the Package CD is covered later in this document. |
13967 |
</p> |
13968 |
|
13969 |
</body> |
13970 |
</subsection> |
13971 |
</section> |
13972 |
<!-- STOP --> |
13973 |
<section> |
13974 |
<title>Download, Burn and Boot a Gentoo Installation CD</title> |
13975 |
<subsection> |
13976 |
<title>Downloading and Burning the Installation CDs</title> |
13977 |
<body> |
13978 |
|
13979 |
<p> |
13980 |
You can download the Universal Installation CD (and, if you want to, the |
13981 |
Packages CD as well) from one of our <uri |
13982 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located |
13983 |
in the <path>releases/ppc64/2005.1-r1/installcd</path> directory; |
13984 |
the Package CDs are located in the <path>releases/ppc64/2005.1/packagecd</path> |
13985 |
directory. |
13986 |
</p> |
13987 |
|
13988 |
<p> |
13989 |
Inside those directories you'll find ISO-files. Those are full CD images which |
13990 |
you can write on a CD-R. |
13991 |
</p> |
13992 |
|
13993 |
<p> |
13994 |
After downloading the file, you can verify its integrity to see if it is |
13995 |
corrupted or not: |
13996 |
</p> |
13997 |
|
13998 |
<ul> |
13999 |
<li> |
14000 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
14001 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
14002 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows). How |
14003 |
to verify MD5 checksums with Mac OS X is described in the <uri |
14004 |
link="/doc/en/gentoo-ppc-faq.xml#doc_chap1">Gentoo PPC FAQ</uri>. |
14005 |
</li> |
14006 |
<li> |
14007 |
You can verify the cryptographic signature that we provide. You need to |
14008 |
obtain the public key we use (0x17072058) before you proceed though. |
14009 |
</li> |
14010 |
</ul> |
14011 |
|
14012 |
<p> |
14013 |
To fetch our public key using the GnuPG application, run the following command: |
14014 |
</p> |
14015 |
|
14016 |
<pre caption="Obtaining the public key"> |
14017 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 0x17072058</i> |
14018 |
</pre> |
14019 |
|
14020 |
<p> |
14021 |
Now verify the signature: |
14022 |
</p> |
14023 |
|
14024 |
<pre caption="Verify the cryptographic signature"> |
14025 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
14026 |
</pre> |
14027 |
|
14028 |
<p> |
14029 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
14030 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
14031 |
<c>K3B</c> here; more information can be found in our <uri |
14032 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
14033 |
</p> |
14034 |
|
14035 |
<ul> |
14036 |
<li> |
14037 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
14038 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
14039 |
path). |
14040 |
</li> |
14041 |
<li> |
14042 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
14043 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
14044 |
<c>Start</c>. |
14045 |
</li> |
14046 |
</ul> |
14047 |
|
14048 |
</body> |
14049 |
</subsection> |
14050 |
<subsection> |
14051 |
<title>Booting the Installation CD on an Apple</title> |
14052 |
<body> |
14053 |
|
14054 |
<p> |
14055 |
Place the Installation CD in the CD-ROM and reboot the system. Hold down the |
14056 |
'C' key at bootup. You will be greeted by a friendly welcome message and a |
14057 |
<e>boot:</e> prompt at the bottom of the screen. |
14058 |
</p> |
14059 |
|
14060 |
<p> |
14061 |
You are also able to tweak some kernel options at this prompt. The following |
14062 |
table lists the available boot options you can add: |
14063 |
</p> |
14064 |
|
14065 |
<table> |
14066 |
<tr> |
14067 |
<th>Boot Option</th> |
14068 |
<th>Description</th> |
14069 |
</tr> |
14070 |
<tr> |
14071 |
<ti><c>video</c></ti> |
14072 |
<ti> |
14073 |
This option takes one of the following vendor-specific tags: |
14074 |
<c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, <c>aty128</c> or |
14075 |
<c>ofonly</c>. You can follow this tag with the resolution and refreshrate |
14076 |
you want to use. For instance <c>video=radeonfb:1280x1024@75</c>. If you are |
14077 |
uncertain what to choose, <c>ofonly</c> will most certainly work. |
14078 |
</ti> |
14079 |
</tr> |
14080 |
<tr> |
14081 |
<ti><c>nol3</c></ti> |
14082 |
<ti> |
14083 |
Disables level 3 cache on some powerbooks (needed for at least the 17'') |
14084 |
</ti> |
14085 |
</tr> |
14086 |
<tr> |
14087 |
<ti><c>debug</c></ti> |
14088 |
<ti> |
14089 |
Enables verbose booting, spawns an initrd shell that can be used to debug |
14090 |
the Installation CD |
14091 |
</ti> |
14092 |
</tr> |
14093 |
<tr> |
14094 |
<ti><c>sleep=X</c></ti> |
14095 |
<ti> |
14096 |
Wait X seconds before continuing; this can be needed by some very old SCSI |
14097 |
CD-ROMs which don't speed up the CD quick enough |
14098 |
</ti> |
14099 |
</tr> |
14100 |
<tr> |
14101 |
<ti><c>bootfrom=X</c></ti> |
14102 |
<ti> |
14103 |
Boot from a different device |
14104 |
</ti> |
14105 |
</tr> |
14106 |
</table> |
14107 |
|
14108 |
<p> |
14109 |
At this prompt, hit enter, and a complete Gentoo Linux environment will be |
14110 |
loaded from the CD. Continue with <uri link="#booted">And When You're |
14111 |
Booted...</uri>. |
14112 |
</p> |
14113 |
|
14114 |
</body> |
14115 |
</subsection> |
14116 |
<subsection> |
14117 |
<title>Booting the Installation CD on an IBM pSeries</title> |
14118 |
<body> |
14119 |
|
14120 |
<p> |
14121 |
For pSeries boxes, sometimes the cds might not autoboot. You might have |
14122 |
to set up your cdrom as a bootable device in the multi-boot menu. (F1 at |
14123 |
startup) The other option is to jump into OF and do it from there: |
14124 |
</p> |
14125 |
|
14126 |
<p> |
14127 |
1) Boot into OF (this is 8 from the serial cons or F8 from a graphics |
14128 |
cons, start hitting the key when you see the keyboard mouse etc etc |
14129 |
messages |
14130 |
</p> |
14131 |
<p> |
14132 |
2) run the command 0> boot cdrom:1,yaboot |
14133 |
</p> |
14134 |
<p> |
14135 |
3) stand back and enjoy! |
14136 |
</p> |
14137 |
|
14138 |
</body> |
14139 |
</subsection> |
14140 |
<subsection id="booted"> |
14141 |
<title>And When You're Booted...</title> |
14142 |
<body> |
14143 |
|
14144 |
<p> |
14145 |
You will be greeted by a root ("#") prompt on the current console. You can also |
14146 |
switch to other consoles by pressing Alt-fn-F2, Alt-fn-F3 and Alt-fn-F4. Get |
14147 |
back to the one you started on by pressing Alt-fn-F1. |
14148 |
</p> |
14149 |
|
14150 |
<p> |
14151 |
If you are installing Gentoo on a system with a non-US keyboard, use |
14152 |
<c>loadkeys</c> to load the keymap for your keyboard. To list the available |
14153 |
keymaps, execute <c>ls /usr/share/keymaps/i386</c>. |
14154 |
</p> |
14155 |
|
14156 |
<pre caption="Listing available keymaps"> |
14157 |
<comment>(PPC uses x86 keymaps on most systems. The mac/ppc keymaps provided |
14158 |
on the Installation CD are ADB keymaps and unusable with the |
14159 |
Installation CD kernel)</comment> |
14160 |
# <i>ls /usr/share/keymaps/i386</i> |
14161 |
</pre> |
14162 |
|
14163 |
<p> |
14164 |
Now load the keymap of your choice: |
14165 |
</p> |
14166 |
|
14167 |
<pre caption="Loading a keymap"> |
14168 |
# <i>loadkeys be-latin1</i> |
14169 |
</pre> |
14170 |
|
14171 |
<p> |
14172 |
Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
14173 |
</p> |
14174 |
|
14175 |
</body> |
14176 |
</subsection> |
14177 |
<subsection id="hardware"> |
14178 |
<title>Extra Hardware Configuration</title> |
14179 |
<body> |
14180 |
|
14181 |
<p> |
14182 |
When the Installation CD boots, it tries to detect all your hardware devices and |
14183 |
loads the appropriate kernel modules to support your hardware. In the |
14184 |
vast majority of cases, it does a very good job. However, in some cases it may |
14185 |
not auto-load the kernel |
14186 |
modules you need. If the PCI auto-detection missed some of your system's |
14187 |
hardware, you will have to load the appropriate kernel modules manually. |
14188 |
</p> |
14189 |
|
14190 |
<p> |
14191 |
In the next example we try to load the <c>8139too</c> module (support for |
14192 |
certain kinds of network interfaces): |
14193 |
</p> |
14194 |
|
14195 |
<pre caption="Loading kernel modules"> |
14196 |
# <i>modprobe 8139too</i> |
14197 |
</pre> |
14198 |
|
14199 |
</body> |
14200 |
</subsection> |
14201 |
<subsection> |
14202 |
<title>Optional: Tweaking Hard Disk Performance</title> |
14203 |
<body> |
14204 |
|
14205 |
<p> |
14206 |
If you are an advanced user, you might want to tweak the IDE hard disk |
14207 |
performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
14208 |
test the performance of your disk (execute it several times to get a |
14209 |
more precise impression): |
14210 |
</p> |
14211 |
|
14212 |
<pre caption="Testing disk performance"> |
14213 |
# <i>hdparm -tT /dev/hda</i> |
14214 |
</pre> |
14215 |
|
14216 |
<p> |
14217 |
To tweak, you can use any of the following examples (or experiment |
14218 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
14219 |
disk): |
14220 |
</p> |
14221 |
|
14222 |
<pre caption="Tweaking hard disk performance"> |
14223 |
<comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i> |
14224 |
<comment>Activate DMA + Safe Performance-enhancing Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
14225 |
</pre> |
14226 |
|
14227 |
</body> |
14228 |
</subsection> |
14229 |
<subsection id="useraccounts"> |
14230 |
<title>Optional: User Accounts</title> |
14231 |
<body> |
14232 |
|
14233 |
<p> |
14234 |
If you plan on giving other people access to your installation |
14235 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
14236 |
security reasons), you need to create the necessary user accounts and change |
14237 |
the root password. |
14238 |
</p> |
14239 |
|
14240 |
<p> |
14241 |
To change the root password, use the <c>passwd</c> utility: |
14242 |
</p> |
14243 |
|
14244 |
<pre caption="Changing the root password"> |
14245 |
# <i>passwd</i> |
14246 |
New password: <comment>(Enter your new password)</comment> |
14247 |
Re-enter password: <comment>(Re-enter your password)</comment> |
14248 |
</pre> |
14249 |
|
14250 |
<p> |
14251 |
To create a user account, we first enter their credentials, followed by |
14252 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
14253 |
In the next example, we create a user called "john". |
14254 |
</p> |
14255 |
|
14256 |
<pre caption="Creating a user account"> |
14257 |
# <i>useradd -m -G users john</i> |
14258 |
# <i>passwd john</i> |
14259 |
New password: <comment>(Enter john's password)</comment> |
14260 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
14261 |
</pre> |
14262 |
|
14263 |
<p> |
14264 |
You can change your user id from root to the newly created user by using |
14265 |
<c>su</c>: |
14266 |
</p> |
14267 |
|
14268 |
<pre caption="Changing user id"> |
14269 |
# <i>su - john</i> |
14270 |
</pre> |
14271 |
|
14272 |
</body> |
14273 |
</subsection> |
14274 |
<subsection> |
14275 |
<title>Optional: Viewing Documentation while Installing</title> |
14276 |
<body> |
14277 |
|
14278 |
<p> |
14279 |
If you want to view the Gentoo Handbook during the installation, make sure you |
14280 |
have created a user account (see <uri link="#useraccounts">Optional: User |
14281 |
Accounts</uri>). Then press <c>Alt-F2</c> to go to a new terminal and log in. |
14282 |
</p> |
14283 |
|
14284 |
<p> |
14285 |
If you want to view the documentation on the CD you can immediately run |
14286 |
<c>links2</c> to read it: |
14287 |
</p> |
14288 |
|
14289 |
<pre caption="Viewing the on-CD documentation"> |
14290 |
# <i>links2 /mnt/cdrom/docs/handbook/html/index.html</i> |
14291 |
</pre> |
14292 |
|
14293 |
<p> |
14294 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
14295 |
more recent than the one provided on the CD. |
14296 |
</p> |
14297 |
|
14298 |
<pre caption="Viewing the Online Documentation"> |
14299 |
# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-ppc64.xml</i> |
14300 |
</pre> |
14301 |
|
14302 |
<p> |
14303 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
14304 |
</p> |
14305 |
|
14306 |
</body> |
14307 |
</subsection> |
14308 |
<subsection> |
14309 |
<title>Optional: Starting the SSH Daemon</title> |
14310 |
<body> |
14311 |
|
14312 |
<p> |
14313 |
If you want to allow other users to access your computer during the |
14314 |
Gentoo installation (perhaps because those users are going to help you |
14315 |
install Gentoo, or even do it for you), you need to create a user |
14316 |
account for them and perhaps even provide them with your root password |
14317 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
14318 |
</p> |
14319 |
|
14320 |
<p> |
14321 |
To fire up the SSH daemon, execute the following command: |
14322 |
</p> |
14323 |
|
14324 |
<pre caption="Starting the SSH daemon"> |
14325 |
# <i>/etc/init.d/sshd start</i> |
14326 |
</pre> |
14327 |
|
14328 |
<p> |
14329 |
To be able to use sshd, you first need to set up your networking. Continue with |
14330 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
14331 |
</p> |
14332 |
|
14333 |
</body> |
14334 |
</subsection> |
14335 |
</section> |
14336 |
</sections> |
14337 |
|
14338 |
|
14339 |
|
14340 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-sparc-bootloader.xml |
14341 |
|
14342 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-sparc-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
14343 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-sparc-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
14344 |
|
14345 |
Index: hb-install-sparc-bootloader.xml |
14346 |
=================================================================== |
14347 |
<?xml version='1.0' encoding='UTF-8'?> |
14348 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
14349 |
|
14350 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
14351 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
14352 |
|
14353 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-sparc-bootloader.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
14354 |
|
14355 |
<sections> |
14356 |
|
14357 |
<version>5.3</version> |
14358 |
<date>2006-01-19</date> |
14359 |
|
14360 |
<section> |
14361 |
<title>Making your Choice</title> |
14362 |
<subsection> |
14363 |
<title>Introduction</title> |
14364 |
<body> |
14365 |
|
14366 |
<p> |
14367 |
Now that your kernel is configured and compiled and the necessary system |
14368 |
configuration files are filled in correctly, it is time to install a |
14369 |
program that will fire up your kernel when you start the system. Such a |
14370 |
program is called a <e>bootloader</e>. |
14371 |
</p> |
14372 |
|
14373 |
</body> |
14374 |
</subsection> |
14375 |
</section> |
14376 |
<section> |
14377 |
<title>Installing the SPARC Bootloader: SILO</title> |
14378 |
<body> |
14379 |
|
14380 |
<p> |
14381 |
It is now time to install and configure <uri |
14382 |
link="http://www.sparc-boot.org">SILO</uri>, the Sparc Improved boot |
14383 |
LOader. |
14384 |
</p> |
14385 |
|
14386 |
<pre caption = "Installing SILO"> |
14387 |
# <i>emerge silo</i> |
14388 |
</pre> |
14389 |
|
14390 |
<p> |
14391 |
Now open up your favorite editor (we use <c>nano</c> as an example) and |
14392 |
create <path>/etc/silo.conf</path>. |
14393 |
</p> |
14394 |
|
14395 |
<pre caption = "Creating /etc/silo.conf"> |
14396 |
# <i>nano -w /etc/silo.conf</i> |
14397 |
</pre> |
14398 |
|
14399 |
<p> |
14400 |
Below you'll find an example <path>silo.conf</path> file. It uses the |
14401 |
partitioning scheme we use throughout this book and |
14402 |
<path>kernel-2.4.31</path> as kernelimage. |
14403 |
</p> |
14404 |
|
14405 |
<pre caption = "Example /etc/silo.conf"> |
14406 |
partition = 1 <comment># Boot partition (= root partition)</comment> |
14407 |
root = /dev/sda1 <comment># Root partition</comment> |
14408 |
timeout = 150 <comment># Wait 15 seconds before booting the default section</comment> |
14409 |
|
14410 |
image = /boot/kernel-2.4.31 |
14411 |
label = linux |
14412 |
</pre> |
14413 |
|
14414 |
<p> |
14415 |
If you use the example <path>silo.conf</path> delivered by Portage, be |
14416 |
sure to comment out <e>all</e> lines that you do not need. |
14417 |
</p> |
14418 |
|
14419 |
<p> |
14420 |
If the physical disk on which you want to install SILO (as bootloader) differs |
14421 |
from the physical disk on which <path>/etc/silo.conf</path> resides, you must |
14422 |
copy over <path>/etc/silo.conf</path> to a partition on that disk. Assuming that |
14423 |
<path>/boot</path> is a separate partition on that disk, copy over the |
14424 |
configuration file to <path>/boot</path> and run <c>/sbin/silo</c>: |
14425 |
</p> |
14426 |
|
14427 |
<pre caption = "Only if /boot and the SILO destination are not on the same disk"> |
14428 |
# <i>cp /etc/silo.conf /boot</i> |
14429 |
# <i>/sbin/silo -C /boot/silo.conf</i> |
14430 |
/boot/silo.conf appears to be valid |
14431 |
</pre> |
14432 |
|
14433 |
<p> |
14434 |
Otherwise just run <c>/sbin/silo</c>: |
14435 |
</p> |
14436 |
|
14437 |
<pre caption = "Run silo"> |
14438 |
# <i>/sbin/silo</i> |
14439 |
/etc/silo.conf appears to be valid |
14440 |
</pre> |
14441 |
|
14442 |
<p> |
14443 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
14444 |
</p> |
14445 |
|
14446 |
</body> |
14447 |
</section> |
14448 |
<section id="reboot"> |
14449 |
<title>Rebooting the System</title> |
14450 |
<subsection> |
14451 |
<body> |
14452 |
|
14453 |
<p> |
14454 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
14455 |
that one magical command you have been waiting for: <c>reboot</c>. |
14456 |
</p> |
14457 |
|
14458 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
14459 |
# <i>exit</i> |
14460 |
cdimage ~# <i>cd</i> |
14461 |
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
14462 |
cdimage ~# <i>reboot</i> |
14463 |
</pre> |
14464 |
|
14465 |
<p> |
14466 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
14467 |
booted again instead of your new Gentoo system. |
14468 |
</p> |
14469 |
|
14470 |
<p> |
14471 |
Once rebooted in your Gentoo installation, finish up with <uri |
14472 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
14473 |
</p> |
14474 |
|
14475 |
</body> |
14476 |
</subsection> |
14477 |
</section> |
14478 |
</sections> |
14479 |
|
14480 |
|
14481 |
|
14482 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-sparc-disk.xml |
14483 |
|
14484 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-sparc-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
14485 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-sparc-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
14486 |
|
14487 |
Index: hb-install-sparc-disk.xml |
14488 |
=================================================================== |
14489 |
<?xml version='1.0' encoding='UTF-8'?> |
14490 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
14491 |
|
14492 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
14493 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
14494 |
|
14495 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-sparc-disk.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
14496 |
|
14497 |
<sections> |
14498 |
|
14499 |
<version>5.1</version> |
14500 |
<date>2005-08-25</date> |
14501 |
|
14502 |
<section> |
14503 |
<title>Introduction to Block Devices</title> |
14504 |
<subsection> |
14505 |
<title>Block Devices</title> |
14506 |
<body> |
14507 |
|
14508 |
<p> |
14509 |
We'll take a good look at some of the disk-oriented aspects of Gentoo Linux |
14510 |
and Linux in general, including Linux filesystems, partitions, and block |
14511 |
devices. Then, once you're familiar with the ins and outs of disks and |
14512 |
filesystems, you'll be guided through the process of setting up partitions |
14513 |
and filesystems for your Gentoo Linux installation. |
14514 |
</p> |
14515 |
|
14516 |
<p> |
14517 |
To begin, we introduce <e>block devices</e>. The most typical block device is |
14518 |
probably the one that represents the first SCSI hard disk in a Linux system, |
14519 |
namely <path>/dev/sda</path>. |
14520 |
</p> |
14521 |
|
14522 |
<p> |
14523 |
Block devices represent an abstract interface to the disk. User programs can |
14524 |
use these block devices to interact with your disk without worrying about |
14525 |
whether your drives are IDE, SCSI, or something else. The program can simply |
14526 |
address the storage on the disk as a bunch of contiguous, randomly-accessible |
14527 |
512-byte blocks. |
14528 |
</p> |
14529 |
|
14530 |
<p> |
14531 |
Block devices show up as entries in <path>/dev/</path>. Typically, the first |
14532 |
SCSI drive is named <path>/dev/sda</path>, the second <path>/dev/sdb</path>, |
14533 |
and so on. IDE drives are named similarly, however, they are prefixed by hd- |
14534 |
instead of sd-. If you are using IDE drives, the first one will be named |
14535 |
<path>/dev/hda</path>, the second <path>/dev/hdb</path>, and so on. |
14536 |
</p> |
14537 |
|
14538 |
</body> |
14539 |
</subsection> |
14540 |
<subsection> |
14541 |
<title>Partitions</title> |
14542 |
<body> |
14543 |
|
14544 |
<p> |
14545 |
Although it is theoretically possible to use the entire disk to house your Linux |
14546 |
system, this is almost never done in practice. Instead, full disk block devices |
14547 |
are split up in smaller, more manageable block devices. These are known as |
14548 |
<e>partitions</e> or <e>slices</e>. |
14549 |
</p> |
14550 |
|
14551 |
<p> |
14552 |
The first partition on the first SCSI disk is <path>/dev/sda1</path>, the second |
14553 |
<path>/dev/sda2</path> and so on. Similarly, the first two partitions on the |
14554 |
first IDE disk are <path>/dev/hda1</path> and <path>/dev/hda2</path>. |
14555 |
</p> |
14556 |
|
14557 |
<p> |
14558 |
The third partition on Sun systems is set aside as a special "whole disk" |
14559 |
slice. This partition must not contain a file system. |
14560 |
</p> |
14561 |
|
14562 |
<p> |
14563 |
Users who are used to the DOS partitioning scheme should note that Sun |
14564 |
disklabels do not have "primary" and "extended" partitions. Instead, up to |
14565 |
eight partitions are available per drive, with the third of these being |
14566 |
reserved. |
14567 |
</p> |
14568 |
|
14569 |
</body> |
14570 |
</subsection> |
14571 |
</section> |
14572 |
<section> |
14573 |
<title>Designing a Partitioning Scheme</title> |
14574 |
<subsection> |
14575 |
<title>Default Partitioning Scheme</title> |
14576 |
<body> |
14577 |
|
14578 |
<p> |
14579 |
If you are not interested in drawing up a partitioning scheme, |
14580 |
the table below suggests a suitable starting point for most systems. For |
14581 |
IDE-based systems, substitute <c>hda</c> for <c>sda</c> in the following. |
14582 |
</p> |
14583 |
|
14584 |
<p> |
14585 |
Note that a separate <path>/boot</path> partition is generally <e>not</e> |
14586 |
recommended on SPARC, as it complicates the bootloader configuration. |
14587 |
</p> |
14588 |
|
14589 |
<table> |
14590 |
<tr> |
14591 |
<th>Partition</th> |
14592 |
<th>Filesystem</th> |
14593 |
<th>Size</th> |
14594 |
<th>Mount Point</th> |
14595 |
<th>Description</th> |
14596 |
</tr> |
14597 |
<tr> |
14598 |
<ti>/dev/sda1</ti> |
14599 |
<ti>ext3</ti> |
14600 |
<ti><2 GByte</ti> |
14601 |
<ti>/</ti> |
14602 |
<ti> |
14603 |
Root partition. For all sparc32 systems, and sparc64 systems with older |
14604 |
OBP versions, this <e>must</e> be less than 2 GBytes in size, and the first |
14605 |
partition on the disk. |
14606 |
</ti> |
14607 |
</tr> |
14608 |
<tr> |
14609 |
<ti>/dev/sda2</ti> |
14610 |
<ti>swap</ti> |
14611 |
<ti>512 MBytes</ti> |
14612 |
<ti>none</ti> |
14613 |
<ti> |
14614 |
Swap partition. For bootstrap and certain larger compiles, at least 512 |
14615 |
MBytes of RAM (including swap) is required. |
14616 |
</ti> |
14617 |
</tr> |
14618 |
<tr> |
14619 |
<ti>/dev/sda3</ti> |
14620 |
<ti>none</ti> |
14621 |
<ti>Whole disk</ti> |
14622 |
<ti>none</ti> |
14623 |
<ti>Whole disk partition. This is required on SPARC systems.</ti> |
14624 |
</tr> |
14625 |
<tr> |
14626 |
<ti>/dev/sda4</ti> |
14627 |
<ti>ext3</ti> |
14628 |
<ti>at least 2 GBytes</ti> |
14629 |
<ti>/usr</ti> |
14630 |
<ti> |
14631 |
/usr partition. Applications are installed here. By default this partition |
14632 |
is also used for Portage data (which takes around 500 Mbyte excluding |
14633 |
source code). |
14634 |
</ti> |
14635 |
</tr> |
14636 |
<tr> |
14637 |
<ti>/dev/sda5</ti> |
14638 |
<ti>ext3</ti> |
14639 |
<ti>at least 1GByte</ti> |
14640 |
<ti>/var</ti> |
14641 |
<ti> |
14642 |
/var partition. Used for program-generated data. By default Portage uses |
14643 |
this partition for temporary space whilst compiling. Certain larger |
14644 |
applications such as Mozilla and OpenOffice.org can require over 1 GByte |
14645 |
of temporary space here when building. |
14646 |
</ti> |
14647 |
</tr> |
14648 |
<tr> |
14649 |
<ti>/dev/sda6</ti> |
14650 |
<ti>ext3</ti> |
14651 |
<ti>remaining space</ti> |
14652 |
<ti>/home</ti> |
14653 |
<ti>/home partition. Used for users' home directories.</ti> |
14654 |
</tr> |
14655 |
</table> |
14656 |
|
14657 |
</body> |
14658 |
</subsection> |
14659 |
</section> |
14660 |
|
14661 |
<section id="fdisk"> |
14662 |
<title>Using fdisk to Partition your Disk</title> |
14663 |
<subsection> |
14664 |
<body> |
14665 |
|
14666 |
<p> |
14667 |
The following parts explain how to create the example partition layout described |
14668 |
previously, namely: |
14669 |
</p> |
14670 |
|
14671 |
<table> |
14672 |
<tr> |
14673 |
<th>Partition</th> |
14674 |
<th>Description</th> |
14675 |
</tr> |
14676 |
<tr> |
14677 |
<ti>/dev/sda1</ti> |
14678 |
<ti>/</ti> |
14679 |
</tr> |
14680 |
<tr> |
14681 |
<ti>/dev/sda2</ti> |
14682 |
<ti>swap</ti> |
14683 |
</tr> |
14684 |
<tr> |
14685 |
<ti>/dev/sda3</ti> |
14686 |
<ti>whole disk slice</ti> |
14687 |
</tr> |
14688 |
<tr> |
14689 |
<ti>/dev/sda4</ti> |
14690 |
<ti>/usr</ti> |
14691 |
</tr> |
14692 |
<tr> |
14693 |
<ti>/dev/sda5</ti> |
14694 |
<ti>/var</ti> |
14695 |
</tr> |
14696 |
<tr> |
14697 |
<ti>/dev/sda6</ti> |
14698 |
<ti>/home</ti> |
14699 |
</tr> |
14700 |
</table> |
14701 |
|
14702 |
<p> |
14703 |
Change the partition layout as required. Remember to keep the root partition |
14704 |
entirely within the first 2 GBytes of the disk for older systems. There is also |
14705 |
a 15-partition limit for SCSI and SATA. |
14706 |
</p> |
14707 |
|
14708 |
</body> |
14709 |
</subsection> |
14710 |
<subsection> |
14711 |
<title>Firing up fdisk</title> |
14712 |
<body> |
14713 |
|
14714 |
<p> |
14715 |
Start <c>fdisk</c> with your disk as argument: |
14716 |
</p> |
14717 |
|
14718 |
<pre caption="Starting fdisk"> |
14719 |
# <i>fdisk /dev/sda</i> |
14720 |
</pre> |
14721 |
|
14722 |
<p> |
14723 |
You should be greeted with the fdisk prompt: |
14724 |
</p> |
14725 |
|
14726 |
<pre caption="The fdisk prompt"> |
14727 |
Command (m for help): |
14728 |
</pre> |
14729 |
|
14730 |
<p> |
14731 |
To view the available partitions, type in <c>p</c>: |
14732 |
</p> |
14733 |
|
14734 |
<pre caption="Listing available partitions"> |
14735 |
Command (m for help): <i>p</i> |
14736 |
|
14737 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
14738 |
Units = cylinders of 2048 * 512 bytes |
14739 |
|
14740 |
Device Flag Start End Blocks Id System |
14741 |
/dev/sda1 0 488 499712 83 Linux native |
14742 |
/dev/sda2 488 976 499712 82 Linux swap |
14743 |
/dev/sda3 0 8635 8842240 5 Whole disk |
14744 |
/dev/sda4 976 1953 1000448 83 Linux native |
14745 |
/dev/sda5 1953 2144 195584 83 Linux native |
14746 |
/dev/sda6 2144 8635 6646784 83 Linux native |
14747 |
</pre> |
14748 |
|
14749 |
<p> |
14750 |
Note the <c>Sun disk label</c> in the output. If this is missing, the disk is |
14751 |
using the DOS-partitioning, not the Sun partitioning. In this case, use <c>s</c> |
14752 |
to ensure that the disk has a sun partition table: |
14753 |
</p> |
14754 |
|
14755 |
<pre caption="Creating a Sun Disklabel"> |
14756 |
Command (m for help): s |
14757 |
Building a new sun disklabel. Changes will remain in memory only, |
14758 |
until you decide to write them. After that, of course, the previous |
14759 |
content won't be recoverable. |
14760 |
|
14761 |
Drive type |
14762 |
? auto configure |
14763 |
0 custom (with hardware detected defaults) |
14764 |
a Quantum ProDrive 80S |
14765 |
b Quantum ProDrive 105S |
14766 |
c CDC Wren IV 94171-344 |
14767 |
d IBM DPES-31080 |
14768 |
e IBM DORS-32160 |
14769 |
f IBM DNES-318350 |
14770 |
g SEAGATE ST34371 |
14771 |
h SUN0104 |
14772 |
i SUN0207 |
14773 |
j SUN0327 |
14774 |
k SUN0340 |
14775 |
l SUN0424 |
14776 |
m SUN0535 |
14777 |
n SUN0669 |
14778 |
o SUN1.0G |
14779 |
p SUN1.05 |
14780 |
q SUN1.3G |
14781 |
r SUN2.1G |
14782 |
s IOMEGA Jaz |
14783 |
Select type (? for auto, 0 for custom): <i>0</i> |
14784 |
Heads (1-1024, default 64): |
14785 |
Using default value 64 |
14786 |
Sectors/track (1-1024, default 32): |
14787 |
Using default value 32 |
14788 |
Cylinders (1-65535, default 8635): |
14789 |
Using default value 8635 |
14790 |
Alternate cylinders (0-65535, default 2): |
14791 |
Using default value 2 |
14792 |
Physical cylinders (0-65535, default 8637): |
14793 |
Using default value 8637 |
14794 |
Rotation speed (rpm) (1-100000, default 5400): <i>10000</i> |
14795 |
Interleave factor (1-32, default 1): |
14796 |
Using default value 1 |
14797 |
Extra sectors per cylinder (0-32, default 0): |
14798 |
Using default value 0 |
14799 |
</pre> |
14800 |
|
14801 |
<p> |
14802 |
You can find the correct values in your disk's documentation. The |
14803 |
'auto configure' option does not usually work. |
14804 |
</p> |
14805 |
|
14806 |
</body> |
14807 |
</subsection> |
14808 |
<subsection> |
14809 |
<title>Deleting Existing Partitions</title> |
14810 |
<body> |
14811 |
|
14812 |
<p> |
14813 |
It's time to delete any existing partitions. To do this, type <c>d</c> and hit |
14814 |
Enter. You will then be prompted for the partition number you would like to |
14815 |
delete. To delete a pre-existing <path>/dev/sda1</path>, you would type: |
14816 |
</p> |
14817 |
|
14818 |
<pre caption="Deleting a partition"> |
14819 |
Command (m for help): <i>d</i> |
14820 |
Partition number (1-4): <i>1</i> |
14821 |
</pre> |
14822 |
|
14823 |
<p> |
14824 |
<e>You should not delete partition 3 (whole disk).</e> This is required. If |
14825 |
this partition does not exist, follow the "Creating a Sun Disklabel" |
14826 |
instructions above. |
14827 |
</p> |
14828 |
|
14829 |
<p> |
14830 |
After deleting all partitions except the Whole disk slice, you should have a |
14831 |
partition layout similar to the following: |
14832 |
</p> |
14833 |
|
14834 |
<pre caption="View an empty partition scheme"> |
14835 |
Command (m for help): <i>p</i> |
14836 |
|
14837 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
14838 |
Units = cylinders of 2048 * 512 bytes |
14839 |
|
14840 |
Device Flag Start End Blocks Id System |
14841 |
/dev/sda3 0 8635 8842240 5 Whole disk |
14842 |
</pre> |
14843 |
|
14844 |
|
14845 |
</body> |
14846 |
</subsection> |
14847 |
|
14848 |
<subsection> |
14849 |
<title>Creating the Root Partition</title> |
14850 |
<body> |
14851 |
|
14852 |
<p> |
14853 |
We're ready to create the root partition. To do this, type <c>n</c> to create a |
14854 |
new partition, then type <c>1</c> to create the partition. When prompted for |
14855 |
the first cylinder, hit enter. When prompted for the last cylinder, type |
14856 |
<c>+512M</c> to create a partition <c>512MBytes</c> in size. Make sure that the |
14857 |
entire root partition fits within the first 2GBytes of the disk. You can see |
14858 |
output from these steps below: |
14859 |
</p> |
14860 |
|
14861 |
<pre caption="Creating a root partition"> |
14862 |
Command (m for help): <i>n</i> |
14863 |
Partition number (1-8): <i>1</i> |
14864 |
First cylinder (0-8635): <i>(press Enter)</i> |
14865 |
Last cylinder or +size or +sizeM or +sizeK (0-8635, default 8635): <i>+512M</i> |
14866 |
</pre> |
14867 |
|
14868 |
<p> |
14869 |
Now, when you type <c>p</c>, you should see the following partition printout: |
14870 |
</p> |
14871 |
|
14872 |
<pre caption="Listing the partition layout"> |
14873 |
Command (m for help): <i>p</i> |
14874 |
|
14875 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
14876 |
Units = cylinders of 2048 * 512 bytes |
14877 |
|
14878 |
Device Flag Start End Blocks Id System |
14879 |
/dev/sda1 0 488 499712 83 Linux native |
14880 |
/dev/sda3 0 8635 8842240 5 Whole disk |
14881 |
</pre> |
14882 |
|
14883 |
</body> |
14884 |
</subsection> |
14885 |
<subsection> |
14886 |
<title>Creating a swap partition</title> |
14887 |
<body> |
14888 |
|
14889 |
<p> |
14890 |
Next, let's create the swap partition. To do this, type <c>n</c> to create a new |
14891 |
partition, then <c>2</c> to create the second partition, <path>/dev/sda2</path> |
14892 |
in our case. When prompted for the first cylinder, hit enter. When prompted for |
14893 |
the last cylinder, type <c>+512M</c> to create a partition 512MB in size. After |
14894 |
you've done this, type <c>t</c> to set the partition type, and then type in |
14895 |
<c>82</c> to set the partition type to "Linux Swap". After completing these |
14896 |
steps, typing <c>p</c> should display a partition table that looks similar to |
14897 |
this: |
14898 |
</p> |
14899 |
|
14900 |
<pre caption="Listing of available partitions"> |
14901 |
Command (m for help): <i>p</i> |
14902 |
|
14903 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
14904 |
Units = cylinders of 2048 * 512 bytes |
14905 |
|
14906 |
Device Flag Start End Blocks Id System |
14907 |
/dev/sda1 0 488 499712 83 Linux native |
14908 |
/dev/sda2 488 976 499712 82 Linux swap |
14909 |
/dev/sda3 0 8635 8842240 5 Whole disk |
14910 |
</pre> |
14911 |
|
14912 |
</body> |
14913 |
</subsection> |
14914 |
<subsection> |
14915 |
<title>Creating the /usr, /var and /home partitions</title> |
14916 |
<body> |
14917 |
|
14918 |
<p> |
14919 |
Finally, let's create the /usr, /var and /home partitions. As before, |
14920 |
type <c>n</c> to create a new partition, then type <c>4</c> to create the |
14921 |
third partition, <path>/dev/sda4</path> in our case. When prompted for the |
14922 |
first cylinder, hit enter. When prompted for the last cylinder, enter |
14923 |
<c>+2048M</c> to create a partition 2 GBytes in size. Repeat this process |
14924 |
for <path>sda5</path> and <path>sda6</path>, using the desired sizes. Once |
14925 |
you're done, you should see something like this: |
14926 |
</p> |
14927 |
|
14928 |
<pre caption="Listing complete partition table"> |
14929 |
Command (m for help): <i>p</i> |
14930 |
|
14931 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
14932 |
Units = cylinders of 2048 * 512 bytes |
14933 |
|
14934 |
Device Flag Start End Blocks Id System |
14935 |
/dev/sda1 0 488 499712 83 Linux native |
14936 |
/dev/sda2 488 976 499712 82 Linux swap |
14937 |
/dev/sda3 0 8635 8842240 5 Whole disk |
14938 |
/dev/sda4 976 1953 1000448 83 Linux native |
14939 |
/dev/sda5 1953 2144 195584 83 Linux native |
14940 |
/dev/sda6 2144 8635 6646784 83 Linux native |
14941 |
</pre> |
14942 |
|
14943 |
</body> |
14944 |
</subsection> |
14945 |
<subsection> |
14946 |
<title>Save and Exit</title> |
14947 |
<body> |
14948 |
|
14949 |
<p> |
14950 |
To save your partition layout and exit <c>fdisk</c>, type <c>w</c>: |
14951 |
</p> |
14952 |
|
14953 |
<pre caption="Save and exit fdisk"> |
14954 |
Command (m for help): <i>w</i> |
14955 |
</pre> |
14956 |
|
14957 |
<p> |
14958 |
Now that your partitions are created, you can now continue with <uri |
14959 |
link="#filesystems">Creating Filesystems</uri>. |
14960 |
</p> |
14961 |
|
14962 |
</body> |
14963 |
</subsection> |
14964 |
</section> |
14965 |
<section id="filesystems"> |
14966 |
<title>Creating Filesystems</title> |
14967 |
<subsection> |
14968 |
<title>Introduction</title> |
14969 |
<body> |
14970 |
|
14971 |
<p> |
14972 |
Now that your partitions are created, it is time to place a filesystem on them. |
14973 |
If you don't care about what filesystem to choose and are happy with what is |
14974 |
used as default in this handbook, continue with <uri |
14975 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
14976 |
Otherwise, read on to learn about the available filesystems... |
14977 |
</p> |
14978 |
|
14979 |
</body> |
14980 |
</subsection> |
14981 |
<subsection> |
14982 |
<title>Filesystems?</title> |
14983 |
<body> |
14984 |
|
14985 |
<p> |
14986 |
Several filesystems are available, some are known to be stable on the |
14987 |
SPARC architecture. Ext2 and ext3, for example, are known to work well. |
14988 |
Alternate filesystems may not function correctly. |
14989 |
</p> |
14990 |
|
14991 |
<p> |
14992 |
<b>ext2</b> is the tried-and-true Linux filesystem. It does not support |
14993 |
journaling, which means that periodic checks of ext2 filesystems at startup |
14994 |
can be quite time-consuming. There is quite a selection of newer-generation |
14995 |
journaled filesystems that can be checked for consistency very quickly at |
14996 |
startup, and are therefore generally preferred over their non-journaled |
14997 |
counterparts. In general, journaled filesystems prevent long delays when a |
14998 |
system is booted and the filesystem is in an inconsistent state. |
14999 |
</p> |
15000 |
|
15001 |
<p> |
15002 |
<b>ext3</b> is the journaled version of the ext2 filesystem. It provides |
15003 |
metadata journaling for fast recovery as well as other enhanced journaling |
15004 |
modes like full-data and ordered-data journaling. Ext3 has an additional hashed |
15005 |
b-tree indexing option that enables high performance in almost all situations. |
15006 |
You can enable this indexing by adding <c>-O dir_index</c> to the <c>mke2fs</c> |
15007 |
command. Ext3 makes an excellent and reliable alternative to ext2. |
15008 |
</p> |
15009 |
|
15010 |
</body> |
15011 |
</subsection> |
15012 |
<subsection id="filesystems-apply"> |
15013 |
<title>Applying a Filesystem to a Partition</title> |
15014 |
<body> |
15015 |
|
15016 |
<p> |
15017 |
To create a filesystem on a partition or volume, tools specific to the chosen |
15018 |
filesystem are available: |
15019 |
</p> |
15020 |
|
15021 |
<table> |
15022 |
<tr> |
15023 |
<th>Filesystem</th> |
15024 |
<th>Creation Command</th> |
15025 |
</tr> |
15026 |
<tr> |
15027 |
<ti>ext2</ti> |
15028 |
<ti><c>mke2fs</c></ti> |
15029 |
</tr> |
15030 |
<tr> |
15031 |
<ti>ext3</ti> |
15032 |
<ti><c>mke2fs -j</c></ti> |
15033 |
</tr> |
15034 |
<tr> |
15035 |
<ti>ext3 with hashed b-tree indexing (2.6 kernels only)</ti> |
15036 |
<ti><c>mke2fs -j -O dir_index</c></ti> |
15037 |
</tr> |
15038 |
</table> |
15039 |
|
15040 |
<p> |
15041 |
For instance, to create the root partition (<path>/dev/sda1</path> in our |
15042 |
example) as ext2, and the <path>/usr</path>, <path>/var</path>, and |
15043 |
<path>/home</path> partitions (<path>/dev/sda4</path>, <path>5</path> |
15044 |
and <path>6</path> in our example, respectively) as ext3, you would use: |
15045 |
</p> |
15046 |
|
15047 |
<pre caption="Applying a filesystem on a partition"> |
15048 |
# <i>mke2fs /dev/sda1</i> |
15049 |
# <i>mke2fs -j /dev/sda4</i> |
15050 |
# <i>mke2fs -j /dev/sda5</i> |
15051 |
# <i>mke2fs -j /dev/sda6</i> |
15052 |
</pre> |
15053 |
|
15054 |
</body> |
15055 |
</subsection> |
15056 |
<subsection> |
15057 |
<title>Activating the Swap Partition</title> |
15058 |
<body> |
15059 |
|
15060 |
<p> |
15061 |
<c>mkswap</c> is the command used to initialize swap partitions: |
15062 |
</p> |
15063 |
|
15064 |
<pre caption="Creating a Swap signature"> |
15065 |
# <i>mkswap /dev/sda2</i> |
15066 |
</pre> |
15067 |
|
15068 |
<p> |
15069 |
To activate the swap partition, use <c>swapon</c>: |
15070 |
</p> |
15071 |
|
15072 |
<pre caption="Activating the swap partition"> |
15073 |
# <i>swapon /dev/sda2</i> |
15074 |
</pre> |
15075 |
|
15076 |
<p> |
15077 |
Create and activate the swap now. |
15078 |
</p> |
15079 |
|
15080 |
</body> |
15081 |
</subsection> |
15082 |
</section> |
15083 |
<section> |
15084 |
<title>Mounting</title> |
15085 |
<body> |
15086 |
|
15087 |
<p> |
15088 |
Now that your partitions are initialized and are housing a filesystem, it is |
15089 |
time to mount them using the <c>mount</c> command. Don't forget to first |
15090 |
create the necessary mount directories for every partition you created. For |
15091 |
example: |
15092 |
</p> |
15093 |
|
15094 |
<pre caption="Mounting partitions"> |
15095 |
# <i>mount /dev/sda1 /mnt/gentoo</i> |
15096 |
# <i>mkdir /mnt/gentoo/usr</i> |
15097 |
# <i>mount /dev/sda4 /mnt/gentoo/usr</i> |
15098 |
# <i>mkdir /mnt/gentoo/var</i> |
15099 |
# <i>mount /dev/sda5 /mnt/gentoo/var</i> |
15100 |
# <i>mkdir /mnt/gentoo/home</i> |
15101 |
# <i>mount /dev/sda6 /mnt/gentoo/home</i> |
15102 |
</pre> |
15103 |
|
15104 |
<note> |
15105 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure |
15106 |
to change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. |
15107 |
This also holds for <path>/var/tmp</path>. |
15108 |
</note> |
15109 |
|
15110 |
<p> |
15111 |
We will also have to mount the proc filesystem (a virtual interface with the |
15112 |
kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. |
15113 |
</p> |
15114 |
|
15115 |
<p> |
15116 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
15117 |
Installation Files</uri>. |
15118 |
</p> |
15119 |
|
15120 |
</body> |
15121 |
</section> |
15122 |
</sections> |
15123 |
|
15124 |
|
15125 |
|
15126 |
|
15127 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-sparc-kernel.xml |
15128 |
|
15129 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-sparc-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
15130 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-sparc-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
15131 |
|
15132 |
Index: hb-install-sparc-kernel.xml |
15133 |
=================================================================== |
15134 |
<?xml version='1.0' encoding='UTF-8'?> |
15135 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
15136 |
|
15137 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
15138 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
15139 |
|
15140 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-sparc-kernel.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
15141 |
|
15142 |
<sections> |
15143 |
|
15144 |
<version>5.5</version> |
15145 |
<date>2006-01-06</date> |
15146 |
|
15147 |
<section> |
15148 |
<title>Timezone</title> |
15149 |
<body> |
15150 |
|
15151 |
<p> |
15152 |
You first need to select your timezone so that your system knows where it is |
15153 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
15154 |
it to <path>/etc/localtime</path>. Please avoid the |
15155 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
15156 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
15157 |
</p> |
15158 |
|
15159 |
<pre caption="Setting the timezone information"> |
15160 |
# <i>ls /usr/share/zoneinfo</i> |
15161 |
<comment>(Suppose you want to use GMT)</comment> |
15162 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
15163 |
</pre> |
15164 |
|
15165 |
</body> |
15166 |
</section> |
15167 |
<section> |
15168 |
<title>Installing the Sources</title> |
15169 |
<subsection> |
15170 |
<title>Choosing a Kernel</title> |
15171 |
<body> |
15172 |
|
15173 |
<p> |
15174 |
The core around which all distributions are built is the Linux kernel. It is the |
15175 |
layer between the user programs and your system hardware. Gentoo provides its |
15176 |
users several possible kernel sources. A full listing with description is |
15177 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
15178 |
Guide</uri>. |
15179 |
</p> |
15180 |
|
15181 |
<p> |
15182 |
For sparc-based systems we have <c>sparc-sources</c> (kernel source optimized |
15183 |
for SPARC users) and <c>vanilla-sources</c> (the default kernel source as |
15184 |
developed by the linux-kernel developers). |
15185 |
</p> |
15186 |
|
15187 |
<p> |
15188 |
In the next example we install the <c>sparc-sources</c>. Of course substitute |
15189 |
with your choice of sources, this is merely an example. The <c>USE="-doc"</c> |
15190 |
is necessary to avoid installing xorg-x11 or other dependencies at this point. |
15191 |
<c>USE="symlink"</c> is not necessary for a new install, but ensures proper |
15192 |
creation of the <path>/usr/src/linux</path> symlink. |
15193 |
</p> |
15194 |
|
15195 |
<pre caption="Installing a kernel source"> |
15196 |
# <i>USE="-doc symlink" emerge sparc-sources</i> |
15197 |
</pre> |
15198 |
|
15199 |
<p> |
15200 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
15201 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
15202 |
kernel source points to <c>sparc-sources-2.4.31</c>. Your version may be |
15203 |
different, so keep this in mind. |
15204 |
</p> |
15205 |
|
15206 |
<pre caption="Viewing the kernel source symlink"> |
15207 |
# <i>ls -l /usr/src/linux</i> |
15208 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-2.4.31-sparc |
15209 |
</pre> |
15210 |
|
15211 |
<p> |
15212 |
Now it is time to configure and compile your kernel source. |
15213 |
</p> |
15214 |
|
15215 |
</body> |
15216 |
</subsection> |
15217 |
</section> |
15218 |
<section> |
15219 |
<title>Manual Configuration</title> |
15220 |
<subsection> |
15221 |
<title>Introduction</title> |
15222 |
<body> |
15223 |
|
15224 |
<p> |
15225 |
Manually configuring a kernel is often seen as the most difficult procedure a |
15226 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
15227 |
couple of kernels you don't even remember that it was difficult ;) |
15228 |
</p> |
15229 |
|
15230 |
<p> |
15231 |
However, one thing <e>is</e> true: you must know your system when you start |
15232 |
configuring a kernel manually. Most information can be gathered by emerging |
15233 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
15234 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
15235 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
15236 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
15237 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
15238 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
15239 |
uses (it might provide you with a nice hint on what to enable). |
15240 |
</p> |
15241 |
|
15242 |
<p> |
15243 |
Now go to your kernel source directory and execute <c>make menuconfig</c>. This |
15244 |
will fire up an ncurses-based configuration menu. |
15245 |
</p> |
15246 |
|
15247 |
<pre caption="Invoking menuconfig"> |
15248 |
# <i>cd /usr/src/linux</i> |
15249 |
# <i>make menuconfig</i> |
15250 |
</pre> |
15251 |
|
15252 |
<p> |
15253 |
You will be greeted with several configuration sections. We'll first list some |
15254 |
options you must activate (otherwise Gentoo will not function, or not function |
15255 |
properly without additional tweaks). |
15256 |
</p> |
15257 |
|
15258 |
</body> |
15259 |
</subsection> |
15260 |
<subsection> |
15261 |
<title>Activating Required Options</title> |
15262 |
<body> |
15263 |
|
15264 |
<p> |
15265 |
First of all, activate the use of development and experimental code/drivers. |
15266 |
You need this, otherwise some very important code/drivers won't show up: |
15267 |
</p> |
15268 |
|
15269 |
<pre caption="Selecting experimental code/drivers"> |
15270 |
Code maturity level options ---> |
15271 |
[*] Prompt for development and/or incomplete code/drivers |
15272 |
</pre> |
15273 |
|
15274 |
<p> |
15275 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
15276 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
15277 |
able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc |
15278 |
file system</c>. If you are running a 2.4 kernel, you should also select |
15279 |
<c>/dev file system</c> + <c>Automatically mount at boot</c>: |
15280 |
</p> |
15281 |
|
15282 |
<pre caption="Selecting necessary file systems"> |
15283 |
File systems ---> |
15284 |
[*] Virtual memory file system support (former shm fs) |
15285 |
[*] /proc file system support |
15286 |
[ ] /dev/pts file system for Unix98 PTYs |
15287 |
|
15288 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
15289 |
<*> Ext3 journalling file system support |
15290 |
<*> Second extended fs support |
15291 |
</pre> |
15292 |
|
15293 |
<p> |
15294 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
15295 |
modem, you will need the following options in the kernel: |
15296 |
</p> |
15297 |
|
15298 |
<pre caption="Selecting PPPoE necessary drivers"> |
15299 |
Network device support ---> |
15300 |
<*> PPP (point-to-point protocol) support |
15301 |
<*> PPP support for async serial ports |
15302 |
<*> PPP support for sync tty ports |
15303 |
</pre> |
15304 |
|
15305 |
<p> |
15306 |
The two compression options won't harm but are not definitely needed, neither |
15307 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
15308 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
15309 |
</p> |
15310 |
|
15311 |
<p> |
15312 |
Now activate the correct bus-support: |
15313 |
</p> |
15314 |
|
15315 |
<pre caption="Activating SBUS/UPA"> |
15316 |
Console drivers ---> |
15317 |
Frame-buffer support ---> |
15318 |
[*] SBUS and UPA framebuffers |
15319 |
[*] Creator/Creator3D support <comment>(Only for UPA slot adapter used in many Ultras)</comment> |
15320 |
[*] CGsix (GX,TurboGX) support <comment>(Only for SBUS slot adapter used in many SPARCStations)</comment> |
15321 |
</pre> |
15322 |
|
15323 |
<p> |
15324 |
Of course you want support for the OBP: |
15325 |
</p> |
15326 |
|
15327 |
<pre caption="Activating OBP Support"> |
15328 |
Misc Linux/SPARC drivers ---> |
15329 |
[*] /dev/openprom device support |
15330 |
</pre> |
15331 |
|
15332 |
<p> |
15333 |
You will also need SCSI-specific support: |
15334 |
</p> |
15335 |
|
15336 |
<pre caption="Activating SCSI-specific support"> |
15337 |
SCSI support ---> |
15338 |
SCSI low-level drivers ---> |
15339 |
<*> Sparc ESP Scsi Driver <comment>(Only for SPARC ESP on-board SCSI adapter)</comment> |
15340 |
<*> PTI Qlogic, ISP Driver <comment>(Only for SBUS SCSI controllers from PTI or QLogic)</comment> |
15341 |
<*> SYM53C8XX Version 2 SCSI support <comment>(Only for Ultra 60 on-board SCSI adapter)</comment> |
15342 |
</pre> |
15343 |
|
15344 |
<p> |
15345 |
To support your network card, select one of the following: |
15346 |
</p> |
15347 |
|
15348 |
<pre caption="Activating networking support"> |
15349 |
Network device support ---> |
15350 |
Ethernet (10 or 100Mbit) ---> |
15351 |
<*> Sun LANCE support <comment>(Only for SPARCStation, older Ultra systems, and as Sbus option)</comment> |
15352 |
<*> Sun Happy Meal 10/100baseT support <comment>(Only for Ultra; also supports "qfe" quad-ethernet on PCI and Sbus)</comment> |
15353 |
<*> DECchip Tulip (dc21x4x) PCI support <comment>(For some Netras, like N1)</comment> |
15354 |
Ethernet (1000Mbit) ---> |
15355 |
<*> Broadcom Tigon3 support <comment>(Modern Netra, Sun Fire machines)</comment> |
15356 |
</pre> |
15357 |
|
15358 |
<p> |
15359 |
When you have a 4-port Ethernet machine (10/100 or 10/100/1000) the port order |
15360 |
is different from the one used by Solaris. You can use <c>sys-apps/ethtool</c> |
15361 |
or <c>mii-tool</c> to check the port link status. |
15362 |
</p> |
15363 |
|
15364 |
<p> |
15365 |
When you're done configuring your kernel, continue with <uri |
15366 |
link="#compiling">Compiling and Installing</uri>. However, after having |
15367 |
compiled the kernel, check its size: |
15368 |
</p> |
15369 |
|
15370 |
<pre caption="Check kernel size"> |
15371 |
# <i>ls -lh vmlinux</i> |
15372 |
-rw-r--r-- 1 root root 2.4M Oct 25 14:38 vmlinux |
15373 |
</pre> |
15374 |
|
15375 |
<p> |
15376 |
If the (uncompressed) size is bigger than 2.5 MB (for Sparc32) or 3.5 MB (for |
15377 |
Sparc64), reconfigure your kernel until it doesn't exceed these limits. One way |
15378 |
of accomplishing this is by having most kernel drivers compiled as modules. |
15379 |
Ignoring this can lead to a non-booting kernel. |
15380 |
</p> |
15381 |
|
15382 |
<p> |
15383 |
Also, if your kernel is just a tad too big, you can try stripping it using the |
15384 |
<c>strip</c> command: |
15385 |
</p> |
15386 |
|
15387 |
<pre caption="Stripping the kernel"> |
15388 |
# <i>strip -R .comment -R .note vmlinux</i> |
15389 |
</pre> |
15390 |
|
15391 |
</body> |
15392 |
</subsection> |
15393 |
<subsection id="compiling"> |
15394 |
<title>Compiling and Installing</title> |
15395 |
<body> |
15396 |
|
15397 |
<p> |
15398 |
Now that your kernel is configured, it is time to compile and install it. Exit |
15399 |
the configuration and start the compilation process: |
15400 |
</p> |
15401 |
|
15402 |
<pre caption="Compiling the kernel"> |
15403 |
<comment>(sparc32)</comment> |
15404 |
# <i>make dep && make clean vmlinux modules modules_install</i> |
15405 |
|
15406 |
<comment>(sparc64)</comment> |
15407 |
# <i>make dep && make clean vmlinux image modules modules_install</i> |
15408 |
</pre> |
15409 |
|
15410 |
<p> |
15411 |
When the kernel has finished compiling, copy the kernel image to |
15412 |
<path>/boot</path>. Remember to replace <path><kernel-version></path> |
15413 |
with your actual kernel version. |
15414 |
</p> |
15415 |
|
15416 |
<pre caption="Installing the kernel"> |
15417 |
<comment>(sparc32)</comment> |
15418 |
# <i>cp vmlinux /boot/<kernel-version></i> |
15419 |
|
15420 |
<comment>(sparc64)</comment> |
15421 |
# <i>cp arch/sparc64/boot/image /boot/<kernel-version></i> |
15422 |
</pre> |
15423 |
|
15424 |
<p> |
15425 |
Now continue with <uri link="#kernel_modules">Installing Separate Kernel |
15426 |
Modules</uri>. |
15427 |
</p> |
15428 |
|
15429 |
</body> |
15430 |
</subsection> |
15431 |
</section> |
15432 |
<section id="kernel_modules"> |
15433 |
<title>Installing Separate Kernel Modules</title> |
15434 |
<subsection> |
15435 |
<title>Configuring the Modules</title> |
15436 |
<body> |
15437 |
|
15438 |
<p> |
15439 |
You should list the modules you want automatically loaded in |
15440 |
<path>/etc/modules.autoload.d/kernel-2.4</path>. |
15441 |
You can add extra options to the modules too if you want. |
15442 |
</p> |
15443 |
|
15444 |
<p> |
15445 |
To view all available modules, run the following <c>find</c> command. Don't |
15446 |
forget to substitute "<kernel version>" with the version of the kernel you |
15447 |
just compiled: |
15448 |
</p> |
15449 |
|
15450 |
<pre caption="Viewing all available modules"> |
15451 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
15452 |
</pre> |
15453 |
|
15454 |
<p> |
15455 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
15456 |
<path>kernel-2.4</path> file and enter the module name in it. |
15457 |
</p> |
15458 |
|
15459 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.4"> |
15460 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.4</i> |
15461 |
</pre> |
15462 |
|
15463 |
<pre caption="/etc/modules.autoload.d/kernel-2.4"> |
15464 |
3c59x |
15465 |
</pre> |
15466 |
|
15467 |
<p> |
15468 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
15469 |
your System</uri>. |
15470 |
</p> |
15471 |
|
15472 |
</body> |
15473 |
</subsection> |
15474 |
</section> |
15475 |
</sections> |
15476 |
|
15477 |
|
15478 |
|
15479 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-sparc-medium.xml |
15480 |
|
15481 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-sparc-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
15482 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-sparc-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
15483 |
|
15484 |
Index: hb-install-sparc-medium.xml |
15485 |
=================================================================== |
15486 |
<?xml version='1.0' encoding='UTF-8'?> |
15487 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
15488 |
|
15489 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
15490 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
15491 |
|
15492 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-sparc-medium.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
15493 |
|
15494 |
<sections> |
15495 |
|
15496 |
<version>5.4</version> |
15497 |
<date>2005-11-29</date> |
15498 |
|
15499 |
<section> |
15500 |
<title>Hardware Requirements</title> |
15501 |
<subsection> |
15502 |
<title>Introduction</title> |
15503 |
<body> |
15504 |
|
15505 |
<p> |
15506 |
Before we start, we first list what hardware requirements you need to |
15507 |
successfully install Gentoo on your box. |
15508 |
</p> |
15509 |
|
15510 |
</body> |
15511 |
</subsection> |
15512 |
<subsection> |
15513 |
<title>Hardware Requirements</title> |
15514 |
<body> |
15515 |
|
15516 |
<table> |
15517 |
<tr> |
15518 |
<th>Sparc System</th> |
15519 |
<ti> |
15520 |
Please check the <uri |
15521 |
link="http://www.ultralinux.org/faq.html#s_2">UltraLinux FAQ</uri> |
15522 |
</ti> |
15523 |
</tr> |
15524 |
<tr> |
15525 |
<th>CPU</th> |
15526 |
<ti> |
15527 |
Although sparc64 is the only officially supported platform, experimental |
15528 |
support for sparc32 is available as well |
15529 |
</ti> |
15530 |
</tr> |
15531 |
<tr> |
15532 |
<th>Memory</th> |
15533 |
<ti>64 MB</ti> |
15534 |
</tr> |
15535 |
<tr> |
15536 |
<th>Diskspace</th> |
15537 |
<ti>1.5 GB (excluding swap space)</ti> |
15538 |
</tr> |
15539 |
<tr> |
15540 |
<th>Swap space</th> |
15541 |
<ti>At least 256 MB</ti> |
15542 |
</tr> |
15543 |
</table> |
15544 |
|
15545 |
<p> |
15546 |
We currently only provide Installation CDs for the sparc64 architecture. Users |
15547 |
of sparc32 can use the experimental netboot images to install Gentoo from. |
15548 |
More information about netbooting can be found in our <uri |
15549 |
link="/doc/en/gentoo-sparc-netboot-howto.xml">Gentoo Linux based Netboot |
15550 |
HOWTO</uri>. |
15551 |
</p> |
15552 |
|
15553 |
</body> |
15554 |
</subsection> |
15555 |
</section> |
15556 |
<!-- Copy/Paste from hb-install-x86-medium.xml --> |
15557 |
<!-- START --> |
15558 |
<section> |
15559 |
<title>The Gentoo Universal Installation CD</title> |
15560 |
<subsection> |
15561 |
<title>Introduction</title> |
15562 |
<body> |
15563 |
|
15564 |
<p> |
15565 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
15566 |
Such a tarball is an archive that contains a minimal environment from |
15567 |
which you can successfully install Gentoo Linux onto your system. |
15568 |
</p> |
15569 |
|
15570 |
<p> |
15571 |
Installations using a stage1 or stage2 tarball file are not documented in the |
15572 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
15573 |
FAQ</uri> on these matters. |
15574 |
</p> |
15575 |
|
15576 |
</body> |
15577 |
</subsection> |
15578 |
<subsection> |
15579 |
<title>Gentoo Universal Installation CD</title> |
15580 |
<body> |
15581 |
|
15582 |
<p> |
15583 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
15584 |
environment. It allows you to boot Linux from the CD. During the boot process |
15585 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
15586 |
Installation CDs are maintained by Gentoo developers. |
15587 |
</p> |
15588 |
|
15589 |
<p> |
15590 |
There currently are two Installation CDs available: |
15591 |
</p> |
15592 |
|
15593 |
<ul> |
15594 |
<li> |
15595 |
The Universal Installation CD contains everything you need to install |
15596 |
Gentoo. It provides stage3 files for common architectures, source code |
15597 |
for the extra applications you need to choose from and, of course, the |
15598 |
installation instructions for your architecture. |
15599 |
</li> |
15600 |
<li> |
15601 |
The Minimal Installation CD contains only a minimal environment that allows |
15602 |
you to boot up and configure your network so you can connect to the |
15603 |
Internet. It does not contain any additional files and cannot be used |
15604 |
during the current installation approach. |
15605 |
</li> |
15606 |
</ul> |
15607 |
|
15608 |
<p> |
15609 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
15610 |
additional resource that you can exploit during the installation of your Gentoo |
15611 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
15612 |
you to easily and quickly install additional applications (such as |
15613 |
OpenOffice.org, KDE, GNOME, ...) immediately after the Gentoo installation and |
15614 |
right before you update your Portage tree. |
15615 |
</p> |
15616 |
|
15617 |
<p> |
15618 |
The use of the Package CD is covered later in this document. |
15619 |
</p> |
15620 |
|
15621 |
</body> |
15622 |
</subsection> |
15623 |
</section> |
15624 |
<!-- STOP --> |
15625 |
<section> |
15626 |
<title>Download, Burn and Boot a Gentoo Installation CD</title> |
15627 |
<subsection> |
15628 |
<title>Downloading and Burning the Installation CDs</title> |
15629 |
<body> |
15630 |
|
15631 |
<p> |
15632 |
You can download the Universal Installation CD (and, if you want to, the |
15633 |
Packages CD as well) from one of our <uri |
15634 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located in |
15635 |
the <path>releases/sparc/2005.1-r1/sparc64/installcd</path> |
15636 |
directory; the Package CDs are located in the |
15637 |
<path>releases/sparc/2005.1/sparc64/packagecd</path> directory. |
15638 |
</p> |
15639 |
|
15640 |
<p> |
15641 |
Inside those directories you'll find ISO-files. Those are full CD images which |
15642 |
you can write on a CD-R. |
15643 |
</p> |
15644 |
|
15645 |
<p> |
15646 |
After downloading the file, you can verify its integrity to see if it is |
15647 |
corrupted or not: |
15648 |
</p> |
15649 |
|
15650 |
<ul> |
15651 |
<li> |
15652 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
15653 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
15654 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows) |
15655 |
</li> |
15656 |
<li> |
15657 |
You can verify the cryptographic signature that we provide. You need to |
15658 |
obtain the public key we use (17072058) before you proceed though. |
15659 |
</li> |
15660 |
</ul> |
15661 |
|
15662 |
<p> |
15663 |
To fetch our public key using the GnuPG application, run the following command: |
15664 |
</p> |
15665 |
|
15666 |
<pre caption="Obtaining the public key"> |
15667 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
15668 |
</pre> |
15669 |
|
15670 |
<p> |
15671 |
Now verify the signature: |
15672 |
</p> |
15673 |
|
15674 |
<pre caption="Verify the cryptographic signature"> |
15675 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
15676 |
</pre> |
15677 |
|
15678 |
<p> |
15679 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
15680 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
15681 |
<c>K3B</c> here; more information can be found in our <uri |
15682 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
15683 |
</p> |
15684 |
|
15685 |
<ul> |
15686 |
<li> |
15687 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded |
15688 |
iso></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
15689 |
path). |
15690 |
</li> |
15691 |
<li> |
15692 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
15693 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
15694 |
<c>Start</c>. |
15695 |
</li> |
15696 |
</ul> |
15697 |
|
15698 |
</body> |
15699 |
</subsection> |
15700 |
<subsection> |
15701 |
<title>Booting the Universal Installation CD</title> |
15702 |
<body> |
15703 |
|
15704 |
<p> |
15705 |
Insert the Gentoo Installation CD in the CD-ROM and boot your system. During |
15706 |
startup, press Stop-A to enter OpenBootPROM (OBP). Once you are in the OBP, |
15707 |
boot from the CD-ROM: |
15708 |
</p> |
15709 |
|
15710 |
<pre caption="Booting the Installation CD"> |
15711 |
ok <i>boot cdrom</i> |
15712 |
</pre> |
15713 |
|
15714 |
<p> |
15715 |
You will be greeted by the SILO boot manager (on the Installation CD). Type in |
15716 |
<c>gentoo-2.4</c> and press enter to continue booting the |
15717 |
system: |
15718 |
</p> |
15719 |
|
15720 |
<pre caption="Continue booting from the Installation CD"> |
15721 |
boot: <i>gentoo-2.4</i> |
15722 |
</pre> |
15723 |
|
15724 |
<p> |
15725 |
Once the Installation CD is booted, you will be automatically logged on to the |
15726 |
system. |
15727 |
</p> |
15728 |
|
15729 |
<p> |
15730 |
You should have a root ("#") prompt on the current console and can also switch |
15731 |
to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get back to the one you |
15732 |
started on by pressing Alt-F1. You will also find a root prompt on the serial |
15733 |
console (<path>ttyS0</path>). |
15734 |
</p> |
15735 |
|
15736 |
<p> |
15737 |
Continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
15738 |
</p> |
15739 |
|
15740 |
</body> |
15741 |
</subsection> |
15742 |
<subsection id="hardware"> |
15743 |
<title>Extra Hardware Configuration</title> |
15744 |
<body> |
15745 |
|
15746 |
<p> |
15747 |
If not all hardware is supported out-of-the-box, you will need to load the |
15748 |
appropriate kernel modules. |
15749 |
</p> |
15750 |
|
15751 |
<p> |
15752 |
In the next example we try to load the <c>8139too</c> module (support for |
15753 |
certain kinds of network interfaces): |
15754 |
</p> |
15755 |
|
15756 |
<pre caption="Loading kernel modules"> |
15757 |
# <i>modprobe 8139too</i> |
15758 |
</pre> |
15759 |
|
15760 |
</body> |
15761 |
</subsection> |
15762 |
<subsection id="useraccounts"> |
15763 |
<title>Optional: User Accounts</title> |
15764 |
<body> |
15765 |
|
15766 |
<p> |
15767 |
If you plan on giving other people access to your installation |
15768 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
15769 |
security reasons), you need to create the necessary user accounts and change |
15770 |
the root password. |
15771 |
</p> |
15772 |
|
15773 |
<p> |
15774 |
To change the root password, use the <c>passwd</c> utility: |
15775 |
</p> |
15776 |
|
15777 |
<pre caption="Changing the root password"> |
15778 |
# <i>passwd</i> |
15779 |
New password: <comment>(Enter your new password)</comment> |
15780 |
Re-enter password: <comment>(Re-enter your password)</comment> |
15781 |
</pre> |
15782 |
|
15783 |
<p> |
15784 |
To create a user account, we first enter their credentials, followed by |
15785 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
15786 |
In the next example, we create a user called "john". |
15787 |
</p> |
15788 |
|
15789 |
<pre caption="Creating a user account"> |
15790 |
# <i>useradd -m -G users john</i> |
15791 |
# <i>passwd john</i> |
15792 |
New password: <comment>(Enter john's password)</comment> |
15793 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
15794 |
</pre> |
15795 |
|
15796 |
<p> |
15797 |
You can change your user id from root to the newly created user by using |
15798 |
<c>su</c>: |
15799 |
</p> |
15800 |
|
15801 |
<pre caption="Changing user id"> |
15802 |
# <i>su - john</i> |
15803 |
</pre> |
15804 |
|
15805 |
</body> |
15806 |
</subsection> |
15807 |
<subsection> |
15808 |
<title>Optional: Viewing Documentation while Installing</title> |
15809 |
<body> |
15810 |
|
15811 |
<p> |
15812 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
15813 |
installation, make sure you have created a user account (see <uri |
15814 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
15815 |
go to a new terminal and log in. |
15816 |
</p> |
15817 |
|
15818 |
<p> |
15819 |
If you want to view the documentation on the CD you can immediately run |
15820 |
<c>links2</c> to read it: |
15821 |
</p> |
15822 |
|
15823 |
<pre caption="Viewing the on-CD documentation"> |
15824 |
# <i>links2 /mnt/cdrom/docs/handbook/html/index.html</i> |
15825 |
</pre> |
15826 |
|
15827 |
<p> |
15828 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
15829 |
more recent than the one provided on the CD. You can view it using <c>links2</c> |
15830 |
as well, but only after having completed the <e>Configuring your Network</e> |
15831 |
chapter (otherwise you won't be able to go on the Internet to view the |
15832 |
document): |
15833 |
</p> |
15834 |
|
15835 |
<pre caption="Viewing the Online Documentation"> |
15836 |
# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-sparc.xml</i> |
15837 |
</pre> |
15838 |
|
15839 |
<p> |
15840 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
15841 |
</p> |
15842 |
|
15843 |
</body> |
15844 |
</subsection> |
15845 |
<subsection> |
15846 |
<title>Optional: Starting the SSH Daemon</title> |
15847 |
<body> |
15848 |
|
15849 |
<p> |
15850 |
If you want to allow other users to access your computer during the |
15851 |
Gentoo installation (perhaps because those users are going to help you |
15852 |
install Gentoo, or even do it for you), you need to create a user |
15853 |
account for them and perhaps even provide them with your root password |
15854 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
15855 |
</p> |
15856 |
|
15857 |
<p> |
15858 |
To fire up the SSH daemon, execute the following command: |
15859 |
</p> |
15860 |
|
15861 |
<pre caption="Starting the SSH daemon"> |
15862 |
# <i>/etc/init.d/sshd start</i> |
15863 |
</pre> |
15864 |
|
15865 |
<p> |
15866 |
To be able to use sshd, you first need to set up your networking. Continue with |
15867 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
15868 |
</p> |
15869 |
|
15870 |
</body> |
15871 |
</subsection> |
15872 |
</section> |
15873 |
</sections> |
15874 |
|
15875 |
|
15876 |
|
15877 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-stage.xml |
15878 |
|
15879 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-stage.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
15880 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-stage.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
15881 |
|
15882 |
Index: hb-install-stage.xml |
15883 |
=================================================================== |
15884 |
<?xml version='1.0' encoding='UTF-8'?> |
15885 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
15886 |
|
15887 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
15888 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
15889 |
|
15890 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-stage.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
15891 |
|
15892 |
<sections> |
15893 |
|
15894 |
<version>5.8</version> |
15895 |
<date>2005-12-20</date> |
15896 |
|
15897 |
<section> |
15898 |
<title>Installing a Stage Tarball</title> |
15899 |
<subsection> |
15900 |
<title>Setting the Date/Time Right</title> |
15901 |
<body> |
15902 |
|
15903 |
<p> |
15904 |
Before you continue you need to check your date/time and update it. A |
15905 |
misconfigured clock may lead to strange results in the future! |
15906 |
</p> |
15907 |
|
15908 |
<p> |
15909 |
To verify the current date/time, run <c>date</c>: |
15910 |
</p> |
15911 |
|
15912 |
<pre caption="Verifying the date/time"> |
15913 |
# <i>date</i> |
15914 |
Fri Mar 29 16:21:18 CEST 2005 |
15915 |
</pre> |
15916 |
|
15917 |
<p> |
15918 |
If the date/time displayed is wrong, update it using the <c>date |
15919 |
MMDDhhmmYYYY</c> syntax (<b>M</b>onth, <b>D</b>ay, <b>h</b>our, <b>m</b>inute |
15920 |
and <b>Y</b>ear). For instance, to set the date to Mar 29th, 16:21 in the |
15921 |
year 2005: |
15922 |
</p> |
15923 |
|
15924 |
<pre caption="Setting the date/time"> |
15925 |
# <i>date 032916212005</i> |
15926 |
</pre> |
15927 |
|
15928 |
</body> |
15929 |
</subsection> |
15930 |
<subsection> |
15931 |
<title>Locating the Stage3 File</title> |
15932 |
<body> |
15933 |
|
15934 |
<p> |
15935 |
If you have configured networking because you need to download a stage3 file for |
15936 |
your architecture, continue with <uri link="#download">Alternative: Using a |
15937 |
Stage3 from the Internet</uri>. Otherwise read <uri link="#available">Default: |
15938 |
Using a Stage3 from the Installation CD</uri>. |
15939 |
</p> |
15940 |
|
15941 |
</body> |
15942 |
</subsection> |
15943 |
</section> |
15944 |
<section id="available"> |
15945 |
<title>Default: Using a Stage from the Installation CD</title> |
15946 |
<subsection> |
15947 |
<title>Extracting the Stage Tarball</title> |
15948 |
<body> |
15949 |
|
15950 |
<p> |
15951 |
The stages on the CD reside in the <path>/mnt/cdrom/stages</path> directory. To |
15952 |
see a listing of available stages, use <c>ls</c>: |
15953 |
</p> |
15954 |
|
15955 |
<pre caption="List all available stages"> |
15956 |
# <i>ls /mnt/cdrom/stages</i> |
15957 |
</pre> |
15958 |
|
15959 |
<p> |
15960 |
If the system replies with an error, you may need to mount the CD-ROM first: |
15961 |
</p> |
15962 |
|
15963 |
<pre caption="Mounting the CD-ROM"> |
15964 |
# <i>ls /mnt/cdrom/stages</i> |
15965 |
ls: /mnt/cdrom/stages: No such file or directory |
15966 |
# <i>mount /dev/cdroms/cdrom0 /mnt/cdrom</i> |
15967 |
# <i>ls /mnt/cdrom/stages</i> |
15968 |
</pre> |
15969 |
|
15970 |
<p> |
15971 |
Now go into your Gentoo mountpoint (usually <path>/mnt/gentoo</path>): |
15972 |
</p> |
15973 |
|
15974 |
<pre caption="Changing directory to /mnt/gentoo"> |
15975 |
# <i>cd /mnt/gentoo</i> |
15976 |
</pre> |
15977 |
|
15978 |
<p> |
15979 |
We will now extract the stage tarball of your choice. We will do this with the |
15980 |
<c>tar</c> tool. Make sure you use the same options (<c>xvjpf</c>)! The |
15981 |
<c>x</c> stands for <e>Extract</e>, the <c>v</c> for <e>Verbose</e> to see what |
15982 |
happens during the extraction process (this one is optional), the <c>j</c> for |
15983 |
<e>Decompress with bzip2</e>, the <c>p</c> for <e>Preserve permissions</e> and |
15984 |
the <c>f</c> to denote that we want to extract a file, not standard input. In |
15985 |
the next example, we extract the stage tarball |
15986 |
<path>stage3-<subarch>-2005.1-r1.tar.bz2</path>. Be sure to substitute |
15987 |
the tarball filename with your stage. |
15988 |
</p> |
15989 |
|
15990 |
<pre caption="Extracting the stage tarball"> |
15991 |
# <i>tar xvjpf /mnt/cdrom/stages/stage3-<subarch>-2005.1-r1.tar.bz2</i> |
15992 |
</pre> |
15993 |
|
15994 |
<p> |
15995 |
Now that the stage is installed, continue with <uri |
15996 |
link="#installing_portage">Installing Portage</uri>. |
15997 |
</p> |
15998 |
|
15999 |
</body> |
16000 |
</subsection> |
16001 |
</section> |
16002 |
<section id="download"> |
16003 |
<title>Alternative: Using a Stage from the Internet</title> |
16004 |
<subsection> |
16005 |
<title>Downloading the Stage Tarball</title> |
16006 |
<body> |
16007 |
|
16008 |
<p> |
16009 |
Go to the Gentoo mountpoint at which you mounted your filesystems |
16010 |
(most likely <path>/mnt/gentoo</path>): |
16011 |
</p> |
16012 |
|
16013 |
<pre caption="Going to the Gentoo mountpoint"> |
16014 |
# <i>cd /mnt/gentoo</i> |
16015 |
</pre> |
16016 |
|
16017 |
<p> |
16018 |
Depending on your installation medium, you have a couple of tools available to |
16019 |
download a stage. If you have <c>links2</c> available, then you can immediately |
16020 |
surf to <uri link="/main/en/mirrors.xml">the Gentoo mirrorlist</uri> and |
16021 |
choose a mirror close to you. |
16022 |
</p> |
16023 |
|
16024 |
<p> |
16025 |
If you don't have <c>links2</c> available you should have <c>lynx</c> at your |
16026 |
disposal. If you need to go through a proxy, export the <c>http_proxy</c> and |
16027 |
<c>ftp_proxy</c> variables: |
16028 |
</p> |
16029 |
|
16030 |
<pre caption="Setting proxy information for lynx"> |
16031 |
# <i>export http_proxy="http://proxy.server.com:port"</i> |
16032 |
# <i>export ftp_proxy="http://proxy.server.com:port"</i> |
16033 |
</pre> |
16034 |
|
16035 |
<p> |
16036 |
We will now assume that you have <c>links2</c> at your disposal. |
16037 |
</p> |
16038 |
|
16039 |
<p> |
16040 |
Pick the <path>releases/</path> directory, followed by your architecture (for |
16041 |
instance <path>x86/</path>) and the Gentoo version (<path>2005.1/</path> or |
16042 |
<path>2005.1-r1/</path> if available) to finish up with the <path>stages/</path> |
16043 |
directory. There you should see all available stage files for your architecture |
16044 |
(they might be stored within subdirectories named to the individual sub |
16045 |
architectures). Select one and press <c>D</c> to download. When you're |
16046 |
finished, press <c>Q</c> to quit the browser. |
16047 |
</p> |
16048 |
|
16049 |
<pre caption="Surfing to the mirror listing with links2"> |
16050 |
# <i>links2 http://www.gentoo.org/main/en/mirrors.xml</i> |
16051 |
|
16052 |
<comment>(If you need proxy support with links2:)</comment> |
16053 |
# <i>links2 -http-proxy proxy.server.com:8080 http://www.gentoo.org/main/en/mirrors.xml</i> |
16054 |
</pre> |
16055 |
|
16056 |
<p> |
16057 |
Make sure you download a stage3 tarball - installations using a stage1 or stage2 |
16058 |
tarball are not supported anymore. |
16059 |
</p> |
16060 |
|
16061 |
<p> |
16062 |
If you want to check the integrity of the downloaded stage tarball, use |
16063 |
<c>md5sum</c> and compare the output with the MD5 checksum provided on the |
16064 |
mirror. For instance, to check the validity of the x86 stage tarball: |
16065 |
</p> |
16066 |
|
16067 |
<pre caption="Example checking integrity of a stage tarball"> |
16068 |
# <i>md5sum -c stage3-x86-2005.1-r1.tar.bz2.md5</i> |
16069 |
stage3-x86-2005.1-r1.tar.bz2: OK |
16070 |
</pre> |
16071 |
|
16072 |
</body> |
16073 |
</subsection> |
16074 |
<subsection> |
16075 |
<title>Unpacking the Stage Tarball</title> |
16076 |
<body> |
16077 |
|
16078 |
<p> |
16079 |
Now unpack your downloaded stage onto your system. We use <c>tar</c> to proceed |
16080 |
as it is the easiest method: |
16081 |
</p> |
16082 |
|
16083 |
<pre caption="Unpacking the stage"> |
16084 |
# <i>tar xvjpf stage3-*.tar.bz2</i> |
16085 |
</pre> |
16086 |
|
16087 |
<p> |
16088 |
Make sure that you use the same options (<c>xvjpf</c>). The <c>x</c> stands |
16089 |
for <e>Extract</e>, the <c>v</c> for <e>Verbose</e> to see what happens during |
16090 |
the extraction process (this one is optional), the <c>j</c> for <e>Decompress |
16091 |
with bzip2</e>, the <c>p</c> for <e>Preserve permissions</e> and the <c>f</c> |
16092 |
to denote that we want to extract a file, not standard input. |
16093 |
</p> |
16094 |
|
16095 |
<p> |
16096 |
Now that the stage is installed, continue with <uri |
16097 |
link="#installing_portage">Installing Portage</uri>. |
16098 |
</p> |
16099 |
|
16100 |
</body> |
16101 |
</subsection> |
16102 |
</section> |
16103 |
<section id="installing_portage"> |
16104 |
<title>Installing Portage</title> |
16105 |
<subsection> |
16106 |
<title>Unpacking a Portage Snapshot</title> |
16107 |
<body> |
16108 |
|
16109 |
<p> |
16110 |
You now have to install a Portage snapshot, a collection of files that inform |
16111 |
Portage what software titles you can install, which profiles are available, etc. |
16112 |
</p> |
16113 |
|
16114 |
</body> |
16115 |
</subsection> |
16116 |
<subsection id="installing_from_InstallCD"> |
16117 |
<title>Unpack the Snapshot from the Installation CD</title> |
16118 |
<body> |
16119 |
|
16120 |
<p> |
16121 |
To install the snapshot, take a look inside <path>/mnt/cdrom/snapshots/</path> |
16122 |
to see what snapshot is available: |
16123 |
</p> |
16124 |
|
16125 |
<pre caption="Checking the /mnt/cdrom/snapshots content"> |
16126 |
# <i>ls /mnt/cdrom/snapshots</i> |
16127 |
</pre> |
16128 |
|
16129 |
<p> |
16130 |
Now extract the snapshot using the following construct. Again, make sure you |
16131 |
use the correct options with <c>tar</c>. Also, the <c>-C</c> is with a capital |
16132 |
<c>C</c>, not <c>c</c>. In the next example we use |
16133 |
<path>portage-<date>.tar.bz2</path> as the snapshot filename. Be sure to |
16134 |
substitute with the name of the snapshot that is on your Installation CD. |
16135 |
</p> |
16136 |
|
16137 |
<pre caption="Extracting a Portage snapshot"> |
16138 |
# <i>tar xvjf /mnt/cdrom/snapshots/portage-<date>.tar.bz2 -C /mnt/gentoo/usr</i> |
16139 |
</pre> |
16140 |
|
16141 |
</body> |
16142 |
</subsection> |
16143 |
<subsection id="copysources"> |
16144 |
<title>Copy Source Code Archives</title> |
16145 |
<body> |
16146 |
|
16147 |
<p> |
16148 |
You also need to copy over all source code from the Universal Installation CD. |
16149 |
</p> |
16150 |
|
16151 |
<pre caption="Copy over source code"> |
16152 |
# <i>mkdir /mnt/gentoo/usr/portage/distfiles</i> |
16153 |
# <i>cp /mnt/cdrom/distfiles/* /mnt/gentoo/usr/portage/distfiles/</i> |
16154 |
</pre> |
16155 |
|
16156 |
</body> |
16157 |
</subsection> |
16158 |
</section> |
16159 |
<section id="compile_options"> |
16160 |
<title>Configuring the Compile Options</title> |
16161 |
<subsection> |
16162 |
<title>Introduction</title> |
16163 |
<body> |
16164 |
|
16165 |
<p> |
16166 |
To optimize Gentoo, you can set a couple of variables which impact Portage |
16167 |
behaviour. All those variables can be set as environment variables (using |
16168 |
<c>export</c>) but that isn't permanent. To keep your settings, Portage provides |
16169 |
you with <path>/etc/make.conf</path>, a configuration file for Portage. It is |
16170 |
this file we will edit now. |
16171 |
</p> |
16172 |
|
16173 |
<note> |
16174 |
A commented listing of all possible variables can be found in |
16175 |
<path>/mnt/gentoo/etc/make.conf.example</path>. For a successful Gentoo |
16176 |
installation you'll only need to set the variables which are mentioned beneath. |
16177 |
</note> |
16178 |
|
16179 |
<p> |
16180 |
Fire up your favorite editor (in this guide we use <c>nano</c>) so we can alter |
16181 |
the optimization variables we will discuss hereafter. |
16182 |
</p> |
16183 |
|
16184 |
<pre caption="Opening /etc/make.conf"> |
16185 |
# <i>nano -w /mnt/gentoo/etc/make.conf</i> |
16186 |
</pre> |
16187 |
|
16188 |
<p> |
16189 |
As you probably noticed, the <path>make.conf.example</path> file is |
16190 |
structured in a generic way: commented lines start with "#", other lines define |
16191 |
variables using the <c>VARIABLE="content"</c> syntax. The <path>make.conf</path> |
16192 |
file uses the same syntax. Several of those variables are discussed next. |
16193 |
</p> |
16194 |
|
16195 |
<warn> |
16196 |
Do not make any modifications to the USE variable if you are performing a stage3 |
16197 |
with GRP installation. You can alter the USE variable after having installed the |
16198 |
packages you want. Gremlins are known to attack your system if you ignore this |
16199 |
warning! |
16200 |
</warn> |
16201 |
|
16202 |
</body> |
16203 |
</subsection> |
16204 |
<subsection> |
16205 |
<title>CHOST</title> |
16206 |
<body> |
16207 |
|
16208 |
<p> |
16209 |
The <c>CHOST</c> variable declares the target build host for your system. This |
16210 |
variable should already be set to the correct value. <brite>Do not edit |
16211 |
it</brite> as that might break your system. If the <c>CHOST</c> variable does |
16212 |
not look correct to you, you might be using the wrong stage3 tarball. |
16213 |
</p> |
16214 |
|
16215 |
</body> |
16216 |
</subsection> |
16217 |
<subsection> |
16218 |
<title>CFLAGS and CXXFLAGS</title> |
16219 |
<body> |
16220 |
|
16221 |
<p> |
16222 |
The <c>CFLAGS</c> and <c>CXXFLAGS</c> variables define the optimization flags |
16223 |
for the <c>gcc</c> C and C++ compiler respectively. Although we define those |
16224 |
generally here, you will only have maximum performance if you optimize these |
16225 |
flags for each program separately. The reason for this is because every program |
16226 |
is different. |
16227 |
</p> |
16228 |
|
16229 |
<p> |
16230 |
In <path>make.conf</path> you should define the optimization flags you think |
16231 |
will make your system the most responsive <e>generally</e>. Don't place |
16232 |
experimental settings in this variable; too much optimization can make |
16233 |
programs behave bad (crash, or even worse, malfunction). |
16234 |
</p> |
16235 |
|
16236 |
<p> |
16237 |
We will not explain all possible optimization options. If you want to know |
16238 |
them all, read the <uri link="http://gcc.gnu.org/onlinedocs/">GNU |
16239 |
Online Manual(s)</uri> or the <c>gcc</c> info page (<c>info gcc</c> -- only |
16240 |
works on a working Linux system). The <path>make.conf.example</path> file |
16241 |
itself also contains lots of examples and information; don't forget to read it |
16242 |
too. |
16243 |
</p> |
16244 |
|
16245 |
<p> |
16246 |
A first setting is the <c>-march=</c> flag, which specifies the name of the |
16247 |
target architecture. Possible options are described in the |
16248 |
<path>make.conf.example</path> file (as comments). For instance, for the x86 |
16249 |
Athlon XP architecture: |
16250 |
</p> |
16251 |
|
16252 |
<pre caption="The GCC march setting"> |
16253 |
<comment># AMD64 users who want to use a native 64 bit system should use -march=k8</comment> |
16254 |
<comment># EM64T users should use -march=nocona</comment> |
16255 |
-march=athlon-xp |
16256 |
</pre> |
16257 |
|
16258 |
<p> |
16259 |
A second one is the <c>-O</c> flag (that is a capital O, not a zero), |
16260 |
which specifies the <c>gcc</c> optimization |
16261 |
class flag. Possible classes are <c>s</c> (for size-optimized), |
16262 |
<c>0</c> (zero - for no optimizations), <c>1</c>, <c>2</c> or <c>3</c> for more |
16263 |
speed-optimization flags (every class has the same flags as the one before, plus |
16264 |
some extras). For instance, for a class-2 optimization: |
16265 |
</p> |
16266 |
|
16267 |
<pre caption="The GCC O setting"> |
16268 |
-O2 |
16269 |
</pre> |
16270 |
|
16271 |
<p> |
16272 |
Another popular optimization flag is <c>-pipe</c> (use pipes rather than |
16273 |
temporary files for communication between the various stages of compilation). |
16274 |
</p> |
16275 |
|
16276 |
<p> |
16277 |
Mind you that using <c>-fomit-frame-pointer</c> (which doesn't keep the frame |
16278 |
pointer in a register for functions that don't need one) might have serious |
16279 |
repercussions on the debugging of applications! |
16280 |
</p> |
16281 |
|
16282 |
<p> |
16283 |
When you define the <c>CFLAGS</c> and <c>CXXFLAGS</c>, you should combine |
16284 |
several optimization flags, like in the following example: |
16285 |
</p> |
16286 |
|
16287 |
<pre caption="Defining the CFLAGS and CXXFLAGS variable"> |
16288 |
CFLAGS="-march=athlon-xp -pipe -O2" <comment># AMD64 users use march=k8</comment> |
16289 |
<comment># EM64T users use march=nocona</comment> |
16290 |
CXXFLAGS="${CFLAGS}" <comment># Use the same settings for both variables</comment> |
16291 |
</pre> |
16292 |
|
16293 |
</body> |
16294 |
</subsection> |
16295 |
<subsection> |
16296 |
<title>MAKEOPTS</title> |
16297 |
<body> |
16298 |
|
16299 |
<p> |
16300 |
With <c>MAKEOPTS</c> you define how many parallel compilations should occur when |
16301 |
you install a package. A good choice is the number of CPUs in your system plus |
16302 |
one, but this guideline isn't always perfect. |
16303 |
</p> |
16304 |
|
16305 |
<pre caption="MAKEOPTS for a regular, 1-CPU system"> |
16306 |
MAKEOPTS="-j2" |
16307 |
</pre> |
16308 |
|
16309 |
</body> |
16310 |
</subsection> |
16311 |
<subsection> |
16312 |
<title>Ready, Set, Go!</title> |
16313 |
<body> |
16314 |
|
16315 |
<p> |
16316 |
Update your <path>/mnt/gentoo/etc/make.conf</path> to your own preference and |
16317 |
save (<c>nano</c> users would hit <c>Ctrl-X</c>). You are now ready to continue |
16318 |
with <uri link="?part=1&chap=6">Chrooting into the Gentoo Base System</uri>. |
16319 |
</p> |
16320 |
|
16321 |
</body> |
16322 |
</subsection> |
16323 |
</section> |
16324 |
</sections> |
16325 |
|
16326 |
|
16327 |
|
16328 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-system.xml |
16329 |
|
16330 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-system.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
16331 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-system.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
16332 |
|
16333 |
Index: hb-install-system.xml |
16334 |
=================================================================== |
16335 |
<?xml version='1.0' encoding='UTF-8'?> |
16336 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
16337 |
|
16338 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
16339 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
16340 |
|
16341 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-system.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
16342 |
|
16343 |
<sections> |
16344 |
|
16345 |
<version>5.4</version> |
16346 |
<date>2006-02-22</date> |
16347 |
|
16348 |
<section> |
16349 |
<title>Chrooting</title> |
16350 |
<subsection> |
16351 |
<title>Mounting the /proc and /dev Filesystems</title> |
16352 |
<body> |
16353 |
|
16354 |
<p> |
16355 |
Mount the <path>/proc</path> filesystem on <path>/mnt/gentoo/proc</path> to |
16356 |
allow the installation to use the kernel-provided information within the |
16357 |
chrooted environment, and then mount-bind the <path>/dev</path> filesystem. |
16358 |
</p> |
16359 |
|
16360 |
<pre caption="Mounting /proc and /dev"> |
16361 |
# <i>mount -t proc none /mnt/gentoo/proc</i> |
16362 |
# <i>mount -o bind /dev /mnt/gentoo/dev</i> |
16363 |
</pre> |
16364 |
|
16365 |
</body> |
16366 |
</subsection> |
16367 |
<subsection> |
16368 |
<title>Optional: Copy over DNS Information</title> |
16369 |
<body> |
16370 |
|
16371 |
<p> |
16372 |
If you configured your network to fetch the appropriate stage file later on from |
16373 |
the Internet, you need to copy over the DNS information stored in |
16374 |
<path>/etc/resolv.conf</path> to <path>/mnt/gentoo/etc/resolv.conf</path>. This |
16375 |
file contains the nameservers your system will use to resolve names to IP |
16376 |
addresses. |
16377 |
</p> |
16378 |
|
16379 |
<pre caption="Copy over DNS Information"> |
16380 |
# <i>cp -L /etc/resolv.conf /mnt/gentoo/etc/resolv.conf</i> |
16381 |
</pre> |
16382 |
|
16383 |
</body> |
16384 |
</subsection> |
16385 |
<subsection> |
16386 |
<title>Entering the new Environment</title> |
16387 |
<body> |
16388 |
|
16389 |
<p> |
16390 |
Now that all partitions are initialized and the base environment |
16391 |
installed, it is time to enter our new installation environment by |
16392 |
<e>chrooting</e> into it. This means that we change from the current |
16393 |
installation environment to your installation system (namely the |
16394 |
initialized partitions). |
16395 |
</p> |
16396 |
|
16397 |
<p> |
16398 |
This chrooting is done in three steps. First we will change the root |
16399 |
from <path>/</path> (on the installation medium) to <path>/mnt/gentoo</path> |
16400 |
(on your partitions) using <c>chroot</c>. Then we will create a new environment |
16401 |
using <c>env-update</c>, which essentially creates environment variables. |
16402 |
Finally, we load those variables into memory using <c>source</c>. |
16403 |
</p> |
16404 |
|
16405 |
<pre caption="Chrooting into the new environment"> |
16406 |
# <i>chroot /mnt/gentoo /bin/bash</i> |
16407 |
# <i>env-update</i> |
16408 |
>>> Regenerating /etc/ld.so.cache... |
16409 |
# <i>source /etc/profile</i> |
16410 |
# <i>export PS1="(chroot) $PS1"</i> |
16411 |
</pre> |
16412 |
|
16413 |
<p> |
16414 |
Congratulations! You are now inside your own Gentoo Linux environment. |
16415 |
Of course it is far from finished, which is why the installation still |
16416 |
has some sections left :-) |
16417 |
</p> |
16418 |
|
16419 |
</body> |
16420 |
</subsection> |
16421 |
<subsection> |
16422 |
<title>Creating the Portage cache</title> |
16423 |
<body> |
16424 |
|
16425 |
<p> |
16426 |
You have already installed the Portage tree, but you should now build the |
16427 |
Portage cache to speed up future emerges. <c>emerge --metadata</c> does this |
16428 |
for you. |
16429 |
</p> |
16430 |
|
16431 |
<pre caption="Creating the Portage cache"> |
16432 |
# <i>emerge --metadata</i> |
16433 |
</pre> |
16434 |
|
16435 |
</body> |
16436 |
</subsection> |
16437 |
</section> |
16438 |
|
16439 |
<section id="configure_USE"> |
16440 |
<title>Configuring the USE Variable</title> |
16441 |
<subsection> |
16442 |
<title>What is the USE Variable?</title> |
16443 |
<body> |
16444 |
|
16445 |
<p> |
16446 |
<c>USE</c> is one of the most powerful variables Gentoo provides to its users. |
16447 |
Several programs can be compiled with or without optional support for certain |
16448 |
items. For instance, some programs can be compiled with gtk-support, or with |
16449 |
qt-support. Others can be compiled with or without SSL support. Some programs |
16450 |
can even be compiled with framebuffer support (svgalib) instead of X11 support |
16451 |
(X-server). |
16452 |
</p> |
16453 |
|
16454 |
<p> |
16455 |
Most distributions compile their packages with support for as much as possible, |
16456 |
increasing the size of the programs and startup time, not to mention an enormous |
16457 |
amount of dependencies. With Gentoo you can define what options a package |
16458 |
should be compiled with. This is where <c>USE</c> comes into play. |
16459 |
</p> |
16460 |
|
16461 |
<p> |
16462 |
In the <c>USE</c> variable you define keywords which are mapped onto |
16463 |
compile-options. For instance, <e>ssl</e> will compile ssl-support in the |
16464 |
programs that support it. <e>-X</e> will remove X-server support (note the minus |
16465 |
sign in front). <e>gnome gtk -kde -qt</e> will compile your programs with gnome |
16466 |
(and gtk) support, and not with kde (and qt) support, making your system fully |
16467 |
tweaked for GNOME. |
16468 |
</p> |
16469 |
|
16470 |
</body> |
16471 |
</subsection> |
16472 |
<subsection> |
16473 |
<title>Modifying the USE Variable</title> |
16474 |
<body> |
16475 |
|
16476 |
<warn> |
16477 |
Do not make any modifications to the USE variable yet if you plan to use our |
16478 |
prebuilt packages (GRP set). You can alter the USE variable after having |
16479 |
installed the packages you want. Gremlins are known to attack your system |
16480 |
if you ignore this warning! |
16481 |
</warn> |
16482 |
|
16483 |
<p> |
16484 |
The default <c>USE</c> settings are placed in |
16485 |
<path>/etc/make.profile/make.defaults</path>. What you place in |
16486 |
<path>/etc/make.conf</path> is calculated against these defaults settings. If |
16487 |
you add something to the <c>USE</c> setting, it is added to the default list. If |
16488 |
you remove something from the <c>USE</c> setting (by placing a minus sign in |
16489 |
front of it) it is removed from the default list (if it was in the default list |
16490 |
at all). <e>Never</e> alter anything inside the <path>/etc/make.profile</path> |
16491 |
directory; it gets overwritten when you update Portage! |
16492 |
</p> |
16493 |
|
16494 |
<p> |
16495 |
A full description on <c>USE</c> can be found in the second part of the Gentoo |
16496 |
Handbook, <uri link="?part=2&chap=2">USE flags</uri>. A full description on |
16497 |
the available USE flags can be found on your system in |
16498 |
<path>/usr/portage/profiles/use.desc</path>. |
16499 |
</p> |
16500 |
|
16501 |
<pre caption="Viewing available USE flags"> |
16502 |
# <i>less /usr/portage/profiles/use.desc</i> |
16503 |
<comment>(You can scroll using your arrow keys, exit by pressing 'q')</comment> |
16504 |
</pre> |
16505 |
|
16506 |
<p> |
16507 |
As an example we show a <c>USE</c> setting for a KDE-based system with DVD, ALSA |
16508 |
and CD Recording support: |
16509 |
</p> |
16510 |
|
16511 |
<pre caption="Opening /etc/make.conf"> |
16512 |
# <i>nano -w /etc/make.conf</i> |
16513 |
</pre> |
16514 |
|
16515 |
<pre caption="USE setting"> |
16516 |
USE="-gtk -gnome qt kde dvd alsa cdr" |
16517 |
</pre> |
16518 |
|
16519 |
</body> |
16520 |
</subsection> |
16521 |
</section> |
16522 |
</sections> |
16523 |
|
16524 |
|
16525 |
|
16526 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-tools.xml |
16527 |
|
16528 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-tools.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
16529 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-tools.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
16530 |
|
16531 |
Index: hb-install-tools.xml |
16532 |
=================================================================== |
16533 |
<?xml version='1.0' encoding='UTF-8'?> |
16534 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
16535 |
|
16536 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
16537 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
16538 |
|
16539 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-tools.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
16540 |
|
16541 |
<sections> |
16542 |
|
16543 |
<version>5.2</version> |
16544 |
<date>2005-11-21</date> |
16545 |
|
16546 |
<section> |
16547 |
<title>System Logger</title> |
16548 |
<body> |
16549 |
|
16550 |
<p> |
16551 |
Some tools are missing from the <e>stage3</e> archive because several packages |
16552 |
provide the same functionality. It is now up to you to choose which ones you |
16553 |
want to install. |
16554 |
</p> |
16555 |
|
16556 |
<p> |
16557 |
The first tool you need to decide on has to provide logging facilities for your |
16558 |
system. Unix and Linux have an excellent history of logging capabilities -- if |
16559 |
you want you can log everything that happens on your system in logfiles. This |
16560 |
happens through the <e>system logger</e>. |
16561 |
</p> |
16562 |
|
16563 |
<p> |
16564 |
Gentoo offers several system loggers to choose from. There are <c>sysklogd</c>, |
16565 |
which is the traditional set of system logging daemons, <c>syslog-ng</c>, an |
16566 |
advanced system logger, and <c>metalog</c> which is a highly-configurable |
16567 |
system logger. Others might be available through Portage as well - our number of |
16568 |
available packages increases on a daily basis. |
16569 |
</p> |
16570 |
|
16571 |
<p> |
16572 |
If you plan on using <c>sysklogd</c> or <c>syslog-ng</c> you might want to |
16573 |
install <c>logrotate</c> afterwards as those system loggers don't provide any |
16574 |
rotation mechanism for the log files. |
16575 |
</p> |
16576 |
|
16577 |
<!-- |
16578 |
Even though syslog-ng does not rotate the logs, it does conform to the syslog |
16579 |
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 |
16580 |
above others (metalog for instance doesn't work nicely with sparc all the |
16581 |
time). |
16582 |
--> |
16583 |
|
16584 |
<p> |
16585 |
To install the system logger of your choice, <c>emerge</c> it and have it added |
16586 |
to the default runlevel using <c>rc-update</c>. The following example installs |
16587 |
<c>syslog-ng</c>. Of course substitute with your system logger: |
16588 |
</p> |
16589 |
|
16590 |
<pre caption="Installing a system logger"> |
16591 |
# <i>emerge syslog-ng</i> |
16592 |
# <i>rc-update add syslog-ng default</i> |
16593 |
</pre> |
16594 |
|
16595 |
</body> |
16596 |
</section> |
16597 |
<section> |
16598 |
<title>Optional: Cron Daemon</title> |
16599 |
<body> |
16600 |
|
16601 |
<p> |
16602 |
Next is the cron daemon. Although it is optional and not required for your |
16603 |
system, it is wise to install one. But what is a cron daemon? A cron daemon |
16604 |
executes scheduled commands. It is very handy if you need to execute some |
16605 |
command regularly (for instance daily, weekly or monthly). |
16606 |
</p> |
16607 |
|
16608 |
<p> |
16609 |
We only provide <c>vixie-cron</c> for networkless installations. If you want |
16610 |
another cron daemon you can wait and install it later on. |
16611 |
</p> |
16612 |
|
16613 |
<pre caption="Installing a cron daemon"> |
16614 |
# <i>emerge vixie-cron</i> |
16615 |
# <i>rc-update add vixie-cron default</i> |
16616 |
</pre> |
16617 |
|
16618 |
</body> |
16619 |
</section> |
16620 |
<section> |
16621 |
<title>Optional: File Indexing</title> |
16622 |
<body> |
16623 |
|
16624 |
<p> |
16625 |
If you want to index your system's files so you are able to quickly |
16626 |
locate them using the <c>locate</c> tool, you need to install |
16627 |
<c>sys-apps/slocate</c>. |
16628 |
</p> |
16629 |
|
16630 |
<pre caption="Installing slocate"> |
16631 |
# <i>emerge slocate</i> |
16632 |
</pre> |
16633 |
|
16634 |
</body> |
16635 |
</section> |
16636 |
<section> |
16637 |
<title>File System Tools</title> |
16638 |
<body> |
16639 |
|
16640 |
<p> |
16641 |
Depending on what file systems you are using, you need to install the necessary |
16642 |
file system utilities (for checking the filesystem integrity, creating |
16643 |
additional file systems etc.). |
16644 |
</p> |
16645 |
|
16646 |
<p> |
16647 |
The following table lists the tools you need to install if you use a certain |
16648 |
file system. Not all filesystems are available for each and every architecture |
16649 |
though. |
16650 |
</p> |
16651 |
|
16652 |
<table> |
16653 |
<tr> |
16654 |
<th>File System</th> |
16655 |
<th>Tool</th> |
16656 |
<th>Install Command</th> |
16657 |
</tr> |
16658 |
<tr> |
16659 |
<ti>XFS</ti> |
16660 |
<ti>xfsprogs</ti> |
16661 |
<ti><c>emerge xfsprogs</c></ti> |
16662 |
</tr> |
16663 |
<tr> |
16664 |
<ti>ReiserFS</ti> |
16665 |
<ti>reiserfsprogs</ti> |
16666 |
<ti><c>emerge reiserfsprogs</c></ti> |
16667 |
</tr> |
16668 |
<tr> |
16669 |
<ti>JFS</ti> |
16670 |
<ti>jfsutils</ti> |
16671 |
<ti><c>emerge jfsutils</c></ti> |
16672 |
</tr> |
16673 |
</table> |
16674 |
|
16675 |
<p> |
16676 |
If you are an EVMS user, you need to install <c>emvs</c>: |
16677 |
</p> |
16678 |
|
16679 |
<pre caption="Installing EVMS utilities"> |
16680 |
# <i>USE="-gtk" emerge evms</i> |
16681 |
</pre> |
16682 |
|
16683 |
<p> |
16684 |
The <c>USE="-gtk"</c> will prevent the installation of dependencies. If you |
16685 |
want to enable the <c>evms</c> graphical tools, you can recompile <c>evms</c> |
16686 |
later on. |
16687 |
</p> |
16688 |
|
16689 |
<p> |
16690 |
If you don't require any additional networking-related tools (such as rp-pppoe |
16691 |
or a dhcp client) continue with <uri link="?part=1&chap=10">Configuring the |
16692 |
Bootloader</uri>. |
16693 |
</p> |
16694 |
|
16695 |
</body> |
16696 |
</section> |
16697 |
<section> |
16698 |
<title>Networking Tools</title> |
16699 |
<subsection> |
16700 |
<title>Optional: Installing a DHCP Client</title> |
16701 |
<body> |
16702 |
|
16703 |
<p> |
16704 |
If you require Gentoo to automatically obtain an IP address for your network |
16705 |
interface(s), you need to install <c>dhcpcd</c> (or any other DHCP Client) |
16706 |
on your system. If you don't do this now, you might not be able to connect |
16707 |
to the internet after the installation! |
16708 |
</p> |
16709 |
|
16710 |
<pre caption="Installing dhcpcd"> |
16711 |
# <i>emerge dhcpcd</i> |
16712 |
</pre> |
16713 |
|
16714 |
</body> |
16715 |
</subsection> |
16716 |
<subsection> |
16717 |
<title>Optional: Installing a PPPoE Client</title> |
16718 |
<body> |
16719 |
|
16720 |
<p> |
16721 |
If you need <c>rp-pppoe</c> to connect to the net, you need to install it. |
16722 |
</p> |
16723 |
|
16724 |
<pre caption="Installing rp-pppoe"> |
16725 |
# <i>USE="-X" emerge rp-pppoe</i> |
16726 |
</pre> |
16727 |
|
16728 |
<p> |
16729 |
The <c>USE="-X"</c> will prohibit xorg-x11 to be installed as a dependency |
16730 |
(<c>rp-pppoe</c> has graphical tools; if you want those enabled, you can |
16731 |
recompile <c>rp-pppoe</c> later on or have xorg-x11 installed now -- which takes a |
16732 |
long time to compile). |
16733 |
</p> |
16734 |
|
16735 |
<p> |
16736 |
Now continue with <uri link="?part=1&chap=10">Configuring the |
16737 |
Bootloader</uri>. |
16738 |
</p> |
16739 |
|
16740 |
</body> |
16741 |
</subsection> |
16742 |
</section> |
16743 |
</sections> |
16744 |
|
16745 |
|
16746 |
|
16747 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-x86-bootloader.xml |
16748 |
|
16749 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-x86-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
16750 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-x86-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
16751 |
|
16752 |
Index: hb-install-x86-bootloader.xml |
16753 |
=================================================================== |
16754 |
<?xml version='1.0' encoding='UTF-8'?> |
16755 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
16756 |
|
16757 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
16758 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
16759 |
|
16760 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-x86-bootloader.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
16761 |
|
16762 |
<sections> |
16763 |
|
16764 |
<version>5.5</version> |
16765 |
<date>2006-02-02</date> |
16766 |
|
16767 |
<section> |
16768 |
<title>Making your Choice</title> |
16769 |
<subsection> |
16770 |
<title>Introduction</title> |
16771 |
<body> |
16772 |
|
16773 |
<p> |
16774 |
Now that your kernel is configured and compiled and the necessary system |
16775 |
configuration files are filled in correctly, it is time to install a |
16776 |
program that will fire up your kernel when you start the system. Such a |
16777 |
program is called a <e>bootloader</e>. For x86, Gentoo Linux provides <uri |
16778 |
link="#grub">GRUB</uri> and <uri link="#lilo">LILO</uri>. But before we |
16779 |
install one of these two bootloaders, we inform you how to configure framebuffer |
16780 |
(assuming you want it of course). With framebuffer you can run the Linux command |
16781 |
line with (limited) graphical features (such as using the nice bootsplash |
16782 |
image Gentoo provides). |
16783 |
</p> |
16784 |
|
16785 |
</body> |
16786 |
</subsection> |
16787 |
<subsection> |
16788 |
<title>Optional: Framebuffer</title> |
16789 |
<body> |
16790 |
|
16791 |
<p> |
16792 |
<e>If</e> you have configured your kernel with framebuffer support (or you used |
16793 |
<c>genkernel</c>'s default kernel configuration), you can activate it by adding |
16794 |
a <c>vga</c> and/or a <c>video</c> statement to your bootloader configuration |
16795 |
file. |
16796 |
</p> |
16797 |
|
16798 |
<p> |
16799 |
First of all you need to know what type of framebuffer device you're using. If |
16800 |
you use a Gentoo patched kernel tree (such as <c>gentoo-sources</c>) you will |
16801 |
have had the possibility of selecting <c>vesafb-tng</c> as the <e>VESA driver |
16802 |
type</e> (which is default for these kernel sources). If this is the case, you |
16803 |
are using <c>vesafb-tng</c> and do not need to set a <c>vga</c> statement. |
16804 |
Otherwise you are using the <c>vesafb</c> driver and need to set the <c>vga</c> |
16805 |
statement. |
16806 |
</p> |
16807 |
|
16808 |
<p> |
16809 |
The <c>vga</c> statement controls the resolution and color depth of your |
16810 |
framebuffer screen for <c>vesafb</c>. As stated in |
16811 |
<path>/usr/src/linux/Documentation/fb/vesafb.txt</path> (which gets installed |
16812 |
when you install a kernel source package), you need to pass the VESA number |
16813 |
corresponding to the requested resolution and color depth to it. |
16814 |
</p> |
16815 |
|
16816 |
<p> |
16817 |
The following table lists the available resolutions and colordepths and matches |
16818 |
those against the value that you need to pass on to the <c>vga</c> statement. |
16819 |
</p> |
16820 |
|
16821 |
<table> |
16822 |
<tr> |
16823 |
<ti></ti> |
16824 |
<th>640x480</th> |
16825 |
<th>800x600</th> |
16826 |
<th>1024x768</th> |
16827 |
<th>1280x1024</th> |
16828 |
</tr> |
16829 |
<tr> |
16830 |
<th>256</th> |
16831 |
<ti>0x301</ti> |
16832 |
<ti>0x303</ti> |
16833 |
<ti>0x305</ti> |
16834 |
<ti>0x307</ti> |
16835 |
</tr> |
16836 |
<tr> |
16837 |
<th>32k</th> |
16838 |
<ti>0x310</ti> |
16839 |
<ti>0x313</ti> |
16840 |
<ti>0x316</ti> |
16841 |
<ti>0x319</ti> |
16842 |
</tr> |
16843 |
<tr> |
16844 |
<th>64k</th> |
16845 |
<ti>0x311</ti> |
16846 |
<ti>0x314</ti> |
16847 |
<ti>0x317</ti> |
16848 |
<ti>0x31A</ti> |
16849 |
</tr> |
16850 |
<tr> |
16851 |
<th>16M</th> |
16852 |
<ti>0x312</ti> |
16853 |
<ti>0x315</ti> |
16854 |
<ti>0x318</ti> |
16855 |
<ti>0x31B</ti> |
16856 |
</tr> |
16857 |
</table> |
16858 |
|
16859 |
<p> |
16860 |
The <c>video</c> statement controls framebuffer display options. It needs to be |
16861 |
given the framebuffer driver (<c>vesafb</c> for 2.6 kernels, or <c>vesa</c> for |
16862 |
2.4 kernels) followed by the control statements you wish to enable. All |
16863 |
variables are listed in <path>/usr/src/linux/Documentation/fb/vesafb.txt</path>, |
16864 |
but we'll inform you about three most-used options: |
16865 |
</p> |
16866 |
|
16867 |
<table> |
16868 |
<tr> |
16869 |
<th>Control</th> |
16870 |
<th>Description</th> |
16871 |
</tr> |
16872 |
<tr> |
16873 |
<ti>ywrap</ti> |
16874 |
<ti> |
16875 |
Assume that the graphical card can wrap around its memory (i.e. continue at |
16876 |
the beginning when it has approached the end) |
16877 |
</ti> |
16878 |
</tr> |
16879 |
<tr> |
16880 |
<ti>mtrr</ti> |
16881 |
<ti> |
16882 |
Setup MTRR registers |
16883 |
</ti> |
16884 |
</tr> |
16885 |
<tr> |
16886 |
<ti><c>mode</c></ti> |
16887 |
<ti> |
16888 |
(<c>vesafb-tng</c> only)<br/> |
16889 |
Set up the resolution, color depth and refresh rate. For instance, |
16890 |
<c>1024x768-32@85</c> for a resolution of 1024x768, 32 bit color depth and a |
16891 |
refresh rate of 85 Hz. |
16892 |
</ti> |
16893 |
</tr> |
16894 |
</table> |
16895 |
|
16896 |
<p> |
16897 |
The result of those two statements could be something like <c>vga=0x318 |
16898 |
video=vesafb:mtrr,ywrap</c> or <c>video=vesafb:mtrr,ywrap,1024x768-32@85</c>. |
16899 |
Remember (or write down) this setting; you will need it shortly. |
16900 |
</p> |
16901 |
|
16902 |
<p> |
16903 |
Now continue by installing <uri link="#grub">GRUB</uri> <e>or</e> <uri |
16904 |
link="#lilo">LILO</uri>. |
16905 |
</p> |
16906 |
|
16907 |
</body> |
16908 |
</subsection> |
16909 |
</section> |
16910 |
<section id="grub"> |
16911 |
<title>Default: Using GRUB</title> |
16912 |
<subsection> |
16913 |
<title>Understanding GRUB's terminology</title> |
16914 |
<body> |
16915 |
|
16916 |
<p> |
16917 |
The most critical part of understanding GRUB is getting comfortable with |
16918 |
how GRUB refers to hard drives and partitions. Your Linux partition |
16919 |
<path>/dev/hda1</path> will most likely be called <path>(hd0,0)</path> under |
16920 |
GRUB. Notice the parenthesis around the <path>hd0,0</path> - they are required. |
16921 |
</p> |
16922 |
|
16923 |
<p> |
16924 |
Hard drives count from zero rather than "a" and partitions start at zero |
16925 |
rather than one. Be aware too that with the hd devices, only hard drives are |
16926 |
counted, not atapi-ide devices such as cdrom players and burners. Also, the |
16927 |
same construct is used with SCSI drives. (Normally they get higher numbers |
16928 |
than IDE drives except when the BIOS is configured to boot from SCSI devices.) |
16929 |
When you ask the BIOS to boot from a different hard disk (for instance your |
16930 |
primary slave), <e>that</e> harddisk is seen as <path>hd0</path>. |
16931 |
</p> |
16932 |
|
16933 |
<p> |
16934 |
Assuming you have a hard drive on <path>/dev/hda</path>, a cdrom player on |
16935 |
<path>/dev/hdb</path>, a burner on <path>/dev/hdc</path>, a second hard drive |
16936 |
on <path>/dev/hdd</path> and no SCSI hard drive, <path>/dev/hdd7</path> gets |
16937 |
translated to <path>(hd1,6)</path>. It might sound tricky and tricky it is |
16938 |
indeed, but as we will see, GRUB offers a tab completion mechanism |
16939 |
that comes handy for those of you having a lot of hard drives and |
16940 |
partitions and who are a little lost in the GRUB numbering scheme. |
16941 |
</p> |
16942 |
|
16943 |
<p> |
16944 |
Having gotten the feel for that, it is time to install GRUB. |
16945 |
</p> |
16946 |
|
16947 |
</body> |
16948 |
</subsection> |
16949 |
<subsection> |
16950 |
<title>Installing GRUB</title> |
16951 |
<body> |
16952 |
|
16953 |
<p> |
16954 |
To install GRUB, let's first emerge it: |
16955 |
</p> |
16956 |
|
16957 |
<pre caption="Installing GRUB"> |
16958 |
# <i>emerge grub</i> |
16959 |
</pre> |
16960 |
|
16961 |
<p> |
16962 |
Although GRUB is now installed, we still need to write up a |
16963 |
configuration file for it and place GRUB in our MBR so that GRUB automatically |
16964 |
boots your newly created kernel. Create <path>/boot/grub/grub.conf</path> with |
16965 |
<c>nano</c> (or, if applicable, another editor): |
16966 |
</p> |
16967 |
|
16968 |
<pre caption="Creating /boot/grub/grub.conf"> |
16969 |
# <i>nano -w /boot/grub/grub.conf</i> |
16970 |
</pre> |
16971 |
|
16972 |
<p> |
16973 |
Now we are going to write up a <path>grub.conf</path>. Below you'll |
16974 |
find two possible <path>grub.conf</path> for the partitioning example we use |
16975 |
in this guide. We've |
16976 |
only extensively commented the first <path>grub.conf</path>. Make sure you use |
16977 |
<e>your</e> kernel image filename and, if appropriate, <e>your</e> initrd image |
16978 |
filename. |
16979 |
</p> |
16980 |
|
16981 |
<ul> |
16982 |
<li> |
16983 |
The first <path>grub.conf</path> is for people who have not used |
16984 |
<c>genkernel</c> to build their kernel |
16985 |
</li> |
16986 |
<li> |
16987 |
The second <path>grub.conf</path> is for people who have used |
16988 |
<c>genkernel</c> to build their kernel |
16989 |
</li> |
16990 |
</ul> |
16991 |
|
16992 |
<note> |
16993 |
If your root filesystem is JFS, you <e>must</e> add " ro" to the <c>kernel</c> |
16994 |
line since JFS needs to replay its log before it allows read-write mounting. |
16995 |
</note> |
16996 |
|
16997 |
<pre caption="grub.conf for non-genkernel users"> |
16998 |
<comment># Which listing to boot as default. 0 is the first, 1 the second etc.</comment> |
16999 |
default 0 |
17000 |
<comment># How many seconds to wait before the default listing is booted.</comment> |
17001 |
timeout 30 |
17002 |
<comment># Nice, fat splash-image to spice things up :) |
17003 |
# Comment out if you don't have a graphics card installed</comment> |
17004 |
splashimage=(hd0,0)/boot/grub/splash.xpm.gz |
17005 |
|
17006 |
title=Gentoo Linux 2.6.12-r10 |
17007 |
<comment># Partition where the kernel image (or operating system) is located</comment> |
17008 |
root (hd0,0) |
17009 |
kernel /boot/kernel-2.6.12-gentoo-r10 root=/dev/hda3 |
17010 |
|
17011 |
<comment># The next four lines are only if you dualboot with a Windows system.</comment> |
17012 |
<comment># In this case, Windows is hosted on /dev/hda6.</comment> |
17013 |
title=Windows XP |
17014 |
rootnoverify (hd0,5) |
17015 |
makeactive |
17016 |
chainloader +1 |
17017 |
</pre> |
17018 |
|
17019 |
<pre caption="grub.conf for genkernel users"> |
17020 |
default 0 |
17021 |
timeout 30 |
17022 |
splashimage=(hd0,0)/boot/grub/splash.xpm.gz |
17023 |
|
17024 |
title=Gentoo Linux 2.6.12-r10 |
17025 |
root (hd0,0) |
17026 |
kernel /boot/kernel-genkernel-x86-2.6.12-gentoo-r10 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 udev |
17027 |
initrd /boot/initramfs-genkernel-x86-2.6.12-gentoo-r10 |
17028 |
|
17029 |
<comment># Only in case you want to dual-boot</comment> |
17030 |
title=Windows XP |
17031 |
rootnoverify (hd0,5) |
17032 |
makeactive |
17033 |
chainloader +1 |
17034 |
</pre> |
17035 |
|
17036 |
<p> |
17037 |
If you used a different partitioning scheme and/or kernel image, adjust |
17038 |
accordingly. However, make sure that anything that follows a GRUB-device (such |
17039 |
as <path>(hd0,0)</path>) is relative to the mountpoint, not the root. In other |
17040 |
words, <path>(hd0,0)/grub/splash.xpm.gz</path> is in reality |
17041 |
<path>/boot/grub/splash.xpm.gz</path> since <path>(hd0,0)</path> is |
17042 |
<path>/boot</path>. |
17043 |
</p> |
17044 |
|
17045 |
<p> |
17046 |
Besides, if you chose to use a different partitioning scheme and did not put |
17047 |
<path>/boot</path> in a separate partition, the <path>/boot</path> prefix used |
17048 |
in the above code samples is really <e>required</e>. If you followed our |
17049 |
suggested partitioning plan, the <path>/boot</path> prefix it not required, but |
17050 |
a <path>boot</path> symlink makes it work. In short, the above examples should |
17051 |
work whether you defined a separate <path>/boot</path> partition or not. |
17052 |
</p> |
17053 |
|
17054 |
<p> |
17055 |
If you need to pass any additional options to the kernel, simply add |
17056 |
them to the end of the kernel command. We're already passing one option |
17057 |
(<c>root=/dev/hda3</c> or <c>real_root=/dev/hda3</c>), but you can pass others |
17058 |
as well, such as the <c>video</c> and/or <c>vga</c> statements for framebuffer |
17059 |
as we discussed previously. |
17060 |
</p> |
17061 |
|
17062 |
<p> |
17063 |
If you're using a 2.6.7 or higher kernel and you jumpered your harddrive |
17064 |
because the BIOS can't handle large harddrives you'll need to append |
17065 |
<c>hdx=stroke</c>. |
17066 |
</p> |
17067 |
|
17068 |
<p> |
17069 |
<c>genkernel</c> users should know that their kernels use the same boot options |
17070 |
as is used for the Installation CD. For instance, if you have SCSI devices, you |
17071 |
should add <c>doscsi</c> as kernel option. |
17072 |
</p> |
17073 |
|
17074 |
<p> |
17075 |
Now save the <path>grub.conf</path> file and exit. You still need to install |
17076 |
GRUB in the MBR (Master Boot Record) so that GRUB is automatically executed when |
17077 |
you boot your system. |
17078 |
</p> |
17079 |
|
17080 |
<p> |
17081 |
The GRUB developers recommend the use of <c>grub-install</c>. However, if for |
17082 |
some reason <c>grub-install</c> fails to work correctly you still have the |
17083 |
option to manually install GRUB. |
17084 |
</p> |
17085 |
|
17086 |
<p> |
17087 |
Continue with <uri link="#grub-install-auto">Default: Setting up GRUB using |
17088 |
grub-install</uri> or <uri link="#grub-install-manual">Alternative: Setting up |
17089 |
GRUB using manual instructions</uri>. |
17090 |
</p> |
17091 |
|
17092 |
</body> |
17093 |
</subsection> |
17094 |
<subsection id="grub-install-auto"> |
17095 |
<title>Default: Setting up GRUB using grub-install</title> |
17096 |
<body> |
17097 |
|
17098 |
<p> |
17099 |
To install GRUB you will need to issue the <c>grub-install</c> command. |
17100 |
However, <c>grub-install</c> won't work off-the-shelf since we are inside a |
17101 |
chrooted environment. We need to create <path>/etc/mtab</path> which lists all |
17102 |
mounted filesystems. Fortunately, there is an easy way to accomplish this - |
17103 |
just copy over <path>/proc/mounts</path> to <path>/etc/mtab</path>, excluding |
17104 |
the <c>rootfs</c> line if you haven't created a separate boot partition. The |
17105 |
following command will work in both cases: |
17106 |
</p> |
17107 |
|
17108 |
<pre caption="Creating /etc/mtab"> |
17109 |
# <i>grep -v rootfs /proc/mounts > /etc/mtab</i> |
17110 |
</pre> |
17111 |
|
17112 |
<p> |
17113 |
Now we can install GRUB using <c>grub-install</c>: |
17114 |
</p> |
17115 |
|
17116 |
<pre caption="Running grub-install"> |
17117 |
# <i>grub-install /dev/hda</i> |
17118 |
</pre> |
17119 |
|
17120 |
<p> |
17121 |
If you have more questions regarding GRUB, please consult the <uri |
17122 |
link="http://www.gnu.org/software/grub/grub-faq.html">GRUB FAQ</uri> or the <uri |
17123 |
link="http://www.gnu.org/software/grub/manual/">GRUB Manual</uri>. |
17124 |
</p> |
17125 |
|
17126 |
<p> |
17127 |
Continue with <uri link="#reboot">Rebooting the System</uri>. |
17128 |
</p> |
17129 |
|
17130 |
</body> |
17131 |
</subsection> |
17132 |
<subsection id="grub-install-manual"> |
17133 |
<title>Alternative: Setting up GRUB using manual instructions</title> |
17134 |
<body> |
17135 |
|
17136 |
<p> |
17137 |
To start configuring GRUB, you type in <c>grub</c>. You'll be presented |
17138 |
with the <path>grub></path> grub command-line prompt. Now, you need to type |
17139 |
in the right commands to install the GRUB boot record onto your hard drive. |
17140 |
</p> |
17141 |
|
17142 |
<pre caption =" Starting the GRUB shell"> |
17143 |
# <i>grub</i> |
17144 |
</pre> |
17145 |
|
17146 |
<note> |
17147 |
If your system does not have any floppy drives, add the <c>--no-floppy</c> |
17148 |
option to the above command to prevent grub from probing the (non-existing) |
17149 |
floppy drives. |
17150 |
</note> |
17151 |
|
17152 |
<p> |
17153 |
In the example configuration we want to install GRUB so that it reads its |
17154 |
information from the boot-partition <path>/dev/hda1</path>, and installs the |
17155 |
GRUB boot record on the hard drive's MBR (master boot record) so that the first |
17156 |
thing we see when we turn on the computer is the GRUB prompt. Of course, if you |
17157 |
haven't followed the example configuration during the installation, |
17158 |
change the commands accordingly. |
17159 |
</p> |
17160 |
|
17161 |
<p> |
17162 |
The tab completion mechanism of GRUB can be used from within GRUB. |
17163 |
For instance, if you type in "<c>root (</c>" followed by a TAB, you will |
17164 |
be presented with a list of devices (such as <path>hd0</path>). If you |
17165 |
type in "<c>root (hd0,</c>" followed by a TAB, you will receive a list |
17166 |
of available partitions to choose from (such as <path>hd0,0</path>). |
17167 |
</p> |
17168 |
|
17169 |
<p> |
17170 |
By using the tab completion, setting up GRUB should be not that hard. |
17171 |
Now go on, configure GRUB, shall we? :-) |
17172 |
</p> |
17173 |
|
17174 |
<pre caption =" Installing GRUB in the MBR"> |
17175 |
grub> <i>root (hd0,0)</i> <comment>(Specify where your /boot partition resides)</comment> |
17176 |
grub> <i>setup (hd0)</i> <comment>(Install GRUB in the MBR)</comment> |
17177 |
grub> <i>quit</i> <comment>(Exit the GRUB shell)</comment> |
17178 |
</pre> |
17179 |
|
17180 |
<note> |
17181 |
If you want to install GRUB in a certain partition instead of the MBR, |
17182 |
you have to alter the <c>setup</c> command so it points to the right |
17183 |
partition. For instance, if you want GRUB installed in |
17184 |
<path>/dev/hda3</path>, then the command becomes <c>setup (hd0,2)</c>. |
17185 |
Few users however want to do this. |
17186 |
</note> |
17187 |
|
17188 |
<p> |
17189 |
If you have more questions regarding GRUB, please consult the <uri |
17190 |
link="http://www.gnu.org/software/grub/grub-faq.html">GRUB FAQ</uri> or the <uri |
17191 |
link="http://www.gnu.org/software/grub/manual/">GRUB Manual</uri>. |
17192 |
</p> |
17193 |
|
17194 |
<note> |
17195 |
When you reinstall a kernel, you do not need to copy over the files anymore. |
17196 |
Just run <c>make install</c> after compiling the kernel; it will automatically |
17197 |
copy the necessary files and adjust the GRUB configuration. |
17198 |
</note> |
17199 |
|
17200 |
<p> |
17201 |
Continue with <uri link="#reboot">Rebooting the System</uri>. |
17202 |
</p> |
17203 |
|
17204 |
</body> |
17205 |
</subsection> |
17206 |
</section> |
17207 |
<section id="lilo"> |
17208 |
<title>Alternative: Using LILO</title> |
17209 |
<subsection> |
17210 |
<title>Installing LILO</title> |
17211 |
<body> |
17212 |
|
17213 |
<p> |
17214 |
LILO, the LInuxLOader, is the tried and true workhorse of Linux |
17215 |
bootloaders. However, it lacks some features that GRUB has (which is |
17216 |
also the reason why GRUB is currently gaining popularity). The reason |
17217 |
why LILO is still used is that, on some systems, GRUB doesn't work and |
17218 |
LILO does. Of course, it is also used because some people know LILO and |
17219 |
want to stick with it. Either way, Gentoo supports both, and apparently |
17220 |
you have chosen to use LILO. |
17221 |
</p> |
17222 |
|
17223 |
<p> |
17224 |
Installing LILO is a breeze; just use <c>emerge</c>. |
17225 |
</p> |
17226 |
|
17227 |
<pre caption = "Installing LILO"> |
17228 |
# <i>emerge lilo</i> |
17229 |
</pre> |
17230 |
|
17231 |
</body> |
17232 |
</subsection> |
17233 |
<subsection> |
17234 |
<title>Configuring LILO</title> |
17235 |
<body> |
17236 |
|
17237 |
<p> |
17238 |
To configure LILO, you must create <path>/etc/lilo.conf</path>. Fire up |
17239 |
your favorite editor (in this handbook we use <c>nano</c> for |
17240 |
consistency) and create the file. |
17241 |
</p> |
17242 |
|
17243 |
<pre caption = "Creating /etc/lilo.conf"> |
17244 |
# <i>nano -w /etc/lilo.conf</i> |
17245 |
</pre> |
17246 |
|
17247 |
<p> |
17248 |
Some sections ago we have asked you to remember the kernel-image name |
17249 |
you have created. In the next example <path>lilo.conf</path> we also use the |
17250 |
example partitioning scheme. There are two separate parts: |
17251 |
</p> |
17252 |
|
17253 |
<ul> |
17254 |
<li> |
17255 |
One for those who have not used <c>genkernel</c> to build their kernel |
17256 |
</li> |
17257 |
<li> |
17258 |
One for those who have used <c>genkernel</c> to build their kernel |
17259 |
</li> |
17260 |
</ul> |
17261 |
|
17262 |
<p> |
17263 |
Make sure you use <e>your</e> kernel image filename and, if appropriate, |
17264 |
<e>your</e> initrd image filename. |
17265 |
</p> |
17266 |
|
17267 |
<note> |
17268 |
If your root filesystem is JFS, you <e>must</e> add an <c>append="ro"</c> line |
17269 |
to each boot image since JFS needs to replay its log before it allows |
17270 |
read-write mounting. |
17271 |
</note> |
17272 |
|
17273 |
<pre caption="Example /etc/lilo.conf"> |
17274 |
boot=/dev/hda <comment># Install LILO in the MBR</comment> |
17275 |
prompt <comment># Give the user the chance to select another section</comment> |
17276 |
timeout=50 <comment># Wait 5 (five) seconds before booting the default section</comment> |
17277 |
default=gentoo <comment># When the timeout has passed, boot the "gentoo" section</comment> |
17278 |
|
17279 |
<comment># For non-genkernel users</comment> |
17280 |
image=/boot/kernel-2.6.12-gentoo-r10 |
17281 |
label=gentoo <comment># Name we give to this section</comment> |
17282 |
read-only <comment># Start with a read-only root. Do not alter!</comment> |
17283 |
root=/dev/hda3 <comment># Location of the root filesystem</comment> |
17284 |
|
17285 |
<comment># For genkernel users</comment> |
17286 |
image=/boot/kernel-genkernel-x86-2.6.12-gentoo-r10 |
17287 |
label=gentoo |
17288 |
read-only |
17289 |
root=/dev/ram0 |
17290 |
append="init=/linuxrc ramdisk=8192 real_root=/dev/hda3 udev" |
17291 |
initrd=/boot/initramfs-genkernel-x86-2.6.12-gentoo-r10 |
17292 |
|
17293 |
<comment># The next two lines are only if you dualboot with a Windows system.</comment> |
17294 |
<comment># In this case, Windows is hosted on /dev/hda6.</comment> |
17295 |
other=/dev/hda6 |
17296 |
label=windows |
17297 |
</pre> |
17298 |
|
17299 |
<note> |
17300 |
If you use a different partitioning scheme and/or kernel image, adjust |
17301 |
accordingly. |
17302 |
</note> |
17303 |
|
17304 |
<p> |
17305 |
If you need to pass any additional options to the kernel, add an |
17306 |
<c>append</c> statement to the section. As an example, we add the |
17307 |
<c>video</c> statement to enable framebuffer: |
17308 |
</p> |
17309 |
|
17310 |
<pre caption="Using append to add kernel options"> |
17311 |
image=/boot/kernel-2.6.12-gentoo-r10 |
17312 |
label=gentoo |
17313 |
read-only |
17314 |
root=/dev/hda3 |
17315 |
<i>append="video=vesafb:mtrr,ywrap,1024x768-32@85"</i> |
17316 |
</pre> |
17317 |
|
17318 |
<p> |
17319 |
If you're using a 2.6.7 or higher kernel and you jumpered your harddrive |
17320 |
because the BIOS can't handle large harddrives you'll need to append |
17321 |
<c>hdx=stroke</c>. |
17322 |
</p> |
17323 |
|
17324 |
<p> |
17325 |
<c>genkernel</c> users should know that their kernels use the same boot options |
17326 |
as is used for the Installation CD. For instance, if you have SCSI devices, you |
17327 |
should add <c>doscsi</c> as kernel option. |
17328 |
</p> |
17329 |
|
17330 |
|
17331 |
<p> |
17332 |
Now save the file and exit. To finish up, you have to run <c>/sbin/lilo</c> so |
17333 |
LILO can apply the <path>/etc/lilo.conf</path> to your system (i.e. install |
17334 |
itself on the disk). Keep in mind that you'll also have to rerun |
17335 |
<c>/sbin/lilo</c> every time you install a new kernel or make any changes to |
17336 |
the menu. |
17337 |
</p> |
17338 |
|
17339 |
<pre caption = "Finishing the LILO installation"> |
17340 |
# <i>/sbin/lilo</i> |
17341 |
</pre> |
17342 |
|
17343 |
<note> |
17344 |
When you reinstall a kernel, you do not need to copy over the files anymore. |
17345 |
Just run <c>make install</c> after compiling the kernel; it will automatically |
17346 |
copy the necessary files and adjust the LILO configuration. |
17347 |
</note> |
17348 |
|
17349 |
<p> |
17350 |
You can now continue with <uri link="#reboot">Rebooting the System</uri>. |
17351 |
</p> |
17352 |
|
17353 |
</body> |
17354 |
</subsection> |
17355 |
</section> |
17356 |
<section id="reboot"> |
17357 |
<title>Rebooting the System</title> |
17358 |
<subsection> |
17359 |
<body> |
17360 |
|
17361 |
<p> |
17362 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
17363 |
that one magical command you have been waiting for: <c>reboot</c>. |
17364 |
</p> |
17365 |
|
17366 |
<pre caption="Unmounting all partitions and rebooting"> |
17367 |
# <i>exit</i> |
17368 |
cdimage ~# <i>cd</i> |
17369 |
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
17370 |
cdimage ~# <i>reboot</i> |
17371 |
</pre> |
17372 |
|
17373 |
<p> |
17374 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
17375 |
booted again instead of your new Gentoo system. |
17376 |
</p> |
17377 |
|
17378 |
<p> |
17379 |
Once rebooted in your Gentoo installation, finish up with <uri |
17380 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
17381 |
</p> |
17382 |
|
17383 |
</body> |
17384 |
</subsection> |
17385 |
</section> |
17386 |
</sections> |
17387 |
|
17388 |
|
17389 |
|
17390 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-x86-disk.xml |
17391 |
|
17392 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-x86-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
17393 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-x86-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
17394 |
|
17395 |
Index: hb-install-x86-disk.xml |
17396 |
=================================================================== |
17397 |
<?xml version='1.0' encoding='UTF-8'?> |
17398 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
17399 |
|
17400 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
17401 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
17402 |
|
17403 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-x86-disk.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
17404 |
|
17405 |
<sections> |
17406 |
|
17407 |
<version>5.2</version> |
17408 |
<date>2006-01-01</date> |
17409 |
|
17410 |
<section> |
17411 |
<title>Introduction to Block Devices</title> |
17412 |
<subsection> |
17413 |
<title>Block Devices</title> |
17414 |
<body> |
17415 |
|
17416 |
<p> |
17417 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
17418 |
and Linux in general, including Linux filesystems, partitions and block devices. |
17419 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
17420 |
you'll be guided through the process of setting up partitions and filesystems |
17421 |
for your Gentoo Linux installation. |
17422 |
</p> |
17423 |
|
17424 |
<p> |
17425 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
17426 |
probably the one that represents the first IDE drive in a Linux system, namely |
17427 |
<path>/dev/hda</path>. If your system uses SCSI or SATA drives, then your |
17428 |
first hard drive would be <path>/dev/sda</path>. |
17429 |
</p> |
17430 |
|
17431 |
<p> |
17432 |
The block devices above represent an abstract interface to the disk. User |
17433 |
programs can use these block devices to interact with your disk without worrying |
17434 |
about whether your drives are IDE, SCSI or something else. The program can |
17435 |
simply address the storage on the disk as a bunch of contiguous, |
17436 |
randomly-accessible 512-byte blocks. |
17437 |
</p> |
17438 |
|
17439 |
</body> |
17440 |
</subsection> |
17441 |
<subsection> |
17442 |
<title>Partitions</title> |
17443 |
<body> |
17444 |
|
17445 |
<p> |
17446 |
Although it is theoretically possible to use a full disk to house your Linux |
17447 |
system, this is almost never done in practice. Instead, full disk block devices |
17448 |
are split up in smaller, more manageable block devices. On x86 systems, |
17449 |
these are called <e>partitions</e>. |
17450 |
</p> |
17451 |
|
17452 |
<p> |
17453 |
Partitions are divided in three types: |
17454 |
<e>primary</e>, <e>extended</e> and <e>logical</e>. |
17455 |
</p> |
17456 |
|
17457 |
<p> |
17458 |
A <e>primary</e> partition is a partition which has its information stored in |
17459 |
the MBR (master boot record). As an MBR is very small (512 bytes) only four |
17460 |
primary partitions can be defined (for instance, <path>/dev/hda1</path> to |
17461 |
<path>/dev/hda4</path>). |
17462 |
</p> |
17463 |
|
17464 |
<p> |
17465 |
An <e>extended</e> partition is a special primary partition (meaning the |
17466 |
extended partition must be one of the four possible primary partitions) which |
17467 |
contains more partitions. Such a partition didn't exist originally, but as |
17468 |
four partitions were too few, it was brought to life to extend the formatting |
17469 |
scheme without losing backward compatibility. |
17470 |
</p> |
17471 |
|
17472 |
<p> |
17473 |
A <e>logical</e> partition is a partition inside the extended partition. Their |
17474 |
definitions aren't placed inside the MBR, but are declared inside the extended |
17475 |
partition. |
17476 |
</p> |
17477 |
|
17478 |
</body> |
17479 |
</subsection> |
17480 |
<subsection> |
17481 |
<title>Advanced Storage</title> |
17482 |
<body> |
17483 |
|
17484 |
<p> |
17485 |
The x86 Installation CDs provide support for EVMS and LVM2. EVMS and LVM2 |
17486 |
increase the flexibility offered by your partitioning setup. During the |
17487 |
installation instructions, we will focus on "regular" partitions, but it is |
17488 |
still good to know EVMS and LVM2 are supported as well. |
17489 |
</p> |
17490 |
|
17491 |
</body> |
17492 |
</subsection> |
17493 |
</section> |
17494 |
<section> |
17495 |
<title>Designing a Partitioning Scheme</title> |
17496 |
<subsection> |
17497 |
<title>Default Partitioning Scheme</title> |
17498 |
<body> |
17499 |
|
17500 |
<p> |
17501 |
If you are not interested in drawing up a partitioning scheme for your system, |
17502 |
you can use the partitioning scheme we use throughout this book: |
17503 |
</p> |
17504 |
|
17505 |
<table> |
17506 |
<tr> |
17507 |
<th>Partition</th> |
17508 |
<th>Filesystem</th> |
17509 |
<th>Size</th> |
17510 |
<th>Description</th> |
17511 |
</tr> |
17512 |
<tr> |
17513 |
<ti><path>/dev/hda1</path></ti> |
17514 |
<ti>ext2</ti> |
17515 |
<ti>32M</ti> |
17516 |
<ti>Boot partition</ti> |
17517 |
</tr> |
17518 |
<tr> |
17519 |
<ti><path>/dev/hda2</path></ti> |
17520 |
<ti>(swap)</ti> |
17521 |
<ti>512M</ti> |
17522 |
<ti>Swap partition</ti> |
17523 |
</tr> |
17524 |
<tr> |
17525 |
<ti><path>/dev/hda3</path></ti> |
17526 |
<ti>ext3</ti> |
17527 |
<ti>Rest of the disk</ti> |
17528 |
<ti>Root partition</ti> |
17529 |
</tr> |
17530 |
</table> |
17531 |
|
17532 |
<p> |
17533 |
If you are interested in knowing how big a partition should be, or even how |
17534 |
many partitions you need, read on. Otherwise continue now with partitioning |
17535 |
your disk by reading <uri link="#fdisk">Using fdisk to Partition your |
17536 |
Disk</uri>. |
17537 |
</p> |
17538 |
|
17539 |
</body> |
17540 |
</subsection> |
17541 |
<subsection> |
17542 |
<title>How Many and How Big?</title> |
17543 |
<body> |
17544 |
|
17545 |
<p> |
17546 |
The number of partitions is highly dependent on your environment. For instance, |
17547 |
if you have lots of users, you will most likely want to have your |
17548 |
<path>/home</path> separate as it increases security and makes backups easier. |
17549 |
If you are installing Gentoo to perform as a mailserver, your |
17550 |
<path>/var</path> should be separate as all mails are stored inside |
17551 |
<path>/var</path>. A good choice of filesystem will then maximise your |
17552 |
performance. Gameservers will have a separate <path>/opt</path> as most gaming |
17553 |
servers are installed there. The reason is similar for <path>/home</path>: |
17554 |
security and backups. You will definitely want to keep <path>/usr</path> big: |
17555 |
not only will it contain the majority of applications, the Portage tree alone |
17556 |
takes around 500 Mbyte excluding the various sources that are stored in it. |
17557 |
</p> |
17558 |
|
17559 |
<p> |
17560 |
As you can see, it very much depends on what you want to achieve. Separate |
17561 |
partitions or volumes have the following advantages: |
17562 |
</p> |
17563 |
|
17564 |
<ul> |
17565 |
<li> |
17566 |
You can choose the best performing filesystem for each partition or volume |
17567 |
</li> |
17568 |
<li> |
17569 |
Your entire system cannot run out of free space if one defunct tool is |
17570 |
continuously writing files to a partition or volume |
17571 |
</li> |
17572 |
<li> |
17573 |
If necessary, file system checks are reduced in time, as multiple checks can |
17574 |
be done in parallel (although this advantage is more with multiple disks than |
17575 |
it is with multiple partitions) |
17576 |
</li> |
17577 |
<li> |
17578 |
Security can be enhanced by mounting some partitions or volumes read-only, |
17579 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
17580 |
</li> |
17581 |
</ul> |
17582 |
|
17583 |
<p> |
17584 |
However, multiple partitions have one big disadvantage: if not configured |
17585 |
properly, you might result in having a system with lots |
17586 |
of free space on one partition and none on another. There is also a 15-partition |
17587 |
limit for SCSI and SATA. |
17588 |
</p> |
17589 |
|
17590 |
<p> |
17591 |
As an example partitioning, we show you one for a 20GB disk, used as a |
17592 |
demonstration laptop (containing webserver, mailserver, gnome, ...): |
17593 |
</p> |
17594 |
|
17595 |
<pre caption="Filesystem usage example"> |
17596 |
Filesystem Type Size Used Avail Use% Mounted on |
17597 |
/dev/hda5 ext3 509M 132M 351M 28% / |
17598 |
/dev/hda2 ext3 5.0G 3.0G 1.8G 63% /home |
17599 |
/dev/hda7 ext3 7.9G 6.2G 1.3G 83% /usr |
17600 |
/dev/hda8 ext3 1011M 483M 477M 51% /opt |
17601 |
/dev/hda9 ext3 2.0G 607M 1.3G 32% /var |
17602 |
/dev/hda1 ext2 51M 17M 31M 36% /boot |
17603 |
/dev/hda6 swap 516M 12M 504M 2% <not mounted> |
17604 |
<comment>(Unpartitioned space for future usage: 2 GB)</comment> |
17605 |
</pre> |
17606 |
|
17607 |
<p> |
17608 |
<path>/usr</path> is rather full (83% used) here, but once |
17609 |
all software is installed, <path>/usr</path> doesn't tend to grow that much. |
17610 |
Although allocating a few gigabytes of disk space for <path>/var</path> may |
17611 |
seem excessive, remember that Portage uses this partition by default for |
17612 |
compiling packages. If you want to keep <path>/var</path> at a more reasonable |
17613 |
size, such as 1GB, you will need to alter your <c>PORTAGE_TMPDIR</c> variable |
17614 |
in <path>/etc/make.conf</path> to point to the partition with enough free space |
17615 |
for compiling extremely large packages such as OpenOffice. |
17616 |
</p> |
17617 |
|
17618 |
</body> |
17619 |
</subsection> |
17620 |
</section> |
17621 |
<section id="fdisk"> |
17622 |
<title>Using fdisk to Partition your Disk</title> |
17623 |
<subsection> |
17624 |
<body> |
17625 |
|
17626 |
<p> |
17627 |
The following parts explain how to create the example partition layout |
17628 |
described previously, namely: |
17629 |
</p> |
17630 |
|
17631 |
<table> |
17632 |
<tr> |
17633 |
<th>Partition</th> |
17634 |
<th>Description</th> |
17635 |
</tr> |
17636 |
<tr> |
17637 |
<ti><path>/dev/hda1</path></ti> |
17638 |
<ti>Boot partition</ti> |
17639 |
</tr> |
17640 |
<tr> |
17641 |
<ti><path>/dev/hda2</path></ti> |
17642 |
<ti>Swap partition</ti> |
17643 |
</tr> |
17644 |
<tr> |
17645 |
<ti><path>/dev/hda3</path></ti> |
17646 |
<ti>Root partition</ti> |
17647 |
</tr> |
17648 |
</table> |
17649 |
|
17650 |
<p> |
17651 |
Change your partition layout according to your own preference. |
17652 |
</p> |
17653 |
|
17654 |
</body> |
17655 |
</subsection> |
17656 |
<subsection> |
17657 |
<title>Viewing the Current Partition Layout</title> |
17658 |
<body> |
17659 |
|
17660 |
<p> |
17661 |
<c>fdisk</c> is a popular and powerful tool to split your disk into partitions. |
17662 |
Fire up <c>fdisk</c> on your disk (in our example, we use |
17663 |
<path>/dev/hda</path>): |
17664 |
</p> |
17665 |
|
17666 |
<pre caption="Starting fdisk"> |
17667 |
# <i>fdisk /dev/hda</i> |
17668 |
</pre> |
17669 |
|
17670 |
<p> |
17671 |
Once in <c>fdisk</c>, you'll be greeted with a prompt that looks like this: |
17672 |
</p> |
17673 |
|
17674 |
<pre caption="fdisk prompt"> |
17675 |
Command (m for help): |
17676 |
</pre> |
17677 |
|
17678 |
<p> |
17679 |
Type <c>p</c> to display your disk's current partition configuration: |
17680 |
</p> |
17681 |
|
17682 |
<pre caption="An example partition configuration"> |
17683 |
Command (m for help): <i>p</i> |
17684 |
|
17685 |
Disk /dev/hda: 240 heads, 63 sectors, 2184 cylinders |
17686 |
Units = cylinders of 15120 * 512 bytes |
17687 |
|
17688 |
Device Boot Start End Blocks Id System |
17689 |
/dev/hda1 1 14 105808+ 83 Linux |
17690 |
/dev/hda2 15 49 264600 82 Linux swap |
17691 |
/dev/hda3 50 70 158760 83 Linux |
17692 |
/dev/hda4 71 2184 15981840 5 Extended |
17693 |
/dev/hda5 71 209 1050808+ 83 Linux |
17694 |
/dev/hda6 210 348 1050808+ 83 Linux |
17695 |
/dev/hda7 349 626 2101648+ 83 Linux |
17696 |
/dev/hda8 627 904 2101648+ 83 Linux |
17697 |
/dev/hda9 905 2184 9676768+ 83 Linux |
17698 |
|
17699 |
Command (m for help): |
17700 |
</pre> |
17701 |
|
17702 |
<p> |
17703 |
This particular disk is configured to house seven Linux filesystems (each with a |
17704 |
corresponding partition listed as "Linux") as well as a swap partition (listed |
17705 |
as "Linux swap"). |
17706 |
</p> |
17707 |
|
17708 |
</body> |
17709 |
</subsection> |
17710 |
<subsection> |
17711 |
<title>Removing all Partitions</title> |
17712 |
<body> |
17713 |
|
17714 |
<p> |
17715 |
We will first remove all existing partitions from the disk. Type <c>d</c> to |
17716 |
delete a partition. For instance, to delete an existing <path>/dev/hda1</path>: |
17717 |
</p> |
17718 |
|
17719 |
<pre caption="Deleting a partition"> |
17720 |
Command (m for help): <i>d</i> |
17721 |
Partition number (1-4): <i>1</i> |
17722 |
</pre> |
17723 |
|
17724 |
<p> |
17725 |
The partition has been scheduled for deletion. It will no longer show up if you |
17726 |
type <c>p</c>, but it will not be erased until your changes have been saved. If |
17727 |
you made a mistake and want to abort without saving your changes, type <c>q</c> |
17728 |
immediately and hit enter and your partition will not be deleted. |
17729 |
</p> |
17730 |
|
17731 |
<p> |
17732 |
Now, assuming that you do indeed want to wipe out all the partitions on your |
17733 |
system, repeatedly type <c>p</c> to print out a partition listing and then type |
17734 |
<c>d</c> and the number of the partition to delete it. Eventually, you'll end |
17735 |
up with a partition table with nothing in it: |
17736 |
</p> |
17737 |
|
17738 |
<pre caption="An empty partition table"> |
17739 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
17740 |
240 heads, 63 sectors/track, 3876 cylinders |
17741 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
17742 |
|
17743 |
Device Boot Start End Blocks Id System |
17744 |
|
17745 |
Command (m for help): |
17746 |
</pre> |
17747 |
|
17748 |
<p> |
17749 |
Now that the in-memory partition table is empty, we're ready to create the |
17750 |
partitions. We will use a default partitioning scheme as discussed previously. |
17751 |
Of course, don't follow these instructions to the letter if you don't want the |
17752 |
same partitioning scheme! |
17753 |
</p> |
17754 |
|
17755 |
</body> |
17756 |
</subsection> |
17757 |
<subsection> |
17758 |
<title>Creating the Boot Partition</title> |
17759 |
<body> |
17760 |
|
17761 |
<p> |
17762 |
We first create a small boot partition. Type <c>n</c> to create a new partition, |
17763 |
then <c>p</c> to select a primary partition, followed by <c>1</c> to select the |
17764 |
first primary partition. When prompted for the first cylinder, hit enter. When |
17765 |
prompted for the last cylinder, type <c>+32M</c> to create a partition 32 Mbyte |
17766 |
in size: |
17767 |
</p> |
17768 |
|
17769 |
<pre caption="Creating the boot partition"> |
17770 |
Command (m for help): <i>n</i> |
17771 |
Command action |
17772 |
e extended |
17773 |
p primary partition (1-4) |
17774 |
<i>p</i> |
17775 |
Partition number (1-4): <i>1</i> |
17776 |
First cylinder (1-3876, default 1): <comment>(Hit Enter)</comment> |
17777 |
Using default value 1 |
17778 |
Last cylinder or +size or +sizeM or +sizeK (1-3876, default 3876): <i>+32M</i> |
17779 |
</pre> |
17780 |
|
17781 |
<p> |
17782 |
Now, when you type <c>p</c>, you should see the following partition printout: |
17783 |
</p> |
17784 |
|
17785 |
<pre caption="Created boot partition"> |
17786 |
Command (m for help): <i>p</i> |
17787 |
|
17788 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
17789 |
240 heads, 63 sectors/track, 3876 cylinders |
17790 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
17791 |
|
17792 |
Device Boot Start End Blocks Id System |
17793 |
/dev/hda1 1 14 105808+ 83 Linux |
17794 |
</pre> |
17795 |
|
17796 |
<p> |
17797 |
We need to make this partition bootable. Type <c>a</c> to toggle the bootable |
17798 |
flag on a partition and select <c>1</c>. If you press <c>p</c> again, you will |
17799 |
notice that an <path>*</path> is placed in the "Boot" column. |
17800 |
</p> |
17801 |
|
17802 |
</body> |
17803 |
</subsection> |
17804 |
<subsection> |
17805 |
<title>Creating the Swap Partition</title> |
17806 |
<body> |
17807 |
|
17808 |
<p> |
17809 |
Let's now create the swap partition. To do this, type <c>n</c> to create a new |
17810 |
partition, then <c>p</c> to tell fdisk that you want a primary partition. Then |
17811 |
type <c>2</c> to create the second primary partition, <path>/dev/hda2</path> in |
17812 |
our case. When prompted for the first cylinder, hit enter. When prompted for |
17813 |
the last cylinder, type <c>+512M</c> to create a partition 512MB in size. After |
17814 |
you've done this, type <c>t</c> to set the partition type, <c>2</c> to select |
17815 |
the partition you just created and then type in <c>82</c> to set the partition |
17816 |
type to "Linux Swap". After completing these steps, typing <c>p</c> should |
17817 |
display a partition table that looks similar to this: |
17818 |
</p> |
17819 |
|
17820 |
<pre caption="Partition listing after creating a swap partition"> |
17821 |
Command (m for help): <i>p</i> |
17822 |
|
17823 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
17824 |
240 heads, 63 sectors/track, 3876 cylinders |
17825 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
17826 |
|
17827 |
Device Boot Start End Blocks Id System |
17828 |
/dev/hda1 * 1 14 105808+ 83 Linux |
17829 |
/dev/hda2 15 81 506520 82 Linux swap |
17830 |
</pre> |
17831 |
|
17832 |
</body> |
17833 |
</subsection> |
17834 |
<subsection> |
17835 |
<title>Creating the Root Partition</title> |
17836 |
<body> |
17837 |
|
17838 |
<p> |
17839 |
Finally, let's create the root partition. To do this, type <c>n</c> to create a |
17840 |
new partition, then <c>p</c> to tell fdisk that you want a primary partition. |
17841 |
Then type <c>3</c> to create the third primary partition, <path>/dev/hda3</path> |
17842 |
in our case. When prompted for the first cylinder, hit enter. When prompted for |
17843 |
the last cylinder, hit enter to create a partition that takes up the rest of the |
17844 |
remaining space on your disk. After completing these steps, typing <c>p</c> |
17845 |
should display a partition table that looks similar to this: |
17846 |
</p> |
17847 |
|
17848 |
<pre caption="Partition listing after creating the root partition"> |
17849 |
Command (m for help): <i>p</i> |
17850 |
|
17851 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
17852 |
240 heads, 63 sectors/track, 3876 cylinders |
17853 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
17854 |
|
17855 |
Device Boot Start End Blocks Id System |
17856 |
/dev/hda1 * 1 14 105808+ 83 Linux |
17857 |
/dev/hda2 15 81 506520 82 Linux swap |
17858 |
/dev/hda3 82 3876 28690200 83 Linux |
17859 |
</pre> |
17860 |
|
17861 |
|
17862 |
</body> |
17863 |
</subsection> |
17864 |
<subsection> |
17865 |
<title>Saving the Partition Layout</title> |
17866 |
<body> |
17867 |
|
17868 |
<p> |
17869 |
To save the partition layout and exit <c>fdisk</c>, type <c>w</c>. |
17870 |
</p> |
17871 |
|
17872 |
<pre caption="Save and exit fdisk"> |
17873 |
Command (m for help): <i>w</i> |
17874 |
</pre> |
17875 |
|
17876 |
<p> |
17877 |
Now that your partitions are created, you can now continue with <uri |
17878 |
link="#filesystems">Creating Filesystems</uri>. |
17879 |
</p> |
17880 |
|
17881 |
</body> |
17882 |
</subsection> |
17883 |
</section> |
17884 |
<section id="filesystems"> |
17885 |
<title>Creating Filesystems</title> |
17886 |
<subsection> |
17887 |
<title>Introduction</title> |
17888 |
<body> |
17889 |
|
17890 |
<p> |
17891 |
Now that your partitions are created, it is time to place a filesystem on them. |
17892 |
If you don't care about what filesystem to choose and are happy with what we use |
17893 |
as default in this handbook, continue with <uri |
17894 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
17895 |
Otherwise read on to learn about the available filesystems... |
17896 |
</p> |
17897 |
|
17898 |
</body> |
17899 |
</subsection> |
17900 |
<subsection> |
17901 |
<title>Filesystems?</title> |
17902 |
<body> |
17903 |
|
17904 |
<p> |
17905 |
The Linux kernel supports various filesystems. We'll explain ext2, ext3, |
17906 |
ReiserFS, XFS and JFS as these are the most commonly used filesystems on Linux |
17907 |
systems. |
17908 |
</p> |
17909 |
|
17910 |
<p> |
17911 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
17912 |
journaling, which means that routine ext2 filesystem checks at startup time can |
17913 |
be quite time-consuming. There is now quite a selection of newer-generation |
17914 |
journaled filesystems that can be checked for consistency very quickly and are |
17915 |
thus generally preferred over their non-journaled counterparts. Journaled |
17916 |
filesystems prevent long delays when you boot your system and your filesystem |
17917 |
happens to be in an inconsistent state. |
17918 |
</p> |
17919 |
|
17920 |
<p> |
17921 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
17922 |
journaling for fast recovery in addition to other enhanced journaling modes like |
17923 |
full data and ordered data journaling. ext3 is a very good and reliable |
17924 |
filesystem. It has an additional hashed b-tree indexing option that enables |
17925 |
high performance in almost all situations. You can enable this indexing by |
17926 |
adding <c>-O dir_index</c> to the <c>mke2fs</c> command. In short, ext3 is an |
17927 |
excellent filesystem. |
17928 |
</p> |
17929 |
|
17930 |
<p> |
17931 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
17932 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
17933 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
17934 |
extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is |
17935 |
solid and usable as both general-purpose filesystem and for extreme cases such |
17936 |
as the creation of large filesystems, the use of many small files, very large |
17937 |
files and directories containing tens of thousands of files. |
17938 |
</p> |
17939 |
|
17940 |
<p> |
17941 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
17942 |
feature-set and is optimized for scalability. We only recommend using this |
17943 |
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
17944 |
an uninterruptible power supply. Because XFS aggressively caches in-transit data |
17945 |
in RAM, improperly designed programs (those that don't take proper precautions |
17946 |
when writing files to disk and there are quite a few of them) can lose a good |
17947 |
deal of data if the system goes down unexpectedly. |
17948 |
</p> |
17949 |
|
17950 |
<p> |
17951 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
17952 |
become production-ready and there hasn't been a sufficient track record to |
17953 |
comment positively nor negatively on its general stability at this point. |
17954 |
</p> |
17955 |
|
17956 |
</body> |
17957 |
</subsection> |
17958 |
<subsection id="filesystems-apply"> |
17959 |
<title>Applying a Filesystem to a Partition</title> |
17960 |
<body> |
17961 |
|
17962 |
<p> |
17963 |
To create a filesystem on a partition or volume, there are tools available for |
17964 |
each possible filesystem: |
17965 |
</p> |
17966 |
|
17967 |
<table> |
17968 |
<tr> |
17969 |
<th>Filesystem</th> |
17970 |
<th>Creation Command</th> |
17971 |
</tr> |
17972 |
<tr> |
17973 |
<ti>ext2</ti> |
17974 |
<ti><c>mke2fs</c></ti> |
17975 |
</tr> |
17976 |
<tr> |
17977 |
<ti>ext3</ti> |
17978 |
<ti><c>mke2fs -j</c></ti> |
17979 |
</tr> |
17980 |
<tr> |
17981 |
<ti>reiserfs</ti> |
17982 |
<ti><c>mkreiserfs</c></ti> |
17983 |
</tr> |
17984 |
<tr> |
17985 |
<ti>xfs</ti> |
17986 |
<ti><c>mkfs.xfs</c></ti> |
17987 |
</tr> |
17988 |
<tr> |
17989 |
<ti>jfs</ti> |
17990 |
<ti><c>mkfs.jfs</c></ti> |
17991 |
</tr> |
17992 |
</table> |
17993 |
|
17994 |
<p> |
17995 |
For instance, to have the boot partition (<path>/dev/hda1</path> in our |
17996 |
example) in ext2 and the root partition (<path>/dev/hda3</path> in our example) |
17997 |
in ext3 (as in our example), you would use: |
17998 |
</p> |
17999 |
|
18000 |
<pre caption="Applying a filesystem on a partition"> |
18001 |
# <i>mke2fs /dev/hda1</i> |
18002 |
# <i>mke2fs -j /dev/hda3</i> |
18003 |
</pre> |
18004 |
|
18005 |
<p> |
18006 |
Now create the filesystems on your newly created partitions (or logical |
18007 |
volumes). |
18008 |
</p> |
18009 |
|
18010 |
</body> |
18011 |
</subsection> |
18012 |
<subsection> |
18013 |
<title>Activating the Swap Partition</title> |
18014 |
<body> |
18015 |
|
18016 |
<p> |
18017 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
18018 |
</p> |
18019 |
|
18020 |
<pre caption="Creating a Swap signature"> |
18021 |
# <i>mkswap /dev/hda2</i> |
18022 |
</pre> |
18023 |
|
18024 |
<p> |
18025 |
To activate the swap partition, use <c>swapon</c>: |
18026 |
</p> |
18027 |
|
18028 |
<pre caption="Activating the swap partition"> |
18029 |
# <i>swapon /dev/hda2</i> |
18030 |
</pre> |
18031 |
|
18032 |
<p> |
18033 |
Create and activate the swap now. |
18034 |
</p> |
18035 |
|
18036 |
</body> |
18037 |
</subsection> |
18038 |
</section> |
18039 |
<section> |
18040 |
<title>Mounting</title> |
18041 |
<body> |
18042 |
|
18043 |
<p> |
18044 |
Now that your partitions are initialized and are housing a filesystem, it is |
18045 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
18046 |
create the necessary mount directories for every partition you created. As an |
18047 |
example we mount the root and boot partition: |
18048 |
</p> |
18049 |
|
18050 |
<pre caption="Mounting partitions"> |
18051 |
# <i>mount /dev/hda3 /mnt/gentoo</i> |
18052 |
# <i>mkdir /mnt/gentoo/boot</i> |
18053 |
# <i>mount /dev/hda1 /mnt/gentoo/boot</i> |
18054 |
</pre> |
18055 |
|
18056 |
<note> |
18057 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
18058 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
18059 |
also holds for <path>/var/tmp</path>. |
18060 |
</note> |
18061 |
|
18062 |
<p> |
18063 |
We will also have to mount the proc filesystem (a virtual interface with the |
18064 |
kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. |
18065 |
</p> |
18066 |
|
18067 |
<p> |
18068 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
18069 |
Installation Files</uri>. |
18070 |
</p> |
18071 |
|
18072 |
</body> |
18073 |
</section> |
18074 |
</sections> |
18075 |
|
18076 |
|
18077 |
|
18078 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-x86-kernel.xml |
18079 |
|
18080 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-x86-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
18081 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-x86-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
18082 |
|
18083 |
Index: hb-install-x86-kernel.xml |
18084 |
=================================================================== |
18085 |
<?xml version='1.0' encoding='UTF-8'?> |
18086 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
18087 |
|
18088 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
18089 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
18090 |
|
18091 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-x86-kernel.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
18092 |
|
18093 |
<sections> |
18094 |
|
18095 |
<version>5.5</version> |
18096 |
<date>2006-01-06</date> |
18097 |
|
18098 |
<section> |
18099 |
<title>Timezone</title> |
18100 |
<body> |
18101 |
|
18102 |
<p> |
18103 |
You first need to select your timezone so that your system knows where it is |
18104 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
18105 |
it to <path>/etc/localtime</path>. Please avoid the |
18106 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
18107 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
18108 |
</p> |
18109 |
|
18110 |
<pre caption="Setting the timezone information"> |
18111 |
# <i>ls /usr/share/zoneinfo</i> |
18112 |
<comment>(Suppose you want to use GMT)</comment> |
18113 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
18114 |
</pre> |
18115 |
|
18116 |
</body> |
18117 |
</section> |
18118 |
<section> |
18119 |
<title>Installing the Sources</title> |
18120 |
<subsection> |
18121 |
<title>Choosing a Kernel</title> |
18122 |
<body> |
18123 |
|
18124 |
<p> |
18125 |
The core around which all distributions are built is the Linux kernel. It is the |
18126 |
layer between the user programs and your system hardware. Gentoo provides its |
18127 |
users several possible kernel sources. A full listing with description is |
18128 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
18129 |
Guide</uri>. |
18130 |
</p> |
18131 |
|
18132 |
<p> |
18133 |
For x86-based systems, our main supported kernel is named |
18134 |
<c>gentoo-sources</c>. This kernel is based on the official Linux sources, but |
18135 |
has security, stability, compatibility and bug fixes applied on top. |
18136 |
Alternatively, the plain and unpatched Linux sources are supplied through the |
18137 |
<c>vanilla-sources</c> package. |
18138 |
</p> |
18139 |
|
18140 |
<p> |
18141 |
Both kernel sources are based on the official 2.6 kernel sources. If you |
18142 |
want to install a 2.4-based kernel, you will need to install Gentoo with a |
18143 |
working Internet connection as we do not supply these sources on our |
18144 |
Installation CD. |
18145 |
</p> |
18146 |
|
18147 |
<p> |
18148 |
Choose your kernel source and install it using <c>emerge</c>. The |
18149 |
<c>USE="-doc"</c> is necessary to avoid installing xorg-x11 or other |
18150 |
dependencies at this point. <c>USE="symlink"</c> is not necessary for a new |
18151 |
install, but ensures proper creation of the <path>/usr/src/linux</path> |
18152 |
symlink. |
18153 |
</p> |
18154 |
|
18155 |
<pre caption="Installing a kernel source"> |
18156 |
# <i>USE="-doc symlink" emerge gentoo-sources</i> |
18157 |
</pre> |
18158 |
|
18159 |
<p> |
18160 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
18161 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
18162 |
kernel source points to <c>gentoo-sources-2.6.12-r10</c>. Your version may be |
18163 |
different, so keep this in mind. |
18164 |
</p> |
18165 |
|
18166 |
<pre caption="Viewing the kernel source symlink"> |
18167 |
# <i>ls -l /usr/src/linux</i> |
18168 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-2.6.12-gentoo-r10 |
18169 |
</pre> |
18170 |
|
18171 |
<p> |
18172 |
Now it is time to configure and compile your kernel source. You |
18173 |
can use <c>genkernel</c> for this, which will build a generic kernel as used |
18174 |
by the Installation CD. We explain the "manual" configuration first though, as |
18175 |
it is the best way to optimize your environment. |
18176 |
</p> |
18177 |
|
18178 |
<p> |
18179 |
If you want to manually configure your kernel, continue now with <uri |
18180 |
link="#manual">Default: Manual Configuration</uri>. If you want to use |
18181 |
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
18182 |
genkernel</uri> instead. |
18183 |
</p> |
18184 |
|
18185 |
</body> |
18186 |
</subsection> |
18187 |
</section> |
18188 |
<section id="manual"> |
18189 |
<title>Default: Manual Configuration</title> |
18190 |
<subsection> |
18191 |
<title>Introduction</title> |
18192 |
<body> |
18193 |
|
18194 |
<p> |
18195 |
Manually configuring a kernel is often seen as the most difficult procedure a |
18196 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
18197 |
couple of kernels you don't even remember that it was difficult ;) |
18198 |
</p> |
18199 |
|
18200 |
<p> |
18201 |
However, one thing <e>is</e> true: you must know your system when you start |
18202 |
configuring a kernel manually. Most information can be gathered by emerging |
18203 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
18204 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
18205 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
18206 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
18207 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
18208 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
18209 |
uses (it might provide you with a nice hint on what to enable). |
18210 |
</p> |
18211 |
|
18212 |
<p> |
18213 |
Now go to your kernel source directory and execute <c>make menuconfig</c>. This |
18214 |
will fire up an ncurses-based configuration menu. |
18215 |
</p> |
18216 |
|
18217 |
<pre caption="Invoking menuconfig"> |
18218 |
# <i>cd /usr/src/linux</i> |
18219 |
# <i>make menuconfig</i> |
18220 |
</pre> |
18221 |
|
18222 |
<p> |
18223 |
You will be greeted with several configuration sections. We'll first list some |
18224 |
options you must activate (otherwise Gentoo will not function, or not function |
18225 |
properly without additional tweaks). |
18226 |
</p> |
18227 |
|
18228 |
</body> |
18229 |
</subsection> |
18230 |
<subsection> |
18231 |
<title>Activating Required Options</title> |
18232 |
<body> |
18233 |
|
18234 |
<p> |
18235 |
Make sure that every driver that is vital to the booting of your system (such as |
18236 |
SCSI controller, ...) is compiled <e>in</e> the kernel and not as a module, |
18237 |
otherwise your system will not be able to boot completely. |
18238 |
</p> |
18239 |
|
18240 |
<p> |
18241 |
Now select the correct processor family: |
18242 |
</p> |
18243 |
|
18244 |
<pre caption="General Support and processor family"> |
18245 |
General setup ---> |
18246 |
[*] Support for hot-pluggable devices |
18247 |
Processor type and features ---> |
18248 |
Subarchitecture Type (PC-compatible) ---> |
18249 |
<comment>(Change according to your system)</comment> |
18250 |
(<i>Athlon/Duron/K7</i>) Processor family |
18251 |
</pre> |
18252 |
|
18253 |
<p> |
18254 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
18255 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
18256 |
able to mount your partitions. Also select <c>/proc file system</c> and |
18257 |
<c>Virtual memory</c>. |
18258 |
</p> |
18259 |
|
18260 |
<pre caption="Selecting necessary file systems"> |
18261 |
File systems ---> |
18262 |
Pseudo Filesystems ---> |
18263 |
<*> /proc file system support |
18264 |
<*> Virtual memory file system support (former shm fs) |
18265 |
|
18266 |
|
18267 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
18268 |
<*> Reiserfs support |
18269 |
<*> Ext3 journalling file system support |
18270 |
<*> JFS filesystem support |
18271 |
<*> Second extended fs support |
18272 |
<*> XFS filesystem support |
18273 |
</pre> |
18274 |
|
18275 |
<p> |
18276 |
Do not forget to enable DMA for your drives: |
18277 |
</p> |
18278 |
|
18279 |
<pre caption="Activating DMA"> |
18280 |
Device Drivers ---> |
18281 |
ATA/ATAPI/MFM/RLL support ---> |
18282 |
[*] Generic PCI bus-master DMA support |
18283 |
[*] Use PCI DMA by default when available |
18284 |
</pre> |
18285 |
|
18286 |
<p> |
18287 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
18288 |
modem, you will need the following options in the kernel: |
18289 |
</p> |
18290 |
|
18291 |
<pre caption="Selecting PPPoE necessary drivers"> |
18292 |
Device Drivers ---> |
18293 |
Networking support ---> |
18294 |
<*> PPP (point-to-point protocol) support |
18295 |
<*> PPP support for async serial ports |
18296 |
<*> PPP support for sync tty ports |
18297 |
</pre> |
18298 |
|
18299 |
<p> |
18300 |
The two compression options won't harm but are not definitely needed, neither |
18301 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
18302 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
18303 |
</p> |
18304 |
|
18305 |
<p> |
18306 |
If you require it, don't forget to include support in the kernel for your |
18307 |
ethernet card. |
18308 |
</p> |
18309 |
|
18310 |
<p> |
18311 |
If you have an Intel CPU that supports HyperThreading (tm), or you have a |
18312 |
multi-CPU system, you should activate "Symmetric multi-processing support": |
18313 |
</p> |
18314 |
|
18315 |
<pre caption="Activating SMP support"> |
18316 |
Processor type and features ---> |
18317 |
<*> Symmetric multi-processing support |
18318 |
</pre> |
18319 |
|
18320 |
<p> |
18321 |
If you use USB Input Devices (like Keyboard or Mouse) don't forget to enable |
18322 |
those as well: |
18323 |
</p> |
18324 |
|
18325 |
<pre caption="Activating USB Support for Input Devices"> |
18326 |
Device Drivers ---> |
18327 |
USB Support ---> |
18328 |
<*> USB Human Interface Device (full HID) support |
18329 |
[*] HID input layer support |
18330 |
</pre> |
18331 |
|
18332 |
<p> |
18333 |
If you are a laptop user and require PCMCIA support, remember to compile it |
18334 |
into the kernel. As well as the option below, be sure to enable support for |
18335 |
the PCMCIA card bridge present in your system (found in the same menu of the |
18336 |
configuration). |
18337 |
</p> |
18338 |
|
18339 |
<pre caption="Activating PCMCIA support"> |
18340 |
Bus options (PCI, PCMCIA, EISA, MCA, ISA) ---> |
18341 |
PCCARD (PCMCIA/CardBus) support ---> |
18342 |
<*> PCCard (PCMCIA/CardBus) support |
18343 |
<comment>(select 16 bit if you need support for older PCMCIA cards. Most people want this.)</comment> |
18344 |
<*> 16-bit PCMCIA support |
18345 |
[*] 32-bit CardBus support |
18346 |
<comment>(select the relevant bridges below)</comment> |
18347 |
--- PC-card bridges |
18348 |
<*> CardBus yenta-compatible bridge support (NEW) |
18349 |
<*> Cirrus PD6729 compatible bridge support (NEW) |
18350 |
<*> i82092 compatible bridge support (NEW) |
18351 |
<*> i82365 compatible bridge support (NEW) |
18352 |
<*> Databook TCIC host bridge support (NEW) |
18353 |
</pre> |
18354 |
|
18355 |
</body> |
18356 |
</subsection> |
18357 |
<subsection id="compiling"> |
18358 |
<title>Compiling and Installing</title> |
18359 |
<body> |
18360 |
|
18361 |
<p> |
18362 |
Now that your kernel is configured, it is time to compile and install it. Exit |
18363 |
the configuration and start the compilation process: |
18364 |
</p> |
18365 |
|
18366 |
<pre caption="Compiling the kernel"> |
18367 |
# <i>make && make modules_install</i> |
18368 |
</pre> |
18369 |
|
18370 |
<p> |
18371 |
When the kernel has finished compiling, copy the kernel image to |
18372 |
<path>/boot</path>. Use whatever name you feel is appropriate for your kernel |
18373 |
choice and remember it as you will need it later on when you configure your |
18374 |
bootloader. Remember to replace <path><kernel-version></path> with the |
18375 |
name and version of your kernel. |
18376 |
</p> |
18377 |
|
18378 |
<pre caption="Installing the kernel"> |
18379 |
# <i>cp arch/i386/boot/bzImage /boot/<kernel-version></i> |
18380 |
</pre> |
18381 |
|
18382 |
<p> |
18383 |
Now continue with <uri link="#kernel_modules">Configuring Kernel |
18384 |
Modules</uri>. |
18385 |
</p> |
18386 |
|
18387 |
</body> |
18388 |
</subsection> |
18389 |
</section> |
18390 |
<section id="genkernel"> |
18391 |
<title>Alternative: Using genkernel</title> |
18392 |
<body> |
18393 |
|
18394 |
<p> |
18395 |
If you are reading this section, you have chosen to use our <c>genkernel</c> |
18396 |
script to configure your kernel for you. |
18397 |
</p> |
18398 |
|
18399 |
<p> |
18400 |
Now that your kernel source tree is installed, it's now time to compile your |
18401 |
kernel by using our <c>genkernel</c> script to automatically build a kernel for |
18402 |
you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
18403 |
way our Installation CD kernel is configured. This means that when you use |
18404 |
<c>genkernel</c> to build your kernel, your system will generally detect all |
18405 |
your hardware at boot-time, just like our Installation CD does. Because genkernel |
18406 |
doesn't require any manual kernel configuration, it is an ideal solution for |
18407 |
those users who may not be comfortable compiling their own kernels. |
18408 |
</p> |
18409 |
|
18410 |
<p> |
18411 |
Now, let's see how to use genkernel. First, emerge the genkernel ebuild: |
18412 |
</p> |
18413 |
|
18414 |
<pre caption="Emerging genkernel"> |
18415 |
# <i>emerge genkernel</i> |
18416 |
</pre> |
18417 |
|
18418 |
<p> |
18419 |
Now, compile your kernel sources by running <c>genkernel all</c>. |
18420 |
Be aware though, as <c>genkernel</c> compiles a kernel that supports almost all |
18421 |
hardware, this compilation will take quite a while to finish! |
18422 |
</p> |
18423 |
|
18424 |
<p> |
18425 |
Note that, if your boot partition doesn't use ext2 or ext3 as filesystem you |
18426 |
might need to manually configure your kernel using <c>genkernel --menuconfig |
18427 |
all</c> and add support for your filesystem <e>in</e> the kernel (i.e. |
18428 |
<e>not</e> as a module). Users of EVMS2 or LVM2 will probably want to add |
18429 |
<c>--evms2</c> or <c>--lvm2</c> as argument as well. |
18430 |
</p> |
18431 |
|
18432 |
<pre caption="Running genkernel"> |
18433 |
# <i>genkernel all</i> |
18434 |
</pre> |
18435 |
|
18436 |
<p> |
18437 |
Once <c>genkernel</c> completes, a kernel, full set of modules and |
18438 |
<e>initial root disk</e> (initrd) will be created. We will use the kernel |
18439 |
and initrd when configuring a boot loader later in this document. Write |
18440 |
down the names of the kernel and initrd as you will need it when writing |
18441 |
the bootloader configuration file. The initrd will be started immediately after |
18442 |
booting to perform hardware autodetection (just like on the Installation CD) |
18443 |
before your "real" system starts up. |
18444 |
</p> |
18445 |
|
18446 |
<pre caption="Checking the created kernel image name and initrd"> |
18447 |
# <i>ls /boot/kernel* /boot/initramfs*</i> |
18448 |
</pre> |
18449 |
|
18450 |
<p> |
18451 |
If you want your system to be more like the Installation CD you should |
18452 |
emerge <c>coldplug</c>. While the initrd autodetects hardware that is |
18453 |
needed to boot your system, <c>coldplug</c> autodetects everything |
18454 |
else. |
18455 |
</p> |
18456 |
|
18457 |
<pre caption="Emerging and enabling coldplug"> |
18458 |
# <i>emerge coldplug</i> |
18459 |
# <i>rc-update add coldplug boot</i> |
18460 |
</pre> |
18461 |
|
18462 |
</body> |
18463 |
</section> |
18464 |
<section id="kernel_modules"> |
18465 |
<title>Configuring Kernel Modules</title> |
18466 |
<subsection> |
18467 |
<title>Configuring the Modules</title> |
18468 |
<body> |
18469 |
|
18470 |
<p> |
18471 |
You should list the modules you want automatically loaded in |
18472 |
<path>/etc/modules.autoload.d/kernel-2.6</path> (or <path>kernel-2.4</path>). |
18473 |
You can add extra options to the modules too if you want. |
18474 |
</p> |
18475 |
|
18476 |
<p> |
18477 |
To view all available modules, run the following <c>find</c> command. Don't |
18478 |
forget to substitute "<kernel version>" with the version of the kernel you |
18479 |
just compiled: |
18480 |
</p> |
18481 |
|
18482 |
<pre caption="Viewing all available modules"> |
18483 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
18484 |
</pre> |
18485 |
|
18486 |
<p> |
18487 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
18488 |
<path>kernel-2.6</path> (or <path>kernel-2.4</path>) file and enter the module |
18489 |
name in it. |
18490 |
</p> |
18491 |
|
18492 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
18493 |
<comment>(Example for 2.6 kernels)</comment> |
18494 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
18495 |
</pre> |
18496 |
|
18497 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
18498 |
3c59x |
18499 |
</pre> |
18500 |
|
18501 |
<p> |
18502 |
Now continue with <uri link="?part=1&chap=8">Configuring your System</uri>. |
18503 |
</p> |
18504 |
|
18505 |
</body> |
18506 |
</subsection> |
18507 |
</section> |
18508 |
</sections> |
18509 |
|
18510 |
|
18511 |
|
18512 |
1.1 xml/htdocs/doc/en/handbook/2006.0/hb-install-x86-medium.xml |
18513 |
|
18514 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-x86-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
18515 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2006.0/hb-install-x86-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
18516 |
|
18517 |
Index: hb-install-x86-medium.xml |
18518 |
=================================================================== |
18519 |
<?xml version='1.0' encoding='UTF-8'?> |
18520 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
18521 |
|
18522 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
18523 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
18524 |
|
18525 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2006.0/hb-install-x86-medium.xml,v 1.1 2006/02/27 00:11:36 fox2mike Exp $ --> |
18526 |
|
18527 |
<sections> |
18528 |
|
18529 |
<version>5.5</version> |
18530 |
<date>2005-11-29</date> |
18531 |
|
18532 |
<section> |
18533 |
<title>Hardware Requirements</title> |
18534 |
<subsection> |
18535 |
<title>Introduction</title> |
18536 |
<body> |
18537 |
|
18538 |
<p> |
18539 |
Before we start, we first list what hardware requirements you need to |
18540 |
successfully install Gentoo on your box. |
18541 |
</p> |
18542 |
|
18543 |
</body> |
18544 |
</subsection> |
18545 |
<subsection> |
18546 |
<title>Hardware Requirements</title> |
18547 |
<body> |
18548 |
|
18549 |
<table> |
18550 |
<tr> |
18551 |
<th>CPU</th> |
18552 |
<ti>i486 or later</ti> |
18553 |
</tr> |
18554 |
<tr> |
18555 |
<th>Memory</th> |
18556 |
<ti>64 MB</ti> |
18557 |
</tr> |
18558 |
<tr> |
18559 |
<th>Diskspace</th> |
18560 |
<ti>1.5 GB (excluding swap space)</ti> |
18561 |
</tr> |
18562 |
<tr> |
18563 |
<th>Swap space</th> |
18564 |
<ti>At least 256 MB</ti> |
18565 |
</tr> |
18566 |
</table> |
18567 |
|
18568 |
|
18569 |
</body> |
18570 |
</subsection> |
18571 |
</section> |
18572 |
<!-- General description, propagated to other architectures as well --> |
18573 |
<!-- START --> |
18574 |
<section> |
18575 |
<title>The Gentoo Universal Installation CD</title> |
18576 |
<subsection> |
18577 |
<title>Introduction</title> |
18578 |
<body> |
18579 |
|
18580 |
<p> |
18581 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
18582 |
Such a tarball is an archive that contains a minimal environment from |
18583 |
which you can successfully install Gentoo Linux onto your system. |
18584 |
</p> |
18585 |
|
18586 |
<p> |
18587 |
Installations using a stage1 or stage2 tarball file are not documented in the |
18588 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
18589 |
FAQ</uri> on these matters. |
18590 |
</p> |
18591 |
|
18592 |
</body> |
18593 |
</subsection> |
18594 |
<subsection> |
18595 |
<title>Gentoo Universal Installation CD</title> |
18596 |
<body> |
18597 |
|
18598 |
<p> |
18599 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
18600 |
environment. It allows you to boot Linux from the CD. During the boot process |
18601 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
18602 |
Installation CDs are maintained by Gentoo developers. |
18603 |
</p> |
18604 |
|
18605 |
<p> |
18606 |
There currently are two Installation CDs available: |
18607 |
</p> |
18608 |
|
18609 |
<ul> |
18610 |
<li> |
18611 |
The Universal Installation CD contains everything you need to install |
18612 |
Gentoo. It provides stage3 files for common architectures, source code |
18613 |
for the extra applications you need to choose from and, of course, the |
18614 |
installation instructions for your architecture. |
18615 |
</li> |
18616 |
<li> |
18617 |
The Minimal Installation CD contains only a minimal environment that allows |
18618 |
you to boot up and configure your network so you can connect to the |
18619 |
Internet. It does not contain any additional files and cannot be used |
18620 |
during the current installation approach. |
18621 |
</li> |
18622 |
</ul> |
18623 |
|
18624 |
<p> |
18625 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
18626 |
additional resource that you can exploit during the installation of your Gentoo |
18627 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
18628 |
you to easily and quickly install additional applications (such as |
18629 |
OpenOffice.org, KDE, GNOME, ...) immediately after the Gentoo installation and |
18630 |
right before you update your Portage tree. |
18631 |
</p> |
18632 |
|
18633 |
<p> |
18634 |
The use of the Package CD is covered later in this document. |
18635 |
</p> |
18636 |
|
18637 |
</body> |
18638 |
</subsection> |
18639 |
</section> |
18640 |
<!-- STOP --> |
18641 |
<section> |
18642 |
<title>Download, Burn and Boot the Gentoo Universal Installation CD</title> |
18643 |
<subsection> |
18644 |
<title>Downloading and Burning the Installation CD</title> |
18645 |
<body> |
18646 |
|
18647 |
<p> |
18648 |
You can download the Universal Installation CDs (and, if you want to, the |
18649 |
Packages CD as well) from one of our <uri |
18650 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located in |
18651 |
the <path>releases/x86/2005.1-r1/installcd</path> directory; |
18652 |
the Package CDs are located in the <path>releases/x86/2005.1/packagecd</path> |
18653 |
directory. |
18654 |
</p> |
18655 |
|
18656 |
<p> |
18657 |
i686, athlon-xp, pentium3 and pentium4 Package CDs are available via |
18658 |
<uri link="http://tracker.netdomination.org">BitTorrent</uri>. |
18659 |
</p> |
18660 |
|
18661 |
<p> |
18662 |
Inside those directories you'll find ISO-files. Those are full CD images which |
18663 |
you can write on a CD-R. |
18664 |
</p> |
18665 |
|
18666 |
<p> |
18667 |
After downloading the file, you can verify its integrity to see if it is |
18668 |
corrupted or not: |
18669 |
</p> |
18670 |
|
18671 |
<ul> |
18672 |
<li> |
18673 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
18674 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
18675 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows) |
18676 |
</li> |
18677 |
<li> |
18678 |
You can verify the cryptographic signature that we provide. You need to |
18679 |
obtain the public key we use (17072058) before you proceed though. |
18680 |
</li> |
18681 |
</ul> |
18682 |
|
18683 |
<p> |
18684 |
To fetch our public key using the GnuPG application, run the following command: |
18685 |
</p> |
18686 |
|
18687 |
<pre caption="Obtaining the public key"> |
18688 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
18689 |
</pre> |
18690 |
|
18691 |
<p> |
18692 |
Now verify the signature: |
18693 |
</p> |
18694 |
|
18695 |
<pre caption="Verify the cryptographic signature"> |
18696 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
18697 |
</pre> |
18698 |
|
18699 |
<p> |
18700 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
18701 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
18702 |
<c>K3B</c> here; more information can be found in our <uri |
18703 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
18704 |
</p> |
18705 |
|
18706 |
<ul> |
18707 |
<li> |
18708 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
18709 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
18710 |
path). |
18711 |
</li> |
18712 |
<li> |
18713 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
18714 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
18715 |
<c>Start</c>. |
18716 |
</li> |
18717 |
</ul> |
18718 |
|
18719 |
</body> |
18720 |
</subsection> |
18721 |
<subsection> |
18722 |
<title>Booting the Universal Installation CD</title> |
18723 |
<body> |
18724 |
|
18725 |
<impo> |
18726 |
Read this whole subsection before continuing, as you will probably not have the |
18727 |
opportunity to read it before doing things later. |
18728 |
</impo> |
18729 |
|
18730 |
<p> |
18731 |
Once you have burned your installation CD, it is time to boot it. |
18732 |
Remove all CDs from your CD drives, reboot your system and enter the BIOS. |
18733 |
This is usually done by hitting DEL, F1 or ESC, depending on your BIOS. Inside |
18734 |
the BIOS, change the boot order so that the CD-ROM is tried before the hard |
18735 |
disk. This is often found under "CMOS Setup". If you don't do this, your system |
18736 |
will just reboot from the hard disk, ignoring the CD-ROM. |
18737 |
</p> |
18738 |
|
18739 |
<p> |
18740 |
Now place the installation CD in the CD-ROM drive and reboot. You |
18741 |
should see a boot prompt. At this screen, you can hit Enter to begin the |
18742 |
boot process with the default boot options, or boot the Installation CD with |
18743 |
custom boot options by specifying a kernel followed by boot options and then |
18744 |
hitting Enter. |
18745 |
</p> |
18746 |
|
18747 |
<p> |
18748 |
Specifying a kernel? Yes, we provide several kernels on our Installation CDs. |
18749 |
The default one is <c>gentoo</c>. Other kernels are for specific hardware needs |
18750 |
and the <c>-nofb</c> variants which disable framebuffer. |
18751 |
</p> |
18752 |
|
18753 |
<p> |
18754 |
Below you'll find a short overview on the available kernels: |
18755 |
</p> |
18756 |
|
18757 |
<table> |
18758 |
<tr> |
18759 |
<th>Kernel</th> |
18760 |
<th>Description</th> |
18761 |
</tr> |
18762 |
<tr> |
18763 |
<ti>gentoo</ti> |
18764 |
<ti>Default 2.6 kernel with support for multiple CPUs</ti> |
18765 |
</tr> |
18766 |
<tr> |
18767 |
<ti>gentoo-nofb</ti> |
18768 |
<ti>Same as <c>gentoo</c> but without framebuffer support</ti> |
18769 |
</tr> |
18770 |
<tr> |
18771 |
<ti>memtest86</ti> |
18772 |
<ti>Test your local RAM for errors</ti> |
18773 |
</tr> |
18774 |
</table> |
18775 |
|
18776 |
<p> |
18777 |
You can also provide kernel options. They represent optional settings you can |
18778 |
(de)activate at will. The following list is the same as the one you receive |
18779 |
when you press F2 at the bootscreen. |
18780 |
</p> |
18781 |
|
18782 |
<pre caption="Options available to pass to your kernel of choice"> |
18783 |
- agpgart loads agpgart (use if you have graphic problems,lockups) |
18784 |
- acpi=on loads support for ACPI firmware |
18785 |
- ide=nodma force disabling of DMA for malfunctioning IDE devices |
18786 |
- doscsi scan for scsi devices (breaks some ethernet cards) |
18787 |
- dopcmcia starts pcmcia service for PCMCIA cdroms |
18788 |
- nofirewire disables firewire modules in initrd (for firewire cdroms,etc) |
18789 |
- nokeymap disables keymap selection for non-us keyboard layouts |
18790 |
- docache cache the entire runtime portion of cd in RAM, allows you |
18791 |
to umount /mnt/cdrom to mount another cdrom. |
18792 |
- nodetect causes hwsetup/kudzu and hotplug not to run |
18793 |
- nousb disables usb module load from initrd, disables hotplug |
18794 |
- nodhcp dhcp does not automatically start if nic detected |
18795 |
- nohotplug disables loading hotplug service |
18796 |
- noapic disable apic (try if having hardware problems nics,scsi,etc) |
18797 |
- noevms2 disable loading of EVMS2 modules |
18798 |
- nolvm2 disable loading of LVM2 modules |
18799 |
- hdx=stroke allows you to partition the whole harddrive even when your BIOS |
18800 |
can't handle large harddrives |
18801 |
- noload=module1[,module2[,...]] |
18802 |
disable loading of specific kernel modules |
18803 |
</pre> |
18804 |
|
18805 |
<p> |
18806 |
Now boot your CD, select a kernel (if you are not happy with the default |
18807 |
<c>gentoo</c> kernel) and boot options. As an example, we show you how |
18808 |
to boot the <c>gentoo</c> kernel, with <c>dopcmcia</c> as kernel |
18809 |
parameters: |
18810 |
</p> |
18811 |
|
18812 |
<pre caption="Booting an Installation CD"> |
18813 |
boot: <i>gentoo dopcmcia</i> |
18814 |
</pre> |
18815 |
|
18816 |
<p> |
18817 |
You will then be greeted with a boot screen and progress bar. If you are |
18818 |
installing Gentoo on a system with a non-US keyboard, make sure you |
18819 |
immediately press Alt-F1 to switch to verbose mode and follow the prompt. If no |
18820 |
selection is made in 10 seconds the default (US keyboard) will be accepted and |
18821 |
the boot process will continue. Once the boot process completes, you will be |
18822 |
automatically logged in to the "Live" Gentoo Linux as |
18823 |
"root", the super user. You should have a root ("#") prompt |
18824 |
on the current console and can also switch to other consoles by pressing Alt-F2, |
18825 |
Alt-F3 and Alt-F4. Get back to the one you started on by pressing Alt-F1. |
18826 |
</p> |
18827 |
|
18828 |
</body> |
18829 |
</subsection> |
18830 |
<subsection id="hardware"> |
18831 |
<title>Extra Hardware Configuration</title> |
18832 |
<body> |
18833 |
|
18834 |
<p> |
18835 |
When the Installation CD boots, it tries to detect all your hardware devices and |
18836 |
loads the appropriate kernel modules to support your hardware. In the |
18837 |
vast majority of cases, it does a very good job. However, in some cases, it |
18838 |
may not auto-load the kernel modules you need. If the PCI auto-detection |
18839 |
missed some of your system's hardware, you will have to load the appropriate |
18840 |
kernel modules manually. |
18841 |
</p> |
18842 |
|
18843 |
<p> |
18844 |
In the next example we try to load the <c>8139too</c> module (support for |
18845 |
certain kinds of network interfaces): |
18846 |
</p> |
18847 |
|
18848 |
<pre caption="Loading kernel modules"> |
18849 |
# <i>modprobe 8139too</i> |
18850 |
</pre> |
18851 |
|
18852 |
<p> |
18853 |
If you need PCMCIA support, you should start the <c>pcmcia</c> init script: |
18854 |
</p> |
18855 |
|
18856 |
<pre caption="Starting the PCMCIA init script"> |
18857 |
# <i>/etc/init.d/pcmcia start</i> |
18858 |
</pre> |
18859 |
|
18860 |
</body> |
18861 |
</subsection> |
18862 |
<subsection> |
18863 |
<title>Optional: Tweaking Hard Disk Performance</title> |
18864 |
<body> |
18865 |
|
18866 |
<p> |
18867 |
If you are an advanced user, you might want to tweak the IDE hard disk |
18868 |
performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
18869 |
test the performance of your disk (execute it several times to get a |
18870 |
more precise impression): |
18871 |
</p> |
18872 |
|
18873 |
<pre caption="Testing disk performance"> |
18874 |
# <i>hdparm -tT /dev/hda</i> |
18875 |
</pre> |
18876 |
|
18877 |
<p> |
18878 |
To tweak, you can use any of the following examples (or experiment |
18879 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
18880 |
disk): |
18881 |
</p> |
18882 |
|
18883 |
<pre caption="Tweaking hard disk performance"> |
18884 |
<comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i> |
18885 |
<comment>Activate Safe Performance Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
18886 |
</pre> |
18887 |
|
18888 |
</body> |
18889 |
</subsection> |
18890 |
<subsection id="useraccounts"> |
18891 |
<title>Optional: User Accounts</title> |
18892 |
<body> |
18893 |
|
18894 |
<p> |
18895 |
If you plan on giving other people access to your installation |
18896 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
18897 |
security reasons), you need to create the necessary user accounts and change |
18898 |
the root password. |
18899 |
</p> |
18900 |
|
18901 |
<p> |
18902 |
To change the root password, use the <c>passwd</c> utility: |
18903 |
</p> |
18904 |
|
18905 |
<pre caption="Changing the root password"> |
18906 |
# <i>passwd</i> |
18907 |
New password: <comment>(Enter your new password)</comment> |
18908 |
Re-enter password: <comment>(Re-enter your password)</comment> |
18909 |
</pre> |
18910 |
|
18911 |
<p> |
18912 |
To create a user account, we first enter their credentials, followed by |
18913 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
18914 |
In the next example, we create a user called "john". |
18915 |
</p> |
18916 |
|
18917 |
<pre caption="Creating a user account"> |
18918 |
# <i>useradd -m -G users john</i> |
18919 |
# <i>passwd john</i> |
18920 |
New password: <comment>(Enter john's password)</comment> |
18921 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
18922 |
</pre> |
18923 |
|
18924 |
<p> |
18925 |
You can change your user id from root to the newly created user by using |
18926 |
<c>su</c>: |
18927 |
</p> |
18928 |
|
18929 |
<pre caption="Changing user id"> |
18930 |
# <i>su - john</i> |
18931 |
</pre> |
18932 |
|
18933 |
</body> |
18934 |
</subsection> |
18935 |
<subsection> |
18936 |
<title>Optional: Viewing Documentation while Installing</title> |
18937 |
<body> |
18938 |
|
18939 |
<p> |
18940 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
18941 |
installation, make sure you have created a user account (see <uri |
18942 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
18943 |
go to a new terminal and log in. |
18944 |
</p> |
18945 |
|
18946 |
<p> |
18947 |
If you want to view the documentation on the CD you can immediately run |
18948 |
<c>links2</c> to read it: |
18949 |
</p> |
18950 |
|
18951 |
<pre caption="Viewing the on-CD documentation"> |
18952 |
# <i>links2 /mnt/cdrom/docs/html/index.html</i> |
18953 |
</pre> |
18954 |
|
18955 |
<p> |
18956 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
18957 |
more recent than the one provided on the CD. You can view it using <c>links2</c> |
18958 |
as well, but only after having completed the <e>Configuring your Network</e> |
18959 |
chapter (otherwise you won't be able to go on the Internet to view the |
18960 |
document): |
18961 |
</p> |
18962 |
|
18963 |
<pre caption="Viewing the Online Documentation"> |
18964 |
# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-x86.xml</i> |
18965 |
</pre> |
18966 |
|
18967 |
<p> |
18968 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
18969 |
</p> |
18970 |
|
18971 |
</body> |
18972 |
</subsection> |
18973 |
<subsection> |
18974 |
<title>Optional: Starting the SSH Daemon</title> |
18975 |
<body> |
18976 |
|
18977 |
<p> |
18978 |
If you want to allow other users to access your computer during the |
18979 |
Gentoo installation (perhaps because those users are going to help you |
18980 |
install Gentoo, or even do it for you), you need to create a user |
18981 |
account for them and perhaps even provide them with your root password |
18982 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
18983 |
</p> |
18984 |
|
18985 |
<p> |
18986 |
To fire up the SSH daemon, execute the following command: |
18987 |
</p> |
18988 |
|
18989 |
<pre caption="Starting the SSH daemon"> |
18990 |
# <i>/etc/init.d/sshd start</i> |
18991 |
</pre> |
18992 |
|
18993 |
<p> |
18994 |
To be able to use sshd, you first need to set up your networking. Continue with |
18995 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
18996 |
</p> |
18997 |
|
18998 |
</body> |
18999 |
</subsection> |
19000 |
</section> |
19001 |
</sections> |
19002 |
|
19003 |
|
19004 |
|
19005 |
-- |
19006 |
gentoo-doc-cvs@g.o mailing list |