en/handbook/hb-install-system.xml

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-system.xml,v 1.74 2005/03/29 15:23:30 swift Exp $ -->

<sections>

<version>2.3</version>
<date>2005-04-07</date>

<section>
<title>Chrooting</title>
<subsection>
<title>Optional: Selecting Mirrors</title>
<body>

<p>
In order to download source code quickly it is recommended to select a fast
mirror. Portage will look in your <path>make.conf</path> file for the
GENTOO_MIRRORS variable and use the mirrors listed therein. You can surf to
our <uri link="/main/en/mirrors.xml">mirror list</uri> and search
for a mirror (or mirrors) close to you (as those are most frequently the 
fastest ones), but we provide a nice tool called <c>mirrorselect</c> which
provides you with a nice interface to select the mirrors you want.
</p>
  
<pre caption="Using mirrorselect for the GENTOO_MIRRORS variable">
# <i>mirrorselect -i -o &gt;&gt; /mnt/gentoo/etc/make.conf</i>
</pre>

<warn>
Do not select any IPv6 mirrors. Our stages currently do not support IPv6.
</warn>

<p>
A second important setting is the SYNC setting in <path>make.conf</path>. This
variable contains the rsync server you want to use when updating your Portage
tree (the collection of ebuilds, scripts containing all the information Portage
needs to download and install software). Although you can manually enter a SYNC
server for yourself, <c>mirrorselect</c> can ease that operation for you:
</p>

<pre caption="Selecting an rsync mirror using mirrorselect">
# <i>mirrorselect -i -r -o &gt;&gt; /mnt/gentoo/etc/make.conf</i>
</pre>

<p>
After running <c>mirrorselect</c> it is adviseable to double-check the settings
in <path>/mnt/gentoo/etc/make.conf</path> !
</p>

</body>
</subsection>
<subsection>
<title>Copy DNS Info</title>
<body>

<p>
One thing still remains to be done before we enter the new environment and that
is copying over the DNS information in <path>/etc/resolv.conf</path>. You need
to do this to ensure that networking still works even after entering the new
environment. <path>/etc/resolv.conf</path> contains the nameservers for your
network.
</p>

<pre caption="Copy over DNS information">
<comment>(The "-L" option is needed to make sure we don't copy a symbolic link)</comment>
# <i>cp -L /etc/resolv.conf /mnt/gentoo/etc/resolv.conf</i>
</pre>

</body>
</subsection>
<subsection>
<title>Mounting the proc Filesystem</title>
<body>

<p>
Mount the <path>/proc</path> filesystem on <path>/mnt/gentoo/proc</path> to
allow the installation to use the kernel-provided information even within the
chrooted environment.
</p>

<pre caption="Mounting /proc">
# <i>mount -t proc none /mnt/gentoo/proc</i>
</pre>

</body>
</subsection>
<subsection>
<title>Entering the new Environment</title>
<body>

<p>
Now that all partitions are initialized and the base environment
installed, it is time to enter our new installation environment by
<e>chrooting</e> into it. This means that we change from the current
installation environment (Installation CD or other installation medium) to your
installation system (namely the initialized partitions).
</p>

<p>
This chrooting is done in three steps. First we will change the root
from <path>/</path> (on the installation medium) to <path>/mnt/gentoo</path> 
(on your partitions) using <c>chroot</c>. Then we will create a new environment
using <c>env-update</c>, which essentially creates environment variables.
Finally, we load those variables into memory using <c>source</c>.
</p>

<pre caption = "Chrooting into the new environment">
# <i>chroot /mnt/gentoo /bin/bash</i>
# <i>env-update</i>
 * Caching service dependencies...
# <i>source /etc/profile</i>
</pre>

<p>
Congratulations! You are now inside your own Gentoo Linux environment.
Of course it is far from finished, which is why the installation still
has some sections left :-)
</p>

</body>
</subsection>
<subsection>
<title>Updating the Portage tree</title>
<body>

<p>
You should now update your Portage tree to the latest version. <c>emerge 
--sync</c> does this for you.
</p>

<pre caption="Updating the Portage tree">
# <i>emerge --sync</i>
</pre>

<p>
If you are behind a firewall that blocks rsync traffic, you can use
<c>emerge-webrsync</c> which will download and install a portage snapshot for
you.
</p>

<p>
If you are warned that a new Portage version is available and that you should
update Portage, you should ignore it. Portage will be updated for you later
on during the installation.
</p>

</body>
</subsection>
<subsection>
<title>Choosing the Right Profile</title>
<body>

<p>
First, a small definition is in place.
</p>

<p>
A profile is a building block for any Gentoo system. Not only does it specify
default values for CHOST, CFLAGS and other important variables, it also locks
the system to a certain range of package versions. This is all maintained by the
Gentoo developers.
</p>

<p>
Previously, such a profile was barely touched by the user. However, recently,
x86, hppa and alpha users can choose between two profiles, one for a 2.4 kernel
and one for a 2.6 kernel. This requirement has been imposed to improve the
integration of the 2.6 kernels.
</p>

<p>
You can see what profile you are currently using by issuing the following
command:
</p>

<pre caption="Verifying system profile">
# <i>ls -l /etc/make.profile</i>
lrwxrwxrwx  1 root root 48 Mar  7 11:55 /etc/make.profile ->
      ../usr/portage/profiles/default-linux/x86/2005.0
</pre>

<p>
If you are using one of the abovementioned three architectures, you will see an
additional profile in the one listed by the <path>make.profile</path> symlink:
</p>

<pre caption="Finding out if an additional profile exists">
# <i>ls -F /etc/make.profile/</i>
2.4/  packages  parent  virtuals
</pre>

<p>
As you can see, in the above example there is a 2.4 subdirectory. This means
that the current profile uses the 2.6 kernel; if you want a 2.4-based system,
you need to relink your <path>make.profile</path> symlink:
</p>

<pre caption="Relinking the profile">
# <i>ln -snf /usr/portage/profiles/default-linux/x86/2005.0/2.4 /etc/make.profile</i>
</pre>

</body>
</subsection>
<subsection id="configure_USE">
<title>Configuring the USE variable</title>
<body>

<p>
<c>USE</c> is one of the most powerful variables Gentoo provides to its users.
Several programs can be compiled with or without optional support for certain
items. For instance, some programs can be compiled with gtk-support, or with
qt-support. Others can be compiled with or without SSL support. Some programs
can even be compiled with framebuffer support (svgalib) instead of X11 support
(X-server).
</p>

<p>
Most distributions compile their packages with support for as much as possible,
increasing the size of the programs and startup time, not to mention an enormous
amount of dependencies. With Gentoo you can define what options a package 
should be compiled with. This is where <c>USE</c> comes into play.
</p>

<p>
In the <c>USE</c> variable you define keywords which are mapped onto
compile-options. For instance, <e>ssl</e> will compile ssl-support in the
programs that support it. <e>-X</e> will remove X-server support (note the minus
sign in front). <e>gnome gtk -kde -qt</e> will compile your programs with gnome
(and gtk) support, and not with kde (and qt) support, making your system fully
tweaked for GNOME.
</p>

<p>
The default <c>USE</c> settings are placed in the <path>make.defaults</path> 
files of your profile. You will find <path>make.defaults</path> files in the
directory which <path>/etc/make.profile</path> points to and all parent 
directories as well. The default <c>USE</c> setting is the sum of all <c>USE</c>
settings in all <path>make.defaults</path> files. What you place in
<path>/etc/make.conf</path> is calculated against these defaults settings. If
you add something to the <c>USE</c> setting, it is added to the default list. If
you remove something from the <c>USE</c> setting (by placing a minus sign in
front of it) it is removed from the default list (if it was in the default list
at all). <e>Never</e> alter anything inside the <path>/etc/make.profile</path>
directory; it gets overwritten when you update Portage!
</p>

<p>
A full description on <c>USE</c> can be found in the second part of the Gentoo
Handbook, <uri link="?part=2&amp;chap=2">USE flags</uri>. A full description on
the available USE flags can be found on your system in
<path>/usr/portage/profiles/use.desc</path>. 
</p>

<pre caption="Viewing available USE flags">
# <i>less /usr/portage/profiles/use.desc</i>
<comment>(You can scroll using your arrow keys, exit by pressing 'q')</comment>
</pre>

<p>
As an example we show a <c>USE</c> setting for a KDE-based system with DVD, ALSA
and CD Recording support:
</p>

<pre caption="Opening /etc/make.conf">
# <i>nano -w /etc/make.conf</i>
</pre>

<pre caption="USE setting">
USE="-gtk -gnome qt kde dvd alsa cdr"
</pre>

</body>
</subsection>
<subsection>
<title>Optional: GLIBC Locales</title>
<body>

<p>
You will probably only use one or maybe two locales on your system. Up until now
after compiling <c>glibc</c> a full set of all available locales will be
created. As of now you can activate the <c>userlocales</c> USE flag and specify
only the locales you will need in <path>/etc/locales.build</path>. Only do this
if you know what locales to choose. This will not work for the bootstrapping,
but when you recompile glibc afterwards it will.
</p>

<pre caption="Activate the userlocales USE flag especially for glibc">
# <i>mkdir /etc/portage</i>
# <i>echo "sys-libs/glibc userlocales" >> /etc/portage/package.use</i>
</pre>

<p>
Now specify the locales you want to be able to use:
</p>

<pre caption="Opening /etc/locales.build">
# <i>nano -w /etc/locales.build</i>
</pre>

<p>
The following locales are an example to get both English (United States) and
German (Germany) with the accompanying character formats (like UTF-8).
</p>

<pre caption="Specify your locales">
en_US/ISO-8859-1
en_US.UTF-8/UTF-8
de_DE/ISO-8859-1
de_DE@euro/ISO-8859-15
</pre>

</body>
</subsection>
</section>
<section>
<title>Differences between Stage1, Stage2 and Stage3</title>
<body>

<p>
Now take a seat and think of your previous steps. We asked you to
select a <e>stage1</e>, <e>stage2</e> or <e>stage3</e> and warned you
that your choice is important for further installation steps. Well, this
is the first place where your choice defines the subsequent steps.
</p>

<ul>
<li>
  If you chose <e>stage1</e>, then you have to follow <e>both</e> steps in
  this chapter (starting with <uri link="#doc_chap3">Progressing from Stage1 
  to Stage2</uri>)
</li>
<li>
  If you chose <e>stage2</e> you only can skip the first step
  and immediately start with the second one (<uri link="#doc_chap4">Progressing
  from Stage2 to Stage3</uri>)
</li>
<li>
  If you chose <e>stage3</e> then you can skip both
  steps and continue with <uri link="?part=1&amp;chap=7">Configuring the 
  Kernel</uri>
</li>
</ul>

</body>
</section>
<section>
<title>Progressing from Stage1 to Stage2</title>
<subsection>
<title>Introduction to Bootstrapping</title>
<body>

<p>
So, you want to compile everything from scratch? Okay then :-)
</p>

<p>
In this step, we will <e>bootstrap</e> your Gentoo system. This takes a
long time, but the result is a system that has been optimized from the
ground up for your specific machine and needs.
</p>

<p>
<e>Bootstrapping</e> means building the GNU C Library, GNU Compiler
Collection and several other key system programs. 
</p>

<p>
Before starting the bootstrap, you might want to download all necessary
sourcecode first. If you do not want to do this, continue 
with <uri link="#bootstrap">Bootstrapping the System</uri>.
</p>

</body>
</subsection>
<subsection>
<title>Optional: Downloading the Sources First</title>
<body>

<p>
If you haven't copied over all source code before, then the bootstrap
script will download all necessary files. If you want to 
download the source code first and later bootstrap the system (for instance 
because you don't want to have your internet connection open during the 
compilation) use the <e>-f</e> option of the bootstrap script, which will 
fetch (hence the letter <e>f</e>) all source code for you.
</p>

<pre caption = "Downloading the necessary sources">
# <i>cd /usr/portage</i>
# <i>scripts/bootstrap.sh -f</i>
</pre>

</body>
</subsection>
<subsection id="bootstrap">
<title>Bootstrapping the System</title>
<body>

<p>
Okay then, take your keyboard and punch in the next commands to start
the bootstrap. Then go amuse yourself with something else because this step 
takes quite some time to finish.
</p>

<pre caption = "Bootstrapping the system">
# <i>cd /usr/portage</i>
# <i>scripts/bootstrap.sh</i>
</pre>

<p>
Now continue with the next step, <uri link="#doc_chap4">Progressing from Stage2
to Stage3</uri>.
</p>

</body>
</subsection>
</section>
<section>
<title>Progressing from Stage2 to Stage3</title>
<subsection>
<title>Introduction</title>
<body>

<p>
If you are reading this section, then you have a bootstrapped system
(either because you bootstrapped it previously, or you are using a
<e>stage2</e>). Then it is now time to build all system packages.
</p>

<p>
<e>All</e> system packages? No, not really. In this step, you will build
the system packages of which there are no alternatives to use.
Some system packages have several alternatives (such as system loggers)
and as Gentoo is all about choices, we don't want to force one upon you.
</p>

</body>
</subsection>
<subsection>
<title>Optional: Viewing what will be done</title>
<body>

<p>
If you want to know what packages will be installed, execute <c>emerge
--pretend --emptytree system</c>. This will list all packages that will be 
built. As this list is pretty big, you should also use a pager like 
<c>less</c> or <c>more</c> to go up and down the list.
</p>

<pre caption = "View what 'emerge system' will do">
# <i>emerge --pretend --emptytree system | less</i>
</pre>

<p>
Note that, if you haven't touched the default CFLAGS/CXXFLAGS setting, using 
<c>emerge --pretend --newuse system</c> is sufficient. If you didn't touch the 
USE flag either, why are you running a stage2 installation then?
</p>

</body>
</subsection>
<subsection>
<title>Optional: Downloading the Sources</title>
<body>

<p>
If you want <c>emerge</c> to download the sources before you continue
(for instance because you don't want the internet connection to be left
open while you are building all packages) you can use the <e>--fetchonly</e>
option of <c>emerge</c> which will fetch all sources for you. 
</p>

<pre caption = "Fetching the sources">
# <i>emerge --fetchonly --emptytree system</i>
</pre>

</body>
</subsection>
<subsection>
<title>Building the System</title>
<body>

<p>
To start building the system, execute <c>emerge --emptytree system</c>. Then 
go do something to keep your mind busy, because this step takes a long time to 
complete.
</p>

<pre caption = "Building the System">
# <i>emerge --emptytree system</i>
</pre>

<p>
Again, if you haven't touched the default CFLAGS and CXXFLAGS setting, using
<c>--newuse</c> is sufficient.
</p>

<p>
You can for now safely ignore any warnings about updated configuration files
(and running <c>etc-update</c>). When your Gentoo system is fully installed and
booted, do read our documentation on <uri
link="?part=3&amp;chap=2#doc_chap3">Configuration File Protection</uri>.
</p>

<p>
When the build process has completed, continue with <uri
link="?part=1&amp;chap=7">Configuring the Kernel</uri>.
</p>

</body>
</subsection>
</section>

</sections>
1	<?xml version='1.0' encoding='UTF-8'?>
2	<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3
4	<!-- The content of this document is licensed under the CC-BY-SA license -->
5	<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
6
7	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-system.xml,v 1.74 2005/03/29 15:23:30 swift Exp $ -->
8
9	<sections>
10
11	<version>2.3</version>
12	<date>2005-04-07</date>
13
14	<section>
15	<title>Chrooting</title>
16	<subsection>
17	<title>Optional: Selecting Mirrors</title>
18	<body>
19
20	<p>
21	In order to download source code quickly it is recommended to select a fast
22	mirror. Portage will look in your <path>make.conf</path> file for the
23	GENTOO_MIRRORS variable and use the mirrors listed therein. You can surf to
24	our <uri link="/main/en/mirrors.xml">mirror list</uri> and search
25	for a mirror (or mirrors) close to you (as those are most frequently the
26	fastest ones), but we provide a nice tool called <c>mirrorselect</c> which
27	provides you with a nice interface to select the mirrors you want.
28	</p>
29
30	<pre caption="Using mirrorselect for the GENTOO_MIRRORS variable">
31	# <i>mirrorselect -i -o >> /mnt/gentoo/etc/make.conf</i>
32	</pre>
33
34	<warn>
35	Do not select any IPv6 mirrors. Our stages currently do not support IPv6.
36	</warn>
37
38	<p>
39	A second important setting is the SYNC setting in <path>make.conf</path>. This
40	variable contains the rsync server you want to use when updating your Portage
41	tree (the collection of ebuilds, scripts containing all the information Portage
42	needs to download and install software). Although you can manually enter a SYNC
43	server for yourself, <c>mirrorselect</c> can ease that operation for you:
44	</p>
45
46	<pre caption="Selecting an rsync mirror using mirrorselect">
47	# <i>mirrorselect -i -r -o >> /mnt/gentoo/etc/make.conf</i>
48	</pre>
49
50	<p>
51	After running <c>mirrorselect</c> it is adviseable to double-check the settings
52	in <path>/mnt/gentoo/etc/make.conf</path> !
53	</p>
54
55	</body>
56	</subsection>
57	<subsection>
58	<title>Copy DNS Info</title>
59	<body>
60
61	<p>
62	One thing still remains to be done before we enter the new environment and that
63	is copying over the DNS information in <path>/etc/resolv.conf</path>. You need
64	to do this to ensure that networking still works even after entering the new
65	environment. <path>/etc/resolv.conf</path> contains the nameservers for your
66	network.
67	</p>
68
69	<pre caption="Copy over DNS information">
70	<comment>(The "-L" option is needed to make sure we don't copy a symbolic link)</comment>
71	# <i>cp -L /etc/resolv.conf /mnt/gentoo/etc/resolv.conf</i>
72	</pre>
73
74	</body>
75	</subsection>
76	<subsection>
77	<title>Mounting the proc Filesystem</title>
78	<body>
79
80	<p>
81	Mount the <path>/proc</path> filesystem on <path>/mnt/gentoo/proc</path> to
82	allow the installation to use the kernel-provided information even within the
83	chrooted environment.
84	</p>
85
86	<pre caption="Mounting /proc">
87	# <i>mount -t proc none /mnt/gentoo/proc</i>
88	</pre>
89
90	</body>
91	</subsection>
92	<subsection>
93	<title>Entering the new Environment</title>
94	<body>
95
96	<p>
97	Now that all partitions are initialized and the base environment
98	installed, it is time to enter our new installation environment by
99	<e>chrooting</e> into it. This means that we change from the current
100	installation environment (Installation CD or other installation medium) to your
101	installation system (namely the initialized partitions).
102	</p>
103
104	<p>
105	This chrooting is done in three steps. First we will change the root
106	from <path>/</path> (on the installation medium) to <path>/mnt/gentoo</path>
107	(on your partitions) using <c>chroot</c>. Then we will create a new environment
108	using <c>env-update</c>, which essentially creates environment variables.
109	Finally, we load those variables into memory using <c>source</c>.
110	</p>
111
112	<pre caption = "Chrooting into the new environment">
113	# <i>chroot /mnt/gentoo /bin/bash</i>
114	# <i>env-update</i>
115	* Caching service dependencies...
116	# <i>source /etc/profile</i>
117	</pre>
118
119	<p>
120	Congratulations! You are now inside your own Gentoo Linux environment.
121	Of course it is far from finished, which is why the installation still
122	has some sections left :-)
123	</p>
124
125	</body>
126	</subsection>
127	<subsection>
128	<title>Updating the Portage tree</title>
129	<body>
130
131	<p>
132	You should now update your Portage tree to the latest version. <c>emerge
133	--sync</c> does this for you.
134	</p>
135
136	<pre caption="Updating the Portage tree">
137	# <i>emerge --sync</i>
138	</pre>
139
140	<p>
141	If you are behind a firewall that blocks rsync traffic, you can use
142	<c>emerge-webrsync</c> which will download and install a portage snapshot for
143	you.
144	</p>
145
146	<p>
147	If you are warned that a new Portage version is available and that you should
148	update Portage, you should ignore it. Portage will be updated for you later
149	on during the installation.
150	</p>
151
152	</body>
153	</subsection>
154	<subsection>
155	<title>Choosing the Right Profile</title>
156	<body>
157
158	<p>
159	First, a small definition is in place.
160	</p>
161
162	<p>
163	A profile is a building block for any Gentoo system. Not only does it specify
164	default values for CHOST, CFLAGS and other important variables, it also locks
165	the system to a certain range of package versions. This is all maintained by the
166	Gentoo developers.
167	</p>
168
169	<p>
170	Previously, such a profile was barely touched by the user. However, recently,
171	x86, hppa and alpha users can choose between two profiles, one for a 2.4 kernel
172	and one for a 2.6 kernel. This requirement has been imposed to improve the
173	integration of the 2.6 kernels.
174	</p>
175
176	<p>
177	You can see what profile you are currently using by issuing the following
178	command:
179	</p>
180
181	<pre caption="Verifying system profile">
182	# <i>ls -l /etc/make.profile</i>
183	lrwxrwxrwx 1 root root 48 Mar 7 11:55 /etc/make.profile ->
184	../usr/portage/profiles/default-linux/x86/2005.0
185	</pre>
186
187	<p>
188	If you are using one of the abovementioned three architectures, you will see an
189	additional profile in the one listed by the <path>make.profile</path> symlink:
190	</p>
191
192	<pre caption="Finding out if an additional profile exists">
193	# <i>ls -F /etc/make.profile/</i>
194	2.4/ packages parent virtuals
195	</pre>
196
197	<p>
198	As you can see, in the above example there is a 2.4 subdirectory. This means
199	that the current profile uses the 2.6 kernel; if you want a 2.4-based system,
200	you need to relink your <path>make.profile</path> symlink:
201	</p>
202
203	<pre caption="Relinking the profile">
204	# <i>ln -snf /usr/portage/profiles/default-linux/x86/2005.0/2.4 /etc/make.profile</i>
205	</pre>
206
207	</body>
208	</subsection>
209	<subsection id="configure_USE">
210	<title>Configuring the USE variable</title>
211	<body>
212
213	<p>
214	<c>USE</c> is one of the most powerful variables Gentoo provides to its users.
215	Several programs can be compiled with or without optional support for certain
216	items. For instance, some programs can be compiled with gtk-support, or with
217	qt-support. Others can be compiled with or without SSL support. Some programs
218	can even be compiled with framebuffer support (svgalib) instead of X11 support
219	(X-server).
220	</p>
221
222	<p>
223	Most distributions compile their packages with support for as much as possible,
224	increasing the size of the programs and startup time, not to mention an enormous
225	amount of dependencies. With Gentoo you can define what options a package
226	should be compiled with. This is where <c>USE</c> comes into play.
227	</p>
228
229	<p>
230	In the <c>USE</c> variable you define keywords which are mapped onto
231	compile-options. For instance, <e>ssl</e> will compile ssl-support in the
232	programs that support it. <e>-X</e> will remove X-server support (note the minus
233	sign in front). <e>gnome gtk -kde -qt</e> will compile your programs with gnome
234	(and gtk) support, and not with kde (and qt) support, making your system fully
235	tweaked for GNOME.
236	</p>
237
238	<p>
239	The default <c>USE</c> settings are placed in the <path>make.defaults</path>
240	files of your profile. You will find <path>make.defaults</path> files in the
241	directory which <path>/etc/make.profile</path> points to and all parent
242	directories as well. The default <c>USE</c> setting is the sum of all <c>USE</c>
243	settings in all <path>make.defaults</path> files. What you place in
244	<path>/etc/make.conf</path> is calculated against these defaults settings. If
245	you add something to the <c>USE</c> setting, it is added to the default list. If
246	you remove something from the <c>USE</c> setting (by placing a minus sign in
247	front of it) it is removed from the default list (if it was in the default list
248	at all). <e>Never</e> alter anything inside the <path>/etc/make.profile</path>
249	directory; it gets overwritten when you update Portage!
250	</p>
251
252	<p>
253	A full description on <c>USE</c> can be found in the second part of the Gentoo
254	Handbook, <uri link="?part=2&chap=2">USE flags</uri>. A full description on
255	the available USE flags can be found on your system in
256	<path>/usr/portage/profiles/use.desc</path>.
257	</p>
258
259	<pre caption="Viewing available USE flags">
260	# <i>less /usr/portage/profiles/use.desc</i>
261	<comment>(You can scroll using your arrow keys, exit by pressing 'q')</comment>
262	</pre>
263
264	<p>
265	As an example we show a <c>USE</c> setting for a KDE-based system with DVD, ALSA
266	and CD Recording support:
267	</p>
268
269	<pre caption="Opening /etc/make.conf">
270	# <i>nano -w /etc/make.conf</i>
271	</pre>
272
273	<pre caption="USE setting">
274	USE="-gtk -gnome qt kde dvd alsa cdr"
275	</pre>
276
277	</body>
278	</subsection>
279	<subsection>
280	<title>Optional: GLIBC Locales</title>
281	<body>
282
283	<p>
284	You will probably only use one or maybe two locales on your system. Up until now
285	after compiling <c>glibc</c> a full set of all available locales will be
286	created. As of now you can activate the <c>userlocales</c> USE flag and specify
287	only the locales you will need in <path>/etc/locales.build</path>. Only do this
288	if you know what locales to choose. This will not work for the bootstrapping,
289	but when you recompile glibc afterwards it will.
290	</p>
291
292	<pre caption="Activate the userlocales USE flag especially for glibc">
293	# <i>mkdir /etc/portage</i>
294	# <i>echo "sys-libs/glibc userlocales" >> /etc/portage/package.use</i>
295	</pre>
296
297	<p>
298	Now specify the locales you want to be able to use:
299	</p>
300
301	<pre caption="Opening /etc/locales.build">
302	# <i>nano -w /etc/locales.build</i>
303	</pre>
304
305	<p>
306	The following locales are an example to get both English (United States) and
307	German (Germany) with the accompanying character formats (like UTF-8).
308	</p>
309
310	<pre caption="Specify your locales">
311	en_US/ISO-8859-1
312	en_US.UTF-8/UTF-8
313	de_DE/ISO-8859-1
314	de_DE@euro/ISO-8859-15
315	</pre>
316
317	</body>
318	</subsection>
319	</section>
320	<section>
321	<title>Differences between Stage1, Stage2 and Stage3</title>
322	<body>
323
324	<p>
325	Now take a seat and think of your previous steps. We asked you to
326	select a <e>stage1</e>, <e>stage2</e> or <e>stage3</e> and warned you
327	that your choice is important for further installation steps. Well, this
328	is the first place where your choice defines the subsequent steps.
329	</p>
330
331	<ul>
332	<li>
333	If you chose <e>stage1</e>, then you have to follow <e>both</e> steps in
334	this chapter (starting with <uri link="#doc_chap3">Progressing from Stage1
335	to Stage2</uri>)
336	</li>
337	<li>
338	If you chose <e>stage2</e> you only can skip the first step
339	and immediately start with the second one (<uri link="#doc_chap4">Progressing
340	from Stage2 to Stage3</uri>)
341	</li>
342	<li>
343	If you chose <e>stage3</e> then you can skip both
344	steps and continue with <uri link="?part=1&chap=7">Configuring the
345	Kernel</uri>
346	</li>
347	</ul>
348
349	</body>
350	</section>
351	<section>
352	<title>Progressing from Stage1 to Stage2</title>
353	<subsection>
354	<title>Introduction to Bootstrapping</title>
355	<body>
356
357	<p>
358	So, you want to compile everything from scratch? Okay then :-)
359	</p>
360
361	<p>
362	In this step, we will <e>bootstrap</e> your Gentoo system. This takes a
363	long time, but the result is a system that has been optimized from the
364	ground up for your specific machine and needs.
365	</p>
366
367	<p>
368	<e>Bootstrapping</e> means building the GNU C Library, GNU Compiler
369	Collection and several other key system programs.
370	</p>
371
372	<p>
373	Before starting the bootstrap, you might want to download all necessary
374	sourcecode first. If you do not want to do this, continue
375	with <uri link="#bootstrap">Bootstrapping the System</uri>.
376	</p>
377
378	</body>
379	</subsection>
380	<subsection>
381	<title>Optional: Downloading the Sources First</title>
382	<body>
383
384	<p>
385	If you haven't copied over all source code before, then the bootstrap
386	script will download all necessary files. If you want to
387	download the source code first and later bootstrap the system (for instance
388	because you don't want to have your internet connection open during the
389	compilation) use the <e>-f</e> option of the bootstrap script, which will
390	fetch (hence the letter <e>f</e>) all source code for you.
391	</p>
392
393	<pre caption = "Downloading the necessary sources">
394	# <i>cd /usr/portage</i>
395	# <i>scripts/bootstrap.sh -f</i>
396	</pre>
397
398	</body>
399	</subsection>
400	<subsection id="bootstrap">
401	<title>Bootstrapping the System</title>
402	<body>
403
404	<p>
405	Okay then, take your keyboard and punch in the next commands to start
406	the bootstrap. Then go amuse yourself with something else because this step
407	takes quite some time to finish.
408	</p>
409
410	<pre caption = "Bootstrapping the system">
411	# <i>cd /usr/portage</i>
412	# <i>scripts/bootstrap.sh</i>
413	</pre>
414
415	<p>
416	Now continue with the next step, <uri link="#doc_chap4">Progressing from Stage2
417	to Stage3</uri>.
418	</p>
419
420	</body>
421	</subsection>
422	</section>
423	<section>
424	<title>Progressing from Stage2 to Stage3</title>
425	<subsection>
426	<title>Introduction</title>
427	<body>
428
429	<p>
430	If you are reading this section, then you have a bootstrapped system
431	(either because you bootstrapped it previously, or you are using a
432	<e>stage2</e>). Then it is now time to build all system packages.
433	</p>
434
435	<p>
436	<e>All</e> system packages? No, not really. In this step, you will build
437	the system packages of which there are no alternatives to use.
438	Some system packages have several alternatives (such as system loggers)
439	and as Gentoo is all about choices, we don't want to force one upon you.
440	</p>
441
442	</body>
443	</subsection>
444	<subsection>
445	<title>Optional: Viewing what will be done</title>
446	<body>
447
448	<p>
449	If you want to know what packages will be installed, execute <c>emerge
450	--pretend --emptytree system</c>. This will list all packages that will be
451	built. As this list is pretty big, you should also use a pager like
452	<c>less</c> or <c>more</c> to go up and down the list.
453	</p>
454
455	<pre caption = "View what 'emerge system' will do">
456	# <i>emerge --pretend --emptytree system \| less</i>
457	</pre>
458
459	<p>
460	Note that, if you haven't touched the default CFLAGS/CXXFLAGS setting, using
461	<c>emerge --pretend --newuse system</c> is sufficient. If you didn't touch the
462	USE flag either, why are you running a stage2 installation then?
463	</p>
464
465	</body>
466	</subsection>
467	<subsection>
468	<title>Optional: Downloading the Sources</title>
469	<body>
470
471	<p>
472	If you want <c>emerge</c> to download the sources before you continue
473	(for instance because you don't want the internet connection to be left
474	open while you are building all packages) you can use the <e>--fetchonly</e>
475	option of <c>emerge</c> which will fetch all sources for you.
476	</p>
477
478	<pre caption = "Fetching the sources">
479	# <i>emerge --fetchonly --emptytree system</i>
480	</pre>
481
482	</body>
483	</subsection>
484	<subsection>
485	<title>Building the System</title>
486	<body>
487
488	<p>
489	To start building the system, execute <c>emerge --emptytree system</c>. Then
490	go do something to keep your mind busy, because this step takes a long time to
491	complete.
492	</p>
493
494	<pre caption = "Building the System">
495	# <i>emerge --emptytree system</i>
496	</pre>
497
498	<p>
499	Again, if you haven't touched the default CFLAGS and CXXFLAGS setting, using
500	<c>--newuse</c> is sufficient.
501	</p>
502
503	<p>
504	You can for now safely ignore any warnings about updated configuration files
505	(and running <c>etc-update</c>). When your Gentoo system is fully installed and
506	booted, do read our documentation on <uri
507	link="?part=3&chap=2#doc_chap3">Configuration File Protection</uri>.
508	</p>
509
510	<p>
511	When the build process has completed, continue with <uri
512	link="?part=1&chap=7">Configuring the Kernel</uri>.
513	</p>
514
515	</body>
516	</subsection>
517	</section>
518
519	</sections>