/[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.1 - (show annotations) (download) (as text)
Thu Oct 9 11:06:45 2003 UTC (11 years ago) by swift
Branch: MAIN
File MIME type: application/xml
First draft handbook; not for public use

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

  ViewVC Help
Powered by ViewVC 1.1.20