| 1 |
fox2mike 06/02/01 18:38:18 |
| 2 |
|
| 3 |
Added: xml/htdocs/doc/en/handbook/draft/2006.0 handbook-alpha.xml |
| 4 |
handbook-amd64.xml handbook-hppa.xml |
| 5 |
handbook-ppc.xml handbook-ppc64.xml |
| 6 |
handbook-sparc.xml handbook-x86.xml |
| 7 |
hb-install-about.xml |
| 8 |
hb-install-alpha-bootloader.xml |
| 9 |
hb-install-alpha-disk.xml |
| 10 |
hb-install-alpha-kernel.xml |
| 11 |
hb-install-alpha-medium.xml |
| 12 |
hb-install-amd64-bootloader.xml |
| 13 |
hb-install-amd64-disk.xml |
| 14 |
hb-install-amd64-kernel.xml |
| 15 |
hb-install-amd64-medium.xml hb-install-config.xml |
| 16 |
hb-install-finalise.xml |
| 17 |
hb-install-hppa-bootloader.xml |
| 18 |
hb-install-hppa-disk.xml hb-install-hppa-kernel.xml |
| 19 |
hb-install-hppa-medium.xml hb-install-network.xml |
| 20 |
hb-install-next.xml hb-install-ppc-bootloader.xml |
| 21 |
hb-install-ppc-disk.xml hb-install-ppc-kernel.xml |
| 22 |
hb-install-ppc-medium.xml |
| 23 |
hb-install-ppc64-bootloader.xml |
| 24 |
hb-install-ppc64-disk.xml |
| 25 |
hb-install-ppc64-kernel.xml |
| 26 |
hb-install-ppc64-medium.xml |
| 27 |
hb-install-sparc-bootloader.xml |
| 28 |
hb-install-sparc-disk.xml |
| 29 |
hb-install-sparc-kernel.xml |
| 30 |
hb-install-sparc-medium.xml hb-install-stage.xml |
| 31 |
hb-install-system.xml hb-install-tools.xml |
| 32 |
hb-install-x86-bootloader.xml |
| 33 |
hb-install-x86-disk.xml hb-install-x86-kernel.xml |
| 34 |
hb-install-x86-medium.xml |
| 35 |
Log: |
| 36 |
Bunch of 2005.1 -> 2006.0 files, initial version. |
| 37 |
|
| 38 |
Revision Changes Path |
| 39 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/handbook-alpha.xml |
| 40 |
|
| 41 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-alpha.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 42 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-alpha.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 43 |
|
| 44 |
Index: handbook-alpha.xml |
| 45 |
=================================================================== |
| 46 |
<?xml version='1.0' encoding='UTF-8'?> |
| 47 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
| 48 |
|
| 49 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-alpha.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 50 |
|
| 51 |
<book link="handbook-alpha.xml"> |
| 52 |
<title>Gentoo Linux 2006.0 Alpha Handbook</title> |
| 53 |
|
| 54 |
<author title="Author"> |
| 55 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
| 56 |
</author> |
| 57 |
<author title="Author"> |
| 58 |
<mail link="uberlord@g.o">Roy Marples</mail> |
| 59 |
</author> |
| 60 |
<author title="Author"> |
| 61 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
| 62 |
</author> |
| 63 |
<author title="Author"> |
| 64 |
<mail link="chouser@g.o">Chris Houser</mail> |
| 65 |
</author> |
| 66 |
<author title="Author"> |
| 67 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
| 68 |
</author> |
| 69 |
<author title="Gentoo x86 Developer"> |
| 70 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
| 71 |
</author> |
| 72 |
<author title="Gentoo Alpha Developer"> |
| 73 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
| 74 |
</author><!-- Does not want to be listed on the rendered page |
| 75 |
<author title="Gentoo Developer"> |
| 76 |
Aron Griffis |
| 77 |
</author> |
| 78 |
--> |
| 79 |
<author title="Gentoo AMD64 Developer"> |
| 80 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
| 81 |
</author> |
| 82 |
<author title="Gentoo HPPA developer"> |
| 83 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
| 84 |
</author> |
| 85 |
<author title="Gentoo PPC developer"> |
| 86 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
| 87 |
</author> |
| 88 |
<author title="Gentoo SPARC developer"> |
| 89 |
<mail link="blademan@g.o">Joe Kallar</mail> |
| 90 |
</author> |
| 91 |
<author title="Editor"> |
| 92 |
<mail link="zhen@g.o">John P. Davis</mail> |
| 93 |
</author> |
| 94 |
<author title="Editor">Pierre-Henri Jondot</author> |
| 95 |
<author title="Editor"> |
| 96 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
| 97 |
</author> |
| 98 |
<author title="Editor"> |
| 99 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
| 100 |
</author> |
| 101 |
<author title="Editor"> |
| 102 |
<mail link="seo@g.o">Jungmin Seo</mail> |
| 103 |
</author> |
| 104 |
<author title="Editor"> |
| 105 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
| 106 |
</author> |
| 107 |
<author title="Editor"> |
| 108 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
| 109 |
</author> |
| 110 |
<author title="Editor"> |
| 111 |
<mail link="peitolm@g.o">Colin Morey</mail> |
| 112 |
</author> |
| 113 |
<author title="Editor"> |
| 114 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
| 115 |
</author> |
| 116 |
<author title="Editor"> |
| 117 |
<mail link="carl@g.o">Carl Anderson</mail> |
| 118 |
</author> |
| 119 |
<author title="Editor"> |
| 120 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
| 121 |
</author> |
| 122 |
<author title="Editor"> |
| 123 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
| 124 |
</author> |
| 125 |
<author title="Editor"> |
| 126 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
| 127 |
</author> |
| 128 |
<author title="Editor"> |
| 129 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
| 130 |
</author> |
| 131 |
<author title="Editor"> |
| 132 |
<mail link="erwin@g.o">Erwin</mail> |
| 133 |
</author> |
| 134 |
<author title="Editor"> |
| 135 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
| 136 |
</author> |
| 137 |
<author title="Editor"> |
| 138 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
| 139 |
</author> |
| 140 |
<author title="Editor"> |
| 141 |
<mail link="neysx@g.o">Xavier Neys</mail> |
| 142 |
</author> |
| 143 |
<author title="Reviewer"> |
| 144 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
| 145 |
</author> |
| 146 |
<author title="Reviewer"> |
| 147 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
| 148 |
</author> |
| 149 |
<author title="Reviewer"> |
| 150 |
<mail link="spyderous@g.o">Donnie Berkholz</mail> |
| 151 |
</author> |
| 152 |
<author title="Reviewer"> |
| 153 |
<mail link="antifa@g.o">Ken Nowack</mail> |
| 154 |
</author> |
| 155 |
<author title="Contributor"> |
| 156 |
<mail link="pylon@g.o">Lars Weiler</mail> |
| 157 |
</author> |
| 158 |
|
| 159 |
<abstract> |
| 160 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
| 161 |
This handbook contains the installation instructions for a networkless |
| 162 |
installation on Alpha systems and parts about working with Gentoo and Portage. |
| 163 |
</abstract> |
| 164 |
|
| 165 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 166 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 167 |
<license/> |
| 168 |
|
| 169 |
<version>5.2</version> |
| 170 |
<date>2005-10-13</date> |
| 171 |
|
| 172 |
<part> |
| 173 |
<title>Installing Gentoo</title> |
| 174 |
<abstract> |
| 175 |
In this part you learn how to install Gentoo on your system. |
| 176 |
</abstract> |
| 177 |
|
| 178 |
<chapter> |
| 179 |
<title>About the Gentoo Linux Installation</title> |
| 180 |
<abstract> |
| 181 |
Users not familiar with Gentoo do not always know that choice is what |
| 182 |
Gentoo is all about. |
| 183 |
</abstract> |
| 184 |
<include href="hb-install-about.xml"/> |
| 185 |
</chapter> |
| 186 |
|
| 187 |
<chapter> |
| 188 |
<title>Booting the Universal Installation CD</title> |
| 189 |
<abstract> |
| 190 |
Using our Universal Installation CD you can boot up your system into a running |
| 191 |
environment that allows you to install Gentoo. |
| 192 |
</abstract> |
| 193 |
<include href="hb-install-alpha-medium.xml"/> |
| 194 |
</chapter> |
| 195 |
|
| 196 |
<chapter> |
| 197 |
<title>Configuring your Network</title> |
| 198 |
<abstract> |
| 199 |
If you need networking, this is the place where the network (and Internet |
| 200 |
connection) is configured. |
| 201 |
</abstract> |
| 202 |
<include href="hb-install-network.xml"/> |
| 203 |
</chapter> |
| 204 |
|
| 205 |
<chapter> |
| 206 |
<title>Preparing the Disks</title> |
| 207 |
<abstract> |
| 208 |
To be able to install Gentoo, you must create the necessary partitions. |
| 209 |
This chapter describes how to partition a disk for future usage. |
| 210 |
</abstract> |
| 211 |
<include href="hb-install-alpha-disk.xml"/> |
| 212 |
</chapter> |
| 213 |
|
| 214 |
<chapter> |
| 215 |
<title>Installing the Gentoo Installation Files</title> |
| 216 |
<abstract> |
| 217 |
In this chapter we describe how you extract a stage3 file and how to configure |
| 218 |
Portage. |
| 219 |
</abstract> |
| 220 |
<include href="hb-install-stage.xml"/> |
| 221 |
</chapter> |
| 222 |
|
| 223 |
<chapter> |
| 224 |
<title>Chrooting into the Gentoo Base System</title> |
| 225 |
<abstract> |
| 226 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
| 227 |
the USE variable. |
| 228 |
</abstract> |
| 229 |
<include href="hb-install-system.xml"/> |
| 230 |
</chapter> |
| 231 |
|
| 232 |
<chapter> |
| 233 |
<title>Configuring the Kernel</title> |
| 234 |
<abstract> |
| 235 |
The Linux kernel is the core of every distribution. This chapter |
| 236 |
explains how to configure your kernel. |
| 237 |
</abstract> |
| 238 |
<include href="hb-install-alpha-kernel.xml"/> |
| 239 |
</chapter> |
| 240 |
|
| 241 |
<chapter> |
| 242 |
<title>Configuring your System</title> |
| 243 |
<abstract> |
| 244 |
You need to edit some important configuration files. In this chapter |
| 245 |
you receive an overview of these files and an explanation on how to |
| 246 |
proceed. |
| 247 |
</abstract> |
| 248 |
<include href="hb-install-config.xml"/> |
| 249 |
</chapter> |
| 250 |
|
| 251 |
<chapter> |
| 252 |
<title>Installing Necessary System Tools</title> |
| 253 |
<abstract> |
| 254 |
As mentioned before, Gentoo is about choices. In this chapter we help you |
| 255 |
choose and install some important tools. |
| 256 |
</abstract> |
| 257 |
<include href="hb-install-tools.xml"/> |
| 258 |
</chapter> |
| 259 |
|
| 260 |
<chapter> |
| 261 |
<title>Configuring the Bootloader</title> |
| 262 |
<abstract> |
| 263 |
Several bootloaders exist. Each one of them has its own way of |
| 264 |
configuration. In this chapter we'll describe all possibilities for you |
| 265 |
and step you through the process of configuring a bootloader to your |
| 266 |
needs. |
| 267 |
</abstract> |
| 268 |
<include href="hb-install-alpha-bootloader.xml"/> |
| 269 |
</chapter> |
| 270 |
|
| 271 |
<chapter> |
| 272 |
<title>Finalizing your Gentoo Installation</title> |
| 273 |
<abstract> |
| 274 |
You're almost done. We'll just create one (or more) users for your |
| 275 |
system and (optionally) install the prebuild packages. |
| 276 |
</abstract> |
| 277 |
<include href="hb-install-finalise.xml"/> |
| 278 |
</chapter> |
| 279 |
|
| 280 |
<chapter> |
| 281 |
<title>Where to go from here?</title> |
| 282 |
<abstract> |
| 283 |
Now you have your Gentoo system, but what's next? |
| 284 |
</abstract> |
| 285 |
<include href="hb-install-next.xml"/> |
| 286 |
</chapter> |
| 287 |
</part> |
| 288 |
|
| 289 |
<part> |
| 290 |
<title>Working with Gentoo</title> |
| 291 |
<abstract> |
| 292 |
Learn how to work with Gentoo: installing software, altering variables, changing |
| 293 |
Portage behaviour etc. |
| 294 |
</abstract> |
| 295 |
|
| 296 |
<chapter> |
| 297 |
<title>A Portage Introduction</title> |
| 298 |
<abstract> |
| 299 |
This chapter explains the "simple" steps a user definitely needs to know to |
| 300 |
maintain the software on his system. |
| 301 |
</abstract> |
| 302 |
<include href="../hb-working-portage.xml"/> |
| 303 |
</chapter> |
| 304 |
|
| 305 |
<chapter> |
| 306 |
<title>USE flags</title> |
| 307 |
<abstract> |
| 308 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
| 309 |
work with USE-flags and understand how USE-flags interact with your system. |
| 310 |
</abstract> |
| 311 |
<include href="../hb-working-use.xml"/> |
| 312 |
</chapter> |
| 313 |
|
| 314 |
<chapter> |
| 315 |
<title>Portage Features</title> |
| 316 |
<abstract> |
| 317 |
Discover the features Portage has, such as support for distributed compiling, |
| 318 |
ccache and more. |
| 319 |
</abstract> |
| 320 |
<include href="../hb-working-features.xml"/> |
| 321 |
</chapter> |
| 322 |
|
| 323 |
<chapter> |
| 324 |
<title>Initscripts</title> |
| 325 |
<abstract> |
| 326 |
Gentoo uses a special initscript format which, amongst other features, allows |
| 327 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
| 328 |
these aspects and explains how to deal with these scripts. |
| 329 |
</abstract> |
| 330 |
<include href="../hb-working-rcscripts.xml"/> |
| 331 |
</chapter> |
| 332 |
|
| 333 |
<chapter> |
| 334 |
<title>Environment Variables</title> |
| 335 |
<abstract> |
| 336 |
With Gentoo you can easily manage the environment variables for your system. |
| 337 |
This chapter explains how you do that, and also describes frequently used |
| 338 |
variables. |
| 339 |
</abstract> |
| 340 |
<include href="../hb-working-variables.xml"/> |
| 341 |
</chapter> |
| 342 |
</part> |
| 343 |
|
| 344 |
<part> |
| 345 |
<title>Working with Portage</title> |
| 346 |
<abstract> |
| 347 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
| 348 |
Software Management Tool. |
| 349 |
</abstract> |
| 350 |
|
| 351 |
<chapter> |
| 352 |
<title>Files and Directories</title> |
| 353 |
<abstract> |
| 354 |
Once you want to know Portage in-depth you need to know where it stores its |
| 355 |
files and data. |
| 356 |
</abstract> |
| 357 |
<include href="../hb-portage-files.xml"/> |
| 358 |
</chapter> |
| 359 |
|
| 360 |
<chapter> |
| 361 |
<title>Configuring through Variables</title> |
| 362 |
<abstract> |
| 363 |
Portage is completely configurable through various variables you can set in the |
| 364 |
configuration file or as environment variable. |
| 365 |
</abstract> |
| 366 |
<include href="../hb-portage-configuration.xml"/> |
| 367 |
</chapter> |
| 368 |
|
| 369 |
<chapter> |
| 370 |
<title>Mixing Software Branches</title> |
| 371 |
<abstract> |
| 372 |
Gentoo provides software separated in several branches, depending on stability |
| 373 |
and architectural support. "Mixing Software Branches" inform you how these |
| 374 |
branches can be configured and how you can override this separation |
| 375 |
individually. |
| 376 |
</abstract> |
| 377 |
<include href="../hb-portage-branches.xml"/> |
| 378 |
</chapter> |
| 379 |
|
| 380 |
<chapter> |
| 381 |
<title>Additional Portage Tools</title> |
| 382 |
<abstract> |
| 383 |
Portage comes with a few extra tools that might make your Gentoo experience even |
| 384 |
better. Read on to discover how to use dispatch-conf and other tools. |
| 385 |
</abstract> |
| 386 |
<include href="../hb-portage-tools.xml"/> |
| 387 |
</chapter> |
| 388 |
|
| 389 |
<chapter> |
| 390 |
<title>Diverting from the Official Tree</title> |
| 391 |
<abstract> |
| 392 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
| 393 |
your own Portage tree, how to synchronise only the categories you want, inject |
| 394 |
packages and more. |
| 395 |
</abstract> |
| 396 |
<include href="../hb-portage-diverttree.xml"/> |
| 397 |
</chapter> |
| 398 |
|
| 399 |
<chapter> |
| 400 |
<title>The Ebuild Application</title> |
| 401 |
<abstract> |
| 402 |
In "The Ebuild Application" you are informed about the steps Portage takes while |
| 403 |
installing software and how you can do this yourself using the ebuild |
| 404 |
application. |
| 405 |
</abstract> |
| 406 |
<include href="../hb-portage-ebuild.xml"/> |
| 407 |
</chapter> |
| 408 |
</part> |
| 409 |
|
| 410 |
<part> |
| 411 |
<title>Gentoo Network Configuration</title> |
| 412 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
| 413 |
|
| 414 |
<chapter> |
| 415 |
<title>Getting Started</title> |
| 416 |
<abstract> |
| 417 |
A guide to quickly get your network interface up and running in most common |
| 418 |
environments. |
| 419 |
</abstract> |
| 420 |
<include href="../hb-net-start.xml"/> |
| 421 |
</chapter> |
| 422 |
|
| 423 |
<chapter> |
| 424 |
<title>Advanced Configuration</title> |
| 425 |
<abstract> |
| 426 |
Here we learn about how the configuration works - you need to know this |
| 427 |
before we learn about modular networking. |
| 428 |
</abstract> |
| 429 |
<include href="../hb-net-advanced.xml"/> |
| 430 |
</chapter> |
| 431 |
|
| 432 |
<chapter> |
| 433 |
<title>Modular Networking</title> |
| 434 |
<abstract> |
| 435 |
Gentoo provides you flexible networking - here you are told about choosing |
| 436 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
| 437 |
</abstract> |
| 438 |
<include href="../hb-net-modules.xml"/> |
| 439 |
</chapter> |
| 440 |
|
| 441 |
<chapter> |
| 442 |
<title>Wireless Networking</title> |
| 443 |
<abstract> |
| 444 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
| 445 |
</abstract> |
| 446 |
<include href="../hb-net-wireless.xml"/> |
| 447 |
</chapter> |
| 448 |
|
| 449 |
<chapter> |
| 450 |
<title>Adding Functionality</title> |
| 451 |
<abstract> |
| 452 |
If you're feeling adventurous, you can add your own functions to networking. |
| 453 |
</abstract> |
| 454 |
<include href="../hb-net-functions.xml"/> |
| 455 |
</chapter> |
| 456 |
|
| 457 |
<chapter> |
| 458 |
<title>Network Management</title> |
| 459 |
<abstract> |
| 460 |
For laptop users or people who move their computer around different networks. |
| 461 |
</abstract> |
| 462 |
<include href="../hb-net-management.xml"/> |
| 463 |
</chapter> |
| 464 |
</part> |
| 465 |
|
| 466 |
</book> |
| 467 |
|
| 468 |
|
| 469 |
|
| 470 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/handbook-amd64.xml |
| 471 |
|
| 472 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-amd64.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 473 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-amd64.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 474 |
|
| 475 |
Index: handbook-amd64.xml |
| 476 |
=================================================================== |
| 477 |
<?xml version='1.0' encoding='UTF-8'?> |
| 478 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
| 479 |
|
| 480 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-amd64.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 481 |
|
| 482 |
<book link="handbook-amd64.xml"> |
| 483 |
<title>Gentoo Linux 2006.0 AMD64 Handbook</title> |
| 484 |
|
| 485 |
<author title="Author"> |
| 486 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
| 487 |
</author> |
| 488 |
<author title="Author"> |
| 489 |
<mail link="uberlord@g.o">Roy Marples</mail> |
| 490 |
</author> |
| 491 |
<author title="Author"> |
| 492 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
| 493 |
</author> |
| 494 |
<author title="Author"> |
| 495 |
<mail link="chouser@g.o">Chris Houser</mail> |
| 496 |
</author> |
| 497 |
<author title="Author"> |
| 498 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
| 499 |
</author> |
| 500 |
<author title="Gentoo x86 Developer"> |
| 501 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
| 502 |
</author> |
| 503 |
<author title="Gentoo Alpha Developer"> |
| 504 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
| 505 |
</author><!-- Does not want to be listed on the rendered page |
| 506 |
<author title="Gentoo Developer"> |
| 507 |
Aron Griffis |
| 508 |
</author> |
| 509 |
--> |
| 510 |
<author title="Gentoo AMD64 Developer"> |
| 511 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
| 512 |
</author> |
| 513 |
<author title="Gentoo HPPA developer"> |
| 514 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
| 515 |
</author> |
| 516 |
<author title="Gentoo PPC developer"> |
| 517 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
| 518 |
</author> |
| 519 |
<author title="Gentoo SPARC developer"> |
| 520 |
<mail link="blademan@g.o">Joe Kallar</mail> |
| 521 |
</author> |
| 522 |
<author title="Editor"> |
| 523 |
<mail link="zhen@g.o">John P. Davis</mail> |
| 524 |
</author> |
| 525 |
<author title="Editor">Pierre-Henri Jondot</author> |
| 526 |
<author title="Editor"> |
| 527 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
| 528 |
</author> |
| 529 |
<author title="Editor"> |
| 530 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
| 531 |
</author> |
| 532 |
<author title="Editor"> |
| 533 |
<mail link="seo@g.o">Jungmin Seo</mail> |
| 534 |
</author> |
| 535 |
<author title="Editor"> |
| 536 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
| 537 |
</author> |
| 538 |
<author title="Editor"> |
| 539 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
| 540 |
</author> |
| 541 |
<author title="Editor"> |
| 542 |
<mail link="peitolm@g.o">Colin Morey</mail> |
| 543 |
</author> |
| 544 |
<author title="Editor"> |
| 545 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
| 546 |
</author> |
| 547 |
<author title="Editor"> |
| 548 |
<mail link="carl@g.o">Carl Anderson</mail> |
| 549 |
</author> |
| 550 |
<author title="Editor"> |
| 551 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
| 552 |
</author> |
| 553 |
<author title="Editor"> |
| 554 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
| 555 |
</author> |
| 556 |
<author title="Editor"> |
| 557 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
| 558 |
</author> |
| 559 |
<author title="Editor"> |
| 560 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
| 561 |
</author> |
| 562 |
<author title="Editor"> |
| 563 |
<mail link="erwin@g.o">Erwin</mail> |
| 564 |
</author> |
| 565 |
<author title="Editor"> |
| 566 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
| 567 |
</author> |
| 568 |
<author title="Editor"> |
| 569 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
| 570 |
</author> |
| 571 |
<author title="Editor"> |
| 572 |
<mail link="neysx@g.o">Xavier Neys</mail> |
| 573 |
</author> |
| 574 |
<author title="Reviewer"> |
| 575 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
| 576 |
</author> |
| 577 |
<author title="Reviewer"> |
| 578 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
| 579 |
</author> |
| 580 |
<author title="Reviewer"> |
| 581 |
<mail link="spyderous@g.o">Donnie Berkholz</mail> |
| 582 |
</author> |
| 583 |
<author title="Reviewer"> |
| 584 |
<mail link="antifa@g.o">Ken Nowack</mail> |
| 585 |
</author> |
| 586 |
<author title="Contributor"> |
| 587 |
<mail link="pylon@g.o">Lars Weiler</mail> |
| 588 |
</author> |
| 589 |
|
| 590 |
<abstract> |
| 591 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
| 592 |
This handbook contains the installation instructions for a networkless |
| 593 |
installation on AMD64 systems and parts about working with Gentoo and Portage. |
| 594 |
</abstract> |
| 595 |
|
| 596 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 597 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 598 |
<license/> |
| 599 |
|
| 600 |
<version>5.2</version> |
| 601 |
<date>2005-10-13</date> |
| 602 |
|
| 603 |
<part> |
| 604 |
<title>Installing Gentoo</title> |
| 605 |
<abstract> |
| 606 |
In this part you learn how to install Gentoo on your system. |
| 607 |
</abstract> |
| 608 |
|
| 609 |
<chapter> |
| 610 |
<title>About the Gentoo Linux Installation</title> |
| 611 |
<abstract> |
| 612 |
Users not familiar with Gentoo do not always know that choice is what |
| 613 |
Gentoo is all about. |
| 614 |
</abstract> |
| 615 |
<include href="hb-install-about.xml"/> |
| 616 |
</chapter> |
| 617 |
|
| 618 |
<chapter> |
| 619 |
<title>Booting the Universal Installation CD</title> |
| 620 |
<abstract> |
| 621 |
Using our Universal Installation CD you can boot up your system into a running |
| 622 |
environment that allows you to install Gentoo. |
| 623 |
</abstract> |
| 624 |
<include href="hb-install-amd64-medium.xml"/> |
| 625 |
</chapter> |
| 626 |
|
| 627 |
<chapter> |
| 628 |
<title>Configuring your Network</title> |
| 629 |
<abstract> |
| 630 |
If you need networking, this is the place where the network (and Internet |
| 631 |
connection) is configured. |
| 632 |
</abstract> |
| 633 |
<include href="hb-install-network.xml"/> |
| 634 |
</chapter> |
| 635 |
|
| 636 |
<chapter> |
| 637 |
<title>Preparing the Disks</title> |
| 638 |
<abstract> |
| 639 |
To be able to install Gentoo, you must create the necessary partitions. |
| 640 |
This chapter describes how to partition a disk for future usage. |
| 641 |
</abstract> |
| 642 |
<include href="hb-install-amd64-disk.xml"/> |
| 643 |
</chapter> |
| 644 |
|
| 645 |
<chapter> |
| 646 |
<title>Installing the Gentoo Installation Files</title> |
| 647 |
<abstract> |
| 648 |
In this chapter we describe how you extract a stage3 file and how to configure |
| 649 |
Portage. |
| 650 |
</abstract> |
| 651 |
<include href="hb-install-stage.xml"/> |
| 652 |
</chapter> |
| 653 |
|
| 654 |
<chapter> |
| 655 |
<title>Chrooting into the Gentoo Base System</title> |
| 656 |
<abstract> |
| 657 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
| 658 |
the USE variable. |
| 659 |
</abstract> |
| 660 |
<include href="hb-install-system.xml"/> |
| 661 |
</chapter> |
| 662 |
|
| 663 |
<chapter> |
| 664 |
<title>Configuring the Kernel</title> |
| 665 |
<abstract> |
| 666 |
The Linux kernel is the core of every distribution. This chapter |
| 667 |
explains how to configure your kernel. |
| 668 |
</abstract> |
| 669 |
<include href="hb-install-amd64-kernel.xml"/> |
| 670 |
</chapter> |
| 671 |
|
| 672 |
<chapter> |
| 673 |
<title>Configuring your System</title> |
| 674 |
<abstract> |
| 675 |
You need to edit some important configuration files. In this chapter |
| 676 |
you receive an overview of these files and an explanation on how to |
| 677 |
proceed. |
| 678 |
</abstract> |
| 679 |
<include href="hb-install-config.xml"/> |
| 680 |
</chapter> |
| 681 |
|
| 682 |
<chapter> |
| 683 |
<title>Installing Necessary System Tools</title> |
| 684 |
<abstract> |
| 685 |
As mentioned before, Gentoo is about choices. In this chapter we help you |
| 686 |
choose and install some important tools. |
| 687 |
</abstract> |
| 688 |
<include href="hb-install-tools.xml"/> |
| 689 |
</chapter> |
| 690 |
|
| 691 |
<chapter> |
| 692 |
<title>Configuring the Bootloader</title> |
| 693 |
<abstract> |
| 694 |
In this chapter we'll describe the GRUB bootloader |
| 695 |
and step you through the process of configuring GRUB to your |
| 696 |
needs. |
| 697 |
</abstract> |
| 698 |
<include href="hb-install-amd64-bootloader.xml"/> |
| 699 |
</chapter> |
| 700 |
|
| 701 |
<chapter> |
| 702 |
<title>Finalizing your Gentoo Installation</title> |
| 703 |
<abstract> |
| 704 |
You're almost done. We'll just create one (or more) users for your |
| 705 |
system and (optionally) install the prebuild packages. |
| 706 |
</abstract> |
| 707 |
<include href="hb-install-finalise.xml"/> |
| 708 |
</chapter> |
| 709 |
|
| 710 |
<chapter> |
| 711 |
<title>Where to go from here?</title> |
| 712 |
<abstract> |
| 713 |
Now you have your Gentoo system, but what's next? |
| 714 |
</abstract> |
| 715 |
<include href="hb-install-next.xml"/> |
| 716 |
</chapter> |
| 717 |
</part> |
| 718 |
|
| 719 |
<part> |
| 720 |
<title>Working with Gentoo</title> |
| 721 |
<abstract> |
| 722 |
Learn how to work with Gentoo: installing software, altering variables, changing |
| 723 |
Portage behaviour etc. |
| 724 |
</abstract> |
| 725 |
|
| 726 |
<chapter> |
| 727 |
<title>A Portage Introduction</title> |
| 728 |
<abstract> |
| 729 |
This chapter explains the "simple" steps a user definitely needs to know to |
| 730 |
maintain the software on his system. |
| 731 |
</abstract> |
| 732 |
<include href="../hb-working-portage.xml"/> |
| 733 |
</chapter> |
| 734 |
|
| 735 |
<chapter> |
| 736 |
<title>USE flags</title> |
| 737 |
<abstract> |
| 738 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
| 739 |
work with USE-flags and understand how USE-flags interact with your system. |
| 740 |
</abstract> |
| 741 |
<include href="../hb-working-use.xml"/> |
| 742 |
</chapter> |
| 743 |
|
| 744 |
<chapter> |
| 745 |
<title>Portage Features</title> |
| 746 |
<abstract> |
| 747 |
Discover the features Portage has, such as support for distributed compiling, |
| 748 |
ccache and more. |
| 749 |
</abstract> |
| 750 |
<include href="../hb-working-features.xml"/> |
| 751 |
</chapter> |
| 752 |
|
| 753 |
<chapter> |
| 754 |
<title>Initscripts</title> |
| 755 |
<abstract> |
| 756 |
Gentoo uses a special initscript format which, amongst other features, allows |
| 757 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
| 758 |
these aspects and explains how to deal with these scripts. |
| 759 |
</abstract> |
| 760 |
<include href="../hb-working-rcscripts.xml"/> |
| 761 |
</chapter> |
| 762 |
|
| 763 |
<chapter> |
| 764 |
<title>Environment Variables</title> |
| 765 |
<abstract> |
| 766 |
With Gentoo you can easily manage the environment variables for your system. |
| 767 |
This chapter explains how you do that, and also describes frequently used |
| 768 |
variables. |
| 769 |
</abstract> |
| 770 |
<include href="../hb-working-variables.xml"/> |
| 771 |
</chapter> |
| 772 |
</part> |
| 773 |
|
| 774 |
<part> |
| 775 |
<title>Working with Portage</title> |
| 776 |
<abstract> |
| 777 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
| 778 |
Software Management Tool. |
| 779 |
</abstract> |
| 780 |
|
| 781 |
<chapter> |
| 782 |
<title>Files and Directories</title> |
| 783 |
<abstract> |
| 784 |
Once you want to know Portage in-depth you need to know where it stores its |
| 785 |
files and data. |
| 786 |
</abstract> |
| 787 |
<include href="../hb-portage-files.xml"/> |
| 788 |
</chapter> |
| 789 |
|
| 790 |
<chapter> |
| 791 |
<title>Configuring through Variables</title> |
| 792 |
<abstract> |
| 793 |
Portage is completely configurable through various variables you can set in the |
| 794 |
configuration file or as environment variable. |
| 795 |
</abstract> |
| 796 |
<include href="../hb-portage-configuration.xml"/> |
| 797 |
</chapter> |
| 798 |
|
| 799 |
<chapter> |
| 800 |
<title>Mixing Software Branches</title> |
| 801 |
<abstract> |
| 802 |
Gentoo provides software separated in several branches, depending on stability |
| 803 |
and architectural support. "Mixing Software Branches" inform you how these |
| 804 |
branches can be configured and how you can override this separation |
| 805 |
individually. |
| 806 |
</abstract> |
| 807 |
<include href="../hb-portage-branches.xml"/> |
| 808 |
</chapter> |
| 809 |
|
| 810 |
<chapter> |
| 811 |
<title>Additional Portage Tools</title> |
| 812 |
<abstract> |
| 813 |
Portage comes with a few extra tools that might make your Gentoo experience even |
| 814 |
better. Read on to discover how to use dispatch-conf and other tools. |
| 815 |
</abstract> |
| 816 |
<include href="../hb-portage-tools.xml"/> |
| 817 |
</chapter> |
| 818 |
|
| 819 |
<chapter> |
| 820 |
<title>Diverting from the Official Tree</title> |
| 821 |
<abstract> |
| 822 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
| 823 |
your own Portage tree, how to synchronise only the categories you want, inject |
| 824 |
packages and more. |
| 825 |
</abstract> |
| 826 |
<include href="../hb-portage-diverttree.xml"/> |
| 827 |
</chapter> |
| 828 |
|
| 829 |
<chapter> |
| 830 |
<title>The Ebuild Application</title> |
| 831 |
<abstract> |
| 832 |
In "The Ebuild Application" you are informed about the steps Portage takes while |
| 833 |
installing software and how you can do this yourself using the ebuild |
| 834 |
application. |
| 835 |
</abstract> |
| 836 |
<include href="../hb-portage-ebuild.xml"/> |
| 837 |
</chapter> |
| 838 |
</part> |
| 839 |
|
| 840 |
<part> |
| 841 |
<title>Gentoo Network Configuration</title> |
| 842 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
| 843 |
|
| 844 |
<chapter> |
| 845 |
<title>Getting Started</title> |
| 846 |
<abstract> |
| 847 |
A guide to quickly get your network interface up and running in most common |
| 848 |
environments. |
| 849 |
</abstract> |
| 850 |
<include href="../hb-net-start.xml"/> |
| 851 |
</chapter> |
| 852 |
|
| 853 |
<chapter> |
| 854 |
<title>Advanced Configuration</title> |
| 855 |
<abstract> |
| 856 |
Here we learn about how the configuration works - you need to know this |
| 857 |
before we learn about modular networking. |
| 858 |
</abstract> |
| 859 |
<include href="../hb-net-advanced.xml"/> |
| 860 |
</chapter> |
| 861 |
|
| 862 |
<chapter> |
| 863 |
<title>Modular Networking</title> |
| 864 |
<abstract> |
| 865 |
Gentoo provides you flexible networking - here you are told about choosing |
| 866 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
| 867 |
</abstract> |
| 868 |
<include href="../hb-net-modules.xml"/> |
| 869 |
</chapter> |
| 870 |
|
| 871 |
<chapter> |
| 872 |
<title>Wireless Networking</title> |
| 873 |
<abstract> |
| 874 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
| 875 |
</abstract> |
| 876 |
<include href="../hb-net-wireless.xml"/> |
| 877 |
</chapter> |
| 878 |
|
| 879 |
<chapter> |
| 880 |
<title>Adding Functionality</title> |
| 881 |
<abstract> |
| 882 |
If you're feeling adventurous, you can add your own functions to networking. |
| 883 |
</abstract> |
| 884 |
<include href="../hb-net-functions.xml"/> |
| 885 |
</chapter> |
| 886 |
|
| 887 |
<chapter> |
| 888 |
<title>Network Management</title> |
| 889 |
<abstract> |
| 890 |
For laptop users or people who move their computer around different networks. |
| 891 |
</abstract> |
| 892 |
<include href="../hb-net-management.xml"/> |
| 893 |
</chapter> |
| 894 |
</part> |
| 895 |
|
| 896 |
</book> |
| 897 |
|
| 898 |
|
| 899 |
|
| 900 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/handbook-hppa.xml |
| 901 |
|
| 902 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-hppa.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 903 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-hppa.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 904 |
|
| 905 |
Index: handbook-hppa.xml |
| 906 |
=================================================================== |
| 907 |
<?xml version='1.0' encoding='UTF-8'?> |
| 908 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
| 909 |
|
| 910 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-hppa.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 911 |
|
| 912 |
<book link="handbook-hppa.xml"> |
| 913 |
<title>Gentoo Linux 2006.0 HPPA Handbook</title> |
| 914 |
|
| 915 |
<author title="Author"> |
| 916 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
| 917 |
</author> |
| 918 |
<author title="Author"> |
| 919 |
<mail link="uberlord@g.o">Roy Marples</mail> |
| 920 |
</author> |
| 921 |
<author title="Author"> |
| 922 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
| 923 |
</author> |
| 924 |
<author title="Author"> |
| 925 |
<mail link="chouser@g.o">Chris Houser</mail> |
| 926 |
</author> |
| 927 |
<author title="Author"> |
| 928 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
| 929 |
</author> |
| 930 |
<author title="Gentoo x86 Developer"> |
| 931 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
| 932 |
</author> |
| 933 |
<author title="Gentoo Alpha Developer"> |
| 934 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
| 935 |
</author><!-- Does not want to be listed on the rendered page |
| 936 |
<author title="Gentoo Developer"> |
| 937 |
Aron Griffis |
| 938 |
</author> |
| 939 |
--> |
| 940 |
<author title="Gentoo AMD64 Developer"> |
| 941 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
| 942 |
</author> |
| 943 |
<author title="Gentoo HPPA developer"> |
| 944 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
| 945 |
</author> |
| 946 |
<author title="Gentoo PPC developer"> |
| 947 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
| 948 |
</author> |
| 949 |
<author title="Gentoo SPARC developer"> |
| 950 |
<mail link="blademan@g.o">Joe Kallar</mail> |
| 951 |
</author> |
| 952 |
<author title="Editor"> |
| 953 |
<mail link="zhen@g.o">John P. Davis</mail> |
| 954 |
</author> |
| 955 |
<author title="Editor">Pierre-Henri Jondot</author> |
| 956 |
<author title="Editor"> |
| 957 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
| 958 |
</author> |
| 959 |
<author title="Editor"> |
| 960 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
| 961 |
</author> |
| 962 |
<author title="Editor"> |
| 963 |
<mail link="seo@g.o">Jungmin Seo</mail> |
| 964 |
</author> |
| 965 |
<author title="Editor"> |
| 966 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
| 967 |
</author> |
| 968 |
<author title="Editor"> |
| 969 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
| 970 |
</author> |
| 971 |
<author title="Editor"> |
| 972 |
<mail link="peitolm@g.o">Colin Morey</mail> |
| 973 |
</author> |
| 974 |
<author title="Editor"> |
| 975 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
| 976 |
</author> |
| 977 |
<author title="Editor"> |
| 978 |
<mail link="carl@g.o">Carl Anderson</mail> |
| 979 |
</author> |
| 980 |
<author title="Editor"> |
| 981 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
| 982 |
</author> |
| 983 |
<author title="Editor"> |
| 984 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
| 985 |
</author> |
| 986 |
<author title="Editor"> |
| 987 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
| 988 |
</author> |
| 989 |
<author title="Editor"> |
| 990 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
| 991 |
</author> |
| 992 |
<author title="Editor"> |
| 993 |
<mail link="erwin@g.o">Erwin</mail> |
| 994 |
</author> |
| 995 |
<author title="Editor"> |
| 996 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
| 997 |
</author> |
| 998 |
<author title="Editor"> |
| 999 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
| 1000 |
</author> |
| 1001 |
<author title="Editor"> |
| 1002 |
<mail link="neysx@g.o">Xavier Neys</mail> |
| 1003 |
</author> |
| 1004 |
<author title="Reviewer"> |
| 1005 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
| 1006 |
</author> |
| 1007 |
<author title="Reviewer"> |
| 1008 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
| 1009 |
</author> |
| 1010 |
<author title="Reviewer"> |
| 1011 |
<mail link="spyderous@g.o">Donnie Berkholz</mail> |
| 1012 |
</author> |
| 1013 |
<author title="Reviewer"> |
| 1014 |
<mail link="antifa@g.o">Ken Nowack</mail> |
| 1015 |
</author> |
| 1016 |
<author title="Contributor"> |
| 1017 |
<mail link="pylon@g.o">Lars Weiler</mail> |
| 1018 |
</author> |
| 1019 |
|
| 1020 |
<abstract> |
| 1021 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
| 1022 |
This handbook contains the installation instructions for a networkless |
| 1023 |
installation on HPPA systems and parts about working with Gentoo and Portage. |
| 1024 |
</abstract> |
| 1025 |
|
| 1026 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 1027 |
<!-- See http://creativecommons.org/licenses/by-sa/2.0 --> |
| 1028 |
<license/> |
| 1029 |
|
| 1030 |
<version>5.2</version> |
| 1031 |
<date>2005-10-13</date> |
| 1032 |
|
| 1033 |
<part> |
| 1034 |
<title>Installing Gentoo</title> |
| 1035 |
<abstract> |
| 1036 |
In this part you learn how to install Gentoo on your system. |
| 1037 |
</abstract> |
| 1038 |
|
| 1039 |
<chapter> |
| 1040 |
<title>About the Gentoo Linux Installation</title> |
| 1041 |
<abstract> |
| 1042 |
Users not familiar with Gentoo do not always know that choice is what |
| 1043 |
Gentoo is all about. |
| 1044 |
</abstract> |
| 1045 |
<include href="hb-install-about.xml"/> |
| 1046 |
</chapter> |
| 1047 |
|
| 1048 |
<chapter> |
| 1049 |
<title>Booting the Universal Installation CD</title> |
| 1050 |
<abstract> |
| 1051 |
Using our Universal Installation CD you can boot up your system into a running |
| 1052 |
environment that allows you to install Gentoo. |
| 1053 |
</abstract> |
| 1054 |
<include href="hb-install-hppa-medium.xml"/> |
| 1055 |
</chapter> |
| 1056 |
|
| 1057 |
<chapter> |
| 1058 |
<title>Configuring your Network</title> |
| 1059 |
<abstract> |
| 1060 |
If you need networking, this is the place where the network (and Internet |
| 1061 |
connection) is configured. |
| 1062 |
</abstract> |
| 1063 |
<include href="hb-install-network.xml"/> |
| 1064 |
</chapter> |
| 1065 |
|
| 1066 |
<chapter> |
| 1067 |
<title>Preparing the Disks</title> |
| 1068 |
<abstract> |
| 1069 |
To be able to install Gentoo, you must create the necessary partitions. |
| 1070 |
This chapter describes how to partition a disk for future usage. |
| 1071 |
</abstract> |
| 1072 |
<include href="hb-install-hppa-disk.xml"/> |
| 1073 |
</chapter> |
| 1074 |
|
| 1075 |
<chapter> |
| 1076 |
<title>Installing the Gentoo Installation Files</title> |
| 1077 |
<abstract> |
| 1078 |
Gentoo installs work through so-called stage-files. In this chapter we |
| 1079 |
describe how you extract a stage-file and configure Portage. |
| 1080 |
</abstract> |
| 1081 |
<include href="hb-install-stage.xml"/> |
| 1082 |
</chapter> |
| 1083 |
|
| 1084 |
<chapter> |
| 1085 |
<title>Chrooting into the Gentoo Base System</title> |
| 1086 |
<abstract> |
| 1087 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
| 1088 |
the USE variable. |
| 1089 |
</abstract> |
| 1090 |
<include href="hb-install-system.xml"/> |
| 1091 |
</chapter> |
| 1092 |
|
| 1093 |
<chapter> |
| 1094 |
<title>Configuring the Kernel</title> |
| 1095 |
<abstract> |
| 1096 |
The Linux kernel is the core of every distribution. This chapter |
| 1097 |
explains how to configure your kernel. |
| 1098 |
</abstract> |
| 1099 |
<include href="hb-install-hppa-kernel.xml"/> |
| 1100 |
</chapter> |
| 1101 |
|
| 1102 |
<chapter> |
| 1103 |
<title>Configuring your System</title> |
| 1104 |
<abstract> |
| 1105 |
You need to edit some important configuration files. In this chapter |
| 1106 |
you receive an overview of these files and an explanation on how to |
| 1107 |
proceed. |
| 1108 |
</abstract> |
| 1109 |
<include href="hb-install-config.xml"/> |
| 1110 |
</chapter> |
| 1111 |
|
| 1112 |
<chapter> |
| 1113 |
<title>Installing Necessary System Tools</title> |
| 1114 |
<abstract> |
| 1115 |
As mentioned before, Gentoo is about choices. In this chapter we help you |
| 1116 |
choose and install some important tools. |
| 1117 |
</abstract> |
| 1118 |
<include href="hb-install-tools.xml"/> |
| 1119 |
</chapter> |
| 1120 |
|
| 1121 |
<chapter> |
| 1122 |
<title>Configuring the Bootloader</title> |
| 1123 |
<abstract> |
| 1124 |
In this chapter we'll describe the PALO bootloader |
| 1125 |
and step you through the process of configuring PALO to your |
| 1126 |
needs. |
| 1127 |
</abstract> |
| 1128 |
<include href="hb-install-hppa-bootloader.xml"/> |
| 1129 |
</chapter> |
| 1130 |
|
| 1131 |
<chapter> |
| 1132 |
<title>Finalizing your Gentoo Installation</title> |
| 1133 |
<abstract> |
| 1134 |
You're almost done. We'll just create one (or more) users for your |
| 1135 |
system and (optionally) install prebuilt packages. |
| 1136 |
</abstract> |
| 1137 |
<include href="hb-install-finalise.xml"/> |
| 1138 |
</chapter> |
| 1139 |
|
| 1140 |
<chapter> |
| 1141 |
<title>Where to go from here?</title> |
| 1142 |
<abstract> |
| 1143 |
Now you have your Gentoo system, but what's next? |
| 1144 |
</abstract> |
| 1145 |
<include href="hb-install-next.xml"/> |
| 1146 |
</chapter> |
| 1147 |
</part> |
| 1148 |
|
| 1149 |
<part> |
| 1150 |
<title>Working with Gentoo</title> |
| 1151 |
<abstract> |
| 1152 |
Learn how to work with Gentoo: installing software, altering variables, changing |
| 1153 |
Portage behaviour etc. |
| 1154 |
</abstract> |
| 1155 |
|
| 1156 |
<chapter> |
| 1157 |
<title>A Portage Introduction</title> |
| 1158 |
<abstract> |
| 1159 |
This chapter explains the "simple" steps a user definitely needs to know to |
| 1160 |
maintain the software on his system. |
| 1161 |
</abstract> |
| 1162 |
<include href="../hb-working-portage.xml"/> |
| 1163 |
</chapter> |
| 1164 |
|
| 1165 |
<chapter> |
| 1166 |
<title>USE flags</title> |
| 1167 |
<abstract> |
| 1168 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
| 1169 |
work with USE-flags and understand how USE-flags interact with your system. |
| 1170 |
</abstract> |
| 1171 |
<include href="../hb-working-use.xml"/> |
| 1172 |
</chapter> |
| 1173 |
|
| 1174 |
<chapter> |
| 1175 |
<title>Portage Features</title> |
| 1176 |
<abstract> |
| 1177 |
Discover the features Portage has, such as support for distributed compiling, |
| 1178 |
ccache and more. |
| 1179 |
</abstract> |
| 1180 |
<include href="../hb-working-features.xml"/> |
| 1181 |
</chapter> |
| 1182 |
|
| 1183 |
<chapter> |
| 1184 |
<title>Initscripts</title> |
| 1185 |
<abstract> |
| 1186 |
Gentoo uses a special initscript format which, amongst other features, allows |
| 1187 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
| 1188 |
these aspects and explains how to deal with these scripts. |
| 1189 |
</abstract> |
| 1190 |
<include href="../hb-working-rcscripts.xml"/> |
| 1191 |
</chapter> |
| 1192 |
|
| 1193 |
<chapter> |
| 1194 |
<title>Environment Variables</title> |
| 1195 |
<abstract> |
| 1196 |
With Gentoo you can easily manage the environment variables for your system. |
| 1197 |
This chapter explains how you do that, and also describes frequently used |
| 1198 |
variables. |
| 1199 |
</abstract> |
| 1200 |
<include href="../hb-working-variables.xml"/> |
| 1201 |
</chapter> |
| 1202 |
</part> |
| 1203 |
|
| 1204 |
<part> |
| 1205 |
<title>Working with Portage</title> |
| 1206 |
<abstract> |
| 1207 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
| 1208 |
Software Management Tool. |
| 1209 |
</abstract> |
| 1210 |
|
| 1211 |
<chapter> |
| 1212 |
<title>Files and Directories</title> |
| 1213 |
<abstract> |
| 1214 |
Once you want to know Portage in-depth you need to know where it stores its |
| 1215 |
files and data. |
| 1216 |
</abstract> |
| 1217 |
<include href="../hb-portage-files.xml"/> |
| 1218 |
</chapter> |
| 1219 |
|
| 1220 |
<chapter> |
| 1221 |
<title>Configuring through Variables</title> |
| 1222 |
<abstract> |
| 1223 |
Portage is completely configurable through various variables you can set in the |
| 1224 |
configuration file or as environment variable. |
| 1225 |
</abstract> |
| 1226 |
<include href="../hb-portage-configuration.xml"/> |
| 1227 |
</chapter> |
| 1228 |
|
| 1229 |
<chapter> |
| 1230 |
<title>Mixing Software Branches</title> |
| 1231 |
<abstract> |
| 1232 |
Gentoo provides software separated in several branches, depending on stability |
| 1233 |
and architectural support. "Mixing Software Branches" inform you how these |
| 1234 |
branches can be configured and how you can override this separation |
| 1235 |
individually. |
| 1236 |
</abstract> |
| 1237 |
<include href="../hb-portage-branches.xml"/> |
| 1238 |
</chapter> |
| 1239 |
|
| 1240 |
<chapter> |
| 1241 |
<title>Additional Portage Tools</title> |
| 1242 |
<abstract> |
| 1243 |
Portage comes with a few extra tools that might make your Gentoo experience even |
| 1244 |
better. Read on to discover how to use dispatch-conf and other tools. |
| 1245 |
</abstract> |
| 1246 |
<include href="../hb-portage-tools.xml"/> |
| 1247 |
</chapter> |
| 1248 |
|
| 1249 |
<chapter> |
| 1250 |
<title>Diverting from the Official Tree</title> |
| 1251 |
<abstract> |
| 1252 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
| 1253 |
your own Portage tree, how to synchronise only the categories you want, inject |
| 1254 |
packages and more. |
| 1255 |
</abstract> |
| 1256 |
<include href="../hb-portage-diverttree.xml"/> |
| 1257 |
</chapter> |
| 1258 |
|
| 1259 |
<chapter> |
| 1260 |
<title>The Ebuild Application</title> |
| 1261 |
<abstract> |
| 1262 |
In "The Ebuild Application" you are informed about the steps Portage takes while |
| 1263 |
installing software and how you can do this yourself using the ebuild |
| 1264 |
application. |
| 1265 |
</abstract> |
| 1266 |
<include href="../hb-portage-ebuild.xml"/> |
| 1267 |
</chapter> |
| 1268 |
</part> |
| 1269 |
|
| 1270 |
<part> |
| 1271 |
<title>Gentoo Network Configuration</title> |
| 1272 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
| 1273 |
|
| 1274 |
<chapter> |
| 1275 |
<title>Getting Started</title> |
| 1276 |
<abstract> |
| 1277 |
A guide to quickly get your network interface up and running in most common |
| 1278 |
environments. |
| 1279 |
</abstract> |
| 1280 |
<include href="../hb-net-start.xml"/> |
| 1281 |
</chapter> |
| 1282 |
|
| 1283 |
<chapter> |
| 1284 |
<title>Advanced Configuration</title> |
| 1285 |
<abstract> |
| 1286 |
Here we learn about how the configuration works - you need to know this |
| 1287 |
before we learn about modular networking. |
| 1288 |
</abstract> |
| 1289 |
<include href="../hb-net-advanced.xml"/> |
| 1290 |
</chapter> |
| 1291 |
|
| 1292 |
<chapter> |
| 1293 |
<title>Modular Networking</title> |
| 1294 |
<abstract> |
| 1295 |
Gentoo provides you flexible networking - here you are told about choosing |
| 1296 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
| 1297 |
</abstract> |
| 1298 |
<include href="../hb-net-modules.xml"/> |
| 1299 |
</chapter> |
| 1300 |
|
| 1301 |
<chapter> |
| 1302 |
<title>Wireless Networking</title> |
| 1303 |
<abstract> |
| 1304 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
| 1305 |
</abstract> |
| 1306 |
<include href="../hb-net-wireless.xml"/> |
| 1307 |
</chapter> |
| 1308 |
|
| 1309 |
<chapter> |
| 1310 |
<title>Adding Functionality</title> |
| 1311 |
<abstract> |
| 1312 |
If you're feeling adventurous, you can add your own functions to networking. |
| 1313 |
</abstract> |
| 1314 |
<include href="../hb-net-functions.xml"/> |
| 1315 |
</chapter> |
| 1316 |
|
| 1317 |
<chapter> |
| 1318 |
<title>Network Management</title> |
| 1319 |
<abstract> |
| 1320 |
For laptop users or people who move their computer around different networks. |
| 1321 |
</abstract> |
| 1322 |
<include href="../hb-net-management.xml"/> |
| 1323 |
</chapter> |
| 1324 |
</part> |
| 1325 |
|
| 1326 |
</book> |
| 1327 |
|
| 1328 |
|
| 1329 |
|
| 1330 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/handbook-ppc.xml |
| 1331 |
|
| 1332 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-ppc.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 1333 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-ppc.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 1334 |
|
| 1335 |
Index: handbook-ppc.xml |
| 1336 |
=================================================================== |
| 1337 |
<?xml version='1.0' encoding='UTF-8'?> |
| 1338 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
| 1339 |
|
| 1340 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-ppc.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 1341 |
|
| 1342 |
<book link="handbook-ppc.xml"> |
| 1343 |
<title>Gentoo Linux 2006.0 PPC Handbook</title> |
| 1344 |
|
| 1345 |
<author title="Author"> |
| 1346 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
| 1347 |
</author> |
| 1348 |
<author title="Author"> |
| 1349 |
<mail link="uberlord@g.o">Roy Marples</mail> |
| 1350 |
</author> |
| 1351 |
<author title="Author"> |
| 1352 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
| 1353 |
</author> |
| 1354 |
<author title="Author"> |
| 1355 |
<mail link="chouser@g.o">Chris Houser</mail> |
| 1356 |
</author> |
| 1357 |
<author title="Author"> |
| 1358 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
| 1359 |
</author> |
| 1360 |
<author title="Gentoo x86 Developer"> |
| 1361 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
| 1362 |
</author> |
| 1363 |
<author title="Gentoo Alpha Developer"> |
| 1364 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
| 1365 |
</author><!-- Does not want to be listed on the rendered page |
| 1366 |
<author title="Gentoo Developer"> |
| 1367 |
Aron Griffis |
| 1368 |
</author> |
| 1369 |
--> |
| 1370 |
<author title="Gentoo AMD64 Developer"> |
| 1371 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
| 1372 |
</author> |
| 1373 |
<author title="Gentoo HPPA developer"> |
| 1374 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
| 1375 |
</author> |
| 1376 |
<author title="Gentoo PPC developer"> |
| 1377 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
| 1378 |
</author> |
| 1379 |
<author title="Gentoo SPARC developer"> |
| 1380 |
<mail link="blademan@g.o">Joe Kallar</mail> |
| 1381 |
</author> |
| 1382 |
<author title="Editor"> |
| 1383 |
<mail link="zhen@g.o">John P. Davis</mail> |
| 1384 |
</author> |
| 1385 |
<author title="Editor">Pierre-Henri Jondot</author> |
| 1386 |
<author title="Editor"> |
| 1387 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
| 1388 |
</author> |
| 1389 |
<author title="Editor"> |
| 1390 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
| 1391 |
</author> |
| 1392 |
<author title="Editor"> |
| 1393 |
<mail link="seo@g.o">Jungmin Seo</mail> |
| 1394 |
</author> |
| 1395 |
<author title="Editor"> |
| 1396 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
| 1397 |
</author> |
| 1398 |
<author title="Editor"> |
| 1399 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
| 1400 |
</author> |
| 1401 |
<author title="Editor"> |
| 1402 |
<mail link="peitolm@g.o">Colin Morey</mail> |
| 1403 |
</author> |
| 1404 |
<author title="Editor"> |
| 1405 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
| 1406 |
</author> |
| 1407 |
<author title="Editor"> |
| 1408 |
<mail link="carl@g.o">Carl Anderson</mail> |
| 1409 |
</author> |
| 1410 |
<author title="Editor"> |
| 1411 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
| 1412 |
</author> |
| 1413 |
<author title="Editor"> |
| 1414 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
| 1415 |
</author> |
| 1416 |
<author title="Editor"> |
| 1417 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
| 1418 |
</author> |
| 1419 |
<author title="Editor"> |
| 1420 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
| 1421 |
</author> |
| 1422 |
<author title="Editor"> |
| 1423 |
<mail link="erwin@g.o">Erwin</mail> |
| 1424 |
</author> |
| 1425 |
<author title="Editor"> |
| 1426 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
| 1427 |
</author> |
| 1428 |
<author title="Editor"> |
| 1429 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
| 1430 |
</author> |
| 1431 |
<author title="Editor"> |
| 1432 |
<mail link="pylon@g.o">Lars Weiler</mail> |
| 1433 |
</author> |
| 1434 |
<author title="Editor"> |
| 1435 |
<mail link="sejo@g.o">Jochen Maes </mail> |
| 1436 |
</author> |
| 1437 |
<author title="Editor"> |
| 1438 |
<mail link="neysx@g.o">Xavier Neys</mail> |
| 1439 |
</author> |
| 1440 |
<author title="Reviewer"> |
| 1441 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
| 1442 |
</author> |
| 1443 |
<author title="Reviewer"> |
| 1444 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
| 1445 |
</author> |
| 1446 |
<author title="Reviewer"> |
| 1447 |
<mail link="spyderous@g.o">Donnie Berkholz</mail> |
| 1448 |
</author> |
| 1449 |
<author title="Reviewer"> |
| 1450 |
<mail link="antifa@g.o">Ken Nowack</mail> |
| 1451 |
</author> |
| 1452 |
|
| 1453 |
<abstract> |
| 1454 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
| 1455 |
This handbook contains the installation instructions for a networkless |
| 1456 |
installation on PPC systems and parts about working with Gentoo and Portage. |
| 1457 |
</abstract> |
| 1458 |
|
| 1459 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 1460 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 1461 |
<license/> |
| 1462 |
|
| 1463 |
<version>5.2</version> |
| 1464 |
<date>2005-10-13</date> |
| 1465 |
|
| 1466 |
<part> |
| 1467 |
<title>Installing Gentoo</title> |
| 1468 |
<abstract> |
| 1469 |
In this part you learn how to install Gentoo on your system. |
| 1470 |
</abstract> |
| 1471 |
|
| 1472 |
<chapter> |
| 1473 |
<title>About the Gentoo Linux Installation</title> |
| 1474 |
<abstract> |
| 1475 |
Users not familiar with Gentoo do not always know that choice is what |
| 1476 |
Gentoo is all about. |
| 1477 |
</abstract> |
| 1478 |
<include href="hb-install-about.xml"/> |
| 1479 |
</chapter> |
| 1480 |
|
| 1481 |
<chapter> |
| 1482 |
<title>Booting the Universal Installation CD</title> |
| 1483 |
<abstract> |
| 1484 |
Using our Universal Installation CD you can boot up your system into a running |
| 1485 |
environment that allows you to install Gentoo. |
| 1486 |
</abstract> |
| 1487 |
<include href="hb-install-ppc-medium.xml"/> |
| 1488 |
</chapter> |
| 1489 |
|
| 1490 |
<chapter> |
| 1491 |
<title>Configuring your Network</title> |
| 1492 |
<abstract> |
| 1493 |
If you need networking, this is the place where the network (and Internet |
| 1494 |
connection) is configured. |
| 1495 |
</abstract> |
| 1496 |
<include href="hb-install-network.xml"/> |
| 1497 |
</chapter> |
| 1498 |
|
| 1499 |
<chapter> |
| 1500 |
<title>Preparing the Disks</title> |
| 1501 |
<abstract> |
| 1502 |
To be able to install Gentoo, you must create the necessary partitions. |
| 1503 |
This chapter describes how to partition a disk for future usage. |
| 1504 |
</abstract> |
| 1505 |
<include href="hb-install-ppc-disk.xml"/> |
| 1506 |
</chapter> |
| 1507 |
|
| 1508 |
<chapter> |
| 1509 |
<title>Installing the Gentoo Installation Files</title> |
| 1510 |
<abstract> |
| 1511 |
In this chapter we describe how you extract a stage3 file and how to configure |
| 1512 |
Portage. |
| 1513 |
</abstract> |
| 1514 |
<include href="hb-install-stage.xml"/> |
| 1515 |
</chapter> |
| 1516 |
|
| 1517 |
<chapter> |
| 1518 |
<title>Chrooting into the Gentoo Base System</title> |
| 1519 |
<abstract> |
| 1520 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
| 1521 |
the USE variable. |
| 1522 |
</abstract> |
| 1523 |
<include href="hb-install-system.xml"/> |
| 1524 |
</chapter> |
| 1525 |
|
| 1526 |
<chapter> |
| 1527 |
<title>Configuring the Kernel</title> |
| 1528 |
<abstract> |
| 1529 |
The Linux kernel is the core of every distribution. This chapter |
| 1530 |
explains how to configure your kernel. |
| 1531 |
</abstract> |
| 1532 |
<include href="hb-install-ppc-kernel.xml"/> |
| 1533 |
</chapter> |
| 1534 |
|
| 1535 |
<chapter> |
| 1536 |
<title>Configuring your System</title> |
| 1537 |
<abstract> |
| 1538 |
You need to edit some important configuration files. In this chapter |
| 1539 |
you receive an overview of these files and an explanation on how to |
| 1540 |
proceed. |
| 1541 |
</abstract> |
| 1542 |
<include href="hb-install-config.xml"/> |
| 1543 |
</chapter> |
| 1544 |
|
| 1545 |
<chapter> |
| 1546 |
<title>Installing Necessary System Tools</title> |
| 1547 |
<abstract> |
| 1548 |
As mentioned before, Gentoo is about choices. In this chapter we help you |
| 1549 |
choose and install some important tools. |
| 1550 |
</abstract> |
| 1551 |
<include href="hb-install-tools.xml"/> |
| 1552 |
</chapter> |
| 1553 |
|
| 1554 |
<chapter> |
| 1555 |
<title>Configuring the Bootloader</title> |
| 1556 |
<abstract> |
| 1557 |
Several bootloaders exist. Each one of them has its own way of |
| 1558 |
configuration. In this chapter we'll describe all possibilities for you |
| 1559 |
and step you through the process of configuring a bootloader to your |
| 1560 |
needs. |
| 1561 |
</abstract> |
| 1562 |
<include href="hb-install-ppc-bootloader.xml"/> |
| 1563 |
</chapter> |
| 1564 |
|
| 1565 |
<chapter> |
| 1566 |
<title>Finalizing your Gentoo Installation</title> |
| 1567 |
<abstract> |
| 1568 |
You're almost done. We'll just create one (or more) users for your |
| 1569 |
system and (optionally) install prebuilt packages. |
| 1570 |
</abstract> |
| 1571 |
<include href="hb-install-finalise.xml"/> |
| 1572 |
</chapter> |
| 1573 |
|
| 1574 |
<chapter> |
| 1575 |
<title>Where to go from here?</title> |
| 1576 |
<abstract> |
| 1577 |
Now you have your Gentoo system, but what's next? |
| 1578 |
</abstract> |
| 1579 |
<include href="hb-install-next.xml"/> |
| 1580 |
</chapter> |
| 1581 |
</part> |
| 1582 |
|
| 1583 |
<part> |
| 1584 |
<title>Working with Gentoo</title> |
| 1585 |
<abstract> |
| 1586 |
Learn how to work with Gentoo: installing software, altering variables, changing |
| 1587 |
Portage behaviour etc. |
| 1588 |
</abstract> |
| 1589 |
|
| 1590 |
<chapter> |
| 1591 |
<title>A Portage Introduction</title> |
| 1592 |
<abstract> |
| 1593 |
This chapter explains the "simple" steps a user definitely needs to know to |
| 1594 |
maintain the software on his system. |
| 1595 |
</abstract> |
| 1596 |
<include href="../hb-working-portage.xml"/> |
| 1597 |
</chapter> |
| 1598 |
|
| 1599 |
<chapter> |
| 1600 |
<title>USE flags</title> |
| 1601 |
<abstract> |
| 1602 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
| 1603 |
work with USE-flags and understand how USE-flags interact with your system. |
| 1604 |
</abstract> |
| 1605 |
<include href="../hb-working-use.xml"/> |
| 1606 |
</chapter> |
| 1607 |
|
| 1608 |
<chapter> |
| 1609 |
<title>Portage Features</title> |
| 1610 |
<abstract> |
| 1611 |
Discover the features Portage has, such as support for distributed compiling, |
| 1612 |
ccache and more. |
| 1613 |
</abstract> |
| 1614 |
<include href="../hb-working-features.xml"/> |
| 1615 |
</chapter> |
| 1616 |
|
| 1617 |
<chapter> |
| 1618 |
<title>Initscripts</title> |
| 1619 |
<abstract> |
| 1620 |
Gentoo uses a special initscript format which, amongst other features, allows |
| 1621 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
| 1622 |
these aspects and explains how to deal with these scripts. |
| 1623 |
</abstract> |
| 1624 |
<include href="../hb-working-rcscripts.xml"/> |
| 1625 |
</chapter> |
| 1626 |
|
| 1627 |
<chapter> |
| 1628 |
<title>Environment Variables</title> |
| 1629 |
<abstract> |
| 1630 |
With Gentoo you can easily manage the environment variables for your system. |
| 1631 |
This chapter explains how you do that, and also describes frequently used |
| 1632 |
variables. |
| 1633 |
</abstract> |
| 1634 |
<include href="../hb-working-variables.xml"/> |
| 1635 |
</chapter> |
| 1636 |
</part> |
| 1637 |
|
| 1638 |
<part> |
| 1639 |
<title>Working with Portage</title> |
| 1640 |
<abstract> |
| 1641 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
| 1642 |
Software Management Tool. |
| 1643 |
</abstract> |
| 1644 |
|
| 1645 |
<chapter> |
| 1646 |
<title>Files and Directories</title> |
| 1647 |
<abstract> |
| 1648 |
Once you want to know Portage in-depth you need to know where it stores its |
| 1649 |
files and data. |
| 1650 |
</abstract> |
| 1651 |
<include href="../hb-portage-files.xml"/> |
| 1652 |
</chapter> |
| 1653 |
|
| 1654 |
<chapter> |
| 1655 |
<title>Configuring through Variables</title> |
| 1656 |
<abstract> |
| 1657 |
Portage is completely configurable through various variables you can set in the |
| 1658 |
configuration file or as environment variable. |
| 1659 |
</abstract> |
| 1660 |
<include href="../hb-portage-configuration.xml"/> |
| 1661 |
</chapter> |
| 1662 |
|
| 1663 |
<chapter> |
| 1664 |
<title>Mixing Software Branches</title> |
| 1665 |
<abstract> |
| 1666 |
Gentoo provides software separated in several branches, depending on stability |
| 1667 |
and architectural support. "Mixing Software Branches" inform you how these |
| 1668 |
branches can be configured and how you can override this separation |
| 1669 |
individually. |
| 1670 |
</abstract> |
| 1671 |
<include href="../hb-portage-branches.xml"/> |
| 1672 |
</chapter> |
| 1673 |
|
| 1674 |
<chapter> |
| 1675 |
<title>Additional Portage Tools</title> |
| 1676 |
<abstract> |
| 1677 |
Portage comes with a few extra tools that might make your Gentoo experience even |
| 1678 |
better. Read on to discover how to use dispatch-conf and other tools. |
| 1679 |
</abstract> |
| 1680 |
<include href="../hb-portage-tools.xml"/> |
| 1681 |
</chapter> |
| 1682 |
|
| 1683 |
<chapter> |
| 1684 |
<title>Diverting from the Official Tree</title> |
| 1685 |
<abstract> |
| 1686 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
| 1687 |
your own Portage tree, how to synchronise only the categories you want, inject |
| 1688 |
packages and more. |
| 1689 |
</abstract> |
| 1690 |
<include href="../hb-portage-diverttree.xml"/> |
| 1691 |
</chapter> |
| 1692 |
|
| 1693 |
<chapter> |
| 1694 |
<title>The Ebuild Application</title> |
| 1695 |
<abstract> |
| 1696 |
In "The Ebuild Application" you are informed about the steps Portage takes while |
| 1697 |
installing software and how you can do this yourself using the ebuild |
| 1698 |
application. |
| 1699 |
</abstract> |
| 1700 |
<include href="../hb-portage-ebuild.xml"/> |
| 1701 |
</chapter> |
| 1702 |
</part> |
| 1703 |
|
| 1704 |
<part> |
| 1705 |
<title>Gentoo Network Configuration</title> |
| 1706 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
| 1707 |
|
| 1708 |
<chapter> |
| 1709 |
<title>Getting Started</title> |
| 1710 |
<abstract> |
| 1711 |
A guide to quickly get your network interface up and running in most common |
| 1712 |
environments. |
| 1713 |
</abstract> |
| 1714 |
<include href="../hb-net-start.xml"/> |
| 1715 |
</chapter> |
| 1716 |
|
| 1717 |
<chapter> |
| 1718 |
<title>Advanced Configuration</title> |
| 1719 |
<abstract> |
| 1720 |
Here we learn about how the configuration works - you need to know this |
| 1721 |
before we learn about modular networking. |
| 1722 |
</abstract> |
| 1723 |
<include href="../hb-net-advanced.xml"/> |
| 1724 |
</chapter> |
| 1725 |
|
| 1726 |
<chapter> |
| 1727 |
<title>Modular Networking</title> |
| 1728 |
<abstract> |
| 1729 |
Gentoo provides you flexible networking - here you are told about choosing |
| 1730 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
| 1731 |
</abstract> |
| 1732 |
<include href="../hb-net-modules.xml"/> |
| 1733 |
</chapter> |
| 1734 |
|
| 1735 |
<chapter> |
| 1736 |
<title>Wireless Networking</title> |
| 1737 |
<abstract> |
| 1738 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
| 1739 |
</abstract> |
| 1740 |
<include href="../hb-net-wireless.xml"/> |
| 1741 |
</chapter> |
| 1742 |
|
| 1743 |
<chapter> |
| 1744 |
<title>Adding Functionality</title> |
| 1745 |
<abstract> |
| 1746 |
If you're feeling adventurous, you can add your own functions to networking. |
| 1747 |
</abstract> |
| 1748 |
<include href="../hb-net-functions.xml"/> |
| 1749 |
</chapter> |
| 1750 |
|
| 1751 |
<chapter> |
| 1752 |
<title>Network Management</title> |
| 1753 |
<abstract> |
| 1754 |
For laptop users or people who move their computer around different networks. |
| 1755 |
</abstract> |
| 1756 |
<include href="../hb-net-management.xml"/> |
| 1757 |
</chapter> |
| 1758 |
</part> |
| 1759 |
|
| 1760 |
</book> |
| 1761 |
|
| 1762 |
|
| 1763 |
|
| 1764 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/handbook-ppc64.xml |
| 1765 |
|
| 1766 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-ppc64.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 1767 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-ppc64.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 1768 |
|
| 1769 |
Index: handbook-ppc64.xml |
| 1770 |
=================================================================== |
| 1771 |
<?xml version='1.0' encoding='UTF-8'?> |
| 1772 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
| 1773 |
|
| 1774 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-ppc64.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 1775 |
|
| 1776 |
<book link="handbook-ppc64.xml"> |
| 1777 |
<title>Gentoo Linux 2006.0 PPC64 Handbook</title> |
| 1778 |
|
| 1779 |
<author title="Author"> |
| 1780 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
| 1781 |
</author> |
| 1782 |
<author title="Author"> |
| 1783 |
<mail link="uberlord@g.o">Roy Marples</mail> |
| 1784 |
</author> |
| 1785 |
<author title="Author"> |
| 1786 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
| 1787 |
</author> |
| 1788 |
<author title="Author"> |
| 1789 |
<mail link="chouser@g.o">Chris Houser</mail> |
| 1790 |
</author> |
| 1791 |
<author title="Author"> |
| 1792 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
| 1793 |
</author> |
| 1794 |
<author title="Gentoo x86 Developer"> |
| 1795 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
| 1796 |
</author> |
| 1797 |
<author title="Gentoo Alpha Developer"> |
| 1798 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
| 1799 |
</author><!-- Does not want to be listed on the rendered page |
| 1800 |
<author title="Gentoo Developer"> |
| 1801 |
Aron Griffis |
| 1802 |
</author> |
| 1803 |
--> |
| 1804 |
<author title="Gentoo AMD64 Developer"> |
| 1805 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
| 1806 |
</author> |
| 1807 |
<author title="Gentoo HPPA developer"> |
| 1808 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
| 1809 |
</author> |
| 1810 |
<author title="Gentoo PPC developer"> |
| 1811 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
| 1812 |
</author> |
| 1813 |
<author title="Gentoo SPARC developer"> |
| 1814 |
<mail link="blademan@g.o">Joe Kallar</mail> |
| 1815 |
</author> |
| 1816 |
<author title="Editor"> |
| 1817 |
<mail link="zhen@g.o">John P. Davis</mail> |
| 1818 |
</author> |
| 1819 |
<author title="Editor">Pierre-Henri Jondot</author> |
| 1820 |
<author title="Editor"> |
| 1821 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
| 1822 |
</author> |
| 1823 |
<author title="Editor"> |
| 1824 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
| 1825 |
</author> |
| 1826 |
<author title="Editor"> |
| 1827 |
<mail link="seo@g.o">Jungmin Seo</mail> |
| 1828 |
</author> |
| 1829 |
<author title="Editor"> |
| 1830 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
| 1831 |
</author> |
| 1832 |
<author title="Editor"> |
| 1833 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
| 1834 |
</author> |
| 1835 |
<author title="Editor"> |
| 1836 |
<mail link="peitolm@g.o">Colin Morey</mail> |
| 1837 |
</author> |
| 1838 |
<author title="Editor"> |
| 1839 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
| 1840 |
</author> |
| 1841 |
<author title="Editor"> |
| 1842 |
<mail link="carl@g.o">Carl Anderson</mail> |
| 1843 |
</author> |
| 1844 |
<author title="Editor"> |
| 1845 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
| 1846 |
</author> |
| 1847 |
<author title="Editor"> |
| 1848 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
| 1849 |
</author> |
| 1850 |
<author title="Editor"> |
| 1851 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
| 1852 |
</author> |
| 1853 |
<author title="Editor"> |
| 1854 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
| 1855 |
</author> |
| 1856 |
<author title="Editor"> |
| 1857 |
<mail link="erwin@g.o">Erwin</mail> |
| 1858 |
</author> |
| 1859 |
<author title="Editor"> |
| 1860 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
| 1861 |
</author> |
| 1862 |
<author title="Editor"> |
| 1863 |
<mail link="neysx@g.o">Xavier Neys</mail> |
| 1864 |
</author> |
| 1865 |
<author title="Reviewer"> |
| 1866 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
| 1867 |
</author> |
| 1868 |
<author title="Reviewer"> |
| 1869 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
| 1870 |
</author> |
| 1871 |
<author title="Reviewer"> |
| 1872 |
<mail link="spyderous@g.o">Donnie Berkholz</mail> |
| 1873 |
</author> |
| 1874 |
<author title="Reviewer"> |
| 1875 |
<mail link="antifa@g.o">Ken Nowack</mail> |
| 1876 |
</author> |
| 1877 |
<author title="Contributor"> |
| 1878 |
<mail link="pylon@g.o">Lars Weiler</mail> |
| 1879 |
</author> |
| 1880 |
<author title="Editor"> |
| 1881 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
| 1882 |
</author> |
| 1883 |
|
| 1884 |
<abstract> |
| 1885 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
| 1886 |
This handbook contains the installation instructions for a networkless |
| 1887 |
installation on PPC64 systems and parts about working with Gentoo and Portage. |
| 1888 |
</abstract> |
| 1889 |
|
| 1890 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 1891 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 1892 |
<license/> |
| 1893 |
|
| 1894 |
<version>5.2</version> |
| 1895 |
<date>2005-10-13</date> |
| 1896 |
|
| 1897 |
<part> |
| 1898 |
<title>Installing Gentoo</title> |
| 1899 |
<abstract> |
| 1900 |
In this part you learn how to install Gentoo on your system. |
| 1901 |
</abstract> |
| 1902 |
|
| 1903 |
<chapter> |
| 1904 |
<title>About the Gentoo Linux Installation</title> |
| 1905 |
<abstract> |
| 1906 |
Users not familiar with Gentoo do not always know that choice is what |
| 1907 |
Gentoo is all about. |
| 1908 |
</abstract> |
| 1909 |
<include href="hb-install-about.xml"/> |
| 1910 |
</chapter> |
| 1911 |
|
| 1912 |
<chapter> |
| 1913 |
<title>Booting the Universal Installation CD</title> |
| 1914 |
<abstract> |
| 1915 |
Using our Universal Installation CD you can boot up your system into a running |
| 1916 |
environment that allows you to install Gentoo. |
| 1917 |
</abstract> |
| 1918 |
<include href="hb-install-ppc64-medium.xml"/> |
| 1919 |
</chapter> |
| 1920 |
|
| 1921 |
<chapter> |
| 1922 |
<title>Configuring your Network</title> |
| 1923 |
<abstract> |
| 1924 |
If you need networking, this is the place where the network (and Internet |
| 1925 |
connection) is configured. |
| 1926 |
</abstract> |
| 1927 |
<include href="hb-install-network.xml"/> |
| 1928 |
</chapter> |
| 1929 |
|
| 1930 |
<chapter> |
| 1931 |
<title>Preparing the Disks</title> |
| 1932 |
<abstract> |
| 1933 |
To be able to install Gentoo, you must create the necessary partitions. |
| 1934 |
This chapter describes how to partition a disk for future usage. |
| 1935 |
</abstract> |
| 1936 |
<include href="hb-install-ppc64-disk.xml"/> |
| 1937 |
</chapter> |
| 1938 |
|
| 1939 |
<chapter> |
| 1940 |
<title>Installing the Gentoo Installation Files</title> |
| 1941 |
<abstract> |
| 1942 |
In this chapter we describe how you extract a stage3 file and how to configure |
| 1943 |
Portage. |
| 1944 |
</abstract> |
| 1945 |
<include href="hb-install-stage.xml"/> |
| 1946 |
</chapter> |
| 1947 |
|
| 1948 |
<chapter> |
| 1949 |
<title>Chrooting into the Gentoo Base System</title> |
| 1950 |
<abstract> |
| 1951 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
| 1952 |
the USE variable. |
| 1953 |
</abstract> |
| 1954 |
<include href="hb-install-system.xml"/> |
| 1955 |
</chapter> |
| 1956 |
|
| 1957 |
<chapter> |
| 1958 |
<title>Configuring the Kernel</title> |
| 1959 |
<abstract> |
| 1960 |
The Linux kernel is the core of every distribution. This chapter |
| 1961 |
explains how to configure your kernel. |
| 1962 |
</abstract> |
| 1963 |
<include href="hb-install-ppc64-kernel.xml"/> |
| 1964 |
</chapter> |
| 1965 |
|
| 1966 |
<chapter> |
| 1967 |
<title>Configuring your System</title> |
| 1968 |
<abstract> |
| 1969 |
You need to edit some important configuration files. In this chapter |
| 1970 |
you receive an overview of these files and an explanation on how to |
| 1971 |
proceed. |
| 1972 |
</abstract> |
| 1973 |
<include href="hb-install-config.xml"/> |
| 1974 |
</chapter> |
| 1975 |
|
| 1976 |
<chapter> |
| 1977 |
<title>Installing Necessary System Tools</title> |
| 1978 |
<abstract> |
| 1979 |
As mentioned before, Gentoo is about choices. In this chapter we help you |
| 1980 |
choose and install some important tools. |
| 1981 |
</abstract> |
| 1982 |
<include href="hb-install-tools.xml"/> |
| 1983 |
</chapter> |
| 1984 |
|
| 1985 |
<chapter> |
| 1986 |
<title>Configuring the Bootloader</title> |
| 1987 |
<abstract> |
| 1988 |
Several bootloaders exist. Each one of them has its own way of |
| 1989 |
configuration. In this chapter we'll describe all possibilities for you |
| 1990 |
and step you through the process of configuring a bootloader to your |
| 1991 |
needs. |
| 1992 |
</abstract> |
| 1993 |
<include href="hb-install-ppc64-bootloader.xml"/> |
| 1994 |
</chapter> |
| 1995 |
|
| 1996 |
|
| 1997 |
<chapter> |
| 1998 |
<title>Finalizing your Gentoo Installation</title> |
| 1999 |
<abstract> |
| 2000 |
You're almost done. We'll just create one (or more) users for your |
| 2001 |
system and (optionally) install prebuilt packages. |
| 2002 |
</abstract> |
| 2003 |
<include href="hb-install-finalise.xml"/> |
| 2004 |
</chapter> |
| 2005 |
|
| 2006 |
<chapter> |
| 2007 |
<title>Where to go from here?</title> |
| 2008 |
<abstract> |
| 2009 |
Now you have your Gentoo system, but what's next? |
| 2010 |
</abstract> |
| 2011 |
<include href="hb-install-next.xml"/> |
| 2012 |
</chapter> |
| 2013 |
</part> |
| 2014 |
|
| 2015 |
<part> |
| 2016 |
<title>Working with Gentoo</title> |
| 2017 |
<abstract> |
| 2018 |
Learn how to work with Gentoo: installing software, altering variables, changing |
| 2019 |
Portage behaviour etc. |
| 2020 |
</abstract> |
| 2021 |
|
| 2022 |
<chapter> |
| 2023 |
<title>A Portage Introduction</title> |
| 2024 |
<abstract> |
| 2025 |
This chapter explains the "simple" steps a user definitely needs to know to |
| 2026 |
maintain the software on his system. |
| 2027 |
</abstract> |
| 2028 |
<include href="../hb-working-portage.xml"/> |
| 2029 |
</chapter> |
| 2030 |
|
| 2031 |
<chapter> |
| 2032 |
<title>USE flags</title> |
| 2033 |
<abstract> |
| 2034 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
| 2035 |
work with USE-flags and understand how USE-flags interact with your system. |
| 2036 |
</abstract> |
| 2037 |
<include href="../hb-working-use.xml"/> |
| 2038 |
</chapter> |
| 2039 |
|
| 2040 |
<chapter> |
| 2041 |
<title>Portage Features</title> |
| 2042 |
<abstract> |
| 2043 |
Discover the features Portage has, such as support for distributed compiling, |
| 2044 |
ccache and more. |
| 2045 |
</abstract> |
| 2046 |
<include href="../hb-working-features.xml"/> |
| 2047 |
</chapter> |
| 2048 |
|
| 2049 |
<chapter> |
| 2050 |
<title>Initscripts</title> |
| 2051 |
<abstract> |
| 2052 |
Gentoo uses a special initscript format which, amongst other features, allows |
| 2053 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
| 2054 |
these aspects and explains how to deal with these scripts. |
| 2055 |
</abstract> |
| 2056 |
<include href="../hb-working-rcscripts.xml"/> |
| 2057 |
</chapter> |
| 2058 |
|
| 2059 |
<chapter> |
| 2060 |
<title>Environment Variables</title> |
| 2061 |
<abstract> |
| 2062 |
With Gentoo you can easily manage the environment variables for your system. |
| 2063 |
This chapter explains how you do that, and also describes frequently used |
| 2064 |
variables. |
| 2065 |
</abstract> |
| 2066 |
<include href="../hb-working-variables.xml"/> |
| 2067 |
</chapter> |
| 2068 |
</part> |
| 2069 |
|
| 2070 |
<part> |
| 2071 |
<title>Working with Portage</title> |
| 2072 |
<abstract> |
| 2073 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
| 2074 |
Software Management Tool. |
| 2075 |
</abstract> |
| 2076 |
|
| 2077 |
<chapter> |
| 2078 |
<title>Files and Directories</title> |
| 2079 |
<abstract> |
| 2080 |
Once you want to know Portage in-depth you need to know where it stores its |
| 2081 |
files and data. |
| 2082 |
</abstract> |
| 2083 |
<include href="../hb-portage-files.xml"/> |
| 2084 |
</chapter> |
| 2085 |
|
| 2086 |
<chapter> |
| 2087 |
<title>Configuring through Variables</title> |
| 2088 |
<abstract> |
| 2089 |
Portage is completely configurable through various variables you can set in the |
| 2090 |
configuration file or as environment variable. |
| 2091 |
</abstract> |
| 2092 |
<include href="../hb-portage-configuration.xml"/> |
| 2093 |
</chapter> |
| 2094 |
|
| 2095 |
<chapter> |
| 2096 |
<title>Mixing Software Branches</title> |
| 2097 |
<abstract> |
| 2098 |
Gentoo provides software separated in several branches, depending on stability |
| 2099 |
and architectural support. "Mixing Software Branches" inform you how these |
| 2100 |
branches can be configured and how you can override this separation |
| 2101 |
individually. |
| 2102 |
</abstract> |
| 2103 |
<include href="../hb-portage-branches.xml"/> |
| 2104 |
</chapter> |
| 2105 |
|
| 2106 |
<chapter> |
| 2107 |
<title>Additional Portage Tools</title> |
| 2108 |
<abstract> |
| 2109 |
Portage comes with a few extra tools that might make your Gentoo experience even |
| 2110 |
better. Read on to discover how to use dispatch-conf and other tools. |
| 2111 |
</abstract> |
| 2112 |
<include href="../hb-portage-tools.xml"/> |
| 2113 |
</chapter> |
| 2114 |
|
| 2115 |
<chapter> |
| 2116 |
<title>Diverting from the Official Tree</title> |
| 2117 |
<abstract> |
| 2118 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
| 2119 |
your own Portage tree, how to synchronise only the categories you want, inject |
| 2120 |
packages and more. |
| 2121 |
</abstract> |
| 2122 |
<include href="../hb-portage-diverttree.xml"/> |
| 2123 |
</chapter> |
| 2124 |
|
| 2125 |
<chapter> |
| 2126 |
<title>The Ebuild Application</title> |
| 2127 |
<abstract> |
| 2128 |
In "The Ebuild Application" you are informed about the steps Portage takes while |
| 2129 |
installing software and how you can do this yourself using the ebuild |
| 2130 |
application. |
| 2131 |
</abstract> |
| 2132 |
<include href="../hb-portage-ebuild.xml"/> |
| 2133 |
</chapter> |
| 2134 |
</part> |
| 2135 |
|
| 2136 |
<part> |
| 2137 |
<title>Gentoo Network Configuration</title> |
| 2138 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
| 2139 |
|
| 2140 |
<chapter> |
| 2141 |
<title>Getting Started</title> |
| 2142 |
<abstract> |
| 2143 |
A guide to quickly get your network interface up and running in most common |
| 2144 |
environments. |
| 2145 |
</abstract> |
| 2146 |
<include href="../hb-net-start.xml"/> |
| 2147 |
</chapter> |
| 2148 |
|
| 2149 |
<chapter> |
| 2150 |
<title>Advanced Configuration</title> |
| 2151 |
<abstract> |
| 2152 |
Here we learn about how the configuration works - you need to know this |
| 2153 |
before we learn about modular networking. |
| 2154 |
</abstract> |
| 2155 |
<include href="../hb-net-advanced.xml"/> |
| 2156 |
</chapter> |
| 2157 |
|
| 2158 |
<chapter> |
| 2159 |
<title>Modular Networking</title> |
| 2160 |
<abstract> |
| 2161 |
Gentoo provides you flexible networking - here you are told about choosing |
| 2162 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
| 2163 |
</abstract> |
| 2164 |
<include href="../hb-net-modules.xml"/> |
| 2165 |
</chapter> |
| 2166 |
|
| 2167 |
<chapter> |
| 2168 |
<title>Wireless Networking</title> |
| 2169 |
<abstract> |
| 2170 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
| 2171 |
</abstract> |
| 2172 |
<include href="../hb-net-wireless.xml"/> |
| 2173 |
</chapter> |
| 2174 |
|
| 2175 |
<chapter> |
| 2176 |
<title>Adding Functionality</title> |
| 2177 |
<abstract> |
| 2178 |
If you're feeling adventurous, you can add your own functions to networking. |
| 2179 |
</abstract> |
| 2180 |
<include href="../hb-net-functions.xml"/> |
| 2181 |
</chapter> |
| 2182 |
|
| 2183 |
<chapter> |
| 2184 |
<title>Network Management</title> |
| 2185 |
<abstract> |
| 2186 |
For laptop users or people who move their computer around different networks. |
| 2187 |
</abstract> |
| 2188 |
<include href="../hb-net-management.xml"/> |
| 2189 |
</chapter> |
| 2190 |
</part> |
| 2191 |
|
| 2192 |
</book> |
| 2193 |
|
| 2194 |
|
| 2195 |
|
| 2196 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/handbook-sparc.xml |
| 2197 |
|
| 2198 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-sparc.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 2199 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-sparc.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 2200 |
|
| 2201 |
Index: handbook-sparc.xml |
| 2202 |
=================================================================== |
| 2203 |
<?xml version='1.0' encoding='UTF-8'?> |
| 2204 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
| 2205 |
|
| 2206 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-sparc.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 2207 |
|
| 2208 |
<book link="handbook-sparc.xml"> |
| 2209 |
<title>Gentoo Linux 2006.0 SPARC Handbook</title> |
| 2210 |
|
| 2211 |
<author title="Author"> |
| 2212 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
| 2213 |
</author> |
| 2214 |
<author title="Author"> |
| 2215 |
<mail link="uberlord@g.o">Roy Marples</mail> |
| 2216 |
</author> |
| 2217 |
<author title="Author"> |
| 2218 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
| 2219 |
</author> |
| 2220 |
<author title="Author"> |
| 2221 |
<mail link="chouser@g.o">Chris Houser</mail> |
| 2222 |
</author> |
| 2223 |
<author title="Author"> |
| 2224 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
| 2225 |
</author> |
| 2226 |
<author title="Gentoo x86 Developer"> |
| 2227 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
| 2228 |
</author> |
| 2229 |
<author title="Gentoo Alpha Developer"> |
| 2230 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
| 2231 |
</author><!-- Does not want to be listed on the rendered page |
| 2232 |
<author title="Gentoo Developer"> |
| 2233 |
Aron Griffis |
| 2234 |
</author> |
| 2235 |
--> |
| 2236 |
<author title="Gentoo AMD64 Developer"> |
| 2237 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
| 2238 |
</author> |
| 2239 |
<author title="Gentoo HPPA developer"> |
| 2240 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
| 2241 |
</author> |
| 2242 |
<author title="Gentoo PPC developer"> |
| 2243 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
| 2244 |
</author> |
| 2245 |
<author title="Gentoo SPARC developer"> |
| 2246 |
<mail link="blademan@g.o">Joe Kallar</mail> |
| 2247 |
</author> |
| 2248 |
<author title="Editor"> |
| 2249 |
<mail link="zhen@g.o">John P. Davis</mail> |
| 2250 |
</author> |
| 2251 |
<author title="Editor">Pierre-Henri Jondot</author> |
| 2252 |
<author title="Editor"> |
| 2253 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
| 2254 |
</author> |
| 2255 |
<author title="Editor"> |
| 2256 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
| 2257 |
</author> |
| 2258 |
<author title="Editor"> |
| 2259 |
<mail link="seo@g.o">Jungmin Seo</mail> |
| 2260 |
</author> |
| 2261 |
<author title="Editor"> |
| 2262 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
| 2263 |
</author> |
| 2264 |
<author title="Editor"> |
| 2265 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
| 2266 |
</author> |
| 2267 |
<author title="Editor"> |
| 2268 |
<mail link="peitolm@g.o">Colin Morey</mail> |
| 2269 |
</author> |
| 2270 |
<author title="Editor"> |
| 2271 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
| 2272 |
</author> |
| 2273 |
<author title="Editor"> |
| 2274 |
<mail link="carl@g.o">Carl Anderson</mail> |
| 2275 |
</author> |
| 2276 |
<author title="Editor"> |
| 2277 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
| 2278 |
</author> |
| 2279 |
<author title="Editor"> |
| 2280 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
| 2281 |
</author> |
| 2282 |
<author title="Editor"> |
| 2283 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
| 2284 |
</author> |
| 2285 |
<author title="Editor"> |
| 2286 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
| 2287 |
</author> |
| 2288 |
<author title="Editor"> |
| 2289 |
<mail link="erwin@g.o">Erwin</mail> |
| 2290 |
</author> |
| 2291 |
<author title="Editor"> |
| 2292 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
| 2293 |
</author> |
| 2294 |
<author title="Editor"> |
| 2295 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
| 2296 |
</author> |
| 2297 |
<author title="Editor"> |
| 2298 |
<mail link="neysx@g.o">Xavier Neys</mail> |
| 2299 |
</author> |
| 2300 |
<author title="Reviewer"> |
| 2301 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
| 2302 |
</author> |
| 2303 |
<author title="Reviewer"> |
| 2304 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
| 2305 |
</author> |
| 2306 |
<author title="Reviewer"> |
| 2307 |
<mail link="spyderous@g.o">Donnie Berkholz</mail> |
| 2308 |
</author> |
| 2309 |
<author title="Reviewer"> |
| 2310 |
<mail link="antifa@g.o">Ken Nowack</mail> |
| 2311 |
</author> |
| 2312 |
<author title="Contributor"> |
| 2313 |
<mail link="pylon@g.o">Lars Weiler</mail> |
| 2314 |
</author> |
| 2315 |
|
| 2316 |
<abstract> |
| 2317 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
| 2318 |
This handbook contains the installation instructions for a networkless |
| 2319 |
installation on Sparc systems and parts about working with Gentoo and Portage. |
| 2320 |
</abstract> |
| 2321 |
|
| 2322 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 2323 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 2324 |
<license/> |
| 2325 |
|
| 2326 |
<version>5.2</version> |
| 2327 |
<date>2005-10-13</date> |
| 2328 |
|
| 2329 |
<part> |
| 2330 |
<title>Installing Gentoo</title> |
| 2331 |
<abstract> |
| 2332 |
In this part you learn how to install Gentoo on your system. |
| 2333 |
</abstract> |
| 2334 |
|
| 2335 |
<chapter> |
| 2336 |
<title>About the Gentoo Linux Installation</title> |
| 2337 |
<abstract> |
| 2338 |
Users not familiar with Gentoo do not always know that choice is what |
| 2339 |
Gentoo is all about. |
| 2340 |
</abstract> |
| 2341 |
<include href="hb-install-about.xml"/> |
| 2342 |
</chapter> |
| 2343 |
|
| 2344 |
<chapter> |
| 2345 |
<title>Booting the Universal Installation CD</title> |
| 2346 |
<abstract> |
| 2347 |
Using our Universal Installation CD you can boot up your system into a running |
| 2348 |
environment that allows you to install Gentoo. |
| 2349 |
</abstract> |
| 2350 |
<include href="hb-install-sparc-medium.xml"/> |
| 2351 |
</chapter> |
| 2352 |
|
| 2353 |
<chapter> |
| 2354 |
<title>Configuring your Network</title> |
| 2355 |
<abstract> |
| 2356 |
If you need networking, this is the place where the network (and Internet |
| 2357 |
connection) is configured. |
| 2358 |
</abstract> |
| 2359 |
<include href="hb-install-network.xml"/> |
| 2360 |
</chapter> |
| 2361 |
|
| 2362 |
<chapter> |
| 2363 |
<title>Preparing the Disks</title> |
| 2364 |
<abstract> |
| 2365 |
To be able to install Gentoo, you must create the necessary partitions. |
| 2366 |
This chapter describes how to partition a disk for future usage. |
| 2367 |
</abstract> |
| 2368 |
<include href="hb-install-sparc-disk.xml"/> |
| 2369 |
</chapter> |
| 2370 |
|
| 2371 |
<chapter> |
| 2372 |
<title>Installing the Gentoo Installation Files</title> |
| 2373 |
<abstract> |
| 2374 |
In this chapter we describe how you extract a stage3 file and how to configure |
| 2375 |
Portage. |
| 2376 |
</abstract> |
| 2377 |
<include href="hb-install-stage.xml"/> |
| 2378 |
</chapter> |
| 2379 |
|
| 2380 |
<chapter> |
| 2381 |
<title>Chrooting into the Gentoo Base System</title> |
| 2382 |
<abstract> |
| 2383 |
Now that the stage3 file is extracted, we chroot into the new system and modify |
| 2384 |
the USE variable. |
| 2385 |
</abstract> |
| 2386 |
<include href="hb-install-system.xml"/> |
| 2387 |
</chapter> |
| 2388 |
|
| 2389 |
<chapter> |
| 2390 |
<title>Configuring the Kernel</title> |
| 2391 |
<abstract> |
| 2392 |
The Linux kernel is the core of every distribution. This chapter |
| 2393 |
explains how to configure your kernel. |
| 2394 |
</abstract> |
| 2395 |
<include href="hb-install-sparc-kernel.xml"/> |
| 2396 |
</chapter> |
| 2397 |
|
| 2398 |
<chapter> |
| 2399 |
<title>Configuring your System</title> |
| 2400 |
<abstract> |
| 2401 |
You need to edit some important configuration files. In this chapter |
| 2402 |
you receive an overview of these files and an explanation on how to |
| 2403 |
proceed. |
| 2404 |
</abstract> |
| 2405 |
<include href="hb-install-config.xml"/> |
| 2406 |
</chapter> |
| 2407 |
|
| 2408 |
<chapter> |
| 2409 |
<title>Installing Necessary System Tools</title> |
| 2410 |
<abstract> |
| 2411 |
As mentioned before, Gentoo is about choices. In this chapter we help you |
| 2412 |
choose and install some important tools. |
| 2413 |
</abstract> |
| 2414 |
<include href="hb-install-tools.xml"/> |
| 2415 |
</chapter> |
| 2416 |
|
| 2417 |
<chapter> |
| 2418 |
<title>Configuring the Bootloader</title> |
| 2419 |
<abstract> |
| 2420 |
The SPARC architecture uses the SILO bootloader to fire up your Linux system. In |
| 2421 |
this chapter we step you through the process of configuring this bootloader to |
| 2422 |
your needs. |
| 2423 |
</abstract> |
| 2424 |
<include href="hb-install-sparc-bootloader.xml"/> |
| 2425 |
</chapter> |
| 2426 |
|
| 2427 |
<chapter> |
| 2428 |
<title>Finalizing your Gentoo Installation</title> |
| 2429 |
<abstract> |
| 2430 |
You're almost done. We'll just create one (or more) users for your |
| 2431 |
system and (optionally) install prebuilt packages. |
| 2432 |
</abstract> |
| 2433 |
<include href="hb-install-finalise.xml"/> |
| 2434 |
</chapter> |
| 2435 |
|
| 2436 |
<chapter> |
| 2437 |
<title>Where to go from here?</title> |
| 2438 |
<abstract> |
| 2439 |
Now you have your Gentoo system, but what's next? |
| 2440 |
</abstract> |
| 2441 |
<include href="hb-install-next.xml"/> |
| 2442 |
</chapter> |
| 2443 |
</part> |
| 2444 |
|
| 2445 |
<part> |
| 2446 |
<title>Working with Gentoo</title> |
| 2447 |
<abstract> |
| 2448 |
Learn how to work with Gentoo: installing software, altering variables, changing |
| 2449 |
Portage behaviour etc. |
| 2450 |
</abstract> |
| 2451 |
|
| 2452 |
<chapter> |
| 2453 |
<title>A Portage Introduction</title> |
| 2454 |
<abstract> |
| 2455 |
This chapter explains the "simple" steps a user definitely needs to know to |
| 2456 |
maintain the software on his system. |
| 2457 |
</abstract> |
| 2458 |
<include href="../hb-working-portage.xml"/> |
| 2459 |
</chapter> |
| 2460 |
|
| 2461 |
<chapter> |
| 2462 |
<title>USE flags</title> |
| 2463 |
<abstract> |
| 2464 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
| 2465 |
work with USE-flags and understand how USE-flags interact with your system. |
| 2466 |
</abstract> |
| 2467 |
<include href="../hb-working-use.xml"/> |
| 2468 |
</chapter> |
| 2469 |
|
| 2470 |
<chapter> |
| 2471 |
<title>Portage Features</title> |
| 2472 |
<abstract> |
| 2473 |
Discover the features Portage has, such as support for distributed compiling, |
| 2474 |
ccache and more. |
| 2475 |
</abstract> |
| 2476 |
<include href="../hb-working-features.xml"/> |
| 2477 |
</chapter> |
| 2478 |
|
| 2479 |
<chapter> |
| 2480 |
<title>Initscripts</title> |
| 2481 |
<abstract> |
| 2482 |
Gentoo uses a special initscript format which, amongst other features, allows |
| 2483 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
| 2484 |
these aspects and explains how to deal with these scripts. |
| 2485 |
</abstract> |
| 2486 |
<include href="../hb-working-rcscripts.xml"/> |
| 2487 |
</chapter> |
| 2488 |
|
| 2489 |
<chapter> |
| 2490 |
<title>Environment Variables</title> |
| 2491 |
<abstract> |
| 2492 |
With Gentoo you can easily manage the environment variables for your system. |
| 2493 |
This chapter explains how you do that, and also describes frequently used |
| 2494 |
variables. |
| 2495 |
</abstract> |
| 2496 |
<include href="../hb-working-variables.xml"/> |
| 2497 |
</chapter> |
| 2498 |
</part> |
| 2499 |
|
| 2500 |
<part> |
| 2501 |
<title>Working with Portage</title> |
| 2502 |
<abstract> |
| 2503 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
| 2504 |
Software Management Tool. |
| 2505 |
</abstract> |
| 2506 |
|
| 2507 |
<chapter> |
| 2508 |
<title>Files and Directories</title> |
| 2509 |
<abstract> |
| 2510 |
Once you want to know Portage in-depth you need to know where it stores its |
| 2511 |
files and data. |
| 2512 |
</abstract> |
| 2513 |
<include href="../hb-portage-files.xml"/> |
| 2514 |
</chapter> |
| 2515 |
|
| 2516 |
<chapter> |
| 2517 |
<title>Configuring through Variables</title> |
| 2518 |
<abstract> |
| 2519 |
Portage is completely configurable through various variables you can set in the |
| 2520 |
configuration file or as environment variable. |
| 2521 |
</abstract> |
| 2522 |
<include href="../hb-portage-configuration.xml"/> |
| 2523 |
</chapter> |
| 2524 |
|
| 2525 |
<chapter> |
| 2526 |
<title>Mixing Software Branches</title> |
| 2527 |
<abstract> |
| 2528 |
Gentoo provides software separated in several branches, depending on stability |
| 2529 |
and architectural support. "Mixing Software Branches" inform you how these |
| 2530 |
branches can be configured and how you can override this separation |
| 2531 |
individually. |
| 2532 |
</abstract> |
| 2533 |
<include href="../hb-portage-branches.xml"/> |
| 2534 |
</chapter> |
| 2535 |
|
| 2536 |
<chapter> |
| 2537 |
<title>Additional Portage Tools</title> |
| 2538 |
<abstract> |
| 2539 |
Portage comes with a few extra tools that might make your Gentoo experience even |
| 2540 |
better. Read on to discover how to use dispatch-conf and other tools. |
| 2541 |
</abstract> |
| 2542 |
<include href="../hb-portage-tools.xml"/> |
| 2543 |
</chapter> |
| 2544 |
|
| 2545 |
<chapter> |
| 2546 |
<title>Diverting from the Official Tree</title> |
| 2547 |
<abstract> |
| 2548 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
| 2549 |
your own Portage tree, how to synchronise only the categories you want, inject |
| 2550 |
packages and more. |
| 2551 |
</abstract> |
| 2552 |
<include href="../hb-portage-diverttree.xml"/> |
| 2553 |
</chapter> |
| 2554 |
|
| 2555 |
<chapter> |
| 2556 |
<title>The Ebuild Application</title> |
| 2557 |
<abstract> |
| 2558 |
In "The Ebuild Application" you are informed about the steps Portage takes while |
| 2559 |
installing software and how you can do this yourself using the ebuild |
| 2560 |
application. |
| 2561 |
</abstract> |
| 2562 |
<include href="../hb-portage-ebuild.xml"/> |
| 2563 |
</chapter> |
| 2564 |
</part> |
| 2565 |
|
| 2566 |
<part> |
| 2567 |
<title>Gentoo Network Configuration</title> |
| 2568 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
| 2569 |
|
| 2570 |
<chapter> |
| 2571 |
<title>Getting Started</title> |
| 2572 |
<abstract> |
| 2573 |
A guide to quickly get your network interface up and running in most common |
| 2574 |
environments. |
| 2575 |
</abstract> |
| 2576 |
<include href="../hb-net-start.xml"/> |
| 2577 |
</chapter> |
| 2578 |
|
| 2579 |
<chapter> |
| 2580 |
<title>Advanced Configuration</title> |
| 2581 |
<abstract> |
| 2582 |
Here we learn about how the configuration works - you need to know this |
| 2583 |
before we learn about modular networking. |
| 2584 |
</abstract> |
| 2585 |
<include href="../hb-net-advanced.xml"/> |
| 2586 |
</chapter> |
| 2587 |
|
| 2588 |
<chapter> |
| 2589 |
<title>Modular Networking</title> |
| 2590 |
<abstract> |
| 2591 |
Gentoo provides you flexible networking - here you are told about choosing |
| 2592 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
| 2593 |
</abstract> |
| 2594 |
<include href="../hb-net-modules.xml"/> |
| 2595 |
</chapter> |
| 2596 |
|
| 2597 |
<chapter> |
| 2598 |
<title>Wireless Networking</title> |
| 2599 |
<abstract> |
| 2600 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
| 2601 |
</abstract> |
| 2602 |
<include href="../hb-net-wireless.xml"/> |
| 2603 |
</chapter> |
| 2604 |
|
| 2605 |
<chapter> |
| 2606 |
<title>Adding Functionality</title> |
| 2607 |
<abstract> |
| 2608 |
If you're feeling adventurous, you can add your own functions to networking. |
| 2609 |
</abstract> |
| 2610 |
<include href="../hb-net-functions.xml"/> |
| 2611 |
</chapter> |
| 2612 |
|
| 2613 |
<chapter> |
| 2614 |
<title>Network Management</title> |
| 2615 |
<abstract> |
| 2616 |
For laptop users or people who move their computer around different networks. |
| 2617 |
</abstract> |
| 2618 |
<include href="../hb-net-management.xml"/> |
| 2619 |
</chapter> |
| 2620 |
</part> |
| 2621 |
|
| 2622 |
</book> |
| 2623 |
|
| 2624 |
|
| 2625 |
|
| 2626 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/handbook-x86.xml |
| 2627 |
|
| 2628 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-x86.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 2629 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-x86.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 2630 |
|
| 2631 |
Index: handbook-x86.xml |
| 2632 |
=================================================================== |
| 2633 |
<?xml version='1.0' encoding='UTF-8'?> |
| 2634 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
| 2635 |
|
| 2636 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-x86.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 2637 |
|
| 2638 |
<book link="handbook-x86.xml"> |
| 2639 |
<title>Gentoo Linux 2006.0 x86 Handbook</title> |
| 2640 |
|
| 2641 |
<author title="Author"> |
| 2642 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
| 2643 |
</author> |
| 2644 |
<author title="Author"> |
| 2645 |
<mail link="uberlord@g.o">Roy Marples</mail> |
| 2646 |
</author> |
| 2647 |
<author title="Author"> |
| 2648 |
<mail link="drobbins@g.o">Daniel Robbins</mail> |
| 2649 |
</author> |
| 2650 |
<author title="Author"> |
| 2651 |
<mail link="chouser@g.o">Chris Houser</mail> |
| 2652 |
</author> |
| 2653 |
<author title="Author"> |
| 2654 |
<mail link="jerry@g.o">Jerry Alexandratos</mail> |
| 2655 |
</author> |
| 2656 |
<author title="Gentoo x86 Developer"> |
| 2657 |
<mail link="seemant@g.o">Seemant Kulleen</mail> |
| 2658 |
</author> |
| 2659 |
<author title="Gentoo Alpha Developer"> |
| 2660 |
<mail link="taviso@g.o">Tavis Ormandy</mail> |
| 2661 |
</author><!-- Does not want to be listed on the rendered page |
| 2662 |
<author title="Gentoo Developer"> |
| 2663 |
Aron Griffis |
| 2664 |
</author> |
| 2665 |
--> |
| 2666 |
<author title="Gentoo AMD64 Developer"> |
| 2667 |
<mail link="jhuebel@g.o">Jason Huebel</mail> |
| 2668 |
</author> |
| 2669 |
<author title="Gentoo HPPA developer"> |
| 2670 |
<mail link="gmsoft@g.o">Guy Martin</mail> |
| 2671 |
</author> |
| 2672 |
<author title="Gentoo PPC developer"> |
| 2673 |
<mail link="pvdabeel@g.o">Pieter Van den Abeele</mail> |
| 2674 |
</author> |
| 2675 |
<author title="Gentoo SPARC developer"> |
| 2676 |
<mail link="blademan@g.o">Joe Kallar</mail> |
| 2677 |
</author> |
| 2678 |
<author title="Editor"> |
| 2679 |
<mail link="zhen@g.o">John P. Davis</mail> |
| 2680 |
</author> |
| 2681 |
<author title="Editor">Pierre-Henri Jondot</author> |
| 2682 |
<author title="Editor"> |
| 2683 |
<mail link="stocke2@g.o">Eric Stockbridge</mail> |
| 2684 |
</author> |
| 2685 |
<author title="Editor"> |
| 2686 |
<mail link="rajiv@g.o">Rajiv Manglani</mail> |
| 2687 |
</author> |
| 2688 |
<author title="Editor"> |
| 2689 |
<mail link="seo@g.o">Jungmin Seo</mail> |
| 2690 |
</author> |
| 2691 |
<author title="Editor"> |
| 2692 |
<mail link="zhware@g.o">Stoyan Zhekov</mail> |
| 2693 |
</author> |
| 2694 |
<author title="Editor"> |
| 2695 |
<mail link="jhhudso@g.o">Jared Hudson</mail> |
| 2696 |
</author> |
| 2697 |
<author title="Editor"> |
| 2698 |
<mail link="peitolm@g.o">Colin Morey</mail> |
| 2699 |
</author> |
| 2700 |
<author title="Editor"> |
| 2701 |
<mail link="peesh@g.o">Jorge Paulo</mail> |
| 2702 |
</author> |
| 2703 |
<author title="Editor"> |
| 2704 |
<mail link="carl@g.o">Carl Anderson</mail> |
| 2705 |
</author> |
| 2706 |
<author title="Editor"> |
| 2707 |
<mail link="avenj@g.o">Jon Portnoy</mail> |
| 2708 |
</author> |
| 2709 |
<author title="Editor"> |
| 2710 |
<mail link="klasikahl@g.o">Zack Gilburd</mail> |
| 2711 |
</author> |
| 2712 |
<author title="Editor"> |
| 2713 |
<mail link="jmorgan@g.o">Jack Morgan</mail> |
| 2714 |
</author> |
| 2715 |
<author title="Editor"> |
| 2716 |
<mail link="bennyc@g.o">Benny Chuang</mail> |
| 2717 |
</author> |
| 2718 |
<author title="Editor"> |
| 2719 |
<mail link="erwin@g.o">Erwin</mail> |
| 2720 |
</author> |
| 2721 |
<author title="Editor"> |
| 2722 |
<mail link="kumba@g.o">Joshua Kinard</mail> |
| 2723 |
</author> |
| 2724 |
<author title="Editor"> |
| 2725 |
<mail link="dertobi123@g.o">Tobias Scherbaum</mail> |
| 2726 |
</author> |
| 2727 |
<author title="Editor"> |
| 2728 |
<mail link="neysx@g.o">Xavier Neys</mail> |
| 2729 |
</author> |
| 2730 |
<author title="Reviewer"> |
| 2731 |
<mail link="g2boojum@g.o">Grant Goodyear</mail> |
| 2732 |
</author> |
| 2733 |
<author title="Reviewer"> |
| 2734 |
<mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
| 2735 |
</author> |
| 2736 |
<author title="Reviewer"> |
| 2737 |
<mail link="spyderous@g.o">Donnie Berkholz</mail> |
| 2738 |
</author> |
| 2739 |
<author title="Reviewer"> |
| 2740 |
<mail link="antifa@g.o">Ken Nowack</mail> |
| 2741 |
</author> |
| 2742 |
<author title="Contributor"> |
| 2743 |
<mail link="pylon@g.o">Lars Weiler</mail> |
| 2744 |
</author> |
| 2745 |
|
| 2746 |
<abstract> |
| 2747 |
This is the Gentoo Handbook, an effort to centralise Gentoo/Linux information. |
| 2748 |
This handbook contains the installation instructions for a networkless |
| 2749 |
installation on x86 systems and parts about working with Gentoo and Portage. |
| 2750 |
</abstract> |
| 2751 |
|
| 2752 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 2753 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 2754 |
<license/> |
| 2755 |
|
| 2756 |
<version>5.2</version> |
| 2757 |
<date>2005-10-13</date> |
| 2758 |
|
| 2759 |
<part> |
| 2760 |
<title>Installing Gentoo</title> |
| 2761 |
<abstract> |
| 2762 |
In this part you learn how to install Gentoo on your system. |
| 2763 |
</abstract> |
| 2764 |
|
| 2765 |
<chapter> |
| 2766 |
<title>About the Gentoo Linux Installation</title> |
| 2767 |
<abstract> |
| 2768 |
Users not familiar with Gentoo do not always know that choice is what |
| 2769 |
Gentoo is all about. |
| 2770 |
</abstract> |
| 2771 |
<include href="hb-install-about.xml"/> |
| 2772 |
</chapter> |
| 2773 |
|
| 2774 |
<chapter> |
| 2775 |
<title>Booting the Universal Installation CD</title> |
| 2776 |
<abstract> |
| 2777 |
Using our Universal Installation CD you can boot up your system into a running |
| 2778 |
environment that allows you to install Gentoo. |
| 2779 |
</abstract> |
| 2780 |
<include href="hb-install-x86-medium.xml"/> |
| 2781 |
</chapter> |
| 2782 |
|
| 2783 |
<chapter> |
| 2784 |
<title>Configuring your Network</title> |
| 2785 |
<abstract> |
| 2786 |
If you need networking, this is the place where the network (and Internet |
| 2787 |
connection) is configured. |
| 2788 |
</abstract> |
| 2789 |
<include href="hb-install-network.xml"/> |
| 2790 |
</chapter> |
| 2791 |
|
| 2792 |
<chapter> |
| 2793 |
<title>Preparing the Disks</title> |
| 2794 |
<abstract> |
| 2795 |
To be able to install Gentoo, you must create the necessary partitions. |
| 2796 |
This chapter describes how to partition a disk for future usage. |
| 2797 |
</abstract> |
| 2798 |
<include href="hb-install-x86-disk.xml"/> |
| 2799 |
</chapter> |
| 2800 |
|
| 2801 |
<chapter> |
| 2802 |
<title>Installing the Gentoo Installation Files</title> |
| 2803 |
<abstract> |
| 2804 |
In this chapter we describe how you extract a stage3 file and |
| 2805 |
how to configure Portage. |
| 2806 |
</abstract> |
| 2807 |
<include href="hb-install-stage.xml"/> |
| 2808 |
</chapter> |
| 2809 |
|
| 2810 |
<chapter> |
| 2811 |
<title>Chrooting into the Gentoo Base System</title> |
| 2812 |
<abstract> |
| 2813 |
Now that the stage3 file is extracted, we chroot into the new system and |
| 2814 |
modify the USE variable. |
| 2815 |
</abstract> |
| 2816 |
<include href="hb-install-system.xml"/> |
| 2817 |
</chapter> |
| 2818 |
|
| 2819 |
<chapter> |
| 2820 |
<title>Configuring the Kernel</title> |
| 2821 |
<abstract> |
| 2822 |
The Linux kernel is the core of every distribution. This chapter |
| 2823 |
explains how to configure your kernel. |
| 2824 |
</abstract> |
| 2825 |
<include href="hb-install-x86-kernel.xml"/> |
| 2826 |
</chapter> |
| 2827 |
|
| 2828 |
<chapter> |
| 2829 |
<title>Configuring your System</title> |
| 2830 |
<abstract> |
| 2831 |
You need to edit some important configuration files. In this chapter |
| 2832 |
you receive an overview of these files and an explanation on how to |
| 2833 |
proceed. |
| 2834 |
</abstract> |
| 2835 |
<include href="hb-install-config.xml"/> |
| 2836 |
</chapter> |
| 2837 |
|
| 2838 |
<chapter> |
| 2839 |
<title>Installing Necessary System Tools</title> |
| 2840 |
<abstract> |
| 2841 |
As mentioned before, Gentoo is about choices. In this chapter we help you |
| 2842 |
choose and install some important tools. |
| 2843 |
</abstract> |
| 2844 |
<include href="hb-install-tools.xml"/> |
| 2845 |
</chapter> |
| 2846 |
|
| 2847 |
<chapter> |
| 2848 |
<title>Configuring the Bootloader</title> |
| 2849 |
<abstract> |
| 2850 |
Several bootloaders exist for the x86 architecture. Each one of them has its |
| 2851 |
own way of configuration. We step you through the process of configuring a |
| 2852 |
bootloader to your needs. |
| 2853 |
</abstract> |
| 2854 |
<include href="hb-install-x86-bootloader.xml"/> |
| 2855 |
</chapter> |
| 2856 |
|
| 2857 |
<chapter> |
| 2858 |
<title>Finalizing your Gentoo Installation</title> |
| 2859 |
<abstract> |
| 2860 |
You're almost done. We'll just create one (or more) users for your |
| 2861 |
system and (optionally) install prebuilt packages. |
| 2862 |
</abstract> |
| 2863 |
<include href="hb-install-finalise.xml"/> |
| 2864 |
</chapter> |
| 2865 |
|
| 2866 |
<chapter> |
| 2867 |
<title>Where to go from here?</title> |
| 2868 |
<abstract> |
| 2869 |
Now you have your Gentoo system, but what's next? |
| 2870 |
</abstract> |
| 2871 |
<include href="hb-install-next.xml"/> |
| 2872 |
</chapter> |
| 2873 |
</part> |
| 2874 |
|
| 2875 |
<part> |
| 2876 |
<title>Working with Gentoo</title> |
| 2877 |
<abstract> |
| 2878 |
Learn how to work with Gentoo: installing software, altering variables, changing |
| 2879 |
Portage behaviour etc. |
| 2880 |
</abstract> |
| 2881 |
|
| 2882 |
<chapter> |
| 2883 |
<title>A Portage Introduction</title> |
| 2884 |
<abstract> |
| 2885 |
This chapter explains the "simple" steps a user definitely needs to know to |
| 2886 |
maintain the software on his system. |
| 2887 |
</abstract> |
| 2888 |
<include href="../hb-working-portage.xml"/> |
| 2889 |
</chapter> |
| 2890 |
|
| 2891 |
<chapter> |
| 2892 |
<title>USE flags</title> |
| 2893 |
<abstract> |
| 2894 |
USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
| 2895 |
work with USE-flags and understand how USE-flags interact with your system. |
| 2896 |
</abstract> |
| 2897 |
<include href="../hb-working-use.xml"/> |
| 2898 |
</chapter> |
| 2899 |
|
| 2900 |
<chapter> |
| 2901 |
<title>Portage Features</title> |
| 2902 |
<abstract> |
| 2903 |
Discover the features Portage has, such as support for distributed compiling, |
| 2904 |
ccache and more. |
| 2905 |
</abstract> |
| 2906 |
<include href="../hb-working-features.xml"/> |
| 2907 |
</chapter> |
| 2908 |
|
| 2909 |
<chapter> |
| 2910 |
<title>Initscripts</title> |
| 2911 |
<abstract> |
| 2912 |
Gentoo uses a special initscript format which, amongst other features, allows |
| 2913 |
dependency-driven decisions and virtual initscripts. This chapter explains all |
| 2914 |
these aspects and explains how to deal with these scripts. |
| 2915 |
</abstract> |
| 2916 |
<include href="../hb-working-rcscripts.xml"/> |
| 2917 |
</chapter> |
| 2918 |
|
| 2919 |
<chapter> |
| 2920 |
<title>Environment Variables</title> |
| 2921 |
<abstract> |
| 2922 |
With Gentoo you can easily manage the environment variables for your system. |
| 2923 |
This chapter explains how you do that, and also describes frequently used |
| 2924 |
variables. |
| 2925 |
</abstract> |
| 2926 |
<include href="../hb-working-variables.xml"/> |
| 2927 |
</chapter> |
| 2928 |
</part> |
| 2929 |
|
| 2930 |
<part> |
| 2931 |
<title>Working with Portage</title> |
| 2932 |
<abstract> |
| 2933 |
"Working with Portage" provides an in-depth coverage of Portage, Gentoo's |
| 2934 |
Software Management Tool. |
| 2935 |
</abstract> |
| 2936 |
|
| 2937 |
<chapter> |
| 2938 |
<title>Files and Directories</title> |
| 2939 |
<abstract> |
| 2940 |
Once you want to know Portage in-depth you need to know where it stores its |
| 2941 |
files and data. |
| 2942 |
</abstract> |
| 2943 |
<include href="../hb-portage-files.xml"/> |
| 2944 |
</chapter> |
| 2945 |
|
| 2946 |
<chapter> |
| 2947 |
<title>Configuring through Variables</title> |
| 2948 |
<abstract> |
| 2949 |
Portage is completely configurable through various variables you can set in the |
| 2950 |
configuration file or as environment variable. |
| 2951 |
</abstract> |
| 2952 |
<include href="../hb-portage-configuration.xml"/> |
| 2953 |
</chapter> |
| 2954 |
|
| 2955 |
<chapter> |
| 2956 |
<title>Mixing Software Branches</title> |
| 2957 |
<abstract> |
| 2958 |
Gentoo provides software separated in several branches, depending on stability |
| 2959 |
and architectural support. "Mixing Software Branches" inform you how these |
| 2960 |
branches can be configured and how you can override this separation |
| 2961 |
individually. |
| 2962 |
</abstract> |
| 2963 |
<include href="../hb-portage-branches.xml"/> |
| 2964 |
</chapter> |
| 2965 |
|
| 2966 |
<chapter> |
| 2967 |
<title>Additional Portage Tools</title> |
| 2968 |
<abstract> |
| 2969 |
Portage comes with a few extra tools that might make your Gentoo experience even |
| 2970 |
better. Read on to discover how to use dispatch-conf and other tools. |
| 2971 |
</abstract> |
| 2972 |
<include href="../hb-portage-tools.xml"/> |
| 2973 |
</chapter> |
| 2974 |
|
| 2975 |
<chapter> |
| 2976 |
<title>Diverting from the Official Tree</title> |
| 2977 |
<abstract> |
| 2978 |
"Diverting from the Official Tree" gives you some tips and tricks on how to use |
| 2979 |
your own Portage tree, how to synchronise only the categories you want, inject |
| 2980 |
packages and more. |
| 2981 |
</abstract> |
| 2982 |
<include href="../hb-portage-diverttree.xml"/> |
| 2983 |
</chapter> |
| 2984 |
|
| 2985 |
<chapter> |
| 2986 |
<title>The Ebuild Application</title> |
| 2987 |
<abstract> |
| 2988 |
In "The Ebuild Application" you are informed about the steps Portage takes while |
| 2989 |
installing software and how you can do this yourself using the ebuild |
| 2990 |
application. |
| 2991 |
</abstract> |
| 2992 |
<include href="../hb-portage-ebuild.xml"/> |
| 2993 |
</chapter> |
| 2994 |
</part> |
| 2995 |
|
| 2996 |
<part> |
| 2997 |
<title>Gentoo Network Configuration</title> |
| 2998 |
<abstract>A comprehensive guide to Networking in Gentoo.</abstract> |
| 2999 |
|
| 3000 |
<chapter> |
| 3001 |
<title>Getting Started</title> |
| 3002 |
<abstract> |
| 3003 |
A guide to quickly get your network interface up and running in most common |
| 3004 |
environments. |
| 3005 |
</abstract> |
| 3006 |
<include href="../hb-net-start.xml"/> |
| 3007 |
</chapter> |
| 3008 |
|
| 3009 |
<chapter> |
| 3010 |
<title>Advanced Configuration</title> |
| 3011 |
<abstract> |
| 3012 |
Here we learn about how the configuration works - you need to know this |
| 3013 |
before we learn about modular networking. |
| 3014 |
</abstract> |
| 3015 |
<include href="../hb-net-advanced.xml"/> |
| 3016 |
</chapter> |
| 3017 |
|
| 3018 |
<chapter> |
| 3019 |
<title>Modular Networking</title> |
| 3020 |
<abstract> |
| 3021 |
Gentoo provides you flexible networking - here you are told about choosing |
| 3022 |
different DHCP clients, setting up bonding, bridging, VLANs and more. |
| 3023 |
</abstract> |
| 3024 |
<include href="../hb-net-modules.xml"/> |
| 3025 |
</chapter> |
| 3026 |
|
| 3027 |
<chapter> |
| 3028 |
<title>Wireless Networking</title> |
| 3029 |
<abstract> |
| 3030 |
Wireless isn't straight-forward. Hopefully we'll get you working! |
| 3031 |
</abstract> |
| 3032 |
<include href="../hb-net-wireless.xml"/> |
| 3033 |
</chapter> |
| 3034 |
|
| 3035 |
<chapter> |
| 3036 |
<title>Adding Functionality</title> |
| 3037 |
<abstract> |
| 3038 |
If you're feeling adventurous, you can add your own functions to networking. |
| 3039 |
</abstract> |
| 3040 |
<include href="../hb-net-functions.xml"/> |
| 3041 |
</chapter> |
| 3042 |
|
| 3043 |
<chapter> |
| 3044 |
<title>Network Management</title> |
| 3045 |
<abstract> |
| 3046 |
For laptop users or people who move their computer around different networks. |
| 3047 |
</abstract> |
| 3048 |
<include href="../hb-net-management.xml"/> |
| 3049 |
</chapter> |
| 3050 |
</part> |
| 3051 |
|
| 3052 |
</book> |
| 3053 |
|
| 3054 |
|
| 3055 |
|
| 3056 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml |
| 3057 |
|
| 3058 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 3059 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 3060 |
|
| 3061 |
Index: hb-install-about.xml |
| 3062 |
=================================================================== |
| 3063 |
<?xml version='1.0' encoding='UTF-8'?> |
| 3064 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 3065 |
|
| 3066 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 3067 |
<!-- See http://creativecommons.org/licenses/by-sa/2.0 --> |
| 3068 |
|
| 3069 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-about.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 3070 |
|
| 3071 |
<sections> |
| 3072 |
|
| 3073 |
<version>5.0</version> |
| 3074 |
<date>2005-08-08</date> |
| 3075 |
|
| 3076 |
<section> |
| 3077 |
<title>Introduction</title> |
| 3078 |
<subsection> |
| 3079 |
<title>Welcome!</title> |
| 3080 |
<body> |
| 3081 |
|
| 3082 |
<p> |
| 3083 |
First of all, <e>welcome</e> to Gentoo. You are about to enter the world |
| 3084 |
of choices and performance. Gentoo is all about choices. When |
| 3085 |
installing Gentoo, this is made clear to you several times -- you can |
| 3086 |
choose how much you want to compile yourself, how to install Gentoo, |
| 3087 |
what system logger you want, etc. |
| 3088 |
</p> |
| 3089 |
|
| 3090 |
<p> |
| 3091 |
Gentoo is a fast, modern metadistribution with a clean and flexible |
| 3092 |
design. Gentoo is built around free software and doesn't hide from its |
| 3093 |
users what is beneath the hood. Portage, the package maintenance system |
| 3094 |
which Gentoo uses, is written in Python, meaning you can easily view and |
| 3095 |
modify the source code. Gentoo's packaging system uses source code |
| 3096 |
(although support for precompiled packages is included too) and |
| 3097 |
configuring Gentoo happens through regular textfiles. In other words, |
| 3098 |
openness everywhere. |
| 3099 |
</p> |
| 3100 |
|
| 3101 |
<p> |
| 3102 |
It is very important that you understand that <e>choices</e> are what |
| 3103 |
makes Gentoo run. We try not to force you onto anything you don't like. |
| 3104 |
If you feel like we do, please <uri |
| 3105 |
link="http://bugs.gentoo.org">bugreport</uri> it. |
| 3106 |
</p> |
| 3107 |
|
| 3108 |
</body> |
| 3109 |
</subsection> |
| 3110 |
<subsection> |
| 3111 |
<title>How is the Installation Structured?</title> |
| 3112 |
<body> |
| 3113 |
|
| 3114 |
<p> |
| 3115 |
The Gentoo Installation can be seen as a 10-step procedure, |
| 3116 |
corresponding to chapters 2 - 11. Every step results in |
| 3117 |
a certain state: |
| 3118 |
</p> |
| 3119 |
|
| 3120 |
<ul> |
| 3121 |
<li> |
| 3122 |
After step 1, you are in a working environment ready to install Gentoo |
| 3123 |
</li> |
| 3124 |
<li> |
| 3125 |
After step 2, your internet connection is prepared in case you need it (this |
| 3126 |
is however optional) |
| 3127 |
</li> |
| 3128 |
<li> |
| 3129 |
After step 3, your hard disks are initialized to house your Gentoo |
| 3130 |
installation |
| 3131 |
</li> |
| 3132 |
<li> |
| 3133 |
After step 4, your installation environment is prepared and you are |
| 3134 |
ready to chroot into the new environment |
| 3135 |
</li> |
| 3136 |
<li> |
| 3137 |
After step 5, core packages, which are the same on all Gentoo |
| 3138 |
installations, are installed |
| 3139 |
</li> |
| 3140 |
<li> |
| 3141 |
After step 6, you have compiled your Linux kernel |
| 3142 |
</li> |
| 3143 |
<li> |
| 3144 |
After step 7, you have written most of your Gentoo system |
| 3145 |
configuration files |
| 3146 |
</li> |
| 3147 |
<li> |
| 3148 |
After step 8, necessary system tools (which you can choose from a nice |
| 3149 |
list) are installed |
| 3150 |
</li> |
| 3151 |
<li> |
| 3152 |
After step 9, your choice of bootloader has been installed and |
| 3153 |
configured and you are logged in into your new Gentoo installation |
| 3154 |
</li> |
| 3155 |
<li> |
| 3156 |
After step 10, your Gentoo Linux environment is ready to be explored |
| 3157 |
</li> |
| 3158 |
</ul> |
| 3159 |
|
| 3160 |
<p> |
| 3161 |
When you are given a certain choice, we try our best to explain what the pros |
| 3162 |
and cons are. We will continue then with a default |
| 3163 |
choice, identified by "Default: " in the title. The other |
| 3164 |
possibilities are marked by "Alternative: ". Do <e>not</e> |
| 3165 |
think that the default is what we recommend. It is however what we |
| 3166 |
believe most users will use. |
| 3167 |
</p> |
| 3168 |
|
| 3169 |
<p> |
| 3170 |
Sometimes you can pursue an optional step. Such steps are marked as |
| 3171 |
"Optional: " and are therefore not needed to install Gentoo. |
| 3172 |
However, some optional steps are dependant on a previous decision you |
| 3173 |
made. We will inform you when this happens, both when you make the |
| 3174 |
decision, and right before the optional step is described. |
| 3175 |
</p> |
| 3176 |
|
| 3177 |
</body> |
| 3178 |
</subsection> |
| 3179 |
<subsection> |
| 3180 |
<title>What are my Options?</title> |
| 3181 |
<body> |
| 3182 |
|
| 3183 |
<p> |
| 3184 |
You can install Gentoo in many different ways. You can download and install from |
| 3185 |
one of our Installation CDs, from an existing distribution, |
| 3186 |
from a bootable CD (such as Knoppix), from a netbooted environment, from a |
| 3187 |
rescue floppy, etc. |
| 3188 |
</p> |
| 3189 |
|
| 3190 |
<p> |
| 3191 |
This document covers the installation using the Universal Installation CD, a |
| 3192 |
bootable CD that contains everything you need to get Gentoo Linux up and |
| 3193 |
running. You can optionally use one of our Package CDs as well to install a |
| 3194 |
complete system in a matter of minutes after having installed the Gentoo base |
| 3195 |
system. |
| 3196 |
</p> |
| 3197 |
|
| 3198 |
<p> |
| 3199 |
This installation approach however does not immediately use the latest version |
| 3200 |
of the available packages; if you want this you should check out the |
| 3201 |
Installation Instructions inside our <uri |
| 3202 |
link="/doc/en/handbook/index.xml">Gentoo Linux Handbooks</uri>. |
| 3203 |
</p> |
| 3204 |
|
| 3205 |
<p> |
| 3206 |
For help on the other installation approaches, |
| 3207 |
please read our <uri link="/doc/en/altinstall.xml">Alternative Installation |
| 3208 |
Guide</uri>. We also provide a <uri |
| 3209 |
link="/doc/en/gentoo-x86-tipsntricks.xml">Gentoo Installation Tips & |
| 3210 |
Tricks</uri> document that might be useful to read as well. If you feel that |
| 3211 |
the current installation instructions are too elaborate, feel free to use our |
| 3212 |
Quick Installation Guide available from our <uri |
| 3213 |
link="/doc/en/index.xml">Documentation Resources</uri> if your architecture |
| 3214 |
has such a document available. |
| 3215 |
</p> |
| 3216 |
|
| 3217 |
</body> |
| 3218 |
</subsection> |
| 3219 |
<subsection> |
| 3220 |
<title>Troubles?</title> |
| 3221 |
<body> |
| 3222 |
|
| 3223 |
<p> |
| 3224 |
If you find a problem in the installation (or in the installation |
| 3225 |
documentation), please check the errata from our <uri |
| 3226 |
link="/proj/en/releng/">Gentoo Release Engineering Project</uri>, |
| 3227 |
visit our <uri link="http://bugs.gentoo.org">bugtracking |
| 3228 |
system</uri> and check if the bug is known. If not, please create a bugreport |
| 3229 |
for it so we can take care of it. Do not be afraid of the developers who are |
| 3230 |
assigned to (your) bugs -- they generally don't eat people. |
| 3231 |
</p> |
| 3232 |
|
| 3233 |
<p> |
| 3234 |
Note though that, although the document you are now reading is |
| 3235 |
architecture-specific, it will contain references to other architectures as |
| 3236 |
well. This is due to the fact that large parts of the Gentoo Handbook use source |
| 3237 |
code that is common for all architectures (to avoid duplication of efforts and |
| 3238 |
starvation of development resources). We will try to keep this to a minimum |
| 3239 |
to avoid confusion. |
| 3240 |
</p> |
| 3241 |
|
| 3242 |
<p> |
| 3243 |
If you are uncertain if the problem is a user-problem (some error you |
| 3244 |
made despite having read the documentation carefully) or a |
| 3245 |
software-problem (some error we made despite having tested the |
| 3246 |
installation/documentation carefully) you are free to join #gentoo on |
| 3247 |
irc.freenode.net. Of course, you are welcome otherwise too :) |
| 3248 |
</p> |
| 3249 |
|
| 3250 |
<p> |
| 3251 |
If you have a question regarding Gentoo, check out our <uri |
| 3252 |
link="/doc/en/faq.xml">Frequently Asked |
| 3253 |
Questions</uri>, available from the <uri |
| 3254 |
link="/doc/en/">Gentoo Documentation</uri>. You can |
| 3255 |
also view the <uri |
| 3256 |
link="http://forums.gentoo.org/viewforum.php?f=40">FAQs</uri> on our |
| 3257 |
<uri link="http://forums.gentoo.org">forums</uri>. If you can't find the answer |
| 3258 |
there ask on #gentoo, our IRC-channel on irc.freenode.net. Yes, several of |
| 3259 |
us are freaks who sit on IRC :-) |
| 3260 |
</p> |
| 3261 |
|
| 3262 |
</body> |
| 3263 |
</subsection> |
| 3264 |
</section> |
| 3265 |
<section> |
| 3266 |
<title>Fast Installation using the Gentoo Reference Platform</title> |
| 3267 |
<subsection> |
| 3268 |
<title>What is the Gentoo Reference Platform?</title> |
| 3269 |
<body> |
| 3270 |
|
| 3271 |
<p> |
| 3272 |
The Gentoo Reference Platform, from now on abbreviated to GRP, is a snapshot of |
| 3273 |
prebuilt packages users (that means you!) can install during the installation |
| 3274 |
of Gentoo to speed up the installation process. The GRP consists of all |
| 3275 |
packages required to have a fully functional Gentoo installation. They are not |
| 3276 |
just the ones you need to have a base installation up to speed in no time, but |
| 3277 |
all lengthier builds (such as KDE, xorg-x11, GNOME, OpenOffice, Mozilla, ...) |
| 3278 |
are available as GRP packages too. |
| 3279 |
</p> |
| 3280 |
|
| 3281 |
<p> |
| 3282 |
However, these prebuilt packages aren't maintained during the lifetime of the |
| 3283 |
Gentoo distribution. They are snapshots released at every Gentoo release and |
| 3284 |
make it possible to have a functional environment in a short amount of time. You |
| 3285 |
can then upgrade your system in the background while working in your Gentoo |
| 3286 |
environment. |
| 3287 |
</p> |
| 3288 |
|
| 3289 |
</body> |
| 3290 |
</subsection> |
| 3291 |
<subsection> |
| 3292 |
<title>How Portage Handles GRP Packages</title> |
| 3293 |
<body> |
| 3294 |
|
| 3295 |
<p> |
| 3296 |
Your Portage tree - the collection of <e>ebuilds</e> (files that contain all |
| 3297 |
information about a package, such as its description, homepage, sourcecode URLs, |
| 3298 |
compilation instructions, dependencies, etc.) - must be synchronised with the |
| 3299 |
GRP set: the versions of the available ebuilds and their accompanying GRP |
| 3300 |
packages must match. |
| 3301 |
</p> |
| 3302 |
|
| 3303 |
<p> |
| 3304 |
For this reason you can only benefit from the GRP packages Gentoo provides while |
| 3305 |
performing the current installation approach. GRP is not available for those |
| 3306 |
interested in performing an installation using the latest versions of all |
| 3307 |
available packages. |
| 3308 |
</p> |
| 3309 |
|
| 3310 |
</body> |
| 3311 |
</subsection> |
| 3312 |
<subsection> |
| 3313 |
<title>Is GRP Available?</title> |
| 3314 |
<body> |
| 3315 |
|
| 3316 |
<p> |
| 3317 |
Not all architectures provide GRP packages. That doesn't mean GRP isn't |
| 3318 |
supported on the other architectures, but it means that we don't have the |
| 3319 |
resources to build and test the GRP packages. |
| 3320 |
</p> |
| 3321 |
|
| 3322 |
<p> |
| 3323 |
At present we provide GRP packages for the following architectures: |
| 3324 |
</p> |
| 3325 |
|
| 3326 |
<ul> |
| 3327 |
<li> |
| 3328 |
The <b>x86</b> architecture (x86, athlon-xp, pentium3, pentium4) |
| 3329 |
Note: The x86 packages (packages-x86-2006.0.iso) are available on |
| 3330 |
our mirrors, while pentium3, pentium4 and athlon-xp are only available |
| 3331 |
via bittorrent. |
| 3332 |
</li> |
| 3333 |
<li> |
| 3334 |
The <b>amd64</b> architecture (amd64) |
| 3335 |
</li> |
| 3336 |
<li> |
| 3337 |
The <b>sparc</b> architecture (sparc64) |
| 3338 |
</li> |
| 3339 |
<li> |
| 3340 |
The <b>ppc</b> architecture (G3, G4, G5) |
| 3341 |
</li> |
| 3342 |
<li> |
| 3343 |
The <b>alpha</b> architecture |
| 3344 |
</li> |
| 3345 |
</ul> |
| 3346 |
|
| 3347 |
<p> |
| 3348 |
If your architecture (or subarchitecture) isn't on this list, you are not |
| 3349 |
able to opt for a GRP installation. |
| 3350 |
</p> |
| 3351 |
|
| 3352 |
<p> |
| 3353 |
Now that this introduction is over, let's continue with <uri |
| 3354 |
link="?part=1&chap=2">Booting the Universal Installation CD</uri>. |
| 3355 |
</p> |
| 3356 |
|
| 3357 |
</body> |
| 3358 |
</subsection> |
| 3359 |
</section> |
| 3360 |
</sections> |
| 3361 |
|
| 3362 |
|
| 3363 |
|
| 3364 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-alpha-bootloader.xml |
| 3365 |
|
| 3366 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-alpha-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 3367 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-alpha-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 3368 |
|
| 3369 |
Index: hb-install-alpha-bootloader.xml |
| 3370 |
=================================================================== |
| 3371 |
<?xml version='1.0' encoding='UTF-8'?> |
| 3372 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 3373 |
|
| 3374 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 3375 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
| 3376 |
|
| 3377 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-alpha-bootloader.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 3378 |
|
| 3379 |
<sections> |
| 3380 |
|
| 3381 |
<version>5.1</version> |
| 3382 |
<date>2006-01-19</date> |
| 3383 |
|
| 3384 |
<section> |
| 3385 |
<title>Making your Choice</title> |
| 3386 |
<subsection> |
| 3387 |
<title>Introduction</title> |
| 3388 |
<body> |
| 3389 |
|
| 3390 |
<p> |
| 3391 |
Now that your kernel is configured and compiled and the necessary system |
| 3392 |
configuration files are filled in correctly, it is time to install a |
| 3393 |
program that will fire up your kernel when you start the system. Such a |
| 3394 |
program is called a <e>bootloader</e>. |
| 3395 |
</p> |
| 3396 |
|
| 3397 |
<p> |
| 3398 |
Several bootloaders exist for Linux/Alpha. You must choose one of the supported |
| 3399 |
bootloaders, not all. You have the choice between <uri link="#aboot">aBoot</uri> |
| 3400 |
and <uri link="#milo">MILO</uri>. |
| 3401 |
</p> |
| 3402 |
|
| 3403 |
</body> |
| 3404 |
</subsection> |
| 3405 |
</section> |
| 3406 |
<section id="aboot"> |
| 3407 |
<title>Default: Using aboot</title> |
| 3408 |
<body> |
| 3409 |
|
| 3410 |
<p> |
| 3411 |
We first install aboot on our system. Of course we use <c>emerge</c> to |
| 3412 |
do so: |
| 3413 |
</p> |
| 3414 |
|
| 3415 |
<pre caption = "Installing aboot"> |
| 3416 |
# <i>emerge --usepkg aboot</i> |
| 3417 |
</pre> |
| 3418 |
|
| 3419 |
<p> |
| 3420 |
The next step is to make our bootdisk bootable. This will start |
| 3421 |
<c>aboot</c> when you boot your system. We make our bootdisk bootable by |
| 3422 |
writing the <c>aboot</c> bootloader to the start of the disk. |
| 3423 |
</p> |
| 3424 |
|
| 3425 |
<pre caption = "Making your bootdisk bootable"> |
| 3426 |
# <i>swriteboot -f3 /dev/sda /boot/bootlx</i> |
| 3427 |
# <i>abootconf /dev/sda 2</i> |
| 3428 |
</pre> |
| 3429 |
|
| 3430 |
<note> |
| 3431 |
If you use a different partitioning scheme than the one we use |
| 3432 |
throughout this chapter, you have to change the commands accordingly. |
| 3433 |
Please read the appropriate manual pages (<c>man 8 swriteboot</c> and |
| 3434 |
<c>man 8 abootconf</c>). Also, if your root filesystem uses the JFS filesystem, |
| 3435 |
make sure to pass the <c>ro</c> kernel option so that it can replay its log |
| 3436 |
before it gets mounted read-write. |
| 3437 |
</note> |
| 3438 |
|
| 3439 |
<p> |
| 3440 |
Additionally, you can make Gentoo boot automatically by setting up the |
| 3441 |
aboot configuration file and some SRM variables. You can try setting |
| 3442 |
these variables from Linux, but it may be easier to do so from the SRM |
| 3443 |
console itself. |
| 3444 |
</p> |
| 3445 |
|
| 3446 |
<pre caption = "Automatically booting Gentoo"> |
| 3447 |
# <i>echo '0:2/boot/vmlinux.gz root=/dev/sda2' > /etc/aboot.conf</i> |
| 3448 |
# <i>cd /proc/srm_environment/named_variables</i> |
| 3449 |
# <i>echo -n 0 > boot_osflags</i> |
| 3450 |
# <i>echo -n '' > boot_file</i> |
| 3451 |
# <i>echo -n 'BOOT' > auto_action</i> |
| 3452 |
# <i>echo -n 'dkc100' > bootdef_dev</i> |
| 3453 |
<comment>(Substitute dkc100 with whatever your boot device is)</comment> |
| 3454 |
</pre> |
| 3455 |
|
| 3456 |
<p> |
| 3457 |
If you need to get into the SRM console again in the future (to recover |
| 3458 |
your Gentoo install, play with some variables, or whatever), just hit |
| 3459 |
CTRL+C to abort the automatic loading process. |
| 3460 |
</p> |
| 3461 |
|
| 3462 |
<p> |
| 3463 |
If you're installing using a serial console, don't forget to include |
| 3464 |
the serial console boot flag in <path>aboot.conf</path>. See |
| 3465 |
<path>/etc/aboot.conf.example</path> for some further information. |
| 3466 |
</p> |
| 3467 |
|
| 3468 |
<p> |
| 3469 |
Aboot is now configured and ready to use. Continue with <uri |
| 3470 |
link="#reboot">Rebooting the System</uri>. |
| 3471 |
</p> |
| 3472 |
|
| 3473 |
</body> |
| 3474 |
</section> |
| 3475 |
<section id="milo"> |
| 3476 |
<title>Alternative: Using MILO</title> |
| 3477 |
<body> |
| 3478 |
|
| 3479 |
<p> |
| 3480 |
Before continuing, you should decide on how to use MILO. In this |
| 3481 |
section, we will assume that you want to make a MILO boot floppy. If you |
| 3482 |
are going to boot from an MS-DOS partition on your hard disk, you should |
| 3483 |
amend the commands appropriately. |
| 3484 |
</p> |
| 3485 |
|
| 3486 |
<p> |
| 3487 |
To install MILO, we use <c>emerge</c>. |
| 3488 |
</p> |
| 3489 |
|
| 3490 |
<pre caption = "Installing MILO"> |
| 3491 |
# <i>emerge --usepkg milo</i> |
| 3492 |
</pre> |
| 3493 |
|
| 3494 |
<p> |
| 3495 |
After MILO has been installed, the MILO images should be in |
| 3496 |
<path>/opt/milo</path>. The commands below make a bootfloppy for use |
| 3497 |
with MILO. Remember to use the correct image for your Alpha-system. |
| 3498 |
</p> |
| 3499 |
|
| 3500 |
<pre caption = "Installing MILO on a floppy"> |
| 3501 |
<comment>(First insert a blank floppy)</comment> |
| 3502 |
# <i>fdformat /dev/fd0</i> |
| 3503 |
# <i>mformat a:</i> |
| 3504 |
# <i>mcopy /opt/milo/milo-2.2-18-gentoo-ruffian a:\milo</i> |
| 3505 |
# <i>mcopy /opt/milo/linload.exe a:\lilnload.exe</i> |
| 3506 |
<comment>(Only if you have a Ruffian:</comment> |
| 3507 |
# <i>mcopy /opt/milo/ldmilo.exe a:\ldmilo.exe</i> |
| 3508 |
<comment>)</comment> |
| 3509 |
# <i>echo -ne '\125\252' | dd of=/dev/fd0 bs=1 seek=510 count=2</i> |
| 3510 |
</pre> |
| 3511 |
|
| 3512 |
<p> |
| 3513 |
Your MILO boot floppy is now ready to boot Gentoo Linux. You may need to |
| 3514 |
set environment variables in your ARCS Firmware to get MILO to start; |
| 3515 |
this is all explained in the <uri |
| 3516 |
link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri> with some examples |
| 3517 |
on common systems, and examples of the commands to use in interactive mode. |
| 3518 |
</p> |
| 3519 |
|
| 3520 |
<p> |
| 3521 |
Not reading the <uri link="http://tldp.org/HOWTO/MILO-HOWTO/">MILO-HOWTO</uri> |
| 3522 |
is a <e>bad</e> idea. |
| 3523 |
</p> |
| 3524 |
|
| 3525 |
<p> |
| 3526 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
| 3527 |
</p> |
| 3528 |
|
| 3529 |
</body> |
| 3530 |
</section> |
| 3531 |
<section id="reboot"> |
| 3532 |
<title>Rebooting the System</title> |
| 3533 |
<subsection> |
| 3534 |
<body> |
| 3535 |
|
| 3536 |
<p> |
| 3537 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
| 3538 |
that one magical command you have been waiting for: <c>reboot</c>. |
| 3539 |
</p> |
| 3540 |
|
| 3541 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
| 3542 |
# <i>exit</i> |
| 3543 |
cdimage ~# <i>cd</i> |
| 3544 |
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
| 3545 |
cdimage ~# <i>reboot</i> |
| 3546 |
</pre> |
| 3547 |
|
| 3548 |
<p> |
| 3549 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
| 3550 |
booted again instead of your new Gentoo system. |
| 3551 |
</p> |
| 3552 |
|
| 3553 |
<p> |
| 3554 |
Once rebooted in your Gentoo installation, finish up with <uri |
| 3555 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
| 3556 |
</p> |
| 3557 |
|
| 3558 |
</body> |
| 3559 |
</subsection> |
| 3560 |
</section> |
| 3561 |
|
| 3562 |
</sections> |
| 3563 |
|
| 3564 |
|
| 3565 |
|
| 3566 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-alpha-disk.xml |
| 3567 |
|
| 3568 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-alpha-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 3569 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-alpha-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 3570 |
|
| 3571 |
Index: hb-install-alpha-disk.xml |
| 3572 |
=================================================================== |
| 3573 |
<?xml version='1.0' encoding='UTF-8'?> |
| 3574 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 3575 |
|
| 3576 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 3577 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 3578 |
|
| 3579 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-alpha-disk.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 3580 |
|
| 3581 |
<sections> |
| 3582 |
|
| 3583 |
<version>5.1</version> |
| 3584 |
<date>2005-08-25</date> |
| 3585 |
|
| 3586 |
<section> |
| 3587 |
<title>Introduction to Block Devices</title> |
| 3588 |
<subsection> |
| 3589 |
<title>Block Devices</title> |
| 3590 |
<body> |
| 3591 |
|
| 3592 |
<p> |
| 3593 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
| 3594 |
and Linux in general, including Linux filesystems, partitions and block devices. |
| 3595 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
| 3596 |
you'll be guided through the process of setting up partitions and filesystems |
| 3597 |
for your Gentoo Linux installation. |
| 3598 |
</p> |
| 3599 |
|
| 3600 |
<p> |
| 3601 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
| 3602 |
probably the one that represents the first SCSI HD in a Linux system, namely |
| 3603 |
<path>/dev/sda</path>. |
| 3604 |
</p> |
| 3605 |
|
| 3606 |
<p> |
| 3607 |
The block devices above represent an abstract interface to the disk. User |
| 3608 |
programs can use these block devices to interact with your disk without worrying |
| 3609 |
about whether your drives are IDE, SCSI or something else. The program can |
| 3610 |
simply address the storage on the disk as a bunch of contiguous, |
| 3611 |
randomly-accessible 512-byte blocks. |
| 3612 |
</p> |
| 3613 |
|
| 3614 |
</body> |
| 3615 |
</subsection> |
| 3616 |
<subsection> |
| 3617 |
<title>Slices</title> |
| 3618 |
<body> |
| 3619 |
|
| 3620 |
<p> |
| 3621 |
Although it is theoretically possible to use a full disk to house your Linux |
| 3622 |
system, this is almost never done in practice. Instead, full disk block devices |
| 3623 |
are split up in smaller, more manageable block devices. On Alpha systems, |
| 3624 |
these are called <e>slices</e>. |
| 3625 |
</p> |
| 3626 |
|
| 3627 |
</body> |
| 3628 |
</subsection> |
| 3629 |
</section> |
| 3630 |
<section> |
| 3631 |
<title>Designing a Partitioning Scheme</title> |
| 3632 |
<subsection> |
| 3633 |
<title>Default Partitioning Scheme</title> |
| 3634 |
<body> |
| 3635 |
|
| 3636 |
<p> |
| 3637 |
As an example we use the following slice layout: |
| 3638 |
</p> |
| 3639 |
|
| 3640 |
<table> |
| 3641 |
<tr> |
| 3642 |
<th>Slice</th> |
| 3643 |
<th>Description</th> |
| 3644 |
</tr> |
| 3645 |
<tr> |
| 3646 |
<ti><path>/dev/sda1</path></ti> |
| 3647 |
<ti>Swap slice</ti> |
| 3648 |
</tr> |
| 3649 |
<tr> |
| 3650 |
<ti><path>/dev/sda2</path></ti> |
| 3651 |
<ti>Root slice</ti> |
| 3652 |
</tr> |
| 3653 |
<tr> |
| 3654 |
<ti><path>/dev/sda3</path></ti> |
| 3655 |
<ti>Full disk (required)</ti> |
| 3656 |
</tr> |
| 3657 |
</table> |
| 3658 |
|
| 3659 |
|
| 3660 |
<p> |
| 3661 |
If you are interested in knowing how big a partition should be, or even how |
| 3662 |
many partitions (or volumes) you need, read on. Otherwise continue now with |
| 3663 |
<uri link="#fdisk_SRM">Using fdisk to Partition your Disk (SRM only)</uri> |
| 3664 |
or <uri link="#fdisk_ARC">Using fdisk to Partition your Disk (ARC/AlphaBIOS |
| 3665 |
only)</uri>. |
| 3666 |
</p> |
| 3667 |
|
| 3668 |
</body> |
| 3669 |
</subsection> |
| 3670 |
<subsection> |
| 3671 |
<title>How Many and How Big?</title> |
| 3672 |
<body> |
| 3673 |
|
| 3674 |
<p> |
| 3675 |
The number of partitions is highly dependent on your environment. For instance, |
| 3676 |
if you have lots of users, you will most likely want to have your |
| 3677 |
<path>/home</path> separate as it increases security and makes backups easier. |
| 3678 |
If you are installing Gentoo to perform as a mailserver, your |
| 3679 |
<path>/var</path> should be separate as all mails are stored inside |
| 3680 |
<path>/var</path>. A good choice of filesystem will then maximise your |
| 3681 |
performance. Gameservers will have a separate <path>/opt</path> as most gaming |
| 3682 |
servers are installed there. The reason is similar for <path>/home</path>: |
| 3683 |
security and backups. You will definitely want to keep <path>/usr</path> big: |
| 3684 |
not only will it contain the majority of applications, the Portage tree alone |
| 3685 |
takes around 500 Mbyte excluding the various sources that are stored in it. |
| 3686 |
</p> |
| 3687 |
|
| 3688 |
<p> |
| 3689 |
As you can see, it very much depends on what you want to achieve. Separate |
| 3690 |
partitions or volumes have the following advantages: |
| 3691 |
</p> |
| 3692 |
|
| 3693 |
<ul> |
| 3694 |
<li> |
| 3695 |
You can choose the best performing filesystem for each partition or volume |
| 3696 |
</li> |
| 3697 |
<li> |
| 3698 |
Your entire system cannot run out of free space if one defunct tool is |
| 3699 |
continuously writing files to a partition or volume |
| 3700 |
</li> |
| 3701 |
<li> |
| 3702 |
If necessary, file system checks are reduced in time, as multiple checks can |
| 3703 |
be done in parallel (although this advantage is more with multiple disks than |
| 3704 |
it is with multiple partitions) |
| 3705 |
</li> |
| 3706 |
<li> |
| 3707 |
Security can be enhanced by mounting some partitions or volumes read-only, |
| 3708 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
| 3709 |
</li> |
| 3710 |
</ul> |
| 3711 |
|
| 3712 |
<p> |
| 3713 |
However, multiple partitions have one big disadvantage: if not configured |
| 3714 |
properly, you might result in having a system with lots |
| 3715 |
of free space on one partition and none on another. |
| 3716 |
</p> |
| 3717 |
|
| 3718 |
</body> |
| 3719 |
</subsection> |
| 3720 |
</section> |
| 3721 |
<section id="fdisk_SRM"> |
| 3722 |
<title>Using fdisk to Partition your Disk (SRM only)</title> |
| 3723 |
<subsection> |
| 3724 |
<body> |
| 3725 |
|
| 3726 |
<p> |
| 3727 |
The following parts explain how to create the example slice layout described |
| 3728 |
previously, namely: |
| 3729 |
</p> |
| 3730 |
|
| 3731 |
<table> |
| 3732 |
<tr> |
| 3733 |
<th>Slice</th> |
| 3734 |
<th>Description</th> |
| 3735 |
</tr> |
| 3736 |
<tr> |
| 3737 |
<ti><path>/dev/sda1</path></ti> |
| 3738 |
<ti>Swap slice</ti> |
| 3739 |
</tr> |
| 3740 |
<tr> |
| 3741 |
<ti><path>/dev/sda2</path></ti> |
| 3742 |
<ti>Root slice</ti> |
| 3743 |
</tr> |
| 3744 |
<tr> |
| 3745 |
<ti><path>/dev/sda3</path></ti> |
| 3746 |
<ti>Full disk (required)</ti> |
| 3747 |
</tr> |
| 3748 |
</table> |
| 3749 |
|
| 3750 |
<p> |
| 3751 |
Change your slice layout according to your own preference. |
| 3752 |
</p> |
| 3753 |
|
| 3754 |
|
| 3755 |
</body> |
| 3756 |
</subsection> |
| 3757 |
<subsection> |
| 3758 |
<title>Identifying Available Disks</title> |
| 3759 |
<body> |
| 3760 |
|
| 3761 |
<p> |
| 3762 |
To figure out what disks you have running, use the following commands: |
| 3763 |
</p> |
| 3764 |
|
| 3765 |
<pre caption="Identifying available disks"> |
| 3766 |
# <i>dmesg | grep 'drive$'</i> <comment>(For IDE disks)</comment> |
| 3767 |
# <i>dmesg | grep 'scsi'</i> <comment>(For SCSI disks)</comment> |
| 3768 |
</pre> |
| 3769 |
|
| 3770 |
<p> |
| 3771 |
>From this output you should be able to see what disks were detected and their |
| 3772 |
respective <path>/dev</path> entry. In the following parts we assume that the |
| 3773 |
disk is a SCSI disk on <path>/dev/sda</path>. |
| 3774 |
</p> |
| 3775 |
|
| 3776 |
<p> |
| 3777 |
Now fire up <c>fdisk</c>: |
| 3778 |
</p> |
| 3779 |
|
| 3780 |
<pre caption="Starting fdisk"> |
| 3781 |
# <i>fdisk /dev/sda</i> |
| 3782 |
</pre> |
| 3783 |
|
| 3784 |
</body> |
| 3785 |
</subsection> |
| 3786 |
<subsection> |
| 3787 |
<title>Deleting All Slices</title> |
| 3788 |
<body> |
| 3789 |
|
| 3790 |
<p> |
| 3791 |
If your hard drive is completely blank, then you'll have to first create |
| 3792 |
a BSD disklabel. |
| 3793 |
</p> |
| 3794 |
|
| 3795 |
<pre caption="Creating a BSD disklabel"> |
| 3796 |
Command (m for help): <i>b</i> |
| 3797 |
/dev/sda contains no disklabel. |
| 3798 |
Do you want to create a disklabel? (y/n) <i>y</i> |
| 3799 |
<comment>A bunch of drive-specific info will show here</comment> |
| 3800 |
3 partitions: |
| 3801 |
# start end size fstype [fsize bsize cpg] |
| 3802 |
c: 1 5290* 5289* unused 0 0 |
| 3803 |
</pre> |
| 3804 |
|
| 3805 |
<p> |
| 3806 |
We start with deleting all slices <e>except</e> the 'c'-slice (a requirement |
| 3807 |
for using BSD disklabels). The following shows how to delete a slice (in |
| 3808 |
the example we use 'a'). Repeat the process to delete all other slices |
| 3809 |
(again, except the 'c'-slice). |
| 3810 |
</p> |
| 3811 |
|
| 3812 |
<p> |
| 3813 |
Use <c>p</c> to view all existing slices. <c>d</c> is used to delete a slice. |
| 3814 |
</p> |
| 3815 |
|
| 3816 |
<pre caption="Deleting a slice"> |
| 3817 |
BSD disklabel command (m for help): <i>p</i> |
| 3818 |
|
| 3819 |
8 partitions: |
| 3820 |
# start end size fstype [fsize bsize cpg] |
| 3821 |
a: 1 235* 234* 4.2BSD 1024 8192 16 |
| 3822 |
b: 235* 469* 234* swap |
| 3823 |
c: 1 5290* 5289* unused 0 0 |
| 3824 |
d: 469* 2076* 1607* unused 0 0 |
| 3825 |
e: 2076* 3683* 1607* unused 0 0 |
| 3826 |
f: 3683* 5290* 1607* unused 0 0 |
| 3827 |
g: 469* 1749* 1280 4.2BSD 1024 8192 16 |
| 3828 |
h: 1749* 5290* 3541* unused 0 0 |
| 3829 |
|
| 3830 |
BSD disklabel command (m for help): <i>d</i> |
| 3831 |
Partition (a-h): <i>a</i> |
| 3832 |
</pre> |
| 3833 |
|
| 3834 |
<p> |
| 3835 |
After repeating this process for all slices, a listing should show you something |
| 3836 |
similar to this: |
| 3837 |
</p> |
| 3838 |
|
| 3839 |
<pre caption="Viewing an empty scheme"> |
| 3840 |
BSD disklabel command (m for help): <i>p</i> |
| 3841 |
|
| 3842 |
3 partitions: |
| 3843 |
# start end size fstype [fsize bsize cpg] |
| 3844 |
c: 1 5290* 5289* unused 0 0 |
| 3845 |
</pre> |
| 3846 |
|
| 3847 |
</body> |
| 3848 |
</subsection> |
| 3849 |
<subsection> |
| 3850 |
<title>Creating the Swap Slice</title> |
| 3851 |
<body> |
| 3852 |
|
| 3853 |
<p> |
| 3854 |
On Alpha based systems you don't need a separate boot partition. However, the |
| 3855 |
first cylinder cannot be used as the <c>aboot</c> image will be placed there. |
| 3856 |
</p> |
| 3857 |
|
| 3858 |
<p> |
| 3859 |
We will create a swap slice starting at the third cylinder, with a total |
| 3860 |
size of 1 GB. Use <c>n</c> to create a new slice. After creating the slice, |
| 3861 |
we will change its type to <c>1</c> (one), meaning <e>swap</e>. |
| 3862 |
</p> |
| 3863 |
|
| 3864 |
<pre caption="Creating the swap slice"> |
| 3865 |
BSD disklabel command (m for help): <i>n</i> |
| 3866 |
Partition (a-p): <i>a</i> |
| 3867 |
First cylinder (1-5290, default 1): <i>3</i> |
| 3868 |
Last cylinder or +size or +sizeM or +sizeK (3-5290, default 5290): <i>+1024M</i> |
| 3869 |
|
| 3870 |
BSD disklabel command (m for help): <i>t</i> |
| 3871 |
Partition (a-c): <i>a</i> |
| 3872 |
Hex code (type L to list codes): <i>1</i> |
| 3873 |
</pre> |
| 3874 |
|
| 3875 |
<p> |
| 3876 |
After these steps you should see a layout similar to the following: |
| 3877 |
</p> |
| 3878 |
|
| 3879 |
<pre caption="Slice layout after creating the swap slice"> |
| 3880 |
BSD disklabel command (m for help): <i>p</i> |
| 3881 |
|
| 3882 |
3 partitions: |
| 3883 |
# start end size fstype [fsize bsize cpg] |
| 3884 |
a: 3 1003 1001 swap |
| 3885 |
c: 1 5290* 5289* unused 0 0 |
| 3886 |
</pre> |
| 3887 |
|
| 3888 |
</body> |
| 3889 |
</subsection> |
| 3890 |
<subsection> |
| 3891 |
<title>Create the Root Slice</title> |
| 3892 |
<body> |
| 3893 |
|
| 3894 |
<p> |
| 3895 |
We will now create the root slice, starting from the first cylinder <e>after</e> |
| 3896 |
the swap slice. Use the <c>p</c> command to view where the swap slice ends. In |
| 3897 |
our example, this is at 1003, making the root partition start at 1004. |
| 3898 |
</p> |
| 3899 |
|
| 3900 |
<p> |
| 3901 |
Another problem is that there is currently a bug in <c>fdisk</c> making it think |
| 3902 |
the number of available cylinders is one above the real number of cylinders. In |
| 3903 |
other words, when you are asked for the last cylinder, decrease the cylinder |
| 3904 |
number (in this example: 5290) with one. |
| 3905 |
</p> |
| 3906 |
|
| 3907 |
<p> |
| 3908 |
When the partition is created, we change the type to <c>8</c>, for <e>ext2</e>. |
| 3909 |
</p> |
| 3910 |
|
| 3911 |
<pre caption="Creating the root slice"> |
| 3912 |
D disklabel command (m for help): <i>n</i> |
| 3913 |
Partition (a-p): <i>b</i> |
| 3914 |
First cylinder (1-5290, default 1): <i>1004</i> |
| 3915 |
Last cylinder or +size or +sizeM or +sizeK (1004-5290, default 5290): <i>5289</i> |
| 3916 |
|
| 3917 |
BSD disklabel command (m for help): <i>t</i> |
| 3918 |
Partition (a-c): <i>b</i> |
| 3919 |
Hex code (type L to list codes): <i>8</i> |
| 3920 |
</pre> |
| 3921 |
|
| 3922 |
<p> |
| 3923 |
Your slice layout should now be similar to this: |
| 3924 |
</p> |
| 3925 |
|
| 3926 |
<pre caption="Viewing the slice layout"> |
| 3927 |
BSD disklabel command (m for help): <i>p</i> |
| 3928 |
|
| 3929 |
3 partitions: |
| 3930 |
# start end size fstype [fsize bsize cpg] |
| 3931 |
a: 3 1003 1001 swap |
| 3932 |
b: 1004 5289 4286 ext2 |
| 3933 |
c: 1 5290* 5289* unused 0 0 |
| 3934 |
</pre> |
| 3935 |
|
| 3936 |
</body> |
| 3937 |
</subsection> |
| 3938 |
<subsection> |
| 3939 |
<title>Save the Slice Layout and Exit</title> |
| 3940 |
<body> |
| 3941 |
|
| 3942 |
<p> |
| 3943 |
Save <c>fdisk</c> by typing <c>w</c>. This will also save your slice layout. |
| 3944 |
</p> |
| 3945 |
|
| 3946 |
<pre caption="Save and exit fdisk"> |
| 3947 |
Command (m for help): <i>w</i> |
| 3948 |
</pre> |
| 3949 |
|
| 3950 |
<p> |
| 3951 |
Now that your slices are created, you can now continue with <uri |
| 3952 |
link="#filesystems">Creating Filesystems</uri>. |
| 3953 |
</p> |
| 3954 |
|
| 3955 |
</body> |
| 3956 |
</subsection> |
| 3957 |
</section> |
| 3958 |
<section id="fdisk_ARC"> |
| 3959 |
<title>Using fdisk to Partition your Disk (ARC/AlphaBIOS only)</title> |
| 3960 |
<subsection> |
| 3961 |
<body> |
| 3962 |
|
| 3963 |
<p> |
| 3964 |
The following parts explain how to partition the disk with a layout |
| 3965 |
similar to the one described previously, namely: |
| 3966 |
</p> |
| 3967 |
|
| 3968 |
<table> |
| 3969 |
<tr> |
| 3970 |
<th>Partition</th> |
| 3971 |
<th>Description</th> |
| 3972 |
</tr> |
| 3973 |
<tr> |
| 3974 |
<ti><path>/dev/sda1</path></ti> |
| 3975 |
<ti>Boot partition</ti> |
| 3976 |
</tr> |
| 3977 |
<tr> |
| 3978 |
<ti><path>/dev/sda2</path></ti> |
| 3979 |
<ti>Swap partition</ti> |
| 3980 |
</tr> |
| 3981 |
<tr> |
| 3982 |
<ti><path>/dev/sda3</path></ti> |
| 3983 |
<ti>Root partition</ti> |
| 3984 |
</tr> |
| 3985 |
</table> |
| 3986 |
|
| 3987 |
<p> |
| 3988 |
Change your partition layout according to your own preference. |
| 3989 |
</p> |
| 3990 |
|
| 3991 |
</body> |
| 3992 |
</subsection> |
| 3993 |
<subsection> |
| 3994 |
<title>Identifying Available Disks</title> |
| 3995 |
<body> |
| 3996 |
|
| 3997 |
<p> |
| 3998 |
To figure out what disks you have running, use the following commands: |
| 3999 |
</p> |
| 4000 |
|
| 4001 |
<pre caption="Identifying available disks"> |
| 4002 |
# <i>dmesg | grep 'drive$'</i> <comment>(For IDE disks)</comment> |
| 4003 |
# <i>dmesg | grep 'scsi'</i> <comment>(For SCSI disks)</comment> |
| 4004 |
</pre> |
| 4005 |
|
| 4006 |
<p> |
| 4007 |
>From this output you should be able to see what disks were detected and their |
| 4008 |
respective <path>/dev</path> entry. In the following parts we assume that the |
| 4009 |
disk is a SCSI disk on <path>/dev/sda</path>. |
| 4010 |
</p> |
| 4011 |
|
| 4012 |
<p> |
| 4013 |
Now fire up <c>fdisk</c>: |
| 4014 |
</p> |
| 4015 |
|
| 4016 |
<pre caption="Starting fdisk"> |
| 4017 |
# <i>fdisk /dev/sda</i> |
| 4018 |
</pre> |
| 4019 |
|
| 4020 |
</body> |
| 4021 |
</subsection> |
| 4022 |
<subsection> |
| 4023 |
<title>Deleting All Partitions</title> |
| 4024 |
<body> |
| 4025 |
|
| 4026 |
<p> |
| 4027 |
If your hard drive is completely blank, then you'll have to first create |
| 4028 |
a DOS disklabel. |
| 4029 |
</p> |
| 4030 |
|
| 4031 |
<pre caption="Creating a DOS disklabel"> |
| 4032 |
Command (m for help): <i>o</i> |
| 4033 |
Building a new DOS disklabel. |
| 4034 |
</pre> |
| 4035 |
|
| 4036 |
<p> |
| 4037 |
We start with deleting all partitions. The following shows how to delete |
| 4038 |
a partition (in the example we use '1'). Repeat the process to delete all |
| 4039 |
other partitions. |
| 4040 |
</p> |
| 4041 |
|
| 4042 |
<p> |
| 4043 |
Use <c>p</c> to view all existing partitions. <c>d</c> is used to delete a |
| 4044 |
partition. |
| 4045 |
</p> |
| 4046 |
|
| 4047 |
<pre caption="Deleting a partition"> |
| 4048 |
command (m for help): <i>p</i> |
| 4049 |
|
| 4050 |
Disk /dev/sda: 9150 MB, 9150996480 bytes |
| 4051 |
64 heads, 32 sectors/track, 8727 cylinders |
| 4052 |
Units = cylinders of 2048 * 512 = 1048576 bytes |
| 4053 |
|
| 4054 |
Device Boot Start End Blocks Id System |
| 4055 |
/dev/sda1 1 478 489456 83 Linux |
| 4056 |
/dev/sda2 479 8727 8446976 5 Extended |
| 4057 |
/dev/sda5 479 1433 977904 83 Linux Swap |
| 4058 |
/dev/sda6 1434 8727 7469040 83 Linux |
| 4059 |
|
| 4060 |
command (m for help): <i>d</i> |
| 4061 |
Partition number (1-6): <i>1</i> |
| 4062 |
</pre> |
| 4063 |
|
| 4064 |
|
| 4065 |
</body> |
| 4066 |
</subsection> |
| 4067 |
<subsection> |
| 4068 |
<title>Creating the Boot Partition</title> |
| 4069 |
<body> |
| 4070 |
|
| 4071 |
<p> |
| 4072 |
On Alpha systems which use MILO to boot, we have to create a small vfat |
| 4073 |
boot partition. |
| 4074 |
</p> |
| 4075 |
|
| 4076 |
<pre caption="Creating the boot partition"> |
| 4077 |
Command (m for help): <i>n</i> |
| 4078 |
Command action |
| 4079 |
e extended |
| 4080 |
p primary partition (1-4) |
| 4081 |
<i>p</i> |
| 4082 |
Partition number (1-4): <i>1</i> |
| 4083 |
First cylinder (1-8727, default 1): <i>1</i> |
| 4084 |
Last cylinder or +size or +sizeM or +sizeK (1-8727, default 8727): <i>+16M</i> |
| 4085 |
|
| 4086 |
Command (m for help): <i>t</i> |
| 4087 |
Selected partition 1 |
| 4088 |
Hex code (type L to list codes): <i>6</i> |
| 4089 |
Changed system type of partition 1 to 6 (FAT16) |
| 4090 |
</pre> |
| 4091 |
|
| 4092 |
</body> |
| 4093 |
</subsection> |
| 4094 |
<subsection> |
| 4095 |
<title>Creating the Swap Partition</title> |
| 4096 |
<body> |
| 4097 |
|
| 4098 |
<p> |
| 4099 |
We will create a swap partition starting at the third cylinder, with a total |
| 4100 |
size of 1 GB. Use <c>n</c> to create a new partition. |
| 4101 |
</p> |
| 4102 |
|
| 4103 |
<pre caption="Creating the swap partition"> |
| 4104 |
Command (m for help): <i>n</i> |
| 4105 |
Command action |
| 4106 |
e extended |
| 4107 |
p primary partition (1-4) |
| 4108 |
<i>p</i> |
| 4109 |
Partition number (1-4): <i>2</i> |
| 4110 |
First cylinder (17-8727, default 17): <i>17</i> |
| 4111 |
Last cylinder or +size or +sizeM or +sizeK (17-8727, default 8727): <i>+1000M</i> |
| 4112 |
|
| 4113 |
Command (m for help): <i>t</i> |
| 4114 |
Partition number (1-4): <i>1</i> |
| 4115 |
Hex code (type L to list codes): <i>82</i> |
| 4116 |
Changed system type of partition 2 to 82 (Linux swap) |
| 4117 |
</pre> |
| 4118 |
|
| 4119 |
<p> |
| 4120 |
After these steps you should see a layout similar to the following: |
| 4121 |
</p> |
| 4122 |
|
| 4123 |
<pre caption="Partition listing after creating a swap partition"> |
| 4124 |
Command (m for help): <i>p</i> |
| 4125 |
|
| 4126 |
Disk /dev/sda: 9150 MB, 9150996480 bytes |
| 4127 |
64 heads, 32 sectors/track, 8727 cylinders |
| 4128 |
Units = cylinders of 2048 * 512 = 1048576 bytes |
| 4129 |
|
| 4130 |
Device Boot Start End Blocks Id System |
| 4131 |
/dev/sda1 1 16 16368 6 FAT16 |
| 4132 |
/dev/sda2 17 971 977920 82 Linux swap |
| 4133 |
</pre> |
| 4134 |
|
| 4135 |
</body> |
| 4136 |
</subsection> |
| 4137 |
<subsection> |
| 4138 |
<title>Creating the Root Partition</title> |
| 4139 |
<body> |
| 4140 |
|
| 4141 |
<p> |
| 4142 |
We will now create the root partition. Again, just use the <c>n</c> command. |
| 4143 |
</p> |
| 4144 |
|
| 4145 |
<pre caption="Creating the root partition"> |
| 4146 |
Command (m for help): <i>n</i> |
| 4147 |
Command action |
| 4148 |
e extended |
| 4149 |
p primary partition (1-4) |
| 4150 |
<i>p</i> |
| 4151 |
Partition number (1-4): <i>3</i> |
| 4152 |
First cylinder (972-8727, default 972): <i>972</i> |
| 4153 |
Last cylinder or +size or +sizeM or +sizeK (972-8727, default 8727): <i>8727</i> |
| 4154 |
</pre> |
| 4155 |
|
| 4156 |
<p> |
| 4157 |
After these steps you should see a layout similar to the following: |
| 4158 |
</p> |
| 4159 |
|
| 4160 |
<pre caption="Partition listing after creating the root partition"> |
| 4161 |
Command (m for help): <i>p</i> |
| 4162 |
|
| 4163 |
Disk /dev/sda: 9150 MB, 9150996480 bytes |
| 4164 |
64 heads, 32 sectors/track, 8727 cylinders |
| 4165 |
Units = cylinders of 2048 * 512 = 1048576 bytes |
| 4166 |
|
| 4167 |
Device Boot Start End Blocks Id System |
| 4168 |
/dev/sda1 1 16 16368 6 FAT16 |
| 4169 |
/dev/sda2 17 971 977920 82 Linux swap |
| 4170 |
/dev/sda3 972 8727 7942144 83 Linux |
| 4171 |
</pre> |
| 4172 |
|
| 4173 |
</body> |
| 4174 |
</subsection> |
| 4175 |
<subsection> |
| 4176 |
<title>Save the Partition Layout and Exit</title> |
| 4177 |
<body> |
| 4178 |
|
| 4179 |
<p> |
| 4180 |
Save <c>fdisk</c> by typing <c>w</c>. This will also save your partition layout. |
| 4181 |
</p> |
| 4182 |
|
| 4183 |
<pre caption="Save and exit fdisk"> |
| 4184 |
Command (m for help): <i>w</i> |
| 4185 |
</pre> |
| 4186 |
|
| 4187 |
<p> |
| 4188 |
Now that your partitions are created, you can now continue with <uri |
| 4189 |
link="#filesystems">Creating Filesystems</uri>. |
| 4190 |
</p> |
| 4191 |
|
| 4192 |
</body> |
| 4193 |
</subsection> |
| 4194 |
</section> |
| 4195 |
<section id="filesystems"> |
| 4196 |
<title>Creating Filesystems</title> |
| 4197 |
<subsection> |
| 4198 |
<title>Introduction</title> |
| 4199 |
<body> |
| 4200 |
|
| 4201 |
<p> |
| 4202 |
Now that your partitions are created, it is time to place a filesystem on them. |
| 4203 |
If you don't care about what filesystem to choose and are happy with what we use |
| 4204 |
as default in this handbook, continue with <uri |
| 4205 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
| 4206 |
Otherwise read on to learn about the available filesystems... |
| 4207 |
</p> |
| 4208 |
|
| 4209 |
</body> |
| 4210 |
</subsection> |
| 4211 |
<subsection> |
| 4212 |
<title>Filesystems?</title> |
| 4213 |
<body> |
| 4214 |
|
| 4215 |
<p> |
| 4216 |
Several filesystems are available. Most of them are found stable on the |
| 4217 |
Alpha architecture. |
| 4218 |
</p> |
| 4219 |
|
| 4220 |
<p> |
| 4221 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
| 4222 |
journaling, which means that routine ext2 filesystem checks at startup time can |
| 4223 |
be quite time-consuming. There is now quite a selection of newer-generation |
| 4224 |
journaled filesystems that can be checked for consistency very quickly and are |
| 4225 |
thus generally preferred over their non-journaled counterparts. Journaled |
| 4226 |
filesystems prevent long delays when you boot your system and your filesystem |
| 4227 |
happens to be in an inconsistent state. |
| 4228 |
</p> |
| 4229 |
|
| 4230 |
<p> |
| 4231 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
| 4232 |
journaling for fast recovery in addition to other enhanced journaling modes like |
| 4233 |
full data and ordered data journaling. ext3 is a very good and reliable |
| 4234 |
filesystem. It has an additional hashed b-tree indexing option that enables |
| 4235 |
high performance in almost all situations. You can enable this indexing by |
| 4236 |
adding <c>-O dir_index</c> to the <c>mke2fs</c> command. In short, ext3 is an |
| 4237 |
excellent filesystem. |
| 4238 |
</p> |
| 4239 |
|
| 4240 |
<p> |
| 4241 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
| 4242 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
| 4243 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
| 4244 |
extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is |
| 4245 |
solid and usable as both general-purpose filesystem and for extreme cases such |
| 4246 |
as the creation of large filesystems, the use of many small files, very large |
| 4247 |
files and directories containing tens of thousands of files. |
| 4248 |
</p> |
| 4249 |
|
| 4250 |
<p> |
| 4251 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
| 4252 |
feature-set and is optimized for scalability. We only recommend using this |
| 4253 |
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
| 4254 |
an uninterruptible power supply. Because XFS aggressively caches in-transit data |
| 4255 |
in RAM, improperly designed programs (those that don't take proper precautions |
| 4256 |
when writing files to disk and there are quite a few of them) can lose a good |
| 4257 |
deal of data if the system goes down unexpectedly. |
| 4258 |
</p> |
| 4259 |
|
| 4260 |
<p> |
| 4261 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
| 4262 |
become production-ready and there hasn't been a sufficient track record to |
| 4263 |
comment positively nor negatively on its general stability at this point. |
| 4264 |
</p> |
| 4265 |
|
| 4266 |
</body> |
| 4267 |
</subsection> |
| 4268 |
<subsection id="filesystems-apply"> |
| 4269 |
<title>Applying a Filesystem to a Partition</title> |
| 4270 |
<body> |
| 4271 |
|
| 4272 |
<p> |
| 4273 |
To create a filesystem on a partition or volume, there are tools available for |
| 4274 |
each possible filesystem: |
| 4275 |
</p> |
| 4276 |
|
| 4277 |
<table> |
| 4278 |
<tr> |
| 4279 |
<th>Filesystem</th> |
| 4280 |
<th>Creation Command</th> |
| 4281 |
</tr> |
| 4282 |
<tr> |
| 4283 |
<ti>ext2</ti> |
| 4284 |
<ti><c>mke2fs</c></ti> |
| 4285 |
</tr> |
| 4286 |
<tr> |
| 4287 |
<ti>ext3</ti> |
| 4288 |
<ti><c>mke2fs -j</c></ti> |
| 4289 |
</tr> |
| 4290 |
<tr> |
| 4291 |
<ti>reiserfs</ti> |
| 4292 |
<ti><c>mkreiserfs</c></ti> |
| 4293 |
</tr> |
| 4294 |
<tr> |
| 4295 |
<ti>xfs</ti> |
| 4296 |
<ti><c>mkfs.xfs</c></ti> |
| 4297 |
</tr> |
| 4298 |
<tr> |
| 4299 |
<ti>jfs</ti> |
| 4300 |
<ti><c>mkfs.jfs</c></ti> |
| 4301 |
</tr> |
| 4302 |
</table> |
| 4303 |
|
| 4304 |
<p> |
| 4305 |
For instance, to have the root partition (<path>/dev/sda2</path> in our example) |
| 4306 |
in ext3, you would use: |
| 4307 |
</p> |
| 4308 |
|
| 4309 |
<pre caption="Applying a filesystem on a partition"> |
| 4310 |
# <i>mke2fs -j /dev/sda2</i> |
| 4311 |
</pre> |
| 4312 |
|
| 4313 |
<p> |
| 4314 |
Now create the filesystems on your newly created partitions (or logical |
| 4315 |
volumes). |
| 4316 |
</p> |
| 4317 |
|
| 4318 |
</body> |
| 4319 |
</subsection> |
| 4320 |
<subsection> |
| 4321 |
<title>Activating the Swap Partition</title> |
| 4322 |
<body> |
| 4323 |
|
| 4324 |
<p> |
| 4325 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
| 4326 |
</p> |
| 4327 |
|
| 4328 |
<pre caption="Creating a Swap signature"> |
| 4329 |
# <i>mkswap /dev/sda1</i> |
| 4330 |
</pre> |
| 4331 |
|
| 4332 |
<p> |
| 4333 |
To activate the swap partition, use <c>swapon</c>: |
| 4334 |
</p> |
| 4335 |
|
| 4336 |
<pre caption="Activating the swap partition"> |
| 4337 |
# <i>swapon /dev/sda1</i> |
| 4338 |
</pre> |
| 4339 |
|
| 4340 |
<p> |
| 4341 |
Create and activate the swap with the commands mentioned above. |
| 4342 |
</p> |
| 4343 |
|
| 4344 |
</body> |
| 4345 |
</subsection> |
| 4346 |
</section> |
| 4347 |
<section> |
| 4348 |
<title>Mounting</title> |
| 4349 |
<body> |
| 4350 |
|
| 4351 |
<p> |
| 4352 |
Now that your partitions are initialized and are housing a filesystem, it is |
| 4353 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
| 4354 |
create the necessary mount directories for every partition you created. As an |
| 4355 |
example we mount the root and boot partition: |
| 4356 |
</p> |
| 4357 |
|
| 4358 |
<pre caption="Mounting partitions"> |
| 4359 |
# <i>mount /dev/sda2 /mnt/gentoo</i> |
| 4360 |
</pre> |
| 4361 |
|
| 4362 |
<note> |
| 4363 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
| 4364 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
| 4365 |
also holds for <path>/var/tmp</path>. |
| 4366 |
</note> |
| 4367 |
|
| 4368 |
<p> |
| 4369 |
We will also have to mount the proc filesystem (a virtual interface with the |
| 4370 |
kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. |
| 4371 |
</p> |
| 4372 |
|
| 4373 |
<p> |
| 4374 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
| 4375 |
Installation Files</uri>. |
| 4376 |
</p> |
| 4377 |
|
| 4378 |
</body> |
| 4379 |
</section> |
| 4380 |
</sections> |
| 4381 |
|
| 4382 |
|
| 4383 |
|
| 4384 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-alpha-kernel.xml |
| 4385 |
|
| 4386 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-alpha-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 4387 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-alpha-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 4388 |
|
| 4389 |
Index: hb-install-alpha-kernel.xml |
| 4390 |
=================================================================== |
| 4391 |
<?xml version='1.0' encoding='UTF-8'?> |
| 4392 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 4393 |
|
| 4394 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 4395 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 4396 |
|
| 4397 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-alpha-kernel.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 4398 |
|
| 4399 |
<sections> |
| 4400 |
|
| 4401 |
<version>5.5</version> |
| 4402 |
<date>2006-01-06</date> |
| 4403 |
|
| 4404 |
<section> |
| 4405 |
<title>Timezone</title> |
| 4406 |
<body> |
| 4407 |
|
| 4408 |
<p> |
| 4409 |
You first need to select your timezone so that your system knows where it is |
| 4410 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
| 4411 |
it to <path>/etc/localtime</path>. Please avoid the |
| 4412 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
| 4413 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
| 4414 |
</p> |
| 4415 |
|
| 4416 |
<pre caption="Setting the timezone information"> |
| 4417 |
# <i>ls /usr/share/zoneinfo</i> |
| 4418 |
<comment>(Suppose you want to use GMT)</comment> |
| 4419 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
| 4420 |
</pre> |
| 4421 |
|
| 4422 |
</body> |
| 4423 |
</section> |
| 4424 |
<section> |
| 4425 |
<title>Installing the Sources</title> |
| 4426 |
<subsection> |
| 4427 |
<title>Choosing a Kernel</title> |
| 4428 |
<body> |
| 4429 |
|
| 4430 |
<p> |
| 4431 |
The core around which all distributions are built is the Linux kernel. It is the |
| 4432 |
layer between the user programs and your system hardware. Gentoo provides its |
| 4433 |
users several possible kernel sources. A full listing with description is |
| 4434 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
| 4435 |
Guide</uri>. |
| 4436 |
</p> |
| 4437 |
|
| 4438 |
<p> |
| 4439 |
For alpha-based systems we have <c>vanilla-sources</c> (the default 2.6 kernel source). |
| 4440 |
</p> |
| 4441 |
|
| 4442 |
<p> |
| 4443 |
Choose your kernel source and install it using <c>emerge</c>. The |
| 4444 |
<c>USE="-doc"</c> is necessary to avoid installing xorg-x11 or other |
| 4445 |
dependencies at this point. <c>USE="symlink"</c> is not necessary for a new |
| 4446 |
install, but ensures proper creation of the <path>/usr/src/linux</path> |
| 4447 |
symlink. |
| 4448 |
</p> |
| 4449 |
|
| 4450 |
<p> |
| 4451 |
In the next example we install the <c>vanilla-sources</c>. |
| 4452 |
Of course substitute with your choice of sources, this is merely an example: |
| 4453 |
</p> |
| 4454 |
|
| 4455 |
<pre caption="Installing a kernel source"> |
| 4456 |
# <i>USE="-doc symlink" emerge vanilla-sources</i> |
| 4457 |
</pre> |
| 4458 |
|
| 4459 |
<p> |
| 4460 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
| 4461 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
| 4462 |
kernel source points to <c>vanilla-sources-2.6.11.2</c>. Your version may be |
| 4463 |
different, so keep this in mind. |
| 4464 |
</p> |
| 4465 |
|
| 4466 |
<pre caption="Viewing the kernel source symlink"> |
| 4467 |
# <i>ls -l /usr/src/linux</i> |
| 4468 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-2.6.11.2 |
| 4469 |
</pre> |
| 4470 |
|
| 4471 |
<p> |
| 4472 |
Now it is time to configure and compile your kernel source. You |
| 4473 |
can use <c>genkernel</c> for this, which will build a generic kernel as used |
| 4474 |
by the Installation CD. We explain the "manual" configuration first though, as it is |
| 4475 |
the best way to optimize your environment. |
| 4476 |
</p> |
| 4477 |
|
| 4478 |
<p> |
| 4479 |
If you want to manually configure your kernel, continue now with <uri |
| 4480 |
link="#manual">Default: Manual Configuration</uri>. If you want to use |
| 4481 |
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
| 4482 |
genkernel</uri> instead. |
| 4483 |
</p> |
| 4484 |
|
| 4485 |
</body> |
| 4486 |
</subsection> |
| 4487 |
</section> |
| 4488 |
<section id="manual"> |
| 4489 |
<title>Default: Manual Configuration</title> |
| 4490 |
<subsection> |
| 4491 |
<title>Introduction</title> |
| 4492 |
<body> |
| 4493 |
|
| 4494 |
<p> |
| 4495 |
Manually configuring a kernel is often seen as the most difficult procedure a |
| 4496 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
| 4497 |
couple of kernels you don't even remember that it was difficult ;) |
| 4498 |
</p> |
| 4499 |
|
| 4500 |
<p> |
| 4501 |
However, one thing <e>is</e> true: you must know your system when you start |
| 4502 |
configuring a kernel manually. You can run <c>lsmod</c> to see what kernel |
| 4503 |
modules the Installation CD uses (it might provide you with a nice hint on |
| 4504 |
what to enable). |
| 4505 |
</p> |
| 4506 |
|
| 4507 |
<p> |
| 4508 |
Now go to your kernel source directory and execute <c>make menuconfig</c>. This |
| 4509 |
will fire up an ncurses-based configuration menu. |
| 4510 |
</p> |
| 4511 |
|
| 4512 |
<pre caption="Invoking menuconfig"> |
| 4513 |
# <i>cd /usr/src/linux</i> |
| 4514 |
# <i>make menuconfig</i> |
| 4515 |
</pre> |
| 4516 |
|
| 4517 |
<p> |
| 4518 |
You will be greeted with several configuration sections. We'll first list some |
| 4519 |
options you must activate (otherwise Gentoo will not function, or not function |
| 4520 |
properly without additional tweaks). |
| 4521 |
</p> |
| 4522 |
|
| 4523 |
</body> |
| 4524 |
</subsection> |
| 4525 |
<subsection> |
| 4526 |
<title>Activating Required Options</title> |
| 4527 |
<body> |
| 4528 |
|
| 4529 |
<p> |
| 4530 |
First of all, activate the use of development and experimental code/drivers. |
| 4531 |
You need this, otherwise some very important code/drivers won't show up: |
| 4532 |
</p> |
| 4533 |
|
| 4534 |
<pre caption="Selecting experimental code/drivers, General setup"> |
| 4535 |
Code maturity level options ---> |
| 4536 |
[*] Prompt for development and/or incomplete code/drivers |
| 4537 |
General setup ---> |
| 4538 |
[*] Support for hot-pluggable devices |
| 4539 |
</pre> |
| 4540 |
|
| 4541 |
<p> |
| 4542 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
| 4543 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
| 4544 |
able to mount your partitions. Also select <c>Virtual memory</c>, <c>/proc |
| 4545 |
file system</c>, (<c>/dev file system</c> + <c>Automatically mount at boot</c> only for 2.4 kernel): |
| 4546 |
</p> |
| 4547 |
|
| 4548 |
<pre caption="Selecting necessary file systems"> |
| 4549 |
<comment>(With a 2.4.x kernel)</comment> |
| 4550 |
File systems ---> |
| 4551 |
[*] Virtual memory file system support (former shm fs) |
| 4552 |
[*] /proc file system support |
| 4553 |
[*] /dev file system support (EXPERIMENTAL) |
| 4554 |
[*] Automatically mount at boot |
| 4555 |
[ ] /dev/pts file system for Unix98 PTYs |
| 4556 |
|
| 4557 |
<comment>(With a 2.6.x kernel)</comment> |
| 4558 |
File systems ---> |
| 4559 |
Pseudo Filesystems ---> |
| 4560 |
[*] /proc file system support |
| 4561 |
[*] Virtual memory file system support (former shm fs) |
| 4562 |
|
| 4563 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
| 4564 |
<*> Reiserfs support |
| 4565 |
<*> Ext3 journalling file system support |
| 4566 |
<*> JFS filesystem support |
| 4567 |
<*> Second extended fs support |
| 4568 |
<*> XFS filesystem support |
| 4569 |
</pre> |
| 4570 |
|
| 4571 |
<p> |
| 4572 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
| 4573 |
modem, you will need the following options in the kernel: |
| 4574 |
</p> |
| 4575 |
|
| 4576 |
<pre caption="Selecting PPPoE necessary drivers"> |
| 4577 |
<comment>(With a 2.4.x kernel)</comment> |
| 4578 |
Network device support ---> |
| 4579 |
<*> PPP (point-to-point protocol) support |
| 4580 |
<*> PPP support for async serial ports |
| 4581 |
<*> PPP support for sync tty ports |
| 4582 |
|
| 4583 |
<comment>(With a 2.6.x kernel)</comment> |
| 4584 |
Device Drivers ---> |
| 4585 |
Networking support ---> |
| 4586 |
<*> PPP (point-to-point protocol) support |
| 4587 |
<*> PPP support for async serial ports |
| 4588 |
<*> PPP support for sync tty ports |
| 4589 |
</pre> |
| 4590 |
|
| 4591 |
<p> |
| 4592 |
The two compression options won't harm but are not definitely needed, neither |
| 4593 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
| 4594 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
| 4595 |
</p> |
| 4596 |
|
| 4597 |
<p> |
| 4598 |
If you require it, don't forget to include support in the kernel for your |
| 4599 |
ethernet card. |
| 4600 |
</p> |
| 4601 |
|
| 4602 |
<p> |
| 4603 |
The following options are recommended as well: |
| 4604 |
</p> |
| 4605 |
|
| 4606 |
<pre caption="Recommended Alpha options"> |
| 4607 |
General setup ---> |
| 4608 |
<*> SRM environment through procfs |
| 4609 |
<*> Configure uac policy via sysctl |
| 4610 |
|
| 4611 |
Plug and Play configuration ---> |
| 4612 |
<*> Plug and Play support |
| 4613 |
<M> ISA Plug and Play support |
| 4614 |
|
| 4615 |
SCSI support ---> |
| 4616 |
SCSI low-level drivers ---> |
| 4617 |
<*> SYM53C8XX Version 2 SCSI support (NEW) |
| 4618 |
<*> Qlogic ISP SCSI support |
| 4619 |
|
| 4620 |
Network device support ---> |
| 4621 |
Ethernet (10 or 100 Mbit) ---> |
| 4622 |
<M> DECchip Tulip (dc21x4x) PCI support |
| 4623 |
<M> Generic DECchip & DIGITAL EtherWORKS PCI/EISA |
| 4624 |
<M> EtherExpressPro/100 support (eepro100) |
| 4625 |
<M> EtherExpressPro/100 support (e100) |
| 4626 |
Ethernet (1000 Mbit) ---> |
| 4627 |
<M> Alteon AceNIC |
| 4628 |
[*] Omit support for old Tigon I |
| 4629 |
<M> Broadcom Tigon3 |
| 4630 |
[*] FDDI driver support |
| 4631 |
<M> Digital DEFEA and DEFPA |
| 4632 |
<*> PPP support |
| 4633 |
<*> PPP Deflate compression |
| 4634 |
|
| 4635 |
Character devices ---> |
| 4636 |
[*] Support for console on serial port |
| 4637 |
[*] Direct Rendering Manager |
| 4638 |
|
| 4639 |
File systems ---> |
| 4640 |
<*> Kernel automounter version 4 support |
| 4641 |
Network File Systems ---> |
| 4642 |
<*> NFS |
| 4643 |
[*] NFSv3 client |
| 4644 |
<*> NFS server |
| 4645 |
[*] NFSv3 server |
| 4646 |
Partition Types ---> |
| 4647 |
[*] Advanced partition selection |
| 4648 |
[*] Alpha OSF partition support |
| 4649 |
Native Language Support |
| 4650 |
<*> NLS ISO 8859-1 |
| 4651 |
|
| 4652 |
Sound ---> |
| 4653 |
<M> Sound card support |
| 4654 |
<M> OSS sound modules |
| 4655 |
[*] Verbose initialisation |
| 4656 |
[*] Persistent DMA buffers |
| 4657 |
<M> 100% Sound Blaster compatibles |
| 4658 |
</pre> |
| 4659 |
|
| 4660 |
<p> |
| 4661 |
When you've finished configuring the kernel, continue with <uri |
| 4662 |
link="#compiling">Compiling and Installing</uri>. |
| 4663 |
</p> |
| 4664 |
|
| 4665 |
</body> |
| 4666 |
</subsection> |
| 4667 |
<subsection id="compiling"> |
| 4668 |
<title>Compiling and Installing</title> |
| 4669 |
<body> |
| 4670 |
|
| 4671 |
<p> |
| 4672 |
Now that your kernel is configured, it is time to compile and install it. Exit |
| 4673 |
the configuration and start the compilation process: |
| 4674 |
</p> |
| 4675 |
|
| 4676 |
<pre caption="Compiling the kernel"> |
| 4677 |
<comment>(For 2.4 kernel)</comment> |
| 4678 |
# <i>make dep && make vmlinux modules modules_install</i> |
| 4679 |
|
| 4680 |
<comment>(For 2.6 kernel)</comment> |
| 4681 |
# <i>make && make modules_install</i> |
| 4682 |
|
| 4683 |
<comment>(For all kernels)</comment> |
| 4684 |
# <i>make boot</i> |
| 4685 |
</pre> |
| 4686 |
|
| 4687 |
<p> |
| 4688 |
When the kernel has finished compiling, copy the kernel image to |
| 4689 |
<path>/boot</path>. Recent kernels might create <path>vmlinux</path> instead of |
| 4690 |
<path>vmlinux.gz</path>. Keep this in mind when you copy your kernel image. |
| 4691 |
</p> |
| 4692 |
|
| 4693 |
<pre caption="Installing the kernel"> |
| 4694 |
# <i>cp arch/alpha/boot/vmlinux.gz /boot/</i> |
| 4695 |
</pre> |
| 4696 |
|
| 4697 |
<p> |
| 4698 |
Now continue with <uri link="#kernel_modules">Installing Separate Kernel |
| 4699 |
Modules</uri>. |
| 4700 |
</p> |
| 4701 |
|
| 4702 |
</body> |
| 4703 |
</subsection> |
| 4704 |
</section> |
| 4705 |
<section id="genkernel"> |
| 4706 |
<title>Alternative: Using genkernel</title> |
| 4707 |
<body> |
| 4708 |
|
| 4709 |
<p> |
| 4710 |
If you are reading this section, you have chosen to use our <c>genkernel</c> |
| 4711 |
script to configure your kernel for you. |
| 4712 |
</p> |
| 4713 |
|
| 4714 |
<p> |
| 4715 |
Now that your kernel source tree is installed, it's now time to compile your |
| 4716 |
kernel by using our <c>genkernel</c> script to automatically build a kernel for |
| 4717 |
you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
| 4718 |
way our Installation CD kernel is configured. This means that when you use |
| 4719 |
<c>genkernel</c> to build your kernel, your system will generally detect all |
| 4720 |
your hardware at boot-time, just like our Installation CD does. Because genkernel |
| 4721 |
doesn't require any manual kernel configuration, it is an ideal solution for |
| 4722 |
those users who may not be comfortable compiling their own kernels. |
| 4723 |
</p> |
| 4724 |
|
| 4725 |
<p> |
| 4726 |
Now, let's see how to use genkernel. First, emerge the genkernel ebuild: |
| 4727 |
</p> |
| 4728 |
|
| 4729 |
<pre caption="Emerging genkernel"> |
| 4730 |
# <i>emerge genkernel</i> |
| 4731 |
</pre> |
| 4732 |
|
| 4733 |
<p> |
| 4734 |
Now, compile your kernel sources by running <c>genkernel all</c>. |
| 4735 |
Be aware though, as <c>genkernel</c> compiles a kernel that supports almost all |
| 4736 |
hardware, this compilation will take quite a while to finish! |
| 4737 |
</p> |
| 4738 |
|
| 4739 |
<p> |
| 4740 |
Note that, if your boot partition doesn't use ext2 or ext3 as filesystem you |
| 4741 |
need to manually configure your kernel using <c>genkernel --menuconfig all</c> |
| 4742 |
and add support for your filesystem <e>in</e> the kernel (i.e. <e>not</e> as a |
| 4743 |
module). |
| 4744 |
</p> |
| 4745 |
|
| 4746 |
<pre caption="Running genkernel"> |
| 4747 |
# <i>genkernel all</i> |
| 4748 |
GenKernel v3.0.1_beta10 |
| 4749 |
* ARCH: Alpha |
| 4750 |
* KERNEL VER: 2.6.11.2 |
| 4751 |
* kernel: configuring source |
| 4752 |
* kernel: running mrproper |
| 4753 |
<comment>(Output removed to increase readability)</comment> |
| 4754 |
* Kernel compiled successfully! |
| 4755 |
* Required Kernel Params: |
| 4756 |
* : root=/dev/ram0 init=/linuxrc real_root=/dev/$ROOT |
| 4757 |
* where $ROOT is the devicenode for your root partition as |
| 4758 |
* you should have specified in /etc/fstab |
| 4759 |
* |
| 4760 |
* You MUST tell your bootloader to use the generated initrd |
| 4761 |
* |
| 4762 |
* Recommended Kernel Params: |
| 4763 |
* : vga=0x317 splash=verbose |
| 4764 |
* |
| 4765 |
* Do NOT report kernel bugs (configs included) as genkernel bugs. |
| 4766 |
* Make sure you have the latest genkernel before reporting bugs |
| 4767 |
* |
| 4768 |
* For more info see /usr/share/genkernel/README |
| 4769 |
</pre> |
| 4770 |
|
| 4771 |
<p> |
| 4772 |
Once <c>genkernel</c> completes, a kernel, full set of modules and |
| 4773 |
<e>initial root disk</e> (initrd) will be created. We will use the kernel |
| 4774 |
and initrd when configuring a boot loader later in this document. Write |
| 4775 |
down the names of the kernel and initrd as you will need it when writing |
| 4776 |
the bootloader configuration file. The initrd will be started immediately after |
| 4777 |
booting to perform hardware autodetection (just like on the Installation CD) before |
| 4778 |
your "real" system starts up. |
| 4779 |
</p> |
| 4780 |
|
| 4781 |
<pre caption="Checking the created kernel image name and initrd"> |
| 4782 |
# <i>ls /boot/kernel* /boot/initramfs*</i> |
| 4783 |
</pre> |
| 4784 |
|
| 4785 |
<p> |
| 4786 |
Now, let's perform one more step to get our system to be more like the Installation CD -- let's emerge <c>coldplug</c>. While the initrd autodetects hardware that |
| 4787 |
is needed to boot your system, <c>coldplug</c> autodetects everything else. |
| 4788 |
To emerge and enable <c>coldplug</c>, type the following: |
| 4789 |
</p> |
| 4790 |
|
| 4791 |
<pre caption="Emerging and enabling coldplug"> |
| 4792 |
# <i>emerge coldplug</i> |
| 4793 |
# <i>rc-update add coldplug boot</i> |
| 4794 |
</pre> |
| 4795 |
|
| 4796 |
</body> |
| 4797 |
</section> |
| 4798 |
<section id="kernel_modules"> |
| 4799 |
<title>Installing Separate Kernel Modules</title> |
| 4800 |
<subsection> |
| 4801 |
<title>Installing Extra Modules</title> |
| 4802 |
<body> |
| 4803 |
|
| 4804 |
<p> |
| 4805 |
If appropriate, you should emerge ebuilds for any additional hardware that is |
| 4806 |
on your system. Here is a list of kernel-related ebuilds that you could emerge: |
| 4807 |
</p> |
| 4808 |
|
| 4809 |
<table> |
| 4810 |
<tcolumn width="1in"/> |
| 4811 |
<tcolumn width="4in"/> |
| 4812 |
<tcolumn width="2in"/> |
| 4813 |
<tr> |
| 4814 |
<th>Ebuild</th> |
| 4815 |
<th>Purpose</th> |
| 4816 |
<th>Command</th> |
| 4817 |
</tr> |
| 4818 |
<tr> |
| 4819 |
<ti>x11-drm</ti> |
| 4820 |
<ti> |
| 4821 |
Accelerated graphics for ATI Radeon up to 9200, Rage128, Matrox, Voodoo and |
| 4822 |
other cards for xorg-x11. Please check the <c>IUSE_VIDEO_CARDS</c> variable |
| 4823 |
in the <path>/usr/portage/x11-base/x11-drm</path> ebuilds to see what you |
| 4824 |
need to fill in as <c>yourcard</c>. |
| 4825 |
</ti> |
| 4826 |
<ti><c>VIDEO_CARDS="yourcard" emerge x11-drm</c></ti> |
| 4827 |
</tr> |
| 4828 |
</table> |
| 4829 |
|
| 4830 |
<p> |
| 4831 |
Beware though, some of these ebuilds might deal with big dependencies. To verify |
| 4832 |
what packages will be installed by emerging an ebuild, use <c>emerge |
| 4833 |
--pretend</c>. For instance, for the <c>x11-drm</c> package: |
| 4834 |
</p> |
| 4835 |
|
| 4836 |
<pre caption="View full installation package listing"> |
| 4837 |
# <i>emerge --pretend x11-drm</i> |
| 4838 |
</pre> |
| 4839 |
|
| 4840 |
</body> |
| 4841 |
</subsection> |
| 4842 |
<subsection> |
| 4843 |
<title>Configuring the Modules</title> |
| 4844 |
<body> |
| 4845 |
|
| 4846 |
<p> |
| 4847 |
You should list the modules you want automatically loaded in |
| 4848 |
<path>/etc/modules.autoload.d/kernel-2.4</path> (or <path>kernel-2.6</path>). |
| 4849 |
You can add extra options to the modules too if you want. |
| 4850 |
</p> |
| 4851 |
|
| 4852 |
<p> |
| 4853 |
To view all available modules, run the following <c>find</c> command. Don't |
| 4854 |
forget to substitute "<kernel version>" with the version of the kernel you |
| 4855 |
just compiled: |
| 4856 |
</p> |
| 4857 |
|
| 4858 |
<pre caption="Viewing all available modules"> |
| 4859 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
| 4860 |
</pre> |
| 4861 |
|
| 4862 |
<p> |
| 4863 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
| 4864 |
<path>kernel-2.4</path> or <path>kernel-2.6</path> file and enter the module |
| 4865 |
name in it. |
| 4866 |
</p> |
| 4867 |
|
| 4868 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.4"> |
| 4869 |
<comment>(Example for 2.4 kernels)</comment> |
| 4870 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.4</i> |
| 4871 |
</pre> |
| 4872 |
|
| 4873 |
<pre caption="/etc/modules.autoload.d/kernel-2.4 or kernel-2.6"> |
| 4874 |
3c59x |
| 4875 |
</pre> |
| 4876 |
|
| 4877 |
<p> |
| 4878 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
| 4879 |
your System</uri>. |
| 4880 |
</p> |
| 4881 |
|
| 4882 |
</body> |
| 4883 |
</subsection> |
| 4884 |
</section> |
| 4885 |
</sections> |
| 4886 |
|
| 4887 |
|
| 4888 |
|
| 4889 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-alpha-medium.xml |
| 4890 |
|
| 4891 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-alpha-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 4892 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-alpha-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 4893 |
|
| 4894 |
Index: hb-install-alpha-medium.xml |
| 4895 |
=================================================================== |
| 4896 |
<?xml version='1.0' encoding='UTF-8'?> |
| 4897 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 4898 |
|
| 4899 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 4900 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 4901 |
|
| 4902 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-alpha-medium.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 4903 |
|
| 4904 |
<sections> |
| 4905 |
|
| 4906 |
<version>5.3</version> |
| 4907 |
<date>2005-11-29</date> |
| 4908 |
|
| 4909 |
<section> |
| 4910 |
<title>Hardware Requirements</title> |
| 4911 |
<subsection> |
| 4912 |
<title>Introduction</title> |
| 4913 |
<body> |
| 4914 |
|
| 4915 |
<p> |
| 4916 |
Before we start, we first list what hardware requirements you need to |
| 4917 |
successfully install Gentoo on your box. |
| 4918 |
</p> |
| 4919 |
|
| 4920 |
</body> |
| 4921 |
</subsection> |
| 4922 |
<subsection> |
| 4923 |
<title>Hardware Requirements</title> |
| 4924 |
<body> |
| 4925 |
|
| 4926 |
<table> |
| 4927 |
<tr> |
| 4928 |
<th>CPU</th> |
| 4929 |
<ti> |
| 4930 |
Please check with the <uri |
| 4931 |
link="http://www.alphalinux.org/faq/FAQ-5.html">Alpha/Linux FAQ</uri> |
| 4932 |
</ti> |
| 4933 |
</tr> |
| 4934 |
<tr> |
| 4935 |
<th>Memory</th> |
| 4936 |
<ti>64 MB</ti> |
| 4937 |
</tr> |
| 4938 |
<tr> |
| 4939 |
<th>Diskspace</th> |
| 4940 |
<ti>1.5 GB (excluding swap space)</ti> |
| 4941 |
</tr> |
| 4942 |
<tr> |
| 4943 |
<th>Swap space</th> |
| 4944 |
<ti>At least 256 MB</ti> |
| 4945 |
</tr> |
| 4946 |
</table> |
| 4947 |
|
| 4948 |
</body> |
| 4949 |
</subsection> |
| 4950 |
</section> |
| 4951 |
<!-- Copy/paste from the hb-install-x86-medium.xml file but no Universal |
| 4952 |
Installation CD. |
| 4953 |
Also s/x86/alpha --> |
| 4954 |
<!-- START --> |
| 4955 |
<section> |
| 4956 |
<title>The Gentoo Universal Installation CD</title> |
| 4957 |
<subsection> |
| 4958 |
<title>Introduction</title> |
| 4959 |
<body> |
| 4960 |
|
| 4961 |
<p> |
| 4962 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
| 4963 |
Such a tarball is an archive that contains a minimal environment from |
| 4964 |
which you can succesfully install Gentoo Linux onto your system. |
| 4965 |
</p> |
| 4966 |
|
| 4967 |
<p> |
| 4968 |
Installations using a stage1 or stage2 tarball file are not documented in the |
| 4969 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
| 4970 |
FAQ</uri> on these matters. |
| 4971 |
</p> |
| 4972 |
|
| 4973 |
</body> |
| 4974 |
</subsection> |
| 4975 |
<subsection> |
| 4976 |
<title>Gentoo Universal Installation CD</title> |
| 4977 |
<body> |
| 4978 |
|
| 4979 |
<p> |
| 4980 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
| 4981 |
environment. It allows you to boot Linux from the CD. During the boot process |
| 4982 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
| 4983 |
Installation CDs are maintained by Gentoo developers. |
| 4984 |
</p> |
| 4985 |
|
| 4986 |
<p> |
| 4987 |
There currently are two Installation CDs available: |
| 4988 |
</p> |
| 4989 |
|
| 4990 |
<ul> |
| 4991 |
<li> |
| 4992 |
The Universal Installation CD contains everything you need to install |
| 4993 |
Gentoo. It provides stage3 files for common architectures, source code |
| 4994 |
for the extra applications you need to choose from and, of course, the |
| 4995 |
installation instructions for your architecture. |
| 4996 |
</li> |
| 4997 |
<li> |
| 4998 |
The Minimal Installation CD contains only a minimal environment that allows |
| 4999 |
you to boot up and configure your network so you can connect to the |
| 5000 |
Internet. It does not contain any additional files and cannot be used |
| 5001 |
during the current installation approach. |
| 5002 |
</li> |
| 5003 |
</ul> |
| 5004 |
|
| 5005 |
<p> |
| 5006 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
| 5007 |
additional resource that you can exploit during the installation of your Gentoo |
| 5008 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
| 5009 |
you to easily and quickly install additional applications (such as |
| 5010 |
OpenOffice.org, KDE, GNOME, ...) immediately after the Gentoo installation and |
| 5011 |
right before you update your Portage tree. |
| 5012 |
</p> |
| 5013 |
|
| 5014 |
<p> |
| 5015 |
The use of the Package CD is covered later in this document. |
| 5016 |
</p> |
| 5017 |
|
| 5018 |
</body> |
| 5019 |
</subsection> |
| 5020 |
</section> |
| 5021 |
<!-- STOP --> |
| 5022 |
<section> |
| 5023 |
<title>Download, Burn and Boot the Gentoo Universal Installation CD</title> |
| 5024 |
<subsection> |
| 5025 |
<title>Downloading and Burning the Installation CD</title> |
| 5026 |
<body> |
| 5027 |
|
| 5028 |
<p> |
| 5029 |
You can download the Universal Installation CD (and, if you want to, the |
| 5030 |
Packages CD as well) from one of our <uri |
| 5031 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CD is located in |
| 5032 |
the <path>releases/alpha/2006.0/installcd</path> directory; |
| 5033 |
the Package CD is located in the <path>releases/alpha/2006.0/packagecd</path> |
| 5034 |
directory. |
| 5035 |
</p> |
| 5036 |
|
| 5037 |
<p> |
| 5038 |
Inside those directories you'll find ISO-files. Those are full CD images which |
| 5039 |
you can write on a CD-R. |
| 5040 |
</p> |
| 5041 |
|
| 5042 |
<p> |
| 5043 |
After downloading the file, you can verify its integrity to see if it is |
| 5044 |
corrupted or not: |
| 5045 |
</p> |
| 5046 |
|
| 5047 |
<ul> |
| 5048 |
<li> |
| 5049 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
| 5050 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
| 5051 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows) |
| 5052 |
</li> |
| 5053 |
<li> |
| 5054 |
You can verify the cryptographic signature that we provide. You need to |
| 5055 |
obtain the public key we use (17072058) before you proceed though. |
| 5056 |
</li> |
| 5057 |
</ul> |
| 5058 |
|
| 5059 |
<p> |
| 5060 |
To fetch our public key using the GnuPG application, run the following command: |
| 5061 |
</p> |
| 5062 |
|
| 5063 |
<pre caption="Obtaining the public key"> |
| 5064 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
| 5065 |
</pre> |
| 5066 |
|
| 5067 |
<p> |
| 5068 |
Now verify the signature: |
| 5069 |
</p> |
| 5070 |
|
| 5071 |
<pre caption="Verify the cryptographic signature"> |
| 5072 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
| 5073 |
</pre> |
| 5074 |
|
| 5075 |
<p> |
| 5076 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
| 5077 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
| 5078 |
<c>K3B</c> here; more information can be found in our <uri |
| 5079 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
| 5080 |
</p> |
| 5081 |
|
| 5082 |
<ul> |
| 5083 |
<li> |
| 5084 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
| 5085 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
| 5086 |
path). |
| 5087 |
</li> |
| 5088 |
<li> |
| 5089 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
| 5090 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
| 5091 |
<c>Start</c>. |
| 5092 |
</li> |
| 5093 |
</ul> |
| 5094 |
|
| 5095 |
</body> |
| 5096 |
</subsection> |
| 5097 |
<subsection> |
| 5098 |
<title>Booting the Universal Installation CD</title> |
| 5099 |
<body> |
| 5100 |
|
| 5101 |
<p> |
| 5102 |
When your Alpha is powered on, the first thing that gets started is the |
| 5103 |
firmware. It is loosely synonymous with the BIOS software on PC systems. There |
| 5104 |
are two types of firmware on Alpha systems: SRM (<e>Systems Reference |
| 5105 |
Manual</e>) and ARC (<e>Advanced Risc Console</e>). |
| 5106 |
</p> |
| 5107 |
|
| 5108 |
<p> |
| 5109 |
SRM is based on the Alpha Console Subsystem specification, which provides an |
| 5110 |
operating environment for OpenVMS, Tru64 UNIX, and Linux operating systems. ARC |
| 5111 |
is based on the Advanced RISC Computing (ARC) specification, which provides |
| 5112 |
an operating environment for Windows NT. You can find a |
| 5113 |
<uri link="http://www.alphalinux.org/faq/SRM-HOWTO/">detailed guide</uri> on |
| 5114 |
using SRM over at the Alpha Linux website. |
| 5115 |
</p> |
| 5116 |
|
| 5117 |
<p> |
| 5118 |
If your Alpha system supports both SRC and ARCs (ARC, AlphaBIOS, ARCSBIOS) you |
| 5119 |
should follow <uri link="http://www.alphalinux.org/faq/x31.html">these |
| 5120 |
instructions</uri> for switching to SRM. If your system already uses SRM, you |
| 5121 |
are all set. If your system can only use ARCs (Ruffian, nautilus, xl, etc.) you |
| 5122 |
will need to choose <c>MILO</c> later on when we are talking about bootloaders. |
| 5123 |
</p> |
| 5124 |
|
| 5125 |
<p> |
| 5126 |
Now to boot an Alpha Installation CD, put the CD-ROM in the tray and reboot the system. |
| 5127 |
You can use SRM to boot the Installation CD. If you cannot do that, you will have to use |
| 5128 |
<c>MILO</c>. If you don't have <c>MILO</c> installed already, use one of the |
| 5129 |
precompiled <c>MILO</c> images available on <uri |
| 5130 |
link="http://dev.gentoo.org/~taviso/milo/">taviso's homepage</uri>. |
| 5131 |
</p> |
| 5132 |
|
| 5133 |
<pre caption="Booting a CD-ROM using SRM"> |
| 5134 |
<comment>(List available hardware drives)</comment> |
| 5135 |
>>> <i>show device</i> |
| 5136 |
dkb0.0.1.4.0 DKB0 TOSHIBA CDROM |
| 5137 |
<comment>(...)</comment> |
| 5138 |
<comment>(Substitute dkb0 with your CD-ROM drive device)</comment> |
| 5139 |
>>> <i>boot dkb0 -flags 0</i> |
| 5140 |
<comment>To boot the 2.4 kernel instead of the default 2.6 kernel use:</comment> |
| 5141 |
>>> <i>boot dkb -flags 1</i> |
| 5142 |
</pre> |
| 5143 |
|
| 5144 |
<pre caption="Booting a CD-ROM using MILO"> |
| 5145 |
<comment>(Substitute hdb with your CD-ROM drive device)</comment> |
| 5146 |
MILO> <i>boot hdb:/boot/gentoo_2.6 initrd=/boot/gentoo_2_6.igz root=/dev/ram0 init=/linuxrc looptype=zisofs loop=/zisofs cdroot</i> |
| 5147 |
<comment>To boot the 2.4 kernel instead of the default 2.6 kernel use:</comment> |
| 5148 |
MILO> <i>boot hdb:/boot/gentoo_2.4 initrd=/boot/gentoo_2_4.igz root=/dev/ram0 init=/linuxrc looptype=zisofs loop=/zisofs cdroot</i> |
| 5149 |
</pre> |
| 5150 |
|
| 5151 |
<p> |
| 5152 |
You should have a root ("#") prompt on the current console and can also switch |
| 5153 |
to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get back to the one you |
| 5154 |
started on by pressing Alt-F1. |
| 5155 |
</p> |
| 5156 |
|
| 5157 |
<p> |
| 5158 |
Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
| 5159 |
</p> |
| 5160 |
|
| 5161 |
</body> |
| 5162 |
</subsection> |
| 5163 |
<subsection id="hardware"> |
| 5164 |
<title>Extra Hardware Configuration</title> |
| 5165 |
<body> |
| 5166 |
|
| 5167 |
<p> |
| 5168 |
When the Installation CD boots, it tries to detect all your hardware devices and |
| 5169 |
loads the appropriate kernel modules to support your hardware. In the |
| 5170 |
vast majority of cases, it does a very good job. However, in some cases (the |
| 5171 |
SPARC Installation CDs don't even do autodetection), it may not auto-load the kernel |
| 5172 |
modules you need. If the PCI auto-detection missed some of your system's |
| 5173 |
hardware, you will have to load the appropriate kernel modules manually. |
| 5174 |
</p> |
| 5175 |
|
| 5176 |
<p> |
| 5177 |
In the next example we try to load the <c>8139too</c> module (support for |
| 5178 |
certain kinds of network interfaces): |
| 5179 |
</p> |
| 5180 |
|
| 5181 |
<pre caption="Loading kernel modules"> |
| 5182 |
# <i>modprobe 8139too</i> |
| 5183 |
</pre> |
| 5184 |
|
| 5185 |
<p> |
| 5186 |
If you need PCMCIA support, you should start the <c>pcmcia</c> init script: |
| 5187 |
</p> |
| 5188 |
|
| 5189 |
<pre caption="Starting the PCMCIA init script"> |
| 5190 |
# <i>/etc/init.d/pcmcia start</i> |
| 5191 |
</pre> |
| 5192 |
|
| 5193 |
</body> |
| 5194 |
</subsection> |
| 5195 |
<subsection> |
| 5196 |
<title>Optional: Tweaking Hard Disk Performance</title> |
| 5197 |
<body> |
| 5198 |
|
| 5199 |
<p> |
| 5200 |
If you are an advanced user, you might want to tweak the IDE hard disk |
| 5201 |
performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
| 5202 |
test the performance of your disk (execute it several times to get a |
| 5203 |
more precise impression): |
| 5204 |
</p> |
| 5205 |
|
| 5206 |
<pre caption="Testing disk performance"> |
| 5207 |
# <i>hdparm -tT /dev/hda</i> |
| 5208 |
</pre> |
| 5209 |
|
| 5210 |
<p> |
| 5211 |
To tweak, you can use any of the following examples (or experiment |
| 5212 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
| 5213 |
disk): |
| 5214 |
</p> |
| 5215 |
|
| 5216 |
<pre caption="Tweaking hard disk performance"> |
| 5217 |
<comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i> |
| 5218 |
<comment>Activate DMA + Safe Performance-enhancing Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
| 5219 |
</pre> |
| 5220 |
|
| 5221 |
</body> |
| 5222 |
</subsection> |
| 5223 |
<subsection id="useraccounts"> |
| 5224 |
<title>Optional: User Accounts</title> |
| 5225 |
<body> |
| 5226 |
|
| 5227 |
<p> |
| 5228 |
If you plan on giving other people access to your installation |
| 5229 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
| 5230 |
security reasons), you need to create the necessary user accounts and change |
| 5231 |
the root password. |
| 5232 |
</p> |
| 5233 |
|
| 5234 |
<p> |
| 5235 |
To change the root password, use the <c>passwd</c> utility: |
| 5236 |
</p> |
| 5237 |
|
| 5238 |
<pre caption="Changing the root password"> |
| 5239 |
# <i>passwd</i> |
| 5240 |
New password: <comment>(Enter your new password)</comment> |
| 5241 |
Re-enter password: <comment>(Re-enter your password)</comment> |
| 5242 |
</pre> |
| 5243 |
|
| 5244 |
<p> |
| 5245 |
To create a user account, we first enter their credentials, followed by |
| 5246 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
| 5247 |
In the next example, we create a user called "john". |
| 5248 |
</p> |
| 5249 |
|
| 5250 |
<pre caption="Creating a user account"> |
| 5251 |
# <i>useradd -m -G users john</i> |
| 5252 |
# <i>passwd john</i> |
| 5253 |
New password: <comment>(Enter john's password)</comment> |
| 5254 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
| 5255 |
</pre> |
| 5256 |
|
| 5257 |
<p> |
| 5258 |
You can change your user id from root to the newly created user by using |
| 5259 |
<c>su</c>: |
| 5260 |
</p> |
| 5261 |
|
| 5262 |
<pre caption="Changing user id"> |
| 5263 |
# <i>su - john</i> |
| 5264 |
</pre> |
| 5265 |
|
| 5266 |
</body> |
| 5267 |
</subsection> |
| 5268 |
<subsection> |
| 5269 |
<title>Optional: Viewing Documentation while Installing</title> |
| 5270 |
<body> |
| 5271 |
|
| 5272 |
<p> |
| 5273 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
| 5274 |
installation, make sure you have created a user account (see <uri |
| 5275 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
| 5276 |
go to a new terminal and log in. |
| 5277 |
</p> |
| 5278 |
|
| 5279 |
<p> |
| 5280 |
If you want to view the documentation on the CD you can immediately run |
| 5281 |
<c>lynx</c> to read it: |
| 5282 |
</p> |
| 5283 |
|
| 5284 |
<pre caption="Viewing the on-CD documentation"> |
| 5285 |
# <i>lynx /mnt/cdrom/docs/html/index.html</i> |
| 5286 |
</pre> |
| 5287 |
|
| 5288 |
<p> |
| 5289 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
| 5290 |
more recent than the one provided on the CD. You can view it using <c>lynx</c> |
| 5291 |
as well, but only after having completed the <e>Configuring your Network</e> |
| 5292 |
chapter (otherwise you won't be able to go on the Internet to view the |
| 5293 |
document): |
| 5294 |
</p> |
| 5295 |
|
| 5296 |
<pre caption="Viewing the Online Documentation"> |
| 5297 |
# <i>lynx http://www.gentoo.org/doc/en/handbook/handbook-alpha.xml</i> |
| 5298 |
</pre> |
| 5299 |
|
| 5300 |
<p> |
| 5301 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
| 5302 |
</p> |
| 5303 |
|
| 5304 |
</body> |
| 5305 |
</subsection> |
| 5306 |
<subsection> |
| 5307 |
<title>Optional: Starting the SSH Daemon</title> |
| 5308 |
<body> |
| 5309 |
|
| 5310 |
<p> |
| 5311 |
If you want to allow other users to access your computer during the |
| 5312 |
Gentoo installation (perhaps because those users are going to help you |
| 5313 |
install Gentoo, or even do it for you), you need to create a user |
| 5314 |
account for them and perhaps even provide them with your root password |
| 5315 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
| 5316 |
</p> |
| 5317 |
|
| 5318 |
<p> |
| 5319 |
To fire up the SSH daemon, execute the following command: |
| 5320 |
</p> |
| 5321 |
|
| 5322 |
<pre caption="Starting the SSH daemon"> |
| 5323 |
# <i>/etc/init.d/sshd start</i> |
| 5324 |
</pre> |
| 5325 |
|
| 5326 |
<p> |
| 5327 |
To be able to use sshd, you first need to set up your networking. Continue with |
| 5328 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
| 5329 |
</p> |
| 5330 |
|
| 5331 |
</body> |
| 5332 |
</subsection> |
| 5333 |
</section> |
| 5334 |
</sections> |
| 5335 |
|
| 5336 |
|
| 5337 |
|
| 5338 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-amd64-bootloader.xml |
| 5339 |
|
| 5340 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-amd64-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 5341 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-amd64-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 5342 |
|
| 5343 |
Index: hb-install-amd64-bootloader.xml |
| 5344 |
=================================================================== |
| 5345 |
<?xml version='1.0' encoding='UTF-8'?> |
| 5346 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 5347 |
|
| 5348 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 5349 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
| 5350 |
|
| 5351 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-amd64-bootloader.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 5352 |
|
| 5353 |
<sections> |
| 5354 |
|
| 5355 |
<version>5.8</version> |
| 5356 |
<date>2006-01-29</date> |
| 5357 |
|
| 5358 |
<section> |
| 5359 |
<title>Making your Choice</title> |
| 5360 |
<subsection> |
| 5361 |
<title>Introduction</title> |
| 5362 |
<body> |
| 5363 |
|
| 5364 |
<p> |
| 5365 |
Now that your kernel is configured and compiled and the necessary system |
| 5366 |
configuration files are filled in correctly, it is time to install a |
| 5367 |
program that will fire up your kernel when you start the system. Such a |
| 5368 |
program is called a <e>bootloader</e>. |
| 5369 |
</p> |
| 5370 |
|
| 5371 |
</body> |
| 5372 |
</subsection> |
| 5373 |
<subsection> |
| 5374 |
<title>Optional: Framebuffer</title> |
| 5375 |
<body> |
| 5376 |
|
| 5377 |
<!-- |
| 5378 |
Verbatim copy from x86 bootloader framebuffer explanation, minus the section on |
| 5379 |
vesafb-tng |
| 5380 |
--> |
| 5381 |
|
| 5382 |
<p> |
| 5383 |
<e>If</e> you have configured your kernel with framebuffer support (or you used |
| 5384 |
<c>genkernel</c>'s default kernel configuration), you can activate it by adding |
| 5385 |
a <c>vga</c> and/or a <c>video</c> statement to your bootloader configuration |
| 5386 |
file. |
| 5387 |
</p> |
| 5388 |
|
| 5389 |
<p> |
| 5390 |
64-bit systems must use the the <c>vesafb</c> driver, and so will need to set |
| 5391 |
the <c>vga</c> statement. The <c>vga</c> statement controls the resolution and |
| 5392 |
color depth of your framebuffer screen for <c>vesafb</c>. As stated in |
| 5393 |
<path>/usr/src/linux/Documentation/fb/vesafb.txt</path> (which gets installed |
| 5394 |
when you install a kernel source package), you need to pass the VESA number |
| 5395 |
corresponding to the requested resolution and color depth to it. |
| 5396 |
</p> |
| 5397 |
|
| 5398 |
<p> |
| 5399 |
The following table lists the available resolutions and colordepths and matches |
| 5400 |
those against the value that you need to pass on to the <c>vga</c> statement. |
| 5401 |
</p> |
| 5402 |
|
| 5403 |
<table> |
| 5404 |
<tr> |
| 5405 |
<ti></ti> |
| 5406 |
<th>640x480</th> |
| 5407 |
<th>800x600</th> |
| 5408 |
<th>1024x768</th> |
| 5409 |
<th>1280x1024</th> |
| 5410 |
</tr> |
| 5411 |
<tr> |
| 5412 |
<th>256</th> |
| 5413 |
<ti>0x301</ti> |
| 5414 |
<ti>0x303</ti> |
| 5415 |
<ti>0x305</ti> |
| 5416 |
<ti>0x307</ti> |
| 5417 |
</tr> |
| 5418 |
<tr> |
| 5419 |
<th>32k</th> |
| 5420 |
<ti>0x310</ti> |
| 5421 |
<ti>0x313</ti> |
| 5422 |
<ti>0x316</ti> |
| 5423 |
<ti>0x319</ti> |
| 5424 |
</tr> |
| 5425 |
<tr> |
| 5426 |
<th>64k</th> |
| 5427 |
<ti>0x311</ti> |
| 5428 |
<ti>0x314</ti> |
| 5429 |
<ti>0x317</ti> |
| 5430 |
<ti>0x31A</ti> |
| 5431 |
</tr> |
| 5432 |
<tr> |
| 5433 |
<th>16M</th> |
| 5434 |
<ti>0x312</ti> |
| 5435 |
<ti>0x315</ti> |
| 5436 |
<ti>0x318</ti> |
| 5437 |
<ti>0x31B</ti> |
| 5438 |
</tr> |
| 5439 |
</table> |
| 5440 |
|
| 5441 |
<p> |
| 5442 |
The <c>video</c> statement controls framebuffer display options. It needs to be |
| 5443 |
given the framebuffer driver (<c>vesafb</c> for 2.6 kernels, or <c>vesa</c> for |
| 5444 |
2.4 kernels) followed by the control statements you wish to enable. All |
| 5445 |
variables are listed in <path>/usr/src/linux/Documentation/fb/vesafb.txt</path>, |
| 5446 |
but we'll inform you about three most-used options: |
| 5447 |
</p> |
| 5448 |
|
| 5449 |
<table> |
| 5450 |
<tr> |
| 5451 |
<th>Control</th> |
| 5452 |
<th>Description</th> |
| 5453 |
</tr> |
| 5454 |
<tr> |
| 5455 |
<ti>ywrap</ti> |
| 5456 |
<ti> |
| 5457 |
Assume that the graphical card can wrap around its memory (i.e. continue at |
| 5458 |
the beginning when it has approached the end) |
| 5459 |
</ti> |
| 5460 |
</tr> |
| 5461 |
<tr> |
| 5462 |
<ti>mtrr</ti> |
| 5463 |
<ti> |
| 5464 |
Setup MTRR registers |
| 5465 |
</ti> |
| 5466 |
</tr> |
| 5467 |
</table> |
| 5468 |
|
| 5469 |
<p> |
| 5470 |
The result of those two statements could be something like <c>vga=0x318 |
| 5471 |
video=vesafb:mtrr,ywrap</c> or <c>video=vesafb:mtrr,ywrap,1024x768-32@85</c>. |
| 5472 |
Remember (or write down) this setting; you will need it shortly. |
| 5473 |
</p> |
| 5474 |
|
| 5475 |
<p> |
| 5476 |
While LILO does work on AMD64, Gentoo only supports using GRUB. Now continue by |
| 5477 |
its installation. |
| 5478 |
</p> |
| 5479 |
|
| 5480 |
</body> |
| 5481 |
</subsection> |
| 5482 |
</section> |
| 5483 |
<section> |
| 5484 |
<title>Using GRUB</title> |
| 5485 |
<subsection> |
| 5486 |
<title>Understanding GRUB's terminology</title> |
| 5487 |
<body> |
| 5488 |
|
| 5489 |
<p> |
| 5490 |
The most critical part of understanding GRUB is getting comfortable with |
| 5491 |
how GRUB refers to hard drives and partitions. Your Linux partition |
| 5492 |
<path>/dev/hda1</path> will most likely be called <path>(hd0,0)</path> under |
| 5493 |
GRUB. Notice the parenthesis around the <path>hd0,0</path> - they are required. |
| 5494 |
</p> |
| 5495 |
|
| 5496 |
<p> |
| 5497 |
Hard drives count from zero rather than "a" and partitions start at zero |
| 5498 |
rather than one. Be aware too that with the hd devices, only hard drives are |
| 5499 |
counted, not atapi-ide devices such as cdrom players and burners. Also, the |
| 5500 |
same construct is used with SCSI drives. (Normally they get higher numbers |
| 5501 |
than IDE drives except when the BIOS is configured to boot from SCSI devices.) |
| 5502 |
When you ask the BIOS to boot from a different hard disk (for instance your |
| 5503 |
primary slave), <e>that</e> harddisk is seen as <path>hd0</path>. |
| 5504 |
</p> |
| 5505 |
|
| 5506 |
<p> |
| 5507 |
Assuming you have a hard drive on <path>/dev/hda</path>, a cdrom player on |
| 5508 |
<path>/dev/hdb</path>, a burner on <path>/dev/hdc</path>, a second hard drive |
| 5509 |
on <path>/dev/hdd</path> and no SCSI hard drive, <path>/dev/hdd7</path> gets |
| 5510 |
translated to <path>(hd1,6)</path>. It might sound tricky and tricky it is |
| 5511 |
indeed, but as we will see, GRUB offers a tab completion mechanism |
| 5512 |
that comes handy for those of you having a lot of hard drives and |
| 5513 |
partitions and who are a little lost in the GRUB numbering scheme. |
| 5514 |
</p> |
| 5515 |
|
| 5516 |
<p> |
| 5517 |
Having gotten the feel for that, it is time to install GRUB. |
| 5518 |
</p> |
| 5519 |
|
| 5520 |
</body> |
| 5521 |
</subsection> |
| 5522 |
<subsection> |
| 5523 |
<title>Installing GRUB</title> |
| 5524 |
<body> |
| 5525 |
|
| 5526 |
<p> |
| 5527 |
To install GRUB, let's first emerge it. |
| 5528 |
</p> |
| 5529 |
|
| 5530 |
<pre caption="Installing GRUB"> |
| 5531 |
# <i>emerge grub</i> |
| 5532 |
</pre> |
| 5533 |
|
| 5534 |
<p> |
| 5535 |
Although GRUB is now installed, we still need to write up a |
| 5536 |
configuration file for it and install GRUB in the MBR so that GRUB |
| 5537 |
automatically boots your newly created kernel. Create |
| 5538 |
<path>/boot/grub/grub.conf</path> with <c>nano</c> (or, if applicable, another |
| 5539 |
editor): |
| 5540 |
</p> |
| 5541 |
|
| 5542 |
<pre caption="Creating /boot/grub/grub.conf"> |
| 5543 |
# <i>nano -w /boot/grub/grub.conf</i> |
| 5544 |
</pre> |
| 5545 |
|
| 5546 |
<p> |
| 5547 |
Now we are going to write up a <path>grub.conf</path>. Below you'll |
| 5548 |
find two possible <path>grub.conf</path> for the partitioning example we use |
| 5549 |
in this guide, with kernel image <path>kernel-2.6.12-gentoo-r10</path>. We've |
| 5550 |
only extensively commented the first <path>grub.conf</path>. |
| 5551 |
</p> |
| 5552 |
|
| 5553 |
<ul> |
| 5554 |
<li> |
| 5555 |
The first <path>grub.conf</path> is for people who have not used |
| 5556 |
<c>genkernel</c> to build their kernel |
| 5557 |
</li> |
| 5558 |
<li> |
| 5559 |
The second <path>grub.conf</path> is for people who have used |
| 5560 |
<c>genkernel</c> to build their kernel |
| 5561 |
</li> |
| 5562 |
</ul> |
| 5563 |
|
| 5564 |
<note> |
| 5565 |
If your root filesystem is JFS, you <e>must</e> add " ro" to the <c>kernel</c> |
| 5566 |
line since JFS needs to replay its log before it allows read-write mounting. |
| 5567 |
</note> |
| 5568 |
|
| 5569 |
<pre caption="grub.conf for non-genkernel users"> |
| 5570 |
<comment># Which listing to boot as default. 0 is the first, 1 the second etc.</comment> |
| 5571 |
default 0 |
| 5572 |
<comment># How many seconds to wait before the default listing is booted.</comment> |
| 5573 |
timeout 30 |
| 5574 |
<comment># Nice, fat splash-image to spice things up :) |
| 5575 |
# Comment out if you don't have a graphics card installed</comment> |
| 5576 |
splashimage=(hd0,0)/boot/grub/splash.xpm.gz |
| 5577 |
|
| 5578 |
title=Gentoo Linux 2.6.12 |
| 5579 |
<comment># Partition where the kernel image (or operating system) is located</comment> |
| 5580 |
root (hd0,0) |
| 5581 |
kernel /boot/kernel-2.6.12-gentoo-r10 root=/dev/hda3 |
| 5582 |
|
| 5583 |
<comment># The next four lines are only if you dualboot with a Windows system.</comment> |
| 5584 |
<comment># In this case, Windows is hosted on /dev/hda6.</comment> |
| 5585 |
title=Windows XP |
| 5586 |
rootnoverify (hd0,5) |
| 5587 |
makeactive |
| 5588 |
chainloader +1 |
| 5589 |
</pre> |
| 5590 |
|
| 5591 |
<pre caption="grub.conf for genkernel users"> |
| 5592 |
default 0 |
| 5593 |
timeout 30 |
| 5594 |
splashimage=(hd0,0)/boot/grub/splash.xpm.gz |
| 5595 |
|
| 5596 |
title=Gentoo Linux 2.6.12 |
| 5597 |
root (hd0,0) |
| 5598 |
kernel /boot/kernel-2.6.12-gentoo-r10 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 udev |
| 5599 |
initrd /boot/initramfs-genkernel-amd64-2.6.12-gentoo-r10 |
| 5600 |
|
| 5601 |
<comment># Only in case you want to dual-boot</comment> |
| 5602 |
title=Windows XP |
| 5603 |
root (hd0,5) |
| 5604 |
makeactive |
| 5605 |
chainloader +1 |
| 5606 |
</pre> |
| 5607 |
|
| 5608 |
<p> |
| 5609 |
If you used a different partitioning scheme and/or kernel image, adjust |
| 5610 |
accordingly. However, make sure that anything that follows a GRUB-device (such |
| 5611 |
as <path>(hd0,0)</path>) is relative to the mountpoint, not the root. In other |
| 5612 |
words, <path>(hd0,0)/grub/splash.xpm.gz</path> is in reality |
| 5613 |
<path>/boot/grub/splash.xpm.gz</path> since <path>(hd0,0)</path> is |
| 5614 |
<path>/boot</path>. |
| 5615 |
</p> |
| 5616 |
|
| 5617 |
<p> |
| 5618 |
Besides, if you chose to use a different partitioning scheme and did not put |
| 5619 |
<path>/boot</path> in a separate partition, the <path>/boot</path> prefix used |
| 5620 |
in the above code samples is really <e>required</e>. If you followed our |
| 5621 |
suggested partitioning plan, the <path>/boot</path> prefix it not required, but |
| 5622 |
a <path>boot</path> symlink makes it work. In short, the above examples should |
| 5623 |
work whether you defined a separate <path>/boot</path> partition or not. |
| 5624 |
</p> |
| 5625 |
|
| 5626 |
<p> |
| 5627 |
If you need to pass any additional options to the kernel, simply add |
| 5628 |
them to the end of the kernel command. We're already passing one option |
| 5629 |
(<c>root=/dev/hda3</c> or <c>real_root=/dev/hda3</c>), but you can pass others |
| 5630 |
as well, such as the <c>video</c> statement for framebuffer as we discussed |
| 5631 |
previously. |
| 5632 |
</p> |
| 5633 |
|
| 5634 |
<p> |
| 5635 |
<c>genkernel</c> users should know that their kernels use the same boot options |
| 5636 |
as is used for the Installation CD. For instance, if you have SCSI devices, you |
| 5637 |
should add <c>doscsi</c> as kernel option. |
| 5638 |
</p> |
| 5639 |
|
| 5640 |
<p> |
| 5641 |
Now save the <path>grub.conf</path> file and exit. We still need to install GRUB |
| 5642 |
in the MBR (Master Boot Record) though. |
| 5643 |
</p> |
| 5644 |
|
| 5645 |
<p> |
| 5646 |
The GRUB developers recommend the use of <c>grub-install</c>. However, if for |
| 5647 |
some reason <c>grub-install</c> fails to work correctly you still have the |
| 5648 |
option to manually install GRUB. |
| 5649 |
</p> |
| 5650 |
|
| 5651 |
<p> |
| 5652 |
Continue with <uri link="#grub-install-auto">Default: Setting up GRUB using |
| 5653 |
grub-install</uri> or <uri link="#grub-install-manual">Alternative: Setting up |
| 5654 |
GRUB using manual instructions</uri>. |
| 5655 |
</p> |
| 5656 |
|
| 5657 |
</body> |
| 5658 |
</subsection> |
| 5659 |
<subsection id="grub-install-auto"> |
| 5660 |
<title>Default: Setting up GRUB using grub-install</title> |
| 5661 |
<body> |
| 5662 |
|
| 5663 |
<p> |
| 5664 |
To install GRUB you will need to issue the <c>grub-install</c> command. |
| 5665 |
However, <c>grub-install</c> won't work off-the-shelf since we are inside a |
| 5666 |
chrooted environment. We need to create <path>/etc/mtab</path> which lists all |
| 5667 |
mounted filesystems. Fortunately, there is an easy way to accomplish this - |
| 5668 |
just copy over <path>/proc/mounts</path> to <path>/etc/mtab</path>, excluding |
| 5669 |
the <c>rootfs</c> line if you haven't created a separate boot partition. The |
| 5670 |
following command will work in both cases: |
| 5671 |
</p> |
| 5672 |
|
| 5673 |
<pre caption="Creating /etc/mtab"> |
| 5674 |
# <i>grep -v rootfs /proc/mounts > /etc/mtab</i> |
| 5675 |
</pre> |
| 5676 |
|
| 5677 |
<p> |
| 5678 |
Now we can install GRUB using <c>grub-install</c>: |
| 5679 |
</p> |
| 5680 |
|
| 5681 |
<pre caption="Running grub-install"> |
| 5682 |
# <i>grub-install /dev/hda</i> |
| 5683 |
</pre> |
| 5684 |
|
| 5685 |
<p> |
| 5686 |
If you have more questions regarding GRUB, please consult the <uri |
| 5687 |
link="http://www.gnu.org/software/grub/grub-faq.html">GRUB FAQ</uri> or the <uri |
| 5688 |
link="http://www.gnu.org/software/grub/manual/">GRUB Manual</uri>. |
| 5689 |
</p> |
| 5690 |
|
| 5691 |
<p> |
| 5692 |
Continue with <uri link="#reboot">Rebooting the System</uri>. |
| 5693 |
</p> |
| 5694 |
|
| 5695 |
</body> |
| 5696 |
</subsection> |
| 5697 |
<subsection id="grub-install-manual"> |
| 5698 |
<title>Alternative: Setting up GRUB using manual instructions</title> |
| 5699 |
<body> |
| 5700 |
|
| 5701 |
<p> |
| 5702 |
To start configuring GRUB, you type in <c>grub</c>. You'll be presented |
| 5703 |
with the <path>grub></path> grub command-line prompt. Now, you need to type |
| 5704 |
in the right commands to install the GRUB boot record onto your hard drive. |
| 5705 |
</p> |
| 5706 |
|
| 5707 |
<pre caption=" Starting the GRUB shell"> |
| 5708 |
# <i>grub</i> |
| 5709 |
</pre> |
| 5710 |
|
| 5711 |
<note> |
| 5712 |
If your system does not have any floppy drives, add the <c>--no-floppy</c> |
| 5713 |
option to the above command to prevent grub from probing the (non-existing) |
| 5714 |
floppy drives. |
| 5715 |
</note> |
| 5716 |
|
| 5717 |
<p> |
| 5718 |
In the example configuration we want to install GRUB so that it reads its |
| 5719 |
information from the boot-partition <path>/dev/hda1</path>, and installs the |
| 5720 |
GRUB boot record on the hard drive's MBR (master boot record) so that the first |
| 5721 |
thing we see when we turn on the computer is the GRUB prompt. Of course, if you |
| 5722 |
haven't followed the example configuration during the installation, |
| 5723 |
change the commands accordingly. |
| 5724 |
</p> |
| 5725 |
|
| 5726 |
<p> |
| 5727 |
The tab completion mechanism of GRUB can be used from within GRUB. |
| 5728 |
For instance, if you type in "<c>root (</c>" followed by a TAB, you will |
| 5729 |
be presented with a list of devices (such as <path>hd0</path>). If you |
| 5730 |
type in "<c>root (hd0,</c>" followed by a TAB, you will receive a list |
| 5731 |
of available partitions to choose from (such as <path>hd0,0</path>). |
| 5732 |
</p> |
| 5733 |
|
| 5734 |
<p> |
| 5735 |
By using the tab completion, setting up GRUB should be not that hard. |
| 5736 |
Now go on, configure GRUB, shall we? :-) |
| 5737 |
</p> |
| 5738 |
|
| 5739 |
<pre caption=" Installing GRUB in the MBR"> |
| 5740 |
grub> <i>root (hd0,0)</i> <comment>(Specify where your /boot partition resides)</comment> |
| 5741 |
grub> <i>setup (hd0)</i> <comment>(Install GRUB in the MBR)</comment> |
| 5742 |
grub> <i>quit</i> <comment>(Exit the GRUB shell)</comment> |
| 5743 |
</pre> |
| 5744 |
|
| 5745 |
<note> |
| 5746 |
If you want to install GRUB in a certain partition instead of the MBR, |
| 5747 |
you have to alter the <c>setup</c> command so it points to the right |
| 5748 |
partition. For instance, if you want GRUB installed in |
| 5749 |
<path>/dev/hda3</path>, then the command becomes <c>setup (hd0,2)</c>. |
| 5750 |
Few users however want to do this. |
| 5751 |
</note> |
| 5752 |
|
| 5753 |
<p> |
| 5754 |
If you have more questions regarding GRUB, please consult the <uri |
| 5755 |
link="http://www.gnu.org/software/grub/grub-faq.html">GRUB FAQ</uri> or the <uri |
| 5756 |
link="http://www.gnu.org/software/grub/manual/">GRUB Manual</uri>. |
| 5757 |
</p> |
| 5758 |
|
| 5759 |
<p> |
| 5760 |
Continue with <uri link="#reboot">Rebooting the System</uri>. |
| 5761 |
</p> |
| 5762 |
|
| 5763 |
</body> |
| 5764 |
</subsection> |
| 5765 |
</section> |
| 5766 |
<section id="reboot"> |
| 5767 |
<title>Rebooting the System</title> |
| 5768 |
<subsection> |
| 5769 |
<body> |
| 5770 |
|
| 5771 |
<p> |
| 5772 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
| 5773 |
that one magical command you have been waiting for: <c>reboot</c>. |
| 5774 |
</p> |
| 5775 |
|
| 5776 |
<pre caption="Unmounting all partitions and rebooting"> |
| 5777 |
# <i>exit</i> |
| 5778 |
# <i>cd</i> |
| 5779 |
# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
| 5780 |
# <i>reboot</i> |
| 5781 |
</pre> |
| 5782 |
|
| 5783 |
<p> |
| 5784 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
| 5785 |
booted again instead of your new Gentoo system. |
| 5786 |
</p> |
| 5787 |
|
| 5788 |
<p> |
| 5789 |
Once rebooted in your Gentoo installation, finish up with <uri |
| 5790 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
| 5791 |
</p> |
| 5792 |
|
| 5793 |
</body> |
| 5794 |
</subsection> |
| 5795 |
</section> |
| 5796 |
</sections> |
| 5797 |
|
| 5798 |
|
| 5799 |
|
| 5800 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-amd64-disk.xml |
| 5801 |
|
| 5802 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-amd64-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 5803 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-amd64-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 5804 |
|
| 5805 |
Index: hb-install-amd64-disk.xml |
| 5806 |
=================================================================== |
| 5807 |
<?xml version='1.0' encoding='UTF-8'?> |
| 5808 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 5809 |
|
| 5810 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 5811 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 5812 |
|
| 5813 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-amd64-disk.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 5814 |
|
| 5815 |
<sections> |
| 5816 |
|
| 5817 |
<version>5.2</version> |
| 5818 |
<date>2006-01-01</date> |
| 5819 |
|
| 5820 |
<section> |
| 5821 |
<title>Introduction to Block Devices</title> |
| 5822 |
<subsection> |
| 5823 |
<title>Block Devices</title> |
| 5824 |
<body> |
| 5825 |
|
| 5826 |
<p> |
| 5827 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
| 5828 |
and Linux in general, including Linux filesystems, partitions and block devices. |
| 5829 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
| 5830 |
you'll be guided through the process of setting up partitions and filesystems |
| 5831 |
for your Gentoo Linux installation. |
| 5832 |
</p> |
| 5833 |
|
| 5834 |
<p> |
| 5835 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
| 5836 |
probably the one that represents the first IDE drive in a Linux system, namely |
| 5837 |
<path>/dev/hda</path>. If your system uses SCSI drives, then your first hard |
| 5838 |
drive would be <path>/dev/sda</path>. |
| 5839 |
</p> |
| 5840 |
|
| 5841 |
<p> |
| 5842 |
The block devices above represent an abstract interface to the disk. User |
| 5843 |
programs can use these block devices to interact with your disk without worrying |
| 5844 |
about whether your drives are IDE, SCSI or something else. The program can |
| 5845 |
simply address the storage on the disk as a bunch of contiguous, |
| 5846 |
randomly-accessible 512-byte blocks. |
| 5847 |
</p> |
| 5848 |
|
| 5849 |
</body> |
| 5850 |
</subsection> |
| 5851 |
<subsection> |
| 5852 |
<title>Partitions and Slices</title> |
| 5853 |
<body> |
| 5854 |
|
| 5855 |
<p> |
| 5856 |
Although it is theoretically possible to use a full disk to house your Linux |
| 5857 |
system, this is almost never done in practice. Instead, full disk block devices |
| 5858 |
are split up in smaller, more manageable block devices. On amd64 systems, |
| 5859 |
these are called <e>partitions</e>. |
| 5860 |
</p> |
| 5861 |
|
| 5862 |
</body> |
| 5863 |
</subsection> |
| 5864 |
<subsection> |
| 5865 |
<title>Partitions</title> |
| 5866 |
<body> |
| 5867 |
|
| 5868 |
<p> |
| 5869 |
Partitions are divided in three types: |
| 5870 |
<e>primary</e>, <e>extended</e> and <e>logical</e>. |
| 5871 |
</p> |
| 5872 |
|
| 5873 |
<p> |
| 5874 |
A <e>primary</e> partition is a partition which has its information stored in |
| 5875 |
the MBR (master boot record). As an MBR is very small (512 bytes) only four |
| 5876 |
primary partitions can be defined (for instance, <path>/dev/hda1</path> to |
| 5877 |
<path>/dev/hda4</path>). |
| 5878 |
</p> |
| 5879 |
|
| 5880 |
<p> |
| 5881 |
An <e>extended</e> partition is a special primary partition (meaning the |
| 5882 |
extended partition must be one of the four possible primary partitions) which |
| 5883 |
contains more partitions. Such a partition didn't exist originally, but as |
| 5884 |
four partitions were too few, it was brought to life to extend the formatting |
| 5885 |
scheme without losing backward compatibility. |
| 5886 |
</p> |
| 5887 |
|
| 5888 |
<p> |
| 5889 |
A <e>logical</e> partition is a partition inside the extended partition. Their |
| 5890 |
definitions aren't placed inside the MBR, but are declared inside the extended |
| 5891 |
partition. |
| 5892 |
</p> |
| 5893 |
|
| 5894 |
</body> |
| 5895 |
</subsection> |
| 5896 |
</section> |
| 5897 |
<section> |
| 5898 |
<title>Designing a Partitioning Scheme</title> |
| 5899 |
<subsection> |
| 5900 |
<title>Default Partitioning Scheme</title> |
| 5901 |
<body> |
| 5902 |
|
| 5903 |
<p> |
| 5904 |
If you are not interested in drawing up a partitioning scheme for your system, |
| 5905 |
you can use the partitioning scheme we use throughout this book: |
| 5906 |
</p> |
| 5907 |
|
| 5908 |
<table> |
| 5909 |
<tr> |
| 5910 |
<th>Partition</th> |
| 5911 |
<th>Filesystem</th> |
| 5912 |
<th>Size</th> |
| 5913 |
<th>Description</th> |
| 5914 |
</tr> |
| 5915 |
<tr> |
| 5916 |
<ti><path>/dev/hda1</path></ti> |
| 5917 |
<ti>ext2</ti> |
| 5918 |
<ti>32M</ti> |
| 5919 |
<ti>Boot partition</ti> |
| 5920 |
</tr> |
| 5921 |
<tr> |
| 5922 |
<ti><path>/dev/hda2</path></ti> |
| 5923 |
<ti>(swap)</ti> |
| 5924 |
<ti>512M</ti> |
| 5925 |
<ti>Swap partition</ti> |
| 5926 |
</tr> |
| 5927 |
<tr> |
| 5928 |
<ti><path>/dev/hda3</path></ti> |
| 5929 |
<ti>ext3</ti> |
| 5930 |
<ti>Rest of the disk</ti> |
| 5931 |
<ti>Root partition</ti> |
| 5932 |
</tr> |
| 5933 |
</table> |
| 5934 |
|
| 5935 |
<p> |
| 5936 |
If you are interested in knowing how big a partition (or logical |
| 5937 |
volume) should be, or even how many partitions (or volumes) you need, read on. |
| 5938 |
Otherwise continue with <uri link="#fdisk">Using fdisk to Partition your |
| 5939 |
Disk</uri>. |
| 5940 |
</p> |
| 5941 |
|
| 5942 |
</body> |
| 5943 |
</subsection> |
| 5944 |
<subsection> |
| 5945 |
<title>How Many and How Big?</title> |
| 5946 |
<body> |
| 5947 |
|
| 5948 |
<p> |
| 5949 |
The number of partitions is highly dependent on your environment. For instance, |
| 5950 |
if you have lots of users, you will most likely want to have your |
| 5951 |
<path>/home</path> separate as it increases security and makes backups easier. |
| 5952 |
If you are installing Gentoo to perform as a mailserver, your |
| 5953 |
<path>/var</path> should be separate as all mails are stored inside |
| 5954 |
<path>/var</path>. A good choice of filesystem will then maximise your |
| 5955 |
performance. Gameservers will have a separate <path>/opt</path> as most gaming |
| 5956 |
servers are installed there. The reason is similar for <path>/home</path>: |
| 5957 |
security and backups. You will definitely want to keep <path>/usr</path> big: |
| 5958 |
not only will it contain the majority of applications, the Portage tree alone |
| 5959 |
takes around 500 Mbyte excluding the various sources that are stored in it. |
| 5960 |
</p> |
| 5961 |
|
| 5962 |
<p> |
| 5963 |
As you can see, it very much depends on what you want to achieve. Separate |
| 5964 |
partitions or volumes have the following advantages: |
| 5965 |
</p> |
| 5966 |
|
| 5967 |
<ul> |
| 5968 |
<li> |
| 5969 |
You can choose the best performing filesystem for each partition or volume |
| 5970 |
</li> |
| 5971 |
<li> |
| 5972 |
Your entire system cannot run out of free space if one defunct tool is |
| 5973 |
continuously writing files to a partition or volume |
| 5974 |
</li> |
| 5975 |
<li> |
| 5976 |
If necessary, file system checks are reduced in time, as multiple checks can |
| 5977 |
be done in parallel (although this advantage is more with multiple disks than |
| 5978 |
it is with multiple partitions) |
| 5979 |
</li> |
| 5980 |
<li> |
| 5981 |
Security can be enhanced by mounting some partitions or volumes read-only, |
| 5982 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
| 5983 |
</li> |
| 5984 |
</ul> |
| 5985 |
|
| 5986 |
<p> |
| 5987 |
However, multiple partitions have one big disadvantage: if not configured |
| 5988 |
properly, you might result in having a system with lots |
| 5989 |
of free space on one partition and none on another. There is also a 15-partition |
| 5990 |
limit for SCSI and SATA. |
| 5991 |
</p> |
| 5992 |
|
| 5993 |
<p> |
| 5994 |
As an example partitioning, we show you one for a 20GB disk, used as a |
| 5995 |
demonstration laptop (containing webserver, mailserver, gnome, ...): |
| 5996 |
</p> |
| 5997 |
|
| 5998 |
<pre caption="Filesystem usage example"> |
| 5999 |
Filesystem Type Size Used Avail Use% Mounted on |
| 6000 |
/dev/hda5 ext3 509M 132M 351M 28% / |
| 6001 |
/dev/hda2 ext3 5.0G 3.0G 1.8G 63% /home |
| 6002 |
/dev/hda7 ext3 7.9G 6.2G 1.3G 83% /usr |
| 6003 |
/dev/hda8 ext3 1011M 483M 477M 51% /opt |
| 6004 |
/dev/hda9 ext3 2.0G 607M 1.3G 32% /var |
| 6005 |
/dev/hda1 ext2 51M 17M 31M 36% /boot |
| 6006 |
/dev/hda6 swap 516M 12M 504M 2% <not mounted> |
| 6007 |
<comment>(Unpartitioned space for future usage: 2 GB)</comment> |
| 6008 |
</pre> |
| 6009 |
|
| 6010 |
<p> |
| 6011 |
<path>/usr</path> is rather full (83% used) here, but once |
| 6012 |
all software is installed, <path>/usr</path> doesn't tend to grow that much. |
| 6013 |
Although allocating a few gigabytes of disk space for <path>/var</path> may |
| 6014 |
seem excessive, remember that Portage uses this partition by default for |
| 6015 |
compiling packages. If you want to keep <path>/var</path> at a more reasonable |
| 6016 |
size, such as 1GB, you will need to alter your <c>PORTAGE_TMPDIR</c> variable |
| 6017 |
in <path>/etc/make.conf</path> to point to the partition with enough free space |
| 6018 |
for compiling extremely large packages such as OpenOffice. |
| 6019 |
</p> |
| 6020 |
|
| 6021 |
</body> |
| 6022 |
</subsection> |
| 6023 |
</section> |
| 6024 |
<section id="fdisk"> |
| 6025 |
<title>Using fdisk to Partition your Disk</title> |
| 6026 |
<subsection> |
| 6027 |
<body> |
| 6028 |
|
| 6029 |
<p> |
| 6030 |
The following parts explain how to create the example partition layout |
| 6031 |
described previously, namely: |
| 6032 |
</p> |
| 6033 |
|
| 6034 |
<table> |
| 6035 |
<tr> |
| 6036 |
<th>Partition</th> |
| 6037 |
<th>Description</th> |
| 6038 |
</tr> |
| 6039 |
<tr> |
| 6040 |
<ti><path>/dev/hda1</path></ti> |
| 6041 |
<ti>Boot partition</ti> |
| 6042 |
</tr> |
| 6043 |
<tr> |
| 6044 |
<ti><path>/dev/hda2</path></ti> |
| 6045 |
<ti>Swap partition</ti> |
| 6046 |
</tr> |
| 6047 |
<tr> |
| 6048 |
<ti><path>/dev/hda3</path></ti> |
| 6049 |
<ti>Root partition</ti> |
| 6050 |
</tr> |
| 6051 |
</table> |
| 6052 |
|
| 6053 |
<p> |
| 6054 |
Change your partition layout according to your own preference. |
| 6055 |
</p> |
| 6056 |
|
| 6057 |
</body> |
| 6058 |
</subsection> |
| 6059 |
<subsection> |
| 6060 |
<title>Viewing the Current Partition Layout</title> |
| 6061 |
<body> |
| 6062 |
|
| 6063 |
<p> |
| 6064 |
<c>fdisk</c> is a popular and powerful tool to split your disk into partitions. |
| 6065 |
Fire up <c>fdisk</c> on your disk (in our example, we use |
| 6066 |
<path>/dev/hda</path>): |
| 6067 |
</p> |
| 6068 |
|
| 6069 |
<pre caption="Starting fdisk"> |
| 6070 |
# <i>fdisk /dev/hda</i> |
| 6071 |
</pre> |
| 6072 |
|
| 6073 |
<p> |
| 6074 |
Once in <c>fdisk</c>, you'll be greeted with a prompt that looks like this: |
| 6075 |
</p> |
| 6076 |
|
| 6077 |
<pre caption="fdisk prompt"> |
| 6078 |
Command (m for help): |
| 6079 |
</pre> |
| 6080 |
|
| 6081 |
<p> |
| 6082 |
Type <c>p</c> to display your disk's current partition configuration: |
| 6083 |
</p> |
| 6084 |
|
| 6085 |
<pre caption="An example partition configuration"> |
| 6086 |
Command (m for help): <i>p</i> |
| 6087 |
|
| 6088 |
Disk /dev/hda: 240 heads, 63 sectors, 2184 cylinders |
| 6089 |
Units = cylinders of 15120 * 512 bytes |
| 6090 |
|
| 6091 |
Device Boot Start End Blocks Id System |
| 6092 |
/dev/hda1 1 14 105808+ 83 Linux |
| 6093 |
/dev/hda2 15 49 264600 82 Linux swap |
| 6094 |
/dev/hda3 50 70 158760 83 Linux |
| 6095 |
/dev/hda4 71 2184 15981840 5 Extended |
| 6096 |
/dev/hda5 71 209 1050808+ 83 Linux |
| 6097 |
/dev/hda6 210 348 1050808+ 83 Linux |
| 6098 |
/dev/hda7 349 626 2101648+ 83 Linux |
| 6099 |
/dev/hda8 627 904 2101648+ 83 Linux |
| 6100 |
/dev/hda9 905 2184 9676768+ 83 Linux |
| 6101 |
|
| 6102 |
Command (m for help): |
| 6103 |
</pre> |
| 6104 |
|
| 6105 |
<p> |
| 6106 |
This particular disk is configured to house seven Linux filesystems (each with a |
| 6107 |
corresponding partition listed as "Linux") as well as a swap partition (listed |
| 6108 |
as "Linux swap"). |
| 6109 |
</p> |
| 6110 |
|
| 6111 |
</body> |
| 6112 |
</subsection> |
| 6113 |
<subsection> |
| 6114 |
<title>Removing all Partitions</title> |
| 6115 |
<body> |
| 6116 |
|
| 6117 |
<p> |
| 6118 |
We will first remove all existing partitions from the disk. Type <c>d</c> to |
| 6119 |
delete a partition. For instance, to delete an existing <path>/dev/hda1</path>: |
| 6120 |
</p> |
| 6121 |
|
| 6122 |
<pre caption="Deleting a partition"> |
| 6123 |
Command (m for help): <i>d</i> |
| 6124 |
Partition number (1-4): <i>1</i> |
| 6125 |
</pre> |
| 6126 |
|
| 6127 |
<p> |
| 6128 |
The partition has been scheduled for deletion. It will no longer show up if you |
| 6129 |
type <c>p</c>, but it will not be erased until your changes have been saved. If |
| 6130 |
you made a mistake and want to abort without saving your changes, type <c>q</c> |
| 6131 |
immediately and hit enter and your partition will not be deleted. |
| 6132 |
</p> |
| 6133 |
|
| 6134 |
<p> |
| 6135 |
Now, assuming that you do indeed want to wipe out all the partitions on your |
| 6136 |
system, repeatedly type <c>p</c> to print out a partition listing and then type |
| 6137 |
<c>d</c> and the number of the partition to delete it. Eventually, you'll end |
| 6138 |
up with a partition table with nothing in it: |
| 6139 |
</p> |
| 6140 |
|
| 6141 |
<pre caption="An empty partition table"> |
| 6142 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
| 6143 |
240 heads, 63 sectors/track, 3876 cylinders |
| 6144 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
| 6145 |
|
| 6146 |
Device Boot Start End Blocks Id System |
| 6147 |
|
| 6148 |
Command (m for help): |
| 6149 |
</pre> |
| 6150 |
|
| 6151 |
<p> |
| 6152 |
Now that the in-memory partition table is empty, we're ready to create the |
| 6153 |
partitions. We will use a default partitioning scheme as discussed previously. |
| 6154 |
Of course, don't follow these instructions to the letter if you don't want the |
| 6155 |
same partitioning scheme! |
| 6156 |
</p> |
| 6157 |
|
| 6158 |
</body> |
| 6159 |
</subsection> |
| 6160 |
<subsection> |
| 6161 |
<title>Creating the Boot Partition</title> |
| 6162 |
<body> |
| 6163 |
|
| 6164 |
<p> |
| 6165 |
We first create a small boot partition. Type <c>n</c> to create a new partition, |
| 6166 |
then <c>p</c> to select a primary partition, followed by <c>1</c> to select the |
| 6167 |
first primary partition. When prompted for the first cylinder, hit enter. When |
| 6168 |
prompted for the last cylinder, type <c>+32M</c> to create a partition 32 Mbyte |
| 6169 |
in size: |
| 6170 |
</p> |
| 6171 |
|
| 6172 |
<pre caption="Creating the boot partition"> |
| 6173 |
Command (m for help): <i>n</i> |
| 6174 |
Command action |
| 6175 |
e extended |
| 6176 |
p primary partition (1-4) |
| 6177 |
<i>p</i> |
| 6178 |
Partition number (1-4): <i>1</i> |
| 6179 |
First cylinder (1-3876, default 1): <comment>(Hit Enter)</comment> |
| 6180 |
Using default value 1 |
| 6181 |
Last cylinder or +size or +sizeM or +sizeK (1-3876, default 3876): <i>+32M</i> |
| 6182 |
</pre> |
| 6183 |
|
| 6184 |
<p> |
| 6185 |
Now, when you type <c>p</c>, you should see the following partition printout: |
| 6186 |
</p> |
| 6187 |
|
| 6188 |
<pre caption="Created boot partition"> |
| 6189 |
Command (m for help): <i>p</i> |
| 6190 |
|
| 6191 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
| 6192 |
240 heads, 63 sectors/track, 3876 cylinders |
| 6193 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
| 6194 |
|
| 6195 |
Device Boot Start End Blocks Id System |
| 6196 |
/dev/hda1 1 14 105808+ 83 Linux |
| 6197 |
</pre> |
| 6198 |
|
| 6199 |
<p> |
| 6200 |
We need to make this partition bootable. Type <c>a</c> to toggle the bootable |
| 6201 |
flag on a partition and select <c>1</c>. If you press <c>p</c> again, you will |
| 6202 |
notice that an <path>*</path> is placed in the "Boot" column. |
| 6203 |
</p> |
| 6204 |
|
| 6205 |
</body> |
| 6206 |
</subsection> |
| 6207 |
<subsection> |
| 6208 |
<title>Creating the Swap Partition</title> |
| 6209 |
<body> |
| 6210 |
|
| 6211 |
<p> |
| 6212 |
Let's now create the swap partition. To do this, type <c>n</c> to create a new |
| 6213 |
partition, then <c>p</c> to tell fdisk that you want a primary partition. Then |
| 6214 |
type <c>2</c> to create the second primary partition, <path>/dev/hda2</path> in |
| 6215 |
our case. When prompted for the first cylinder, hit enter. When prompted for |
| 6216 |
the last cylinder, type <c>+512M</c> to create a partition 512MB in size. After |
| 6217 |
you've done this, type <c>t</c> to set the partition type, <c>2</c> to select |
| 6218 |
the partition you just created and then type in <c>82</c> to set the partition |
| 6219 |
type to "Linux Swap". After completing these steps, typing <c>p</c> should |
| 6220 |
display a partition table that looks similar to this: |
| 6221 |
</p> |
| 6222 |
|
| 6223 |
<pre caption="Partition listing after creating a swap partition"> |
| 6224 |
Command (m for help): <i>p</i> |
| 6225 |
|
| 6226 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
| 6227 |
240 heads, 63 sectors/track, 3876 cylinders |
| 6228 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
| 6229 |
|
| 6230 |
Device Boot Start End Blocks Id System |
| 6231 |
/dev/hda1 * 1 14 105808+ 83 Linux |
| 6232 |
/dev/hda2 15 81 506520 82 Linux swap |
| 6233 |
</pre> |
| 6234 |
|
| 6235 |
</body> |
| 6236 |
</subsection> |
| 6237 |
<subsection> |
| 6238 |
<title>Creating the Root Partition</title> |
| 6239 |
<body> |
| 6240 |
|
| 6241 |
<p> |
| 6242 |
Finally, let's create the root partition. To do this, type <c>n</c> to create a |
| 6243 |
new partition, then <c>p</c> to tell fdisk that you want a primary partition. |
| 6244 |
Then type <c>3</c> to create the third primary partition, <path>/dev/hda3</path> |
| 6245 |
in our case. When prompted for the first cylinder, hit enter. When prompted for |
| 6246 |
the last cylinder, hit enter to create a partition that takes up the rest of the |
| 6247 |
remaining space on your disk. After completing these steps, typing <c>p</c> |
| 6248 |
should display a partition table that looks similar to this: |
| 6249 |
</p> |
| 6250 |
|
| 6251 |
<pre caption="Partition listing after creating the root partition"> |
| 6252 |
Command (m for help): <i>p</i> |
| 6253 |
|
| 6254 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
| 6255 |
240 heads, 63 sectors/track, 3876 cylinders |
| 6256 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
| 6257 |
|
| 6258 |
Device Boot Start End Blocks Id System |
| 6259 |
/dev/hda1 * 1 14 105808+ 83 Linux |
| 6260 |
/dev/hda2 15 81 506520 82 Linux swap |
| 6261 |
/dev/hda3 82 3876 28690200 83 Linux |
| 6262 |
</pre> |
| 6263 |
|
| 6264 |
|
| 6265 |
</body> |
| 6266 |
</subsection> |
| 6267 |
<subsection> |
| 6268 |
<title>Saving the Partition Layout</title> |
| 6269 |
<body> |
| 6270 |
|
| 6271 |
<p> |
| 6272 |
To save the partition layout and exit <c>fdisk</c>, type <c>w</c>. |
| 6273 |
</p> |
| 6274 |
|
| 6275 |
<pre caption="Save and exit fdisk"> |
| 6276 |
Command (m for help): <i>w</i> |
| 6277 |
</pre> |
| 6278 |
|
| 6279 |
<p> |
| 6280 |
Now that your partitions are created, you can now continue with <uri |
| 6281 |
link="#filesystems">Creating Filesystems</uri>. |
| 6282 |
</p> |
| 6283 |
|
| 6284 |
</body> |
| 6285 |
</subsection> |
| 6286 |
</section> |
| 6287 |
<section id="filesystems"> |
| 6288 |
<title>Creating Filesystems</title> |
| 6289 |
<subsection> |
| 6290 |
<title>Introduction</title> |
| 6291 |
<body> |
| 6292 |
|
| 6293 |
<p> |
| 6294 |
Now that your partitions are created, it is time to place a filesystem on them. |
| 6295 |
If you don't care about what filesystem to choose and are happy with what we use |
| 6296 |
as default in this handbook, continue with <uri |
| 6297 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
| 6298 |
Otherwise read on to learn about the available filesystems... |
| 6299 |
</p> |
| 6300 |
|
| 6301 |
</body> |
| 6302 |
</subsection> |
| 6303 |
<subsection> |
| 6304 |
<title>Filesystems?</title> |
| 6305 |
<body> |
| 6306 |
|
| 6307 |
<p> |
| 6308 |
Several filesystems are available. Some of them are found stable on the amd64 |
| 6309 |
architecture, others aren't. The following filesystems are found to be stable: |
| 6310 |
ext2 and ext3. jfs and reiserfs may work but need more testing. If you're really |
| 6311 |
adventurous you can try the unsupported filesystems. |
| 6312 |
</p> |
| 6313 |
|
| 6314 |
<p> |
| 6315 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
| 6316 |
journaling, which means that routine ext2 filesystem checks at startup time can |
| 6317 |
be quite time-consuming. There is now quite a selection of newer-generation |
| 6318 |
journaled filesystems that can be checked for consistency very quickly and are |
| 6319 |
thus generally preferred over their non-journaled counterparts. Journaled |
| 6320 |
filesystems prevent long delays when you boot your system and your filesystem |
| 6321 |
happens to be in an inconsistent state. |
| 6322 |
</p> |
| 6323 |
|
| 6324 |
<p> |
| 6325 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
| 6326 |
journaling for fast recovery in addition to other enhanced journaling modes like |
| 6327 |
full data and ordered data journaling. ext3 is a very good and reliable |
| 6328 |
filesystem. It has an additional hashed b-tree indexing option that enables |
| 6329 |
high performance in almost all situations. You can enable this indexing by |
| 6330 |
adding <c>-O dir_index</c> to the <c>mke2fs</c> command. In short, ext3 is an |
| 6331 |
excellent filesystem. |
| 6332 |
</p> |
| 6333 |
|
| 6334 |
<p> |
| 6335 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
| 6336 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
| 6337 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
| 6338 |
extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is |
| 6339 |
solid and usable as both general-purpose filesystem and for extreme cases such |
| 6340 |
as the creation of large filesystems, the use of many small files, very large |
| 6341 |
files and directories containing tens of thousands of files. |
| 6342 |
</p> |
| 6343 |
|
| 6344 |
<p> |
| 6345 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
| 6346 |
feature-set and is optimized for scalability. We only recommend using this |
| 6347 |
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
| 6348 |
an uninterruptible power supply. Because XFS aggressively caches in-transit data |
| 6349 |
in RAM, improperly designed programs (those that don't take proper precautions |
| 6350 |
when writing files to disk and there are quite a few of them) can lose a good |
| 6351 |
deal of data if the system goes down unexpectedly. |
| 6352 |
</p> |
| 6353 |
|
| 6354 |
<p> |
| 6355 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
| 6356 |
become production-ready and there hasn't been a sufficient track record to |
| 6357 |
comment positively nor negatively on its general stability at this point. |
| 6358 |
</p> |
| 6359 |
|
| 6360 |
</body> |
| 6361 |
</subsection> |
| 6362 |
<subsection id="filesystems-apply"> |
| 6363 |
<title>Applying a Filesystem to a Partition</title> |
| 6364 |
<body> |
| 6365 |
|
| 6366 |
<p> |
| 6367 |
To create a filesystem on a partition or volume, there are tools available for |
| 6368 |
each possible filesystem: |
| 6369 |
</p> |
| 6370 |
|
| 6371 |
<table> |
| 6372 |
<tr> |
| 6373 |
<th>Filesystem</th> |
| 6374 |
<th>Creation Command</th> |
| 6375 |
</tr> |
| 6376 |
<tr> |
| 6377 |
<ti>ext2</ti> |
| 6378 |
<ti><c>mke2fs</c></ti> |
| 6379 |
</tr> |
| 6380 |
<tr> |
| 6381 |
<ti>ext3</ti> |
| 6382 |
<ti><c>mke2fs -j</c></ti> |
| 6383 |
</tr> |
| 6384 |
<tr> |
| 6385 |
<ti>reiserfs</ti> |
| 6386 |
<ti><c>mkreiserfs</c></ti> |
| 6387 |
</tr> |
| 6388 |
<tr> |
| 6389 |
<ti>xfs</ti> |
| 6390 |
<ti><c>mkfs.xfs</c></ti> |
| 6391 |
</tr> |
| 6392 |
<tr> |
| 6393 |
<ti>jfs</ti> |
| 6394 |
<ti><c>mkfs.jfs</c></ti> |
| 6395 |
</tr> |
| 6396 |
</table> |
| 6397 |
|
| 6398 |
<p> |
| 6399 |
For instance, to have the boot partition (<path>/dev/hda1</path> in our |
| 6400 |
example) in ext2 and the root partition (<path>/dev/hda3</path> in our example) |
| 6401 |
in ext3 (as in our example), you would use: |
| 6402 |
</p> |
| 6403 |
|
| 6404 |
<pre caption="Applying a filesystem on a partition"> |
| 6405 |
# <i>mke2fs /dev/hda1</i> |
| 6406 |
# <i>mke2fs -j /dev/hda3</i> |
| 6407 |
</pre> |
| 6408 |
|
| 6409 |
<p> |
| 6410 |
Now create the filesystems on your newly created partitions. |
| 6411 |
</p> |
| 6412 |
|
| 6413 |
</body> |
| 6414 |
</subsection> |
| 6415 |
<subsection> |
| 6416 |
<title>Activating the Swap Partition</title> |
| 6417 |
<body> |
| 6418 |
|
| 6419 |
<p> |
| 6420 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
| 6421 |
</p> |
| 6422 |
|
| 6423 |
<pre caption="Creating a Swap signature"> |
| 6424 |
# <i>mkswap /dev/hda2</i> |
| 6425 |
</pre> |
| 6426 |
|
| 6427 |
<p> |
| 6428 |
To activate the swap partition, use <c>swapon</c>: |
| 6429 |
</p> |
| 6430 |
|
| 6431 |
<pre caption="Activating the swap partition"> |
| 6432 |
# <i>swapon /dev/hda2</i> |
| 6433 |
</pre> |
| 6434 |
|
| 6435 |
<p> |
| 6436 |
Create and activate the swap now. |
| 6437 |
</p> |
| 6438 |
|
| 6439 |
</body> |
| 6440 |
</subsection> |
| 6441 |
</section> |
| 6442 |
<section> |
| 6443 |
<title>Mounting</title> |
| 6444 |
<body> |
| 6445 |
|
| 6446 |
<p> |
| 6447 |
Now that your partitions are initialized and are housing a filesystem, it is |
| 6448 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
| 6449 |
create the necessary mount directories for every partition you created. As an |
| 6450 |
example we mount the root and boot partition: |
| 6451 |
</p> |
| 6452 |
|
| 6453 |
<pre caption="Mounting partitions"> |
| 6454 |
# <i>mount /dev/hda3 /mnt/gentoo</i> |
| 6455 |
# <i>mkdir /mnt/gentoo/boot</i> |
| 6456 |
# <i>mount /dev/hda1 /mnt/gentoo/boot</i> |
| 6457 |
</pre> |
| 6458 |
|
| 6459 |
<note> |
| 6460 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
| 6461 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
| 6462 |
also holds for <path>/var/tmp</path>. |
| 6463 |
</note> |
| 6464 |
|
| 6465 |
<p> |
| 6466 |
We will also have to mount the proc filesystem (a virtual interface with the |
| 6467 |
kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. |
| 6468 |
</p> |
| 6469 |
|
| 6470 |
<p> |
| 6471 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
| 6472 |
Installation Files</uri>. |
| 6473 |
</p> |
| 6474 |
|
| 6475 |
</body> |
| 6476 |
</section> |
| 6477 |
</sections> |
| 6478 |
|
| 6479 |
|
| 6480 |
|
| 6481 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-amd64-kernel.xml |
| 6482 |
|
| 6483 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-amd64-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 6484 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-amd64-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 6485 |
|
| 6486 |
Index: hb-install-amd64-kernel.xml |
| 6487 |
=================================================================== |
| 6488 |
<?xml version='1.0' encoding='UTF-8'?> |
| 6489 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 6490 |
|
| 6491 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 6492 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 6493 |
|
| 6494 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-amd64-kernel.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 6495 |
|
| 6496 |
<sections> |
| 6497 |
|
| 6498 |
<version>5.5</version> |
| 6499 |
<date>2006-01-06</date> |
| 6500 |
|
| 6501 |
<section> |
| 6502 |
<title>Timezone</title> |
| 6503 |
<body> |
| 6504 |
|
| 6505 |
<p> |
| 6506 |
You first need to select your timezone so that your system knows where it is |
| 6507 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
| 6508 |
it to <path>/etc/localtime</path>. Please avoid the |
| 6509 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
| 6510 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
| 6511 |
</p> |
| 6512 |
|
| 6513 |
<pre caption="Setting the timezone information"> |
| 6514 |
# <i>ls /usr/share/zoneinfo</i> |
| 6515 |
<comment>(Suppose you want to use GMT)</comment> |
| 6516 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
| 6517 |
</pre> |
| 6518 |
|
| 6519 |
</body> |
| 6520 |
</section> |
| 6521 |
<section> |
| 6522 |
<title>Installing the Sources</title> |
| 6523 |
<subsection> |
| 6524 |
<title>Choosing a Kernel</title> |
| 6525 |
<body> |
| 6526 |
|
| 6527 |
<p> |
| 6528 |
The core around which all distributions are built is the Linux kernel. It is the |
| 6529 |
layer between the user programs and your system hardware. Gentoo provides its |
| 6530 |
users several possible kernel sources. A full listing with description is |
| 6531 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
| 6532 |
Guide</uri>. |
| 6533 |
</p> |
| 6534 |
|
| 6535 |
<p> |
| 6536 |
For AMD64-based systems we have <c>gentoo-sources</c> (kernel v2.6 source |
| 6537 |
patched with amd64 specific fixes for stability, performance and hardware |
| 6538 |
support). |
| 6539 |
</p> |
| 6540 |
|
| 6541 |
<p> |
| 6542 |
Choose your kernel source and install it using <c>emerge</c>. The |
| 6543 |
<c>USE="-doc"</c> is necessary to avoid installing xorg-x11 or other |
| 6544 |
dependencies at this point. <c>USE="symlink"</c> is not necessary for a new |
| 6545 |
install, but ensures proper creation of the <path>/usr/src/linux</path> |
| 6546 |
symlink. |
| 6547 |
</p> |
| 6548 |
|
| 6549 |
<pre caption="Installing a kernel source"> |
| 6550 |
# <i>USE="-doc symlink" emerge gentoo-sources</i> |
| 6551 |
</pre> |
| 6552 |
|
| 6553 |
<p> |
| 6554 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
| 6555 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
| 6556 |
kernel source points to <c>gentoo-sources-2.6.12-r10</c>. Your version may be |
| 6557 |
different, so keep this in mind. |
| 6558 |
</p> |
| 6559 |
|
| 6560 |
<pre caption="Viewing the kernel source symlink"> |
| 6561 |
# <i>ls -l /usr/src/linux</i> |
| 6562 |
lrwxrwxrwx 1 root root 12 Jul 28 11:04 /usr/src/linux -> linux-2.6.12-gentoo-r10 |
| 6563 |
</pre> |
| 6564 |
|
| 6565 |
<p> |
| 6566 |
Now it is time to configure and compile your kernel source. |
| 6567 |
You can use <c>genkernel</c> for this, which will build a generic kernel as used |
| 6568 |
by the Installation CD. We explain the "manual" configuration first though, as |
| 6569 |
it is the best way to optimize your environment. |
| 6570 |
</p> |
| 6571 |
|
| 6572 |
<p> |
| 6573 |
If you want to manually configure your kernel, continue now with <uri |
| 6574 |
link="#manual">Default: Manual Configuration</uri>. If you want to use |
| 6575 |
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
| 6576 |
genkernel</uri> instead. |
| 6577 |
</p> |
| 6578 |
|
| 6579 |
</body> |
| 6580 |
</subsection> |
| 6581 |
</section> |
| 6582 |
<section id="manual"> |
| 6583 |
<title>Default: Manual Configuration</title> |
| 6584 |
<subsection> |
| 6585 |
<title>Introduction</title> |
| 6586 |
<body> |
| 6587 |
|
| 6588 |
<p> |
| 6589 |
Manually configuring a kernel is often seen as the most difficult procedure a |
| 6590 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
| 6591 |
couple of kernels you don't even remember that it was difficult ;) |
| 6592 |
</p> |
| 6593 |
|
| 6594 |
<p> |
| 6595 |
However, one thing <e>is</e> true: you must know your system when you start |
| 6596 |
configuring a kernel manually. Most information can be gathered by emerging |
| 6597 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
| 6598 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
| 6599 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
| 6600 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
| 6601 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
| 6602 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
| 6603 |
uses (it might provide you with a nice hint on what to enable). |
| 6604 |
</p> |
| 6605 |
|
| 6606 |
<p> |
| 6607 |
Now go to your kernel source directory and execute <c>make menuconfig</c>. This |
| 6608 |
will fire up an ncurses-based configuration menu. |
| 6609 |
</p> |
| 6610 |
|
| 6611 |
<pre caption="Invoking menuconfig"> |
| 6612 |
# <i>cd /usr/src/linux</i> |
| 6613 |
# <i>make menuconfig</i> |
| 6614 |
</pre> |
| 6615 |
|
| 6616 |
<p> |
| 6617 |
You will be greeted with several configuration sections. We'll first list some |
| 6618 |
options you must activate (otherwise Gentoo will not function, or not function |
| 6619 |
properly without additional tweaks). |
| 6620 |
</p> |
| 6621 |
|
| 6622 |
</body> |
| 6623 |
</subsection> |
| 6624 |
<subsection> |
| 6625 |
<title>Activating Required Options</title> |
| 6626 |
<body> |
| 6627 |
|
| 6628 |
<p> |
| 6629 |
First of all, activate the use of development and experimental code/drivers. |
| 6630 |
You need this, otherwise some very important code/drivers won't show up: |
| 6631 |
</p> |
| 6632 |
|
| 6633 |
<pre caption="Selecting experimental code/drivers, General setup"> |
| 6634 |
Code maturity level options ---> |
| 6635 |
[*] Prompt for development and/or incomplete code/drivers |
| 6636 |
General setup ---> |
| 6637 |
[*] Support for hot-pluggable devices |
| 6638 |
</pre> |
| 6639 |
|
| 6640 |
<p> |
| 6641 |
Then we select the exact processor type. |
| 6642 |
</p> |
| 6643 |
|
| 6644 |
<pre caption="Selecting processor type and features"> |
| 6645 |
Processor type and features ---> |
| 6646 |
Processor family (AMD-Opteron/Athlon64) ---> |
| 6647 |
( ) AMD-Opteron/Athlon64 |
| 6648 |
( ) Intel EM64T |
| 6649 |
( ) Generic-x86-64" |
| 6650 |
</pre> |
| 6651 |
|
| 6652 |
<p> |
| 6653 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
| 6654 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
| 6655 |
able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc |
| 6656 |
file system</c>. |
| 6657 |
</p> |
| 6658 |
|
| 6659 |
<pre caption="Selecting necessary file systems"> |
| 6660 |
File systems ---> |
| 6661 |
Pseudo Filesystems ---> |
| 6662 |
<*> /proc file system support |
| 6663 |
<*> Virtual memory file system support (former shm fs) |
| 6664 |
|
| 6665 |
|
| 6666 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
| 6667 |
<*> Reiserfs support |
| 6668 |
<*> Ext3 journalling file system support |
| 6669 |
<*> JFS filesystem support |
| 6670 |
<*> Second extended fs support |
| 6671 |
<*> XFS filesystem support |
| 6672 |
</pre> |
| 6673 |
|
| 6674 |
<p> |
| 6675 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
| 6676 |
modem, you will need the following options in the kernel: |
| 6677 |
</p> |
| 6678 |
|
| 6679 |
<pre caption="Selecting PPPoE necessary drivers"> |
| 6680 |
Device Drivers ---> |
| 6681 |
Networking Support ---> |
| 6682 |
<*> PPP (point-to-point protocol) support |
| 6683 |
<*> PPP support for async serial ports |
| 6684 |
<*> PPP support for sync tty ports |
| 6685 |
</pre> |
| 6686 |
|
| 6687 |
<p> |
| 6688 |
The two compression options won't harm but are not definitely needed, neither |
| 6689 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
| 6690 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
| 6691 |
</p> |
| 6692 |
|
| 6693 |
<p> |
| 6694 |
If you require it, don't forget to include support in the kernel for your |
| 6695 |
ethernet card. |
| 6696 |
</p> |
| 6697 |
|
| 6698 |
<p> |
| 6699 |
If you have a multi-CPU Opteron system, you should activate "Symmetric |
| 6700 |
multi-processing support": |
| 6701 |
</p> |
| 6702 |
|
| 6703 |
<pre caption="Activating SMP support"> |
| 6704 |
Processor type and features ---> |
| 6705 |
[*] Symmetric multi-processing support |
| 6706 |
</pre> |
| 6707 |
|
| 6708 |
<p> |
| 6709 |
If you use USB Input Devices (like Keyboard or Mouse) don't forget to enable |
| 6710 |
those as well: |
| 6711 |
</p> |
| 6712 |
|
| 6713 |
<pre caption="Activating USB Support for Input Devices"> |
| 6714 |
Device Drivers ---> |
| 6715 |
USB Support ---> |
| 6716 |
<*> USB Human Interface Device (full HID) support |
| 6717 |
[*] HID input layer support |
| 6718 |
</pre> |
| 6719 |
|
| 6720 |
<p> |
| 6721 |
When you've finished configuring the kernel, continue with <uri |
| 6722 |
link="#compiling">Compiling and Installing</uri>. |
| 6723 |
</p> |
| 6724 |
|
| 6725 |
</body> |
| 6726 |
</subsection> |
| 6727 |
<subsection id="compiling"> |
| 6728 |
<title>Compiling and Installing</title> |
| 6729 |
<body> |
| 6730 |
|
| 6731 |
<p> |
| 6732 |
Now that your kernel is configured, it is time to compile and install it. Exit |
| 6733 |
the configuration and start the compilation process: |
| 6734 |
</p> |
| 6735 |
|
| 6736 |
<pre caption="Compiling the kernel"> |
| 6737 |
# <i>make && make modules_install</i> |
| 6738 |
</pre> |
| 6739 |
|
| 6740 |
<p> |
| 6741 |
When the kernel has finished compiling, copy the kernel image to |
| 6742 |
<path>/boot</path>. Use whatever name you feel is appropriate for your kernel |
| 6743 |
choice and remember it as you will need it later on when you configure your |
| 6744 |
bootloader. Remember to replace <path><kernel-version></path> with the |
| 6745 |
name and version of your kernel. |
| 6746 |
</p> |
| 6747 |
|
| 6748 |
<pre caption="Installing the kernel"> |
| 6749 |
# <i>cp arch/x86_64/boot/bzImage /boot/<kernel-version></i> |
| 6750 |
</pre> |
| 6751 |
|
| 6752 |
<p> |
| 6753 |
Now continue with <uri link="#kernel_modules">Configuring Kernel |
| 6754 |
Modules</uri>. |
| 6755 |
</p> |
| 6756 |
|
| 6757 |
</body> |
| 6758 |
</subsection> |
| 6759 |
</section> |
| 6760 |
<section id="genkernel"> |
| 6761 |
<title>Alternative: Using genkernel</title> |
| 6762 |
<body> |
| 6763 |
|
| 6764 |
<p> |
| 6765 |
If you are reading this section, you have chosen to use our <c>genkernel</c> |
| 6766 |
script to configure your kernel for you. |
| 6767 |
</p> |
| 6768 |
|
| 6769 |
<p> |
| 6770 |
Now that your kernel source tree is installed, it's now time to compile your |
| 6771 |
kernel by using our <c>genkernel</c> script to automatically build a kernel for |
| 6772 |
you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
| 6773 |
way our Installation CD kernel is configured. This means that when you use |
| 6774 |
<c>genkernel</c> to build your kernel, your system will generally detect all |
| 6775 |
your hardware at boot-time, just like our Installation CD does. Because |
| 6776 |
genkernel doesn't require any manual kernel configuration, it is an ideal |
| 6777 |
solution for those users who may not be comfortable compiling their own kernels. |
| 6778 |
</p> |
| 6779 |
|
| 6780 |
<p> |
| 6781 |
Now, let's see how to use genkernel. First, emerge the genkernel ebuild: |
| 6782 |
</p> |
| 6783 |
|
| 6784 |
<pre caption="Emerging genkernel"> |
| 6785 |
# <i>emerge genkernel</i> |
| 6786 |
</pre> |
| 6787 |
|
| 6788 |
<p> |
| 6789 |
Now, compile your kernel sources by running <c>genkernel all</c>. |
| 6790 |
Be aware though, as <c>genkernel</c> compiles a kernel that supports almost all |
| 6791 |
hardware, this compilation will take quite a while to finish! |
| 6792 |
</p> |
| 6793 |
|
| 6794 |
<p> |
| 6795 |
Note that, if your boot partition doesn't use ext2 or ext3 as filesystem you |
| 6796 |
need to manually configure your kernel using <c>genkernel --menuconfig all</c> |
| 6797 |
and add support for your filesystem <e>in</e> the kernel (i.e. <e>not</e> as a |
| 6798 |
module). |
| 6799 |
</p> |
| 6800 |
|
| 6801 |
<pre caption="Running genkernel"> |
| 6802 |
# <i>genkernel all</i> |
| 6803 |
</pre> |
| 6804 |
|
| 6805 |
<p> |
| 6806 |
Once <c>genkernel</c> completes, a kernel, full set of modules and |
| 6807 |
<e>initial root disk</e> (initrd) will be created. We will use the kernel |
| 6808 |
and initrd when configuring a boot loader later in this document. Write |
| 6809 |
down the names of the kernel and initrd as you will need it when writing |
| 6810 |
the bootloader configuration file. The initrd will be started immediately after |
| 6811 |
booting to perform hardware autodetection (just like on the Installation CD) |
| 6812 |
before your "real" system starts up. |
| 6813 |
</p> |
| 6814 |
|
| 6815 |
<pre caption="Checking the created kernel image name and initrd"> |
| 6816 |
# <i>ls /boot/kernel* /boot/initramfs*</i> |
| 6817 |
</pre> |
| 6818 |
|
| 6819 |
<p> |
| 6820 |
Now, let's perform one more step to get our system to be more like the |
| 6821 |
Installation CD -- let's emerge <c>coldplug</c>. While the initrd autodetects |
| 6822 |
hardware that is needed to boot your system, <c>coldplug</c> autodetects |
| 6823 |
everything else. To emerge and enable <c>coldplug</c>, type the following: |
| 6824 |
</p> |
| 6825 |
|
| 6826 |
<pre caption="Emerging and enabling coldplug"> |
| 6827 |
# <i>emerge coldplug</i> |
| 6828 |
# <i>rc-update add coldplug boot</i> |
| 6829 |
</pre> |
| 6830 |
|
| 6831 |
</body> |
| 6832 |
</section> |
| 6833 |
|
| 6834 |
<section id="kernel_modules"> |
| 6835 |
<title>Configuring Kernel Modules</title> |
| 6836 |
<subsection> |
| 6837 |
<title>Configuring the Modules</title> |
| 6838 |
<body> |
| 6839 |
|
| 6840 |
<p> |
| 6841 |
You should list the modules you want automatically loaded in |
| 6842 |
<path>/etc/modules.autoload.d/kernel-2.4</path> (or <path>kernel-2.6</path>). |
| 6843 |
You can add extra options to the modules too if you want. |
| 6844 |
</p> |
| 6845 |
|
| 6846 |
<p> |
| 6847 |
To view all available modules, run the following <c>find</c> command. Don't |
| 6848 |
forget to substitute "<kernel version>" with the version of the kernel you |
| 6849 |
just compiled: |
| 6850 |
</p> |
| 6851 |
|
| 6852 |
<pre caption="Viewing all available modules"> |
| 6853 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
| 6854 |
</pre> |
| 6855 |
|
| 6856 |
<p> |
| 6857 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
| 6858 |
<path>kernel-2.6</path> file and enter the module name in it. |
| 6859 |
</p> |
| 6860 |
|
| 6861 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
| 6862 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
| 6863 |
</pre> |
| 6864 |
|
| 6865 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
| 6866 |
3c59x |
| 6867 |
</pre> |
| 6868 |
|
| 6869 |
<p> |
| 6870 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
| 6871 |
your System</uri>. |
| 6872 |
</p> |
| 6873 |
|
| 6874 |
</body> |
| 6875 |
</subsection> |
| 6876 |
</section> |
| 6877 |
</sections> |
| 6878 |
|
| 6879 |
|
| 6880 |
|
| 6881 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-amd64-medium.xml |
| 6882 |
|
| 6883 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-amd64-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 6884 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-amd64-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 6885 |
|
| 6886 |
Index: hb-install-amd64-medium.xml |
| 6887 |
=================================================================== |
| 6888 |
<?xml version='1.0' encoding='UTF-8'?> |
| 6889 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 6890 |
|
| 6891 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 6892 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 6893 |
|
| 6894 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-amd64-medium.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 6895 |
|
| 6896 |
<sections> |
| 6897 |
|
| 6898 |
<version>5.3</version> |
| 6899 |
<date>2005-11-29</date> |
| 6900 |
|
| 6901 |
<section> |
| 6902 |
<title>Hardware Requirements</title> |
| 6903 |
<subsection> |
| 6904 |
<title>Introduction</title> |
| 6905 |
<body> |
| 6906 |
|
| 6907 |
<p> |
| 6908 |
Before we start, we first list what hardware requirements you need to |
| 6909 |
successfully install Gentoo on your box. |
| 6910 |
</p> |
| 6911 |
|
| 6912 |
</body> |
| 6913 |
</subsection> |
| 6914 |
<subsection> |
| 6915 |
<title>Hardware Requirements</title> |
| 6916 |
<body> |
| 6917 |
|
| 6918 |
<table> |
| 6919 |
<tr> |
| 6920 |
<th>CPU</th> |
| 6921 |
<ti>Any AMD64 CPU *</ti> |
| 6922 |
</tr> |
| 6923 |
<tr> |
| 6924 |
<th>Memory</th> |
| 6925 |
<ti>64 MB</ti> |
| 6926 |
</tr> |
| 6927 |
<tr> |
| 6928 |
<th>Diskspace</th> |
| 6929 |
<ti>1.5 GB (excluding swap space)</ti> |
| 6930 |
</tr> |
| 6931 |
<tr> |
| 6932 |
<th>Swap space</th> |
| 6933 |
<ti>At least 256 MB</ti> |
| 6934 |
</tr> |
| 6935 |
</table> |
| 6936 |
|
| 6937 |
<p> |
| 6938 |
You should check the <uri link="http://amd64.gentoo.org">Gentoo |
| 6939 |
AMD64 Project Page</uri> before proceeding. |
| 6940 |
</p> |
| 6941 |
|
| 6942 |
</body> |
| 6943 |
</subsection> |
| 6944 |
</section> |
| 6945 |
<!-- Copy/paste from hb-install-x86-medium.xml (with s/x86/amd64/) --> |
| 6946 |
<!-- START --> |
| 6947 |
<section> |
| 6948 |
<title>The Gentoo Universal Installation CD</title> |
| 6949 |
<subsection> |
| 6950 |
<title>Introduction</title> |
| 6951 |
<body> |
| 6952 |
|
| 6953 |
<p> |
| 6954 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
| 6955 |
Such a tarball is an archive that contains a minimal environment from |
| 6956 |
which you can succesfully install Gentoo Linux onto your system. |
| 6957 |
</p> |
| 6958 |
|
| 6959 |
<p> |
| 6960 |
Installations using a stage1 or stage2 tarball file are not documented in the |
| 6961 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
| 6962 |
FAQ</uri> on these matters. |
| 6963 |
</p> |
| 6964 |
|
| 6965 |
</body> |
| 6966 |
</subsection> |
| 6967 |
<subsection> |
| 6968 |
<title>Gentoo Universal Installation CD</title> |
| 6969 |
<body> |
| 6970 |
|
| 6971 |
<p> |
| 6972 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
| 6973 |
environment. It allows you to boot Linux from the CD. During the boot process |
| 6974 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
| 6975 |
Installation CDs are maintained by Gentoo developers. |
| 6976 |
</p> |
| 6977 |
|
| 6978 |
<p> |
| 6979 |
There currently are two Installation CDs available: |
| 6980 |
</p> |
| 6981 |
|
| 6982 |
<ul> |
| 6983 |
<li> |
| 6984 |
The Universal Installation CD contains everything you need to install |
| 6985 |
Gentoo. It provides stage3 files for common architectures, source code |
| 6986 |
for the extra applications you need to choose from and, of course, the |
| 6987 |
installation instructions for your architecture. |
| 6988 |
</li> |
| 6989 |
<li> |
| 6990 |
The Minimal Installation CD contains only a minimal environment that allows |
| 6991 |
you to boot up and configure your network so you can connect to the |
| 6992 |
Internet. It does not contain any additional files and cannot be used |
| 6993 |
during the current installation approach. |
| 6994 |
</li> |
| 6995 |
</ul> |
| 6996 |
|
| 6997 |
<p> |
| 6998 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
| 6999 |
additional resource that you can exploit during the installation of your Gentoo |
| 7000 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
| 7001 |
you to easily and quickly install additional applications (such as |
| 7002 |
OpenOffice.org, KDE, GNOME, ...) immediately after the Gentoo installation and |
| 7003 |
right before you update your Portage tree. |
| 7004 |
</p> |
| 7005 |
|
| 7006 |
<p> |
| 7007 |
The use of the Package CD is covered later in this document. |
| 7008 |
</p> |
| 7009 |
|
| 7010 |
</body> |
| 7011 |
</subsection> |
| 7012 |
</section> |
| 7013 |
<!-- STOP --> |
| 7014 |
<section> |
| 7015 |
<title>Download, Burn and Boot the Gentoo Universal Installation CD</title> |
| 7016 |
<subsection> |
| 7017 |
<title>Downloading and Burning the Installation CD</title> |
| 7018 |
<body> |
| 7019 |
|
| 7020 |
<p> |
| 7021 |
You can download the Universal Installation CD (and, if you want to, the |
| 7022 |
Packages CD as well) from one of our <uri |
| 7023 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CD is located in |
| 7024 |
the <path>releases/amd64/2006.0-r1/installcd</path> directory; |
| 7025 |
the Package CD is located in the <path>releases/amd64/2006.0/packagecd</path> |
| 7026 |
directory. |
| 7027 |
</p> |
| 7028 |
|
| 7029 |
<p> |
| 7030 |
Inside those directories you'll find ISO-files. Those are full CD images which |
| 7031 |
you can write on a CD-R. |
| 7032 |
</p> |
| 7033 |
|
| 7034 |
<p> |
| 7035 |
After downloading the file, you can verify its integrity to see if it is |
| 7036 |
corrupted or not: |
| 7037 |
</p> |
| 7038 |
|
| 7039 |
<ul> |
| 7040 |
<li> |
| 7041 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
| 7042 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
| 7043 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows) |
| 7044 |
</li> |
| 7045 |
<li> |
| 7046 |
You can verify the cryptographic signature that we provide. You need to |
| 7047 |
obtain the public key we use (17072058) before you proceed though. |
| 7048 |
</li> |
| 7049 |
</ul> |
| 7050 |
|
| 7051 |
<p> |
| 7052 |
To fetch our public key using the GnuPG application, run the following command: |
| 7053 |
</p> |
| 7054 |
|
| 7055 |
<pre caption="Obtaining the public key"> |
| 7056 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
| 7057 |
</pre> |
| 7058 |
|
| 7059 |
<p> |
| 7060 |
Now verify the signature: |
| 7061 |
</p> |
| 7062 |
|
| 7063 |
<pre caption="Verify the cryptographic signature"> |
| 7064 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
| 7065 |
</pre> |
| 7066 |
|
| 7067 |
<p> |
| 7068 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
| 7069 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
| 7070 |
<c>K3B</c> here; more information can be found in our <uri |
| 7071 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
| 7072 |
</p> |
| 7073 |
|
| 7074 |
<ul> |
| 7075 |
<li> |
| 7076 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
| 7077 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
| 7078 |
path). |
| 7079 |
</li> |
| 7080 |
<li> |
| 7081 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
| 7082 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
| 7083 |
<c>Start</c>. |
| 7084 |
</li> |
| 7085 |
</ul> |
| 7086 |
|
| 7087 |
</body> |
| 7088 |
</subsection> |
| 7089 |
<subsection> |
| 7090 |
<title>Booting the Universal Installation CD</title> |
| 7091 |
<body> |
| 7092 |
|
| 7093 |
<p> |
| 7094 |
Once you have burned your installation CDs, it is time to boot them. |
| 7095 |
Remove all CDs from the CD drives, reboot your system and enter the BIOS. |
| 7096 |
This is usually done by hitting DEL, F1 |
| 7097 |
or ESC, depending on your BIOS. Inside the BIOS, change the boot |
| 7098 |
order so that the CD-ROM is tried before the hard disk. This is often found |
| 7099 |
under "CMOS Setup". If you don't do this, your system will just reboot from the |
| 7100 |
hard disk, ignoring the CD-ROM. |
| 7101 |
</p> |
| 7102 |
|
| 7103 |
<p> |
| 7104 |
Now place the installation CD in the CD-ROM drive and reboot. You |
| 7105 |
should see a boot prompt. At this |
| 7106 |
screen, you can hit Enter to begin the boot process with the default |
| 7107 |
boot options, or boot the Installation CD with custom boot options by specifying |
| 7108 |
a kernel followed by boot options and then hitting Enter. |
| 7109 |
</p> |
| 7110 |
|
| 7111 |
<p> |
| 7112 |
Specifying a kernel? Yes, we provide several kernels on our Installation CD. The |
| 7113 |
default one is <c>gentoo</c>. Other kernels are for specific hardware needs and |
| 7114 |
the <c>-nofb</c> variants which disable framebuffer. |
| 7115 |
</p> |
| 7116 |
|
| 7117 |
<p> |
| 7118 |
Below you'll find a short overview on the available kernels: |
| 7119 |
</p> |
| 7120 |
|
| 7121 |
<table> |
| 7122 |
<tr> |
| 7123 |
<th>Kernel</th> |
| 7124 |
<th>Description</th> |
| 7125 |
</tr> |
| 7126 |
<tr> |
| 7127 |
<ti>gentoo</ti> |
| 7128 |
<ti>Default kernel with support for K8 CPUs with NUMA</ti> |
| 7129 |
</tr> |
| 7130 |
</table> |
| 7131 |
|
| 7132 |
<p> |
| 7133 |
You can also provide kernel options. They represent optional settings |
| 7134 |
you can (de)activate at will. The following code listing explains all available |
| 7135 |
kernel options. |
| 7136 |
</p> |
| 7137 |
|
| 7138 |
<pre caption="Available boot options"> |
| 7139 |
- agpgart loads agpgart (use if you have graphic problems,lockups) |
| 7140 |
- acpi=on loads support for ACPI firmware |
| 7141 |
- ide=nodma force disabling of DMA for malfunctioning IDE devices |
| 7142 |
- doscsi scan for scsi devices (breaks some ethernet cards) |
| 7143 |
- dopcmcia starts pcmcia service for PCMCIA cdroms |
| 7144 |
- nofirewire disables firewire modules in initrd (for firewire cdroms,etc) |
| 7145 |
- nokeymap disables keymap selection for non-us keyboard layouts |
| 7146 |
- docache cache the entire runtime portion of cd in RAM, allows you |
| 7147 |
to umount /mnt/cdrom to mount another cdrom. |
| 7148 |
- nodetect causes hwsetup/kudzu and hotplug not to run |
| 7149 |
- nousb disables usb module load from initrd, disables hotplug |
| 7150 |
- nodhcp dhcp does not automatically start if nic detected |
| 7151 |
- nohotplug disables loading hotplug service |
| 7152 |
- noapic disable apic (try if having hardware problems nics,scsi,etc) |
| 7153 |
- noevms2 disable loading of EVMS2 modules |
| 7154 |
- nolvm2 disable loading of LVM2 modules |
| 7155 |
- hdx=stroke allows you to partition the whole harddrive even when your BIOS |
| 7156 |
can't handle large harddrives |
| 7157 |
- noload=module1[,module2[,...]] |
| 7158 |
disable loading of specific kernel modules |
| 7159 |
</pre> |
| 7160 |
|
| 7161 |
<p> |
| 7162 |
Now boot your CD, select a kernel (if you are not happy with the default |
| 7163 |
<c>gentoo</c> kernel) and boot options. As an example, we show you how |
| 7164 |
to boot the <c>gentoo</c> kernel, with <c>dopcmcia</c> as kernel |
| 7165 |
parameters: |
| 7166 |
</p> |
| 7167 |
|
| 7168 |
<pre caption="Booting an Installation CD"> |
| 7169 |
boot: <i>gentoo dopcmcia</i> |
| 7170 |
</pre> |
| 7171 |
|
| 7172 |
<p> |
| 7173 |
You will then be greeted with a boot screen and progress bar. If you are |
| 7174 |
installing Gentoo on a system with a non-US keyboard, make sure you |
| 7175 |
immediately press Alt-F1 to switch to verbose mode and follow the prompt. If no |
| 7176 |
selection is made in 10 seconds, the default (US keyboard) will be accepted and |
| 7177 |
the boot process will continue. Once the boot process completes, you will be |
| 7178 |
automatically logged in to the "Live" Gentoo Linux as |
| 7179 |
"root", the super user. You should have a root ("#") prompt |
| 7180 |
on the current console and can also switch to other consoles by pressing Alt-F2, |
| 7181 |
Alt-F3 and Alt-F4. Get back to the one you started on by pressing Alt-F1. |
| 7182 |
</p> |
| 7183 |
|
| 7184 |
<p> |
| 7185 |
Now continue with <uri link="#hardware">Extra Hardware |
| 7186 |
Configuration</uri>. |
| 7187 |
</p> |
| 7188 |
|
| 7189 |
</body> |
| 7190 |
</subsection> |
| 7191 |
<subsection id="hardware"> |
| 7192 |
<title>Extra Hardware Configuration</title> |
| 7193 |
<body> |
| 7194 |
|
| 7195 |
<p> |
| 7196 |
When the Installation CD boots, it tries to detect all your hardware devices and |
| 7197 |
loads the appropriate kernel modules to support your hardware. In the |
| 7198 |
vast majority of cases, it does a very good job. However, in some cases it may |
| 7199 |
not auto-load the kernel modules you need. If the PCI auto-detection missed |
| 7200 |
some of your system's hardware, you will have to load the appropriate kernel |
| 7201 |
modules manually. |
| 7202 |
</p> |
| 7203 |
|
| 7204 |
<p> |
| 7205 |
In the next example we try to load the <c>8139too</c> module (support for |
| 7206 |
certain kinds of network interfaces): |
| 7207 |
</p> |
| 7208 |
|
| 7209 |
<pre caption="Loading kernel modules"> |
| 7210 |
# <i>modprobe 8139too</i> |
| 7211 |
</pre> |
| 7212 |
|
| 7213 |
<p> |
| 7214 |
If you need PCMCIA support, you should start the <c>pcmcia</c> init script: |
| 7215 |
</p> |
| 7216 |
|
| 7217 |
<pre caption="Starting the PCMCIA init script"> |
| 7218 |
# <i>/etc/init.d/pcmcia start</i> |
| 7219 |
</pre> |
| 7220 |
|
| 7221 |
</body> |
| 7222 |
</subsection> |
| 7223 |
<subsection> |
| 7224 |
<title>Optional: Tweaking Hard Disk Performance</title> |
| 7225 |
<body> |
| 7226 |
|
| 7227 |
<p> |
| 7228 |
If you are an advanced user, you might want to tweak the IDE hard disk |
| 7229 |
performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
| 7230 |
test the performance of your disk (execute it several times to get a |
| 7231 |
more precise impression): |
| 7232 |
</p> |
| 7233 |
|
| 7234 |
<pre caption="Testing disk performance"> |
| 7235 |
# <i>hdparm -tT /dev/hda</i> |
| 7236 |
</pre> |
| 7237 |
|
| 7238 |
<p> |
| 7239 |
To tweak, you can use any of the following examples (or experiment |
| 7240 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
| 7241 |
disk): |
| 7242 |
</p> |
| 7243 |
|
| 7244 |
<pre caption="Tweaking hard disk performance"> |
| 7245 |
<comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i> |
| 7246 |
<comment>Activate DMA + Safe Performance-enhancing Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
| 7247 |
</pre> |
| 7248 |
|
| 7249 |
</body> |
| 7250 |
</subsection> |
| 7251 |
<subsection id="useraccounts"> |
| 7252 |
<title>Optional: User Accounts</title> |
| 7253 |
<body> |
| 7254 |
|
| 7255 |
<p> |
| 7256 |
If you plan on giving other people access to your installation |
| 7257 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
| 7258 |
security reasons), you need to create the necessary user accounts and change |
| 7259 |
the root password. |
| 7260 |
</p> |
| 7261 |
|
| 7262 |
<p> |
| 7263 |
To change the root password, use the <c>passwd</c> utility: |
| 7264 |
</p> |
| 7265 |
|
| 7266 |
<pre caption="Changing the root password"> |
| 7267 |
# <i>passwd</i> |
| 7268 |
New password: <comment>(Enter your new password)</comment> |
| 7269 |
Re-enter password: <comment>(Re-enter your password)</comment> |
| 7270 |
</pre> |
| 7271 |
|
| 7272 |
<p> |
| 7273 |
To create a user account, we first enter their credentials, followed by |
| 7274 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
| 7275 |
In the next example, we create a user called "john". |
| 7276 |
</p> |
| 7277 |
|
| 7278 |
<pre caption="Creating a user account"> |
| 7279 |
# <i>useradd -m -G users john</i> |
| 7280 |
# <i>passwd john</i> |
| 7281 |
New password: <comment>(Enter john's password)</comment> |
| 7282 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
| 7283 |
</pre> |
| 7284 |
|
| 7285 |
<p> |
| 7286 |
You can change your user id from root to the newly created user by using |
| 7287 |
<c>su</c>: |
| 7288 |
</p> |
| 7289 |
|
| 7290 |
<pre caption="Changing user id"> |
| 7291 |
# <i>su - john</i> |
| 7292 |
</pre> |
| 7293 |
|
| 7294 |
</body> |
| 7295 |
</subsection> |
| 7296 |
<subsection> |
| 7297 |
<title>Optional: Viewing Documentation while Installing</title> |
| 7298 |
<body> |
| 7299 |
|
| 7300 |
<p> |
| 7301 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
| 7302 |
installation, make sure you have created a user account (see <uri |
| 7303 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
| 7304 |
go to a new terminal and log in. |
| 7305 |
</p> |
| 7306 |
|
| 7307 |
<p> |
| 7308 |
If you want to view the documentation on the CD you can immediately run |
| 7309 |
<c>links2</c> to read it: |
| 7310 |
</p> |
| 7311 |
|
| 7312 |
<pre caption="Viewing the on-CD documentation"> |
| 7313 |
# <i>links2 /mnt/cdrom/docs/handbook/html/index.html</i> |
| 7314 |
</pre> |
| 7315 |
|
| 7316 |
<p> |
| 7317 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
| 7318 |
more recent than the one provided on the CD. You can view it using <c>links2</c> |
| 7319 |
as well, but only after having completed the <e>Configuring your Network</e> |
| 7320 |
chapter (otherwise you won't be able to go on the Internet to view the |
| 7321 |
document): |
| 7322 |
</p> |
| 7323 |
|
| 7324 |
<pre caption="Viewing the Online Documentation"> |
| 7325 |
# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml</i> |
| 7326 |
</pre> |
| 7327 |
|
| 7328 |
<p> |
| 7329 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
| 7330 |
</p> |
| 7331 |
|
| 7332 |
</body> |
| 7333 |
</subsection> |
| 7334 |
<subsection> |
| 7335 |
<title>Optional: Starting the SSH Daemon</title> |
| 7336 |
<body> |
| 7337 |
|
| 7338 |
<p> |
| 7339 |
If you want to allow other users to access your computer during the |
| 7340 |
Gentoo installation (perhaps because those users are going to help you |
| 7341 |
install Gentoo, or even do it for you), you need to create a user |
| 7342 |
account for them and perhaps even provide them with your root password |
| 7343 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
| 7344 |
</p> |
| 7345 |
|
| 7346 |
<p> |
| 7347 |
To fire up the SSH daemon, execute the following command: |
| 7348 |
</p> |
| 7349 |
|
| 7350 |
<pre caption="Starting the SSH daemon"> |
| 7351 |
# <i>/etc/init.d/sshd start</i> |
| 7352 |
</pre> |
| 7353 |
|
| 7354 |
<p> |
| 7355 |
To be able to use sshd, you first need to set up your networking. Continue with |
| 7356 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
| 7357 |
</p> |
| 7358 |
|
| 7359 |
</body> |
| 7360 |
</subsection> |
| 7361 |
</section> |
| 7362 |
</sections> |
| 7363 |
|
| 7364 |
|
| 7365 |
|
| 7366 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-config.xml |
| 7367 |
|
| 7368 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-config.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 7369 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-config.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 7370 |
|
| 7371 |
Index: hb-install-config.xml |
| 7372 |
=================================================================== |
| 7373 |
<?xml version='1.0' encoding='UTF-8'?> |
| 7374 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 7375 |
|
| 7376 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 7377 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 7378 |
|
| 7379 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-config.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 7380 |
|
| 7381 |
<sections> |
| 7382 |
|
| 7383 |
<version>5.3</version> |
| 7384 |
<date>2005-11-19</date> |
| 7385 |
|
| 7386 |
<section> |
| 7387 |
<title>Filesystem Information</title> |
| 7388 |
<subsection> |
| 7389 |
<title>What is fstab?</title> |
| 7390 |
<body> |
| 7391 |
|
| 7392 |
<p> |
| 7393 |
Under Linux, all partitions used by the system must be listed in |
| 7394 |
<path>/etc/fstab</path>. This file contains the mountpoints of those partitions |
| 7395 |
(where they are seen in the file system structure), how they should be mounted |
| 7396 |
and with what special options (automatically or not, whether users can mount |
| 7397 |
them or not, etc.) |
| 7398 |
</p> |
| 7399 |
|
| 7400 |
</body> |
| 7401 |
</subsection> |
| 7402 |
<subsection> |
| 7403 |
<title>Creating /etc/fstab</title> |
| 7404 |
<body> |
| 7405 |
|
| 7406 |
<p> |
| 7407 |
<path>/etc/fstab</path> uses a special syntax. Every line consists of six |
| 7408 |
fields, separated by whitespace (space(s), tabs or a mixture). Each field has |
| 7409 |
its own meaning: |
| 7410 |
</p> |
| 7411 |
|
| 7412 |
<ul> |
| 7413 |
<li> |
| 7414 |
The first field shows the <b>partition</b> described (the path to the device |
| 7415 |
file) |
| 7416 |
</li> |
| 7417 |
<li> |
| 7418 |
The second field shows the <b>mountpoint</b> at which the partition should be |
| 7419 |
mounted |
| 7420 |
</li> |
| 7421 |
<li> |
| 7422 |
The third field shows the <b>filesystem</b> used by the partition |
| 7423 |
</li> |
| 7424 |
<li> |
| 7425 |
The fourth field shows the <b>mountoptions</b> used by <c>mount</c> when it |
| 7426 |
wants to mount the partition. As every filesystem has its own mountoptions, |
| 7427 |
you are encouraged to read the mount man page (<c>man mount</c>) for a full |
| 7428 |
listing. Multiple mountoptions are comma-separated. |
| 7429 |
</li> |
| 7430 |
<li> |
| 7431 |
The fifth field is used by <c>dump</c> to determine if the partition needs to |
| 7432 |
be <b>dump</b>ed or not. You can generally leave this as <c>0</c> (zero). |
| 7433 |
</li> |
| 7434 |
<li> |
| 7435 |
The sixth field is used by <c>fsck</c> to determine the order in which |
| 7436 |
filesystems should be <b>check</b>ed if the system wasn't shut down properly. |
| 7437 |
The root filesystem should have <c>1</c> while the rest should have <c>2</c> |
| 7438 |
(or <c>0</c> if a filesystem check isn't necessary). |
| 7439 |
</li> |
| 7440 |
</ul> |
| 7441 |
|
| 7442 |
<p> |
| 7443 |
The default <path>/etc/fstab</path> file provided by Gentoo <e>is no valid fstab |
| 7444 |
file</e>, so start <c>nano</c> (or your favorite editor) to create your |
| 7445 |
<path>/etc/fstab</path>: |
| 7446 |
</p> |
| 7447 |
|
| 7448 |
<pre caption="Opening /etc/fstab"> |
| 7449 |
# <i>nano -w /etc/fstab</i> |
| 7450 |
</pre> |
| 7451 |
|
| 7452 |
<p> |
| 7453 |
Let us take a look at how we write down the options for the <path>/boot</path> |
| 7454 |
partition. This is just an example, so if your architecture doesn't require a |
| 7455 |
<path>/boot</path> partition (such as <b>PPC</b>), don't copy it verbatim. |
| 7456 |
</p> |
| 7457 |
|
| 7458 |
<p> |
| 7459 |
In our default x86 partitioning example <path>/boot</path> is the |
| 7460 |
<path>/dev/hda1</path> partition, with <c>ext2</c> as filesystem. |
| 7461 |
It needs to be checked during boot, so we would write down: |
| 7462 |
</p> |
| 7463 |
|
| 7464 |
<pre caption="An example /boot line for /etc/fstab"> |
| 7465 |
/dev/hda1 /boot ext2 defaults 1 2 |
| 7466 |
</pre> |
| 7467 |
|
| 7468 |
<p> |
| 7469 |
Some users don't want their <path>/boot</path> partition to be mounted |
| 7470 |
automatically to improve their system's security. Those people should |
| 7471 |
substitute <c>defaults</c> with <c>noauto</c>. This does mean that you need to |
| 7472 |
manually mount this partition every time you want to use it. |
| 7473 |
</p> |
| 7474 |
|
| 7475 |
<p> |
| 7476 |
Now, to improve performance, most users would want to add the <c>noatime</c> |
| 7477 |
option as mountoption, which results in a faster system since access times |
| 7478 |
aren't registered (you don't need those generally anyway): |
| 7479 |
</p> |
| 7480 |
|
| 7481 |
<pre caption="An improved /boot line for /etc/fstab"> |
| 7482 |
/dev/hda1 /boot ext2 defaults,noatime 1 2 |
| 7483 |
</pre> |
| 7484 |
|
| 7485 |
<p> |
| 7486 |
If we continue with this, we would end up with the following three lines (for |
| 7487 |
<path>/boot</path>, <path>/</path> and the swap partition): |
| 7488 |
</p> |
| 7489 |
|
| 7490 |
<pre caption="Three /etc/fstab lines"> |
| 7491 |
/dev/hda1 /boot ext2 defaults,noatime 1 2 |
| 7492 |
/dev/hda2 none swap sw 0 0 |
| 7493 |
/dev/hda3 / ext3 noatime 0 1 |
| 7494 |
</pre> |
| 7495 |
|
| 7496 |
<p> |
| 7497 |
To finish up, you should add a rule for <path>/proc</path>, <c>tmpfs</c> |
| 7498 |
(required) and for your CD-ROM drive (and of course, if you have other |
| 7499 |
partitions or drives, for those too): |
| 7500 |
</p> |
| 7501 |
|
| 7502 |
<pre caption="A full /etc/fstab example"> |
| 7503 |
/dev/hda1 /boot ext2 defaults,noatime 1 2 |
| 7504 |
/dev/hda2 none swap sw 0 0 |
| 7505 |
/dev/hda3 / ext3 noatime 0 1 |
| 7506 |
|
| 7507 |
none /proc proc defaults 0 0 |
| 7508 |
none /dev/shm tmpfs nodev,nosuid,noexec 0 0 |
| 7509 |
|
| 7510 |
/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0 |
| 7511 |
</pre> |
| 7512 |
|
| 7513 |
<p> |
| 7514 |
<c>auto</c> makes <c>mount</c> guess for the filesystem (recommended for |
| 7515 |
removable media as they can be created with one of many filesystems) and |
| 7516 |
<c>user</c> makes it possible for non-root users to mount the CD. |
| 7517 |
</p> |
| 7518 |
|
| 7519 |
<p> |
| 7520 |
Now use the above example to create your <path>/etc/fstab</path>. If you are a |
| 7521 |
<b>SPARC</b>-user, you should add the following line to your |
| 7522 |
<path>/etc/fstab</path> |
| 7523 |
too: |
| 7524 |
</p> |
| 7525 |
|
| 7526 |
<pre caption="Adding openprom filesystem to /etc/fstab"> |
| 7527 |
none /proc/openprom openpromfs defaults 0 0 |
| 7528 |
</pre> |
| 7529 |
|
| 7530 |
<p> |
| 7531 |
Double-check your <path>/etc/fstab</path>, save and quit to continue. |
| 7532 |
</p> |
| 7533 |
|
| 7534 |
</body> |
| 7535 |
</subsection> |
| 7536 |
</section> |
| 7537 |
<section> |
| 7538 |
<title>Networking Information</title> |
| 7539 |
<subsection> |
| 7540 |
<title>Hostname, Domainname etc.</title> |
| 7541 |
<body> |
| 7542 |
|
| 7543 |
<p> |
| 7544 |
One of the choices the user has to make is name his/her PC. This seems to be |
| 7545 |
quite easy, but <e>lots</e> of users are having difficulties finding the |
| 7546 |
appropriate name for their Linux-pc. To speed things up, know that any name you |
| 7547 |
choose can be changed afterwards. For all we care, you can just call your system |
| 7548 |
<c>tux</c> and domain <c>homenetwork</c>. |
| 7549 |
</p> |
| 7550 |
|
| 7551 |
<p> |
| 7552 |
We use these values in the next examples. First we set the hostname: |
| 7553 |
</p> |
| 7554 |
|
| 7555 |
<pre caption="Setting the hostname"> |
| 7556 |
# <i>nano -w /etc/conf.d/hostname</i> |
| 7557 |
|
| 7558 |
<comment>(Set the HOSTNAME variable to your hostname)</comment> |
| 7559 |
HOSTNAME="<i>tux</i>" |
| 7560 |
</pre> |
| 7561 |
|
| 7562 |
<p> |
| 7563 |
Second we set the domainname: |
| 7564 |
</p> |
| 7565 |
|
| 7566 |
<pre caption="Setting the domainname"> |
| 7567 |
# <i>nano -w /etc/conf.d/domainname</i> |
| 7568 |
|
| 7569 |
<comment>(Set the DNSDOMAIN variable to your domain name)</comment> |
| 7570 |
DNSDOMAIN="<i>homenetwork</i>" |
| 7571 |
</pre> |
| 7572 |
|
| 7573 |
<p> |
| 7574 |
If you have a NIS domain (if you don't know what that is, then you don't have |
| 7575 |
one), you need to define that one too: |
| 7576 |
</p> |
| 7577 |
|
| 7578 |
<pre caption="Setting the NIS domainname"> |
| 7579 |
# <i>nano -w /etc/conf.d/domainname</i> |
| 7580 |
|
| 7581 |
<comment>(Set the NISDOMAIN variable to your NIS domain name)</comment> |
| 7582 |
NISDOMAIN="<i>my-nisdomain</i>" |
| 7583 |
</pre> |
| 7584 |
|
| 7585 |
<p> |
| 7586 |
Now add the <c>domainname</c> script to the default runlevel: |
| 7587 |
</p> |
| 7588 |
|
| 7589 |
<pre caption="Adding domainname to the default runlevel"> |
| 7590 |
# <i>rc-update add domainname default</i> |
| 7591 |
</pre> |
| 7592 |
|
| 7593 |
</body> |
| 7594 |
</subsection> |
| 7595 |
<subsection> |
| 7596 |
<title>Configuring your Network</title> |
| 7597 |
<body> |
| 7598 |
|
| 7599 |
<p> |
| 7600 |
Before you get that "Hey, we've had that already"-feeling, you should remember |
| 7601 |
that the networking you set up in the beginning of the Gentoo installation was |
| 7602 |
just for the installation. Right now you are going to configure networking for |
| 7603 |
your Gentoo system permanently. |
| 7604 |
</p> |
| 7605 |
|
| 7606 |
<note> |
| 7607 |
More detailed information about networking, including advanced topics like |
| 7608 |
bonding, bridging, 802.1Q VLANs or wireless networking is covered in the <uri |
| 7609 |
link="?part=4">Gentoo Network Configuration</uri> section. |
| 7610 |
</note> |
| 7611 |
|
| 7612 |
<p> |
| 7613 |
All networking information is gathered in <path>/etc/conf.d/net</path>. It uses |
| 7614 |
a straightforward yet not intuitive syntax if you don't know how to set up |
| 7615 |
networking manually. But don't fear, we'll explain everything. A fully |
| 7616 |
commented example that covers many different configurations is available in |
| 7617 |
<path>/etc/conf.d/net.example</path>. |
| 7618 |
</p> |
| 7619 |
|
| 7620 |
<p> |
| 7621 |
DHCP is used by default and does not require any further configuration. |
| 7622 |
</p> |
| 7623 |
|
| 7624 |
<p> |
| 7625 |
If you need to configure your network connection either because you need |
| 7626 |
specific DHCP options or because you do not use DHCP at all, open |
| 7627 |
<path>/etc/conf.d/net</path> with your favorite editor (<c>nano</c> is used in |
| 7628 |
this example): |
| 7629 |
</p> |
| 7630 |
|
| 7631 |
<pre caption="Opening /etc/conf.d/net for editing"> |
| 7632 |
# <i>nano -w /etc/conf.d/net</i> |
| 7633 |
</pre> |
| 7634 |
|
| 7635 |
<p> |
| 7636 |
You will see the following file: |
| 7637 |
</p> |
| 7638 |
|
| 7639 |
<pre caption="Default /etc/conf.d/net"> |
| 7640 |
# This blank configuration will automatically use DHCP for any net.* |
| 7641 |
# scripts in /etc/init.d. To create a more complete configuration, |
| 7642 |
# please review /etc/conf.d/net.example and save your configuration |
| 7643 |
# in /etc/conf.d/net (this file :]!). |
| 7644 |
</pre> |
| 7645 |
|
| 7646 |
<p> |
| 7647 |
To enter your own IP address, netmask and gateway, you need |
| 7648 |
to set both <c>config_eth0</c> and <c>routes_eth0</c>: |
| 7649 |
</p> |
| 7650 |
|
| 7651 |
<pre caption="Manually setting IP information for eth0"> |
| 7652 |
config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" ) |
| 7653 |
routes_eth0=( "default gw 192.168.0.1" ) |
| 7654 |
</pre> |
| 7655 |
|
| 7656 |
<p> |
| 7657 |
To use DHCP and add specific DHCP options, define <c>config_eth0</c> and |
| 7658 |
<c>dhcp_eth0</c>: |
| 7659 |
</p> |
| 7660 |
|
| 7661 |
<pre caption="Automatically obtaining an IP address for eth0"> |
| 7662 |
config_eth0=( "dhcp" ) |
| 7663 |
dhcp_eth0="nodns nontp nonis" |
| 7664 |
</pre> |
| 7665 |
|
| 7666 |
<p> |
| 7667 |
Please read <path>/etc/conf.d/net.example</path> for a list of all available |
| 7668 |
options. |
| 7669 |
</p> |
| 7670 |
|
| 7671 |
<p> |
| 7672 |
If you have several network interfaces repeat the above steps for |
| 7673 |
<c>config_eth1</c>, <c>config_eth2</c>, etc. |
| 7674 |
</p> |
| 7675 |
|
| 7676 |
<p> |
| 7677 |
Now save the configuration and exit to continue. |
| 7678 |
</p> |
| 7679 |
|
| 7680 |
</body> |
| 7681 |
</subsection> |
| 7682 |
<subsection> |
| 7683 |
<title>Automatically Start Networking at Boot</title> |
| 7684 |
<body> |
| 7685 |
|
| 7686 |
<p> |
| 7687 |
To have your network interfaces activated at boot, you need to add them to the |
| 7688 |
default runlevel. If you have PCMCIA interfaces you should skip this action as |
| 7689 |
the PCMCIA interfaces are started by the PCMCIA init script. |
| 7690 |
</p> |
| 7691 |
|
| 7692 |
<pre caption="Adding net.eth0 to the default runlevel"> |
| 7693 |
# <i>rc-update add net.eth0 default</i> |
| 7694 |
</pre> |
| 7695 |
|
| 7696 |
<p> |
| 7697 |
If you have several network interfaces, you need to create the appropriate |
| 7698 |
<path>net.eth1</path>, <path>net.eth2</path> etc. initscripts for those. You can |
| 7699 |
use <c>ln</c> to do this: |
| 7700 |
</p> |
| 7701 |
|
| 7702 |
<pre caption="Creating extra initscripts"> |
| 7703 |
# <i>cd /etc/init.d</i> |
| 7704 |
# <i>ln -s net.eth0 net.eth1</i> |
| 7705 |
# <i>rc-update add net.eth1 default</i> |
| 7706 |
</pre> |
| 7707 |
|
| 7708 |
</body> |
| 7709 |
</subsection> |
| 7710 |
<subsection> |
| 7711 |
<title>Writing Down Network Information</title> |
| 7712 |
<body> |
| 7713 |
|
| 7714 |
<p> |
| 7715 |
You now need to inform Linux about your network. This is defined in |
| 7716 |
<path>/etc/hosts</path> and helps in resolving hostnames to IP addresses |
| 7717 |
for hosts that aren't resolved by your nameserver. For instance, if your |
| 7718 |
internal network consists of three PCs called <c>jenny</c> (192.168.0.5), |
| 7719 |
<c>benny</c> (192.168.0.6) and <c>tux</c> (192.168.0.7 - this system) you would |
| 7720 |
open <path>/etc/hosts</path> and fill in the values: |
| 7721 |
</p> |
| 7722 |
|
| 7723 |
<pre caption="Opening /etc/hosts"> |
| 7724 |
# <i>nano -w /etc/hosts</i> |
| 7725 |
</pre> |
| 7726 |
|
| 7727 |
<pre caption="Filling in the networking information"> |
| 7728 |
127.0.0.1 localhost |
| 7729 |
192.168.0.5 jenny.homenetwork jenny |
| 7730 |
192.168.0.6 benny.homenetwork benny |
| 7731 |
192.168.0.7 tux.homenetwork tux |
| 7732 |
</pre> |
| 7733 |
|
| 7734 |
<p> |
| 7735 |
If your system is the only system (or the nameservers handle all name |
| 7736 |
resolution) a single line is sufficient. For instance, if you want to call your |
| 7737 |
system <c>tux</c>: |
| 7738 |
</p> |
| 7739 |
|
| 7740 |
<pre caption="/etc/hosts for lonely or fully integrated PCs"> |
| 7741 |
127.0.0.1 localhost tux |
| 7742 |
</pre> |
| 7743 |
|
| 7744 |
<p> |
| 7745 |
Save and exit the editor to continue. |
| 7746 |
</p> |
| 7747 |
|
| 7748 |
<p> |
| 7749 |
If you don't have PCMCIA, you can now continue with <uri |
| 7750 |
link="#doc_chap3">System Information</uri>. PCMCIA-users should read the |
| 7751 |
following topic on PCMCIA. |
| 7752 |
</p> |
| 7753 |
|
| 7754 |
</body> |
| 7755 |
</subsection> |
| 7756 |
<subsection> |
| 7757 |
<title>Optional: Get PCMCIA Working</title> |
| 7758 |
<body> |
| 7759 |
|
| 7760 |
<note> |
| 7761 |
pcmcia-cs is only available for x86, amd64 and ppc platforms. |
| 7762 |
</note> |
| 7763 |
|
| 7764 |
<p> |
| 7765 |
PCMCIA-users should first install the <c>pcmcia-cs</c> package. This also |
| 7766 |
includes users who will be working with a 2.6 kernel (even though they won't be |
| 7767 |
using the PCMCIA drivers from this package). The <c>USE="-X"</c> is necessary |
| 7768 |
to avoid installing xorg-x11 at this moment: |
| 7769 |
</p> |
| 7770 |
|
| 7771 |
<pre caption="Installing pcmcia-cs"> |
| 7772 |
# <i>USE="-X" emerge pcmcia-cs</i> |
| 7773 |
</pre> |
| 7774 |
|
| 7775 |
<p> |
| 7776 |
When <c>pcmcia-cs</c> is installed, add <c>pcmcia</c> to the <e>default</e> |
| 7777 |
runlevel: |
| 7778 |
</p> |
| 7779 |
|
| 7780 |
<pre caption="Adding pcmcia to the default runlevel"> |
| 7781 |
# <i>rc-update add pcmcia default</i> |
| 7782 |
</pre> |
| 7783 |
|
| 7784 |
</body> |
| 7785 |
</subsection> |
| 7786 |
</section> |
| 7787 |
<section> |
| 7788 |
<title>System Information</title> |
| 7789 |
<subsection> |
| 7790 |
<title>Root Password</title> |
| 7791 |
<body> |
| 7792 |
|
| 7793 |
<p> |
| 7794 |
First we set the root password by typing: |
| 7795 |
</p> |
| 7796 |
|
| 7797 |
<pre caption="Setting the root password"> |
| 7798 |
# <i>passwd</i> |
| 7799 |
</pre> |
| 7800 |
|
| 7801 |
<p> |
| 7802 |
If you want root to be able to log on through the serial console, add |
| 7803 |
<c>tts/0</c> to <path>/etc/securetty</path>: |
| 7804 |
</p> |
| 7805 |
|
| 7806 |
<pre caption="Adding tts/0 to /etc/securetty"> |
| 7807 |
# <i>echo "tts/0" >> /etc/securetty</i> |
| 7808 |
</pre> |
| 7809 |
|
| 7810 |
</body> |
| 7811 |
</subsection> |
| 7812 |
<subsection> |
| 7813 |
<title>System Information</title> |
| 7814 |
<body> |
| 7815 |
|
| 7816 |
<p> |
| 7817 |
Gentoo uses <path>/etc/rc.conf</path> for general, system-wide configuration. |
| 7818 |
Open up <path>/etc/rc.conf</path> and enjoy all the comments in that file :) |
| 7819 |
</p> |
| 7820 |
|
| 7821 |
<pre caption="Opening /etc/rc.conf"> |
| 7822 |
# <i>nano -w /etc/rc.conf</i> |
| 7823 |
</pre> |
| 7824 |
|
| 7825 |
<p> |
| 7826 |
When you're finished configuring <path>/etc/rc.conf</path>, save and exit. |
| 7827 |
</p> |
| 7828 |
|
| 7829 |
<p> |
| 7830 |
As you can see, this file is well commented to help you set up the necessary |
| 7831 |
configuration variables. You can configure your system to use unicode and |
| 7832 |
define your default editor and your display manager (like gdm or kdm). |
| 7833 |
</p> |
| 7834 |
|
| 7835 |
<p> |
| 7836 |
Gentoo uses <path>/etc/conf.d/keymaps</path> to handle keyboard configuration. |
| 7837 |
Edit it to configure your keyboard. |
| 7838 |
</p> |
| 7839 |
|
| 7840 |
<pre caption="Opening /etc/conf.d/keymaps"> |
| 7841 |
# <i>nano -w /etc/conf.d/keymaps</i> |
| 7842 |
</pre> |
| 7843 |
|
| 7844 |
<p> |
| 7845 |
Take special care with the <c>KEYMAP</c> variable. If you select the wrong |
| 7846 |
<c>KEYMAP</c>, you will get weird results when typing on your keyboard. |
| 7847 |
</p> |
| 7848 |
|
| 7849 |
<note> |
| 7850 |
Users of USB-based <b>SPARC</b> systems and <b>SPARC</b> clones might need to |
| 7851 |
select an i386 keymap (such as "us") instead of "sunkeymap". <b>PPC</b> uses x86 |
| 7852 |
keymaps on most systems. Users who want to be able to use ADB keymaps on boot |
| 7853 |
have to enable ADB keycode sendings in their kernel and have to set a mac/ppc |
| 7854 |
keymap in <path>/etc/conf.d/keymaps</path>. |
| 7855 |
</note> |
| 7856 |
|
| 7857 |
<p> |
| 7858 |
When you're finished configuring <path>/etc/conf.d/keymaps</path>, save and |
| 7859 |
exit. |
| 7860 |
</p> |
| 7861 |
|
| 7862 |
<p> |
| 7863 |
Gentoo uses <path>/etc/conf.d/clock</path> to set clock options. Edit it |
| 7864 |
according to your needs. |
| 7865 |
</p> |
| 7866 |
|
| 7867 |
<pre caption="Opening /etc/conf.d/clock"> |
| 7868 |
# <i>nano -w /etc/conf.d/clock</i> |
| 7869 |
</pre> |
| 7870 |
|
| 7871 |
<p> |
| 7872 |
If your hardware clock is not using UTC, you need to add <c>CLOCK="local"</c> to |
| 7873 |
the file. Otherwise you will notice some clock skew. |
| 7874 |
</p> |
| 7875 |
|
| 7876 |
<p> |
| 7877 |
When you're finished configuring <path>/etc/conf.d/clock</path>, save and |
| 7878 |
exit. |
| 7879 |
</p> |
| 7880 |
|
| 7881 |
<p> |
| 7882 |
If you are not installing Gentoo on IBM PPC64 hardware, continue with |
| 7883 |
<uri link="?part=1&chap=9">Installing Necessary System Tools</uri>. |
| 7884 |
</p> |
| 7885 |
|
| 7886 |
</body> |
| 7887 |
</subsection> |
| 7888 |
<subsection> |
| 7889 |
<title>Configuring the Console</title> |
| 7890 |
<body> |
| 7891 |
|
| 7892 |
<note> |
| 7893 |
The following section applies to the IBM PPC64 hardware platforms. |
| 7894 |
</note> |
| 7895 |
|
| 7896 |
<p> |
| 7897 |
If you are running Gentoo on IBM PPC64 hardware and using a virtual console |
| 7898 |
you must uncomment the appropriate line in <path>/etc/inittab</path> for the |
| 7899 |
virtual console to spawn a login prompt. |
| 7900 |
</p> |
| 7901 |
|
| 7902 |
<pre caption="Enabling hvc or hvsi support in /etc/inittab"> |
| 7903 |
hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0 |
| 7904 |
hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0 |
| 7905 |
</pre> |
| 7906 |
|
| 7907 |
<p> |
| 7908 |
You should also take this time to verify that the appropriate console is |
| 7909 |
listed in <path>/etc/securetty</path>. |
| 7910 |
</p> |
| 7911 |
|
| 7912 |
<p> |
| 7913 |
You may now continue with <uri link="?part=1&chap=9">Installing Necessary |
| 7914 |
System Tools</uri>. |
| 7915 |
</p> |
| 7916 |
|
| 7917 |
</body> |
| 7918 |
</subsection> |
| 7919 |
</section> |
| 7920 |
</sections> |
| 7921 |
|
| 7922 |
|
| 7923 |
|
| 7924 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-finalise.xml |
| 7925 |
|
| 7926 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-finalise.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 7927 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-finalise.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 7928 |
|
| 7929 |
Index: hb-install-finalise.xml |
| 7930 |
=================================================================== |
| 7931 |
<?xml version='1.0' encoding='UTF-8'?> |
| 7932 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 7933 |
|
| 7934 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 7935 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
| 7936 |
|
| 7937 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-finalise.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 7938 |
|
| 7939 |
<sections> |
| 7940 |
|
| 7941 |
<version>5.3</version> |
| 7942 |
<date>2006-01-23</date> |
| 7943 |
|
| 7944 |
<section> |
| 7945 |
<title>User Administration</title> |
| 7946 |
<subsection> |
| 7947 |
<title>Adding a User for Daily Use</title> |
| 7948 |
<body> |
| 7949 |
|
| 7950 |
<p> |
| 7951 |
Working as root on a Unix/Linux system is <e>dangerous</e> and should be avoided |
| 7952 |
as much as possible. Therefore it is <e>strongly</e> recommended to add a user |
| 7953 |
for day-to-day use. |
| 7954 |
</p> |
| 7955 |
|
| 7956 |
<p> |
| 7957 |
The groups the user is member of define what activities the user can perform. |
| 7958 |
The following table lists a number of important groups you might wish to use: |
| 7959 |
</p> |
| 7960 |
|
| 7961 |
<table> |
| 7962 |
<tr> |
| 7963 |
<th>Group</th> |
| 7964 |
<th>Description</th> |
| 7965 |
</tr> |
| 7966 |
<tr> |
| 7967 |
<ti>audio</ti> |
| 7968 |
<ti>be able to access the audio devices</ti> |
| 7969 |
</tr> |
| 7970 |
<tr> |
| 7971 |
<ti>cdrom</ti> |
| 7972 |
<ti>be able to directly access optical devices</ti> |
| 7973 |
</tr> |
| 7974 |
<tr> |
| 7975 |
<ti>floppy</ti> |
| 7976 |
<ti>be able to directly access floppy devices</ti> |
| 7977 |
</tr> |
| 7978 |
<tr> |
| 7979 |
<ti>games</ti> |
| 7980 |
<ti>be able to play games</ti> |
| 7981 |
</tr> |
| 7982 |
<tr> |
| 7983 |
<ti>portage</ti> |
| 7984 |
<ti>be able to use <c>emerge --pretend</c> as a normal user</ti> |
| 7985 |
</tr> |
| 7986 |
<tr> |
| 7987 |
<ti>usb</ti> |
| 7988 |
<ti>be able to access USB devices</ti> |
| 7989 |
</tr> |
| 7990 |
<tr> |
| 7991 |
<ti>plugdev</ti> |
| 7992 |
<ti> |
| 7993 |
Be able to mount and use pluggable devices such as cameras and USB sticks |
| 7994 |
</ti> |
| 7995 |
</tr> |
| 7996 |
<tr> |
| 7997 |
<ti>video</ti> |
| 7998 |
<ti> |
| 7999 |
be able to access video capturing hardware and doing hardware |
| 8000 |
acceleration |
| 8001 |
</ti> |
| 8002 |
</tr> |
| 8003 |
<tr> |
| 8004 |
<ti>wheel</ti> |
| 8005 |
<ti>be able to use <c>su</c></ti> |
| 8006 |
</tr> |
| 8007 |
</table> |
| 8008 |
|
| 8009 |
<p> |
| 8010 |
For instance, to create a user called <c>john</c> who is member of the |
| 8011 |
<c>wheel</c>, <c>users</c> and <c>audio</c> groups, log in as root first |
| 8012 |
(only root can create users) and run <c>useradd</c>: |
| 8013 |
</p> |
| 8014 |
|
| 8015 |
<pre caption="Adding a user for day-to-day use"> |
| 8016 |
Login: <i>root</i> |
| 8017 |
Password: <comment>(Your root password)</comment> |
| 8018 |
|
| 8019 |
# <i>useradd -m -G users,wheel,audio -s /bin/bash john</i> |
| 8020 |
# <i>passwd john</i> |
| 8021 |
Password: <comment>(Enter the password for john)</comment> |
| 8022 |
Re-enter password: <comment>(Re-enter the password to verify)</comment> |
| 8023 |
</pre> |
| 8024 |
|
| 8025 |
<p> |
| 8026 |
If a user ever needs to perform some task as root, they can use <c>su -</c> |
| 8027 |
to temporarily receive root privileges. Another way is to use the <c>sudo</c> |
| 8028 |
package which is, if correctly configured, very secure. |
| 8029 |
</p> |
| 8030 |
|
| 8031 |
</body> |
| 8032 |
</subsection> |
| 8033 |
</section> |
| 8034 |
<section> |
| 8035 |
<title>Optional: Install GRP Packages</title> |
| 8036 |
<body> |
| 8037 |
|
| 8038 |
<impo> |
| 8039 |
This part is for GRP users only. Other users should skip this part and continue |
| 8040 |
with <uri link="?part=1&chap=12">Where to go from here?</uri>. |
| 8041 |
</impo> |
| 8042 |
|
| 8043 |
<p> |
| 8044 |
Now that your system is booted, log on as the user you created (for instance, |
| 8045 |
<c>john</c>) and use <c>su -</c> to gain root privileges: |
| 8046 |
</p> |
| 8047 |
|
| 8048 |
<pre caption="Gaining root privileges"> |
| 8049 |
$ <i>su -</i> |
| 8050 |
Password: <comment>(Enter your root password)</comment> |
| 8051 |
</pre> |
| 8052 |
|
| 8053 |
<p> |
| 8054 |
Now we need to change the Portage configuration to look for the prebuilt |
| 8055 |
binaries from the second CD (Gentoo Packages CD). First mount this CD: |
| 8056 |
</p> |
| 8057 |
|
| 8058 |
<pre caption="Mount the Packages CD"> |
| 8059 |
<comment>(Put the Gentoo Packages CD in the CD tray)</comment> |
| 8060 |
# <i>mount /mnt/cdrom</i> |
| 8061 |
</pre> |
| 8062 |
|
| 8063 |
<p> |
| 8064 |
Now configure Portage to use <path>/mnt/cdrom</path> for its prebuilt packages: |
| 8065 |
</p> |
| 8066 |
|
| 8067 |
<pre caption="Configuring Portage to use /mnt/cdrom"> |
| 8068 |
# <i>ls /mnt/cdrom</i> |
| 8069 |
|
| 8070 |
<comment>(If there is a /mnt/cdrom/packages directory:)</comment> |
| 8071 |
# <i>export PKGDIR="/mnt/cdrom/packages"</i> |
| 8072 |
|
| 8073 |
<comment>(Otherwise:)</comment> |
| 8074 |
# <i>export PKGDIR="/mnt/cdrom"</i> |
| 8075 |
</pre> |
| 8076 |
|
| 8077 |
<p> |
| 8078 |
Now install the packages you want. The Packages CD contains several prebuilt |
| 8079 |
binaries, for instance KDE and GNOME. |
| 8080 |
</p> |
| 8081 |
|
| 8082 |
<pre caption="Installing GNOME"> |
| 8083 |
# <i>emerge --usepkg gnome</i> |
| 8084 |
</pre> |
| 8085 |
|
| 8086 |
<p> |
| 8087 |
To find out what prebuilt packages are available, do a quick listing of all |
| 8088 |
the files in <path>/mnt/cdrom/All</path>. For instance, to find out if KDE is |
| 8089 |
emergeable: |
| 8090 |
</p> |
| 8091 |
|
| 8092 |
<pre caption="Finding out if KDE is installable"> |
| 8093 |
# <i>ls /mnt/cdrom/All/kde*</i> |
| 8094 |
</pre> |
| 8095 |
|
| 8096 |
<p> |
| 8097 |
Be sure to install the binaries now. When you do an <c>emerge --sync</c> to |
| 8098 |
update Portage (as you will learn later), the prebuilt binaries might not match |
| 8099 |
against the ebuilds in your updated Portage. You can try to circumvent this by |
| 8100 |
using <c>emerge --usepkgonly</c> instead of <c>emerge --usepkg</c>. |
| 8101 |
</p> |
| 8102 |
|
| 8103 |
<p> |
| 8104 |
Congratulations, your system is now fully equipped! Continue with <uri |
| 8105 |
link="?part=1&chap=12">Where to go from here?</uri> to learn more about |
| 8106 |
Gentoo. |
| 8107 |
</p> |
| 8108 |
|
| 8109 |
</body> |
| 8110 |
</section> |
| 8111 |
</sections> |
| 8112 |
|
| 8113 |
|
| 8114 |
|
| 8115 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-hppa-bootloader.xml |
| 8116 |
|
| 8117 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-hppa-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 8118 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-hppa-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 8119 |
|
| 8120 |
Index: hb-install-hppa-bootloader.xml |
| 8121 |
=================================================================== |
| 8122 |
<?xml version='1.0' encoding='UTF-8'?> |
| 8123 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 8124 |
|
| 8125 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 8126 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
| 8127 |
|
| 8128 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-hppa-bootloader.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 8129 |
|
| 8130 |
<sections> |
| 8131 |
|
| 8132 |
<version>5.1</version> |
| 8133 |
<date>2006-01-19</date> |
| 8134 |
|
| 8135 |
<section> |
| 8136 |
<title>Installing PALO</title> |
| 8137 |
<body> |
| 8138 |
|
| 8139 |
<p> |
| 8140 |
On the PA-RISC platform, the boot loader is called palo. You can find |
| 8141 |
the configuration file in <path>/etc/palo.conf</path>. Here is a sample |
| 8142 |
configuration: |
| 8143 |
</p> |
| 8144 |
|
| 8145 |
<pre caption = "/etc/palo.conf example"> |
| 8146 |
--commandline=2/kernel-2.6.12.2-pa2 root=/dev/sda4 |
| 8147 |
--recoverykernel=/vmlinux.old |
| 8148 |
--init-partitioned=/dev/sda |
| 8149 |
</pre> |
| 8150 |
|
| 8151 |
<p> |
| 8152 |
The first line tells palo the location of the kernel and which boot |
| 8153 |
parameters it must use. <c>2/kernel-2.6.12.2-pa2</c> means the kernel named |
| 8154 |
<c>kernel-2.6.12.2-pa2</c> resides on the second partition. Beware, the path |
| 8155 |
to the kernel is relative to the partition, not to the root of your filesystem. |
| 8156 |
</p> |
| 8157 |
|
| 8158 |
<p> |
| 8159 |
The second line indicates which recovery kernel to use. If it is your |
| 8160 |
first install and you do not have a recovery kernel, please comment this |
| 8161 |
out. The third line indicates on which disk palo will reside. |
| 8162 |
</p> |
| 8163 |
|
| 8164 |
<p> |
| 8165 |
When configuration is done, just run <c>palo</c>. |
| 8166 |
</p> |
| 8167 |
|
| 8168 |
<pre caption = "Applying the PALO configuration"> |
| 8169 |
# <i>palo</i> |
| 8170 |
</pre> |
| 8171 |
|
| 8172 |
<p> |
| 8173 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
| 8174 |
</p> |
| 8175 |
|
| 8176 |
</body> |
| 8177 |
</section> |
| 8178 |
<section id="reboot"> |
| 8179 |
<title>Rebooting the System</title> |
| 8180 |
<subsection> |
| 8181 |
<body> |
| 8182 |
|
| 8183 |
<p> |
| 8184 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
| 8185 |
that one magical command you have been waiting for: <c>reboot</c>. |
| 8186 |
</p> |
| 8187 |
|
| 8188 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
| 8189 |
# <i>exit</i> |
| 8190 |
cdimage ~# <i>cd</i> |
| 8191 |
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
| 8192 |
cdimage ~# <i>reboot</i> |
| 8193 |
</pre> |
| 8194 |
|
| 8195 |
<p> |
| 8196 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
| 8197 |
booted again instead of your new Gentoo system. |
| 8198 |
</p> |
| 8199 |
|
| 8200 |
<p> |
| 8201 |
Once rebooted in your Gentoo installation, finish up with <uri |
| 8202 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
| 8203 |
</p> |
| 8204 |
|
| 8205 |
</body> |
| 8206 |
</subsection> |
| 8207 |
</section> |
| 8208 |
</sections> |
| 8209 |
|
| 8210 |
|
| 8211 |
|
| 8212 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-hppa-disk.xml |
| 8213 |
|
| 8214 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-hppa-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 8215 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-hppa-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 8216 |
|
| 8217 |
Index: hb-install-hppa-disk.xml |
| 8218 |
=================================================================== |
| 8219 |
<?xml version='1.0' encoding='UTF-8'?> |
| 8220 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 8221 |
|
| 8222 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 8223 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 8224 |
|
| 8225 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-hppa-disk.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 8226 |
|
| 8227 |
<sections> |
| 8228 |
|
| 8229 |
<version>5.1</version> |
| 8230 |
<date>2005-08-25</date> |
| 8231 |
|
| 8232 |
<section> |
| 8233 |
<title>Introduction to Block Devices</title> |
| 8234 |
<subsection> |
| 8235 |
<title>Block Devices</title> |
| 8236 |
<body> |
| 8237 |
|
| 8238 |
<p> |
| 8239 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
| 8240 |
and Linux in general, including Linux filesystems, partitions and block devices. |
| 8241 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
| 8242 |
you'll be guided through the process of setting up partitions and filesystems |
| 8243 |
for your Gentoo Linux installation. |
| 8244 |
</p> |
| 8245 |
|
| 8246 |
<p> |
| 8247 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
| 8248 |
probably the one that represents the first SCSI HD in a Linux system, namely |
| 8249 |
<path>/dev/sda</path>. |
| 8250 |
</p> |
| 8251 |
|
| 8252 |
<p> |
| 8253 |
The block devices above represent an abstract interface to the disk. User |
| 8254 |
programs can use these block devices to interact with your disk without worrying |
| 8255 |
about whether your drives are IDE, SCSI or something else. The program can |
| 8256 |
simply address the storage on the disk as a bunch of contiguous, |
| 8257 |
randomly-accessible 512-byte blocks. |
| 8258 |
</p> |
| 8259 |
|
| 8260 |
</body> |
| 8261 |
</subsection> |
| 8262 |
<subsection> |
| 8263 |
<title>Partitions and Slices</title> |
| 8264 |
<body> |
| 8265 |
|
| 8266 |
<p> |
| 8267 |
Although it is theoretically possible to use a full disk to house your Linux |
| 8268 |
system, this is almost never done in practice. Instead, full disk block devices |
| 8269 |
are split up in smaller, more manageable block devices. On most systems, |
| 8270 |
these are called <e>partitions</e>. Other architectures use a similar technique, |
| 8271 |
called <e>slices</e>. |
| 8272 |
</p> |
| 8273 |
|
| 8274 |
</body> |
| 8275 |
</subsection> |
| 8276 |
</section> |
| 8277 |
<section> |
| 8278 |
<title>Designing a Partitioning Scheme</title> |
| 8279 |
<subsection> |
| 8280 |
<title>How Many and How Big?</title> |
| 8281 |
<body> |
| 8282 |
|
| 8283 |
<p> |
| 8284 |
The number of partitions is highly dependent on your environment. For instance, |
| 8285 |
if you have lots of users, you will most likely want to have your |
| 8286 |
<path>/home</path> separate as it increases security and makes backups easier. |
| 8287 |
If you are installing Gentoo to perform as a mailserver, your |
| 8288 |
<path>/var</path> should be separate as all mails are stored inside |
| 8289 |
<path>/var</path>. A good choice of filesystem will then maximise your |
| 8290 |
performance. Gameservers will have a separate <path>/opt</path> as most gaming |
| 8291 |
servers are installed there. The reason is similar for <path>/home</path>: |
| 8292 |
security and backups. You will definitely want to keep <path>/usr</path> big: |
| 8293 |
not only will it contain the majority of applications, the Portage tree alone |
| 8294 |
takes around 500 Mbyte excluding the various sources that are stored in it. |
| 8295 |
</p> |
| 8296 |
|
| 8297 |
<p> |
| 8298 |
As you can see, it very much depends on what you want to achieve. Separate |
| 8299 |
partitions or volumes have the following advantages: |
| 8300 |
</p> |
| 8301 |
|
| 8302 |
<ul> |
| 8303 |
<li> |
| 8304 |
You can choose the best performing filesystem for each partition or volume |
| 8305 |
</li> |
| 8306 |
<li> |
| 8307 |
Your entire system cannot run out of free space if one defunct tool is |
| 8308 |
continuously writing files to a partition or volume |
| 8309 |
</li> |
| 8310 |
<li> |
| 8311 |
If necessary, file system checks are reduced in time, as multiple checks can |
| 8312 |
be done in parallel (although this advantage is more with multiple disks than |
| 8313 |
it is with multiple partitions) |
| 8314 |
</li> |
| 8315 |
<li> |
| 8316 |
Security can be enhanced by mounting some partitions or volumes read-only, |
| 8317 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
| 8318 |
</li> |
| 8319 |
</ul> |
| 8320 |
|
| 8321 |
<p> |
| 8322 |
However, multiple partitions have one big disadvantage: if not configured |
| 8323 |
properly, you might result in having a system with lots |
| 8324 |
of free space on one partition and none on another. There is also a 15-partition |
| 8325 |
limit for SCSI and SATA. |
| 8326 |
</p> |
| 8327 |
|
| 8328 |
</body> |
| 8329 |
</subsection> |
| 8330 |
</section> |
| 8331 |
<section> |
| 8332 |
<title>Using fdisk on HPPA to Partition your Disk</title> |
| 8333 |
<body> |
| 8334 |
|
| 8335 |
<p> |
| 8336 |
Use <c>fdisk</c> to create the partitions you want: |
| 8337 |
</p> |
| 8338 |
|
| 8339 |
<pre caption="Partitioning the disk"> |
| 8340 |
# <i>fdisk /dev/sda</i> |
| 8341 |
</pre> |
| 8342 |
|
| 8343 |
<p> |
| 8344 |
HPPA machines use the PC standard DOS partition tables. To create a new |
| 8345 |
DOS partition table, simply use the <c>o</c> command. |
| 8346 |
</p> |
| 8347 |
|
| 8348 |
<pre caption="Creating a DOS partition table"> |
| 8349 |
# <i>fdisk /dev/sda</i> |
| 8350 |
|
| 8351 |
Command (m for help): <i>o</i> |
| 8352 |
Building a new DOS disklabel. |
| 8353 |
</pre> |
| 8354 |
|
| 8355 |
<p> |
| 8356 |
PALO (the HPPA bootloader) needs a special partition to work. You have |
| 8357 |
to create a partition of at least 16MB at the beginning of your disk. |
| 8358 |
The partition type must be of type <e>f0</e> (Linux/PA-RISC boot). |
| 8359 |
</p> |
| 8360 |
|
| 8361 |
<impo> |
| 8362 |
If you ignore this and continue without a special PALO partition, your system |
| 8363 |
will stop loving you and fail to start. Also, if your disk is larger than 2GB, |
| 8364 |
make sure that the boot partition is in the first 2GB of your disk. PALO is |
| 8365 |
unable to read a kernel after the 2GB limit. |
| 8366 |
</impo> |
| 8367 |
|
| 8368 |
<pre caption="A simple default partition schema"> |
| 8369 |
# <i>cat /etc/fstab</i> |
| 8370 |
/dev/sda2 /boot ext3 noauto,noatime 1 1 |
| 8371 |
/dev/sda3 none swap sw 0 0 |
| 8372 |
/dev/sda4 / ext3 noatime 0 0 |
| 8373 |
|
| 8374 |
# <i>fdisk /dev/sda</i> |
| 8375 |
|
| 8376 |
Command (m for help): <i>p</i> |
| 8377 |
|
| 8378 |
Disk /dev/sda: 4294 MB, 4294816768 bytes |
| 8379 |
133 heads, 62 sectors/track, 1017 cylinders |
| 8380 |
Units = cylinders of 8246 * 512 = 4221952 bytes |
| 8381 |
|
| 8382 |
Device Boot Start End Blocks Id System |
| 8383 |
/dev/sda1 1 8 32953 f0 Linux/PA-RISC boot |
| 8384 |
/dev/sda2 9 20 49476 83 Linux |
| 8385 |
/dev/sda3 21 70 206150 82 Linux swap |
| 8386 |
/dev/sda4 71 1017 3904481 83 Linux |
| 8387 |
</pre> |
| 8388 |
|
| 8389 |
<p> |
| 8390 |
Now that your partitions are created, you can now continue with <uri |
| 8391 |
link="#filesystems">Creating Filesystems</uri>. |
| 8392 |
</p> |
| 8393 |
|
| 8394 |
</body> |
| 8395 |
</section> |
| 8396 |
<section id="filesystems"> |
| 8397 |
<title>Creating Filesystems</title> |
| 8398 |
<subsection> |
| 8399 |
<title>Introduction</title> |
| 8400 |
<body> |
| 8401 |
|
| 8402 |
<p> |
| 8403 |
Now that your partitions are created, it is time to place a filesystem on them. |
| 8404 |
If you don't care about what filesystem to choose and are happy with what we use |
| 8405 |
as default in this handbook, continue with <uri |
| 8406 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
| 8407 |
Otherwise read on to learn about the available filesystems... |
| 8408 |
</p> |
| 8409 |
|
| 8410 |
</body> |
| 8411 |
</subsection> |
| 8412 |
<subsection> |
| 8413 |
<title>Filesystems?</title> |
| 8414 |
<body> |
| 8415 |
|
| 8416 |
<p> |
| 8417 |
Several filesystems are available. Ext2, ext3, XFS and reiserfs are found stable on |
| 8418 |
the HPPA architecture. The others are very experimental. |
| 8419 |
</p> |
| 8420 |
|
| 8421 |
<p> |
| 8422 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
| 8423 |
journaling, which means that routine ext2 filesystem checks at startup time can |
| 8424 |
be quite time-consuming. There is now quite a selection of newer-generation |
| 8425 |
journaled filesystems that can be checked for consistency very quickly and are |
| 8426 |
thus generally preferred over their non-journaled counterparts. Journaled |
| 8427 |
filesystems prevent long delays when you boot your system and your filesystem |
| 8428 |
happens to be in an inconsistent state. |
| 8429 |
</p> |
| 8430 |
|
| 8431 |
<p> |
| 8432 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
| 8433 |
journaling for fast recovery in addition to other enhanced journaling modes like |
| 8434 |
full data and ordered data journaling. ext3 is a very good and reliable |
| 8435 |
filesystem. It has an additional hashed b-tree indexing option that enables |
| 8436 |
high performance in almost all situations. You can enable this indexing by |
| 8437 |
adding <c>-O dir_index</c> to the <c>mke2fs</c> command. In short, ext3 is an |
| 8438 |
excellent filesystem. |
| 8439 |
</p> |
| 8440 |
|
| 8441 |
<p> |
| 8442 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
| 8443 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
| 8444 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
| 8445 |
extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is |
| 8446 |
solid and usable as both general-purpose filesystem and for extreme cases such |
| 8447 |
as the creation of large filesystems, the use of many small files, very large |
| 8448 |
files and directories containing tens of thousands of files. |
| 8449 |
</p> |
| 8450 |
|
| 8451 |
<p> |
| 8452 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
| 8453 |
feature-set and is optimized for scalability. We only recommend using this |
| 8454 |
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
| 8455 |
an uninterruptible power supply. Because XFS aggressively caches in-transit data |
| 8456 |
in RAM, improperly designed programs (those that don't take proper precautions |
| 8457 |
when writing files to disk and there are quite a few of them) can lose a good |
| 8458 |
deal of data if the system goes down unexpectedly. |
| 8459 |
</p> |
| 8460 |
|
| 8461 |
<p> |
| 8462 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
| 8463 |
become production-ready and there hasn't been a sufficient track record to |
| 8464 |
comment positively nor negatively on its general stability at this point. |
| 8465 |
</p> |
| 8466 |
|
| 8467 |
</body> |
| 8468 |
</subsection> |
| 8469 |
<subsection id="filesystems-apply"> |
| 8470 |
<title>Applying a Filesystem to a Partition</title> |
| 8471 |
<body> |
| 8472 |
|
| 8473 |
<p> |
| 8474 |
To create a filesystem on a partition or volume, there are tools available for |
| 8475 |
each possible filesystem: |
| 8476 |
</p> |
| 8477 |
|
| 8478 |
<table> |
| 8479 |
<tr> |
| 8480 |
<th>Filesystem</th> |
| 8481 |
<th>Creation Command</th> |
| 8482 |
</tr> |
| 8483 |
<tr> |
| 8484 |
<ti>ext2</ti> |
| 8485 |
<ti><c>mke2fs</c></ti> |
| 8486 |
</tr> |
| 8487 |
<tr> |
| 8488 |
<ti>ext3</ti> |
| 8489 |
<ti><c>mke2fs -j</c></ti> |
| 8490 |
</tr> |
| 8491 |
<tr> |
| 8492 |
<ti>reiserfs</ti> |
| 8493 |
<ti><c>mkreiserfs</c></ti> |
| 8494 |
</tr> |
| 8495 |
<tr> |
| 8496 |
<ti>xfs</ti> |
| 8497 |
<ti><c>mkfs.xfs</c></ti> |
| 8498 |
</tr> |
| 8499 |
<tr> |
| 8500 |
<ti>jfs</ti> |
| 8501 |
<ti><c>mkfs.jfs</c></ti> |
| 8502 |
</tr> |
| 8503 |
</table> |
| 8504 |
|
| 8505 |
<p> |
| 8506 |
For instance, to have the boot partition (<path>/dev/sda2</path> in our |
| 8507 |
example) in ext2 and the root partition (<path>/dev/sda4</path> in our example) |
| 8508 |
in ext3 (as in our example), you would use: |
| 8509 |
</p> |
| 8510 |
|
| 8511 |
<pre caption="Applying a filesystem on a partition"> |
| 8512 |
# <i>mke2fs /dev/sda2</i> |
| 8513 |
# <i>mke2fs -j /dev/sda4</i> |
| 8514 |
</pre> |
| 8515 |
|
| 8516 |
<p> |
| 8517 |
Now create the filesystems on your newly created partitions (or logical |
| 8518 |
volumes). |
| 8519 |
</p> |
| 8520 |
|
| 8521 |
</body> |
| 8522 |
</subsection> |
| 8523 |
<subsection> |
| 8524 |
<title>Activating the Swap Partition</title> |
| 8525 |
<body> |
| 8526 |
|
| 8527 |
<p> |
| 8528 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
| 8529 |
</p> |
| 8530 |
|
| 8531 |
<pre caption="Creating a Swap signature"> |
| 8532 |
# <i>mkswap /dev/sda3</i> |
| 8533 |
</pre> |
| 8534 |
|
| 8535 |
<p> |
| 8536 |
To activate the swap partition, use <c>swapon</c>: |
| 8537 |
</p> |
| 8538 |
|
| 8539 |
<pre caption="Activating the swap partition"> |
| 8540 |
# <i>swapon /dev/sda3</i> |
| 8541 |
</pre> |
| 8542 |
|
| 8543 |
<p> |
| 8544 |
Create and activate the swap now. |
| 8545 |
</p> |
| 8546 |
|
| 8547 |
</body> |
| 8548 |
</subsection> |
| 8549 |
</section> |
| 8550 |
<section> |
| 8551 |
<title>Mounting</title> |
| 8552 |
<body> |
| 8553 |
|
| 8554 |
<p> |
| 8555 |
Now that your partitions are initialized and are housing a filesystem, it is |
| 8556 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
| 8557 |
create the necessary mount directories for every partition you created. As an |
| 8558 |
example we mount the root and boot partition: |
| 8559 |
</p> |
| 8560 |
|
| 8561 |
<pre caption="Mounting partitions"> |
| 8562 |
# <i>mount /dev/sda4 /mnt/gentoo</i> |
| 8563 |
# <i>mkdir /mnt/gentoo/boot</i> |
| 8564 |
# <i>mount /dev/sda2 /mnt/gentoo/boot</i> |
| 8565 |
</pre> |
| 8566 |
|
| 8567 |
<note> |
| 8568 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
| 8569 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
| 8570 |
also holds for <path>/var/tmp</path>. |
| 8571 |
</note> |
| 8572 |
|
| 8573 |
<p> |
| 8574 |
We will also have to mount the proc filesystem (a virtual interface with the |
| 8575 |
kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. |
| 8576 |
</p> |
| 8577 |
|
| 8578 |
<p> |
| 8579 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
| 8580 |
Installation Files</uri>. |
| 8581 |
</p> |
| 8582 |
|
| 8583 |
</body> |
| 8584 |
</section> |
| 8585 |
</sections> |
| 8586 |
|
| 8587 |
|
| 8588 |
|
| 8589 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-hppa-kernel.xml |
| 8590 |
|
| 8591 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-hppa-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 8592 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-hppa-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 8593 |
|
| 8594 |
Index: hb-install-hppa-kernel.xml |
| 8595 |
=================================================================== |
| 8596 |
<?xml version='1.0' encoding='UTF-8'?> |
| 8597 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 8598 |
|
| 8599 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 8600 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 8601 |
|
| 8602 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-hppa-kernel.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 8603 |
|
| 8604 |
<sections> |
| 8605 |
|
| 8606 |
<version>5.5</version> |
| 8607 |
<date>2006-01-06</date> |
| 8608 |
|
| 8609 |
<section> |
| 8610 |
<title>Timezone</title> |
| 8611 |
<body> |
| 8612 |
|
| 8613 |
<p> |
| 8614 |
You first need to select your timezone so that your system knows where it is |
| 8615 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
| 8616 |
it to <path>/etc/localtime</path>. Please avoid the |
| 8617 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
| 8618 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
| 8619 |
</p> |
| 8620 |
|
| 8621 |
<pre caption="Setting the timezone information"> |
| 8622 |
# <i>ls /usr/share/zoneinfo</i> |
| 8623 |
<comment>(Suppose you want to use GMT)</comment> |
| 8624 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
| 8625 |
</pre> |
| 8626 |
|
| 8627 |
</body> |
| 8628 |
</section> |
| 8629 |
<section> |
| 8630 |
<title>Installing the Sources</title> |
| 8631 |
<subsection> |
| 8632 |
<title>Choosing a Kernel</title> |
| 8633 |
<body> |
| 8634 |
|
| 8635 |
<p> |
| 8636 |
The core around which all distributions are built is the Linux kernel. It is the |
| 8637 |
layer between the user programs and your system hardware. Gentoo provides its |
| 8638 |
users several possible kernel sources. A full listing with description is |
| 8639 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
| 8640 |
Guide</uri>. |
| 8641 |
</p> |
| 8642 |
|
| 8643 |
<p> |
| 8644 |
For HPPA we have <c>hppa-sources</c>. Default these sources are based on the |
| 8645 |
2.6 kernel sources. If you want to install a 2.4 kernel, you will need to |
| 8646 |
install Gentoo from a working Internet connection as we do not supply those |
| 8647 |
sources on our Installation CD. Continue by installing the kernel source. The |
| 8648 |
<c>USE="-doc"</c> is necessary to avoid installing xorg-x11 or other |
| 8649 |
dependencies at this point. <c>USE="symlink"</c> is not necessary for a new |
| 8650 |
install, but ensures proper creation of the <path>/usr/src/linux</path> |
| 8651 |
symlink. |
| 8652 |
</p> |
| 8653 |
|
| 8654 |
<pre caption="Installing a kernel source"> |
| 8655 |
# <i>USE="-doc symlink" emerge hppa-sources</i> |
| 8656 |
</pre> |
| 8657 |
|
| 8658 |
<p> |
| 8659 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
| 8660 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
| 8661 |
kernel source points to <c>hppa-sources-2.6.12.2-pa2</c>. Your version may be |
| 8662 |
different, so keep this in mind. |
| 8663 |
</p> |
| 8664 |
|
| 8665 |
<pre caption="Viewing the kernel source symlink"> |
| 8666 |
# <i>ls -l /usr/src/linux</i> |
| 8667 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-2.6.12.2-pa2 |
| 8668 |
</pre> |
| 8669 |
|
| 8670 |
<p> |
| 8671 |
Now it is time to configure and compile your kernel source. All architectures |
| 8672 |
can use <c>genkernel</c> for this, which will build a generic kernel as used |
| 8673 |
by the Installation CD. We explain the "manual" configuration first though, as |
| 8674 |
it is the best way to optimize your environment. |
| 8675 |
</p> |
| 8676 |
|
| 8677 |
<p> |
| 8678 |
If you want to manually configure your kernel, continue now with <uri |
| 8679 |
link="#manual">Default: Manual Configuration</uri>. If you want to use |
| 8680 |
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
| 8681 |
genkernel</uri> instead. |
| 8682 |
</p> |
| 8683 |
|
| 8684 |
</body> |
| 8685 |
</subsection> |
| 8686 |
</section> |
| 8687 |
<section id="manual"> |
| 8688 |
<title>Default: Manual Configuration</title> |
| 8689 |
<subsection> |
| 8690 |
<title>Introduction</title> |
| 8691 |
<body> |
| 8692 |
|
| 8693 |
<p> |
| 8694 |
Manually configuring a kernel is often seen as the most difficult procedure a |
| 8695 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
| 8696 |
couple of kernels you don't even remember that it was difficult ;) |
| 8697 |
</p> |
| 8698 |
|
| 8699 |
<p> |
| 8700 |
However, one thing <e>is</e> true: you must know your system when you start |
| 8701 |
configuring a kernel manually. Most information can be gathered by emerging |
| 8702 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
| 8703 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
| 8704 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
| 8705 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
| 8706 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
| 8707 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
| 8708 |
uses (it might provide you with a nice hint on what to enable). |
| 8709 |
</p> |
| 8710 |
|
| 8711 |
<p> |
| 8712 |
Now go to your kernel source directory and execute <c>make menuconfig</c>. This |
| 8713 |
will fire up an ncurses-based configuration menu. |
| 8714 |
</p> |
| 8715 |
|
| 8716 |
<pre caption="Invoking menuconfig"> |
| 8717 |
# <i>cd /usr/src/linux</i> |
| 8718 |
# <i>make menuconfig</i> |
| 8719 |
</pre> |
| 8720 |
|
| 8721 |
<p> |
| 8722 |
You will be greeted with several configuration sections. We'll first list some |
| 8723 |
options you must activate (otherwise Gentoo will not function, or not function |
| 8724 |
properly without additional tweaks). |
| 8725 |
</p> |
| 8726 |
|
| 8727 |
</body> |
| 8728 |
</subsection> |
| 8729 |
<subsection> |
| 8730 |
<title>Activating Required Options</title> |
| 8731 |
<body> |
| 8732 |
|
| 8733 |
<p> |
| 8734 |
First of all, activate the use of development and experimental code/drivers. |
| 8735 |
You need this, otherwise some very important code/drivers won't show up: |
| 8736 |
</p> |
| 8737 |
|
| 8738 |
<pre caption="Selecting experimental code/drivers, General setup"> |
| 8739 |
Code maturity level options ---> |
| 8740 |
[*] Prompt for development and/or incomplete code/drivers |
| 8741 |
General setup ---> |
| 8742 |
[*] Support for hot-pluggable devices |
| 8743 |
</pre> |
| 8744 |
|
| 8745 |
<p> |
| 8746 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
| 8747 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
| 8748 |
able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc |
| 8749 |
file system</c>. |
| 8750 |
</p> |
| 8751 |
|
| 8752 |
<pre caption="Selecting necessary file systems"> |
| 8753 |
File systems ---> |
| 8754 |
Pseudo Filesystems ---> |
| 8755 |
[*] /proc file system support |
| 8756 |
[*] Virtual memory file system support (former shm fs) |
| 8757 |
|
| 8758 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
| 8759 |
<*> Reiserfs support |
| 8760 |
<*> Ext3 journalling file system support |
| 8761 |
<*> JFS filesystem support |
| 8762 |
<*> Second extended fs support |
| 8763 |
<*> XFS filesystem support |
| 8764 |
</pre> |
| 8765 |
|
| 8766 |
<p> |
| 8767 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
| 8768 |
modem, you will need the following options in the kernel: |
| 8769 |
</p> |
| 8770 |
|
| 8771 |
<pre caption="Selecting PPPoE necessary drivers"> |
| 8772 |
Device Drivers ---> |
| 8773 |
Networking support ---> |
| 8774 |
<*> PPP (point-to-point protocol) support |
| 8775 |
<*> PPP support for async serial ports |
| 8776 |
<*> PPP support for sync tty ports |
| 8777 |
</pre> |
| 8778 |
|
| 8779 |
<p> |
| 8780 |
The two compression options won't harm but are not definitely needed, neither |
| 8781 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
| 8782 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
| 8783 |
</p> |
| 8784 |
|
| 8785 |
<p> |
| 8786 |
If you require it, don't forget to include support in the kernel for your |
| 8787 |
ethernet card. |
| 8788 |
</p> |
| 8789 |
|
| 8790 |
<p> |
| 8791 |
If you have a HIL mouse or keyboard, do not forget to compile in support for |
| 8792 |
them. |
| 8793 |
</p> |
| 8794 |
|
| 8795 |
<pre caption="Activating HIL support"> |
| 8796 |
Input core support ---> |
| 8797 |
[*] Keyboard support |
| 8798 |
[*] Mouse support |
| 8799 |
[*] Event interface support |
| 8800 |
</pre> |
| 8801 |
|
| 8802 |
<p> |
| 8803 |
If you have no mouse on your HIL port, only use the basic support: |
| 8804 |
</p> |
| 8805 |
|
| 8806 |
<pre caption="Basic HIL support"> |
| 8807 |
HIL support ---> |
| 8808 |
[*] HIL Keyboard (basic) support |
| 8809 |
</pre> |
| 8810 |
|
| 8811 |
<p> |
| 8812 |
If you however want <e>full</e> HIL support, select the following options: |
| 8813 |
</p> |
| 8814 |
|
| 8815 |
<pre caption="Full HIL support"> |
| 8816 |
HIL support ---> |
| 8817 |
[*] HP System Device Controller i8042 Support |
| 8818 |
[*] HIL MLC Support |
| 8819 |
[*] HIL Keyboard (full) support |
| 8820 |
[*] HIL Mouse & Pointer support |
| 8821 |
</pre> |
| 8822 |
|
| 8823 |
<p> |
| 8824 |
Also include display driver support: |
| 8825 |
</p> |
| 8826 |
|
| 8827 |
<pre caption="Display Driver support"> |
| 8828 |
Graphics support ---> |
| 8829 |
[*] Support for frame buffer devices |
| 8830 |
[*] HP STI frame buffer device support |
| 8831 |
Console display driver support ---> |
| 8832 |
[*] STI text console |
| 8833 |
</pre> |
| 8834 |
|
| 8835 |
<p> |
| 8836 |
When you're done configuring your kernel, continue with <uri |
| 8837 |
link="#compiling">Compiling and Installing</uri>. |
| 8838 |
</p> |
| 8839 |
|
| 8840 |
</body> |
| 8841 |
</subsection> |
| 8842 |
<subsection id="compiling"> |
| 8843 |
<title>Compiling and Installing</title> |
| 8844 |
<body> |
| 8845 |
|
| 8846 |
<p> |
| 8847 |
Now that your kernel is configured, it is time to compile and install it. Exit |
| 8848 |
the configuration and start the compilation process: |
| 8849 |
</p> |
| 8850 |
|
| 8851 |
<pre caption="Compiling the kernel"> |
| 8852 |
# <i>make && make modules_install</i> |
| 8853 |
</pre> |
| 8854 |
|
| 8855 |
<p> |
| 8856 |
When the kernel has finished compiling, copy the kernel image to |
| 8857 |
<path>/boot</path>. Use whatever name you feel is appropriate for your kernel |
| 8858 |
choice and remember it as you will need it later on when you configure your |
| 8859 |
bootloader. Remember to replace <path><kernel-version></path> with the |
| 8860 |
name and version of your kernel. |
| 8861 |
</p> |
| 8862 |
|
| 8863 |
<pre caption="Installing the kernel"> |
| 8864 |
# <i>cp vmlinux /boot/<kernel-version></i> |
| 8865 |
</pre> |
| 8866 |
|
| 8867 |
<p> |
| 8868 |
Now continue with <uri link="#kernel_modules">Configuring Kernel |
| 8869 |
Modules</uri>. |
| 8870 |
</p> |
| 8871 |
|
| 8872 |
</body> |
| 8873 |
</subsection> |
| 8874 |
</section> |
| 8875 |
<section id="genkernel"> |
| 8876 |
<title>Alternative: Using genkernel</title> |
| 8877 |
<body> |
| 8878 |
|
| 8879 |
<p> |
| 8880 |
If you are reading this section, you have chosen to use our <c>genkernel</c> |
| 8881 |
script to configure your kernel for you. |
| 8882 |
</p> |
| 8883 |
|
| 8884 |
<p> |
| 8885 |
Now that your kernel source tree is installed, it's now time to compile your |
| 8886 |
kernel by using our <c>genkernel</c> script to automatically build a kernel for |
| 8887 |
you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
| 8888 |
way our Installation CD kernel is configured. This means that when you use |
| 8889 |
<c>genkernel</c> to build your kernel, your system will generally detect all |
| 8890 |
your hardware at boot-time, just like our Installation CD does. Because genkernel |
| 8891 |
doesn't require any manual kernel configuration, it is an ideal solution for |
| 8892 |
those users who may not be comfortable compiling their own kernels. |
| 8893 |
</p> |
| 8894 |
|
| 8895 |
<p> |
| 8896 |
Now, let's see how to use genkernel. First, emerge the genkernel ebuild: |
| 8897 |
</p> |
| 8898 |
|
| 8899 |
<pre caption="Emerging genkernel"> |
| 8900 |
# <i>emerge genkernel</i> |
| 8901 |
</pre> |
| 8902 |
|
| 8903 |
<p> |
| 8904 |
Now, compile your kernel sources by running <c>genkernel all</c>. |
| 8905 |
Be aware though, as <c>genkernel</c> compiles a kernel that supports almost all |
| 8906 |
hardware, this compilation will take quite a while to finish! |
| 8907 |
</p> |
| 8908 |
|
| 8909 |
<p> |
| 8910 |
Note that, if your boot partition doesn't use ext2 or ext3 as filesystem you |
| 8911 |
need to manually configure your kernel using <c>genkernel --menuconfig all</c> |
| 8912 |
and add support for your filesystem <e>in</e> the kernel (i.e. <e>not</e> as a |
| 8913 |
module). |
| 8914 |
</p> |
| 8915 |
|
| 8916 |
<pre caption="Running genkernel"> |
| 8917 |
# <i>genkernel all</i> |
| 8918 |
<comment>(Output removed to increase readability)</comment> |
| 8919 |
* Kernel compiled successfully! |
| 8920 |
* Required Kernel Params: |
| 8921 |
* : root=/dev/ram0 init=/linuxrc real_root=/dev/$ROOT |
| 8922 |
* where $ROOT is the devicenode for your root partition as |
| 8923 |
* you should have specified in /etc/fstab |
| 8924 |
* |
| 8925 |
* You MUST tell your bootloader to use the generated initrd |
| 8926 |
* |
| 8927 |
* Recommended Kernel Params: |
| 8928 |
* : vga=0x317 splash=verbose |
| 8929 |
* |
| 8930 |
* Do NOT report kernel bugs (configs included) as genkernel bugs. |
| 8931 |
* Make sure you have the latest genkernel before reporting bugs |
| 8932 |
* |
| 8933 |
* For more info see /usr/share/genkernel/README |
| 8934 |
</pre> |
| 8935 |
|
| 8936 |
<p> |
| 8937 |
Once <c>genkernel</c> completes, a kernel, full set of modules and |
| 8938 |
<e>initial root disk</e> (initrd) will be created. We will use the kernel |
| 8939 |
and initrd when configuring a boot loader later in this document. Write |
| 8940 |
down the names of the kernel and initrd as you will need it when writing |
| 8941 |
the bootloader configuration file. The initrd will be started immediately after |
| 8942 |
booting to perform hardware autodetection (just like on the Installation CD) |
| 8943 |
before your "real" system starts up. |
| 8944 |
</p> |
| 8945 |
|
| 8946 |
<pre caption="Checking the created kernel image name and initrd"> |
| 8947 |
# <i>ls /boot/kernel* /boot/initramfs*</i> |
| 8948 |
</pre> |
| 8949 |
|
| 8950 |
<p> |
| 8951 |
Now, let's perform one more step to get our system to be more like the |
| 8952 |
Installation CD -- let's emerge <c>coldplug</c>. While the initrd autodetects |
| 8953 |
hardware that is needed to boot your system, <c>coldplug</c> autodetects |
| 8954 |
everything else. To emerge and enable <c>coldplug</c>, type the following: |
| 8955 |
</p> |
| 8956 |
|
| 8957 |
<pre caption="Emerging and enabling coldplug"> |
| 8958 |
# <i>emerge coldplug</i> |
| 8959 |
# <i>rc-update add coldplug default</i> |
| 8960 |
</pre> |
| 8961 |
|
| 8962 |
</body> |
| 8963 |
</section> |
| 8964 |
<section id="kernel_modules"> |
| 8965 |
<title>Configuring Kernel Modules</title> |
| 8966 |
<subsection> |
| 8967 |
<title>Configuring the Modules</title> |
| 8968 |
<body> |
| 8969 |
|
| 8970 |
<p> |
| 8971 |
You should list the modules you want automatically loaded in |
| 8972 |
<path>/etc/modules.autoload.d/kernel-2.6</path>. |
| 8973 |
You can add extra options to the modules too if you want. |
| 8974 |
</p> |
| 8975 |
|
| 8976 |
<p> |
| 8977 |
To view all available modules, run the following <c>find</c> command. Don't |
| 8978 |
forget to substitute "<kernel version>" with the version of the kernel you |
| 8979 |
just compiled: |
| 8980 |
</p> |
| 8981 |
|
| 8982 |
<pre caption="Viewing all available modules"> |
| 8983 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
| 8984 |
</pre> |
| 8985 |
|
| 8986 |
<p> |
| 8987 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
| 8988 |
<path>kernel-2.6</path> file and enter the module |
| 8989 |
name in it. |
| 8990 |
</p> |
| 8991 |
|
| 8992 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
| 8993 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
| 8994 |
</pre> |
| 8995 |
|
| 8996 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
| 8997 |
3c59x |
| 8998 |
</pre> |
| 8999 |
|
| 9000 |
<p> |
| 9001 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
| 9002 |
your System</uri>. |
| 9003 |
</p> |
| 9004 |
|
| 9005 |
</body> |
| 9006 |
</subsection> |
| 9007 |
</section> |
| 9008 |
</sections> |
| 9009 |
|
| 9010 |
|
| 9011 |
|
| 9012 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-hppa-medium.xml |
| 9013 |
|
| 9014 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-hppa-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 9015 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-hppa-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 9016 |
|
| 9017 |
Index: hb-install-hppa-medium.xml |
| 9018 |
=================================================================== |
| 9019 |
<?xml version='1.0' encoding='UTF-8'?> |
| 9020 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 9021 |
|
| 9022 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 9023 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 9024 |
|
| 9025 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-hppa-medium.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 9026 |
|
| 9027 |
<sections> |
| 9028 |
|
| 9029 |
<version>5.2</version> |
| 9030 |
<date>2005-11-29</date> |
| 9031 |
|
| 9032 |
<section> |
| 9033 |
<title>Hardware Requirements</title> |
| 9034 |
<subsection> |
| 9035 |
<title>Introduction</title> |
| 9036 |
<body> |
| 9037 |
|
| 9038 |
<p> |
| 9039 |
Before we start, we first list what hardware requirements you need to |
| 9040 |
successfully install Gentoo on your box. |
| 9041 |
</p> |
| 9042 |
|
| 9043 |
</body> |
| 9044 |
</subsection> |
| 9045 |
<subsection> |
| 9046 |
<title>Hardware Requirements</title> |
| 9047 |
<body> |
| 9048 |
|
| 9049 |
<p> |
| 9050 |
A list of supported hardware can be found on the |
| 9051 |
<uri link="http://www.pateam.org/list.html">PA Team website</uri>. |
| 9052 |
You may find additional information about your box in the <uri |
| 9053 |
link="http://hwdb.parisc-linux.org">Parisc-Linux Hardware Database</uri>. |
| 9054 |
</p> |
| 9055 |
|
| 9056 |
<table> |
| 9057 |
<tr> |
| 9058 |
<th>Memory</th> |
| 9059 |
<ti>64 MB</ti> |
| 9060 |
</tr> |
| 9061 |
<tr> |
| 9062 |
<th>Diskspace</th> |
| 9063 |
<ti>1.5 GB (excluding swap space)</ti> |
| 9064 |
</tr> |
| 9065 |
<tr> |
| 9066 |
<th>Swap space</th> |
| 9067 |
<ti>At least 256 MB</ti> |
| 9068 |
</tr> |
| 9069 |
</table> |
| 9070 |
|
| 9071 |
</body> |
| 9072 |
</subsection> |
| 9073 |
</section> |
| 9074 |
<!-- Copy/paste from hb-install-x86-medium.xml --> |
| 9075 |
<!-- START --> |
| 9076 |
<section> |
| 9077 |
<title>The Gentoo Universal Installation CD</title> |
| 9078 |
<subsection> |
| 9079 |
<title>Introduction</title> |
| 9080 |
<body> |
| 9081 |
|
| 9082 |
<p> |
| 9083 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
| 9084 |
Such a tarball is an archive that contains a minimal environment from |
| 9085 |
which you can succesfully install Gentoo Linux onto your system. |
| 9086 |
</p> |
| 9087 |
|
| 9088 |
<p> |
| 9089 |
Installations using a stage1 or stage2 tarball file are not documented in the |
| 9090 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
| 9091 |
FAQ</uri> on these matters. |
| 9092 |
</p> |
| 9093 |
|
| 9094 |
</body> |
| 9095 |
</subsection> |
| 9096 |
<subsection> |
| 9097 |
<title>Gentoo Universal Installation CD</title> |
| 9098 |
<body> |
| 9099 |
|
| 9100 |
<p> |
| 9101 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
| 9102 |
environment. It allows you to boot Linux from the CD. During the boot process |
| 9103 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
| 9104 |
Installation CDs are maintained by Gentoo developers. |
| 9105 |
</p> |
| 9106 |
|
| 9107 |
<p> |
| 9108 |
There currently are two Installation CDs available: |
| 9109 |
</p> |
| 9110 |
|
| 9111 |
<ul> |
| 9112 |
<li> |
| 9113 |
The Universal Installation CD contains everything you need to install |
| 9114 |
Gentoo. It provides stage3 files for common architectures, source code |
| 9115 |
for the extra applications you need to choose from and, of course, the |
| 9116 |
installation instructions for your architecture. |
| 9117 |
</li> |
| 9118 |
<li> |
| 9119 |
The Minimal Installation CD contains only a minimal environment that allows |
| 9120 |
you to boot up and configure your network so you can connect to the |
| 9121 |
Internet. It does not contain any additional files and cannot be used |
| 9122 |
during the current installation approach. |
| 9123 |
</li> |
| 9124 |
</ul> |
| 9125 |
|
| 9126 |
</body> |
| 9127 |
</subsection> |
| 9128 |
</section> |
| 9129 |
<!-- STOP --> |
| 9130 |
<section> |
| 9131 |
<title>Download, Burn and Boot the Gentoo Universal Installation CD</title> |
| 9132 |
<subsection> |
| 9133 |
<title>Downloading and Burning the Installation CD</title> |
| 9134 |
<body> |
| 9135 |
|
| 9136 |
<p> |
| 9137 |
You can download the Universal Installation CD from one of our <uri |
| 9138 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CD is located in |
| 9139 |
the <path>releases/hppa/2006.0/installcd</path> directory. |
| 9140 |
</p> |
| 9141 |
|
| 9142 |
<p> |
| 9143 |
Inside those directories you'll find ISO-files. Those are full CD images which |
| 9144 |
you can write on a CD-R. |
| 9145 |
</p> |
| 9146 |
|
| 9147 |
<p> |
| 9148 |
After downloading the file, you can verify its integrity to see if it is |
| 9149 |
corrupted or not: |
| 9150 |
</p> |
| 9151 |
|
| 9152 |
<ul> |
| 9153 |
<li> |
| 9154 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
| 9155 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
| 9156 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows) |
| 9157 |
</li> |
| 9158 |
<li> |
| 9159 |
You can verify the cryptographic signature that we provide. You need to |
| 9160 |
obtain the public key we use (17072058) before you proceed though. |
| 9161 |
</li> |
| 9162 |
</ul> |
| 9163 |
|
| 9164 |
<p> |
| 9165 |
To fetch our public key using the GnuPG application, run the following command: |
| 9166 |
</p> |
| 9167 |
|
| 9168 |
<pre caption="Obtaining the public key"> |
| 9169 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
| 9170 |
</pre> |
| 9171 |
|
| 9172 |
<p> |
| 9173 |
Now verify the signature: |
| 9174 |
</p> |
| 9175 |
|
| 9176 |
<pre caption="Verify the cryptographic signature"> |
| 9177 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
| 9178 |
</pre> |
| 9179 |
|
| 9180 |
<p> |
| 9181 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
| 9182 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
| 9183 |
<c>K3B</c> here; more information can be found in our <uri |
| 9184 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
| 9185 |
</p> |
| 9186 |
|
| 9187 |
<ul> |
| 9188 |
<li> |
| 9189 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
| 9190 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
| 9191 |
path). |
| 9192 |
</li> |
| 9193 |
<li> |
| 9194 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
| 9195 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
| 9196 |
<c>Start</c>. |
| 9197 |
</li> |
| 9198 |
</ul> |
| 9199 |
|
| 9200 |
</body> |
| 9201 |
</subsection> |
| 9202 |
<subsection> |
| 9203 |
<title>Booting the Universal Installation CD</title> |
| 9204 |
<body> |
| 9205 |
|
| 9206 |
<note> |
| 9207 |
If you have problems booting the Installation CD or any other media, please |
| 9208 |
read the <uri |
| 9209 |
link="http://www.tldp.org/HOWTO/PA-RISC-Linux-Boot-HOWTO/index.html"> |
| 9210 |
PA-RISC Linux Boot HOWTO</uri>. |
| 9211 |
</note> |
| 9212 |
|
| 9213 |
<p> |
| 9214 |
Boot your HPPA system. During the boot process, you will see a message similar |
| 9215 |
to the following: |
| 9216 |
</p> |
| 9217 |
|
| 9218 |
<pre caption="HPPA boot message"> |
| 9219 |
Searching for Potential Boot Devices. |
| 9220 |
To terminate search, press and hold the ESCAPE key. |
| 9221 |
</pre> |
| 9222 |
|
| 9223 |
<p> |
| 9224 |
When this message appears, press and hold the Esc-key until an option menu |
| 9225 |
appears. This can take a while, be patient. By default, you should enter the |
| 9226 |
BOOT_ADMIN console. If you receive an option menu, choose <c>Enter Boot |
| 9227 |
Administration mode</c> to enter the BOOT_ADMIN console. You should now have an |
| 9228 |
'>' prompt. |
| 9229 |
</p> |
| 9230 |
|
| 9231 |
<p> |
| 9232 |
Put the Gentoo Installation CD in the CD-ROM. If you do not know the SCSI ID of |
| 9233 |
your CD-ROM drive, your PA-RISC station will search for it when you issue the |
| 9234 |
<c>search</c> command. |
| 9235 |
</p> |
| 9236 |
|
| 9237 |
<pre caption="Searching for SCSI ID"> |
| 9238 |
> <i>search</i> |
| 9239 |
Searching for Devices with Bootable Media. |
| 9240 |
To terminate search, please press and hold the ESCAPE key. |
| 9241 |
</pre> |
| 9242 |
|
| 9243 |
<p> |
| 9244 |
Your PA-RISC station will now display all the available boot media. This is an |
| 9245 |
example result of this command: |
| 9246 |
</p> |
| 9247 |
|
| 9248 |
<pre caption="Available boot media"> |
| 9249 |
Device Selection Device Path Device Type and Utilities |
| 9250 |
--------------------------------------------------------------------------- |
| 9251 |
|
| 9252 |
P0 scsi.5.0 TOSHIBA CD-ROM XM-3301TA |
| 9253 |
IPL |
| 9254 |
P1 scsi.2.0 COMPAQ ST32550N |
| 9255 |
IPL |
| 9256 |
P2 lan.0010a7-06d1b6.3.6 server |
| 9257 |
IPL |
| 9258 |
</pre> |
| 9259 |
|
| 9260 |
<p> |
| 9261 |
To boot from a CD-ROM you need the accompanying Device Path. For instance, if we |
| 9262 |
want to boot from the TOSHIBA CD-ROM in the above example, we would need to type |
| 9263 |
the following command: |
| 9264 |
</p> |
| 9265 |
|
| 9266 |
<pre caption="Booting from a CD-ROM"> |
| 9267 |
> <i>boot scsi.5.0 ipl</i> |
| 9268 |
|
| 9269 |
Trying scsi.5.0 |
| 9270 |
</pre> |
| 9271 |
|
| 9272 |
<p> |
| 9273 |
The <c>ipl</c> keyword (Initial Program Loader) tells palo (the PA-RISC boot |
| 9274 |
LOader) to enter interactive mode. This will allow you to change, for example, |
| 9275 |
the kernel boot parameters. |
| 9276 |
</p> |
| 9277 |
|
| 9278 |
<p> |
| 9279 |
When the boot is successful, palo will start in interactive mode: |
| 9280 |
</p> |
| 9281 |
|
| 9282 |
<pre caption="PALO Interactive Mode"> |
| 9283 |
Boot path initialized. |
| 9284 |
Attempting to load IPL. |
| 9285 |
|
| 9286 |
|
| 9287 |
HARD Booted. |
| 9288 |
palo ipl 1.5 root@hope Sat Apr 23 18:06:47 CEST 2005 |
| 9289 |
|
| 9290 |
Boot image contains: |
| 9291 |
0/vmlinux32 6241293 bytes @ 0x3904000 |
| 9292 |
0/vmlinux64 8352719 bytes @ 0x3ef8000 |
| 9293 |
0/ramdisk 1007589 bytes @ 0x105800 |
| 9294 |
|
| 9295 |
Information: No console specified on kernel command line. This is normal. |
| 9296 |
PALO will choose the console currently used by firmware (serial).Current command line: |
| 9297 |
0/vmlinux initrd=initrd TERM=linux root=/dev/ram0 init=/linuxrc cdroot looptype=squashfs loop=/livecd.squashfs hda=scsi console=ttyS0 |
| 9298 |
0: 0/vmlinux |
| 9299 |
1: initrd=initrd |
| 9300 |
2: TERM=linux |
| 9301 |
3: root=/dev/ram0 |
| 9302 |
4: init=/linuxrc |
| 9303 |
5: cdroot |
| 9304 |
6: looptype=squashfs |
| 9305 |
7: loop=/livecd.squashfs |
| 9306 |
8: hda=scsi |
| 9307 |
9: console=ttyS0 |
| 9308 |
|
| 9309 |
<#> edit the numbered field |
| 9310 |
'b' boot with this command line |
| 9311 |
'r' restore command line |
| 9312 |
'l' list dir |
| 9313 |
</pre> |
| 9314 |
|
| 9315 |
<p> |
| 9316 |
These parameters are suitable for most situations. |
| 9317 |
</p> |
| 9318 |
|
| 9319 |
<p> |
| 9320 |
If you need extra features you must add the appropriate keyword(s) to the end of |
| 9321 |
the command line. To add a keyword, edit the last field, add a space and type |
| 9322 |
your keyword. The only implemented keywords as of now are <c>cdcache</c> which |
| 9323 |
tells the Installation CD to load itself into RAM, allowing you to unmount the |
| 9324 |
CD, and <c>noload=module1[,module2[,...]]</c> which allows you to explicitly |
| 9325 |
disable loading of particular modules. |
| 9326 |
</p> |
| 9327 |
|
| 9328 |
<pre caption="Adding hdb=scsi as boot option"> |
| 9329 |
(or 'b' to boot with this command line)? <i>9</i> |
| 9330 |
console=ttyS0 <i>hdb=scsi</i> |
| 9331 |
</pre> |
| 9332 |
|
| 9333 |
<p> |
| 9334 |
Now that you have tweaked your kernel boot params, boot it. |
| 9335 |
</p> |
| 9336 |
|
| 9337 |
<pre caption="Booting the kernel"> |
| 9338 |
(or 'b' to boot with this command line)? <i>b</i> |
| 9339 |
</pre> |
| 9340 |
|
| 9341 |
<p> |
| 9342 |
You should have a root ("#") prompt on the current console and can also switch |
| 9343 |
to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get back to the one you |
| 9344 |
started on by pressing Alt-F1. |
| 9345 |
</p> |
| 9346 |
|
| 9347 |
<p> |
| 9348 |
Now continue with <uri link="#hardware">Extra Hardware |
| 9349 |
Configuration</uri>. |
| 9350 |
</p> |
| 9351 |
|
| 9352 |
</body> |
| 9353 |
</subsection> |
| 9354 |
<subsection id="hardware"> |
| 9355 |
<title>Extra Hardware Configuration</title> |
| 9356 |
<body> |
| 9357 |
|
| 9358 |
<p> |
| 9359 |
Most hppa machines have an onboard ethernet card. Old ones use the lasi driver |
| 9360 |
which is compiled in the kernel. Newer ones need the tulip driver which is |
| 9361 |
compiled as a module. To use the latter, you need to load its driver. |
| 9362 |
</p> |
| 9363 |
|
| 9364 |
<p> |
| 9365 |
In the next example, we try to load the <c>tulip</c> module (support for |
| 9366 |
certain kinds of network interfaces): |
| 9367 |
</p> |
| 9368 |
|
| 9369 |
<pre caption="Loading kernel modules"> |
| 9370 |
# <i>modprobe tulip</i> |
| 9371 |
</pre> |
| 9372 |
|
| 9373 |
</body> |
| 9374 |
</subsection> |
| 9375 |
|
| 9376 |
<subsection id="useraccounts"> |
| 9377 |
<title>Optional: User Accounts</title> |
| 9378 |
<body> |
| 9379 |
|
| 9380 |
<p> |
| 9381 |
If you plan on giving other people access to your installation |
| 9382 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
| 9383 |
security reasons), you need to create the necessary user accounts and change |
| 9384 |
the root password. |
| 9385 |
</p> |
| 9386 |
|
| 9387 |
<p> |
| 9388 |
To change the root password, use the <c>passwd</c> utility: |
| 9389 |
</p> |
| 9390 |
|
| 9391 |
<pre caption="Changing the root password"> |
| 9392 |
# <i>passwd</i> |
| 9393 |
New password: <comment>(Enter your new password)</comment> |
| 9394 |
Re-enter password: <comment>(Re-enter your password)</comment> |
| 9395 |
</pre> |
| 9396 |
|
| 9397 |
<p> |
| 9398 |
To create a user account, we first enter their credentials, followed by |
| 9399 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
| 9400 |
In the next example, we create a user called "john". |
| 9401 |
</p> |
| 9402 |
|
| 9403 |
<pre caption="Creating a user account"> |
| 9404 |
# <i>useradd -m -G users john</i> |
| 9405 |
# <i>passwd john</i> |
| 9406 |
New password: <comment>(Enter john's password)</comment> |
| 9407 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
| 9408 |
</pre> |
| 9409 |
|
| 9410 |
<p> |
| 9411 |
You can change your user id from root to the newly created user by using |
| 9412 |
<c>su</c>: |
| 9413 |
</p> |
| 9414 |
|
| 9415 |
<pre caption="Changing user id"> |
| 9416 |
# <i>su - john</i> |
| 9417 |
</pre> |
| 9418 |
|
| 9419 |
</body> |
| 9420 |
</subsection> |
| 9421 |
<subsection> |
| 9422 |
<title>Optional: Viewing Documentation while Installing</title> |
| 9423 |
<body> |
| 9424 |
|
| 9425 |
<p> |
| 9426 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
| 9427 |
installation, make sure you have created a user account (see <uri |
| 9428 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
| 9429 |
go to a new terminal and log in. |
| 9430 |
</p> |
| 9431 |
|
| 9432 |
<p> |
| 9433 |
If you want to view the documentation on the CD you can immediately run |
| 9434 |
<c>links2</c> to read it: |
| 9435 |
</p> |
| 9436 |
|
| 9437 |
<pre caption="Viewing the on-CD documentation"> |
| 9438 |
# <i>links2 /mnt/cdrom/docs/handbook/html/index.html</i> |
| 9439 |
</pre> |
| 9440 |
|
| 9441 |
<p> |
| 9442 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
| 9443 |
more recent than the one provided on the CD. You can view it using <c>links2</c> |
| 9444 |
as well, but only after having completed the <e>Configuring your Network</e> |
| 9445 |
chapter (otherwise you won't be able to go on the Internet to view the |
| 9446 |
document): |
| 9447 |
</p> |
| 9448 |
|
| 9449 |
<pre caption="Viewing the Online Documentation"> |
| 9450 |
# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-hppa.xml</i> |
| 9451 |
</pre> |
| 9452 |
|
| 9453 |
<p> |
| 9454 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
| 9455 |
</p> |
| 9456 |
|
| 9457 |
</body> |
| 9458 |
</subsection> |
| 9459 |
<subsection> |
| 9460 |
<title>Optional: Starting the SSH Daemon</title> |
| 9461 |
<body> |
| 9462 |
|
| 9463 |
<p> |
| 9464 |
If you want to allow other users to access your computer during the |
| 9465 |
Gentoo installation (perhaps because those users are going to help you |
| 9466 |
install Gentoo, or even do it for you), you need to create a user |
| 9467 |
account for them and perhaps even provide them with your root password |
| 9468 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
| 9469 |
</p> |
| 9470 |
|
| 9471 |
<p> |
| 9472 |
To fire up the SSH daemon, execute the following command: |
| 9473 |
</p> |
| 9474 |
|
| 9475 |
<pre caption="Starting the SSH daemon"> |
| 9476 |
# <i>/etc/init.d/sshd start</i> |
| 9477 |
</pre> |
| 9478 |
|
| 9479 |
<p> |
| 9480 |
To be able to use sshd, you first need to set up your networking. Continue with |
| 9481 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
| 9482 |
</p> |
| 9483 |
|
| 9484 |
</body> |
| 9485 |
</subsection> |
| 9486 |
</section> |
| 9487 |
</sections> |
| 9488 |
|
| 9489 |
|
| 9490 |
|
| 9491 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-network.xml |
| 9492 |
|
| 9493 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-network.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 9494 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-network.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 9495 |
|
| 9496 |
Index: hb-install-network.xml |
| 9497 |
=================================================================== |
| 9498 |
<?xml version='1.0' encoding='UTF-8'?> |
| 9499 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 9500 |
|
| 9501 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 9502 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
| 9503 |
|
| 9504 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-network.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 9505 |
|
| 9506 |
<sections> |
| 9507 |
|
| 9508 |
<version>5.0</version> |
| 9509 |
<date>2005-08-08</date> |
| 9510 |
|
| 9511 |
<section> |
| 9512 |
<title>Do you need Networking?</title> |
| 9513 |
<subsection> |
| 9514 |
<title>Who can do without?</title> |
| 9515 |
<body> |
| 9516 |
|
| 9517 |
<p> |
| 9518 |
Generally, you don't need a working network connection to install Gentoo using |
| 9519 |
the Universal Installation CD. However, there are some circumstances where you |
| 9520 |
do want to have a working Internet connection: |
| 9521 |
</p> |
| 9522 |
|
| 9523 |
<ul> |
| 9524 |
<li> |
| 9525 |
The stage3 files that are stored in the Universal Installation CD do not |
| 9526 |
match your architecture and you need to download the correct stage3 file |
| 9527 |
</li> |
| 9528 |
<li> |
| 9529 |
You need to install a specific networking application that will allow you to |
| 9530 |
connect to the Internet which isn't available on the Universal Installation |
| 9531 |
CD but is supported by the Installation CD (i.e. you can connect to the |
| 9532 |
Internet using the Installation CD but the necessary sources are not |
| 9533 |
available on the Installation CD) |
| 9534 |
</li> |
| 9535 |
<li> |
| 9536 |
You want remote assistance during the installation (using SSH or through |
| 9537 |
direct conversations using IRC) |
| 9538 |
</li> |
| 9539 |
</ul> |
| 9540 |
|
| 9541 |
</body> |
| 9542 |
</subsection> |
| 9543 |
<subsection> |
| 9544 |
<title>Do I need Networking?</title> |
| 9545 |
<body> |
| 9546 |
|
| 9547 |
<p> |
| 9548 |
To find out if the stage3 file for your architecture is available, take a look |
| 9549 |
inside <path>/mnt/cdrom/stages</path> and check if one of the available stages |
| 9550 |
matches your architecture. If not, you can still opt for a stage3 file of an |
| 9551 |
architecture compatible with yours. |
| 9552 |
</p> |
| 9553 |
|
| 9554 |
<p> |
| 9555 |
If you on the other hand want to use a stage3 file optimized for your |
| 9556 |
architecture and the stage3 file of your choice is not available, then you will |
| 9557 |
need networking to download the appropriate stage3 file. |
| 9558 |
</p> |
| 9559 |
|
| 9560 |
<p> |
| 9561 |
So, if you don't need networking, you can skip the rest of this chapter and |
| 9562 |
continue with <uri link="?part=1&chap=4">Preparing the Disks</uri>. |
| 9563 |
Otherwise, continue with the networking configuration sections below. |
| 9564 |
</p> |
| 9565 |
|
| 9566 |
</body> |
| 9567 |
</subsection> |
| 9568 |
</section> |
| 9569 |
<section> |
| 9570 |
<title>Automatic Network Detection</title> |
| 9571 |
<subsection> |
| 9572 |
<title>Maybe it just works?</title> |
| 9573 |
<body> |
| 9574 |
|
| 9575 |
<p> |
| 9576 |
If your system is plugged into an Ethernet network with a DHCP server, it is |
| 9577 |
very likely that your networking configuration has already been set up |
| 9578 |
automatically for you. If so, you should be able to take advantage of the many |
| 9579 |
included network-aware commands on the Installation CD such as <c>ssh</c>, |
| 9580 |
<c>scp</c>, <c>ping</c>, <c>irssi</c>, <c>wget</c> and <c>links</c>, among |
| 9581 |
others. |
| 9582 |
</p> |
| 9583 |
|
| 9584 |
<p> |
| 9585 |
If networking has been configured for you, the <c>/sbin/ifconfig</c> command |
| 9586 |
should list some network interfaces besides lo, such as eth0: |
| 9587 |
</p> |
| 9588 |
|
| 9589 |
<pre caption="/sbin/ifconfig for a working network configuration"> |
| 9590 |
# <i>/sbin/ifconfig</i> |
| 9591 |
<comment>(...)</comment> |
| 9592 |
eth0 Link encap:Ethernet HWaddr 00:50:BA:8F:61:7A |
| 9593 |
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 |
| 9594 |
inet6 addr: fe80::50:ba8f:617a/10 Scope:Link |
| 9595 |
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 |
| 9596 |
RX packets:1498792 errors:0 dropped:0 overruns:0 frame:0 |
| 9597 |
TX packets:1284980 errors:0 dropped:0 overruns:0 carrier:0 |
| 9598 |
collisions:1984 txqueuelen:100 |
| 9599 |
RX bytes:485691215 (463.1 Mb) TX bytes:123951388 (118.2 Mb) |
| 9600 |
Interrupt:11 Base address:0xe800 |
| 9601 |
</pre> |
| 9602 |
|
| 9603 |
</body> |
| 9604 |
</subsection> |
| 9605 |
<subsection> |
| 9606 |
<title>Optional: Configure any Proxies</title> |
| 9607 |
<body> |
| 9608 |
|
| 9609 |
<p> |
| 9610 |
If you access the Internet through a proxy, you might need to set up proxy |
| 9611 |
information during the installation. It is very easy to define a proxy: you just |
| 9612 |
need to define a variable which contains the proxy server information. |
| 9613 |
</p> |
| 9614 |
|
| 9615 |
<p> |
| 9616 |
In most cases, you can just define the variables using the server hostname. As |
| 9617 |
an example, we assume the proxy is called <c>proxy.gentoo.org</c> and the port |
| 9618 |
is <c>8080</c>. |
| 9619 |
</p> |
| 9620 |
|
| 9621 |
<pre caption="Defining proxy servers"> |
| 9622 |
<comment>(If the proxy filters HTTP traffic)</comment> |
| 9623 |
# <i>export http_proxy="http://proxy.gentoo.org:8080"</i> |
| 9624 |
<comment>(If the proxy filters FTP traffic)</comment> |
| 9625 |
# <i>export ftp_proxy="ftp://proxy.gentoo.org:8080"</i> |
| 9626 |
<comment>(If the proxy filters RSYNC traffic)</comment> |
| 9627 |
# <i>export RSYNC_PROXY="proxy.gentoo.org:8080"</i> |
| 9628 |
</pre> |
| 9629 |
|
| 9630 |
<p> |
| 9631 |
If your proxy requires a username and password, you should use the following |
| 9632 |
syntax for the variable: |
| 9633 |
</p> |
| 9634 |
|
| 9635 |
<pre caption="Adding username/password to the proxy variable"> |
| 9636 |
http://<i>username</i>:<i>password</i>@proxy.gentoo.org:8080 |
| 9637 |
</pre> |
| 9638 |
|
| 9639 |
</body> |
| 9640 |
</subsection> |
| 9641 |
<subsection> |
| 9642 |
<title>Testing the Network</title> |
| 9643 |
<body> |
| 9644 |
|
| 9645 |
<p> |
| 9646 |
You may want to try pinging your ISP's DNS server (found in |
| 9647 |
<path>/etc/resolv.conf</path>) and a Web site of your choice, just to make sure |
| 9648 |
that your packets are reaching the net, DNS name resolution is working |
| 9649 |
correctly, etc. |
| 9650 |
</p> |
| 9651 |
|
| 9652 |
<pre caption="Further network testing"> |
| 9653 |
# <i>ping -c 3 www.yahoo.com</i> |
| 9654 |
</pre> |
| 9655 |
|
| 9656 |
<p> |
| 9657 |
If you are now able to use your network, you can skip the rest of this |
| 9658 |
section and continue with <uri link="?part=1&chap=4">Preparing the |
| 9659 |
Disks</uri>. If not, read on. |
| 9660 |
</p> |
| 9661 |
|
| 9662 |
</body> |
| 9663 |
</subsection> |
| 9664 |
</section> |
| 9665 |
<section> |
| 9666 |
<title>Automatic Network Configuration</title> |
| 9667 |
<subsection> |
| 9668 |
<body> |
| 9669 |
|
| 9670 |
<p> |
| 9671 |
If the network doesn't work immediately, some installation media allow you to |
| 9672 |
use <c>net-setup</c> (for regular or wireless networks), <c>adsl-setup</c> |
| 9673 |
(for ADSL-users) or <c>pptp</c> (for PPTP-users - only available on x86). |
| 9674 |
</p> |
| 9675 |
|
| 9676 |
<p> |
| 9677 |
If your installation medium does not contain any of these tools or your network |
| 9678 |
doesn't function yet, continue with <uri link="#doc_chap3">Manual Network |
| 9679 |
Configuration</uri>. |
| 9680 |
</p> |
| 9681 |
|
| 9682 |
<ul> |
| 9683 |
<li> |
| 9684 |
Regular Ethernet users should continue with <uri |
| 9685 |
link="#net-setup">Default: Using net-setup</uri> |
| 9686 |
</li> |
| 9687 |
<li> |
| 9688 |
ADSL users should continue with <uri link="#rp-pppoe">Alternative: |
| 9689 |
Using RP-PPPoE</uri> |
| 9690 |
</li> |
| 9691 |
<li> |
| 9692 |
PPTP users should continue with <uri link="#pptp">Alternative: |
| 9693 |
Using PPTP</uri> |
| 9694 |
</li> |
| 9695 |
</ul> |
| 9696 |
|
| 9697 |
</body> |
| 9698 |
</subsection> |
| 9699 |
<subsection id="net-setup"> |
| 9700 |
<title>Default: Using net-setup</title> |
| 9701 |
<body> |
| 9702 |
|
| 9703 |
<p> |
| 9704 |
The simplest way to set up networking if it didn't get configured |
| 9705 |
automatically is to run the <c>net-setup</c> script: |
| 9706 |
</p> |
| 9707 |
|
| 9708 |
<pre caption="Running the net-setup script"> |
| 9709 |
# <i>net-setup eth0</i> |
| 9710 |
</pre> |
| 9711 |
|
| 9712 |
<p> |
| 9713 |
<c>net-setup</c> will ask you some questions about your network |
| 9714 |
environment. When all is done, you should have a working network |
| 9715 |
connection. Test your network connection as stated before. If the tests |
| 9716 |
are positive, congratulations! You are now ready to install Gentoo. Skip |
| 9717 |
the rest of this section and continue with <uri |
| 9718 |
link="?part=1&chap=4">Preparing the Disks</uri>. |
| 9719 |
</p> |
| 9720 |
|
| 9721 |
<p> |
| 9722 |
If your network still doesn't work, continue with <uri link="#doc_chap3">Manual |
| 9723 |
Network Configuration</uri>. |
| 9724 |
</p> |
| 9725 |
|
| 9726 |
|
| 9727 |
</body> |
| 9728 |
</subsection> |
| 9729 |
<subsection id="rp-pppoe"> |
| 9730 |
<title>Alternative: Using RP-PPPoE</title> |
| 9731 |
<body> |
| 9732 |
|
| 9733 |
<p> |
| 9734 |
Assuming you need PPPoE to connect to the internet, the Installation CD (any |
| 9735 |
version) has made things easy for you by including <c>rp-pppoe</c>. Use the |
| 9736 |
provided <c>adsl-setup</c> script to configure your connection. You will be |
| 9737 |
prompted for the ethernet device that is connected to your adsl modem, your |
| 9738 |
username and password, the IPs of your DNS servers and if you need a basic |
| 9739 |
firewall or not. |
| 9740 |
</p> |
| 9741 |
|
| 9742 |
<pre caption="Using rp-pppoe"> |
| 9743 |
# <i>adsl-setup</i> |
| 9744 |
# <i>adsl-start</i> |
| 9745 |
</pre> |
| 9746 |
|
| 9747 |
<p> |
| 9748 |
If something goes wrong, double-check that you correctly typed your username and |
| 9749 |
password by looking at <path>/etc/ppp/pap-secrets</path> or |
| 9750 |
<path>/etc/ppp/chap-secrets</path> and make sure you are using the right |
| 9751 |
ethernet device. If your ethernet device doesn't exist, you will have to load |
| 9752 |
the appropriate network modules. In that case you should continue with |
| 9753 |
<uri link="#doc_chap3">Manual Network Configuration</uri> as we explain how to |
| 9754 |
load the appropriate network modules there. |
| 9755 |
</p> |
| 9756 |
|
| 9757 |
<p> |
| 9758 |
If everything worked, continue with <uri link="?part=1&chap=4">Preparing the |
| 9759 |
Disks</uri>. |
| 9760 |
</p> |
| 9761 |
|
| 9762 |
</body> |
| 9763 |
</subsection> |
| 9764 |
<subsection id="pptp"> |
| 9765 |
<title>Alternative: Using PPTP</title> |
| 9766 |
<body> |
| 9767 |
|
| 9768 |
<note> |
| 9769 |
PPTP support is only available for x86 |
| 9770 |
</note> |
| 9771 |
|
| 9772 |
<p> |
| 9773 |
If you need PPTP support, you can use <c>pptpclient</c> which is provided by our |
| 9774 |
Installation CDs. But first you need to make sure that your configuration is |
| 9775 |
correct. Edit <path>/etc/ppp/pap-secrets</path> or |
| 9776 |
<path>/etc/ppp/chap-secrets</path> so it contains the correct username/password |
| 9777 |
combination: |
| 9778 |
</p> |
| 9779 |
|
| 9780 |
<pre caption="Editing /etc/ppp/chap-secrets"> |
| 9781 |
# <i>nano -w /etc/ppp/chap-secrets</i> |
| 9782 |
</pre> |
| 9783 |
|
| 9784 |
<p> |
| 9785 |
Then adjust <path>/etc/ppp/options.pptp</path> if necessary: |
| 9786 |
</p> |
| 9787 |
|
| 9788 |
<pre caption="Editing /etc/ppp/options.pptp"> |
| 9789 |
# <i>nano -w /etc/ppp/options.pptp</i> |
| 9790 |
</pre> |
| 9791 |
|
| 9792 |
<p> |
| 9793 |
When all that is done, just run <c>pptp</c> (along with the options you couldn't |
| 9794 |
set in <path>options.pptp</path>) to connect the server: |
| 9795 |
</p> |
| 9796 |
|
| 9797 |
<pre caption="Connection to a dial-in server"> |
| 9798 |
# <i>pptp <server ip></i> |
| 9799 |
</pre> |
| 9800 |
|
| 9801 |
<p> |
| 9802 |
Now continue with <uri link="?part=1&chap=4">Preparing the Disks</uri>. |
| 9803 |
</p> |
| 9804 |
|
| 9805 |
</body> |
| 9806 |
</subsection> |
| 9807 |
</section> |
| 9808 |
<section> |
| 9809 |
<title>Manual Network Configuration</title> |
| 9810 |
<subsection> |
| 9811 |
<title>Loading the Appropriate Network Modules</title> |
| 9812 |
<body> |
| 9813 |
|
| 9814 |
<p> |
| 9815 |
When the Installation CD boots, it tries to detect all your hardware devices and |
| 9816 |
loads the appropriate kernel modules (drivers) to support your hardware. In the |
| 9817 |
vast majority of cases, it does a very good job. However, in some cases, |
| 9818 |
it may not auto-load the kernel modules you need. |
| 9819 |
</p> |
| 9820 |
|
| 9821 |
<p> |
| 9822 |
If <c>net-setup</c> or <c>adsl-setup</c> failed, then it is possible that |
| 9823 |
your network card wasn't found immediately. This means you may have to load |
| 9824 |
the appropriate kernel modules manually. |
| 9825 |
</p> |
| 9826 |
|
| 9827 |
<p> |
| 9828 |
To find out what kernel modules we provide for networking, use |
| 9829 |
<c>ls</c>: |
| 9830 |
</p> |
| 9831 |
|
| 9832 |
<pre caption="Searching for provided modules"> |
| 9833 |
# <i>ls /lib/modules/`uname -r`/kernel/drivers/net</i> |
| 9834 |
</pre> |
| 9835 |
|
| 9836 |
<p> |
| 9837 |
If you find a driver for your network card, use <c>modprobe</c> to load |
| 9838 |
the kernel module: |
| 9839 |
</p> |
| 9840 |
|
| 9841 |
<pre caption="Using modprobe to load a kernel module"> |
| 9842 |
<comment>(As an example, we load the pcnet32 module)</comment> |
| 9843 |
# <i>modprobe pcnet32</i> |
| 9844 |
</pre> |
| 9845 |
|
| 9846 |
<p> |
| 9847 |
To check if your network card is now detected, use <c>ifconfig</c>. A |
| 9848 |
detected network card would result in something like this: |
| 9849 |
</p> |
| 9850 |
|
| 9851 |
<pre caption="Testing availability of your network card, successful"> |
| 9852 |
# <i>ifconfig eth0</i> |
| 9853 |
eth0 Link encap:Ethernet HWaddr FE:FD:00:00:00:00 |
| 9854 |
BROADCAST NOARP MULTICAST MTU:1500 Metric:1 |
| 9855 |
RX packets:0 errors:0 dropped:0 overruns:0 frame:0 |
| 9856 |
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 |
| 9857 |
collisions:0 txqueuelen:0 |
| 9858 |
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) |
| 9859 |
</pre> |
| 9860 |
|
| 9861 |
<p> |
| 9862 |
If however you receive the following error, the network card is not |
| 9863 |
detected: |
| 9864 |
</p> |
| 9865 |
|
| 9866 |
<pre caption="Testing availability of your network card, failed"> |
| 9867 |
# <i>ifconfig eth0</i> |
| 9868 |
eth0: error fetching interface information: Device not found |
| 9869 |
</pre> |
| 9870 |
|
| 9871 |
<p> |
| 9872 |
If you have multiple network cards in your system they are named <e>eth0</e>, |
| 9873 |
<e>eth1</e>, etc. Make sure that the network card you want to use works well and |
| 9874 |
remember to use the correct naming throughout this document. We will assume that |
| 9875 |
the network card <e>eth0</e> is used. |
| 9876 |
</p> |
| 9877 |
|
| 9878 |
<p> |
| 9879 |
Assuming that you now have a detected network card, you can |
| 9880 |
retry <c>net-setup</c> or <c>adsl-setup</c> again (which should work |
| 9881 |
now), but for the hardcore people amongst you we explain how to configure your |
| 9882 |
network manually. |
| 9883 |
</p> |
| 9884 |
|
| 9885 |
<p> |
| 9886 |
Select one of the following sections based on your network setup: |
| 9887 |
</p> |
| 9888 |
|
| 9889 |
<ul> |
| 9890 |
<li><uri link="#dhcp">Using DHCP</uri> for automatic IP retrieval</li> |
| 9891 |
<li> |
| 9892 |
<uri link="#wireless">Preparing for Wireless Access</uri> if you have a |
| 9893 |
wireless card |
| 9894 |
</li> |
| 9895 |
<li> |
| 9896 |
<uri link="#network_term">Understanding Network Terminology</uri> explains |
| 9897 |
what you need to know about networking |
| 9898 |
</li> |
| 9899 |
<li> |
| 9900 |
<uri link="#ifconfig_route">Using ifconfig and route</uri> explains how to |
| 9901 |
set up your networking manually |
| 9902 |
</li> |
| 9903 |
</ul> |
| 9904 |
|
| 9905 |
</body> |
| 9906 |
</subsection> |
| 9907 |
<subsection id="dhcp"> |
| 9908 |
<title>Using DHCP</title> |
| 9909 |
<body> |
| 9910 |
|
| 9911 |
<p> |
| 9912 |
DHCP (Dynamic Host Configuration Protocol) makes it possible to |
| 9913 |
automatically receive networking information (IP address, netmask, |
| 9914 |
broadcast address, gateway, nameservers etc.). This only works if you |
| 9915 |
have a DHCP server in your network (or if your provider provides a DHCP |
| 9916 |
service). To have a network interface receive this information automatically, |
| 9917 |
use <c>dhcpcd</c>: |
| 9918 |
</p> |
| 9919 |
|
| 9920 |
<pre caption="Using dhcpcd"> |
| 9921 |
# <i>dhcpcd eth0</i> |
| 9922 |
<comment>Some network admins require that you use the</comment> |
| 9923 |
<comment>hostname and domainname provided by the DHCP server.</comment> |
| 9924 |
<comment>In that case, use</comment> |
| 9925 |
# <i>dhcpcd -HD eth0</i> |
| 9926 |
</pre> |
| 9927 |
|
| 9928 |
<p> |
| 9929 |
If this works (try pinging some internet server, like <uri |
| 9930 |
link="http://www.google.com">Google</uri>), then you are all set and |
| 9931 |
ready to continue. Skip the rest of this section and continue with <uri |
| 9932 |
link="?part=1&chap=4">Preparing the Disks</uri>. |
| 9933 |
</p> |
| 9934 |
|
| 9935 |
</body> |
| 9936 |
</subsection> |
| 9937 |
<subsection id="wireless"> |
| 9938 |
<title>Preparing for Wireless Access</title> |
| 9939 |
<body> |
| 9940 |
|
| 9941 |
<note> |
| 9942 |
Support for the <c>iwconfig</c> command is only available on x86, amd64 and ppc |
| 9943 |
Installation CDs. You can still get the extensions working otherwise |
| 9944 |
by following the instructions of the |
| 9945 |
<uri link="ftp://ftp.linux-wlan.org/pub/linux-wlan-ng/README">linux-wlan-ng |
| 9946 |
project</uri>. |
| 9947 |
</note> |
| 9948 |
|
| 9949 |
<p> |
| 9950 |
If you are using a wireless (802.11) card, you may need to configure your |
| 9951 |
wireless settings before going any further. To see the current wireless settings |
| 9952 |
on your card, you can use <c>iwconfig</c>. Running <c>iwconfig</c> might show |
| 9953 |
something like: |
| 9954 |
</p> |
| 9955 |
|
| 9956 |
<pre caption="Showing the current wireless settings"> |
| 9957 |
# <i>iwconfig eth0</i> |
| 9958 |
eth0 IEEE 802.11-DS ESSID:"GentooNode" |
| 9959 |
Mode:Managed Frequency:2.442GHz Access Point: 00:09:5B:11:CC:F2 |
| 9960 |
Bit Rate:11Mb/s Tx-Power=20 dBm Sensitivity=0/65535 |
| 9961 |
Retry limit:16 RTS thr:off Fragment thr:off |
| 9962 |
Power Management:off |
| 9963 |
Link Quality:25/10 Signal level:-51 dBm Noise level:-102 dBm |
| 9964 |
Rx invalid nwid:5901 Rx invalid crypt:0 Rx invalid frag:0 Tx |
| 9965 |
excessive retries:237 Invalid misc:350282 Missed beacon:84 |
| 9966 |
</pre> |
| 9967 |
|
| 9968 |
<note> |
| 9969 |
Some wireless cards may have a device name of <c>wlan0</c> or <c>ra0</c> instead |
| 9970 |
of <c>eth0</c>. Run <c>iwconfig</c> without any command-line parameters to |
| 9971 |
determine the correct device name. |
| 9972 |
</note> |
| 9973 |
|
| 9974 |
<p> |
| 9975 |
For most users, there are only two settings that might be important to change, |
| 9976 |
the ESSID (aka wireless network name) or the WEP key. If the ESSID and Access |
| 9977 |
Point address listed are already that of your access point and you are not using |
| 9978 |
WEP, then your wireless is working. If you need to change your ESSID, or add a |
| 9979 |
WEP key, you can issue the following commands: |
| 9980 |
</p> |
| 9981 |
|
| 9982 |
<pre caption="Changing ESSID and/or adding WEP key"> |
| 9983 |
<comment>(This sets the network name to "GentooNode")</comment> |
| 9984 |
# <i>iwconfig eth0 essid GentooNode</i> |
| 9985 |
|
| 9986 |
<comment>(This sets a hex WEP key)</comment> |
| 9987 |
# <i>iwconfig eth0 key 1234123412341234abcd</i> |
| 9988 |
|
| 9989 |
<comment>(This sets an ASCII key - prefix it with "s:")</comment> |
| 9990 |
# <i>iwconfig eth0 key s:some-password</i> |
| 9991 |
</pre> |
| 9992 |
|
| 9993 |
<p> |
| 9994 |
You can then confirm your wireless settings again by using <c>iwconfig</c>. |
| 9995 |
Once you have wireless working, you can continue configuring the IP level |
| 9996 |
networking options as described in the next section (<uri |
| 9997 |
link="#network_term">Understanding Network Terminology</uri>) or use the |
| 9998 |
<c>net-setup</c> tool as described previously. |
| 9999 |
</p> |
| 10000 |
|
| 10001 |
</body> |
| 10002 |
</subsection> |
| 10003 |
<subsection id="network_term"> |
| 10004 |
<title>Understanding Network Terminology</title> |
| 10005 |
<body> |
| 10006 |
|
| 10007 |
<note> |
| 10008 |
If you know your IP address, broadcast address, netmask and nameservers, |
| 10009 |
then you can skip this subsection and continue with <uri |
| 10010 |
link="#ifconfig_route">Using ifconfig and route</uri>. |
| 10011 |
</note> |
| 10012 |
|
| 10013 |
<p> |
| 10014 |
If all of the above fails, you will have to configure your network manually. |
| 10015 |
This is not difficult at all. However, you need to be familiar with some |
| 10016 |
network terminology, as you will need it to be able to |
| 10017 |
configure your network to your satisfaction. After reading this, you |
| 10018 |
will know what a <e>gateway</e> is, what a <e>netmask</e> serves for, |
| 10019 |
how a <e>broadcast</e> address is formed and why you need |
| 10020 |
<e>nameservers</e>. |
| 10021 |
</p> |
| 10022 |
|
| 10023 |
<p> |
| 10024 |
In a network, hosts are identified by their <e>IP address</e> (Internet |
| 10025 |
Protocol address). Such an address is a combination of four numbers |
| 10026 |
between 0 and 255. Well, at least that is how we perceive it. In |
| 10027 |
reality, such an IP address consists of 32 bits (ones and zeros). Let's |
| 10028 |
view an example: |
| 10029 |
</p> |
| 10030 |
|
| 10031 |
<pre caption="Example of an IP address"> |
| 10032 |
IP Address (numbers): 192.168.0.2 |
| 10033 |
IP Address (bits): 11000000 10101000 00000000 00000010 |
| 10034 |
-------- -------- -------- -------- |
| 10035 |
192 168 0 2 |
| 10036 |
</pre> |
| 10037 |
|
| 10038 |
<p> |
| 10039 |
Such an IP address is unique to a host as far as all accessible networks are |
| 10040 |
concerned (i.e. every host that you are able to reach must have a unique IP |
| 10041 |
address). In order to distinguish between hosts inside and outside a |
| 10042 |
network, the IP address is divided in two parts: the |
| 10043 |
<e>network</e> part and the <e>host</e> part. |
| 10044 |
</p> |
| 10045 |
|
| 10046 |
<p> |
| 10047 |
The separation is written down with the <e>netmask</e>, a collection of |
| 10048 |
ones followed by a collection of zeros. The part of the IP that can be |
| 10049 |
mapped on the ones is the network-part, the other one is the host-part. |
| 10050 |
As usual, the netmask can be written down as an IP-address. |
| 10051 |
</p> |
| 10052 |
|
| 10053 |
<pre caption="Example of network/host separation"> |
| 10054 |
IP-address: 192 168 0 2 |
| 10055 |
11000000 10101000 00000000 00000010 |
| 10056 |
Netmask: 11111111 11111111 11111111 00000000 |
| 10057 |
255 255 255 0 |
| 10058 |
+--------------------------+--------+ |
| 10059 |
Network Host |
| 10060 |
</pre> |
| 10061 |
|
| 10062 |
<p> |
| 10063 |
In other words, 192.168.0.14 is still part of our example network, but |
| 10064 |
192.168.1.2 is not. |
| 10065 |
</p> |
| 10066 |
|
| 10067 |
<p> |
| 10068 |
The <e>broadcast</e> address is an IP-address with the same network-part |
| 10069 |
as your network, but with only ones as host-part. Every host on your |
| 10070 |
network listens to this IP address. It is truly meant for broadcasting |
| 10071 |
packets. |
| 10072 |
</p> |
| 10073 |
|
| 10074 |
<pre caption="Broadcast address"> |
| 10075 |
IP-address: 192 168 0 2 |
| 10076 |
11000000 10101000 00000000 00000010 |
| 10077 |
Broadcast: 11000000 10101000 00000000 11111111 |
| 10078 |
192 168 0 255 |
| 10079 |
+--------------------------+--------+ |
| 10080 |
Network Host |
| 10081 |
</pre> |
| 10082 |
|
| 10083 |
<p> |
| 10084 |
To be able to surf on the internet, you must know which host shares the |
| 10085 |
Internet connection. This host is called the <e>gateway</e>. Since it is |
| 10086 |
a regular host, it has a regular IP address (for instance 192.168.0.1). |
| 10087 |
</p> |
| 10088 |
|
| 10089 |
<p> |
| 10090 |
We previously stated that every host has its own IP address. To be able |
| 10091 |
to reach this host by a name (instead of an IP address) you need a |
| 10092 |
service that translates a name (such as <e>dev.gentoo.org</e>) to an IP |
| 10093 |
address (such as <e>64.5.62.82</e>). Such a service is called a name |
| 10094 |
service. To use such a service, you must define the necessary <e>name |
| 10095 |
servers</e> in <path>/etc/resolv.conf</path>. |
| 10096 |
</p> |
| 10097 |
|
| 10098 |
<p> |
| 10099 |
In some cases, your gateway also serves as nameserver. Otherwise you |
| 10100 |
will have to enter the nameservers provided by your ISP. |
| 10101 |
</p> |
| 10102 |
|
| 10103 |
<p> |
| 10104 |
To summarise, you will need the following information before continuing: |
| 10105 |
</p> |
| 10106 |
|
| 10107 |
<table> |
| 10108 |
<tr> |
| 10109 |
<th>Network Item</th> |
| 10110 |
<th>Example</th> |
| 10111 |
</tr> |
| 10112 |
<tr> |
| 10113 |
<ti>Your IP address</ti> |
| 10114 |
<ti>192.168.0.2</ti> |
| 10115 |
</tr> |
| 10116 |
<tr> |
| 10117 |
<ti>Netmask</ti> |
| 10118 |
<ti>255.255.255.0</ti> |
| 10119 |
</tr> |
| 10120 |
<tr> |
| 10121 |
<ti>Broadcast</ti> |
| 10122 |
<ti>192.168.0.255</ti> |
| 10123 |
</tr> |
| 10124 |
<tr> |
| 10125 |
<ti>Gateway</ti> |
| 10126 |
<ti>192.168.0.1</ti> |
| 10127 |
</tr> |
| 10128 |
<tr> |
| 10129 |
<ti>Nameserver(s)</ti> |
| 10130 |
<ti>195.130.130.5, 195.130.130.133</ti> |
| 10131 |
</tr> |
| 10132 |
</table> |
| 10133 |
|
| 10134 |
</body> |
| 10135 |
</subsection> |
| 10136 |
<subsection id="ifconfig_route"> |
| 10137 |
<title>Using ifconfig and route</title> |
| 10138 |
<body> |
| 10139 |
|
| 10140 |
<p> |
| 10141 |
Setting up your network consists of three steps. First we assign |
| 10142 |
ourselves an IP address using <c>ifconfig</c>. Then we set up routing to |
| 10143 |
the gateway using <c>route</c>. Then we finish up by placing the |
| 10144 |
nameserver IPs in <path>/etc/resolv.conf</path>. |
| 10145 |
</p> |
| 10146 |
|
| 10147 |
<p> |
| 10148 |
To assign an IP address, you will need your IP address, broadcast |
| 10149 |
address and netmask. Then execute the following command, substituting |
| 10150 |
<c>${IP_ADDR}</c> with your IP address, <c>${BROADCAST}</c> with your |
| 10151 |
broadcast address and <c>${NETMASK}</c> with your netmask: |
| 10152 |
</p> |
| 10153 |
|
| 10154 |
<pre caption="Using ifconfig"> |
| 10155 |
# <i>ifconfig eth0 ${IP_ADDR} broadcast ${BROADCAST} netmask ${NETMASK} up</i> |
| 10156 |
</pre> |
| 10157 |
|
| 10158 |
<p> |
| 10159 |
Now set up routing using <c>route</c>. Substitute <c>${GATEWAY}</c> with |
| 10160 |
your gateway IP address: |
| 10161 |
</p> |
| 10162 |
|
| 10163 |
<pre caption="Using route"> |
| 10164 |
# <i>route add default gw ${GATEWAY}</i> |
| 10165 |
</pre> |
| 10166 |
|
| 10167 |
<p> |
| 10168 |
Now open <path>/etc/resolv.conf</path> with your favorite editor (in our |
| 10169 |
example, we use <c>nano</c>): |
| 10170 |
</p> |
| 10171 |
|
| 10172 |
<pre caption="Creating /etc/resolv.conf"> |
| 10173 |
# <i>nano -w /etc/resolv.conf</i> |
| 10174 |
</pre> |
| 10175 |
|
| 10176 |
<p> |
| 10177 |
Now fill in your nameserver(s) using the following as a template. Make |
| 10178 |
sure you substitute <c>${NAMESERVER1}</c> and <c>${NAMESERVER2}</c> with |
| 10179 |
the appropriate nameserver addresses: |
| 10180 |
</p> |
| 10181 |
|
| 10182 |
<pre caption="/etc/resolv.conf template"> |
| 10183 |
nameserver ${NAMESERVER1} |
| 10184 |
nameserver ${NAMESERVER2} |
| 10185 |
</pre> |
| 10186 |
|
| 10187 |
<p> |
| 10188 |
That's it. Now test your network by pinging some Internet server (like |
| 10189 |
<uri link="http://www.google.com">Google</uri>). If this works, |
| 10190 |
congratulations then. You are now ready to install Gentoo. Continue with <uri |
| 10191 |
link="?part=1&chap=4">Preparing the Disks</uri>. |
| 10192 |
</p> |
| 10193 |
|
| 10194 |
</body> |
| 10195 |
</subsection> |
| 10196 |
</section> |
| 10197 |
</sections> |
| 10198 |
|
| 10199 |
|
| 10200 |
|
| 10201 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-next.xml |
| 10202 |
|
| 10203 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-next.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 10204 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-next.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 10205 |
|
| 10206 |
Index: hb-install-next.xml |
| 10207 |
=================================================================== |
| 10208 |
<?xml version='1.0' encoding='UTF-8'?> |
| 10209 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 10210 |
|
| 10211 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 10212 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 10213 |
|
| 10214 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-next.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 10215 |
|
| 10216 |
<sections> |
| 10217 |
|
| 10218 |
<version>5.1</version> |
| 10219 |
<date>2005-08-22</date> |
| 10220 |
|
| 10221 |
<section> |
| 10222 |
<title>Documentation</title> |
| 10223 |
<subsection> |
| 10224 |
<body> |
| 10225 |
|
| 10226 |
<p> |
| 10227 |
Congratulations! You now have a working Gentoo system. But where to go from |
| 10228 |
here? What are your options now? What to explore first? Gentoo provides its |
| 10229 |
users with lots of possibilities, and therefore lots of documented (and less |
| 10230 |
documented) features. |
| 10231 |
</p> |
| 10232 |
|
| 10233 |
<p> |
| 10234 |
You should definitely take a look at the next part of the Gentoo Handbook |
| 10235 |
entitled <uri link="?part=2">Working with Gentoo</uri> which explains |
| 10236 |
how to keep your software up to date, how to install more software, what USE |
| 10237 |
flags are, how the Gentoo Init system works, etc. |
| 10238 |
</p> |
| 10239 |
|
| 10240 |
<p> |
| 10241 |
If you are interested in optimizing your system for desktop use, or you want to |
| 10242 |
learn how to configure your system to be a full working desktop system, consult |
| 10243 |
our extensive <uri link="/doc/en/index.xml?catid=desktop">Gentoo Desktop |
| 10244 |
Documentation Resources</uri>. Besides, you might want to use our <uri |
| 10245 |
link="/doc/en/guide-localization.xml">localization guide</uri> to make your |
| 10246 |
system feel more at home. |
| 10247 |
</p> |
| 10248 |
|
| 10249 |
<p> |
| 10250 |
We also have a <uri link="/doc/en/security/">Gentoo Security Handbook</uri> |
| 10251 |
which is worth reading. |
| 10252 |
</p> |
| 10253 |
|
| 10254 |
<p> |
| 10255 |
For a full listing of all our available documentation check out our <uri |
| 10256 |
link="/doc/en/index.xml">Documentation Resources</uri> page. |
| 10257 |
</p> |
| 10258 |
|
| 10259 |
</body> |
| 10260 |
</subsection> |
| 10261 |
</section> |
| 10262 |
<section> |
| 10263 |
<title>Gentoo Online</title> |
| 10264 |
<body> |
| 10265 |
|
| 10266 |
<p> |
| 10267 |
You are of course always welcome on our <uri |
| 10268 |
link="http://forums.gentoo.org">Gentoo Forums</uri> or on one of our many |
| 10269 |
<uri link="/main/en/irc.xml">Gentoo IRC channels</uri>. |
| 10270 |
</p> |
| 10271 |
|
| 10272 |
<p> |
| 10273 |
We also have several <uri |
| 10274 |
link="/main/en/lists.xml">mailinglists</uri> open to all |
| 10275 |
our users. Information on how to join is contained in that page. |
| 10276 |
</p> |
| 10277 |
|
| 10278 |
<p> |
| 10279 |
We'll shut up now and let you enjoy your installation :) |
| 10280 |
</p> |
| 10281 |
|
| 10282 |
</body> |
| 10283 |
</section> |
| 10284 |
<section> |
| 10285 |
<title>Gentoo Changes since 2006.0</title> |
| 10286 |
<subsection> |
| 10287 |
<title>Changes?</title> |
| 10288 |
<body> |
| 10289 |
|
| 10290 |
<p> |
| 10291 |
Gentoo is a fast-moving target. The following sections describe important |
| 10292 |
changes that affect a Gentoo installation. We only list those that have anything |
| 10293 |
in common with the installation, not with package changes that did not occur |
| 10294 |
during the installation. |
| 10295 |
</p> |
| 10296 |
|
| 10297 |
<p> |
| 10298 |
There have been no significant changes since. |
| 10299 |
</p> |
| 10300 |
|
| 10301 |
</body> |
| 10302 |
</subsection> |
| 10303 |
</section> |
| 10304 |
</sections> |
| 10305 |
|
| 10306 |
|
| 10307 |
|
| 10308 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc-bootloader.xml |
| 10309 |
|
| 10310 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 10311 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 10312 |
|
| 10313 |
Index: hb-install-ppc-bootloader.xml |
| 10314 |
=================================================================== |
| 10315 |
<?xml version='1.0' encoding='UTF-8'?> |
| 10316 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 10317 |
|
| 10318 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 10319 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
| 10320 |
|
| 10321 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc-bootloader.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 10322 |
|
| 10323 |
<sections> |
| 10324 |
|
| 10325 |
<version>5.3</version> |
| 10326 |
<date>2006-01-19</date> |
| 10327 |
|
| 10328 |
<section> |
| 10329 |
<title>Choosing a Bootloader</title> |
| 10330 |
<subsection> |
| 10331 |
<title>Introduction</title> |
| 10332 |
<body> |
| 10333 |
|
| 10334 |
<p> |
| 10335 |
Now that the kernel is configured and compiled, you'll need a <e>bootloader</e> |
| 10336 |
to start your new linux installation. The <e>bootloader</e> that you use will |
| 10337 |
depend upon the type of PPC machine you have. |
| 10338 |
</p> |
| 10339 |
|
| 10340 |
<p> |
| 10341 |
If you are using a NewWorld Apple or IBM machine, you need to use |
| 10342 |
<uri link="#yaboot">yaboot</uri>. OldWorld Apple machines have two options, |
| 10343 |
<uri link="#bootx">BootX</uri> (recommended) and <uri link="#quik">quik</uri>. |
| 10344 |
The Pegasos does not require a bootloader, but you will need to emerge |
| 10345 |
<uri link="#bootcreator">BootCreator</uri> to create SmartFirmware bootmenus. |
| 10346 |
</p> |
| 10347 |
|
| 10348 |
</body> |
| 10349 |
</subsection> |
| 10350 |
</section> |
| 10351 |
<section id="yaboot"> |
| 10352 |
<title>Default: Using yaboot</title> |
| 10353 |
<subsection> |
| 10354 |
<title>Introduction</title> |
| 10355 |
<body> |
| 10356 |
|
| 10357 |
<impo> |
| 10358 |
yaboot can only be used on NewWorld Apple and IBM systems! |
| 10359 |
</impo> |
| 10360 |
|
| 10361 |
<p> |
| 10362 |
In order to find the boot devices, yaboot needs access to the <path>/dev</path> |
| 10363 |
filesystem. To do this, you will need to "bind-map" the <path>/dev</path> |
| 10364 |
filesystem from the Installation CD to <path>/dev</path> inside of the chroot. |
| 10365 |
</p> |
| 10366 |
|
| 10367 |
<pre caption="Bind-mounting the /dev-filesystem"> |
| 10368 |
# <i>exit </i> # this will exit the chroot |
| 10369 |
# <i>mount -o bind /dev /mnt/gentoo/dev</i> |
| 10370 |
# <i>chroot /mnt/gentoo /bin/bash</i> |
| 10371 |
# <i>/usr/sbin/env-update && source /etc/profile </i> |
| 10372 |
</pre> |
| 10373 |
|
| 10374 |
<p> |
| 10375 |
To set up yaboot, you can use <c>yabootconfig</c> to automatically create a |
| 10376 |
configuration file for you. If you are installing Gentoo on a G5 (where |
| 10377 |
<c>yabootconfig</c> does not always work), or you plan to boot from firewire |
| 10378 |
or USB, you will need to manually configure yaboot. |
| 10379 |
</p> |
| 10380 |
|
| 10381 |
<note> |
| 10382 |
You will need to manually edit the yaboot.conf when using genkernel, even if |
| 10383 |
yabootconfig is used. The kernel image section of yaboot.conf should be |
| 10384 |
modified as follows: |
| 10385 |
</note> |
| 10386 |
|
| 10387 |
<pre caption="Adding genkernel boot arguments to yaboot.conf"> |
| 10388 |
<comment>########################################################### |
| 10389 |
## This section can be duplicated if you have more than one |
| 10390 |
## kernel or set of boot options - replace kernel-2.6.12 |
| 10391 |
## with the exact filename of your kernel. |
| 10392 |
###########################################################</comment> |
| 10393 |
image=/boot/kernel-2.6.12 |
| 10394 |
label=Linux |
| 10395 |
root=/dev/ram0 <comment># If using genkernel this is /dev/ram0</comment> |
| 10396 |
partition=3 |
| 10397 |
append="real_root=/dev/hda3 init=/linuxrc" |
| 10398 |
<comment># You can add additional kernel arguments to append such as |
| 10399 |
# rootdelay=10 for a USB/Firewire Boot</comment> |
| 10400 |
read-only |
| 10401 |
<comment>##########################################################</comment> |
| 10402 |
</pre> |
| 10403 |
|
| 10404 |
<ul> |
| 10405 |
<li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li> |
| 10406 |
<li> |
| 10407 |
<uri link="#manual_yaboot">Alternative: Manual yaboot Configuration</uri> |
| 10408 |
</li> |
| 10409 |
</ul> |
| 10410 |
|
| 10411 |
</body> |
| 10412 |
</subsection> |
| 10413 |
<subsection id="yabootconfig"> |
| 10414 |
<title>Default: Using yabootconfig</title> |
| 10415 |
<body> |
| 10416 |
|
| 10417 |
<p> |
| 10418 |
<c>yabootconfig</c> will auto-detect the partitions on your machine and will |
| 10419 |
set up dual and triple boot combinations with Linux, Mac OS, and Mac OS X. |
| 10420 |
</p> |
| 10421 |
|
| 10422 |
<p> |
| 10423 |
To use <c>yabootconfig</c>, your drive must have an Apple_Bootstrap partition, |
| 10424 |
and <path>/etc/fstab</path> must be configured with your Linux partitions. Both |
| 10425 |
of these should have been done already in the steps above. To start, ensure that |
| 10426 |
you have the latest <c>yaboot</c> installed. |
| 10427 |
</p> |
| 10428 |
|
| 10429 |
<pre caption = "Installing yaboot with GRP"> |
| 10430 |
# <i>emerge --usepkg --update yaboot</i> |
| 10431 |
</pre> |
| 10432 |
|
| 10433 |
<p> |
| 10434 |
Now exit the chroot and run <c>yabootconfig --chroot /mnt/gentoo</c>. The |
| 10435 |
program will run and it will confirm the location of the bootstrap partition. |
| 10436 |
Type <c>Y</c> if it is correct. If not, double check <path>/etc/fstab</path>. |
| 10437 |
yabootconfig will then scan your system setup, create |
| 10438 |
<path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for you. <c>mkofboot</c> |
| 10439 |
is used to format the Apple_Bootstrap partition, and install the yaboot |
| 10440 |
configuration file into it. After this enter the chroot again. |
| 10441 |
</p> |
| 10442 |
<pre caption="enter chroot"> |
| 10443 |
# <i>chroot /mnt/gentoo /bin/bash</i> |
| 10444 |
# <i>/usr/sbin/env-update && source /etc/profile</i> |
| 10445 |
</pre> |
| 10446 |
|
| 10447 |
<p> |
| 10448 |
You might want to verify the contents of <path>/etc/yaboot.conf</path>. If you |
| 10449 |
make changes to <path>/etc/yaboot.conf</path> (like setting the default/boot |
| 10450 |
OS), make sure to rerun <c>ybin -v</c> to apply changes to the Apple_Bootstrap |
| 10451 |
partition. |
| 10452 |
</p> |
| 10453 |
|
| 10454 |
<p> |
| 10455 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
| 10456 |
</p> |
| 10457 |
|
| 10458 |
</body> |
| 10459 |
</subsection> |
| 10460 |
<subsection id="manual_yaboot"> |
| 10461 |
<title>Alternative: Manual yaboot Configuration</title> |
| 10462 |
<body> |
| 10463 |
|
| 10464 |
<p> |
| 10465 |
First make sure you have the latest <c>yaboot</c> installed on your |
| 10466 |
system: |
| 10467 |
</p> |
| 10468 |
|
| 10469 |
<pre caption = "Installing yaboot"> |
| 10470 |
# <i>emerge --usepkg --update yaboot</i> |
| 10471 |
</pre> |
| 10472 |
|
| 10473 |
<p> |
| 10474 |
An example <path>yaboot.conf</path> file is given below, but you will need to |
| 10475 |
alter it to fit your needs. G5 users and users booting from firewire and USB |
| 10476 |
should be aware that their disks are seen as SCSI disks by the Linux kernel, so |
| 10477 |
you will need to substitute <path>/dev/hda</path> with <path>/dev/sda</path>). |
| 10478 |
</p> |
| 10479 |
|
| 10480 |
<pre caption = "/etc/yaboot.conf"> |
| 10481 |
<comment>## /etc/yaboot.conf |
| 10482 |
## |
| 10483 |
## run: "man yaboot.conf" for details. Do not make changes until you have!! |
| 10484 |
## see also: /usr/share/doc/yaboot/examples for example configurations. |
| 10485 |
## |
| 10486 |
## For a dual-boot menu, add one or more of: |
| 10487 |
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ |
| 10488 |
|
| 10489 |
## our bootstrap partition:</comment> |
| 10490 |
|
| 10491 |
boot=/dev/hda2 |
| 10492 |
|
| 10493 |
<comment>## ofboot is the openfirmware way to specify the bootstrap partition. |
| 10494 |
## If this isn't defined, yaboot fails on the G5 and some G4s (unless |
| 10495 |
## you pass the necessary arguments to the mkofboot/ybin program). |
| 10496 |
## hd:X means /dev/sdaX (or /dev/hdaX). |
| 10497 |
## |
| 10498 |
## G5 users should uncomment this line!! |
| 10499 |
|
| 10500 |
#ofboot=hd:2 |
| 10501 |
|
| 10502 |
## Users booting from firewire should use something like this line: |
| 10503 |
# ofboot=fw/node/sbp-2/disk@0: |
| 10504 |
|
| 10505 |
## Users booting from USB should use something like this line: |
| 10506 |
# ofboot=usb/disk@0: |
| 10507 |
|
| 10508 |
## hd: is shorthand for the first hard drive OpenFirmware sees</comment> |
| 10509 |
device=hd: |
| 10510 |
|
| 10511 |
<comment>## Firewire and USB users will need to specify the whole OF device name |
| 10512 |
## This can be found using ofpath, which is included with yaboot. |
| 10513 |
|
| 10514 |
# device=fw/node@0001d200e00d0207/sbp-2@c000/disk@0: |
| 10515 |
</comment> |
| 10516 |
|
| 10517 |
delay=5 |
| 10518 |
defaultos=macosx |
| 10519 |
timeout=30 |
| 10520 |
install=/usr/lib/yaboot/yaboot |
| 10521 |
magicboot=/usr/lib/yaboot/ofboot |
| 10522 |
|
| 10523 |
<comment>################# |
| 10524 |
## This section can be duplicated if you have more than one kernel or set of |
| 10525 |
## boot options - replace 2.6.9 with your kernel-version |
| 10526 |
#################</comment> |
| 10527 |
image=/boot/kernel-2.6.9 |
| 10528 |
label=Linux |
| 10529 |
root=/dev/hda3 |
| 10530 |
partition=3 |
| 10531 |
<comment># append="rootdelay=10" # Required for booting USB/Firewire</comment> |
| 10532 |
read-only |
| 10533 |
<comment>################## |
| 10534 |
|
| 10535 |
## G5 users and some G4 users should set |
| 10536 |
## macos=hd:13 |
| 10537 |
## macosx=hd:12 |
| 10538 |
## instead of the example values.</comment> |
| 10539 |
macos=/dev/hda13 |
| 10540 |
macosx=/dev/hda12 |
| 10541 |
enablecdboot |
| 10542 |
enableofboot |
| 10543 |
</pre> |
| 10544 |
|
| 10545 |
<p> |
| 10546 |
Once <path>yaboot.conf</path> is configured, run <c>mkofboot -v</c> to format |
| 10547 |
the Apple_bootstrap partition and install the settings. If you change |
| 10548 |
yaboot.conf after the Apple_bootstrap partition has been created, you can |
| 10549 |
update the settings by running <c>ybin -v</c> |
| 10550 |
</p> |
| 10551 |
|
| 10552 |
<p> |
| 10553 |
For more information on yaboot, take a look at the <uri |
| 10554 |
link="http://penguinppc.org/bootloaders/yaboot">yaboot project</uri>. For |
| 10555 |
now, continue the installation with <uri link="#reboot">Rebooting the |
| 10556 |
System</uri>. |
| 10557 |
</p> |
| 10558 |
|
| 10559 |
</body> |
| 10560 |
</subsection> |
| 10561 |
</section> |
| 10562 |
<section id="bootx"> |
| 10563 |
<title>Alternative: BootX</title> |
| 10564 |
<body> |
| 10565 |
|
| 10566 |
<impo> |
| 10567 |
BootX can only be used on OldWorld Apple systems! |
| 10568 |
</impo> |
| 10569 |
|
| 10570 |
<p> |
| 10571 |
Since BootX boots Linux from within MacOS, the kernel will need to be copied |
| 10572 |
from the Linux Partition to the MacOS partition. First, mount the MacOS |
| 10573 |
partition from outside of the chroot. Use <c>mac-fdisk -l</c> to find the |
| 10574 |
MacOS partition number, sda6 is used as an example here. Once the partition is |
| 10575 |
mounted, we'll copy the kernel to the system folder so BootX can find it. |
| 10576 |
</p> |
| 10577 |
|
| 10578 |
<pre caption="Copying the kernel to the MacOS partition"> |
| 10579 |
# <i>exit</i> |
| 10580 |
cdimage ~# <i>mkdir /mnt/mac</i> |
| 10581 |
cdimage ~# <i>mount /dev/sda6 /mnt/mac -t hfs</i> |
| 10582 |
cdimage ~# <i>cp /mnt/gentoo/usr/src/linux/vmlinux "/mnt/mac/System Folder/Linux Kernels"</i> |
| 10583 |
</pre> |
| 10584 |
|
| 10585 |
<p> |
| 10586 |
If genkernel is used, both the kernel and initrd will need to be copied to the |
| 10587 |
MacOS partition. |
| 10588 |
</p> |
| 10589 |
|
| 10590 |
<pre caption="Copying the Genkernel kernel and initrd to the MacOS partition"> |
| 10591 |
# <i>exit</i> |
| 10592 |
cdimage ~# <i>mkdir /mnt/mac</i> |
| 10593 |
cdimage ~# <i>mount /dev/sda6 /mnt/mac -t hfs</i> |
| 10594 |
cdimage ~# <i>cp /mnt/gentoo/boot/kernel-* "/mnt/mac/System Folder/Linux Kernels"</i> |
| 10595 |
cdimage ~# <i>cp /mnt/gentoo/boot/initramfs-* "/mnt/mac/System Folder"</i> |
| 10596 |
</pre> |
| 10597 |
|
| 10598 |
<p> |
| 10599 |
Now that the kernel is copied over, we'll need to reboot to set up BootX. |
| 10600 |
</p> |
| 10601 |
|
| 10602 |
<pre caption="Unmounting all partitions and rebooting"> |
| 10603 |
cdimage ~# <i>cd /</i> |
| 10604 |
cdimage ~# <i>umount /mnt/gentoo/proc /mnt/gentoo/dev /mnt/gentoo /mnt/mac</i> |
| 10605 |
cdimage ~# <i>reboot</i> |
| 10606 |
</pre> |
| 10607 |
|
| 10608 |
<p> |
| 10609 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
| 10610 |
booted again instead of MacOS. |
| 10611 |
</p> |
| 10612 |
|
| 10613 |
<p> |
| 10614 |
Once the machine has booted into MacOS, open the BootX control panel. If you're |
| 10615 |
not using genkernel, select <c>Options</c> and uncheck <c>Use specified RAM |
| 10616 |
disk</c>. If you are using genkernel, ensure that the genkernel initrd is |
| 10617 |
selected instead of the Installation CD initrd. If not using genkernel, |
| 10618 |
there is now an option to specify the machine's Linux root disk and partition. |
| 10619 |
Fill these in with the appropriate values. Depending upon the kernel |
| 10620 |
configuration, additional boot arguments may need to be applied. |
| 10621 |
</p> |
| 10622 |
|
| 10623 |
<p> |
| 10624 |
BootX can be configured to start Linux upon boot. If you do this, you will first |
| 10625 |
see your machine boot into MacOS then, during startup, BootX will load and start |
| 10626 |
Linux. See the <uri link="http://penguinppc.org/bootloaders/bootx/">BootX home |
| 10627 |
page</uri> for more information. |
| 10628 |
</p> |
| 10629 |
|
| 10630 |
<p> |
| 10631 |
Now reboot again and boot into Linux, then continue with <uri |
| 10632 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
| 10633 |
</p> |
| 10634 |
|
| 10635 |
</body> |
| 10636 |
</section> |
| 10637 |
<section id="quik"> |
| 10638 |
<title>Alternative: quik</title> |
| 10639 |
<body> |
| 10640 |
|
| 10641 |
<p> |
| 10642 |
quik allows OldWorld Macs to boot without MacOS. However, it isn't well |
| 10643 |
supported and has a number of quirks. If you have the option, it is recommended |
| 10644 |
that you use BootX instead since it is much more reliable and easier to set up |
| 10645 |
than quik. |
| 10646 |
</p> |
| 10647 |
|
| 10648 |
<p> |
| 10649 |
First, we'll need to install quik: |
| 10650 |
</p> |
| 10651 |
|
| 10652 |
<pre caption="Emerge quik"> |
| 10653 |
# <i>emerge quik</i> |
| 10654 |
</pre> |
| 10655 |
|
| 10656 |
<p> |
| 10657 |
Next, we'll need to set it up. Edit /etc/quik.conf and set your image to the |
| 10658 |
kernel that we copied to your boot partition. |
| 10659 |
</p> |
| 10660 |
|
| 10661 |
<pre caption="Configuring quik.conf"> |
| 10662 |
# Example of quik.conf |
| 10663 |
init-message = "Gentoo 2006.0\n" |
| 10664 |
partition = 2 <comment># This is the boot partition</comment> |
| 10665 |
root = /dev/hda4 |
| 10666 |
timeout = 30 |
| 10667 |
default = gentoo |
| 10668 |
image = /vmlinux-2.6.12 |
| 10669 |
label = gentoo |
| 10670 |
</pre> |
| 10671 |
|
| 10672 |
<p> |
| 10673 |
Your quik.conf file <e>must</e> be on the same disk as the quik boot images, |
| 10674 |
however it can be on a different partition on the same disk, although it is |
| 10675 |
recommended to move it to your boot partition. |
| 10676 |
</p> |
| 10677 |
|
| 10678 |
<pre caption="Moving quik.conf to /boot"> |
| 10679 |
# <i>mv /etc/quik.conf /boot/quik.conf</i> |
| 10680 |
</pre> |
| 10681 |
|
| 10682 |
<p> |
| 10683 |
We will now set your boot variables so that quik loads on boot. To do this, |
| 10684 |
we'll use a program called <c>nvsetenv</c>. The variables that you want to |
| 10685 |
set vary from machine to machine, it's best to find your machine's |
| 10686 |
<uri link="http://penguinppc.org/bootloaders/quik/quirks.php">quirks</uri> |
| 10687 |
before attempting this. |
| 10688 |
</p> |
| 10689 |
|
| 10690 |
<pre caption="Setting the boot variables"> |
| 10691 |
# <i>nvsetenv auto-boot true</i> <comment># Set to false if you want to boot into OF, not all models can display the OF output</comment> |
| 10692 |
# <i>nvsetenv output-device video</i> <comment># Check the quirks page, there are many variations here</comment> |
| 10693 |
# <i>nvsetenv input-device kbd</i> |
| 10694 |
# <i>nvsetenv boot-device scsi/sd@1:0</i> <comment># For SCSI</comment> |
| 10695 |
# <i>nvsetenv boot-device ata/ata-disk@0:0</i> <comment># For ATA</comment> |
| 10696 |
# <i>nvsetenv boot-file /boot/vmlinux-2.6.12 root=/dev/hda4</i> <comment>First item is the path to the kernel, the second is the root partition. You may append any kernel options to the end of this line.</comment> |
| 10697 |
# <i>nvsetenv boot-command boot</i> <comment># Set this to bye for MacOS and boot for Linux</comment> |
| 10698 |
</pre> |
| 10699 |
|
| 10700 |
<note> |
| 10701 |
It is also possible to change your boot variables from MacOS. Depending |
| 10702 |
upon the model, either |
| 10703 |
<uri link="http://penguinppc.org/bootloaders/quik/BootVars.sit.hqx">bootvars</uri> or |
| 10704 |
<uri link="ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin"> |
| 10705 |
Apple System Disk</uri> should be used. Please see the quik quirks page |
| 10706 |
above for more information. |
| 10707 |
</note> |
| 10708 |
|
| 10709 |
<p> |
| 10710 |
Now that we've set up our machine to boot, we'll need to make sure the boot |
| 10711 |
images are installed correctly. Run <c>quik -v -C /boot/quik.conf</c>. It |
| 10712 |
should tell you that it has installed the first stage QUIK boot block. |
| 10713 |
</p> |
| 10714 |
|
| 10715 |
<note> |
| 10716 |
If something has gone wrong, you can always reset your PRAM back to the default |
| 10717 |
values by holding down <c>command + option + p + r</c> before powering on your |
| 10718 |
machine. This will clear the values you set with nvsetenv and should allow you |
| 10719 |
to boot either a MacOS bootdisk or a Linux bootdisk. |
| 10720 |
</note> |
| 10721 |
|
| 10722 |
<p> |
| 10723 |
Now, continue the installation with |
| 10724 |
<uri link="#reboot">Rebooting the System</uri>. |
| 10725 |
</p> |
| 10726 |
|
| 10727 |
</body> |
| 10728 |
</section> |
| 10729 |
<section id="bootcreator"> |
| 10730 |
<title>Alternative: BootCreator</title> |
| 10731 |
<body> |
| 10732 |
|
| 10733 |
<impo> |
| 10734 |
BootCreator will build a nice SmartFirmware bootmenu written in Forth for the |
| 10735 |
Pegasos. |
| 10736 |
</impo> |
| 10737 |
|
| 10738 |
<p> |
| 10739 |
First make sure you have the latest <c>bootcreator</c> installed on your |
| 10740 |
system: |
| 10741 |
</p> |
| 10742 |
|
| 10743 |
<pre caption = "Installing bootcreator"> |
| 10744 |
# <i>emerge --usepkg --update bootcreator</i> |
| 10745 |
</pre> |
| 10746 |
|
| 10747 |
<p> |
| 10748 |
Now copy the file <path>/etc/bootmenu.example</path> into |
| 10749 |
<path>/etc/bootmenu</path> and edit it to your needs: |
| 10750 |
</p> |
| 10751 |
|
| 10752 |
<pre caption = "Edit the bootcreator config file"> |
| 10753 |
# <i>cp /etc/bootmenu.example /etc/bootmenu</i> |
| 10754 |
# <i>nano -w /etc/bootmenu</i> |
| 10755 |
</pre> |
| 10756 |
|
| 10757 |
<p> |
| 10758 |
Below you find a completed <path>/etc/bootmenu</path> config file. Alter it at |
| 10759 |
will. |
| 10760 |
</p> |
| 10761 |
|
| 10762 |
<pre caption = "bootcreator config file"> |
| 10763 |
<comment># |
| 10764 |
# Example description file for bootcreator 1.1 |
| 10765 |
#</comment> |
| 10766 |
|
| 10767 |
[VERSION] |
| 10768 |
1 |
| 10769 |
|
| 10770 |
[TITLE] |
| 10771 |
Boot Menu |
| 10772 |
|
| 10773 |
[SETTINGS] |
| 10774 |
AbortOnKey = false |
| 10775 |
Timeout = 9 |
| 10776 |
Default = 1 |
| 10777 |
|
| 10778 |
[SECTION] |
| 10779 |
Local HD -> Morphos (Normal) |
| 10780 |
ide:0 boot2.img ramdebug edebugflags="logkprintf" |
| 10781 |
|
| 10782 |
[SECTION] |
| 10783 |
Local HD -> Linux 2.6.12 (Normal) |
| 10784 |
ide:0 linux-2.6.12 video=radeonfb:1024x768@70 root=/dev/hda3 |
| 10785 |
|
| 10786 |
[SECTION] |
| 10787 |
Local HD -> Genkernel (Normal) |
| 10788 |
ide:0 kernelz-2.6.12 root=/dev/ram0 real_root=/dev/hda3 init=/linuxrc |
| 10789 |
</pre> |
| 10790 |
|
| 10791 |
<p> |
| 10792 |
Finally the <path>bootmenu</path> must be transfered into Forth and copied to |
| 10793 |
your boot partition, so that the SmartFirmware can read it. Therefore you have |
| 10794 |
to call <c>bootcreator</c>: |
| 10795 |
</p> |
| 10796 |
|
| 10797 |
<pre caption = "Install the bootmenu"> |
| 10798 |
# <i>bootcreator /etc/bootmenu /boot/menu</i> |
| 10799 |
</pre> |
| 10800 |
|
| 10801 |
<note> |
| 10802 |
Be sure to have a look into the SmartFirmware's settings when you reboot, that |
| 10803 |
<path>menu</path> is the file that will be loaded by default. |
| 10804 |
</note> |
| 10805 |
|
| 10806 |
<p> |
| 10807 |
For now, continue the installation with <uri link="#reboot">Rebooting the |
| 10808 |
System</uri>. |
| 10809 |
</p> |
| 10810 |
|
| 10811 |
|
| 10812 |
</body> |
| 10813 |
</section> |
| 10814 |
<section id="reboot"> |
| 10815 |
<title>Rebooting the System</title> |
| 10816 |
<subsection> |
| 10817 |
<body> |
| 10818 |
|
| 10819 |
<p> |
| 10820 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
| 10821 |
that one magical command you have been waiting for: <c>reboot</c>. |
| 10822 |
</p> |
| 10823 |
|
| 10824 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
| 10825 |
# <i>exit</i> |
| 10826 |
livecd ~# <i>umount /mnt/gentoo/proc /mnt/gentoo/dev /mnt/gentoo</i> |
| 10827 |
livecd ~# <i>reboot</i> |
| 10828 |
</pre> |
| 10829 |
|
| 10830 |
<p> |
| 10831 |
Once rebooted in your Gentoo installation, finish up with <uri |
| 10832 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
| 10833 |
</p> |
| 10834 |
|
| 10835 |
</body> |
| 10836 |
</subsection> |
| 10837 |
</section> |
| 10838 |
</sections> |
| 10839 |
|
| 10840 |
|
| 10841 |
|
| 10842 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc-disk.xml |
| 10843 |
|
| 10844 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 10845 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 10846 |
|
| 10847 |
Index: hb-install-ppc-disk.xml |
| 10848 |
=================================================================== |
| 10849 |
<?xml version='1.0' encoding='UTF-8'?> |
| 10850 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 10851 |
|
| 10852 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 10853 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 10854 |
|
| 10855 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc-disk.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 10856 |
|
| 10857 |
<sections> |
| 10858 |
|
| 10859 |
<version>5.1</version> |
| 10860 |
<date>2005-08-25</date> |
| 10861 |
|
| 10862 |
<section> |
| 10863 |
<title>Introduction to Block Devices</title> |
| 10864 |
<subsection> |
| 10865 |
<title>Block Devices</title> |
| 10866 |
<body> |
| 10867 |
|
| 10868 |
<p> |
| 10869 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
| 10870 |
and Linux in general, including Linux filesystems, partitions and block devices. |
| 10871 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
| 10872 |
you'll be guided through the process of setting up partitions and filesystems |
| 10873 |
for your Gentoo Linux installation. |
| 10874 |
</p> |
| 10875 |
|
| 10876 |
<p> |
| 10877 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
| 10878 |
probably the one that represents the first IDE drive in a Linux system, namely |
| 10879 |
<path>/dev/hda</path>. If your system uses SCSI or SATA drives, then your first |
| 10880 |
hard drive would be <path>/dev/sda</path>. |
| 10881 |
</p> |
| 10882 |
|
| 10883 |
<p> |
| 10884 |
The block devices above represent an abstract interface to the disk. User |
| 10885 |
programs can use these block devices to interact with your disk without worrying |
| 10886 |
about whether your drives are IDE, SCSI or something else. The program can |
| 10887 |
simply address the storage on the disk as a bunch of contiguous, |
| 10888 |
randomly-accessible 512-byte blocks. |
| 10889 |
</p> |
| 10890 |
|
| 10891 |
</body> |
| 10892 |
</subsection> |
| 10893 |
<subsection> |
| 10894 |
<title>Partitions</title> |
| 10895 |
<body> |
| 10896 |
|
| 10897 |
<p> |
| 10898 |
Although it is theoretically possible to use a full disk to house your Linux |
| 10899 |
system, this is almost never done in practice. Instead, full disk block devices |
| 10900 |
are split up in smaller, more manageable block devices. On most systems, |
| 10901 |
these are called <e>partitions</e>. |
| 10902 |
</p> |
| 10903 |
|
| 10904 |
</body> |
| 10905 |
</subsection> |
| 10906 |
</section> |
| 10907 |
<section> |
| 10908 |
<title>Designing a Partitioning Scheme</title> |
| 10909 |
<subsection> |
| 10910 |
<title>Default Partitioning Scheme</title> |
| 10911 |
<body> |
| 10912 |
|
| 10913 |
<p> |
| 10914 |
If you are not interested in drawing up a partitioning scheme for your system, |
| 10915 |
you can use the partitioning scheme we use throughout this book: |
| 10916 |
</p> |
| 10917 |
|
| 10918 |
<table> |
| 10919 |
<tr> |
| 10920 |
<th>Partition NewWorld</th> |
| 10921 |
<th>Partition OldWorld</th> |
| 10922 |
<th>Partition Pegasos</th> |
| 10923 |
<th>Partition RS/6000</th> |
| 10924 |
<th>Filesystem</th> |
| 10925 |
<th>Size</th> |
| 10926 |
<th>Description</th> |
| 10927 |
</tr> |
| 10928 |
<tr> |
| 10929 |
<ti><path>/dev/hda1</path></ti> |
| 10930 |
<ti><path>/dev/hda1</path></ti> |
| 10931 |
<ti>(Not applicable)</ti> |
| 10932 |
<ti>(Not applicable)</ti> |
| 10933 |
<ti>(Partition Map)</ti> |
| 10934 |
<ti>32k</ti> |
| 10935 |
<ti>Apple_partition_map</ti> |
| 10936 |
</tr> |
| 10937 |
<tr> |
| 10938 |
<ti><path>/dev/hda2</path></ti> |
| 10939 |
<ti>(Not needed)</ti> |
| 10940 |
<ti>(Not applicable)</ti> |
| 10941 |
<ti>(Not applicable)</ti> |
| 10942 |
<ti>(bootstrap)</ti> |
| 10943 |
<ti>800k</ti> |
| 10944 |
<ti>Apple_Bootstrap</ti> |
| 10945 |
</tr> |
| 10946 |
<tr> |
| 10947 |
<ti>(Not applicable)</ti> |
| 10948 |
<ti>(Not applicable)</ti> |
| 10949 |
<ti>(Not applicable)</ti> |
| 10950 |
<ti><path>/dev/sda1</path></ti> |
| 10951 |
<ti>(PReP Boot)</ti> |
| 10952 |
<ti>800k</ti> |
| 10953 |
<ti>Type 0x41</ti> |
| 10954 |
</tr> |
| 10955 |
<tr> |
| 10956 |
<ti>(Not applicable)</ti> |
| 10957 |
<ti><path>/dev/hda2</path> (If using quik)</ti> |
| 10958 |
<ti><path>/dev/hda1</path></ti> |
| 10959 |
<ti>(Not needed)</ti> |
| 10960 |
<ti>ext2</ti> |
| 10961 |
<ti>32MB</ti> |
| 10962 |
<ti>Boot partition</ti> |
| 10963 |
</tr> |
| 10964 |
<tr> |
| 10965 |
<ti><path>/dev/hda3</path></ti> |
| 10966 |
<ti><path>/dev/hda2</path> (<path>/dev/hda3</path> if using quik)</ti> |
| 10967 |
<ti><path>/dev/hda2</path></ti> |
| 10968 |
<ti><path>/dev/sda2</path></ti> |
| 10969 |
<ti>(swap)</ti> |
| 10970 |
<ti>512M</ti> |
| 10971 |
<ti>Swap partition, Type 0x82</ti> |
| 10972 |
</tr> |
| 10973 |
<tr> |
| 10974 |
<ti><path>/dev/hda4</path></ti> |
| 10975 |
<ti><path>/dev/hda3</path> (<path>/dev/hda4</path> if using quik)</ti> |
| 10976 |
<ti><path>/dev/hda3</path></ti> |
| 10977 |
<ti><path>/dev/sda3</path></ti> |
| 10978 |
<ti>ext3, xfs</ti> |
| 10979 |
<ti>Rest of the disk</ti> |
| 10980 |
<ti>Root partition, Type 0x83</ti> |
| 10981 |
</tr> |
| 10982 |
</table> |
| 10983 |
|
| 10984 |
<note> |
| 10985 |
There are some partitions named: <path>Apple_Driver63, Apple_Driver_ATA, |
| 10986 |
Apple_FWDriver, Apple_Driver_IOKit, Apple_Patches</path>. If you are not |
| 10987 |
planning to use MacOS 9 you can delete them, because MacOS X and Linux don't |
| 10988 |
need them. To delete them, either use parted or erase the whole disk by |
| 10989 |
initialing the partition map. |
| 10990 |
</note> |
| 10991 |
|
| 10992 |
<warn> |
| 10993 |
<c>parted</c> is able to resize partitions. On the Installation CD there |
| 10994 |
are patches included to resize HFS+ filesystem. Unfortunately it is not |
| 10995 |
possible to resize HFS+ journaled filesystems, even if the journaling has been |
| 10996 |
switchedoff in Mac OS X. Everything you do with resizing in parted you do it |
| 10997 |
on your own risk! Be sure to have a backup of your data! |
| 10998 |
</warn> |
| 10999 |
|
| 11000 |
<p> |
| 11001 |
If you are interested in knowing how big a partition should be, or even how many |
| 11002 |
partitions you need, read on. Otherwise continue now with |
| 11003 |
<uri link="#mac-fdisk"> Default: Using mac-fdisk (Apple) to Partition your Disk |
| 11004 |
</uri> or <uri link="#parted">Alternative: Using parted (IBM/Pegasos) to |
| 11005 |
Partition your Disk</uri>. |
| 11006 |
</p> |
| 11007 |
|
| 11008 |
</body> |
| 11009 |
</subsection> |
| 11010 |
<subsection> |
| 11011 |
<title>How Many and How Big?</title> |
| 11012 |
<body> |
| 11013 |
|
| 11014 |
<p> |
| 11015 |
The number of partitions is highly dependent on your environment. For instance, |
| 11016 |
if you have lots of users, you will most likely want to have your |
| 11017 |
<path>/home</path> separate as it increases security and makes backups easier. |
| 11018 |
If you are installing Gentoo to perform as a mailserver, your <path>/var</path> |
| 11019 |
should be separate as all mails are stored inside <path>/var</path>. A good |
| 11020 |
choice of filesystem will then maximise your performance. Gameservers will have |
| 11021 |
a separate <path>/opt</path> as most gaming servers are installed there. The |
| 11022 |
reason is similar for <path>/home</path>: security and backups. You will |
| 11023 |
definitely want to keep <path>/usr</path> big: not only will it contain the |
| 11024 |
majority of applications, the Portage tree alone takes around 500 Mbyte |
| 11025 |
excluding the various sources that are stored in it. |
| 11026 |
</p> |
| 11027 |
|
| 11028 |
<p> |
| 11029 |
As you can see, it very much depends on what you want to achieve. Separate |
| 11030 |
partitions or volumes have the following advantages: |
| 11031 |
</p> |
| 11032 |
|
| 11033 |
<ul> |
| 11034 |
<li> |
| 11035 |
You can choose the best performing filesystem for each partition or volume |
| 11036 |
</li> |
| 11037 |
<li> |
| 11038 |
Your entire system cannot run out of free space if one defunct tool is |
| 11039 |
continuously writing files to a partition or volume |
| 11040 |
</li> |
| 11041 |
<li> |
| 11042 |
If necessary, file system checks are reduced in time, as multiple checks can |
| 11043 |
be done in parallel (although this advantage is more with multiple disks than |
| 11044 |
it is with multiple partitions) |
| 11045 |
</li> |
| 11046 |
<li> |
| 11047 |
Security can be enhanced by mounting some partitions or volumes read-only, |
| 11048 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
| 11049 |
</li> |
| 11050 |
</ul> |
| 11051 |
|
| 11052 |
<p> |
| 11053 |
However, multiple partitions have one big disadvantage: if not configured |
| 11054 |
properly, you might result in having a system with lots of free space on one |
| 11055 |
partition and none on another. There is also a 15-partition limit for SCSI and |
| 11056 |
SATA. |
| 11057 |
</p> |
| 11058 |
|
| 11059 |
</body> |
| 11060 |
</subsection> |
| 11061 |
</section> |
| 11062 |
<section id="mac-fdisk"> |
| 11063 |
<title>Default: Using mac-fdisk (Apple) Partition your Disk</title> |
| 11064 |
<body> |
| 11065 |
|
| 11066 |
<p> |
| 11067 |
At this point, create your partitions using <c>mac-fdisk</c>: |
| 11068 |
</p> |
| 11069 |
|
| 11070 |
<pre caption="Starting mac-fdisk"> |
| 11071 |
# <i>mac-fdisk /dev/hda</i> |
| 11072 |
</pre> |
| 11073 |
|
| 11074 |
<p> |
| 11075 |
First delete the partitions you have cleared previously to make room for your |
| 11076 |
Linux partitions. Use <c>d</c> in <c>mac-fdisk</c> to delete those partition(s). |
| 11077 |
It will ask for the partition number to delete. Usually the first partition on |
| 11078 |
NewWorld machines (Apple_partition_map) could not be deleted. |
| 11079 |
</p> |
| 11080 |
|
| 11081 |
<p> |
| 11082 |
Second, create an <e>Apple_Bootstrap</e> partition by using <c>b</c>. It will |
| 11083 |
ask for what block you want to start. Enter the number of your first free |
| 11084 |
partition, followed by a <c>p</c>. For instance this is <c>2p</c>. |
| 11085 |
</p> |
| 11086 |
|
| 11087 |
<note> |
| 11088 |
This partition is <e>not</e> a <path>/boot</path> partition. It is not used by |
| 11089 |
Linux at all; you don't have to place any filesystem on it and you should never |
| 11090 |
mount it. Apple users don't need an extra partition for <path>/boot</path>. |
| 11091 |
</note> |
| 11092 |
|
| 11093 |
<p> |
| 11094 |
Now create a swap partition by pressing <c>c</c>. Again <c>mac-fdisk</c> will |
| 11095 |
ask for what block you want to start this partition from. As we used <c>2</c> |
| 11096 |
before to create the Apple_Bootstrap partition, you now have to enter |
| 11097 |
<c>3p</c>. When you're asked for the size, enter <c>512M</c> (or whatever size |
| 11098 |
you want -- 512MB is recommended though). When asked for a name, enter <c>swap</c> |
| 11099 |
(mandatory). |
| 11100 |
</p> |
| 11101 |
|
| 11102 |
<p> |
| 11103 |
To create the root partition, enter <c>c</c>, followed by <c>4p</c> to select |
| 11104 |
from what block the root partition should start. When asked for the size, enter |
| 11105 |
<c>4p</c> again. <c>mac-fdisk</c> will interpret this as "Use all available |
| 11106 |
space". When asked for the name, enter <c>root</c> (mandatory). |
| 11107 |
</p> |
| 11108 |
|
| 11109 |
<p> |
| 11110 |
To finish up, write the partition to the disk using <c>w</c> and <c>q</c> to |
| 11111 |
quit <c>mac-fdisk</c>. |
| 11112 |
</p> |
| 11113 |
|
| 11114 |
<note> |
| 11115 |
To make sure everything is ok, you should run mac-fdisk once more and check |
| 11116 |
whether all the partitions are there. If you don't see any of the partitions |
| 11117 |
you created, or the changes you made, you should reinitialize your partitions |
| 11118 |
by pressing "i" in mac-fdisk. Note that this will recreate the partition map |
| 11119 |
and thus remove all your partitions. |
| 11120 |
</note> |
| 11121 |
|
| 11122 |
<p> |
| 11123 |
Now that your partitions are created, you can continue with <uri |
| 11124 |
link="#filesystems">Creating Filesystems</uri>. |
| 11125 |
</p> |
| 11126 |
|
| 11127 |
</body> |
| 11128 |
</section> |
| 11129 |
<section id="parted"> |
| 11130 |
<title>Using parted (especially Pegasos) to Partition your Disk</title> |
| 11131 |
<body> |
| 11132 |
|
| 11133 |
<p> |
| 11134 |
<c>parted</c>, the Partition Editor, can now handle HFS+ partitions used by |
| 11135 |
Mac OS and Mac OS X. With this tool you can resize your Mac-partitions and |
| 11136 |
create space for your Linux partitions. Nevertheless, the example below |
| 11137 |
describes partitioning for Pegasos machines only. |
| 11138 |
</p> |
| 11139 |
|
| 11140 |
<p> |
| 11141 |
To begin let's fire up <c>parted</c>: |
| 11142 |
</p> |
| 11143 |
|
| 11144 |
<pre caption="Starting parted"> |
| 11145 |
# <i>parted /dev/hda</i> |
| 11146 |
</pre> |
| 11147 |
|
| 11148 |
<p> |
| 11149 |
If the drive is unpartitioned, run <c>mklabel amiga</c> to create a new |
| 11150 |
disklabel for the drive. |
| 11151 |
</p> |
| 11152 |
|
| 11153 |
<p> |
| 11154 |
You can type <c>print</c> at any time in parted to display the current partition |
| 11155 |
table. If at any time you change your mind or made a mistake you can press |
| 11156 |
<c>Ctrl-c</c> to abort parted. |
| 11157 |
</p> |
| 11158 |
|
| 11159 |
<p> |
| 11160 |
If you intend to also install MorphOS on your Pegasos create an affs1 filesystem |
| 11161 |
named "BI0" (BI zero) at the start of the drive. 32MB should be more than enough |
| 11162 |
to store the MorphOS kernel. If you have a Pegasos I or intend to use reiserfs or |
| 11163 |
xfs, you will also have to store your Linux kernel on this partition (the |
| 11164 |
Pegasos II can only boot from ext2/ext3 or affs1 partitions). To create the partition run |
| 11165 |
<c>mkpart primary affs1 START END</c> where <c>START</c> and <c>END</c> should |
| 11166 |
be replaced with the megabyte range (e.g. <c>0 32</c> creates a 32 MB partition |
| 11167 |
starting at 0MB and ending at 32MB. |
| 11168 |
</p> |
| 11169 |
|
| 11170 |
<p> |
| 11171 |
You need to create two partitions for Linux, one root filesystem for all your |
| 11172 |
program files etc, and one swap partition. To create the root filesystem you |
| 11173 |
must first decide which filesystem to use. Possible options are ext2, ext3, |
| 11174 |
reiserfs and xfs. Unless you know what you are doing, use ext3. Run |
| 11175 |
<c>mkpart primary ext3 START END</c> to create an ext3 partition. Again, replace |
| 11176 |
<c>START</c> and <c>END</c> with the megabyte start and stop marks for the |
| 11177 |
partition. |
| 11178 |
</p> |
| 11179 |
|
| 11180 |
<p> |
| 11181 |
It is generally recommended that you create a swap partition the same size as |
| 11182 |
the amount of RAM in your computer times two. You will probably get away with a |
| 11183 |
smaller swap partition unless you intend to run a lot of applications at the |
| 11184 |
same time (although at least 512MB is recommended). To create the swap |
| 11185 |
partition, run <c>mkpart primary linux-swap START END</c>. |
| 11186 |
</p> |
| 11187 |
|
| 11188 |
<p> |
| 11189 |
Write down the partition minor numbers as they are required during the |
| 11190 |
installation process. To display the minor numbers run <c>print</c>. Your drives |
| 11191 |
are accessed as <path>/dev/hdaX</path> where X is replaced with the minor number |
| 11192 |
of the partition. |
| 11193 |
</p> |
| 11194 |
|
| 11195 |
<p> |
| 11196 |
When you are done in parted simply run <c>quit</c>. |
| 11197 |
</p> |
| 11198 |
|
| 11199 |
</body> |
| 11200 |
</section> |
| 11201 |
<section id="filesystems"> |
| 11202 |
<title>Creating Filesystems</title> |
| 11203 |
<subsection> |
| 11204 |
<title>Introduction</title> |
| 11205 |
<body> |
| 11206 |
|
| 11207 |
<p> |
| 11208 |
Now that your partitions are created, it is time to place a filesystem on them. |
| 11209 |
If you don't care about what filesystem to choose and are happy with what we use |
| 11210 |
as default in this handbook, continue with <uri |
| 11211 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
| 11212 |
Otherwise read on to learn about the available filesystems... |
| 11213 |
</p> |
| 11214 |
|
| 11215 |
</body> |
| 11216 |
</subsection> |
| 11217 |
<subsection> |
| 11218 |
<title>Filesystems?</title> |
| 11219 |
<body> |
| 11220 |
|
| 11221 |
<p> |
| 11222 |
Several filesystems are available. ext2, ext3, ReiserFS and XFS have been found |
| 11223 |
stable on the PPC architecture. |
| 11224 |
</p> |
| 11225 |
|
| 11226 |
<p> |
| 11227 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
| 11228 |
journaling, which means that routine ext2 filesystem checks at startup time can |
| 11229 |
be quite time-consuming. There is now quite a selection of newer-generation |
| 11230 |
journaled filesystems that can be checked for consistency very quickly and are |
| 11231 |
thus generally preferred over their non-journaled counterparts. Journaled |
| 11232 |
filesystems prevent long delays when you boot your system and your filesystem |
| 11233 |
happens to be in an inconsistent state. |
| 11234 |
</p> |
| 11235 |
|
| 11236 |
<p> |
| 11237 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
| 11238 |
journaling for fast recovery in addition to other enhanced journaling modes like |
| 11239 |
full data and ordered data journaling. ext3 is a very good and reliable |
| 11240 |
filesystem. It has an additional hashed b-tree indexing option that enables |
| 11241 |
high performance in almost all situations. You can enable this indexing by |
| 11242 |
adding <c>-O dir_index</c> to the <c>mke2fs</c> command. In short, ext3 is an |
| 11243 |
excellent filesystem. |
| 11244 |
</p> |
| 11245 |
|
| 11246 |
<p> |
| 11247 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
| 11248 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
| 11249 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
| 11250 |
extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is |
| 11251 |
solid and usable as both general-purpose filesystem and for extreme cases such |
| 11252 |
as the creation of large filesystems, the use of many small files, very large |
| 11253 |
files and directories containing tens of thousands of files. |
| 11254 |
</p> |
| 11255 |
|
| 11256 |
<p> |
| 11257 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
| 11258 |
feature-set and is optimized for scalability. We only recommend using this |
| 11259 |
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
| 11260 |
an uninterruptible power supply. Because XFS aggressively caches in-transit data |
| 11261 |
in RAM, improperly designed programs (those that don't take proper precautions |
| 11262 |
when writing files to disk and there are quite a few of them) can lose a good |
| 11263 |
deal of data if the system goes down unexpectedly. |
| 11264 |
</p> |
| 11265 |
|
| 11266 |
</body> |
| 11267 |
</subsection> |
| 11268 |
<subsection id="filesystems-apply"> |
| 11269 |
<title>Applying a Filesystem to a Partition</title> |
| 11270 |
<body> |
| 11271 |
|
| 11272 |
<p> |
| 11273 |
To create a filesystem on a partition or volume, there are tools available for |
| 11274 |
each possible filesystem: |
| 11275 |
</p> |
| 11276 |
|
| 11277 |
<table> |
| 11278 |
<tr> |
| 11279 |
<th>Filesystem</th> |
| 11280 |
<th>Creation Command</th> |
| 11281 |
</tr> |
| 11282 |
<tr> |
| 11283 |
<ti>ext2</ti> |
| 11284 |
<ti><c>mkfs.ext2</c></ti> |
| 11285 |
</tr> |
| 11286 |
<tr> |
| 11287 |
<ti>ext3</ti> |
| 11288 |
<ti><c>mkfs.ext3</c></ti> |
| 11289 |
</tr> |
| 11290 |
<tr> |
| 11291 |
<ti>reiserfs</ti> |
| 11292 |
<ti><c>mkfs.reiserfs</c></ti> |
| 11293 |
</tr> |
| 11294 |
<tr> |
| 11295 |
<ti>xfs</ti> |
| 11296 |
<ti><c>mkfs.xfs</c></ti> |
| 11297 |
</tr> |
| 11298 |
</table> |
| 11299 |
|
| 11300 |
<p> |
| 11301 |
For instance, to have the root partition (<path>/dev/hda4</path> in our example) |
| 11302 |
in ext3 (as in our example), you would use: |
| 11303 |
</p> |
| 11304 |
|
| 11305 |
<pre caption="Applying a filesystem on a partition"> |
| 11306 |
# <i>mkfs.ext3 /dev/hda4</i> |
| 11307 |
</pre> |
| 11308 |
|
| 11309 |
<p> |
| 11310 |
Now create the filesystems on your newly created partitions (or logical |
| 11311 |
volumes). |
| 11312 |
</p> |
| 11313 |
|
| 11314 |
<note> |
| 11315 |
On the PegasosII your partition which holds the kernel must be ext2 or ext3. |
| 11316 |
NewWorld machines can boot from any of ext2, ext3, XFS, ReiserFS or even |
| 11317 |
HFS/HFS+ filesystems. On OldWorld machines booting with BootX, the kernel must |
| 11318 |
be placed on an HFS partition, but this will be completed when you configure |
| 11319 |
your bootloader. |
| 11320 |
</note> |
| 11321 |
|
| 11322 |
</body> |
| 11323 |
</subsection> |
| 11324 |
<subsection> |
| 11325 |
<title>Activating the Swap Partition</title> |
| 11326 |
<body> |
| 11327 |
|
| 11328 |
<p> |
| 11329 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
| 11330 |
</p> |
| 11331 |
|
| 11332 |
<pre caption="Creating a Swap signature"> |
| 11333 |
# <i>mkswap /dev/hda3</i> |
| 11334 |
</pre> |
| 11335 |
|
| 11336 |
<p> |
| 11337 |
To activate the swap partition, use <c>swapon</c>: |
| 11338 |
</p> |
| 11339 |
|
| 11340 |
<pre caption="Activating the swap partition"> |
| 11341 |
# <i>swapon /dev/hda3</i> |
| 11342 |
</pre> |
| 11343 |
|
| 11344 |
<p> |
| 11345 |
Create and activate the swap now. |
| 11346 |
</p> |
| 11347 |
|
| 11348 |
</body> |
| 11349 |
</subsection> |
| 11350 |
</section> |
| 11351 |
<section> |
| 11352 |
<title>Mounting</title> |
| 11353 |
<body> |
| 11354 |
|
| 11355 |
<p> |
| 11356 |
Now that your partitions are initialized and are housing a filesystem, it is |
| 11357 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
| 11358 |
create the necessary mount directories for every partition you created. As an |
| 11359 |
example we create a mount-point and mount the root partition: |
| 11360 |
</p> |
| 11361 |
|
| 11362 |
<pre caption="Mounting partitions"> |
| 11363 |
# <i>mkdir /mnt/gentoo</i> |
| 11364 |
# <i>mount /dev/hda4 /mnt/gentoo</i> |
| 11365 |
</pre> |
| 11366 |
|
| 11367 |
<note> |
| 11368 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
| 11369 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
| 11370 |
also holds for <path>/var/tmp</path>. |
| 11371 |
</note> |
| 11372 |
|
| 11373 |
|
| 11374 |
<p> |
| 11375 |
We will have to mount the proc filesystem (a virtual interface with the |
| 11376 |
kernel) on <path>/proc</path>. But first we will need to place our files on the |
| 11377 |
partitions. |
| 11378 |
</p> |
| 11379 |
|
| 11380 |
<p> |
| 11381 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
| 11382 |
Installation Files</uri>. |
| 11383 |
</p> |
| 11384 |
|
| 11385 |
</body> |
| 11386 |
</section> |
| 11387 |
</sections> |
| 11388 |
|
| 11389 |
|
| 11390 |
|
| 11391 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc-kernel.xml |
| 11392 |
|
| 11393 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 11394 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 11395 |
|
| 11396 |
Index: hb-install-ppc-kernel.xml |
| 11397 |
=================================================================== |
| 11398 |
<?xml version='1.0' encoding='UTF-8'?> |
| 11399 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 11400 |
|
| 11401 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 11402 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 11403 |
|
| 11404 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc-kernel.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 11405 |
|
| 11406 |
<sections> |
| 11407 |
|
| 11408 |
<version>5.4</version> |
| 11409 |
<date>2006-01-06</date> |
| 11410 |
|
| 11411 |
<section> |
| 11412 |
<title>Timezone</title> |
| 11413 |
<body> |
| 11414 |
|
| 11415 |
<p> |
| 11416 |
You first need to select your timezone so that your system knows where it is |
| 11417 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
| 11418 |
it to <path>/etc/localtime</path>. Please avoid the |
| 11419 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
| 11420 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
| 11421 |
</p> |
| 11422 |
|
| 11423 |
<pre caption="Setting the timezone information"> |
| 11424 |
# <i>ls /usr/share/zoneinfo</i> |
| 11425 |
<comment>(Suppose you want to use GMT)</comment> |
| 11426 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
| 11427 |
</pre> |
| 11428 |
|
| 11429 |
</body> |
| 11430 |
</section> |
| 11431 |
<section> |
| 11432 |
<title>Installing the Sources</title> |
| 11433 |
<subsection> |
| 11434 |
<title>Choosing a Kernel</title> |
| 11435 |
<body> |
| 11436 |
|
| 11437 |
<p> |
| 11438 |
The core around which all distributions are built is the Linux kernel. It is the |
| 11439 |
layer between the user programs and your system hardware. Gentoo provides its |
| 11440 |
users several possible kernel sources. A full listing with description is |
| 11441 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
| 11442 |
Guide</uri>. |
| 11443 |
</p> |
| 11444 |
|
| 11445 |
<p> |
| 11446 |
We suggest using either <c>vanilla-sources</c> or <c>gentoo-sources</c> on PPC, |
| 11447 |
which are both 2.6 kernels. The latter is available when you perform a |
| 11448 |
networkless installation. So let's continue with <c>emerge</c>'ing the kernel |
| 11449 |
sources. The <c>USE="-doc"</c> is necessary to avoid installing xorg-x11 or |
| 11450 |
other dependencies at this point. <c>USE="symlink"</c> is not necessary for a |
| 11451 |
new install, but ensures proper creation of the <path>/usr/src/linux</path> |
| 11452 |
symlink. |
| 11453 |
</p> |
| 11454 |
|
| 11455 |
<pre caption="Installing a kernel source"> |
| 11456 |
# <i>USE="-doc symlink" emerge gentoo-sources</i> |
| 11457 |
</pre> |
| 11458 |
|
| 11459 |
<p> |
| 11460 |
If you take a look in <path>/usr/src</path> you should see a symlink named |
| 11461 |
<path>linux</path> pointing to your current kernel source. In this case, the |
| 11462 |
installed kernel source points to <c>gentoo-sources-2.6.12-r6</c>. Your version |
| 11463 |
may be different, so keep this in mind. |
| 11464 |
</p> |
| 11465 |
|
| 11466 |
<pre caption="Viewing the kernel source symlink"> |
| 11467 |
# <i>ls -l /usr/src/linux</i> |
| 11468 |
lrwxrwxrwx 1 root root 22 Mar 18 16:23 /usr/src/linux -> linux-2.6.12-gentoo-r6 |
| 11469 |
</pre> |
| 11470 |
|
| 11471 |
<p> |
| 11472 |
Now it is time to configure and compile your kernel source. You |
| 11473 |
can use <c>genkernel</c> for this, which will build a generic kernel as used |
| 11474 |
by the Installation CD. We explain the "manual" configuration first though, as |
| 11475 |
it is the best way to optimize your environment. |
| 11476 |
</p> |
| 11477 |
|
| 11478 |
<p> |
| 11479 |
If you want to manually configure your kernel, continue now with <uri |
| 11480 |
link="#manual">Default: Manual Configuration</uri>. If you want to use |
| 11481 |
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
| 11482 |
genkernel</uri> instead. |
| 11483 |
</p> |
| 11484 |
|
| 11485 |
</body> |
| 11486 |
</subsection> |
| 11487 |
</section> |
| 11488 |
<section id="manual"> |
| 11489 |
<title>Default: Manual Configuration</title> |
| 11490 |
<subsection> |
| 11491 |
<title>Introduction</title> |
| 11492 |
<body> |
| 11493 |
|
| 11494 |
<p> |
| 11495 |
Manually configuring a kernel is often seen as the most difficult procedure a |
| 11496 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
| 11497 |
couple of kernels you don't even remember that it was difficult ;) |
| 11498 |
</p> |
| 11499 |
|
| 11500 |
<p> |
| 11501 |
However, one thing <e>is</e> true: you must know your system when you start |
| 11502 |
configuring a kernel manually. Most information can be gathered by emerging |
| 11503 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
| 11504 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
| 11505 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
| 11506 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
| 11507 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
| 11508 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
| 11509 |
uses (it might provide you with a nice hint on what to enable). Another place |
| 11510 |
to look for clues as to what components to enable is to check the kernel |
| 11511 |
message logs from the successful boot that got you this far. Type <c>dmesg</c> |
| 11512 |
to see the kernel messages. |
| 11513 |
</p> |
| 11514 |
|
| 11515 |
<p> |
| 11516 |
Now, go to your kernel source directory, it's time to configure your kernel. |
| 11517 |
It is recommended that you add the default settings to your configuration by |
| 11518 |
first running <c>make defconfig</c>. After the default configuration has been |
| 11519 |
generated, run <c>make menuconfig</c> which will fire up an ncurses-based |
| 11520 |
configuration menu. |
| 11521 |
</p> |
| 11522 |
|
| 11523 |
<pre caption="Invoking menuconfig"> |
| 11524 |
# <i>cd /usr/src/linux</i> |
| 11525 |
# <i>make defconfig</i> |
| 11526 |
# <i>make menuconfig</i> |
| 11527 |
</pre> |
| 11528 |
|
| 11529 |
<p> |
| 11530 |
You will be greeted with several configuration sections. We'll first list some |
| 11531 |
options you must activate (otherwise Gentoo will not function, or not function |
| 11532 |
properly without additional tweaks). |
| 11533 |
</p> |
| 11534 |
|
| 11535 |
</body> |
| 11536 |
</subsection> |
| 11537 |
<subsection> |
| 11538 |
<title>Activating Required Options</title> |
| 11539 |
<body> |
| 11540 |
|
| 11541 |
<p> |
| 11542 |
First of all, activate the use of development and experimental code/drivers. |
| 11543 |
You need this, otherwise some very important code/drivers won't show up: |
| 11544 |
</p> |
| 11545 |
|
| 11546 |
<pre caption="Selecting experimental code/drivers, General setup"> |
| 11547 |
Code maturity level options ---> |
| 11548 |
[*] Prompt for development and/or incomplete code/drivers |
| 11549 |
General setup ---> |
| 11550 |
[*] Support for hot-pluggable devices |
| 11551 |
</pre> |
| 11552 |
|
| 11553 |
<p> |
| 11554 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
| 11555 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
| 11556 |
able to mount your partitions. Also select <c>/proc file system</c> and |
| 11557 |
<c>Virtual memory</c>. |
| 11558 |
</p> |
| 11559 |
|
| 11560 |
<pre caption="Selecting necessary file systems"> |
| 11561 |
File systems ---> |
| 11562 |
Pseudo Filesystems ---> |
| 11563 |
[*] /proc file system support |
| 11564 |
[*] Virtual memory file system support (former shm fs) |
| 11565 |
|
| 11566 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
| 11567 |
<*> Reiserfs support |
| 11568 |
<*> Ext3 journalling file system support |
| 11569 |
<*> Second extended fs support |
| 11570 |
<*> XFS filesystem support |
| 11571 |
</pre> |
| 11572 |
|
| 11573 |
<p> |
| 11574 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
| 11575 |
modem, you will need the following options in the kernel: |
| 11576 |
</p> |
| 11577 |
|
| 11578 |
<pre caption="Selecting PPPoE necessary drivers"> |
| 11579 |
Device Drivers ---> |
| 11580 |
Networking support ---> |
| 11581 |
<*> PPP (point-to-point protocol) support |
| 11582 |
<*> PPP support for async serial ports |
| 11583 |
<*> PPP support for sync tty ports |
| 11584 |
</pre> |
| 11585 |
|
| 11586 |
<p> |
| 11587 |
The two compression options won't harm but are not definitely needed, neither |
| 11588 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
| 11589 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
| 11590 |
</p> |
| 11591 |
|
| 11592 |
<p> |
| 11593 |
If you require it, don't forget to include support in the kernel for your |
| 11594 |
ethernet card. |
| 11595 |
</p> |
| 11596 |
|
| 11597 |
<p> |
| 11598 |
Users of NewWorld and OldWorld machines will want HFS support as well. OldWorld |
| 11599 |
users require it for copying compiled kernels to the MacOS partition. NewWorld |
| 11600 |
users require it for configuring the special Apple_Bootstrap partition: |
| 11601 |
</p> |
| 11602 |
|
| 11603 |
<pre caption="Activating HFS support"> |
| 11604 |
File Systems ---> |
| 11605 |
[*] HFS Support |
| 11606 |
</pre> |
| 11607 |
|
| 11608 |
<p> |
| 11609 |
At this time, kernel preemption is still unstable on PPC and may cause |
| 11610 |
compilation failures and random segfaults. It is <e>strongly</e> suggested |
| 11611 |
that you do not use this feature. |
| 11612 |
</p> |
| 11613 |
|
| 11614 |
<pre caption="Ensure the Preemptible Kernel Option is Off"> |
| 11615 |
Platform options ---> |
| 11616 |
[ ] Preemptible Kernel |
| 11617 |
</pre> |
| 11618 |
|
| 11619 |
<p> |
| 11620 |
If you're booting from Firewire, you'll need to enable these options. If you do |
| 11621 |
not want to compile in support, you'll need to include these modules and their |
| 11622 |
dependencies in an initrd. |
| 11623 |
</p> |
| 11624 |
|
| 11625 |
<pre caption="Enable support for firewire devices on boot"> |
| 11626 |
Device Drivers ---> |
| 11627 |
IEEE 1394 (FireWire) support ---> |
| 11628 |
<*> IEEE 1394 (FireWire) support |
| 11629 |
<*> OHCI-1394 support |
| 11630 |
<*> SBP-2 support (Harddisks etc.) |
| 11631 |
</pre> |
| 11632 |
|
| 11633 |
<p> |
| 11634 |
If you're booting from USB, you'll need to enable these options. If you do not |
| 11635 |
want to compile in support, you'll need to include these modules and their |
| 11636 |
dependencies in an initrd. |
| 11637 |
</p> |
| 11638 |
|
| 11639 |
<pre caption="Enable support for USB devices on boot"> |
| 11640 |
Device Drivers ---> |
| 11641 |
USB support ---> |
| 11642 |
<*> Support for Host-side USB |
| 11643 |
<*> OHCI HCD support |
| 11644 |
<*> USB Mass Storage support |
| 11645 |
</pre> |
| 11646 |
|
| 11647 |
<p> |
| 11648 |
Do not turn off kernel framebuffer support as it is required for a successful |
| 11649 |
boot. If you are using an NVIDIA based chipset, you should use the OpenFirmware |
| 11650 |
framebuffer. If you are using an ATI based chipset, you should select the |
| 11651 |
framebuffer driver based upon your chipset (Mach64, Rage128 or Radeon). |
| 11652 |
</p> |
| 11653 |
|
| 11654 |
<pre caption="Chosing a Framebuffer Driver"> |
| 11655 |
Device Drivers ---> |
| 11656 |
Graphics support ---> |
| 11657 |
<*> Support for frame buffer devices |
| 11658 |
[*] Open Firmware frame buffer device support |
| 11659 |
<*> ATI Radeon display support |
| 11660 |
<*> ATI Rage128 display support |
| 11661 |
<*> ATI Mach64 display support |
| 11662 |
Console display driver support ---> |
| 11663 |
<*> Framebuffer Console support |
| 11664 |
</pre> |
| 11665 |
|
| 11666 |
<note> |
| 11667 |
If you select more than one framebuffer device, it may default to a less than |
| 11668 |
optimal driver. Either use only one framebuffer device or specify which |
| 11669 |
to use by passing the driver to use to the kernel on boot such as |
| 11670 |
<c>video=radeonfb</c>. |
| 11671 |
</note> |
| 11672 |
|
| 11673 |
<p> |
| 11674 |
When you're done configuring your kernel, continue with <uri |
| 11675 |
link="#compiling">Compiling and Installing</uri>. |
| 11676 |
</p> |
| 11677 |
|
| 11678 |
</body> |
| 11679 |
</subsection> |
| 11680 |
<subsection id="compiling"> |
| 11681 |
<title>Compiling and Installing</title> |
| 11682 |
<body> |
| 11683 |
|
| 11684 |
<p> |
| 11685 |
Now that your kernel is configured, it is time to compile and install it. Exit |
| 11686 |
the configuration and run the commands which will compile the kernel: |
| 11687 |
</p> |
| 11688 |
|
| 11689 |
<pre caption="Compiling the kernel"> |
| 11690 |
# <i>make && make modules_install</i> |
| 11691 |
</pre> |
| 11692 |
|
| 11693 |
<p> |
| 11694 |
When the kernel has finished compiling, copy the kernel image to |
| 11695 |
<path>/boot</path> (be sure that it is mounted properly on the Pegasos). |
| 11696 |
</p> |
| 11697 |
|
| 11698 |
<pre caption="Installing the kernel"> |
| 11699 |
<comment>replace <kernel-version> with your kernel version</comment> |
| 11700 |
(Apple/IBM) # <i>cp vmlinux /boot/<kernel-version></i> |
| 11701 |
(Pegasos) # <i>cp arch/ppc/boot/images/zImage.chrp /boot/<kernel-version></i> |
| 11702 |
</pre> |
| 11703 |
|
| 11704 |
<p> |
| 11705 |
Now continue with <uri link="#kernel_modules">Installing Separate Kernel |
| 11706 |
Modules</uri>. |
| 11707 |
</p> |
| 11708 |
|
| 11709 |
</body> |
| 11710 |
</subsection> |
| 11711 |
</section> |
| 11712 |
<section id="kernel_modules"> |
| 11713 |
<title>Installing Separate Kernel Modules</title> |
| 11714 |
<subsection> |
| 11715 |
<title>Configuring the Modules</title> |
| 11716 |
<body> |
| 11717 |
|
| 11718 |
<p> |
| 11719 |
You should list the modules you want automatically loaded in |
| 11720 |
<path>/etc/modules.autoload.d/kernel-2.6</path>. |
| 11721 |
You can add extra options to the modules too if you want. |
| 11722 |
</p> |
| 11723 |
|
| 11724 |
<p> |
| 11725 |
To view all available modules, run the following <c>find</c> command. Don't |
| 11726 |
forget to substitute "<kernel version>" with the version of the kernel you |
| 11727 |
just compiled: |
| 11728 |
</p> |
| 11729 |
|
| 11730 |
<pre caption="Viewing all available modules"> |
| 11731 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
| 11732 |
</pre> |
| 11733 |
|
| 11734 |
<p> |
| 11735 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
| 11736 |
<path>kernel-2.6</path> file and enter the module |
| 11737 |
name in it. |
| 11738 |
</p> |
| 11739 |
|
| 11740 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
| 11741 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
| 11742 |
</pre> |
| 11743 |
|
| 11744 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
| 11745 |
3c59x |
| 11746 |
</pre> |
| 11747 |
|
| 11748 |
<p> |
| 11749 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
| 11750 |
your System</uri>. |
| 11751 |
</p> |
| 11752 |
|
| 11753 |
</body> |
| 11754 |
</subsection> |
| 11755 |
</section> |
| 11756 |
<section id="genkernel"> |
| 11757 |
<title>Alternative: Using genkernel</title> |
| 11758 |
<body> |
| 11759 |
|
| 11760 |
<p> |
| 11761 |
If you are reading this section, you have chosen to use our <c>genkernel</c> |
| 11762 |
script to configure your kernel for you. |
| 11763 |
</p> |
| 11764 |
|
| 11765 |
<p> |
| 11766 |
Now that your kernel source tree is installed, it's now time to compile your |
| 11767 |
kernel by using our <c>genkernel</c> script to automatically build a kernel for |
| 11768 |
you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
| 11769 |
way our Installation CD kernel is configured. This means that when you use |
| 11770 |
<c>genkernel</c> to build your kernel, your system will generally detect all |
| 11771 |
your hardware at boot-time, just like our Installation CD does. Because genkernel |
| 11772 |
doesn't require any manual kernel configuration, it is an ideal solution for |
| 11773 |
those users who may not be comfortable compiling their own kernels. |
| 11774 |
</p> |
| 11775 |
|
| 11776 |
<p> |
| 11777 |
Now, let's see how to use genkernel. First, emerge the genkernel ebuild: |
| 11778 |
</p> |
| 11779 |
|
| 11780 |
<pre caption="Emerging genkernel"> |
| 11781 |
# <i>emerge genkernel</i> |
| 11782 |
</pre> |
| 11783 |
|
| 11784 |
<p> |
| 11785 |
Next, copy over the kernel configuration used by the Installation CD to the |
| 11786 |
location where genkernel looks for the default kernel configuration: |
| 11787 |
</p> |
| 11788 |
|
| 11789 |
<pre caption="Copying over the Installation CD kernel config"> |
| 11790 |
# <i>zcat /proc/config.gz > /usr/share/genkernel/ppc/kernel-config-2.6</i> |
| 11791 |
</pre> |
| 11792 |
|
| 11793 |
<p> |
| 11794 |
If you are using firewire or USB to boot, you'll need to add modules to the |
| 11795 |
initrd. Edit <path>/usr/share/genkernel/ppc/modules_load</path> and change |
| 11796 |
<c>MODULES_FIREWIRE="ieee1394 ohci1394 sbp2"</c> for firewire support or |
| 11797 |
<c>MODULES_USB="usbcore ohci-hcd ehci-hcd usb-storage"</c> for USB support. |
| 11798 |
</p> |
| 11799 |
|
| 11800 |
|
| 11801 |
<p> |
| 11802 |
Now, compile your kernel sources by running <c>genkernel --genzimage all</c>. |
| 11803 |
For Pegasos, we will need to use a different config and create a zImage instead |
| 11804 |
of the vmlinux kernel used on Apple machines. Be aware, as <c>genkernel</c> |
| 11805 |
compiles a kernel that supports almost all hardware, this compilation can take |
| 11806 |
quite a while to finish! |
| 11807 |
</p> |
| 11808 |
|
| 11809 |
<p> |
| 11810 |
Note that, if your partition where the kernel should be located doesn't use ext2 |
| 11811 |
or ext3 as filesystem you might need to manually configure your kernel using |
| 11812 |
<c>genkernel --menuconfig --genzimage all</c> and add support for your |
| 11813 |
filesystem <e>in</e> the kernel (i.e. <e>not</e> as a module). Users of EVMS2 or |
| 11814 |
LVM2 will probably want to add <c>--evms2</c> or <c>--lvm2</c> as argument as |
| 11815 |
well. |
| 11816 |
</p> |
| 11817 |
|
| 11818 |
<pre caption="Running genkernel"> |
| 11819 |
# <i>genkernel --genzimage all</i> |
| 11820 |
</pre> |
| 11821 |
|
| 11822 |
<pre caption="Running genkernel on the Pegasos"> |
| 11823 |
# <i>genkernel --genzimage --kernel-config=/usr/share/genkernel/ppc/Pegasos all</i> |
| 11824 |
</pre> |
| 11825 |
|
| 11826 |
<p> |
| 11827 |
Once <c>genkernel</c> completes, a kernel, full set of modules and |
| 11828 |
<e>initial root disk</e> (initrd) will be created. We will use the kernel |
| 11829 |
and initrd when configuring a boot loader later in this document. Write |
| 11830 |
down the names of the kernel and initrd as you will need it when writing |
| 11831 |
the bootloader configuration file. The initrd will be started immediately after |
| 11832 |
booting to perform hardware autodetection (just like on the Installation CD) |
| 11833 |
before your "real" system starts up. Be sure to also copy down the required |
| 11834 |
boot arguments, these are required for a sucessful boot with genkernel. |
| 11835 |
</p> |
| 11836 |
|
| 11837 |
<pre caption="Checking the created kernel image name and initrd"> |
| 11838 |
# <i>ls /boot/kernel* /boot/initramfs*</i> |
| 11839 |
</pre> |
| 11840 |
|
| 11841 |
<p> |
| 11842 |
If you want your system to be more like the Installation CD you should, |
| 11843 |
when your Gentoo installation is over, emerge <c>coldplug</c>. While the |
| 11844 |
initrd autodetects hardware that is needed to boot your system, |
| 11845 |
<c>coldplug</c> autodetects everything else. <c>coldplug</c> is available as one |
| 11846 |
of the packages on the Package CD. |
| 11847 |
</p> |
| 11848 |
|
| 11849 |
<pre caption="Emerging and enabling coldplug"> |
| 11850 |
<comment>(Do this after the installation, during the GRP installation instructions)</comment> |
| 11851 |
# <i>emerge -k coldplug</i> |
| 11852 |
# <i>rc-update add coldplug boot</i> |
| 11853 |
</pre> |
| 11854 |
|
| 11855 |
<p> |
| 11856 |
If you want your system to react to hotplugging events, you will need to install |
| 11857 |
and setup <c>hotplug</c> as well: |
| 11858 |
</p> |
| 11859 |
|
| 11860 |
<pre caption="Emerging and enabling hotplug"> |
| 11861 |
# <i>emerge hotplug</i> |
| 11862 |
# <i>rc-update add hotplug default</i> |
| 11863 |
</pre> |
| 11864 |
|
| 11865 |
<p> |
| 11866 |
Now continue with <uri link="?part=1&chap=8">Configuring your System</uri>. |
| 11867 |
</p> |
| 11868 |
|
| 11869 |
</body> |
| 11870 |
</section> |
| 11871 |
|
| 11872 |
</sections> |
| 11873 |
|
| 11874 |
|
| 11875 |
|
| 11876 |
|
| 11877 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc-medium.xml |
| 11878 |
|
| 11879 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 11880 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 11881 |
|
| 11882 |
Index: hb-install-ppc-medium.xml |
| 11883 |
=================================================================== |
| 11884 |
<?xml version='1.0' encoding='UTF-8'?> |
| 11885 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 11886 |
|
| 11887 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 11888 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 11889 |
|
| 11890 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc-medium.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 11891 |
|
| 11892 |
<sections> |
| 11893 |
|
| 11894 |
<version>5.3</version> |
| 11895 |
<date>2005-11-29</date> |
| 11896 |
|
| 11897 |
<section> |
| 11898 |
<title>Hardware Requirements</title> |
| 11899 |
<subsection> |
| 11900 |
<title>Introduction</title> |
| 11901 |
<body> |
| 11902 |
|
| 11903 |
<p> |
| 11904 |
Before we start, we first list what hardware requirements you need to |
| 11905 |
successfully install Gentoo on your box. |
| 11906 |
</p> |
| 11907 |
|
| 11908 |
</body> |
| 11909 |
</subsection> |
| 11910 |
<subsection> |
| 11911 |
<title>Hardware Requirements</title> |
| 11912 |
<body> |
| 11913 |
|
| 11914 |
<table> |
| 11915 |
<tr> |
| 11916 |
<th>Apple NewWorld Machines</th> |
| 11917 |
<ti> |
| 11918 |
Power/PowerPC microprocessors (G3, G4, G5) such as iMac, eMac, iBook |
| 11919 |
PowerBook, Xserver, PowerMac |
| 11920 |
</ti> |
| 11921 |
</tr> |
| 11922 |
<tr> |
| 11923 |
<th>Apple OldWorld machines</th> |
| 11924 |
<ti> |
| 11925 |
Apple Machines with an OpenFirmware revision less than 3, such as the Beige |
| 11926 |
G3s, PCI PowerMacs and PCI PowerBooks. PCI based Apple Clones should also |
| 11927 |
be supported. |
| 11928 |
</ti> |
| 11929 |
</tr> |
| 11930 |
<tr> |
| 11931 |
<th>Genesi's Pegasos</th> |
| 11932 |
<ti> |
| 11933 |
Pegasos I/II, Open Desktop Workstation |
| 11934 |
</ti> |
| 11935 |
</tr> |
| 11936 |
<tr> |
| 11937 |
<th>IBM</th> |
| 11938 |
<ti> |
| 11939 |
RS/6000, iSeries, pSeries |
| 11940 |
</ti> |
| 11941 |
</tr> |
| 11942 |
<tr> |
| 11943 |
<th>Memory</th> |
| 11944 |
<ti>At least 64 MB</ti> |
| 11945 |
</tr> |
| 11946 |
<tr> |
| 11947 |
<th>Diskspace</th> |
| 11948 |
<ti>1.5 GB (excluding swap space)</ti> |
| 11949 |
</tr> |
| 11950 |
<tr> |
| 11951 |
<th>Swap space</th> |
| 11952 |
<ti>At least 256 MB</ti> |
| 11953 |
</tr> |
| 11954 |
</table> |
| 11955 |
|
| 11956 |
<p> |
| 11957 |
Be sure to read up on the <uri link="/doc/en/gentoo-ppc-faq.xml">Gentoo |
| 11958 |
PPC FAQ</uri> before you begin. |
| 11959 |
</p> |
| 11960 |
|
| 11961 |
</body> |
| 11962 |
</subsection> |
| 11963 |
</section> |
| 11964 |
<!-- Copy/paste of hb-install-x86-medium.xml, with s/x86/ppc/ --> |
| 11965 |
<!-- START --> |
| 11966 |
<section> |
| 11967 |
<title>The Gentoo Universal Installation CD</title> |
| 11968 |
<subsection> |
| 11969 |
<title>Introduction</title> |
| 11970 |
<body> |
| 11971 |
|
| 11972 |
<p> |
| 11973 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
| 11974 |
Such a tarball is an archive that contains a minimal environment from |
| 11975 |
which you can succesfully install Gentoo Linux onto your system. |
| 11976 |
</p> |
| 11977 |
|
| 11978 |
<p> |
| 11979 |
Installations using a stage1 or stage2 tarball file are not documented in the |
| 11980 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
| 11981 |
FAQ</uri> on these matters. |
| 11982 |
</p> |
| 11983 |
|
| 11984 |
</body> |
| 11985 |
</subsection> |
| 11986 |
<subsection> |
| 11987 |
<title>Gentoo Universal Installation CD</title> |
| 11988 |
<body> |
| 11989 |
|
| 11990 |
<p> |
| 11991 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
| 11992 |
environment. It allows you to boot Linux from the CD. During the boot process |
| 11993 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
| 11994 |
Installation CDs are maintained by Gentoo developers. |
| 11995 |
</p> |
| 11996 |
|
| 11997 |
<p> |
| 11998 |
There currently are two Installation CDs available: |
| 11999 |
</p> |
| 12000 |
|
| 12001 |
<ul> |
| 12002 |
<li> |
| 12003 |
The Universal Installation CD contains everything you need to install |
| 12004 |
Gentoo. It provides stage3 files for common architectures, source code |
| 12005 |
for the extra applications you need to choose from and, of course, the |
| 12006 |
installation instructions for your architecture. |
| 12007 |
</li> |
| 12008 |
<li> |
| 12009 |
The Minimal Installation CD contains only a minimal environment that allows |
| 12010 |
you to boot up and configure your network so you can connect to the |
| 12011 |
Internet. It does not contain any additional files and cannot be used |
| 12012 |
during the current installation approach. |
| 12013 |
</li> |
| 12014 |
</ul> |
| 12015 |
|
| 12016 |
<p> |
| 12017 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
| 12018 |
additional resource that you can exploit during the installation of your Gentoo |
| 12019 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
| 12020 |
you to easily and quickly install additional applications (such as |
| 12021 |
OpenOffice.org, KDE, GNOME, ...) immediately after the Gentoo installation and |
| 12022 |
right before you update your Portage tree. |
| 12023 |
</p> |
| 12024 |
|
| 12025 |
<p> |
| 12026 |
The use of the Package CD is covered later in this document. |
| 12027 |
</p> |
| 12028 |
|
| 12029 |
</body> |
| 12030 |
</subsection> |
| 12031 |
</section> |
| 12032 |
<!-- STOP --> |
| 12033 |
<section> |
| 12034 |
<title>Download, Burn and Boot the Gentoo Universal Installation CD</title> |
| 12035 |
<subsection> |
| 12036 |
<title>Downloading and Burning the Installation CD</title> |
| 12037 |
<body> |
| 12038 |
|
| 12039 |
<p> |
| 12040 |
You can download the Universal Installation CD (and, if you want to, the |
| 12041 |
Packages CD as well) from one of our <uri |
| 12042 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located |
| 12043 |
in the <path>releases/ppc/2006.0/installcd</path> directory; |
| 12044 |
the Package CDs are located in the |
| 12045 |
<path>releases/ppc/2006.0/packagecd</path> directory. |
| 12046 |
</p> |
| 12047 |
|
| 12048 |
<p> |
| 12049 |
Inside those directories you'll find ISO-files. Those are full CD images which |
| 12050 |
you can write on a CD-R. |
| 12051 |
</p> |
| 12052 |
|
| 12053 |
<p> |
| 12054 |
After downloading the file, you can verify its integrity to see if it is |
| 12055 |
corrupted or not: |
| 12056 |
</p> |
| 12057 |
|
| 12058 |
<ul> |
| 12059 |
<li> |
| 12060 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
| 12061 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
| 12062 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows). |
| 12063 |
Verifying MD5 checksums with Mac OS X is described in the <uri |
| 12064 |
link="/doc/en/gentoo-ppc-faq.xml#doc_chap1">Gentoo PPC FAQ</uri>. |
| 12065 |
</li> |
| 12066 |
<li> |
| 12067 |
You can verify the cryptographic signature that we provide. You need to |
| 12068 |
obtain the public key we use (0x17072058) before you proceed though. |
| 12069 |
</li> |
| 12070 |
</ul> |
| 12071 |
|
| 12072 |
<p> |
| 12073 |
To fetch our public key using the GnuPG application, run the following command: |
| 12074 |
</p> |
| 12075 |
|
| 12076 |
<pre caption="Obtaining the public key"> |
| 12077 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 0x17072058</i> |
| 12078 |
</pre> |
| 12079 |
|
| 12080 |
<p> |
| 12081 |
Now verify the signature: |
| 12082 |
</p> |
| 12083 |
|
| 12084 |
<pre caption="Verify the cryptographic signature"> |
| 12085 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
| 12086 |
</pre> |
| 12087 |
|
| 12088 |
<p> |
| 12089 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
| 12090 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
| 12091 |
<c>K3B</c> here; more information can be found in our <uri |
| 12092 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
| 12093 |
</p> |
| 12094 |
|
| 12095 |
<ul> |
| 12096 |
<li> |
| 12097 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
| 12098 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
| 12099 |
path). |
| 12100 |
</li> |
| 12101 |
<li> |
| 12102 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
| 12103 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
| 12104 |
<c>Start</c>. |
| 12105 |
</li> |
| 12106 |
</ul> |
| 12107 |
|
| 12108 |
</body> |
| 12109 |
</subsection> |
| 12110 |
<subsection> |
| 12111 |
<title>Default: Booting the Installation CD with Yaboot</title> |
| 12112 |
<body> |
| 12113 |
|
| 12114 |
<p> |
| 12115 |
On NewWorld machines place the Installation CD in the CD-ROM and reboot the |
| 12116 |
system. When the system-start-bell sounds, simply hold down the 'C' until the |
| 12117 |
CD loads. |
| 12118 |
</p> |
| 12119 |
|
| 12120 |
<p> |
| 12121 |
After the Installation CD loaded, you will be greeted by a friendly welcome |
| 12122 |
message and a <e>boot:</e> prompt at the bottom of the screen. |
| 12123 |
</p> |
| 12124 |
|
| 12125 |
<p> |
| 12126 |
At this prompt you are able to select a kernel for the subarchitecture you use. |
| 12127 |
We provide <c>G3</c>, <c>G4</c> and <c>G5</c>. All kernels are built with |
| 12128 |
support for multiple CPUs, but they will boot on single processor machines as |
| 12129 |
well. |
| 12130 |
</p> |
| 12131 |
|
| 12132 |
<p> |
| 12133 |
You are also able to tweak some kernel options at this prompt. The following |
| 12134 |
table lists some of the available boot options you can add: |
| 12135 |
</p> |
| 12136 |
|
| 12137 |
<table> |
| 12138 |
<tr> |
| 12139 |
<th>Boot Option</th> |
| 12140 |
<th>Description</th> |
| 12141 |
</tr> |
| 12142 |
<tr> |
| 12143 |
<ti><c>video</c></ti> |
| 12144 |
<ti> |
| 12145 |
This option takes one of the following vendor-specific tags: |
| 12146 |
<c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, <c>aty128</c> or |
| 12147 |
<c>ofonly</c>. You can follow this tag with the resolution and refreshrate |
| 12148 |
you want to use. For instance <c>video=radeonfb:1280x1024@75</c>. If you are |
| 12149 |
uncertain what to choose, <c>ofonly</c> will most certainly work. |
| 12150 |
</ti> |
| 12151 |
</tr> |
| 12152 |
<tr> |
| 12153 |
<ti><c>nol3</c></ti> |
| 12154 |
<ti> |
| 12155 |
Disables level 3 cache on some PowerBooks (needed for at least the 17") |
| 12156 |
</ti> |
| 12157 |
</tr> |
| 12158 |
<tr> |
| 12159 |
<ti><c>dofirewire</c></ti> |
| 12160 |
<ti> |
| 12161 |
Enables support for IEEE1394 (FireWire) devices, like external harddisks. |
| 12162 |
</ti> |
| 12163 |
</tr> |
| 12164 |
<tr> |
| 12165 |
<ti><c>dopcmcia</c></ti> |
| 12166 |
<ti> |
| 12167 |
If you want to use PCMCIA devices during your installation (like PCMCIA |
| 12168 |
network cards) you have to enable this option. |
| 12169 |
</ti> |
| 12170 |
</tr> |
| 12171 |
</table> |
| 12172 |
|
| 12173 |
<p> |
| 12174 |
At this prompt, hit enter, and a complete Gentoo Linux environment will be |
| 12175 |
loaded from the CD. Continue with <uri link="#booted">And When You're |
| 12176 |
Booted...</uri>. |
| 12177 |
</p> |
| 12178 |
|
| 12179 |
</body> |
| 12180 |
</subsection> |
| 12181 |
<subsection> |
| 12182 |
<title>Alternative: Booting the Installation CD on a Pegasos</title> |
| 12183 |
<body> |
| 12184 |
|
| 12185 |
<p> |
| 12186 |
On the Pegasos simply insert the CD and at the SmartFirmware boot-prompt type |
| 12187 |
<c>boot cd /boot/menu</c>. This will open a small bootmenu where you can choose |
| 12188 |
between several preconfigured video configs. If you need any special boot |
| 12189 |
options you can append them to the command-line. For instance <c>boot cd |
| 12190 |
/boot/pegasos video=radeonfb:1280x1024@75 mem=256M</c>. The complete list of |
| 12191 |
kernel appends (in case something goes wrong and you need it) is preconfigured |
| 12192 |
in the kernel with <c>console=ttyS0,115200 console=tty0 init=/linuxrc |
| 12193 |
looptype=squashfs loop=/livecd.squashfs udev nodevfs cdroot root=/dev/ram0</c>. |
| 12194 |
</p> |
| 12195 |
|
| 12196 |
</body> |
| 12197 |
</subsection> |
| 12198 |
|
| 12199 |
<subsection> |
| 12200 |
<title>Alternative: Booting the Installation CD with BootX</title> |
| 12201 |
<body> |
| 12202 |
|
| 12203 |
<p> |
| 12204 |
If you have an OldWorld Mac the bootable portion of the livecd can't be used. |
| 12205 |
The most simple solution is to use MacOS to bootstrap into a Linux environment |
| 12206 |
with a tool called BootX. Boot floppies are being prepared for Macs without |
| 12207 |
MacOS, but they are not available at this time. |
| 12208 |
</p> |
| 12209 |
|
| 12210 |
<p> |
| 12211 |
First, download <uri link="http://penguinppc.org/projects/bootx/">BootX</uri> |
| 12212 |
and unpack the archive. Copy the the <c>BootX Extension</c> from the unpacked |
| 12213 |
archive into <c>Extensions Folder</c> and the BootX App Control Panel into |
| 12214 |
<c>Control Panels</c>, both of which are located in your MacOS System Folder. |
| 12215 |
Next, create a folder called "Linux Kernels" in your System folder and copy the |
| 12216 |
<c>G3G4</c> kernel from the CD to this folder. Finally, copy <c>G3G4.igz</c> |
| 12217 |
from the Installation CD <path>boot</path> folder into the MacOS |
| 12218 |
<c>System Folder</c>. |
| 12219 |
</p> |
| 12220 |
|
| 12221 |
<p> |
| 12222 |
To prepare BootX, start the BootX App Control Panel. First select the Options |
| 12223 |
dialog and check <c>Use Specified RAM Disk</c> and select <c>G3G4.igz</c> from |
| 12224 |
your System Folder. Continue back to the initial screen and ensure that the |
| 12225 |
ramdisk size is at least <c>32000</c>. Finally, set the kernel arguments as |
| 12226 |
shown below: |
| 12227 |
</p> |
| 12228 |
|
| 12229 |
<pre caption="BootX kernel arguments"> |
| 12230 |
cdroot root=/dev/ram0 init=linuxrc loop=livecd.squashfs looptype=squashfs console=tty0 nodevfs udev |
| 12231 |
</pre> |
| 12232 |
|
| 12233 |
<note> |
| 12234 |
The kernel parameters in the yaboot section above are also applicable here. |
| 12235 |
</note> |
| 12236 |
|
| 12237 |
<p> |
| 12238 |
Check once more to make sure the settings are correct and then save the |
| 12239 |
configuration. This saves typing just in case it doesn't boot or something is |
| 12240 |
missing. Press the Linux button at the top of the window to boot into the |
| 12241 |
Installation CD and continue with <uri link="#booted">And When |
| 12242 |
You're Booted...</uri> |
| 12243 |
</p> |
| 12244 |
|
| 12245 |
</body> |
| 12246 |
</subsection> |
| 12247 |
|
| 12248 |
<subsection id="booted"> |
| 12249 |
<title>And When You're Booted...</title> |
| 12250 |
<body> |
| 12251 |
|
| 12252 |
<p> |
| 12253 |
You will be greeted by a root ("#") prompt on the current console. You can also |
| 12254 |
switch to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get |
| 12255 |
back to the one you started on by pressing Alt-F1. Probably you have to hit |
| 12256 |
Alt-fn-Fx on Apple machines. |
| 12257 |
</p> |
| 12258 |
|
| 12259 |
<p> |
| 12260 |
If you are installing Gentoo on a system with a non-US keyboard, use |
| 12261 |
<c>loadkeys</c> to load the keymap for your keyboard. To list the available |
| 12262 |
keymaps, execute <c>ls /usr/share/keymaps/i386</c>. On NewWorld machines or the |
| 12263 |
Pegasos do not use the keymaps in <path>ppc</path> or <path>mac</path> as they |
| 12264 |
are for ADB-based OldWorld machines. |
| 12265 |
</p> |
| 12266 |
|
| 12267 |
<pre caption="Listing available keymaps"> |
| 12268 |
<comment>(PPC uses x86 keymaps on most systems. The mac/ppc keymaps provided |
| 12269 |
on the Installation CD are ADB keymaps and unusable with the Installation CD |
| 12270 |
kernel)</comment> |
| 12271 |
# <i>ls /usr/share/keymaps/i386</i> |
| 12272 |
</pre> |
| 12273 |
|
| 12274 |
<p> |
| 12275 |
Now load the keymap of your choice: |
| 12276 |
</p> |
| 12277 |
|
| 12278 |
<pre caption="Loading a keymap"> |
| 12279 |
# <i>loadkeys be-latin1</i> |
| 12280 |
</pre> |
| 12281 |
|
| 12282 |
<p> |
| 12283 |
Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
| 12284 |
</p> |
| 12285 |
|
| 12286 |
</body> |
| 12287 |
</subsection> |
| 12288 |
<subsection id="hardware"> |
| 12289 |
<title>Extra Hardware Configuration</title> |
| 12290 |
<body> |
| 12291 |
|
| 12292 |
<p> |
| 12293 |
When the Installation CD boots, it tries to detect all your hardware devices and |
| 12294 |
loads the appropriate kernel modules to support your hardware. In the |
| 12295 |
vast majority of cases, it does a very good job. However, in some cases, it may |
| 12296 |
not auto-load the kernel modules you need. If the PCI auto-detection missed some |
| 12297 |
of your system's hardware, you will have to load the appropriate kernel modules |
| 12298 |
manually. |
| 12299 |
</p> |
| 12300 |
|
| 12301 |
<p> |
| 12302 |
In the next example we try to load the <c>airport</c> module. This module |
| 12303 |
supports only the old Airport cards (b-net). AirportExtreme is not supported |
| 12304 |
under Linux: |
| 12305 |
</p> |
| 12306 |
|
| 12307 |
<pre caption="Loading kernel modules"> |
| 12308 |
# <i>modprobe airport</i> |
| 12309 |
</pre> |
| 12310 |
|
| 12311 |
</body> |
| 12312 |
</subsection> |
| 12313 |
<subsection> |
| 12314 |
<title>Optional: Tweaking Hard Disk Performance</title> |
| 12315 |
<body> |
| 12316 |
|
| 12317 |
<p> |
| 12318 |
If you are an advanced user, you might want to tweak the IDE hard disk |
| 12319 |
performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
| 12320 |
test the performance of your disk (execute it several times to get a |
| 12321 |
more precise impression): |
| 12322 |
</p> |
| 12323 |
|
| 12324 |
<pre caption="Testing disk performance"> |
| 12325 |
# <i>hdparm -tT /dev/hda</i> |
| 12326 |
</pre> |
| 12327 |
|
| 12328 |
<p> |
| 12329 |
To tweak, you can use any of the following examples (or experiment |
| 12330 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
| 12331 |
disk): |
| 12332 |
</p> |
| 12333 |
|
| 12334 |
<pre caption="Tweaking hard disk performance"> |
| 12335 |
<comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i> |
| 12336 |
<comment>Activate DMA + Safe Performance-enhancing Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
| 12337 |
</pre> |
| 12338 |
|
| 12339 |
</body> |
| 12340 |
</subsection> |
| 12341 |
<subsection id="useraccounts"> |
| 12342 |
<title>Optional: User Accounts</title> |
| 12343 |
<body> |
| 12344 |
|
| 12345 |
<p> |
| 12346 |
If you plan on giving other people access to your installation |
| 12347 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
| 12348 |
security reasons), you need to create the necessary user accounts and change |
| 12349 |
the root password. |
| 12350 |
</p> |
| 12351 |
|
| 12352 |
<p> |
| 12353 |
To change the root password, use the <c>passwd</c> utility: |
| 12354 |
</p> |
| 12355 |
|
| 12356 |
<pre caption="Changing the root password"> |
| 12357 |
# <i>passwd</i> |
| 12358 |
New password: <comment>(Enter your new password)</comment> |
| 12359 |
Re-enter password: <comment>(Re-enter your password)</comment> |
| 12360 |
</pre> |
| 12361 |
|
| 12362 |
<p> |
| 12363 |
To create a user account, we first enter their credentials, followed by |
| 12364 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
| 12365 |
In the next example, we create a user called "john". |
| 12366 |
</p> |
| 12367 |
|
| 12368 |
<pre caption="Creating a user account"> |
| 12369 |
# <i>useradd -m -G users john</i> |
| 12370 |
# <i>passwd john</i> |
| 12371 |
New password: <comment>(Enter john's password)</comment> |
| 12372 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
| 12373 |
</pre> |
| 12374 |
|
| 12375 |
<p> |
| 12376 |
You can change your user id from root to the newly created user by using |
| 12377 |
<c>su</c>: |
| 12378 |
</p> |
| 12379 |
|
| 12380 |
<pre caption="Changing user id"> |
| 12381 |
# <i>su - john</i> |
| 12382 |
</pre> |
| 12383 |
|
| 12384 |
</body> |
| 12385 |
</subsection> |
| 12386 |
<subsection> |
| 12387 |
<title>Optional: Viewing Documentation while Installing</title> |
| 12388 |
<body> |
| 12389 |
|
| 12390 |
<p> |
| 12391 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
| 12392 |
installation, make sure you have created a user account (see <uri |
| 12393 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
| 12394 |
go to a new terminal and log in. |
| 12395 |
</p> |
| 12396 |
|
| 12397 |
<p> |
| 12398 |
If you want to view the documentation on the CD you can immediately run |
| 12399 |
<c>links2</c> or even <c>links -g</c> for a graphical framebuffer browser to |
| 12400 |
read it: |
| 12401 |
</p> |
| 12402 |
|
| 12403 |
<pre caption="Viewing the on-CD documentation"> |
| 12404 |
# <i>links2 /mnt/cdrom/docs/html/index.html</i> |
| 12405 |
</pre> |
| 12406 |
|
| 12407 |
<p> |
| 12408 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
| 12409 |
more recent than the one provided on the CD. You can view it using <c>links2</c> |
| 12410 |
as well, but only after having completed the <e>Configuring your Network</e> |
| 12411 |
chapter (otherwise you won't be able to go on the Internet to view the |
| 12412 |
document): |
| 12413 |
</p> |
| 12414 |
|
| 12415 |
<pre caption="Viewing the Online Documentation"> |
| 12416 |
# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-ppc.xml</i> |
| 12417 |
</pre> |
| 12418 |
|
| 12419 |
<p> |
| 12420 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
| 12421 |
</p> |
| 12422 |
|
| 12423 |
</body> |
| 12424 |
</subsection> |
| 12425 |
<subsection> |
| 12426 |
<title>Optional: Starting the SSH Daemon</title> |
| 12427 |
<body> |
| 12428 |
|
| 12429 |
<p> |
| 12430 |
If you want to allow other users to access your computer during the |
| 12431 |
Gentoo installation (perhaps because those users are going to help you |
| 12432 |
install Gentoo, or even do it for you), you need to create a user |
| 12433 |
account for them and perhaps even provide them with your root password |
| 12434 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
| 12435 |
</p> |
| 12436 |
|
| 12437 |
<p> |
| 12438 |
To fire up the SSH daemon, execute the following command: |
| 12439 |
</p> |
| 12440 |
|
| 12441 |
<pre caption="Starting the SSH daemon"> |
| 12442 |
# <i>/etc/init.d/sshd start</i> |
| 12443 |
</pre> |
| 12444 |
|
| 12445 |
<p> |
| 12446 |
To be able to use sshd, you first need to set up your networking. Continue with |
| 12447 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
| 12448 |
</p> |
| 12449 |
|
| 12450 |
</body> |
| 12451 |
</subsection> |
| 12452 |
</section> |
| 12453 |
</sections> |
| 12454 |
|
| 12455 |
|
| 12456 |
|
| 12457 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc64-bootloader.xml |
| 12458 |
|
| 12459 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc64-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 12460 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc64-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 12461 |
|
| 12462 |
Index: hb-install-ppc64-bootloader.xml |
| 12463 |
=================================================================== |
| 12464 |
<?xml version='1.0' encoding='UTF-8'?> |
| 12465 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 12466 |
|
| 12467 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 12468 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
| 12469 |
|
| 12470 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc64-bootloader.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 12471 |
|
| 12472 |
<sections> |
| 12473 |
|
| 12474 |
<version>5.3</version> |
| 12475 |
<date>2006-01-20</date> |
| 12476 |
|
| 12477 |
<section> |
| 12478 |
<title>Making your Choice</title> |
| 12479 |
<subsection> |
| 12480 |
<title>Introduction</title> |
| 12481 |
<body> |
| 12482 |
|
| 12483 |
<p> |
| 12484 |
Now that your kernel is configured and compiled and the necessary system |
| 12485 |
configuration files are filled in correctly, it is time to install a |
| 12486 |
program that will fire up your kernel when you start the system. Such a |
| 12487 |
program is called a <e>bootloader</e>. |
| 12488 |
</p> |
| 12489 |
|
| 12490 |
<p> |
| 12491 |
On Linux/PPC64 we have only yaBoot as a bootloader until grub2 is |
| 12492 |
finished. |
| 12493 |
</p> |
| 12494 |
|
| 12495 |
</body> |
| 12496 |
</subsection> |
| 12497 |
</section> |
| 12498 |
<section id="yaboot"> |
| 12499 |
<title>Using yaBoot</title> |
| 12500 |
<subsection> |
| 12501 |
<title>Introduction</title> |
| 12502 |
<body> |
| 12503 |
|
| 12504 |
<impo> |
| 12505 |
For a 64bit userland use yaboot-static instead of yaboot, because yaboot won't |
| 12506 |
compile on 64bit userland systems. For a 32bit userland use yaboot as you |
| 12507 |
normally would. |
| 12508 |
</impo> |
| 12509 |
|
| 12510 |
<p> |
| 12511 |
There are two ways to configure yaBoot for your system. You can use the |
| 12512 |
new and improved <c>yabootconfig</c> included with |
| 12513 |
<path>yaboot-1.3.8-r1</path> and later to automatically set up yaboot. If |
| 12514 |
for some reason you do not want to run <c>yabootconfig</c> to |
| 12515 |
automatically set up <path>/etc/yaboot.conf</path> or you are installing Gentoo |
| 12516 |
on a G5 (on which <c>yabootconfig</c> does not always work), you can just edit |
| 12517 |
the sample file already installed on your system. |
| 12518 |
</p> |
| 12519 |
|
| 12520 |
<impo> |
| 12521 |
If you are installing on a G5 using an online install and have not used the |
| 12522 |
G5 optimized stages you must change what profile you are linked to now. If you |
| 12523 |
do not you will not get dependencies necessary for yaboot to run on Apple |
| 12524 |
equipment. In the command below replace <c>(userland)</c> with your chosen |
| 12525 |
userland bit level. If you are installing on a G5 using an offline install |
| 12526 |
you have to install these packages by hand. |
| 12527 |
</impo> |
| 12528 |
|
| 12529 |
<pre caption = "(ONLINE INSTALL FOR G5 USERS ONLY) Changing your profile"> |
| 12530 |
# <i>rm /etc/make.profile</i> |
| 12531 |
# <i>ln -sf /usr/portage/profiles/default-linux/ppc/2006.0/ppc64/(userland)/970/pmac /etc/make.profile</i> |
| 12532 |
</pre> |
| 12533 |
|
| 12534 |
<pre caption = "(OFFLINE INSTALL FOR G5 USERS ONLY) Installing Necessary File System Tools"> |
| 12535 |
# <i>emerge hfsutils hfsplusutils</i> |
| 12536 |
</pre> |
| 12537 |
|
| 12538 |
<pre caption = "Installing the bootloader"> |
| 12539 |
<comment>(64bit userland)</comment> |
| 12540 |
# <i>emerge --update yaboot-static</i> |
| 12541 |
<comment>(32bit userland)</comment> |
| 12542 |
# <i>emerge --update yaboot</i> |
| 12543 |
</pre> |
| 12544 |
|
| 12545 |
<impo> |
| 12546 |
yabootconfig/ybin won't work on IBM. You have to install yaboot another way: |
| 12547 |
<uri link="#yaboot-ibm">Using yaboot on IBM hardware</uri> |
| 12548 |
</impo> |
| 12549 |
|
| 12550 |
<note> |
| 12551 |
If your root filesystem uses the JFS filesystem, be sure to add <c>ro</c> as a |
| 12552 |
kernel parameter. JFS must be able to replay its log in read-only mode before it |
| 12553 |
gets mounted read-write. |
| 12554 |
</note> |
| 12555 |
|
| 12556 |
<ul> |
| 12557 |
<li><uri link="#yabootconfig">Default: Using yabootconfig</uri></li> |
| 12558 |
<li> |
| 12559 |
<uri link="#manual_yaboot">Alternative: Manual yaBoot Configuration</uri> |
| 12560 |
</li> |
| 12561 |
</ul> |
| 12562 |
|
| 12563 |
</body> |
| 12564 |
</subsection> |
| 12565 |
<subsection id="yabootconfig"> |
| 12566 |
<title>Default: Using yabootconfig</title> |
| 12567 |
<body> |
| 12568 |
|
| 12569 |
<p> |
| 12570 |
<c>yabootconfig</c> will auto-detect the partitions on your machine and will |
| 12571 |
set up dual and triple boot combinations with Linux, Mac OS, and Mac OS |
| 12572 |
X. |
| 12573 |
</p> |
| 12574 |
|
| 12575 |
<p> |
| 12576 |
To use <c>yabootconfig</c>, your drive must have a bootstrap partition, and |
| 12577 |
<path>/etc/fstab</path> must be configured with your Linux partitions. Both of |
| 12578 |
these should have been done already in the steps above. To start, ensure that |
| 12579 |
you have the latest version of yaboot installed by running <c>emerge --update |
| 12580 |
yaboot-static</c>. This is necessary as the latest version will be available via |
| 12581 |
Portage, but it may not have made it into the stage files. |
| 12582 |
</p> |
| 12583 |
|
| 12584 |
<p> |
| 12585 |
Now run <c>yabootconfig</c>. The program will run and it will confirm |
| 12586 |
the location of the bootstrap partition. Type <c>Y</c> if it is correct. If |
| 12587 |
not, double check <path>/etc/fstab</path>. yabootconfig will then scan your |
| 12588 |
system setup, create <path>/etc/yaboot.conf</path> and run <c>mkofboot</c> for |
| 12589 |
you. <c>mkofboot</c> is used to format the bootstrap partition, and install |
| 12590 |
the yaboot configuration file into it. |
| 12591 |
</p> |
| 12592 |
|
| 12593 |
<p> |
| 12594 |
You might want to verify the contents of <path>/etc/yaboot.conf</path>. If |
| 12595 |
you make changes to <path>/etc/yaboot.conf</path> (like setting the |
| 12596 |
default/boot OS), make sure to rerun <c>ybin -v</c> to apply changes to the |
| 12597 |
bootstrap partition. |
| 12598 |
</p> |
| 12599 |
|
| 12600 |
<p> |
| 12601 |
Now continue with <uri link="#reboot">Rebooting your System</uri>. |
| 12602 |
</p> |
| 12603 |
|
| 12604 |
</body> |
| 12605 |
</subsection> |
| 12606 |
<subsection id="manual_yaboot"> |
| 12607 |
<title>Alternative: Manual yaBoot Configuration</title> |
| 12608 |
<body> |
| 12609 |
|
| 12610 |
<p> |
| 12611 |
Below you find a completed <path>yaboot.conf</path> file. Alter it at |
| 12612 |
will. |
| 12613 |
</p> |
| 12614 |
|
| 12615 |
<pre caption = "/etc/yaboot.conf"> |
| 12616 |
<comment>## /etc/yaboot.conf |
| 12617 |
## |
| 12618 |
## run: "man yaboot.conf" for details. Do not make changes until you have!! |
| 12619 |
## see also: /usr/share/doc/yaboot/examples for example configurations. |
| 12620 |
## |
| 12621 |
## For a dual-boot menu, add one or more of: |
| 12622 |
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ |
| 12623 |
|
| 12624 |
## our bootstrap partition:</comment> |
| 12625 |
|
| 12626 |
boot=/dev/hda2 |
| 12627 |
|
| 12628 |
<comment>## ofboot is the openfirmware way to specify the bootstrap partition. |
| 12629 |
## If this isn't defined, yaboot fails on the G5 and some G4s (unless |
| 12630 |
## you pass the necessary arguments to the mkofboot/ybin program). |
| 12631 |
## hd:X means /dev/sdaX (or /dev/hdaX).</comment> |
| 12632 |
|
| 12633 |
ofboot=hd:2 |
| 12634 |
|
| 12635 |
<comment>## hd: is open firmware speak for hda</comment> |
| 12636 |
device=hd: |
| 12637 |
|
| 12638 |
delay=5 |
| 12639 |
defaultos=macosx |
| 12640 |
timeout=30 |
| 12641 |
install=/usr/lib/yaboot/yaboot |
| 12642 |
magicboot=/usr/lib/yaboot/ofboot |
| 12643 |
|
| 12644 |
<comment>################# |
| 12645 |
## This section can be duplicated if you have more than one kernel or set of |
| 12646 |
## boot options - replace 2.6.12-gentoo-r10 with your kernel-version |
| 12647 |
#################</comment> |
| 12648 |
image=/boot/kernel-2.6.12-gentoo-r10 |
| 12649 |
label=Linux |
| 12650 |
root=/dev/hda3 |
| 12651 |
partition=3 |
| 12652 |
read-only |
| 12653 |
|
| 12654 |
macos=hd:13 |
| 12655 |
macosx=hd:12 |
| 12656 |
enablecdboot |
| 12657 |
enableofboot |
| 12658 |
</pre> |
| 12659 |
|
| 12660 |
<p> |
| 12661 |
Once <path>yaboot.conf</path> is set up the way you want it, you run |
| 12662 |
<c>mkofboot -v</c> to install the settings in the bootstrap partition. |
| 12663 |
<e>Don't forget this!</e> Confirm when <c>mkofboot</c> asks you to create a new |
| 12664 |
filesystem. |
| 12665 |
</p> |
| 12666 |
|
| 12667 |
<p> |
| 12668 |
If all goes well, and you have the same |
| 12669 |
options as the sample above, your next reboot will give you a simple, |
| 12670 |
five-entry boot menu. If you update your yaboot config later on, you'll |
| 12671 |
just need to run <c>ybin -v</c> to update the bootstrap partition - |
| 12672 |
<c>mkofboot</c> is for initial setup only. |
| 12673 |
</p> |
| 12674 |
|
| 12675 |
<p> |
| 12676 |
For more information on yaboot, take a look at the <uri |
| 12677 |
link="http://penguinppc.org/projects/yaboot">yaboot project</uri>. For |
| 12678 |
now, continue the installation with <uri link="#reboot">Rebooting your |
| 12679 |
System</uri>. |
| 12680 |
</p> |
| 12681 |
|
| 12682 |
</body> |
| 12683 |
</subsection> |
| 12684 |
</section> |
| 12685 |
<section id="yaboot-ibm"> |
| 12686 |
<title>Using yaboot on IBM hardware</title> |
| 12687 |
<body> |
| 12688 |
|
| 12689 |
<p> |
| 12690 |
On IBM hardware you cannot run yabootconfig or ybin. You must proceed with the |
| 12691 |
following steps: |
| 12692 |
</p> |
| 12693 |
|
| 12694 |
<ul> |
| 12695 |
<li>Install yaboot-static</li> |
| 12696 |
<li>Run 'dd if=/usr/lib/yaboot/yaboot.chrp of=/dev/sdXX' (fill in XX |
| 12697 |
with your disk and partition for the PReP partition; this was in our |
| 12698 |
example /dev/sda1)</li> |
| 12699 |
<li>Next construct your own yaboot.conf file and place into /etc. |
| 12700 |
(Take a look at the config above, look into the man page of |
| 12701 |
yaboot.conf or look at the below yaboot.conf example)</li> |
| 12702 |
<li>Assuming your boot device in OF is pointing to the harddrive you |
| 12703 |
prep boot partition is on then it'll just work, otherwise at IPL time, |
| 12704 |
go into the multiboot menu and set the boot device to the one with |
| 12705 |
your prep boot partition.</li> |
| 12706 |
<li>That's it!</li> |
| 12707 |
</ul> |
| 12708 |
|
| 12709 |
<pre caption = "yaboot.conf for IBM hardware"> |
| 12710 |
device=disk: |
| 12711 |
partition=2 |
| 12712 |
root=/dev/sda2 |
| 12713 |
default=2.6.12-gentoo-r10 |
| 12714 |
timeout=50 |
| 12715 |
|
| 12716 |
image=/boot/kernel-2.6.12-gentoo-r10 |
| 12717 |
label=Linux |
| 12718 |
append="console=ttyS0,9600" |
| 12719 |
read-only |
| 12720 |
</pre> |
| 12721 |
|
| 12722 |
<p> |
| 12723 |
For POWER4, POWER5, and blade-based hardware where the PReP disk partition |
| 12724 |
and the disk partition that contains your kernel are on the same physical disk, |
| 12725 |
you can use a simplified yaboot.conf. The following should be sufficient: |
| 12726 |
</p> |
| 12727 |
|
| 12728 |
<pre caption="yaboot.conf for PReP hardware"> |
| 12729 |
default = linux |
| 12730 |
timeout = 100 |
| 12731 |
image=/boot/kernel-2.6.12-gentoo-r10 |
| 12732 |
label=linux |
| 12733 |
read-only |
| 12734 |
root = /dev/sda2 |
| 12735 |
append="root=/dev/sda2" |
| 12736 |
</pre> |
| 12737 |
|
| 12738 |
<p> |
| 12739 |
To verify that yaboot has been copied to the PReP partition: |
| 12740 |
</p> |
| 12741 |
|
| 12742 |
<pre caption="Verifying the yaboot install on PReP"> |
| 12743 |
# <i>dd if=/dev/sda1 count=10 | grep ELF</i> |
| 12744 |
Binary file (standard input) matches |
| 12745 |
10+0 records in |
| 12746 |
10+0 records out |
| 12747 |
</pre> |
| 12748 |
|
| 12749 |
<p> |
| 12750 |
A match signifies that yaboot was installed correctly. |
| 12751 |
</p> |
| 12752 |
|
| 12753 |
</body> |
| 12754 |
</section> |
| 12755 |
<section id="reboot"> |
| 12756 |
<title>Rebooting the System</title> |
| 12757 |
<subsection> |
| 12758 |
<body> |
| 12759 |
|
| 12760 |
<p> |
| 12761 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
| 12762 |
that one magical command you have been waiting for: <c>reboot</c>. |
| 12763 |
</p> |
| 12764 |
|
| 12765 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
| 12766 |
# <i>exit</i> |
| 12767 |
~# <i>cd</i> |
| 12768 |
~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
| 12769 |
~# <i>reboot</i> |
| 12770 |
</pre> |
| 12771 |
|
| 12772 |
<p> |
| 12773 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
| 12774 |
booted again instead of your new Gentoo system. |
| 12775 |
</p> |
| 12776 |
|
| 12777 |
<p> |
| 12778 |
Once rebooted in your Gentoo installation, finish up with <uri |
| 12779 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
| 12780 |
</p> |
| 12781 |
|
| 12782 |
</body> |
| 12783 |
</subsection> |
| 12784 |
</section> |
| 12785 |
|
| 12786 |
</sections> |
| 12787 |
|
| 12788 |
|
| 12789 |
|
| 12790 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc64-disk.xml |
| 12791 |
|
| 12792 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc64-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 12793 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc64-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 12794 |
|
| 12795 |
Index: hb-install-ppc64-disk.xml |
| 12796 |
=================================================================== |
| 12797 |
<?xml version='1.0' encoding='UTF-8'?> |
| 12798 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 12799 |
|
| 12800 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 12801 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 12802 |
|
| 12803 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc64-disk.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 12804 |
|
| 12805 |
<sections> |
| 12806 |
|
| 12807 |
<version>5.2</version> |
| 12808 |
<date>2006-01-20</date> |
| 12809 |
|
| 12810 |
<section> |
| 12811 |
<title>Introduction to Block Devices</title> |
| 12812 |
<subsection> |
| 12813 |
<title>Block Devices</title> |
| 12814 |
<body> |
| 12815 |
|
| 12816 |
<p> |
| 12817 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
| 12818 |
and Linux in general, including Linux filesystems, partitions and block devices. |
| 12819 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
| 12820 |
you'll be guided through the process of setting up partitions and filesystems |
| 12821 |
for your Gentoo Linux installation. |
| 12822 |
</p> |
| 12823 |
|
| 12824 |
<p> |
| 12825 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
| 12826 |
probably the one that represents the first IDE drive in a Linux system, namely |
| 12827 |
<path>/dev/hda</path>. If your system uses SCSI drives, then your first hard |
| 12828 |
drive would be <path>/dev/sda</path>. Serial ATA drives are also |
| 12829 |
<path>/dev/sda</path> even if they are IDE drives. |
| 12830 |
</p> |
| 12831 |
|
| 12832 |
<p> |
| 12833 |
The block devices above represent an abstract interface to the disk. User |
| 12834 |
programs can use these block devices to interact with your disk without worrying |
| 12835 |
about whether your drives are IDE, SCSI or something else. The program can |
| 12836 |
simply address the storage on the disk as a bunch of contiguous, |
| 12837 |
randomly-accessible 512-byte blocks. |
| 12838 |
</p> |
| 12839 |
|
| 12840 |
</body> |
| 12841 |
</subsection> |
| 12842 |
<subsection> |
| 12843 |
<title>Partitions and Slices</title> |
| 12844 |
<body> |
| 12845 |
|
| 12846 |
<p> |
| 12847 |
Although it is theoretically possible to use a full disk to house your Linux |
| 12848 |
system, this is almost never done in practice. Instead, full disk block devices |
| 12849 |
are split up in smaller, more manageable block devices. On most systems, |
| 12850 |
these are called <e>partitions</e>. Other architectures use a similar technique, |
| 12851 |
called <e>slices</e>. |
| 12852 |
</p> |
| 12853 |
|
| 12854 |
</body> |
| 12855 |
</subsection> |
| 12856 |
</section> |
| 12857 |
<section> |
| 12858 |
<title>Designing a Partitioning Scheme</title> |
| 12859 |
<subsection> |
| 12860 |
<title>Default Partitioning Scheme</title> |
| 12861 |
<body> |
| 12862 |
|
| 12863 |
<p> |
| 12864 |
If you are not interested in drawing up a partitioning scheme for your system, |
| 12865 |
you can use the partitioning scheme we use throughout this book: |
| 12866 |
</p> |
| 12867 |
|
| 12868 |
<table> |
| 12869 |
<tr> |
| 12870 |
<th>Partition</th> |
| 12871 |
<th>Filesystem</th> |
| 12872 |
<th>Size</th> |
| 12873 |
<th>Description</th> |
| 12874 |
</tr> |
| 12875 |
<tr> |
| 12876 |
<ti><path>/dev/sda1</path></ti> |
| 12877 |
<ti>Partition map</ti> |
| 12878 |
<ti>31.5k</ti> |
| 12879 |
<ti>Partition map</ti> |
| 12880 |
</tr> |
| 12881 |
<tr> |
| 12882 |
<ti><path>/dev/sda2</path></ti> |
| 12883 |
<ti>(bootstrap)</ti> |
| 12884 |
<ti>800k</ti> |
| 12885 |
<ti>Apple_Bootstrap</ti> |
| 12886 |
</tr> |
| 12887 |
<tr> |
| 12888 |
<ti><path>/dev/sda3</path></ti> |
| 12889 |
<ti>(swap)</ti> |
| 12890 |
<ti>512M</ti> |
| 12891 |
<ti>Swap partition</ti> |
| 12892 |
</tr> |
| 12893 |
<tr> |
| 12894 |
<ti><path>/dev/sda4</path></ti> |
| 12895 |
<ti>ext3</ti> |
| 12896 |
<ti>Rest of the disk</ti> |
| 12897 |
<ti>Root partition</ti> |
| 12898 |
</tr> |
| 12899 |
</table> |
| 12900 |
|
| 12901 |
<note> |
| 12902 |
There are some partitions named like this: <path>Apple_Driver43, |
| 12903 |
Apple_Driver_ATA, Apple_FWDriver, Apple_Driver_IOKit, |
| 12904 |
Apple_Patches</path>. If you are not planning to use MacOS 9 you can |
| 12905 |
delete them, because MacOS X and Linux don't need them. |
| 12906 |
You might have to use parted in order to delete them, as mac-fdisk can't delete them yet. |
| 12907 |
</note> |
| 12908 |
|
| 12909 |
<p> |
| 12910 |
If you are interested in knowing how big a partition should be, or even how |
| 12911 |
many partitions you need, read on. Otherwise continue now with |
| 12912 |
<uri link="#mac-fdisk">Apple G5: Using mac-fdisk to Partition your |
| 12913 |
Disk</uri> or <uri link="#fdisk">IBM pSeries: using fdisk to Partition |
| 12914 |
your Disk</uri> |
| 12915 |
</p> |
| 12916 |
|
| 12917 |
</body> |
| 12918 |
</subsection> |
| 12919 |
<subsection> |
| 12920 |
<title>How Many and How Big?</title> |
| 12921 |
<body> |
| 12922 |
|
| 12923 |
<p> |
| 12924 |
The number of partitions is highly dependent on your environment. For instance, |
| 12925 |
if you have lots of users, you will most likely want to have your |
| 12926 |
<path>/home</path> separate as it increases security and makes backups easier. |
| 12927 |
If you are installing Gentoo to perform as a mailserver, your |
| 12928 |
<path>/var</path> should be separate as all mails are stored inside |
| 12929 |
<path>/var</path>. A good choice of filesystem will then maximise your |
| 12930 |
performance. Gameservers will have a separate <path>/opt</path> as most gaming |
| 12931 |
servers are installed there. The reason is similar for <path>/home</path>: |
| 12932 |
security and backups. You will definitely want to keep <path>/usr</path> big: |
| 12933 |
not only will it contain the majority of applications, the Portage tree alone |
| 12934 |
takes around 500 Mbyte excluding the various sources that are stored in it. |
| 12935 |
</p> |
| 12936 |
|
| 12937 |
<p> |
| 12938 |
As you can see, it very much depends on what you want to achieve. Separate |
| 12939 |
partitions or volumes have the following advantages: |
| 12940 |
</p> |
| 12941 |
|
| 12942 |
<ul> |
| 12943 |
<li> |
| 12944 |
You can choose the best performing filesystem for each partition or volume |
| 12945 |
</li> |
| 12946 |
<li> |
| 12947 |
Your entire system cannot run out of free space if one defunct tool is |
| 12948 |
continuously writing files to a partition or volume |
| 12949 |
</li> |
| 12950 |
<li> |
| 12951 |
If necessary, file system checks are reduced in time, as multiple checks can |
| 12952 |
be done in parallel (although this advantage is more with multiple disks than |
| 12953 |
it is with multiple partitions) |
| 12954 |
</li> |
| 12955 |
<li> |
| 12956 |
Security can be enhanced by mounting some partitions or volumes read-only, |
| 12957 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
| 12958 |
</li> |
| 12959 |
</ul> |
| 12960 |
|
| 12961 |
<p> |
| 12962 |
However, multiple partitions have one big disadvantage: if not configured |
| 12963 |
properly, you might result in having a system with lots |
| 12964 |
of free space on one partition and none on another. There is also a 15-partition |
| 12965 |
limit for SCSI and SATA. |
| 12966 |
</p> |
| 12967 |
|
| 12968 |
</body> |
| 12969 |
</subsection> |
| 12970 |
</section> |
| 12971 |
<section id="mac-fdisk"> |
| 12972 |
<title>Default: Using mac-fdisk (Apple G5) Partition your Disk</title> |
| 12973 |
<body> |
| 12974 |
|
| 12975 |
<p> |
| 12976 |
At this point, create your partitions using <c>mac-fdisk</c>: |
| 12977 |
</p> |
| 12978 |
|
| 12979 |
<pre caption="Starting mac-fdisk"> |
| 12980 |
# <i>mac-fdisk /dev/sda</i> |
| 12981 |
</pre> |
| 12982 |
|
| 12983 |
<p> |
| 12984 |
First delete the partitions you have cleared previously to make room for your |
| 12985 |
Linux partitions. Use <c>d</c> in <c>mac-fdisk</c> to delete those partition(s). |
| 12986 |
It will ask for the partition number to delete. |
| 12987 |
</p> |
| 12988 |
|
| 12989 |
<p> |
| 12990 |
Second, create an <e>Apple_Bootstrap</e> partition by using <c>b</c>. It will |
| 12991 |
ask for what block you want to start. Enter the number of your first free |
| 12992 |
partition, followed by a <c>p</c>. For instance this is <c>2p</c>. |
| 12993 |
</p> |
| 12994 |
|
| 12995 |
<note> |
| 12996 |
This partition is <e>not</e> a "boot" partition. It is not used by Linux at all; |
| 12997 |
you don't have to place any filesystem on it and you should never mount it. PPC |
| 12998 |
users don't need an extra partition for <path>/boot</path>. |
| 12999 |
</note> |
| 13000 |
|
| 13001 |
<p> |
| 13002 |
Now create a swap partition by pressing <c>c</c>. Again <c>mac-fdisk</c> will |
| 13003 |
ask for what block you want to start this partition from. As we used <c>2</c> |
| 13004 |
before to create the Apple_Bootstrap partition, you now have to enter |
| 13005 |
<c>3p</c>. When you're asked for the size, enter <c>512M</c> (or whatever size |
| 13006 |
you want). When asked for a name, enter <c>swap</c> (mandatory). |
| 13007 |
</p> |
| 13008 |
|
| 13009 |
<p> |
| 13010 |
To create the root partition, enter <c>c</c>, followed by <c>4p</c> to select |
| 13011 |
from what block the root partition should start. When asked for the size, enter |
| 13012 |
<c>4p</c> again. <c>mac-fdisk</c> will interpret this as "Use all available |
| 13013 |
space". When asked for the name, enter <c>root</c> (mandatory). |
| 13014 |
</p> |
| 13015 |
|
| 13016 |
<p> |
| 13017 |
To finish up, write the partition to the disk using <c>w</c> and <c>q</c> to |
| 13018 |
quit <c>mac-fdisk</c>. |
| 13019 |
</p> |
| 13020 |
|
| 13021 |
<note> |
| 13022 |
To make sure everything is ok, you should run mac-fdisk once more and check whether all the partitions are there. |
| 13023 |
If you don't see any of the partitions you created, or the changes you made, you should reinitialize your partitions by pressing "i" in mac-fdisk. |
| 13024 |
Note that this will recreate the partition map and thus remove all your partitions. |
| 13025 |
</note> |
| 13026 |
|
| 13027 |
<p> |
| 13028 |
Now that your partitions are created, you can now continue with <uri |
| 13029 |
link="#filesystems">Creating Filesystems</uri>. |
| 13030 |
</p> |
| 13031 |
|
| 13032 |
</body> |
| 13033 |
</section> |
| 13034 |
<section id="fdisk"> |
| 13035 |
<title>IBM pSeries, iSeries and OpenPower: using fdisk to Partition your Disk</title> |
| 13036 |
<subsection> |
| 13037 |
<body> |
| 13038 |
|
| 13039 |
<note> |
| 13040 |
If you are planning to use a RAID disk array for your gentoo installation and |
| 13041 |
you are using POWER5-based hardware, you should now run <c>iprutils</c> to |
| 13042 |
format the disks to Advanced Function format and create the disk array. You |
| 13043 |
should also consider emerging this package after your install is complete. |
| 13044 |
</note> |
| 13045 |
|
| 13046 |
<p> |
| 13047 |
The following parts explain how to create the example partition layout |
| 13048 |
described previously, namely: |
| 13049 |
</p> |
| 13050 |
|
| 13051 |
<table> |
| 13052 |
<tr> |
| 13053 |
<th>Partition</th> |
| 13054 |
<th>Description</th> |
| 13055 |
</tr> |
| 13056 |
<tr> |
| 13057 |
<ti><path>/dev/sda1</path></ti> |
| 13058 |
<ti>PPC PReP Boot partition</ti> |
| 13059 |
</tr> |
| 13060 |
<tr> |
| 13061 |
<ti><path>/dev/sda2</path></ti> |
| 13062 |
<ti>Swap partition</ti> |
| 13063 |
</tr> |
| 13064 |
<tr> |
| 13065 |
<ti><path>/dev/sda3</path></ti> |
| 13066 |
<ti>Root partition</ti> |
| 13067 |
</tr> |
| 13068 |
</table> |
| 13069 |
|
| 13070 |
<p> |
| 13071 |
Change your partition layout according to your own preference. |
| 13072 |
</p> |
| 13073 |
|
| 13074 |
</body> |
| 13075 |
</subsection> |
| 13076 |
<subsection> |
| 13077 |
<title>Viewing the Current Partition Layout</title> |
| 13078 |
<body> |
| 13079 |
|
| 13080 |
<p> |
| 13081 |
<c>fdisk</c> is a popular and powerful tool to split your disk into |
| 13082 |
partitions. Fire up <c>fdisk</c> on your disk (in our example, we |
| 13083 |
use <path>/dev/sda</path>): |
| 13084 |
</p> |
| 13085 |
|
| 13086 |
<pre caption="Starting fdisk"> |
| 13087 |
# <i>fdisk /dev/sda</i> |
| 13088 |
</pre> |
| 13089 |
|
| 13090 |
<p> |
| 13091 |
Once in <c>fdisk</c>, you'll be greeted with a prompt that looks like |
| 13092 |
this: |
| 13093 |
</p> |
| 13094 |
|
| 13095 |
<pre caption="fdisk prompt"> |
| 13096 |
Command (m for help): |
| 13097 |
</pre> |
| 13098 |
|
| 13099 |
<p> |
| 13100 |
Type <c>p</c> to display your disk's current partition configuration: |
| 13101 |
</p> |
| 13102 |
|
| 13103 |
<pre caption="An example partition configuration"> |
| 13104 |
Command (m for help): p |
| 13105 |
|
| 13106 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
| 13107 |
141 heads, 63 sectors/track, 6761 cylinders |
| 13108 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
| 13109 |
|
| 13110 |
Device Boot Start End Blocks Id System |
| 13111 |
/dev/sda1 1 12 53266+ 83 Linux |
| 13112 |
/dev/sda2 13 233 981571+ 82 Linux swap |
| 13113 |
/dev/sda3 234 674 1958701+ 83 Linux |
| 13114 |
/dev/sda4 675 6761 27035410+ 5 Extended |
| 13115 |
/dev/sda5 675 2874 9771268+ 83 Linux |
| 13116 |
/dev/sda6 2875 2919 199836 83 Linux |
| 13117 |
/dev/sda7 2920 3008 395262 83 Linux |
| 13118 |
/dev/sda8 3009 6761 16668918 83 Linux |
| 13119 |
|
| 13120 |
Command (m for help): |
| 13121 |
</pre> |
| 13122 |
|
| 13123 |
<p> |
| 13124 |
This particular disk is configured to house six Linux filesystems |
| 13125 |
(each with a corresponding partition listed as "Linux") as well as a |
| 13126 |
swap partition (listed as "Linux swap"). |
| 13127 |
</p> |
| 13128 |
|
| 13129 |
</body> |
| 13130 |
</subsection> |
| 13131 |
<subsection> |
| 13132 |
<title>Removing all Partitions</title> |
| 13133 |
<body> |
| 13134 |
|
| 13135 |
<p> |
| 13136 |
We will first remove all existing partitions from the disk. Type |
| 13137 |
<c>d</c> to delete a partition. For instance, to delete an existing |
| 13138 |
<path>/dev/sda1</path>: |
| 13139 |
</p> |
| 13140 |
|
| 13141 |
<note> |
| 13142 |
If you don't want to delete all partitions just delete those you |
| 13143 |
want to delete. At this point the author recommends a backup of your |
| 13144 |
data to avoid the lose of it. |
| 13145 |
</note> |
| 13146 |
|
| 13147 |
<pre caption="Deleting a partition"> |
| 13148 |
Command (m for help): <i>d</i> |
| 13149 |
Partition number (1-4): <i>1</i> |
| 13150 |
</pre> |
| 13151 |
|
| 13152 |
<p> |
| 13153 |
The partition has been scheduled for deletion. It will no longer show up |
| 13154 |
if you type <c>p</c>, but it will not be erased until your changes have |
| 13155 |
been saved. If you made a mistake and want to abort without saving your |
| 13156 |
changes, type <c>q</c> immediately and hit enter and your partition will |
| 13157 |
not be deleted. |
| 13158 |
</p> |
| 13159 |
|
| 13160 |
<p> |
| 13161 |
Now, assuming that you do indeed want to wipe out all the partitions on |
| 13162 |
your system, repeatedly type <c>p</c> to print out a partition listing |
| 13163 |
and then type <c>d</c> and the number of the partition to delete it. |
| 13164 |
Eventually, you'll end up with a partition table with nothing in it: |
| 13165 |
</p> |
| 13166 |
|
| 13167 |
<pre caption="An empty partition table"> |
| 13168 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
| 13169 |
141 heads, 63 sectors/track, 6761 cylinders |
| 13170 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
| 13171 |
|
| 13172 |
Device Boot Start End Blocks Id System |
| 13173 |
|
| 13174 |
Command (m for help): |
| 13175 |
</pre> |
| 13176 |
|
| 13177 |
<p> |
| 13178 |
Now that the in-memory partition table is empty, we're ready to create |
| 13179 |
the partitions. We will use a default partitioning scheme as discussed |
| 13180 |
previously. Of course, don't follow these instructions to the letter if |
| 13181 |
you don't want the same partitioning scheme! |
| 13182 |
</p> |
| 13183 |
|
| 13184 |
</body> |
| 13185 |
</subsection> |
| 13186 |
<subsection> |
| 13187 |
<title>Creating the PPC PReP boot partition</title> |
| 13188 |
<body> |
| 13189 |
|
| 13190 |
<p> |
| 13191 |
We first create a small PReP boot partition. Type <c>n</c> to create a new |
| 13192 |
partition, then <c>p</c> to select a primary partition, followed by |
| 13193 |
<c>1</c> to select the first primary partition. When prompted for the |
| 13194 |
first cylinder, hit enter. When prompted for the last cylinder, type |
| 13195 |
<c>+7M</c> to create a partition 7 Mbyte in size. After you've done |
| 13196 |
this, type <c>t</c> to set the partition type, <c>1</c> to select the |
| 13197 |
partition you just created and then type in <c>41</c> to set the |
| 13198 |
partition type to "PPC PReP Boot". Finally, you'll need to mark the PReP |
| 13199 |
partition as bootable. |
| 13200 |
</p> |
| 13201 |
|
| 13202 |
<note> |
| 13203 |
The PReP partition has to be smaller than 8 MByte! |
| 13204 |
</note> |
| 13205 |
|
| 13206 |
<pre caption="Creating the PReP boot partition"> |
| 13207 |
Command (m for help): <i>p</i> |
| 13208 |
|
| 13209 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
| 13210 |
141 heads, 63 sectors/track, 6761 cylinders |
| 13211 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
| 13212 |
|
| 13213 |
Device Boot Start End Blocks Id System |
| 13214 |
|
| 13215 |
Command (m for help): <i>n</i> |
| 13216 |
Command action |
| 13217 |
e extended |
| 13218 |
p primary partition (1-4) |
| 13219 |
<i>p</i> |
| 13220 |
Partition number (1-4): <i>1</i> |
| 13221 |
First cylinder (1-6761, default 1): |
| 13222 |
Using default value 1 |
| 13223 |
Last cylinder or +size or +sizeM or +sizeK (1-6761, default |
| 13224 |
6761): <i>+8M</i> |
| 13225 |
|
| 13226 |
Command (m for help): <i>t</i> |
| 13227 |
Selected partition 1 |
| 13228 |
Hex code (type L to list codes): <i>41</i> |
| 13229 |
Changed system type of partition 1 to 41 (PPC PReP Boot) |
| 13230 |
|
| 13231 |
Command (m for help): <i>a</i> |
| 13232 |
Partition number (1-4): <i>1</i> |
| 13233 |
Command (m for help): |
| 13234 |
</pre> |
| 13235 |
|
| 13236 |
<p> |
| 13237 |
Now, when you type <c>p</c>, you should see the following partition information: |
| 13238 |
</p> |
| 13239 |
|
| 13240 |
<pre caption="Created boot partition"> |
| 13241 |
Command (m for help): <i>p</i> |
| 13242 |
|
| 13243 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
| 13244 |
141 heads, 63 sectors/track, 6761 cylinders |
| 13245 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
| 13246 |
|
| 13247 |
Device Boot Start End Blocks Id System |
| 13248 |
/dev/sda1 * 1 3 13293 41 PPC PReP Boot |
| 13249 |
|
| 13250 |
Command (m for help): |
| 13251 |
</pre> |
| 13252 |
</body> |
| 13253 |
</subsection> |
| 13254 |
<subsection> |
| 13255 |
<title>Creating the Swap Partition</title> |
| 13256 |
<body> |
| 13257 |
|
| 13258 |
<p> |
| 13259 |
Let's now create the swap partition. To do this, type <c>n</c> to create |
| 13260 |
a new partition, then <c>p</c> to tell fdisk that you want a primary |
| 13261 |
partition. Then type <c>2</c> to create the second primary partition, |
| 13262 |
<path>/dev/sda2</path> in our case. When prompted for the first |
| 13263 |
cylinder, hit enter. When prompted for the last cylinder, type |
| 13264 |
<c>+512M</c> to create a partition 512MB in size. After you've done |
| 13265 |
this, type <c>t</c> to set the partition type, <c>2</c> to select the |
| 13266 |
partition you just created and then type in <c>82</c> to set the |
| 13267 |
partition type to "Linux Swap". After completing these steps, typing |
| 13268 |
<c>p</c> should display a partition table that looks similar to this: |
| 13269 |
</p> |
| 13270 |
|
| 13271 |
<pre caption="Partition listing after creating a swap partition"> |
| 13272 |
Command (m for help): <i>p</i> |
| 13273 |
|
| 13274 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
| 13275 |
141 heads, 63 sectors/track, 6761 cylinders |
| 13276 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
| 13277 |
|
| 13278 |
Device Boot Start End Blocks Id System |
| 13279 |
/dev/sda1 1 3 13293 41 PPC PReP Boot |
| 13280 |
/dev/sda2 4 117 506331 82 Linux swap |
| 13281 |
|
| 13282 |
Command (m for help): |
| 13283 |
</pre> |
| 13284 |
|
| 13285 |
</body> |
| 13286 |
</subsection> |
| 13287 |
<subsection> |
| 13288 |
<title>Creating the Root Partition</title> |
| 13289 |
<body> |
| 13290 |
|
| 13291 |
<p> |
| 13292 |
Finally, let's create the root partition. To do this, type <c>n</c> to |
| 13293 |
create a new partition, then <c>p</c> to tell fdisk that you want a |
| 13294 |
primary partition. Then type <c>3</c> to create the third primary |
| 13295 |
partition, <path>/dev/sda3</path> in our case. When prompted for the |
| 13296 |
first cylinder, hit enter. When prompted for the last cylinder, hit |
| 13297 |
enter to create a partition that takes up the rest of the remaining |
| 13298 |
space on your disk. After completing these steps, typing <c>p</c> should |
| 13299 |
display a partition table that looks similar to this: |
| 13300 |
</p> |
| 13301 |
|
| 13302 |
<pre caption="Partition listing after creating the root partition"> |
| 13303 |
Command (m for help): p |
| 13304 |
|
| 13305 |
Disk /dev/sda: 30.7 GB, 30750031872 bytes |
| 13306 |
141 heads, 63 sectors/track, 6761 cylinders |
| 13307 |
Units = cylinders of 8883 * 512 = 4548096 bytes |
| 13308 |
|
| 13309 |
Device Boot Start End Blocks Id System |
| 13310 |
/dev/sda1 1 3 13293 41 PPC PReP Boot |
| 13311 |
/dev/sda2 4 117 506331 82 Linux swap |
| 13312 |
/dev/sda3 118 6761 29509326 83 Linux |
| 13313 |
|
| 13314 |
Command (m for help): |
| 13315 |
</pre> |
| 13316 |
</body> |
| 13317 |
</subsection> |
| 13318 |
<subsection> |
| 13319 |
<title>Saving the Partition Layout</title> |
| 13320 |
<body> |
| 13321 |
|
| 13322 |
<p> |
| 13323 |
To save the partition layout and exit <c>fdisk</c>, type <c>w</c>. |
| 13324 |
</p> |
| 13325 |
|
| 13326 |
<pre caption="Save and exit fdisk"> |
| 13327 |
Command (m for help): <i>w</i> |
| 13328 |
</pre> |
| 13329 |
|
| 13330 |
<p> |
| 13331 |
Now that your partitions are created, you can now continue with <uri |
| 13332 |
link="#filesystems">Creating Filesystems</uri>. |
| 13333 |
</p> |
| 13334 |
|
| 13335 |
</body> |
| 13336 |
</subsection> |
| 13337 |
</section> |
| 13338 |
<section id="filesystems"> |
| 13339 |
<title>Creating Filesystems</title> |
| 13340 |
<subsection> |
| 13341 |
<title>Introduction</title> |
| 13342 |
<body> |
| 13343 |
|
| 13344 |
<p> |
| 13345 |
Now that your partitions are created, it is time to place a filesystem on them. |
| 13346 |
If you don't care about what filesystem to choose and are happy with what we use |
| 13347 |
as default in this handbook, continue with <uri |
| 13348 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
| 13349 |
Otherwise read on to learn about the available filesystems... |
| 13350 |
</p> |
| 13351 |
|
| 13352 |
</body> |
| 13353 |
</subsection> |
| 13354 |
<subsection> |
| 13355 |
<title>Filesystems?</title> |
| 13356 |
<body> |
| 13357 |
|
| 13358 |
<note> |
| 13359 |
Several filesystems are available. |
| 13360 |
</note> |
| 13361 |
|
| 13362 |
<p> |
| 13363 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
| 13364 |
journaling, which means that routine ext2 filesystem checks at startup time can |
| 13365 |
be quite time-consuming. There is now quite a selection of newer-generation |
| 13366 |
journaled filesystems that can be checked for consistency very quickly and are |
| 13367 |
thus generally preferred over their non-journaled counterparts. Journaled |
| 13368 |
filesystems prevent long delays when you boot your system and your filesystem |
| 13369 |
happens to be in an inconsistent state. |
| 13370 |
</p> |
| 13371 |
|
| 13372 |
<p> |
| 13373 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
| 13374 |
journaling for fast recovery in addition to other enhanced journaling modes like |
| 13375 |
full data and ordered data journaling. ext3 is a very good and reliable |
| 13376 |
filesystem. It has an additional hashed b-tree indexing option that enables |
| 13377 |
high performance in almost all situations. You can enable this indexing by |
| 13378 |
adding <c>-O dir_index</c> to the <c>mke2fs</c> command. In short, ext3 is an |
| 13379 |
excellent filesystem. |
| 13380 |
</p> |
| 13381 |
|
| 13382 |
<p> |
| 13383 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
| 13384 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
| 13385 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
| 13386 |
extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is |
| 13387 |
solid and usable as both general-purpose filesystem and for extreme cases such |
| 13388 |
as the creation of large filesystems, the use of many small files, very large |
| 13389 |
files and directories containing tens of thousands of files. |
| 13390 |
</p> |
| 13391 |
|
| 13392 |
<p> |
| 13393 |
<b>XFS</b> is a filesystem with metadata journaling that is fully supported |
| 13394 |
under Gentoo Linux's xfs-sources kernel. It comes with a robust feature-set and |
| 13395 |
is optimized for scalability. We only recommend using this filesystem on Linux |
| 13396 |
systems with high-end SCSI and/or fibre channel storage and a uninterruptible |
| 13397 |
power supply. Because XFS aggressively caches in-transit data in RAM, improperly |
| 13398 |
designed programs (those that don't take proper precautions when writing files |
| 13399 |
to disk and there are quite a few of them) can lose a good deal of data if the |
| 13400 |
system goes down unexpectedly. |
| 13401 |
</p> |
| 13402 |
|
| 13403 |
<p> |
| 13404 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
| 13405 |
become production-ready. |
| 13406 |
</p> |
| 13407 |
|
| 13408 |
</body> |
| 13409 |
</subsection> |
| 13410 |
<subsection id="filesystems-apply"> |
| 13411 |
<title>Applying a Filesystem to a Partition</title> |
| 13412 |
<body> |
| 13413 |
|
| 13414 |
<p> |
| 13415 |
To create a filesystem on a partition or volume, there are tools available for |
| 13416 |
each possible filesystem: |
| 13417 |
</p> |
| 13418 |
|
| 13419 |
<table> |
| 13420 |
<tr> |
| 13421 |
<th>Filesystem</th> |
| 13422 |
<th>Creation Command</th> |
| 13423 |
</tr> |
| 13424 |
<tr> |
| 13425 |
<ti>ext2</ti> |
| 13426 |
<ti><c>mke2fs</c></ti> |
| 13427 |
</tr> |
| 13428 |
<tr> |
| 13429 |
<ti>ext3</ti> |
| 13430 |
<ti><c>mke2fs -j</c></ti> |
| 13431 |
</tr> |
| 13432 |
<tr> |
| 13433 |
<ti>reiserfs</ti> |
| 13434 |
<ti><c>mkreiserfs</c></ti> |
| 13435 |
</tr> |
| 13436 |
<tr> |
| 13437 |
<ti>xfs</ti> |
| 13438 |
<ti><c>mkfs.xfs</c></ti> |
| 13439 |
</tr> |
| 13440 |
<tr> |
| 13441 |
<ti>jfs</ti> |
| 13442 |
<ti><c>mkfs.jfs</c></ti> |
| 13443 |
</tr> |
| 13444 |
</table> |
| 13445 |
|
| 13446 |
<p> |
| 13447 |
For instance, to have the root partition (<path>/dev/sda4</path> in our example) |
| 13448 |
in ext3 (as in our example), you would use: |
| 13449 |
</p> |
| 13450 |
|
| 13451 |
<pre caption="Applying a filesystem on a partition"> |
| 13452 |
# <i>mke2fs -j /dev/sda4</i> |
| 13453 |
</pre> |
| 13454 |
|
| 13455 |
<p> |
| 13456 |
Now create the filesystems on your newly created partitions (or logical |
| 13457 |
volumes). |
| 13458 |
</p> |
| 13459 |
|
| 13460 |
</body> |
| 13461 |
</subsection> |
| 13462 |
<subsection> |
| 13463 |
<title>Activating the Swap Partition</title> |
| 13464 |
<body> |
| 13465 |
|
| 13466 |
<p> |
| 13467 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
| 13468 |
</p> |
| 13469 |
|
| 13470 |
<pre caption="Creating a Swap signature"> |
| 13471 |
# <i>mkswap /dev/sda3</i> |
| 13472 |
</pre> |
| 13473 |
|
| 13474 |
<p> |
| 13475 |
To activate the swap partition, use <c>swapon</c>: |
| 13476 |
</p> |
| 13477 |
|
| 13478 |
<pre caption="Activating the swap partition"> |
| 13479 |
# <i>swapon /dev/sda3</i> |
| 13480 |
</pre> |
| 13481 |
|
| 13482 |
<p> |
| 13483 |
Create and activate the swap with the commands mentioned above. |
| 13484 |
</p> |
| 13485 |
|
| 13486 |
</body> |
| 13487 |
</subsection> |
| 13488 |
</section> |
| 13489 |
<section> |
| 13490 |
<title>Mounting</title> |
| 13491 |
<body> |
| 13492 |
|
| 13493 |
<p> |
| 13494 |
Now that your partitions are initialized and are housing a filesystem, it is |
| 13495 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
| 13496 |
create the necessary mount directories for every partition you created. As an |
| 13497 |
example we create a mount-point and mount the root and boot partition: |
| 13498 |
</p> |
| 13499 |
|
| 13500 |
<pre caption="Mounting partitions"> |
| 13501 |
# <i>mkdir /mnt/gentoo</i> |
| 13502 |
# <i>mount /dev/sda4 /mnt/gentoo</i> |
| 13503 |
</pre> |
| 13504 |
|
| 13505 |
<note> |
| 13506 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
| 13507 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
| 13508 |
also holds for <path>/var/tmp</path>. |
| 13509 |
</note> |
| 13510 |
|
| 13511 |
<p> |
| 13512 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
| 13513 |
Installation Files</uri>. |
| 13514 |
</p> |
| 13515 |
|
| 13516 |
</body> |
| 13517 |
</section> |
| 13518 |
</sections> |
| 13519 |
|
| 13520 |
|
| 13521 |
|
| 13522 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc64-kernel.xml |
| 13523 |
|
| 13524 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc64-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 13525 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc64-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 13526 |
|
| 13527 |
Index: hb-install-ppc64-kernel.xml |
| 13528 |
=================================================================== |
| 13529 |
<?xml version='1.0' encoding='UTF-8'?> |
| 13530 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 13531 |
|
| 13532 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 13533 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 13534 |
|
| 13535 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc64-kernel.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 13536 |
|
| 13537 |
<sections> |
| 13538 |
|
| 13539 |
<version>5.5</version> |
| 13540 |
<date>2006-01-06</date> |
| 13541 |
|
| 13542 |
<section> |
| 13543 |
<title>Timezone</title> |
| 13544 |
<body> |
| 13545 |
|
| 13546 |
<p> |
| 13547 |
You first need to select your timezone so that your system knows where it is |
| 13548 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
| 13549 |
it to <path>/etc/localtime</path>. Please avoid the |
| 13550 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
| 13551 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
| 13552 |
</p> |
| 13553 |
|
| 13554 |
<pre caption="Setting the timezone information"> |
| 13555 |
# <i>ls /usr/share/zoneinfo</i> |
| 13556 |
<comment>(Suppose you want to use GMT)</comment> |
| 13557 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
| 13558 |
</pre> |
| 13559 |
|
| 13560 |
</body> |
| 13561 |
</section> |
| 13562 |
<section> |
| 13563 |
<title>Installing the Sources</title> |
| 13564 |
<subsection> |
| 13565 |
<title>Choosing a Kernel</title> |
| 13566 |
<body> |
| 13567 |
|
| 13568 |
<p> |
| 13569 |
The core around which all distributions are built is the Linux kernel. |
| 13570 |
It is the layer between the user programs and your system hardware. |
| 13571 |
Gentoo provides its users several possible kernel sources. A full |
| 13572 |
listing with description is available at the <uri |
| 13573 |
link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>. |
| 13574 |
</p> |
| 13575 |
|
| 13576 |
<p> |
| 13577 |
For PPC64 you should use <c>gentoo-sources</c>. So let's continue with |
| 13578 |
<c>emerge</c>'ing the kernel sources. The <c>USE="-doc"</c> is necessary to |
| 13579 |
avoid installing xorg-x11 or other dependencies at this point. |
| 13580 |
<c>USE="symlink"</c> is not necessary for a new install, but ensures proper |
| 13581 |
creation of the <path>/usr/src/linux</path> symlink. |
| 13582 |
</p> |
| 13583 |
|
| 13584 |
<pre caption="Installing a kernel source"> |
| 13585 |
# <i>USE="-doc symlink" emerge gentoo-sources</i> |
| 13586 |
</pre> |
| 13587 |
|
| 13588 |
<p> |
| 13589 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
| 13590 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
| 13591 |
kernel source points to <c>gentoo-sources-2.6.12-r10</c>. Your version may be |
| 13592 |
different, so keep this in mind. |
| 13593 |
</p> |
| 13594 |
|
| 13595 |
<pre caption="Viewing the kernel source symlink"> |
| 13596 |
# <i>ls -l /usr/src/linux</i> |
| 13597 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-2.6.12-gentoo-r10 |
| 13598 |
</pre> |
| 13599 |
|
| 13600 |
<p> |
| 13601 |
Now it is time to configure and compile your kernel source. There is the |
| 13602 |
ability to use "genkernel" which would create a generic kernel like the |
| 13603 |
ones used on the installation CDs, but it is not fully functional for PPC64 at |
| 13604 |
the moment. |
| 13605 |
</p> |
| 13606 |
|
| 13607 |
<p> |
| 13608 |
Continue now with <uri link="#manual">Manual Configuration</uri>. |
| 13609 |
</p> |
| 13610 |
|
| 13611 |
</body> |
| 13612 |
</subsection> |
| 13613 |
</section> |
| 13614 |
<section id="manual"> |
| 13615 |
<title>Manual Configuration</title> |
| 13616 |
<subsection> |
| 13617 |
<title>Introduction</title> |
| 13618 |
<body> |
| 13619 |
|
| 13620 |
<p> |
| 13621 |
Manually configuring a kernel is often seen as the most difficult procedure a |
| 13622 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
| 13623 |
couple of kernels you don't even remember that it was difficult ;) |
| 13624 |
</p> |
| 13625 |
|
| 13626 |
<p> |
| 13627 |
However, one thing <e>is</e> true: you must know your system when you |
| 13628 |
configuring a kernel manually. Most information can be gathered by emerging |
| 13629 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
| 13630 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
| 13631 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
| 13632 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
| 13633 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
| 13634 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
| 13635 |
uses (it might provide you with a nice hint on what to enable). |
| 13636 |
</p> |
| 13637 |
|
| 13638 |
<p> |
| 13639 |
Now go to your kernel source directory and execute <c>make |
| 13640 |
menuconfig</c>. This will fire up an ncurses-based configuration menu. |
| 13641 |
</p> |
| 13642 |
|
| 13643 |
<p> |
| 13644 |
When compiling the kernel on a 32bit userland system add the following to |
| 13645 |
the bottom of /etc/profile: |
| 13646 |
</p> |
| 13647 |
|
| 13648 |
<pre caption="32bit userland make alias"> |
| 13649 |
# <i>echo 'alias ppc64make="make ARCH=ppc64 CROSS_COMPILE=powerpc64-unknown-linux-gnu-"' >> /etc/profile</i> |
| 13650 |
# <i>source /etc/profile</i> |
| 13651 |
</pre> |
| 13652 |
|
| 13653 |
<pre caption="Invoking menuconfig"> |
| 13654 |
# <i>cd /usr/src/linux</i> |
| 13655 |
(64bit userland) # <i>make menuconfig</i> |
| 13656 |
(32bit userland) # <i>ppc64make menuconfig</i> |
| 13657 |
</pre> |
| 13658 |
|
| 13659 |
<p> |
| 13660 |
You will be greeted with several configuration sections. We'll first |
| 13661 |
list some options you must activate (otherwise Gentoo will not function, |
| 13662 |
or not function properly without additional tweaks). |
| 13663 |
</p> |
| 13664 |
|
| 13665 |
</body> |
| 13666 |
</subsection> |
| 13667 |
<subsection> |
| 13668 |
<title>Activating Required Options</title> |
| 13669 |
<body> |
| 13670 |
|
| 13671 |
<p> |
| 13672 |
First of all, activate the use of development and experimental |
| 13673 |
code/drivers. You need this, otherwise some very important code/drivers |
| 13674 |
won't show up: |
| 13675 |
</p> |
| 13676 |
|
| 13677 |
<pre caption="Selecting experimental code/drivers, General setup"> |
| 13678 |
Code maturity level options ---> |
| 13679 |
[*] Prompt for development and/or incomplete code/drivers |
| 13680 |
General setup ---> |
| 13681 |
[*] Support for hot-pluggable devices |
| 13682 |
</pre> |
| 13683 |
|
| 13684 |
<p> |
| 13685 |
Now go to <c>File Systems</c> and select support for the filesystems you |
| 13686 |
use. <e>Don't</e> compile them as modules, otherwise your Gentoo system |
| 13687 |
will not be able to mount your partitions. Also select <c>Virtual |
| 13688 |
memory</c>, <c>/proc file system</c>, and <c>/dev/pts file system for |
| 13689 |
Unix98 PTYs</c>: |
| 13690 |
</p> |
| 13691 |
|
| 13692 |
<pre caption="Selecting necessary file systems"> |
| 13693 |
File systems ---> |
| 13694 |
[*] Virtual memory file system support (former shm fs) |
| 13695 |
[*] /proc file system support |
| 13696 |
[*] /dev/pts file system for Unix98 PTYs |
| 13697 |
|
| 13698 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
| 13699 |
<*> Reiserfs support |
| 13700 |
<*> Ext3 journalling file system support |
| 13701 |
<*> JFS filesystem support |
| 13702 |
<*> Second extended fs support |
| 13703 |
<*> XFS filesystem support |
| 13704 |
</pre> |
| 13705 |
|
| 13706 |
<note> |
| 13707 |
You will find some of the mentioned options under <c>Pseudo |
| 13708 |
filesystems</c> which is a subpart of <c>File systems</c>. |
| 13709 |
</note> |
| 13710 |
|
| 13711 |
<p> |
| 13712 |
If you are using PPPoE to connect to the Internet or you are using a |
| 13713 |
dial-up modem, you will need the following options in the kernel (you |
| 13714 |
will find the mentioned options under <c>Networking support</c> which is |
| 13715 |
a subpart of <c>Device Drivers</c>): |
| 13716 |
</p> |
| 13717 |
|
| 13718 |
<pre caption="Selecting PPPoE necessary drivers"> |
| 13719 |
Network device support ---> |
| 13720 |
<*> PPP (point-to-point protocol) support |
| 13721 |
<*> PPP support for async serial ports |
| 13722 |
<*> PPP support for sync tty ports |
| 13723 |
</pre> |
| 13724 |
|
| 13725 |
<p> |
| 13726 |
The two compression options won't harm but are not definitely needed, neither |
| 13727 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
| 13728 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
| 13729 |
</p> |
| 13730 |
|
| 13731 |
<p> |
| 13732 |
If you require it, don't forget to include support in the kernel for your |
| 13733 |
ethernet card. |
| 13734 |
</p> |
| 13735 |
|
| 13736 |
<p> |
| 13737 |
Disable ADB raw keycodes: |
| 13738 |
</p> |
| 13739 |
|
| 13740 |
<pre caption="Disabling ADB raw keycodes"> |
| 13741 |
Macintosh Device Drivers ---> |
| 13742 |
[ ] Support for ADB raw keycodes |
| 13743 |
</pre> |
| 13744 |
|
| 13745 |
<p> |
| 13746 |
When you're done configuring your kernel, continue with <uri |
| 13747 |
link="#compiling">Compiling and Installing</uri>. |
| 13748 |
</p> |
| 13749 |
|
| 13750 |
</body> |
| 13751 |
</subsection> |
| 13752 |
<subsection id="compiling"> |
| 13753 |
<title>Compiling and Installing</title> |
| 13754 |
<body> |
| 13755 |
|
| 13756 |
<p> |
| 13757 |
Now that your kernel is configured, it is time to compile and install it. Exit |
| 13758 |
the configuration and start the compilation process: |
| 13759 |
</p> |
| 13760 |
|
| 13761 |
<pre caption="Compiling the kernel"> |
| 13762 |
(64bit userland) # <i>make && make modules_install</i> |
| 13763 |
(32bit userland) # <i>ppc64make && ppc64make modules_install</i> |
| 13764 |
</pre> |
| 13765 |
|
| 13766 |
<p> |
| 13767 |
When the kernel has finished compiling, copy the kernel image to |
| 13768 |
<path>/boot</path>. Remember to replace <path><kernel-version<</path> |
| 13769 |
with your actual kernel version: |
| 13770 |
</p> |
| 13771 |
|
| 13772 |
<pre caption="Installing the kernel"> |
| 13773 |
# <i>cp vmlinux /boot/<kernel-version<</i> |
| 13774 |
</pre> |
| 13775 |
|
| 13776 |
<p> |
| 13777 |
Now continue with <uri link="#kernel_modules">Configuring the Modules</uri>. |
| 13778 |
</p> |
| 13779 |
|
| 13780 |
</body> |
| 13781 |
</subsection> |
| 13782 |
</section> |
| 13783 |
<section id="kernel_modules"> |
| 13784 |
<title>Configuring the Modules</title> |
| 13785 |
<body> |
| 13786 |
|
| 13787 |
<p> |
| 13788 |
You should list the modules you want automatically loaded in |
| 13789 |
<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra |
| 13790 |
options to the modules too if you want. |
| 13791 |
</p> |
| 13792 |
|
| 13793 |
<p> |
| 13794 |
To view all available modules, run the following <c>find</c> command. Don't |
| 13795 |
forget to substitute "<kernel version>" with the version of the kernel you |
| 13796 |
just compiled: |
| 13797 |
</p> |
| 13798 |
|
| 13799 |
<pre caption="Viewing all available modules"> |
| 13800 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
| 13801 |
</pre> |
| 13802 |
|
| 13803 |
<p> |
| 13804 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
| 13805 |
<path>kernel-2.6</path> file and enter the module name in it. |
| 13806 |
</p> |
| 13807 |
|
| 13808 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
| 13809 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
| 13810 |
</pre> |
| 13811 |
|
| 13812 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
| 13813 |
3c59x |
| 13814 |
</pre> |
| 13815 |
|
| 13816 |
<p> |
| 13817 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
| 13818 |
your System</uri>. |
| 13819 |
</p> |
| 13820 |
|
| 13821 |
</body> |
| 13822 |
</section> |
| 13823 |
</sections> |
| 13824 |
|
| 13825 |
|
| 13826 |
|
| 13827 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc64-medium.xml |
| 13828 |
|
| 13829 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc64-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 13830 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc64-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 13831 |
|
| 13832 |
Index: hb-install-ppc64-medium.xml |
| 13833 |
=================================================================== |
| 13834 |
<?xml version='1.0' encoding='UTF-8'?> |
| 13835 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 13836 |
|
| 13837 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 13838 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 13839 |
|
| 13840 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-ppc64-medium.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 13841 |
|
| 13842 |
<sections> |
| 13843 |
|
| 13844 |
<version>5.5</version> |
| 13845 |
<date>2005-11-29</date> |
| 13846 |
|
| 13847 |
<section> |
| 13848 |
<title>Hardware Requirements</title> |
| 13849 |
<subsection> |
| 13850 |
<title>Introduction</title> |
| 13851 |
<body> |
| 13852 |
|
| 13853 |
<p> |
| 13854 |
Before we start, we first list what hardware requirements you need to |
| 13855 |
successfully install Gentoo on your box. |
| 13856 |
</p> |
| 13857 |
|
| 13858 |
</body> |
| 13859 |
</subsection> |
| 13860 |
<subsection> |
| 13861 |
<title>Hardware Requirements</title> |
| 13862 |
<body> |
| 13863 |
|
| 13864 |
<table> |
| 13865 |
<tr> |
| 13866 |
<th>CPU</th> |
| 13867 |
<ti>Any PowerPC64 CPU</ti> |
| 13868 |
</tr> |
| 13869 |
<tr> |
| 13870 |
<th>Systems</th> |
| 13871 |
<ti> |
| 13872 |
IBM RS/6000s, Power Macintosh G5, iMac G5, IBP pSeries and IBM OpenPower |
| 13873 |
</ti> |
| 13874 |
</tr> |
| 13875 |
<tr> |
| 13876 |
<th>Memory</th> |
| 13877 |
<ti>64 MB</ti> |
| 13878 |
</tr> |
| 13879 |
<tr> |
| 13880 |
<th>Diskspace</th> |
| 13881 |
<ti>1.5 GB (excluding swap space)</ti> |
| 13882 |
</tr> |
| 13883 |
<tr> |
| 13884 |
<th>Swap space</th> |
| 13885 |
<ti>At least 256 MB</ti> |
| 13886 |
</tr> |
| 13887 |
</table> |
| 13888 |
|
| 13889 |
<p> |
| 13890 |
For a full list of supported systems, please go to |
| 13891 |
<uri>http://www.linuxppc64.org/hardware.shtml</uri>. |
| 13892 |
</p> |
| 13893 |
|
| 13894 |
</body> |
| 13895 |
</subsection> |
| 13896 |
</section> |
| 13897 |
<!-- Copy/paste from hb-install-x86-medium.xml, with s/x86/ppc64/ --> |
| 13898 |
<!-- START --> |
| 13899 |
<section> |
| 13900 |
<title>The Gentoo Universal Installation CD</title> |
| 13901 |
<subsection> |
| 13902 |
<title>Introduction</title> |
| 13903 |
<body> |
| 13904 |
|
| 13905 |
<p> |
| 13906 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
| 13907 |
Such a tarball is an archive that contains a minimal environment from |
| 13908 |
which you can succesfully install Gentoo Linux onto your system. |
| 13909 |
</p> |
| 13910 |
|
| 13911 |
<p> |
| 13912 |
Installations using a stage1 or stage2 tarball file are not documented in the |
| 13913 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
| 13914 |
FAQ</uri> on these matters. |
| 13915 |
</p> |
| 13916 |
|
| 13917 |
</body> |
| 13918 |
</subsection> |
| 13919 |
<subsection> |
| 13920 |
<title>Gentoo Universal Installation CD</title> |
| 13921 |
<body> |
| 13922 |
|
| 13923 |
<p> |
| 13924 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
| 13925 |
environment. It allows you to boot Linux from the CD. During the boot process |
| 13926 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
| 13927 |
Installation CDs are maintained by Gentoo developers. |
| 13928 |
</p> |
| 13929 |
|
| 13930 |
<p> |
| 13931 |
There currently are two Installation CDs available: |
| 13932 |
</p> |
| 13933 |
|
| 13934 |
<ul> |
| 13935 |
<li> |
| 13936 |
The Universal Installation CD contains everything you need to install |
| 13937 |
Gentoo. It provides stage3 files for common architectures, source code |
| 13938 |
for the extra applications you need to choose from and, of course, the |
| 13939 |
installation instructions for your architecture. |
| 13940 |
</li> |
| 13941 |
<li> |
| 13942 |
The Minimal Installation CD contains only a minimal environment that allows |
| 13943 |
you to boot up and configure your network so you can connect to the |
| 13944 |
Internet. It does not contain any additional files and cannot be used |
| 13945 |
during the current installation approach. |
| 13946 |
</li> |
| 13947 |
</ul> |
| 13948 |
|
| 13949 |
<p> |
| 13950 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
| 13951 |
additional resource that you can exploit during the installation of your Gentoo |
| 13952 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
| 13953 |
you to easily and quickly install additional applications immediately after the |
| 13954 |
Gentoo installation and right before you update your Portage tree. |
| 13955 |
</p> |
| 13956 |
|
| 13957 |
<p> |
| 13958 |
The use of the Package CD is covered later in this document. |
| 13959 |
</p> |
| 13960 |
|
| 13961 |
</body> |
| 13962 |
</subsection> |
| 13963 |
</section> |
| 13964 |
<!-- STOP --> |
| 13965 |
<section> |
| 13966 |
<title>Download, Burn and Boot a Gentoo Installation CD</title> |
| 13967 |
<subsection> |
| 13968 |
<title>Downloading and Burning the Installation CDs</title> |
| 13969 |
<body> |
| 13970 |
|
| 13971 |
<p> |
| 13972 |
You can download the Universal Installation CD (and, if you want to, the |
| 13973 |
Packages CD as well) from one of our <uri |
| 13974 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located |
| 13975 |
in the <path>releases/ppc64/2006.0-r1/installcd</path> directory; |
| 13976 |
the Package CDs are located in the <path>releases/ppc64/2006.0/packagecd</path> |
| 13977 |
directory. |
| 13978 |
</p> |
| 13979 |
|
| 13980 |
<p> |
| 13981 |
Inside those directories you'll find ISO-files. Those are full CD images which |
| 13982 |
you can write on a CD-R. |
| 13983 |
</p> |
| 13984 |
|
| 13985 |
<p> |
| 13986 |
After downloading the file, you can verify its integrity to see if it is |
| 13987 |
corrupted or not: |
| 13988 |
</p> |
| 13989 |
|
| 13990 |
<ul> |
| 13991 |
<li> |
| 13992 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
| 13993 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
| 13994 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows). How |
| 13995 |
to verify MD5 checksums with Mac OS X is described in the <uri |
| 13996 |
link="/doc/en/gentoo-ppc-faq.xml#doc_chap1">Gentoo PPC FAQ</uri>. |
| 13997 |
</li> |
| 13998 |
<li> |
| 13999 |
You can verify the cryptographic signature that we provide. You need to |
| 14000 |
obtain the public key we use (0x17072058) before you proceed though. |
| 14001 |
</li> |
| 14002 |
</ul> |
| 14003 |
|
| 14004 |
<p> |
| 14005 |
To fetch our public key using the GnuPG application, run the following command: |
| 14006 |
</p> |
| 14007 |
|
| 14008 |
<pre caption="Obtaining the public key"> |
| 14009 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 0x17072058</i> |
| 14010 |
</pre> |
| 14011 |
|
| 14012 |
<p> |
| 14013 |
Now verify the signature: |
| 14014 |
</p> |
| 14015 |
|
| 14016 |
<pre caption="Verify the cryptographic signature"> |
| 14017 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
| 14018 |
</pre> |
| 14019 |
|
| 14020 |
<p> |
| 14021 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
| 14022 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
| 14023 |
<c>K3B</c> here; more information can be found in our <uri |
| 14024 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
| 14025 |
</p> |
| 14026 |
|
| 14027 |
<ul> |
| 14028 |
<li> |
| 14029 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
| 14030 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
| 14031 |
path). |
| 14032 |
</li> |
| 14033 |
<li> |
| 14034 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
| 14035 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
| 14036 |
<c>Start</c>. |
| 14037 |
</li> |
| 14038 |
</ul> |
| 14039 |
|
| 14040 |
</body> |
| 14041 |
</subsection> |
| 14042 |
<subsection> |
| 14043 |
<title>Booting the Installation CD on an Apple</title> |
| 14044 |
<body> |
| 14045 |
|
| 14046 |
<p> |
| 14047 |
Place the Installation CD in the CD-ROM and reboot the system. Hold down the |
| 14048 |
'C' key at bootup. You will be greeted by a friendly welcome message and a |
| 14049 |
<e>boot:</e> prompt at the bottom of the screen. |
| 14050 |
</p> |
| 14051 |
|
| 14052 |
<p> |
| 14053 |
You are also able to tweak some kernel options at this prompt. The following |
| 14054 |
table lists the available boot options you can add: |
| 14055 |
</p> |
| 14056 |
|
| 14057 |
<table> |
| 14058 |
<tr> |
| 14059 |
<th>Boot Option</th> |
| 14060 |
<th>Description</th> |
| 14061 |
</tr> |
| 14062 |
<tr> |
| 14063 |
<ti><c>video</c></ti> |
| 14064 |
<ti> |
| 14065 |
This option takes one of the following vendor-specific tags: |
| 14066 |
<c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, <c>aty128</c> or |
| 14067 |
<c>ofonly</c>. You can follow this tag with the resolution and refreshrate |
| 14068 |
you want to use. For instance <c>video=radeonfb:1280x1024@75</c>. If you are |
| 14069 |
uncertain what to choose, <c>ofonly</c> will most certainly work. |
| 14070 |
</ti> |
| 14071 |
</tr> |
| 14072 |
<tr> |
| 14073 |
<ti><c>nol3</c></ti> |
| 14074 |
<ti> |
| 14075 |
Disables level 3 cache on some powerbooks (needed for at least the 17'') |
| 14076 |
</ti> |
| 14077 |
</tr> |
| 14078 |
<tr> |
| 14079 |
<ti><c>debug</c></ti> |
| 14080 |
<ti> |
| 14081 |
Enables verbose booting, spawns an initrd shell that can be used to debug |
| 14082 |
the Installation CD |
| 14083 |
</ti> |
| 14084 |
</tr> |
| 14085 |
<tr> |
| 14086 |
<ti><c>sleep=X</c></ti> |
| 14087 |
<ti> |
| 14088 |
Wait X seconds before continuing; this can be needed by some very old SCSI |
| 14089 |
CD-ROMs which don't speed up the CD quick enough |
| 14090 |
</ti> |
| 14091 |
</tr> |
| 14092 |
<tr> |
| 14093 |
<ti><c>bootfrom=X</c></ti> |
| 14094 |
<ti> |
| 14095 |
Boot from a different device |
| 14096 |
</ti> |
| 14097 |
</tr> |
| 14098 |
</table> |
| 14099 |
|
| 14100 |
<p> |
| 14101 |
At this prompt, hit enter, and a complete Gentoo Linux environment will be |
| 14102 |
loaded from the CD. Continue with <uri link="#booted">And When You're |
| 14103 |
Booted...</uri>. |
| 14104 |
</p> |
| 14105 |
|
| 14106 |
</body> |
| 14107 |
</subsection> |
| 14108 |
<subsection> |
| 14109 |
<title>Booting the Installation CD on an IBM pSeries</title> |
| 14110 |
<body> |
| 14111 |
|
| 14112 |
<p> |
| 14113 |
For pSeries boxes, sometimes the cds might not autoboot. You might have |
| 14114 |
to set up your cdrom as a bootable device in the multi-boot menu. (F1 at |
| 14115 |
startup) The other option is to jump into OF and do it from there: |
| 14116 |
</p> |
| 14117 |
|
| 14118 |
<p> |
| 14119 |
1) Boot into OF (this is 8 from the serial cons or F8 from a graphics |
| 14120 |
cons, start hitting the key when you see the keyboard mouse etc etc |
| 14121 |
messages |
| 14122 |
</p> |
| 14123 |
<p> |
| 14124 |
2) run the command 0> boot cdrom:1,yaboot |
| 14125 |
</p> |
| 14126 |
<p> |
| 14127 |
3) stand back and enjoy! |
| 14128 |
</p> |
| 14129 |
|
| 14130 |
</body> |
| 14131 |
</subsection> |
| 14132 |
<subsection id="booted"> |
| 14133 |
<title>And When You're Booted...</title> |
| 14134 |
<body> |
| 14135 |
|
| 14136 |
<p> |
| 14137 |
You will be greeted by a root ("#") prompt on the current console. You can also |
| 14138 |
switch to other consoles by pressing Alt-fn-F2, Alt-fn-F3 and Alt-fn-F4. Get |
| 14139 |
back to the one you started on by pressing Alt-fn-F1. |
| 14140 |
</p> |
| 14141 |
|
| 14142 |
<p> |
| 14143 |
If you are installing Gentoo on a system with a non-US keyboard, use |
| 14144 |
<c>loadkeys</c> to load the keymap for your keyboard. To list the available |
| 14145 |
keymaps, execute <c>ls /usr/share/keymaps/i386</c>. |
| 14146 |
</p> |
| 14147 |
|
| 14148 |
<pre caption="Listing available keymaps"> |
| 14149 |
<comment>(PPC uses x86 keymaps on most systems. The mac/ppc keymaps provided |
| 14150 |
on the Installation CD are ADB keymaps and unusable with the |
| 14151 |
Installation CD kernel)</comment> |
| 14152 |
# <i>ls /usr/share/keymaps/i386</i> |
| 14153 |
</pre> |
| 14154 |
|
| 14155 |
<p> |
| 14156 |
Now load the keymap of your choice: |
| 14157 |
</p> |
| 14158 |
|
| 14159 |
<pre caption="Loading a keymap"> |
| 14160 |
# <i>loadkeys be-latin1</i> |
| 14161 |
</pre> |
| 14162 |
|
| 14163 |
<p> |
| 14164 |
Now continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
| 14165 |
</p> |
| 14166 |
|
| 14167 |
</body> |
| 14168 |
</subsection> |
| 14169 |
<subsection id="hardware"> |
| 14170 |
<title>Extra Hardware Configuration</title> |
| 14171 |
<body> |
| 14172 |
|
| 14173 |
<p> |
| 14174 |
When the Installation CD boots, it tries to detect all your hardware devices and |
| 14175 |
loads the appropriate kernel modules to support your hardware. In the |
| 14176 |
vast majority of cases, it does a very good job. However, in some cases it may |
| 14177 |
not auto-load the kernel |
| 14178 |
modules you need. If the PCI auto-detection missed some of your system's |
| 14179 |
hardware, you will have to load the appropriate kernel modules manually. |
| 14180 |
</p> |
| 14181 |
|
| 14182 |
<p> |
| 14183 |
In the next example we try to load the <c>8139too</c> module (support for |
| 14184 |
certain kinds of network interfaces): |
| 14185 |
</p> |
| 14186 |
|
| 14187 |
<pre caption="Loading kernel modules"> |
| 14188 |
# <i>modprobe 8139too</i> |
| 14189 |
</pre> |
| 14190 |
|
| 14191 |
</body> |
| 14192 |
</subsection> |
| 14193 |
<subsection> |
| 14194 |
<title>Optional: Tweaking Hard Disk Performance</title> |
| 14195 |
<body> |
| 14196 |
|
| 14197 |
<p> |
| 14198 |
If you are an advanced user, you might want to tweak the IDE hard disk |
| 14199 |
performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
| 14200 |
test the performance of your disk (execute it several times to get a |
| 14201 |
more precise impression): |
| 14202 |
</p> |
| 14203 |
|
| 14204 |
<pre caption="Testing disk performance"> |
| 14205 |
# <i>hdparm -tT /dev/hda</i> |
| 14206 |
</pre> |
| 14207 |
|
| 14208 |
<p> |
| 14209 |
To tweak, you can use any of the following examples (or experiment |
| 14210 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
| 14211 |
disk): |
| 14212 |
</p> |
| 14213 |
|
| 14214 |
<pre caption="Tweaking hard disk performance"> |
| 14215 |
<comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i> |
| 14216 |
<comment>Activate DMA + Safe Performance-enhancing Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
| 14217 |
</pre> |
| 14218 |
|
| 14219 |
</body> |
| 14220 |
</subsection> |
| 14221 |
<subsection id="useraccounts"> |
| 14222 |
<title>Optional: User Accounts</title> |
| 14223 |
<body> |
| 14224 |
|
| 14225 |
<p> |
| 14226 |
If you plan on giving other people access to your installation |
| 14227 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
| 14228 |
security reasons), you need to create the necessary user accounts and change |
| 14229 |
the root password. |
| 14230 |
</p> |
| 14231 |
|
| 14232 |
<p> |
| 14233 |
To change the root password, use the <c>passwd</c> utility: |
| 14234 |
</p> |
| 14235 |
|
| 14236 |
<pre caption="Changing the root password"> |
| 14237 |
# <i>passwd</i> |
| 14238 |
New password: <comment>(Enter your new password)</comment> |
| 14239 |
Re-enter password: <comment>(Re-enter your password)</comment> |
| 14240 |
</pre> |
| 14241 |
|
| 14242 |
<p> |
| 14243 |
To create a user account, we first enter their credentials, followed by |
| 14244 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
| 14245 |
In the next example, we create a user called "john". |
| 14246 |
</p> |
| 14247 |
|
| 14248 |
<pre caption="Creating a user account"> |
| 14249 |
# <i>useradd -m -G users john</i> |
| 14250 |
# <i>passwd john</i> |
| 14251 |
New password: <comment>(Enter john's password)</comment> |
| 14252 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
| 14253 |
</pre> |
| 14254 |
|
| 14255 |
<p> |
| 14256 |
You can change your user id from root to the newly created user by using |
| 14257 |
<c>su</c>: |
| 14258 |
</p> |
| 14259 |
|
| 14260 |
<pre caption="Changing user id"> |
| 14261 |
# <i>su - john</i> |
| 14262 |
</pre> |
| 14263 |
|
| 14264 |
</body> |
| 14265 |
</subsection> |
| 14266 |
<subsection> |
| 14267 |
<title>Optional: Viewing Documentation while Installing</title> |
| 14268 |
<body> |
| 14269 |
|
| 14270 |
<p> |
| 14271 |
If you want to view the Gentoo Handbook during the installation, make sure you |
| 14272 |
have created a user account (see <uri link="#useraccounts">Optional: User |
| 14273 |
Accounts</uri>). Then press <c>Alt-F2</c> to go to a new terminal and log in. |
| 14274 |
</p> |
| 14275 |
|
| 14276 |
<p> |
| 14277 |
If you want to view the documentation on the CD you can immediately run |
| 14278 |
<c>links2</c> to read it: |
| 14279 |
</p> |
| 14280 |
|
| 14281 |
<pre caption="Viewing the on-CD documentation"> |
| 14282 |
# <i>links2 /mnt/cdrom/docs/handbook/html/index.html</i> |
| 14283 |
</pre> |
| 14284 |
|
| 14285 |
<p> |
| 14286 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
| 14287 |
more recent than the one provided on the CD. |
| 14288 |
</p> |
| 14289 |
|
| 14290 |
<pre caption="Viewing the Online Documentation"> |
| 14291 |
# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-ppc64.xml</i> |
| 14292 |
</pre> |
| 14293 |
|
| 14294 |
<p> |
| 14295 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
| 14296 |
</p> |
| 14297 |
|
| 14298 |
</body> |
| 14299 |
</subsection> |
| 14300 |
<subsection> |
| 14301 |
<title>Optional: Starting the SSH Daemon</title> |
| 14302 |
<body> |
| 14303 |
|
| 14304 |
<p> |
| 14305 |
If you want to allow other users to access your computer during the |
| 14306 |
Gentoo installation (perhaps because those users are going to help you |
| 14307 |
install Gentoo, or even do it for you), you need to create a user |
| 14308 |
account for them and perhaps even provide them with your root password |
| 14309 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
| 14310 |
</p> |
| 14311 |
|
| 14312 |
<p> |
| 14313 |
To fire up the SSH daemon, execute the following command: |
| 14314 |
</p> |
| 14315 |
|
| 14316 |
<pre caption="Starting the SSH daemon"> |
| 14317 |
# <i>/etc/init.d/sshd start</i> |
| 14318 |
</pre> |
| 14319 |
|
| 14320 |
<p> |
| 14321 |
To be able to use sshd, you first need to set up your networking. Continue with |
| 14322 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
| 14323 |
</p> |
| 14324 |
|
| 14325 |
</body> |
| 14326 |
</subsection> |
| 14327 |
</section> |
| 14328 |
</sections> |
| 14329 |
|
| 14330 |
|
| 14331 |
|
| 14332 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-sparc-bootloader.xml |
| 14333 |
|
| 14334 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-sparc-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 14335 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-sparc-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 14336 |
|
| 14337 |
Index: hb-install-sparc-bootloader.xml |
| 14338 |
=================================================================== |
| 14339 |
<?xml version='1.0' encoding='UTF-8'?> |
| 14340 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 14341 |
|
| 14342 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 14343 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 14344 |
|
| 14345 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-sparc-bootloader.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 14346 |
|
| 14347 |
<sections> |
| 14348 |
|
| 14349 |
<version>5.3</version> |
| 14350 |
<date>2006-01-19</date> |
| 14351 |
|
| 14352 |
<section> |
| 14353 |
<title>Making your Choice</title> |
| 14354 |
<subsection> |
| 14355 |
<title>Introduction</title> |
| 14356 |
<body> |
| 14357 |
|
| 14358 |
<p> |
| 14359 |
Now that your kernel is configured and compiled and the necessary system |
| 14360 |
configuration files are filled in correctly, it is time to install a |
| 14361 |
program that will fire up your kernel when you start the system. Such a |
| 14362 |
program is called a <e>bootloader</e>. |
| 14363 |
</p> |
| 14364 |
|
| 14365 |
</body> |
| 14366 |
</subsection> |
| 14367 |
</section> |
| 14368 |
<section> |
| 14369 |
<title>Installing the SPARC Bootloader: SILO</title> |
| 14370 |
<body> |
| 14371 |
|
| 14372 |
<p> |
| 14373 |
It is now time to install and configure <uri |
| 14374 |
link="http://www.sparc-boot.org">SILO</uri>, the Sparc Improved boot |
| 14375 |
LOader. |
| 14376 |
</p> |
| 14377 |
|
| 14378 |
<pre caption = "Installing SILO"> |
| 14379 |
# <i>emerge silo</i> |
| 14380 |
</pre> |
| 14381 |
|
| 14382 |
<p> |
| 14383 |
Now open up your favorite editor (we use <c>nano</c> as an example) and |
| 14384 |
create <path>/etc/silo.conf</path>. |
| 14385 |
</p> |
| 14386 |
|
| 14387 |
<pre caption = "Creating /etc/silo.conf"> |
| 14388 |
# <i>nano -w /etc/silo.conf</i> |
| 14389 |
</pre> |
| 14390 |
|
| 14391 |
<p> |
| 14392 |
Below you'll find an example <path>silo.conf</path> file. It uses the |
| 14393 |
partitioning scheme we use throughout this book and |
| 14394 |
<path>kernel-2.4.31</path> as kernelimage. |
| 14395 |
</p> |
| 14396 |
|
| 14397 |
<pre caption = "Example /etc/silo.conf"> |
| 14398 |
partition = 1 <comment># Boot partition (= root partition)</comment> |
| 14399 |
root = /dev/sda1 <comment># Root partition</comment> |
| 14400 |
timeout = 150 <comment># Wait 15 seconds before booting the default section</comment> |
| 14401 |
|
| 14402 |
image = /boot/kernel-2.4.31 |
| 14403 |
label = linux |
| 14404 |
</pre> |
| 14405 |
|
| 14406 |
<p> |
| 14407 |
If you use the example <path>silo.conf</path> delivered by Portage, be |
| 14408 |
sure to comment out <e>all</e> lines that you do not need. |
| 14409 |
</p> |
| 14410 |
|
| 14411 |
<p> |
| 14412 |
If the physical disk on which you want to install SILO (as bootloader) differs |
| 14413 |
from the physical disk on which <path>/etc/silo.conf</path> resides, you must |
| 14414 |
copy over <path>/etc/silo.conf</path> to a partition on that disk. Assuming that |
| 14415 |
<path>/boot</path> is a separate partition on that disk, copy over the |
| 14416 |
configuration file to <path>/boot</path> and run <c>/sbin/silo</c>: |
| 14417 |
</p> |
| 14418 |
|
| 14419 |
<pre caption = "Only if /boot and the SILO destination are not on the same disk"> |
| 14420 |
# <i>cp /etc/silo.conf /boot</i> |
| 14421 |
# <i>/sbin/silo -C /boot/silo.conf</i> |
| 14422 |
/boot/silo.conf appears to be valid |
| 14423 |
</pre> |
| 14424 |
|
| 14425 |
<p> |
| 14426 |
Otherwise just run <c>/sbin/silo</c>: |
| 14427 |
</p> |
| 14428 |
|
| 14429 |
<pre caption = "Run silo"> |
| 14430 |
# <i>/sbin/silo</i> |
| 14431 |
/etc/silo.conf appears to be valid |
| 14432 |
</pre> |
| 14433 |
|
| 14434 |
<p> |
| 14435 |
Now continue with <uri link="#reboot">Rebooting the System</uri>. |
| 14436 |
</p> |
| 14437 |
|
| 14438 |
</body> |
| 14439 |
</section> |
| 14440 |
<section id="reboot"> |
| 14441 |
<title>Rebooting the System</title> |
| 14442 |
<subsection> |
| 14443 |
<body> |
| 14444 |
|
| 14445 |
<p> |
| 14446 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
| 14447 |
that one magical command you have been waiting for: <c>reboot</c>. |
| 14448 |
</p> |
| 14449 |
|
| 14450 |
<pre caption="Exiting the chroot, unmounting all partitions and rebooting"> |
| 14451 |
# <i>exit</i> |
| 14452 |
cdimage ~# <i>cd</i> |
| 14453 |
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
| 14454 |
cdimage ~# <i>reboot</i> |
| 14455 |
</pre> |
| 14456 |
|
| 14457 |
<p> |
| 14458 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
| 14459 |
booted again instead of your new Gentoo system. |
| 14460 |
</p> |
| 14461 |
|
| 14462 |
<p> |
| 14463 |
Once rebooted in your Gentoo installation, finish up with <uri |
| 14464 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
| 14465 |
</p> |
| 14466 |
|
| 14467 |
</body> |
| 14468 |
</subsection> |
| 14469 |
</section> |
| 14470 |
</sections> |
| 14471 |
|
| 14472 |
|
| 14473 |
|
| 14474 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-sparc-disk.xml |
| 14475 |
|
| 14476 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-sparc-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 14477 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-sparc-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 14478 |
|
| 14479 |
Index: hb-install-sparc-disk.xml |
| 14480 |
=================================================================== |
| 14481 |
<?xml version='1.0' encoding='UTF-8'?> |
| 14482 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 14483 |
|
| 14484 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 14485 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 14486 |
|
| 14487 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-sparc-disk.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 14488 |
|
| 14489 |
<sections> |
| 14490 |
|
| 14491 |
<version>5.1</version> |
| 14492 |
<date>2005-08-25</date> |
| 14493 |
|
| 14494 |
<section> |
| 14495 |
<title>Introduction to Block Devices</title> |
| 14496 |
<subsection> |
| 14497 |
<title>Block Devices</title> |
| 14498 |
<body> |
| 14499 |
|
| 14500 |
<p> |
| 14501 |
We'll take a good look at some of the disk-oriented aspects of Gentoo Linux |
| 14502 |
and Linux in general, including Linux filesystems, partitions, and block |
| 14503 |
devices. Then, once you're familiar with the ins and outs of disks and |
| 14504 |
filesystems, you'll be guided through the process of setting up partitions |
| 14505 |
and filesystems for your Gentoo Linux installation. |
| 14506 |
</p> |
| 14507 |
|
| 14508 |
<p> |
| 14509 |
To begin, we introduce <e>block devices</e>. The most typical block device is |
| 14510 |
probably the one that represents the first SCSI hard disk in a Linux system, |
| 14511 |
namely <path>/dev/sda</path>. |
| 14512 |
</p> |
| 14513 |
|
| 14514 |
<p> |
| 14515 |
Block devices represent an abstract interface to the disk. User programs can |
| 14516 |
use these block devices to interact with your disk without worrying about |
| 14517 |
whether your drives are IDE, SCSI, or something else. The program can simply |
| 14518 |
address the storage on the disk as a bunch of contiguous, randomly-accessible |
| 14519 |
512-byte blocks. |
| 14520 |
</p> |
| 14521 |
|
| 14522 |
<p> |
| 14523 |
Block devices show up as entries in <path>/dev/</path>. Typically, the first |
| 14524 |
SCSI drive is named <path>/dev/sda</path>, the second <path>/dev/sdb</path>, |
| 14525 |
and so on. IDE drives are named similarly, however, they are prefixed by hd- |
| 14526 |
instead of sd-. If you are using IDE drives, the first one will be named |
| 14527 |
<path>/dev/hda</path>, the second <path>/dev/hdb</path>, and so on. |
| 14528 |
</p> |
| 14529 |
|
| 14530 |
</body> |
| 14531 |
</subsection> |
| 14532 |
<subsection> |
| 14533 |
<title>Partitions</title> |
| 14534 |
<body> |
| 14535 |
|
| 14536 |
<p> |
| 14537 |
Although it is theoretically possible to use the entire disk to house your Linux |
| 14538 |
system, this is almost never done in practice. Instead, full disk block devices |
| 14539 |
are split up in smaller, more manageable block devices. These are known as |
| 14540 |
<e>partitions</e> or <e>slices</e>. |
| 14541 |
</p> |
| 14542 |
|
| 14543 |
<p> |
| 14544 |
The first partition on the first SCSI disk is <path>/dev/sda1</path>, the second |
| 14545 |
<path>/dev/sda2</path> and so on. Similarly, the first two partitions on the |
| 14546 |
first IDE disk are <path>/dev/hda1</path> and <path>/dev/hda2</path>. |
| 14547 |
</p> |
| 14548 |
|
| 14549 |
<p> |
| 14550 |
The third partition on Sun systems is set aside as a special "whole disk" |
| 14551 |
slice. This partition must not contain a file system. |
| 14552 |
</p> |
| 14553 |
|
| 14554 |
<p> |
| 14555 |
Users who are used to the DOS partitioning scheme should note that Sun |
| 14556 |
disklabels do not have "primary" and "extended" partitions. Instead, up to |
| 14557 |
eight partitions are available per drive, with the third of these being |
| 14558 |
reserved. |
| 14559 |
</p> |
| 14560 |
|
| 14561 |
</body> |
| 14562 |
</subsection> |
| 14563 |
</section> |
| 14564 |
<section> |
| 14565 |
<title>Designing a Partitioning Scheme</title> |
| 14566 |
<subsection> |
| 14567 |
<title>Default Partitioning Scheme</title> |
| 14568 |
<body> |
| 14569 |
|
| 14570 |
<p> |
| 14571 |
If you are not interested in drawing up a partitioning scheme, |
| 14572 |
the table below suggests a suitable starting point for most systems. For |
| 14573 |
IDE-based systems, substitute <c>hda</c> for <c>sda</c> in the following. |
| 14574 |
</p> |
| 14575 |
|
| 14576 |
<p> |
| 14577 |
Note that a separate <path>/boot</path> partition is generally <e>not</e> |
| 14578 |
recommended on SPARC, as it complicates the bootloader configuration. |
| 14579 |
</p> |
| 14580 |
|
| 14581 |
<table> |
| 14582 |
<tr> |
| 14583 |
<th>Partition</th> |
| 14584 |
<th>Filesystem</th> |
| 14585 |
<th>Size</th> |
| 14586 |
<th>Mount Point</th> |
| 14587 |
<th>Description</th> |
| 14588 |
</tr> |
| 14589 |
<tr> |
| 14590 |
<ti>/dev/sda1</ti> |
| 14591 |
<ti>ext3</ti> |
| 14592 |
<ti><2 GByte</ti> |
| 14593 |
<ti>/</ti> |
| 14594 |
<ti> |
| 14595 |
Root partition. For all sparc32 systems, and sparc64 systems with older |
| 14596 |
OBP versions, this <e>must</e> be less than 2 GBytes in size, and the first |
| 14597 |
partition on the disk. |
| 14598 |
</ti> |
| 14599 |
</tr> |
| 14600 |
<tr> |
| 14601 |
<ti>/dev/sda2</ti> |
| 14602 |
<ti>swap</ti> |
| 14603 |
<ti>512 MBytes</ti> |
| 14604 |
<ti>none</ti> |
| 14605 |
<ti> |
| 14606 |
Swap partition. For bootstrap and certain larger compiles, at least 512 |
| 14607 |
MBytes of RAM (including swap) is required. |
| 14608 |
</ti> |
| 14609 |
</tr> |
| 14610 |
<tr> |
| 14611 |
<ti>/dev/sda3</ti> |
| 14612 |
<ti>none</ti> |
| 14613 |
<ti>Whole disk</ti> |
| 14614 |
<ti>none</ti> |
| 14615 |
<ti>Whole disk partition. This is required on SPARC systems.</ti> |
| 14616 |
</tr> |
| 14617 |
<tr> |
| 14618 |
<ti>/dev/sda4</ti> |
| 14619 |
<ti>ext3</ti> |
| 14620 |
<ti>at least 2 GBytes</ti> |
| 14621 |
<ti>/usr</ti> |
| 14622 |
<ti> |
| 14623 |
/usr partition. Applications are installed here. By default this partition |
| 14624 |
is also used for Portage data (which takes around 500 Mbyte excluding |
| 14625 |
source code). |
| 14626 |
</ti> |
| 14627 |
</tr> |
| 14628 |
<tr> |
| 14629 |
<ti>/dev/sda5</ti> |
| 14630 |
<ti>ext3</ti> |
| 14631 |
<ti>at least 1GByte</ti> |
| 14632 |
<ti>/var</ti> |
| 14633 |
<ti> |
| 14634 |
/var partition. Used for program-generated data. By default Portage uses |
| 14635 |
this partition for temporary space whilst compiling. Certain larger |
| 14636 |
applications such as Mozilla and OpenOffice.org can require over 1 GByte |
| 14637 |
of temporary space here when building. |
| 14638 |
</ti> |
| 14639 |
</tr> |
| 14640 |
<tr> |
| 14641 |
<ti>/dev/sda6</ti> |
| 14642 |
<ti>ext3</ti> |
| 14643 |
<ti>remaining space</ti> |
| 14644 |
<ti>/home</ti> |
| 14645 |
<ti>/home partition. Used for users' home directories.</ti> |
| 14646 |
</tr> |
| 14647 |
</table> |
| 14648 |
|
| 14649 |
</body> |
| 14650 |
</subsection> |
| 14651 |
</section> |
| 14652 |
|
| 14653 |
<section id="fdisk"> |
| 14654 |
<title>Using fdisk to Partition your Disk</title> |
| 14655 |
<subsection> |
| 14656 |
<body> |
| 14657 |
|
| 14658 |
<p> |
| 14659 |
The following parts explain how to create the example partition layout described |
| 14660 |
previously, namely: |
| 14661 |
</p> |
| 14662 |
|
| 14663 |
<table> |
| 14664 |
<tr> |
| 14665 |
<th>Partition</th> |
| 14666 |
<th>Description</th> |
| 14667 |
</tr> |
| 14668 |
<tr> |
| 14669 |
<ti>/dev/sda1</ti> |
| 14670 |
<ti>/</ti> |
| 14671 |
</tr> |
| 14672 |
<tr> |
| 14673 |
<ti>/dev/sda2</ti> |
| 14674 |
<ti>swap</ti> |
| 14675 |
</tr> |
| 14676 |
<tr> |
| 14677 |
<ti>/dev/sda3</ti> |
| 14678 |
<ti>whole disk slice</ti> |
| 14679 |
</tr> |
| 14680 |
<tr> |
| 14681 |
<ti>/dev/sda4</ti> |
| 14682 |
<ti>/usr</ti> |
| 14683 |
</tr> |
| 14684 |
<tr> |
| 14685 |
<ti>/dev/sda5</ti> |
| 14686 |
<ti>/var</ti> |
| 14687 |
</tr> |
| 14688 |
<tr> |
| 14689 |
<ti>/dev/sda6</ti> |
| 14690 |
<ti>/home</ti> |
| 14691 |
</tr> |
| 14692 |
</table> |
| 14693 |
|
| 14694 |
<p> |
| 14695 |
Change the partition layout as required. Remember to keep the root partition |
| 14696 |
entirely within the first 2 GBytes of the disk for older systems. There is also |
| 14697 |
a 15-partition limit for SCSI and SATA. |
| 14698 |
</p> |
| 14699 |
|
| 14700 |
</body> |
| 14701 |
</subsection> |
| 14702 |
<subsection> |
| 14703 |
<title>Firing up fdisk</title> |
| 14704 |
<body> |
| 14705 |
|
| 14706 |
<p> |
| 14707 |
Start <c>fdisk</c> with your disk as argument: |
| 14708 |
</p> |
| 14709 |
|
| 14710 |
<pre caption="Starting fdisk"> |
| 14711 |
# <i>fdisk /dev/sda</i> |
| 14712 |
</pre> |
| 14713 |
|
| 14714 |
<p> |
| 14715 |
You should be greeted with the fdisk prompt: |
| 14716 |
</p> |
| 14717 |
|
| 14718 |
<pre caption="The fdisk prompt"> |
| 14719 |
Command (m for help): |
| 14720 |
</pre> |
| 14721 |
|
| 14722 |
<p> |
| 14723 |
To view the available partitions, type in <c>p</c>: |
| 14724 |
</p> |
| 14725 |
|
| 14726 |
<pre caption="Listing available partitions"> |
| 14727 |
Command (m for help): <i>p</i> |
| 14728 |
|
| 14729 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
| 14730 |
Units = cylinders of 2048 * 512 bytes |
| 14731 |
|
| 14732 |
Device Flag Start End Blocks Id System |
| 14733 |
/dev/sda1 0 488 499712 83 Linux native |
| 14734 |
/dev/sda2 488 976 499712 82 Linux swap |
| 14735 |
/dev/sda3 0 8635 8842240 5 Whole disk |
| 14736 |
/dev/sda4 976 1953 1000448 83 Linux native |
| 14737 |
/dev/sda5 1953 2144 195584 83 Linux native |
| 14738 |
/dev/sda6 2144 8635 6646784 83 Linux native |
| 14739 |
</pre> |
| 14740 |
|
| 14741 |
<p> |
| 14742 |
Note the <c>Sun disk label</c> in the output. If this is missing, the disk is |
| 14743 |
using the DOS-partitioning, not the Sun partitioning. In this case, use <c>s</c> |
| 14744 |
to ensure that the disk has a sun partition table: |
| 14745 |
</p> |
| 14746 |
|
| 14747 |
<pre caption="Creating a Sun Disklabel"> |
| 14748 |
Command (m for help): s |
| 14749 |
Building a new sun disklabel. Changes will remain in memory only, |
| 14750 |
until you decide to write them. After that, of course, the previous |
| 14751 |
content won't be recoverable. |
| 14752 |
|
| 14753 |
Drive type |
| 14754 |
? auto configure |
| 14755 |
0 custom (with hardware detected defaults) |
| 14756 |
a Quantum ProDrive 80S |
| 14757 |
b Quantum ProDrive 105S |
| 14758 |
c CDC Wren IV 94171-344 |
| 14759 |
d IBM DPES-31080 |
| 14760 |
e IBM DORS-32160 |
| 14761 |
f IBM DNES-318350 |
| 14762 |
g SEAGATE ST34371 |
| 14763 |
h SUN0104 |
| 14764 |
i SUN0207 |
| 14765 |
j SUN0327 |
| 14766 |
k SUN0340 |
| 14767 |
l SUN0424 |
| 14768 |
m SUN0535 |
| 14769 |
n SUN0669 |
| 14770 |
o SUN1.0G |
| 14771 |
p SUN1.05 |
| 14772 |
q SUN1.3G |
| 14773 |
r SUN2.1G |
| 14774 |
s IOMEGA Jaz |
| 14775 |
Select type (? for auto, 0 for custom): <i>0</i> |
| 14776 |
Heads (1-1024, default 64): |
| 14777 |
Using default value 64 |
| 14778 |
Sectors/track (1-1024, default 32): |
| 14779 |
Using default value 32 |
| 14780 |
Cylinders (1-65535, default 8635): |
| 14781 |
Using default value 8635 |
| 14782 |
Alternate cylinders (0-65535, default 2): |
| 14783 |
Using default value 2 |
| 14784 |
Physical cylinders (0-65535, default 8637): |
| 14785 |
Using default value 8637 |
| 14786 |
Rotation speed (rpm) (1-100000, default 5400): <i>10000</i> |
| 14787 |
Interleave factor (1-32, default 1): |
| 14788 |
Using default value 1 |
| 14789 |
Extra sectors per cylinder (0-32, default 0): |
| 14790 |
Using default value 0 |
| 14791 |
</pre> |
| 14792 |
|
| 14793 |
<p> |
| 14794 |
You can find the correct values in your disk's documentation. The |
| 14795 |
'auto configure' option does not usually work. |
| 14796 |
</p> |
| 14797 |
|
| 14798 |
</body> |
| 14799 |
</subsection> |
| 14800 |
<subsection> |
| 14801 |
<title>Deleting Existing Partitions</title> |
| 14802 |
<body> |
| 14803 |
|
| 14804 |
<p> |
| 14805 |
It's time to delete any existing partitions. To do this, type <c>d</c> and hit |
| 14806 |
Enter. You will then be prompted for the partition number you would like to |
| 14807 |
delete. To delete a pre-existing <path>/dev/sda1</path>, you would type: |
| 14808 |
</p> |
| 14809 |
|
| 14810 |
<pre caption="Deleting a partition"> |
| 14811 |
Command (m for help): <i>d</i> |
| 14812 |
Partition number (1-4): <i>1</i> |
| 14813 |
</pre> |
| 14814 |
|
| 14815 |
<p> |
| 14816 |
<e>You should not delete partition 3 (whole disk).</e> This is required. If |
| 14817 |
this partition does not exist, follow the "Creating a Sun Disklabel" |
| 14818 |
instructions above. |
| 14819 |
</p> |
| 14820 |
|
| 14821 |
<p> |
| 14822 |
After deleting all partitions except the Whole disk slice, you should have a |
| 14823 |
partition layout similar to the following: |
| 14824 |
</p> |
| 14825 |
|
| 14826 |
<pre caption="View an empty partition scheme"> |
| 14827 |
Command (m for help): <i>p</i> |
| 14828 |
|
| 14829 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
| 14830 |
Units = cylinders of 2048 * 512 bytes |
| 14831 |
|
| 14832 |
Device Flag Start End Blocks Id System |
| 14833 |
/dev/sda3 0 8635 8842240 5 Whole disk |
| 14834 |
</pre> |
| 14835 |
|
| 14836 |
|
| 14837 |
</body> |
| 14838 |
</subsection> |
| 14839 |
|
| 14840 |
<subsection> |
| 14841 |
<title>Creating the Root Partition</title> |
| 14842 |
<body> |
| 14843 |
|
| 14844 |
<p> |
| 14845 |
We're ready to create the root partition. To do this, type <c>n</c> to create a |
| 14846 |
new partition, then type <c>1</c> to create the partition. When prompted for |
| 14847 |
the first cylinder, hit enter. When prompted for the last cylinder, type |
| 14848 |
<c>+512M</c> to create a partition <c>512MBytes</c> in size. Make sure that the |
| 14849 |
entire root partition fits within the first 2GBytes of the disk. You can see |
| 14850 |
output from these steps below: |
| 14851 |
</p> |
| 14852 |
|
| 14853 |
<pre caption="Creating a root partition"> |
| 14854 |
Command (m for help): <i>n</i> |
| 14855 |
Partition number (1-8): <i>1</i> |
| 14856 |
First cylinder (0-8635): <i>(press Enter)</i> |
| 14857 |
Last cylinder or +size or +sizeM or +sizeK (0-8635, default 8635): <i>+512M</i> |
| 14858 |
</pre> |
| 14859 |
|
| 14860 |
<p> |
| 14861 |
Now, when you type <c>p</c>, you should see the following partition printout: |
| 14862 |
</p> |
| 14863 |
|
| 14864 |
<pre caption="Listing the partition layout"> |
| 14865 |
Command (m for help): <i>p</i> |
| 14866 |
|
| 14867 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
| 14868 |
Units = cylinders of 2048 * 512 bytes |
| 14869 |
|
| 14870 |
Device Flag Start End Blocks Id System |
| 14871 |
/dev/sda1 0 488 499712 83 Linux native |
| 14872 |
/dev/sda3 0 8635 8842240 5 Whole disk |
| 14873 |
</pre> |
| 14874 |
|
| 14875 |
</body> |
| 14876 |
</subsection> |
| 14877 |
<subsection> |
| 14878 |
<title>Creating a swap partition</title> |
| 14879 |
<body> |
| 14880 |
|
| 14881 |
<p> |
| 14882 |
Next, let's create the swap partition. To do this, type <c>n</c> to create a new |
| 14883 |
partition, then <c>2</c> to create the second partition, <path>/dev/sda2</path> |
| 14884 |
in our case. When prompted for the first cylinder, hit enter. When prompted for |
| 14885 |
the last cylinder, type <c>+512M</c> to create a partition 512MB in size. After |
| 14886 |
you've done this, type <c>t</c> to set the partition type, and then type in |
| 14887 |
<c>82</c> to set the partition type to "Linux Swap". After completing these |
| 14888 |
steps, typing <c>p</c> should display a partition table that looks similar to |
| 14889 |
this: |
| 14890 |
</p> |
| 14891 |
|
| 14892 |
<pre caption="Listing of available partitions"> |
| 14893 |
Command (m for help): <i>p</i> |
| 14894 |
|
| 14895 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
| 14896 |
Units = cylinders of 2048 * 512 bytes |
| 14897 |
|
| 14898 |
Device Flag Start End Blocks Id System |
| 14899 |
/dev/sda1 0 488 499712 83 Linux native |
| 14900 |
/dev/sda2 488 976 499712 82 Linux swap |
| 14901 |
/dev/sda3 0 8635 8842240 5 Whole disk |
| 14902 |
</pre> |
| 14903 |
|
| 14904 |
</body> |
| 14905 |
</subsection> |
| 14906 |
<subsection> |
| 14907 |
<title>Creating the /usr, /var and /home partitions</title> |
| 14908 |
<body> |
| 14909 |
|
| 14910 |
<p> |
| 14911 |
Finally, let's create the /usr, /var and /home partitions. As before, |
| 14912 |
type <c>n</c> to create a new partition, then type <c>4</c> to create the |
| 14913 |
third partition, <path>/dev/sda4</path> in our case. When prompted for the |
| 14914 |
first cylinder, hit enter. When prompted for the last cylinder, enter |
| 14915 |
<c>+2048M</c> to create a partition 2 GBytes in size. Repeat this process |
| 14916 |
for <path>sda5</path> and <path>sda6</path>, using the desired sizes. Once |
| 14917 |
you're done, you should see something like this: |
| 14918 |
</p> |
| 14919 |
|
| 14920 |
<pre caption="Listing complete partition table"> |
| 14921 |
Command (m for help): <i>p</i> |
| 14922 |
|
| 14923 |
Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 8635 cylinders |
| 14924 |
Units = cylinders of 2048 * 512 bytes |
| 14925 |
|
| 14926 |
Device Flag Start End Blocks Id System |
| 14927 |
/dev/sda1 0 488 499712 83 Linux native |
| 14928 |
/dev/sda2 488 976 499712 82 Linux swap |
| 14929 |
/dev/sda3 0 8635 8842240 5 Whole disk |
| 14930 |
/dev/sda4 976 1953 1000448 83 Linux native |
| 14931 |
/dev/sda5 1953 2144 195584 83 Linux native |
| 14932 |
/dev/sda6 2144 8635 6646784 83 Linux native |
| 14933 |
</pre> |
| 14934 |
|
| 14935 |
</body> |
| 14936 |
</subsection> |
| 14937 |
<subsection> |
| 14938 |
<title>Save and Exit</title> |
| 14939 |
<body> |
| 14940 |
|
| 14941 |
<p> |
| 14942 |
To save your partition layout and exit <c>fdisk</c>, type <c>w</c>: |
| 14943 |
</p> |
| 14944 |
|
| 14945 |
<pre caption="Save and exit fdisk"> |
| 14946 |
Command (m for help): <i>w</i> |
| 14947 |
</pre> |
| 14948 |
|
| 14949 |
<p> |
| 14950 |
Now that your partitions are created, you can now continue with <uri |
| 14951 |
link="#filesystems">Creating Filesystems</uri>. |
| 14952 |
</p> |
| 14953 |
|
| 14954 |
</body> |
| 14955 |
</subsection> |
| 14956 |
</section> |
| 14957 |
<section id="filesystems"> |
| 14958 |
<title>Creating Filesystems</title> |
| 14959 |
<subsection> |
| 14960 |
<title>Introduction</title> |
| 14961 |
<body> |
| 14962 |
|
| 14963 |
<p> |
| 14964 |
Now that your partitions are created, it is time to place a filesystem on them. |
| 14965 |
If you don't care about what filesystem to choose and are happy with what is |
| 14966 |
used as default in this handbook, continue with <uri |
| 14967 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
| 14968 |
Otherwise, read on to learn about the available filesystems... |
| 14969 |
</p> |
| 14970 |
|
| 14971 |
</body> |
| 14972 |
</subsection> |
| 14973 |
<subsection> |
| 14974 |
<title>Filesystems?</title> |
| 14975 |
<body> |
| 14976 |
|
| 14977 |
<p> |
| 14978 |
Several filesystems are available, some are known to be stable on the |
| 14979 |
SPARC architecture. Ext2 and ext3, for example, are known to work well. |
| 14980 |
Alternate filesystems may not function correctly. |
| 14981 |
</p> |
| 14982 |
|
| 14983 |
<p> |
| 14984 |
<b>ext2</b> is the tried-and-true Linux filesystem. It does not support |
| 14985 |
journaling, which means that periodic checks of ext2 filesystems at startup |
| 14986 |
can be quite time-consuming. There is quite a selection of newer-generation |
| 14987 |
journaled filesystems that can be checked for consistency very quickly at |
| 14988 |
startup, and are therefore generally preferred over their non-journaled |
| 14989 |
counterparts. In general, journaled filesystems prevent long delays when a |
| 14990 |
system is booted and the filesystem is in an inconsistent state. |
| 14991 |
</p> |
| 14992 |
|
| 14993 |
<p> |
| 14994 |
<b>ext3</b> is the journaled version of the ext2 filesystem. It provides |
| 14995 |
metadata journaling for fast recovery as well as other enhanced journaling |
| 14996 |
modes like full-data and ordered-data journaling. Ext3 has an additional hashed |
| 14997 |
b-tree indexing option that enables high performance in almost all situations. |
| 14998 |
You can enable this indexing by adding <c>-O dir_index</c> to the <c>mke2fs</c> |
| 14999 |
command. Ext3 makes an excellent and reliable alternative to ext2. |
| 15000 |
</p> |
| 15001 |
|
| 15002 |
</body> |
| 15003 |
</subsection> |
| 15004 |
<subsection id="filesystems-apply"> |
| 15005 |
<title>Applying a Filesystem to a Partition</title> |
| 15006 |
<body> |
| 15007 |
|
| 15008 |
<p> |
| 15009 |
To create a filesystem on a partition or volume, tools specific to the chosen |
| 15010 |
filesystem are available: |
| 15011 |
</p> |
| 15012 |
|
| 15013 |
<table> |
| 15014 |
<tr> |
| 15015 |
<th>Filesystem</th> |
| 15016 |
<th>Creation Command</th> |
| 15017 |
</tr> |
| 15018 |
<tr> |
| 15019 |
<ti>ext2</ti> |
| 15020 |
<ti><c>mke2fs</c></ti> |
| 15021 |
</tr> |
| 15022 |
<tr> |
| 15023 |
<ti>ext3</ti> |
| 15024 |
<ti><c>mke2fs -j</c></ti> |
| 15025 |
</tr> |
| 15026 |
<tr> |
| 15027 |
<ti>ext3 with hashed b-tree indexing (2.6 kernels only)</ti> |
| 15028 |
<ti><c>mke2fs -j -O dir_index</c></ti> |
| 15029 |
</tr> |
| 15030 |
</table> |
| 15031 |
|
| 15032 |
<p> |
| 15033 |
For instance, to create the root partition (<path>/dev/sda1</path> in our |
| 15034 |
example) as ext2, and the <path>/usr</path>, <path>/var</path>, and |
| 15035 |
<path>/home</path> partitions (<path>/dev/sda4</path>, <path>5</path> |
| 15036 |
and <path>6</path> in our example, respectively) as ext3, you would use: |
| 15037 |
</p> |
| 15038 |
|
| 15039 |
<pre caption="Applying a filesystem on a partition"> |
| 15040 |
# <i>mke2fs /dev/sda1</i> |
| 15041 |
# <i>mke2fs -j /dev/sda4</i> |
| 15042 |
# <i>mke2fs -j /dev/sda5</i> |
| 15043 |
# <i>mke2fs -j /dev/sda6</i> |
| 15044 |
</pre> |
| 15045 |
|
| 15046 |
</body> |
| 15047 |
</subsection> |
| 15048 |
<subsection> |
| 15049 |
<title>Activating the Swap Partition</title> |
| 15050 |
<body> |
| 15051 |
|
| 15052 |
<p> |
| 15053 |
<c>mkswap</c> is the command used to initialize swap partitions: |
| 15054 |
</p> |
| 15055 |
|
| 15056 |
<pre caption="Creating a Swap signature"> |
| 15057 |
# <i>mkswap /dev/sda2</i> |
| 15058 |
</pre> |
| 15059 |
|
| 15060 |
<p> |
| 15061 |
To activate the swap partition, use <c>swapon</c>: |
| 15062 |
</p> |
| 15063 |
|
| 15064 |
<pre caption="Activating the swap partition"> |
| 15065 |
# <i>swapon /dev/sda2</i> |
| 15066 |
</pre> |
| 15067 |
|
| 15068 |
<p> |
| 15069 |
Create and activate the swap now. |
| 15070 |
</p> |
| 15071 |
|
| 15072 |
</body> |
| 15073 |
</subsection> |
| 15074 |
</section> |
| 15075 |
<section> |
| 15076 |
<title>Mounting</title> |
| 15077 |
<body> |
| 15078 |
|
| 15079 |
<p> |
| 15080 |
Now that your partitions are initialized and are housing a filesystem, it is |
| 15081 |
time to mount them using the <c>mount</c> command. Don't forget to first |
| 15082 |
create the necessary mount directories for every partition you created. For |
| 15083 |
example: |
| 15084 |
</p> |
| 15085 |
|
| 15086 |
<pre caption="Mounting partitions"> |
| 15087 |
# <i>mount /dev/sda1 /mnt/gentoo</i> |
| 15088 |
# <i>mkdir /mnt/gentoo/usr</i> |
| 15089 |
# <i>mount /dev/sda4 /mnt/gentoo/usr</i> |
| 15090 |
# <i>mkdir /mnt/gentoo/var</i> |
| 15091 |
# <i>mount /dev/sda5 /mnt/gentoo/var</i> |
| 15092 |
# <i>mkdir /mnt/gentoo/home</i> |
| 15093 |
# <i>mount /dev/sda6 /mnt/gentoo/home</i> |
| 15094 |
</pre> |
| 15095 |
|
| 15096 |
<note> |
| 15097 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure |
| 15098 |
to change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. |
| 15099 |
This also holds for <path>/var/tmp</path>. |
| 15100 |
</note> |
| 15101 |
|
| 15102 |
<p> |
| 15103 |
We will also have to mount the proc filesystem (a virtual interface with the |
| 15104 |
kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. |
| 15105 |
</p> |
| 15106 |
|
| 15107 |
<p> |
| 15108 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
| 15109 |
Installation Files</uri>. |
| 15110 |
</p> |
| 15111 |
|
| 15112 |
</body> |
| 15113 |
</section> |
| 15114 |
</sections> |
| 15115 |
|
| 15116 |
|
| 15117 |
|
| 15118 |
|
| 15119 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-sparc-kernel.xml |
| 15120 |
|
| 15121 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-sparc-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 15122 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-sparc-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 15123 |
|
| 15124 |
Index: hb-install-sparc-kernel.xml |
| 15125 |
=================================================================== |
| 15126 |
<?xml version='1.0' encoding='UTF-8'?> |
| 15127 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 15128 |
|
| 15129 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 15130 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 15131 |
|
| 15132 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-sparc-kernel.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 15133 |
|
| 15134 |
<sections> |
| 15135 |
|
| 15136 |
<version>5.5</version> |
| 15137 |
<date>2006-01-06</date> |
| 15138 |
|
| 15139 |
<section> |
| 15140 |
<title>Timezone</title> |
| 15141 |
<body> |
| 15142 |
|
| 15143 |
<p> |
| 15144 |
You first need to select your timezone so that your system knows where it is |
| 15145 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
| 15146 |
it to <path>/etc/localtime</path>. Please avoid the |
| 15147 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
| 15148 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
| 15149 |
</p> |
| 15150 |
|
| 15151 |
<pre caption="Setting the timezone information"> |
| 15152 |
# <i>ls /usr/share/zoneinfo</i> |
| 15153 |
<comment>(Suppose you want to use GMT)</comment> |
| 15154 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
| 15155 |
</pre> |
| 15156 |
|
| 15157 |
</body> |
| 15158 |
</section> |
| 15159 |
<section> |
| 15160 |
<title>Installing the Sources</title> |
| 15161 |
<subsection> |
| 15162 |
<title>Choosing a Kernel</title> |
| 15163 |
<body> |
| 15164 |
|
| 15165 |
<p> |
| 15166 |
The core around which all distributions are built is the Linux kernel. It is the |
| 15167 |
layer between the user programs and your system hardware. Gentoo provides its |
| 15168 |
users several possible kernel sources. A full listing with description is |
| 15169 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
| 15170 |
Guide</uri>. |
| 15171 |
</p> |
| 15172 |
|
| 15173 |
<p> |
| 15174 |
For sparc-based systems we have <c>sparc-sources</c> (kernel source optimized |
| 15175 |
for SPARC users) and <c>vanilla-sources</c> (the default kernel source as |
| 15176 |
developed by the linux-kernel developers). |
| 15177 |
</p> |
| 15178 |
|
| 15179 |
<p> |
| 15180 |
In the next example we install the <c>sparc-sources</c>. Of course substitute |
| 15181 |
with your choice of sources, this is merely an example. The <c>USE="-doc"</c> |
| 15182 |
is necessary to avoid installing xorg-x11 or other dependencies at this point. |
| 15183 |
<c>USE="symlink"</c> is not necessary for a new install, but ensures proper |
| 15184 |
creation of the <path>/usr/src/linux</path> symlink. |
| 15185 |
</p> |
| 15186 |
|
| 15187 |
<pre caption="Installing a kernel source"> |
| 15188 |
# <i>USE="-doc symlink" emerge sparc-sources</i> |
| 15189 |
</pre> |
| 15190 |
|
| 15191 |
<p> |
| 15192 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
| 15193 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
| 15194 |
kernel source points to <c>sparc-sources-2.4.31</c>. Your version may be |
| 15195 |
different, so keep this in mind. |
| 15196 |
</p> |
| 15197 |
|
| 15198 |
<pre caption="Viewing the kernel source symlink"> |
| 15199 |
# <i>ls -l /usr/src/linux</i> |
| 15200 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-2.4.31-sparc |
| 15201 |
</pre> |
| 15202 |
|
| 15203 |
<p> |
| 15204 |
Now it is time to configure and compile your kernel source. |
| 15205 |
</p> |
| 15206 |
|
| 15207 |
</body> |
| 15208 |
</subsection> |
| 15209 |
</section> |
| 15210 |
<section> |
| 15211 |
<title>Manual Configuration</title> |
| 15212 |
<subsection> |
| 15213 |
<title>Introduction</title> |
| 15214 |
<body> |
| 15215 |
|
| 15216 |
<p> |
| 15217 |
Manually configuring a kernel is often seen as the most difficult procedure a |
| 15218 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
| 15219 |
couple of kernels you don't even remember that it was difficult ;) |
| 15220 |
</p> |
| 15221 |
|
| 15222 |
<p> |
| 15223 |
However, one thing <e>is</e> true: you must know your system when you start |
| 15224 |
configuring a kernel manually. Most information can be gathered by emerging |
| 15225 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
| 15226 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
| 15227 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
| 15228 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
| 15229 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
| 15230 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
| 15231 |
uses (it might provide you with a nice hint on what to enable). |
| 15232 |
</p> |
| 15233 |
|
| 15234 |
<p> |
| 15235 |
Now go to your kernel source directory and execute <c>make menuconfig</c>. This |
| 15236 |
will fire up an ncurses-based configuration menu. |
| 15237 |
</p> |
| 15238 |
|
| 15239 |
<pre caption="Invoking menuconfig"> |
| 15240 |
# <i>cd /usr/src/linux</i> |
| 15241 |
# <i>make menuconfig</i> |
| 15242 |
</pre> |
| 15243 |
|
| 15244 |
<p> |
| 15245 |
You will be greeted with several configuration sections. We'll first list some |
| 15246 |
options you must activate (otherwise Gentoo will not function, or not function |
| 15247 |
properly without additional tweaks). |
| 15248 |
</p> |
| 15249 |
|
| 15250 |
</body> |
| 15251 |
</subsection> |
| 15252 |
<subsection> |
| 15253 |
<title>Activating Required Options</title> |
| 15254 |
<body> |
| 15255 |
|
| 15256 |
<p> |
| 15257 |
First of all, activate the use of development and experimental code/drivers. |
| 15258 |
You need this, otherwise some very important code/drivers won't show up: |
| 15259 |
</p> |
| 15260 |
|
| 15261 |
<pre caption="Selecting experimental code/drivers"> |
| 15262 |
Code maturity level options ---> |
| 15263 |
[*] Prompt for development and/or incomplete code/drivers |
| 15264 |
</pre> |
| 15265 |
|
| 15266 |
<p> |
| 15267 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
| 15268 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
| 15269 |
able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc |
| 15270 |
file system</c>. If you are running a 2.4 kernel, you should also select |
| 15271 |
<c>/dev file system</c> + <c>Automatically mount at boot</c>: |
| 15272 |
</p> |
| 15273 |
|
| 15274 |
<pre caption="Selecting necessary file systems"> |
| 15275 |
File systems ---> |
| 15276 |
[*] Virtual memory file system support (former shm fs) |
| 15277 |
[*] /proc file system support |
| 15278 |
[ ] /dev/pts file system for Unix98 PTYs |
| 15279 |
|
| 15280 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
| 15281 |
<*> Ext3 journalling file system support |
| 15282 |
<*> Second extended fs support |
| 15283 |
</pre> |
| 15284 |
|
| 15285 |
<p> |
| 15286 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
| 15287 |
modem, you will need the following options in the kernel: |
| 15288 |
</p> |
| 15289 |
|
| 15290 |
<pre caption="Selecting PPPoE necessary drivers"> |
| 15291 |
Network device support ---> |
| 15292 |
<*> PPP (point-to-point protocol) support |
| 15293 |
<*> PPP support for async serial ports |
| 15294 |
<*> PPP support for sync tty ports |
| 15295 |
</pre> |
| 15296 |
|
| 15297 |
<p> |
| 15298 |
The two compression options won't harm but are not definitely needed, neither |
| 15299 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
| 15300 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
| 15301 |
</p> |
| 15302 |
|
| 15303 |
<p> |
| 15304 |
Now activate the correct bus-support: |
| 15305 |
</p> |
| 15306 |
|
| 15307 |
<pre caption="Activating SBUS/UPA"> |
| 15308 |
Console drivers ---> |
| 15309 |
Frame-buffer support ---> |
| 15310 |
[*] SBUS and UPA framebuffers |
| 15311 |
[*] Creator/Creator3D support <comment>(Only for UPA slot adapter used in many Ultras)</comment> |
| 15312 |
[*] CGsix (GX,TurboGX) support <comment>(Only for SBUS slot adapter used in many SPARCStations)</comment> |
| 15313 |
</pre> |
| 15314 |
|
| 15315 |
<p> |
| 15316 |
Of course you want support for the OBP: |
| 15317 |
</p> |
| 15318 |
|
| 15319 |
<pre caption="Activating OBP Support"> |
| 15320 |
Misc Linux/SPARC drivers ---> |
| 15321 |
[*] /dev/openprom device support |
| 15322 |
</pre> |
| 15323 |
|
| 15324 |
<p> |
| 15325 |
You will also need SCSI-specific support: |
| 15326 |
</p> |
| 15327 |
|
| 15328 |
<pre caption="Activating SCSI-specific support"> |
| 15329 |
SCSI support ---> |
| 15330 |
SCSI low-level drivers ---> |
| 15331 |
<*> Sparc ESP Scsi Driver <comment>(Only for SPARC ESP on-board SCSI adapter)</comment> |
| 15332 |
<*> PTI Qlogic, ISP Driver <comment>(Only for SBUS SCSI controllers from PTI or QLogic)</comment> |
| 15333 |
<*> SYM53C8XX Version 2 SCSI support <comment>(Only for Ultra 60 on-board SCSI adapter)</comment> |
| 15334 |
</pre> |
| 15335 |
|
| 15336 |
<p> |
| 15337 |
To support your network card, select one of the following: |
| 15338 |
</p> |
| 15339 |
|
| 15340 |
<pre caption="Activating networking support"> |
| 15341 |
Network device support ---> |
| 15342 |
Ethernet (10 or 100Mbit) ---> |
| 15343 |
<*> Sun LANCE support <comment>(Only for SPARCStation, older Ultra systems, and as Sbus option)</comment> |
| 15344 |
<*> Sun Happy Meal 10/100baseT support <comment>(Only for Ultra; also supports "qfe" quad-ethernet on PCI and Sbus)</comment> |
| 15345 |
<*> DECchip Tulip (dc21x4x) PCI support <comment>(For some Netras, like N1)</comment> |
| 15346 |
Ethernet (1000Mbit) ---> |
| 15347 |
<*> Broadcom Tigon3 support <comment>(Modern Netra, Sun Fire machines)</comment> |
| 15348 |
</pre> |
| 15349 |
|
| 15350 |
<p> |
| 15351 |
When you have a 4-port Ethernet machine (10/100 or 10/100/1000) the port order |
| 15352 |
is different from the one used by Solaris. You can use <c>sys-apps/ethtool</c> |
| 15353 |
or <c>mii-tool</c> to check the port link status. |
| 15354 |
</p> |
| 15355 |
|
| 15356 |
<p> |
| 15357 |
When you're done configuring your kernel, continue with <uri |
| 15358 |
link="#compiling">Compiling and Installing</uri>. However, after having |
| 15359 |
compiled the kernel, check its size: |
| 15360 |
</p> |
| 15361 |
|
| 15362 |
<pre caption="Check kernel size"> |
| 15363 |
# <i>ls -lh vmlinux</i> |
| 15364 |
-rw-r--r-- 1 root root 2.4M Oct 25 14:38 vmlinux |
| 15365 |
</pre> |
| 15366 |
|
| 15367 |
<p> |
| 15368 |
If the (uncompressed) size is bigger than 2.5 MB (for Sparc32) or 3.5 MB (for |
| 15369 |
Sparc64), reconfigure your kernel until it doesn't exceed these limits. One way |
| 15370 |
of accomplishing this is by having most kernel drivers compiled as modules. |
| 15371 |
Ignoring this can lead to a non-booting kernel. |
| 15372 |
</p> |
| 15373 |
|
| 15374 |
<p> |
| 15375 |
Also, if your kernel is just a tad too big, you can try stripping it using the |
| 15376 |
<c>strip</c> command: |
| 15377 |
</p> |
| 15378 |
|
| 15379 |
<pre caption="Stripping the kernel"> |
| 15380 |
# <i>strip -R .comment -R .note vmlinux</i> |
| 15381 |
</pre> |
| 15382 |
|
| 15383 |
</body> |
| 15384 |
</subsection> |
| 15385 |
<subsection id="compiling"> |
| 15386 |
<title>Compiling and Installing</title> |
| 15387 |
<body> |
| 15388 |
|
| 15389 |
<p> |
| 15390 |
Now that your kernel is configured, it is time to compile and install it. Exit |
| 15391 |
the configuration and start the compilation process: |
| 15392 |
</p> |
| 15393 |
|
| 15394 |
<pre caption="Compiling the kernel"> |
| 15395 |
<comment>(sparc32)</comment> |
| 15396 |
# <i>make dep && make clean vmlinux modules modules_install</i> |
| 15397 |
|
| 15398 |
<comment>(sparc64)</comment> |
| 15399 |
# <i>make dep && make clean vmlinux image modules modules_install</i> |
| 15400 |
</pre> |
| 15401 |
|
| 15402 |
<p> |
| 15403 |
When the kernel has finished compiling, copy the kernel image to |
| 15404 |
<path>/boot</path>. Remember to replace <path><kernel-version></path> |
| 15405 |
with your actual kernel version. |
| 15406 |
</p> |
| 15407 |
|
| 15408 |
<pre caption="Installing the kernel"> |
| 15409 |
<comment>(sparc32)</comment> |
| 15410 |
# <i>cp vmlinux /boot/<kernel-version></i> |
| 15411 |
|
| 15412 |
<comment>(sparc64)</comment> |
| 15413 |
# <i>cp arch/sparc64/boot/image /boot/<kernel-version></i> |
| 15414 |
</pre> |
| 15415 |
|
| 15416 |
<p> |
| 15417 |
Now continue with <uri link="#kernel_modules">Installing Separate Kernel |
| 15418 |
Modules</uri>. |
| 15419 |
</p> |
| 15420 |
|
| 15421 |
</body> |
| 15422 |
</subsection> |
| 15423 |
</section> |
| 15424 |
<section id="kernel_modules"> |
| 15425 |
<title>Installing Separate Kernel Modules</title> |
| 15426 |
<subsection> |
| 15427 |
<title>Configuring the Modules</title> |
| 15428 |
<body> |
| 15429 |
|
| 15430 |
<p> |
| 15431 |
You should list the modules you want automatically loaded in |
| 15432 |
<path>/etc/modules.autoload.d/kernel-2.4</path>. |
| 15433 |
You can add extra options to the modules too if you want. |
| 15434 |
</p> |
| 15435 |
|
| 15436 |
<p> |
| 15437 |
To view all available modules, run the following <c>find</c> command. Don't |
| 15438 |
forget to substitute "<kernel version>" with the version of the kernel you |
| 15439 |
just compiled: |
| 15440 |
</p> |
| 15441 |
|
| 15442 |
<pre caption="Viewing all available modules"> |
| 15443 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
| 15444 |
</pre> |
| 15445 |
|
| 15446 |
<p> |
| 15447 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
| 15448 |
<path>kernel-2.4</path> file and enter the module name in it. |
| 15449 |
</p> |
| 15450 |
|
| 15451 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.4"> |
| 15452 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.4</i> |
| 15453 |
</pre> |
| 15454 |
|
| 15455 |
<pre caption="/etc/modules.autoload.d/kernel-2.4"> |
| 15456 |
3c59x |
| 15457 |
</pre> |
| 15458 |
|
| 15459 |
<p> |
| 15460 |
Continue the installation with <uri link="?part=1&chap=8">Configuring |
| 15461 |
your System</uri>. |
| 15462 |
</p> |
| 15463 |
|
| 15464 |
</body> |
| 15465 |
</subsection> |
| 15466 |
</section> |
| 15467 |
</sections> |
| 15468 |
|
| 15469 |
|
| 15470 |
|
| 15471 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-sparc-medium.xml |
| 15472 |
|
| 15473 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-sparc-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 15474 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-sparc-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 15475 |
|
| 15476 |
Index: hb-install-sparc-medium.xml |
| 15477 |
=================================================================== |
| 15478 |
<?xml version='1.0' encoding='UTF-8'?> |
| 15479 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 15480 |
|
| 15481 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 15482 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 15483 |
|
| 15484 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-sparc-medium.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 15485 |
|
| 15486 |
<sections> |
| 15487 |
|
| 15488 |
<version>5.4</version> |
| 15489 |
<date>2005-11-29</date> |
| 15490 |
|
| 15491 |
<section> |
| 15492 |
<title>Hardware Requirements</title> |
| 15493 |
<subsection> |
| 15494 |
<title>Introduction</title> |
| 15495 |
<body> |
| 15496 |
|
| 15497 |
<p> |
| 15498 |
Before we start, we first list what hardware requirements you need to |
| 15499 |
successfully install Gentoo on your box. |
| 15500 |
</p> |
| 15501 |
|
| 15502 |
</body> |
| 15503 |
</subsection> |
| 15504 |
<subsection> |
| 15505 |
<title>Hardware Requirements</title> |
| 15506 |
<body> |
| 15507 |
|
| 15508 |
<table> |
| 15509 |
<tr> |
| 15510 |
<th>Sparc System</th> |
| 15511 |
<ti> |
| 15512 |
Please check the <uri |
| 15513 |
link="http://www.ultralinux.org/faq.html#s_2">UltraLinux FAQ</uri> |
| 15514 |
</ti> |
| 15515 |
</tr> |
| 15516 |
<tr> |
| 15517 |
<th>CPU</th> |
| 15518 |
<ti> |
| 15519 |
Although sparc64 is the only officially supported platform, experimental |
| 15520 |
support for sparc32 is available as well |
| 15521 |
</ti> |
| 15522 |
</tr> |
| 15523 |
<tr> |
| 15524 |
<th>Memory</th> |
| 15525 |
<ti>64 MB</ti> |
| 15526 |
</tr> |
| 15527 |
<tr> |
| 15528 |
<th>Diskspace</th> |
| 15529 |
<ti>1.5 GB (excluding swap space)</ti> |
| 15530 |
</tr> |
| 15531 |
<tr> |
| 15532 |
<th>Swap space</th> |
| 15533 |
<ti>At least 256 MB</ti> |
| 15534 |
</tr> |
| 15535 |
</table> |
| 15536 |
|
| 15537 |
<p> |
| 15538 |
We currently only provide Installation CDs for the sparc64 architecture. Users |
| 15539 |
of sparc32 can use the experimental netboot images to install Gentoo from. |
| 15540 |
More information about netbooting can be found in our <uri |
| 15541 |
link="/doc/en/gentoo-sparc-netboot-howto.xml">Gentoo Linux based Netboot |
| 15542 |
HOWTO</uri>. |
| 15543 |
</p> |
| 15544 |
|
| 15545 |
</body> |
| 15546 |
</subsection> |
| 15547 |
</section> |
| 15548 |
<!-- Copy/Paste from hb-install-x86-medium.xml --> |
| 15549 |
<!-- START --> |
| 15550 |
<section> |
| 15551 |
<title>The Gentoo Universal Installation CD</title> |
| 15552 |
<subsection> |
| 15553 |
<title>Introduction</title> |
| 15554 |
<body> |
| 15555 |
|
| 15556 |
<p> |
| 15557 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
| 15558 |
Such a tarball is an archive that contains a minimal environment from |
| 15559 |
which you can succesfully install Gentoo Linux onto your system. |
| 15560 |
</p> |
| 15561 |
|
| 15562 |
<p> |
| 15563 |
Installations using a stage1 or stage2 tarball file are not documented in the |
| 15564 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
| 15565 |
FAQ</uri> on these matters. |
| 15566 |
</p> |
| 15567 |
|
| 15568 |
</body> |
| 15569 |
</subsection> |
| 15570 |
<subsection> |
| 15571 |
<title>Gentoo Universal Installation CD</title> |
| 15572 |
<body> |
| 15573 |
|
| 15574 |
<p> |
| 15575 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
| 15576 |
environment. It allows you to boot Linux from the CD. During the boot process |
| 15577 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
| 15578 |
Installation CDs are maintained by Gentoo developers. |
| 15579 |
</p> |
| 15580 |
|
| 15581 |
<p> |
| 15582 |
There currently are two Installation CDs available: |
| 15583 |
</p> |
| 15584 |
|
| 15585 |
<ul> |
| 15586 |
<li> |
| 15587 |
The Universal Installation CD contains everything you need to install |
| 15588 |
Gentoo. It provides stage3 files for common architectures, source code |
| 15589 |
for the extra applications you need to choose from and, of course, the |
| 15590 |
installation instructions for your architecture. |
| 15591 |
</li> |
| 15592 |
<li> |
| 15593 |
The Minimal Installation CD contains only a minimal environment that allows |
| 15594 |
you to boot up and configure your network so you can connect to the |
| 15595 |
Internet. It does not contain any additional files and cannot be used |
| 15596 |
during the current installation approach. |
| 15597 |
</li> |
| 15598 |
</ul> |
| 15599 |
|
| 15600 |
<p> |
| 15601 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
| 15602 |
additional resource that you can exploit during the installation of your Gentoo |
| 15603 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
| 15604 |
you to easily and quickly install additional applications (such as |
| 15605 |
OpenOffice.org, KDE, GNOME, ...) immediately after the Gentoo installation and |
| 15606 |
right before you update your Portage tree. |
| 15607 |
</p> |
| 15608 |
|
| 15609 |
<p> |
| 15610 |
The use of the Package CD is covered later in this document. |
| 15611 |
</p> |
| 15612 |
|
| 15613 |
</body> |
| 15614 |
</subsection> |
| 15615 |
</section> |
| 15616 |
<!-- STOP --> |
| 15617 |
<section> |
| 15618 |
<title>Download, Burn and Boot a Gentoo Installation CD</title> |
| 15619 |
<subsection> |
| 15620 |
<title>Downloading and Burning the Installation CDs</title> |
| 15621 |
<body> |
| 15622 |
|
| 15623 |
<p> |
| 15624 |
You can download the Universal Installation CD (and, if you want to, the |
| 15625 |
Packages CD as well) from one of our <uri |
| 15626 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located in |
| 15627 |
the <path>releases/sparc/2006.0-r1/sparc64/installcd</path> |
| 15628 |
directory; the Package CDs are located in the |
| 15629 |
<path>releases/sparc/2006.0/sparc64/packagecd</path> directory. |
| 15630 |
</p> |
| 15631 |
|
| 15632 |
<p> |
| 15633 |
Inside those directories you'll find ISO-files. Those are full CD images which |
| 15634 |
you can write on a CD-R. |
| 15635 |
</p> |
| 15636 |
|
| 15637 |
<p> |
| 15638 |
After downloading the file, you can verify its integrity to see if it is |
| 15639 |
corrupted or not: |
| 15640 |
</p> |
| 15641 |
|
| 15642 |
<ul> |
| 15643 |
<li> |
| 15644 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
| 15645 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
| 15646 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows) |
| 15647 |
</li> |
| 15648 |
<li> |
| 15649 |
You can verify the cryptographic signature that we provide. You need to |
| 15650 |
obtain the public key we use (17072058) before you proceed though. |
| 15651 |
</li> |
| 15652 |
</ul> |
| 15653 |
|
| 15654 |
<p> |
| 15655 |
To fetch our public key using the GnuPG application, run the following command: |
| 15656 |
</p> |
| 15657 |
|
| 15658 |
<pre caption="Obtaining the public key"> |
| 15659 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
| 15660 |
</pre> |
| 15661 |
|
| 15662 |
<p> |
| 15663 |
Now verify the signature: |
| 15664 |
</p> |
| 15665 |
|
| 15666 |
<pre caption="Verify the cryptographic signature"> |
| 15667 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
| 15668 |
</pre> |
| 15669 |
|
| 15670 |
<p> |
| 15671 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
| 15672 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
| 15673 |
<c>K3B</c> here; more information can be found in our <uri |
| 15674 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
| 15675 |
</p> |
| 15676 |
|
| 15677 |
<ul> |
| 15678 |
<li> |
| 15679 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded |
| 15680 |
iso></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
| 15681 |
path). |
| 15682 |
</li> |
| 15683 |
<li> |
| 15684 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
| 15685 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
| 15686 |
<c>Start</c>. |
| 15687 |
</li> |
| 15688 |
</ul> |
| 15689 |
|
| 15690 |
</body> |
| 15691 |
</subsection> |
| 15692 |
<subsection> |
| 15693 |
<title>Booting the Universal Installation CD</title> |
| 15694 |
<body> |
| 15695 |
|
| 15696 |
<p> |
| 15697 |
Insert the Gentoo Installation CD in the CD-ROM and boot your system. During |
| 15698 |
startup, press Stop-A to enter OpenBootPROM (OBP). Once you are in the OBP, |
| 15699 |
boot from the CD-ROM: |
| 15700 |
</p> |
| 15701 |
|
| 15702 |
<pre caption="Booting the Installation CD"> |
| 15703 |
ok <i>boot cdrom</i> |
| 15704 |
</pre> |
| 15705 |
|
| 15706 |
<p> |
| 15707 |
You will be greeted by the SILO boot manager (on the Installation CD). Type in |
| 15708 |
<c>gentoo-2.4</c> and press enter to continue booting the |
| 15709 |
system: |
| 15710 |
</p> |
| 15711 |
|
| 15712 |
<pre caption="Continue booting from the Installation CD"> |
| 15713 |
boot: <i>gentoo-2.4</i> |
| 15714 |
</pre> |
| 15715 |
|
| 15716 |
<p> |
| 15717 |
Once the Installation CD is booted, you will be automatically logged on to the |
| 15718 |
system. |
| 15719 |
</p> |
| 15720 |
|
| 15721 |
<p> |
| 15722 |
You should have a root ("#") prompt on the current console and can also switch |
| 15723 |
to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get back to the one you |
| 15724 |
started on by pressing Alt-F1. You will also find a root prompt on the serial |
| 15725 |
console (<path>ttyS0</path>). |
| 15726 |
</p> |
| 15727 |
|
| 15728 |
<p> |
| 15729 |
Continue with <uri link="#hardware">Extra Hardware Configuration</uri>. |
| 15730 |
</p> |
| 15731 |
|
| 15732 |
</body> |
| 15733 |
</subsection> |
| 15734 |
<subsection id="hardware"> |
| 15735 |
<title>Extra Hardware Configuration</title> |
| 15736 |
<body> |
| 15737 |
|
| 15738 |
<p> |
| 15739 |
If not all hardware is supported out-of-the-box, you will need to load the |
| 15740 |
appropriate kernel modules. |
| 15741 |
</p> |
| 15742 |
|
| 15743 |
<p> |
| 15744 |
In the next example we try to load the <c>8139too</c> module (support for |
| 15745 |
certain kinds of network interfaces): |
| 15746 |
</p> |
| 15747 |
|
| 15748 |
<pre caption="Loading kernel modules"> |
| 15749 |
# <i>modprobe 8139too</i> |
| 15750 |
</pre> |
| 15751 |
|
| 15752 |
</body> |
| 15753 |
</subsection> |
| 15754 |
<subsection id="useraccounts"> |
| 15755 |
<title>Optional: User Accounts</title> |
| 15756 |
<body> |
| 15757 |
|
| 15758 |
<p> |
| 15759 |
If you plan on giving other people access to your installation |
| 15760 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
| 15761 |
security reasons), you need to create the necessary user accounts and change |
| 15762 |
the root password. |
| 15763 |
</p> |
| 15764 |
|
| 15765 |
<p> |
| 15766 |
To change the root password, use the <c>passwd</c> utility: |
| 15767 |
</p> |
| 15768 |
|
| 15769 |
<pre caption="Changing the root password"> |
| 15770 |
# <i>passwd</i> |
| 15771 |
New password: <comment>(Enter your new password)</comment> |
| 15772 |
Re-enter password: <comment>(Re-enter your password)</comment> |
| 15773 |
</pre> |
| 15774 |
|
| 15775 |
<p> |
| 15776 |
To create a user account, we first enter their credentials, followed by |
| 15777 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
| 15778 |
In the next example, we create a user called "john". |
| 15779 |
</p> |
| 15780 |
|
| 15781 |
<pre caption="Creating a user account"> |
| 15782 |
# <i>useradd -m -G users john</i> |
| 15783 |
# <i>passwd john</i> |
| 15784 |
New password: <comment>(Enter john's password)</comment> |
| 15785 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
| 15786 |
</pre> |
| 15787 |
|
| 15788 |
<p> |
| 15789 |
You can change your user id from root to the newly created user by using |
| 15790 |
<c>su</c>: |
| 15791 |
</p> |
| 15792 |
|
| 15793 |
<pre caption="Changing user id"> |
| 15794 |
# <i>su - john</i> |
| 15795 |
</pre> |
| 15796 |
|
| 15797 |
</body> |
| 15798 |
</subsection> |
| 15799 |
<subsection> |
| 15800 |
<title>Optional: Viewing Documentation while Installing</title> |
| 15801 |
<body> |
| 15802 |
|
| 15803 |
<p> |
| 15804 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
| 15805 |
installation, make sure you have created a user account (see <uri |
| 15806 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
| 15807 |
go to a new terminal and log in. |
| 15808 |
</p> |
| 15809 |
|
| 15810 |
<p> |
| 15811 |
If you want to view the documentation on the CD you can immediately run |
| 15812 |
<c>links2</c> to read it: |
| 15813 |
</p> |
| 15814 |
|
| 15815 |
<pre caption="Viewing the on-CD documentation"> |
| 15816 |
# <i>links2 /mnt/cdrom/docs/handbook/html/index.html</i> |
| 15817 |
</pre> |
| 15818 |
|
| 15819 |
<p> |
| 15820 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
| 15821 |
more recent than the one provided on the CD. You can view it using <c>links2</c> |
| 15822 |
as well, but only after having completed the <e>Configuring your Network</e> |
| 15823 |
chapter (otherwise you won't be able to go on the Internet to view the |
| 15824 |
document): |
| 15825 |
</p> |
| 15826 |
|
| 15827 |
<pre caption="Viewing the Online Documentation"> |
| 15828 |
# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-sparc.xml</i> |
| 15829 |
</pre> |
| 15830 |
|
| 15831 |
<p> |
| 15832 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
| 15833 |
</p> |
| 15834 |
|
| 15835 |
</body> |
| 15836 |
</subsection> |
| 15837 |
<subsection> |
| 15838 |
<title>Optional: Starting the SSH Daemon</title> |
| 15839 |
<body> |
| 15840 |
|
| 15841 |
<p> |
| 15842 |
If you want to allow other users to access your computer during the |
| 15843 |
Gentoo installation (perhaps because those users are going to help you |
| 15844 |
install Gentoo, or even do it for you), you need to create a user |
| 15845 |
account for them and perhaps even provide them with your root password |
| 15846 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
| 15847 |
</p> |
| 15848 |
|
| 15849 |
<p> |
| 15850 |
To fire up the SSH daemon, execute the following command: |
| 15851 |
</p> |
| 15852 |
|
| 15853 |
<pre caption="Starting the SSH daemon"> |
| 15854 |
# <i>/etc/init.d/sshd start</i> |
| 15855 |
</pre> |
| 15856 |
|
| 15857 |
<p> |
| 15858 |
To be able to use sshd, you first need to set up your networking. Continue with |
| 15859 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
| 15860 |
</p> |
| 15861 |
|
| 15862 |
</body> |
| 15863 |
</subsection> |
| 15864 |
</section> |
| 15865 |
</sections> |
| 15866 |
|
| 15867 |
|
| 15868 |
|
| 15869 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-stage.xml |
| 15870 |
|
| 15871 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-stage.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 15872 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-stage.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 15873 |
|
| 15874 |
Index: hb-install-stage.xml |
| 15875 |
=================================================================== |
| 15876 |
<?xml version='1.0' encoding='UTF-8'?> |
| 15877 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 15878 |
|
| 15879 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 15880 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 15881 |
|
| 15882 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-stage.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 15883 |
|
| 15884 |
<sections> |
| 15885 |
|
| 15886 |
<version>5.8</version> |
| 15887 |
<date>2005-12-20</date> |
| 15888 |
|
| 15889 |
<section> |
| 15890 |
<title>Installing a Stage Tarball</title> |
| 15891 |
<subsection> |
| 15892 |
<title>Setting the Date/Time Right</title> |
| 15893 |
<body> |
| 15894 |
|
| 15895 |
<p> |
| 15896 |
Before you continue you need to check your date/time and update it. A |
| 15897 |
misconfigured clock may lead to strange results in the future! |
| 15898 |
</p> |
| 15899 |
|
| 15900 |
<p> |
| 15901 |
To verify the current date/time, run <c>date</c>: |
| 15902 |
</p> |
| 15903 |
|
| 15904 |
<pre caption="Verifying the date/time"> |
| 15905 |
# <i>date</i> |
| 15906 |
Fri Mar 29 16:21:18 CEST 2005 |
| 15907 |
</pre> |
| 15908 |
|
| 15909 |
<p> |
| 15910 |
If the date/time displayed is wrong, update it using the <c>date |
| 15911 |
MMDDhhmmYYYY</c> syntax (<b>M</b>onth, <b>D</b>ay, <b>h</b>our, <b>m</b>inute |
| 15912 |
and <b>Y</b>ear). For instance, to set the date to Mar 29th, 16:21 in the |
| 15913 |
year 2005: |
| 15914 |
</p> |
| 15915 |
|
| 15916 |
<pre caption="Setting the date/time"> |
| 15917 |
# <i>date 032916212005</i> |
| 15918 |
</pre> |
| 15919 |
|
| 15920 |
</body> |
| 15921 |
</subsection> |
| 15922 |
<subsection> |
| 15923 |
<title>Locating the Stage3 File</title> |
| 15924 |
<body> |
| 15925 |
|
| 15926 |
<p> |
| 15927 |
If you have configured networking because you need to download a stage3 file for |
| 15928 |
your architecture, continue with <uri link="#download">Alternative: Using a |
| 15929 |
Stage3 from the Internet</uri>. Otherwise read <uri link="#available">Default: |
| 15930 |
Using a Stage3 from the Installation CD</uri>. |
| 15931 |
</p> |
| 15932 |
|
| 15933 |
</body> |
| 15934 |
</subsection> |
| 15935 |
</section> |
| 15936 |
<section id="available"> |
| 15937 |
<title>Default: Using a Stage from the Installation CD</title> |
| 15938 |
<subsection> |
| 15939 |
<title>Extracting the Stage Tarball</title> |
| 15940 |
<body> |
| 15941 |
|
| 15942 |
<p> |
| 15943 |
The stages on the CD reside in the <path>/mnt/cdrom/stages</path> directory. To |
| 15944 |
see a listing of available stages, use <c>ls</c>: |
| 15945 |
</p> |
| 15946 |
|
| 15947 |
<pre caption="List all available stages"> |
| 15948 |
# <i>ls /mnt/cdrom/stages</i> |
| 15949 |
</pre> |
| 15950 |
|
| 15951 |
<p> |
| 15952 |
If the system replies with an error, you may need to mount the CD-ROM first: |
| 15953 |
</p> |
| 15954 |
|
| 15955 |
<pre caption="Mounting the CD-ROM"> |
| 15956 |
# <i>ls /mnt/cdrom/stages</i> |
| 15957 |
ls: /mnt/cdrom/stages: No such file or directory |
| 15958 |
# <i>mount /dev/cdroms/cdrom0 /mnt/cdrom</i> |
| 15959 |
# <i>ls /mnt/cdrom/stages</i> |
| 15960 |
</pre> |
| 15961 |
|
| 15962 |
<p> |
| 15963 |
Now go into your Gentoo mountpoint (usually <path>/mnt/gentoo</path>): |
| 15964 |
</p> |
| 15965 |
|
| 15966 |
<pre caption="Changing directory to /mnt/gentoo"> |
| 15967 |
# <i>cd /mnt/gentoo</i> |
| 15968 |
</pre> |
| 15969 |
|
| 15970 |
<p> |
| 15971 |
We will now extract the stage tarball of your choice. We will do this with the |
| 15972 |
<c>tar</c> tool. Make sure you use the same options (<c>xvjpf</c>)! The |
| 15973 |
<c>x</c> stands for <e>Extract</e>, the <c>v</c> for <e>Verbose</e> to see what |
| 15974 |
happens during the extraction process (this one is optional), the <c>j</c> for |
| 15975 |
<e>Decompress with bzip2</e>, the <c>p</c> for <e>Preserve permissions</e> and |
| 15976 |
the <c>f</c> to denote that we want to extract a file, not standard input. In |
| 15977 |
the next example, we extract the stage tarball |
| 15978 |
<path>stage3-<subarch>-2006.0.tar.bz2</path>. Be sure to substitute |
| 15979 |
the tarball filename with your stage. |
| 15980 |
</p> |
| 15981 |
|
| 15982 |
<pre caption="Extracting the stage tarball"> |
| 15983 |
# <i>tar xvjpf /mnt/cdrom/stages/stage3-<subarch>-2006.0.tar.bz2</i> |
| 15984 |
</pre> |
| 15985 |
|
| 15986 |
<p> |
| 15987 |
Now that the stage is installed, continue with <uri |
| 15988 |
link="#installing_portage">Installing Portage</uri>. |
| 15989 |
</p> |
| 15990 |
|
| 15991 |
</body> |
| 15992 |
</subsection> |
| 15993 |
</section> |
| 15994 |
<section id="download"> |
| 15995 |
<title>Alternative: Using a Stage from the Internet</title> |
| 15996 |
<subsection> |
| 15997 |
<title>Downloading the Stage Tarball</title> |
| 15998 |
<body> |
| 15999 |
|
| 16000 |
<p> |
| 16001 |
Go to the Gentoo mountpoint at which you mounted your filesystems |
| 16002 |
(most likely <path>/mnt/gentoo</path>): |
| 16003 |
</p> |
| 16004 |
|
| 16005 |
<pre caption="Going to the Gentoo mountpoint"> |
| 16006 |
# <i>cd /mnt/gentoo</i> |
| 16007 |
</pre> |
| 16008 |
|
| 16009 |
<p> |
| 16010 |
Depending on your installation medium, you have a couple of tools available to |
| 16011 |
download a stage. If you have <c>links2</c> available, then you can immediately |
| 16012 |
surf to <uri link="/main/en/mirrors.xml">the Gentoo mirrorlist</uri> and |
| 16013 |
choose a mirror close to you. |
| 16014 |
</p> |
| 16015 |
|
| 16016 |
<p> |
| 16017 |
If you don't have <c>links2</c> available you should have <c>lynx</c> at your |
| 16018 |
disposal. If you need to go through a proxy, export the <c>http_proxy</c> and |
| 16019 |
<c>ftp_proxy</c> variables: |
| 16020 |
</p> |
| 16021 |
|
| 16022 |
<pre caption="Setting proxy information for lynx"> |
| 16023 |
# <i>export http_proxy="http://proxy.server.com:port"</i> |
| 16024 |
# <i>export ftp_proxy="http://proxy.server.com:port"</i> |
| 16025 |
</pre> |
| 16026 |
|
| 16027 |
<p> |
| 16028 |
We will now assume that you have <c>links2</c> at your disposal. |
| 16029 |
</p> |
| 16030 |
|
| 16031 |
<p> |
| 16032 |
Pick the <path>releases/</path> directory, followed by your architecture (for |
| 16033 |
instance <path>x86/</path>) and the Gentoo version (<path>2006.0/</path>) to |
| 16034 |
finish up with the <path>stages/</path> directory. There you should see all |
| 16035 |
available stage files for your architecture (they might be stored within |
| 16036 |
subdirectories named to the individual sub architectures). Select one and press |
| 16037 |
<c>D</c> to download. When you're finished, press <c>Q</c> to quit the browser. |
| 16038 |
</p> |
| 16039 |
|
| 16040 |
<pre caption="Surfing to the mirror listing with links2"> |
| 16041 |
# <i>links2 http://www.gentoo.org/main/en/mirrors.xml</i> |
| 16042 |
|
| 16043 |
<comment>(If you need proxy support with links2:)</comment> |
| 16044 |
# <i>links2 -http-proxy proxy.server.com:8080 http://www.gentoo.org/main/en/mirrors.xml</i> |
| 16045 |
</pre> |
| 16046 |
|
| 16047 |
<p> |
| 16048 |
Make sure you download a stage3 tarball - installations using a stage1 or stage2 |
| 16049 |
tarball are not supported anymore. |
| 16050 |
</p> |
| 16051 |
|
| 16052 |
<p> |
| 16053 |
If you want to check the integrity of the downloaded stage tarball, use |
| 16054 |
<c>md5sum</c> and compare the output with the MD5 checksum provided on the |
| 16055 |
mirror. For instance, to check the validity of the x86 stage tarball: |
| 16056 |
</p> |
| 16057 |
|
| 16058 |
<pre caption="Example checking integrity of a stage tarball"> |
| 16059 |
# <i>md5sum -c stage3-x86-2006.0.tar.bz2.md5</i> |
| 16060 |
stage3-x86-2006.0.tar.bz2: OK |
| 16061 |
</pre> |
| 16062 |
|
| 16063 |
</body> |
| 16064 |
</subsection> |
| 16065 |
<subsection> |
| 16066 |
<title>Unpacking the Stage Tarball</title> |
| 16067 |
<body> |
| 16068 |
|
| 16069 |
<p> |
| 16070 |
Now unpack your downloaded stage onto your system. We use <c>tar</c> to proceed |
| 16071 |
as it is the easiest method: |
| 16072 |
</p> |
| 16073 |
|
| 16074 |
<pre caption="Unpacking the stage"> |
| 16075 |
# <i>tar xvjpf stage3-*.tar.bz2</i> |
| 16076 |
</pre> |
| 16077 |
|
| 16078 |
<p> |
| 16079 |
Make sure that you use the same options (<c>xvjpf</c>). The <c>x</c> stands |
| 16080 |
for <e>Extract</e>, the <c>v</c> for <e>Verbose</e> to see what happens during |
| 16081 |
the extraction process (this one is optional), the <c>j</c> for <e>Decompress |
| 16082 |
with bzip2</e>, the <c>p</c> for <e>Preserve permissions</e> and the <c>f</c> |
| 16083 |
to denote that we want to extract a file, not standard input. |
| 16084 |
</p> |
| 16085 |
|
| 16086 |
<p> |
| 16087 |
Now that the stage is installed, continue with <uri |
| 16088 |
link="#installing_portage">Installing Portage</uri>. |
| 16089 |
</p> |
| 16090 |
|
| 16091 |
</body> |
| 16092 |
</subsection> |
| 16093 |
</section> |
| 16094 |
<section id="installing_portage"> |
| 16095 |
<title>Installing Portage</title> |
| 16096 |
<subsection> |
| 16097 |
<title>Unpacking a Portage Snapshot</title> |
| 16098 |
<body> |
| 16099 |
|
| 16100 |
<p> |
| 16101 |
You now have to install a Portage snapshot, a collection of files that inform |
| 16102 |
Portage what software titles you can install, which profiles are available, etc. |
| 16103 |
</p> |
| 16104 |
|
| 16105 |
</body> |
| 16106 |
</subsection> |
| 16107 |
<subsection id="installing_from_InstallCD"> |
| 16108 |
<title>Unpack the Snapshot from the Installation CD</title> |
| 16109 |
<body> |
| 16110 |
|
| 16111 |
<p> |
| 16112 |
To install the snapshot, take a look inside <path>/mnt/cdrom/snapshots/</path> |
| 16113 |
to see what snapshot is available: |
| 16114 |
</p> |
| 16115 |
|
| 16116 |
<pre caption="Checking the /mnt/cdrom/snapshots content"> |
| 16117 |
# <i>ls /mnt/cdrom/snapshots</i> |
| 16118 |
</pre> |
| 16119 |
|
| 16120 |
<p> |
| 16121 |
Now extract the snapshot using the following construct. Again, make sure you |
| 16122 |
use the correct options with <c>tar</c>. Also, the <c>-C</c> is with a capital |
| 16123 |
<c>C</c>, not <c>c</c>. In the next example we use |
| 16124 |
<path>portage-<date>.tar.bz2</path> as the snapshot filename. Be sure to |
| 16125 |
substitute with the name of the snapshot that is on your Installation CD. |
| 16126 |
</p> |
| 16127 |
|
| 16128 |
<pre caption="Extracting a Portage snapshot"> |
| 16129 |
# <i>tar xvjf /mnt/cdrom/snapshots/portage-<date>.tar.bz2 -C /mnt/gentoo/usr</i> |
| 16130 |
</pre> |
| 16131 |
|
| 16132 |
</body> |
| 16133 |
</subsection> |
| 16134 |
<subsection id="copysources"> |
| 16135 |
<title>Copy Source Code Archives</title> |
| 16136 |
<body> |
| 16137 |
|
| 16138 |
<p> |
| 16139 |
You also need to copy over all source code from the Universal Installation CD. |
| 16140 |
</p> |
| 16141 |
|
| 16142 |
<pre caption="Copy over source code"> |
| 16143 |
# <i>mkdir /mnt/gentoo/usr/portage/distfiles</i> |
| 16144 |
# <i>cp /mnt/cdrom/distfiles/* /mnt/gentoo/usr/portage/distfiles/</i> |
| 16145 |
</pre> |
| 16146 |
|
| 16147 |
</body> |
| 16148 |
</subsection> |
| 16149 |
</section> |
| 16150 |
<section id="compile_options"> |
| 16151 |
<title>Configuring the Compile Options</title> |
| 16152 |
<subsection> |
| 16153 |
<title>Introduction</title> |
| 16154 |
<body> |
| 16155 |
|
| 16156 |
<p> |
| 16157 |
To optimize Gentoo, you can set a couple of variables which impact Portage |
| 16158 |
behaviour. All those variables can be set as environment variables (using |
| 16159 |
<c>export</c>) but that isn't permanent. To keep your settings, Portage provides |
| 16160 |
you with <path>/etc/make.conf</path>, a configuration file for Portage. It is |
| 16161 |
this file we will edit now. |
| 16162 |
</p> |
| 16163 |
|
| 16164 |
<note> |
| 16165 |
A commented listing of all possible variables can be found in |
| 16166 |
<path>/mnt/gentoo/etc/make.conf.example</path>. For a successful Gentoo |
| 16167 |
installation you'll only need to set the variables which are mentioned beneath. |
| 16168 |
</note> |
| 16169 |
|
| 16170 |
<p> |
| 16171 |
Fire up your favorite editor (in this guide we use <c>nano</c>) so we can alter |
| 16172 |
the optimization variables we will discuss hereafter. |
| 16173 |
</p> |
| 16174 |
|
| 16175 |
<pre caption="Opening /etc/make.conf"> |
| 16176 |
# <i>nano -w /mnt/gentoo/etc/make.conf</i> |
| 16177 |
</pre> |
| 16178 |
|
| 16179 |
<p> |
| 16180 |
As you probably noticed, the <path>make.conf.example</path> file is |
| 16181 |
structured in a generic way: commented lines start with "#", other lines define |
| 16182 |
variables using the <c>VARIABLE="content"</c> syntax. The <path>make.conf</path> |
| 16183 |
file uses the same syntax. Several of those variables are discussed next. |
| 16184 |
</p> |
| 16185 |
|
| 16186 |
<warn> |
| 16187 |
Do not make any modifications to the USE variable if you are performing a stage3 |
| 16188 |
with GRP installation. You can alter the USE variable after having installed the |
| 16189 |
packages you want. Gremlins are known to attack your system if you ignore this |
| 16190 |
warning! |
| 16191 |
</warn> |
| 16192 |
|
| 16193 |
</body> |
| 16194 |
</subsection> |
| 16195 |
<subsection> |
| 16196 |
<title>CHOST</title> |
| 16197 |
<body> |
| 16198 |
|
| 16199 |
<p> |
| 16200 |
The <c>CHOST</c> variable declares the target build host for your system. This |
| 16201 |
variable should already be set to the correct value. <brite>Do not edit |
| 16202 |
it</brite> as that might break your system. If the <c>CHOST</c> variable does |
| 16203 |
not look correct to you, you might be using the wrong stage3 tarball. |
| 16204 |
</p> |
| 16205 |
|
| 16206 |
</body> |
| 16207 |
</subsection> |
| 16208 |
<subsection> |
| 16209 |
<title>CFLAGS and CXXFLAGS</title> |
| 16210 |
<body> |
| 16211 |
|
| 16212 |
<p> |
| 16213 |
The <c>CFLAGS</c> and <c>CXXFLAGS</c> variables define the optimization flags |
| 16214 |
for the <c>gcc</c> C and C++ compiler respectively. Although we define those |
| 16215 |
generally here, you will only have maximum performance if you optimize these |
| 16216 |
flags for each program separately. The reason for this is because every program |
| 16217 |
is different. |
| 16218 |
</p> |
| 16219 |
|
| 16220 |
<p> |
| 16221 |
In <path>make.conf</path> you should define the optimization flags you think |
| 16222 |
will make your system the most responsive <e>generally</e>. Don't place |
| 16223 |
experimental settings in this variable; too much optimization can make |
| 16224 |
programs behave bad (crash, or even worse, malfunction). |
| 16225 |
</p> |
| 16226 |
|
| 16227 |
<p> |
| 16228 |
We will not explain all possible optimization options. If you want to know |
| 16229 |
them all, read the <uri link="http://gcc.gnu.org/onlinedocs/">GNU |
| 16230 |
Online Manual(s)</uri> or the <c>gcc</c> info page (<c>info gcc</c> -- only |
| 16231 |
works on a working Linux system). The <path>make.conf.example</path> file |
| 16232 |
itself also contains lots of examples and information; don't forget to read it |
| 16233 |
too. |
| 16234 |
</p> |
| 16235 |
|
| 16236 |
<p> |
| 16237 |
A first setting is the <c>-march=</c> flag, which specifies the name of the |
| 16238 |
target architecture. Possible options are described in the |
| 16239 |
<path>make.conf.example</path> file (as comments). For instance, for the x86 |
| 16240 |
Athlon XP architecture: |
| 16241 |
</p> |
| 16242 |
|
| 16243 |
<pre caption="The GCC march setting"> |
| 16244 |
<comment># AMD64 users who want to use a native 64 bit system should use -march=k8</comment> |
| 16245 |
<comment># EM64T users should use -march=nocona</comment> |
| 16246 |
-march=athlon-xp |
| 16247 |
</pre> |
| 16248 |
|
| 16249 |
<p> |
| 16250 |
A second one is the <c>-O</c> flag (that is a capital O, not a zero), |
| 16251 |
which specifies the <c>gcc</c> optimization |
| 16252 |
class flag. Possible classes are <c>s</c> (for size-optimized), |
| 16253 |
<c>0</c> (zero - for no optimizations), <c>1</c>, <c>2</c> or <c>3</c> for more |
| 16254 |
speed-optimization flags (every class has the same flags as the one before, plus |
| 16255 |
some extras). For instance, for a class-2 optimization: |
| 16256 |
</p> |
| 16257 |
|
| 16258 |
<pre caption="The GCC O setting"> |
| 16259 |
-O2 |
| 16260 |
</pre> |
| 16261 |
|
| 16262 |
<p> |
| 16263 |
Another popular optimization flag is <c>-pipe</c> (use pipes rather than |
| 16264 |
temporary files for communication between the various stages of compilation). |
| 16265 |
</p> |
| 16266 |
|
| 16267 |
<p> |
| 16268 |
Mind you that using <c>-fomit-frame-pointer</c> (which doesn't keep the frame |
| 16269 |
pointer in a register for functions that don't need one) might have serious |
| 16270 |
repercussions on the debugging of applications! |
| 16271 |
</p> |
| 16272 |
|
| 16273 |
<p> |
| 16274 |
When you define the <c>CFLAGS</c> and <c>CXXFLAGS</c>, you should combine |
| 16275 |
several optimization flags, like in the following example: |
| 16276 |
</p> |
| 16277 |
|
| 16278 |
<pre caption="Defining the CFLAGS and CXXFLAGS variable"> |
| 16279 |
CFLAGS="-march=athlon-xp -pipe -O2" <comment># AMD64 users use march=k8</comment> |
| 16280 |
<comment># EM64T users use march=nocona</comment> |
| 16281 |
CXXFLAGS="${CFLAGS}" <comment># Use the same settings for both variables</comment> |
| 16282 |
</pre> |
| 16283 |
|
| 16284 |
</body> |
| 16285 |
</subsection> |
| 16286 |
<subsection> |
| 16287 |
<title>MAKEOPTS</title> |
| 16288 |
<body> |
| 16289 |
|
| 16290 |
<p> |
| 16291 |
With <c>MAKEOPTS</c> you define how many parallel compilations should occur when |
| 16292 |
you install a package. A good choice is the number of CPUs in your system plus |
| 16293 |
one, but this guideline isn't always perfect. |
| 16294 |
</p> |
| 16295 |
|
| 16296 |
<pre caption="MAKEOPTS for a regular, 1-CPU system"> |
| 16297 |
MAKEOPTS="-j2" |
| 16298 |
</pre> |
| 16299 |
|
| 16300 |
</body> |
| 16301 |
</subsection> |
| 16302 |
<subsection> |
| 16303 |
<title>Ready, Set, Go!</title> |
| 16304 |
<body> |
| 16305 |
|
| 16306 |
<p> |
| 16307 |
Update your <path>/mnt/gentoo/etc/make.conf</path> to your own preference and |
| 16308 |
save (<c>nano</c> users would hit <c>Ctrl-X</c>). You are now ready to continue |
| 16309 |
with <uri link="?part=1&chap=6">Chrooting into the Gentoo Base System</uri>. |
| 16310 |
</p> |
| 16311 |
|
| 16312 |
</body> |
| 16313 |
</subsection> |
| 16314 |
</section> |
| 16315 |
</sections> |
| 16316 |
|
| 16317 |
|
| 16318 |
|
| 16319 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-system.xml |
| 16320 |
|
| 16321 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-system.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 16322 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-system.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 16323 |
|
| 16324 |
Index: hb-install-system.xml |
| 16325 |
=================================================================== |
| 16326 |
<?xml version='1.0' encoding='UTF-8'?> |
| 16327 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 16328 |
|
| 16329 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 16330 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 16331 |
|
| 16332 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-system.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 16333 |
|
| 16334 |
<sections> |
| 16335 |
|
| 16336 |
<version>5.3</version> |
| 16337 |
<date>2006-01-19</date> |
| 16338 |
|
| 16339 |
<section> |
| 16340 |
<title>Chrooting</title> |
| 16341 |
<subsection> |
| 16342 |
<title>Mounting the /proc and /dev Filesystems</title> |
| 16343 |
<body> |
| 16344 |
|
| 16345 |
<p> |
| 16346 |
Mount the <path>/proc</path> filesystem on <path>/mnt/gentoo/proc</path> to |
| 16347 |
allow the installation to use the kernel-provided information within the |
| 16348 |
chrooted environment, and then mount-bind the <path>/dev</path> filesystem. |
| 16349 |
</p> |
| 16350 |
|
| 16351 |
<pre caption="Mounting /proc and /dev"> |
| 16352 |
# <i>mount -t proc none /mnt/gentoo/proc</i> |
| 16353 |
# <i>mount -o bind /dev /mnt/gentoo/dev</i> |
| 16354 |
</pre> |
| 16355 |
|
| 16356 |
</body> |
| 16357 |
</subsection> |
| 16358 |
<subsection> |
| 16359 |
<title>Optional: Copy over DNS Information</title> |
| 16360 |
<body> |
| 16361 |
|
| 16362 |
<p> |
| 16363 |
If you configured your network to fetch the appropriate stage file later on from |
| 16364 |
the Internet, you need to copy over the DNS information stored in |
| 16365 |
<path>/etc/resolv.conf</path> to <path>/mnt/gentoo/etc/resolv.conf</path>. This |
| 16366 |
file contains the nameservers your system will use to resolve names to IP |
| 16367 |
addresses. |
| 16368 |
</p> |
| 16369 |
|
| 16370 |
<pre caption="Copy over DNS Information"> |
| 16371 |
# <i>cp -L /etc/resolv.conf /mnt/gentoo/etc/resolv.conf</i> |
| 16372 |
</pre> |
| 16373 |
|
| 16374 |
</body> |
| 16375 |
</subsection> |
| 16376 |
<subsection> |
| 16377 |
<title>Entering the new Environment</title> |
| 16378 |
<body> |
| 16379 |
|
| 16380 |
<p> |
| 16381 |
Now that all partitions are initialized and the base environment |
| 16382 |
installed, it is time to enter our new installation environment by |
| 16383 |
<e>chrooting</e> into it. This means that we change from the current |
| 16384 |
installation environment to your installation system (namely the |
| 16385 |
initialized partitions). |
| 16386 |
</p> |
| 16387 |
|
| 16388 |
<p> |
| 16389 |
This chrooting is done in three steps. First we will change the root |
| 16390 |
from <path>/</path> (on the installation medium) to <path>/mnt/gentoo</path> |
| 16391 |
(on your partitions) using <c>chroot</c>. Then we will create a new environment |
| 16392 |
using <c>env-update</c>, which essentially creates environment variables. |
| 16393 |
Finally, we load those variables into memory using <c>source</c>. |
| 16394 |
</p> |
| 16395 |
|
| 16396 |
<pre caption="Chrooting into the new environment"> |
| 16397 |
# <i>chroot /mnt/gentoo /bin/bash</i> |
| 16398 |
# <i>env-update</i> |
| 16399 |
* Caching service dependencies... |
| 16400 |
# <i>source /etc/profile</i> |
| 16401 |
# <i>export PS1="(chroot) $PS1"</i> |
| 16402 |
</pre> |
| 16403 |
|
| 16404 |
<p> |
| 16405 |
Congratulations! You are now inside your own Gentoo Linux environment. |
| 16406 |
Of course it is far from finished, which is why the installation still |
| 16407 |
has some sections left :-) |
| 16408 |
</p> |
| 16409 |
|
| 16410 |
</body> |
| 16411 |
</subsection> |
| 16412 |
<subsection> |
| 16413 |
<title>Creating the Portage cache</title> |
| 16414 |
<body> |
| 16415 |
|
| 16416 |
<p> |
| 16417 |
You have already installed the Portage tree, but you should now build the |
| 16418 |
Portage cache to speed up future emerges. <c>emerge --metadata</c> does this |
| 16419 |
for you. |
| 16420 |
</p> |
| 16421 |
|
| 16422 |
<pre caption="Creating the Portage cache"> |
| 16423 |
# <i>emerge --metadata</i> |
| 16424 |
</pre> |
| 16425 |
|
| 16426 |
</body> |
| 16427 |
</subsection> |
| 16428 |
</section> |
| 16429 |
|
| 16430 |
<section id="configure_USE"> |
| 16431 |
<title>Configuring the USE Variable</title> |
| 16432 |
<subsection> |
| 16433 |
<title>What is the USE Variable?</title> |
| 16434 |
<body> |
| 16435 |
|
| 16436 |
<p> |
| 16437 |
<c>USE</c> is one of the most powerful variables Gentoo provides to its users. |
| 16438 |
Several programs can be compiled with or without optional support for certain |
| 16439 |
items. For instance, some programs can be compiled with gtk-support, or with |
| 16440 |
qt-support. Others can be compiled with or without SSL support. Some programs |
| 16441 |
can even be compiled with framebuffer support (svgalib) instead of X11 support |
| 16442 |
(X-server). |
| 16443 |
</p> |
| 16444 |
|
| 16445 |
<p> |
| 16446 |
Most distributions compile their packages with support for as much as possible, |
| 16447 |
increasing the size of the programs and startup time, not to mention an enormous |
| 16448 |
amount of dependencies. With Gentoo you can define what options a package |
| 16449 |
should be compiled with. This is where <c>USE</c> comes into play. |
| 16450 |
</p> |
| 16451 |
|
| 16452 |
<p> |
| 16453 |
In the <c>USE</c> variable you define keywords which are mapped onto |
| 16454 |
compile-options. For instance, <e>ssl</e> will compile ssl-support in the |
| 16455 |
programs that support it. <e>-X</e> will remove X-server support (note the minus |
| 16456 |
sign in front). <e>gnome gtk -kde -qt</e> will compile your programs with gnome |
| 16457 |
(and gtk) support, and not with kde (and qt) support, making your system fully |
| 16458 |
tweaked for GNOME. |
| 16459 |
</p> |
| 16460 |
|
| 16461 |
</body> |
| 16462 |
</subsection> |
| 16463 |
<subsection> |
| 16464 |
<title>Modifying the USE Variable</title> |
| 16465 |
<body> |
| 16466 |
|
| 16467 |
<warn> |
| 16468 |
Do not make any modifications to the USE variable yet if you plan to use our |
| 16469 |
prebuilt packages (GRP set). You can alter the USE variable after having |
| 16470 |
installed the packages you want. Gremlins are known to attack your system |
| 16471 |
if you ignore this warning! |
| 16472 |
</warn> |
| 16473 |
|
| 16474 |
<p> |
| 16475 |
The default <c>USE</c> settings are placed in |
| 16476 |
<path>/etc/make.profile/make.defaults</path>. What you place in |
| 16477 |
<path>/etc/make.conf</path> is calculated against these defaults settings. If |
| 16478 |
you add something to the <c>USE</c> setting, it is added to the default list. If |
| 16479 |
you remove something from the <c>USE</c> setting (by placing a minus sign in |
| 16480 |
front of it) it is removed from the default list (if it was in the default list |
| 16481 |
at all). <e>Never</e> alter anything inside the <path>/etc/make.profile</path> |
| 16482 |
directory; it gets overwritten when you update Portage! |
| 16483 |
</p> |
| 16484 |
|
| 16485 |
<p> |
| 16486 |
A full description on <c>USE</c> can be found in the second part of the Gentoo |
| 16487 |
Handbook, <uri link="?part=2&chap=2">USE flags</uri>. A full description on |
| 16488 |
the available USE flags can be found on your system in |
| 16489 |
<path>/usr/portage/profiles/use.desc</path>. |
| 16490 |
</p> |
| 16491 |
|
| 16492 |
<pre caption="Viewing available USE flags"> |
| 16493 |
# <i>less /usr/portage/profiles/use.desc</i> |
| 16494 |
<comment>(You can scroll using your arrow keys, exit by pressing 'q')</comment> |
| 16495 |
</pre> |
| 16496 |
|
| 16497 |
<p> |
| 16498 |
As an example we show a <c>USE</c> setting for a KDE-based system with DVD, ALSA |
| 16499 |
and CD Recording support: |
| 16500 |
</p> |
| 16501 |
|
| 16502 |
<pre caption="Opening /etc/make.conf"> |
| 16503 |
# <i>nano -w /etc/make.conf</i> |
| 16504 |
</pre> |
| 16505 |
|
| 16506 |
<pre caption="USE setting"> |
| 16507 |
USE="-gtk -gnome qt kde dvd alsa cdr" |
| 16508 |
</pre> |
| 16509 |
|
| 16510 |
</body> |
| 16511 |
</subsection> |
| 16512 |
</section> |
| 16513 |
</sections> |
| 16514 |
|
| 16515 |
|
| 16516 |
|
| 16517 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-tools.xml |
| 16518 |
|
| 16519 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-tools.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 16520 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-tools.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 16521 |
|
| 16522 |
Index: hb-install-tools.xml |
| 16523 |
=================================================================== |
| 16524 |
<?xml version='1.0' encoding='UTF-8'?> |
| 16525 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 16526 |
|
| 16527 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 16528 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
| 16529 |
|
| 16530 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-tools.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 16531 |
|
| 16532 |
<sections> |
| 16533 |
|
| 16534 |
<version>5.2</version> |
| 16535 |
<date>2005-11-21</date> |
| 16536 |
|
| 16537 |
<section> |
| 16538 |
<title>System Logger</title> |
| 16539 |
<body> |
| 16540 |
|
| 16541 |
<p> |
| 16542 |
Some tools are missing from the <e>stage3</e> archive because several packages |
| 16543 |
provide the same functionality. It is now up to you to choose which ones you |
| 16544 |
want to install. |
| 16545 |
</p> |
| 16546 |
|
| 16547 |
<p> |
| 16548 |
The first tool you need to decide on has to provide logging facilities for your |
| 16549 |
system. Unix and Linux have an excellent history of logging capabilities -- if |
| 16550 |
you want you can log everything that happens on your system in logfiles. This |
| 16551 |
happens through the <e>system logger</e>. |
| 16552 |
</p> |
| 16553 |
|
| 16554 |
<p> |
| 16555 |
Gentoo offers several system loggers to choose from. There are <c>sysklogd</c>, |
| 16556 |
which is the traditional set of system logging daemons, <c>syslog-ng</c>, an |
| 16557 |
advanced system logger, and <c>metalog</c> which is a highly-configurable |
| 16558 |
system logger. Others might be available through Portage as well - our number of |
| 16559 |
available packages increases on a daily basis. |
| 16560 |
</p> |
| 16561 |
|
| 16562 |
<p> |
| 16563 |
If you plan on using <c>sysklogd</c> or <c>syslog-ng</c> you might want to |
| 16564 |
install <c>logrotate</c> afterwards as those system loggers don't provide any |
| 16565 |
rotation mechanism for the log files. |
| 16566 |
</p> |
| 16567 |
|
| 16568 |
<!-- |
| 16569 |
Even though syslog-ng does not rotate the logs, it does conform to the syslog |
| 16570 |
RFC (http://www.faqs.org/rfcs/rfc3164.html) and is far more powerful than most other system loggers. That and some architectures really prefer syslog-ng |
| 16571 |
above others (metalog for instance doesn't work nicely with sparc all the |
| 16572 |
time). |
| 16573 |
--> |
| 16574 |
|
| 16575 |
<p> |
| 16576 |
To install the system logger of your choice, <c>emerge</c> it and have it added |
| 16577 |
to the default runlevel using <c>rc-update</c>. The following example installs |
| 16578 |
<c>syslog-ng</c>. Of course substitute with your system logger: |
| 16579 |
</p> |
| 16580 |
|
| 16581 |
<pre caption="Installing a system logger"> |
| 16582 |
# <i>emerge syslog-ng</i> |
| 16583 |
# <i>rc-update add syslog-ng default</i> |
| 16584 |
</pre> |
| 16585 |
|
| 16586 |
</body> |
| 16587 |
</section> |
| 16588 |
<section> |
| 16589 |
<title>Optional: Cron Daemon</title> |
| 16590 |
<body> |
| 16591 |
|
| 16592 |
<p> |
| 16593 |
Next is the cron daemon. Although it is optional and not required for your |
| 16594 |
system, it is wise to install one. But what is a cron daemon? A cron daemon |
| 16595 |
executes scheduled commands. It is very handy if you need to execute some |
| 16596 |
command regularly (for instance daily, weekly or monthly). |
| 16597 |
</p> |
| 16598 |
|
| 16599 |
<p> |
| 16600 |
We only provide <c>vixie-cron</c> for networkless installations. If you want |
| 16601 |
another cron daemon you can wait and install it later on. |
| 16602 |
</p> |
| 16603 |
|
| 16604 |
<pre caption="Installing a cron daemon"> |
| 16605 |
# <i>emerge vixie-cron</i> |
| 16606 |
# <i>rc-update add vixie-cron default</i> |
| 16607 |
</pre> |
| 16608 |
|
| 16609 |
</body> |
| 16610 |
</section> |
| 16611 |
<section> |
| 16612 |
<title>Optional: File Indexing</title> |
| 16613 |
<body> |
| 16614 |
|
| 16615 |
<p> |
| 16616 |
If you want to index your system's files so you are able to quickly |
| 16617 |
locate them using the <c>locate</c> tool, you need to install |
| 16618 |
<c>sys-apps/slocate</c>. |
| 16619 |
</p> |
| 16620 |
|
| 16621 |
<pre caption="Installing slocate"> |
| 16622 |
# <i>emerge slocate</i> |
| 16623 |
</pre> |
| 16624 |
|
| 16625 |
</body> |
| 16626 |
</section> |
| 16627 |
<section> |
| 16628 |
<title>File System Tools</title> |
| 16629 |
<body> |
| 16630 |
|
| 16631 |
<p> |
| 16632 |
Depending on what file systems you are using, you need to install the necessary |
| 16633 |
file system utilities (for checking the filesystem integrity, creating |
| 16634 |
additional file systems etc.). |
| 16635 |
</p> |
| 16636 |
|
| 16637 |
<p> |
| 16638 |
The following table lists the tools you need to install if you use a certain |
| 16639 |
file system. Not all filesystems are available for each and every architecture |
| 16640 |
though. |
| 16641 |
</p> |
| 16642 |
|
| 16643 |
<table> |
| 16644 |
<tr> |
| 16645 |
<th>File System</th> |
| 16646 |
<th>Tool</th> |
| 16647 |
<th>Install Command</th> |
| 16648 |
</tr> |
| 16649 |
<tr> |
| 16650 |
<ti>XFS</ti> |
| 16651 |
<ti>xfsprogs</ti> |
| 16652 |
<ti><c>emerge xfsprogs</c></ti> |
| 16653 |
</tr> |
| 16654 |
<tr> |
| 16655 |
<ti>ReiserFS</ti> |
| 16656 |
<ti>reiserfsprogs</ti> |
| 16657 |
<ti><c>emerge reiserfsprogs</c></ti> |
| 16658 |
</tr> |
| 16659 |
<tr> |
| 16660 |
<ti>JFS</ti> |
| 16661 |
<ti>jfsutils</ti> |
| 16662 |
<ti><c>emerge jfsutils</c></ti> |
| 16663 |
</tr> |
| 16664 |
</table> |
| 16665 |
|
| 16666 |
<p> |
| 16667 |
If you are an EVMS user, you need to install <c>emvs</c>: |
| 16668 |
</p> |
| 16669 |
|
| 16670 |
<pre caption="Installing EVMS utilities"> |
| 16671 |
# <i>USE="-gtk" emerge evms</i> |
| 16672 |
</pre> |
| 16673 |
|
| 16674 |
<p> |
| 16675 |
The <c>USE="-gtk"</c> will prevent the installation of dependencies. If you |
| 16676 |
want to enable the <c>evms</c> graphical tools, you can recompile <c>evms</c> |
| 16677 |
later on. |
| 16678 |
</p> |
| 16679 |
|
| 16680 |
<p> |
| 16681 |
If you don't require any additional networking-related tools (such as rp-pppoe |
| 16682 |
or a dhcp client) continue with <uri link="?part=1&chap=10">Configuring the |
| 16683 |
Bootloader</uri>. |
| 16684 |
</p> |
| 16685 |
|
| 16686 |
</body> |
| 16687 |
</section> |
| 16688 |
<section> |
| 16689 |
<title>Networking Tools</title> |
| 16690 |
<subsection> |
| 16691 |
<title>Optional: Installing a DHCP Client</title> |
| 16692 |
<body> |
| 16693 |
|
| 16694 |
<p> |
| 16695 |
If you require Gentoo to automatically obtain an IP address for your network |
| 16696 |
interface(s), you need to install <c>dhcpcd</c> (or any other DHCP Client) |
| 16697 |
on your system. If you don't do this now, you might not be able to connect |
| 16698 |
to the internet after the installation! |
| 16699 |
</p> |
| 16700 |
|
| 16701 |
<pre caption="Installing dhcpcd"> |
| 16702 |
# <i>emerge dhcpcd</i> |
| 16703 |
</pre> |
| 16704 |
|
| 16705 |
</body> |
| 16706 |
</subsection> |
| 16707 |
<subsection> |
| 16708 |
<title>Optional: Installing a PPPoE Client</title> |
| 16709 |
<body> |
| 16710 |
|
| 16711 |
<p> |
| 16712 |
If you need <c>rp-pppoe</c> to connect to the net, you need to install it. |
| 16713 |
</p> |
| 16714 |
|
| 16715 |
<pre caption="Installing rp-pppoe"> |
| 16716 |
# <i>USE="-X" emerge rp-pppoe</i> |
| 16717 |
</pre> |
| 16718 |
|
| 16719 |
<p> |
| 16720 |
The <c>USE="-X"</c> will prohibit xorg-x11 to be installed as a dependency |
| 16721 |
(<c>rp-pppoe</c> has graphical tools; if you want those enabled, you can |
| 16722 |
recompile <c>rp-pppoe</c> later on or have xorg-x11 installed now -- which takes a |
| 16723 |
long time to compile). |
| 16724 |
</p> |
| 16725 |
|
| 16726 |
<p> |
| 16727 |
Now continue with <uri link="?part=1&chap=10">Configuring the |
| 16728 |
Bootloader</uri>. |
| 16729 |
</p> |
| 16730 |
|
| 16731 |
</body> |
| 16732 |
</subsection> |
| 16733 |
</section> |
| 16734 |
</sections> |
| 16735 |
|
| 16736 |
|
| 16737 |
|
| 16738 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-bootloader.xml |
| 16739 |
|
| 16740 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-bootloader.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 16741 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-bootloader.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 16742 |
|
| 16743 |
Index: hb-install-x86-bootloader.xml |
| 16744 |
=================================================================== |
| 16745 |
<?xml version='1.0' encoding='UTF-8'?> |
| 16746 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 16747 |
|
| 16748 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 16749 |
<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
| 16750 |
|
| 16751 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-bootloader.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 16752 |
|
| 16753 |
<sections> |
| 16754 |
|
| 16755 |
<version>5.4</version> |
| 16756 |
<date>2006-01-19</date> |
| 16757 |
|
| 16758 |
<section> |
| 16759 |
<title>Making your Choice</title> |
| 16760 |
<subsection> |
| 16761 |
<title>Introduction</title> |
| 16762 |
<body> |
| 16763 |
|
| 16764 |
<p> |
| 16765 |
Now that your kernel is configured and compiled and the necessary system |
| 16766 |
configuration files are filled in correctly, it is time to install a |
| 16767 |
program that will fire up your kernel when you start the system. Such a |
| 16768 |
program is called a <e>bootloader</e>. For x86, Gentoo Linux provides <uri |
| 16769 |
link="#grub">GRUB</uri> and <uri link="#lilo">LILO</uri>. But before we |
| 16770 |
install one of these two bootloaders, we inform you how to configure framebuffer |
| 16771 |
(assuming you want it of course). With framebuffer you can run the Linux command |
| 16772 |
line with (limited) graphical features (such as using the nice bootsplash |
| 16773 |
image Gentoo provides). |
| 16774 |
</p> |
| 16775 |
|
| 16776 |
</body> |
| 16777 |
</subsection> |
| 16778 |
<subsection> |
| 16779 |
<title>Optional: Framebuffer</title> |
| 16780 |
<body> |
| 16781 |
|
| 16782 |
<p> |
| 16783 |
<e>If</e> you have configured your kernel with framebuffer support (or you used |
| 16784 |
<c>genkernel</c>'s default kernel configuration), you can activate it by adding |
| 16785 |
a <c>vga</c> and/or a <c>video</c> statement to your bootloader configuration |
| 16786 |
file. |
| 16787 |
</p> |
| 16788 |
|
| 16789 |
<p> |
| 16790 |
First of all you need to know what type of framebuffer device you're using. If |
| 16791 |
you use a Gentoo patched kernel tree (such as <c>gentoo-sources</c>) you will |
| 16792 |
have had the possibility of selecting <c>vesafb-tng</c> as the <e>VESA driver |
| 16793 |
type</e> (which is default for these kernel sources). If this is the case, you |
| 16794 |
are using <c>vesafb-tng</c> and do not need to set a <c>vga</c> statement. |
| 16795 |
Otherwise you are using the <c>vesafb</c> driver and need to set the <c>vga</c> |
| 16796 |
statement. |
| 16797 |
</p> |
| 16798 |
|
| 16799 |
<p> |
| 16800 |
The <c>vga</c> statement controls the resolution and color depth of your |
| 16801 |
framebuffer screen for <c>vesafb</c>. As stated in |
| 16802 |
<path>/usr/src/linux/Documentation/fb/vesafb.txt</path> (which gets installed |
| 16803 |
when you install a kernel source package), you need to pass the VESA number |
| 16804 |
corresponding to the requested resolution and color depth to it. |
| 16805 |
</p> |
| 16806 |
|
| 16807 |
<p> |
| 16808 |
The following table lists the available resolutions and colordepths and matches |
| 16809 |
those against the value that you need to pass on to the <c>vga</c> statement. |
| 16810 |
</p> |
| 16811 |
|
| 16812 |
<table> |
| 16813 |
<tr> |
| 16814 |
<ti></ti> |
| 16815 |
<th>640x480</th> |
| 16816 |
<th>800x600</th> |
| 16817 |
<th>1024x768</th> |
| 16818 |
<th>1280x1024</th> |
| 16819 |
</tr> |
| 16820 |
<tr> |
| 16821 |
<th>256</th> |
| 16822 |
<ti>0x301</ti> |
| 16823 |
<ti>0x303</ti> |
| 16824 |
<ti>0x305</ti> |
| 16825 |
<ti>0x307</ti> |
| 16826 |
</tr> |
| 16827 |
<tr> |
| 16828 |
<th>32k</th> |
| 16829 |
<ti>0x310</ti> |
| 16830 |
<ti>0x313</ti> |
| 16831 |
<ti>0x316</ti> |
| 16832 |
<ti>0x319</ti> |
| 16833 |
</tr> |
| 16834 |
<tr> |
| 16835 |
<th>64k</th> |
| 16836 |
<ti>0x311</ti> |
| 16837 |
<ti>0x314</ti> |
| 16838 |
<ti>0x317</ti> |
| 16839 |
<ti>0x31A</ti> |
| 16840 |
</tr> |
| 16841 |
<tr> |
| 16842 |
<th>16M</th> |
| 16843 |
<ti>0x312</ti> |
| 16844 |
<ti>0x315</ti> |
| 16845 |
<ti>0x318</ti> |
| 16846 |
<ti>0x31B</ti> |
| 16847 |
</tr> |
| 16848 |
</table> |
| 16849 |
|
| 16850 |
<p> |
| 16851 |
The <c>video</c> statement controls framebuffer display options. It needs to be |
| 16852 |
given the framebuffer driver (<c>vesafb</c> for 2.6 kernels, or <c>vesa</c> for |
| 16853 |
2.4 kernels) followed by the control statements you wish to enable. All |
| 16854 |
variables are listed in <path>/usr/src/linux/Documentation/fb/vesafb.txt</path>, |
| 16855 |
but we'll inform you about three most-used options: |
| 16856 |
</p> |
| 16857 |
|
| 16858 |
<table> |
| 16859 |
<tr> |
| 16860 |
<th>Control</th> |
| 16861 |
<th>Description</th> |
| 16862 |
</tr> |
| 16863 |
<tr> |
| 16864 |
<ti>ywrap</ti> |
| 16865 |
<ti> |
| 16866 |
Assume that the graphical card can wrap around its memory (i.e. continue at |
| 16867 |
the beginning when it has approached the end) |
| 16868 |
</ti> |
| 16869 |
</tr> |
| 16870 |
<tr> |
| 16871 |
<ti>mtrr</ti> |
| 16872 |
<ti> |
| 16873 |
Setup MTRR registers |
| 16874 |
</ti> |
| 16875 |
</tr> |
| 16876 |
<tr> |
| 16877 |
<ti><c>mode</c></ti> |
| 16878 |
<ti> |
| 16879 |
(<c>vesafb-tng</c> only)<br/> |
| 16880 |
Set up the resolution, color depth and refresh rate. For instance, |
| 16881 |
<c>1024x768-32@85</c> for a resolution of 1024x768, 32 bit color depth and a |
| 16882 |
refresh rate of 85 Hz. |
| 16883 |
</ti> |
| 16884 |
</tr> |
| 16885 |
</table> |
| 16886 |
|
| 16887 |
<p> |
| 16888 |
The result of those two statements could be something like <c>vga=0x318 |
| 16889 |
video=vesafb:mtrr,ywrap</c> or <c>video=vesafb:mtrr,ywrap,1024x768-32@85</c>. |
| 16890 |
Remember (or write down) this setting; you will need it shortly. |
| 16891 |
</p> |
| 16892 |
|
| 16893 |
<p> |
| 16894 |
Now continue by installing <uri link="#grub">GRUB</uri> <e>or</e> <uri |
| 16895 |
link="#lilo">LILO</uri>. |
| 16896 |
</p> |
| 16897 |
|
| 16898 |
</body> |
| 16899 |
</subsection> |
| 16900 |
</section> |
| 16901 |
<section id="grub"> |
| 16902 |
<title>Default: Using GRUB</title> |
| 16903 |
<subsection> |
| 16904 |
<title>Understanding GRUB's terminology</title> |
| 16905 |
<body> |
| 16906 |
|
| 16907 |
<p> |
| 16908 |
The most critical part of understanding GRUB is getting comfortable with |
| 16909 |
how GRUB refers to hard drives and partitions. Your Linux partition |
| 16910 |
<path>/dev/hda1</path> will most likely be called <path>(hd0,0)</path> under |
| 16911 |
GRUB. Notice the parenthesis around the <path>hd0,0</path> - they are required. |
| 16912 |
</p> |
| 16913 |
|
| 16914 |
<p> |
| 16915 |
Hard drives count from zero rather than "a" and partitions start at zero |
| 16916 |
rather than one. Be aware too that with the hd devices, only hard drives are |
| 16917 |
counted, not atapi-ide devices such as cdrom players and burners. Also, the |
| 16918 |
same construct is used with SCSI drives. (Normally they get higher numbers |
| 16919 |
than IDE drives except when the BIOS is configured to boot from SCSI devices.) |
| 16920 |
When you ask the BIOS to boot from a different hard disk (for instance your |
| 16921 |
primary slave), <e>that</e> harddisk is seen as <path>hd0</path>. |
| 16922 |
</p> |
| 16923 |
|
| 16924 |
<p> |
| 16925 |
Assuming you have a hard drive on <path>/dev/hda</path>, a cdrom player on |
| 16926 |
<path>/dev/hdb</path>, a burner on <path>/dev/hdc</path>, a second hard drive |
| 16927 |
on <path>/dev/hdd</path> and no SCSI hard drive, <path>/dev/hdd7</path> gets |
| 16928 |
translated to <path>(hd1,6)</path>. It might sound tricky and tricky it is |
| 16929 |
indeed, but as we will see, GRUB offers a tab completion mechanism |
| 16930 |
that comes handy for those of you having a lot of hard drives and |
| 16931 |
partitions and who are a little lost in the GRUB numbering scheme. |
| 16932 |
</p> |
| 16933 |
|
| 16934 |
<p> |
| 16935 |
Having gotten the feel for that, it is time to install GRUB. |
| 16936 |
</p> |
| 16937 |
|
| 16938 |
</body> |
| 16939 |
</subsection> |
| 16940 |
<subsection> |
| 16941 |
<title>Installing GRUB</title> |
| 16942 |
<body> |
| 16943 |
|
| 16944 |
<p> |
| 16945 |
To install GRUB, let's first emerge it: |
| 16946 |
</p> |
| 16947 |
|
| 16948 |
<pre caption="Installing GRUB"> |
| 16949 |
# <i>emerge grub</i> |
| 16950 |
</pre> |
| 16951 |
|
| 16952 |
<p> |
| 16953 |
Although GRUB is now installed, we still need to write up a |
| 16954 |
configuration file for it and place GRUB in our MBR so that GRUB automatically |
| 16955 |
boots your newly created kernel. Create <path>/boot/grub/grub.conf</path> with |
| 16956 |
<c>nano</c> (or, if applicable, another editor): |
| 16957 |
</p> |
| 16958 |
|
| 16959 |
<pre caption="Creating /boot/grub/grub.conf"> |
| 16960 |
# <i>nano -w /boot/grub/grub.conf</i> |
| 16961 |
</pre> |
| 16962 |
|
| 16963 |
<p> |
| 16964 |
Now we are going to write up a <path>grub.conf</path>. Below you'll |
| 16965 |
find two possible <path>grub.conf</path> for the partitioning example we use |
| 16966 |
in this guide. We've |
| 16967 |
only extensively commented the first <path>grub.conf</path>. Make sure you use |
| 16968 |
<e>your</e> kernel image filename and, if appropriate, <e>your</e> initrd image |
| 16969 |
filename. |
| 16970 |
</p> |
| 16971 |
|
| 16972 |
<ul> |
| 16973 |
<li> |
| 16974 |
The first <path>grub.conf</path> is for people who have not used |
| 16975 |
<c>genkernel</c> to build their kernel |
| 16976 |
</li> |
| 16977 |
<li> |
| 16978 |
The second <path>grub.conf</path> is for people who have used |
| 16979 |
<c>genkernel</c> to build their kernel |
| 16980 |
</li> |
| 16981 |
</ul> |
| 16982 |
|
| 16983 |
<note> |
| 16984 |
If your root filesystem is JFS, you <e>must</e> add " ro" to the <c>kernel</c> |
| 16985 |
line since JFS needs to replay its log before it allows read-write mounting. |
| 16986 |
</note> |
| 16987 |
|
| 16988 |
<pre caption="grub.conf for non-genkernel users"> |
| 16989 |
<comment># Which listing to boot as default. 0 is the first, 1 the second etc.</comment> |
| 16990 |
default 0 |
| 16991 |
<comment># How many seconds to wait before the default listing is booted.</comment> |
| 16992 |
timeout 30 |
| 16993 |
<comment># Nice, fat splash-image to spice things up :) |
| 16994 |
# Comment out if you don't have a graphics card installed</comment> |
| 16995 |
splashimage=(hd0,0)/boot/grub/splash.xpm.gz |
| 16996 |
|
| 16997 |
title=Gentoo Linux 2.6.12-r10 |
| 16998 |
<comment># Partition where the kernel image (or operating system) is located</comment> |
| 16999 |
root (hd0,0) |
| 17000 |
kernel /boot/kernel-2.6.12-gentoo-r10 root=/dev/hda3 |
| 17001 |
|
| 17002 |
<comment># The next four lines are only if you dualboot with a Windows system.</comment> |
| 17003 |
<comment># In this case, Windows is hosted on /dev/hda6.</comment> |
| 17004 |
title=Windows XP |
| 17005 |
rootnoverify (hd0,5) |
| 17006 |
makeactive |
| 17007 |
chainloader +1 |
| 17008 |
</pre> |
| 17009 |
|
| 17010 |
<pre caption="grub.conf for genkernel users"> |
| 17011 |
default 0 |
| 17012 |
timeout 30 |
| 17013 |
splashimage=(hd0,0)/boot/grub/splash.xpm.gz |
| 17014 |
|
| 17015 |
title=Gentoo Linux 2.6.12-r10 |
| 17016 |
root (hd0,0) |
| 17017 |
kernel /boot/kernel-genkernel-x86-2.6.12-gentoo-r10 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 udev |
| 17018 |
initrd /boot/initramfs-genkernel-x86-2.6.12-gentoo-r10 |
| 17019 |
|
| 17020 |
<comment># Only in case you want to dual-boot</comment> |
| 17021 |
title=Windows XP |
| 17022 |
root (hd0,5) |
| 17023 |
makeactive |
| 17024 |
chainloader +1 |
| 17025 |
</pre> |
| 17026 |
|
| 17027 |
<p> |
| 17028 |
If you used a different partitioning scheme and/or kernel image, adjust |
| 17029 |
accordingly. However, make sure that anything that follows a GRUB-device (such |
| 17030 |
as <path>(hd0,0)</path>) is relative to the mountpoint, not the root. In other |
| 17031 |
words, <path>(hd0,0)/grub/splash.xpm.gz</path> is in reality |
| 17032 |
<path>/boot/grub/splash.xpm.gz</path> since <path>(hd0,0)</path> is |
| 17033 |
<path>/boot</path>. |
| 17034 |
</p> |
| 17035 |
|
| 17036 |
<p> |
| 17037 |
Besides, if you chose to use a different partitioning scheme and did not put |
| 17038 |
<path>/boot</path> in a separate partition, the <path>/boot</path> prefix used |
| 17039 |
in the above code samples is really <e>required</e>. If you followed our |
| 17040 |
suggested partitioning plan, the <path>/boot</path> prefix it not required, but |
| 17041 |
a <path>boot</path> symlink makes it work. In short, the above examples should |
| 17042 |
work whether you defined a separate <path>/boot</path> partition or not. |
| 17043 |
</p> |
| 17044 |
|
| 17045 |
<p> |
| 17046 |
If you need to pass any additional options to the kernel, simply add |
| 17047 |
them to the end of the kernel command. We're already passing one option |
| 17048 |
(<c>root=/dev/hda3</c> or <c>real_root=/dev/hda3</c>), but you can pass others |
| 17049 |
as well, such as the <c>video</c> and/or <c>vga</c> statements for framebuffer |
| 17050 |
as we discussed previously. |
| 17051 |
</p> |
| 17052 |
|
| 17053 |
<p> |
| 17054 |
If you're using a 2.6.7 or higher kernel and you jumpered your harddrive |
| 17055 |
because the BIOS can't handle large harddrives you'll need to append |
| 17056 |
<c>hdx=stroke</c>. |
| 17057 |
</p> |
| 17058 |
|
| 17059 |
<p> |
| 17060 |
<c>genkernel</c> users should know that their kernels use the same boot options |
| 17061 |
as is used for the Installation CD. For instance, if you have SCSI devices, you |
| 17062 |
should add <c>doscsi</c> as kernel option. |
| 17063 |
</p> |
| 17064 |
|
| 17065 |
<p> |
| 17066 |
Now save the <path>grub.conf</path> file and exit. You still need to install |
| 17067 |
GRUB in the MBR (Master Boot Record) so that GRUB is automatically executed when |
| 17068 |
you boot your system. |
| 17069 |
</p> |
| 17070 |
|
| 17071 |
<p> |
| 17072 |
The GRUB developers recommend the use of <c>grub-install</c>. However, if for |
| 17073 |
some reason <c>grub-install</c> fails to work correctly you still have the |
| 17074 |
option to manually install GRUB. |
| 17075 |
</p> |
| 17076 |
|
| 17077 |
<p> |
| 17078 |
Continue with <uri link="#grub-install-auto">Default: Setting up GRUB using |
| 17079 |
grub-install</uri> or <uri link="#grub-install-manual">Alternative: Setting up |
| 17080 |
GRUB using manual instructions</uri>. |
| 17081 |
</p> |
| 17082 |
|
| 17083 |
</body> |
| 17084 |
</subsection> |
| 17085 |
<subsection id="grub-install-auto"> |
| 17086 |
<title>Default: Setting up GRUB using grub-install</title> |
| 17087 |
<body> |
| 17088 |
|
| 17089 |
<p> |
| 17090 |
To install GRUB you will need to issue the <c>grub-install</c> command. |
| 17091 |
However, <c>grub-install</c> won't work off-the-shelf since we are inside a |
| 17092 |
chrooted environment. We need to create <path>/etc/mtab</path> which lists all |
| 17093 |
mounted filesystems. Fortunately, there is an easy way to accomplish this - |
| 17094 |
just copy over <path>/proc/mounts</path> to <path>/etc/mtab</path>, excluding |
| 17095 |
the <c>rootfs</c> line if you haven't created a separate boot partition. The |
| 17096 |
following command will work in both cases: |
| 17097 |
</p> |
| 17098 |
|
| 17099 |
<pre caption="Creating /etc/mtab"> |
| 17100 |
# <i>grep -v rootfs /proc/mounts > /etc/mtab</i> |
| 17101 |
</pre> |
| 17102 |
|
| 17103 |
<p> |
| 17104 |
Now we can install GRUB using <c>grub-install</c>: |
| 17105 |
</p> |
| 17106 |
|
| 17107 |
<pre caption="Running grub-install"> |
| 17108 |
# <i>grub-install /dev/hda</i> |
| 17109 |
</pre> |
| 17110 |
|
| 17111 |
<p> |
| 17112 |
If you have more questions regarding GRUB, please consult the <uri |
| 17113 |
link="http://www.gnu.org/software/grub/grub-faq.html">GRUB FAQ</uri> or the <uri |
| 17114 |
link="http://www.gnu.org/software/grub/manual/">GRUB Manual</uri>. |
| 17115 |
</p> |
| 17116 |
|
| 17117 |
<p> |
| 17118 |
Continue with <uri link="#reboot">Rebooting the System</uri>. |
| 17119 |
</p> |
| 17120 |
|
| 17121 |
</body> |
| 17122 |
</subsection> |
| 17123 |
<subsection id="grub-install-manual"> |
| 17124 |
<title>Alternative: Setting up GRUB using manual instructions</title> |
| 17125 |
<body> |
| 17126 |
|
| 17127 |
<p> |
| 17128 |
To start configuring GRUB, you type in <c>grub</c>. You'll be presented |
| 17129 |
with the <path>grub></path> grub command-line prompt. Now, you need to type |
| 17130 |
in the right commands to install the GRUB boot record onto your hard drive. |
| 17131 |
</p> |
| 17132 |
|
| 17133 |
<pre caption =" Starting the GRUB shell"> |
| 17134 |
# <i>grub</i> |
| 17135 |
</pre> |
| 17136 |
|
| 17137 |
<note> |
| 17138 |
If your system does not have any floppy drives, add the <c>--no-floppy</c> |
| 17139 |
option to the above command to prevent grub from probing the (non-existing) |
| 17140 |
floppy drives. |
| 17141 |
</note> |
| 17142 |
|
| 17143 |
<p> |
| 17144 |
In the example configuration we want to install GRUB so that it reads its |
| 17145 |
information from the boot-partition <path>/dev/hda1</path>, and installs the |
| 17146 |
GRUB boot record on the hard drive's MBR (master boot record) so that the first |
| 17147 |
thing we see when we turn on the computer is the GRUB prompt. Of course, if you |
| 17148 |
haven't followed the example configuration during the installation, |
| 17149 |
change the commands accordingly. |
| 17150 |
</p> |
| 17151 |
|
| 17152 |
<p> |
| 17153 |
The tab completion mechanism of GRUB can be used from within GRUB. |
| 17154 |
For instance, if you type in "<c>root (</c>" followed by a TAB, you will |
| 17155 |
be presented with a list of devices (such as <path>hd0</path>). If you |
| 17156 |
type in "<c>root (hd0,</c>" followed by a TAB, you will receive a list |
| 17157 |
of available partitions to choose from (such as <path>hd0,0</path>). |
| 17158 |
</p> |
| 17159 |
|
| 17160 |
<p> |
| 17161 |
By using the tab completion, setting up GRUB should be not that hard. |
| 17162 |
Now go on, configure GRUB, shall we? :-) |
| 17163 |
</p> |
| 17164 |
|
| 17165 |
<pre caption =" Installing GRUB in the MBR"> |
| 17166 |
grub> <i>root (hd0,0)</i> <comment>(Specify where your /boot partition resides)</comment> |
| 17167 |
grub> <i>setup (hd0)</i> <comment>(Install GRUB in the MBR)</comment> |
| 17168 |
grub> <i>quit</i> <comment>(Exit the GRUB shell)</comment> |
| 17169 |
</pre> |
| 17170 |
|
| 17171 |
<note> |
| 17172 |
If you want to install GRUB in a certain partition instead of the MBR, |
| 17173 |
you have to alter the <c>setup</c> command so it points to the right |
| 17174 |
partition. For instance, if you want GRUB installed in |
| 17175 |
<path>/dev/hda3</path>, then the command becomes <c>setup (hd0,2)</c>. |
| 17176 |
Few users however want to do this. |
| 17177 |
</note> |
| 17178 |
|
| 17179 |
<p> |
| 17180 |
If you have more questions regarding GRUB, please consult the <uri |
| 17181 |
link="http://www.gnu.org/software/grub/grub-faq.html">GRUB FAQ</uri> or the <uri |
| 17182 |
link="http://www.gnu.org/software/grub/manual/">GRUB Manual</uri>. |
| 17183 |
</p> |
| 17184 |
|
| 17185 |
<note> |
| 17186 |
When you reinstall a kernel, you do not need to copy over the files anymore. |
| 17187 |
Just run <c>make install</c> after compiling the kernel; it will automatically |
| 17188 |
copy the necessary files and adjust the GRUB configuration. |
| 17189 |
</note> |
| 17190 |
|
| 17191 |
<p> |
| 17192 |
Continue with <uri link="#reboot">Rebooting the System</uri>. |
| 17193 |
</p> |
| 17194 |
|
| 17195 |
</body> |
| 17196 |
</subsection> |
| 17197 |
</section> |
| 17198 |
<section id="lilo"> |
| 17199 |
<title>Alternative: Using LILO</title> |
| 17200 |
<subsection> |
| 17201 |
<title>Installing LILO</title> |
| 17202 |
<body> |
| 17203 |
|
| 17204 |
<p> |
| 17205 |
LILO, the LInuxLOader, is the tried and true workhorse of Linux |
| 17206 |
bootloaders. However, it lacks some features that GRUB has (which is |
| 17207 |
also the reason why GRUB is currently gaining popularity). The reason |
| 17208 |
why LILO is still used is that, on some systems, GRUB doesn't work and |
| 17209 |
LILO does. Of course, it is also used because some people know LILO and |
| 17210 |
want to stick with it. Either way, Gentoo supports both, and apparently |
| 17211 |
you have chosen to use LILO. |
| 17212 |
</p> |
| 17213 |
|
| 17214 |
<p> |
| 17215 |
Installing LILO is a breeze; just use <c>emerge</c>. |
| 17216 |
</p> |
| 17217 |
|
| 17218 |
<pre caption = "Installing LILO"> |
| 17219 |
# <i>emerge lilo</i> |
| 17220 |
</pre> |
| 17221 |
|
| 17222 |
</body> |
| 17223 |
</subsection> |
| 17224 |
<subsection> |
| 17225 |
<title>Configuring LILO</title> |
| 17226 |
<body> |
| 17227 |
|
| 17228 |
<p> |
| 17229 |
To configure LILO, you must create <path>/etc/lilo.conf</path>. Fire up |
| 17230 |
your favorite editor (in this handbook we use <c>nano</c> for |
| 17231 |
consistency) and create the file. |
| 17232 |
</p> |
| 17233 |
|
| 17234 |
<pre caption = "Creating /etc/lilo.conf"> |
| 17235 |
# <i>nano -w /etc/lilo.conf</i> |
| 17236 |
</pre> |
| 17237 |
|
| 17238 |
<p> |
| 17239 |
Some sections ago we have asked you to remember the kernel-image name |
| 17240 |
you have created. In the next example <path>lilo.conf</path> we also use the |
| 17241 |
example partitioning scheme. There are two separate parts: |
| 17242 |
</p> |
| 17243 |
|
| 17244 |
<ul> |
| 17245 |
<li> |
| 17246 |
One for those who have not used <c>genkernel</c> to build their kernel |
| 17247 |
</li> |
| 17248 |
<li> |
| 17249 |
One for those who have used <c>genkernel</c> to build their kernel |
| 17250 |
</li> |
| 17251 |
</ul> |
| 17252 |
|
| 17253 |
<p> |
| 17254 |
Make sure you use <e>your</e> kernel image filename and, if appropriate, |
| 17255 |
<e>your</e> initrd image filename. |
| 17256 |
</p> |
| 17257 |
|
| 17258 |
<note> |
| 17259 |
If your root filesystem is JFS, you <e>must</e> add an <c>append="ro"</c> line |
| 17260 |
to each boot image since JFS needs to replay its log before it allows |
| 17261 |
read-write mounting. |
| 17262 |
</note> |
| 17263 |
|
| 17264 |
<pre caption="Example /etc/lilo.conf"> |
| 17265 |
boot=/dev/hda <comment># Install LILO in the MBR</comment> |
| 17266 |
prompt <comment># Give the user the chance to select another section</comment> |
| 17267 |
timeout=50 <comment># Wait 5 (five) seconds before booting the default section</comment> |
| 17268 |
default=gentoo <comment># When the timeout has passed, boot the "gentoo" section</comment> |
| 17269 |
|
| 17270 |
<comment># For non-genkernel users</comment> |
| 17271 |
image=/boot/kernel-2.6.12-gentoo-r10 |
| 17272 |
label=gentoo <comment># Name we give to this section</comment> |
| 17273 |
read-only <comment># Start with a read-only root. Do not alter!</comment> |
| 17274 |
root=/dev/hda3 <comment># Location of the root filesystem</comment> |
| 17275 |
|
| 17276 |
<comment># For genkernel users</comment> |
| 17277 |
image=/boot/kernel-genkernel-x86-2.6.12-gentoo-r10 |
| 17278 |
label=gentoo |
| 17279 |
read-only |
| 17280 |
root=/dev/ram0 |
| 17281 |
append="init=/linuxrc ramdisk=8192 real_root=/dev/hda3 udev" |
| 17282 |
initrd=/boot/initramfs-genkernel-x86-2.6.12-gentoo-r10 |
| 17283 |
|
| 17284 |
<comment># The next two lines are only if you dualboot with a Windows system.</comment> |
| 17285 |
<comment># In this case, Windows is hosted on /dev/hda6.</comment> |
| 17286 |
other=/dev/hda6 |
| 17287 |
label=windows |
| 17288 |
</pre> |
| 17289 |
|
| 17290 |
<note> |
| 17291 |
If you use a different partitioning scheme and/or kernel image, adjust |
| 17292 |
accordingly. |
| 17293 |
</note> |
| 17294 |
|
| 17295 |
<p> |
| 17296 |
If you need to pass any additional options to the kernel, add an |
| 17297 |
<c>append</c> statement to the section. As an example, we add the |
| 17298 |
<c>video</c> statement to enable framebuffer: |
| 17299 |
</p> |
| 17300 |
|
| 17301 |
<pre caption="Using append to add kernel options"> |
| 17302 |
image=/boot/kernel-2.6.12-gentoo-r10 |
| 17303 |
label=gentoo |
| 17304 |
read-only |
| 17305 |
root=/dev/hda3 |
| 17306 |
<i>append="video=vesafb:mtrr,ywrap,1024x768-32@85"</i> |
| 17307 |
</pre> |
| 17308 |
|
| 17309 |
<p> |
| 17310 |
If you're using a 2.6.7 or higher kernel and you jumpered your harddrive |
| 17311 |
because the BIOS can't handle large harddrives you'll need to append |
| 17312 |
<c>hdx=stroke</c>. |
| 17313 |
</p> |
| 17314 |
|
| 17315 |
<p> |
| 17316 |
<c>genkernel</c> users should know that their kernels use the same boot options |
| 17317 |
as is used for the Installation CD. For instance, if you have SCSI devices, you |
| 17318 |
should add <c>doscsi</c> as kernel option. |
| 17319 |
</p> |
| 17320 |
|
| 17321 |
|
| 17322 |
<p> |
| 17323 |
Now save the file and exit. To finish up, you have to run <c>/sbin/lilo</c> so |
| 17324 |
LILO can apply the <path>/etc/lilo.conf</path> to your system (i.e. install |
| 17325 |
itself on the disk). Keep in mind that you'll also have to rerun |
| 17326 |
<c>/sbin/lilo</c> every time you install a new kernel or make any changes to |
| 17327 |
the menu. |
| 17328 |
</p> |
| 17329 |
|
| 17330 |
<pre caption = "Finishing the LILO installation"> |
| 17331 |
# <i>/sbin/lilo</i> |
| 17332 |
</pre> |
| 17333 |
|
| 17334 |
<note> |
| 17335 |
When you reinstall a kernel, you do not need to copy over the files anymore. |
| 17336 |
Just run <c>make install</c> after compiling the kernel; it will automatically |
| 17337 |
copy the necessary files and adjust the LILO configuration. |
| 17338 |
</note> |
| 17339 |
|
| 17340 |
<p> |
| 17341 |
You can now continue with <uri link="#reboot">Rebooting the System</uri>. |
| 17342 |
</p> |
| 17343 |
|
| 17344 |
</body> |
| 17345 |
</subsection> |
| 17346 |
</section> |
| 17347 |
<section id="reboot"> |
| 17348 |
<title>Rebooting the System</title> |
| 17349 |
<subsection> |
| 17350 |
<body> |
| 17351 |
|
| 17352 |
<p> |
| 17353 |
Exit the chrooted environment and unmount all mounted partitions. Then type in |
| 17354 |
that one magical command you have been waiting for: <c>reboot</c>. |
| 17355 |
</p> |
| 17356 |
|
| 17357 |
<pre caption="Unmounting all partitions and rebooting"> |
| 17358 |
# <i>exit</i> |
| 17359 |
cdimage ~# <i>cd</i> |
| 17360 |
cdimage ~# <i>umount /mnt/gentoo/boot /mnt/gentoo/dev /mnt/gentoo/proc /mnt/gentoo</i> |
| 17361 |
cdimage ~# <i>reboot</i> |
| 17362 |
</pre> |
| 17363 |
|
| 17364 |
<p> |
| 17365 |
Of course, don't forget to remove the bootable CD, otherwise the CD will be |
| 17366 |
booted again instead of your new Gentoo system. |
| 17367 |
</p> |
| 17368 |
|
| 17369 |
<p> |
| 17370 |
Once rebooted in your Gentoo installation, finish up with <uri |
| 17371 |
link="?part=1&chap=11">Finalizing your Gentoo Installation</uri>. |
| 17372 |
</p> |
| 17373 |
|
| 17374 |
</body> |
| 17375 |
</subsection> |
| 17376 |
</section> |
| 17377 |
</sections> |
| 17378 |
|
| 17379 |
|
| 17380 |
|
| 17381 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-disk.xml |
| 17382 |
|
| 17383 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-disk.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 17384 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-disk.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 17385 |
|
| 17386 |
Index: hb-install-x86-disk.xml |
| 17387 |
=================================================================== |
| 17388 |
<?xml version='1.0' encoding='UTF-8'?> |
| 17389 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 17390 |
|
| 17391 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 17392 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 17393 |
|
| 17394 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-disk.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 17395 |
|
| 17396 |
<sections> |
| 17397 |
|
| 17398 |
<version>5.2</version> |
| 17399 |
<date>2006-01-01</date> |
| 17400 |
|
| 17401 |
<section> |
| 17402 |
<title>Introduction to Block Devices</title> |
| 17403 |
<subsection> |
| 17404 |
<title>Block Devices</title> |
| 17405 |
<body> |
| 17406 |
|
| 17407 |
<p> |
| 17408 |
We'll take a good look at disk-oriented aspects of Gentoo Linux |
| 17409 |
and Linux in general, including Linux filesystems, partitions and block devices. |
| 17410 |
Then, once you're familiar with the ins and outs of disks and filesystems, |
| 17411 |
you'll be guided through the process of setting up partitions and filesystems |
| 17412 |
for your Gentoo Linux installation. |
| 17413 |
</p> |
| 17414 |
|
| 17415 |
<p> |
| 17416 |
To begin, we'll introduce <e>block devices</e>. The most famous block device is |
| 17417 |
probably the one that represents the first IDE drive in a Linux system, namely |
| 17418 |
<path>/dev/hda</path>. If your system uses SCSI or SATA drives, then your |
| 17419 |
first hard drive would be <path>/dev/sda</path>. |
| 17420 |
</p> |
| 17421 |
|
| 17422 |
<p> |
| 17423 |
The block devices above represent an abstract interface to the disk. User |
| 17424 |
programs can use these block devices to interact with your disk without worrying |
| 17425 |
about whether your drives are IDE, SCSI or something else. The program can |
| 17426 |
simply address the storage on the disk as a bunch of contiguous, |
| 17427 |
randomly-accessible 512-byte blocks. |
| 17428 |
</p> |
| 17429 |
|
| 17430 |
</body> |
| 17431 |
</subsection> |
| 17432 |
<subsection> |
| 17433 |
<title>Partitions</title> |
| 17434 |
<body> |
| 17435 |
|
| 17436 |
<p> |
| 17437 |
Although it is theoretically possible to use a full disk to house your Linux |
| 17438 |
system, this is almost never done in practice. Instead, full disk block devices |
| 17439 |
are split up in smaller, more manageable block devices. On x86 systems, |
| 17440 |
these are called <e>partitions</e>. |
| 17441 |
</p> |
| 17442 |
|
| 17443 |
<p> |
| 17444 |
Partitions are divided in three types: |
| 17445 |
<e>primary</e>, <e>extended</e> and <e>logical</e>. |
| 17446 |
</p> |
| 17447 |
|
| 17448 |
<p> |
| 17449 |
A <e>primary</e> partition is a partition which has its information stored in |
| 17450 |
the MBR (master boot record). As an MBR is very small (512 bytes) only four |
| 17451 |
primary partitions can be defined (for instance, <path>/dev/hda1</path> to |
| 17452 |
<path>/dev/hda4</path>). |
| 17453 |
</p> |
| 17454 |
|
| 17455 |
<p> |
| 17456 |
An <e>extended</e> partition is a special primary partition (meaning the |
| 17457 |
extended partition must be one of the four possible primary partitions) which |
| 17458 |
contains more partitions. Such a partition didn't exist originally, but as |
| 17459 |
four partitions were too few, it was brought to life to extend the formatting |
| 17460 |
scheme without losing backward compatibility. |
| 17461 |
</p> |
| 17462 |
|
| 17463 |
<p> |
| 17464 |
A <e>logical</e> partition is a partition inside the extended partition. Their |
| 17465 |
definitions aren't placed inside the MBR, but are declared inside the extended |
| 17466 |
partition. |
| 17467 |
</p> |
| 17468 |
|
| 17469 |
</body> |
| 17470 |
</subsection> |
| 17471 |
<subsection> |
| 17472 |
<title>Advanced Storage</title> |
| 17473 |
<body> |
| 17474 |
|
| 17475 |
<p> |
| 17476 |
The x86 Installation CDs provide support for EVMS and LVM2. EVMS and LVM2 |
| 17477 |
increase the flexibility offered by your partitioning setup. During the |
| 17478 |
installation instructions, we will focus on "regular" partitions, but it is |
| 17479 |
still good to know EVMS and LVM2 are supported as well. |
| 17480 |
</p> |
| 17481 |
|
| 17482 |
</body> |
| 17483 |
</subsection> |
| 17484 |
</section> |
| 17485 |
<section> |
| 17486 |
<title>Designing a Partitioning Scheme</title> |
| 17487 |
<subsection> |
| 17488 |
<title>Default Partitioning Scheme</title> |
| 17489 |
<body> |
| 17490 |
|
| 17491 |
<p> |
| 17492 |
If you are not interested in drawing up a partitioning scheme for your system, |
| 17493 |
you can use the partitioning scheme we use throughout this book: |
| 17494 |
</p> |
| 17495 |
|
| 17496 |
<table> |
| 17497 |
<tr> |
| 17498 |
<th>Partition</th> |
| 17499 |
<th>Filesystem</th> |
| 17500 |
<th>Size</th> |
| 17501 |
<th>Description</th> |
| 17502 |
</tr> |
| 17503 |
<tr> |
| 17504 |
<ti><path>/dev/hda1</path></ti> |
| 17505 |
<ti>ext2</ti> |
| 17506 |
<ti>32M</ti> |
| 17507 |
<ti>Boot partition</ti> |
| 17508 |
</tr> |
| 17509 |
<tr> |
| 17510 |
<ti><path>/dev/hda2</path></ti> |
| 17511 |
<ti>(swap)</ti> |
| 17512 |
<ti>512M</ti> |
| 17513 |
<ti>Swap partition</ti> |
| 17514 |
</tr> |
| 17515 |
<tr> |
| 17516 |
<ti><path>/dev/hda3</path></ti> |
| 17517 |
<ti>ext3</ti> |
| 17518 |
<ti>Rest of the disk</ti> |
| 17519 |
<ti>Root partition</ti> |
| 17520 |
</tr> |
| 17521 |
</table> |
| 17522 |
|
| 17523 |
<p> |
| 17524 |
If you are interested in knowing how big a partition should be, or even how |
| 17525 |
many partitions you need, read on. Otherwise continue now with partitioning |
| 17526 |
your disk by reading <uri link="#fdisk">Using fdisk to Partition your |
| 17527 |
Disk</uri>. |
| 17528 |
</p> |
| 17529 |
|
| 17530 |
</body> |
| 17531 |
</subsection> |
| 17532 |
<subsection> |
| 17533 |
<title>How Many and How Big?</title> |
| 17534 |
<body> |
| 17535 |
|
| 17536 |
<p> |
| 17537 |
The number of partitions is highly dependent on your environment. For instance, |
| 17538 |
if you have lots of users, you will most likely want to have your |
| 17539 |
<path>/home</path> separate as it increases security and makes backups easier. |
| 17540 |
If you are installing Gentoo to perform as a mailserver, your |
| 17541 |
<path>/var</path> should be separate as all mails are stored inside |
| 17542 |
<path>/var</path>. A good choice of filesystem will then maximise your |
| 17543 |
performance. Gameservers will have a separate <path>/opt</path> as most gaming |
| 17544 |
servers are installed there. The reason is similar for <path>/home</path>: |
| 17545 |
security and backups. You will definitely want to keep <path>/usr</path> big: |
| 17546 |
not only will it contain the majority of applications, the Portage tree alone |
| 17547 |
takes around 500 Mbyte excluding the various sources that are stored in it. |
| 17548 |
</p> |
| 17549 |
|
| 17550 |
<p> |
| 17551 |
As you can see, it very much depends on what you want to achieve. Separate |
| 17552 |
partitions or volumes have the following advantages: |
| 17553 |
</p> |
| 17554 |
|
| 17555 |
<ul> |
| 17556 |
<li> |
| 17557 |
You can choose the best performing filesystem for each partition or volume |
| 17558 |
</li> |
| 17559 |
<li> |
| 17560 |
Your entire system cannot run out of free space if one defunct tool is |
| 17561 |
continuously writing files to a partition or volume |
| 17562 |
</li> |
| 17563 |
<li> |
| 17564 |
If necessary, file system checks are reduced in time, as multiple checks can |
| 17565 |
be done in parallel (although this advantage is more with multiple disks than |
| 17566 |
it is with multiple partitions) |
| 17567 |
</li> |
| 17568 |
<li> |
| 17569 |
Security can be enhanced by mounting some partitions or volumes read-only, |
| 17570 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
| 17571 |
</li> |
| 17572 |
</ul> |
| 17573 |
|
| 17574 |
<p> |
| 17575 |
However, multiple partitions have one big disadvantage: if not configured |
| 17576 |
properly, you might result in having a system with lots |
| 17577 |
of free space on one partition and none on another. There is also a 15-partition |
| 17578 |
limit for SCSI and SATA. |
| 17579 |
</p> |
| 17580 |
|
| 17581 |
<p> |
| 17582 |
As an example partitioning, we show you one for a 20GB disk, used as a |
| 17583 |
demonstration laptop (containing webserver, mailserver, gnome, ...): |
| 17584 |
</p> |
| 17585 |
|
| 17586 |
<pre caption="Filesystem usage example"> |
| 17587 |
Filesystem Type Size Used Avail Use% Mounted on |
| 17588 |
/dev/hda5 ext3 509M 132M 351M 28% / |
| 17589 |
/dev/hda2 ext3 5.0G 3.0G 1.8G 63% /home |
| 17590 |
/dev/hda7 ext3 7.9G 6.2G 1.3G 83% /usr |
| 17591 |
/dev/hda8 ext3 1011M 483M 477M 51% /opt |
| 17592 |
/dev/hda9 ext3 2.0G 607M 1.3G 32% /var |
| 17593 |
/dev/hda1 ext2 51M 17M 31M 36% /boot |
| 17594 |
/dev/hda6 swap 516M 12M 504M 2% <not mounted> |
| 17595 |
<comment>(Unpartitioned space for future usage: 2 GB)</comment> |
| 17596 |
</pre> |
| 17597 |
|
| 17598 |
<p> |
| 17599 |
<path>/usr</path> is rather full (83% used) here, but once |
| 17600 |
all software is installed, <path>/usr</path> doesn't tend to grow that much. |
| 17601 |
Although allocating a few gigabytes of disk space for <path>/var</path> may |
| 17602 |
seem excessive, remember that Portage uses this partition by default for |
| 17603 |
compiling packages. If you want to keep <path>/var</path> at a more reasonable |
| 17604 |
size, such as 1GB, you will need to alter your <c>PORTAGE_TMPDIR</c> variable |
| 17605 |
in <path>/etc/make.conf</path> to point to the partition with enough free space |
| 17606 |
for compiling extremely large packages such as OpenOffice. |
| 17607 |
</p> |
| 17608 |
|
| 17609 |
</body> |
| 17610 |
</subsection> |
| 17611 |
</section> |
| 17612 |
<section id="fdisk"> |
| 17613 |
<title>Using fdisk to Partition your Disk</title> |
| 17614 |
<subsection> |
| 17615 |
<body> |
| 17616 |
|
| 17617 |
<p> |
| 17618 |
The following parts explain how to create the example partition layout |
| 17619 |
described previously, namely: |
| 17620 |
</p> |
| 17621 |
|
| 17622 |
<table> |
| 17623 |
<tr> |
| 17624 |
<th>Partition</th> |
| 17625 |
<th>Description</th> |
| 17626 |
</tr> |
| 17627 |
<tr> |
| 17628 |
<ti><path>/dev/hda1</path></ti> |
| 17629 |
<ti>Boot partition</ti> |
| 17630 |
</tr> |
| 17631 |
<tr> |
| 17632 |
<ti><path>/dev/hda2</path></ti> |
| 17633 |
<ti>Swap partition</ti> |
| 17634 |
</tr> |
| 17635 |
<tr> |
| 17636 |
<ti><path>/dev/hda3</path></ti> |
| 17637 |
<ti>Root partition</ti> |
| 17638 |
</tr> |
| 17639 |
</table> |
| 17640 |
|
| 17641 |
<p> |
| 17642 |
Change your partition layout according to your own preference. |
| 17643 |
</p> |
| 17644 |
|
| 17645 |
</body> |
| 17646 |
</subsection> |
| 17647 |
<subsection> |
| 17648 |
<title>Viewing the Current Partition Layout</title> |
| 17649 |
<body> |
| 17650 |
|
| 17651 |
<p> |
| 17652 |
<c>fdisk</c> is a popular and powerful tool to split your disk into partitions. |
| 17653 |
Fire up <c>fdisk</c> on your disk (in our example, we use |
| 17654 |
<path>/dev/hda</path>): |
| 17655 |
</p> |
| 17656 |
|
| 17657 |
<pre caption="Starting fdisk"> |
| 17658 |
# <i>fdisk /dev/hda</i> |
| 17659 |
</pre> |
| 17660 |
|
| 17661 |
<p> |
| 17662 |
Once in <c>fdisk</c>, you'll be greeted with a prompt that looks like this: |
| 17663 |
</p> |
| 17664 |
|
| 17665 |
<pre caption="fdisk prompt"> |
| 17666 |
Command (m for help): |
| 17667 |
</pre> |
| 17668 |
|
| 17669 |
<p> |
| 17670 |
Type <c>p</c> to display your disk's current partition configuration: |
| 17671 |
</p> |
| 17672 |
|
| 17673 |
<pre caption="An example partition configuration"> |
| 17674 |
Command (m for help): <i>p</i> |
| 17675 |
|
| 17676 |
Disk /dev/hda: 240 heads, 63 sectors, 2184 cylinders |
| 17677 |
Units = cylinders of 15120 * 512 bytes |
| 17678 |
|
| 17679 |
Device Boot Start End Blocks Id System |
| 17680 |
/dev/hda1 1 14 105808+ 83 Linux |
| 17681 |
/dev/hda2 15 49 264600 82 Linux swap |
| 17682 |
/dev/hda3 50 70 158760 83 Linux |
| 17683 |
/dev/hda4 71 2184 15981840 5 Extended |
| 17684 |
/dev/hda5 71 209 1050808+ 83 Linux |
| 17685 |
/dev/hda6 210 348 1050808+ 83 Linux |
| 17686 |
/dev/hda7 349 626 2101648+ 83 Linux |
| 17687 |
/dev/hda8 627 904 2101648+ 83 Linux |
| 17688 |
/dev/hda9 905 2184 9676768+ 83 Linux |
| 17689 |
|
| 17690 |
Command (m for help): |
| 17691 |
</pre> |
| 17692 |
|
| 17693 |
<p> |
| 17694 |
This particular disk is configured to house seven Linux filesystems (each with a |
| 17695 |
corresponding partition listed as "Linux") as well as a swap partition (listed |
| 17696 |
as "Linux swap"). |
| 17697 |
</p> |
| 17698 |
|
| 17699 |
</body> |
| 17700 |
</subsection> |
| 17701 |
<subsection> |
| 17702 |
<title>Removing all Partitions</title> |
| 17703 |
<body> |
| 17704 |
|
| 17705 |
<p> |
| 17706 |
We will first remove all existing partitions from the disk. Type <c>d</c> to |
| 17707 |
delete a partition. For instance, to delete an existing <path>/dev/hda1</path>: |
| 17708 |
</p> |
| 17709 |
|
| 17710 |
<pre caption="Deleting a partition"> |
| 17711 |
Command (m for help): <i>d</i> |
| 17712 |
Partition number (1-4): <i>1</i> |
| 17713 |
</pre> |
| 17714 |
|
| 17715 |
<p> |
| 17716 |
The partition has been scheduled for deletion. It will no longer show up if you |
| 17717 |
type <c>p</c>, but it will not be erased until your changes have been saved. If |
| 17718 |
you made a mistake and want to abort without saving your changes, type <c>q</c> |
| 17719 |
immediately and hit enter and your partition will not be deleted. |
| 17720 |
</p> |
| 17721 |
|
| 17722 |
<p> |
| 17723 |
Now, assuming that you do indeed want to wipe out all the partitions on your |
| 17724 |
system, repeatedly type <c>p</c> to print out a partition listing and then type |
| 17725 |
<c>d</c> and the number of the partition to delete it. Eventually, you'll end |
| 17726 |
up with a partition table with nothing in it: |
| 17727 |
</p> |
| 17728 |
|
| 17729 |
<pre caption="An empty partition table"> |
| 17730 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
| 17731 |
240 heads, 63 sectors/track, 3876 cylinders |
| 17732 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
| 17733 |
|
| 17734 |
Device Boot Start End Blocks Id System |
| 17735 |
|
| 17736 |
Command (m for help): |
| 17737 |
</pre> |
| 17738 |
|
| 17739 |
<p> |
| 17740 |
Now that the in-memory partition table is empty, we're ready to create the |
| 17741 |
partitions. We will use a default partitioning scheme as discussed previously. |
| 17742 |
Of course, don't follow these instructions to the letter if you don't want the |
| 17743 |
same partitioning scheme! |
| 17744 |
</p> |
| 17745 |
|
| 17746 |
</body> |
| 17747 |
</subsection> |
| 17748 |
<subsection> |
| 17749 |
<title>Creating the Boot Partition</title> |
| 17750 |
<body> |
| 17751 |
|
| 17752 |
<p> |
| 17753 |
We first create a small boot partition. Type <c>n</c> to create a new partition, |
| 17754 |
then <c>p</c> to select a primary partition, followed by <c>1</c> to select the |
| 17755 |
first primary partition. When prompted for the first cylinder, hit enter. When |
| 17756 |
prompted for the last cylinder, type <c>+32M</c> to create a partition 32 Mbyte |
| 17757 |
in size: |
| 17758 |
</p> |
| 17759 |
|
| 17760 |
<pre caption="Creating the boot partition"> |
| 17761 |
Command (m for help): <i>n</i> |
| 17762 |
Command action |
| 17763 |
e extended |
| 17764 |
p primary partition (1-4) |
| 17765 |
<i>p</i> |
| 17766 |
Partition number (1-4): <i>1</i> |
| 17767 |
First cylinder (1-3876, default 1): <comment>(Hit Enter)</comment> |
| 17768 |
Using default value 1 |
| 17769 |
Last cylinder or +size or +sizeM or +sizeK (1-3876, default 3876): <i>+32M</i> |
| 17770 |
</pre> |
| 17771 |
|
| 17772 |
<p> |
| 17773 |
Now, when you type <c>p</c>, you should see the following partition printout: |
| 17774 |
</p> |
| 17775 |
|
| 17776 |
<pre caption="Created boot partition"> |
| 17777 |
Command (m for help): <i>p</i> |
| 17778 |
|
| 17779 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
| 17780 |
240 heads, 63 sectors/track, 3876 cylinders |
| 17781 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
| 17782 |
|
| 17783 |
Device Boot Start End Blocks Id System |
| 17784 |
/dev/hda1 1 14 105808+ 83 Linux |
| 17785 |
</pre> |
| 17786 |
|
| 17787 |
<p> |
| 17788 |
We need to make this partition bootable. Type <c>a</c> to toggle the bootable |
| 17789 |
flag on a partition and select <c>1</c>. If you press <c>p</c> again, you will |
| 17790 |
notice that an <path>*</path> is placed in the "Boot" column. |
| 17791 |
</p> |
| 17792 |
|
| 17793 |
</body> |
| 17794 |
</subsection> |
| 17795 |
<subsection> |
| 17796 |
<title>Creating the Swap Partition</title> |
| 17797 |
<body> |
| 17798 |
|
| 17799 |
<p> |
| 17800 |
Let's now create the swap partition. To do this, type <c>n</c> to create a new |
| 17801 |
partition, then <c>p</c> to tell fdisk that you want a primary partition. Then |
| 17802 |
type <c>2</c> to create the second primary partition, <path>/dev/hda2</path> in |
| 17803 |
our case. When prompted for the first cylinder, hit enter. When prompted for |
| 17804 |
the last cylinder, type <c>+512M</c> to create a partition 512MB in size. After |
| 17805 |
you've done this, type <c>t</c> to set the partition type, <c>2</c> to select |
| 17806 |
the partition you just created and then type in <c>82</c> to set the partition |
| 17807 |
type to "Linux Swap". After completing these steps, typing <c>p</c> should |
| 17808 |
display a partition table that looks similar to this: |
| 17809 |
</p> |
| 17810 |
|
| 17811 |
<pre caption="Partition listing after creating a swap partition"> |
| 17812 |
Command (m for help): <i>p</i> |
| 17813 |
|
| 17814 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
| 17815 |
240 heads, 63 sectors/track, 3876 cylinders |
| 17816 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
| 17817 |
|
| 17818 |
Device Boot Start End Blocks Id System |
| 17819 |
/dev/hda1 * 1 14 105808+ 83 Linux |
| 17820 |
/dev/hda2 15 81 506520 82 Linux swap |
| 17821 |
</pre> |
| 17822 |
|
| 17823 |
</body> |
| 17824 |
</subsection> |
| 17825 |
<subsection> |
| 17826 |
<title>Creating the Root Partition</title> |
| 17827 |
<body> |
| 17828 |
|
| 17829 |
<p> |
| 17830 |
Finally, let's create the root partition. To do this, type <c>n</c> to create a |
| 17831 |
new partition, then <c>p</c> to tell fdisk that you want a primary partition. |
| 17832 |
Then type <c>3</c> to create the third primary partition, <path>/dev/hda3</path> |
| 17833 |
in our case. When prompted for the first cylinder, hit enter. When prompted for |
| 17834 |
the last cylinder, hit enter to create a partition that takes up the rest of the |
| 17835 |
remaining space on your disk. After completing these steps, typing <c>p</c> |
| 17836 |
should display a partition table that looks similar to this: |
| 17837 |
</p> |
| 17838 |
|
| 17839 |
<pre caption="Partition listing after creating the root partition"> |
| 17840 |
Command (m for help): <i>p</i> |
| 17841 |
|
| 17842 |
Disk /dev/hda: 30.0 GB, 30005821440 bytes |
| 17843 |
240 heads, 63 sectors/track, 3876 cylinders |
| 17844 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
| 17845 |
|
| 17846 |
Device Boot Start End Blocks Id System |
| 17847 |
/dev/hda1 * 1 14 105808+ 83 Linux |
| 17848 |
/dev/hda2 15 81 506520 82 Linux swap |
| 17849 |
/dev/hda3 82 3876 28690200 83 Linux |
| 17850 |
</pre> |
| 17851 |
|
| 17852 |
|
| 17853 |
</body> |
| 17854 |
</subsection> |
| 17855 |
<subsection> |
| 17856 |
<title>Saving the Partition Layout</title> |
| 17857 |
<body> |
| 17858 |
|
| 17859 |
<p> |
| 17860 |
To save the partition layout and exit <c>fdisk</c>, type <c>w</c>. |
| 17861 |
</p> |
| 17862 |
|
| 17863 |
<pre caption="Save and exit fdisk"> |
| 17864 |
Command (m for help): <i>w</i> |
| 17865 |
</pre> |
| 17866 |
|
| 17867 |
<p> |
| 17868 |
Now that your partitions are created, you can now continue with <uri |
| 17869 |
link="#filesystems">Creating Filesystems</uri>. |
| 17870 |
</p> |
| 17871 |
|
| 17872 |
</body> |
| 17873 |
</subsection> |
| 17874 |
</section> |
| 17875 |
<section id="filesystems"> |
| 17876 |
<title>Creating Filesystems</title> |
| 17877 |
<subsection> |
| 17878 |
<title>Introduction</title> |
| 17879 |
<body> |
| 17880 |
|
| 17881 |
<p> |
| 17882 |
Now that your partitions are created, it is time to place a filesystem on them. |
| 17883 |
If you don't care about what filesystem to choose and are happy with what we use |
| 17884 |
as default in this handbook, continue with <uri |
| 17885 |
link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. |
| 17886 |
Otherwise read on to learn about the available filesystems... |
| 17887 |
</p> |
| 17888 |
|
| 17889 |
</body> |
| 17890 |
</subsection> |
| 17891 |
<subsection> |
| 17892 |
<title>Filesystems?</title> |
| 17893 |
<body> |
| 17894 |
|
| 17895 |
<p> |
| 17896 |
The Linux kernel supports various filesystems. We'll explain ext2, ext3, |
| 17897 |
ReiserFS, XFS and JFS as these are the most commonly used filesystems on Linux |
| 17898 |
systems. |
| 17899 |
</p> |
| 17900 |
|
| 17901 |
<p> |
| 17902 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
| 17903 |
journaling, which means that routine ext2 filesystem checks at startup time can |
| 17904 |
be quite time-consuming. There is now quite a selection of newer-generation |
| 17905 |
journaled filesystems that can be checked for consistency very quickly and are |
| 17906 |
thus generally preferred over their non-journaled counterparts. Journaled |
| 17907 |
filesystems prevent long delays when you boot your system and your filesystem |
| 17908 |
happens to be in an inconsistent state. |
| 17909 |
</p> |
| 17910 |
|
| 17911 |
<p> |
| 17912 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
| 17913 |
journaling for fast recovery in addition to other enhanced journaling modes like |
| 17914 |
full data and ordered data journaling. ext3 is a very good and reliable |
| 17915 |
filesystem. It has an additional hashed b-tree indexing option that enables |
| 17916 |
high performance in almost all situations. You can enable this indexing by |
| 17917 |
adding <c>-O dir_index</c> to the <c>mke2fs</c> command. In short, ext3 is an |
| 17918 |
excellent filesystem. |
| 17919 |
</p> |
| 17920 |
|
| 17921 |
<p> |
| 17922 |
<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall |
| 17923 |
performance and greatly outperforms both ext2 and ext3 when dealing with small |
| 17924 |
files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
| 17925 |
extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is |
| 17926 |
solid and usable as both general-purpose filesystem and for extreme cases such |
| 17927 |
as the creation of large filesystems, the use of many small files, very large |
| 17928 |
files and directories containing tens of thousands of files. |
| 17929 |
</p> |
| 17930 |
|
| 17931 |
<p> |
| 17932 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
| 17933 |
feature-set and is optimized for scalability. We only recommend using this |
| 17934 |
filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
| 17935 |
an uninterruptible power supply. Because XFS aggressively caches in-transit data |
| 17936 |
in RAM, improperly designed programs (those that don't take proper precautions |
| 17937 |
when writing files to disk and there are quite a few of them) can lose a good |
| 17938 |
deal of data if the system goes down unexpectedly. |
| 17939 |
</p> |
| 17940 |
|
| 17941 |
<p> |
| 17942 |
<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
| 17943 |
become production-ready and there hasn't been a sufficient track record to |
| 17944 |
comment positively nor negatively on its general stability at this point. |
| 17945 |
</p> |
| 17946 |
|
| 17947 |
</body> |
| 17948 |
</subsection> |
| 17949 |
<subsection id="filesystems-apply"> |
| 17950 |
<title>Applying a Filesystem to a Partition</title> |
| 17951 |
<body> |
| 17952 |
|
| 17953 |
<p> |
| 17954 |
To create a filesystem on a partition or volume, there are tools available for |
| 17955 |
each possible filesystem: |
| 17956 |
</p> |
| 17957 |
|
| 17958 |
<table> |
| 17959 |
<tr> |
| 17960 |
<th>Filesystem</th> |
| 17961 |
<th>Creation Command</th> |
| 17962 |
</tr> |
| 17963 |
<tr> |
| 17964 |
<ti>ext2</ti> |
| 17965 |
<ti><c>mke2fs</c></ti> |
| 17966 |
</tr> |
| 17967 |
<tr> |
| 17968 |
<ti>ext3</ti> |
| 17969 |
<ti><c>mke2fs -j</c></ti> |
| 17970 |
</tr> |
| 17971 |
<tr> |
| 17972 |
<ti>reiserfs</ti> |
| 17973 |
<ti><c>mkreiserfs</c></ti> |
| 17974 |
</tr> |
| 17975 |
<tr> |
| 17976 |
<ti>xfs</ti> |
| 17977 |
<ti><c>mkfs.xfs</c></ti> |
| 17978 |
</tr> |
| 17979 |
<tr> |
| 17980 |
<ti>jfs</ti> |
| 17981 |
<ti><c>mkfs.jfs</c></ti> |
| 17982 |
</tr> |
| 17983 |
</table> |
| 17984 |
|
| 17985 |
<p> |
| 17986 |
For instance, to have the boot partition (<path>/dev/hda1</path> in our |
| 17987 |
example) in ext2 and the root partition (<path>/dev/hda3</path> in our example) |
| 17988 |
in ext3 (as in our example), you would use: |
| 17989 |
</p> |
| 17990 |
|
| 17991 |
<pre caption="Applying a filesystem on a partition"> |
| 17992 |
# <i>mke2fs /dev/hda1</i> |
| 17993 |
# <i>mke2fs -j /dev/hda3</i> |
| 17994 |
</pre> |
| 17995 |
|
| 17996 |
<p> |
| 17997 |
Now create the filesystems on your newly created partitions (or logical |
| 17998 |
volumes). |
| 17999 |
</p> |
| 18000 |
|
| 18001 |
</body> |
| 18002 |
</subsection> |
| 18003 |
<subsection> |
| 18004 |
<title>Activating the Swap Partition</title> |
| 18005 |
<body> |
| 18006 |
|
| 18007 |
<p> |
| 18008 |
<c>mkswap</c> is the command that is used to initialize swap partitions: |
| 18009 |
</p> |
| 18010 |
|
| 18011 |
<pre caption="Creating a Swap signature"> |
| 18012 |
# <i>mkswap /dev/hda2</i> |
| 18013 |
</pre> |
| 18014 |
|
| 18015 |
<p> |
| 18016 |
To activate the swap partition, use <c>swapon</c>: |
| 18017 |
</p> |
| 18018 |
|
| 18019 |
<pre caption="Activating the swap partition"> |
| 18020 |
# <i>swapon /dev/hda2</i> |
| 18021 |
</pre> |
| 18022 |
|
| 18023 |
<p> |
| 18024 |
Create and activate the swap now. |
| 18025 |
</p> |
| 18026 |
|
| 18027 |
</body> |
| 18028 |
</subsection> |
| 18029 |
</section> |
| 18030 |
<section> |
| 18031 |
<title>Mounting</title> |
| 18032 |
<body> |
| 18033 |
|
| 18034 |
<p> |
| 18035 |
Now that your partitions are initialized and are housing a filesystem, it is |
| 18036 |
time to mount those partitions. Use the <c>mount</c> command. Don't forget to |
| 18037 |
create the necessary mount directories for every partition you created. As an |
| 18038 |
example we mount the root and boot partition: |
| 18039 |
</p> |
| 18040 |
|
| 18041 |
<pre caption="Mounting partitions"> |
| 18042 |
# <i>mount /dev/hda3 /mnt/gentoo</i> |
| 18043 |
# <i>mkdir /mnt/gentoo/boot</i> |
| 18044 |
# <i>mount /dev/hda1 /mnt/gentoo/boot</i> |
| 18045 |
</pre> |
| 18046 |
|
| 18047 |
<note> |
| 18048 |
If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
| 18049 |
change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
| 18050 |
also holds for <path>/var/tmp</path>. |
| 18051 |
</note> |
| 18052 |
|
| 18053 |
<p> |
| 18054 |
We will also have to mount the proc filesystem (a virtual interface with the |
| 18055 |
kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. |
| 18056 |
</p> |
| 18057 |
|
| 18058 |
<p> |
| 18059 |
Continue with <uri link="?part=1&chap=5">Installing the Gentoo |
| 18060 |
Installation Files</uri>. |
| 18061 |
</p> |
| 18062 |
|
| 18063 |
</body> |
| 18064 |
</section> |
| 18065 |
</sections> |
| 18066 |
|
| 18067 |
|
| 18068 |
|
| 18069 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-kernel.xml |
| 18070 |
|
| 18071 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-kernel.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 18072 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-kernel.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 18073 |
|
| 18074 |
Index: hb-install-x86-kernel.xml |
| 18075 |
=================================================================== |
| 18076 |
<?xml version='1.0' encoding='UTF-8'?> |
| 18077 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 18078 |
|
| 18079 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 18080 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 18081 |
|
| 18082 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-kernel.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 18083 |
|
| 18084 |
<sections> |
| 18085 |
|
| 18086 |
<version>5.5</version> |
| 18087 |
<date>2006-01-06</date> |
| 18088 |
|
| 18089 |
<section> |
| 18090 |
<title>Timezone</title> |
| 18091 |
<body> |
| 18092 |
|
| 18093 |
<p> |
| 18094 |
You first need to select your timezone so that your system knows where it is |
| 18095 |
located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy |
| 18096 |
it to <path>/etc/localtime</path>. Please avoid the |
| 18097 |
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not |
| 18098 |
indicate the expected zones. For instance, <path>GMT-8</path> is in fact GMT+8. |
| 18099 |
</p> |
| 18100 |
|
| 18101 |
<pre caption="Setting the timezone information"> |
| 18102 |
# <i>ls /usr/share/zoneinfo</i> |
| 18103 |
<comment>(Suppose you want to use GMT)</comment> |
| 18104 |
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i> |
| 18105 |
</pre> |
| 18106 |
|
| 18107 |
</body> |
| 18108 |
</section> |
| 18109 |
<section> |
| 18110 |
<title>Installing the Sources</title> |
| 18111 |
<subsection> |
| 18112 |
<title>Choosing a Kernel</title> |
| 18113 |
<body> |
| 18114 |
|
| 18115 |
<p> |
| 18116 |
The core around which all distributions are built is the Linux kernel. It is the |
| 18117 |
layer between the user programs and your system hardware. Gentoo provides its |
| 18118 |
users several possible kernel sources. A full listing with description is |
| 18119 |
available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel |
| 18120 |
Guide</uri>. |
| 18121 |
</p> |
| 18122 |
|
| 18123 |
<p> |
| 18124 |
For x86-based systems, our main supported kernel is named |
| 18125 |
<c>gentoo-sources</c>. This kernel is based on the official Linux sources, but |
| 18126 |
has security, stability, compatibility and bug fixes applied on top. |
| 18127 |
Alternatively, the plain and unpatched Linux sources are supplied through the |
| 18128 |
<c>vanilla-sources</c> package. |
| 18129 |
</p> |
| 18130 |
|
| 18131 |
<p> |
| 18132 |
Both kernel sources are based on the official 2.6 kernel sources. If you |
| 18133 |
want to install a 2.4-based kernel, you will need to install Gentoo with a |
| 18134 |
working Internet connection as we do not supply these sources on our |
| 18135 |
Installation CD. |
| 18136 |
</p> |
| 18137 |
|
| 18138 |
<p> |
| 18139 |
Choose your kernel source and install it using <c>emerge</c>. The |
| 18140 |
<c>USE="-doc"</c> is necessary to avoid installing xorg-x11 or other |
| 18141 |
dependencies at this point. <c>USE="symlink"</c> is not necessary for a new |
| 18142 |
install, but ensures proper creation of the <path>/usr/src/linux</path> |
| 18143 |
symlink. |
| 18144 |
</p> |
| 18145 |
|
| 18146 |
<pre caption="Installing a kernel source"> |
| 18147 |
# <i>USE="-doc symlink" emerge gentoo-sources</i> |
| 18148 |
</pre> |
| 18149 |
|
| 18150 |
<p> |
| 18151 |
When you take a look in <path>/usr/src</path> you should see a symlink called |
| 18152 |
<path>linux</path> pointing to your kernel source. In this case, the installed |
| 18153 |
kernel source points to <c>gentoo-sources-2.6.12-r10</c>. Your version may be |
| 18154 |
different, so keep this in mind. |
| 18155 |
</p> |
| 18156 |
|
| 18157 |
<pre caption="Viewing the kernel source symlink"> |
| 18158 |
# <i>ls -l /usr/src/linux</i> |
| 18159 |
lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -> linux-2.6.12-gentoo-r10 |
| 18160 |
</pre> |
| 18161 |
|
| 18162 |
<p> |
| 18163 |
Now it is time to configure and compile your kernel source. You |
| 18164 |
can use <c>genkernel</c> for this, which will build a generic kernel as used |
| 18165 |
by the Installation CD. We explain the "manual" configuration first though, as |
| 18166 |
it is the best way to optimize your environment. |
| 18167 |
</p> |
| 18168 |
|
| 18169 |
<p> |
| 18170 |
If you want to manually configure your kernel, continue now with <uri |
| 18171 |
link="#manual">Default: Manual Configuration</uri>. If you want to use |
| 18172 |
<c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using |
| 18173 |
genkernel</uri> instead. |
| 18174 |
</p> |
| 18175 |
|
| 18176 |
</body> |
| 18177 |
</subsection> |
| 18178 |
</section> |
| 18179 |
<section id="manual"> |
| 18180 |
<title>Default: Manual Configuration</title> |
| 18181 |
<subsection> |
| 18182 |
<title>Introduction</title> |
| 18183 |
<body> |
| 18184 |
|
| 18185 |
<p> |
| 18186 |
Manually configuring a kernel is often seen as the most difficult procedure a |
| 18187 |
Linux user ever has to perform. Nothing is less true -- after configuring a |
| 18188 |
couple of kernels you don't even remember that it was difficult ;) |
| 18189 |
</p> |
| 18190 |
|
| 18191 |
<p> |
| 18192 |
However, one thing <e>is</e> true: you must know your system when you start |
| 18193 |
configuring a kernel manually. Most information can be gathered by emerging |
| 18194 |
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now |
| 18195 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
| 18196 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
| 18197 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
| 18198 |
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. |
| 18199 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
| 18200 |
uses (it might provide you with a nice hint on what to enable). |
| 18201 |
</p> |
| 18202 |
|
| 18203 |
<p> |
| 18204 |
Now go to your kernel source directory and execute <c>make menuconfig</c>. This |
| 18205 |
will fire up an ncurses-based configuration menu. |
| 18206 |
</p> |
| 18207 |
|
| 18208 |
<pre caption="Invoking menuconfig"> |
| 18209 |
# <i>cd /usr/src/linux</i> |
| 18210 |
# <i>make menuconfig</i> |
| 18211 |
</pre> |
| 18212 |
|
| 18213 |
<p> |
| 18214 |
You will be greeted with several configuration sections. We'll first list some |
| 18215 |
options you must activate (otherwise Gentoo will not function, or not function |
| 18216 |
properly without additional tweaks). |
| 18217 |
</p> |
| 18218 |
|
| 18219 |
</body> |
| 18220 |
</subsection> |
| 18221 |
<subsection> |
| 18222 |
<title>Activating Required Options</title> |
| 18223 |
<body> |
| 18224 |
|
| 18225 |
<p> |
| 18226 |
Make sure that every driver that is vital to the booting of your system (such as |
| 18227 |
SCSI controller, ...) is compiled <e>in</e> the kernel and not as a module, |
| 18228 |
otherwise your system will not be able to boot completely. |
| 18229 |
</p> |
| 18230 |
|
| 18231 |
<p> |
| 18232 |
Now select the correct processor family: |
| 18233 |
</p> |
| 18234 |
|
| 18235 |
<pre caption="General Support and processor family"> |
| 18236 |
General setup ---> |
| 18237 |
[*] Support for hot-pluggable devices |
| 18238 |
Processor type and features ---> |
| 18239 |
Subarchitecture Type (PC-compatible) ---> |
| 18240 |
<comment>(Change according to your system)</comment> |
| 18241 |
(<i>Athlon/Duron/K7</i>) Processor family |
| 18242 |
</pre> |
| 18243 |
|
| 18244 |
<p> |
| 18245 |
Now go to <c>File Systems</c> and select support for the filesystems you use. |
| 18246 |
<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be |
| 18247 |
able to mount your partitions. Also select <c>/proc file system</c> and |
| 18248 |
<c>Virtual memory</c>. |
| 18249 |
</p> |
| 18250 |
|
| 18251 |
<pre caption="Selecting necessary file systems"> |
| 18252 |
File systems ---> |
| 18253 |
Pseudo Filesystems ---> |
| 18254 |
<*> /proc file system support |
| 18255 |
<*> Virtual memory file system support (former shm fs) |
| 18256 |
|
| 18257 |
|
| 18258 |
<comment>(Select one or more of the following options as needed by your system)</comment> |
| 18259 |
<*> Reiserfs support |
| 18260 |
<*> Ext3 journalling file system support |
| 18261 |
<*> JFS filesystem support |
| 18262 |
<*> Second extended fs support |
| 18263 |
<*> XFS filesystem support |
| 18264 |
</pre> |
| 18265 |
|
| 18266 |
<p> |
| 18267 |
Do not forget to enable DMA for your drives: |
| 18268 |
</p> |
| 18269 |
|
| 18270 |
<pre caption="Activating DMA"> |
| 18271 |
Device Drivers ---> |
| 18272 |
ATA/ATAPI/MFM/RLL support ---> |
| 18273 |
[*] Generic PCI bus-master DMA support |
| 18274 |
[*] Use PCI DMA by default when available |
| 18275 |
</pre> |
| 18276 |
|
| 18277 |
<p> |
| 18278 |
If you are using PPPoE to connect to the Internet or you are using a dial-up |
| 18279 |
modem, you will need the following options in the kernel: |
| 18280 |
</p> |
| 18281 |
|
| 18282 |
<pre caption="Selecting PPPoE necessary drivers"> |
| 18283 |
Device Drivers ---> |
| 18284 |
Networking support ---> |
| 18285 |
<*> PPP (point-to-point protocol) support |
| 18286 |
<*> PPP support for async serial ports |
| 18287 |
<*> PPP support for sync tty ports |
| 18288 |
</pre> |
| 18289 |
|
| 18290 |
<p> |
| 18291 |
The two compression options won't harm but are not definitely needed, neither |
| 18292 |
does the <c>PPP over Ethernet</c> option, that might only be used by |
| 18293 |
<c>rp-pppoe</c> when configured to do kernel mode PPPoE. |
| 18294 |
</p> |
| 18295 |
|
| 18296 |
<p> |
| 18297 |
If you require it, don't forget to include support in the kernel for your |
| 18298 |
ethernet card. |
| 18299 |
</p> |
| 18300 |
|
| 18301 |
<p> |
| 18302 |
If you have an Intel CPU that supports HyperThreading (tm), or you have a |
| 18303 |
multi-CPU system, you should activate "Symmetric multi-processing support": |
| 18304 |
</p> |
| 18305 |
|
| 18306 |
<pre caption="Activating SMP support"> |
| 18307 |
Processor type and features ---> |
| 18308 |
<*> Symmetric multi-processing support |
| 18309 |
</pre> |
| 18310 |
|
| 18311 |
<p> |
| 18312 |
If you use USB Input Devices (like Keyboard or Mouse) don't forget to enable |
| 18313 |
those as well: |
| 18314 |
</p> |
| 18315 |
|
| 18316 |
<pre caption="Activating USB Support for Input Devices"> |
| 18317 |
Device Drivers ---> |
| 18318 |
USB Support ---> |
| 18319 |
<*> USB Human Interface Device (full HID) support |
| 18320 |
[*] HID input layer support |
| 18321 |
</pre> |
| 18322 |
|
| 18323 |
<p> |
| 18324 |
If you are a laptop user and require PCMCIA support, remember to compile it |
| 18325 |
into the kernel. As well as the option below, be sure to enable support for |
| 18326 |
the PCMCIA card bridge present in your system (found in the same menu of the |
| 18327 |
configuration). |
| 18328 |
</p> |
| 18329 |
|
| 18330 |
<pre caption="Activating PCMCIA support"> |
| 18331 |
Bus options (PCI, PCMCIA, EISA, MCA, ISA) ---> |
| 18332 |
PCCARD (PCMCIA/CardBus) support ---> |
| 18333 |
<*> PCCard (PCMCIA/CardBus) support |
| 18334 |
<comment>(select 16 bit if you need support for older PCMCIA cards. Most people want this.)</comment> |
| 18335 |
<*> 16-bit PCMCIA support |
| 18336 |
[*] 32-bit CardBus support |
| 18337 |
<comment>(select the relevant bridges below)</comment> |
| 18338 |
--- PC-card bridges |
| 18339 |
<*> CardBus yenta-compatible bridge support (NEW) |
| 18340 |
<*> Cirrus PD6729 compatible bridge support (NEW) |
| 18341 |
<*> i82092 compatible bridge support (NEW) |
| 18342 |
<*> i82365 compatible bridge support (NEW) |
| 18343 |
<*> Databook TCIC host bridge support (NEW) |
| 18344 |
</pre> |
| 18345 |
|
| 18346 |
</body> |
| 18347 |
</subsection> |
| 18348 |
<subsection id="compiling"> |
| 18349 |
<title>Compiling and Installing</title> |
| 18350 |
<body> |
| 18351 |
|
| 18352 |
<p> |
| 18353 |
Now that your kernel is configured, it is time to compile and install it. Exit |
| 18354 |
the configuration and start the compilation process: |
| 18355 |
</p> |
| 18356 |
|
| 18357 |
<pre caption="Compiling the kernel"> |
| 18358 |
# <i>make && make modules_install</i> |
| 18359 |
</pre> |
| 18360 |
|
| 18361 |
<p> |
| 18362 |
When the kernel has finished compiling, copy the kernel image to |
| 18363 |
<path>/boot</path>. Use whatever name you feel is appropriate for your kernel |
| 18364 |
choice and remember it as you will need it later on when you configure your |
| 18365 |
bootloader. Remember to replace <path><kernel-version></path> with the |
| 18366 |
name and version of your kernel. |
| 18367 |
</p> |
| 18368 |
|
| 18369 |
<pre caption="Installing the kernel"> |
| 18370 |
# <i>cp arch/i386/boot/bzImage /boot/<kernel-version></i> |
| 18371 |
</pre> |
| 18372 |
|
| 18373 |
<p> |
| 18374 |
Now continue with <uri link="#kernel_modules">Configuring Kernel |
| 18375 |
Modules</uri>. |
| 18376 |
</p> |
| 18377 |
|
| 18378 |
</body> |
| 18379 |
</subsection> |
| 18380 |
</section> |
| 18381 |
<section id="genkernel"> |
| 18382 |
<title>Alternative: Using genkernel</title> |
| 18383 |
<body> |
| 18384 |
|
| 18385 |
<p> |
| 18386 |
If you are reading this section, you have chosen to use our <c>genkernel</c> |
| 18387 |
script to configure your kernel for you. |
| 18388 |
</p> |
| 18389 |
|
| 18390 |
<p> |
| 18391 |
Now that your kernel source tree is installed, it's now time to compile your |
| 18392 |
kernel by using our <c>genkernel</c> script to automatically build a kernel for |
| 18393 |
you. <c>genkernel</c> works by configuring a kernel nearly identically to the |
| 18394 |
way our Installation CD kernel is configured. This means that when you use |
| 18395 |
<c>genkernel</c> to build your kernel, your system will generally detect all |
| 18396 |
your hardware at boot-time, just like our Installation CD does. Because genkernel |
| 18397 |
doesn't require any manual kernel configuration, it is an ideal solution for |
| 18398 |
those users who may not be comfortable compiling their own kernels. |
| 18399 |
</p> |
| 18400 |
|
| 18401 |
<p> |
| 18402 |
Now, let's see how to use genkernel. First, emerge the genkernel ebuild: |
| 18403 |
</p> |
| 18404 |
|
| 18405 |
<pre caption="Emerging genkernel"> |
| 18406 |
# <i>emerge genkernel</i> |
| 18407 |
</pre> |
| 18408 |
|
| 18409 |
<p> |
| 18410 |
Now, compile your kernel sources by running <c>genkernel all</c>. |
| 18411 |
Be aware though, as <c>genkernel</c> compiles a kernel that supports almost all |
| 18412 |
hardware, this compilation will take quite a while to finish! |
| 18413 |
</p> |
| 18414 |
|
| 18415 |
<p> |
| 18416 |
Note that, if your boot partition doesn't use ext2 or ext3 as filesystem you |
| 18417 |
might need to manually configure your kernel using <c>genkernel --menuconfig |
| 18418 |
all</c> and add support for your filesystem <e>in</e> the kernel (i.e. |
| 18419 |
<e>not</e> as a module). Users of EVMS2 or LVM2 will probably want to add |
| 18420 |
<c>--evms2</c> or <c>--lvm2</c> as argument as well. |
| 18421 |
</p> |
| 18422 |
|
| 18423 |
<pre caption="Running genkernel"> |
| 18424 |
# <i>genkernel all</i> |
| 18425 |
</pre> |
| 18426 |
|
| 18427 |
<p> |
| 18428 |
Once <c>genkernel</c> completes, a kernel, full set of modules and |
| 18429 |
<e>initial root disk</e> (initrd) will be created. We will use the kernel |
| 18430 |
and initrd when configuring a boot loader later in this document. Write |
| 18431 |
down the names of the kernel and initrd as you will need it when writing |
| 18432 |
the bootloader configuration file. The initrd will be started immediately after |
| 18433 |
booting to perform hardware autodetection (just like on the Installation CD) |
| 18434 |
before your "real" system starts up. |
| 18435 |
</p> |
| 18436 |
|
| 18437 |
<pre caption="Checking the created kernel image name and initrd"> |
| 18438 |
# <i>ls /boot/kernel* /boot/initramfs*</i> |
| 18439 |
</pre> |
| 18440 |
|
| 18441 |
<p> |
| 18442 |
If you want your system to be more like the Installation CD you should |
| 18443 |
emerge <c>coldplug</c>. While the initrd autodetects hardware that is |
| 18444 |
needed to boot your system, <c>coldplug</c> autodetects everything |
| 18445 |
else. |
| 18446 |
</p> |
| 18447 |
|
| 18448 |
<pre caption="Emerging and enabling coldplug"> |
| 18449 |
# <i>emerge coldplug</i> |
| 18450 |
# <i>rc-update add coldplug boot</i> |
| 18451 |
</pre> |
| 18452 |
|
| 18453 |
</body> |
| 18454 |
</section> |
| 18455 |
<section id="kernel_modules"> |
| 18456 |
<title>Configuring Kernel Modules</title> |
| 18457 |
<subsection> |
| 18458 |
<title>Configuring the Modules</title> |
| 18459 |
<body> |
| 18460 |
|
| 18461 |
<p> |
| 18462 |
You should list the modules you want automatically loaded in |
| 18463 |
<path>/etc/modules.autoload.d/kernel-2.6</path> (or <path>kernel-2.4</path>). |
| 18464 |
You can add extra options to the modules too if you want. |
| 18465 |
</p> |
| 18466 |
|
| 18467 |
<p> |
| 18468 |
To view all available modules, run the following <c>find</c> command. Don't |
| 18469 |
forget to substitute "<kernel version>" with the version of the kernel you |
| 18470 |
just compiled: |
| 18471 |
</p> |
| 18472 |
|
| 18473 |
<pre caption="Viewing all available modules"> |
| 18474 |
# <i>find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'</i> |
| 18475 |
</pre> |
| 18476 |
|
| 18477 |
<p> |
| 18478 |
For instance, to automatically load the <c>3c59x.o</c> module, edit the |
| 18479 |
<path>kernel-2.6</path> (or <path>kernel-2.4</path>) file and enter the module |
| 18480 |
name in it. |
| 18481 |
</p> |
| 18482 |
|
| 18483 |
<pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> |
| 18484 |
<comment>(Example for 2.6 kernels)</comment> |
| 18485 |
# <i>nano -w /etc/modules.autoload.d/kernel-2.6</i> |
| 18486 |
</pre> |
| 18487 |
|
| 18488 |
<pre caption="/etc/modules.autoload.d/kernel-2.6"> |
| 18489 |
3c59x |
| 18490 |
</pre> |
| 18491 |
|
| 18492 |
<p> |
| 18493 |
Now continue with <uri link="?part=1&chap=8">Configuring your System</uri>. |
| 18494 |
</p> |
| 18495 |
|
| 18496 |
</body> |
| 18497 |
</subsection> |
| 18498 |
</section> |
| 18499 |
</sections> |
| 18500 |
|
| 18501 |
|
| 18502 |
|
| 18503 |
1.1 xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml |
| 18504 |
|
| 18505 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 18506 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo |
| 18507 |
|
| 18508 |
Index: hb-install-x86-medium.xml |
| 18509 |
=================================================================== |
| 18510 |
<?xml version='1.0' encoding='UTF-8'?> |
| 18511 |
<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 18512 |
|
| 18513 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 18514 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 18515 |
|
| 18516 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-x86-medium.xml,v 1.1 2006/02/01 18:38:17 fox2mike Exp $ --> |
| 18517 |
|
| 18518 |
<sections> |
| 18519 |
|
| 18520 |
<version>5.5</version> |
| 18521 |
<date>2005-11-29</date> |
| 18522 |
|
| 18523 |
<section> |
| 18524 |
<title>Hardware Requirements</title> |
| 18525 |
<subsection> |
| 18526 |
<title>Introduction</title> |
| 18527 |
<body> |
| 18528 |
|
| 18529 |
<p> |
| 18530 |
Before we start, we first list what hardware requirements you need to |
| 18531 |
successfully install Gentoo on your box. |
| 18532 |
</p> |
| 18533 |
|
| 18534 |
</body> |
| 18535 |
</subsection> |
| 18536 |
<subsection> |
| 18537 |
<title>Hardware Requirements</title> |
| 18538 |
<body> |
| 18539 |
|
| 18540 |
<table> |
| 18541 |
<tr> |
| 18542 |
<th>CPU</th> |
| 18543 |
<ti>i486 or later</ti> |
| 18544 |
</tr> |
| 18545 |
<tr> |
| 18546 |
<th>Memory</th> |
| 18547 |
<ti>64 MB</ti> |
| 18548 |
</tr> |
| 18549 |
<tr> |
| 18550 |
<th>Diskspace</th> |
| 18551 |
<ti>1.5 GB (excluding swap space)</ti> |
| 18552 |
</tr> |
| 18553 |
<tr> |
| 18554 |
<th>Swap space</th> |
| 18555 |
<ti>At least 256 MB</ti> |
| 18556 |
</tr> |
| 18557 |
</table> |
| 18558 |
|
| 18559 |
|
| 18560 |
</body> |
| 18561 |
</subsection> |
| 18562 |
</section> |
| 18563 |
<!-- General description, propagated to other architectures as well --> |
| 18564 |
<!-- START --> |
| 18565 |
<section> |
| 18566 |
<title>The Gentoo Universal Installation CD</title> |
| 18567 |
<subsection> |
| 18568 |
<title>Introduction</title> |
| 18569 |
<body> |
| 18570 |
|
| 18571 |
<p> |
| 18572 |
Gentoo Linux can be installed using a <e>stage3</e> tarball file. |
| 18573 |
Such a tarball is an archive that contains a minimal environment from |
| 18574 |
which you can succesfully install Gentoo Linux onto your system. |
| 18575 |
</p> |
| 18576 |
|
| 18577 |
<p> |
| 18578 |
Installations using a stage1 or stage2 tarball file are not documented in the |
| 18579 |
Gentoo Handbook - please read the <uri link="/doc/en/faq.xml#stage12">Gentoo |
| 18580 |
FAQ</uri> on these matters. |
| 18581 |
</p> |
| 18582 |
|
| 18583 |
</body> |
| 18584 |
</subsection> |
| 18585 |
<subsection> |
| 18586 |
<title>Gentoo Universal Installation CD</title> |
| 18587 |
<body> |
| 18588 |
|
| 18589 |
<p> |
| 18590 |
An Installation CD is a bootable medium which contains a self-sustained Gentoo |
| 18591 |
environment. It allows you to boot Linux from the CD. During the boot process |
| 18592 |
your hardware is detected and the appropriate drivers are loaded. The Gentoo |
| 18593 |
Installation CDs are maintained by Gentoo developers. |
| 18594 |
</p> |
| 18595 |
|
| 18596 |
<p> |
| 18597 |
There currently are two Installation CDs available: |
| 18598 |
</p> |
| 18599 |
|
| 18600 |
<ul> |
| 18601 |
<li> |
| 18602 |
The Universal Installation CD contains everything you need to install |
| 18603 |
Gentoo. It provides stage3 files for common architectures, source code |
| 18604 |
for the extra applications you need to choose from and, of course, the |
| 18605 |
installation instructions for your architecture. |
| 18606 |
</li> |
| 18607 |
<li> |
| 18608 |
The Minimal Installation CD contains only a minimal environment that allows |
| 18609 |
you to boot up and configure your network so you can connect to the |
| 18610 |
Internet. It does not contain any additional files and cannot be used |
| 18611 |
during the current installation approach. |
| 18612 |
</li> |
| 18613 |
</ul> |
| 18614 |
|
| 18615 |
<p> |
| 18616 |
Gentoo also provides a Package CD. This is not an Installation CD but an |
| 18617 |
additional resource that you can exploit during the installation of your Gentoo |
| 18618 |
system. It contains prebuilt packages (also known as the GRP set) that allow |
| 18619 |
you to easily and quickly install additional applications (such as |
| 18620 |
OpenOffice.org, KDE, GNOME, ...) immediately after the Gentoo installation and |
| 18621 |
right before you update your Portage tree. |
| 18622 |
</p> |
| 18623 |
|
| 18624 |
<p> |
| 18625 |
The use of the Package CD is covered later in this document. |
| 18626 |
</p> |
| 18627 |
|
| 18628 |
</body> |
| 18629 |
</subsection> |
| 18630 |
</section> |
| 18631 |
<!-- STOP --> |
| 18632 |
<section> |
| 18633 |
<title>Download, Burn and Boot the Gentoo Universal Installation CD</title> |
| 18634 |
<subsection> |
| 18635 |
<title>Downloading and Burning the Installation CD</title> |
| 18636 |
<body> |
| 18637 |
|
| 18638 |
<p> |
| 18639 |
You can download the Universal Installation CDs (and, if you want to, the |
| 18640 |
Packages CD as well) from one of our <uri |
| 18641 |
link="/main/en/mirrors.xml">mirrors</uri>. The Installation CDs are located in |
| 18642 |
the <path>releases/x86/2006.0-r1/installcd</path> directory; |
| 18643 |
the Package CDs are located in the <path>releases/x86/2006.0/packagecd</path> |
| 18644 |
directory. |
| 18645 |
</p> |
| 18646 |
|
| 18647 |
<p> |
| 18648 |
i686, athlon-xp, pentium3 and pentium4 Package CDs are available via |
| 18649 |
<uri link="http://tracker.netdomination.org">BitTorrent</uri>. |
| 18650 |
</p> |
| 18651 |
|
| 18652 |
<p> |
| 18653 |
Inside those directories you'll find ISO-files. Those are full CD images which |
| 18654 |
you can write on a CD-R. |
| 18655 |
</p> |
| 18656 |
|
| 18657 |
<p> |
| 18658 |
After downloading the file, you can verify its integrity to see if it is |
| 18659 |
corrupted or not: |
| 18660 |
</p> |
| 18661 |
|
| 18662 |
<ul> |
| 18663 |
<li> |
| 18664 |
You can check its MD5 checksum and compare it with the MD5 checksum we |
| 18665 |
provide (for instance with the <c>md5sum</c> tool under Linux/Unix or |
| 18666 |
<uri link="http://www.etree.org/md5com.html">md5sum</uri> for Windows) |
| 18667 |
</li> |
| 18668 |
<li> |
| 18669 |
You can verify the cryptographic signature that we provide. You need to |
| 18670 |
obtain the public key we use (17072058) before you proceed though. |
| 18671 |
</li> |
| 18672 |
</ul> |
| 18673 |
|
| 18674 |
<p> |
| 18675 |
To fetch our public key using the GnuPG application, run the following command: |
| 18676 |
</p> |
| 18677 |
|
| 18678 |
<pre caption="Obtaining the public key"> |
| 18679 |
$ <i>gpg --keyserver subkeys.pgp.net --recv-keys 17072058</i> |
| 18680 |
</pre> |
| 18681 |
|
| 18682 |
<p> |
| 18683 |
Now verify the signature: |
| 18684 |
</p> |
| 18685 |
|
| 18686 |
<pre caption="Verify the cryptographic signature"> |
| 18687 |
$ <i>gpg --verify <signature file> <downloaded iso></i> |
| 18688 |
</pre> |
| 18689 |
|
| 18690 |
<p> |
| 18691 |
To burn the downloaded ISO(s), you have to select raw-burning. How you |
| 18692 |
do this is highly program-dependent. We will discuss <c>cdrecord</c> and |
| 18693 |
<c>K3B</c> here; more information can be found in our <uri |
| 18694 |
link="/doc/en/faq.xml#isoburning">Gentoo FAQ</uri>. |
| 18695 |
</p> |
| 18696 |
|
| 18697 |
<ul> |
| 18698 |
<li> |
| 18699 |
With cdrecord, you simply type <c>cdrecord dev=/dev/hdc <downloaded iso |
| 18700 |
file></c> (replace <path>/dev/hdc</path> with your CD-RW drive's device |
| 18701 |
path). |
| 18702 |
</li> |
| 18703 |
<li> |
| 18704 |
With K3B, select <c>Tools</c> > <c>CD</c> > <c>Burn Image</c>. Then |
| 18705 |
you can locate your ISO file within the 'Image to Burn' area. Finally click |
| 18706 |
<c>Start</c>. |
| 18707 |
</li> |
| 18708 |
</ul> |
| 18709 |
|
| 18710 |
</body> |
| 18711 |
</subsection> |
| 18712 |
<subsection> |
| 18713 |
<title>Booting the Universal Installation CD</title> |
| 18714 |
<body> |
| 18715 |
|
| 18716 |
<impo> |
| 18717 |
Read this whole subsection before continuing, as you will probably not have the |
| 18718 |
opportunity to read it before doing things later. |
| 18719 |
</impo> |
| 18720 |
|
| 18721 |
<p> |
| 18722 |
Once you have burned your installation CD, it is time to boot it. |
| 18723 |
Remove all CDs from your CD drives, reboot your system and enter the BIOS. |
| 18724 |
This is usually done by hitting DEL, F1 or ESC, depending on your BIOS. Inside |
| 18725 |
the BIOS, change the boot order so that the CD-ROM is tried before the hard |
| 18726 |
disk. This is often found under "CMOS Setup". If you don't do this, your system |
| 18727 |
will just reboot from the hard disk, ignoring the CD-ROM. |
| 18728 |
</p> |
| 18729 |
|
| 18730 |
<p> |
| 18731 |
Now place the installation CD in the CD-ROM drive and reboot. You |
| 18732 |
should see a boot prompt. At this screen, you can hit Enter to begin the |
| 18733 |
boot process with the default boot options, or boot the Installation CD with |
| 18734 |
custom boot options by specifying a kernel followed by boot options and then |
| 18735 |
hitting Enter. |
| 18736 |
</p> |
| 18737 |
|
| 18738 |
<p> |
| 18739 |
Specifying a kernel? Yes, we provide several kernels on our Installation CDs. |
| 18740 |
The default one is <c>gentoo</c>. Other kernels are for specific hardware needs |
| 18741 |
and the <c>-nofb</c> variants which disable framebuffer. |
| 18742 |
</p> |
| 18743 |
|
| 18744 |
<p> |
| 18745 |
Below you'll find a short overview on the available kernels: |
| 18746 |
</p> |
| 18747 |
|
| 18748 |
<table> |
| 18749 |
<tr> |
| 18750 |
<th>Kernel</th> |
| 18751 |
<th>Description</th> |
| 18752 |
</tr> |
| 18753 |
<tr> |
| 18754 |
<ti>gentoo</ti> |
| 18755 |
<ti>Default 2.6 kernel with support for multiple CPUs</ti> |
| 18756 |
</tr> |
| 18757 |
<tr> |
| 18758 |
<ti>gentoo-nofb</ti> |
| 18759 |
<ti>Same as <c>gentoo</c> but without framebuffer support</ti> |
| 18760 |
</tr> |
| 18761 |
<tr> |
| 18762 |
<ti>memtest86</ti> |
| 18763 |
<ti>Test your local RAM for errors</ti> |
| 18764 |
</tr> |
| 18765 |
</table> |
| 18766 |
|
| 18767 |
<p> |
| 18768 |
You can also provide kernel options. They represent optional settings you can |
| 18769 |
(de)activate at will. The following list is the same as the one you receive |
| 18770 |
when you press F2 at the bootscreen. |
| 18771 |
</p> |
| 18772 |
|
| 18773 |
<pre caption="Options available to pass to your kernel of choice"> |
| 18774 |
- agpgart loads agpgart (use if you have graphic problems,lockups) |
| 18775 |
- acpi=on loads support for ACPI firmware |
| 18776 |
- ide=nodma force disabling of DMA for malfunctioning IDE devices |
| 18777 |
- doscsi scan for scsi devices (breaks some ethernet cards) |
| 18778 |
- dopcmcia starts pcmcia service for PCMCIA cdroms |
| 18779 |
- nofirewire disables firewire modules in initrd (for firewire cdroms,etc) |
| 18780 |
- nokeymap disables keymap selection for non-us keyboard layouts |
| 18781 |
- docache cache the entire runtime portion of cd in RAM, allows you |
| 18782 |
to umount /mnt/cdrom to mount another cdrom. |
| 18783 |
- nodetect causes hwsetup/kudzu and hotplug not to run |
| 18784 |
- nousb disables usb module load from initrd, disables hotplug |
| 18785 |
- nodhcp dhcp does not automatically start if nic detected |
| 18786 |
- nohotplug disables loading hotplug service |
| 18787 |
- noapic disable apic (try if having hardware problems nics,scsi,etc) |
| 18788 |
- noevms2 disable loading of EVMS2 modules |
| 18789 |
- nolvm2 disable loading of LVM2 modules |
| 18790 |
- hdx=stroke allows you to partition the whole harddrive even when your BIOS |
| 18791 |
can't handle large harddrives |
| 18792 |
- noload=module1[,module2[,...]] |
| 18793 |
disable loading of specific kernel modules |
| 18794 |
</pre> |
| 18795 |
|
| 18796 |
<p> |
| 18797 |
Now boot your CD, select a kernel (if you are not happy with the default |
| 18798 |
<c>gentoo</c> kernel) and boot options. As an example, we show you how |
| 18799 |
to boot the <c>gentoo</c> kernel, with <c>dopcmcia</c> as kernel |
| 18800 |
parameters: |
| 18801 |
</p> |
| 18802 |
|
| 18803 |
<pre caption="Booting an Installation CD"> |
| 18804 |
boot: <i>gentoo dopcmcia</i> |
| 18805 |
</pre> |
| 18806 |
|
| 18807 |
<p> |
| 18808 |
You will then be greeted with a boot screen and progress bar. If you are |
| 18809 |
installing Gentoo on a system with a non-US keyboard, make sure you |
| 18810 |
immediately press Alt-F1 to switch to verbose mode and follow the prompt. If no |
| 18811 |
selection is made in 10 seconds the default (US keyboard) will be accepted and |
| 18812 |
the boot process will continue. Once the boot process completes, you will be |
| 18813 |
automatically logged in to the "Live" Gentoo Linux as |
| 18814 |
"root", the super user. You should have a root ("#") prompt |
| 18815 |
on the current console and can also switch to other consoles by pressing Alt-F2, |
| 18816 |
Alt-F3 and Alt-F4. Get back to the one you started on by pressing Alt-F1. |
| 18817 |
</p> |
| 18818 |
|
| 18819 |
</body> |
| 18820 |
</subsection> |
| 18821 |
<subsection id="hardware"> |
| 18822 |
<title>Extra Hardware Configuration</title> |
| 18823 |
<body> |
| 18824 |
|
| 18825 |
<p> |
| 18826 |
When the Installation CD boots, it tries to detect all your hardware devices and |
| 18827 |
loads the appropriate kernel modules to support your hardware. In the |
| 18828 |
vast majority of cases, it does a very good job. However, in some cases, it |
| 18829 |
may not auto-load the kernel modules you need. If the PCI auto-detection |
| 18830 |
missed some of your system's hardware, you will have to load the appropriate |
| 18831 |
kernel modules manually. |
| 18832 |
</p> |
| 18833 |
|
| 18834 |
<p> |
| 18835 |
In the next example we try to load the <c>8139too</c> module (support for |
| 18836 |
certain kinds of network interfaces): |
| 18837 |
</p> |
| 18838 |
|
| 18839 |
<pre caption="Loading kernel modules"> |
| 18840 |
# <i>modprobe 8139too</i> |
| 18841 |
</pre> |
| 18842 |
|
| 18843 |
<p> |
| 18844 |
If you need PCMCIA support, you should start the <c>pcmcia</c> init script: |
| 18845 |
</p> |
| 18846 |
|
| 18847 |
<pre caption="Starting the PCMCIA init script"> |
| 18848 |
# <i>/etc/init.d/pcmcia start</i> |
| 18849 |
</pre> |
| 18850 |
|
| 18851 |
</body> |
| 18852 |
</subsection> |
| 18853 |
<subsection> |
| 18854 |
<title>Optional: Tweaking Hard Disk Performance</title> |
| 18855 |
<body> |
| 18856 |
|
| 18857 |
<p> |
| 18858 |
If you are an advanced user, you might want to tweak the IDE hard disk |
| 18859 |
performance using <c>hdparm</c>. With the <c>-tT</c> options you can |
| 18860 |
test the performance of your disk (execute it several times to get a |
| 18861 |
more precise impression): |
| 18862 |
</p> |
| 18863 |
|
| 18864 |
<pre caption="Testing disk performance"> |
| 18865 |
# <i>hdparm -tT /dev/hda</i> |
| 18866 |
</pre> |
| 18867 |
|
| 18868 |
<p> |
| 18869 |
To tweak, you can use any of the following examples (or experiment |
| 18870 |
yourself) which use <path>/dev/hda</path> as disk (substitute with your |
| 18871 |
disk): |
| 18872 |
</p> |
| 18873 |
|
| 18874 |
<pre caption="Tweaking hard disk performance"> |
| 18875 |
<comment>Activate DMA:</comment> # <i>hdparm -d 1 /dev/hda</i> |
| 18876 |
<comment>Activate Safe Performance Options:</comment> # <i>hdparm -d 1 -A 1 -m 16 -u 1 -a 64 /dev/hda</i> |
| 18877 |
</pre> |
| 18878 |
|
| 18879 |
</body> |
| 18880 |
</subsection> |
| 18881 |
<subsection id="useraccounts"> |
| 18882 |
<title>Optional: User Accounts</title> |
| 18883 |
<body> |
| 18884 |
|
| 18885 |
<p> |
| 18886 |
If you plan on giving other people access to your installation |
| 18887 |
environment or you want to chat using <c>irssi</c> without root privileges (for |
| 18888 |
security reasons), you need to create the necessary user accounts and change |
| 18889 |
the root password. |
| 18890 |
</p> |
| 18891 |
|
| 18892 |
<p> |
| 18893 |
To change the root password, use the <c>passwd</c> utility: |
| 18894 |
</p> |
| 18895 |
|
| 18896 |
<pre caption="Changing the root password"> |
| 18897 |
# <i>passwd</i> |
| 18898 |
New password: <comment>(Enter your new password)</comment> |
| 18899 |
Re-enter password: <comment>(Re-enter your password)</comment> |
| 18900 |
</pre> |
| 18901 |
|
| 18902 |
<p> |
| 18903 |
To create a user account, we first enter their credentials, followed by |
| 18904 |
its password. We use <c>useradd</c> and <c>passwd</c> for these tasks. |
| 18905 |
In the next example, we create a user called "john". |
| 18906 |
</p> |
| 18907 |
|
| 18908 |
<pre caption="Creating a user account"> |
| 18909 |
# <i>useradd -m -G users john</i> |
| 18910 |
# <i>passwd john</i> |
| 18911 |
New password: <comment>(Enter john's password)</comment> |
| 18912 |
Re-enter password: <comment>(Re-enter john's password)</comment> |
| 18913 |
</pre> |
| 18914 |
|
| 18915 |
<p> |
| 18916 |
You can change your user id from root to the newly created user by using |
| 18917 |
<c>su</c>: |
| 18918 |
</p> |
| 18919 |
|
| 18920 |
<pre caption="Changing user id"> |
| 18921 |
# <i>su - john</i> |
| 18922 |
</pre> |
| 18923 |
|
| 18924 |
</body> |
| 18925 |
</subsection> |
| 18926 |
<subsection> |
| 18927 |
<title>Optional: Viewing Documentation while Installing</title> |
| 18928 |
<body> |
| 18929 |
|
| 18930 |
<p> |
| 18931 |
If you want to view the Gentoo Handbook (either from-CD or online) during the |
| 18932 |
installation, make sure you have created a user account (see <uri |
| 18933 |
link="#useraccounts">Optional: User Accounts</uri>). Then press <c>Alt-F2</c> to |
| 18934 |
go to a new terminal and log in. |
| 18935 |
</p> |
| 18936 |
|
| 18937 |
<p> |
| 18938 |
If you want to view the documentation on the CD you can immediately run |
| 18939 |
<c>links2</c> to read it: |
| 18940 |
</p> |
| 18941 |
|
| 18942 |
<pre caption="Viewing the on-CD documentation"> |
| 18943 |
# <i>links2 /mnt/cdrom/docs/html/index.html</i> |
| 18944 |
</pre> |
| 18945 |
|
| 18946 |
<p> |
| 18947 |
However, it is preferred that you use the online Gentoo Handbook as it will be |
| 18948 |
more recent than the one provided on the CD. You can view it using <c>links2</c> |
| 18949 |
as well, but only after having completed the <e>Configuring your Network</e> |
| 18950 |
chapter (otherwise you won't be able to go on the Internet to view the |
| 18951 |
document): |
| 18952 |
</p> |
| 18953 |
|
| 18954 |
<pre caption="Viewing the Online Documentation"> |
| 18955 |
# <i>links2 http://www.gentoo.org/doc/en/handbook/handbook-x86.xml</i> |
| 18956 |
</pre> |
| 18957 |
|
| 18958 |
<p> |
| 18959 |
You can go back to your original terminal by pressing <c>Alt-F1</c>. |
| 18960 |
</p> |
| 18961 |
|
| 18962 |
</body> |
| 18963 |
</subsection> |
| 18964 |
<subsection> |
| 18965 |
<title>Optional: Starting the SSH Daemon</title> |
| 18966 |
<body> |
| 18967 |
|
| 18968 |
<p> |
| 18969 |
If you want to allow other users to access your computer during the |
| 18970 |
Gentoo installation (perhaps because those users are going to help you |
| 18971 |
install Gentoo, or even do it for you), you need to create a user |
| 18972 |
account for them and perhaps even provide them with your root password |
| 18973 |
(<e>only</e> do that <e>if</e> you <b>fully trust</b> that user). |
| 18974 |
</p> |
| 18975 |
|
| 18976 |
<p> |
| 18977 |
To fire up the SSH daemon, execute the following command: |
| 18978 |
</p> |
| 18979 |
|
| 18980 |
<pre caption="Starting the SSH daemon"> |
| 18981 |
# <i>/etc/init.d/sshd start</i> |
| 18982 |
</pre> |
| 18983 |
|
| 18984 |
<p> |
| 18985 |
To be able to use sshd, you first need to set up your networking. Continue with |
| 18986 |
the chapter on <uri link="?part=1&chap=3">Configuring your Network</uri>. |
| 18987 |
</p> |
| 18988 |
|
| 18989 |
</body> |
| 18990 |
</subsection> |
| 18991 |
</section> |
| 18992 |
</sections> |
| 18993 |
|
| 18994 |
|
| 18995 |
|
| 18996 |
-- |
| 18997 |
gentoo-doc-cvs@g.o mailing list |
Archives