/[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.4 - (show annotations) (download) (as text)
Thu Oct 23 16:00:25 2003 UTC (10 years, 5 months ago) by swift
Branch: MAIN
Changes since 1.3: +27 -19 lines
File MIME type: application/xml
Small updates to increase readability

1 <sections>
2 <section>
3 <title>Chrooting</title>
4 <subsection>
5 <title>Optional: Selecting Mirrors</title>
6 <body>
7
8 <p>
9 If you are booted from a Gentoo LiveCD, you are able to use <c>mirrorselect</c>
10 to update <path>/etc/make.conf</path> so fast mirrors are used for both Portage
11 as source code:
12 </p>
13
14 <pre caption="Selecting fast mirrors">
15 # <i>mirrorselect -a -s4 -o &gt;&gt; /mnt/gentoo/etc/make.conf</i>
16 </pre>
17
18 <p>
19 If for some reason <c>mirrorselect</c> fails, don't panic. This step is
20 completely optional. If <c>mirrorselect</c> fails, the default values suffice.
21 </p>
22
23 </body>
24 </subsection>
25 <subsection>
26 <title>Entering the new Environment</title>
27 <body>
28
29 <p>
30 Now that all partitions are initialised and the base environment
31 installed, it is time to enter our new installation environment by
32 <e>chrooting</e> in it. This means that we change from the current
33 installation environment (LiveCD or other installation medium) to your
34 installation system (namely the initialised partitions).
35 </p>
36
37 <p>
38 This chrooting is done in three steps. First we will change the root
39 from <path>/</path> (on the installation medium) to <path>/mnt/gentoo</path>
40 (on your partitions) using <c>chroot</c>. Then we will create a new environment
41 using <c>env-update</c>, which essentially creates environment variables.
42 Finally, we load those variables into memory using <c>source</c>.
43 </p>
44
45 <pre caption = "Chrooting into the new environment">
46 # <i>chroot /mnt/gentoo /bin/bash</i>
47 # <i>env-update</i>
48 Regenerating /etc/ld.so.cache...
49 # <i>source /etc/profile</i>
50 </pre>
51
52 <p>
53 Congratulations! You are now inside your own Gentoo Linux environment.
54 Ofcourse it is far from finished, which is why the installation still
55 has some sections left :-)
56 </p>
57
58 </body>
59 </subsection>
60 <subsection>
61 <title>Optional: Updating Portage</title>
62 <body>
63
64 <p>
65 If you are <e>not</e> using GRP, you must download a recent Portage snapshot
66 from the Internet. <c>emerge sync</c> does this for you. GRP-users should skip
67 this and continue with <uri link="#doc_chap2">Differences between
68 Stage1, Stage2 and Stage3</uri>.
69 </p>
70
71 <pre caption="Updating Portage">
72 # <i>emerge sync</i>
73 </pre>
74
75 </body>
76 </subsection>
77 </section>
78 <section>
79 <title>Differences between Stage1, Stage2 and Stage3</title>
80 <body>
81
82 <p>
83 Now take a seat and think of your previous steps. We asked you to
84 select a <e>stage1</e>, <e>stage2</e> or <e>stage3</e> and warned you
85 that your choice is important for further installation steps. Well, this
86 is the first place where your choice defines the further steps.
87 </p>
88
89 <ul>
90 <li>
91 If you chose <e>stage1</e>, then you have to follow <e>both</e> steps in
92 this chapter (starting with <uri link="#doc_chap3">Progressing from Stage1
93 to Stage2</uri>)
94 </li>
95 <li>
96 If you chose <e>stage2</e> you only can skip the first step
97 and immediately start with the second one (<uri link="#doc_chap4">Progressing
98 from Stage2 to Stage3</uri>)
99 </li>
100 <li>
101 If you chose <e>stage3</e> (either with or without GRP) then you can skip both
102 steps and continue with the next section: <uri
103 link="?part=1&amp;chap=7">Configuring the Kernel</uri>
104 </li>
105 </ul>
106
107 </body>
108 </section>
109 <section>
110 <title>Progressing from Stage1 to Stage2</title>
111 <subsection>
112 <title>Introduction to Bootstrapping</title>
113 <body>
114
115 <p>
116 So, you want to compile everything from scratch? Okay then :-)
117 </p>
118
119 <p>
120 In this step, we will <e>bootstrap</e> your Gentoo system. This takes a
121 long time, but the result is a system that has been optimized from the
122 ground up for your specific machine and needs.
123 </p>
124
125 <p>
126 <e>Bootstrapping</e> means building the GNU C Library, GNU Compiler
127 Collection and several other key system programs. The GNU Compiler
128 Collection even has to be built twice: first with the "generic" compiler
129 we provide, and a second time with the compiler you then just built.
130 </p>
131
132 <p>
133 Before starting the bootstrap, we list a couple of options you might or
134 might not want. If you do not want to read those, continue with <uri
135 link="#doc_chap3_sect4">Bootstrapping the System</uri>.
136 </p>
137
138 </body>
139 </subsection>
140 <subsection>
141 <title>Optional: Decreasing Compilation Time</title>
142 <body>
143
144 <p>
145 If you want to speed up the bootstrapping, you can temporarily deselect
146 java-support. This means that the GNU Compiler Collection and the GNU C
147 Library will be compiled without java-support (which decreases
148 compilation time considerably). Although this means that you wont have
149 the GNU Java Compiler (<c>gjc</c>) this does <e>not</e> mean that your
150 system won't be able to use java applets and other java-related stuff.
151 </p>
152
153 <p>
154 To deselect java-support temporarily, define <e>USE="-java"</e> before
155 firing up the bootstrap script.
156 </p>
157
158 <pre caption = "Deselecting java support">
159 # <i>export USE="-java"</i>
160 </pre>
161
162 </body>
163 </subsection>
164 <subsection>
165 <title>Optional: Downloading the Sources First</title>
166 <body>
167
168 <p>
169 If you haven't copied over all sourcecode before, then the bootstrap
170 script will download all necessary files. It goes without saying that
171 this only works if you have a working network connnection :-) If you want to
172 download the sourcecode first and later bootstrap the system (for instance
173 because you don't want to have your internet connection open during the
174 compilation) use the <e>-f</e> option of the bootstrap script, which will
175 fetch (hence the letter <e>f</e>) all sourcecode for you.
176 </p>
177
178 <pre caption = "Downloading the necessary sources">
179 # <i>cd /usr/portage</i>
180 # <i>scripts/bootstrap.sh -f</i>
181 </pre>
182
183 </body>
184 </subsection>
185 <subsection>
186 <title>Bootstrapping the System</title>
187 <body>
188
189 <p>
190 Okay then, take your keyboard and punch in the next commands to start
191 the bootstrap. Then go amuse yourself with something else (for instance harass
192 Gentoo developers on #gentoo), because this step takes quite some time to
193 finish.
194 </p>
195
196 <pre caption = "Bootstrapping the system">
197 # <i>cd /usr/portage</i>
198 # <i>scripts/bootstrap.sh</i>
199 </pre>
200
201 <p>
202 Now continue with the next step, <uri link="#doc_chap4">Progressing from Stage2
203 to Stage3</uri>.
204 </p>
205
206 </body>
207 </subsection>
208 </section>
209 <section>
210 <title>Progressing from Stage2 to Stage3</title>
211 <subsection>
212 <title>Introduction</title>
213 <body>
214
215 <p>
216 If you are reading this section, then you have a bootstrapped system
217 (either because you bootstrapped it previously, or you are using a
218 <e>stage2</e>). Then it is now time to build all system packages.
219 </p>
220
221 <p>
222 <e>All</e> system packages? No, not really. In this step, you will build
223 the system packages of which there are no alternatives to use. However,
224 some system packages have several alternatives (such as system loggers)
225 and as Gentoo is all about choices, we don't want to force one upon you.
226 </p>
227
228 </body>
229 </subsection>
230 <subsection>
231 <title>Optional: Viewing what will be done</title>
232 <body>
233
234 <p>
235 If you want to know what packages will be installed, execute <c>emerge
236 -p system</c>. This will list all packages that will be built. As this
237 list is pretty big, you should also use a pager like <c>less</c> or
238 <c>more</c> to go up and down the list.
239 </p>
240
241 <pre caption = "View what 'emerge system' will do">
242 # <i>emerge -p system | less</i>
243 </pre>
244
245 </body>
246 </subsection>
247 <subsection>
248 <title>Optional: Downloading the Sources</title>
249 <body>
250
251 <p>
252 If you want <c>emerge</c> to download the sources before you continue
253 (for instance because you don't want the internet connection to be left
254 open while you are building all packages) you can use the <e>-f</e>
255 option of <c>emerge</c> which will fetch all sources for you.
256 </p>
257
258 <pre caption = "Fetching the sources">
259 # <i>emerge -f system</i>
260 </pre>
261
262 </body>
263 </subsection>
264 <subsection>
265 <title>Building the System</title>
266 <body>
267
268 <p>
269 To start building the system, execute <c>emerge system</c>. Then go do
270 something to keep your mind busy, because this step takes a long time to
271 complete.
272 </p>
273
274 <pre caption = "Building the System">
275 # <i>emerge system</i>
276 </pre>
277
278 <p>
279 When the building has completed, continue with <uri
280 link="?part=1&amp;chap=7">Configuring the Kernel</uri>.
281 </p>
282
283 </body>
284 </subsection>
285 </section>
286 </sections>

  ViewVC Help
Powered by ViewVC 1.1.20