/[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.80 Revision 1.81
161 will have to load the appropriate kernel modules manually. 161 will have to load the appropriate kernel modules manually.
162 To view a list of all available network card modules, type <c>ls 162 To view a list of all available network card modules, type <c>ls
163 /lib/modules/*/kernel/drivers/net/*</c>. To load a particular module, 163 /lib/modules/*/kernel/drivers/net/*</c>. To load a particular module,
164 type: 164 type:
165 </p> 165 </p>
166 <pre caption="PCI Modules Configuration"> 166<pre caption="PCI Modules Configuration">
167# <c>modprobe pcnet32</c> 167# <c>modprobe pcnet32</c>
168<comment>(replace pcnet32 with your NIC module)</comment> 168<comment>(replace pcnet32 with your NIC module)</comment>
169 </pre> 169</pre>
170 <p>Likewise, if you want to be able to access any SCSI hardware that wasn't detected 170 <p>Likewise, if you want to be able to access any SCSI hardware that wasn't detected
171 during the initial boot autodetection process, you will need to load the appropriate 171 during the initial boot autodetection process, you will need to load the appropriate
172 modules from /lib/modules, again using <c>modprobe</c>: 172 modules from /lib/modules, again using <c>modprobe</c>:
173 </p> 173 </p>
174 <pre caption="Loading SCSI Modules"> 174<pre caption="Loading SCSI Modules">
175# <c>modprobe aic7xxx</c> 175# <c>modprobe aic7xxx</c>
176<comment>(replace aic7xxx with your SCSI adapter module)</comment> 176<comment>(replace aic7xxx with your SCSI adapter module)</comment>
177# <c>modprobe sd_mod</c> 177# <c>modprobe sd_mod</c>
178<comment>(sd_mod is the module for SCSI disk support)</comment> 178<comment>(sd_mod is the module for SCSI disk support)</comment>
179 </pre> 179</pre>
180 <note> 180 <note>
181 Support for a SCSI CD-ROMs and disks are built-in in the kernel. 181 Support for a SCSI CD-ROMs and disks are built-in in the kernel.
182 </note> 182 </note>
183 <p>If you are using hardware RAID, you will need to load the 183 <p>If you are using hardware RAID, you will need to load the
184 ATA-RAID modules for your RAID controller. 184 ATA-RAID modules for your RAID controller.
185 </p> 185 </p>
186 <pre caption="Loading RAID Modules"> 186<pre caption="Loading RAID Modules">
187# <c>modprobe ataraid</c> 187# <c>modprobe ataraid</c>
188# <c>modprobe pdcraid</c> 188# <c>modprobe pdcraid</c>
189 <comment>(Promise Raid Controller)</comment> 189<comment>(Promise Raid Controller)</comment>
190# <c>modprobe hptraid</c> 190# <c>modprobe hptraid</c>
191 <comment>(Highpoint Raid Controller)</comment> 191<comment>(Highpoint Raid Controller)</comment>
192 </pre> 192</pre>
193 <p>The Gentoo LiveCD should have enabled DMA on your disks, but if it did not, 193 <p>The Gentoo LiveCD should have enabled DMA on your disks, but if it did not,
194 <c>hdparm</c> can be used to set DMA on your drives. </p> 194 <c>hdparm</c> can be used to set DMA on your drives. </p>
195<pre caption="Setting DMA">
195 <pre caption="Setting DMA"><comment>Replace hdX with your disk device.</comment> 196<comment>Replace hdX with your disk device.</comment>
196# hdparm -d 1 /dev/hdX <comment>Enables DMA </comment> 197# hdparm -d 1 /dev/hdX <comment>Enables DMA </comment>
197# hdparm -d1 -A1 -m16 -u1 -a64 /dev/hdX 198# hdparm -d1 -A1 -m16 -u1 -a64 /dev/hdX
198<comment>(Enables DMA and other safe performance-enhancing options)</comment> 199<comment>(Enables DMA and other safe performance-enhancing options)</comment>
199# hdparm -X66 /dev/hdX 200# hdparm -X66 /dev/hdX
200<comment>(Force-enables Ultra-DMA -- dangerous -- may cause some drives to mess up)</comment> 201<comment>(Force-enables Ultra-DMA -- dangerous -- may cause some drives to mess up)</comment>
209 <body> 210 <body>
210 <p>If you have a PCMCIA network card, you will need to perform a few extra steps. 211 <p>If you have a PCMCIA network card, you will need to perform a few extra steps.
211 </p> 212 </p>
212 <warn>To avoid problems with <c>cardmgr</c>, you <e>must</e> run it <e>before</e> you enter the chroot 213 <warn>To avoid problems with <c>cardmgr</c>, you <e>must</e> run it <e>before</e> you enter the chroot
213 portion of the install. </warn> 214 portion of the install. </warn>
214 <pre caption="Loading PCMCIA Modules"> 215<pre caption="Loading PCMCIA Modules">
215# <i>modprobe pcmcia_core</i> 216# <i>modprobe pcmcia_core</i>
216# <i>modprobe i82365</i> 217# <i>modprobe i82365</i>
217# <i>modprobe ds</i> 218# <i>modprobe ds</i>
218# <i>cardmgr -f</i> 219# <i>cardmgr -f</i>
219 </pre> 220</pre>
220 <p>As <c>cardmgr</c> detects which hardware is present, your speaker should emit a 221 <p>As <c>cardmgr</c> detects which hardware is present, your speaker should emit a
221 few reassuring beeps, and your PCMCIA network card should be active. You can 222 few reassuring beeps, and your PCMCIA network card should be active. You can
222 of course insert the PCMCIA card after loading <c>cardmgr</c> too, if that is 223 of course insert the PCMCIA card after loading <c>cardmgr</c> too, if that is
223 preferable. (Technically, you need not run 224 preferable. (Technically, you need not run
224 <c>cardmgr</c> if you know exactly which module your PCMCIA card requires. 225 <c>cardmgr</c> if you know exactly which module your PCMCIA card requires.
241 among others.</p> 242 among others.</p>
242 243
243 <p>If networking has been configured for you, the <c>/sbin/ifconfig</c> command should 244 <p>If networking has been configured for you, the <c>/sbin/ifconfig</c> command should
244 list some internet interfaces besides <c>lo</c>, such as <c>eth0</c>: 245 list some internet interfaces besides <c>lo</c>, such as <c>eth0</c>:
245 </p> 246 </p>
246 <pre caption="/sbin/ifconfig for a working network card"> 247<pre caption="/sbin/ifconfig for a working network card">
247eth0 Link encap:Ethernet HWaddr 00:50:BA:8F:61:7A 248eth0 Link encap:Ethernet HWaddr 00:50:BA:8F:61:7A
248 inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 249 inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
249 inet6 addr: fe80::50:ba8f:617a/10 Scope:Link 250 inet6 addr: fe80::50:ba8f:617a/10 Scope:Link
250 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 251 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
251 RX packets:1498792 errors:0 dropped:0 overruns:0 frame:0 252 RX packets:1498792 errors:0 dropped:0 overruns:0 frame:0
252 TX packets:1284980 errors:0 dropped:0 overruns:0 carrier:0 253 TX packets:1284980 errors:0 dropped:0 overruns:0 carrier:0
253 collisions:1984 txqueuelen:100 254 collisions:1984 txqueuelen:100
254 RX bytes:485691215 (463.1 Mb) TX bytes:123951388 (118.2 Mb) 255 RX bytes:485691215 (463.1 Mb) TX bytes:123951388 (118.2 Mb)
255 Interrupt:11 256 Interrupt:11
256 </pre> 257</pre>
257 <p>You may want to also try pinging your ISP's DNS server (found in <path>/etc/resolv.conf</path>), 258 <p>You may want to also try pinging your ISP's DNS server (found in <path>/etc/resolv.conf</path>),
258 and a Web site of choice, just to make sure that your packets are reaching the net, DNS name 259 and a Web site of choice, just to make sure that your packets are reaching the net, DNS name
259 resolution is working correctly, etc. 260 resolution is working correctly, etc.
260 </p> 261 </p>
261 <pre caption="Further Network Testing"> 262<pre caption="Further Network Testing">
262# <c>ping www.some_website.com </c> 263# <c>ping www.gentoo.com </c>
263 </pre> 264</pre>
264 <p>Are you able to use your network? If so, you can skip the rest of this section.</p> 265 <p>Are you able to use your network? If so, you can skip the rest of this section.</p>
265 </body> 266 </body>
266 </section> 267 </section>
267 <section> 268 <section>
268 <title> PPPoE configuration</title> 269 <title> PPPoE configuration</title>
270 <p>Assuming you need PPPoE to connect to the internet, the LiveCD (any version) has 271 <p>Assuming you need PPPoE to connect to the internet, the LiveCD (any version) has
271 made things easy for you by including <c>rp-pppoe</c>. Use the provided <c>adsl-setup</c> 272 made things easy for you by including <c>rp-pppoe</c>. Use the provided <c>adsl-setup</c>
272 script to configure your connection. You will be prompted for the ethernet 273 script to configure your connection. You will be prompted for the ethernet
273 device that is connected to your adsl modem, your username and password, 274 device that is connected to your adsl modem, your username and password,
274 the IPs of your DNS servers, and if you need a basic firewall or not. </p> 275 the IPs of your DNS servers, and if you need a basic firewall or not. </p>
275 <pre caption="Configuring PPPoE"> 276<pre caption="Configuring PPPoE">
276# <c> adsl-setup </c> 277# <c> adsl-setup </c>
277# <c> adsl-start </c> 278# <c> adsl-start </c>
278 </pre> 279</pre>
279 <p>If something goes wrong, double-check that you correctly typed 280 <p>If something goes wrong, double-check that you correctly typed
280 your username and password by looking at <path>/etc/ppp/pap-secrets</path> or 281 your username and password by looking at <path>/etc/ppp/pap-secrets</path> or
281 <path>/etc/ppp/chap-secrets</path>, and make sure you are using the right ethernet device. </p> 282 <path>/etc/ppp/chap-secrets</path>, and make sure you are using the right ethernet device. </p>
282 </body> 283 </body>
283 </section> 284 </section>
284 <section> 285 <section>
285 <title> Automatic Network Configuration </title> 286 <title> Automatic Network Configuration </title>
286 <body> 287 <body>
287 <p>The simplest way to set up networking if it didn't get configured automatically is to run the <c>net-setup</c> script.</p> 288 <p>The simplest way to set up networking if it didn't get configured automatically is to run the <c>net-setup</c> script.</p>
288 <pre caption="Net-Setup Script"> 289<pre caption="Net-Setup Script">
289# <c>net-setup eth0</c> 290# <c>net-setup eth0</c>
290 </pre> 291</pre>
291 <p>Of course, if you prefer, you may still set up networking manually. This is covered next.</p> 292 <p>Of course, if you prefer, you may still set up networking manually. This is covered next.</p>
292 </body> 293 </body>
293 </section> 294 </section>
294 <section> 295 <section>
295 <title>Manual DHCP Configuration</title> 296 <title>Manual DHCP Configuration</title>
296 <body> 297 <body>
297 <p>Network configuration is simple with DHCP; If your ISP is not using 298 <p>Network configuration is simple with DHCP; If your ISP is not using
298 DHCP, skip down to the static configuration section below. </p> 299 DHCP, skip down to the static configuration section below. </p>
299 <pre caption="Network configuration with DHCP"> 300<pre caption="Network configuration with DHCP">
300# <c>dhcpcd eth0</c> 301# <c>dhcpcd eth0</c>
301 </pre> 302</pre>
302 <note>Some ISPs require you to provide a hostname. To do that, 303 <note>Some ISPs require you to provide a hostname. To do that,
303 add a <c>-h myhostname</c> flag to the dhcpcd command line above. 304 add a <c>-h myhostname</c> flag to the dhcpcd command line above.
304 </note> 305 </note>
305 <p>If you receive <i>dhcpConfig</i> warnings, don't panic; the errors 306 <p>If you receive <i>dhcpConfig</i> warnings, don't panic; the errors
306 are most likely cosmetic. Skip down to Network testing below.</p> 307 are most likely cosmetic. Skip down to Network testing below.</p>
315 $IFACE with your network interface (typically <c>eth0</c>), $IPNUM 316 $IFACE with your network interface (typically <c>eth0</c>), $IPNUM
316 with your IP address, $BCAST with your broadcast address, and $NMASK 317 with your IP address, $BCAST with your broadcast address, and $NMASK
317 with your network mask. For the <c>route</c> command, replace 318 with your network mask. For the <c>route</c> command, replace
318 $GTWAY with your default gateway. 319 $GTWAY with your default gateway.
319 </p> 320 </p>
320 <pre caption="Static IP Network Configuration"> 321<pre caption="Static IP Network Configuration">
321# <c>ifconfig $IFACE $IPNUM broadcast $BCAST netmask $NMASK</c> 322# <c>ifconfig $IFACE $IPNUM broadcast $BCAST netmask $NMASK</c>
322# <c>/sbin/route add -net default gw $GTWAY netmask 0.0.0.0 metric 1</c> 323# <c>/sbin/route add -net default gw $GTWAY netmask 0.0.0.0 metric 1</c>
323 </pre> 324</pre>
324 <p>Now it is time to create the <path>/etc/resolv.conf</path> 325 <p>Now it is time to create the <path>/etc/resolv.conf</path>
325 file so that name resolution (finding Web/FTP sites by name, rather than just by IP address) will work.</p> 326 file so that name resolution (finding Web/FTP sites by name, rather than just by IP address) will work.</p>
326 <p>Here is a template to follow for creating your /etc/resolv.conf file: </p> 327 <p>Here is a template to follow for creating your /etc/resolv.conf file: </p>
327 <pre caption="/etc/resolv.conf template"> 328<pre caption="/etc/resolv.conf template">
328domain mydomain.com 329domain mydomain.com
329nameserver 10.0.0.1 330nameserver 10.0.0.1
330nameserver 10.0.0.2 331nameserver 10.0.0.2
331 </pre> 332</pre>
332 <p>Replace <c>10.0.0.1</c> and <c>10.0.0.2</c> with the IP addresses of your 333 <p>Replace <c>10.0.0.1</c> and <c>10.0.0.2</c> with the IP addresses of your
333 primary and secondary DNS servers respectively.</p> 334 primary and secondary DNS servers respectively.</p>
334 </body> 335 </body>
335 </section> 336 </section>
336 <section> 337 <section>
337 <title>Proxy Configuration</title> 338 <title>Proxy Configuration</title>
338 <body> 339 <body>
339 <p>If you are behind a proxy, it is necessary to configure your proxy before 340 <p>If you are behind a proxy, it is necessary to configure your proxy before
340 you continue. We will export some variables to set up the proxy accordingly. 341 you continue. We will export some variables to set up the proxy accordingly.
341 </p> 342 </p>
342 <pre caption="Setting a Proxy"> 343<pre caption="Setting a Proxy">
343# <c>export http_proxy=&quot;machine.company.com:1234&quot; </c> 344# <c>export http_proxy=&quot;machine.company.com:1234&quot; </c>
344# <c>export ftp_proxy=&quot;$http_proxy&quot; </c> 345# <c>export ftp_proxy=&quot;$http_proxy&quot; </c>
345# <c>export RSYNC_PROXY=&quot;$http_proxy&quot; </c> 346# <c>export RSYNC_PROXY=&quot;$http_proxy&quot; </c>
346 </pre> 347</pre>
347 </body> 348 </body>
348 </section> 349 </section>
349 <section> 350 <section>
350 <title>Networking is go!</title> 351 <title>Networking is go!</title>
351 <body> 352 <body>
352 <p>Networking should now be configured and usable. You should be able to use the included 353 <p>Networking should now be configured and usable. You should be able to use the included
353 <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> 354 <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>
355 </body>
356 </section>
357 </chapter>
358 <chapter>
359 <title>Setting your system's date and time</title>
360 <section>
361 <body>
362 <p>Now you need to set your system's date and time.
363 You can do this using the <c>date</c> command.</p>
364<pre caption="Setting your system's date">
365# <c>date</c>
366Thu Feb 27 09:04:42 CST 2003
367<comment>(If your date is wrong, set your date with this next command)</comment>
368# <c>date 022709042003</c>
369<comment>(date MMDDhhmmCCYY)</comment>
370</pre>
354 </body> 371 </body>
355 </section> 372 </section>
356 </chapter> 373 </chapter>
357 <chapter> 374 <chapter>
358 <title>Partition Configuration</title> 375 <title>Partition Configuration</title>
366 We're going to create at least three partitions: a swap partition, a root 383 We're going to create at least three partitions: a swap partition, a root
367 partition (to hold the bulk of Gentoo Linux), and a special boot partition. 384 partition (to hold the bulk of Gentoo Linux), and a special boot partition.
368 The boot partition is designed to hold the boot loader information as well as 385 The boot partition is designed to hold the boot loader information as well as
369 your Linux kernel(s). The boot partition gives us a safe place to store 386 your Linux kernel(s). The boot partition gives us a safe place to store
370 everything related to booting Linux. During normal day-to-day Gentoo Linux use, 387 everything related to booting Linux. During normal day-to-day Gentoo Linux use,
371 your boot partition should remain <e>unmounted</e>. A working kernel will enable you recover from most forms of 388 your boot partition should remain <e>unmounted</e>. A working kernel will enable you to recover from most forms of
372filesystem corruption, having your kernel in a non-mounted partition 389filesystem corruption. Having your kernel in a non-mounted partition
373will prevent filesystem corruption from affecting it. 390will prevent filesystem corruption from affecting it.
374 </p> 391 </p>
375 <p>Now, on to filesystem types. Right now, you have five filesystem options: 392 <p>Now, on to filesystem types. Right now, you have five filesystem options:
376 XFS, ext2, ext3 (journaling), jfs, and ReiserFS. ext2 is the tried and true Linux 393 XFS, ext2, ext3 (ext2 with journaling), jfs, and ReiserFS. ext2 is the tried and true Linux
377 filesystem but doesn't have metadata journaling. ext3 is the new version of 394 filesystem but doesn't have metadata journaling. ext3 is the new version of
378 ext2 with both metadata journaling and ordered data writes, effectively 395 ext2 with both metadata journaling and ordered data writes, effectively
379 providing data journaling as well. ReiserFS is a B*-tree based filesystem 396 providing data journaling as well. ReiserFS is a B*-tree based filesystem
380 that has very good small file performance, and greatly outperforms both ext2 and 397 that has very good small file performance, and greatly outperforms both ext2 and
381 ext3 when dealing with small files (files less than 4k), often by a factor of 398 ext3 when dealing with small files (files less than 4k), often by a factor of
434disc0.Y is the partition number as in <path>/dev/hdaY</path> </note> 451disc0.Y is the partition number as in <path>/dev/hdaY</path> </note>
435 <p>Once you've created your partitions, it is time to initialize 452 <p>Once you've created your partitions, it is time to initialize
436 the filesystems that will be used to house your data.</p> 453 the filesystems that will be used to house your data.</p>
437 454
438 <p>But before creating filesystems, you may want to initialize the 455 <p>But before creating filesystems, you may want to initialize the
439 beginning of your hard disk using <c>dd</c> if you are using a pre-existing partition that has been used before. 456 beginning of your partition using <c>dd</c> if you are using a pre-existing partition that has been used before.
440 This is particularly helpful when you're going to create a new XFS filesystem on a partition that previously contained 457 This is particularly helpful when you're going to create a new XFS filesystem on a partition that previously contained
441 a ReiserFS filesystem. Doing this will ensure that your new filesystem 458 a ReiserFS filesystem. Doing this will ensure that your new filesystem
442 will not be mis-identified by Linux's filesystem auto-detection code. 459 will not be mis-identified by Linux's filesystem auto-detection code.
443 This can be done as follows: 460 This can be done as follows:
444 </p> 461 </p>
445 <pre caption="Initializing first 1024 Sectors of HD"> 462<pre caption="Initializing first 1024 bytes of your partition">
446# <c>dd if=/dev/zero of=/dev/hdxy bs=1K count=1</c> 463# <c>dd if=/dev/zero of=/dev/hda3 bs=1k count=1</c>
447<comment>Replace /dev/hdxy with the device you wish to &quot;clean.&quot;</comment> 464<comment>(Replace /dev/hda3 with the partition you wish to &quot;clean.&quot;)</comment>
448 </pre> 465</pre>
449 <warn>The command above will destroy all data from <path>/dev/hdxy</path>. 466 <warn>The command above will destroy all data from <path>/dev/hda3</path>.
450 Be careful and check twice which partition you specify for zeroing. 467 Be careful and check twice which partition you specify for zeroing.
451 If you make a mistake it might result in a loss of data. 468 If you make a mistake it might result in a loss of data.
452 </warn> 469 </warn>
453 <p>Now, initialize your swap partition as follows:</p> 470 <p>Now, initialize your swap partition as follows:</p>
454 <pre caption="Initializing Swap"> 471<pre caption="Initializing Swap">
455# <c>mkswap /dev/hda2</c> 472# <c>mkswap /dev/hda2</c>
456 </pre> 473</pre>
457 <p>You can use the <c>mke2fs</c> command to create ext2 filesystems.</p> 474 <p>You can use the <c>mke2fs</c> command to create ext2 filesystems.</p>
458 <pre caption="Creating an ext2 Filesystem"> 475<pre caption="Creating an ext2 Filesystem">
459# <i>mke2fs /dev/hda1</i> 476# <i>mke2fs /dev/hda1</i>
460 </pre> 477</pre>
461 <p>To create an XFS filesystem, use the <c>mkfs.xfs</c> command.</p> 478 <p>To create an XFS filesystem, use the <c>mkfs.xfs</c> command.</p>
462 <pre caption="Creating a XFS Filesystem"> 479<pre caption="Creating a XFS Filesystem">
463# <c>mkfs.xfs /dev/hda3</c> 480# <c>mkfs.xfs /dev/hda3</c>
464 </pre> 481</pre>
465 <note> 482 <note>You may want to add a couple of additional flags to the
466 You may want to add a couple of additional flags to the <c>mkfs.xfs</c> command: <c>-d agcount=3 -l size=32m</c>. 483 <c>mkfs.xfs</c> command: <c>-d agcount=3 -l size=32m</c>.
467 The <c>-d agcount=3</c> command will lower 484 The <c>-d agcount=3</c> command will lower the number of allocation groups.
468 the number of allocation groups. XFS will insist on using at least 1 allocation group per 4 GB of your partition, 485 XFS will insist on using at least 1 allocation group per 4 GB of your
469 so, for example, if you have a 20 GB partition you will need a minimum agcount of 5. 486 partition, so, for example, if you have a 20 GB partition you will need
470 The <c>-l size=32m</c> command increases the journal size to 32 Mb, increasing performance. 487 a minimum agcount of 5. The <c>-l size=32m</c> command increases the
471 </note> 488 journal size to 32 Mb, increasing performance.</note>
472 <p>If you would like to use ext3, you can create ext3 filesystems using <c>mke2fs -j</c>.</p> 489 <p>If you would like to use ext3, you can create ext3 filesystems using
490 <c>mke2fs -j</c>.</p>
473 <pre caption="Creating an ext3 Filesystem"> 491<pre caption="Creating an ext3 Filesystem">
474# <c>mke2fs -j /dev/hda3</c> 492# <c>mke2fs -j /dev/hda3</c>
475 </pre> 493</pre>
476 <note>You can find out more about using ext3 under Linux 2.4 at 494 <note>You can find out more about using ext3 under Linux 2.4 at
477 <uri>http://www.zip.com.au/~akpm/linux/ext3/ext3-usage.html</uri>. 495 <uri>http://www.zip.com.au/~akpm/linux/ext3/ext3-usage.html</uri>.</note>
478 </note>
479 <p>To create ReiserFS filesystems, use the <c>mkreiserfs</c> command.</p> 496 <p>To create ReiserFS filesystems, use the <c>mkreiserfs</c> command.</p>
480 <pre caption="Creating a ReiserFS Filesystem"> 497<pre caption="Creating a ReiserFS Filesystem">
481# <c>mkreiserfs /dev/hda3</c> 498# <c>mkreiserfs /dev/hda3</c>
482 </pre> 499</pre>
483
484 <p>To create JFS filesystems, use the <c>mkfs.jfs</c> command.</p> 500 <p>To create JFS filesystems, use the <c>mkfs.jfs</c> command.</p>
485 <pre caption="Creating a JFS Filesystem"> 501<pre caption="Creating a JFS Filesystem">
486# <c>mkfs.jfs /dev/hda3</c> 502# <c>mkfs.jfs /dev/hda3</c>
487 </pre> 503</pre>
488
489 </body> 504 </body>
490 </section> 505 </section>
491 </chapter> 506 </chapter>
492 <chapter> 507 <chapter>
493 <title>Mount Partitions</title> 508 <title>Mount Partitions</title>
494 <section> 509 <section>
495 <body> 510 <body>
496 <p>Now, we will activate our new swap, since we may need the additional virtual memory that it 511 <p>Now, we will activate our new swap, since we may need the additional virtual memory that it
497 provides later: 512 provides later:
498 </p> 513 </p>
499 <pre caption="Activating Swap"> 514<pre caption="Activating Swap">
500# <c>swapon /dev/hda2</c> 515# <c>swapon /dev/hda2</c>
501 </pre> 516</pre>
502 <p>Next, we will create the <path>/mnt/gentoo</path> and <path>/mnt/gentoo/boot</path> mount points, 517 <p>Next, we will create the <path>/mnt/gentoo</path> and <path>/mnt/gentoo/boot</path> mount points,
503 and we will mount our filesystems to these mount points. </p> 518 and we will mount our filesystems to these mount points. </p>
504 <pre caption="Creating Mount Points"> 519<pre caption="Creating Mount Points">
505# <c>mkdir /mnt/gentoo</c> 520# <c>mkdir /mnt/gentoo</c>
506# <c>mount /dev/hda3 /mnt/gentoo</c> 521# <c>mount /dev/hda3 /mnt/gentoo</c>
507# <c>mkdir /mnt/gentoo/boot</c> 522# <c>mkdir /mnt/gentoo/boot</c>
508# <c>mount /dev/hda1 /mnt/gentoo/boot</c> 523# <c>mount /dev/hda1 /mnt/gentoo/boot</c>
509 </pre> 524</pre>
510 <p> 525 <p>
511 If you are setting up Gentoo 526 If you are setting up Gentoo
512 Linux with a separate <path>/usr</path> or <path>/var</path>, these would get mounted to 527 Linux with a separate <path>/usr</path> or <path>/var</path>, these would get mounted to
513 <path>/mnt/gentoo/usr</path> and <path>/mnt/gentoo/var</path>, respectively. 528 <path>/mnt/gentoo/usr</path> and <path>/mnt/gentoo/var</path>, respectively.
514 </p> 529 </p>
534 <p>Alternatively, if you have the basic LiveCD, the stage1 tarball is still available on 549 <p>Alternatively, if you have the basic LiveCD, the stage1 tarball is still available on
535 the CD in <path>/mnt/cdrom/gentoo</path>. You will have to download the other stages though, 550 the CD in <path>/mnt/cdrom/gentoo</path>. You will have to download the other stages though,
536 and the best place to which to download them is <path>/mnt/gentoo</path>. 551 and the best place to which to download them is <path>/mnt/gentoo</path>.
537 </p> 552 </p>
538 553
539 <pre caption="Downloading Required Stages"> 554<pre caption="Downloading Required Stages">
540# <c>cd /mnt/gentoo</c> 555# <c>cd /mnt/gentoo</c>
541<comment>Use lynx to get the URL for your tarball:</comment> 556<comment>Use lynx to get the URL for your tarball:</comment>
542# <c>lynx http://www.ibiblio.org/pub/Linux/distributions/gentoo/releases/1.4_rc3/x86/</c> 557# <c>lynx http://www.ibiblio.org/pub/Linux/distributions/gentoo/releases/1.4_rc3/x86/</c>
543<comment>Use <c>Up</c> and <c>Down</c> arrows keys (or the <c>TAB</c> key) to go to the right directory 558<comment>Use <c>Up</c> and <c>Down</c> arrows keys (or the <c>TAB</c> key) to go to the right directory
544Highlight the appropriate stage you want to download 559Highlight the appropriate stage you want to download
545Press <c>d</c> which will initiate the download 560Press <c>d</c> which will initiate the download
546Save the file and quit the browser 561Save the file and quit the browser
547 562
548<b>OR</b> use wget from the command line:</comment> 563<b>OR</b> use wget from the command line:</comment>
549# <c>wget <comment>insert URL to the required stage tarball here.</comment></c> 564# <c>wget <comment>insert URL to the required stage tarball here.</comment></c>
550 </pre> 565</pre>
551 </body> 566 </body>
552 </section> 567 </section>
553 </chapter>
554 <chapter> 568 </chapter>
569 <chapter>
555 <title>Unpacking the Stage Tarballs</title> 570 <title>Unpacking the Stage Tarball</title>
556 <section> 571 <section>
557 <body> 572 <body>
558 <p>Now it is time to extract the compressed stage tarball of your choice to <path>/mnt/gentoo</path>. 573 <p>Now it is time to extract the compressed stage tarball of your choice
574 to <path>/mnt/gentoo</path>. You only need to unpack the stage tarball
575 for the stage you want to start at. So, if you wanted to perform a
576 stage3 install of Gentoo, then you would unpack the stage3 tarball.
559 Then, we will <c>chroot</c> over to the new Gentoo Linux build installation to &quot;enter&quot; the new 577 Next, we will <c>chroot</c> over to the new Gentoo Linux build installation to &quot;enter&quot; the new
560 Gentoo Linux system. 578 Gentoo Linux system.
561 </p> 579 </p>
562 <impo>Be sure to use the <c>p</c> option with <c>tar</c>. Forgetting to do this will 580 <impo>Be sure to use the <c>p</c> option with <c>tar</c>. Forgetting to do this will
563 cause certain files to have incorrect permissions.</impo> 581 cause certain files to have incorrect permissions.</impo>
564 <p>If you are using the &quot;from scratch, build everything&quot; install method, 582 <p>If you are using the &quot;from scratch, build everything&quot; install method,
565 you will want to use the <path>stage1-ix86-1.4_beta.tbz2</path> image. 583 you will want to use the <path>stage1-x86-1.4_rc3.tar.bz2</path> image.
566 If you're using one of our bigger CDs, you will also have a choice of a stage2 and stage3 image. 584 If you're using one of our bigger CDs, you will also have a choice of a stage2 and stage3 image.
567 These images allow you to save time at the expense of configurability (we've already chosen 585 These images allow you to save time at the expense of configurability (we've already chosen
568 compiler optimizations and default USE variables for you.) 586 compiler optimizations and default USE variables for you.)
569 </p> 587 </p>
570 <pre caption="Unpacking the Stages"> 588<pre caption="Unpacking the Stages">
571# <c>cd /mnt/gentoo</c> 589# <c>cd /mnt/gentoo</c>
572# <c>tar -xvjpf /mnt/cdrom/gentoo/stage?-*.tbz2</c> 590# <c>tar -xvjpf /mnt/cdrom/gentoo/stage?-*.tbz2</c>
573# <c>mount -o bind /proc /mnt/gentoo/proc</c> 591# <c>mount -o bind /proc /mnt/gentoo/proc</c>
574# <c>cp /etc/resolv.conf /mnt/gentoo/etc/resolv.conf</c> 592# <c>cp /etc/resolv.conf /mnt/gentoo/etc/resolv.conf</c>
575 </pre> 593</pre>
576 <pre caption="Entering the chroot Environment"> 594<pre caption="Entering the chroot Environment">
577# <c>chroot /mnt/gentoo /bin/bash</c> 595# <c>chroot /mnt/gentoo /bin/bash</c>
578# <c>env-update</c> 596# <c>env-update</c>
579Regenerating /etc/ld.so.cache... 597Regenerating /etc/ld.so.cache...
580# <c>source /etc/profile</c> 598# <c>source /etc/profile</c>
581<comment>The above points your shell to the new paths and updated binaries. </comment> 599<comment>(The above points your shell to the new paths and updated binaries.)</comment>
582 </pre> 600</pre>
583 <p>After you execute these commands, you will be &quot;inside&quot; your new Gentoo Linux environment. 601 <p>After you execute these commands, you will be &quot;inside&quot; your new Gentoo Linux environment.</p>
584 </p>
585 </body> 602 </body>
586 </section> 603 </section>
587 </chapter> 604 </chapter>
588 <chapter> 605 <chapter>
589 <title>Getting the Current Portage Tree using sync</title> 606 <title>Getting the Current Portage Tree using sync</title>
590 <section> 607 <section>
591 <body> 608 <body>
592 <p>Now, you will need to run <c>emerge sync</c>. This will make sure that 609 <p>Now, you will need to run <c>emerge sync</c>. This will make sure that
593 you have the most current copy of the Portage tree. </p> 610 you have the most current copy of the Portage tree. </p>
594 <pre caption="Updating Using sync"> 611<pre caption="Updating Using sync">
595
596# <c>emerge sync</c> 612# <c>emerge sync</c>
597# <c>export CONFIG_PROTECT="-*"</c> 613# <c>export CONFIG_PROTECT="-*"</c>
598# <c>export USE="-* bootstrap build"</c> 614# <c>export USE="-* bootstrap build"</c>
599# <c>emerge portage</c> 615# <c>emerge portage</c>
600# <c>unset USE</c> 616# <c>unset USE</c>
601 </pre> 617</pre>
602 <p>The Portage tree will be downloaded and stored in <path>/usr/portage</path>; 618 <p>The Portage tree will be downloaded and stored in <path>/usr/portage</path>;
603 it is about 90Mb in size without tarballs. 619 it is about 90Mb in size without tarballs.
604 </p> 620 </p>
605 <note>The <c>export CONFIG_PROTECT=&quot;-*&quot;</c> line ensures that any new scripts 621 <note>The <c>export CONFIG_PROTECT=&quot;-*&quot;</c> line ensures that any new scripts
606 installed to <path>/etc</path> will overwrite the old scripts (stored in 622 installed to <path>/etc</path> will overwrite the old scripts (stored in
637 file contains a general guide for the proper settings of CFLAGS and CXXFLAGS.</p> 653 file contains a general guide for the proper settings of CFLAGS and CXXFLAGS.</p>
638 654
639 <p>If necessary, you can also set proxy information here if you are behind a 655 <p>If necessary, you can also set proxy information here if you are behind a
640 firewall. 656 firewall.
641 </p> 657 </p>
642 <pre caption="Setting make.conf Options"> 658<pre caption="Setting make.conf Options">
643# <c>nano -w /etc/make.conf</c> <comment>(Adjust these settings)</comment> 659# <c>nano -w /etc/make.conf</c>
660<comment>(Adjust these settings)</comment>
644 </pre> 661</pre>
645 <note> 662 <note>
646 People who need to substantially customize the build process should take a look at 663 People who need to substantially customize the build process should take a look at
647 the <path>/etc/make.globals</path> file. This file comprises gentoo defaults and 664 the <path>/etc/make.globals</path> file. This file comprises gentoo defaults and
648 should never be touched. If the defaults do not suffice, then new values should 665 should never be touched. If the defaults do not suffice, then new values should
649 be put in <path>/etc/make.conf</path>, as entries in <path>make.conf</path> 666 be put in <path>/etc/make.conf</path>, as entries in <path>make.conf</path>
665 is a system that has been optimized from the ground up for your specific machine and needs. 682 is a system that has been optimized from the ground up for your specific machine and needs.
666 </p> 683 </p>
667 <p>Now, it is time to start the &quot;bootstrap&quot; process. This process takes about two hours on 684 <p>Now, it is time to start the &quot;bootstrap&quot; process. This process takes about two hours on
668 my 1200Mhz AMD Athlon system. 685 my 1200Mhz AMD Athlon system.
669During this time, the extracted build image will be prepared and the GNU compiler suite and Libraries will be built. </p> 686During this time, the extracted build image will be prepared and the GNU compiler suite and Libraries will be built. </p>
670 <pre caption="Bootstrapping"> 687<pre caption="Bootstrapping">
671# <c>cd /usr/portage</c> 688# <c>cd /usr/portage</c>
672# <c>scripts/bootstrap.sh</c> 689# <c>scripts/bootstrap.sh</c>
673 </pre> 690</pre>
674 <p>The &quot;bootstrap&quot; process will now begin. 691 <p>The &quot;bootstrap&quot; process will now begin.
675 </p> 692 </p>
676 <note> 693 <note>
677 Portage by default uses <c>/var/tmp</c> during package building, often 694 Portage by default uses <c>/var/tmp</c> during package building, often
678 using several hundred megabytes of temporary storage. If you would like to 695 using several hundred megabytes of temporary storage. If you would like to
679 change where Portage stores these temporary files, set a new PORTAGE_TMPDIR <e>before</e> 696 change where Portage stores these temporary files, set a new PORTAGE_TMPDIR <e>before</e>
680 starting the bootstrap process, as follows: 697 starting the bootstrap process, as follows:
681 </note> 698 </note>
682 <pre caption="Changing Portage's Storage Path"> 699<pre caption="Changing Portage's Storage Path">
683# <c>export PORTAGE_TMPDIR=&quot;/otherdir/tmp&quot;</c> 700# <c>export PORTAGE_TMPDIR=&quot;/otherdir/tmp&quot;</c>
684 </pre> 701</pre>
685 <p><c>bootstrap.sh</c> will build <c>binutils</c>, <c>gcc</c>, <c>gettext</c>, 702 <p><c>bootstrap.sh</c> will build <c>binutils</c>, <c>gcc</c>, <c>gettext</c>,
686 and <c>glibc</c>, rebuilding <c>binutils</c>, <c>gcc</c>, and <c>gettext</c> 703 and <c>glibc</c>, rebuilding <c>binutils</c>, <c>gcc</c>, and <c>gettext</c>
687 after <c>glibc</c>. Needless to say, this process takes a while. 704 after <c>glibc</c>. Needless to say, this process takes a while.
688 Once this process completes, your system will be equivalent to a &quot;stage2&quot; system, 705 Once this process completes, your system will be equivalent to a &quot;stage2&quot; system,
689 which means you can now move on to the stage2 instructions. 706 which means you can now move on to the stage2 instructions.
700 </p> 717 </p>
701 <note> 718 <note>
702 If you have not already edited /etc/make.conf to fit your specifications, 719 If you have not already edited /etc/make.conf to fit your specifications,
703now would be a good time to do so. 720now would be a good time to do so.
704 </note> 721 </note>
705 <pre caption="Installing the Rest of the System"> 722<pre caption="Installing the Rest of the System">
706# <c>emerge -p system</c> 723# <c>emerge -p system</c>
707 <comment>[lists the packages to be installed]</comment> 724<comment>(lists the packages to be installed)</comment>
708# <c>emerge system</c> 725# <c>emerge system</c>
709 </pre> 726</pre>
710 <p>It is going to take a while 727 <p>It is going to take a while
711 to finish building the entire base system. Your reward is that it will be 728 to finish building the entire base system. Your reward is that it will be
712 thoroughly optimized for your system. The drawback is that you have to find a 729 thoroughly optimized for your system. The drawback is that you have to find a
713 way to keep yourself occupied for some time to come. The author suggests &quot;Star 730 way to keep yourself occupied for some time to come. The author suggests &quot;Star
714 Wars - Super Bombad Racing&quot; for the PS2. 731 Wars - Super Bombad Racing&quot; for the PS2.
729 <p>The stage3 tarball is already configured for your system. There is not much to do for this stage, 746 <p>The stage3 tarball is already configured for your system. There is not much to do for this stage,
730 but it is a very good idea to update your system to the newest available packages. </p> 747 but it is a very good idea to update your system to the newest available packages. </p>
731 748
732 <note>If you have not already edited <path>/etc/make.conf</path> to fit your specifications, 749 <note>If you have not already edited <path>/etc/make.conf</path> to fit your specifications,
733 now would be a good time to do so. </note> 750 now would be a good time to do so. </note>
734 <pre caption="Getting up-to-date"> 751<pre caption="Getting up-to-date">
735 # <c>emerge sync</c> 752# <c>emerge sync</c>
736 # <c>emerge -up world</c> 753# <c>emerge -up world</c>
737 <comment>lists [<i>packages</i>] to be installed</comment> 754<comment>(lists the packages to be installed)</comment>
738 # <c>emerge -u world</c> 755# <c>emerge -u world</c>
739 </pre> 756</pre>
740 </body> 757 </body>
741 </section>
742 </chapter>
743 <chapter>
744 <title>Setting your time zone and date</title>
745 <section> 758 </section>
759 </chapter>
760 <chapter>
761 <title>Setting your time zone</title>
762 <section>
746 <body> 763 <body>
747 <p>You need to set your time zone and date before you start installing your system.</p> 764 <p>Now you need to set your time zone.</p>
748 <p>Look for your time zone (or GMT if you are using Greenwich Mean Time) in 765 <p>Look for your time zone (or GMT if you are using Greenwich Mean Time)
749 <path>/usr/share/zoneinfo</path>. Then, make a symbolic link by typing: 766 in <path>/usr/share/zoneinfo</path>. Then, make a symbolic link to
750 </p> 767 /etc/localtime by typing:</p>
751 <pre caption="Creating a symbolic link for time zone"> 768<pre caption="Creating a symbolic link for time zone">
752# <c>ln -sf /usr/share/zoneinfo/path/to/timezonefile /etc/localtime</c> 769# <c>ln -sf /usr/share/zoneinfo/path/to/timezonefile /etc/localtime</c>
753# <c>date</c>
754Thu Feb 27 09:04:42 CST 2003
755<comment>(If your date is wrong set your date with this next command)</comment>
756# <c>date 022709042003</c>
757<comment>(date MMDDhhmmCCYY)</comment>
758
759 </pre> 770</pre>
760
761 </body> 771 </body>
762 </section> 772 </section>
763 </chapter> 773 </chapter>
764 <chapter> 774 <chapter>
765 <title>Installing the kernel and a System Logger</title> 775 <title>Installing the kernel and a System Logger</title>
810 <warn> 820 <warn>
811 If you are configuring your own kernel, be careful with the <i>grsecurity</i> option. Being too aggressive with your 821 If you are configuring your own kernel, be careful with the <i>grsecurity</i> option. Being too aggressive with your
812 security settings can cause certain programs (such as X) to not run properly. If in doubt, leave it out. 822 security settings can cause certain programs (such as X) to not run properly. If in doubt, leave it out.
813 </warn> 823 </warn>
814 <p>Choose a kernel and then merge as follows:</p> 824 <p>Choose a kernel and then merge as follows:</p>
815 <pre caption="Emerging Kernel Sources"> 825<pre caption="Emerging Kernel Sources">
816# <c>emerge sys-kernel/gentoo-sources</c> 826# <c>emerge sys-kernel/gentoo-sources</c>
817 </pre> 827</pre>
818 <p>Once you have a Linux kernel source tree available, it is time to compile your own custom kernel. 828 <p>Once you have a Linux kernel source tree available, it is time to compile your own custom kernel.
819 </p> 829 </p>
820 <p>Please note that <path>/usr/src/linux</path> is a symlink to your current emerged kernel source package, 830 <p>Please note that <path>/usr/src/linux</path> is a symlink to your current emerged kernel source package,
821 and is set automatically by Portage at emerge time. 831 and is set automatically by Portage at emerge time.
822 If you have multiple kernel source packages, it is necessary to set the <path>/usr/src/linux</path> symlink 832 If you have multiple kernel source packages, it is necessary to set the <path>/usr/src/linux</path> symlink
823 to the correct one before proceeding. 833 to the correct one before proceeding.
824 </p> 834 </p>
825 <pre caption="Compiling the Linux Kernel"> 835<pre caption="Compiling the Linux Kernel">
826# <c>cd /usr/src/linux</c> 836# <c>cd /usr/src/linux</c>
827# <c>source /etc/profile</c> 837# <c>source /etc/profile</c>
828<comment>Again, this updates your paths. If you get an error saying gcc is not found, 838<comment>Again, this updates your paths. If you get an error saying gcc is not found,
829this is what you may have to do. </comment> 839this is what you may have to do. </comment>
830# <c>make menuconfig</c> 840# <c>make menuconfig</c>
831# <c>make dep &amp;&amp; make clean bzImage modules modules_install</c> 841# <c>make dep &amp;&amp; make clean bzImage modules modules_install</c>
832# <c>mv /boot/bzImage /boot/bzImage.orig</c>
833<comment>[if bzImage already exists]</comment>
834# <c>cp /usr/src/linux/arch/i386/boot/bzImage /boot</c> 842# <c>cp /usr/src/linux/arch/i386/boot/bzImage /boot</c>
835 </pre> 843</pre>
836 <warn>For your kernel to function properly, there are several options that you will 844 <warn>For your kernel to function properly, there are several options that you will
837 need to ensure are in the kernel proper -- that is, they should <i>be enabled and not 845 need to ensure are in the kernel proper -- that is, they should <i>be enabled and not
838 compiled as modules</i>. You will need to enable the <i>&quot;Code maturity 846 compiled as modules</i>. Be sure to enable &quot;ReiserFS&quot; if you have
839 level options --&gt; Prompt for development and/or incomplete code/drivers&quot;</i>
840 option to see several of these selections.
841 Under the &quot;File systems&quot; section, be sure to enable the <i>&quot;/dev&quot; file system support</i> (note that
842 you <e>do not</e> need to enable the &quot;/dev/pts file system support&quot; option). You will also
843 need to enable the <i>&quot;Virtual Memory Filesystem&quot;</i>. Be sure to enable &quot;ReiserFS&quot; if you have
844 any ReiserFS partitions; the same goes for &quot;Ext3&quot;. If you're using XFS, enable the 847 any ReiserFS partitions; the same goes for &quot;Ext3&quot;. If you're using XFS, enable the
845 &quot;SGI XFS filesystem support&quot; 848 &quot;SGI XFS filesystem support&quot; option. It's always a good idea to leave ext2
846 option. It is always a good idea to leave ext2 849 enabled whether you are using it or not. Below are some common options that you will need:</warn>
847 enabled whether you are using it or not. Also, most people using IDE hard drives will 850<pre caption="make menuconfig options">
848 want to enable the &quot;USE DMA by default&quot; option; otherwise, your IDE drives may perform 851Code maturity level options ---&gt;
849 very poorly. Of course, remember to enable &quot;IDE disk&quot; support as well -- otherwise your 852 [*] Prompt for development and/or incomplete code/drivers&quot;
850 kernel won't be able to see your IDE disks. 853<comment>(You need this to enable some of the options below.)</comment>
851 </warn> 854 ...
855
856File systems ---&gt;
857 &lt;*&gt; Reiserfs support
858<comment>(Only needed if you are using reiserfs.)</comment>
859 ...
860 &lt;*&gt; Ext3 journalling file system support
861<comment>(Only needed if you are using ext3.)</comment>
862 ...
863 [*] Virtual memory file system support (former shm fs)
864<comment>(Required for Gentoo Linux.)</comment>
865 ...
866 &lt;*&gt; JFS filesystem support
867<comment>(Only needed if you are using JFS.)</comment>
868 ...
869 [*] /proc file system support
870<comment>(Required for Gentoo Linux.)</comment>
871 [*] /dev file system support (EXPERIMENTAL)
872 [*] Automatically mount at boot
873<comment>(Required for Gentoo Linux.)</comment>
874 [ ] /dev/pts file system for Unix98 PTYs
875<comment>(Uncheck this, it is NOT needed.)</comment>
876 ...
877 &lt;*&gt; Second extended fs support
878<comment>(Only needed if you are using ext2.)</comment>
879 ...
880 &lt;*&gt; XFS filesystem support
881<comment>(Only needed if you are using XFS.)</comment>
882</pre>
852 <p>If you are using hardware RAID you will need to enable a couple more options in the kernel: 883 <p>If you are using hardware RAID you will need to enable a couple more options in the kernel:
853 For Highpoint RAID controllers select hpt366 chipset support, support for IDE RAID controllers and Highpoint 884 For Highpoint RAID controllers select hpt366 chipset support, support for IDE RAID controllers and Highpoint
854 370 software RAID.For Promise RAID controllers select PROMISE PDC202{46|62|65|67|68|69|70} support, 885 370 software RAID.For Promise RAID controllers select PROMISE PDC202{46|62|65|67|68|69|70} support,
855 support for IDE RAID 886 support for IDE RAID
856 controllers and Support Promise software RAID (Fasttrak(tm)) 887 controllers and Support Promise software RAID (Fasttrak(tm))
891 to gravitate away from sysklogd (not very good performance) and towards the 922 to gravitate away from sysklogd (not very good performance) and towards the
892 newer alternatives. 923 newer alternatives.
893 If in doubt, you may want to try metalog, since it seems to be quite popular. 924 If in doubt, you may want to try metalog, since it seems to be quite popular.
894 To merge your logger of choice, type <e>one</e> of the next four lines: 925 To merge your logger of choice, type <e>one</e> of the next four lines:
895 </p> 926 </p>
896 <pre caption="Emerging System Logger of Choice"> 927<pre caption="Emerging System Logger of Choice">
897# <c>emerge app-admin/sysklogd</c> 928# <c>emerge app-admin/sysklogd</c>
898# <c>rc-update add sysklogd default</c> 929# <c>rc-update add sysklogd default</c>
899<comment>or</comment> 930<comment>or</comment>
900# <c>emerge app-admin/syslog-ng</c> 931# <c>emerge app-admin/syslog-ng</c>
901# <c>rc-update add syslog-ng default</c> 932# <c>rc-update add syslog-ng default</c>
903# <c>emerge app-admin/metalog</c> 934# <c>emerge app-admin/metalog</c>
904# <c>rc-update add metalog default</c> 935# <c>rc-update add metalog default</c>
905<comment>or</comment> 936<comment>or</comment>
906# <c>emerge app-admin/msyslog</c> 937# <c>emerge app-admin/msyslog</c>
907# <c>rc-update add msyslog default</c> 938# <c>rc-update add msyslog default</c>
908 </pre> 939</pre>
909 <warn> 940 <warn>
910 In the case of syslog-ng you need to create 941 In the case of syslog-ng you need to create
911 <path>/etc/syslog-ng/syslog-ng.conf</path>. 942 <path>/etc/syslog-ng/syslog-ng.conf</path>.
912 See <path>/etc/syslog-ng</path> 943 See <path>/etc/syslog-ng</path>
913 for a sample configuration file. 944 for a sample configuration file.
925 </impo> 956 </impo>
926 <p>Now, you may optionally choose a cron package that you would like to use. 957 <p>Now, you may optionally choose a cron package that you would like to use.
927 Right now, we offer dcron, fcron and vcron. If you do not know which one to choose, 958 Right now, we offer dcron, fcron and vcron. If you do not know which one to choose,
928 you might as well grab vcron. They can be installed as follows: 959 you might as well grab vcron. They can be installed as follows:
929 </p> 960 </p>
930 <pre caption="Choosing a CRON Daemon"> 961<pre caption="Choosing a CRON Daemon">
931# <c>emerge sys-apps/dcron</c> 962# <c>emerge sys-apps/dcron</c>
963# <c>rc-update add dcron default</c>
932# <c>crontab /etc/crontab</c> 964# <c>crontab /etc/crontab</c>
933<comment>or</comment> 965<comment>or</comment>
934# <c>emerge sys-apps/fcron</c> 966# <c>emerge sys-apps/fcron</c>
967# <c>rc-update add fcron default</c>
935# <c>crontab /etc/crontab</c> 968# <c>crontab /etc/crontab</c>
936<comment>or</comment> 969<comment>or</comment>
937# <c>emerge sys-apps/vcron</c> 970# <c>emerge sys-apps/vcron</c>
971# <c>rc-update add vcron default</c>
938<comment>You do not need to run <c>crontab /etc/crontab</c> if using vcron. </comment> 972<comment>You do not need to run <c>crontab /etc/crontab</c> if using vcron.</comment>
939<comment>Do not forget to add your *cron to the proper init level. </comment>
940# <c>rc-update add *cron default </c>
941 </pre> 973</pre>
942<!--<p>For more information how how cron works under Gentoo Linux,
943 see <uri link="http://lists.gentoo.org/pipermail/gentoo-announce/2002-April/000151.html">this announcement</uri>.</p>-->
944 <p>For more information on starting programs and daemons at startup, see the 974 <p>For more information on starting programs and daemons at startup, see the
945 <uri link="/doc/en/rc-scripts.xml">rc-script guide</uri>. 975 <uri link="/doc/en/rc-scripts.xml">rc-script guide</uri>.
946 </p> 976 </p>
947 </body> 977 </body>
948 </section> 978 </section>
949 </chapter> 979 </chapter>
951 <title>Installing miscellany necessary packages</title> 981 <title>Installing miscellany necessary packages</title>
952 <section> 982 <section>
953 <body> 983 <body>
954 <p>If you need rp-pppoe to connect to the net, be aware that at this point 984 <p>If you need rp-pppoe to connect to the net, be aware that at this point
955 it has not been installed. It would be the good time to do it. </p> 985 it has not been installed. It would be the good time to do it. </p>
956 <pre caption="Installing rp-pppoe"> 986<pre caption="Installing rp-pppoe">
957# <c>USE="-X" emerge rp-pppoe</c> 987# <c>USE="-X" emerge rp-pppoe</c>
958 </pre> 988</pre>
959 989
960 <note>The <i>USE="-X"</i> prevents pppoe from installing its optional X interface, which is a good thing, 990 <note>The <i>USE="-X"</i> prevents pppoe from installing its optional X interface, which is a good thing,
961 because X and its dependencies would also be emerged. You can always recompile <i>rp-pppoe</i> with 991 because X and its dependencies would also be emerged. You can always recompile <i>rp-pppoe</i> with
962 X support later. 992 X support later.
963 </note> 993 </note>
967 </note> 997 </note>
968 <p>You may need to install some additional packages in the Portage tree 998 <p>You may need to install some additional packages in the Portage tree
969 if you are using any optional features like XFS, ReiserFS or LVM. If you're 999 if you are using any optional features like XFS, ReiserFS or LVM. If you're
970 using XFS, you should emerge the <c>xfsprogs</c> package: 1000 using XFS, you should emerge the <c>xfsprogs</c> package:
971 </p> 1001 </p>
972 <pre caption="Emerging Filesystem Tools"> 1002<pre caption="Emerging Filesystem Tools">
973# <c>emerge sys-apps/xfsprogs</c> 1003# <c>emerge sys-apps/xfsprogs</c>
974<comment>If you would like to use ReiserFS, you should emerge the ReiserFS tools: </comment> 1004<comment>If you would like to use ReiserFS, you should emerge the ReiserFS tools: </comment>
975# <c>emerge sys-apps/reiserfsprogs</c> 1005# <c>emerge sys-apps/reiserfsprogs</c>
976<comment>If you would like to use JFS, you should emerge the JFS tools: </comment> 1006<comment>If you would like to use JFS, you should emerge the JFS tools: </comment>
977# <c>emerge jfsutils</c> 1007# <c>emerge jfsutils</c>
978<comment>If you're using LVM, you should emerge the <c>lvm-user</c> package: </comment> 1008<comment>If you're using LVM, you should emerge the <c>lvm-user</c> package: </comment>
979# <c>emerge sys-apps/lvm-user</c> 1009# <c>emerge sys-apps/lvm-user</c>
980 </pre> 1010</pre>
981 <p>If you're a laptop user and wish to use your PCMCIA slots on your first 1011 <p>If you're a laptop user and wish to use your PCMCIA slots on your first
982 real reboot, you will want to make sure you install the <i>pcmcia-cs</i> package. 1012 real reboot, you will want to make sure you install the <i>pcmcia-cs</i> package.
983 </p> 1013 </p>
984 <pre caption="Emerging PCMCIA-cs"> 1014<pre caption="Emerging PCMCIA-cs">
985# <c>emerge sys-apps/pcmcia-cs</c> 1015# <c>emerge sys-apps/pcmcia-cs</c>
986 </pre> 1016</pre>
987 <warn>You will have to re-emerge <i>pcmcia-cs</i> after installation to get PCMCIA 1017 <warn>You will have to re-emerge <i>pcmcia-cs</i> after installation to get PCMCIA
988 to work. 1018 to work.
989 </warn> 1019 </warn>
990 </body> 1020 </body>
991 </section> 1021 </section>
1001 the <c>notail</c> option for your boot partition if you chose to create a ReiserFS filesystem on it. 1031 the <c>notail</c> option for your boot partition if you chose to create a ReiserFS filesystem on it.
1002 Remember to specify <c>ext2</c>, <c>ext3</c> or <c>reiserfs</c> filesystem types as appropriate. 1032 Remember to specify <c>ext2</c>, <c>ext3</c> or <c>reiserfs</c> filesystem types as appropriate.
1003 </p> 1033 </p>
1004 <p>Use something like the <path>/etc/fstab</path> listed below, but of course be sure to replace &quot;BOOT&quot;, 1034 <p>Use something like the <path>/etc/fstab</path> listed below, but of course be sure to replace &quot;BOOT&quot;,
1005 &quot;ROOT&quot; and &quot;SWAP&quot; with the actual block devices you are using (such as <c>hda1</c>, etc.)</p> 1035 &quot;ROOT&quot; and &quot;SWAP&quot; with the actual block devices you are using (such as <c>hda1</c>, etc.)</p>
1006 <pre caption="Editing fstab"><comment> 1036<pre caption="Editing fstab">
1007# /etc/fstab: static file system information. 1037<comment># /etc/fstab: static file system information.
1008# 1038#
1009# noatime turns off atimes for increased performance (atimes normally aren't 1039# noatime turns off atimes for increased performance (atimes normally aren't
1010# needed; notail increases performance of ReiserFS (at the expense of storage 1040# needed; notail increases performance of ReiserFS (at the expense of storage
1011# efficiency). It is safe to drop the noatime options if you want and to 1041# efficiency). It is safe to drop the noatime options if you want and to
1012# switch between notail and tail freely. 1042# switch between notail and tail freely.
1018/dev/BOOT /boot ext2 noauto,noatime 1 2 1048/dev/BOOT /boot ext2 noauto,noatime 1 2
1019/dev/ROOT / ext3 noatime 0 1 1049/dev/ROOT / ext3 noatime 0 1
1020/dev/SWAP none swap sw 0 0 1050/dev/SWAP none swap sw 0 0
1021/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0 1051/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0
1022proc /proc proc defaults 0 0 1052proc /proc proc defaults 0 0
1023 </pre> 1053</pre>
1024 <warn>Please notice that <i>/boot</i> is NOT mounted at boot time. 1054 <warn>Please notice that <i>/boot</i> is NOT mounted at boot time.
1025 This is to protect the data in <i>/boot</i> from 1055 This is to protect the data in <i>/boot</i> from
1026 corruption. If you need to access <i>/boot</i>, please mount it! 1056 corruption. If you need to access <i>/boot</i>, please mount it!
1027 </warn> 1057 </warn>
1028 </body> 1058 </body>
1031 <chapter> 1061 <chapter>
1032 <title>Setting the Root Password</title> 1062 <title>Setting the Root Password</title>
1033 <section> 1063 <section>
1034 <body> 1064 <body>
1035 <p>Before you forget, set the root password by typing: </p> 1065 <p>Before you forget, set the root password by typing: </p>
1036 <pre caption="Setting the root Password"> 1066<pre caption="Setting the root Password">
1037# <c>passwd</c> 1067# <c>passwd</c>
1038 </pre> 1068</pre>
1039 1069
1040 <p>You will also want to add a non-root user for everyday use. Please consult 1070 <p>You will also want to add a non-root user for everyday use. Please consult
1041 the <uri link="http://www.gentoo.org/doc/en/faq.xml">Gentoo FAQ</uri>. 1071 the <uri link="http://www.gentoo.org/doc/en/faq.xml">Gentoo FAQ</uri>.
1042 </p> 1072 </p>
1043 </body> 1073 </body>
1048 <section> 1078 <section>
1049 <body> 1079 <body>
1050 <p>Edit this file so that it contains your fully-qualified domain name on a single line, 1080 <p>Edit this file so that it contains your fully-qualified domain name on a single line,
1051 i.e. <c>mymachine.mydomain.com</c>. 1081 i.e. <c>mymachine.mydomain.com</c>.
1052 </p> 1082 </p>
1053 <pre caption="Configuring Hostname"> 1083<pre caption="Configuring Hostname">
1054# <c>echo mymachine.mydomain.com &gt; /etc/hostname</c> 1084# <c>echo mymachine.mydomain.com &gt; /etc/hostname</c>
1055 </pre> 1085</pre>
1056 </body> 1086 </body>
1057 </section> 1087 </section>
1058 </chapter> 1088 </chapter>
1059 <chapter> 1089 <chapter>
1060 <title>Modifying /etc/hosts</title> 1090 <title>Modifying /etc/hosts</title>
1062 <body> 1092 <body>
1063 <p>This file contains a list of ip addresses and their associated hostnames. 1093 <p>This file contains a list of ip addresses and their associated hostnames.
1064 It is used by the system to resolve the IP addresses 1094 It is used by the system to resolve the IP addresses
1065 of any hostnames that may not be in your nameservers. Here is a template for this file: 1095 of any hostnames that may not be in your nameservers. Here is a template for this file:
1066 </p> 1096 </p>
1067 <pre caption="Hosts Template"> 1097<pre caption="Hosts Template">
1068127.0.0.1 localhost 1098127.0.0.1 localhost
1069<comment># the next line contains your IP for your local LAN, and your associated machine name</comment> 1099<comment># the next line contains your IP for your local LAN, and your associated machine name</comment>
1070192.168.1.1 mymachine.mydomain.com mymachine 1100192.168.1.1 mymachine.mydomain.com mymachine
1071 </pre> 1101</pre>
1072 <note>If you are on a DHCP network, it might be helpful to set <i>localhost</i> to your machine's 1102 <note>If you are on a DHCP network, it might be helpful to set <i>localhost</i> to your machine's
1073 actual hostname. This will help GNOME and many other programs in name resolution. 1103 actual hostname. This will help GNOME and many other programs in name resolution.
1074 </note> 1104 </note>
1075 </body> 1105 </body>
1076 </section> 1106 </section>
1083 <path>/etc/modules.autoload</path> file (you can also add any options you 1113 <path>/etc/modules.autoload</path> file (you can also add any options you
1084 need to the same line.) When Gentoo Linux boots, these modules will be automatically 1114 need to the same line.) When Gentoo Linux boots, these modules will be automatically
1085 loaded. Of particular importance is your ethernet card module, if you happened to compile 1115 loaded. Of particular importance is your ethernet card module, if you happened to compile
1086 it as a module: 1116 it as a module:
1087 </p> 1117 </p>
1088 <pre caption="/etc/modules.autoload"><comment>This is assuming that you are using a 3com card. 1118<pre caption="/etc/modules.autoload"><comment>This is assuming that you are using a 3com card.
1089 Check <path>/lib/modules/`uname -r`/kernel/drivers/net</path> for your card. </comment> 1119Check <path>/lib/modules/`uname -r`/kernel/drivers/net</path> for your card. </comment>
10903c59x 11203c59x
1091 </pre> 1121</pre>
1092 <p>Edit the <path>/etc/conf.d/net</path> script to get your network configured for your 1122 <p>Edit the <path>/etc/conf.d/net</path> script to get your network configured for your
1093 first boot: </p> 1123 first boot: </p>
1094 <pre caption="Boot time Network Configuration"> 1124<pre caption="Boot time Network Configuration">
1095# <c>nano -w /etc/conf.d/net</c> 1125# <c>nano -w /etc/conf.d/net</c>
1096# <c>rc-update add net.eth0 default</c> 1126# <c>rc-update add net.eth0 default</c>
1097 </pre> 1127</pre>
1098 <p>If you have multiple network cards you need to create additional <path>net.eth<comment>x</comment></path> 1128 <p>If you have multiple network cards you need to create additional <path>net.eth<comment>x</comment></path>
1099 scripts for each one (<comment>x</comment> = 1, 2, ...): </p> 1129 scripts for each one (<comment>x</comment> = 1, 2, ...): </p>
1100 <pre caption="Multiple Network Interfaces"> 1130<pre caption="Multiple Network Interfaces">
1101# <c>cd /etc/init.d</c> 1131# <c>cd /etc/init.d</c>
1102# <c>cp net.eth0 net.eth<comment>x</comment></c> 1132# <c>cp net.eth0 net.eth<comment>x</comment></c>
1103# <c>rc-update add net.eth<comment>x</comment> default</c> 1133# <c>rc-update add net.eth<comment>x</comment> default</c>
1104 </pre> 1134</pre>
1105 <p>If you have a PCMCIA card installed, have a quick look into 1135 <p>If you have a PCMCIA card installed, have a quick look into
1106 <path>/etc/init.d/pcmcia</path> to verify that things seem all right for your setup, 1136 <path>/etc/init.d/pcmcia</path> to verify that things seem all right for your setup,
1107 then add this line to the top of <path>/etc/init.d/net.ethx</path>: 1137 then add this line to the top of <path>/etc/init.d/net.ethx</path>:
1108 </p> 1138 </p>
1109 <pre caption="PCMCIA depend in /etc/init.d/net.ethx"> 1139<pre caption="PCMCIA depend in /etc/init.d/net.ethx">
1110depend() { 1140depend() {
1111 need pcmcia 1141 need pcmcia
1112} 1142}
1113 </pre> 1143</pre>
1114 <p>This makes sure that the PCMCIA drivers are autoloaded whenever your network is loaded. 1144 <p>This makes sure that the PCMCIA drivers are autoloaded whenever your network is loaded.
1115 </p> 1145 </p>
1116 </body> 1146 </body>
1117 </section> 1147 </section>
1118 </chapter> 1148 </chapter>
1119 <chapter> 1149 <chapter>
1120 <title>Final steps: Configure Basic Settings (including the international keymap setting)</title> 1150 <title>Final steps: Configure Basic Settings (including the international keymap setting)</title>
1121 <section> 1151 <section>
1122 <body> 1152 <body>
1123 <pre caption="Basic Configuration"> 1153<pre caption="Basic Configuration">
1124# <c>nano -w /etc/rc.conf</c> 1154# <c>nano -w /etc/rc.conf</c>
1125 </pre> 1155</pre>
1126 <p>Follow the directions in the file to configure the basic settings. 1156 <p>Follow the directions in the file to configure the basic settings.
1127 All users will want to make sure that <c>CLOCK</c> is set to his/her 1157 All users will want to make sure that <c>CLOCK</c> is set to his/her
1128 liking. International keyboard users will want to set the <c>KEYMAP</c> 1158 liking. International keyboard users will want to set the <c>KEYMAP</c>
1129 variable (browse <path>/usr/share/keymaps</path> to see the various 1159 variable (browse <path>/usr/share/keymaps</path> to see the various
1130 possibilities). 1160 possibilities).
1173 a lot of harddrives and partitions and who are a little lost in the 1203 a lot of harddrives and partitions and who are a little lost in the
1174 grub numbering scheme. Having gotten the feel for that, 1204 grub numbering scheme. Having gotten the feel for that,
1175 it is time to install GRUB. 1205 it is time to install GRUB.
1176 </p> 1206 </p>
1177 <p>The easiest way to install GRUB is to simply type <c>grub</c> at your chrooted shell prompt: </p> 1207 <p>The easiest way to install GRUB is to simply type <c>grub</c> at your chrooted shell prompt: </p>
1178 <pre caption="Installing GRUB"> 1208<pre caption="Installing GRUB">
1179# <c>emerge grub</c> 1209# <c>emerge grub</c>
1180# <c>grub</c> 1210# <c>grub</c>
1181 </pre> 1211</pre>
1182 <impo>If you are using hardware RAID this part will not work at 1212 <impo>If you are using hardware RAID this part will not work at
1183 this time. 1213 this time.
1184 Skip to the section on making your <path>grub.conf</path>. After that we will complete the 1214 Skip to the section on making your <path>grub.conf</path>. After that we will complete the
1185 grub setup for RAID controllers 1215 grub setup for RAID controllers
1186 </impo> 1216 </impo>
1190 I want to install the GRUB boot record on my hard drive's MBR (master boot record), so that 1220 I want to install the GRUB boot record on my hard drive's MBR (master boot record), so that
1191 the first thing I see when I turn on the computer is the GRUB prompt. In my case, the commands 1221 the first thing I see when I turn on the computer is the GRUB prompt. In my case, the commands
1192 I want to type are: 1222 I want to type are:
1193 </p> 1223 </p>
1194 1224
1195 <pre caption="GRUB on the MBR"> 1225<pre caption="GRUB on the MBR">
1196grub&gt; <c>root (hd0,0)</c> <codenote>Your boot partition</codenote> 1226grub&gt; <c>root (hd0,0)</c> <codenote>Your boot partition</codenote>
1197grub&gt; <c>setup (hd0)</c> <codenote>Where the boot record is installed, here, it is the MBR</codenote> 1227grub&gt; <c>setup (hd0)</c> <codenote>Where the boot record is installed, here, it is the MBR</codenote>
1198 </pre> 1228</pre>
1199 1229
1200 <pre caption="GRUB not on the MBR"> 1230<pre caption="GRUB not on the MBR">
1201<comment>Alternatively, if you wanted to install the bootloader somewhere other than the MBR</comment> 1231<comment>Alternatively, if you wanted to install the bootloader somewhere other than the MBR</comment>
1202grub&gt; <c>root (hd0,0)</c> <codenote>Your boot partition</codenote> 1232grub&gt; <c>root (hd0,0)</c> <codenote>Your boot partition</codenote>
1203grub&gt; <c>setup (hd0,4)</c> <codenote>Where the boot record is installed, here it is /dev/hda5</codenote> 1233grub&gt; <c>setup (hd0,4)</c> <codenote>Where the boot record is installed, here it is /dev/hda5</codenote>
1204grub&gt; <c>quit</c> 1234grub&gt; <c>quit</c>
1205 </pre> 1235</pre>
1206 1236
1207 <p>Here is how the two commands work. The first <c>root ( )</c> command tells GRUB 1237 <p>Here is how the two commands work. The first <c>root ( )</c> command tells GRUB
1208 the location of your boot partition (in our example, <path>/dev/hda1</path> or 1238 the location of your boot partition (in our example, <path>/dev/hda1</path> or
1209 <path>(hd0,0)</path> in GRUB terminology. Then, the second <c>setup ( ) 1239 <path>(hd0,0)</path> in GRUB terminology. Then, the second <c>setup ( )
1210 </c> command tells GRUB where to install the 1240 </c> command tells GRUB where to install the
1236 <impo>To ensure backwards compatibility with GRUB, make sure to make a link from 1266 <impo>To ensure backwards compatibility with GRUB, make sure to make a link from
1237 <i>grub.conf</i> to <i>menu.lst</i>. You can do this by doing 1267 <i>grub.conf</i> to <i>menu.lst</i>. You can do this by doing
1238 <c>ln -s /boot/grub/grub.conf /boot/grub/menu.lst </c>. </impo> 1268 <c>ln -s /boot/grub/grub.conf /boot/grub/menu.lst </c>. </impo>
1239 <p>Now, create the grub.conf file (<c>nano -w /boot/grub/grub.conf</c>), and add the following to it: 1269 <p>Now, create the grub.conf file (<c>nano -w /boot/grub/grub.conf</c>), and add the following to it:
1240 </p> 1270 </p>
1241 <pre caption="Grub.conf for GRUB"> 1271<pre caption="Grub.conf for GRUB">
1242default 0 1272default 0
1243timeout 30 1273timeout 30
1244splashimage=(hd0,0)/boot/grub/splash.xpm.gz 1274splashimage=(hd0,0)/boot/grub/splash.xpm.gz
1245 1275
1246title=My example Gentoo Linux 1276title=My example Gentoo Linux
1247root (hd0,0) 1277root (hd0,0)
1248kernel (hd0,0)/boot/bzImage root=/dev/hda3 1278kernel (hd0,0)/boot/bzImage root=/dev/hda3
1249 1279
1250<comment> #Below is for setup using hardware RAID</comment> 1280<comment># Below is for setup using hardware RAID</comment>
1251title=My Gentoo Linux on RAID 1281title=My Gentoo Linux on RAID
1252root (hd0,0) 1282root (hd0,0)
1253kernel (hd0,0)/boot/bzImage root=/dev/ataraid/dXpY 1283kernel (hd0,0)/boot/bzImage root=/dev/ataraid/dXpY
1254 1284
1255<comment># Below needed only for people who dual-boot</comment> 1285<comment># Below needed only for people who dual-boot</comment>
1256title=Windows NT Workstation 1286title=Windows XP
1257root (hd0,5) 1287root (hd0,5)
1258chainloader (hd0,5)+1 1288chainloader (hd0,5)+1
1259 </pre> 1289</pre>
1260 <note> 1290 <note>
1261 (hd0,0) should be written without any spaces inside the parentheses. 1291 (hd0,0) should be written without any spaces inside the parentheses.
1262 </note> 1292 </note>
1263 <impo> 1293 <impo>
1264 If you set up scsi emulation for an IDE cd burner earlier, then to get it to 1294 If you set up scsi emulation for an IDE cd burner earlier, then to get it to
1296 LILO, the LInuxLOader, is the tried and true workhorse of Linux bootloaders. Here is how to install 1326 LILO, the LInuxLOader, is the tried and true workhorse of Linux bootloaders. Here is how to install
1297 LILO if you would like to use it instead of GRUB: 1327 LILO if you would like to use it instead of GRUB:
1298 </p> 1328 </p>
1299 <p>The first step is to emerge LILO: 1329 <p>The first step is to emerge LILO:
1300 </p> 1330 </p>
1301 <pre caption="Emerging LILO"> 1331<pre caption="Emerging LILO">
1302# <c>emerge lilo</c> 1332# <c>emerge lilo</c>
1303 </pre> 1333</pre>
1304 <p>Now it is time to configure LILO. Here is a sample configuration file (lilo.conf) 1334 <p>Now it is time to configure LILO. Here is a sample configuration file (lilo.conf)
1305 </p> 1335 </p>
1306 <pre caption="Example lilo.conf"> 1336<pre caption="Example lilo.conf">
1307boot=/dev/hda 1337boot=/dev/hda
1308map=/boot/map 1338map=/boot/map
1309install=/boot/boot.b 1339install=/boot/boot.b
1310prompt 1340prompt
1311timeout=50 1341timeout=50
1319 root=/dev/hda5 1349 root=/dev/hda5
1320 1350
1321#For dual booting windows/other OS 1351#For dual booting windows/other OS
1322other=/dev/hda1 1352other=/dev/hda1
1323 label=dos 1353 label=dos
1324
1325 </pre> 1354</pre>
1326 <ul> 1355 <ul>
1327 <li><i>boot=/dev/hda</i> tells LILO to install itself on the first hard disk on the first IDE controller. </li> 1356 <li><i>boot=/dev/hda</i> tells LILO to install itself on the first hard disk on the first IDE controller. </li>
1328 <li><i>map=/boot/map</i> states the map file. In normal use, this should not be modified. </li> 1357 <li><i>map=/boot/map</i> states the map file. In normal use, this should not be modified. </li>
1329 <li><i>install=/boot/boot.b</i> tells LILO to install the specified file as the new boot sector. 1358 <li><i>install=/boot/boot.b</i> tells LILO to install the specified file as the new boot sector.
1330 In normal use, this should not be altered. If the install line is missing, LILO will 1359 In normal use, this should not be altered. If the install line is missing, LILO will
1351 <note>Thanks to <uri link="http://www.redhat.com">Redhat.com</uri> for this information. 1380 <note>Thanks to <uri link="http://www.redhat.com">Redhat.com</uri> for this information.
1352 </note> 1381 </note>
1353 <p>After you have edited your <i>lilo.conf</i> file, it is time to run LILO to load the information 1382 <p>After you have edited your <i>lilo.conf</i> file, it is time to run LILO to load the information
1354 into the MBR: 1383 into the MBR:
1355 </p> 1384 </p>
1356 <pre caption="Running LILO"> 1385<pre caption="Running LILO">
1357# <c>/sbin/lilo</c> 1386# <c>/sbin/lilo</c>
1358 </pre> 1387</pre>
1359 <p>LILO is configured, and now your machine is ready to boot into Gentoo Linux! 1388 <p>LILO is configured, and now your machine is ready to boot into Gentoo Linux!
1360 </p> 1389 </p>
1361 </body> 1390 </body>
1362 </section> 1391 </section>
1363 </chapter> 1392 </chapter>
1374 make a GRUB 1403 make a GRUB
1375 boot disk, and when you reboot the first time you can install GRUB 1404 boot disk, and when you reboot the first time you can install GRUB
1376 to the MBR. Make your 1405 to the MBR. Make your
1377 bootdisks like this: 1406 bootdisks like this:
1378 </p> 1407 </p>
1379 <pre caption="Creating a GRUB Bootdisk"> 1408<pre caption="Creating a GRUB Bootdisk">
1380# <c>mke2fs /dev/fd0</c> 1409# <c>mke2fs /dev/fd0</c>
1381# <c>mount /dev/fd0 /mnt/floppy</c> 1410# <c>mount /dev/fd0 /mnt/floppy</c>
1382# <c>mkdir -p /mnt/floppy/boot/grub</c> 1411# <c>mkdir -p /mnt/floppy/boot/grub</c>
1383# <c>cp /usr/share/grub/i386-pc/stage1 /mnt/floppy/boot/grub/</c> 1412# <c>cp /usr/share/grub/i386-pc/stage1 /mnt/floppy/boot/grub/</c>
1384# <c>cp /usr/share/grub/i386-pc/stage2 /mnt/floppy/boot/grub/</c> 1413# <c>cp /usr/share/grub/i386-pc/stage2 /mnt/floppy/boot/grub/</c>
1386# <c>grub</c> 1415# <c>grub</c>
1387 1416
1388grub&gt; <c>root (fd0)</c> 1417grub&gt; <c>root (fd0)</c>
1389grub&gt; <c>setup (fd0)</c> 1418grub&gt; <c>setup (fd0)</c>
1390grub&gt; <c>quit</c> 1419grub&gt; <c>quit</c>
1391 </pre> 1420</pre>
1392 <p>Now reboot and load the floppy. At the floppy's <c>grub&gt;</c> prompt, you can now execute the necessary <c>root</c> 1421 <p>Now reboot and load the floppy. At the floppy's <c>grub&gt;</c> prompt, you can now execute the necessary <c>root</c>
1393 and <c>setup</c> commands.</p> 1422 and <c>setup</c> commands.</p>
1394 </body> 1423 </body>
1395 </section> 1424 </section>
1396 <section> 1425 <section>
1397 <title>LILO Bootdisks</title> 1426 <title>LILO Bootdisks</title>
1398 <body> 1427 <body>
1399 <p>If you are using LILO, it is also a good idea to make a bootdisk: 1428 <p>If you are using LILO, it is also a good idea to make a bootdisk:
1400 </p> 1429 </p>
1401 <pre caption="Making a LILO Bootdisk"> 1430<pre caption="Making a LILO Bootdisk">
1402# <c>dd if=/boot/your_kernel of=/dev/fd0 </c> 1431# <c>dd if=/boot/your_kernel of=/dev/fd0 </c>
1403<comment>This will only work if your kernel is smaller than 1.4MB</comment> 1432<comment>This will only work if your kernel is smaller than 1.4MB</comment>
1404 </pre> 1433</pre>
1405 </body> 1434 </body>
1406 </section> 1435 </section>
1407 </chapter> 1436 </chapter>
1408 <chapter> 1437 <chapter>
1409 <title>Installation Complete!</title> 1438 <title>Installation Complete!</title>
1412 <p>Now, Gentoo Linux is installed. The only remaining step is to update necessary configuration files, exit the chrooted shell, 1441 <p>Now, Gentoo Linux is installed. The only remaining step is to update necessary configuration files, exit the chrooted shell,
1413 1442
1414 safely unmount your partitions 1443 safely unmount your partitions
1415 and reboot the system: 1444 and reboot the system:
1416 </p> 1445 </p>
1417 <pre caption="Rebooting the System"> 1446<pre caption="Rebooting the System">
1418# <c>etc-update</c> 1447# <c>etc-update</c>
1419# <c>exit</c> 1448# <c>exit</c>
1420<codenote>This exits the chrooted shell; you can also type <c>^D</c></codenote> 1449<comment>(This exits the chrooted shell; you can also type <c>^D</c>)</comment>
1421# <c>cd / </c> 1450# <c>cd / </c>
1422# <c>umount /mnt/gentoo/boot</c> 1451# <c>umount /mnt/gentoo/boot</c>
1423# <c>umount /mnt/gentoo/proc</c> 1452# <c>umount /mnt/gentoo/proc</c>
1424# <c>umount /mnt/gentoo</c> 1453# <c>umount /mnt/gentoo</c>
1425# <c>reboot</c> 1454# <c>reboot</c>
1426 </pre> 1455</pre>
1427 <note> 1456 <note>
1428 After rebooting, it is a good idea to run the <c>update-modules</c> command to create 1457 After rebooting, it is a good idea to run the <c>update-modules</c> command to create
1429 the <path>/etc/modules.conf</path> file. Instead of modifying this file directly, you should 1458 the <path>/etc/modules.conf</path> file. Instead of modifying this file directly, you should
1430 generally make changes to the files in <path>/etc/modules.d</path>. 1459 generally make changes to the files in <path>/etc/modules.d</path>.
1431 </note> 1460 </note>
1482 <li>The IP address your data transmission originates from will never be logged 1511 <li>The IP address your data transmission originates from will never be logged
1483 in such a way that we can identify you. There are no &quot;IP address/system ID&quot; pairs.</li> 1512 in such a way that we can identify you. There are no &quot;IP address/system ID&quot; pairs.</li>
1484 </ul> 1513 </ul>
1485 <p>The installation is easy - just run the following commands: 1514 <p>The installation is easy - just run the following commands:
1486 </p> 1515 </p>
1487 <pre caption="Installing gentoo-stats"> 1516<pre caption="Installing gentoo-stats">
1488# <c>emerge gentoo-stats</c> <codenote>Installs gentoo-stats</codenote> 1517# <c>emerge gentoo-stats</c> <codenote>Installs gentoo-stats</codenote>
1489# <c>gentoo-stats --new</c> <codenote>Obtains a new system ID</codenote> 1518# <c>gentoo-stats --new</c> <codenote>Obtains a new system ID</codenote>
1490 </pre> 1519</pre>
1491 <p>The second command above will request a new system ID and enter it into 1520 <p>The second command above will request a new system ID and enter it into
1492 <path>/etc/gentoo-stats/gentoo-stats.conf</path> automatically. You can view this file 1521 <path>/etc/gentoo-stats/gentoo-stats.conf</path> automatically. You can view this file
1493 to see additional configuration options. 1522 to see additional configuration options.
1494 </p> 1523 </p>
1495 <p>After that, the program should be run on a regular schedule 1524 <p>After that, the program should be run on a regular schedule
1496 (gentoo-stats does not have to be run as root). Add this line to your <path>crontab</path>: 1525 (gentoo-stats does not have to be run as root). Add this line to your <path>crontab</path>:
1497 </p> 1526 </p>
1498 <pre caption="Updating gentoo-stats with cron"> 1527<pre caption="Updating gentoo-stats with cron">
1499 <c>0 0 * * 0,4 /usr/sbin/gentoo-stats --update &gt; /dev/null</c> 1528<c>0 0 * * 0,4 /usr/sbin/gentoo-stats --update &gt; /dev/null</c>
1500 </pre> 1529</pre>
1501 <p>The <c>gentoo-stats</c> program is a simple perl script which can be 1530 <p>The <c>gentoo-stats</c> program is a simple perl script which can be
1502 viewed with your favorite pager or editor: <path>/usr/sbin/gentoo-stats</path>. </p> 1531 viewed with your favorite pager or editor: <path>/usr/sbin/gentoo-stats</path>. </p>
1503 </body> 1532 </body>
1504 </section> 1533 </section>
1505 </chapter> 1534 </chapter>

Legend:
Removed from v.1.80  
changed lines
  Added in v.1.81

  ViewVC Help
Powered by ViewVC 1.1.20