The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Install/zh-cn
Install Funtoo Linux
介绍
这篇文章指导你如何在 PC 兼容机器上安装 Funtoo Linux 系统，我们将只进行包含基本系统配置的最小化安装。
如果你曾经有过 Gentoo Linux 的安装经验，你会发现很多步骤是相似的。但由于两者安装过程有些许不同，还是建议你通读本文。如果你是第一次安装 Gentoo 系 Linux 发行版，甚至第一次接触 Linux，也没有关系，我们会尽力让安装指南对于纯新手友好。
如果你在 ARM 架构的机器上安装 Funtoo Linux，请阅读 Funtoo Linux Installation on ARM 这篇文章，以了解不同之处。
安装步骤
下面介绍Funtoo Linux安装的基本步骤：
- 准备 Live CD
- 准备硬盘
- 创建 并 挂载 文件系统
- 安装 Stage 3 文件包
- Chroot 进入新系统
- 下载 Portage 源码树
- 系统配置 和 网络配置
- 安装 Linux 内核
- 安装系统引导程序
- 最后扫尾工作
- 重启系统
Live CD
为了安装 Funtoo Linux，你首先要使用一个基于 Linux 的 Live CD 或者 USB 介质启动电脑。我们推荐你使用 Gentoo 系的 System Rescue CD，因为它包含大量的工具，并且同时支持32位和64位的系统，你可以将它烧录在 CD/DVD 或者 USB 介质中，从这里下载它的 ISO 镜像文件：
- 下载镜像 osuosl.org
- 下载镜像 funtoo.org
无显示: System Rescue CD 以 UEFIgig方式启动时可能无法正确初始化显卡。 (请查阅 FL-2030.) 如果碰到此问题，请在System Rescue CD启动 GRUB 菜单时, 输入 e编辑 GRUB 启动行并添加insmod all_video 然后再启动系统。这个问题已经提交到System Rescue CD 的开发者。
如果使用老一些 版本 System Rescue CD进行启动， 在你打算安装64位g系统时，一定要在启动菜单选择rescue64 内核进行启动。默认情况下， System Rescue CD 以32位模式启动，并且能够自动识别64位CPU。
连接网络
如果已经成功启动System Rescue CD，请确认是否连接到Internet，因为安装 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
如果能够ping通外网 (检查64 bytes 信息,) 表示网络连接正常。 输入 Control-C停止ping程序。
如果以WiFi方式连接互联网，System Rescue CD 必须要运行图形界面。可以运行 startx 命令来启动图形界面:
root # startx
接下来，用 NetworkManager软件连接WIFI网络。 (软件图表在图形界面的任务栏的右下方) 然后，在图形界面下运行终端程序，确认电脑已经连接到互联网。
远程安装
当然，也可以通过网络以SSH远程登录到System Rescue CD 的系统进行安装操作。
如果你采取远程登录System Rescue CD 方式进行安装，先要确认系统已经联网，然后还需要给System Rescue CD设置一个root密码:
root # passwd New password: ******** Retype new password: ******** passwd: password updated successfully
设定完root密码后，还要知道System Rescue CD的当前IP地址。然后就可以通过 ssh 连接了。可以在System Rescue CD的终端上输入 ifconfig来获取需要连接的IP地址:
root # ifconfig
可以从某个本地LAN口上看到(包含字段 inet addr:) IP地址信息。该地址就是你通过远程主机连接到 System Rescue CD的IP地址。 例如，你可以通过你现有的Linux 或者MacOS等系统连接System Rescue CD的这样格式的1.2.3.4 IP地址:
(remote system) $ ssh root@1.2.3.4 Password: **********
如果用Microsoft Windows系统来进行远程操作，则需要另外的SSH 客户端，如果没有可以通过 PuTTY
下载。
在通过SSH远程登录 System Rescue CD 系统后，即可执行下一步安装操作。
准备硬盘分区
在本段，我们将了解Funtoo Linux系统如何从硬盘启动。"启动"，意思是在当打开电脑的电源开关后（比如桌面电脑，笔记本，服务器），进入Linux系统的过程。也可以理解为“启动”类似处理器先启动内置的固件，然后查找Linux内核再运行它，并由Linux内核识别系统硬件和启动这些硬件。
背景知识
作为Linux新手，可以忽略下面这段，选择哪一个?
以前, PC机只有一种启动模式。包括所有的个人电脑，服务器的启动固件都是 "PC BIOS,"并且所有的硬盘的主引导记录（MBR） 都位于硬盘的起始位置，PC BIOS 负责在主引导记录上读取分区信息，并查找和装载启动代码，并以此来启动Linux系统。
后来，又出现了新式系统引导固件 EFI （可扩展固件接口） 和 UEFI （统一可扩展固件接口），以及能够定义大于 2.2TB 容量的硬盘分区的 GPT 分区表。忽然之间，我们有了各种引导 Linux 系统的方式可以选择，之前的一招鲜吃遍天变得更加复杂了。
在这里我们先花点时间看看配置你的硬盘引导 Linux 又哪些方法可以选择。这份安装向导使用且通常推荐你使用老式的 BIOS 引导和 MBR 分区表。它们被几乎所有的硬件设备所支持。这种引导方式不会出问题。只要你的硬盘小于 2TB，它也不会妨碍你使用全部的硬盘空间。
然而，有时候老式办法不是最好的选择，如果你的硬盘容量大于 2TB，MBR 分区会阻碍你使用全部的硬盘空间。除此之外，有一些称作 “PC” 的系统不再支持 BIOS 启动，必须使用 UEFI ，所以这份安装指南也记载了如何用 UEFI 引导。
只要你没有特别的理由，我们都推荐你使用老式引导。这里我们用 GRUB 引导 Linux 内核，所以我们称这个方法为 BISOS + GRUB (MBR) 引导。这是在 PC 兼容平台上设置引导 Linux 的传统办法。
如果你需要用 UEFI 引导，我们不推荐使用 MBR 分区表，因为有些 UEFI 系统支持这个，有些不支持。我们推荐用 UEFI 引导 GRUB，由 GRUB 引导 Linux。我们称之为 UEFI + GRUB (GPT) 方法。
是的，还有更多的方法在 启动方法 页面。我们曾经推荐 BISO + GRUB(GPT) 但是这个并不被多少设备支持。
用哪种？
问题是——选哪种呢？ 下面就是答案
- 原则1——旧式引导：如果你能正常启动 System Rescue CD 并且它显示一个蓝色的初始菜单，就说明你是用 BIOS 启动的，以及你应该也能用 BISO 引导 Funtoo。所以，除非你有特殊原因需要用 UEFI，比如有大于 2.2TB 的硬盘，这时你要参考原则2来确认你的设备支持 UEFI。反之则使用 BIOS 引导。
- 原则2——新式引导：如果你能正常启动 System Rescue CD 并且显示黑白的启动菜单——恭喜，你的系统支持 UEFI 引导。可能你的系统也同时支持 BIOS，但是请先试 UEFI。你也可以花点时间研究研究配置
高级用户可能想到: 旧式和新式之间有什么明显差别？: 如果你使用老式的MBR分区，你的/boot分区将是ext2文件系统，并且你需要使用fdisk新建分区。如果你使用新式GPT分区和UEFI启动，你的/boot 分区将使用vfat文件系统，因为vfat是UEFI所能读取的，你将使用gdisk创建分区。GRUB的安装过程将稍微不同。这就是接下来可能会涉及到的内容，满足你的好奇心。
要通过新式的UEFI方式安装Funtoo Linux，你必须让System Rescue CD以UEFI方式启动。如果你成功在UEFI下启动sysresccd，你将看到一个黑白界面让你选择启动rescue cd的模式。或者你将看到带有黑色文本的蓝屏，将不能以UEFI启动，你也不能在安装过程中设置UEFI启动
有些主板貌似支持UEFI但请不要使用例如我的Gigabyte GA-990FXA-UD7 rev 1.1的Award BIOS可以启用让CD/DVD以UEFI启动。但并不能让硬盘以UEFI启动并安装Funtoo Linux。UEFI必须同时支持可移动介质（所以你可以以UEFI启动System Rescue CD）以及固定介质（这样你才能启动Funtoo Linux开始安装）。该BIOS的新版（rev 3.0）完全支持UEFI。这指出了第三个要点——了解你的硬件
老式（BIOS/MBR）方法
如果System Rescue CD启动后菜单是浅蓝色则应该使用BIOS启动。如果你想使用新式方法， 点击此处跳转。
首先，你需要找到正确的磁盘分区。尝试此命令验证/dev/sda是要分区的磁盘
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
现在，建议你删除一切现有磁盘上的MBR或者GPT分区表防止混淆。我们将使用sgdisk完成此操作：
这将使现有分区不可访问，建议事先备份。
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.
如果输出这样的结果，不必担心，命令已有效运行
*************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format in memory. ***************************************************************
现在我们将使用fdisk 创建MBR分区表和分区：
root # fdisk /dev/sda
在fdisk下按照以下步骤操作：
清除分区表：:
Command (m for help): o ↵
创建第一个分区： (boot):
Command (m for help): n ↵ Partition type (default p): ↵ Partition number (1-4, default 1): ↵ First sector: ↵ Last sector: +128M ↵
创建第二个分区： (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 ↵
创建根目录分区：
Command (m for help): n ↵ Partition type (default p): ↵ Partition number (3,4, default 3): ↵ First sector: ↵ Last sector: ↵
Verify the partition table:
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
Write the parition table to disk:
Command (m for help): w
Your new MBR partition table will now be written to your system disk.
You're done with partitioning! Now, jump over to Creating filesystems.
New-School (UEFI/GPT) Method
Use this method if you are interested in booting using UEFI, and if your System Rescue CD initial boot menu was black and white. If it was light blue, this method will not work.
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:
Create a new empty partition table (This will erase all data on the disk when saved):
Command: o ↵ This option deletes all partitions and creates a new protective MBR. Proceed? (Y/N): y ↵
Create Partition 1 (boot):
Command: n ↵ Partition Number: 1 ↵ First sector: ↵ Last sector: +500M ↵ Hex Code: EF00 ↵
Create Partition 2 (swap):
Command: n ↵ Partition Number: 2 ↵ First sector: ↵ Last sector: +4G ↵ Hex Code: 8200 ↵
Create Partition 3 (root):
Command: n ↵ Partition Number: 3 ↵ First sector: ↵ Last sector: ↵ (for rest of disk) Hex Code: ↵
Along the way, you can type "p" and hit Enter to view your current partition table. If you make a mistake, you can type "d" to delete an existing partition that you created. When you are satisfied with your partition setup, type "w" to write your configuration to disk:
Write Partition Table To Disk:
Command: w ↵ Do you want to proceed? (Y/N): Y ↵
The partition table will now be written to the disk and gdisk will close.
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/bootfilesystem,
/dev/sda2, which will be used for swap space, and
/dev/sda3, which will hold your root filesystem.
You can verify that the block devices above were correctly created by running the command lsblk.
Creating filesystems
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
Now, we need to create a root filesystem. This is where Funtoo Linux will live. We generally recommend ext4 or XFS root filesystems. If you're not sure, choose ext4. Here's how to create a root ext4 filesystem:
root # mkfs.ext4 /dev/sda3
...and here's how to create an XFS root filesystem, if you prefer to use XFS instead of 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.
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
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.
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. If you are using a virtualization technology to run Funtoo Linux, and your VM may migrate to different types of hardware, then it's recommended that you use a stage3 that is optimized for the oldest CPU instruction set that your VM will run on, or a generic image if it may run on both AMD and Intel processors.
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
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
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.
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
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
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. Note that it is normal for this file to be empty in Funtoo Linux, as many settings have been migrated to our enhanced profile system. |
/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.
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
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.
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
This is the "official" way to update your Funtoo Linux system. Above, we first update our Portage tree using git to grab the latest ebuilds (scripts), and then run an emerge command to update the world set of packages. The options specified tell emerge to:
a- show us what will be emerged, and ask us if we want to proceedu- 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
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:
See Funtoo Linux Kernels for a full list of kernels supported in Funtoo Linux. We recommend debian-sources for new users.
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.
Let's emerge our kernel:
(chroot) # emerge debian-sources
Once emerge completes, you'll have a brand new kernel and initramfs installed to /boot, plus kernel headers installed in /usr/src/linux, and you'll be ready to configure the boot loader to load these to boot your Funtoo Linux system.
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.
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/.
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 nmtui command (which has an easy-to-use console-based interface) to configure NetworkManager so that it will connect (and automatically reconnect, after reboot) to a Wi-Fi access point:
root # nmtui
For more information about NetworkManager, see the NetworkManager package page.
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.
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
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
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.