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

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

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.71 Revision 1.72
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/1.0 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-system.xml,v 1.71 2005/02/25 09:13:41 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-system.xml,v 1.72 2005/03/28 11:30:53 swift Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>1.66</version> 11<version>2.00</version>
12<date>2005-02-25</date> 12<date>2005-03-28</date>
13 13
14<section> 14<section>
15<title>Chrooting</title> 15<title>Chrooting</title>
16<subsection> 16<subsection>
17<title>Optional: Selecting Mirrors</title> 17<title>Optional: Selecting Mirrors</title>
95 95
96<p> 96<p>
97Now that all partitions are initialized and the base environment 97Now that all partitions are initialized and the base environment
98installed, it is time to enter our new installation environment by 98installed, it is time to enter our new installation environment by
99<e>chrooting</e> into it. This means that we change from the current 99<e>chrooting</e> into it. This means that we change from the current
100installation environment (LiveCD or other installation medium) to your 100installation environment (Installation CD or other installation medium) to your
101installation system (namely the initialized partitions). 101installation system (namely the initialized partitions).
102</p> 102</p>
103 103
104<p> 104<p>
105This chrooting is done in three steps. First we will change the root 105This chrooting is done in three steps. First we will change the root
140<p> 140<p>
141If you are warned that a new Portage version is available and that you should 141If you are warned that a new Portage version is available and that you should
142update Portage, you should ignore it. Portage will be updated for you later 142update Portage, you should ignore it. Portage will be updated for you later
143on during the installation. 143on during the installation.
144</p> 144</p>
145
146</body>
147</subsection>
148<subsection>
149<title>Choosing the Right Profile</title>
150<body>
151
152<p>
153First, a small definition is in place.
154</p>
155
156<p>
157A profile is a building block for any Gentoo system. Not only does it specify
158default values for CHOST, CFLAGS and other important variables, it also locks
159the system to a certain range of package versions. This is all maintained by the
160Gentoo developers.
161</p>
162
163<p>
164Previously, such a profile was barely touched by the user. However, recently,
165x86, hppa and alpha users can choose between two profiles, one for a 2.4 kernel
166and one for a 2.6 kernel. This requirement has been imposed to improve the
167integration of the 2.6 kernels.
168</p>
169
170<p>
171You can see what profile you are currently using by issuing the following
172command:
173</p>
174
175<pre caption="Verifying system profile">
176# <i>ls -l /etc/make.profile</i>
177lrwxrwxrwx 1 root root 48 Mar 7 11:55 /etc/make.profile ->
178 ../usr/portage/profiles/default-linux/x86/2005.0
179</pre>
180
181<p>
182If you are using one of the abovementioned three architectures, you will see an
183additional profile in the one listed by the <path>make.profile</path> symlink:
184</p>
185
186<pre caption="Finding out if an additional profile exists">
187# <i>ls -F /etc/make.profile/</i>
1882.4/ packages parent virtuals
189</pre>
190
191<p>
192As you can see, in the above example there is a 2.4 subdirectory. This means
193that the current profile uses the 2.6 kernel; if you want a 2.4-based system,
194you need to relink your <path>make.profile</path> symlink:
195</p>
196
197<pre caption="Relinking the profile">
198# <i>ln -snf /usr/portage/profiles/default-linux/x86/2005.0/2.4 /etc/make.profile</i>
199</pre>
145 200
146</body> 201</body>
147</subsection> 202</subsection>
148<subsection id="configure_USE"> 203<subsection id="configure_USE">
149<title>Configuring the USE variable</title> 204<title>Configuring the USE variable</title>
395<title>Optional: Viewing what will be done</title> 450<title>Optional: Viewing what will be done</title>
396<body> 451<body>
397 452
398<p> 453<p>
399If you want to know what packages will be installed, execute <c>emerge 454If you want to know what packages will be installed, execute <c>emerge
400--pretend system</c>. This will list all packages that will be built. As this 455--pretend --emptytree system</c>. This will list all packages that will be
401list is pretty big, you should also use a pager like <c>less</c> or 456built. As this list is pretty big, you should also use a pager like
402<c>more</c> to go up and down the list. 457<c>less</c> or <c>more</c> to go up and down the list.
403</p> 458</p>
404 459
405<pre caption = "View what 'emerge system' will do"> 460<pre caption = "View what 'emerge system' will do">
406# <i>emerge --pretend system | less</i> 461# <i>emerge --pretend --emptytree system | less</i>
462</pre>
463
464<p>
465Note that, if you haven't touched the default CFLAGS/CXXFLAGS setting, using
466<c>emerge --pretend --newuse system</c> is sufficient. If you didn't touch the
467USE flag either, why are you running a stage2 installation then?
407</pre> 468</p>
408 469
409</body> 470</body>
410</subsection> 471</subsection>
411<subsection> 472<subsection>
412<title>Optional: Downloading the Sources</title> 473<title>Optional: Downloading the Sources</title>
418open while you are building all packages) you can use the <e>--fetchonly</e> 479open while you are building all packages) you can use the <e>--fetchonly</e>
419option of <c>emerge</c> which will fetch all sources for you. 480option of <c>emerge</c> which will fetch all sources for you.
420</p> 481</p>
421 482
422<pre caption = "Fetching the sources"> 483<pre caption = "Fetching the sources">
423# <i>emerge --fetchonly system</i> 484# <i>emerge --fetchonly --emptytree system</i>
424</pre> 485</pre>
425 486
426</body> 487</body>
427</subsection> 488</subsection>
428<subsection> 489<subsection>
429<title>Building the System</title> 490<title>Building the System</title>
430<body> 491<body>
431 492
432<p> 493<p>
433To start building the system, execute <c>emerge system</c>. Then go do 494To start building the system, execute <c>emerge --emptytree system</c>. Then
434something to keep your mind busy, because this step takes a long time to 495go do something to keep your mind busy, because this step takes a long time to
435complete. 496complete.
436</p> 497</p>
437 498
438<pre caption = "Building the System"> 499<pre caption = "Building the System">
439# <i>emerge system</i> 500# <i>emerge --emptytree system</i>
501</pre>
502
503<p>
504Again, if you haven't touched the default CFLAGS and CXXFLAGS setting, using
505<c>--newuse</c> is sufficient.
440</pre> 506</p>
441 507
442<p> 508<p>
443You can for now safely ignore any warnings about updated configuration files 509You can for now safely ignore any warnings about updated configuration files
444(and running <c>etc-update</c>). When your Gentoo system is fully installed and 510(and running <c>etc-update</c>). When your Gentoo system is fully installed and
445booted, do read our documentation on <uri 511booted, do read our documentation on <uri

Legend:
Removed from v.1.71  
changed lines
  Added in v.1.72

  ViewVC Help
Powered by ViewVC 1.1.20