1 |
nightmorph 07/03/14 06:24:41 |
2 |
|
3 |
Added: handbook-alpha.xml handbook-amd64.xml |
4 |
handbook-arm.xml handbook-hppa.xml |
5 |
handbook-ia64.xml handbook-mips.xml |
6 |
handbook-ppc64.xml handbook-ppc.xml |
7 |
handbook-sparc.xml handbook-x86.xml |
8 |
hb-install-about.xml |
9 |
hb-install-alpha-bootloader.xml |
10 |
hb-install-alpha-disk.xml |
11 |
hb-install-alpha-kernel.xml |
12 |
hb-install-alpha-medium.xml |
13 |
hb-install-arm-bootloader.xml |
14 |
hb-install-arm-disk.xml hb-install-arm-kernel.xml |
15 |
hb-install-arm-medium.xml hb-install-config.xml |
16 |
hb-install-hppa-bootloader.xml |
17 |
hb-install-hppa-disk.xml hb-install-hppa-kernel.xml |
18 |
hb-install-hppa-medium.xml |
19 |
hb-install-ia64-bootloader.xml |
20 |
hb-install-ia64-disk.xml hb-install-ia64-kernel.xml |
21 |
hb-install-ia64-medium.xml |
22 |
hb-install-mips-bootloader.xml |
23 |
hb-install-mips-disk.xml hb-install-mips-kernel.xml |
24 |
hb-install-mips-medium.xml |
25 |
hb-install-mips-stage.xml |
26 |
hb-install-mips-system.xml hb-install-network.xml |
27 |
hb-install-ppc64-bootloader.xml |
28 |
hb-install-ppc64-disk.xml |
29 |
hb-install-ppc64-kernel.xml |
30 |
hb-install-ppc64-medium.xml |
31 |
hb-install-ppc-bootloader.xml |
32 |
hb-install-ppc-disk.xml hb-install-ppc-kernel.xml |
33 |
hb-install-ppc-medium.xml |
34 |
hb-install-sparc-bootloader.xml |
35 |
hb-install-sparc-disk.xml |
36 |
hb-install-sparc-kernel.xml |
37 |
hb-install-sparc-medium.xml hb-install-stage.xml |
38 |
hb-install-system.xml hb-install-tools.xml |
39 |
hb-install-x86+amd64-bootloader.xml |
40 |
hb-install-x86+amd64-disk.xml |
41 |
hb-install-x86+amd64-kernel.xml |
42 |
hb-install-x86+amd64-medium.xml |
43 |
Log: |
44 |
Initial draft import |
45 |
|
46 |
Revision Changes Path |
47 |
1.21 xml/htdocs/doc/en/handbook/draft/handbook-alpha.xml |
48 |
|
49 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-alpha.xml?rev=1.21&view=markup |
50 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-alpha.xml?rev=1.21&content-type=text/plain |
51 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-alpha.xml?r1=1.20&r2=1.21 |
52 |
|
53 |
|
54 |
|
55 |
|
56 |
1.32 xml/htdocs/doc/en/handbook/draft/handbook-amd64.xml |
57 |
|
58 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-amd64.xml?rev=1.32&view=markup |
59 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-amd64.xml?rev=1.32&content-type=text/plain |
60 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-amd64.xml?r1=1.31&r2=1.32 |
61 |
|
62 |
|
63 |
|
64 |
|
65 |
1.15 xml/htdocs/doc/en/handbook/draft/handbook-arm.xml |
66 |
|
67 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-arm.xml?rev=1.15&view=markup |
68 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-arm.xml?rev=1.15&content-type=text/plain |
69 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-arm.xml?r1=1.14&r2=1.15 |
70 |
|
71 |
|
72 |
|
73 |
|
74 |
1.21 xml/htdocs/doc/en/handbook/draft/handbook-hppa.xml |
75 |
|
76 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-hppa.xml?rev=1.21&view=markup |
77 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-hppa.xml?rev=1.21&content-type=text/plain |
78 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-hppa.xml?r1=1.20&r2=1.21 |
79 |
|
80 |
|
81 |
|
82 |
|
83 |
1.1 xml/htdocs/doc/en/handbook/draft/handbook-ia64.xml |
84 |
|
85 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-ia64.xml?rev=1.1&view=markup |
86 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-ia64.xml?rev=1.1&content-type=text/plain |
87 |
|
88 |
Index: handbook-ia64.xml |
89 |
=================================================================== |
90 |
<?xml version='1.0' encoding='UTF-8'?> |
91 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
92 |
|
93 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-ia64.xml,v 1.1 2007/03/14 06:24:40 nightmorph Exp $ --> |
94 |
|
95 |
<book link="/doc/en/handbook/handbook-ia64.xml"> |
96 |
<title>Gentoo Linux/IA64 Handbook</title> |
97 |
|
98 |
<values> |
99 |
<key id="arch">IA64</key> |
100 |
<key id="kernel-version">2.6.17-r5</key> |
101 |
<key id="kernel-name">kernel-2.6.17-gentoo-r5</key> |
102 |
<key id="genkernel-name">kernel-genkernel-ia64-2.6.17-gentoo-r5</key> |
103 |
<key id="genkernel-initrd">initramfs-genkernel-ia64-2.6.17-gentoo-r5</key> |
104 |
<key id="min-cd-name">install-ia64-minimal-2006.1.iso</key> |
105 |
<key id="min-cd-size">52</key> |
106 |
<key id="release-dir">releases/ia64/2006.1/</key> |
107 |
<key id="stage3">stage3-ia64-2006.1.tar.bz2</key> |
108 |
<key id="CFLAGS">-O2 -pipe</key> |
109 |
<key id="online-book">handbook-ia64.xml</key> |
110 |
</values> |
111 |
|
112 |
<author title="Author"> |
113 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
114 |
</author> |
115 |
<author title="Author"> |
116 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
117 |
</author> |
118 |
<author title="Author"> |
119 |
<mail link="uberlord@g.o">Roy Marples</mail> |
120 |
</author> |
121 |
<author title="Author"> |
122 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
123 |
</author> |
124 |
<author title="Author"> |
125 |
<mail link="chouser@g.o">Chris Houser</mail> |
126 |
</author> |
127 |
<author title="Author"> |
128 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
129 |
</author> |
130 |
<author title="Gentoo x86 Developer"> |
131 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
132 |
</author> |
133 |
<author title="Gentoo Alpha Developer"> |
134 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
135 |
</author><!-- Does not want to be listed on the rendered page |
136 |
<author title="Gentoo Developer"> |
137 |
Aron Griffis |
138 |
</author> |
139 |
--> |
140 |
<author title="Gentoo AMD64 Developer"> |
141 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
142 |
</author> |
143 |
<author title="Gentoo HPPA developer"> |
144 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
145 |
</author> |
146 |
<author title="Gentoo IA64 developer"> |
147 |
<mail link="plasmaroo@g.o">Tim Yamin</mail> |
148 |
</author> |
149 |
<author title="Gentoo PPC developer"> |
150 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
151 |
</author> |
152 |
<author title="Gentoo SPARC developer"> |
153 |
<mail link="blademan@g.o">Joe Kallar</mail> |
154 |
</author> |
155 |
<author title="Gentoo * developer"> |
156 |
<mail link="vapier@g.o">Mike Frysinger</mail> |
157 |
</author> |
158 |
<author title="Editor"> |
159 |
<mail link="zhen@g.o">John P. Davis</mail> |
160 |
</author> |
161 |
<author title="Editor">Pierre-Henri Jondot</author> |
162 |
<author title="Editor"> |
163 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
164 |
</author> |
165 |
<author title="Editor"> |
166 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
167 |
</author> |
168 |
<author title="Editor"> |
169 |
<mail link="seo@g.o">Jungmin Seo</mail> |
170 |
</author> |
171 |
<author title="Editor"> |
172 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
173 |
</author> |
174 |
<author title="Editor"> |
175 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
176 |
</author> |
177 |
<author title="Editor"> |
178 |
<mail link="peitolm@g.o">Colin Morey</mail> |
179 |
</author> |
180 |
<author title="Editor"> |
181 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
182 |
</author> |
183 |
<author title="Editor"> |
184 |
<mail link="carl@g.o">Carl Anderson</mail> |
185 |
</author> |
186 |
<author title="Editor"> |
187 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
188 |
</author> |
189 |
<author title="Editor"> |
190 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
191 |
</author> |
192 |
<author title="Editor"> |
193 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
194 |
</author> |
195 |
<author title="Editor"> |
196 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
197 |
</author> |
198 |
<author title="Editor"> |
199 |
<mail link="erwin@g.o">Erwin</mail> |
200 |
</author> |
201 |
<author title="Editor"> |
202 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
203 |
</author> |
204 |
<author title="Editor"> |
205 |
<mail link="redhatter@g.o">Stuart Longland</mail> |
206 |
</author> |
207 |
<author title="Editor"> |
208 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
209 |
</author> |
210 |
<author title="Editor"> |
211 |
<mail link="neysx@g.o">Xavier Neys</mail> |
212 |
</author> |
213 |
<author title="Reviewer"> |
214 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
215 |
</author> |
216 |
<author title="Reviewer"> |
217 |
<mail link="dberkholz@g.o">Donnie Berkholz</mail> |
218 |
</author> |
219 |
<author title="Reviewer"> |
220 |
<mail link="antifa@g.o">Ken Nowack</mail> |
221 |
</author> |
222 |
<author title="Contributor"> |
223 |
<mail link="pylon@g.o">Lars Weiler</mail> |
224 |
</author> |
225 |
|
226 |
<abstract> |
227 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
228 |
</abstract> |
229 |
|
230 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
231 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
232 |
<license/> |
233 |
|
234 |
<version>7.2</version> |
235 |
<date>2007-03-10</date> |
236 |
|
237 |
<part> |
238 |
<title>Installing Gentoo</title> |
239 |
<abstract> |
240 |
In this part you learn how to install Gentoo on your system. |
241 |
</abstract> |
242 |
|
243 |
<chapter> |
244 |
<title>About the Gentoo Linux Installation</title> |
245 |
<include href="hb-install-about.xml"/> |
246 |
</chapter> |
247 |
|
248 |
<chapter> |
249 |
<title>Choosing the Right Installation Medium</title> |
250 |
<abstract> |
251 |
You can install Gentoo in many ways. This chapter explains how to install Gentoo |
252 |
using the minimal Installation CD although installation through the Universal |
253 |
Installation CD is possible as well. |
254 |
</abstract> |
255 |
<include href="hb-install-ia64-medium.xml"/> |
256 |
</chapter> |
257 |
|
258 |
<chapter> |
259 |
<title>Configuring your Network</title> |
260 |
<include href="hb-install-network.xml"/> |
261 |
</chapter> |
262 |
|
263 |
<chapter> |
264 |
<title>Preparing the Disks</title> |
265 |
<abstract> |
266 |
To be able to install Gentoo, you must create the necessary partitions. |
267 |
This chapter describes how to partition a disk for future usage. |
268 |
</abstract> |
269 |
<include href="hb-install-ia64-disk.xml"/> |
270 |
</chapter> |
271 |
|
272 |
<chapter> |
273 |
<title>Installing the Gentoo Installation Files</title> |
274 |
<include href="hb-install-stage.xml"/> |
275 |
</chapter> |
276 |
|
277 |
<chapter> |
278 |
<title>Installing the Gentoo Base System</title> |
279 |
<include href="hb-install-system.xml"/> |
280 |
</chapter> |
281 |
|
282 |
<chapter> |
283 |
<title>Configuring the Kernel</title> |
284 |
<abstract> |
285 |
The Linux kernel is the core of every distribution. This chapter |
286 |
explains how to configure your kernel. |
287 |
</abstract> |
288 |
<include href="hb-install-ia64-kernel.xml"/> |
289 |
</chapter> |
290 |
|
291 |
<chapter> |
292 |
<title>Configuring your System</title> |
293 |
<include href="hb-install-config.xml"/> |
294 |
</chapter> |
295 |
|
296 |
<chapter> |
297 |
<title>Installing Necessary System Tools</title> |
298 |
<include href="hb-install-tools.xml"/> |
299 |
</chapter> |
300 |
|
301 |
<chapter> |
302 |
<title>Configuring the Bootloader</title> |
303 |
<abstract> |
304 |
The ia64 architecture uses the elilo bootloader. |
305 |
This chapter explains how to install and configure elilo. |
306 |
</abstract> |
307 |
<include href="hb-install-ia64-bootloader.xml"/> |
308 |
</chapter> |
309 |
|
310 |
<chapter> |
311 |
<title>Finalizing your Gentoo Installation</title> |
312 |
<include href="hb-install-finalise.xml"/> |
313 |
</chapter> |
314 |
|
315 |
<chapter> |
316 |
<title>Where to go from here?</title> |
317 |
<include href="hb-install-next.xml"/> |
318 |
</chapter> |
319 |
</part> |
320 |
|
321 |
<part> |
322 |
<title>Working with Gentoo</title> |
323 |
<abstract> |
324 |
Learn how to work with Gentoo: installing software, altering variables, changing |
325 |
Portage behaviour etc. |
326 |
</abstract> |
327 |
|
328 |
<chapter> |
329 |
<title>A Portage Introduction</title> |
330 |
<include href="hb-working-portage.xml"/> |
331 |
</chapter> |
332 |
|
333 |
<chapter> |
334 |
<title>USE flags</title> |
335 |
<include href="hb-working-use.xml"/> |
336 |
</chapter> |
337 |
|
338 |
<chapter> |
339 |
<title>Portage Features</title> |
340 |
<include href="hb-working-features.xml"/> |
341 |
</chapter> |
342 |
|
343 |
<chapter> |
344 |
<title>Initscripts</title> |
345 |
<include href="hb-working-rcscripts.xml"/> |
346 |
</chapter> |
347 |
|
348 |
<chapter> |
349 |
<title>Environment Variables</title> |
350 |
<include href="hb-working-variables.xml"/> |
351 |
</chapter> |
352 |
</part> |
353 |
|
354 |
<part> |
355 |
<title>Working with Portage</title> |
356 |
<abstract> |
357 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
358 |
Software Management Tool. |
359 |
</abstract> |
360 |
|
361 |
<chapter> |
362 |
<title>Files and Directories</title> |
363 |
<include href="hb-portage-files.xml"/> |
364 |
</chapter> |
365 |
|
366 |
<chapter> |
367 |
<title>Configuring through Variables</title> |
368 |
<include href="hb-portage-configuration.xml"/> |
369 |
</chapter> |
370 |
|
371 |
<chapter> |
372 |
<title>Mixing Software Branches</title> |
373 |
<include href="hb-portage-branches.xml"/> |
374 |
</chapter> |
375 |
|
376 |
<chapter> |
377 |
<title>Additional Portage Tools</title> |
378 |
<include href="hb-portage-tools.xml"/> |
379 |
</chapter> |
380 |
|
381 |
<chapter> |
382 |
<title>Diverting from the Official Tree</title> |
383 |
<include href="hb-portage-diverttree.xml"/> |
384 |
</chapter> |
385 |
</part> |
386 |
|
387 |
<part> |
388 |
<title>Gentoo Network Configuration</title> |
389 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
390 |
|
391 |
<chapter> |
392 |
<title>Getting Started</title> |
393 |
<include href="hb-net-start.xml"/> |
394 |
</chapter> |
395 |
|
396 |
<chapter> |
397 |
<title>Advanced Configuration</title> |
398 |
<include href="hb-net-advanced.xml"/> |
399 |
</chapter> |
400 |
|
401 |
<chapter> |
402 |
<title>Modular Networking</title> |
403 |
<include href="hb-net-modules.xml"/> |
404 |
</chapter> |
405 |
|
406 |
<chapter> |
407 |
<title>Wireless Networking</title> |
408 |
<include href="hb-net-wireless.xml"/> |
409 |
</chapter> |
410 |
|
411 |
<chapter> |
412 |
<title>Adding Functionality</title> |
413 |
<include href="hb-net-functions.xml"/> |
414 |
</chapter> |
415 |
|
416 |
<chapter> |
417 |
<title>Network Management</title> |
418 |
<include href="hb-net-management.xml"/> |
419 |
</chapter> |
420 |
</part> |
421 |
|
422 |
</book> |
423 |
|
424 |
|
425 |
|
426 |
1.23 xml/htdocs/doc/en/handbook/draft/handbook-mips.xml |
427 |
|
428 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-mips.xml?rev=1.23&view=markup |
429 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-mips.xml?rev=1.23&content-type=text/plain |
430 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-mips.xml?r1=1.22&r2=1.23 |
431 |
|
432 |
|
433 |
|
434 |
|
435 |
1.17 xml/htdocs/doc/en/handbook/draft/handbook-ppc64.xml |
436 |
|
437 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-ppc64.xml?rev=1.17&view=markup |
438 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-ppc64.xml?rev=1.17&content-type=text/plain |
439 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-ppc64.xml?r1=1.16&r2=1.17 |
440 |
|
441 |
|
442 |
|
443 |
|
444 |
1.36 xml/htdocs/doc/en/handbook/draft/handbook-ppc.xml |
445 |
|
446 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-ppc.xml?rev=1.36&view=markup |
447 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-ppc.xml?rev=1.36&content-type=text/plain |
448 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-ppc.xml?r1=1.35&r2=1.36 |
449 |
|
450 |
|
451 |
|
452 |
|
453 |
1.29 xml/htdocs/doc/en/handbook/draft/handbook-sparc.xml |
454 |
|
455 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-sparc.xml?rev=1.29&view=markup |
456 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-sparc.xml?rev=1.29&content-type=text/plain |
457 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-sparc.xml?r1=1.28&r2=1.29 |
458 |
|
459 |
|
460 |
|
461 |
|
462 |
1.53 xml/htdocs/doc/en/handbook/draft/handbook-x86.xml |
463 |
|
464 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-x86.xml?rev=1.53&view=markup |
465 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-x86.xml?rev=1.53&content-type=text/plain |
466 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/handbook-x86.xml?r1=1.52&r2=1.53 |
467 |
|
468 |
|
469 |
|
470 |
|
471 |
1.32 xml/htdocs/doc/en/handbook/draft/hb-install-about.xml |
472 |
|
473 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-about.xml?rev=1.32&view=markup |
474 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-about.xml?rev=1.32&content-type=text/plain |
475 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-about.xml?r1=1.31&r2=1.32 |
476 |
|
477 |
|
478 |
|
479 |
|
480 |
1.14 xml/htdocs/doc/en/handbook/draft/hb-install-alpha-bootloader.xml |
481 |
|
482 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-bootloader.xml?rev=1.14&view=markup |
483 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-bootloader.xml?rev=1.14&content-type=text/plain |
484 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-bootloader.xml?r1=1.13&r2=1.14 |
485 |
|
486 |
|
487 |
|
488 |
|
489 |
1.13 xml/htdocs/doc/en/handbook/draft/hb-install-alpha-disk.xml |
490 |
|
491 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-disk.xml?rev=1.13&view=markup |
492 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-disk.xml?rev=1.13&content-type=text/plain |
493 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-disk.xml?r1=1.12&r2=1.13 |
494 |
|
495 |
|
496 |
|
497 |
|
498 |
1.13 xml/htdocs/doc/en/handbook/draft/hb-install-alpha-kernel.xml |
499 |
|
500 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-kernel.xml?rev=1.13&view=markup |
501 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-kernel.xml?rev=1.13&content-type=text/plain |
502 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-kernel.xml?r1=1.12&r2=1.13 |
503 |
|
504 |
|
505 |
|
506 |
|
507 |
1.19 xml/htdocs/doc/en/handbook/draft/hb-install-alpha-medium.xml |
508 |
|
509 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-medium.xml?rev=1.19&view=markup |
510 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-medium.xml?rev=1.19&content-type=text/plain |
511 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-medium.xml?r1=1.18&r2=1.19 |
512 |
|
513 |
|
514 |
|
515 |
|
516 |
1.1 xml/htdocs/doc/en/handbook/draft/hb-install-arm-bootloader.xml |
517 |
|
518 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-bootloader.xml?rev=1.1&view=markup |
519 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-bootloader.xml?rev=1.1&content-type=text/plain |
520 |
|
521 |
Index: hb-install-arm-bootloader.xml |
522 |
=================================================================== |
523 |
<?xml version='1.0' encoding='UTF-8'?> |
524 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
525 |
|
526 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
527 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
528 |
|
529 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-bootloader.xml,v 1.1 2007/03/14 06:24:40 nightmorph Exp $ --> |
530 |
|
531 |
<sections> |
532 |
|
533 |
<version>7.1</version> |
534 |
<date>2006-08-30</date> |
535 |
|
536 |
<section> |
537 |
<title>Making your Choice</title> |
538 |
<subsection> |
539 |
<title>Introduction</title> |
540 |
<body> |
541 |
|
542 |
<p> |
543 |
Now that your kernel is configured and compiled and the necessary system |
544 |
configuration files are filled in correctly, it is time to install a |
545 |
program that will fire up your kernel when you start the system. Such a |
546 |
program is called a <e>bootloader</e>. |
547 |
</p> |
548 |
|
549 |
<p> |
550 |
Several bootloaders exist for Linux/ARM. You must choose one of the supported |
551 |
bootloaders, not all. Depending on the machine, you may have no choice at all! |
552 |
</p> |
553 |
|
554 |
<table> |
555 |
<tr> |
556 |
<th>Machine</th> |
557 |
<th>Supported Bootloaders</th> |
558 |
</tr> |
559 |
<tr> |
560 |
<ti><uri link="http://www.netwinder.org/about.html">NetWinder</uri></ti> |
561 |
<ti><uri link="#nettrom">NeTTrom</uri></ti> |
562 |
</tr> |
563 |
<tr> |
564 |
<ti><uri link="http://en.wikipedia.org/wiki/NSLU2">NSLU2 (aka SLUG)</uri></ti> |
565 |
<ti><uri link="#redboot">RedBoot</uri></ti> |
566 |
</tr> |
567 |
<tr> |
568 |
<ti><uri link="http://www.giantshoulderinc.com/hardware.html">Loft</uri></ti> |
569 |
<ti><uri link="#redboot">RedBoot</uri></ti> |
570 |
</tr> |
571 |
</table> |
572 |
|
573 |
</body> |
574 |
</subsection> |
575 |
</section> |
576 |
<section id="nettrom"> |
577 |
<title>NeTTrom</title> |
578 |
<subsection> |
579 |
<title>Upgrading NeTTrom</title> |
580 |
<body> |
581 |
|
582 |
<p> |
583 |
The NeTTrom bootloader is a specialized firmware developed specifically for the |
584 |
NetWinder machines. No other board uses this and due to its history, the source |
585 |
code is no longer available. However, there are firmware images of the last |
586 |
release still floating around, so the first thing you want to do is update to |
587 |
the last release of 2.3.3. This section is meant as a quickstart not as a |
588 |
replacement for the full <uri |
589 |
link="http://www.netwinder.org/howto/Firmware-HOWTO-3.html">Firmware Upgrade |
590 |
HOWTO</uri>. |
591 |
</p> |
592 |
|
593 |
<p> |
594 |
In order to flash your firmware, you need the latest release, the flashing |
595 |
utilities, and proper support in your kernel. The NetWinder flash driver is |
596 |
called <c>NetWinder flash support</c> and it is under <c>Character devices</c> |
597 |
in the kernel. |
598 |
</p> |
599 |
|
600 |
<pre caption="Install NeTTrom and NetWinder utilities"> |
601 |
# <i>emerge sys-boot/nettrom sys-block/nwutil</i> |
602 |
</pre> |
603 |
|
604 |
<warn> |
605 |
If the flashing of your firmware goes wrong, then you will be unable to recover |
606 |
via software means. Make sure you've taken all precautions against power |
607 |
failure and you read the flashwrite(8) man page. |
608 |
</warn> |
609 |
|
610 |
<p> |
611 |
Now that you have the latest firmware, you've installed the flash utilities, |
612 |
your kernel has flash write support, and you've read the flashwrite(8) man |
613 |
page, let's flash that sucker! |
614 |
</p> |
615 |
|
616 |
<pre caption="Flashing the NetWinder firmware"> |
617 |
<comment>First back up your existing firmware</comment> |
618 |
# <i>dd if=/dev/nwflash of=/boot/nettrom.old bs=1</i> |
619 |
|
620 |
<comment>Then write the new firmware</comment> |
621 |
# <i>flashwrite /boot/nettrom</i> |
622 |
|
623 |
<comment>Finally verify that the write worked (replace BYTESIZE with the actual byte size of nettrom)</comment> |
624 |
# <i>dd if=/dev/nwflash of=/boot/nettrom.new bs=1 count=BYTESIZE</i> |
625 |
# <i>cmp /boot/nettrom /boot/nettrom.new</i> |
626 |
</pre> |
627 |
|
628 |
<p> |
629 |
If all goes well, you should be able to reboot and not be left with a brick. |
630 |
So lets move on to actually booting a kernel. |
631 |
</p> |
632 |
|
633 |
</body> |
634 |
</subsection> |
635 |
<subsection> |
636 |
<title>Using NeTTrom</title> |
637 |
<body> |
638 |
|
639 |
<p> |
640 |
NeTTrom can boot a kernel many different ways so we will go over the two most |
641 |
common: embedded in the flash and loading off the ext2 boot partition. |
642 |
</p> |
643 |
|
644 |
<p> |
645 |
Embedding the kernel into flash is pretty easy with the nwlilo utility. Simply |
646 |
specify the path to the kernel you wish to embed as well as the kernel |
647 |
commandline (note that the root= value is important), and you're done! |
648 |
</p> |
649 |
|
650 |
<pre caption="Installing the kernel into flash"> |
651 |
# <i>nwlilo /boot/zImage "root=/dev/hda2 video=cyber2000fb"</i> |
652 |
</pre> |
653 |
|
654 |
<p> |
655 |
The other method is copying the vmlinux ELF to your ext2 boot partition and |
656 |
configuring NeTTrom to load that. Once you've copied your kernel over, reboot |
657 |
the machine as the only way to configure NeTTrom is from inside NeTTrom itself. |
658 |
Halt the autoboot process by pressing <c>*</c> twice followed by the return |
659 |
key. In the example below, we will assume your ext2 boot partition is at |
660 |
<path>/dev/hda1</path> while your root partition is at <path>/dev/hda3</path>. |
661 |
</p> |
662 |
|
663 |
<pre caption="Configuring NeTTrom"> |
664 |
NeTTrom> <i>load-defaults</i> |
665 |
NeTTrom> <i>setenv kernconfig fs</i> |
666 |
NeTTrom> <i>setenv kerndev /dev/hda1</i> |
667 |
NeTTrom> <i>setenv rootdev /dev/hda3</i> |
668 |
NeTTrom> <i>setenv kernfile /boot/vmlinux</i> |
669 |
NeTTrom> <i>setenv cmdappend [custom kernel cmdline settings]</i> |
670 |
NeTTrom> <i>save-all</i> |
671 |
NeTTrom> <i>boot</i> |
672 |
</pre> |
673 |
|
674 |
<p> |
675 |
It isn't uncommon for NetWinders to have broken DMA hardware, so if your disks |
676 |
are giving you troubles when DMA is enabled, simply add <c>ide=nodma</c> to the |
677 |
<c>cmdappend</c> line above. |
678 |
</p> |
679 |
|
680 |
<p> |
681 |
For a full NeTTrom command guide/reference, please see the <uri |
682 |
link="http://www.netwinder.org/howto/Firmware-HOWTO.html">NetWinder |
683 |
Firmware-HOWTO</uri>. |
684 |
</p> |
685 |
|
686 |
<p> |
687 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
688 |
</p> |
689 |
|
690 |
</body> |
691 |
</subsection> |
692 |
</section> |
693 |
<section id="redboot"> |
694 |
<title>RedBoot</title> |
695 |
<subsection> |
696 |
<title>Upgrading RedBoot</title> |
697 |
<body> |
698 |
|
699 |
<p> |
700 |
The <uri link="http://www.cygwin.com/redboot/">RedBoot</uri> firmware tends to |
701 |
be pretty popular due to its ease of use. We won't go over the process of |
702 |
updating your firmware as there's just too many ways you could get it wrong :). |
703 |
If you really want to update, please visit the <uri |
704 |
link="http://www.cygwin.com/redboot/">RedBoot homepage</uri>. |
705 |
</p> |
706 |
|
707 |
<p> |
708 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
709 |
</p> |
710 |
|
711 |
</body> |
712 |
</subsection> |
713 |
<!-- TODO: write this |
714 |
<subsection> |
715 |
<title>Using RedBoot</title> |
716 |
<body> |
717 |
|
718 |
</body> |
719 |
</subsection> |
720 |
--> |
721 |
</section> |
722 |
<section id="uboot"> |
723 |
<title>Das U-Boot</title> |
724 |
<subsection> |
725 |
<title>Upgrading Das U-Boot</title> |
726 |
<body> |
727 |
|
728 |
<p> |
729 |
<uri link="http://u-boot.sourceforge.net/">Das U-Boot</uri> tends to its power |
730 |
and portability. We won't go over the process of updating your version as |
731 |
there's just too many ways you could get it wrong :). If you really want to |
732 |
update, please visit the <uri link="http://u-boot.sourceforge.net/">U-Boot |
733 |
homepage</uri>. |
734 |
</p> |
735 |
|
736 |
<p> |
737 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
738 |
</p> |
739 |
|
740 |
</body> |
741 |
</subsection> |
742 |
<!-- TODO: write this |
743 |
<subsection> |
744 |
<title>Using Das U-Boot</title> |
745 |
<body> |
746 |
|
747 |
</body> |
748 |
</subsection> |
749 |
--> |
750 |
</section> |
751 |
<section id="reboot"> |
752 |
<title>Rebooting the System</title> |
753 |
<subsection> |
754 |
<body> |
755 |
|
756 |
<p> |
757 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
758 |
that one magical command you have been waiting for: <c>reboot</c>. |
759 |
</p> |
760 |
|
761 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
762 |
# <i>exit</i> |
763 |
cdimage ~# <i>cd</i> |
764 |
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
765 |
cdimage ~# <i>reboot</i> |
766 |
</pre> |
767 |
|
768 |
<p> |
769 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
770 |
booted again instead of your new Gentoo system. |
771 |
</p> |
772 |
|
773 |
<p> |
774 |
Once rebooted in your Gentoo installation, finish up with <uri |
775 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
776 |
</p> |
777 |
|
778 |
</body> |
779 |
</subsection> |
780 |
</section> |
781 |
</sections> |
782 |
|
783 |
|
784 |
|
785 |
1.1 xml/htdocs/doc/en/handbook/draft/hb-install-arm-disk.xml |
786 |
|
787 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-disk.xml?rev=1.1&view=markup |
788 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-disk.xml?rev=1.1&content-type=text/plain |
789 |
|
790 |
Index: hb-install-arm-disk.xml |
791 |
=================================================================== |
792 |
<?xml version='1.0' encoding='UTF-8'?> |
793 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
794 |
|
795 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
796 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
797 |
|
798 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-disk.xml,v 1.1 2007/03/14 06:24:40 nightmorph Exp $ --> |
799 |
|
800 |
<sections> |
801 |
|
802 |
<version>4.2</version> |
803 |
<date>2007-02-16</date> |
804 |
|
805 |
<!-- TODO: Add section about MTD and such --> |
806 |
|
807 |
<section> |
808 |
<title>Introduction to Block Devices</title> |
809 |
<subsection> |
810 |
<title>Block Devices</title> |
811 |
<body> |
812 |
|
813 |
<p> |
814 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
815 |
and Linux in general, including Linux filesystems, partitions and block devices. |
816 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
817 |
you'll be guided through the process of setting up partitions and filesystems |
818 |
for your Gentoo Linux installation. |
819 |
</p> |
820 |
|
821 |
<p> |
822 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
823 |
probably the one that represents the first IDE drive in a Linux system, namely |
824 |
<path>/dev/hda</path>. If your system uses SCSI or SATA drives, then your |
825 |
first hard drive would be <path>/dev/sda</path>. |
826 |
</p> |
827 |
|
828 |
<p> |
829 |
The block devices above represent an abstract interface to the disk. User |
830 |
programs can use these block devices to interact with your disk without worrying |
831 |
about whether your drives are IDE, SCSI or something else. The program can |
832 |
simply address the storage on the disk as a bunch of contiguous, |
833 |
randomly-accessible 512-byte blocks. |
834 |
</p> |
835 |
|
836 |
</body> |
837 |
</subsection> |
838 |
<subsection> |
839 |
<title>Partitions</title> |
840 |
<body> |
841 |
|
842 |
<p> |
843 |
Although it is theoretically possible to use a full disk to house your Linux |
844 |
system, this is almost never done in practice. Instead, full disk block devices |
845 |
are split up in smaller, more manageable block devices. On <keyval id="arch"/> |
846 |
systems, these are called <e>partitions</e>. |
847 |
</p> |
848 |
|
849 |
<p> |
850 |
Partitions are divided in three types: |
851 |
<e>primary</e>, <e>extended</e> and <e>logical</e>. |
852 |
</p> |
853 |
|
854 |
<p> |
855 |
A <e>primary</e> partition is a partition which has its information stored in |
856 |
the MBR (master boot record). As an MBR is very small (512 bytes) only four |
857 |
primary partitions can be defined (for instance, <path>/dev/hda1</path> to |
858 |
<path>/dev/hda4</path>). |
859 |
</p> |
860 |
|
861 |
<p> |
862 |
An <e>extended</e> partition is a special primary partition (meaning the |
863 |
extended partition must be one of the four possible primary partitions) which |
864 |
contains more partitions. Such a partition didn't exist originally, but as |
865 |
four partitions were too few, it was brought to life to extend the formatting |
866 |
scheme without losing backward compatibility. |
867 |
</p> |
868 |
|
869 |
<p> |
870 |
A <e>logical</e> partition is a partition inside the extended partition. Their |
871 |
definitions aren't placed inside the MBR, but are declared inside the extended |
872 |
partition. |
873 |
</p> |
874 |
|
875 |
</body> |
876 |
</subsection> |
877 |
</section> |
878 |
<section> |
879 |
<title>Designing a Partitioning Scheme</title> |
880 |
<subsection> |
881 |
<title>Default Partitioning Scheme</title> |
882 |
<body> |
883 |
|
884 |
<warn> |
885 |
The NetWinder firmware, NeTTrom, can only read ext2 partitions realiably so you |
886 |
must have a separate ext2 boot partition. |
887 |
</warn> |
888 |
|
889 |
<p> |
890 |
If you are not interested in drawing up a partitioning scheme for your system, |
891 |
you can use the partitioning scheme we use throughout this book: |
892 |
</p> |
893 |
|
894 |
<table> |
895 |
<tr> |
896 |
<th>Partition</th> |
897 |
<th>Filesystem</th> |
898 |
<th>Size</th> |
899 |
<th>Description</th> |
900 |
</tr> |
901 |
<tr> |
902 |
<ti><path>/dev/hda1</path></ti> |
903 |
<ti>ext2</ti> |
904 |
<ti>32M</ti> |
905 |
<ti>Boot partition</ti> |
906 |
</tr> |
907 |
<tr> |
908 |
<ti><path>/dev/hda2</path></ti> |
909 |
<ti>(swap)</ti> |
910 |
<ti>512M</ti> |
911 |
<ti>Swap partition</ti> |
912 |
</tr> |
913 |
<tr> |
914 |
<ti><path>/dev/hda3</path></ti> |
915 |
<ti>ext3</ti> |
916 |
<ti>Rest of the disk</ti> |
917 |
<ti>Root partition</ti> |
918 |
</tr> |
919 |
</table> |
920 |
|
921 |
<p> |
922 |
If you are interested in knowing how big a partition should be, or even how |
923 |
many partitions you need, read on. Otherwise continue now with partitioning |
924 |
your disk by reading <uri link="#fdisk">Using fdisk to Partition your |
925 |
Disk</uri>. |
926 |
</p> |
927 |
|
928 |
</body> |
929 |
</subsection> |
930 |
<subsection> |
931 |
<title>How Many and How Big?</title> |
932 |
<body> |
933 |
|
934 |
<p> |
935 |
The number of partitions is highly dependent on your environment. For instance, |
936 |
if you have lots of users, you will most likely want to have your |
937 |
<path>/home</path> separate as it increases security and makes backups easier. |
938 |
If you are installing Gentoo to perform as a mailserver, your |
939 |
<path>/var</path> should be separate as all mails are stored inside |
940 |
<path>/var</path>. A good choice of filesystem will then maximise your |
941 |
performance. Gameservers will have a separate <path>/opt</path> as most gaming |
942 |
servers are installed there. The reason is similar for <path>/home</path>: |
943 |
security and backups. You will definitely want to keep <path>/usr</path> big: |
944 |
not only will it contain the majority of applications, the Portage tree alone |
945 |
takes around 500 Mbyte excluding the various sources that are stored in it. |
946 |
</p> |
947 |
|
948 |
<p> |
949 |
As you can see, it very much depends on what you want to achieve. Separate |
950 |
partitions or volumes have the following advantages: |
951 |
</p> |
952 |
|
953 |
<ul> |
954 |
<li> |
955 |
You can choose the best performing filesystem for each partition or volume |
956 |
</li> |
957 |
<li> |
958 |
Your entire system cannot run out of free space if one defunct tool is |
959 |
continuously writing files to a partition or volume |
960 |
</li> |
961 |
<li> |
962 |
If necessary, file system checks are reduced in time, as multiple checks can |
963 |
be done in parallel (although this advantage is more with multiple disks than |
964 |
it is with multiple partitions) |
965 |
</li> |
966 |
<li> |
967 |
Security can be enhanced by mounting some partitions or volumes read-only, |
968 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
969 |
</li> |
970 |
</ul> |
971 |
|
972 |
<p> |
973 |
However, multiple partitions have one big disadvantage: if not configured |
974 |
properly, you might result in having a system with lots of free space on one |
975 |
partition and none on another. There is also a 15-partition limit for SCSI and |
976 |
SATA. |
977 |
</p> |
978 |
|
979 |
<p> |
980 |
As an example partitioning, we show you one for a 20GB disk, used as a |
981 |
demonstration laptop (containing webserver, mailserver, gnome, ...): |
982 |
</p> |
983 |
|
984 |
<pre caption="Filesystem usage example"> |
985 |
$ <i>df -h</i> |
986 |
Filesystem Type Size Used Avail Use% Mounted on |
987 |
/dev/hda5 ext3 509M 132M 351M 28% / |
988 |
/dev/hda2 ext3 5.0G 3.0G 1.8G 63% /home |
989 |
/dev/hda7 ext3 7.9G 6.2G 1.3G 83% /usr |
990 |
/dev/hda8 ext3 1011M 483M 477M 51% /opt |
991 |
/dev/hda9 ext3 2.0G 607M 1.3G 32% /var |
992 |
/dev/hda1 ext2 51M 17M 31M 36% /boot |
993 |
/dev/hda6 swap 516M 12M 504M 2% <not mounted> |
994 |
<comment>(Unpartitioned space for future usage: 2 GB)</comment> |
995 |
</pre> |
996 |
|
997 |
<p> |
998 |
<path>/usr</path> is rather full (83% used) here, but once |
999 |
all software is installed, <path>/usr</path> doesn't tend to grow that much. |
1000 |
Although allocating a few gigabytes of disk space for <path>/var</path> may |
1001 |
seem excessive, remember that Portage uses this partition by default for |
1002 |
compiling packages. If you want to keep <path>/var</path> at a more reasonable |
1003 |
size, such as 1GB, you will need to alter your <c>PORTAGE_TMPDIR</c> variable |
1004 |
in <path>/etc/make.conf</path> to point to the partition with enough free space |
1005 |
for compiling extremely large packages such as OpenOffice. |
1006 |
</p> |
1007 |
|
1008 |
</body> |
1009 |
</subsection> |
1010 |
</section> |
1011 |
<section id="fdisk"> |
1012 |
<title>Using fdisk to Partition your Disk</title> |
1013 |
<subsection> |
1014 |
<body> |
1015 |
|
1016 |
<p> |
1017 |
The following parts explain how to create the example partition layout |
1018 |
described previously, namely: |
1019 |
</p> |
1020 |
|
1021 |
<table> |
1022 |
<tr> |
1023 |
<th>Partition</th> |
1024 |
<th>Description</th> |
1025 |
</tr> |
1026 |
<tr> |
1027 |
<ti><path>/dev/hda1</path></ti> |
1028 |
<ti>Boot partition</ti> |
1029 |
</tr> |
1030 |
<tr> |
1031 |
<ti><path>/dev/hda2</path></ti> |
1032 |
<ti>Swap partition</ti> |
1033 |
</tr> |
1034 |
<tr> |
1035 |
<ti><path>/dev/hda3</path></ti> |
1036 |
<ti>Root partition</ti> |
1037 |
</tr> |
1038 |
</table> |
1039 |
|
1040 |
<p> |
1041 |
Change your partition layout according to your own preference. |
1042 |
</p> |
1043 |
|
1044 |
</body> |
1045 |
</subsection> |
1046 |
<subsection> |
1047 |
<title>Viewing the Current Partition Layout</title> |
1048 |
<body> |
1049 |
|
1050 |
<p> |
1051 |
<c>fdisk</c> is a popular and powerful tool to split your disk into partitions. |
1052 |
Fire up <c>fdisk</c> on your disk (in our example, we use |
1053 |
<path>/dev/hda</path>): |
1054 |
</p> |
1055 |
|
1056 |
<pre caption="Starting fdisk"> |
1057 |
# <i>fdisk /dev/hda</i> |
1058 |
</pre> |
1059 |
|
1060 |
<p> |
1061 |
Once in <c>fdisk</c>, you'll be greeted with a prompt that looks like this: |
1062 |
</p> |
1063 |
|
1064 |
<pre caption="fdisk prompt"> |
1065 |
Command (m for help): |
1066 |
</pre> |
1067 |
|
1068 |
<p> |
1069 |
Type <c>p</c> to display your disk's current partition configuration: |
1070 |
</p> |
1071 |
|
1072 |
<pre caption="An example partition configuration"> |
1073 |
Command (m for help): <i>p</i> |
1074 |
|
1075 |
Disk /dev/hda: 240 heads, 63 sectors, 2184 cylinders |
1076 |
Units = cylinders of 15120 * 512 bytes |
1077 |
|
1078 |
Device Boot Start End Blocks Id System |
1079 |
/dev/hda1 1 14 105808+ 83 Linux |
1080 |
/dev/hda2 15 49 264600 82 Linux swap |
1081 |
/dev/hda3 50 70 158760 83 Linux |
1082 |
/dev/hda4 71 2184 15981840 5 Extended |
1083 |
/dev/hda5 71 209 1050808+ 83 Linux |
1084 |
/dev/hda6 210 348 1050808+ 83 Linux |
1085 |
/dev/hda7 349 626 2101648+ 83 Linux |
1086 |
/dev/hda8 627 904 2101648+ 83 Linux |
1087 |
/dev/hda9 905 2184 9676768+ 83 Linux |
1088 |
|
1089 |
Command (m for help): |
1090 |
</pre> |
1091 |
|
1092 |
<p> |
1093 |
This particular disk is configured to house seven Linux filesystems (each with |
1094 |
a corresponding partition listed as "Linux") as well as a swap partition |
1095 |
(listed as "Linux swap"). |
1096 |
</p> |
1097 |
|
1098 |
</body> |
1099 |
</subsection> |
1100 |
<subsection> |
1101 |
<title>Removing all Partitions</title> |
1102 |
<body> |
1103 |
|
1104 |
<p> |
1105 |
We will first remove all existing partitions from the disk. Type <c>d</c> to |
1106 |
delete a partition. For instance, to delete an existing <path>/dev/hda1</path>: |
1107 |
</p> |
1108 |
|
1109 |
<pre caption="Deleting a partition"> |
1110 |
Command (m for help): <i>d</i> |
1111 |
Partition number (1-4): <i>1</i> |
1112 |
</pre> |
1113 |
|
1114 |
<p> |
1115 |
The partition has been scheduled for deletion. It will no longer show up if you |
1116 |
type <c>p</c>, but it will not be erased until your changes have been saved. If |
1117 |
you made a mistake and want to abort without saving your changes, type <c>q</c> |
1118 |
immediately and hit enter and your partition will not be deleted. |
1119 |
</p> |
1120 |
|
1121 |
<p> |
1122 |
Now, assuming that you do indeed want to wipe out all the partitions on your |
1123 |
system, repeatedly type <c>p</c> to print out a partition listing and then type |
1124 |
<c>d</c> and the number of the partition to delete it. Eventually, you'll end |
1125 |
up with a partition table with nothing in it: |
1126 |
</p> |
1127 |
|
1128 |
<pre caption="An empty partition table"> |
1129 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
1130 |
240 heads, 63 sectors/track, 3876 cylinders |
1131 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
1132 |
|
1133 |
Device Boot Start End Blocks Id System |
1134 |
|
1135 |
Command (m for help): |
1136 |
</pre> |
1137 |
|
1138 |
<p> |
1139 |
Now that the in-memory partition table is empty, we're ready to create the |
1140 |
partitions. We will use a default partitioning scheme as discussed previously. |
1141 |
Of course, don't follow these instructions to the letter if you don't want the |
1142 |
same partitioning scheme! |
1143 |
</p> |
1144 |
|
1145 |
</body> |
1146 |
</subsection> |
1147 |
<subsection> |
1148 |
<title>Creating the Boot Partition</title> |
1149 |
<body> |
1150 |
|
1151 |
<p> |
1152 |
We first create a small boot partition. Type <c>n</c> to create a new partition, |
1153 |
then <c>p</c> to select a primary partition, followed by <c>1</c> to select the |
1154 |
first primary partition. When prompted for the first cylinder, hit enter. When |
1155 |
prompted for the last cylinder, type <c>+32M</c> to create a partition 32 Mbyte |
1156 |
in size: |
1157 |
</p> |
1158 |
|
1159 |
<pre caption="Creating the boot partition"> |
1160 |
Command (m for help): <i>n</i> |
1161 |
Command action |
1162 |
e extended |
1163 |
p primary partition (1-4) |
1164 |
<i>p</i> |
1165 |
Partition number (1-4): <i>1</i> |
1166 |
First cylinder (1-3876, default 1): <comment>(Hit Enter)</comment> |
1167 |
Using default value 1 |
1168 |
Last cylinder or +size or +sizeM or +sizeK (1-3876, default 3876): <i>+32M</i> |
1169 |
</pre> |
1170 |
|
1171 |
<p> |
1172 |
Now, when you type <c>p</c>, you should see the following partition printout: |
1173 |
</p> |
1174 |
|
1175 |
<pre caption="Created boot partition"> |
1176 |
Command (m for help): <i>p</i> |
1177 |
|
1178 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
1179 |
240 heads, 63 sectors/track, 3876 cylinders |
1180 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
1181 |
|
1182 |
Device Boot Start End Blocks Id System |
1183 |
/dev/hda1 1 14 105808+ 83 Linux |
1184 |
</pre> |
1185 |
|
1186 |
<p> |
1187 |
We need to make this partition bootable. Type <c>a</c> to toggle the bootable |
1188 |
flag on a partition and select <c>1</c>. If you press <c>p</c> again, you will |
1189 |
notice that an <path>*</path> is placed in the "Boot" column. |
1190 |
</p> |
1191 |
|
1192 |
</body> |
1193 |
</subsection> |
1194 |
<subsection> |
1195 |
<title>Creating the Swap Partition</title> |
1196 |
<body> |
1197 |
|
1198 |
<p> |
1199 |
Let's now create the swap partition. To do this, type <c>n</c> to create a new |
1200 |
partition, then <c>p</c> to tell fdisk that you want a primary partition. Then |
1201 |
type <c>2</c> to create the second primary partition, <path>/dev/hda2</path> in |
1202 |
our case. When prompted for the first cylinder, hit enter. When prompted for |
1203 |
the last cylinder, type <c>+512M</c> to create a partition 512MB in size. After |
1204 |
you've done this, type <c>t</c> to set the partition type, <c>2</c> to select |
1205 |
the partition you just created and then type in <c>82</c> to set the partition |
1206 |
type to "Linux Swap". After completing these steps, typing <c>p</c> should |
1207 |
display a partition table that looks similar to this: |
1208 |
</p> |
1209 |
|
1210 |
<pre caption="Partition listing after creating a swap partition"> |
1211 |
Command (m for help): <i>p</i> |
1212 |
|
1213 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
1214 |
240 heads, 63 sectors/track, 3876 cylinders |
1215 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
1216 |
|
1217 |
Device Boot Start End Blocks Id System |
1218 |
/dev/hda1 * 1 14 105808+ 83 Linux |
1219 |
/dev/hda2 15 81 506520 82 Linux swap |
1220 |
</pre> |
1221 |
|
1222 |
</body> |
1223 |
</subsection> |
1224 |
<subsection> |
1225 |
<title>Creating the Root Partition</title> |
1226 |
<body> |
1227 |
|
1228 |
<p> |
1229 |
Finally, let's create the root partition. To do this, type <c>n</c> to create a |
1230 |
new partition, then <c>p</c> to tell fdisk that you want a primary partition. |
1231 |
Then type <c>3</c> to create the third primary partition, <path>/dev/hda3</path> |
1232 |
in our case. When prompted for the first cylinder, hit enter. When prompted for |
1233 |
the last cylinder, hit enter to create a partition that takes up the rest of the |
1234 |
remaining space on your disk. After completing these steps, typing <c>p</c> |
1235 |
should display a partition table that looks similar to this: |
1236 |
</p> |
1237 |
|
1238 |
<pre caption="Partition listing after creating the root partition"> |
1239 |
Command (m for help): <i>p</i> |
1240 |
|
1241 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
1242 |
240 heads, 63 sectors/track, 3876 cylinders |
1243 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
1244 |
|
1245 |
Device Boot Start End Blocks Id System |
1246 |
/dev/hda1 * 1 14 105808+ 83 Linux |
1247 |
/dev/hda2 15 81 506520 82 Linux swap |
1248 |
/dev/hda3 82 3876 28690200 83 Linux |
1249 |
</pre> |
1250 |
|
1251 |
</body> |
1252 |
</subsection> |
1253 |
<subsection> |
1254 |
<title>Saving the Partition Layout</title> |
1255 |
<body> |
1256 |
|
1257 |
<p> |
1258 |
To save the partition layout and exit <c>fdisk</c>, type <c>w</c>. |
1259 |
</p> |
1260 |
|
1261 |
<pre caption="Save and exit fdisk"> |
1262 |
Command (m for help): <i>w</i> |
1263 |
</pre> |
1264 |
|
1265 |
<p> |
1266 |
Now that your partitions are created, you can now continue with <uri |
1267 |
link="#filesystems">Creating Filesystems</uri>. |
1268 |
</p> |
1269 |
|
1270 |
</body> |
1271 |
</subsection> |
1272 |
</section> |
1273 |
<section id="filesystems"> |
1274 |
<title>Creating Filesystems</title> |
1275 |
<subsection> |
1276 |
<title>Introduction</title> |
1277 |
<body> |
1278 |
|
1279 |
<p> |
1280 |
Now that your partitions are created, it is time to place a filesystem on them. |
1281 |
If you don't care about what filesystem to choose and are happy with what we use |
1282 |
as default in this handbook, continue with <uri |
1283 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
1284 |
Otherwise read on to learn about the available filesystems... |
1285 |
</p> |
1286 |
|
1287 |
</body> |
1288 |
</subsection> |
1289 |
<subsection> |
1290 |
<title>Filesystems?</title> |
1291 |
<body> |
1292 |
|
1293 |
<p> |
1294 |
Several filesystems are available. Some of them are found stable on the amd64 |
1295 |
architecture, others aren't. The following filesystems are found to be stable: |
1296 |
ext2 and ext3. jfs and reiserfs may work but need more testing. If you're |
1297 |
really adventurous you can try the unsupported filesystems. |
1298 |
</p> |
1299 |
|
1300 |
<p> |
1301 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
1302 |
journaling, which means that routine ext2 filesystem checks at startup time can |
1303 |
be quite time-consuming. There is now quite a selection of newer-generation |
1304 |
journaled filesystems that can be checked for consistency very quickly and are |
1305 |
thus generally preferred over their non-journaled counterparts. Journaled |
1306 |
filesystems prevent long delays when you boot your system and your filesystem |
1307 |
happens to be in an inconsistent state. |
1308 |
</p> |
1309 |
|
1310 |
<p> |
1311 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
1312 |
journaling for fast recovery in addition to other enhanced journaling modes |
1313 |
like full data and ordered data journaling. It uses a hashed B*-tree index that |
1314 |
enables high performance in almost all situations. In short, ext3 is a very |
1315 |
good and reliable filesystem. |
1316 |
</p> |
1317 |
|
1318 |
<p> |
1319 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
1320 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
1321 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
1322 |
extremely well and has metadata journaling. ReiserFS is solid and usable as |
1323 |
both general-purpose filesystem and for extreme cases such as the creation of |
1324 |
large filesystems, very large files and directories containing tens of |
1325 |
thousands of small files. |
1326 |
</p> |
1327 |
|
1328 |
<p> |
1329 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
1330 |
feature-set and is optimized for scalability. We only recommend using this |
1331 |
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
1332 |
an uninterruptible power supply. Because XFS aggressively caches in-transit data |
1333 |
in RAM, improperly designed programs (those that don't take proper precautions |
1334 |
when writing files to disk and there are quite a few of them) can lose a good |
1335 |
deal of data if the system goes down unexpectedly. |
1336 |
</p> |
1337 |
|
1338 |
<p> |
1339 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
1340 |
become production-ready and there hasn't been a sufficient track record to |
1341 |
comment positively nor negatively on its general stability at this point. |
1342 |
</p> |
1343 |
|
1344 |
</body> |
1345 |
</subsection> |
1346 |
<subsection id="filesystems-apply"> |
1347 |
<title>Applying a Filesystem to a Partition</title> |
1348 |
<body> |
1349 |
|
1350 |
<p> |
1351 |
To create a filesystem on a partition or volume, there are tools available for |
1352 |
each possible filesystem: |
1353 |
</p> |
1354 |
|
1355 |
<table> |
1356 |
<tr> |
1357 |
<th>Filesystem</th> |
1358 |
<th>Creation Command</th> |
1359 |
</tr> |
1360 |
<tr> |
1361 |
<ti>ext2</ti> |
1362 |
<ti><c>mke2fs</c></ti> |
1363 |
</tr> |
1364 |
<tr> |
1365 |
<ti>ext3</ti> |
1366 |
<ti><c>mke2fs -j</c></ti> |
1367 |
</tr> |
1368 |
<tr> |
1369 |
<ti>reiserfs</ti> |
1370 |
<ti><c>mkreiserfs</c></ti> |
1371 |
</tr> |
1372 |
<tr> |
1373 |
<ti>xfs</ti> |
1374 |
<ti><c>mkfs.xfs</c></ti> |
1375 |
</tr> |
1376 |
<tr> |
1377 |
<ti>jfs</ti> |
1378 |
<ti><c>mkfs.jfs</c></ti> |
1379 |
</tr> |
1380 |
</table> |
1381 |
|
1382 |
<p> |
1383 |
For instance, to have the boot partition (<path>/dev/hda1</path> in our |
1384 |
example) in ext2 and the root partition (<path>/dev/hda3</path> in our example) |
1385 |
in ext3 (as in our example), you would use: |
1386 |
</p> |
1387 |
|
1388 |
<pre caption="Applying a filesystem on a partition"> |
1389 |
# <i>mke2fs /dev/hda1</i> |
1390 |
# <i>mke2fs -j -O dir_index /dev/hda3</i> |
1391 |
</pre> |
1392 |
|
1393 |
<p> |
1394 |
Now create the filesystems on your newly created partitions (or logical |
1395 |
volumes). |
1396 |
</p> |
1397 |
|
1398 |
</body> |
1399 |
</subsection> |
1400 |
<subsection> |
1401 |
<title>Activating the Swap Partition</title> |
1402 |
<body> |
1403 |
|
1404 |
<p> |
1405 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
1406 |
</p> |
1407 |
|
1408 |
<pre caption="Creating a Swap signature"> |
1409 |
# <i>mkswap /dev/hda2</i> |
1410 |
</pre> |
1411 |
|
1412 |
<p> |
1413 |
To activate the swap partition, use <c>swapon</c>: |
1414 |
</p> |
1415 |
|
1416 |
<pre caption="Activating the swap partition"> |
1417 |
# <i>swapon /dev/hda2</i> |
1418 |
</pre> |
1419 |
|
1420 |
<p> |
1421 |
Create and activate the swap with the commands mentioned above. |
1422 |
</p> |
1423 |
|
1424 |
</body> |
1425 |
</subsection> |
1426 |
</section> |
1427 |
<section> |
1428 |
<title>Mounting</title> |
1429 |
<body> |
1430 |
|
1431 |
<p> |
1432 |
Now that your partitions are initialized and are housing a filesystem, it is |
1433 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
1434 |
create the necessary mount directories for every partition you created. As an |
1435 |
example we mount the root and boot partition: |
1436 |
</p> |
1437 |
|
1438 |
<pre caption="Mounting partitions"> |
1439 |
# <i>mount /dev/hda3 /mnt/gentoo</i> |
1440 |
# <i>mkdir /mnt/gentoo/boot</i> |
1441 |
# <i>mount /dev/hda1 /mnt/gentoo/boot</i> |
1442 |
</pre> |
1443 |
|
1444 |
<note> |
1445 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
1446 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
1447 |
also holds for <path>/var/tmp</path>. |
1448 |
</note> |
1449 |
|
1450 |
<p> |
1451 |
We will also have to mount the proc filesystem (a virtual interface with the |
1452 |
kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. |
1453 |
</p> |
1454 |
|
1455 |
<p> |
1456 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
1457 |
Installation Files</uri>. |
1458 |
</p> |
1459 |
|
1460 |
</body> |
1461 |
</section> |
1462 |
</sections> |
1463 |
|
1464 |
|
1465 |
|
1466 |
1.1 xml/htdocs/doc/en/handbook/draft/hb-install-arm-kernel.xml |
1467 |
|
1468 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-kernel.xml?rev=1.1&view=markup |
1469 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-kernel.xml?rev=1.1&content-type=text/plain |
1470 |
|
1471 |
Index: hb-install-arm-kernel.xml |
1472 |
=================================================================== |
1473 |
<?xml version='1.0' encoding='UTF-8'?> |
1474 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
1475 |
|
1476 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
1477 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
1478 |
|
1479 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-kernel.xml,v 1.1 2007/03/14 06:24:40 nightmorph Exp $ --> |
1480 |
|
1481 |
<sections> |
1482 |
|
1483 |
<version>7.2</version> |
1484 |
<date>2007-02-26</date> |
1485 |
|
1486 |
<section> |
1487 |
<title>Timezone</title> |
1488 |
<body> |
1489 |
|
1490 |
<p> |
1491 |
You first need to select your timezone so that your system knows where it is |
1492 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
1493 |
it to <path>/etc/localtime</path>. Please avoid the |
1494 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
1495 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
1496 |
</p> |
1497 |
|
1498 |
<pre caption="Setting the timezone information"> |
1499 |
# <i>ls /usr/share/zoneinfo</i> |
1500 |
<comment>(Suppose you want to use GMT)</comment> |
1501 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
1502 |
</pre> |
1503 |
|
1504 |
</body> |
1505 |
</section> |
1506 |
<section> |
1507 |
<title>Installing the Sources</title> |
1508 |
<subsection> |
1509 |
<title>Choosing a Kernel</title> |
1510 |
<body> |
1511 |
|
1512 |
<p> |
1513 |
The core around which all distributions are built is the Linux kernel. It is the |
1514 |
layer between the user programs and your system hardware. Gentoo provides its |
1515 |
users several possible kernel sources. A full listing with description is |
1516 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
1517 |
Guide</uri>. |
1518 |
</p> |
1519 |
|
1520 |
<p> |
1521 |
For ARM systems, we will use <c>gentoo-sources</c> (contains additional patches |
1522 |
for performance and stability). |
1523 |
</p> |
1524 |
|
1525 |
<p> |
1526 |
Now install it using <c>emerge</c>. |
1527 |
</p> |
1528 |
|
1529 |
<pre caption="Installing a kernel source"> |
1530 |
# <i>emerge gentoo-sources</i> |
1531 |
</pre> |
1532 |
|
1533 |
<p> |
1534 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
1535 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
1536 |
kernel source points to <c>gentoo-sources-<keyval id="kernel-version"/></c>. |
1537 |
Your version may be different, so keep this in mind. |
1538 |
</p> |
1539 |
|
1540 |
<pre caption="Viewing the kernel source symlink"> |
1541 |
# <i>ls -l /usr/src/linux</i> |
1542 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-<keyval id="kernel-version"/> |
1543 |
</pre> |
1544 |
|
1545 |
</body> |
1546 |
</subsection> |
1547 |
</section> |
1548 |
<section id="manual"> |
1549 |
<title>Default: Manual Configuration</title> |
1550 |
<subsection> |
1551 |
<title>Introduction</title> |
1552 |
<body> |
1553 |
|
1554 |
<p> |
1555 |
Manually configuring a kernel is often seen as the most difficult procedure a |
1556 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
1557 |
couple of kernels you don't even remember that it was difficult ;) |
1558 |
</p> |
1559 |
|
1560 |
<p> |
1561 |
However, one thing <e>is</e> true: you must know your system when you start |
1562 |
configuring a kernel manually. Most information can be gathered by emerging |
1563 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
1564 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
1565 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
1566 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
1567 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
1568 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
1569 |
uses (it might provide you with a nice hint on what to enable). |
1570 |
</p> |
1571 |
|
1572 |
<p> |
1573 |
Now go to your kernel source directory and execute <c>make menuconfig</c>. This |
1574 |
will fire up an ncurses-based configuration menu. |
1575 |
</p> |
1576 |
|
1577 |
<pre caption="Invoking menuconfig"> |
1578 |
# <i>cd /usr/src/linux</i> |
1579 |
# <i>make menuconfig</i> |
1580 |
</pre> |
1581 |
|
1582 |
<p> |
1583 |
You will be greeted with several configuration sections. We'll first list some |
1584 |
options you must activate (otherwise Gentoo will not function, or not function |
1585 |
properly without additional tweaks). |
1586 |
</p> |
1587 |
|
1588 |
</body> |
1589 |
</subsection> |
1590 |
<subsection> |
1591 |
<title>Activating Required Options</title> |
1592 |
<body> |
1593 |
|
1594 |
<p> |
1595 |
Due to the highly specific nature of the embedded, we'll cover known |
1596 |
configurations for boards here. If your machine is not listed, then you should |
1597 |
visit the respective community website to figure out how to properly configure |
1598 |
your kernel. |
1599 |
</p> |
1600 |
|
1601 |
<p> |
1602 |
Regardless of your machine, you should make sure to activate the use of |
1603 |
development and experimental code/drivers. You need this, otherwise some very |
1604 |
important code/drivers won't show up: |
1605 |
</p> |
1606 |
|
1607 |
<pre caption="Selecting experimental code/drivers, General setup"> |
1608 |
Code maturity level options ---> |
1609 |
[*] Prompt for development and/or incomplete code/drivers |
1610 |
</pre> |
1611 |
|
1612 |
<p> |
1613 |
Please select your machine from the list below to jump to the configuration |
1614 |
section. |
1615 |
</p> |
1616 |
|
1617 |
<ul> |
1618 |
<li><uri link="#netwinder">NetWinder</uri></li> |
1619 |
</ul> |
1620 |
|
1621 |
</body> |
1622 |
</subsection> |
1623 |
</section> |
1624 |
<section id="netwinder"> |
1625 |
<title>NetWinder configuration options</title> |
1626 |
<body> |
1627 |
|
1628 |
<p> |
1629 |
Remember that EXT2 support is required for the boot partition as that is the |
1630 |
only filesystem that the bootloader can read reliably. Otherwise, the only |
1631 |
filesystem that has been tested is EXT3 but your welcome to try your luck with |
1632 |
the others ;). |
1633 |
</p> |
1634 |
|
1635 |
<pre caption="NetWinder configuration options"> |
1636 |
<comment>First generate a default config</comment> |
1637 |
# <i>make netwinder_defconfig</i> |
1638 |
|
1639 |
<comment>Required options</comment> |
1640 |
System Type ---> |
1641 |
ARM system type (FootBridge) ---> |
1642 |
(X) FootBridge |
1643 |
Footbridge Implementations ---> |
1644 |
[*] NetWinder |
1645 |
|
1646 |
Floating point emulation ---> |
1647 |
[*] NWFPE math emulation |
1648 |
|
1649 |
File systems ---> |
1650 |
[*] Second extended fs support |
1651 |
Pseudo Filesystems ---> |
1652 |
[*] /proc file system support |
1653 |
[*] Virtual memory file system support (former shm fs) |
1654 |
|
1655 |
Device Drivers ---> |
1656 |
ATA/ATAPI/MFM/RLL support ---> |
1657 |
[*] ATA/ATAPI/MFM/RLL support |
1658 |
[*] Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support |
1659 |
[*] Include IDE/ATA-2 DISK support |
1660 |
--- IDE chipset support/bugfixes |
1661 |
[*] PCI IDE chipset support |
1662 |
[*] Winbond SL82c105 support |
1663 |
[*] Generic PCI bus-master DMA support |
1664 |
[*] Use PCI DMA by default when available |
1665 |
|
1666 |
Network device support ---> |
1667 |
[*] Network device support |
1668 |
Ethernet (10 or 100Mbit) ---> |
1669 |
[*] Ethernet (10 or 100Mbit) |
1670 |
Tulip family network device support ---> |
1671 |
[*] "Tulip" family network device support |
1672 |
[*] DECchip Tulip (dc2114x) PCI support |
1673 |
[*] Use PCI shared mem for NIC registers |
1674 |
[*] Use NAPI RX polling |
1675 |
[*] EISA, VLB, PCI and on board controllers |
1676 |
[*] PCI NE2000 and clones support |
1677 |
|
1678 |
Character devices ---> |
1679 |
Serial drivers ---> |
1680 |
[*] 8250/16550 and compatible serial support |
1681 |
[*] Console on 8250/16550 and compatible serial port |
1682 |
--- Non-8250 serial port support |
1683 |
[*] DC21285 serial port support |
1684 |
[*] Console on DC21285 serial port |
1685 |
Watchdog Cards ---> |
1686 |
[*] Watchdog Timer Support |
1687 |
[*] NetWinder WB83C977 watchdog |
1688 |
[*] NetWinder thermometer support |
1689 |
[*] NetWinder Button |
1690 |
[*] Reboot Using Button |
1691 |
|
1692 |
<comment>Recommended options</comment> |
1693 |
Kernel Features ---> |
1694 |
[*] Preemptible Kernel |
1695 |
[*] Timer and CPU usage LEDs |
1696 |
[*] CPU usage LED |
1697 |
|
1698 |
File systems ---> |
1699 |
[*] Ext3 journalling file system support |
1700 |
|
1701 |
Device Drivers ---> |
1702 |
Input device support ---> |
1703 |
[*] Keyboards ---> |
1704 |
[*] AT keyboard |
1705 |
[*] Mouse ---> |
1706 |
[*] PS/2 mouse |
1707 |
|
1708 |
Graphics support ---> |
1709 |
[*] Support for frame buffer devices |
1710 |
[*] Enable firmware EDID |
1711 |
[*] CyberPro 2000/2010/5000 support |
1712 |
Logo configuration ---> |
1713 |
[*] Bootup logo |
1714 |
[*] Standard 224-color Linux logo |
1715 |
|
1716 |
Sound ---> |
1717 |
[*] Sound card support |
1718 |
Open Sound System ---> |
1719 |
[*] Open Sound System |
1720 |
[*] OSS sound modules |
1721 |
[*] Yamaha FM synthesizer (YM3812/OPL-3) support |
1722 |
[*] Netwinder WaveArtist |
1723 |
|
1724 |
<comment>You should only enable this to upgrade your flash</comment> |
1725 |
Device Drivers ---> |
1726 |
Character devices ---> |
1727 |
[*] NetWinder flash support |
1728 |
</pre> |
1729 |
|
1730 |
<p> |
1731 |
When you've finished configuring the kernel, continue with <uri |
1732 |
link="#compiling">Compiling and Installing</uri>. |
1733 |
</p> |
1734 |
|
1735 |
</body> |
1736 |
</section> |
1737 |
<section id="compiling"> |
1738 |
<title>Compiling and Installing</title> |
1739 |
<body> |
1740 |
|
1741 |
<p> |
1742 |
Now that your kernel is configured, it is time to compile and install it. Exit |
1743 |
the configuration and start the compilation process: |
1744 |
</p> |
1745 |
|
1746 |
<pre caption="Compiling the kernel"> |
1747 |
# <i>make && make modules_install</i> |
1748 |
</pre> |
1749 |
|
1750 |
<p> |
1751 |
When the kernel has finished compiling, copy the kernel image to |
1752 |
<path>/boot</path>. Use whatever name you feel is appropriate for your kernel |
1753 |
choice and remember it as you will need it later on when you configure your |
1754 |
bootloader. Remember to replace <c><keyval id="kernel-name"/></c> with the |
1755 |
name and version of your kernel. |
1756 |
</p> |
1757 |
|
1758 |
<pre caption="Installing the kernel"> |
1759 |
# <i>cp vmlinux.gz /boot/<keyval id="kernel-name"/></i> |
1760 |
</pre> |
1761 |
|
1762 |
<p> |
1763 |
Now continue with <uri link="#kernel_modules">Kernel Modules</uri>. |
1764 |
</p> |
1765 |
|
1766 |
</body> |
1767 |
</section> |
1768 |
<section id="kernel_modules"> |
1769 |
<title>Kernel Modules</title> |
1770 |
<subsection> |
1771 |
<title>Configuring the Modules</title> |
1772 |
<body> |
1773 |
|
1774 |
<p> |
1775 |
You should list the modules you want automatically loaded in |
1776 |
<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra options to |
1777 |
the modules too if you want. |
1778 |
</p> |
1779 |
|
1780 |
<p> |
1781 |
To view all available modules, run the following <c>find</c> command. Don't |
1782 |
forget to substitute <c><keyval id="kernel-version"/></c> with the version of |
1783 |
the kernel you just compiled: |
1784 |
</p> |
1785 |
|
1786 |
<pre caption="Viewing all available modules"> |
1787 |
# <i>find /lib/modules/<keyval id="kernel-version"/>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
1788 |
</pre> |
1789 |
|
1790 |
<p> |
1791 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
1792 |
<path>kernel-2.6</path> file and enter the module name in it. |
1793 |
</p> |
1794 |
|
1795 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
1796 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
1797 |
</pre> |
1798 |
|
1799 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
1800 |
3c59x |
1801 |
</pre> |
1802 |
|
1803 |
<p> |
1804 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
1805 |
your System</uri>. |
1806 |
</p> |
1807 |
|
1808 |
</body> |
1809 |
</subsection> |
1810 |
</section> |
1811 |
</sections> |
1812 |
|
1813 |
|
1814 |
|
1815 |
1.5 xml/htdocs/doc/en/handbook/draft/hb-install-arm-medium.xml |
1816 |
|
1817 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-medium.xml?rev=1.5&view=markup |
1818 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-medium.xml?rev=1.5&content-type=text/plain |
1819 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-medium.xml?r1=1.4&r2=1.5 |
1820 |
|
1821 |
|
1822 |
|
1823 |
|
1824 |
1.21 xml/htdocs/doc/en/handbook/draft/hb-install-config.xml |
1825 |
|
1826 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-config.xml?rev=1.21&view=markup |
1827 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-config.xml?rev=1.21&content-type=text/plain |
1828 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-config.xml?r1=1.20&r2=1.21 |
1829 |
|
1830 |
|
1831 |
|
1832 |
|
1833 |
1.15 xml/htdocs/doc/en/handbook/draft/hb-install-hppa-bootloader.xml |
1834 |
|
1835 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-bootloader.xml?rev=1.15&view=markup |
1836 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-bootloader.xml?rev=1.15&content-type=text/plain |
1837 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-bootloader.xml?r1=1.14&r2=1.15 |
1838 |
|
1839 |
|
1840 |
|
1841 |
|
1842 |
1.11 xml/htdocs/doc/en/handbook/draft/hb-install-hppa-disk.xml |
1843 |
|
1844 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-disk.xml?rev=1.11&view=markup |
1845 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-disk.xml?rev=1.11&content-type=text/plain |
1846 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-disk.xml?r1=1.10&r2=1.11 |
1847 |
|
1848 |
|
1849 |
|
1850 |
|
1851 |
1.18 xml/htdocs/doc/en/handbook/draft/hb-install-hppa-kernel.xml |
1852 |
|
1853 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-kernel.xml?rev=1.18&view=markup |
1854 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-kernel.xml?rev=1.18&content-type=text/plain |
1855 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-kernel.xml?r1=1.17&r2=1.18 |
1856 |
|
1857 |
|
1858 |
|
1859 |
|
1860 |
1.20 xml/htdocs/doc/en/handbook/draft/hb-install-hppa-medium.xml |
1861 |
|
1862 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-medium.xml?rev=1.20&view=markup |
1863 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-medium.xml?rev=1.20&content-type=text/plain |
1864 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-medium.xml?r1=1.19&r2=1.20 |
1865 |
|
1866 |
|
1867 |
|
1868 |
|
1869 |
1.1 xml/htdocs/doc/en/handbook/draft/hb-install-ia64-bootloader.xml |
1870 |
|
1871 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-bootloader.xml?rev=1.1&view=markup |
1872 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-bootloader.xml?rev=1.1&content-type=text/plain |
1873 |
|
1874 |
Index: hb-install-ia64-bootloader.xml |
1875 |
=================================================================== |
1876 |
<?xml version='1.0' encoding='UTF-8'?> |
1877 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
1878 |
|
1879 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
1880 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
1881 |
|
1882 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-bootloader.xml,v 1.1 2007/03/14 06:24:40 nightmorph Exp $ --> |
1883 |
|
1884 |
<sections> |
1885 |
|
1886 |
<version>7.2</version> |
1887 |
<date>2007-02-12</date> |
1888 |
|
1889 |
<section> |
1890 |
<title>Installing elilo</title> |
1891 |
<body> |
1892 |
|
1893 |
<p> |
1894 |
On the IA64 platform, the boot loader is called elilo. You may need to |
1895 |
emerge it on your machine first. |
1896 |
</p> |
1897 |
|
1898 |
<pre caption="Installing elilo"> |
1899 |
# <i>emerge elilo</i> |
1900 |
</pre> |
1901 |
|
1902 |
<p> |
1903 |
You can find the configuration file at <path>/etc/elilo.conf</path> and a |
1904 |
sample file in the typical docs dir <path>/usr/share/doc/elilo-<ver>/</path>. |
1905 |
Here is another sample configuration: |
1906 |
</p> |
1907 |
|
1908 |
<pre caption = "/etc/elilo.conf example"> |
1909 |
boot=/dev/sda1 |
1910 |
delay=30 |
1911 |
timeout=50 |
1912 |
default=Gentoo |
1913 |
append="console=ttyS0,9600" |
1914 |
prompt |
1915 |
|
1916 |
image=/vmlinuz |
1917 |
label=Gentoo |
1918 |
root=/dev/sda2 |
1919 |
read-only |
1920 |
|
1921 |
image=/vmlinuz.old |
1922 |
label=Gentoo.old |
1923 |
root=/dev/sda2 |
1924 |
read-only |
1925 |
</pre> |
1926 |
|
1927 |
<p> |
1928 |
The <c>boot</c> line tells elilo the location of the boot partition (in this |
1929 |
case, <path>/dev/sda1</path>). The <c>delay</c> line sets the number of 10th |
1930 |
of seconds before automatically booting the default when in non-interactive |
1931 |
mode. The <c>timeout</c> line is just like the delay line but for interactive |
1932 |
mode. The <c>default</c> line sets the default kernel entry (which is defined |
1933 |
below). The <c>append</c> line adds extra options to the kernel cmdline. The |
1934 |
<c>prompt</c> sets the default elilo behavior to interactive. |
1935 |
</p> |
1936 |
|
1937 |
<p> |
1938 |
The sections that start with <c>image</c> defines different bootable images. |
1939 |
Each image has a nice <c>label</c>, a <c>root</c> filesystem, and will only |
1940 |
mount the root filesystem <c>read-only</c>. |
1941 |
</p> |
1942 |
|
1943 |
<p> |
1944 |
When configuration is done, just run <c>elilo --efiboot</c>. The <c>--efiboot |
1945 |
</c> option adds a menu entry for Gentoo Linux to the EFI Boot Manager. |
1946 |
</p> |
1947 |
|
1948 |
<pre caption = "Applying the elilo configuration"> |
1949 |
# <i>elilo --efiboot</i> |
1950 |
</pre> |
1951 |
|
1952 |
<p> |
1953 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
1954 |
</p> |
1955 |
|
1956 |
</body> |
1957 |
</section> |
1958 |
<section id="reboot"> |
1959 |
<title>Rebooting the System</title> |
1960 |
<subsection> |
1961 |
<body> |
1962 |
|
1963 |
<p> |
1964 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
1965 |
that one magical command you have been waiting for: <c>reboot</c>. |
1966 |
</p> |
1967 |
|
1968 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
1969 |
# <i>exit</i> |
1970 |
cdimage ~# <i>cd</i> |
1971 |
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/sys /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
1972 |
cdimage ~# <i>reboot</i> |
1973 |
</pre> |
1974 |
|
1975 |
<p> |
1976 |
When you reboot you should see a new Gentoo Linux menu option in the |
1977 |
EFI Boot Manager which will boot Gentoo. Once rebooted in your Gentoo |
1978 |
installation, finish up with <uri link="?part=1&chap=11">Finalizing |
1979 |
your Gentoo Installation</uri>. |
1980 |
</p> |
1981 |
|
1982 |
</body> |
1983 |
</subsection> |
1984 |
</section> |
1985 |
</sections> |
1986 |
|
1987 |
|
1988 |
|
1989 |
1.1 xml/htdocs/doc/en/handbook/draft/hb-install-ia64-disk.xml |
1990 |
|
1991 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-disk.xml?rev=1.1&view=markup |
1992 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-disk.xml?rev=1.1&content-type=text/plain |
1993 |
|
1994 |
Index: hb-install-ia64-disk.xml |
1995 |
=================================================================== |
1996 |
<?xml version='1.0' encoding='UTF-8'?> |
1997 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
1998 |
|
1999 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
2000 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
2001 |
|
2002 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-disk.xml,v 1.1 2007/03/14 06:24:40 nightmorph Exp $ --> |
2003 |
|
2004 |
<sections> |
2005 |
|
2006 |
<version>2.4</version> |
2007 |
<date>2007-02-16</date> |
2008 |
|
2009 |
<section> |
2010 |
<title>Introduction to Block Devices</title> |
2011 |
<subsection> |
2012 |
<title>Block Devices</title> |
2013 |
<body> |
2014 |
|
2015 |
<p> |
2016 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
2017 |
and Linux in general, including Linux filesystems, partitions and block devices. |
2018 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
2019 |
you'll be guided through the process of setting up partitions and filesystems |
2020 |
for your Gentoo Linux installation. |
2021 |
</p> |
2022 |
|
2023 |
<p> |
2024 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
2025 |
probably the one that represents the first IDE drive in a Linux system, namely |
2026 |
<path>/dev/hda</path>. If your system uses SCSI or SATA drives, then your |
2027 |
first hard drive would be <path>/dev/sda</path>. |
2028 |
</p> |
2029 |
|
2030 |
<p> |
2031 |
The block devices above represent an abstract interface to the disk. User |
2032 |
programs can use these block devices to interact with your disk without worrying |
2033 |
about whether your drives are IDE, SCSI or something else. The program can |
2034 |
simply address the storage on the disk as a bunch of contiguous, |
2035 |
randomly-accessible 512-byte blocks. |
2036 |
</p> |
2037 |
|
2038 |
</body> |
2039 |
</subsection> |
2040 |
<subsection> |
2041 |
<title>Partitions</title> |
2042 |
<body> |
2043 |
|
2044 |
<p> |
2045 |
Although it is theoretically possible to use a full disk to house your Linux |
2046 |
system, this is almost never done in practice. Instead, full disk block devices |
2047 |
are split up in smaller, more manageable block devices. On <keyval id="arch"/> |
2048 |
systems, these are called <e>partitions</e>. |
2049 |
</p> |
2050 |
|
2051 |
<p> |
2052 |
Itanium systems use EFI, the Extensible Firmware Interface, for booting. The |
2053 |
partition table format that EFI understands is called GPT, or GUID Partition |
2054 |
Table. The partitioning program that understands GPT is called "parted", so |
2055 |
that is the tool we will use below. Additionally, EFI can only read FAT |
2056 |
filesystems, so that is the format to use for the EFI boot partition, where the |
2057 |
kernel will be installed by "elilo". |
2058 |
</p> |
2059 |
|
2060 |
</body> |
2061 |
</subsection> |
2062 |
<subsection> |
2063 |
<title>Advanced Storage</title> |
2064 |
<body> |
2065 |
|
2066 |
<p> |
2067 |
The <keyval id="arch"/> Installation CDs provide support for EVMS and LVM2. |
2068 |
EVMS and LVM2 increase the flexibility offered by your partitioning setup. |
2069 |
During the installation instructions, we will focus on "regular" partitions, |
2070 |
but it is still good to know EVMS and LVM2 are supported as well. |
2071 |
</p> |
2072 |
|
2073 |
</body> |
2074 |
</subsection> |
2075 |
</section> |
2076 |
<section> |
2077 |
<title>Designing a Partitioning Scheme</title> |
2078 |
<subsection> |
2079 |
<title>Default Partitioning Scheme</title> |
2080 |
<body> |
2081 |
|
2082 |
<p> |
2083 |
If you are not interested in drawing up a partitioning scheme for your system, |
2084 |
you can use the partitioning scheme we use throughout this book: |
2085 |
</p> |
2086 |
|
2087 |
<table> |
2088 |
<tr> |
2089 |
<th>Partition</th> |
2090 |
<th>Filesystem</th> |
2091 |
<th>Size</th> |
2092 |
<th>Description</th> |
2093 |
</tr> |
2094 |
<tr> |
2095 |
<ti><path>/dev/sda1</path></ti> |
2096 |
<ti>vfat</ti> |
2097 |
<ti>32M</ti> |
2098 |
<ti>EFI Boot partition</ti> |
2099 |
</tr> |
2100 |
<tr> |
2101 |
<ti><path>/dev/sda2</path></ti> |
2102 |
<ti>(swap)</ti> |
2103 |
<ti>512M</ti> |
2104 |
<ti>Swap partition</ti> |
2105 |
</tr> |
2106 |
<tr> |
2107 |
<ti><path>/dev/sda3</path></ti> |
2108 |
<ti>ext3</ti> |
2109 |
<ti>Rest of the disk</ti> |
2110 |
<ti>Root partition</ti> |
2111 |
</tr> |
2112 |
</table> |
2113 |
|
2114 |
<p> |
2115 |
If you are interested in knowing how big a partition should be, or even how |
2116 |
many partitions you need, read on. Otherwise continue now with partitioning |
2117 |
your disk by reading <uri link="#parted">Using parted to Partition your |
2118 |
Disk</uri>. |
2119 |
</p> |
2120 |
|
2121 |
</body> |
2122 |
</subsection> |
2123 |
<subsection> |
2124 |
<title>How Many and How Big?</title> |
2125 |
<body> |
2126 |
|
2127 |
<p> |
2128 |
The number of partitions is highly dependent on your environment. For instance, |
2129 |
if you have lots of users, you will most likely want to have your |
2130 |
<path>/home</path> separate as it increases security and makes backups easier. |
2131 |
If you are installing Gentoo to perform as a mailserver, your |
2132 |
<path>/var</path> should be separate as all mails are stored inside |
2133 |
<path>/var</path>. A good choice of filesystem will then maximise your |
2134 |
performance. Gameservers will have a separate <path>/opt</path> as most gaming |
2135 |
servers are installed there. The reason is similar for <path>/home</path>: |
2136 |
security and backups. You will definitely want to keep <path>/usr</path> big: |
2137 |
not only will it contain the majority of applications, the Portage tree alone |
2138 |
takes around 500 Mbyte excluding the various sources that are stored in it. |
2139 |
</p> |
2140 |
|
2141 |
<p> |
2142 |
As you can see, it very much depends on what you want to achieve. Separate |
2143 |
partitions or volumes have the following advantages: |
2144 |
</p> |
2145 |
|
2146 |
<ul> |
2147 |
<li> |
2148 |
You can choose the best performing filesystem for each partition or volume |
2149 |
</li> |
2150 |
<li> |
2151 |
Your entire system cannot run out of free space if one defunct tool is |
2152 |
continuously writing files to a partition or volume |
2153 |
</li> |
2154 |
<li> |
2155 |
If necessary, file system checks are reduced in time, as multiple checks can |
2156 |
be done in parallel (although this advantage is more with multiple disks than |
2157 |
it is with multiple partitions) |
2158 |
</li> |
2159 |
<li> |
2160 |
Security can be enhanced by mounting some partitions or volumes read-only, |
2161 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
2162 |
</li> |
2163 |
</ul> |
2164 |
|
2165 |
<p> |
2166 |
However, multiple partitions have one big disadvantage: if not configured |
2167 |
properly, you might result in having a system with lots of free space on one |
2168 |
partition and none on another. There is also a 15-partition limit for SCSI and |
2169 |
SATA. |
2170 |
</p> |
2171 |
|
2172 |
<p> |
2173 |
As an example partitioning, we show you one for a 20GB disk, used as a |
2174 |
demonstration laptop (containing webserver, mailserver, gnome, ...): |
2175 |
</p> |
2176 |
|
2177 |
<pre caption="Filesystem usage example"> |
2178 |
$ <i>df -h</i> |
2179 |
Filesystem Type Size Used Avail Use% Mounted on |
2180 |
/dev/hda5 ext3 509M 132M 351M 28% / |
2181 |
/dev/hda2 ext3 5.0G 3.0G 1.8G 63% /home |
2182 |
/dev/hda7 ext3 7.9G 6.2G 1.3G 83% /usr |
2183 |
/dev/hda8 ext3 1011M 483M 477M 51% /opt |
2184 |
/dev/hda9 ext3 2.0G 607M 1.3G 32% /var |
2185 |
/dev/hda1 ext2 51M 17M 31M 36% /boot |
2186 |
/dev/hda6 swap 516M 12M 504M 2% <not mounted> |
2187 |
<comment>(Unpartitioned space for future usage: 2 GB)</comment> |
2188 |
</pre> |
2189 |
|
2190 |
<p> |
2191 |
<path>/usr</path> is rather full (83% used) here, but once |
2192 |
all software is installed, <path>/usr</path> doesn't tend to grow that much. |
2193 |
Although allocating a few gigabytes of disk space for <path>/var</path> may |
2194 |
seem excessive, remember that Portage uses this partition by default for |
2195 |
compiling packages. If you want to keep <path>/var</path> at a more reasonable |
2196 |
size, such as 1GB, you will need to alter your <c>PORTAGE_TMPDIR</c> variable |
2197 |
in <path>/etc/make.conf</path> to point to the partition with enough free space |
2198 |
for compiling extremely large packages such as OpenOffice. |
2199 |
</p> |
2200 |
|
2201 |
</body> |
2202 |
</subsection> |
2203 |
</section> |
2204 |
<section id="parted"> |
2205 |
<title>Using parted to Partition your Disk</title> |
2206 |
<subsection> |
2207 |
<body> |
2208 |
|
2209 |
<p> |
2210 |
The following parts explain how to create the example partition layout |
2211 |
described previously, namely: |
2212 |
</p> |
2213 |
|
2214 |
<table> |
2215 |
<tr> |
2216 |
<th>Partition</th> |
2217 |
<th>Description</th> |
2218 |
</tr> |
2219 |
<tr> |
2220 |
<ti><path>/dev/sda1</path></ti> |
2221 |
<ti>EFI Boot partition</ti> |
2222 |
</tr> |
2223 |
<tr> |
2224 |
<ti><path>/dev/sda2</path></ti> |
2225 |
<ti>Swap partition</ti> |
2226 |
</tr> |
2227 |
<tr> |
2228 |
<ti><path>/dev/sda3</path></ti> |
2229 |
<ti>Root partition</ti> |
2230 |
</tr> |
2231 |
</table> |
2232 |
|
2233 |
<p> |
2234 |
Change your partition layout according to your own preference. |
2235 |
</p> |
2236 |
|
2237 |
</body> |
2238 |
</subsection> |
2239 |
<subsection> |
2240 |
<title>Viewing the Current Partition Layout</title> |
2241 |
<body> |
2242 |
|
2243 |
<p> |
2244 |
<c>parted</c> is the GNU partition editor. |
2245 |
Fire up <c>parted</c> on your disk (in our example, we use |
2246 |
<path>/dev/sda</path>): |
2247 |
</p> |
2248 |
|
2249 |
<pre caption="Starting parted"> |
2250 |
# <i>parted /dev/sda</i> |
2251 |
</pre> |
2252 |
|
2253 |
<p> |
2254 |
Once in <c>parted</c>, you'll be greeted with a prompt that looks like this: |
2255 |
</p> |
2256 |
|
2257 |
<pre caption="parted prompt"> |
2258 |
GNU Parted 1.6.22 |
2259 |
Copyright (C) 1998 - 2005 Free Software Foundation, Inc. |
2260 |
This program is free software, covered by the GNU General Public License. |
2261 |
|
2262 |
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without |
2263 |
even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU |
2264 |
General Public License for more details. |
2265 |
|
2266 |
Using /dev/sda |
2267 |
(parted) |
2268 |
</pre> |
2269 |
|
2270 |
<p> |
2271 |
At this point one of the available commands is <c>help</c>, which you should use |
2272 |
if you want to see the other available commands. Another command is |
2273 |
<c>print</c> which you should type next to display your disk's current partition |
2274 |
configuration: |
2275 |
</p> |
2276 |
|
2277 |
<pre caption="An example partition configuration"> |
2278 |
(parted) <i>print</i> |
2279 |
Disk geometry for /dev/sda: 0.000-34732.890 megabytes |
2280 |
Disk label type: gpt |
2281 |
Minor Start End Filesystem Name Flags |
2282 |
1 0.017 203.938 fat32 boot |
2283 |
2 203.938 4243.468 linux-swap |
2284 |
3 4243.469 34724.281 ext3 |
2285 |
</pre> |
2286 |
|
2287 |
<p> |
2288 |
This particular configuration is very similar to the one that we recommend |
2289 |
above. Note on the second line that the partition table is type is GPT. If it |
2290 |
is different, then the ia64 system will not be able to boot from this disk. |
2291 |
For the sake of this guide we'll remove the partitions and create them anew. |
2292 |
</p> |
2293 |
|
2294 |
</body> |
2295 |
</subsection> |
2296 |
<subsection> |
2297 |
<title>Removing all Partitions</title> |
2298 |
<body> |
2299 |
|
2300 |
<note> |
2301 |
Unlike fdisk and some other partitioning programs which postpone committing |
2302 |
changes until you give the write instruction, parted commands take effect |
2303 |
immediately. So once you start adding and removing partitions, you can't |
2304 |
simply quit without writing them... they've already been written. |
2305 |
</note> |
2306 |
|
2307 |
<p> |
2308 |
The easy way to remove all partitions and start fresh, which guarantees that we |
2309 |
are using the correct partition type, is to make a new partition table using the |
2310 |
<c>mklabel</c> command. After you do this, you will have an empty GPT partition |
2311 |
table. |
2312 |
</p> |
2313 |
|
2314 |
<pre caption="Creating a new partition table"> |
2315 |
(parted) <i>mklabel gpt</i> |
2316 |
(parted) <i>print</i> |
2317 |
Disk geometry for /dev/sda: 0.000-34732.890 megabytes |
2318 |
Disk label type: gpt |
2319 |
Minor Start End Filesystem Name Flags |
2320 |
</pre> |
2321 |
|
2322 |
<p> |
2323 |
Now that the partition table is empty, we're ready to create the |
2324 |
partitions. We will use a default partitioning scheme as discussed previously. |
2325 |
Of course, don't follow these instructions to the letter if you don't want the |
2326 |
same partitioning scheme! |
2327 |
</p> |
2328 |
|
2329 |
</body> |
2330 |
</subsection> |
2331 |
<subsection> |
2332 |
<title>Creating the EFI Boot Partition</title> |
2333 |
<body> |
2334 |
|
2335 |
<p> |
2336 |
We first create a small EFI boot partition. This is required to be a FAT |
2337 |
filesystem in order for the ia64 firmware to read it. Our example makes this |
2338 |
32 megabytes, which is appropriate for storing kernels and elilo configuration. |
2339 |
You can expect each ia64 kernel to be around 5 megabytes, so this configuration |
2340 |
leaves you some room to grow and experiment. |
2341 |
</p> |
2342 |
|
2343 |
<pre caption="Creating the boot partition"> |
2344 |
(parted) <i>mkpart primary fat32 0 32</i> |
2345 |
(parted) <i>print</i> |
2346 |
Disk geometry for /dev/sda: 0.000-34732.890 megabytes |
2347 |
Disk label type: gpt |
2348 |
Minor Start End Filesystem Name Flags |
2349 |
1 0.017 32.000 fat32 |
2350 |
</pre> |
2351 |
|
2352 |
</body> |
2353 |
</subsection> |
2354 |
<subsection> |
2355 |
<title>Creating the Swap Partition</title> |
2356 |
<body> |
2357 |
|
2358 |
<p> |
2359 |
Let's now create the swap partition. The classic size to make the swap |
2360 |
partition was twice the amount of RAM in the system. In modern systems with |
2361 |
lots of RAM, this is no longer necessary. For most desktop systems, a 512 |
2362 |
megabyte swap partition is sufficient. For a server, you should consider |
2363 |
something larger to reflect the anticipated needs of the server. |
2364 |
</p> |
2365 |
|
2366 |
<pre caption="Creating the swap partition"> |
2367 |
(parted) <i>mkpart primary linux-swap 32 544</i> |
2368 |
(parted) <i>print</i> |
2369 |
Disk geometry for /dev/sda: 0.000-34732.890 megabytes |
2370 |
Disk label type: gpt |
2371 |
Minor Start End Filesystem Name Flags |
2372 |
1 0.017 32.000 fat32 |
2373 |
2 32.000 544.000 |
2374 |
</pre> |
2375 |
|
2376 |
</body> |
2377 |
</subsection> |
2378 |
<subsection> |
2379 |
<title>Creating the Root Partition</title> |
2380 |
<body> |
2381 |
|
2382 |
<p> |
2383 |
Finally, let's create the root partition. Our configuration will make the root |
2384 |
partition to occupy the rest of the disk. We default to ext3, but you can use |
2385 |
ext2, jfs, reiserfs or xfs if you prefer. The actual filesystem is not created |
2386 |
in this step, but the partition table contains an indication of what kind of |
2387 |
filesystem is stored on each partition, and it's a good idea to make the table |
2388 |
match your intentions. |
2389 |
</p> |
2390 |
|
2391 |
<pre caption="Creating the root partition"> |
2392 |
(parted) <i>mkpart primary ext3 544 34732.890</i> |
2393 |
(parted) <i>print</i> |
2394 |
Disk geometry for /dev/sda: 0.000-34732.890 megabytes |
2395 |
Disk label type: gpt |
2396 |
Minor Start End Filesystem Name Flags |
2397 |
1 0.017 32.000 fat32 |
2398 |
2 32.000 544.000 |
2399 |
3 544.000 34732.874 |
2400 |
</pre> |
2401 |
|
2402 |
</body> |
2403 |
</subsection> |
2404 |
<subsection> |
2405 |
<title>Exiting parted</title> |
2406 |
<body> |
2407 |
|
2408 |
<p> |
2409 |
To quit from parted, type <c>quit</c>. There's no need to take a separate step |
2410 |
to save your partition layout since parted has been saving it all along. As you |
2411 |
leave, parted gives you reminder to update your <c>/etc/fstab</c>, which we'll |
2412 |
do later in this guide. |
2413 |
</p> |
2414 |
|
2415 |
<pre caption="Quit from parted"> |
2416 |
(parted) <i>quit</i> |
2417 |
Information: Don't forget to update /etc/fstab, if necessary. |
2418 |
</pre> |
2419 |
|
2420 |
<p> |
2421 |
Now that your partitions are created, you can now continue with <uri |
2422 |
link="#filesystems">Creating Filesystems</uri>. |
2423 |
</p> |
2424 |
|
2425 |
</body> |
2426 |
</subsection> |
2427 |
</section> |
2428 |
<section id="filesystems"> |
2429 |
<title>Creating Filesystems</title> |
2430 |
<subsection> |
2431 |
<title>Introduction</title> |
2432 |
<body> |
2433 |
|
2434 |
<p> |
2435 |
Now that your partitions are created, it is time to place a filesystem on them. |
2436 |
If you don't care about what filesystem to choose and are happy with what we use |
2437 |
as default in this handbook, continue with <uri |
2438 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
2439 |
Otherwise read on to learn about the available filesystems... |
2440 |
</p> |
2441 |
|
2442 |
</body> |
2443 |
</subsection> |
2444 |
<subsection> |
2445 |
<title>Filesystems?</title> |
2446 |
<body> |
2447 |
|
2448 |
<p> |
2449 |
The Linux kernel supports various filesystems. We'll explain ext2, ext3, |
2450 |
ReiserFS, XFS and JFS as these are the most commonly used filesystems on Linux |
2451 |
systems. |
2452 |
</p> |
2453 |
|
2454 |
<p> |
2455 |
<b>vfat</b> is the MS-DOS filesystem, updated to allow long filenames. It is |
2456 |
also the only filesystem type that the EFI firmware on ia64 systems understand. |
2457 |
The boot partition on ia64 systems should always be vfat, but for your data |
2458 |
partitions you should use one of the other filesystems listed below. |
2459 |
</p> |
2460 |
|
2461 |
<p> |
2462 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
2463 |
journaling, which means that routine ext2 filesystem checks at startup time can |
2464 |
be quite time-consuming. There is now quite a selection of newer-generation |
2465 |
journaled filesystems that can be checked for consistency very quickly and are |
2466 |
thus generally preferred over their non-journaled counterparts. Journaled |
2467 |
filesystems prevent long delays when you boot your system and your filesystem |
2468 |
happens to be in an inconsistent state. |
2469 |
</p> |
2470 |
|
2471 |
<p> |
2472 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
2473 |
journaling for fast recovery in addition to other enhanced journaling modes |
2474 |
like full data and ordered data journaling. It uses a hashed B*-tree index that |
2475 |
enables high performance in almost all situations. In short, ext3 is a very |
2476 |
good and reliable filesystem. |
2477 |
</p> |
2478 |
|
2479 |
<p> |
2480 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
2481 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
2482 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
2483 |
extremely well and has metadata journaling. ReiserFS is solid and usable as |
2484 |
both general-purpose filesystem and for extreme cases such as the creation of |
2485 |
large filesystems, very large files and directories containing tens of |
2486 |
thousands of small files. |
2487 |
</p> |
2488 |
|
2489 |
<p> |
2490 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
2491 |
feature-set and is optimized for scalability. We only recommend using this |
2492 |
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
2493 |
an uninterruptible power supply. Because XFS aggressively caches in-transit data |
2494 |
in RAM, improperly designed programs (those that don't take proper precautions |
2495 |
when writing files to disk and there are quite a few of them) can lose a good |
2496 |
deal of data if the system goes down unexpectedly. |
2497 |
</p> |
2498 |
|
2499 |
<p> |
2500 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
2501 |
become production-ready and there hasn't been a sufficient track record to |
2502 |
comment positively nor negatively on its general stability at this point. |
2503 |
</p> |
2504 |
|
2505 |
</body> |
2506 |
</subsection> |
2507 |
<subsection id="filesystems-apply"> |
2508 |
<title>Applying a Filesystem to a Partition</title> |
2509 |
<body> |
2510 |
|
2511 |
<p> |
2512 |
To create a filesystem on a partition or volume, there are tools available for |
2513 |
each possible filesystem: |
2514 |
</p> |
2515 |
|
2516 |
<table> |
2517 |
<tr> |
2518 |
<th>Filesystem</th> |
2519 |
<th>Creation Command</th> |
2520 |
</tr> |
2521 |
<tr> |
2522 |
<ti>vfat</ti> |
2523 |
<ti><c>mkdosfs</c></ti> |
2524 |
</tr> |
2525 |
<tr> |
2526 |
<ti>ext2</ti> |
2527 |
<ti><c>mke2fs</c></ti> |
2528 |
</tr> |
2529 |
<tr> |
2530 |
<ti>ext3</ti> |
2531 |
<ti><c>mke2fs -j</c></ti> |
2532 |
</tr> |
2533 |
<tr> |
2534 |
<ti>reiserfs</ti> |
2535 |
<ti><c>mkreiserfs</c></ti> |
2536 |
</tr> |
2537 |
<tr> |
2538 |
<ti>xfs</ti> |
2539 |
<ti><c>mkfs.xfs</c></ti> |
2540 |
</tr> |
2541 |
<tr> |
2542 |
<ti>jfs</ti> |
2543 |
<ti><c>mkfs.jfs</c></ti> |
2544 |
</tr> |
2545 |
</table> |
2546 |
|
2547 |
<p> |
2548 |
For instance, to have the boot partition (<path>/dev/sda1</path> in our |
2549 |
example) as vfat and the root partition (<path>/dev/sda3</path> in our example) |
2550 |
as ext3, you would run the following commands: |
2551 |
</p> |
2552 |
|
2553 |
<pre caption="Applying a filesystem on a partition"> |
2554 |
# <i>mkdosfs /dev/sda1</i> |
2555 |
mkdosfs 2.10 (22 Sep 2003) |
2556 |
|
2557 |
# <i>mke2fs -j -O dir_index /dev/sda3</i> |
2558 |
mke2fs 1.36 (05-Feb-2005) |
2559 |
Filesystem label= |
2560 |
OS type: Linux |
2561 |
Block size=4096 (log=2) |
2562 |
Fragment size=4096 (log=2) |
2563 |
4382336 inodes, 8752348 blocks |
2564 |
437617 blocks (5.00%) reserved for the super user |
2565 |
First data block=0 |
2566 |
268 block groups |
2567 |
32768 blocks per group, 32768 fragments per group |
2568 |
16352 inodes per group |
2569 |
Superblock backups stored on blocks: |
2570 |
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, |
2571 |
4096000, 7962624 |
2572 |
|
2573 |
Writing inode tables: done |
2574 |
Creating journal (8192 blocks): done |
2575 |
Writing superblocks and filesystem accounting information: done |
2576 |
|
2577 |
This filesystem will be automatically checked every 26 mounts or |
2578 |
180 days, whichever comes first. Use tune2fs -c or -i to override. |
2579 |
</pre> |
2580 |
|
2581 |
</body> |
2582 |
</subsection> |
2583 |
<subsection> |
2584 |
<title>Activating the Swap Partition</title> |
2585 |
<body> |
2586 |
|
2587 |
<p> |
2588 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
2589 |
</p> |
2590 |
|
2591 |
<pre caption="Creating a Swap signature"> |
2592 |
# <i>mkswap /dev/sda2</i> |
2593 |
</pre> |
2594 |
|
2595 |
<p> |
2596 |
To activate the swap partition, use <c>swapon</c>: |
2597 |
</p> |
2598 |
|
2599 |
<pre caption="Activating the swap partition"> |
2600 |
# <i>swapon /dev/sda2</i> |
2601 |
</pre> |
2602 |
|
2603 |
<p> |
2604 |
Create and activate the swap with the commands mentioned above. |
2605 |
</p> |
2606 |
|
2607 |
</body> |
2608 |
</subsection> |
2609 |
</section> |
2610 |
<section> |
2611 |
<title>Mounting</title> |
2612 |
<body> |
2613 |
|
2614 |
<p> |
2615 |
Now that your partitions are initialized and are housing a filesystem, it is |
2616 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
2617 |
create the necessary mount directories for every partition you created. As an |
2618 |
example we mount the root and boot partition: |
2619 |
</p> |
2620 |
|
2621 |
<pre caption="Mounting the root partition"> |
2622 |
# <i>mount /dev/sda3 /mnt/gentoo</i> |
2623 |
</pre> |
2624 |
|
2625 |
<note> |
2626 |
Unlike some of the other architectures supported by Gentoo, <path>/boot</path> |
2627 |
is not mounted on ia64. The reason for this is that the EFI boot partition will |
2628 |
be automatically mounted and written by the elilo command each time that you run |
2629 |
it. Because of this, /boot resides on the root filesystem and is the storage |
2630 |
place for the kernels referenced by your elilo configuration. |
2631 |
</note> |
2632 |
|
2633 |
<note> |
2634 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
2635 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
2636 |
also holds for <path>/var/tmp</path>. |
2637 |
</note> |
2638 |
|
2639 |
<p> |
2640 |
We will also have to mount the proc filesystem (a virtual interface with the |
2641 |
kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. |
2642 |
</p> |
2643 |
|
2644 |
<p> |
2645 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
2646 |
Installation Files</uri>. |
2647 |
</p> |
2648 |
|
2649 |
</body> |
2650 |
</section> |
2651 |
</sections> |
2652 |
|
2653 |
|
2654 |
|
2655 |
1.1 xml/htdocs/doc/en/handbook/draft/hb-install-ia64-kernel.xml |
2656 |
|
2657 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-kernel.xml?rev=1.1&view=markup |
2658 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-kernel.xml?rev=1.1&content-type=text/plain |
2659 |
|
2660 |
Index: hb-install-ia64-kernel.xml |
2661 |
=================================================================== |
2662 |
<?xml version='1.0' encoding='UTF-8'?> |
2663 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
2664 |
|
2665 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
2666 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
2667 |
|
2668 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-kernel.xml,v 1.1 2007/03/14 06:24:40 nightmorph Exp $ --> |
2669 |
|
2670 |
<sections> |
2671 |
|
2672 |
<version>7.4</version> |
2673 |
<date>2007-03-12</date> |
2674 |
|
2675 |
<section> |
2676 |
<title>Timezone</title> |
2677 |
<body> |
2678 |
|
2679 |
<p> |
2680 |
You first need to select your timezone so that your system knows where it is |
2681 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
2682 |
it to <path>/etc/localtime</path>. Please avoid the |
2683 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
2684 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
2685 |
</p> |
2686 |
|
2687 |
<pre caption="Setting the timezone information"> |
2688 |
# <i>ls /usr/share/zoneinfo</i> |
2689 |
<comment>(Suppose you want to use GMT)</comment> |
2690 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
2691 |
</pre> |
2692 |
|
2693 |
</body> |
2694 |
</section> |
2695 |
<section> |
2696 |
<title>Installing the Sources</title> |
2697 |
<subsection> |
2698 |
<title>Choosing a Kernel</title> |
2699 |
<body> |
2700 |
|
2701 |
<p> |
2702 |
The core around which all distributions are built is the Linux kernel. It is the |
2703 |
layer between the user programs and your system hardware. Gentoo provides its |
2704 |
users several possible kernel sources. A full listing with description is |
2705 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
2706 |
Guide</uri>. |
2707 |
</p> |
2708 |
|
2709 |
<p> |
2710 |
For IA64 systems, we will use <c>gentoo-sources</c> (contains additional patches |
2711 |
for performance and stability). |
2712 |
</p> |
2713 |
|
2714 |
<p> |
2715 |
Now install it using <c>emerge</c>. |
2716 |
</p> |
2717 |
|
2718 |
<pre caption="Installing a kernel source"> |
2719 |
# <i>emerge gentoo-sources</i> |
2720 |
</pre> |
2721 |
|
2722 |
<p> |
2723 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
2724 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
2725 |
kernel source points to <c>gentoo-sources-<keyval id="kernel-version"/></c>. |
2726 |
Your version may be different, so keep this in mind. |
2727 |
</p> |
2728 |
|
2729 |
<pre caption="Viewing the kernel source symlink"> |
2730 |
# <i>ls -l /usr/src/linux</i> |
2731 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-<keyval id="kernel-version"/> |
2732 |
</pre> |
2733 |
|
2734 |
<p> |
2735 |
Now it is time to configure and compile your kernel source. You can use |
2736 |
<c>genkernel</c> for this, which will build a generic kernel as used by the |
2737 |
Installation CD. We explain the "manual" configuration first though, as it is |
2738 |
the best way to optimize your environment. |
2739 |
</p> |
2740 |
|
2741 |
<p> |
2742 |
If you want to manually configure your kernel, continue now with <uri |
2743 |
link="#manual">Default: Manual Configuration</uri>. If you want to use |
2744 |
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
2745 |
genkernel</uri> instead. |
2746 |
</p> |
2747 |
|
2748 |
</body> |
2749 |
</subsection> |
2750 |
</section> |
2751 |
<section id="manual"> |
2752 |
<title>Default: Manual Configuration</title> |
2753 |
<subsection> |
2754 |
<title>Introduction</title> |
2755 |
<body> |
2756 |
|
2757 |
<p> |
2758 |
Manually configuring a kernel is often seen as the most difficult procedure a |
2759 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
2760 |
couple of kernels you don't even remember that it was difficult ;) |
2761 |
</p> |
2762 |
|
2763 |
<p> |
2764 |
However, one thing <e>is</e> true: you must know your system when you start |
2765 |
configuring a kernel manually. Most information can be gathered by emerging |
2766 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
2767 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
2768 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
2769 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
2770 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
2771 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
2772 |
uses (it might provide you with a nice hint on what to enable). |
2773 |
</p> |
2774 |
|
2775 |
<p> |
2776 |
Now go to your kernel source directory and execute <c>make menuconfig</c>. This |
2777 |
will fire up an ncurses-based configuration menu. |
2778 |
</p> |
2779 |
|
2780 |
<pre caption="Invoking menuconfig"> |
2781 |
# <i>cd /usr/src/linux</i> |
2782 |
# <i>make menuconfig</i> |
2783 |
</pre> |
2784 |
|
2785 |
<p> |
2786 |
You will be greeted with several configuration sections. We'll first list some |
2787 |
options you must activate (otherwise Gentoo will not function, or not function |
2788 |
properly without additional tweaks). |
2789 |
</p> |
2790 |
|
2791 |
</body> |
2792 |
</subsection> |
2793 |
<subsection> |
2794 |
<title>Activating Required Options</title> |
2795 |
<body> |
2796 |
|
2797 |
<p> |
2798 |
First of all, activate the use of development and experimental code/drivers. |
2799 |
You need this, otherwise some very important code/drivers won't show up: |
2800 |
</p> |
2801 |
|
2802 |
<pre caption="Selecting experimental code/drivers, General setup"> |
2803 |
Code maturity level options ---> |
2804 |
[*] Prompt for development and/or incomplete code/drivers |
2805 |
General setup ---> |
2806 |
[*] Support for hot-pluggable devices |
2807 |
</pre> |
2808 |
|
2809 |
<p> |
2810 |
Make sure that every driver that is vital to the booting of your system (such as |
2811 |
SCSI controller, ...) is compiled <e>in</e> the kernel and not as a module, |
2812 |
otherwise your system will not be able to boot completely. |
2813 |
</p> |
2814 |
|
2815 |
<p> |
2816 |
Now select the correct system type and processor type. If you don't know what |
2817 |
kind of IA64 system type you have, <c>DIG-compliant</c> is a good default |
2818 |
choice. If you are installing on an SGI system make sure you select the |
2819 |
SGI system type, your kernel may just lock up and refuse to boot otherwise. |
2820 |
</p> |
2821 |
|
2822 |
<pre caption="Selecting correct system type"> |
2823 |
System type ---> |
2824 |
<comment>(Change according to your system)</comment> |
2825 |
<i>DIG-compliant</i> |
2826 |
Processor type ---> |
2827 |
<comment>(Change according to your system)</comment> |
2828 |
<i>Itanium 2</i> |
2829 |
</pre> |
2830 |
|
2831 |
<p> |
2832 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
2833 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
2834 |
able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc |
2835 |
file system</c>. |
2836 |
</p> |
2837 |
|
2838 |
<pre caption="Selecting necessary file systems"> |
2839 |
File systems ---> |
2840 |
Pseudo Filesystems ---> |
2841 |
[*] /proc file system support |
2842 |
[*] Virtual memory file system support (former shm fs) |
2843 |
|
2844 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
2845 |
<*> Reiserfs support |
2846 |
<*> Ext3 journalling file system support |
2847 |
<*> JFS filesystem support |
2848 |
<*> Second extended fs support |
2849 |
<*> XFS filesystem support |
2850 |
|
2851 |
<comment>(Be sure to enable VFAT support for the EFI partition)</comment> |
2852 |
DOS/FAT/NT Filesystems ---> |
2853 |
<*> VFAT (Windows-95) fs support |
2854 |
</pre> |
2855 |
|
2856 |
<p> |
2857 |
Do not forget to enable DMA for your drives: |
2858 |
</p> |
2859 |
|
2860 |
<pre caption="Activating DMA"> |
2861 |
Device Drivers ---> |
2862 |
ATA/ATAPI/MFM/RLL support ---> |
2863 |
[*] Generic PCI bus-master DMA support |
2864 |
[*] Use PCI DMA by default when available |
2865 |
</pre> |
2866 |
|
2867 |
<p> |
2868 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
2869 |
modem, you will need the following options in the kernel: |
2870 |
</p> |
2871 |
|
2872 |
<pre caption="Selecting PPPoE necessary drivers"> |
2873 |
Device Drivers ---> |
2874 |
Networking Support ---> |
2875 |
<*> PPP (point-to-point protocol) support |
2876 |
<*> PPP support for async serial ports |
2877 |
<*> PPP support for sync tty ports |
2878 |
</pre> |
2879 |
|
2880 |
<p> |
2881 |
The two compression options won't harm but are not definitely needed, neither |
2882 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
2883 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
2884 |
</p> |
2885 |
|
2886 |
<p> |
2887 |
If you require it, don't forget to include support in the kernel for your |
2888 |
ethernet card. |
2889 |
</p> |
2890 |
|
2891 |
<p> |
2892 |
If you have an Intel CPU that supports HyperThreading (tm), or you have a |
2893 |
multi-CPU system, you should activate "Symmetric multi-processing support": |
2894 |
</p> |
2895 |
|
2896 |
<pre caption="Activating SMP support"> |
2897 |
Processor type and features ---> |
2898 |
[*] Symmetric multi-processing support |
2899 |
</pre> |
2900 |
|
2901 |
<p> |
2902 |
If you use USB Input Devices (like Keyboard or Mouse) don't forget to enable |
2903 |
those as well: |
2904 |
</p> |
2905 |
|
2906 |
<pre caption="Activating USB Support for Input Devices"> |
2907 |
Device Drivers ---> |
2908 |
USB Support ---> |
2909 |
<*> USB Human Interface Device (full HID) support |
2910 |
</pre> |
2911 |
|
2912 |
<p> |
2913 |
When you've finished configuring the kernel, continue with <uri |
2914 |
link="#compiling">Compiling and Installing</uri>. |
2915 |
</p> |
2916 |
|
2917 |
</body> |
2918 |
</subsection> |
2919 |
<subsection id="compiling"> |
2920 |
<title>Compiling and Installing</title> |
2921 |
<body> |
2922 |
|
2923 |
<p> |
2924 |
Now that your kernel is configured, it is time to compile and install it. Exit |
2925 |
the configuration and start the compilation process: |
2926 |
</p> |
2927 |
|
2928 |
<pre caption="Compiling the kernel"> |
2929 |
# <i>make && make modules_install</i> |
2930 |
</pre> |
2931 |
|
2932 |
<p> |
2933 |
When the kernel has finished compiling, copy the kernel image to |
2934 |
<path>/boot</path>. Use whatever name you feel is appropriate for your kernel |
2935 |
choice and remember it as you will need it later on when you configure your |
2936 |
bootloader. Remember to replace <c><keyval id="kernel-name"/></c> with the |
2937 |
name and version of your kernel. |
2938 |
</p> |
2939 |
|
2940 |
<pre caption="Installing the kernel"> |
2941 |
# <i>cp vmlinux.gz /boot/<keyval id="kernel-name"/></i> |
2942 |
</pre> |
2943 |
|
2944 |
<p> |
2945 |
Now continue with <uri link="#kernel_modules">Kernel Modules</uri>. |
2946 |
</p> |
2947 |
|
2948 |
</body> |
2949 |
</subsection> |
2950 |
</section> |
2951 |
<section id="genkernel"> |
2952 |
<title>Alternative: Using genkernel</title> |
2953 |
<body> |
2954 |
|
2955 |
<p> |
2956 |
If you are reading this section, you have chosen to use our <c>genkernel</c> |
2957 |
script to configure your kernel for you. |
2958 |
</p> |
2959 |
|
2960 |
<p> |
2961 |
Now that your kernel source tree is installed, it's now time to compile your |
2962 |
kernel by using our <c>genkernel</c> script to automatically build a kernel for |
2963 |
you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
2964 |
way our Installation CD kernel is configured. This means that when you use |
2965 |
<c>genkernel</c> to build your kernel, your system will generally detect all |
2966 |
your hardware at boot-time, just like our Installation CD does. Because |
2967 |
genkernel doesn't require any manual kernel configuration, it is an ideal |
2968 |
solution for those users who may not be comfortable compiling their own kernels. |
2969 |
</p> |
2970 |
|
2971 |
<p> |
2972 |
Now, let's see how to use genkernel. First, emerge the genkernel ebuild: |
2973 |
</p> |
2974 |
|
2975 |
<pre caption="Emerging genkernel"> |
2976 |
# <i>emerge genkernel</i> |
2977 |
</pre> |
2978 |
|
2979 |
<p> |
2980 |
Now, compile your kernel sources by running <c>genkernel --udev all</c>. |
2981 |
Be aware though, as <c>genkernel</c> compiles a kernel that supports almost all |
2982 |
hardware, this compilation will take quite a while to finish! |
2983 |
</p> |
2984 |
|
2985 |
<note> |
2986 |
Users of EVMS2 or LVM2 will probably want to add |
2987 |
<c>--evms2</c> or <c>--lvm2</c> to the genkernel command-line. |
2988 |
</note> |
2989 |
|
2990 |
<pre caption="Running genkernel"> |
2991 |
# <i>genkernel --udev all</i> |
2992 |
</pre> |
2993 |
|
2994 |
<p> |
2995 |
Once <c>genkernel</c> completes, a kernel, full set of modules and |
2996 |
<e>initial root disk</e> (initrd) will be created. We will use the kernel |
2997 |
and initrd when configuring a boot loader later in this document. Write |
2998 |
down the names of the kernel and initrd as you will need it when writing |
2999 |
the bootloader configuration file. The initrd will be started immediately after |
3000 |
booting to perform hardware autodetection (just like on the Installation CD) |
3001 |
before your "real" system starts up. |
3002 |
</p> |
3003 |
|
3004 |
<pre caption="Checking the created kernel image name and initrd"> |
3005 |
# <i>ls /boot/kernel* /boot/initramfs*</i> |
3006 |
</pre> |
3007 |
|
3008 |
</body> |
3009 |
</section> |
3010 |
<section id="kernel_modules"> |
3011 |
<title>Kernel Modules</title> |
3012 |
<subsection> |
3013 |
<title>Configuring the Modules</title> |
3014 |
<body> |
3015 |
|
3016 |
<p> |
3017 |
You should list the modules you want automatically loaded in |
3018 |
<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra options to |
3019 |
the modules too if you want. |
3020 |
</p> |
3021 |
|
3022 |
<p> |
3023 |
To view all available modules, run the following <c>find</c> command. Don't |
3024 |
forget to substitute <c><keyval id="kernel-version"/></c> with the version of |
3025 |
the kernel you just compiled: |
3026 |
</p> |
3027 |
|
3028 |
<pre caption="Viewing all available modules"> |
3029 |
# <i>find /lib/modules/<keyval id="kernel-version"/>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
3030 |
</pre> |
3031 |
|
3032 |
<p> |
3033 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
3034 |
<path>kernel-2.6</path> file and enter the module name in it. |
3035 |
</p> |
3036 |
|
3037 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
3038 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
3039 |
</pre> |
3040 |
|
3041 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
3042 |
3c59x |
3043 |
</pre> |
3044 |
|
3045 |
<p> |
3046 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
3047 |
your System</uri>. |
3048 |
</p> |
3049 |
|
3050 |
</body> |
3051 |
</subsection> |
3052 |
</section> |
3053 |
</sections> |
3054 |
|
3055 |
|
3056 |
|
3057 |
1.1 xml/htdocs/doc/en/handbook/draft/hb-install-ia64-medium.xml |
3058 |
|
3059 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-medium.xml?rev=1.1&view=markup |
3060 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-medium.xml?rev=1.1&content-type=text/plain |
3061 |
|
3062 |
Index: hb-install-ia64-medium.xml |
3063 |
=================================================================== |
3064 |
<?xml version='1.0' encoding='UTF-8'?> |
3065 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
3066 |
|
3067 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
3068 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
3069 |
|
3070 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-medium.xml,v 1.1 2007/03/14 06:24:40 nightmorph Exp $ --> |
3071 |
|
3072 |
<sections> |
3073 |
|
3074 |
<version>4.0</version> |
3075 |
<date>2006-08-30</date> |
3076 |
|
3077 |
<section> |
3078 |
<title>Hardware Requirements</title> |
3079 |
<subsection> |
3080 |
<title>Introduction</title> |
3081 |
<body> |
3082 |
|
3083 |
<p> |
3084 |
Before we start, we first list what hardware requirements you need to |
3085 |
successfully install Gentoo on your box. |
3086 |
</p> |
3087 |
|
3088 |
</body> |
3089 |
</subsection> |
3090 |
<subsection> |
3091 |
<title>Hardware Requirements</title> |
3092 |
<body> |
3093 |
|
3094 |
<p> |
3095 |
Pretty much every IA64 should be able to boot Gentoo. At the moment we only |
3096 |
have LiveCDs, so your machine must have a CDROM drive installed. |
3097 |
</p> |
3098 |
|
3099 |
</body> |
3100 |
</subsection> |
3101 |
</section> |
3102 |
|
3103 |
<section> |
3104 |
<title>The Gentoo Installation CDs</title> |
3105 |
<subsection> |
3106 |
<title>Introduction</title> |
3107 |
<body> |
3108 |
|
3109 |
<p> |
3110 |
The <e>Gentoo Installation CDs</e> are bootable CDs which contain a |
3111 |
self-sustained Gentoo environment. They allow you to boot Linux from the CD. |
3112 |
During the boot process your hardware is detected and the appropriate drivers |
3113 |
are loaded. They are maintained by Gentoo developers. |
3114 |
</p> |
3115 |
|
3116 |
<p> |
3117 |
All Installation CDs allow you to boot, set up networking, initialize your |
3118 |
partitions and start installing Gentoo from the Internet. We currently provide |
3119 |
two Installation CDs which are equaly suitable to install Gentoo from, as long |
3120 |
as you're planning on performing an Internet-based installation using the |
3121 |
latest version of the available packages. |
3122 |
</p> |
3123 |
|
3124 |
<impo> |
3125 |
If you wish to install Gentoo without a working Internet connection, or would |
3126 |
like to use one of the provided installers, please use the installation |
3127 |
instructions described in the <uri link="2006.1/">Gentoo 2006.1 |
3128 |
Handbooks</uri>. |
3129 |
</impo> |
3130 |
|
3131 |
<p> |
3132 |
The Installation CD that we currently provide for IA64: |
3133 |
</p> |
3134 |
|
3135 |
<ul> |
3136 |
<li> |
3137 |
The Gentoo <e>Minimal</e> Installation CD, a small, no-nonsense, bootable |
3138 |
CD which sole purpose is to boot the system, prepare the networking and |
3139 |
continue with the Gentoo installation. |
3140 |
</li> |
3141 |
</ul> |
3142 |
|
3143 |
</body> |
3144 |
</subsection> |
3145 |
<subsection> |
3146 |
<title>Gentoo Minimal Installation CD</title> |
3147 |
<body> |
3148 |
|
3149 |
<p> |
3150 |
The Minimal Installation CD is called <c><keyval id="min-cd-name"/></c> and |
3151 |
takes up only <keyval id="min-cd-size"/> MB of diskspace. You can use this |
3152 |
Installation CD to install Gentoo, but <e>only</e> with a working Internet |
3153 |
connection. |
3154 |
</p> |
3155 |
|
3156 |
<table> |
3157 |
<tr> |
3158 |
<th>Minimal Installation CD</th> |
3159 |
<th>Pros and Cons</th> |
3160 |
</tr> |
3161 |
<tr> |
3162 |
<th>+</th> |
3163 |
<ti>Smallest download</ti> |
3164 |
</tr> |
3165 |
<tr> |
3166 |
<th>-</th> |
3167 |
<ti> |
3168 |
Contains no stage3 tarball, no Portage snapshot, no prebuilt packages and |
3169 |
is therefore not suitable for networkless installation |
3170 |
</ti> |
3171 |
</tr> |
3172 |
</table> |
3173 |
|
3174 |
</body> |
3175 |
</subsection> |
3176 |
<subsection> |
3177 |
<title>The Stage3 Tarball</title> |
3178 |
<body> |
3179 |
|
3180 |
<p> |
3181 |
A stage3 tarball is an archive containing a minimal Gentoo environment, |
3182 |
suitable to continue the Gentoo installation using the instructions in this |
3183 |
manual. Previously, the Gentoo Handbook described the installation using one of |
3184 |
three stage tarballs. While Gentoo still offers stage1 and stage2 tarballs, the |
3185 |
official installation method uses the stage3 tarball. If you are interested in |
3186 |
performing a Gentoo installation using a stage1 or stage2 tarball, please read |
3187 |
the Gentoo FAQ on <uri link="/doc/en/faq.xml#stage12">How do I Install Gentoo |
3188 |
Using a Stage1 or Stage2 Tarball?</uri> |
3189 |
</p> |
3190 |
|
3191 |
<p> |
3192 |
Stage3 tarballs can be downloaded from <path><keyval |
3193 |
id="release-dir"/>stages/</path> on any of the <uri |
3194 |
link="/main/en/mirrors.xml">Official Gentoo Mirrors</uri> and are not provided |
3195 |
on the LiveCD. |
3196 |
</p> |
3197 |
|
3198 |
</body> |
3199 |
</subsection> |
3200 |
</section> |
3201 |
<section> |
3202 |
<title>Download, Burn and Boot a Gentoo Installation CD</title> |
3203 |
<subsection> |
3204 |
<title>Downloading and Burning the Installation CDs</title> |
3205 |
<body> |
3206 |
|
3207 |
<p> |
3208 |
You have chosen to use a Gentoo Installation CD. We'll first start by |
3209 |
downloading and burning the chosen Installation CD. We previously discussed |
3210 |
the several available Installation CDs, but where can you find them? |
3211 |
</p> |
3212 |
|
3213 |
<p> |
3214 |
You can download any of the Installation CDs from one of our <uri |
3215 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located in |
3216 |
the <path><keyval id="release-dir"/>installcd/</path> directory. |
3217 |
</p> |
3218 |
|
3219 |
<p> |
3220 |
Inside that directory you'll find ISO-files. Those are full CD images which you |
3221 |
can write on a CD-R. |
3222 |
</p> |
3223 |
|
3224 |
<p> |
3225 |
In case you wonder if your downloaded file is corrupted or not, you can check |
3226 |
its MD5 checksum and compare it with the MD5 checksum we provide (such as |
3227 |
<path><keyval id="min-cd-name"/>.DIGESTS</path>). You can check the MD5 |
3228 |
checksum with the <c>md5sum</c> tool under Linux/Unix or <uri |
3229 |
link="http://www.etree.org/md5com.html">md5sum</uri> for Windows. |
3230 |
</p> |
3231 |
|
3232 |
<p> |
3233 |
Another way to check the validity of the downloaded file is to use GnuPG to |
3234 |
verify the cryptographic signature that we provide (the file ending with |
3235 |
<path>.asc</path>). Download the signature file and obtain the public key: |
3236 |
</p> |
3237 |
|
3238 |
<pre caption="Obtaining the public key"> |
3239 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
3240 |
</pre> |
3241 |
|
3242 |
<p> |
3243 |
Now verify the signature: |
3244 |
</p> |
3245 |
|
3246 |
<pre caption="Verify the cryptographic signature"> |
3247 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
3248 |
</pre> |
3249 |
|
3250 |
<p> |
3251 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
3252 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
3253 |
<c>K3B</c> here; more information can be found in our <uri |
3254 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
3255 |
</p> |
3256 |
|
3257 |
<ul> |
3258 |
<li> |
3259 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
3260 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's |
3261 |
device path). |
3262 |
</li> |
3263 |
<li> |
3264 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
3265 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
3266 |
<c>Start</c>. |
3267 |
</li> |
3268 |
</ul> |
3269 |
|
3270 |
</body> |
3271 |
</subsection> |
3272 |
<subsection> |
3273 |
<title>Booting the Installation CD</title> |
3274 |
<body> |
3275 |
|
3276 |
<p> |
3277 |
Once you have burnt your installation CD, it is time to boot it. |
3278 |
Remove all CDs from your CD drives, and insert the Gentoo |
3279 |
InstallCD. Reboot your system and wait for the EFI firmware to load on |
3280 |
the console. The exact option to select will differ depending on your |
3281 |
hardware. |
3282 |
</p> |
3283 |
|
3284 |
<p> |
3285 |
Most implementations usually present an option directly on the first |
3286 |
menu (the EFI Boot Manager). The exact wording would differ but would |
3287 |
usually be something like "CD Boot", "Removable Media |
3288 |
Boot" or "Internal Bootable DVD". Select this option. |
3289 |
</p> |
3290 |
|
3291 |
<p> |
3292 |
If your EFI implementation does not present such an option, you can |
3293 |
boot the CD using the EFI Shell. All implementations will present an |
3294 |
option to enter the shell on the Boot Manager menu. Select this |
3295 |
option. The EFI Shell will display a list of usable block devices |
3296 |
(<c>blk<b>n</b>:</c>) and also a list of filesystems the EFI Shell |
3297 |
can actually access (<c>fs<b>n</b>:</c>). |
3298 |
</p> |
3299 |
|
3300 |
<p> |
3301 |
In most cases the option you want will be the <c>fs0:</c> choice; |
3302 |
regardless, (provided the CD drive recognizes the CD), you should |
3303 |
see one <c>fs<b>n</b></c> entry for your CD drive (the CD drive's |
3304 |
EFI device path will contain <c>CDROM</c> in the wording). Enter |
3305 |
<c>fs<b>n</b>:</c>, replacing <b>n</b> as required and including |
3306 |
the colon, followed by the Enter key. Next just type <c>elilo</c> |
3307 |
followed by the Enter key. |
3308 |
</p> |
3309 |
|
3310 |
<p> |
3311 |
You will now be greeted by the ELILO boot message and asked to |
3312 |
enter a kernel to boot as well as any additional options to pass |
3313 |
to the kernel command line. In most cases just hit the Enter key |
3314 |
or wait five seconds. Only one kernel is supplied on the IA64 |
3315 |
InstallCD, the <c>gentoo</c> kernel. |
3316 |
</p> |
3317 |
|
3318 |
<p> |
3319 |
Several kernel aliases are provided which add extra options to |
3320 |
the kernel command line, which you may have to use instead of |
3321 |
the default <c>gentoo</c> option depending on your hardware: |
3322 |
</p> |
3323 |
|
3324 |
<p> |
3325 |
The <c>gentoo-serial</c> option forces a serial console on the first |
3326 |
serial port (ttyS0) at 9600bps. This may be required on some older EFI |
3327 |
implementations where the kernel can't detect what console to use. You |
3328 |
should try this option if booting the default <c>gentoo</c> kernel |
3329 |
produces no output and if you are using a serial console. If you use a |
3330 |
serial console which is not connected to the first serial port you |
3331 |
must manually select the console by typing <c>gentoo |
3332 |
console=ttyS#,9600</c> where <c>#</c> is the number of the serial |
3333 |
port. You should <b>not</b> have to do this in normal circumstances, |
3334 |
this is only sometimes required for quirky EFI implementations. |
3335 |
</p> |
3336 |
|
3337 |
<p> |
3338 |
The <c>gentoo-sgi</c> option forces a serial console on the <c>ttySG0</c> |
3339 |
serial port at 115200bps. This should only be needed on SGI hardware, and |
3340 |
if the console is properly selected in the default EFI settings, or if you |
3341 |
are using a video console this option should not be required. |
3342 |
</p> |
3343 |
|
3344 |
</body> |
3345 |
<body> |
3346 |
|
3347 |
<p> |
3348 |
You can also provide kernel options. They represent optional settings |
3349 |
you can (de)activate at will. |
3350 |
</p> |
3351 |
|
3352 |
<pre caption="Options available to pass to your kernel of choice"> |
3353 |
- agpgart loads agpgart (use if you have graphic problems,lockups) |
3354 |
- ide=nodma force disabling of DMA for malfunctioning IDE devices |
3355 |
- doscsi scan for scsi devices (breaks some ethernet cards) |
3356 |
- dopcmcia starts pcmcia service for PCMCIA cdroms |
3357 |
- nofirewire disables firewire modules in initrd (for firewire cdroms,etc) |
3358 |
- nokeymap disables keymap selection for non-us keyboard layouts |
3359 |
- docache cache the entire runtime portion of CD in RAM, allows you |
3360 |
to umount /mnt/cdrom to mount another CD. |
3361 |
- nodetect causes hwsetup/kudzu and hotplug not to run |
3362 |
- nousb disables usb module load from initrd, disables hotplug |
3363 |
- nodhcp dhcp does not automatically start if nic detected |
3364 |
- nohotplug disables loading hotplug service |
3365 |
- noapic disable apic (try if having hardware problems nics,scsi,etc) |
3366 |
- noevms disable loading of EVMS2 modules |
3367 |
- nolvm2 disable loading of LVM2 modules |
3368 |
- noload=module1,[module2,[...]] |
3369 |
disable loading of specific kernel modules |
3370 |
</pre> |
3371 |
|
3372 |
<p> |
3373 |
You will then be greeted with a boot screen. If you are installing |
3374 |
Gentoo on a system with a non-US keyboard, make sure you select the |
3375 |
layout at the prompt. If no selection is made in 10 seconds the |
3376 |
default (US keyboard) will be accepted and the boot process will |
3377 |
continue. Once the boot process completes, you will be automatically |
3378 |
logged in to the "Live" Gentoo Linux as "root", the super user. You |
3379 |
should have a root ("#") prompt on the current console. If you are |
3380 |
using a video console and have a keyboard connected you can also |
3381 |
switch to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get |
3382 |
back to the one you started on by pressing Alt-F1. |
3383 |
</p> |
3384 |
|
3385 |
<p> |
3386 |
Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
3387 |
</p> |
3388 |
|
3389 |
</body> |
3390 |
</subsection> |
3391 |
<subsection id="hardware"> |
3392 |
<title>Extra Hardware Configuration</title> |
3393 |
<body> |
3394 |
|
3395 |
<p> |
3396 |
When the Installation CD boots, it tries to detect all your hardware devices |
3397 |
and loads the appropriate kernel modules to support your hardware. In the vast |
3398 |
majority of cases, it does a very good job. However, in some cases it may not |
3399 |
auto-load the kernel modules you need. If the PCI auto-detection missed some of |
3400 |
your system's hardware, you will have to load the appropriate kernel modules |
3401 |
manually. |
3402 |
</p> |
3403 |
|
3404 |
<p> |
3405 |
In the next example we try to load the <c>8139too</c> module (support for |
3406 |
certain kinds of network interfaces): |
3407 |
</p> |
3408 |
|
3409 |
<pre caption="Loading kernel modules"> |
3410 |
# <i>modprobe 8139too</i> |
3411 |
</pre> |
3412 |
|
3413 |
</body> |
3414 |
</subsection> |
3415 |
<subsection> |
3416 |
<title>Optional: Tweaking Hard Disk Performance</title> |
3417 |
<body> |
3418 |
|
3419 |
<p> |
3420 |
If you are an advanced user, you might want to tweak the IDE hard disk |
3421 |
performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
3422 |
test the performance of your disk (execute it several times to get a |
3423 |
more precise impression): |
3424 |
</p> |
3425 |
|
3426 |
<pre caption="Testing disk performance"> |
3427 |
# <i>hdparm -tT /dev/hda</i> |
3428 |
</pre> |
3429 |
|
3430 |
<p> |
3431 |
To tweak, you can use any of the following examples (or experiment |
3432 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
3433 |
disk): |
3434 |
</p> |
3435 |
|
3436 |
<pre caption="Tweaking hard disk performance"> |
3437 |
<comment>(Activate DMA:)</comment> |
3438 |
# <i>hdparm -d 1 /dev/hda</i> |
3439 |
|
3440 |
<comment>(Activate Safe Performance Options:)</comment> |
3441 |
# <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
3442 |
</pre> |
3443 |
|
3444 |
</body> |
3445 |
</subsection> |
3446 |
<subsection id="useraccounts"> |
3447 |
<title>Optional: User Accounts</title> |
3448 |
<body> |
3449 |
|
3450 |
<p> |
3451 |
If you plan on giving other people access to your installation |
3452 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
3453 |
security reasons), you need to create the necessary user accounts and change |
3454 |
the root password. |
3455 |
</p> |
3456 |
|
3457 |
<p> |
3458 |
To change the root password, use the <c>passwd</c> utility: |
3459 |
</p> |
3460 |
|
3461 |
<pre caption="Changing the root password"> |
3462 |
# <i>passwd</i> |
3463 |
New password: <comment>(Enter your new password)</comment> |
3464 |
Re-enter password: <comment>(Re-enter your password)</comment> |
3465 |
</pre> |
3466 |
|
3467 |
<p> |
3468 |
To create a user account, we first enter their credentials, followed by |
3469 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
3470 |
In the next example, we create a user called "john". |
3471 |
</p> |
3472 |
|
3473 |
<pre caption="Creating a user account"> |
3474 |
# <i>useradd -m -G users john</i> |
3475 |
# <i>passwd john</i> |
3476 |
New password: <comment>(Enter john's password)</comment> |
3477 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
3478 |
</pre> |
3479 |
|
3480 |
<p> |
3481 |
You can change your user id from root to the newly created user by using |
3482 |
<c>su</c>: |
3483 |
</p> |
3484 |
|
3485 |
<pre caption="Changing user id"> |
3486 |
# <i>su - john</i> |
3487 |
</pre> |
3488 |
|
3489 |
</body> |
3490 |
</subsection> |
3491 |
<subsection> |
3492 |
<title>Optional: Starting the SSH Daemon</title> |
3493 |
<body> |
3494 |
|
3495 |
<p> |
3496 |
If you want to allow other users to access your computer during the |
3497 |
Gentoo installation (perhaps because those users are going to help you |
3498 |
install Gentoo, or even do it for you), you need to create a user |
3499 |
account for them and perhaps even provide them with your root password |
3500 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
3501 |
</p> |
3502 |
|
3503 |
<p> |
3504 |
To fire up the SSH daemon, execute the following command: |
3505 |
</p> |
3506 |
|
3507 |
<pre caption="Starting the SSH daemon"> |
3508 |
# <i>/etc/init.d/sshd start</i> |
3509 |
</pre> |
3510 |
|
3511 |
<p> |
3512 |
To be able to use sshd, you first need to set up your networking. Continue with |
3513 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
3514 |
</p> |
3515 |
|
3516 |
</body> |
3517 |
</subsection> |
3518 |
</section> |
3519 |
</sections> |
3520 |
|
3521 |
|
3522 |
|
3523 |
1.15 xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml |
3524 |
|
3525 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml?rev=1.15&view=markup |
3526 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml?rev=1.15&content-type=text/plain |
3527 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-bootloader.xml?r1=1.14&r2=1.15 |
3528 |
|
3529 |
|
3530 |
|
3531 |
|
3532 |
1.12 xml/htdocs/doc/en/handbook/draft/hb-install-mips-disk.xml |
3533 |
|
3534 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-disk.xml?rev=1.12&view=markup |
3535 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-disk.xml?rev=1.12&content-type=text/plain |
3536 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-disk.xml?r1=1.11&r2=1.12 |
3537 |
|
3538 |
|
3539 |
|
3540 |
|
3541 |
1.12 xml/htdocs/doc/en/handbook/draft/hb-install-mips-kernel.xml |
3542 |
|
3543 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-kernel.xml?rev=1.12&view=markup |
3544 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-kernel.xml?rev=1.12&content-type=text/plain |
3545 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-kernel.xml?r1=1.11&r2=1.12 |
3546 |
|
3547 |
|
3548 |
|
3549 |
|
3550 |
1.12 xml/htdocs/doc/en/handbook/draft/hb-install-mips-medium.xml |
3551 |
|
3552 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-medium.xml?rev=1.12&view=markup |
3553 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-medium.xml?rev=1.12&content-type=text/plain |
3554 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-medium.xml?r1=1.11&r2=1.12 |
3555 |
|
3556 |
|
3557 |
|
3558 |
|
3559 |
1.4 xml/htdocs/doc/en/handbook/draft/hb-install-mips-stage.xml |
3560 |
|
3561 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-stage.xml?rev=1.4&view=markup |
3562 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-stage.xml?rev=1.4&content-type=text/plain |
3563 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-stage.xml?r1=1.3&r2=1.4 |
3564 |
|
3565 |
|
3566 |
|
3567 |
|
3568 |
1.1 xml/htdocs/doc/en/handbook/draft/hb-install-mips-system.xml |
3569 |
|
3570 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-system.xml?rev=1.1&view=markup |
3571 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-system.xml?rev=1.1&content-type=text/plain |
3572 |
|
3573 |
Index: hb-install-mips-system.xml |
3574 |
=================================================================== |
3575 |
<?xml version='1.0' encoding='UTF-8'?> |
3576 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
3577 |
|
3578 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
3579 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
3580 |
|
3581 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-system.xml,v 1.1 2007/03/14 06:24:40 nightmorph Exp $ --> |
3582 |
|
3583 |
<sections> |
3584 |
|
3585 |
<version>7.2</version> |
3586 |
<date>2006-11-08</date> |
3587 |
|
3588 |
<section> |
3589 |
<title>Chrooting</title> |
3590 |
<!--<subsection> MIPS install media doesn't include mirrorselect |
3591 |
<title>Optional: Selecting Mirrors</title> |
3592 |
<body> |
3593 |
|
3594 |
<p> |
3595 |
In order to download source code quickly it is recommended to select a fast |
3596 |
mirror. Portage will look in your <path>make.conf</path> file for the |
3597 |
GENTOO_MIRRORS variable and use the mirrors listed therein. You can surf to |
3598 |
our <uri link="/main/en/mirrors.xml">mirror list</uri> and search |
3599 |
for a mirror (or mirrors) close to you (as those are most frequently the |
3600 |
fastest ones), but we provide a nice tool called <c>mirrorselect</c> which |
3601 |
provides you with a nice interface to select the mirrors you want. |
3602 |
</p> |
3603 |
|
3604 |
<pre caption="Using mirrorselect for the GENTOO_MIRRORS variable"> |
3605 |
# <i>mirrorselect -i -o >> /mnt/gentoo/etc/make.conf</i> |
3606 |
</pre> |
3607 |
|
3608 |
<warn> |
3609 |
Do not select any IPv6 mirrors. Our stages currently do not support IPv6. |
3610 |
</warn> |
3611 |
|
3612 |
<p> |
3613 |
A second important setting is the SYNC setting in <path>make.conf</path>. This |
3614 |
variable contains the rsync server you want to use when updating your Portage |
3615 |
tree (the collection of ebuilds, scripts containing all the information Portage |
3616 |
needs to download and install software). Although you can manually enter a SYNC |
3617 |
server for yourself, <c>mirrorselect</c> can ease that operation for you: |
3618 |
</p> |
3619 |
|
3620 |
<pre caption="Selecting an rsync mirror using mirrorselect"> |
3621 |
# <i>mirrorselect -i -r -o >> /mnt/gentoo/etc/make.conf</i> |
3622 |
</pre> |
3623 |
|
3624 |
<p> |
3625 |
After running <c>mirrorselect</c> it is adviseable to double-check the settings |
3626 |
in <path>/mnt/gentoo/etc/make.conf</path> ! |
3627 |
</p> |
3628 |
|
3629 |
</body> |
3630 |
</subsection>--> |
3631 |
<subsection> |
3632 |
<title>Copy DNS Info</title> |
3633 |
<body> |
3634 |
|
3635 |
<p> |
3636 |
One thing still remains to be done before we enter the new environment and that |
3637 |
is copying over the DNS information in <path>/etc/resolv.conf</path>. You need |
3638 |
to do this to ensure that networking still works even after entering the new |
3639 |
environment. <path>/etc/resolv.conf</path> contains the nameservers for your |
3640 |
network. |
3641 |
</p> |
3642 |
|
3643 |
<pre caption="Copy over DNS information"> |
3644 |
<comment>(The "-L" option is needed to make sure we don't copy a symbolic link)</comment> |
3645 |
# <i>cp -L /etc/resolv.conf /mnt/gentoo/etc/resolv.conf</i> |
3646 |
</pre> |
3647 |
|
3648 |
</body> |
3649 |
</subsection> |
3650 |
<subsection> |
3651 |
<title>Mounting the /proc and /dev Filesystems</title> |
3652 |
<body> |
3653 |
|
3654 |
<p> |
3655 |
Mount the <path>/proc</path> filesystem on <path>/mnt/gentoo/proc</path> to |
3656 |
allow the installation to use the kernel-provided information within the |
3657 |
chrooted environment, and then mount-bind the <path>/dev</path> filesystem. |
3658 |
</p> |
3659 |
|
3660 |
<pre caption="Mounting /proc and /dev"> |
3661 |
# <i>mount -t proc none /mnt/gentoo/proc</i> |
3662 |
# <i>mount -o bind /dev /mnt/gentoo/dev</i> |
3663 |
</pre> |
3664 |
|
3665 |
</body> |
3666 |
</subsection> |
3667 |
<subsection> |
3668 |
<title>Entering the new Environment</title> |
3669 |
<body> |
3670 |
|
3671 |
<p> |
3672 |
Now that all partitions are initialized and the base environment |
3673 |
installed, it is time to enter our new installation environment by |
3674 |
<e>chrooting</e> into it. This means that we change from the current |
3675 |
installation environment (Installation CD or other installation medium) to your |
3676 |
installation system (namely the initialized partitions). |
3677 |
</p> |
3678 |
|
3679 |
<p> |
3680 |
This chrooting is done in three steps. First we will change the root |
3681 |
from <path>/</path> (on the installation medium) to <path>/mnt/gentoo</path> |
3682 |
(on your partitions) using <c>chroot</c>. Then we will create a new environment |
3683 |
using <c>env-update</c>, which essentially creates environment variables. |
3684 |
Finally, we load those variables into memory using <c>source</c>. |
3685 |
</p> |
3686 |
|
3687 |
<pre caption = "Chrooting into the new environment"> |
3688 |
# <i>chroot /mnt/gentoo /bin/bash</i> |
3689 |
# <i>env-update</i> |
3690 |
>> Regenerating /etc/ld.so.cache... |
3691 |
# <i>source /etc/profile</i> |
3692 |
# <i>export PS1="(chroot) $PS1"</i> |
3693 |
</pre> |
3694 |
|
3695 |
<p> |
3696 |
Congratulations! You are now inside your own Gentoo Linux environment. |
3697 |
Of course it is far from finished, which is why the installation still |
3698 |
has some sections left :-) |
3699 |
</p> |
3700 |
|
3701 |
</body> |
3702 |
</subsection> |
3703 |
</section> |
3704 |
|
3705 |
<section> |
3706 |
<title>Configuring Portage</title> |
3707 |
<subsection> |
3708 |
<title>Updating the Portage tree</title> |
3709 |
<body> |
3710 |
|
3711 |
<p> |
3712 |
You should now update your Portage tree to the latest version. <c>emerge |
3713 |
--sync</c> does this for you. |
3714 |
</p> |
3715 |
|
3716 |
<pre caption="Updating the Portage tree"> |
3717 |
# <i>emerge --sync</i> |
3718 |
<comment>(If you're using a slow terminal like some framebuffers or a serial |
3719 |
console, you can add the --quiet option to speed up this process:)</comment> |
3720 |
# <i>emerge --sync --quiet</i> |
3721 |
</pre> |
3722 |
|
3723 |
<p> |
3724 |
If you are behind a firewall that blocks rsync traffic, you can use |
3725 |
<c>emerge-webrsync</c> which will download and install a portage snapshot for |
3726 |
you. |
3727 |
</p> |
3728 |
|
3729 |
<p> |
3730 |
If you are warned that a new Portage version is available and that you should |
3731 |
update Portage, you should do it now using <c>emerge portage</c> command. |
3732 |
</p> |
3733 |
|
3734 |
</body> |
3735 |
</subsection> |
3736 |
<subsection> |
3737 |
<title>Choosing the Right Profile</title> |
3738 |
<body> |
3739 |
|
3740 |
<p> |
3741 |
First, a small definition is in place. |
3742 |
</p> |
3743 |
|
3744 |
<p> |
3745 |
A profile is a building block for any Gentoo system. Not only does it specify |
3746 |
default values for CHOST, CFLAGS and other important variables, it also locks |
3747 |
the system to a certain range of package versions. This is all maintained by the |
3748 |
Gentoo developers. |
3749 |
</p> |
3750 |
|
3751 |
<p> |
3752 |
Previously, such a profile was barely touched by the user. However, there may be |
3753 |
situations in which you may decide a profile change is necessary. |
3754 |
</p> |
3755 |
|
3756 |
<p> |
3757 |
Since 2006.0, there has been a re-shuffle regarding the profiles for MIPS |
3758 |
systems. These profiles set various options including USE flags, which affect |
3759 |
what patchsets are enabled with various system-critical packages (notably, |
3760 |
<c>gcc</c> and <c>mips-sources</c>). |
3761 |
</p> |
3762 |
|
3763 |
<p> |
3764 |
Thus, care needs to be taken to ensure the correct profile is selected for your |
3765 |
system type. As of Gentoo/MIPS 2006.1, the profiles are: |
3766 |
</p> |
3767 |
|
3768 |
<table> |
3769 |
<tr> |
3770 |
<th>System</th> |
3771 |
<th>Profile</th> |
3772 |
<th>Userland</th> |
3773 |
<th>Status/Notes</th> |
3774 |
</tr> |
3775 |
|
3776 |
<tr> |
3777 |
<ti>Cobalt Qube/RaQ</ti> |
3778 |
<ti>default-linux/mips/2006.1/cobalt/o32</ti> |
3779 |
<ti>32-bit Linuxthreads</ti> |
3780 |
<ti>Recommended</ti> |
3781 |
</tr> |
3782 |
<tr> |
3783 |
<ti>"</ti> |
3784 |
<ti>default-linux/mips/2006.1/cobalt/o32/nptl</ti> |
3785 |
<ti>32-bit NPTL</ti> |
3786 |
<ti>In Testing (1)</ti> |
3787 |
</tr> |
3788 |
|
3789 |
<tr> |
3790 |
<th> </th> |
3791 |
<th> </th> |
3792 |
<th> </th> |
3793 |
<th> </th> |
3794 |
</tr> |
3795 |
|
3796 |
<tr> |
3797 |
<ti> |
3798 |
Generic Big Endian<br /> |
3799 |
<e>Including SGI Indy, Indigo2 (R4x00), Challenge S and O2</e> |
3800 |
</ti> |
3801 |
<ti>default-linux/mips/2006.1/generic-be/o32</ti> |
3802 |
<ti>32-bit Linuxthreads</ti> |
3803 |
<ti>Recommended</ti> |
3804 |
</tr> |
3805 |
<tr> |
3806 |
<ti>"</ti> |
3807 |
<ti>default-linux/mips/2006.1/generic-be/o32/nptl</ti> |
3808 |
<ti>32-bit NPTL</ti> |
3809 |
<ti>In Testing (1)</ti> |
3810 |
</tr> |
3811 |
<tr> |
3812 |
<ti>"</ti> |
3813 |
<ti>default-linux/mips/2006.1/generic-be/n32</ti> |
3814 |
<ti>N32 Linuxthreads</ti> |
3815 |
<ti>Highly Experimental (2)</ti> |
3816 |
</tr> |
3817 |
<tr> |
3818 |
<ti>"</ti> |
3819 |
<ti>default-linux/mips/2006.1/generic-be/n32/nptl</ti> |
3820 |
<ti>N32 NPTL</ti> |
3821 |
<ti>Highly Experimental (1) (2)</ti> |
3822 |
</tr> |
3823 |
<tr> |
3824 |
<ti>"</ti> |
3825 |
<ti>default-linux/mips/2006.1/generic-be/n64</ti> |
3826 |
<ti>N64 Linuxthreads</ti> |
3827 |
<ti>Unsupported (3)</ti> |
3828 |
</tr> |
3829 |
<tr> |
3830 |
<ti>"</ti> |
3831 |
<ti>default-linux/mips/2006.1/generic-be/n64/nptl</ti> |
3832 |
<ti>N64 NPTL</ti> |
3833 |
<ti>Unsupported (1) (3)</ti> |
3834 |
</tr> |
3835 |
|
3836 |
<tr> |
3837 |
<th> </th> |
3838 |
<th> </th> |
3839 |
<th> </th> |
3840 |
<th> </th> |
3841 |
</tr> |
3842 |
|
3843 |
<tr> |
3844 |
<ti>SGI Origin 200/2000</ti> |
3845 |
<ti>default-linux/mips/2006.1/ip27/o32</ti> |
3846 |
<ti>32-bit Linuxthreads</ti> |
3847 |
<ti>Recommended</ti> |
3848 |
</tr> |
3849 |
<tr> |
3850 |
<ti>"</ti> |
3851 |
<ti>default-linux/mips/2006.1/ip27/o32/nptl</ti> |
3852 |
<ti>32-bit NPTL</ti> |
3853 |
<ti>In Testing (1)</ti> |
3854 |
</tr> |
3855 |
<tr> |
3856 |
<ti>"</ti> |
3857 |
<ti>default-linux/mips/2006.1/ip27/n32</ti> |
3858 |
<ti>N32 Linuxthreads</ti> |
3859 |
<ti>Highly Experimental (2)</ti> |
3860 |
</tr> |
3861 |
<tr> |
3862 |
<ti>"</ti> |
3863 |
<ti>default-linux/mips/2006.1/ip27/n32/nptl</ti> |
3864 |
<ti>N32 NPTL</ti> |
3865 |
<ti>Highly Experimental (1) (2)</ti> |
3866 |
</tr> |
3867 |
|
3868 |
<tr> |
3869 |
<th> </th> |
3870 |
<th> </th> |
3871 |
<th> </th> |
3872 |
<th> </th> |
3873 |
</tr> |
3874 |
|
3875 |
<tr> |
3876 |
<ti>SGI Indigo2 Impact R10000</ti> |
3877 |
<ti>default-linux/mips/2006.1/ip28/o32</ti> |
3878 |
<ti>32-bit Linuxthreads</ti> |
3879 |
<ti>Recommended</ti> |
3880 |
</tr> |
3881 |
<tr> |
3882 |
<ti>"</ti> |
3883 |
<ti>default-linux/mips/2006.1/ip28/o32/nptl</ti> |
3884 |
<ti>32-bit NPTL</ti> |
3885 |
<ti>In Testing (1)</ti> |
3886 |
</tr> |
3887 |
<tr> |
3888 |
<ti>"</ti> |
3889 |
<ti>default-linux/mips/2006.1/ip28/n32</ti> |
3890 |
<ti>N32 Linuxthreads</ti> |
3891 |
<ti>Highly Experimental (2)</ti> |
3892 |
</tr> |
3893 |
<tr> |
3894 |
<ti>"</ti> |
3895 |
<ti>default-linux/mips/2006.1/ip28/n32/nptl</ti> |
3896 |
<ti>N32 NPTL</ti> |
3897 |
<ti>Highly Experimental (1) (2)</ti> |
3898 |
</tr> |
3899 |
|
3900 |
<tr> |
3901 |
<th> </th> |
3902 |
<th> </th> |
3903 |
<th> </th> |
3904 |
<th> </th> |
3905 |
</tr> |
3906 |
|
3907 |
<tr> |
3908 |
<ti>SGI Octane/Octane2</ti> |
3909 |
<ti>default-linux/mips/2006.1/ip30/o32</ti> |
3910 |
<ti>32-bit Linuxthreads</ti> |
3911 |
<ti>Recommended</ti> |
3912 |
</tr> |
3913 |
<tr> |
3914 |
<ti>"</ti> |
3915 |
<ti>default-linux/mips/2006.1/ip30/o32/nptl</ti> |
3916 |
<ti>32-bit NPTL</ti> |
3917 |
<ti>In Testing (1)</ti> |
3918 |
</tr> |
3919 |
<tr> |
3920 |
<ti>"</ti> |
3921 |
<ti>default-linux/mips/2006.1/ip30/n32</ti> |
3922 |
<ti>N32 Linuxthreads</ti> |
3923 |
<ti>Highly Experimental (2)</ti> |
3924 |
</tr> |
3925 |
<tr> |
3926 |
<ti>"</ti> |
3927 |
<ti>default-linux/mips/2006.1/ip30/n32/nptl</ti> |
3928 |
<ti>N32 NPTL</ti> |
3929 |
<ti>Highly Experimental (1) (2)</ti> |
3930 |
</tr> |
3931 |
</table> |
3932 |
|
3933 |
<impo> |
3934 |
(1) NPTL is in-testing on MIPS at this stage, requiring |
3935 |
<c>gcc-4.1</c> and <c>glibc-2.4</c>. These profiles |
3936 |
are a work-in-progress, and are not guaranteed to work. It is recommended that |
3937 |
people do not use these profiles until all the issues have been resolved. |
3938 |
</impo> |
3939 |
|
3940 |
<warn> |
3941 |
(2) n32 Userland is highly experimental, a lot of software has problems with |
3942 |
this ABI, and thus it is practically guaranteed that you will run into stability |
3943 |
problems at some point. Work is being done to improve the situation, however, |
3944 |
no support is offered if you use this profile, unless you're willing to help |
3945 |
fix problems by submitting patches. |
3946 |
</warn> |
3947 |
|
3948 |
<warn> |
3949 |
(3) n64 Userland at present is completely unsupported on all systems. At this |
3950 |
time there are no stages available that support n64, and this isn't likely to |
3951 |
change in the near future. |
3952 |
</warn> |
3953 |
|
3954 |
<p> |
3955 |
You can see what profile you are currently using with the following command: |
3956 |
</p> |
3957 |
|
3958 |
<pre caption="Verifying system profile"> |
3959 |
# <i>ls -FGg /etc/make.profile</i> |
3960 |
lrwxrwxrwx 1 48 Apr 8 18:51 /etc/make.profile -> ../usr/portage/profiles/default-linux/mips/2006.1/generic-be/o32/ |
3961 |
</pre> |
3962 |
|
3963 |
<p> |
3964 |
Having looked through the profiles above, and decided which one is the most |
3965 |
appropriate, you need to adjust your <path>make.profile</path> symlink to |
3966 |
reflect this. By default, the profiles are in |
3967 |
<path>/usr/portage/profiles</path>, so if you've moved your portage tree |
3968 |
elsewhere (not recommended), adjust the commands below accordingly. |
3969 |
</p> |
3970 |
|
3971 |
<pre caption="Setting the profile"> |
3972 |
<comment>(Delete the old profile symlink)</comment> |
3973 |
# <i>rm -f /etc/make.profile</i> |
3974 |
|
3975 |
<comment>(Create a new symlink pointing to your chosen profile ) |
3976 |
(For example, this is what one would use on an Indy or O2.)</comment> |
3977 |
# <i>ln -s /usr/portage/profiles/default-linux/mips/2006.1/generic-be/o32</i> |
3978 |
</pre> |
3979 |
|
3980 |
<note> |
3981 |
A tip for those not familiar with the Bourne Again Shell... If you partially |
3982 |
type a filename or command, then hit the TAB key, it will automatically fill out |
3983 |
the command/filename until the last common character. E.g. typing |
3984 |
<c>/usr/portage/profiles/def<TAB></c>, <c>bash</c> will automatically put |
3985 |
down <c>default-</c>. Pressing TAB a couple of more times will reveal the |
3986 |
possibilities, <c>default-linux</c>, <c>default-darwin</c> and |
3987 |
<c>default-bsd</c>. Give it a try, you'll find it very handy for navigating the |
3988 |
command line. |
3989 |
</note> |
3990 |
|
3991 |
</body> |
3992 |
</subsection> |
3993 |
<subsection id="configure_USE"> |
3994 |
<title>Configuring the USE variable</title> |
3995 |
<body> |
3996 |
|
3997 |
<p> |
3998 |
<c>USE</c> is one of the most powerful variables Gentoo provides to its users. |
3999 |
Several programs can be compiled with or without optional support for certain |
4000 |
items. For instance, some programs can be compiled with gtk-support, or with |
4001 |
qt-support. Others can be compiled with or without SSL support. Some programs |
4002 |
can even be compiled with framebuffer support (svgalib) instead of X11 support |
4003 |
(X-server). |
4004 |
</p> |
4005 |
|
4006 |
<p> |
4007 |
Most distributions compile their packages with support for as much as possible, |
4008 |
increasing the size of the programs and startup time, not to mention an enormous |
4009 |
amount of dependencies. With Gentoo you can define what options a package |
4010 |
should be compiled with. This is where <c>USE</c> comes into play. |
4011 |
</p> |
4012 |
|
4013 |
<p> |
4014 |
In the <c>USE</c> variable you define keywords which are mapped onto |
4015 |
compile-options. For instance, <e>ssl</e> will compile ssl-support in the |
4016 |
programs that support it. <e>-X</e> will remove X-server support (note the |
4017 |
minus sign in front). <e>gnome gtk -kde -qt3 -qt4</e> will compile your |
4018 |
programs with gnome (and gtk) support, and not with kde (and qt) support, |
4019 |
making your system fully tweaked for GNOME. |
4020 |
</p> |
4021 |
|
4022 |
<p> |
4023 |
The default <c>USE</c> settings are placed in the <path>make.defaults</path> |
4024 |
files of your profile. You will find <path>make.defaults</path> files in the |
4025 |
directory which <path>/etc/make.profile</path> points to and all parent |
4026 |
directories as well. The default <c>USE</c> setting is the sum of all <c>USE</c> |
4027 |
settings in all <path>make.defaults</path> files. What you place in |
4028 |
<path>/etc/make.conf</path> is calculated against these defaults settings. If |
4029 |
you add something to the <c>USE</c> setting, it is added to the default list. If |
4030 |
you remove something from the <c>USE</c> setting (by placing a minus sign in |
4031 |
front of it) it is removed from the default list (if it was in the default list |
4032 |
at all). <e>Never</e> alter anything inside the <path>/etc/make.profile</path> |
4033 |
directory; it gets overwritten when you update Portage! |
4034 |
</p> |
4035 |
|
4036 |
<p> |
4037 |
A full description on <c>USE</c> can be found in the second part of the Gentoo |
4038 |
Handbook, <uri link="?part=2&chap=2">USE flags</uri>. A full description on |
4039 |
the available USE flags can be found on your system in |
4040 |
<path>/usr/portage/profiles/use.desc</path>. |
4041 |
</p> |
4042 |
|
4043 |
<pre caption="Viewing available USE flags"> |
4044 |
# <i>less /usr/portage/profiles/use.desc</i> |
4045 |
<comment>(You can scroll using your arrow keys, exit by pressing 'q')</comment> |
4046 |
</pre> |
4047 |
|
4048 |
<p> |
4049 |
As an example we show a <c>USE</c> setting for a KDE-based system with DVD, ALSA |
4050 |
and CD Recording support: |
4051 |
</p> |
4052 |
|
4053 |
<pre caption="Opening /etc/make.conf"> |
4054 |
# <i>nano -w /etc/make.conf</i> |
4055 |
</pre> |
4056 |
|
4057 |
<pre caption="USE setting"> |
4058 |
USE="-gtk -gnome qt3 qt4 kde dvd alsa cdr" |
4059 |
</pre> |
4060 |
|
4061 |
</body> |
4062 |
</subsection> |
4063 |
<subsection> |
4064 |
<title>Optional: GLIBC Locales</title> |
4065 |
<body> |
4066 |
|
4067 |
<p> |
4068 |
You will probably only use one or maybe two locales on your system. You can |
4069 |
specify locales you will need in <path>/etc/locale.gen</path>. |
4070 |
</p> |
4071 |
|
4072 |
<pre caption="Opening /etc/locale.gen"> |
4073 |
# <i>nano -w /etc/locale.gen</i> |
4074 |
</pre> |
4075 |
|
4076 |
<p> |
4077 |
The following locales are an example to get both English (United States) and |
4078 |
German (Germany) with the accompanying character formats (like UTF-8). |
4079 |
</p> |
4080 |
|
4081 |
<pre caption="Specify your locales"> |
4082 |
en_US ISO-8859-1 |
4083 |
en_US.UTF-8 UTF-8 |
4084 |
de_DE ISO-8859-1 |
4085 |
de_DE@euro ISO-8859-15 |
4086 |
</pre> |
4087 |
|
4088 |
<p> |
4089 |
The next step is to run <c>locale-gen</c>. It will generate all the locales you |
4090 |
have specified in the <path>/etc/locale.gen</path> file. |
4091 |
</p> |
4092 |
|
4093 |
<note> |
4094 |
<c>locale-gen</c> is available in <c>glibc-2.3.6-r4</c> and newer. If you have |
4095 |
an older version of glibc, you should update it now. |
4096 |
</note> |
4097 |
|
4098 |
<p> |
4099 |
Now continue with <uri link="?part=1&chap=7">Configuring the Kernel</uri>. |
4100 |
</p> |
4101 |
|
4102 |
</body> |
4103 |
</subsection> |
4104 |
</section> |
4105 |
</sections> |
4106 |
|
4107 |
|
4108 |
|
4109 |
1.21 xml/htdocs/doc/en/handbook/draft/hb-install-network.xml |
4110 |
|
4111 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-network.xml?rev=1.21&view=markup |
4112 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-network.xml?rev=1.21&content-type=text/plain |
4113 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-network.xml?r1=1.20&r2=1.21 |
4114 |
|
4115 |
|
4116 |
|
4117 |
|
4118 |
1.14 xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-bootloader.xml |
4119 |
|
4120 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-bootloader.xml?rev=1.14&view=markup |
4121 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-bootloader.xml?rev=1.14&content-type=text/plain |
4122 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-bootloader.xml?r1=1.13&r2=1.14 |
4123 |
|
4124 |
|
4125 |
|
4126 |
|
4127 |
1.15 xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml |
4128 |
|
4129 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml?rev=1.15&view=markup |
4130 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml?rev=1.15&content-type=text/plain |
4131 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml?r1=1.14&r2=1.15 |
4132 |
|
4133 |
|
4134 |
|
4135 |
|
4136 |
1.13 xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-kernel.xml |
4137 |
|
4138 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-kernel.xml?rev=1.13&view=markup |
4139 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-kernel.xml?rev=1.13&content-type=text/plain |
4140 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-kernel.xml?r1=1.12&r2=1.13 |
4141 |
|
4142 |
|
4143 |
|
4144 |
|
4145 |
1.21 xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-medium.xml |
4146 |
|
4147 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-medium.xml?rev=1.21&view=markup |
4148 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-medium.xml?rev=1.21&content-type=text/plain |
4149 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-medium.xml?r1=1.20&r2=1.21 |
4150 |
|
4151 |
|
4152 |
|
4153 |
|
4154 |
1.25 xml/htdocs/doc/en/handbook/draft/hb-install-ppc-bootloader.xml |
4155 |
|
4156 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-bootloader.xml?rev=1.25&view=markup |
4157 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-bootloader.xml?rev=1.25&content-type=text/plain |
4158 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-bootloader.xml?r1=1.24&r2=1.25 |
4159 |
|
4160 |
|
4161 |
|
4162 |
|
4163 |
1.23 xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml |
4164 |
|
4165 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml?rev=1.23&view=markup |
4166 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml?rev=1.23&content-type=text/plain |
4167 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml?r1=1.22&r2=1.23 |
4168 |
|
4169 |
|
4170 |
|
4171 |
|
4172 |
1.28 xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml |
4173 |
|
4174 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml?rev=1.28&view=markup |
4175 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml?rev=1.28&content-type=text/plain |
4176 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-kernel.xml?r1=1.27&r2=1.28 |
4177 |
|
4178 |
|
4179 |
|
4180 |
|
4181 |
1.37 xml/htdocs/doc/en/handbook/draft/hb-install-ppc-medium.xml |
4182 |
|
4183 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-medium.xml?rev=1.37&view=markup |
4184 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-medium.xml?rev=1.37&content-type=text/plain |
4185 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-medium.xml?r1=1.36&r2=1.37 |
4186 |
|
4187 |
|
4188 |
|
4189 |
|
4190 |
1.14 xml/htdocs/doc/en/handbook/draft/hb-install-sparc-bootloader.xml |
4191 |
|
4192 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-bootloader.xml?rev=1.14&view=markup |
4193 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-bootloader.xml?rev=1.14&content-type=text/plain |
4194 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-bootloader.xml?r1=1.13&r2=1.14 |
4195 |
|
4196 |
|
4197 |
|
4198 |
|
4199 |
1.15 xml/htdocs/doc/en/handbook/draft/hb-install-sparc-disk.xml |
4200 |
|
4201 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-disk.xml?rev=1.15&view=markup |
4202 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-disk.xml?rev=1.15&content-type=text/plain |
4203 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-disk.xml?r1=1.14&r2=1.15 |
4204 |
|
4205 |
|
4206 |
|
4207 |
|
4208 |
1.17 xml/htdocs/doc/en/handbook/draft/hb-install-sparc-kernel.xml |
4209 |
|
4210 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-kernel.xml?rev=1.17&view=markup |
4211 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-kernel.xml?rev=1.17&content-type=text/plain |
4212 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-kernel.xml?r1=1.16&r2=1.17 |
4213 |
|
4214 |
|
4215 |
|
4216 |
|
4217 |
1.28 xml/htdocs/doc/en/handbook/draft/hb-install-sparc-medium.xml |
4218 |
|
4219 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-medium.xml?rev=1.28&view=markup |
4220 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-medium.xml?rev=1.28&content-type=text/plain |
4221 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-medium.xml?r1=1.27&r2=1.28 |
4222 |
|
4223 |
|
4224 |
|
4225 |
|
4226 |
1.43 xml/htdocs/doc/en/handbook/draft/hb-install-stage.xml |
4227 |
|
4228 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-stage.xml?rev=1.43&view=markup |
4229 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-stage.xml?rev=1.43&content-type=text/plain |
4230 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-stage.xml?r1=1.42&r2=1.43 |
4231 |
|
4232 |
|
4233 |
|
4234 |
|
4235 |
1.26 xml/htdocs/doc/en/handbook/draft/hb-install-system.xml |
4236 |
|
4237 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-system.xml?rev=1.26&view=markup |
4238 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-system.xml?rev=1.26&content-type=text/plain |
4239 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-system.xml?r1=1.25&r2=1.26 |
4240 |
|
4241 |
|
4242 |
|
4243 |
|
4244 |
1.20 xml/htdocs/doc/en/handbook/draft/hb-install-tools.xml |
4245 |
|
4246 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-tools.xml?rev=1.20&view=markup |
4247 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-tools.xml?rev=1.20&content-type=text/plain |
4248 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-tools.xml?r1=1.19&r2=1.20 |
4249 |
|
4250 |
|
4251 |
|
4252 |
|
4253 |
1.4 xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-bootloader.xml |
4254 |
|
4255 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-bootloader.xml?rev=1.4&view=markup |
4256 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-bootloader.xml?rev=1.4&content-type=text/plain |
4257 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-bootloader.xml?r1=1.3&r2=1.4 |
4258 |
|
4259 |
|
4260 |
|
4261 |
|
4262 |
1.5 xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-disk.xml |
4263 |
|
4264 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-disk.xml?rev=1.5&view=markup |
4265 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-disk.xml?rev=1.5&content-type=text/plain |
4266 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-disk.xml?r1=1.4&r2=1.5 |
4267 |
|
4268 |
|
4269 |
|
4270 |
|
4271 |
1.4 xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-kernel.xml |
4272 |
|
4273 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-kernel.xml?rev=1.4&view=markup |
4274 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-kernel.xml?rev=1.4&content-type=text/plain |
4275 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-kernel.xml?r1=1.3&r2=1.4 |
4276 |
|
4277 |
|
4278 |
|
4279 |
|
4280 |
1.4 xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-medium.xml |
4281 |
|
4282 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-medium.xml?rev=1.4&view=markup |
4283 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-medium.xml?rev=1.4&content-type=text/plain |
4284 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-medium.xml?r1=1.3&r2=1.4 |
4285 |
|
4286 |
|
4287 |
|
4288 |
|
4289 |
-- |
4290 |
gentoo-doc-cvs@g.o mailing list |