Handbook:Parts/Installation/Stage/es

Ajustar la Fecha/Hora correcta
Antes de instalar Gentoo, asegúrese que la fecha y hora del sistema son correctas. ¡Un reloj mal configurado puede provocar resultados extraños mas adelante!

Para comprobar la fecha/hora actual, ejecute la orden date:

Si la fecha/hora mostrada es incorrecta, actualícela con la orden, con la siguiente sintaxis (Mes, Día, hora, minuto y Año). En esta etapa, se recomienda usar la hora UTC. Podrá utilizar su propia zona horaria más adelante.

Por ejemplo, para ajustar la fecha y hora a las 16:21 horas del 29 de marzo del 2014:

Descargar el stage comprimido (tarball)
Vaya al punto de montaje de Gentoo en el que ha montado el sistema de archivos raíz (probablemente ):

Dependiendo del medio de instalación, tendremos un par de herramientas disponibles para descargar el stage. Una de ellas es, un navegador de consola con menús. Para descargar un stage, recorra la lista de servidores espejo (mirror) de Gentoo así:

Para usar un proxy HTTP con, pase la URL con la opción -http-proxy:

Junto a  existe también el navegador. Al igual que  es un navegador de consola pero sin menús.

Si necesita pasar a través de un proxy, exporte las variables  y  :

Seleccione un servidor réplica cercano. Normalmente bastará con los servidores HTTP, sin embargo también están disponibles otros protocolos. Entre en el directorio. En él deberían aparecer todos los archivos de stage disponibles (quizá almacenados en subdirectorios con el nombre de cada subarquitectura). Seleccione uno y pulse para descargarlo.

Al igual que con los CDs de instalación mínimos, hay disponibles descargas adicionales:
 * Un archivo que contiene un listado de todos los archivos contenidos dentro del stage comprimido
 * Un archivo que contiene sumas de comprobación del archivo stage según diferentes algoritmos
 * Un archivo que, al igual que, contiene sumas de comprobación del archivo stage según diferentes algoritmos, y además está firmado criptográficamente para asegurar que es el proporcionado por el proyecto Gentoo

Cuando haya terminado, pulse para cerrar el navegador.

Después de descargar el archivo stage, es posible verificar su integridad. Use  y compare la salida con la suma de comprobación proporcionada por el archivo  o.

Por ejemplo, para validar la suma de comprobación SHA512:

Otra forma es usar la orden :

To validate the Whirlpool checksum:

Compare the output of these commands with the value registered in the files. The values need to match, otherwise the downloaded file might be corrupt (or the digests file is).

Just like with the ISO file, it is also possible to verify the cryptographic signature of the file using   to make sure the checksums have not been tampered with:

Unpacking the stage tarball
Now unpack the downloaded stage onto the system. We use  to proceed:

Make sure that the same options (xvjpf) are used. The x stands for Extract, the v for Verbose to see what happens during the extraction process (optional), the j for Decompress with bzip2, the p for Preserve permissions and the f to denote that we want to extract a File, not standard input.

Now that the stage is installed, continue with Configuring the compile options.

Introduction
To optimize Gentoo, it is possible to set a couple of variables which impact Portage behavior. All those variables can be set as environment variables (using ) but that isn't permanent. To keep the settings, Portage reads in the file, a configuration file for Portage.

Fire up an editor (in this guide we use ) to alter the optimization variables we will discuss hereafter.

From the file it is obvious how the file should be structured: commented lines start with "#", other lines define variables using the VARIABLE="content" syntax. Several of those variables are discussed next.

CFLAGS and CXXFLAGS
The CFLAGS and CXXFLAGS variables define the optimization flags for the gcc C and C++ compiler respectively. Although those are defined generally here, for maximum performance one would need to optimize these flags for each program separately. The reason for this is because every program is different. However, this is not manageable, hence the definition of these flags in the file.

In one should define the optimization flags that will make the system the most responsive generally. Don't place experimental settings in this variable; too much optimization can make programs behave bad (crash, or even worse, malfunction).

We will not explain all possible optimization options. To understand them all, read the GNU Online Manual(s) or the gcc info page ( -- only works on a working Linux system). The file itself also contains lots of examples and information; don't forget to read it too.

A first setting is the  or   flag, which specifies the name of the target architecture. Possible options are described in the file (as comments). A commonly used value is native as that tells the compiler to select the target architecture of the current system (the one users are installing Gentoo on).

A second one is the  flag (that is a capital O, not a zero), which specifies the gcc optimization class flag. Possible classes are s (for size-optimized), 0 (zero - for no optimizations), 1, 2 or even 3 for more speed-optimization flags (every class has the same flags as the one before, plus some extras). is the recommended default. is known to cause problems when used system-wide, so we recommend to stick to.

Another popular optimization flag is  (use pipes rather than temporary files for communication between the various stages of compilation). It has no impact on the generated code, but uses more memory. On systems with low memory, gcc might get killed. In that case, do not use this flag.

Using  (which doesn't keep the frame pointer in a register for functions that don't need one) might have serious repercussions on the debugging of applications.

When the CFLAGS and CXXFLAGS variables are defined, combine the several optimization flags in one string. The default values contained in the stage3 archive that is unpacked should be good enough. The following one is just an example:

MAKEOPTS
The  variable defines how many parallel compilations should occur when installing a package. A good choice is the number of CPUs (or CPU cores) in the system plus one, but this guideline isn't always perfect.

Ready, set, go
Update the file to match personal preference and save (nano users would hit ).

Then continue with Installing the Gentoo base system.