/[gentoo]/xml/htdocs/doc/en/handbook/hb-install-system.xml
Gentoo

Contents of /xml/htdocs/doc/en/handbook/hb-install-system.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.18 - (show annotations) (download) (as text)
Sat Dec 6 20:37:49 2003 UTC (10 years, 7 months ago) by swift
Branch: MAIN
Changes since 1.17: +17 -1 lines
File MIME type: application/xml
Move the /dev bindmounting to the correct place

1 <!-- The content of this document is licensed under the CC-BY-SA license -->
2 <!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
3
4 <!-- $Header: /home/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-system.xml,v 1.17 2003/12/04 15:38:13 swift Exp $ -->
5
6 <sections>
7 <section>
8 <title>Chrooting</title>
9 <subsection>
10 <title>Optional: Selecting Mirrors</title>
11 <body>
12
13 <p>
14 If you are booted from a Gentoo LiveCD, you are able to use <c>mirrorselect</c>
15 to update <path>/etc/make.conf</path> so fast mirrors are used for both Portage
16 as source code:
17 </p>
18
19 <pre caption="Selecting fast mirrors">
20 # <i>mirrorselect -a -s4 -o &gt;&gt; /mnt/gentoo/etc/make.conf</i>
21 </pre>
22
23 <p>
24 If for some reason <c>mirrorselect</c> fails, don't panic. This step is
25 completely optional. If <c>mirrorselect</c> fails, the default values suffice.
26 </p>
27
28 </body>
29 </subsection>
30 <subsection>
31 <title>Copy DNS Info</title>
32 <body>
33
34 <p>
35 One thing still remains to be done before we enter the new environment, and that
36 is copy over the DNS information in <path>/etc/resolv.conf</path>. You need
37 to do this to ensure that networking still works even after entering the new
38 environment. <path>/etc/resolv.conf</path> contains the nameservers for your
39 network.
40 </p>
41
42 <pre caption="Copy over DNS information">
43 # <i>cp /etc/resolv.conf /mnt/gentoo/etc/resolv.conf</i>
44 </pre>
45
46 </body>
47 </subsection>
48 <subsection>
49 <title>Optional: Mounting /dev</title>
50 <body>
51
52 <p>
53 Knoppix users (and people that install Gentoo from an installation medium that
54 does not use DevFS) should now bind-mount the <path>/dev</path> structure:
55 </p>
56
57 <pre caption="Bind-mounting /dev">
58 # <i>mkdir /mnt/gentoo/dev</i>
59 # <i>mount -o bind /dev /mnt/gentoo/dev</i>
60 </pre>
61
62 </body>
63 </subsection>
64 <subsection>
65 <title>Entering the new Environment</title>
66 <body>
67
68 <p>
69 Now that all partitions are initialised and the base environment
70 installed, it is time to enter our new installation environment by
71 <e>chrooting</e> into it. This means that we change from the current
72 installation environment (LiveCD or other installation medium) to your
73 installation system (namely the initialised partitions).
74 </p>
75
76 <p>
77 This chrooting is done in three steps. First we will change the root
78 from <path>/</path> (on the installation medium) to <path>/mnt/gentoo</path>
79 (on your partitions) using <c>chroot</c>. Then we will create a new environment
80 using <c>env-update</c>, which essentially creates environment variables.
81 Finally, we load those variables into memory using <c>source</c>.
82 </p>
83
84 <pre caption = "Chrooting into the new environment">
85 # <i>chroot /mnt/gentoo /bin/bash</i>
86 # <i>env-update</i>
87 Regenerating /etc/ld.so.cache...
88 # <i>source /etc/profile</i>
89 </pre>
90
91 <p>
92 Congratulations! You are now inside your own Gentoo Linux environment.
93 Of course it is far from finished, which is why the installation still
94 has some sections left :-)
95 </p>
96
97 </body>
98 </subsection>
99 <subsection>
100 <title>Optional: Updating Portage</title>
101 <body>
102
103 <p>
104 If you are <e>not</e> using GRP, you must download a recent Portage snapshot
105 from the Internet. <c>emerge sync</c> does this for you. GRP-users should skip
106 this and continue with <uri link="#doc_chap1_sect5">Optional: Using Distributed
107 Compiling</uri> or <uri link="#doc_chap2">Differences between
108 Stage1, Stage2 and Stage3</uri>.
109 </p>
110
111 <pre caption="Updating Portage">
112 # <i>emerge sync</i>
113 </pre>
114
115 <p>
116 If you are warned that a new Portage version is available and that you should
117 update Portage, you can safely ignore it. Portage will be updated for you later
118 on during the installation.
119 </p>
120
121 </body>
122 </subsection>
123 <subsection>
124 <title>Optional: Using Distributed Compiling</title>
125 <body>
126
127 <p>
128 If you are interested in using a collection of systems to help in compiling your
129 system you might want to take a look at our <uri
130 link="/doc/en/distcc.xml">DistCC Guide</uri>. By using <c>distcc</c> you can use
131 the processing power of several systems to aid you with the installation.
132 </p>
133
134 </body>
135 </subsection>
136 </section>
137 <section>
138 <title>Differences between Stage1, Stage2 and Stage3</title>
139 <body>
140
141 <p>
142 Now take a seat and think of your previous steps. We asked you to
143 select a <e>stage1</e>, <e>stage2</e> or <e>stage3</e> and warned you
144 that your choice is important for further installation steps. Well, this
145 is the first place where your choice defines the further steps.
146 </p>
147
148 <ul>
149 <li>
150 If you chose <e>stage1</e>, then you have to follow <e>both</e> steps in
151 this chapter (starting with <uri link="#doc_chap3">Progressing from Stage1
152 to Stage2</uri>)
153 </li>
154 <li>
155 If you chose <e>stage2</e> you only can skip the first step
156 and immediately start with the second one (<uri link="#doc_chap4">Progressing
157 from Stage2 to Stage3</uri>)
158 </li>
159 <li>
160 If you chose <e>stage3</e> (either with or without GRP) then you can skip both
161 steps and continue with the next section: <uri
162 link="?part=1&amp;chap=7">Configuring the Kernel</uri>
163 </li>
164 </ul>
165
166 </body>
167 </section>
168 <section>
169 <title>Progressing from Stage1 to Stage2</title>
170 <subsection>
171 <title>Introduction to Bootstrapping</title>
172 <body>
173
174 <p>
175 So, you want to compile everything from scratch? Okay then :-)
176 </p>
177
178 <p>
179 In this step, we will <e>bootstrap</e> your Gentoo system. This takes a
180 long time, but the result is a system that has been optimized from the
181 ground up for your specific machine and needs.
182 </p>
183
184 <p>
185 <e>Bootstrapping</e> means building the GNU C Library, GNU Compiler
186 Collection and several other key system programs. The GNU Compiler
187 Collection even has to be built twice: first with the "generic" compiler
188 we provide, and a second time with the compiler you then just built.
189 </p>
190
191 <p>
192 Before starting the bootstrap, we list a couple of options you might or
193 might not want. If you do not want to read those, continue with <uri
194 link="#doc_chap3_sect4">Bootstrapping the System</uri>.
195 </p>
196
197 </body>
198 </subsection>
199 <subsection>
200 <title>Optional: Decreasing Compilation Time</title>
201 <body>
202
203 <p>
204 If you want to speed up the bootstrapping, you can temporarily deselect
205 java-support. This means that the GNU Compiler Collection and the GNU C
206 Library will be compiled without java-support (which decreases
207 compilation time considerably). Although this means that you wont have
208 the GNU Java Compiler (<c>gcj</c>) this does <e>not</e> mean that your
209 system won't be able to use java applets and other java-related stuff.
210 </p>
211
212 <p>
213 To deselect java-support temporarily, define <e>USE="-java"</e> before
214 firing up the bootstrap script.
215 </p>
216
217 <pre caption = "Deselecting java support">
218 # <i>export USE="-java"</i>
219 </pre>
220
221 <p>
222 Don't forget to unset the variable after bootstrapping:
223 </p>
224
225 <pre caption="Unsetting USE">
226 # <i>unset USE</i>
227 </pre>
228
229 </body>
230 </subsection>
231 <subsection>
232 <title>Optional: Downloading the Sources First</title>
233 <body>
234
235 <p>
236 If you haven't copied over all sourcecode before, then the bootstrap
237 script will download all necessary files. It goes without saying that
238 this only works if you have a working network connnection :-) If you want to
239 download the sourcecode first and later bootstrap the system (for instance
240 because you don't want to have your internet connection open during the
241 compilation) use the <e>-f</e> option of the bootstrap script, which will
242 fetch (hence the letter <e>f</e>) all sourcecode for you.
243 </p>
244
245 <pre caption = "Downloading the necessary sources">
246 # <i>cd /usr/portage</i>
247 # <i>scripts/bootstrap.sh -f</i>
248 </pre>
249
250 </body>
251 </subsection>
252 <subsection>
253 <title>Bootstrapping the System</title>
254 <body>
255
256 <p>
257 Okay then, take your keyboard and punch in the next commands to start
258 the bootstrap. Then go amuse yourself with something else (for instance harass
259 Gentoo developers on #gentoo), because this step takes quite some time to
260 finish.
261 </p>
262
263 <pre caption = "Bootstrapping the system">
264 # <i>cd /usr/portage</i>
265 # <i>scripts/bootstrap.sh</i>
266 </pre>
267
268 <p>
269 If you have altered the <c>CHOST</c> setting in <path>/etc/make.conf</path>
270 previously, you need to reinitialise some variables in order for <c>gcc</c> to
271 work fast:
272 </p>
273
274 <pre caption="Reinitialise environment variables">
275 # <i>source /etc/profile</i>
276 </pre>
277
278 <p>
279 Now continue with the next step, <uri link="#doc_chap4">Progressing from Stage2
280 to Stage3</uri>.
281 </p>
282
283 </body>
284 </subsection>
285 </section>
286 <section>
287 <title>Progressing from Stage2 to Stage3</title>
288 <subsection>
289 <title>Introduction</title>
290 <body>
291
292 <p>
293 If you are reading this section, then you have a bootstrapped system
294 (either because you bootstrapped it previously, or you are using a
295 <e>stage2</e>). Then it is now time to build all system packages.
296 </p>
297
298 <p>
299 <e>All</e> system packages? No, not really. In this step, you will build
300 the system packages of which there are no alternatives to use. However,
301 some system packages have several alternatives (such as system loggers)
302 and as Gentoo is all about choices, we don't want to force one upon you.
303 </p>
304
305 </body>
306 </subsection>
307 <subsection>
308 <title>Optional: Viewing what will be done</title>
309 <body>
310
311 <p>
312 If you want to know what packages will be installed, execute <c>emerge
313 --pretend system</c>. This will list all packages that will be built. As this
314 list is pretty big, you should also use a pager like <c>less</c> or
315 <c>more</c> to go up and down the list.
316 </p>
317
318 <pre caption = "View what 'emerge system' will do">
319 # <i>emerge --pretend system | less</i>
320 </pre>
321
322 </body>
323 </subsection>
324 <subsection>
325 <title>Optional: Downloading the Sources</title>
326 <body>
327
328 <p>
329 If you want <c>emerge</c> to download the sources before you continue
330 (for instance because you don't want the internet connection to be left
331 open while you are building all packages) you can use the <e>-f</e>
332 option of <c>emerge</c> which will fetch all sources for you.
333 </p>
334
335 <pre caption = "Fetching the sources">
336 # <i>emerge --fetchonly system</i>
337 </pre>
338
339 </body>
340 </subsection>
341 <subsection>
342 <title>Building the System</title>
343 <body>
344
345 <p>
346 To start building the system, execute <c>emerge system</c>. Then go do
347 something to keep your mind busy, because this step takes a long time to
348 complete.
349 </p>
350
351 <pre caption = "Building the System">
352 # <i>emerge system</i>
353 </pre>
354
355 <p>
356 When the building has completed, continue with <uri
357 link="?part=1&amp;chap=7">Configuring the Kernel</uri>.
358 </p>
359
360 </body>
361 </subsection>
362 </section>
363 </sections>

  ViewVC Help
Powered by ViewVC 1.1.20