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

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

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

Revision 1.116 Revision 1.117
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/2.5 --> 5<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml,v 1.116 2009/07/22 05:05:19 nightmorph Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml,v 1.117 2009/10/04 18:37:42 nightmorph Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<abstract> 11<abstract>
12Gentoo installs work through a stage3 archive. In this chapter we 12Gentoo installs work through a stage3 archive. In this chapter we
13describe how you extract the stage3 archive and configure Portage. 13describe how you extract the stage3 archive and configure Portage.
14</abstract> 14</abstract>
15 15
16<version>9.2</version> 16<version>10.0</version>
17<date>2009-07-21</date> 17<date>2009-10-04</date>
18 18
19<section> 19<section>
20<title>Installing a Stage Tarball</title> 20<title>Installing a Stage Tarball</title>
21<subsection> 21<subsection>
22<title>Setting the Date/Time Right</title> 22<title>Setting the Date/Time Right</title>
230</pre> 230</pre>
231 231
232<p> 232<p>
233We will now extract the stage tarball of your choice. We will do this with 233We will now extract the stage tarball of your choice. We will do this with
234<c>tar</c>. Make sure you use the same options (<c>xvjpf</c>). The <c>v</c> 234<c>tar</c>. Make sure you use the same options (<c>xvjpf</c>). The <c>v</c>
235argument is optional and not supported in some <c>tar</c> versions. In the 235argument is optional and not supported in some <c>tar</c> versions. In the next
236next example, we extract the stage tarball 236example, we extract the stage tarball
237<path>stage3-&lt;subarch&gt;-2008.0.tar.bz2</path>. Be sure to substitute 237<path>stage3-&lt;subarch&gt;-&lt;release&gt;.tar.bz2</path>. Be sure to
238the tarball filename with your stage. 238substitute the tarball filename with your stage.
239</p> 239</p>
240 240
241<pre caption="Extracting the stage tarball"> 241<pre caption="Extracting the stage tarball">
242# <i>tar xvjpf /mnt/cdrom/stages/stage3-&lt;subarch&gt;-2008.0.tar.bz2</i> 242# <i>tar xvjpf /mnt/cdrom/stages/stage3-&lt;subarch&gt;-&lt;release&gt;.tar.bz2</i>
243</pre> 243</pre>
244 244
245<p> 245<p>
246Now that the stage is installed, continue with <uri 246Now that the stage is installed, continue with <uri
247link="#installing_portage">Installing Portage</uri>. 247link="#installing_portage">Installing Portage</uri>.
332this file we will edit now. 332this file we will edit now.
333</p> 333</p>
334 334
335<note> 335<note>
336A commented listing of all possible variables can be found in 336A commented listing of all possible variables can be found in
337<path>/mnt/gentoo/etc/make.conf.example</path>. For a successful Gentoo 337<path>/mnt/gentoo/usr/share/portage/config/make.conf.example</path>. For a
338installation you'll only need to set the variables which are mentioned beneath. 338successful Gentoo installation you'll only need to set the variables which are
339mentioned beneath.
339</note> 340</note>
340 341
341<p> 342<p>
342Fire up your favorite editor (in this guide we use <c>nano</c>) so we can alter 343Fire up your favorite editor (in this guide we use <c>nano</c>) so we can alter
343the optimization variables we will discuss hereafter. 344the optimization variables we will discuss hereafter.
350<p> 351<p>
351As you probably noticed, the <path>make.conf.example</path> file is 352As you probably noticed, the <path>make.conf.example</path> file is
352structured in a generic way: commented lines start with "#", other lines define 353structured in a generic way: commented lines start with "#", other lines define
353variables using the <c>VARIABLE="content"</c> syntax. The <path>make.conf</path> 354variables using the <c>VARIABLE="content"</c> syntax. The <path>make.conf</path>
354file uses the same syntax. Several of those variables are discussed next. 355file uses the same syntax. Several of those variables are discussed next.
355</p>
356
357</body>
358</subsection>
359<subsection>
360<title>CHOST</title>
361<body>
362
363<p>
364The <c>CHOST</c> variable declares the target build host for your system. This
365variable should already be set to the correct value. <brite>Do not edit
366it</brite> as that might break your system. If the <c>CHOST</c> variable does
367not look correct to you, you might be using the wrong stage3 tarball.
368</p> 356</p>
369 357
370</body> 358</body>
371</subsection> 359</subsection>
372<subsection> 360<subsection>

Legend:
Removed from v.1.116  
changed lines
  Added in v.1.117

  ViewVC Help
Powered by ViewVC 1.1.20