Install/es

Install Funtoo Linux

   {{{title}}}

{{{body}}}

Introducción

Este documento ha sido escrito para ayudarte a instalar Funtoo Linux en sistemas compatibles con PC, manteniendo opciones distractoras pertinentes a la configuración del sistema al mínimo.

Si tienes experiencia previa instalando Gentoo Linux, entonces muchos pasos te serán familiares, pero aun asi debes leerla, ya que hay algunas diferencias. Si eres nuevo instalando un Linux basado en Gentoo o totalmente nuevo en Linux - ¡Bienvenidos! Hemos intentado hacer estas instrucciones de instalación comprensibles para los nuevos usuarios también.

Resumen de Instalación

Este es el resumen básico del proceso de instalación de Funtoo:

1. Descarga y arranca el live CD de tu elección.
2. Prepara tu disco.
3. Crea y monta el sistema de archivos.
4. Instala el Stage 3 tarball de tu elección.
5. Inicia un Chroot en tu nuevo sistema.
6. Descarga el árbol de Portage.
7. Configura tu sistema y red.
8. Instala un kernel.
9. Instala un gestor de arranque.
10. Completa los pasos finales.
11. Reinicia y disfruta.

Live CD

Para instalar Funtoo Linux, primero necesitas arrancar la computadora mediante un Live CD de un sistema basado en Linux o un Live USB. Recomendamos el System Rescue CD basado en Gentoo, ya que contiene una gran cantidad de herramientas y utilidades y soporta tanto sistemas de 32 bits como de 64 bits. Se puede grabar en un CD/DVD o instalarlo en una memoria USB. Descárgalo aquí:

• Descargar desde osuosl.org
• Descargar desde funtoo.org

Acceso a la Red

Una vez que haya arrancado System Rescue CD, vea si tiene acceso a Internet. Se requiere acceso a Internet para la instalación Funtoo Linux:

root # ping www.google.com
PING www.google.com (216.58.217.36) 56(84) bytes of data.
64 bytes from den03s10-in-f4.1e100.net (216.58.217.36): icmp_seq=1 ttl=57 time=30.1 ms

Si el ping es satisfactorio (mirarás 64 bytes mensajes como el anterior,) entonces tu Red está configurada. Presiona Control-C para detener el ping.

Si necesitas configurar una conexión WiFi para acceso a internet, entonces se necesita realizar usando en el entorno gráfico el System Rescue CD. Ejecuta startx para iniciar una sesión gráfica.

root # startx

Entonces, usa el complemento de NetworkManager (icono en en la parte inferior derecha de la sesión gráfica, en la barra de tareas) para conectarte a una Red WiFi de tu elección. Luego, abre un terminal dentro de entorno gráfico, y deberías estar en condiciones de usar la terminal para completar el resto de los pasos.

Instalación Remota

Alternativamente, tu puedes iniciar sesión dentro de System Rescue CD sobre la red via SSH para realizar la instalación desde otro computador, puede ser el mejor camino para instalar Funtoo Linux.

Si desea completar la instalación remotamente, así es como. Primero, necesitarás asegurarte que System Rescue CD tiene una conexión de Red. Entonces, necesitarás configurar una contraseña para root en System Rescue CD:

root # passwd
New password: ********
Retype new password: ********
passwd: password updated successfully

Una vez que has escrito la contraseña, ahora necesitarás determinar la dirección IP de System Rescue CD, y entonces usa ssh para conectarte. Para saber la dirección IP usada por System Rescue CD, escribe ifconfig:

root # ifconfig

Una de las interfaces tendrá una dirección IP (listada como inet addr:) de tu LAN. Tu puedes conectarte remotamente, desde otro sistema sobre tu LAN, a System Rescue CD, y realizar los pasos desde la comodidad de un sistema operativo existente. Desde tu sistema remoto, escribe lo siguiente, reemplazando 1.2.3.4 con la dirección IP de System Rescue CD. Conectándote desde un existente sistema Linux o MacOS luciría así:

(remote system) $ ssh root@1.2.3.4
Password: **********

   Note

Si quieres conectarte remotamente desde un sistema Microsoft Windows existente, necesitarás descargar un cliente SSH para Windows, como PuTTY.

Después de conectarte via SSH, estarás conectado remotamente a System Rescue CD y podrás realizar los pasos de instalación.

Preparar Disco Duro

En esta sección, vamos a aprender acerca de las diferentes maneras en que Funtoo Linux puede arrancar desde un disco duro. Por arrancar "boot", nos referimos al proceso por el que Linux se inicia después de pulsar el botón de encendido en el pc de escritorio, portátil o servidor. Usted puede pensar en "arranque" como un proceso que se inicia con el firmware de su computadora (software incorporado) en marcha, y luego "encontrar" el núcleo de Linux y ejecutarlo. El kernel de Linux y luego se hace cargo, identifica todo el hardware y comienza.

Antecedentes

   Note

Si eres un principiante absoluto a Linux, puede ser menos confuso si se salta a la siguiente sección,Which to Use?

En épocas anteriores, sólo había una manera de arrancar un ordenador compatible con PC. Todos nuestros equipos de sobremesa y servidores tenían firmware estándar llamado "BIOS del PC," todos los discos duros utilizaban Master Boot Records en el inicio del disco duro, donde el BIOS de la PC era "buscar" para encontrar código del gestor de arranque que a la vez carga Linux y nuestros discos duros se dividen en diferentes regiones utilizando el esquema de partición MBR estándar. Eso fue la antigua manera. Y nos gustó de esa manera!

Luego, llegó EFI y de UEFI, que son de firmware nuevo estilo diseñado para arrancar los sistemas, junto con las tablas de particiones GPT para definir las particiones de disco en los discos de más de 2,2 TB. De repente, tuvimos una gran variedad de opciones para instalar y arrancar los sistemas Linux, convirtiendo lo que antes era un solo método para instalar en algo mucho más complejo.

Tomemos un momento para revisar las opciones disponibles para usted para configurar un disco duro para arrancar Funtoo Linux. Esta Guía de instalación utiliza y recomienda, el método de la vieja escuela de arranque del BIOS y el uso de un MBR. Funciona y (salvo casos excepcionales) se admite universalmente. No hay nada malo en ello. Si su disco de sistema es de 2 TB o más pequeño en tamaño, no le impide el uso de toda la capacidad de su disco.

Sin embargo, hay algunas situaciones en las que el método de la vieja escuela de instalación por medio del BIOS, no es óptima. Si usted tiene un disco duro de sistema> 2 TB de tamaño, con particiones MBR no permitirá acceder a toda su capacidad de almacenamiento. Así que esa es una de las razones. Otra razón es que hay algunos de los llamados sistemas de "PC" por ahí que no son compatibles con el arranque de BIOS ya, y se obliga a utilizar UEFI para arrancar. Así que, por compasión hacia las personas que caen en esta situación, esta Guía de instalación documentos UEFI arranque también.

Nuestra recomendación es todavía ir de la vieja escuela a menos que tenga razones para no hacerlo. El gestor de arranque que usaremos para cargar el kernel de Linux en esta guía se llama GRUB, así que llame a este método, el BIOS + GRUB (MBR) 'método'. Es el método tradicional de la creación de un sistema compatible con PC para arrancar Linux.

Si usted necesita utilizar UEFI para arrancar, no recomendamos utilizar el MBR en absoluto para el arranque, ya que algunos sistemas soportan esto, pero otros no lo hacen. En lugar de ello, le recomendamos que utilice UEFI para arrancar GRUB, que a su vez cargar Linux. Nos referimos a este método como el UEFI + GRUB (GPT) método.

Y sí, hay más métodos, algunas de las cuales están documentadas en el Métodos de arranque página. Se utilizó para recomendar un método 'GRUB + BIOS (GPT)' pero no es compatible consistentemente a través de una amplia variedad de hardware.

¿Cuál Usar?

'La gran pregunta es - el método de arranque que se debe utilizar?' Así es como para decir.

Principio 1 - Old School

Si puede arrancar con fiabilidad Rescue System CD y te muestra un menú de color azul claro inicial, va a iniciar el CD con el BIOS, y es probable que por lo tanto puede arrancar Funtoo Linux usando el BIOS. Por lo tanto, ir de la vieja escuela y el uso arranque de BIOS, a menos que usted tiene alguna razón para utilizar UEFI, como tener un> disco del sistema 2.2TB. En ese caso, véase el Principio 2, ya que su sistema puede soportar el arranque UEFI.

Principio 2 - New School

Si puede arrancar con fiabilidad Rescue System CD y te muestra un menú en blanco y negro inicial - felicitaciones, el sistema está configurado para soportar el arranque UEFI. Esto significa que usted está listo para instalar Funtoo Linux para arrancar a través de UEFI. Su sistema aún puede soportar el arranque de BIOS, pero sólo puede intentar primero UEFI. Usted puede hurgar en la configuración de inicio del BIOS y jugar con esto.

Para instalar Funtoo Linux para arrancar a través del método de UEFI Nueva Escuela, debe arrancar System Rescue CD utilizando UEFI. Si arranca con éxito sysresccd con UEFI, verá una pantalla en blanco y negro inicial para seleccionar el modo en el que va a arrancar cd de boot system rescue. De lo contrario, si usted ve una pantalla azul con el texto negro, UEFI no será activa y usted no será capaz de configurar el arranque UEFI más adelante en el proceso de instalación!

Método de la Vieja Escuela (BIOS/MBR)

En primer lugar, es una buena idea para asegurarse de que ha encontrado el disco duro correcto para particionar. Trate este comando y verifique que / dev / sda es el disco que desea particionar:

root # fdisk -l /dev/sda

Disk /dev/sda: 640.1 GB, 640135028736 bytes, 1250263728 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: gpt

root #         Start          End    Size  Type            Name
 1         2048   1250263694  596.2G  Linux filesyste Linux filesystem

Ahora, se recomienda que borre cualquier MBR existente o tablas de particiones GPT en el disco, lo que podría confundir a la BIOS del sistema durante el arranque. Esto se logra mediante sgdisk: Template:Advertencia

root # sgdisk --zap-all /dev/sda

Creating new GPT entries.
GPT data structures destroyed! You may now partition the disk using fdisk or
other utilities.

Esta salida no es algo de lo que debas preocuparte, siendo que el comando tuvo éxico:

***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory. 
***************************************************************

Ahora vamos a usar fdisk para crear la table de partición MBR y las particiones:

root # fdisk /dev/sda

Dentro de fdisk, sigue estos pasos:

Vaciar la tabla de particiones

Command (m for help): o ↵

Crear la partición 1

Command (m for help): n ↵
Partition type (default p): ↵
Partition number (1-4, default 1): ↵
First sector: ↵
Last sector: +128M ↵

Crear partición 2 (swap):

Command (m for help): n ↵
Partition type (default p): ↵
Partition number (2-4, default 2): ↵
First sector: ↵
Last sector: +2G ↵
Command (m for help): t ↵ 
Partition number (1,2, default 2):  ↵
Hex code (type L to list all codes): 82 ↵

Crear la partición de root:

Command (m for help): n ↵
Partition type (default p): ↵
Partition number (3,4, default 3): ↵
First sector: ↵
Last sector: ↵

Verificar la tabla de particiones:

Command (m for help): p

Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x82abc9a6

Device    Boot     Start       End    Blocks  Id System
/dev/sda1           2048    264191    131072  83 Linux
/dev/sda2         264192   4458495   2097152  82 Linux swap / Solaris
/dev/sda3        4458496 625142447 310341976  83 Linux

Escribir la tabla de particiones al disco:

Command (m for help): w

Tu nueva tabla de particiones MBR será ahora escrita a tu disco de sistema.

   Note

¡Ya terminaste con las particiones! Ahora, brinca a Creando sistemas de archivos.

Método de la Nueva-Escuela (UEFI/GPT)

   Note

Usa este método si te interesas en iniciar usando UEFI, y si el menú de inicio del System Rescue CD fue blanco y negro. Si fue azul claro, este método no funcionará.

The gdisk commands to create a GPT partition table are as follows. Adapt sizes as necessary, although these defaults will work for most users. Start gdisk:

root # gdisk /dev/sda

Within gdisk, follow these steps:

Crea una nueva tabla de particiones vacía (Esto borrará todos los datos en el disco cuando se salva):

Command: o ↵
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): y ↵

Crear la Partición 1 (boot):

Command: n ↵
Partition Number: 1 ↵
First sector: ↵
Last sector: +500M ↵
Hex Code: EF00 ↵

Crea Partición 2 (swap):

Command: n ↵
Partition Number: 2 ↵
First sector: ↵
Last sector: +4G ↵
Hex Code: 8200 ↵

Crea Partición 3 (root):

Command: n ↵
Partition Number: 3 ↵
First sector: ↵
Last sector: ↵ (for rest of disk)
Hex Code: ↵

Durante este proceso puedes teclear "p" y presionar Enter para visualizar la tabla de particiones actuales. Sí cometes algún error, puedes teclear "d" para borrar una partición existente que fue creada por error previamente. Cuando estas de acuerdo con las particiones creadas puedes teclear "w" para grabar la configuración en disco:

Escribir la Tabla de Particiones en Disco:

Command: w ↵
Do you want to proceed? (Y/N): Y ↵

La tabla de particiones ahora estará escrita en disco, puedes presionar gdisk para cerrar

Now, your GPT/GUID partitions have been created, and will show up as the following block devices under Linux:

• /dev/sda1, which will be used to hold the /boot filesystem,

• /dev/sda2, which will be used for swap space, and

• /dev/sda3, which will hold your root filesystem.

   Tip

You can verify that the block devices above were correctly created by running the command lsblk.

Creating filesystems

   Note

This section covers both BIOS and UEFI installs. Don't skip it!

Before your newly-created partitions can be used, the block devices that were created in the previous step need to be initialized with filesystem metadata. This process is known as creating a filesystem on the block devices. After filesystems are created on the block devices, they can be mounted and used to store files.

Let's keep this simple. Are you using old-school MBR partitions? If so, let's create an ext2 filesystem on /dev/sda1:

root # mkfs.ext2 /dev/sda1

If you're using new-school GPT partitions for UEFI, you'll want to create a vfat filesystem on /dev/sda1, because this is what UEFI is able to read:

root # mkfs.vfat -F 32 /dev/sda1

Now, let's create a swap partition. This partition will be used as disk-based virtual memory for your Funtoo Linux system.

You will not create a filesystem on your swap partition, since it is not used to store files. But it is necessary to initialize it using the mkswap command. Then we'll run the swapon command to make your newly-initialized swap space immediately active within the live CD environment, in case it is needed during the rest of the install process:

root # mkswap /dev/sda2
root # swapon /dev/sda2

Ahora, necesitamos crear un sistema de archivos root. Aquí es donde Funtoo Linux vive. Nosotros generalmente recomendamos ext4 o XFS para sistemas de archivos root. Si no estas seguro, elige ext4. Aquí esta como crear un sistema de archivos root ext4.

root # mkfs.ext4 /dev/sda3

...y aquí esta como crear un sistema de archivos root XFS, si prefieres usrar XFS en lugar de ext4

root # mkfs.xfs /dev/sda3

Your filesystems (and swap) have all now been initialized, so that that can be mounted (attached to your existing directory heirarchy) and used to store files. We are ready to begin installing Funtoo Linux on these brand-new filesystems.

   Warning

When deploying an OpenVZ host, please use ext4 exclusively. The Parallels development team tests extensively with ext4, and modern versions of openvz-rhel6-stable are not compatible with XFS, and you may experience kernel bugs.

Mounting filesystems

Mount the newly-created filesystems as follows, creating /mnt/funtoo as the installation mount point:

root # mkdir /mnt/funtoo
root # mount /dev/sda3 /mnt/funtoo
root # mkdir /mnt/funtoo/boot
root # mount /dev/sda1 /mnt/funtoo/boot

Optionally, if you have a separate filesystem for /home or anything else:

root # mkdir /mnt/funtoo/home
root # mount /dev/sda4 /mnt/funtoo/home

If you have /tmp or /var/tmp on a separate filesystem, be sure to change the permissions of the mount point to be globally-writeable after mounting, as follows:

root # chmod 1777 /mnt/funtoo/tmp

Setting the Date

   Important

If your system's date and time are too far off (typically by months or years,) then it may prevent Portage from properly downloading source tarballs. This is because some of our sources are downloaded via HTTPS, which use SSL certificates and are marked with an activation and expiration date. However, if your system time is relatively close to correct, you can probably skip this step for now.

Now is a good time to verify the date and time are correctly set to UTC. Use the date command to verify the date and time:

root # date
Fri Jul 15 19:47:18 UTC 2011

If the date and/or time need to be corrected, do so using date MMDDhhmmYYYY, keeping in mind hhmm are in 24-hour format. The example below changes the date and time to "July 16th, 2011 @ 8:00PM" UTC:

root # date 071620002011
Fri Jul 16 20:00:00 UTC 2011

Once you have set the system clock, it's a very good idea to copy the time to the hardware clock, so it persists across reboots:

root # hwclock --systohc

Installing the Stage 3 tarball

Now that filesystems are created and your hardware and system clock are set, the next step is downloading the initial Stage 3 tarball. The Stage 3 is a pre-compiled system used as a starting point to install Funtoo Linux. Notice: if you're using virtual machines (like Vbox) generic stage3 images are preferred rather than cpu-optimized ones.

To download the correct build of Funtoo Linux for your system, head over to the Subarches page. Subarches are builds of Funtoo Linux that are designed to run on a particular type of CPU, to offer the best possible performance. They also take advantage of the instruction sets available for each CPU.

The Subarches page lists all CPU-optimized versions of Funtoo Linux. Find the one that is appropriate for the type of CPU that your system has, and then click on its name in the first column (such as corei7, for example.) You will then go to a page dedicated to that subarch, and the available stage3's available for download will be listed.

For most subarches, you will have several stage3's available to choose from. This next section will help you understand which one to pick.

Which Build?

If you're not sure, pick funtoo-current.

Funtoo Linux has various different 'builds':

Build	Description
funtoo-current	The most commonly-selected build of Funtoo Linux. Receives rapid updates and preferred by desktop users.
funtoo-stable	Emphasizes less-frequent package updates and trusted, reliable versions of packages over the latest versions.

Which Variant?

If you're not sure, pick standard.

Our "regular" stage3's are listed with a variant of standard. The following variant builds are available:

Variant	Description
standard	The "standard" version of Funtoo Linux
pure64	A 64-bit build that drops multilib (32-bit compatibility) support. Can be ideal for server systems.
hardened	Includes PIE/SSP toolchain for enhanced security. PIE does require the use of PaX in the kernel, while SSP works with any kernel, and provides enhanced security in user-space to avoid stack-based exploits. For expert users.

Download the Stage3

Once you have found the stage3 that you would like to download, use wget to download the Stage 3 tarball you have chosen to use as the basis for your new Funtoo Linux system. It should be saved to the /mnt/funtoo directory as follows:

root # cd /mnt/funtoo
root # wget http://build.funtoo.org/funtoo-current/x86-64bit/generic_64/stage3-latest.tar.xz

Note that 64-bit systems can run 32-bit or 64-bit stages, but 32-bit systems can only run 32-bit stages. Make sure that you select a Stage 3 build that is appropriate for your CPU. If you are not certain, it is a safe bet to choose the generic_64 or generic_32 stage. Consult the Subarches page for more information.

Once the stage is downloaded, extract the contents with the following command, substituting in the actual name of your stage 3 tarball:

root # tar xpf stage3-latest.tar.xz

   Important

It is very important to use tar's "p" option when extracting the Stage 3 tarball - it tells tar to preserve any permissions and ownership that exist within the archive. Without this option, your Funtoo Linux filesystem permissions will be incorrect.

Chroot into Funtoo

To install Funtoo Linux, the chroot command is first used. The chroot command will "switch into" the new Funtoo Linux system, so the commands you execute after running "chroot" will run within your newly-extracted Funtoo Linux system.

Before chrooting, there are a few things that need to be done to set up the chroot environment. You will need to mount /proc, /sys and /dev inside your new system. Use the following commands to do so:

root # cd /mnt/funtoo
root # mount -t proc none proc
root # mount --rbind /sys sys
root # mount --rbind /dev dev

You'll also want to copy over resolv.conf in order to have proper resolution of Internet hostnames from inside the chroot:

root # cp /etc/resolv.conf /mnt/funtoo/etc/

Now you can chroot into your new system. Use env before chroot to ensure that no environment settings from the installation media are pulled in to your new system:

root # env -i HOME=/root TERM=$TERM chroot . bash -l

   Note

For users of live CDs with 64-bit kernels installing 32-bit systems: Some software may use uname -r to check whether the system is 32 or 64-bit. You may want append linux32 to the chroot command as a workaround, but it's generally not needed.

   Important

If you receive the error "chroot: failed to run command `/bin/bash': Exec format error", it is most likely because you are running a 32-bit kernel and trying to execute 64-bit code. Make sure that you have selected the proper type of kernel when booting SystemRescueCD.

It's also a good idea to change the default command prompt while inside the chroot. This will avoid confusion if you have to change terminals. Use this command:

root # export PS1="(chroot) $PS1"

Test internet name resolution from within the chroot:

root # ping -c 5 google.com

If you can't ping, make sure /etc/resolv.conf doesn't contain things like 127.0.x.x addresses, if it does, change the 127.0.x.x entry to 8.8.8.8 -- Google's public dns address. Make sure to replace this with your dns of choice once the system is installed.

Congratulations! You are now chrooted inside a Funtoo Linux system. Now it's time to get Funtoo Linux properly configured so that Funtoo Linux will start successfully, without any manual assistance, when your system is restarted.

Downloading the Portage tree

   Note

For an alternative way to do this, see Installing Portage From Snapshot.

Now it's time to install a copy of the Portage repository, which contains package scripts (ebuilds) that tell portage how to build and install thousands of different software packages. To create the Portage repository, simply run emerge --sync from within the chroot. This will automatically clone the portage tree from GitHub:

(chroot) # emerge --sync

   Important

If you receive the error with initial emerge --sync due to git protocol restrictions, set the SYNC variable in /etc/portage/make.conf to "https://github.com/funtoo/ports-2012.git"

Configuring your system

As is expected from a Linux distribution, Funtoo Linux has its share of configuration files. The one file you are absolutely required to edit in order to ensure that Funtoo Linux boots successfully is /etc/fstab. The others are optional.

Using Nano

The default editor included in the chroot environment is called nano. To edit one of the files below, run nano as follows:

(chroot) # nano /etc/fstab

When in the editor, you can use arrow keys to move the cursor, and common keys like backspace and delete will work as expected. To save the file, press Control-X, and answer y when prompted to save the modified buffer if you would like to save your changes.

Configuration Files

Here are a full list of files that you may want to edit, depending on your needs:

File	Do I need to change it?	Description
/etc/fstab	YES - required	Mount points for all filesystems to be used at boot time. This file must reflect your disk partition setup. We'll guide you through modifying this file below.
/etc/localtime	Maybe - recommended	Your timezone, which will default to UTC if not set. This should be a symbolic link to something located under /usr/share/zoneinfo (e.g. /usr/share/zoneinfo/America/Montreal)
/etc/make.conf (symlink) - also known as: /etc/portage/make.conf	Maybe - recommended	Parameters used by gcc (compiler), portage, and make. It's a good idea to set MAKEOPTS. This is covered later in this document.
/etc/conf.d/hostname	Maybe - recommended	Used to set system hostname. Set the hostname variable to the fully-qualified (with dots, ie. foo.funtoo.org) name if you have one. Otherwise, set to the local system hostname (without dots, ie. foo). Defaults to localhost if not set.
/etc/hosts	No	You no longer need to manually set the hostname in this file. This file is automatically generated by /etc/init.d/hostname.
/etc/conf.d/keymaps	Optional	Keyboard mapping configuration file (for console pseudo-terminals). Set if you have a non-US keyboard. See Funtoo Linux Localization.
/etc/conf.d/hwclock	Optional	How the time of the battery-backed hardware clock of the system is interpreted (UTC or local time). Linux uses the battery-backed hardware clock to initialize the system clock when the system is booted.
/etc/conf.d/modules	Optional	Kernel modules to load automatically at system startup. Typically not required. See Additional Kernel Resources for more info.
/etc/conf.d/consolefont	Optional	Allows you to specify the default console font. To apply this font, enable the consolefont service by running rc-update add consolefont.
profiles	Optional	Some useful portage settings that may help speed up intial configuration.

If you're installing an English version of Funtoo Linux, you're in luck, as most of the configuration files can be used as-is. If you're installing for another locale, don't worry. We will walk you through the necessary configuration steps on the Funtoo Linux Localization page, and if needed, there's always plenty of friendly, helpful support available. (See Community)

Let's go ahead and see what we have to do. Use nano -w <name_of_file> to edit files -- the "-w" argument disables word-wrapping, which is handy when editing configuration files. You can copy and paste from the examples.

   Warning

It's important to edit your /etc/fstab file before you reboot! You will need to modify both the "fs" and "type" columns to match the settings for your partitions and filesystems that you created with gdisk or fdisk. Skipping this step may prevent Funtoo Linux from booting successfully.

/etc/fstab

/etc/fstab is used by the mount command which is run when your system boots. Lines in this file inform mount about filesystems to be mounted and how they should be mounted. In order for the system to boot properly, you must edit /etc/fstab and ensure that it reflects the partition configuration you used earlier in the install process. If you can't remember the partition configuration that you used earlier, the lsblk command may be of help to you:

(chroot) # nano -w /etc/fstab

   /etc/fstab - An example fstab file

# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
#
# See the manpage fstab(5) for more information.
#
# <fs>	     <mountpoint>  <type>  <opts>         <dump/pass>

/dev/sda1    /boot         ext2    noauto,noatime 1 2
/dev/sda2    none          swap    sw             0 0
/dev/sda3    /             ext4    noatime        0 1
#/dev/cdrom  /mnt/cdrom    auto    noauto,ro      0 0

   Note

Currently, our default /etc/fstabfile has the root filesystem as /dev/sda4 and the swap partition as /dev/sda3. These will need to be changed to /dev/sda3 and /dev/sda2, respectively.

   Note

If you're using UEFI to boot, change the /dev/sda1 line so that it says vfat instead of ext2. Similarly, make sure that the /dev/sda3 line specifies either xfs or ext4, depending on which filesystem you chose earlier on in the installation process when you created filesystems.

/etc/localtime

/etc/localtime is used to specify the timezone that your machine is in, and defaults to UTC. If you would like your Funtoo Linux system to use local time, you should replace /etc/localtime with a symbolic link to the timezone that you wish to use.

(chroot) # ln -sf /usr/share/zoneinfo/MST7MDT /etc/localtime

The above sets the timezone to Mountain Standard Time (with daylight savings). Type ls /usr/share/zoneinfo to list available timezones. There are also sub-directories containing timezones described by location.

/etc/portage/make.conf

MAKEOPTS can be used to define how many parallel compilations should occur when you compile a package, which can speed up compilation significantly. A rule of thumb is the number of CPUs (or CPU threads) in your system plus one. If, for example, you have a dual core processor without hyper-threading, then you would set MAKEOPTS to 3:

MAKEOPTS="-j3" 

If you are unsure about how many processors/threads you have, then use nproc to help you.

(chroot) # nproc
16

Set MAKEOPTS to this number plus one:

MAKEOPTS="-j17"

USE flags define what functionality is enabled when packages are built. It is not recommended to add a lot of USE flags during installation; you should wait until you have a working, bootable system before changing your USE flags. A USE flag prefixed with a minus ("-") sign tells Portage not to use the flag when compiling. A Funtoo guide to USE flags will be available in the future. For now, you can find out more information about USE flags in the Gentoo Handbook.

LINGUAS tells Portage which local language to compile the system and applications in (those who use LINGUAS variable like OpenOffice). It is not usually necessary to set this if you use English. If you want another language such as French (fr) or German (de), set LINGUAS appropriately:

LINGUAS="fr"

/etc/conf.d/hwclock

If you dual-boot with Windows, you'll need to edit this file and change the value of clock from UTC to local, because Windows will set your hardware clock to local time every time you boot Windows. Otherwise you normally wouldn't need to edit this file.

(chroot) # nano -w /etc/conf.d/hwclock

Localization

By default, Funtoo Linux is configured with Unicode (UTF-8) enabled, and for the US English locale and keyboard. If you would like to configure your system to use a non-English locale or keyboard, see Funtoo Linux Localization.

Introducing Portage

Portage, the Funtoo Linux package manager has a command called emerge which is used to build and install packages from source. It also takes care of installing all of the package's dependencies. You call emerge like this:

(chroot) # emerge packagename

When you install a package by specifying its name in the command-line, Portage records its name in the /var/lib/portage/world file. It does so because it assumes that, since you have installed it by name, you want to consider it part of your system and want to keep the package updated in the future. This is a handy feature, since when packages are being added to the world set, we can update our entire system by typing:

(chroot) # emerge --sync
(chroot) # emerge -auDN @world

Este es el proceso "oficial" para actualizar tu sistema Funtoo Linux. Arriba, primero actualizamos nuestro árbol Portage usando git para traer nuestros ebuilds (scripts) más recientes, y después executamos un commando emerge para actualizar el conjunto de paquetes world . Las opciones especificadas le indican a emerge:

• a - show us what will be emerged, and ask us if we want to proceed
• u - update the packages we specify -- don't emerge them again if they are already emerged.
• D - Consider the entire dependency tree of packages when looking for updates. In other words, do a deep update.
• N - Update any packages that have changed (new) USE settings.

You should also consider passing --with-bdeps=y when emerging @world, at least once in a while. This will update build dependencies as well.

Of course, sometimes we want to install a package but not add it to the world file. This is often done because you only want the package installed temporarily or because you know the package in question is a dependnecy of another package. If this behavior is desired, you call emerge like this:

(chroot) # emerge -1 packagename

Advanced users may be interested in the Emerge wiki page.

Updating World

Now is actually a very good time to update the entire system and it can be a good idea to do so prior to first boot.

(chroot) # emerge --sync
(chroot) # emerge -auDN @world

   Important

Make sure you read any post emerge messages and follow their instructions. This is especially true if you have upgraded perl or python.

Kernel

Starting mid-May 2015, Funtoo Linux stage3's include a pre-built debian-sources kernel to make installation faster and easier. To see if debian-sources is installed, type:

(chroot) # emerge -s debian-sources
Searching...    
[ Results for search key : debian-sources ]
[ Applications found : 1 ]

*  sys-kernel/debian-sources
      Latest version available: 3.19.3
      Latest version installed: 3.19.3
      Size of files: 81,292 kB
      Homepage:      http://www.debian.org
      Description:   Debian Sources (and optional binary kernel)
      License:       GPL-2

If a version is listed under Latest version installed, then debian-sources is already pre-built for you and you can skip the rest of the Kernel section, and proceed to the Installing a Bootloader section.

Building the Kernel

If you need to build a kernel for Funtoo Linux, please follow these steps:

   Note

See Funtoo Linux Kernels for a full list of kernels supported in Funtoo Linux. We recommend debian-sources for new users.

   Important

debian-sources with binary USE flag requires at least 14GB free in /var/tmp and takes around 1 hour to build on a Intel Core i7 Processor.

Hagamos emerge a nuestro kernel:

(chroot) # emerge debian-sources

Una vez que emerge completa, tendrás instalados en /boot un nuevo kernel y una nueva initramfs , más los encabezados del kernel instalados en /usr/src/linux, y estarás listo para configurar el arrancador para cargar éstos para arrancar tu sistema Funtoo Linux.

   Warning

If you have a RAID in your machine, the kernel installation will pull in the mdadm tool as a dependency. It is important to edit the /etc/mdadm.conf file prior to rebooting the machine so the RAID is properly recognised and set up before the kernel attempts to mount it in the tree. Failing to do so can result in an unusable or even unbootable system! For specific details, consult the mdadm man page man mdadm or the mdadm ebuild page.

   Note

NVIDIA card users: the binary USE flag installs the Nouveau drivers which cannot be loaded at the same time as the proprietary drivers, and cannot be unloaded at runtime because of KMS. You need to blacklist it under /etc/modprobe.d/.

   Note

For an overview of other kernel options for Funtoo Linux, see Funtoo Linux Kernels. There may be modules that the Debian kernel doesn't include, a situation where genkernel would be useful. Also be sure to see hardware compatibility information.

Installing a Bootloader

These install instructions show you how to use GRUB to boot using BIOS (old-school) or UEFI (new-school). As of boot-update-1.7.2, now in Portage, the steps are very similar.

First, emerge boot-update. This will also cause grub-2 and efibootmgr to be merged, since they are dependencies:

(chroot) # emerge boot-update

Then, edit /etc/boot.conf using nano and specify "Funtoo Linux genkernel" as the default setting at the top of the file, replacing "Funtoo Linux".

/etc/boot.conf should now look like this:

   /etc/boot.conf

boot {
	generate grub
	default "Funtoo Linux genkernel" 
	timeout 3 
}

"Funtoo Linux" {
	kernel bzImage[-v]
}

"Funtoo Linux genkernel" {
	kernel kernel[-v]
	initrd initramfs[-v]
	params += real_root=auto 
} 

"Funtoo Linux better-initramfs" {
	kernel vmlinuz[-v]
	initrd /initramfs.cpio.gz
}

If you are booting a custom or non-default kernel, please read man boot.conf for information on the various options available to you.

Old School (BIOS) MBR

When using "old school" BIOS booting, run the following command to install GRUB to your MBR, and generate the /boot/grub/grub.cfg configuration file that GRUB will use for booting:

(chroot) # grub-install --target=i386-pc --no-floppy /dev/sda
(chroot) # boot-update

New School (UEFI) Boot Entry

If you're using "new school" UEFI booting, run of the following sets of commands, depending on whether you are installing a 64-bit or 32-bit system. This will add GRUB as a UEFI boot entry.

For x86-64bit systems:

(chroot) # grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda
(chroot) # boot-update

For x86-32bit systems:

(chroot) # grub-install --target=i386-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda
(chroot) # boot-update

First Boot, and in the future...

OK -- you are ready to boot!

You only need to run grub-install when you first install Funtoo Linux, but you need to re-run boot-update every time you modify your /etc/boot.conf file or add new kernels to your system. This will regenerate /boot/grub/grub.cfg so that you will have new kernels available in your GRUB boot menu, the next time you reboot.

Configuring your network

It's important to ensure that you will be able to connect to your local-area network after you reboot into Funtoo Linux. There are three approaches you can use for configuring your network: NetworkManager, dhcpcd, and the Funtoo Linux Networking scripts. Here's how to choose which one to use based on the type of network you want to set up.

Wi-Fi

For laptop/mobile systems where you will be using Wi-Fi, roaming, and connecting to various networks NetworkManager is strongly recommended. Since Wi-Fi cards require firmware to operate, it is also recommended that you emerge the linux-firmware ebuild:

(chroot) # emerge linux-firmware networkmanager
(chroot) # rc-update add NetworkManager default

The above command will ensure that NetworkManager starts after you boot into Funtoo Linux. Once you've completed these installation steps and have booted into Funtoo Linux, you can use the addwifi command to connect to a Wi-Fi access point:

root # addwifi -S wpa -K 'wifipassword' mywifinetwork

For more information about NetworkManager, see the NetworkManager package page.

   Note

wpa_supplicant is also a good choice for wireless network connections. See the net-wireless/wpa_supplicant package for steps involved in setting up wpa_supplicant.

Desktop (Wired DHCP)

For a home desktop or workstation with wired Ethernet that will use DHCP, the simplest and most effective option to enable network connectivity is to simply add dhcpcd to the default runlevel:

(chroot) # rc-update add dhcpcd default

When you reboot, dhcpcd will run in the background and manage all network interfaces and use DHCP to acquire network addresses from a DHCP server.

If your upstream DHCP server is dnsmasq, it can be configured to assign addresses via mac address to make servers on DHCP feasible.

Server (Static IP)

For servers, the Funtoo Linux Networking scripts are recommended. They are optimized for static configurations and things like virtual ethernet bridging for virtualization setups. See Funtoo Linux Networking for information on how to use Funtoo Linux's template-based network configuration system.

Hostname

By default Funtoo uses "localhost" as hostname. Although the system will work perfectly fine using this name, some ebuilds refuse to install when detecting localhost as hostname. It also may create confusion if several systems use the same hostname. Therefore, it is advised to change it to a more meaningful name. The hostname itself is arbitrary, meaning you can choose almost any combination of characters, as long as it makes sense to the system administrator. To change the hostname, edit

(chroot) # nano /etc/conf.d/hostname

Look for the line starting with hostname and change the entry between the quotes. Save the file, on the next boot Funtoo will use the new hostname.

   Warning

Do not use special characters in the hostname, as the shell may interpret these, leading to unpredictable results. Use the Latin alphabet: a-z, A-Z, 0-9

   Tip

Use short hostnames (up to 8 or 10 characters) to prevent the terminal screen being filled with the hostname, leaving little space for the command itself. This become particularly poignant when coding long command strings in various programming languages like Bash, Python, SQL and Perl

Finishing Steps

Set your root password

It's imperative that you set your root password before rebooting so that you can log in.

(chroot) # passwd

Restart your system

Now is the time to leave chroot, to unmount Funtoo Linux partitions and files and to restart your computer. When you restart, the GRUB boot loader will start, load the Linux kernel and initramfs, and your system will begin booting.

Leave the chroot, change directory to /mnt, unmount your Funtoo partitions, and reboot.

(chroot) # exit
root # cd /mnt
root # umount -lR funtoo
root # reboot

   Note

System Rescue CD will gracefully unmount your new Funtoo filesystems as part of its normal shutdown sequence.

You should now see your system reboot, the GRUB boot loader appear for a few seconds, and then see the Linux kernel and initramfs loading. After this, you should see Funtoo Linux itself start to boot, and you should be greeted with a login: prompt. Funtoo Linux has been successfully installed!

Profiles

Once you have rebooted into Funtoo Linux, you can further customize your system to your needs by using Funtoo Profiles. A quick introduction to profiles is included below -- consult the Funtoo Profiles page for more detailed information. There are five basic profile types: arch, build, subarch, flavors and mix-ins:

Sub-Profile Type	Description
arch	Typically x86-32bit or x86-64bit, this defines the processor type and support of your system. This is defined when your stage was built and should not be changed.
build	Defines whether your system is a current, stable or experimental build. current systems will have newer packages unmasked than stable systems. This is defined when your stage is built and is typically not changed.
subarch	Defines CPU optimizations for your system. The subarch is set at the time the stage3 is built, but can be changed later to better settings if necessary. Be sure to pick a setting that is compatible with your CPU.
flavor	Defines the general type of system, such as server or desktop, and will set default USE flags appropriate for your needs.
mix-ins	Defines various optional settings that you may be interested in enabling.

One arch, build and flavor must be set for each Funtoo Linux system, while mix-ins are optional and you can enable more than one if desired. Often, flavors and mix-ins inherit settings from other sub-profiles. Use epro show to view your current profile settings, in addition to any inheritance information:

(chroot) #  epro show

=== Enabled Profiles: ===

        arch:  x86-64bit
       build:  current
     subarch:  intel64-haswell
      flavor:  desktop
     mix-ins:  gnome


=== All inherited flavors from desktop flavor: ===

                     workstation (from desktop flavor)
                            core (from workstation flavor)
                         minimal (from core flavor)

=== All inherited mix-ins from desktop flavor: ===

                               X (from workstation flavor)
                           audio (from workstation flavor)
                             dvd (from workstation flavor)
                           media (from workstation flavor)
      mediadevice-audio-consumer (from media mix-in)
                mediadevice-base (from mediadevice-audio-consumer mix-in)
      mediadevice-video-consumer (from media mix-in)
                mediadevice-base (from mediadevice-video-consumer mix-in)
        mediaformat-audio-common (from media mix-in)
          mediaformat-gfx-common (from media mix-in)
        mediaformat-video-common (from media mix-in)
                  console-extras (from workstation flavor)
                           print (from desktop flavor)

Here are some basic examples of epro usage:

Description	Command
View available profiles. Enabled profiles will be highlighted in cyan. Directly enabled profiles will be in bold and have a * appended.	(chroot) # epro list
Change the system flavor.	(chroot) # epro flavor desktop
Add a mix-in.	(chroot) # epro mix-in +gnome

Next Steps

If you are brand new to Funtoo Linux and Gentoo Linux, please check out Funtoo Linux First Steps, which will help get you acquainted with your new system. We also have a category for our official documentation, which includes all docs that we officially maintain for installation and operation of Funtoo Linux.

We also have a number of pages dedicated to setting up your system. See First Steps for a list of these pages.

If your system did not boot correctly, see Installation Troubleshooting for steps you can take to resolve the problem.