/[gentoo]/xml/htdocs/doc/en/gentoo-x86-install.xml
Gentoo

Diff of /xml/htdocs/doc/en/gentoo-x86-install.xml

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

Revision 1.141 Revision 1.142
1<?xml version="1.0" encoding="UTF-8"?> 1<?xml version="1.0" encoding="UTF-8"?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<guide link="/doc/en/gentoo-x86-install.xml"> 3<guide link="/doc/en/gentoo-x86-install.xml">
4 <title>Gentoo Linux 1.4_rc4 Installation Instructions</title> 4 <title>Gentoo Linux 1.4 Installation Instructions</title>
5 <author title="Chief Architect"> 5 <author title="Chief Architect">
6 <mail link="drobbins@gentoo.org">Daniel Robbins</mail> 6 <mail link="drobbins@gentoo.org">Daniel Robbins</mail>
7 </author> 7 </author>
8 <author title="Author">Chris Houser</author> 8 <author title="Author">Chris Houser</author>
9 <author title="Author"> 9 <author title="Author">Jerry Alexandratos</author>
10 <mail link="">Jerry Alexandratos</mail>
11 </author>
12 <author title="Ghost"> 10 <author title="Ghost">
13 <mail link="g2boojum@gentoo.org">Grant Goodyear</mail> 11 <mail link="g2boojum@gentoo.org">Grant Goodyear</mail>
14 </author> 12 </author>
15 <author title="Editor"> 13 <author title="Editor">
16 <mail link="zhen@gentoo.org">John P. Davis</mail> 14 <mail link="zhen@gentoo.org">John P. Davis</mail>
40 <mail link="peesh@gentoo.org">Jorge Paulo</mail> 38 <mail link="peesh@gentoo.org">Jorge Paulo</mail>
41 </author> 39 </author>
42 <author title="Editor"> 40 <author title="Editor">
43 <mail link="carl@gentoo.org">Carl Anderson</mail> 41 <mail link="carl@gentoo.org">Carl Anderson</mail>
44 </author> 42 </author>
45 <author title="Editor"> 43 <author title="Editor, Reviewer">
46 <mail link="swift@gentoo.org">Sven Vermeulen</mail> 44 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
47 </author> 45 </author>
46 <author title="Editor">
47 <mail link="avenj@gentoo.org">Jon Portnoy</mail>
48 </author>
49 <author title="Reviewer">
50 <mail link="gerrynjr@gentoo.org">Gerald J. Normandin Jr.</mail>
51 </author>
52 <author title="Reviewer">
53 <mail link="spyderous@gentoo.org">Donnie Berkholz</mail>
54 </author>
48 <abstract>These instructions step you through the process of installing Gentoo 55 <abstract>These instructions step you through the process of installing Gentoo
49 Linux 1.4_rc4. The Gentoo Linux installation process supports various installation 56 Linux 1.4, release version (not _rc versions.) The Gentoo Linux installation process supports various installation
50 approaches, depending upon how much of the system you want to custom-build from 57 approaches, depending upon how much of the system you want to custom-build from
51 scratch. 58 scratch.
52 </abstract> 59 </abstract>
53 60
54 <license/> 61 <license/>
55 62
56<version>2.6.2</version> 63<version>2.6.3</version>
57 <date>19th of July 2003</date> 64 <date>4th of August 2003</date>
58 <chapter> 65 <chapter>
59 <title>About the Install</title> 66 <title>About the Install</title>
60 <section> 67 <section>
61 <body> 68 <body>
62 <p>This new boot CD will boot from nearly any modern IDE CD-ROM drive, as well 69 <p>First, if you are new to this, welcome to Gentoo Linux! Gentoo
63as many SCSI CD-ROM drives, assuming that your CD-ROM and BIOS both support booting. 70 Linux can be installed in many different ways. Those who are looking
64Included on the CD-ROM is Linux support for IDE (and PCI IDE) (built-in to the 71 for a rapid install can use pre-built packages, while those who want
65kernel) as well as support for all SCSI devices (available as modules.) In 72 the ultimate in customizability can compile Gentoo Linux entirely
66addition, we provide modules for literally every kind of network card that 73 from the original source code. The method you choose is up to
67Linux supports, as well as tools to allow you to configure your network and 74 you.</p>
68establish outbound (as well as inbound) <c>ssh</c> connections and to download 75
69files. </p> 76 <p>One significant change in relation to the official 1.4 release is
70 <p>To install from the build CD, you will need to have a 486+ processor and 77 our new 2-CD installation set, which can be ordered from <uri
71ideally at least 64 Megabytes of RAM. (Gentoo Linux has been successfully 78 link="http://store.gentoo.org">The Gentoo Linux Store</uri>, in
72built with 64MB of RAM + 64MB of swap space, but the build process is awfully 79 addition to being available on our mirrors. We currently have 2-CD
73slow under those conditions.)</p> 80 installation sets for x86 (486 and above), i686 (Pentium Pro,
74 <p>Gentoo Linux can be installed using one of three &quot;stage&quot; tarball files. The 81 Pentium II, Athlon/Duron and above), Pentium III, Pentium 4, and Athlon XP.
75one you choose depends on how much of the system you want to compile yourself. 82 To see what 2-CD set is right for you, read the detailed
76The stage1 tarball is used when you want to bootstrap and build the entire 83 descriptions of each product in the <uri
77system from scratch. The stage2 tarball is used for building the entire system 84 link="http://store.gentoo.org">store</uri>. The store descriptions
78from a bootstrapped state. The stage3 tarball already contains a basic Gentoo Linux system.</p> 85 contain fairly comprehensive CPU compatibility information.</p>
79 <p><b>So, should you choose to start from a stage1, stage2, or stage3 tarball?</b> 86
80 Starting from a stage1 allows you to have total control over the optimization settings 87 <p>So, about the 2 CD set -- here's what's on each CD. The first
81 and optional build-time functionality that is initially enabled on your system. This 88 CD ("CD 1") is called "Live CD Installation," and is a bootable CD-ROM,
82 makes stage1 installs good for power users who know what they are doing. Stage2 installs 89 meaning that you can put "CD 1" in your drive and run Gentoo Linux
83 allow you to skip the bootstrap process, and doing this is fine if you are happy with 90 directly from the CD. You can then use this CD-based version of
84 the optimization settings that we chose for your particular stage2 tarball. Choosing to 91 Gentoo to install Gentoo Linux 1.4 to your hard disk. In addition
85 go with a stage3 allows for the fastest install of Gentoo Linux, but also means that 92 to containing a bootable Gentoo Linux environment, every CD 1
86 your base system will have the optimization settings that we chose for you. Since major 93 contains everything you need to install Gentoo Linux quickly, even
87 releases of Gentoo Linux have stage3's specifically optimized for various popular processors, 94 without a connection to the Internet. In addition, several
88 this may be sufficient for you. <b>If you're installing Gentoo Linux for the first time, consider 95 pre-compiled packages are also included on CD 1, such as the
89 using a stage3 tarball for installation.</b></p> 96 ever-important XFree86 X server. If you have an ISO CD-ROM image
97 file for CD 1, its name will end in "-cd1.iso".</p>
98
99 <p>In contrast, the second CD ("CD 2") isn't bootable, and contains
100 lots of pre-built packages for your system. Included on this CD are
101 optimized versions of packages such as KDE, GNOME, OpenOffice,
102 Mozilla, Evolution, and others. CD 2 is <i>optional</i> and is
103 intended for those people who are interested in installing Gentoo
104 Linux very quickly. The packages included on CD 2 typically take
105 about 36 hours to compile from source on a typical modern
106 single-processor system. If you have an ISO CD-ROM image file for CD
107 2, its name will end in "-cd2.iso". </p>
108
109 <note>A complete Gentoo Linux 2-CD set contains the Gentoo Reference
110 Platform, which is a complete pre-built Gentoo Linux system including GNOME,
111 KDE, Mozilla, and OpenOffice. The Gentoo Reference Platform ("GRP")
112 was created to allow rapid Gentoo Linux installs
113 packages for those who need this capability. The "compile from
114 source" functionality, which is the cornerstone of Gentoo Linux,
115 will always be a fully-supported installation option as well. The
116 purpose of the GRP is to make Gentoo Linux more convenient for some
117 users, without impacting Gentoo's powerful "compile from source"
118 installation process in any way.</note>
119
120 <p>In addition to our 2-CD set, we also have a very small "basic"
121 Live CD that you can use to boot your system. Once your system has
122 booted, you can configure a connection to the Internet and then
123 install Gentoo over the network. The advantage of this "basic" CD is
124 that it is small, and thus the ISO CD-ROM image file can be
125 downloaded quickly. If you're an advanced user who wants to install
126 the most up-to-date version of Gentoo Linux available, and have a
127 fast network connection, then you may prefer this option. If you
128 have an ISO CD-ROM image file for our "basic" Live CD, its name will
129 end in "-basic.iso".</p>
90 130
131 <p>To use any Gentoo Linux CD-based installation method, you will
132 need to have a 486+ processor and ideally at least 64 Megabytes of
133 RAM. (Gentoo Linux has been successfully built with 64MB of RAM +
134 64MB of swap space, but the build process is awfully slow under
135 those conditions.)</p>
136
137 <p>Once you boot one of our Live CDs, you have even more options.
138 Gentoo Linux can be installed using one of three &quot;stage&quot;
139 tarball files. The one you choose depends on how much of the system
140 you want to compile yourself. The stage1 tarball is used when you
141 want to bootstrap and build the entire system from scratch. The
142 stage2 tarball is used for building the entire system from a
143 bootstrapped "semi-compiled" state. The stage3 tarball already
144 contains a basic Gentoo Linux system that has been built for
145 you. If you are interested in doing a "GRP" install, then the
146 stage3 tarball should be used.</p>
147
148 <p><b>If you're not doing a GRP install, should you start from a stage1, stage2, or
149 stage3 tarball?</b> Here is some information that should help you
150 make this decision.
151 Starting from a stage1 allows you to have total
152 control over the optimization settings and optional build-time
153 functionality that is initially enabled on your system. This makes
154 stage1 installs good for power users who know what they are doing.
155 It is also a great installation method for those who want to more
156 about the inner workings of Gentoo Linux.</p>
157
158 <p>
159 Stage2 installs allow you to skip the bootstrap process, and doing
160 this is fine if you are happy with the optimization settings that we
161 chose for your particular stage2 tarball. And choosing to go with a
162 stage3 allows for the fastest install of Gentoo Linux, but also
163 means that your base system will have the optimization settings that
164 we chose for you (which to be honest, are good settings and were
165 carefully chosen to enhance performance while maintaining
166 stability.) Since major releases of Gentoo Linux have stage3's
167 specifically optimized for various popular processors, starting
168 from a stage3 can offer the best of all worlds -- a fast install
169 and a system that is well-optimized.
170 <b>If you're installing Gentoo Linux for the
171 first time, consider using a stage3 tarball for
172 installation, or a stage3 with GRP.</b></p>
91 173
92 <p> So, how does one begin the install process? First, you will want to decide which one of our LiveCD ISO images to grab from 174 <note><b>Advanced users:</b> if you use a stage3 install, you should not
93<uri>ftp://ftp.ibiblio.org/pub/linux/distributions/gentoo/releases/1.4_rc4/x86/x86</uri> . Please consider using one of our mirrors to alleviate the heavy load from 175 change the default CHOST setting in make.conf. If you need to make
94 the main server. A list of servers can be found at <uri>http://www.gentoo.org/main/en/mirrors.xml</uri>. 176 such a change, you should start with a stage1 tarball and build up
95</p> 177 your system with the desired CHOST setting. The CHOST setting
96 <p> The LiveCDs are full CD images that should be burned to a CDR or CD-RW 178 typically looks something like this:
97using CD burning software. Currently, we have two types of LiveCDs. The first 179 <c>i686-pc-linux-gnu</c>.</note>
98carries the &quot;gentoo-basic&quot; label, and is approximately 40MB in size, contains only the stage 1 tarball and lives 180
99in the <path>x86/livecd/</path> directory. This LiveCD is of minimal size to
100allow for a initial quick download and contains a stage1 tarball that can be
101found in <path>/mnt/cdrom/gentoo/</path> after the CD has booted.</p>
102 <p>The second flavor of LiveCD we currently offer is labeled &quot;gentoo-3stages.&quot;
103This CD is also found in <path>x86/livecd</path>. It
104contains stage 1, 2 and 3 tarballs. Using this LiveCD, it will be possible
105for you to install a fully-functional Gentoo Linux system very quickly.</p>
106<p><b>What happened to i686, pentium3, athlon, athlon-mp stages, LiveCDs and GRP (Gentoo Reference Platform)?</b>
107Gentoo 1.4_rc4 is meant to be a minimal release candidate only. 1.4_final will contain all the usual x86 architectures and GRP. If you want to install stages optimized for these other x86 architectures or GRP, use the 1.4_rc2 documentation, which can be found at <uri>http://www.gentoo.org/doc/en/gentoo-x86-1.4_rc2-install.xml</uri>
108</p>
109 <impo>If you encounter a problem with any part of the install and wish to 181 <impo>If you encounter a problem with any part of the install and wish to
110report it as a bug, report it to <uri>http://bugs.gentoo.org</uri>. If the bug 182report it as a bug, report it to <uri>http://bugs.gentoo.org</uri>. If the bug
111needs to be sent upstream to the original software developers (eg the KDE team) the 183needs to be sent upstream to the original software developers (eg the KDE team) the
112<e>Gentoo Linux developers</e> will take care of that for you. 184<e>Gentoo Linux developers</e> will take care of that for you.
113</impo> 185</impo>
114 <note>The installation instructions in the LiveCD may not be the most up-to-date. Always refer to 186
187 <note>Another note: the installation instructions in the LiveCD may not
188 be as up-to-date as our Web documentation at
115 <uri>http://www.gentoo.org/doc/en/gentoo-x86-install.xml</uri> for the most up-to-date 189 <uri>http://www.gentoo.org/doc/en/gentoo-x86-install.xml</uri>. Refer to
190 our Web documentation for the most up-to-date
116 installation instructions. 191 installation instructions.
117 </note> 192 </note>
193
194
195
118 <p>Now, let us quickly review the install process. First, we will download, burn 196 <p>Now, let us quickly review the install process. First, we will
197 download, burn CD(s),
119and boot a LiveCD. After getting a root prompt, we will create partitions, create 198and boot a LiveCD. After getting a root prompt, we will create partitions, create
120our filesystems, and extract either a stage1, stage2 or stage3 tarball. If we 199our filesystems, and extract either a stage1, stage2 or stage3 tarball. If we
121are using a stage1 or stage2 tarball, we will take the appropriate steps to get 200are using a stage1 or stage2 tarball, we will take the appropriate steps to get
122our system to stage3. Once our system is at stage3, we can configure it 201our system to stage3. Once our system is at stage3, we can configure it
123(customize configuration files, install a boot loader, etc) and boot it and have a 202(customize configuration files, install a boot loader, etc), boot it and have a
124fully-functional Gentoo Linux system. Depending on what stage of the build 203fully-functional Gentoo Linux system. After your basic Gentoo Linux system
204is running, you can optionally use "CD 2" of our 2-CD set and install any
205number of pre-built packages such as KDE, GNOME, OpenOffice, Mozilla, or
206others that you'd like on your system.
207</p>
208<p>Depending on what stage of the build
125process you're starting from, here is what is required for installation: </p> 209process you're starting from, here is what is required for installation: </p>
126 <table> 210 <table>
127 <tr> 211 <tr>
128 <th>stage tarball</th> 212 <th>stage tarball</th>
129 <th>requirements for installation</th> 213 <th>Internet access required</th>
214 <th>Media required</th>
215 <th>steps</th>
130 </tr> 216 </tr>
131 <tr> 217 <tr>
132 <ti>1</ti> 218 <ti>1</ti>
219 <ti>Yes</ti>
220 <ti>"basic" or "CD 1"</ti>
133 <ti>partition/filesystem setup, emerge sync, bootstrap, emerge system, emerge kernel sources, final configuration</ti> 221 <ti>partition/filesystem setup, emerge sync, bootstrap, emerge system, final config</ti>
134 </tr> 222 </tr>
135 <tr> 223 <tr>
136 <ti>2</ti> 224 <ti>2</ti>
225 <ti>Yes</ti>
226 <ti>"basic" or "CD 1"</ti>
137 <ti>partition/filesystem setup, emerge sync, emerge system, emerge kernel sources, final configuration</ti> 227 <ti>partition/filesystem setup, emerge sync, emerge system, final config</ti>
138 </tr> 228 </tr>
139 <tr> 229 <tr>
140 <ti>3</ti> 230 <ti>3</ti>
141 <ti>partition/filesystem setup, emerge sync, final configuration</ti> 231 <ti>No if using "CD 1", Yes otherwise</ti>
232 <ti>"basic" or "CD 1"</ti>
233 <ti>partition/filesystem setup, emerge sync (not required if
234 using "CD 1"), final config</ti>
142 </tr> 235 </tr>
143 </table> 236 <tr>
237 <ti>3+GRP</ti>
238 <ti>No</ti>
239 <ti>"CD 1", optionally "CD 2"</ti>
240 <ti>partition/filesystem setup, final config, install CD 1
241 pre-built packages (optional), reboot,
242 install extra pre-built packages like KDE and GNOME (if using
243 "CD 2").</ti>
244 </tr>
245 </table>
144 <note>Hardware ATA RAID users should read the section about 246 <note>Hardware ATA RAID users should read the section about
145 ATA RAID on the bottom of this document before proceeding. 247 ATA RAID on the bottom of this document before proceeding.
146 </note> 248 </note>
147 </body> 249 </body>
148 </section> 250 </section>
152 <section> 254 <section>
153 <body> 255 <body>
154 <warn>Read this whole section before proceeding, especially the 256 <warn>Read this whole section before proceeding, especially the
155 available boot options. Ignoring this could lead to wrong 257 available boot options. Ignoring this could lead to wrong
156 keyboard settings, unstarted pcmcia services etc.</warn> 258 keyboard settings, unstarted pcmcia services etc.</warn>
157 <p>Start by booting the LiveCD. You should see a fancy boot screen 259
158 with the Gentoo Linux logo on it. At this screen, you can hit Enter to begin the boot process, 260 <p>Start by booting your Live CD of choice. You should see a fancy
159 or boot the LiveCD with custom boot options by specifying a kernel followed by boot options and then hitting Enter. For example <c>gentoo nousb nohotplug</c>. Consult the following table for a list of available kernels and options or press F2 to view the help screen.</p> 261 boot screen with the Gentoo Linux logo on it. At this screen, you
160 262 can hit Enter to begin the boot process, or boot the LiveCD with
263 custom boot options by specifying a kernel followed by boot options
264 and then hitting Enter. For example <c>gentoo nousb nohotplug</c>.
265 If you are installing Gentoo Linux on a system with more than one
266 processor ("SMP",) then you should type <c>smp</c> instead of
267 <c>gentoo</c> at the prompt. This will allow the LiveCD to see all
268 the processors in your system, not just the first one.</p>
269
270 <p>
271 Consult the following table for a partial list of available kernels and
272 options or press F2 and F3 to view the help screens.</p>
273
161 <table> 274<table>
162 <tr> 275 <tr>
163 <th>Available kernels.</th> 276 <th>Available kernels</th>
164 <th>description</th> 277 <th>description</th>
165 </tr> 278 </tr>
166 279
167 <tr><ti>gentoo</ti><ti>basic gentoo kernel (default)</ti></tr> 280 <tr><ti>gentoo</ti><ti>standard gentoo kernel (default)</ti></tr>
168 <tr><ti>800</ti><ti>800x600 framebuffer mode</ti></tr>
169 <tr><ti>1024</ti><ti>1024x768 framebuffer mode (default)</ti></tr>
170 <tr><ti>1280</ti><ti>1280x1024 framebuffer mode</ti></tr>
171 <tr><ti>nofb</ti><ti>framebuffer mode disabled</ti></tr> 281 <tr><ti>nofb</ti><ti>framebuffer mode disabled</ti></tr>
172 <tr><ti>smp</ti><ti>loads a smp kernel in noframebuffer mode</ti></tr> 282 <tr><ti>smp</ti><ti>loads a smp kernel in noframebuffer mode</ti></tr>
173 <tr><ti>acpi</ti><ti>enables acpi=on + loads acpi modules during init</ti></tr> 283 <tr><ti>acpi</ti><ti>enables acpi=on + loads acpi modules during init</ti></tr>
174 <tr><ti>memtest</ti><ti>boots the memory testing program</ti></tr> 284 <tr><ti>memtest</ti><ti>boots the memory testing program</ti></tr>
175 285
176 </table> 286 </table>
177 287
178 <p> 288 <p>
179 <table> 289 <table>
180 <tr> 290 <tr>
181 <th>Available boot options.</th> 291 <th>Available boot options</th>
182 <th>description</th> 292 <th>description</th>
183 </tr> 293 </tr>
184 294
185 <tr><ti>doataraid</ti> 295 <tr><ti>doataraid</ti>
186 <ti>loads ide raid modules from initrd</ti></tr> 296 <ti>loads ide raid modules from initrd</ti></tr>
221 <tr><ti>cdcache</ti> 331 <tr><ti>cdcache</ti>
222 <ti>Cache the entire runtime portion of cd in ram, This uses 40mb of RAM , but allows you to umount /mnt/cdrom and mount another cdrom.</ti></tr> 332 <ti>Cache the entire runtime portion of cd in ram, This uses 40mb of RAM , but allows you to umount /mnt/cdrom and mount another cdrom.</ti></tr>
223 333
224 </table></p> 334 </table></p>
225 335
336
226 <p> Once you hit Enter, you will be greeted with the standard kernel 337 <p>Once you hit Enter, you will be greeted with an even fancier boot
227booting output, kernel and initrd messages, followed by the normal Gentoo 338 screen and progress bar:</p>
228Linux boot sequence. You will be automatically logged in as 339
229&quot;<c>root</c>&quot; and the root password will be set to a random string 340 <figure link="/images/install/livecd-1.4-boot.png" caption="The Gentoo
230for security purposes. You should have a root (&quot;<c>#</c>&quot;) prompt 341 Linux Live CD booting" />
342
343
344 <p>Once the boot process completes, you will be automatically logged in
345 to the "Live" Gentoo Linux as
346&quot;<c>root</c>&quot;, the "super user." You should have a root (&quot;<c>#</c>&quot;) prompt
231on the current console, and can also switch to other consoles by pressing 347on the current console, and can also switch to other consoles by pressing
232Alt-F2, Alt-F3 and Alt-F4. Get back to the one you started on by pressing 348Alt-F2, Alt-F3 and Alt-F4. Get back to the one you started on by pressing
233Alt-F1. At this point you should set the root password, type <c>passwd</c> and 349Alt-F1. The console will look like this:</p>
234follow the prompts. 350
235 </p> 351 <figure link="/images/install/livecd-1.4-con.png" caption="The Gentoo
352 Linux Live CD console" />
353
354<note><b>Advanced users:</b> When the Live CD boots, the Live CD root password is
355set to a random string for security purposes. If you plan to start
356<c>sshd</c> to allow remote logins to your Live CD, you should set the Live
357CD root password now by typing <c>passwd</c> and following the prompts.
358Otherwise, you will not know the proper password for logging into the Live
359CD over the network. </note>
360
236 <p>You've probably also noticed that above your <c>#</c> prompt is a bunch of help text 361 <p>You've probably also noticed that above your <c>#</c> prompt is a bunch of help text
237 that explains how to do things like configure your Linux networking and telling you where you can find 362 that explains how to do things like configure your Linux networking and telling you where you can find
238 the Gentoo Linux stage tarballs and packages on your CD. 363 the Gentoo Linux stage tarballs and packages on your CD.
239 </p> 364 </p>
240 </body> 365 </body>
241 </section> 366 </section>
242 </chapter> 367 </chapter>
243 <chapter> 368 <chapter>
244 <title>Load Kernel Modules</title> 369 <title>Optional hardware configuration</title>
245 <section> 370 <section>
246 <body> 371 <body>
372 <p>When the Live CD boots, it tries to detect all your hardware
373 devices and loads the appropiate kernel modules to support your
374 hardware. In the vast majority of cases, it does a very good job.
375 However, in some cases, it may not auto-load the kernel modules
247 <p>If the PCI autodetection missed some of your hardware, you 376 you need. If the PCI auto-detection missed some of your system's hardware, you
248 will have to load the appropriate kernel modules manually. 377 will have to load the appropriate kernel modules manually.
249 To view a list of all available network card modules, type <c>ls 378 To view a list of all available network card modules, type <c>ls
250 /lib/modules/*/kernel/drivers/net/*</c>. To load a particular module, 379 /lib/modules/`uname -r`/kernel/drivers/net/*</c>. To load a particular module,
251 type: 380 type:
252 </p> 381 </p>
253<pre caption="PCI Modules Configuration"> 382<pre caption="PCI Modules Configuration">
254# <c>modprobe pcnet32</c> 383# <c>modprobe pcnet32</c>
255<comment>(replace pcnet32 with your NIC module)</comment> 384<comment>(replace pcnet32 with your NIC module)</comment>
263<comment>(replace aic7xxx with your SCSI adapter module)</comment> 392<comment>(replace aic7xxx with your SCSI adapter module)</comment>
264# <c>modprobe sd_mod</c> 393# <c>modprobe sd_mod</c>
265<comment>(sd_mod is the module for SCSI disk support)</comment> 394<comment>(sd_mod is the module for SCSI disk support)</comment>
266</pre> 395</pre>
267 <note> 396 <note>
268 Support for a SCSI CD-ROMs and disks are built-in in the kernel. 397 Support for SCSI CD-ROMs and disks are built-in in the kernel.
269 </note> 398 </note>
270 <p>The Gentoo LiveCD should have enabled DMA on your disks, but if it did not, 399
400 <note><b>Advanced users:</b> The Gentoo LiveCD should have enabled DMA
401 on your disks so that disk transfers are as fast as possible, but if it did not,
271 <c>hdparm</c> can be used to set DMA on your drives. </p> 402 <c>hdparm</c> can be used to set DMA on your drives as follows:
272<pre caption="Setting DMA"> 403 <pre caption="Setting DMA">
273<comment>Replace hdX with your disk device.</comment> 404<comment>Replace hdX with your disk device.</comment>
274# hdparm -d 1 /dev/hdX <comment>Enables DMA </comment> 405# hdparm -d 1 /dev/hdX <comment>Enables DMA </comment>
275# hdparm -d1 -A1 -m16 -u1 -a64 /dev/hdX 406# hdparm -d1 -A1 -m16 -u1 -a64 /dev/hdX
276<comment>(Enables DMA and other safe performance-enhancing options)</comment> 407<comment>(Enables DMA and other safe performance-enhancing options)</comment>
277# hdparm -X66 /dev/hdX 408# hdparm -X66 /dev/hdX
278<comment>(Force-enables Ultra-DMA -- dangerous -- may cause some drives to mess up)</comment> 409<comment>(Force-enables Ultra-DMA -- dangerous -- may cause some drives to mess up)</comment>
279</pre> 410</pre>
411 </note>
412
413
280 </body> 414 </body>
281 </section>
282 </chapter>
283<!-- THIS SECTION SHOULD BE DEPRECATED WITH HOTPLUG ENABLED IN 1.4_rc3 (drobbins)
284 <chapter>
285 <title>Loading PCMCIA Kernel Modules</title>
286 <section> 415 </section>
287 <body>
288 <p>If you have a PCMCIA network card, you will need to perform a few extra steps.
289 </p>
290 <warn>To avoid problems with <c>cardmgr</c>, you <e>must</e> run it <e>before</e> you enter the chroot
291 portion of the install. </warn>
292<pre caption="Loading PCMCIA Modules">
293# <i>modprobe pcmcia_core</i>
294# <i>modprobe i82365</i>
295# <i>modprobe ds</i>
296# <i>cardmgr -f</i>
297</pre>
298 <p>As <c>cardmgr</c> detects which hardware is present, your speaker should emit a
299 few reassuring beeps, and your PCMCIA network card should be active. You can
300 of course insert the PCMCIA card after loading <c>cardmgr</c> too, if that is
301 preferable. (Technically, you need not run
302 <c>cardmgr</c> if you know exactly which module your PCMCIA card requires.
303 But if you don't, loading all PCMCIA modules and see which sticks won't work,
304 as all PCMCIA modules load obligingly and hang around for a PCMCIA card to
305 drop by. <c>cardmgr</c> will also unload the module(s) for any card when you
306 remove it). </p>
307 </body>
308 </section>
309 </chapter>
310-->
311 <chapter> 416 </chapter>
312 <title>Configuring Networking</title> 417 <chapter>
418 <title>Optional Networking configuration</title>
313 <section> 419 <section>
314 <title>Maybe it just works?</title> 420 <title>Maybe it just works?</title>
315 <body> 421 <body>
316 <p>If you're using a 1.4_rc3 or later LiveCD, it is possible that your networking has already been 422 <p>If your system is plugged into an Ethernet network, it is very
423 likely that your networking configuration has already been
317 configured automatically for you. If so, you should be able to take advantage of the many included 424 set up automatically for you. If so, you should be able to take advantage of the many included
318 network-aware commands on the LiveCD such as <c>ssh</c>, <c>scp</c>, <c>ping</c>, <c>irssi</c>, <c>wget</c> and <c>lynx</c>, 425 network-aware commands on the LiveCD such as <c>ssh</c>, <c>scp</c>, <c>ping</c>, <c>irssi</c>, <c>wget</c> and <c>lynx</c>,
319 among others.</p> 426 among others.</p>
320 427
321 <p>If networking has been configured for you, the <c>/sbin/ifconfig</c> command should 428 <p>If networking has been configured for you, the <c>/sbin/ifconfig</c> command should
322 list some internet interfaces besides <c>lo</c>, such as <c>eth0</c>: 429 list some internet interfaces besides <c>lo</c>, such as <c>eth0</c>:
390 <p>We need to setup just enough networking so that we can download 497 <p>We need to setup just enough networking so that we can download
391 sources for the system build, as well as the required localhost interface. The needed information is explained in the next table.</p> 498 sources for the system build, as well as the required localhost interface. The needed information is explained in the next table.</p>
392 499
393<table> 500<table>
394<tr><th>Information</th><th>Description</th><th>Example value</th></tr> 501<tr><th>Information</th><th>Description</th><th>Example value</th></tr>
395<tr><ti>IP address</ti><ti>The IP-address you want to assign to your network card</ti><ti>192.168.1.2</ti></tr> 502<tr><ti>IP address</ti><ti>The IP address you want to assign to your network card</ti><ti>192.168.1.2</ti></tr>
396<tr><ti>Broadcast address</ti><ti>The IP-address which will broadcast the packets to all the hosts in the network.</ti><ti>192.168.1.255</ti></tr> 503<tr><ti>Broadcast address</ti><ti>The IP address which will broadcast the packets to all the hosts in the network.</ti><ti>192.168.1.255</ti></tr>
397<tr><ti>Network mask</ti><ti>The mask which is used together with the IP address to see what part of the address is for network-identification and host-identification</ti><ti>255.255.255.0</ti></tr> 504<tr><ti>Network mask</ti><ti>The mask which is used together with the IP address to see what part of the address is for network-identification and host-identification</ti><ti>255.255.255.0</ti></tr>
398<tr><ti>Gateway</ti><ti>The IP-address of the computer which will forward the packets that are not meant for the local network (most of the time the computer which shares the internet connection)</ti><ti>192.168.1.1</ti></tr> 505<tr><ti>Gateway</ti><ti>The IP address of the computer which will forward the packets that are not meant for the local network (most of the time the computer which shares the internet connection)</ti><ti>192.168.1.1</ti></tr>
399</table> 506</table>
400 507
401 <p>Type in the following commands, replacing 508 <p>Type in the following commands, replacing
402 $IFACE with your network interface (typically <c>eth0</c>), $IPNUM 509 $IFACE with your network interface (typically <c>eth0</c>), $IPNUM
403 with your IP address, $BCAST with your broadcast address, and $NMASK 510 with your IP address, $BCAST with your broadcast address, and $NMASK
444 <body> 551 <body>
445 <p>Networking should now be configured and usable. You should be able to use the included 552 <p>Networking should now be configured and usable. You should be able to use the included
446 <c>ssh</c>, <c>scp</c>, <c>lynx</c>, <c>irssi</c> and <c>wget</c> commands to connect to other machines on your LAN or the Internet.</p> 553 <c>ssh</c>, <c>scp</c>, <c>lynx</c>, <c>irssi</c> and <c>wget</c> commands to connect to other machines on your LAN or the Internet.</p>
447 </body> 554 </body>
448 </section> 555 </section>
449 <section>
450 <title>I don't have networking!</title>
451 <body>If you don't have networking there is some help in the
452 <uri link="http://forums.gentoo.org/">Gentoo Forums</uri>.
453 Some useful links can be found at <uri>http://forums.gentoo.org/viewtopic.php?t=43025</uri>.
454 </body>
455 </section>
456 </chapter> 556 </chapter>
457 <chapter> 557 <chapter>
458 <title>Setting your system's date and time</title> 558 <title>Setting your system's date and time</title>
459 <section> 559 <section>
460 <body> 560 <body>
522 622
523<p> We can take a look at a disk's partition table by running <c>fdisk</c>, 623<p> We can take a look at a disk's partition table by running <c>fdisk</c>,
524specifying a block device that represents a full disk as an argument: </p> 624specifying a block device that represents a full disk as an argument: </p>
525 625
526<note>Alternate interfaces to the disk's partition table include <c>cfdisk</c>, 626<note>Alternate interfaces to the disk's partition table include <c>cfdisk</c>,
527<c>parted</c> and <c>partimage</c>. We recommend <c>fdisk</c> becuase it's 627<c>parted</c> and <c>partimage</c>. We recommend <c>fdisk</c> because it's
528more powerfull and well known in the Unix/Linux world.</note> 628more powerful and well known in the Unix/Linux world.</note>
529 629
530<pre caption="Starting up fdisk"> 630<pre caption="Starting up fdisk">
531# fdisk /dev/hda 631# fdisk /dev/hda
532</pre> 632</pre>
533<p> 633<p>
683 <ti>ext2/3 highly recommended (easiest); if ReiserFS then mount with <c>-o notail</c>. If you will be using ext3 or ReiserFS, you must add the size of the journal to the partitionsize; in these cases 64 Megabytes is recommended</ti> 783 <ti>ext2/3 highly recommended (easiest); if ReiserFS then mount with <c>-o notail</c>. If you will be using ext3 or ReiserFS, you must add the size of the journal to the partitionsize; in these cases 64 Megabytes is recommended</ti>
684 <ti>/dev/hda1</ti> 784 <ti>/dev/hda1</ti>
685 </tr> 785 </tr>
686 <tr> 786 <tr>
687 <ti>swap partition (no longer a 128 Megabyte limit, now 2GB)</ti> 787 <ti>swap partition (no longer a 128 Megabyte limit, now 2GB)</ti>
688 <ti>Generally, configure a swap area that is between one to two times the size of the physical RAM 788 <ti>Generally, configure a swap area that is between one and two times the size of the physical RAM
689 in your system.</ti> 789 in your system.</ti>
690 <ti>Linux swap</ti> 790 <ti>Linux swap</ti>
691 <ti>/dev/hda2</ti> 791 <ti>/dev/hda2</ti>
692 </tr> 792 </tr>
693 <tr> 793 <tr>
747enter. When prompted for the last cylinder, type <c>+32M</c> to create a 847enter. When prompted for the last cylinder, type <c>+32M</c> to create a
748partition 32MB in size. You can see output from these steps below:</p> 848partition 32MB in size. You can see output from these steps below:</p>
749 849
750<note> 850<note>
751Journaled filesystems require extra space for their journal. Default settings 851Journaled filesystems require extra space for their journal. Default settings
752require about 33 Megabytes of space. Therefor, if you are using a journaled 852require about 33 Megabytes of space. Therefore, if you are using a journaled
753filesystem for <path>/boot</path>, you should type <c>+64M</c> when prompted 853filesystem for <path>/boot</path>, you should type <c>+64M</c> when prompted
754for the last cylinder. 854for the last cylinder.
755</note> 855</note>
756 856
757<pre caption="Steps to create our boot partition"> 857<pre caption="Steps to create our boot partition">
884a uninterruptible power supply. Because XFS aggressively caches in-transit data 984a uninterruptible power supply. Because XFS aggressively caches in-transit data
885in RAM, improperly designed programs (those that don't take proper precautions 985in RAM, improperly designed programs (those that don't take proper precautions
886when writing files to disk, and there are quite a few of them) can lose a good 986when writing files to disk, and there are quite a few of them) can lose a good
887deal of data if the system goes down unexpectedly.</p> 987deal of data if the system goes down unexpectedly.</p>
888 988
889<p>JFS is IBM's own high performance journaling filesystem. It has recently 989<p>JFS is IBM's high-performance journaling filesystem. It has recently
890become production-ready, and there hasn't been a sufficient track record to 990become production-ready, and there hasn't been a sufficient track record to
891comment either positively nor negatively on its general stability at this 991comment positively nor negatively on its general stability at this
892point.</p> 992point.</p>
893 993
894<p>If you're looking for the most rugged journaling filesystem, use ext3. If 994<p>If you're looking for the most rugged journaling filesystem, use ext3. If
895you're looking for a good general-purpose high-performance filesystem with 995you're looking for a good general-purpose high-performance filesystem with
896journaling support, use ReiserFS; both ext3 and ReiserFS are mature, 996journaling support, use ReiserFS; both ext3 and ReiserFS are mature,
1015 <title>Selecting the desired stage tarball</title> 1115 <title>Selecting the desired stage tarball</title>
1016 <body> 1116 <body>
1017 1117
1018<p> 1118<p>
1019Now, you need to decide which one you would like to use as a 1119Now, you need to decide which one you would like to use as a
1020basis for the install if you haven't already.</p> 1120basis for the install if you haven't already.
1021 1121The stages on the Live CD are
1022<p>If you are using the &quot;from scratch, build everything&quot; install 1122in <path>/mnt/cdrom/stages/</path>, and you can type <c>ls
1023method, you will want to use the <path>stage1-x86-1.4_rc4.tar.bz2</path> image. 1123/mnt/cdrom/stages/</c>
1024If you're using one of our bigger CDs like the "3stages" ISO, you will also
1025have a choice of a stage2 and stage3 image. These images allow you to save
1026time at the expense of configurability (we've already chosen compiler
1027optimizations and default USE variables for you.) The stages on the CD are
1028accessible at <path>/mnt/cdrom/gentoo</path>, and you can type <c>ls /mnt/cdrom/gentoo</c>
1029to see what's available on your CD.</p> 1124to see what's available on your CD.</p>
1030 1125
1126<p><b>GRP users</b> should use the <path>stage3-xx-yy.tar.bz2</path> tarball.</p>
1127
1031<p>If you would like to perform an install using a stage tarball that is 1128<p>If you would like to perform an install using a stage tarball that is
1129<i>not</i> on your CD (which will likely be the case if you're using our
1032<i>not</i> on your CD , this is still possible, but you'll need to download the 1130"basic" Live CD), this is still possible, but you'll need to download the
1033stage you want using the following instructions. If you already have the stage 1131stage you want using the following instructions. If you already have the stage
1034tarball you want to use (most users), then proceed to the "Extracting the stage 1132tarball you want to use (which most users will have), then proceed to the
1035tarball" section.</p> 1133"Extracting the stage tarball" section.</p>
1036 1134
1037<pre caption="Downloading Required Stages"> 1135<pre caption="Downloading Required Stages">
1038# <c>cd /mnt/gentoo</c> 1136# <c>cd /mnt/gentoo</c>
1039<comment>Use lynx to get the URL for your tarball:</comment> 1137<comment>Use lynx to get the URL for your tarball:</comment>
1040# <c>lynx http://www.ibiblio.org/pub/Linux/distributions/gentoo/releases/1.4_rc4/x86/</c> 1138# <c>lynx http://gentoo.oregonstate.edu/releases/x86/1.4/</c>
1041<comment>Use <c>Up</c> and <c>Down</c> arrows keys (or the <c>TAB</c> key) to go to the right directory 1139<comment>Use <c>Up</c> and <c>Down</c> arrows keys (or the <c>TAB</c> key) to go to the right directory
1042Highlight the appropriate stage you want to download 1140Highlight the appropriate stage you want to download
1043Press <c>d</c> which will initiate the download 1141Press <c>d</c> which will initiate the download
1044Save the file and quit the browser 1142Save the file and quit the browser
1045 1143
1063 1161
1064<pre caption="Unpacking the Stages"> 1162<pre caption="Unpacking the Stages">
1065# <c>cd /mnt/gentoo</c> 1163# <c>cd /mnt/gentoo</c>
1066<comment>Change "stage3" to "stage2" or "stage1" if you want to start from these stages instead.</comment> 1164<comment>Change "stage3" to "stage2" or "stage1" if you want to start from these stages instead.</comment>
1067<comment>If you downloaded your stage tarball, change the path below to begin with "/mnt/gentoo/" 1165<comment>If you downloaded your stage tarball, change the path below to begin with "/mnt/gentoo/"
1068instead of "/mnt/cdrom/gentoo/".</comment> 1166instead of "/mnt/cdrom/stages/".</comment>
1069# <c>tar -xvjpf /mnt/cdrom/gentoo/stage3-*.tar.bz2</c> 1167# <c>tar -xvjpf /mnt/cdrom/stages/stage3-*.tar.bz2</c>
1070</pre> 1168</pre>
1071 1169
1072<p>If you downloaded your stage tarball to <path>/mnt/gentoo</path>, you can now delete it by typing 1170<p>If you downloaded your stage tarball to <path>/mnt/gentoo</path>, you can now delete it by typing
1073<c>rm /mnt/gentoo/stage*.tar.bz2</c>.</p> 1171<c>rm /mnt/gentoo/stage*.tar.bz2</c>.</p>
1172</body>
1173</section>
1174<section>
1175<title>GRP package/snapshot steps</title>
1176<body>
1177<impo>The following instructions are for GRP users only.</impo>
1178<p><b>GRP Users</b>: There is a Portage snapshot on the Live CD. You will
1179need to use this snapshot so that you can skip the <c>emerge sync</c> step
1180later in this document, since <c>emerge sync</c> requires a network
1181connection. Untar this snapshot as follows:</p>
1182<pre caption="Using Portage snapshot">
1183<comment>Replace yyyymmdd with the datestamp in the filename.</comment>
1184# <c>tar -xvjf /mnt/cdrom/snapshots/portage-yyyymmdd.tar.bz2 -C /mnt/gentoo/usr</c>
1185</pre>
1186<p>This will extract a snapshot of the Portage tree to your fresh Gentoo
1187install. Now you won't need to connect to the Internet and use <c>emerge
1188sync</c> to download a Portage tree. Now, copy distfiles and packages
1189from the Live CD into place:</p>
1190
1191<pre caption="Copying GRP files">
1192# <c>cp -R /mnt/cdrom/distfiles /mnt/gentoo/usr/portage/distfiles</c>
1193# <c>cp -a /mnt/cdrom/packages/* /mnt/gentoo/usr/portage/packages/</c>
1194</pre>
1195
1196<p>All relevant files are now in place for using GRP. You should now have
1197everything copied over and unpacked that you'll need to install Gentoo Linux
1198-- even without a network connection.</p>
1199
1074</body> 1200</body>
1075</section> 1201</section>
1076<section> 1202<section>
1077<title>Entering the chroot</title> 1203<title>Entering the chroot</title>
1078<body> 1204<body>
1082</p> 1208</p>
1083 1209
1084<note> 1210<note>
1085You may receive a notice during <c>env-update</c> telling you that 1211You may receive a notice during <c>env-update</c> telling you that
1086<path>/etc/make.profile/make.defaults</path> isn't available: ignore it. We are 1212<path>/etc/make.profile/make.defaults</path> isn't available: ignore it. We are
1087going to issue <c>emerge sync</c> later on in this document which will resolve 1213going to issue <c>emerge sync</c> later on in this document, which will resolve
1088the problem. 1214the problem.
1089</note> 1215</note>
1090 1216
1091<pre caption="Prepping and entering the chroot environment"> 1217<pre caption="Prepping and entering the chroot environment">
1092# <c>mount -t proc proc /mnt/gentoo/proc</c> 1218# <c>mount -t proc proc /mnt/gentoo/proc</c>
1093# <c>cp /etc/resolv.conf /mnt/gentoo/etc/resolv.conf</c> 1219# <c>cp /etc/resolv.conf /mnt/gentoo/etc/resolv.conf</c>
1094# <c>chroot /mnt/gentoo /bin/bash</c> 1220# <c>chroot /mnt/gentoo /bin/bash</c>
1095# <c>env-update</c> 1221# <c>env-update</c>
1096Regenerating /etc/ld.so.cache... 1222Regenerating /etc/ld.so.cache...
1097# <c>source /etc/profile</c> 1223# <c>source /etc/profile</c>
1098<comment>(The above points your shell to the new paths and updated binaries.)</comment> 1224<comment>(The above points your shell to the new paths and updated binaries).</comment>
1099</pre> 1225</pre>
1100 <p>After you execute these commands, you will be &quot;inside&quot; your new Gentoo Linux environment in <path>/mnt/gentoo</path>. 1226 <p>After you execute these commands, you will be &quot;inside&quot; your new Gentoo Linux environment in <path>/mnt/gentoo</path>.
1101 We can perform the rest of the installation process inside the chroot. 1227 We can perform the rest of the installation process inside the chroot.
1102 </p> 1228 </p>
1103 </body> 1229 </body>
1119# <i>mirrorselect -i -r</i> 1245# <i>mirrorselect -i -r</i>
1120</pre> 1246</pre>
1121 1247
1122--> 1248-->
1123 1249
1250
1251
1252<impo>If you doing a GRP install you can ignore the following section on
1253<c>emerge sync</c>.</impo>
1254
1124<p>Now, you will need to run <c>emerge sync</c>. This command tells Portage to download 1255<p>Now, you will need to run <c>emerge sync</c>. This command tells Portage
1125the most recent copy of the Gentoo Linux Portage tree. 1256to download the most recent copy of the Gentoo Linux Portage tree from the
1126The Portage tree 1257Internet. If you extracted a Portage tree snapshot from "CD 1" earlier, you
1127contains all the scripts (called ebuilds) used to build every package 1258can safely skip this step. The Portage tree contains all the scripts
1259(called ebuilds) used to build every package under Gentoo Linux. Currently,
1128under Gentoo Linux. Currently, we have ebuild scripts for close to 4000 packages. Once <c>emerge sync</c> 1260we have ebuild scripts for close to 4000 packages. Once <c>emerge sync</c>
1129completes, you will have a complete Portage tree in <path>/usr/portage</path>.</p> 1261completes, you will have a complete Portage tree in
1262<path>/usr/portage</path>.</p>
1130 1263
1131<pre caption="Updating Using sync"> 1264<pre caption="Updating Using sync">
1132# <c>emerge sync</c> 1265# <c>emerge sync</c>
1133</pre> 1266</pre>
1134 1267
1150fine. More information on <c>USE</c> flags can be found <uri 1283fine. More information on <c>USE</c> flags can be found <uri
1151link="http://www.gentoo.org/doc/en/use-howto.xml">here</uri>. A complete list 1284link="http://www.gentoo.org/doc/en/use-howto.xml">here</uri>. A complete list
1152of current USE flags can be found <uri 1285of current USE flags can be found <uri
1153link="http://www.gentoo.org/dyn/use-index.xml">here</uri>. </p> 1286link="http://www.gentoo.org/dyn/use-index.xml">here</uri>. </p>
1154 1287
1155<p>You also should set appropriate <c>CHOST</c>, <c>CFLAGS</c> and 1288<p>If you are starting from a stage1 tarball, You also should set appropriate <c>CHOST</c>, <c>CFLAGS</c> and
1156<c>CXXFLAGS</c> settings for the kind of system that you are creating 1289<c>CXXFLAGS</c> settings for the kind of system that you are creating
1157(commented examples can be found further down in the file.) These settings 1290(commented examples can be found further down in the file). If you are using
1291a stage2 or stage3 tarball, these settings will already be configured
1292optimally and should not require any modification.</p>
1293
1294<impo><b>Advanced users:</b> The <c>CFLAGS</c> and <c>CXXFLAGS</c> settings
1295settings
1158will be used to tell the C and C++ compiler how to optimize the code that 1296are used to tell the C and C++ compiler how to optimize the code that
1159is generated on your system. It is common for users with Athlon XP processors 1297is generated on your system. It is common for users with Athlon XP processors
1160to specify a "-march=athlon-xp" setting in their CFLAGS and CXXFLAGS settings 1298to specify a "-march=athlon-xp" setting in their CFLAGS and CXXFLAGS settings
1161so that all packages built will be optimized for the instruction set and 1299so that all packages built will be optimized for the instruction set and
1162performance characteristics of their CPU, for example. The <path>/etc/make.conf</path> 1300performance characteristics of their CPU, for example. The <path>/etc/make.conf</path>
1163file contains a general guide for the proper settings of CFLAGS and CXXFLAGS.</p> 1301file contains a general guide for the proper settings of CFLAGS and CXXFLAGS.
1164 1302</impo>
1303
1304<!-- needs qa
1305<note><b>Advanced users:</b>If you are building from a stage1 and don't want
1306to manually configure CFLAGS and CXXFLAGS, you can use the <c>genflags</c>
1307utility, which will try to guess accurate flags for your CPU architecture.
1308Simply type <c>emerge -O genflags</c> and then execute
1309<c>info2flags</c>. <c>info2flags</c> will suggest CHOST, CFLAGS, and
1310CXXFLAGS settings, which you can then add to
1311<path>/etc/make.conf</path>.</note>
1312-->
1313
1165<p>If necessary, you can also set proxy information here if you are behind a 1314<p>If necessary, you can also set proxy information here if you are behind a
1166firewall. Use the following command to edit <path>/etc/make.conf</path> using <c>nano</c>, 1315firewall. Use the following command to edit <path>/etc/make.conf</path> using <c>nano</c>,
1167a simple visual editor. 1316a simple visual editor.
1168</p> 1317</p>
1169<pre caption="Setting make.conf Options"> 1318<pre caption="Setting make.conf Options">
1170# <c>nano -w /etc/make.conf</c> 1319# <c>nano -w /etc/make.conf</c>
1171<comment>(Edit CHOST, CFLAGS, CXXFLAGS and any necessary USE or proxy settings)</comment>
1172</pre> 1320</pre>
1173 <note> 1321 <note>
1174 People who need to substantially customize the build process should take a look at 1322 <b>Advanced users:</b> People who need to substantially customize the build process should take a look at
1175 the <path>/etc/make.globals</path> file. This file comprises gentoo defaults and 1323 the <path>/etc/make.globals</path> file. This file comprises gentoo defaults and
1176 should never be touched. If the defaults do not suffice, then new values should 1324 should never be touched. If the defaults do not suffice, then new values should
1177 be put in <path>/etc/make.conf</path>, as entries in <path>make.conf</path> 1325 be put in <path>/etc/make.conf</path>, as entries in <path>make.conf</path>
1178 <comment>override</comment> the entries in <path>make.globals</path>. If you're 1326 <comment>override</comment> the entries in <path>make.globals</path>. If you're
1179 interested in customizing USE settings, look in <path>/etc/make.profile/make.defaults</path>. 1327 interested in customizing USE settings, look in <path>/etc/make.profile/make.defaults</path>.
1180 If you want to turn off any USE settings found here, add an appropriate <c>USE=&quot;-foo&quot;</c> 1328 If you want to turn off any USE settings found here, add an appropriate <c>USE=&quot;-foo&quot;</c>
1181 in <path>/etc/make.conf</path> to turn off any <c>foo</c> USE setting enabled by default 1329 in <path>/etc/make.conf</path> to turn off any <c>foo</c> USE setting enabled by default
1182 in <path>/etc/make.globals</path> or <path>/etc/make.profile/make.defaults</path>. 1330 in <path>/etc/make.globals</path> or <path>/etc/make.profile/make.defaults</path>.
1183 </note> 1331 </note>
1184 <warn>Make sure not to add '<c>static</c>' to your <c>USE</c> variable until after stage1.</warn> 1332 <warn>Make sure not to add '<c>static</c>' to your <c>USE</c> variables until after stage1.</warn>
1185 </body> 1333 </body>
1186 </section> 1334 </section>
1187 </chapter> 1335 </chapter>
1188 <chapter> 1336 <chapter>
1189 <title>Starting from Stage1</title> 1337 <title>Starting from Stage1</title>
1190 <section> 1338 <section>
1191 <body> 1339 <body>
1192 <note>If you are not starting from a stage1 tarball, skip this section.</note> 1340 <note>If you are not starting from a stage1 tarball, skip this section.</note>
1193 <p>The stage1 tarball is for complete customization and optimization. If you have picked this tarball, 1341 <p>The stage1 tarball is for complete customization and optimization. If you have picked this tarball,
1194 you are most likely looking to have an uber-optimized and up-to-date system. Have fun, because optimization 1342 you are most likely looking to have an uber-optimized and up-to-date
1195 is what Gentoo Linux is all about! Installing from a stage1 takes a lot of time, but the result 1343 system. Have fun! Installing from a stage1 takes a lot of time, but the result
1196 is a system that has been optimized from the ground up for your specific machine and needs. 1344 is a system that has been optimized from the ground up for your specific machine and needs.
1197 </p> 1345 </p>
1198 <p>Now, it is time to start the &quot;bootstrap&quot; process. This process takes about two hours on 1346 <p>Now, it is time to start the &quot;bootstrap&quot; process. This process takes about two hours on
1199 my 1200MHz AMD Athlon system. 1347 my 1200MHz AMD Athlon system.
1200During this time, the GNU C library, compiler suite and other key system programs will be built. Start the bootstrap 1348During this time, the GNU C library, compiler suite and other key system programs will be built. Start the bootstrap
1227 <title>Starting from Stage2 and continuing Stage1</title> 1375 <title>Starting from Stage2 and continuing Stage1</title>
1228 <section> 1376 <section>
1229 <body> 1377 <body>
1230 1378
1231 <note>This section is for those continuing a stage1 install or starting at stage2. If 1379 <note>This section is for those continuing a stage1 install or starting at stage2. If
1232 this is not you (ie. you're using a stage3,) then skip this section. 1380 this is not you (ie. you're using a stage3), then skip this section.
1233 </note> 1381 </note>
1234 1382
1235 <warn> 1383 <warn>
1236 If you start from stage2, don't change the CHOST variable in 1384 If you start from stage2, don't change the CHOST variable in
1237 <path>/etc/make.conf</path>. Doing so results in strange and 1385 <path>/etc/make.conf</path>. Doing so results in strange and
1238 broad compilation failures. We are working on fixing this 1386 broad compilation failures. We are working on fixing this
1239 ofcourse. 1387 of course.
1240 </warn> 1388 </warn>
1241 1389
1242 <p>The stage2 tarball already has the bootstrapping done for you. All that you have 1390 <p>The stage2 tarball already has the bootstrapping done for you. All that you have
1243 to do is install the rest of the system. 1391 to do is install the rest of the system.
1244 </p> 1392 </p>
1268 <chapter> 1416 <chapter>
1269 <title>Starting from Stage3</title> 1417 <title>Starting from Stage3</title>
1270 <section> 1418 <section>
1271 <body> 1419 <body>
1272 <note>This section is for those <b>starting</b> with stage3, and not for those who have started 1420 <note>This section is for those <b>starting</b> with stage3, and not for those who have started
1273 with stage1 or stage2 who should skip this section.</note> 1421 with stage1 or stage2 who should skip this section. GRP users should skip ahead to the next section.</note>
1274 1422
1275 <warn> 1423 <warn>
1276 If you start from stage3, don't change the CHOST variable in 1424 Remember, if you start from stage3, don't change the CHOST variable in
1277 <path>/etc/make.conf</path>. Doing so results in strange and 1425 <path>/etc/make.conf</path>. Doing so can result in compilation failures.
1278 broad compilation failures. We are working on fixing this
1279 ofcourse.
1280 </warn> 1426 </warn>
1281 1427
1282
1283 <p>The stage3 tarball provides a fully-functional basic Gentoo system, so no building is required. 1428 <p>The stage3 tarball provides a fully-functional basic Gentoo system,
1429 so no building is required.</p>
1430
1431 <note><b>Advanced users:</b>
1284 However, since the stage3 tarball is pre-built, it may be slightly out-of-date. If this is a concern 1432 However, since the stage3 tarball is pre-built, it may be slightly out-of-date. If this is a concern
1285 for you, you can automatically update your existing stage3 to contain the most up-to-date versions of all system packages 1433 for you, you can automatically update your existing stage3 to contain the most up-to-date versions of all system packages
1286 by performing the following steps. Note that this could take a long time if your stage3 is very old; 1434 by typing <c>export CONFIG_PROTECT="-* /etc/make.conf" emerge -u
1435 system</c> (this requires a network connection). Note that this could take a long time if your stage3 is very old;
1287 otherwise, this process will generally be quick and will allow you to benefit from the very latest 1436 otherwise, this process will generally be quick and will allow you to benefit from the very latest
1288 Gentoo updates and fixes. 1437 Gentoo updates and fixes.
1289 In any case, feel free to skip these 1438 In any case, feel free to skip these
1290 steps and proceed to the next section if you like. 1439 steps and proceed to the next section if you like.
1291 </p> 1440 </note>
1292 1441
1293<pre caption="Getting up-to-date">
1294# <c>export CONFIG_PROTECT="-* /etc/make.conf"</c>
1295# <c>emerge -up system</c>
1296<comment>(lists the packages that would be installed)</comment>
1297# <c>emerge -u system</c>
1298<comment>(actually merges the packages)</comment>
1299# <c>unset CONFIG_PROTECT</c>
1300</pre>
1301 </body> 1442 </body>
1302 </section> 1443 </section>
1303 </chapter> 1444 </chapter>
1304 <chapter> 1445 <chapter>
1305 <title>Setting your time zone</title> 1446 <title>Setting your time zone</title>
1314</pre> 1455</pre>
1315 </body> 1456 </body>
1316 </section> 1457 </section>
1317 </chapter> 1458 </chapter>
1318 <chapter> 1459 <chapter>
1319 <title>Installing the kernel and a System Logger</title> 1460 <title>Installing the kernel and system logger</title>
1320 <section> 1461 <section>
1462 <title>Kernel selections</title>
1321 <body> 1463 <body>
1322 <note> 1464
1323 If you haven't done so, please edit <path>/etc/make.conf</path> to your flavor. 1465 <p>There are two options for installing a kernel. You can either configure your own kernel or use the <c>genkernel</c>
1324 </note> 1466 utility to configure and compile your kernel automatically.</p>
1325 <p>You now need to merge the Linux kernel sources. 1467
1468
1469 <p>Whether configuring a kernel by hand or using <c>genkernel</c>,
1470 you'll need to merge the Linux kernel sources you'd like to use.
1326 Gentoo provides several kernel ebuilds; a list can be found 1471 Gentoo provides several kernel ebuilds; a list can be found
1327 <uri link="/doc/en/gentoo-kernel.xml">here</uri>. If you are uncertain 1472 <uri link="/doc/en/gentoo-kernel.xml">here</uri>. If you are uncertain
1328 which kernel sources to choose, we advise the <c>gentoo-sources</c> or 1473 which kernel sources to choose, we advise using <c>gentoo-sources</c>.
1329 <c>vanilla-sources</c>. If you want XFS support, you should choose 1474 <!--or <c>vanilla-sources</c>.(2.4.21-vanilla has sound issues)--> If you want XFS support, you should choose
1330 <c>xfs-sources</c>. Btw, Gentoo's LiveCD uses the <c>xfs-sources</c>. 1475 <c>xfs-sources</c> or <c>gs-sources</c>. Gentoo's LiveCD uses
1476 <c>gs-sources</c> and <c>xfs-sources</c>. There is also a
1477 <c>gaming-sources</c> kernel optimized for game-playing
1478 responsiveness that works wonderfully for this purpose when the
1479 "Preemptible kernel" option is enabled.
1331 </p> 1480 </p>
1332 <warn> 1481
1333 If you are configuring your own kernel, be careful with the <i>grsecurity</i> option. Being too aggressive with your 1482
1334 security settings can cause certain programs (such as X) to not run properly. If in doubt, leave it out.
1335 </warn>
1336 <p>Choose a kernel and then merge as follows:</p> 1483<p>Choose a kernel and then merge as follows:</p>
1337<pre caption="Emerging Kernel Sources"> 1484<pre caption="Emerging Kernel Sources">
1338# <c>emerge sys-kernel/gentoo-sources</c> 1485# <c>emerge -k sys-kernel/gentoo-sources</c>
1339</pre> 1486</pre>
1340 <p>Once you have a Linux kernel source tree available, it is time to compile your own custom kernel. 1487
1341 </p> 1488 <p>The
1342 <p>Please note that <path>/usr/src/linux</path> is a symlink to your current emerged kernel source package, 1489 <path>/usr/src/linux</path> symbolic link will point to your
1343 and is set automatically by Portage at emerge time. 1490 newly-installed kernel source tree. Portage uses the
1344 If you have multiple kernel source packages, it is necessary to set the <path>/usr/src/linux</path> symlink 1491 <path>/usr/src/linux</path> symbolic link for a special purpose. Any
1345 to the correct one before proceeding. 1492 ebuilds you install that contain kernel modules will be configured
1493 to work with the kernel source tree pointed to by
1494 <path>/usr/src/linux</path>. <path>/usr/src/linux</path> is created
1495 when you emerge your first kernel source package, but after it
1496 exists, Portage does not modify this symbolic link.</p>
1497</body>
1498</section>
1499<section>
1500 <title>Using genkernel to compile your kernel</title>
1501<body>
1502
1503 <p>Now that your kernel source tree is installed, it's now time to
1504 compile your kernel. There are two ways to do this. The first way is
1505 to use our new <c>genkernel</c> script to automatically build a kernel
1506 for you. <c>genkernel</c> works by configuring a kernel nearly
1507 identically to the way our LiveCD kernel is configured. This means
1508 that when you use <c>genkernel</c> to build your kernel, your system
1509 will generally detect all your hardware at boot-time, just like our Live
1510 CD does. Because genkernel doesn't require any manual kernel
1511 configuration, it is an ideal solution for those users who may not
1512 be comfortable compiling their own kernels.</p>
1513
1514 <p>Now, let's see how to use genkernel. First, emerge the genkernel
1515 ebuild:</p>
1516
1517<pre caption="Emerging genkernel">
1518# <c>emerge -k genkernel</c>
1519</pre>
1520
1521 <p>Now, compile your kernel sources by running <c>genkernel</c>:</p>
1522
1523 <note><b>Advanced users:</b> you can type <c>genkernel --config</c> instead,
1524which will cause genkernel to allow you to tweak the default kernel configuration before
1525building begins.</note>
1526
1527
1528<pre caption="Running genkernel">
1529# <c>genkernel</c>
1530Gentoo Linux genkernel, version 1.4
1531 Copyright 2003 Gentoo Technologies, Inc., Bob Johnson, Daniel Robbins
1532 Distributed under the GNU General Public License version 2
1533
1534Settings:
1535 compile optimization: 1 processor(s)
1536 source tree: /usr/src/linux-2.4.20-gaming-r3
1537 config: gentoo (customized)
1538 config loc: /etc/kernels/config-2.4.20-gaming-r3
1539 initrd config: (default) /etc/kernels/settings
1540
1541 * Running "make oldconfig"... [ ok ]
1542 * Logging to /var/log/genkernel.log... [ ok ]
1543 * Starting 2.4.20-gaming-r3 build... [ ok ]
1544 * Running "make dep"... [ ok ]
1545 * Running "make bzImage"... [ ok ]
1546 * Running "make modules"... [ ok ]
1547 * Running "make modules_install"... [ ok ]
1548 * Moving bzImage to /boot/kernel-2.4.20-gaming-r3... [ ok ]
1549 * Building busybox... [ ok ]
1550 * Creating initrd... [ ok ]
1551
1552 * Build completed successfully!
1553
1554 * Please specify /boot/kernel-2.4.20-gaming-r3 and /boot/initrd-2.4.20-gaming-r3
1555 * when customizing your boot loader configuration files.
1556
1557#
1558</pre>
1559
1560 <p>Once <c>genkernel</c> completes, a kernel, full set of modules and <i>initial root disk</i> (initrd) will
1561 be created. We will use the kernel and initrd when configuring a boot loader later in this document. The
1562 initrd will be started immediately after booting to perform hardware autodetection (just like on the Live CD)
1563 before your "real" system starts up.</p>
1564
1565 <p>Now, let's perform one more step to get our system to be more like the Live CD -- let's emerge hotplug.
1566 While the initrd autodetects hardware that is needed to boot your system, hotplug autodetects everything else.
1567 To emerge and enable hotplug, type the following:</p>
1568
1569<pre caption="Emerging and enabling hotplug">
1570# <c>emerge -k hotplug</c>
1571# <c>rc-update add hotplug default</c>
1572</pre>
1573
1574 <p>Finally, you should emerge ebuilds for any additional hardware that is on your system. Here is a list of
1575 kernel-related ebuilds that you could emerge:</p>
1576
1577 <table>
1578 <tr>
1579 <th>ebuild</th>
1580 <th>purpose</th>
1581 <th>command</th>
1346 </p> 1582 </tr>
1583 <tr>
1584 <ti>nvidia-kernel</ti>
1585 <ti>Accelerated NVIDIA graphics for XFree86</ti>
1586 <ti><c>emerge -k nvidia-kernel</c></ti>
1587 </tr>
1588 <tr>
1589 <ti>nforce-net</ti>
1590 <ti>On-board ethernet controller on NVIDIA NForce(2) motherboards</ti>
1591 <ti><c>emerge nforce-net</c></ti>
1592 </tr>
1593 <tr>
1594 <ti>nforce-audio</ti>
1595 <ti>On-board audio on NVIDIA NForce(2) motherboards</ti>
1596 <ti><c>emerge nforce-audio</c></ti>
1597 </tr>
1598 <tr>
1599 <ti>e100</ti>
1600 <ti>Intel e100 Fast Ethernet Adapters</ti>
1601 <ti><c>emerge e100</c></ti>
1602 </tr>
1603 <tr>
1604 <ti>e1000</ti>
1605 <ti>Intel e1000 Gigabit Ethernet Adapters</ti>
1606 <ti><c>emerge e1000</c></ti>
1607 </tr>
1608 <tr>
1609 <ti>emu10k1</ti>
1610 <ti>Creative Sound Blaster Live!/Audigy support</ti>
1611 <ti><c>emerge emu10k1</c></ti>
1612 </tr>
1613 <tr>
1614 <ti>ati-drivers</ti>
1615 <ti>Accelerated ATI Radeon 8500+/FireGL graphics for XFree86</ti>
1616 <ti><c>emerge ati-drivers</c></ti>
1617 </tr>
1347 <note> 1618 <tr>
1619 <ti>xfree-drm</ti>
1620 <ti>Accelerated graphics for ATI Radeon up to 9200, Rage128,
1621 Matrox, Voodoo and other cards for XFree86</ti>
1622 <ti><c>VIDEO_CARDS="yourcard" emerge xfree-drm</c></ti>
1623 </tr>
1624</table>
1625 <p>The nvidia-kernel, ati-drivers and xfree-drm packages will require additional configuration to be enabled.
1626 All other ebuilds listed above should be auto-detected at boot-time by the hotplug package.</p>
1627
1628 <p>Now that you've run and configured your system to use genkernel, you can skip the "manual kernel configuration"
1629section below.</p>
1630</body>
1631</section>
1632<section>
1633<title>Manual kernel configuration</title>
1634<body>
1635
1636 <p>If you opted not to use genkernel to compile your kernel, this section
1637will guide you through the process of configuring and compiling a kernel by
1638hand. Please note that <path>/usr/src/linux</path> is a symlink to your
1639current emerged kernel source package, and is set automatically by Portage at
1640emerge time. If you have multiple kernel source packages, it is necessary to
1641set the <path>/usr/src/linux</path> symlink to the correct one before
1642proceeding. </p>
1643
1644<warn>
1645If you are configuring your own kernel, be careful with the <i>grsecurity</i> option. Being too aggressive with your
1646security settings can cause certain programs (such as X) to not run properly. If in doubt, leave it out.
1647</warn>
1648
1649<note>
1348 If you want to use the same configuration as the LiveCD kernel or base 1650 If you want to use the same configuration as the LiveCD kernel or base
1349 your configuration on it, you should execute 1651 your configuration on it, you should execute
1350 <c>cd /usr/src/linux &amp;&amp; cat /proc/config > .config &amp;&amp; make oldconfig</c>. 1652 <c>cd /usr/src/linux &amp;&amp; cat /proc/config > .config &amp;&amp; make oldconfig</c>.
1351 If you aren't using <c>xfs-sources</c>, this will ask some questions 1653 If you aren't using <c>xfs-sources</c>, this will ask some questions
1352 about differences between your kernelchoice and <c>xfs-sources</c>. 1654 about differences between your kernelchoice and <c>xfs-sources</c>.
1428 1730
1429<pre caption = "Compiling and Installing the kernel"> 1731<pre caption = "Compiling and Installing the kernel">
1430# <c>make dep &amp;&amp; make clean bzImage modules modules_install</c> 1732# <c>make dep &amp;&amp; make clean bzImage modules modules_install</c>
1431# <c>cp /usr/src/linux/arch/i386/boot/bzImage /boot</c> 1733# <c>cp /usr/src/linux/arch/i386/boot/bzImage /boot</c>
1432</pre> 1734</pre>
1433 1735</body>
1736</section>
1737<section>
1738<title>Installing a system logger</title>
1739<body>
1434 <p>Your new custom kernel (and modules) are now installed. Now you need to choose a system 1740 <p>Your new custom kernel (and modules) are now installed. Now you need to choose a system
1435 logger that you would like to install. We offer sysklogd, which is the traditional set 1741 logger that you would like to install. We offer sysklogd, which is the traditional set
1436 of system logging daemons. We also have msyslog and syslog-ng as well as metalog. Power users seem 1742 of system logging daemons. We also have msyslog and syslog-ng as well as metalog. Power users seem
1437 to gravitate away from sysklogd (not very good performance) and towards the 1743 to gravitate away from sysklogd (not very good performance) and towards the
1438 newer alternatives. 1744 newer alternatives.
1439 If in doubt, you may want to try metalog, since it seems to be quite popular. 1745 If in doubt, you may want to try metalog, since it seems to be quite popular.
1440 To merge your logger of choice, type <e>one</e> of the next four lines: 1746 To merge your logger of choice, type <e>one</e> of the next four
1441 </p> 1747lines. </p>
1442<pre caption="Emerging System Logger of Choice"> 1748<pre caption="Emerging System Logger of Choice">
1443# <c>emerge app-admin/sysklogd</c> 1749# <c>emerge -k app-admin/sysklogd</c>
1444# <c>rc-update add sysklogd default</c> 1750# <c>rc-update add sysklogd default</c>
1445<comment>or</comment> 1751<comment>or</comment>
1446# <c>emerge app-admin/syslog-ng</c> 1752# <c>emerge -k app-admin/syslog-ng</c>
1447# <c>rc-update add syslog-ng default</c> 1753# <c>rc-update add syslog-ng default</c>
1448<comment>or</comment> 1754<comment>or</comment>
1449# <c>emerge app-admin/metalog</c> 1755# <c>emerge -k app-admin/metalog</c>
1450# <c>rc-update add metalog default</c> 1756# <c>rc-update add metalog default</c>
1451<comment>or</comment> 1757<comment>or</comment>
1452# <c>emerge app-admin/msyslog</c> 1758# <c>emerge -k app-admin/msyslog</c>
1453# <c>rc-update add msyslog default</c> 1759# <c>rc-update add msyslog default</c>
1454</pre> 1760</pre>
1455 <impo> 1761 <impo>
1456 Metalog flushes output to the disk in blocks, so messages aren't immediately recorded into 1762 Metalog flushes output to the disk in blocks, so messages aren't immediately recorded into
1457 the system logs. If you are trying to debug a daemon, this performance-enhancing behavior 1763 the system logs. If you are trying to debug a daemon, this performance-enhancing behavior
1469<codenote>To turn the buffering back on:</codenote> 1775<codenote>To turn the buffering back on:</codenote>
1470# <c>killall -USR2 metalog</c> 1776# <c>killall -USR2 metalog</c>
1471</pre> 1777</pre>
1472 <p>Now, you may optionally choose a cron package that you would like to use. 1778 <p>Now, you may optionally choose a cron package that you would like to use.
1473 Right now, we offer dcron, fcron and vcron. If you do not know which one to choose, 1779 Right now, we offer dcron, fcron and vcron. If you do not know which one to choose,
1474 you might as well grab vcron. They can be installed as follows: 1780 you might as well grab vcron.
1475 </p> 1781 </p>
1476<pre caption="Choosing a CRON Daemon"> 1782<pre caption="Choosing a CRON Daemon">
1477# <c>emerge sys-apps/dcron</c> 1783# <c>emerge -k sys-apps/dcron</c>
1478# <c>rc-update add dcron default</c> 1784# <c>rc-update add dcron default</c>
1479# <c>crontab /etc/crontab</c> 1785# <c>crontab /etc/crontab</c>
1480<comment>or</comment> 1786<comment>or</comment>
1481# <c>emerge sys-apps/fcron</c> 1787# <c>emerge -k sys-apps/fcron</c>
1482# <c>rc-update add fcron default</c> 1788# <c>rc-update add fcron default</c>
1483# <c>crontab /etc/crontab</c> 1789# <c>crontab /etc/crontab</c>
1484<comment>or</comment> 1790<comment>or</comment>
1485# <c>emerge sys-apps/vcron</c> 1791# <c>emerge -k sys-apps/vcron</c>
1486# <c>rc-update add vcron default</c> 1792# <c>rc-update add vcron default</c>
1487<comment>You do not need to run <c>crontab /etc/crontab</c> if using vcron.</comment> 1793<comment>You do not need to run <c>crontab /etc/crontab</c> if using vcron.</comment>
1488</pre> 1794</pre>
1489 <p>For more information on starting programs and daemons at startup, see the 1795 <p>For more information on starting programs and daemons at startup, see the
1490 <uri link="/doc/en/rc-scripts.xml">rc-script guide</uri>. 1796 <uri link="/doc/en/rc-scripts.xml">rc-script guide</uri>.
1498 <body> 1804 <body>
1499 <p>If you need rp-pppoe to connect to the net, be aware that at this point 1805 <p>If you need rp-pppoe to connect to the net, be aware that at this point
1500 it has not been installed. It would be the good time to do it. </p> 1806 it has not been installed. It would be the good time to do it. </p>
1501<pre caption="Installing rp-pppoe"> 1807<pre caption="Installing rp-pppoe">
1502# <c>USE="-X" emerge rp-pppoe</c> 1808# <c>USE="-X" emerge rp-pppoe</c>
1809<comment>GRP users should type the following:</comment>
1810# <c>USE="-X bindist" emerge -K rp-pppoe</c>
1503</pre> 1811</pre>
1504 1812
1505 <note>The <i>USE="-X"</i> prevents pppoe from installing its optional X interface, which is a good thing, 1813 <note>The <i>USE="-X"</i> prevents pppoe from installing its optional X interface, which is a good thing,
1506 because X and its dependencies would also be emerged. You can always recompile <i>rp-pppoe</i> with 1814 because X and its dependencies would also be emerged. You can always recompile <i>rp-pppoe</i> with
1507 X support later. 1815 X support later.
1513 <p>You may need to install some additional packages in the Portage tree 1821 <p>You may need to install some additional packages in the Portage tree
1514 if you are using any optional features like XFS, ReiserFS or LVM. If you're 1822 if you are using any optional features like XFS, ReiserFS or LVM. If you're
1515 using XFS, you should emerge the <c>xfsprogs</c> package: 1823 using XFS, you should emerge the <c>xfsprogs</c> package:
1516 </p> 1824 </p>
1517<pre caption="Emerging Filesystem Tools"> 1825<pre caption="Emerging Filesystem Tools">
1518# <c>emerge sys-apps/xfsprogs</c> 1826# <c>emerge -k sys-apps/xfsprogs</c>
1519<comment>If you would like to use ReiserFS, you should emerge the ReiserFS tools: </comment> 1827<comment>If you would like to use ReiserFS, you should emerge the ReiserFS tools: </comment>
1520# <c>emerge sys-apps/reiserfsprogs</c> 1828# <c>emerge -k sys-apps/reiserfsprogs</c>
1521<comment>If you would like to use JFS, you should emerge the JFS tools: </comment> 1829<comment>If you would like to use JFS, you should emerge the JFS tools: </comment>
1522# <c>emerge jfsutils</c> 1830# <c>emerge -k jfsutils</c>
1523<comment>If you're using LVM, you should emerge the <c>lvm-user</c> package: </comment> 1831<comment>If you're using LVM, you should emerge the <c>lvm-user</c> package: </comment>
1524# <c>emerge sys-apps/lvm-user</c> 1832# <c>emerge -k sys-apps/lvm-user</c>
1525</pre> 1833</pre>
1526 <p>If you're a laptop user and wish to use your PCMCIA slots on your first 1834 <p>If you're a laptop user and wish to use your PCMCIA slots on your first
1527 real reboot, you will want to make sure you install the <i>pcmcia-cs</i> package. 1835 real reboot, you will want to make sure you install the <i>pcmcia-cs</i> package.
1528 </p> 1836 </p>
1529<pre caption="Emerging PCMCIA-cs"> 1837<pre caption="Emerging PCMCIA-cs">
1530# <c>emerge sys-apps/pcmcia-cs</c> 1838# <c>emerge -k sys-apps/pcmcia-cs</c>
1531</pre> 1839</pre>
1840 <!-- fix the bug or fix the docs, don't send the user in circles
1841(drobbins)
1532 <warn>You will have to re-emerge <i>pcmcia-cs</i> after installation to get PCMCIA 1842 <warn>You will have to re-emerge <i>pcmcia-cs</i> after installation to get PCMCIA
1533 to work. 1843 to work.
1534 </warn> 1844 </warn>
1535 </body> 1845 -->
1846 </body>
1536 </section> 1847 </section>
1537 </chapter> 1848 </chapter>
1538 <chapter> 1849 <chapter>
1539 <title>Modifying /etc/fstab for your machine</title> 1850 <title>Modifying /etc/fstab for your machine</title>
1540 <section> 1851 <section>
1541 <body> 1852 <body>
1853 <impo>
1854 To edit files, remember to use <c>nano -w "filename"</c>.
1855 </impo>
1542 <p>Your Gentoo Linux system is almost ready for use. All we need to do now is configure 1856 <p>Your Gentoo Linux system is almost ready for use. All we need to do now is configure
1543 a few important system files and install the boot loader. 1857 a few important system files and install the boot loader.
1544 The first file we need to 1858 The first file we need to
1545 configure is <path>/etc/fstab</path>. Remember that you should use 1859 configure is <path>/etc/fstab</path>. Remember that you should use
1546 the <c>notail</c> option for your boot partition if you chose to create a ReiserFS filesystem on it. 1860 the <c>notail</c> option for your boot partition if you chose to create a ReiserFS filesystem on it.
1591 should be avoided as much as possible. Therefor it is <e>strongly</e> 1905 should be avoided as much as possible. Therefor it is <e>strongly</e>
1592 recommended to add a user for day-to-day use.</p> 1906 recommended to add a user for day-to-day use.</p>
1593 <pre caption = "Adding a user"> 1907 <pre caption = "Adding a user">
1594# <i>useradd your_user -m -G users,wheel,audio -s /bin/bash</i> 1908# <i>useradd your_user -m -G users,wheel,audio -s /bin/bash</i>
1595# <i>passwd your_user</i></pre> 1909# <i>passwd your_user</i></pre>
1596 <p>Ofcourse substitute <c>your_user</c> with your username.</p> 1910 <p>Substitute <c>your_user</c> with your username.</p>
1597 <p>Whenever you need to perform some task that only root can handle, 1911 <p>Whenever you need to perform some task that only root can handle,
1598 use <c>su -</c> to change your privileges to root-privileges, or take 1912 use <c>su -</c> to change your privileges to root-privileges, or take
1599 a look at the <c>sudo</c> package.</p> 1913 a look at the <c>sudo</c> package.</p>
1600 </body> 1914 </body>
1601 </section> 1915 </section>
1710 <section> 2024 <section>
1711 <title>Notes</title> 2025 <title>Notes</title>
1712 <body> 2026 <body>
1713 <p> In the spirit of Gentoo, users now have more than one bootloader to choose from. 2027 <p> In the spirit of Gentoo, users now have more than one bootloader to choose from.
1714 Using our virtual package system, users are now able to choose between both GRUB and 2028 Using our virtual package system, users are now able to choose between both GRUB and
1715 LILO as their bootloaders. 2029 LILO as their bootloaders.
1716 </p> 2030 </p>
1717 <p> Please keep in mind that having both bootloaders installed is not necessary. 2031 <p> Please keep in mind that having both bootloaders installed is not necessary.
1718 In fact, it can be a hindrance, so please only choose one. 2032 In fact, it can be a hindrance, so please only choose one.
1719 </p> 2033 </p>
2034 <p>In addition, you will need to configure our bootloader differently depending upon
2035whether you are using <c>genkernel</c> (with kernel and initrd) or a kernel you
2036compiled by hand. Be sure to take note of the important differences.</p>
2037
1720 <impo>If you are installing Gentoo Linux on a system with an NVIDIA nForce or nForce2 chipset 2038 <impo>If you are installing Gentoo Linux on a system with an NVIDIA nForce or nForce2 chipset
1721 with an integrated GeForce graphics card, you should use LILO and avoid GRUB. With on-board 2039 with an integrated GeForce graphics card, you should use LILO and avoid GRUB. With on-board
1722 video enabled, the low memory area of your RAM may be used as video RAM. Since GRUB also uses low 2040 video enabled, the low memory area of your RAM may be used as video RAM. Since GRUB also uses low
1723 memory at boot time, it may experience an "out of memory" condition. So, if you have an nForce 2041 memory at boot time, it may experience an "out of memory" condition. So, if you have an nForce
1724 or potentially other board with on-board video, use LILO. Even if you're using off-board video 2042 or potentially other board with on-board video, use LILO. Even if you're using off-board video
1725 right now, it would be nice to be able to remove the graphics card and use the on-board video in a 2043 right now, it would be nice to be able to remove the graphics card and use the on-board video in a
1726 pinch, wouldn't it? :)</impo> 2044 pinch, wouldn't it? :)</impo>
1727 <p>
1728 People who have selected framebuffer in their kernel should add <c>vga=xxx</c> to their bootloader configuration file as a kernel parameter. <c>xxx</c> is one of the values in the following table:
1729 </p>
1730<table>
1731<tr><ti></ti><th>640x480</th><th>800x600</th><th>1024x768</th><th>1280x1024</th></tr>
1732<tr><th>8 bpp</th><ti>769</ti><ti>771</ti><ti>773</ti><ti>775</ti></tr>
1733<tr><th>16 bpp</th><ti>785</ti><ti>788</ti><ti>791</ti><ti>794</ti></tr>
1734<tr><th>32 bpp</th><ti>786</ti><ti>789</ti><ti>792</ti><ti>795</ti></tr>
1735</table>
1736 </body> 2045 </body>
1737 </section> 2046 </section>
1738 <section> 2047 <section>
1739 <title>Configuring GRUB</title> 2048 <title>Configuring GRUB</title>
1740 <body> 2049 <body>
1741 <p>The most critical part of understanding GRUB is getting comfortable with how GRUB 2050 <p>The most critical part of understanding GRUB is getting comfortable with how GRUB
1742 refers to hard drives and partitions. Your Linux partition <path>/dev/hda1</path> is called 2051 refers to hard drives and partitions. Your Linux partition <path>/dev/hda1</path> is called
1743 <path>(hd0,0)</path> under GRUB. Notice the parenthesis around the hd0,0 - they are required. 2052 <path>(hd0,0)</path> under GRUB. Notice the parenthesis around the hd0,0 - they are required.
1744 Hard drives count from zero rather than &quot;a&quot;, and partitions start at zero rather than one. 2053 Hard drives count from zero rather than &quot;a&quot;, and partitions start at zero rather than one.
1745 Be aware too that with the hd devices, only harddrives are counted, not atapi-ide devices such as 2054 Be aware too that with the hd devices, only hard drives are counted, not atapi-ide devices such as
1746 cdrom players, burners, and that the same construct can be used with scsi drives. 2055 cdrom players, burners, and that the same construct can be used with scsi drives.
1747 (Normally they get higher numbers than ide drives except when the bios is configured 2056 (Normally they get higher numbers than ide drives except when the bios is configured
1748 to boot from scsi devices.) Assuming you have a harddrive on /dev/hda, a cdrom player on /dev/hdb, 2057 to boot from scsi devices.) Assuming you have a hard drive on /dev/hda, a cdrom player on /dev/hdb,
1749 a burner on /dev/hdc, a second hard drive on /dev/hdd and no scsi harddrive, 2058 a burner on /dev/hdc, a second hard drive on /dev/hdd and no SCSI hard drive,
1750 <path>/dev/hdd7</path> gets translated to <path>(hd1,6)</path>. 2059 <path>/dev/hdd7</path> gets translated to <path>(hd1,6)</path>.
1751 2060
1752 It might sound tricky, and tricky it is indeed, but as we will see, grub 2061 It might sound tricky, and tricky it is indeed, but as we will see, GRUB
1753 offers a tab completion mechanism that comes handy for those of you having 2062 offers a tab completion mechanism that comes handy for those of you having
1754 a lot of harddrives and partitions and who are a little lost in the 2063 a lot of hard drives and partitions and who are a little lost in the
1755 grub numbering scheme. Having gotten the feel for that, 2064 GRUB numbering scheme. Having gotten the feel for that,
1756 it is time to install GRUB. 2065 it is time to install GRUB.
1757 </p> 2066 </p>
1758 <p>The easiest way to install GRUB is to simply type <c>grub</c> at your chrooted shell prompt: </p> 2067 <p>The easiest way to install GRUB is to simply type <c>grub</c> at your chrooted shell prompt: </p>
1759<pre caption="Installing GRUB"> 2068<pre caption="Installing GRUB">
1760# <c>emerge grub</c> 2069# <c>emerge -k grub</c>
1761# <c>grub</c> 2070# <c>grub</c>
1762</pre> 2071</pre>
1763 <p>You will be presented with the <c>grub&gt;</c> grub 2072 <p>You will be presented with the <c>grub&gt;</c> grub
1764 command-line prompt. Now, you need to type in the 2073 command-line prompt. Now, you need to type in the
1765 right commands to install the GRUB boot record onto your hard drive. In my example configuration, 2074 right commands to install the GRUB boot record onto your hard drive. In my example configuration,
1791 could install GRUB to the boot record of a particular partition. In that case, 2100 could install GRUB to the boot record of a particular partition. In that case,
1792 I would specify a particular partition rather than the entire disk. Once the GRUB 2101 I would specify a particular partition rather than the entire disk. Once the GRUB
1793 boot record has been successfully installed, you can type <c>quit</c> to quit GRUB. 2102 boot record has been successfully installed, you can type <c>quit</c> to quit GRUB.
1794 </p> 2103 </p>
1795 2104
1796 <note> The tab completion mechanism of grub can be used from within grub, 2105 <note> The tab completion mechanism of GRUB can be used from within GRUB,
1797 assuming you wrote <c> root (</c> and that you hit the TAB key, you would 2106 assuming you wrote <c> root (</c> and that you hit the TAB key, you would
1798 be prompted with a list of the available devices (not only harddrives), 2107 be prompted with a list of the available devices (not only hard drives),
1799 hitting the TAB key having written <c> root (hd</c>, grub would print the 2108 hitting the TAB key having written <c> root (hd</c>, GRUB would print the
1800 available harddrives and hitting the TAB key after writing <c> root (hd0,</c> 2109 available hard drives and hitting the TAB key after writing <c> root (hd0,</c>
1801 would make grub print the list of partitions on the first harddrive. 2110 would make GRUB print the list of partitions on the first hard drive.
1802 2111
1803 Checking the syntax of the grub location with completion should really help 2112 Checking the syntax of the GRUB location with completion should really help
1804 to make the right choice. 2113 to make the right choice.
1805 </note> 2114 </note>
1806 2115
1807 <p> 2116 <p>
1808 Gentoo Linux is now 2117 Gentoo Linux is now
1809 installed, but we need to create the <path>/boot/grub/grub.conf</path> file so that 2118 installed, but we need to create the <path>/boot/grub/grub.conf</path> file so that
1810 we get a nice GRUB boot menu when the system reboots. Here is how to do it. 2119 we get a nice GRUB boot menu when the system reboots. Here is how to do it.
1811 </p> 2120 </p>
1812 <impo>To ensure backwards compatibility with GRUB, make sure to make a link from 2121 <impo>To ensure backwards compatibility with GRUB, make sure to make a link from
1813 <i>grub.conf</i> to <i>menu.lst</i>. You can do this by doing 2122 <i>grub.conf</i> to <i>menu.lst</i>. You can do this by doing
1814 <c>ln -s /boot/grub/grub.conf /boot/grub/menu.lst </c>. </impo> 2123 <c>ln -s /boot/grub/grub.conf /boot/grub/menu.lst</c>. </impo>
1815 <p>Now, create the grub.conf file (<c>nano -w /boot/grub/grub.conf</c>), and add the following to it: 2124 <p>Now, create the grub.conf file (<c>nano -w /boot/grub/grub.conf</c>), and add the following to it:
1816 </p> 2125 </p>
1817<pre caption="Grub.conf for GRUB"> 2126<pre caption="grub.conf for GRUB">
1818default 0 2127default 0
1819timeout 30 2128timeout 30
1820splashimage=(hd0,0)/boot/grub/splash.xpm.gz 2129splashimage=(hd0,0)/boot/grub/splash.xpm.gz
1821 2130
2131<comment>#if you compiled your own kernel, use something like this:</comment>
1822title=My example Gentoo Linux 2132title=My example Gentoo Linux
1823root (hd0,0) 2133root (hd0,0)
1824kernel (hd0,0)/boot/bzImage root=/dev/hda3 2134kernel (hd0,0)/boot/bzImage root=/dev/hda3
2135
2136<comment>#if you're using genkernel, use something like this instead:</comment>
2137title=My example Gentoo Linux (genkernel)
2138root (hd0,0)
2139kernel (hd0,0)/boot/kernel-KV root=/dev/hda3
2140initrd (hd0,0)/boot/initrd-KV
1825 2141
1826<comment># Below needed only for people who dual-boot</comment> 2142<comment># Below needed only for people who dual-boot</comment>
1827title=Windows XP 2143title=Windows XP
1828root (hd0,5) 2144root (hd0,5)
1829chainloader (hd0,5)+1 2145chainloader (hd0,5)+1
1830</pre> 2146</pre>
1831 <note> 2147 <note>
1832 (hd0,0) should be written without any spaces inside the parentheses. 2148 (hd0,0) should be written without any spaces inside the parentheses.
1833 </note> 2149 </note>
1834 <impo> 2150 <impo>
1835 If you set up scsi emulation for an IDE cd burner earlier, then to get it to 2151 If you set up SCSI emulation for an IDE cd burner earlier, then to get it to
1836 actually work you need to add an &quot;hdx=ide-scsi&quot; fragment to the kernel 2152 actually work you need to add an &quot;hdx=ide-scsi&quot; fragment to the kernel
1837 line in grub.conf (where &quot;hdx&quot; should be the device for your cd burner). 2153 line in grub.conf (where &quot;hdx&quot; should be the device for your cd burner).
1838 </impo> 2154 </impo>
1839 <p>After saving this file, Gentoo Linux installation is complete. Selecting the first option will 2155 <p>After saving this file, Gentoo Linux installation is complete. Selecting the first option will
1840 tell GRUB to boot Gentoo Linux without a fuss. The second part of the grub.conf file is optional, 2156 tell GRUB to boot Gentoo Linux without a fuss. The second part of the grub.conf file is optional,
1853 (<c>root=/dev/hda3</c>), but you can pass others as well. In particular, you can 2169 (<c>root=/dev/hda3</c>), but you can pass others as well. In particular, you can
1854 turn off devfs by default (not recommended unless you know what you're doing) by 2170 turn off devfs by default (not recommended unless you know what you're doing) by
1855 adding the <c>gentoo=nodevfs</c> option to the <c>kernel</c> command. 2171 adding the <c>gentoo=nodevfs</c> option to the <c>kernel</c> command.
1856 </p> 2172 </p>
1857 <note>Unlike in earlier versions of Gentoo Linux, you no longer have to add 2173 <note>Unlike in earlier versions of Gentoo Linux, you no longer have to add
1858 <c>devfs=mount</c> to the end of the <c>kernel</c> line to enable devfs. In rc6 2174 <c>devfs=mount</c> to the end of the <c>kernel</c> line to enable devfs.
1859 devfs is enabled by default. 2175 Now devfs is enabled by default.
1860 </note> 2176 </note>
1861 </body> 2177 </body>
1862 </section> 2178 </section>
1863 <section> 2179 <section>
1864 <title>Configuring LILO</title> 2180 <title>Configuring LILO</title>
1868 LILO if you would like to use it instead of GRUB: 2184 LILO if you would like to use it instead of GRUB:
1869 </p> 2185 </p>
1870 <p>The first step is to emerge LILO: 2186 <p>The first step is to emerge LILO:
1871 </p> 2187 </p>
1872<pre caption="Emerging LILO"> 2188<pre caption="Emerging LILO">
1873# <c>emerge lilo</c> 2189# <c>emerge -k lilo</c>
1874</pre> 2190</pre>
1875 <p>Now it is time to configure LILO. Here is a sample configuration file <path>/etc/lilo.conf</path> 2191 <p>Now it is time to configure LILO. Here is a sample configuration file <path>/etc/lilo.conf</path>
1876 </p> 2192 </p>
1877<pre caption="Example lilo.conf"> 2193<pre caption="Example lilo.conf">
1878boot=/dev/hda 2194boot=/dev/hda
1881prompt 2197prompt
1882timeout=50 2198timeout=50
1883lba32 2199lba32
1884default=linux 2200default=linux
1885 2201
2202#use something like the following 4 lines if you compiled your kernel yourself
1886image=/boot/bzImage 2203image=/boot/bzImage
1887 label=linux 2204 label=linux
1888 read-only 2205 read-only
1889 root=/dev/hda3 2206 root=/dev/hda3
2207
2208#if you used genkernel, use something like this:
2209image=/boot/kernel-KV
2210 label=gk_linux
2211 root=/dev/hda3
2212 initrd=/boot/initrd-KV
2213 append="root=/dev/ram0 init=/linuxrc"
2214
1890 2215
1891#For dual booting windows/other OS 2216#For dual booting windows/other OS
1892other=/dev/hda1 2217other=/dev/hda1
1893 label=dos 2218 label=dos
1894</pre> 2219</pre>
1923</pre> 2248</pre>
1924 <p>LILO is configured, and now your machine is ready to boot into Gentoo Linux! 2249 <p>LILO is configured, and now your machine is ready to boot into Gentoo Linux!
1925 </p> 2250 </p>
1926 </body> 2251 </body>
1927 </section> 2252 </section>
2253 <section>
2254 <title>Using framebuffer</title>
2255 <body>
2256 <p>
2257 People who have selected framebuffer in their kernel should add <c>vga=xxx</c> to their bootloader configuration file. <c>xxx</c> is one of the values in the following table:
2258 </p>
2259<table>
2260<tr><ti></ti><th>640x480</th><th>800x600</th><th>1024x768</th><th>1280x1024</th></tr>
2261<tr><th>8 bpp</th><ti>769</ti><ti>771</ti><ti>773</ti><ti>775</ti></tr>
2262<tr><th>16 bpp</th><ti>785</ti><ti>788</ti><ti>791</ti><ti>794</ti></tr>
2263<tr><th>32 bpp</th><ti>786</ti><ti>789</ti><ti>792</ti><ti>795</ti></tr>
2264</table>
2265<p>
2266LILO-users will have to add <c>vga=xxx</c> on top of their configuration
2267file.
2268</p>
2269<p>
2270GRUB-users will have to append <c>vga=xxx</c> to the <c>kernel
2271(hd0,0)...</c> line.
2272</p>
2273</body>
2274</section>
1928 </chapter> 2275 </chapter>
1929 <chapter> 2276 <chapter>
1930 <title>Creating Bootdisks</title> 2277 <title>Creating Bootdisks</title>
1931 <section> 2278 <section>
1932 <title>GRUB Bootdisks</title> 2279 <title>GRUB Bootdisks</title>
1933 <body> 2280 <body>
2281 <impo>
2282 Don't forget to insert a floppy in your floppydrive
2283 before proceeding.
2284 </impo>
1934 <p>It is always a good idea to make a boot disk the first 2285 <p>It is always a good idea to make a boot disk the first
1935 time you install any Linux distribution. This is a security 2286 time you install any Linux distribution. This is a security
1936 blanket, and generally not a bad thing to do. If your hardware doesn't 2287 blanket, and generally not a bad thing to do. If your hardware doesn't
1937 let you install a working bootloader from the chrooted environment, 2288 let you install a working bootloader from the chrooted environment,
1938 you may <e>need</e> to make a GRUB boot disk. 2289 you may <e>need</e> to make a GRUB boot disk.
1949 </body> 2300 </body>
1950 </section> 2301 </section>
1951 <section> 2302 <section>
1952 <title>LILO Bootdisks</title> 2303 <title>LILO Bootdisks</title>
1953 <body> 2304 <body>
2305 <impo>
2306 Don't forget to insert a floppy in your floppydrive
2307 before proceeding.
2308 </impo>
2309
1954 <p>If you are using LILO, it is also a good idea to make a bootdisk: 2310 <p>If you are using LILO, it is also a good idea to make a bootdisk:
1955 </p> 2311 </p>
1956<pre caption="Making a Bootdisk"> 2312<pre caption="Making a Bootdisk">
1957# <c>dd if=/boot/your_kernel of=/dev/fd0 </c> 2313# <c>dd if=/boot/your_kernel of=/dev/fd0 </c>
1958<comment>This will only work if your kernel is smaller than 1.4MB</comment> 2314<comment>This will only work if your kernel is smaller than 1.4MB</comment>
1959</pre> 2315</pre>
1960 </body> 2316 </body>
1961 </section> 2317 </section>
1962 </chapter> 2318 </chapter>
2319
2320 <chapter>
2321 <title>Using GRP</title>
2322 <section>
2323 <body>
2324
2325 <p>GRP users can, at this point, install binary packages:</p>
2326
2327<pre caption="Installing from GRP">
2328# <c>USE="bindist" emerge -k xfree</c>
2329<codenote>USE="bindist" must be set while installing GRP packages that use XFree86.</codenote>
2330</pre>
2331
2332 <p>CD 1 contains enough applications to install a working system with XFree86.
2333 Additionally, CD2 of the 2-CD GRP set contains other applications including KDE, GNOME, Mozilla, and others.
2334 To install these packages, you will need to reboot into your new Gentoo
2335system first (covered in the "Installation complete!" section near the end of this document.) After you are running your basic Gentoo system from the hard
2336drive, you can mount the second CD and copy files:</p>
2337
2338 <pre caption="Loading binary packages from CD2">
2339# <c>mount /dev/cdrom /mnt/cdrom</c>
2340# <c>cp -a /mnt/cdrom/packages/* /usr/portage/packages/</c>
2341</pre>
2342
2343 <p>Now various other applications can be installed the same way. For example:</p>
2344
2345 <pre caption="Installing KDE from GRP">
2346# <c>USE="bindist" emerge -k kde</c>
2347</pre>
2348
2349 </body>
2350 </section>
2351 </chapter>
1963 <chapter> 2352 <chapter>
1964 <title>Installation Complete!</title> 2353 <title>Installation Complete!</title>
1965 <section> 2354 <section>
1966 <body> 2355 <body>
1967 <p>Now, Gentoo Linux is installed. The only remaining step is to update necessary configuration files, exit the chrooted shell, 2356 <p>Now, Gentoo Linux is installed. The only remaining step is to update necessary configuration files, exit the chrooted shell,
1968 2357
1969 safely unmount your partitions 2358 safely unmount your partitions
1970 and reboot the system: 2359 and reboot the system:
1971 </p> 2360 </p>
2361<warn>
2362<c>etc-update</c> can provide you with a list of configuration files
2363that have newer versions at your disposal. Verify that none of the
2364configuration files have a big impact (such as <path>/etc/fstab</path>,
2365<path>/etc/make.conf</path>, <path>/etc/rc.conf</path>, ...). Merge the
2366files that don't have such a big impact, remove the updates of the
2367others or view the diff and manually update the configuration file.
2368</warn>
1972<pre caption="Rebooting the System"> 2369<pre caption="Rebooting the System">
1973# <c>etc-update</c> 2370# <c>etc-update</c>
1974# <c>exit</c> 2371# <c>exit</c>
1975<comment>(This exits the chrooted shell; you can also type <c>^D</c>)</comment> 2372<comment>(This exits the chrooted shell; you can also type <c>^D</c>)</comment>
1976# <c>cd / </c> 2373# <c>cd / </c>
1977# <c>umount /mnt/gentoo/boot</c> 2374# <c>umount /mnt/gentoo/boot</c>
1978# <c>umount /mnt/gentoo/proc</c> 2375# <c>umount /mnt/gentoo/proc</c>
1979# <c>umount /mnt/gentoo</c> 2376# <c>umount /mnt/gentoo</c>
1980# <c>reboot</c> 2377# <c>reboot</c>
2378<comment>(Don't forget to remove the bootable CD)</comment>
1981</pre> 2379</pre>
1982 <note> 2380 <note>
1983 After rebooting, it is a good idea to run the <c>update-modules</c> command to create 2381 After rebooting, it is a good idea to run the <c>update-modules</c> command to create
1984 the <path>/etc/modules.conf</path> file. Instead of modifying this file directly, you should 2382 the <path>/etc/modules.conf</path> file. Instead of modifying this file directly, you should
1985 generally make changes to the files in <path>/etc/modules.d</path>. 2383 generally make changes to the files in <path>/etc/modules.d</path>.

Legend:
Removed from v.1.141  
changed lines
  Added in v.1.142

  ViewVC Help
Powered by ViewVC 1.1.20