1 | <?xml version='1.0' encoding='UTF-8'?> |
1 | <?xml version='1.0' encoding='UTF-8'?> |
2 | <!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
2 | <!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
3 | |
3 | |
4 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
4 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
5 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
5 | <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
6 | |
6 | |
7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-medium.xml,v 1.12 2004/05/09 12:30:05 swift Exp $ --> |
7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-medium.xml,v 1.70 2012/06/29 15:57:32 swift Exp $ --> |
8 | |
8 | |
9 | <sections> |
9 | <sections> |
|
|
10 | |
|
|
11 | <abstract> |
|
|
12 | You can install Gentoo in many ways. This chapter explains how to install |
|
|
13 | Gentoo using the minimal Installation CD. |
|
|
14 | </abstract> |
|
|
15 | |
|
|
16 | <version>13</version> |
|
|
17 | <date>2012-06-29</date> |
|
|
18 | |
10 | <section> |
19 | <section> |
11 | <title>Hardware Requirements</title> |
20 | <title>Hardware Requirements</title> |
12 | <subsection> |
21 | <subsection> |
13 | <title>Introduction</title> |
22 | <title>Introduction</title> |
14 | <body> |
23 | <body> |
15 | |
24 | |
16 | <p> |
25 | <p> |
17 | Before we start, we first list what hardware requirements you need to |
26 | Before we start, we first list what hardware requirements you need to |
18 | successfully install Gentoo on your box. This of course depends on your |
27 | successfully install Gentoo on your box. |
19 | architecture. |
|
|
20 | </p> |
28 | </p> |
21 | |
29 | |
22 | </body> |
30 | </body> |
23 | </subsection> |
|
|
24 | <subsection> |
31 | </subsection> |
25 | <title>The PPC Architecture</title> |
32 | <subsection> |
|
|
33 | <title>Hardware Requirements</title> |
26 | <body> |
34 | <body> |
27 | |
35 | |
28 | <p> |
36 | <table> |
29 | Check the following requirements before you |
37 | <tr> |
30 | continue with the Gentoo installation: |
38 | <th>Apple NewWorld Machines</th> |
|
|
39 | <ti> |
|
|
40 | Power/PowerPC microprocessors (G3, G4, G5) such as iMac, eMac, iBook |
|
|
41 | PowerBook, Xserver, PowerMac |
|
|
42 | </ti> |
|
|
43 | </tr> |
|
|
44 | <tr> |
|
|
45 | <th>Apple OldWorld machines</th> |
|
|
46 | <ti> |
|
|
47 | Apple Machines with an Open Firmware revision less than 3, such as the Beige |
|
|
48 | G3s, PCI PowerMacs and PCI PowerBooks. PCI-based Apple Clones should also |
|
|
49 | be supported. |
|
|
50 | </ti> |
|
|
51 | </tr> |
|
|
52 | <tr> |
|
|
53 | <th>Genesi</th> |
|
|
54 | <ti> |
|
|
55 | Pegasos I/II, Open Desktop Workstation, Efika |
|
|
56 | </ti> |
|
|
57 | </tr> |
|
|
58 | <tr> |
|
|
59 | <th>IBM</th> |
|
|
60 | <ti> |
|
|
61 | RS/6000, iSeries, pSeries |
|
|
62 | </ti> |
|
|
63 | </tr> |
|
|
64 | <tr> |
|
|
65 | <th>Memory</th> |
|
|
66 | <ti>At least 64 MB</ti> |
|
|
67 | </tr> |
|
|
68 | <tr> |
|
|
69 | <th>Diskspace</th> |
|
|
70 | <ti>1.5 GB (excluding swap space)</ti> |
|
|
71 | </tr> |
|
|
72 | <tr> |
|
|
73 | <th>Swap space</th> |
|
|
74 | <ti>At least 256 MB</ti> |
|
|
75 | </tr> |
|
|
76 | </table> |
|
|
77 | |
31 | </p> |
78 | <p> |
32 | |
|
|
33 | <ul> |
|
|
34 | <li> |
|
|
35 | You need at least 1 Gb of free disk space |
|
|
36 | </li> |
|
|
37 | <li> |
|
|
38 | If you do not use prebuilt packages, you need at least 300 Mb of memory (RAM + |
|
|
39 | swap) |
|
|
40 | </li> |
|
|
41 | <li> |
|
|
42 | For the <e>PowerPC architecture</e>, you can install Gentoo/PPC on machines |
|
|
43 | having a Power or PowerPC microprocessor, including but not limited to G3, G4 |
|
|
44 | or G5 powered Apple computers such as the iMac, the iBook, the PowerBook, |
|
|
45 | Xserve, PowerMac, and bPlan's Pegasos I and II... We also provide limited |
|
|
46 | support for oldworld systems, IBM (rs/6000, iSeries, zSeries, ...) and Amiga |
|
|
47 | systems. Be sure to read up on the <uri link="/doc/en/gentoo-ppc-faq.xml">Gentoo |
79 | Be sure to read the <uri link="/doc/en/gentoo-ppc-faq.xml">Gentoo PPC FAQ</uri> |
48 | PPC FAQ</uri> too before you begin. |
80 | for help with some common installation related issues or if you're unsure as to |
49 | </li> |
81 | just what's in that PowerPC machine you've got sitting on your desk right now. |
50 | </ul> |
82 | </p> |
51 | |
83 | |
52 | </body> |
84 | </body> |
53 | </subsection> |
85 | </subsection> |
54 | </section> |
86 | </section> |
|
|
87 | |
|
|
88 | <!-- START --> |
55 | <section> |
89 | <section> |
56 | <title>Make your Choice</title> |
90 | <title>The Gentoo Installation CDs</title> |
57 | <subsection> |
91 | <subsection> |
58 | <title>Introduction</title> |
92 | <title>Introduction</title> |
59 | <body> |
93 | <body> |
60 | |
94 | |
61 | <p> |
95 | <p> |
62 | Still interested in trying out Gentoo? Well, then it is now time to |
|
|
63 | choose the installation medium you want to use. Yes, you have the |
|
|
64 | choice, no, they are not all equal, and yes, the result is always the same: a |
|
|
65 | Gentoo base system. |
|
|
66 | </p> |
|
|
67 | |
|
|
68 | <p> |
|
|
69 | The installation media we will describe are: |
|
|
70 | </p> |
|
|
71 | |
|
|
72 | <ul> |
|
|
73 | <li>Gentoo's Minimal LiveCD</li> |
|
|
74 | <li>Gentoo's Universal LiveCD</li> |
|
|
75 | </ul> |
|
|
76 | |
|
|
77 | <p> |
|
|
78 | Every single media has its advantages and disadvantages. We will list |
|
|
79 | the pros and cons of every medium so you have all the information to |
|
|
80 | make a justified decision. But before we continue, let's explain our |
|
|
81 | three-stage installation. |
|
|
82 | </p> |
|
|
83 | |
|
|
84 | </body> |
|
|
85 | </subsection> |
|
|
86 | <subsection> |
|
|
87 | <title>The Three Stages</title> |
|
|
88 | <body> |
|
|
89 | |
|
|
90 | <p> |
|
|
91 | Gentoo Linux can be installed using one of three <e>stage</e> tarball files. |
|
|
92 | The one you choose depends on how much of the system you want to compile |
|
|
93 | yourself. The <e>stage1</e> tarball is used when you want to bootstrap and |
|
|
94 | build the entire system from scratch. The <e>stage2</e> tarball is used for |
|
|
95 | building the entire system from a bootstrapped "semi-compiled" state. |
|
|
96 | The <e>stage3</e> tarball already contains a basic Gentoo Linux system that has |
|
|
97 | been built for you. As we will explain later, you can also install |
|
|
98 | Gentoo without compiling anything (except your kernel and some optional |
|
|
99 | packages). If you want this, you have to use a <e>stage3</e> tarball. |
|
|
100 | </p> |
|
|
101 | |
|
|
102 | <p> |
|
|
103 | Now what stage do you have to choose? |
|
|
104 | </p> |
|
|
105 | |
|
|
106 | <p> |
|
|
107 | Starting from a <e>stage1</e> allows you to have total control over the |
|
|
108 | optimization settings and optional build-time functionality that is |
|
|
109 | initially enabled on your system. This makes <e>stage1</e> installs good for |
|
|
110 | power users who know what they are doing. It is also a great |
|
|
111 | installation method for those who would like to know more about the |
|
|
112 | inner workings of Gentoo Linux. |
|
|
113 | </p> |
|
|
114 | |
|
|
115 | <p> |
|
|
116 | A <e>stage1</e> installation can only be performed when you have a working |
|
|
117 | Internet connection. |
|
|
118 | </p> |
|
|
119 | |
|
|
120 | <table> |
|
|
121 | <tr> |
|
|
122 | <th>Stage1</th> |
|
|
123 | <th>Pros and Cons</th> |
|
|
124 | </tr> |
|
|
125 | <tr> |
|
|
126 | <th>+</th> |
|
|
127 | <ti> |
|
|
128 | Allows you to have total control over the optimization settings and optional |
|
|
129 | build-time functionality that is initially enabled on your system |
|
|
130 | </ti> |
|
|
131 | </tr> |
|
|
132 | <tr> |
|
|
133 | <th>+</th> |
|
|
134 | <ti>Suitable for powerusers that know what they are doing</ti> |
|
|
135 | </tr> |
|
|
136 | <tr> |
|
|
137 | <th>+</th> |
|
|
138 | <ti>Allows you to learn more about the inner workings of Gentoo</ti> |
|
|
139 | </tr> |
|
|
140 | <tr> |
|
|
141 | <th>-</th> |
|
|
142 | <ti>Takes a long time to finish the installation</ti> |
|
|
143 | </tr> |
|
|
144 | <tr> |
|
|
145 | <th>-</th> |
|
|
146 | <ti> |
|
|
147 | If you don't intend to tweak the settings, it is probably a waste of time |
|
|
148 | </ti> |
|
|
149 | </tr> |
|
|
150 | <tr> |
|
|
151 | <th>-</th> |
|
|
152 | <ti> |
|
|
153 | Not suitable for networkless installations |
|
|
154 | </ti> |
|
|
155 | </tr> |
|
|
156 | </table> |
|
|
157 | |
|
|
158 | <p> |
|
|
159 | <e>Stage2</e> installs allow you to skip the bootstrap process and doing this |
|
|
160 | is fine if you are happy with the optimization settings that we chose |
|
|
161 | for your particular <e>stage2</e> tarball. |
|
|
162 | </p> |
|
|
163 | |
|
|
164 | <p> |
|
|
165 | A <e>stage2</e> installation can only be performed when you have a working |
|
|
166 | Internet connection. |
|
|
167 | </p> |
|
|
168 | |
|
|
169 | <table> |
|
|
170 | <tr> |
|
|
171 | <th>Stage2</th> |
|
|
172 | <th>Pros and Cons</th> |
|
|
173 | </tr> |
|
|
174 | <tr> |
|
|
175 | <th>+</th> |
|
|
176 | <ti>You don't need to bootstrap</ti> |
|
|
177 | </tr> |
|
|
178 | <tr> |
|
|
179 | <th>+</th> |
|
|
180 | <ti>Faster than starting with stage1</ti> |
|
|
181 | </tr> |
|
|
182 | <tr> |
|
|
183 | <th>+</th> |
|
|
184 | <ti>You can still tweak your settings</ti> |
|
|
185 | </tr> |
|
|
186 | <tr> |
|
|
187 | <th>-</th> |
|
|
188 | <ti>You cannot tweak as much as with a stage1</ti> |
|
|
189 | </tr> |
|
|
190 | <tr> |
|
|
191 | <th>-</th> |
|
|
192 | <ti>It's not the fastest way to install Gentoo</ti> |
|
|
193 | </tr> |
|
|
194 | <tr> |
|
|
195 | <th>-</th> |
|
|
196 | <ti>You have to accept the optimizations we chose for the bootstrap</ti> |
|
|
197 | </tr> |
|
|
198 | <tr> |
|
|
199 | <th>-</th> |
|
|
200 | <ti> |
|
|
201 | Not suitable for networkless installations |
|
|
202 | </ti> |
|
|
203 | </tr> |
|
|
204 | </table> |
|
|
205 | |
|
|
206 | <p> |
|
|
207 | Choosing to go with a <e>stage3</e> allows for the fastest install of Gentoo |
|
|
208 | Linux, but also means that your base system will have the optimization |
|
|
209 | settings that we chose for you (which to be honest, are good settings |
|
|
210 | and were carefully chosen to enhance performance while maintaining |
|
|
211 | stability). <e>stage3</e> is also required if you want to install Gentoo using |
|
|
212 | prebuilt packages or without a network connection. |
|
|
213 | </p> |
|
|
214 | |
|
|
215 | <table> |
|
|
216 | <tr> |
|
|
217 | <th>Stage3</th> |
|
|
218 | <th>Pros and Cons</th> |
|
|
219 | </tr> |
|
|
220 | <tr> |
|
|
221 | <th>+</th> |
|
|
222 | <ti>Fastest way to get a Gentoo base system</ti> |
|
|
223 | </tr> |
|
|
224 | <tr> |
|
|
225 | <th>+</th> |
|
|
226 | <ti>Suitable for networkless installations</ti> |
|
|
227 | </tr> |
|
|
228 | <tr> |
|
|
229 | <th>-</th> |
|
|
230 | <ti>You cannot tweak the base system - it's built already</ti> |
|
|
231 | </tr> |
|
|
232 | <tr> |
|
|
233 | <th>-</th> |
|
|
234 | <ti>You cannot brag about having used stage1 or stage2</ti> |
|
|
235 | </tr> |
|
|
236 | </table> |
|
|
237 | |
|
|
238 | <p> |
|
|
239 | Write down (or remember) what stage you want to use. You need this later when |
|
|
240 | you decide what LiveCD (or other installation medium) you want to use. You might |
|
|
241 | be interested to know that, if you decide to use different optimization settings |
|
|
242 | after having installed Gentoo, you will be able to recompile your entire system |
|
|
243 | with the new optimization settings. |
|
|
244 | </p> |
|
|
245 | |
|
|
246 | <p> |
|
|
247 | Now take a look at the available installation media. |
|
|
248 | </p> |
|
|
249 | |
|
|
250 | </body> |
|
|
251 | </subsection> |
|
|
252 | <subsection> |
|
|
253 | <title>Gentoo LiveCDs</title> |
|
|
254 | <body> |
|
|
255 | |
|
|
256 | <p> |
|
|
257 | The <e>Gentoo LiveCDs</e> are bootable CDs which contain a |
96 | The <e>Gentoo Installation CDs</e> are bootable CDs which contain a |
258 | self-sustained Gentoo environment. They allow you to boot Linux from the CD. |
97 | self-sustained Gentoo environment. They allow you to boot Linux from the CD. |
259 | During the boot process your hardware is detected and the appropriate drivers |
98 | During the boot process your hardware is detected and the appropriate drivers |
260 | are loaded. They are maintained by Gentoo developers. |
99 | are loaded. They are maintained by Gentoo developers. |
261 | </p> |
100 | </p> |
262 | |
101 | |
263 | <p> |
102 | <p> |
264 | All LiveCDs allow you to boot, setup networking, initialize your |
103 | All Installation CDs allow you to boot, set up networking, initialize your |
265 | partitions and start installing Gentoo from the Internet. However, some |
104 | partitions and start installing Gentoo from the Internet. |
266 | LiveCDs also contain all necessary source code so you are able to install |
|
|
267 | Gentoo without a working network configuration. |
|
|
268 | </p> |
|
|
269 | |
|
|
270 | <p> |
105 | </p> |
271 | Now what do these LiveCDs contain? |
106 | |
|
|
107 | <!-- |
|
|
108 | <impo> |
|
|
109 | If you wish to install Gentoo without a working Internet connection, or would |
|
|
110 | like to use one of the provided installers, please use the installation |
|
|
111 | instructions described in the <uri link="2008.0/">Gentoo 2008.0 |
|
|
112 | Handbooks</uri>. |
|
|
113 | </impo> |
|
|
114 | --> |
|
|
115 | <!-- |
272 | </p> |
116 | <p> |
|
|
117 | The Installation CDs that we currently provide are: |
|
|
118 | </p> |
273 | |
119 | |
|
|
120 | <ul> |
|
|
121 | <li> |
|
|
122 | The Gentoo <e>Minimal</e> Installation CD, a small, no-nonsense, bootable |
|
|
123 | CD which sole purpose is to boot the system, prepare the networking and |
|
|
124 | continue with the Gentoo installation. |
|
|
125 | </li> |
|
|
126 | <li> |
|
|
127 | The Universal Installation CD contains everything you need to install |
|
|
128 | Gentoo. It provides stage3 files for common architectures, source code |
|
|
129 | for the extra applications you need to choose from and, of course, the |
|
|
130 | installation instructions for your architecture. |
|
|
131 | </li> |
|
|
132 | </ul> |
|
|
133 | |
|
|
134 | <p> |
|
|
135 | Gentoo also provides a Package CD. This is not an Installation CD but an |
|
|
136 | additional resource that you can exploit during the installation of your Gentoo |
|
|
137 | system. It contains prebuilt packages (also known as the GRP set) that allow |
|
|
138 | you to easily and quickly install additional applications (such as |
|
|
139 | OpenOffice.org, KDE, GNOME, ...) immediately after the Gentoo installation and |
|
|
140 | right before you update your Portage tree. |
|
|
141 | </p> |
|
|
142 | |
|
|
143 | <p> |
|
|
144 | The use of the Package CD is covered later in this document. |
|
|
145 | </p> |
|
|
146 | --> |
274 | </body> |
147 | </body> |
275 | </subsection> |
|
|
276 | <subsection> |
148 | </subsection> |
|
|
149 | <subsection> |
277 | <title>Gentoo's Minimal LiveCD</title> |
150 | <title>Gentoo Minimal Installation CD</title> |
278 | <body> |
151 | <body> |
279 | |
152 | |
280 | <p> |
|
|
281 | This is a small, no-nonsense, bootable CD which sole purpose is to boot the |
|
|
282 | system, prepare the networking and continue with the Gentoo installation. It |
|
|
283 | does not contain any stages (or, in some cases, a single stage1 file), |
|
|
284 | source code or precompiled packages. For example the ppc variant of this |
|
|
285 | LiveCD can be found in the <path>universal</path> subdirectory and is called |
|
|
286 | <c>install-ppc-minimal-2004.1.iso</c>. |
|
|
287 | </p> |
153 | <p> |
288 | |
154 | The Minimal Installation CD is called <c><keyval id="min-cd-name"/></c> and |
|
|
155 | takes up around <keyval id="min-cd-size"/> MB of diskspace. You can use this |
|
|
156 | Installation CD to install Gentoo, but <e>only</e> with a working Internet |
|
|
157 | connection. |
|
|
158 | </p> |
|
|
159 | <!-- |
289 | <table> |
160 | <table> |
290 | <tr> |
161 | <tr> |
291 | <th>Minimal LiveCD</th> |
162 | <th>Minimal Installation CD</th> |
292 | <th>Pros and Cons</th> |
163 | <th>Pros and Cons</th> |
293 | </tr> |
164 | </tr> |
294 | <tr> |
165 | <tr> |
295 | <th>+</th> |
166 | <th>+</th> |
296 | <ti>Smallest download</ti> |
167 | <ti>Smallest download</ti> |
297 | </tr> |
168 | </tr> |
298 | <tr> |
169 | <tr> |
299 | <th>+</th> |
|
|
300 | <ti>Suitable for a complete architecture</ti> |
|
|
301 | </tr> |
|
|
302 | <tr> |
|
|
303 | <th>+</th> |
|
|
304 | <ti> |
|
|
305 | You can do a stage1, stage2 or stage3 by getting the stage tarball off the |
|
|
306 | net |
|
|
307 | </ti> |
|
|
308 | </tr> |
|
|
309 | <tr> |
|
|
310 | <th>-</th> |
170 | <th>-</th> |
311 | <ti> |
171 | <ti> |
312 | Contains no stages, no portage snapshot, no GRP packages and therefore not |
172 | Contains no stage3 tarball, no Portage snapshot, no prebuilt packages and |
313 | suitable for networkless installation |
173 | is therefore not suitable for networkless installation |
314 | </ti> |
174 | </ti> |
315 | </tr> |
175 | </tr> |
316 | </table> |
176 | </table> |
317 | |
177 | --> |
318 | </body> |
178 | </body> |
319 | </subsection> |
|
|
320 | <subsection> |
179 | </subsection> |
321 | <title>Gentoo's Universal LiveCD</title> |
180 | <subsection> |
|
|
181 | <title>The Stage3 Tarball</title> |
322 | <body> |
182 | <body> |
323 | |
183 | |
324 | <p> |
|
|
325 | Gentoo's Universal LiveCD is a bootable CD suitable to install Gentoo without |
|
|
326 | networking. It contains a stage1 and several stage3 tarballs (optimized for the |
|
|
327 | individual subarchitectures). For example the ppc variant of this CD is called |
|
|
328 | <c>install-ppc-universal-2004.1.iso</c> and can be found in the |
|
|
329 | <path>universal</path> subdirectory. |
|
|
330 | </p> |
184 | <p> |
331 | |
185 | A stage3 tarball is an archive containing a minimal Gentoo environment, |
|
|
186 | suitable to continue the Gentoo installation using the instructions in this |
|
|
187 | manual. Previously, the Gentoo Handbook described the installation using one of |
|
|
188 | three stage tarballs. While Gentoo still offers stage1 and stage2 tarballs, the |
|
|
189 | official installation method uses the stage3 tarball. If you are interested in |
|
|
190 | performing a Gentoo installation using a stage1 or stage2 tarball, please read |
|
|
191 | the Gentoo FAQ on <uri link="/doc/en/faq.xml#stage12">How do I Install Gentoo |
|
|
192 | Using a Stage1 or Stage2 Tarball?</uri> |
332 | <p> |
193 | </p> |
333 | If you take a closer look on our mirrors, you will see |
194 | |
334 | that we provide <e>Gentoo Package CDs</e>. This CD (which isn't |
|
|
335 | bootable) only contains precompiled packages and can be used to install software |
|
|
336 | after a succesfull Gentoo Installation. To install Gentoo, you only |
|
|
337 | need the Universal LiveCD, but if you want OpenOffice.org, Mozilla, KDE, GNOME |
|
|
338 | etc. without having to compile every single one of them, you need the Packages |
|
|
339 | CD too. For example the G4 (a subarchitecture of ppc) Packages CD is |
|
|
340 | called <c>packages-g4-2004.1.iso</c> and can be found in the appropriate |
|
|
341 | subdirectory (<path>g4/</path>). |
|
|
342 | </p> |
195 | <p> |
343 | |
196 | Stage3 tarballs can be downloaded from <path><keyval |
|
|
197 | id="release-dir"/>current-stage3/</path> on any of the <uri |
|
|
198 | link="/main/en/mirrors.xml">Official Gentoo Mirrors</uri> and are not provided |
|
|
199 | on the LiveCD. |
344 | <p> |
200 | </p> |
345 | You only need the Packages CD if you want to perform a stage3 with GRP |
|
|
346 | installation. |
|
|
347 | </p> |
|
|
348 | |
|
|
349 | <table> |
|
|
350 | <tr> |
|
|
351 | <th>Universal LiveCD with Packages CD</th> |
|
|
352 | <th>Pros and Cons</th> |
|
|
353 | </tr> |
|
|
354 | <tr> |
|
|
355 | <th>+</th> |
|
|
356 | <ti>Packages CD is optimized to your architecture and subarchitecture</ti> |
|
|
357 | </tr> |
|
|
358 | <tr> |
|
|
359 | <th>+</th> |
|
|
360 | <ti> |
|
|
361 | Packages CD provides precompiled packages for fast Gentoo installations |
|
|
362 | </ti> |
|
|
363 | </tr> |
|
|
364 | <tr> |
|
|
365 | <th>+</th> |
|
|
366 | <ti> |
|
|
367 | Contains everything you need. You can even install without a network |
|
|
368 | connection. |
|
|
369 | </ti> |
|
|
370 | </tr> |
|
|
371 | <tr> |
|
|
372 | <th>-</th> |
|
|
373 | <ti>Huge download</ti> |
|
|
374 | </tr> |
|
|
375 | </table> |
|
|
376 | |
201 | |
377 | </body> |
202 | </body> |
378 | </subsection> |
203 | </subsection> |
379 | </section> |
204 | </section> |
|
|
205 | |
|
|
206 | |
|
|
207 | <!-- STOP --> |
380 | <section> |
208 | <section> |
381 | <title>Download, Burn and Boot a Gentoo LiveCD</title> |
209 | <title>Download, Burn and Boot a Gentoo Installation CD</title> |
382 | <subsection> |
210 | <subsection> |
383 | <title>Downloading and Burning the LiveCDs</title> |
211 | <title>Downloading and Burning the Installation CDs</title> |
384 | <body> |
212 | <body> |
385 | |
213 | |
386 | <p> |
|
|
387 | You have chosen to use a Gentoo LiveCD (if not, then you are reading the |
|
|
388 | wrong section). We'll first start by downloading and burning the chosen |
|
|
389 | LiveCD. We previously discussed the several available LiveCDs, but where can you |
|
|
390 | find them? |
|
|
391 | </p> |
214 | <p> |
392 | |
215 | You have chosen to use a Gentoo Installation CD. We'll first start by |
|
|
216 | downloading and burning the chosen Installation CD. We previously discussed |
|
|
217 | the several available Installation CDs, but where can you find them? |
393 | <p> |
218 | </p> |
394 | Visit one of our <uri |
219 | |
395 | link="/main/en/mirrors.xml">mirrors</uri> and go to |
|
|
396 | <path>releases/ppc/2004.1/livecd/universal</path>, which is |
|
|
397 | the path where the LiveCD(s) of your choice are located. Inside that |
|
|
398 | directory you'll find so-called ISO-files. Those are full CD images |
|
|
399 | which you can write on a CD-R. |
|
|
400 | </p> |
220 | <p> |
401 | |
221 | You can download any of the Installation CDs from one of our <uri |
|
|
222 | link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located in |
|
|
223 | the <path><keyval id="release-dir"/>current-iso/</path> directory. |
402 | <p> |
224 | </p> |
|
|
225 | |
|
|
226 | <p> |
|
|
227 | Inside that directory you'll find ISO files. Those are full CD images which you |
|
|
228 | can write on a CD-R. |
|
|
229 | </p> |
|
|
230 | |
|
|
231 | <p> |
403 | In case you wonder if your downloaded file is corrupted or not, you can |
232 | In case you wonder if your downloaded file is corrupted or not, you can check |
404 | check its MD5 checksum and compare it with the MD5 checksum we provide (such as |
233 | its MD5 checksum and compare it with the MD5 checksum we provide (such as |
405 | <path>install-ppc-minimal-2004.1.iso.md5</path>). You can check the MD5 checksum |
234 | <path><keyval id="min-cd-name"/>.DIGESTS</path>). You can check the MD5 |
406 | with the <c>md5sum</c> tool under Linux/Unix or <uri |
235 | checksum with the <c>md5sum</c> tool under Linux/Unix or <uri |
407 | link="http://www.md5summer.org">md5summer</uri> for Windows. |
236 | link="http://www.etree.org/md5com.html">md5sum</uri> for Windows. |
408 | </p> |
237 | </p> |
409 | |
238 | |
410 | <p> |
239 | <p> |
411 | Another way to check the validity of the downloaded file is to use GnuPG to |
240 | Another way to check the validity of the downloaded file is to use GnuPG to |
412 | verify the cryptographic signature that we provide (the file ending with |
241 | verify the cryptographic signature that we provide (the file ending with |
413 | <path>.asc</path>). Download the signature file and obtain the public key: |
242 | <path>.asc</path>). Download the signature file and obtain the public keys whose |
|
|
243 | key ids can be found on the <uri link="/proj/en/releng/index.xml">release |
|
|
244 | engineering project site</uri>. |
414 | </p> |
245 | </p> |
415 | |
246 | |
416 | <pre caption="Obtaining the public key"> |
247 | <pre caption="Obtaining the public key"> |
417 | $ <i>gpg --keyserver pgp.mit.edu --recv-keys 19462D47</i> |
248 | <comment>(... Substitute the key ids with those mentioned on the release engineering site ...)</comment> |
|
|
249 | $ <i>gpg --keyserver subkeys.pgp.net --recv-keys 96D8BF6D 2D182910 17072058</i> |
418 | </pre> |
250 | </pre> |
419 | |
251 | |
420 | <p> |
252 | <p> |
421 | Now verify the signature: |
253 | Now verify the signature: |
422 | </p> |
254 | </p> |
423 | |
255 | |
424 | <pre caption="Verify the cryptographic signature"> |
256 | <pre caption="Verify the files"> |
425 | $ <i>gpg --verify <signature file> <downloaded iso></i> |
257 | <comment>(Verify the cryptographic signature)</comment> |
426 | <comment>(If everything goes well, you should see something like this:)</comment> |
258 | $ <i>gpg --verify <downloaded iso.DIGESTS.asc></i> |
427 | gpg: Signature made Mon Apr 19 18:54:40 2004 EDT using DSA key ID 19462D47 |
259 | <comment>(Verify the checksum)</comment> |
428 | gpg: Good signature from "John Davis (Gentoo Linux Developer) <zhen@gentoo.org>" |
260 | $ <i>sha1sum -c <downloaded iso.DIGESTS.asc></i> |
429 | gpg: aka "Gentoo Linux Release Engineering <releng@gentoo.org>" |
|
|
430 | </pre> |
261 | </pre> |
431 | |
262 | |
432 | <p> |
263 | <p> |
433 | To burn the downloaded ISO(s), you have to select raw-burning. How you |
264 | To burn the downloaded ISO(s), you have to select raw-burning. How you |
434 | do this is highly program-dependent. We will discuss a couple of popular |
265 | do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
435 | tools on how to do this. |
266 | <c>K3B</c> here; more information can be found in our <uri |
|
|
267 | link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
436 | </p> |
268 | </p> |
437 | |
269 | |
438 | <ul> |
270 | <ul> |
439 | <li> |
271 | <li> |
440 | With EasyCD Creator you select <c>File</c>, <c>Record CD |
272 | With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
441 | from CD image</c>. Then you change the <c>Files of type</c> to <c>ISO image |
273 | file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
442 | file</c>. Then locate the ISO file and click <c>Open</c>. When you click on |
274 | path). |
443 | <c>Start recording</c> the ISO image will be burned correctly onto the CD-R. |
|
|
444 | </li> |
275 | </li> |
445 | <li> |
276 | <li> |
446 | With Nero Burning ROM, select <c>File</c>, <c>Burn CD image</c>. Set the |
|
|
447 | type of file to <c>*.*</c> and select the ISO file. Older versions of Nero |
|
|
448 | will tell you they don't recognize the format -- confirm here, it does |
|
|
449 | recognize it but doesn't know it yet :) In the next dialog, set the |
|
|
450 | following parameters: |
|
|
451 | <ul> |
|
|
452 | <li>Type of image: <c>Data Mode 1</c></li> |
|
|
453 | <li>Block size: <c>2048 bytes</c></li> |
|
|
454 | <li>File precursor and length of the image trailer: <c>0 bytes</c></li> |
|
|
455 | <li>Scrambled: <c>no</c></li> |
|
|
456 | <li>Swapped: <c>no</c></li> |
|
|
457 | </ul> |
|
|
458 | Now click on <c>OK</c> and then <c>Burn</c> (the CD-R) |
|
|
459 | </li> |
|
|
460 | <li> |
|
|
461 | With cdrecord, you simply type <c>cdrecord dev=/dev/hdc</c> (replace |
|
|
462 | <path>/dev/hdc</path> with your CD-RW drive's device path) followed |
|
|
463 | by the path to the ISO file :) |
|
|
464 | </li> |
|
|
465 | <li> |
|
|
466 | With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
277 | With K3B, select <c>Tools</c> > <c>Burn CD Image</c>. Then you can locate |
467 | you can locate your ISO file within the 'Image to Burn' area. Finally click |
278 | your ISO file within the 'Image to Burn' area. Finally click <c>Start</c>. |
468 | <c>Start</c>. |
|
|
469 | </li> |
|
|
470 | <li> |
|
|
471 | With Mac OS X Panther, launch <c>Disk Utility</c> from |
|
|
472 | <path>Applications/Utilities</path>, select <c>Open</c> from the |
|
|
473 | <c>Images</c> menu, select the mounted disk image in the main window and |
|
|
474 | select <c>Burn</c> in the <c>Images</c> menu. |
|
|
475 | </li> |
|
|
476 | <li> |
|
|
477 | With Mac OS X Jaguar, launch <c>Disk Copy</c> from |
|
|
478 | <path>Applications/Utilities</path>, select <c>Burn Image</c> from the |
|
|
479 | <c>File</c> menu, select the ISO and click the <c>Burn</c> button. |
|
|
480 | </li> |
279 | </li> |
481 | </ul> |
280 | </ul> |
482 | |
281 | |
483 | </body> |
282 | </body> |
484 | </subsection> |
283 | </subsection> |
485 | </section> |
|
|
486 | <section> |
284 | <subsection> |
487 | <title>Booting the PPC LiveCD(s)</title> |
285 | <title>Default: Booting the Installation CD with Yaboot</title> |
488 | <subsection> |
|
|
489 | <title>Default: Apple/IBM</title> |
|
|
490 | <body> |
286 | <body> |
491 | |
287 | |
492 | <p> |
|
|
493 | Place the LiveCD in the CD-ROM and reboot the system. Hold down the 'C' key at |
|
|
494 | bootup (or run an OldWorld bootloader like BootX or quik). You will be greeted |
|
|
495 | by a friendly welcome message and a <e>boot:</e> prompt at the bottom of the |
|
|
496 | screen. |
|
|
497 | </p> |
288 | <p> |
498 | |
289 | On NewWorld machines place the Installation CD in the CD-ROM and reboot the |
|
|
290 | system. When the system-start-bell sounds, simply hold down the 'C' until the |
|
|
291 | CD loads. |
499 | <p> |
292 | </p> |
500 | At this prompt you are able to select a kernel for the subarchitecture you use. |
293 | |
501 | We provide <c>G3</c>, <c>G3-SMP</c>, <c>G4</c>, <c>G4-SMP</c>, <c>G5</c>, |
|
|
502 | <c>G5-SMP</c> and <c>G</c>. The various <c>-SMP</c> kernels are needed if your |
|
|
503 | system has multiple CPUs. |
|
|
504 | </p> |
294 | <p> |
505 | |
295 | After the Installation CD loaded, you will be greeted by a friendly welcome |
|
|
296 | message and a <e>boot:</e> prompt at the bottom of the screen. |
506 | <p> |
297 | </p> |
|
|
298 | |
|
|
299 | <p> |
|
|
300 | We provide one generic kernel, <e>ppc32</e>. This kernel is built with support |
|
|
301 | for multiple CPUs, but it will boot on single processor machines as well. |
|
|
302 | </p> |
|
|
303 | |
|
|
304 | <p> |
507 | You are also able to tweak some kernel options at this prompt. The following |
305 | You can tweak some kernel options at this prompt. The following table lists |
508 | table lists the available boot options you can add: |
306 | some of the available boot options you can add: |
509 | </p> |
307 | </p> |
510 | |
308 | |
511 | <table> |
309 | <table> |
512 | <tr> |
310 | <tr> |
513 | <th>Boot Option</th> |
311 | <th>Boot Option</th> |
… | |
… | |
515 | </tr> |
313 | </tr> |
516 | <tr> |
314 | <tr> |
517 | <ti><c>video</c></ti> |
315 | <ti><c>video</c></ti> |
518 | <ti> |
316 | <ti> |
519 | This option takes one of the following vendor-specific tags: |
317 | This option takes one of the following vendor-specific tags: |
520 | <c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, <c>aty128</c> or |
318 | <c>nvidiafb</c>, <c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, |
521 | <c>ofonly</c>. You can follow this tag with the resolution and refreshrate |
319 | <c>aty128</c> or <c>ofonly</c>. You can follow this tag with the resolution |
522 | you want to use. For instance <c>video=radeonfb:1280x1024@75</c>. If you are |
320 | refresh rate and color depth you want to use. For instance, |
523 | uncertain what to choose, <c>ofonly</c> will most certainly work. |
321 | <c>video=radeonfb:1280x1024@75-32</c> will select the ATI Radeon frame buffer |
|
|
322 | at a resolution of 1280x1024 with a refresh rate of 75Hz and a color depth of |
|
|
323 | 32 bits. If you are uncertain what to choose, and the default doesn't work, |
|
|
324 | <c>video=ofonly</c> will most certainly work. |
524 | </ti> |
325 | </ti> |
525 | </tr> |
326 | </tr> |
526 | <tr> |
327 | <tr> |
527 | <ti><c>nol3</c></ti> |
328 | <ti><c>nol3</c></ti> |
528 | <ti> |
329 | <ti> |
529 | Disables level 3 cache on some powerbooks (needed for at least the 17'') |
330 | Disables level 3 cache on some PowerBooks (needed for at least the 17") |
530 | </ti> |
|
|
531 | </tr> |
|
|
532 | <tr> |
|
|
533 | <ti><c>debug</c></ti> |
|
|
534 | <ti> |
331 | </ti> |
535 | Enables verbose booting, spawns an initrd shell that can be used to debug |
332 | </tr> |
536 | the LiveCD |
333 | <tr> |
|
|
334 | <ti><c>dofirewire</c></ti> |
537 | </ti> |
335 | <ti> |
538 | </tr> |
336 | Enables support for IEEE1394 (FireWire) devices, like external harddisks. |
539 | <tr> |
|
|
540 | <ti><c>sleep=X</c></ti> |
|
|
541 | <ti> |
337 | </ti> |
542 | Wait X seconds before continuing; this can be needed by some very old SCSI |
338 | </tr> |
543 | CD-ROMs which don't speed up the CD quick enough |
339 | <tr> |
|
|
340 | <ti><c>dopcmcia</c></ti> |
544 | </ti> |
341 | <ti> |
545 | </tr> |
342 | If you want to use PCMCIA devices during your installation (like PCMCIA |
546 | <tr> |
343 | network cards) you have to enable this option. |
547 | <ti><c>bootfrom=X</c></ti> |
|
|
548 | <ti> |
344 | </ti> |
549 | Boot from a different device |
345 | </tr> |
|
|
346 | <tr> |
|
|
347 | <ti><c>dosshd</c></ti> |
|
|
348 | <ti>Starts <c>sshd</c>. Useful for unattended installs.</ti> |
|
|
349 | </tr> |
|
|
350 | <tr> |
|
|
351 | <ti><c>passwd=foo</c></ti> |
|
|
352 | <ti> |
|
|
353 | Sets whatever is after the = as the root password. Use with <c>dosshd</c> |
|
|
354 | for remote installs. |
550 | </ti> |
355 | </ti> |
551 | </tr> |
356 | </tr> |
552 | </table> |
357 | </table> |
553 | |
358 | |
554 | <p> |
359 | <p> |
555 | At this prompt, hit enter, and a complete Gentoo Linux environment will be |
360 | To use the above options, at the <e>boot:</e> prompt, type <e>ppc32</e> followed |
556 | loaded from the CD. Continue with <uri link="#booted">And When You're |
361 | by the desired option. In the example below, we'll force the kernel to use the |
557 | Booted...</uri>. |
362 | Open Firmware framebuffer instead of the device specific driver. |
|
|
363 | </p> |
|
|
364 | |
|
|
365 | <pre caption="Force the use of the Open Firmware framebuffer"> |
|
|
366 | boot: <i>ppc32 video=ofonly</i> |
|
|
367 | </pre> |
|
|
368 | |
558 | </p> |
369 | <p> |
|
|
370 | If you don't need to add any options, just type ppc32 at this prompt, and a |
|
|
371 | complete Gentoo Linux environment will be loaded from the CD. Continue with |
|
|
372 | <uri link="#booted">And When You're Booted...</uri>. |
|
|
373 | </p> |
559 | |
374 | |
560 | </body> |
375 | </body> |
561 | </subsection> |
|
|
562 | <subsection> |
376 | </subsection> |
563 | <title>Alternative: Pegasos</title> |
377 | <subsection> |
|
|
378 | <title>Alternative: Booting the Installation CD on a Pegasos</title> |
564 | <body> |
379 | <body> |
565 | |
380 | |
566 | <p> |
381 | <p> |
567 | On the Pegasos simply insert the CD and at the SmartFirmware boot-prompt type |
382 | On the Pegasos simply insert the CD and at the SmartFirmware boot-prompt type |
568 | <c>boot cd /boot/pegasos root=/dev/ram0 init=/linuxrc looptype=gcloop |
383 | <c>boot cd /boot/menu</c>. This will open a small bootmenu where you can choose |
569 | cdroot</c>. If you need any special boot options you can append them to the |
384 | between several preconfigured video configs. If you need any special boot |
570 | command-line. For instance <c>boot cd /boot/pegasos root=/dev/ram0 |
385 | options you can append them to the command-line just like with Yaboot above. |
571 | init=/linuxrc looptype=gcloop cdroot video=radeonfb:1280x1024@75 mem=256M</c>. |
386 | For example: <c>boot cd /boot/pegasos video=radeonfb:1280x1024@75 mem=256M</c>. |
|
|
387 | The default kernel options (in case something goes wrong and you need it) are |
|
|
388 | preconfigured with <c>console=ttyS0,115200 console=tty0 init=/linuxrc |
|
|
389 | looptype=squashfs loop=/image.squashfs cdroot root=/dev/ram0</c>. |
572 | </p> |
390 | </p> |
573 | |
391 | |
574 | </body> |
392 | </body> |
|
|
393 | </subsection> |
|
|
394 | |
575 | </subsection> |
395 | <subsection> |
|
|
396 | <title>Alternative: Booting the Installation CD with BootX</title> |
|
|
397 | <body> |
|
|
398 | |
|
|
399 | <p> |
|
|
400 | If you have an OldWorld Mac the bootable portion of the livecd can't be used. |
|
|
401 | The most simple solution is to use MacOS 9 or earlier to bootstrap into a Linux |
|
|
402 | environment with a tool called BootX. |
|
|
403 | </p> |
|
|
404 | |
|
|
405 | <p> |
|
|
406 | First, download <uri link="http://penguinppc.org/bootloaders/bootx/">BootX</uri> |
|
|
407 | and unpack the archive. Copy the the <c>BootX Extension</c> from the unpacked |
|
|
408 | archive into <c>Extensions Folder</c> and the BootX App Control Panel into |
|
|
409 | <c>Control Panels</c>, both of which are located in your MacOS System Folder. |
|
|
410 | Next, create a folder called "Linux Kernels" in your System folder and copy the |
|
|
411 | <c>ppc32</c> kernel from the CD to this folder. Finally, copy <c>ppc32.igz</c> |
|
|
412 | from the Installation CD <path>boot</path> folder into the MacOS |
|
|
413 | <c>System Folder</c>. |
|
|
414 | </p> |
|
|
415 | |
|
|
416 | <p> |
|
|
417 | To prepare BootX, start the BootX App Control Panel. First select the Options |
|
|
418 | dialog and check <c>Use Specified RAM Disk</c> and select <c>ppc32.igz</c> from |
|
|
419 | your System Folder. Continue back to the initial screen and ensure that the |
|
|
420 | ramdisk size is at least <c>32000</c>. Finally, set the kernel arguments as |
|
|
421 | shown below: |
|
|
422 | </p> |
|
|
423 | |
|
|
424 | <pre caption="BootX kernel arguments"> |
|
|
425 | cdroot root=/dev/ram0 init=linuxrc loop=image.squashfs looptype=squashfs console=tty0 |
|
|
426 | </pre> |
|
|
427 | |
|
|
428 | <note> |
|
|
429 | The kernel parameters in the yaboot section above are also applicable here. You |
|
|
430 | can append any of those options to the kernel arguments above. |
|
|
431 | </note> |
|
|
432 | |
|
|
433 | <p> |
|
|
434 | Check once more to make sure the settings are correct and then save the |
|
|
435 | configuration. This saves typing just in case it doesn't boot or something is |
|
|
436 | missing. Press the Linux button at the top of the window. If everything goes |
|
|
437 | correctly, it should boot into the Installation CD. Continue with |
|
|
438 | <uri link="#booted">And When You're Booted...</uri> |
|
|
439 | </p> |
|
|
440 | |
|
|
441 | </body> |
|
|
442 | </subsection> |
|
|
443 | |
576 | <subsection id="booted"> |
444 | <subsection id="booted"> |
577 | <title>And When You're Booted...</title> |
445 | <title>And When You're Booted...</title> |
578 | <body> |
446 | <body> |
579 | |
447 | |
580 | <p> |
448 | <p> |
581 | You will be greeted by a root ("#") prompt on the current console. You can also |
449 | You will be greeted by a root ("#") prompt on the current console. You can also |
582 | switch to other consoles by pressing Alt-fn-F2, Alt-fn-F3 and Alt-fn-F4. Get |
450 | switch to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get |
583 | back to the one you started on by pressing Alt-fn-F1. |
451 | back to the one you started on by pressing Alt-F1. Due to the keyboard layout, |
|
|
452 | you may need to press Alt-fn-Fx on Apple machines. |
584 | </p> |
453 | </p> |
585 | |
454 | |
586 | <p> |
455 | <p> |
587 | If you are installing Gentoo on a system with a non-US keyboard, use |
456 | If you are installing Gentoo on a system with a non-US keyboard, use |
588 | <c>loadkeys</c> to load the keymap for your keyboard. To list the available |
457 | <c>loadkeys</c> to load the keymap for your keyboard. To list the available |
589 | keymaps, execute <c>ls /usr/share/keymaps/i386</c>. |
458 | keymaps, execute <c>ls /usr/share/keymaps/i386</c>. |
590 | </p> |
459 | </p> |
591 | |
460 | |
592 | <pre caption="Listing available keymaps"> |
461 | <pre caption="Listing available keymaps"> |
593 | <comment>(PPC uses x86 keymaps on most systems. The mac/ppc keymaps provided |
462 | <comment>(PPC uses x86 keymaps on most systems.)</comment> |
594 | on the LiveCD are ADB keymaps and unusable with the LiveCD kernel)</comment> |
|
|
595 | # <i>ls /usr/share/keymaps/i386</i> |
463 | # <i>ls /usr/share/keymaps/i386</i> |
596 | </pre> |
464 | </pre> |
597 | |
465 | |
598 | <p> |
466 | <p> |
599 | Now load the keymap of your choice: |
467 | Now load the keymap of your choice: |
… | |
… | |
607 | Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
475 | Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
608 | </p> |
476 | </p> |
609 | |
477 | |
610 | </body> |
478 | </body> |
611 | </subsection> |
479 | </subsection> |
612 | <subsection id="hardware"> |
|
|
613 | <title>Extra Hardware Configuration</title> |
|
|
614 | <body> |
|
|
615 | |
480 | |
616 | <p> |
|
|
617 | When the Live CD boots, it tries to detect all your hardware devices and |
|
|
618 | loads the appropriate kernel modules to support your hardware. In the |
|
|
619 | vast majority of cases, it does a very good job. However, in some cases (the |
|
|
620 | SPARC LiveCDs don't even do autodetection), it may not auto-load the kernel |
|
|
621 | modules you need. If the PCI auto-detection missed some of your system's |
|
|
622 | hardware, you will have to load the appropriate kernel modules manually. |
|
|
623 | </p> |
|
|
624 | |
|
|
625 | <p> |
|
|
626 | In the next example we try to load the <c>8139too</c> module (support for |
|
|
627 | certain kinds of network interfaces): |
|
|
628 | </p> |
|
|
629 | |
|
|
630 | <pre caption="Loading kernel modules"> |
|
|
631 | # <i>modprobe 8139too</i> |
|
|
632 | </pre> |
|
|
633 | |
|
|
634 | </body> |
|
|
635 | </subsection> |
481 | <subsection> |
|
|
482 | <include href="hb-install-bootconfig.xml"/> |
636 | <subsection> |
483 | </subsection> |
637 | <title>Optional: Tweaking Hard Disk Performance</title> |
|
|
638 | <body> |
|
|
639 | |
484 | |
640 | <p> |
|
|
641 | If you are an advanced user, you might want to tweak the IDE hard disk |
|
|
642 | performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
|
|
643 | test the performance of your disk (execute it several times to get a |
|
|
644 | more precise impression): |
|
|
645 | </p> |
|
|
646 | |
|
|
647 | <pre caption="Testing disk performance"> |
|
|
648 | # <i>hdparm -tT /dev/hda</i> |
|
|
649 | </pre> |
|
|
650 | |
|
|
651 | <p> |
|
|
652 | To tweak, you can use any of the following examples (or experiment |
|
|
653 | yourself) which use <path>/dev/hda</path> as disk (substitute with your |
|
|
654 | disk): |
|
|
655 | </p> |
|
|
656 | |
|
|
657 | <pre caption="Tweaking hard disk performance"> |
|
|
658 | <comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i> |
|
|
659 | <comment>Activate DMA + Safe Performance-enhancing Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
|
|
660 | </pre> |
|
|
661 | |
|
|
662 | </body> |
|
|
663 | </subsection> |
|
|
664 | <subsection> |
|
|
665 | <title>Optional: User Accounts</title> |
|
|
666 | <body> |
|
|
667 | |
|
|
668 | <p> |
|
|
669 | If you plan on giving other people access to your installation |
|
|
670 | environment or you want to chat using <c>irssi</c> without root privileges (for |
|
|
671 | security reasons), you need to create the necessary user accounts and change |
|
|
672 | the root password. |
|
|
673 | </p> |
|
|
674 | |
|
|
675 | <p> |
|
|
676 | To change the root password, use the <c>passwd</c> utility: |
|
|
677 | </p> |
|
|
678 | |
|
|
679 | <pre caption="Changing the root password"> |
|
|
680 | # <i>passwd</i> |
|
|
681 | New password: <comment>(Enter your new password)</comment> |
|
|
682 | Re-enter password: <comment>(Re-enter your password)</comment> |
|
|
683 | </pre> |
|
|
684 | |
|
|
685 | <p> |
|
|
686 | To create a user account, we first enter their credentials, followed by |
|
|
687 | its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
|
|
688 | In the next example, we create a user called "john". |
|
|
689 | </p> |
|
|
690 | |
|
|
691 | <pre caption="Creating a user account"> |
|
|
692 | # <i>useradd john</i> |
|
|
693 | # <i>passwd john</i> |
|
|
694 | New password: <comment>(Enter john's password)</comment> |
|
|
695 | Re-enter password: <comment>(Re-enter john's password)</comment> |
|
|
696 | </pre> |
|
|
697 | |
|
|
698 | <p> |
|
|
699 | You can change your user id from root to the newly created user by using |
|
|
700 | <c>su</c>: |
|
|
701 | </p> |
|
|
702 | |
|
|
703 | <pre caption="Changing user id"> |
|
|
704 | # <i>su john -</i> |
|
|
705 | </pre> |
|
|
706 | |
|
|
707 | </body> |
|
|
708 | </subsection> |
|
|
709 | <subsection> |
|
|
710 | <title>Optional: Starting the SSH Daemon</title> |
|
|
711 | <body> |
|
|
712 | |
|
|
713 | <p> |
|
|
714 | If you want to allow other users to access your computer during the |
|
|
715 | Gentoo installation (perhaps because those users are going to help you |
|
|
716 | install Gentoo, or even do it for you), you need to create a user |
|
|
717 | account for them and perhaps even provide them with your root password |
|
|
718 | (<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
|
|
719 | </p> |
|
|
720 | |
|
|
721 | <p> |
|
|
722 | To fire up the SSH daemon, execute the following command: |
|
|
723 | </p> |
|
|
724 | |
|
|
725 | <pre caption="Starting the SSH daemon"> |
|
|
726 | # <i>/etc/init.d/sshd start</i> |
|
|
727 | </pre> |
|
|
728 | |
|
|
729 | <p> |
|
|
730 | To be able to use sshd, you first need to setup your networking. Continue with |
|
|
731 | the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
|
|
732 | </p> |
|
|
733 | |
|
|
734 | </body> |
|
|
735 | </subsection> |
|
|
736 | </section> |
485 | </section> |
737 | </sections> |
486 | </sections> |