|
Lines 124-129
Link Here
|
| 124 |
|
124 |
|
| 125 |
</body> |
125 |
</body> |
| 126 |
</subsection> |
126 |
</subsection> |
|
|
127 |
</section> |
| 128 |
|
| 129 |
<section> |
| 130 |
<title>Configuring Portage</title> |
| 127 |
<subsection> |
131 |
<subsection> |
| 128 |
<title>Updating the Portage tree</title> |
132 |
<title>Updating the Portage tree</title> |
| 129 |
<body> |
133 |
<body> |
|
Lines 341-348
Link Here
|
| 341 |
after compiling <c>glibc</c> a full set of all available locales will be |
345 |
after compiling <c>glibc</c> a full set of all available locales will be |
| 342 |
created. As of now you can activate the <c>userlocales</c> USE flag and specify |
346 |
created. As of now you can activate the <c>userlocales</c> USE flag and specify |
| 343 |
only the locales you will need in <path>/etc/locales.build</path>. Only do this |
347 |
only the locales you will need in <path>/etc/locales.build</path>. Only do this |
| 344 |
if you know what locales to choose. This will not work for the bootstrapping, |
348 |
if you know what locales to choose. |
| 345 |
but when you recompile glibc afterwards it will. |
|
|
| 346 |
</p> |
349 |
</p> |
| 347 |
|
350 |
|
| 348 |
<pre caption="Activate the userlocales USE flag especially for glibc"> |
351 |
<pre caption="Activate the userlocales USE flag especially for glibc"> |
|
Lines 370-577
Link Here
|
| 370 |
de_DE@euro/ISO-8859-15 |
373 |
de_DE@euro/ISO-8859-15 |
| 371 |
</pre> |
374 |
</pre> |
| 372 |
|
375 |
|
| 373 |
</body> |
|
|
| 374 |
</subsection> |
| 375 |
</section> |
| 376 |
<section> |
| 377 |
<title>Differences between Stage1, Stage2 and Stage3</title> |
| 378 |
<body> |
| 379 |
|
| 380 |
<p> |
| 381 |
Now take a seat and think of your previous steps. We asked you to |
| 382 |
select a <e>stage1</e>, <e>stage2</e> or <e>stage3</e> and warned you |
| 383 |
that your choice is important for further installation steps. Well, this |
| 384 |
is the first place where your choice defines the subsequent steps. |
| 385 |
</p> |
| 386 |
|
| 387 |
<ul> |
| 388 |
<li> |
| 389 |
If you chose <e>stage1</e>, then you have to follow <e>both</e> steps in |
| 390 |
this chapter (starting with <uri link="#doc_chap3">Progressing from Stage1 |
| 391 |
to Stage2</uri>) |
| 392 |
</li> |
| 393 |
<li> |
| 394 |
If you chose <e>stage2</e> you only can skip the first step |
| 395 |
and immediately start with the second one (<uri link="#doc_chap4">Progressing |
| 396 |
from Stage2 to Stage3</uri>) |
| 397 |
</li> |
| 398 |
<li> |
| 399 |
If you chose <e>stage3</e> then you can skip both |
| 400 |
steps and continue with <uri link="?part=1&chap=7">Configuring the |
| 401 |
Kernel</uri> |
| 402 |
</li> |
| 403 |
</ul> |
| 404 |
|
| 405 |
</body> |
| 406 |
</section> |
| 407 |
<section> |
| 408 |
<title>Progressing from Stage1 to Stage2</title> |
| 409 |
<subsection> |
| 410 |
<title>Introduction to Bootstrapping</title> |
| 411 |
<body> |
| 412 |
|
| 413 |
<p> |
| 414 |
So, you want to compile everything from scratch? Okay then :-) |
| 415 |
</p> |
| 416 |
|
| 417 |
<p> |
| 418 |
In this step, we will <e>bootstrap</e> your Gentoo system. This takes a |
| 419 |
long time, but the result is a system that has been optimized from the |
| 420 |
ground up for your specific machine and needs. |
| 421 |
</p> |
| 422 |
|
| 423 |
<p> |
| 424 |
<e>Bootstrapping</e> means building the GNU C Library, GNU Compiler |
| 425 |
Collection and several other key system programs. |
| 426 |
</p> |
| 427 |
|
| 428 |
<p> |
| 429 |
Before starting the bootstrap, you might want to download all necessary |
| 430 |
sourcecode first. If you do not want to do this, continue |
| 431 |
with <uri link="#bootstrap">Bootstrapping the System</uri>. |
| 432 |
</p> |
| 433 |
|
| 434 |
</body> |
| 435 |
</subsection> |
| 436 |
<subsection> |
| 437 |
<title>Optional: Downloading the Sources First</title> |
| 438 |
<body> |
| 439 |
|
| 440 |
<p> |
| 441 |
If you haven't copied over all source code before, then the bootstrap |
| 442 |
script will download all necessary files. If you want to |
| 443 |
download the source code first and later bootstrap the system (for instance |
| 444 |
because you don't want to have your internet connection open during the |
| 445 |
compilation) use the <e>-f</e> option of the bootstrap script, which will |
| 446 |
fetch (hence the letter <e>f</e>) all source code for you. |
| 447 |
</p> |
| 448 |
|
| 449 |
<pre caption = "Downloading the necessary sources"> |
| 450 |
# <i>cd /usr/portage</i> |
| 451 |
# <i>scripts/bootstrap.sh -f</i> |
| 452 |
</pre> |
| 453 |
|
| 454 |
</body> |
| 455 |
</subsection> |
| 456 |
<subsection id="bootstrap"> |
| 457 |
<title>Bootstrapping the System</title> |
| 458 |
<body> |
| 459 |
|
| 460 |
<p> |
| 461 |
Okay then, take your keyboard and punch in the next commands to start |
| 462 |
the bootstrap. Then go amuse yourself with something else because this step |
| 463 |
takes quite some time to finish. |
| 464 |
</p> |
| 465 |
|
| 466 |
<pre caption = "Bootstrapping the system"> |
| 467 |
# <i>cd /usr/portage</i> |
| 468 |
# <i>scripts/bootstrap.sh</i> |
| 469 |
</pre> |
| 470 |
|
| 471 |
<p> |
| 472 |
Now continue with the next step, <uri link="#doc_chap4">Progressing from Stage2 |
| 473 |
to Stage3</uri>. |
| 474 |
</p> |
| 475 |
|
| 476 |
</body> |
| 477 |
</subsection> |
| 478 |
</section> |
| 479 |
<section> |
| 480 |
<title>Progressing from Stage2 to Stage3</title> |
| 481 |
<subsection> |
| 482 |
<title>Introduction</title> |
| 483 |
<body> |
| 484 |
|
| 485 |
<p> |
| 486 |
If you are reading this section, then you have a bootstrapped system |
| 487 |
(either because you bootstrapped it previously, or you are using a |
| 488 |
<e>stage2</e>). Then it is now time to build all system packages. |
| 489 |
</p> |
| 490 |
|
| 491 |
<p> |
| 492 |
<e>All</e> system packages? No, not really. In this step, you will build |
| 493 |
the system packages of which there are no alternatives to use. |
| 494 |
Some system packages have several alternatives (such as system loggers) |
| 495 |
and as Gentoo is all about choices, we don't want to force one upon you. |
| 496 |
</p> |
| 497 |
|
| 498 |
</body> |
| 499 |
</subsection> |
| 500 |
<subsection> |
| 501 |
<title>Optional: Viewing what will be done</title> |
| 502 |
<body> |
| 503 |
|
| 504 |
<p> |
| 505 |
If you want to know what packages will be installed, execute <c>emerge |
| 506 |
--pretend --emptytree system</c>. This will list all packages that will be |
| 507 |
built. As this list is pretty big, you should also use a pager like |
| 508 |
<c>less</c> or <c>more</c> to go up and down the list. |
| 509 |
</p> |
| 510 |
|
| 511 |
<pre caption = "View what 'emerge system' will do"> |
| 512 |
# <i>emerge --pretend --emptytree system | less</i> |
| 513 |
</pre> |
| 514 |
|
| 515 |
<p> |
| 516 |
Note that, if you haven't touched the default CFLAGS/CXXFLAGS setting, using |
| 517 |
<c>emerge --pretend --newuse system</c> is sufficient: it will rebuild the |
| 518 |
applications that are affected by a change in USE flags (compared to the USE |
| 519 |
flag we used while building the stage2). If you didn't touch |
| 520 |
the USE flag either, why are you running a stage2 installation then? |
| 521 |
</p> |
| 522 |
|
| 523 |
</body> |
| 524 |
</subsection> |
| 525 |
<subsection> |
| 526 |
<title>Optional: Downloading the Sources</title> |
| 527 |
<body> |
| 528 |
|
| 529 |
<p> |
| 530 |
If you want <c>emerge</c> to download the sources before you continue |
| 531 |
(for instance because you don't want the internet connection to be left |
| 532 |
open while you are building all packages) you can use the <e>--fetchonly</e> |
| 533 |
option of <c>emerge</c> which will fetch all sources for you. |
| 534 |
</p> |
| 535 |
|
| 536 |
<pre caption = "Fetching the sources"> |
| 537 |
# <i>emerge --fetchonly --emptytree system</i> |
| 538 |
</pre> |
| 539 |
|
| 540 |
</body> |
| 541 |
</subsection> |
| 542 |
<subsection> |
| 543 |
<title>Building the System</title> |
| 544 |
<body> |
| 545 |
|
| 546 |
<p> |
| 547 |
To start building the system, execute <c>emerge --emptytree system</c>. Then |
| 548 |
go do something to keep your mind busy, because this step takes a long time to |
| 549 |
complete. |
| 550 |
</p> |
| 551 |
|
| 552 |
<pre caption = "Building the System"> |
| 553 |
# <i>emerge --emptytree system</i> |
| 554 |
</pre> |
| 555 |
|
| 556 |
<p> |
376 |
<p> |
| 557 |
Again, if you haven't touched the default CFLAGS and CXXFLAGS setting, using |
377 |
Now continue with <uri link="?part=1&chap=7">Configuring the Kernel</uri>. |
| 558 |
<c>--newuse</c> is sufficient. |
|
|
| 559 |
</p> |
| 560 |
|
| 561 |
<p> |
| 562 |
You can for now safely ignore any warnings about updated configuration files |
| 563 |
(and running <c>etc-update</c>). When your Gentoo system is fully installed and |
| 564 |
booted, do read our documentation on <uri |
| 565 |
link="?part=3&chap=2#doc_chap3">Configuration File Protection</uri>. |
| 566 |
</p> |
| 567 |
|
| 568 |
<p> |
| 569 |
When the build process has completed, continue with <uri |
| 570 |
link="?part=1&chap=7">Configuring the Kernel</uri>. |
| 571 |
</p> |
378 |
</p> |
| 572 |
|
379 |
|
| 573 |
</body> |
380 |
</body> |
| 574 |
</subsection> |
381 |
</subsection> |
| 575 |
</section> |
382 |
</section> |
| 576 |
|
|
|
| 577 |
</sections> |
383 |
</sections> |
