The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Funtoo Linux Installation
Introduction
This document was written to help you install Funtoo Linux as concisely as possible, with a minimum number of distracting options regarding system configuration.
These docs assume you have a "PC compatible" computer system with a standard PC BIOS. Many new computers support UEFI for booting, which is a new firmware interface that frequently replaces the older MBR-based BIOS. If you have a system with UEFI, you will want to use this documentation along with the UEFI Install Guide, which will augment these instructions and explain how to get your system to boot. You may need to change your PC BIOS settings to enable or disable UEFI booting. The UEFI Install Guide has more information on this, and steps on how to determine if your system supports UEFI.
We also offer a ZFS Install Guide, which augment the instructions on this page for those who want to install Funtoo Linux on ZFS. If you are installing Funtoo Linux on ARM architecture, please see Funtoo Linux Installation on ARM for notable differences regarding ARM support. An experimental Funtoo Linux build also exists for SPARC platforms. See Funtoo Linux Installation on SPARC.
New F2FS Install Guide is in progress which will augment the instructions on this page for those who want to install Funtoo Linux on F2FS.
If you've had previous experience installing Gentoo Linux then a lot of steps will be familiar, but you should still read through as there are a few differences.
Installation Overview
This is a basic overview of the Funtoo installation process:
- Download and boot the live CD of your choice.
- Prepare your disk.
- Create and mount filesystems.
- Install the Funtoo stage tarball of your choice.
- Chroot into your new system.
- Download the Portage tree.
- Configure your system and network.
- Install a kernel.
- Install a bootloader.
- Complete final steps.
- Reboot and enjoy.
Live CD
Funtoo doesn't provide an "official" Funtoo Live CD, but there are plenty of good ones out there to choose from. A great choice is the Gentoo-based System Rescue CD as it contains lots of tools and utilities and supports both 32-bit and 64-bit systems. For a generation 2 Hyper-V system, the Ubuntu desktop install DVD as of version 14.04.1 works well enough. Gentoo CDs don't support EFI boot, and the System Rescue CD lacks appropriate graphics support for Hyper-V as of version 4.4.0.
It is also possible to install Funtoo Linux using many other Linux-based live CDs. Generally, any modern bootable Linux live CD or live USB media will work. See requirements for an overview of what the Live Media must provide to allow a problem-free install of Funtoo Linux.
To begin a Funtoo Linux installation, download System Rescue CD from:
- http://build.funtoo.org - Master mirror
- http://ftp.osuosl.org/pub/funtoo - US Funtoo Linux Mirror
- http://ftp.heanet.ie/mirrors/funtoo -European Funtoo Linux mirror
Or, use your preferred live media. Insert it into your disc drive, and boot from it. If using an older version of System Rescue CD, be sure to select the rescue64
kernel at the boot menu if you are installing a 64-bit system. By default, System Rescue CD used to boot in 32-bit mode though the latest version attempts to automatically detect 64-bit processors.
Prepare Hard Disk
Partitions
Funtoo Linux fully supports traditional MBR partitions, as well as newer GPT/GUID partition formats. See below to determine which partitioning scheme to use:
MBR Partitions
- Recommended if your system disk is <=2TB in size
- Legacy, DOS partitioning scheme
- Only 4 primary partitions per disk; after that, you must use "logical" partitions
- Does not support 2 TB+ disks for booting
- Compatible with certain problematic systems (such as the HP ProBook 4520)
- Dual-boot with Windows for BIOS systems (Windows handle GPT only on true EFI systems, whatever version it is)
- Multiple boot loader options, e.g. GRUB 2, GRUB Legacy, lilo
Due to the fact that it is more widely supported on PC hardware, it is best to use MBR partitions if possible.
GPT Partitions
- Recommended if your disk is >2TB in size
- Newer format for Linux systems
- Supports 2 TB+ hard drives for booting
- Supports hundreds of partitions per disk of any size
- Requires legacy BIOS boot partition (~32 MB) to be created if system does not use EFI
- Requires bootloader with support for GPT such as GRUB 2, EXTLINUX, or a patched version of GRUB Legacy
If you have a system disk that is 2TB or greater and want to use the space beyond 2TB, you must partition using the GPT/GUID format. Otherwise, MBR is recommended as the most reliable boot method.
Filesystem Resources
Advanced users may be interested in the following topics:
- GUID Booting Guide
- LVM Install Guide
- Rootfs over encrypted lvm
- Rootfs over encrypted lvm over raid-1 on GPT
- NEW! ZFS Install Guide (Also contains instructions for Rootfs over Encrypted ZFS!)
Partitioning Recommendations
Below are our partitioning recommendations in table form. For MBR-based partitions, use the MBR Block Device and MBR code columns with fdisk
. For GPT-based partitions, use the GPT Block Device and GPT Code columns with gdisk
:
Partition | Size | MBR Block Device (fdisk ) |
GPT Block Device (gdisk ) |
Filesystem | MBR Code | GPT Code |
---|---|---|---|---|---|---|
/boot |
512 MB | /dev/sda1 |
/dev/sda1 |
ext2 | 83 | 8300 |
GRUB boot loader partition | 1 MB | not required for MBR | /dev/sda2 |
For GPT/GUID only, skip for MBR - no filesystem. | N/A | EF02 |
swap | 2x RAM for low-memory systems and production servers; otherwise 2GB. | /dev/sda2 |
/dev/sda3 |
swap (default) | 82 | 8200 |
/ (root) |
Rest of the disk, minimum of 10GB. Note: to compile the debian-sources kernel, as described later on this page, requires a minimum of 14GB free space in /tmp ; consider a minimum of 20GB in this case. |
/dev/sda3 |
/dev/sda4 |
XFS recommended, alternatively ext4 | 83 | 8300 |
/home (optional) |
User storage and media. Typically most of the disk. | /dev/sda4 (if created) |
/dev/sda5 (if created) |
XFS recommended, alternatively ext4 | 83 | 8300 |
LVM (optional) | If you want to create an LVM volume. | /dev/sda4 (PV, if created) |
/dev/sda5 (PV, if created) |
LVM PV | 8E | 8E00 |
Partitioning Using fdisk (MBR)
If you need to create a GPT partition table, see Partitioning using gdisk or Partitioning using parted.
These install instructions assume you are installing Funtoo Linux to an hard disk using Master Boot Record partition tables (MBR). If you are installing Funtoo Linux on a machine where another OS is installed, there is an existing Linux distribution on your system that you want to keep or any other scenario (such as differing swap size requirements), then you will need to adapt these instructions to suit your needs.
fdisk
is the tool used to create an MBR partition table. MBR is well-supported on PCs and is recommended if your system disk is 2TB or smaller.
Preparation
First, it's a good idea to make sure that you've found the correct hard disk to partition. Try this command and verify that /dev/sda
is the disk that you want to partition:
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
Now, it's recommended that you erase any existing MBR or GPT partition tables on the disk, which could confuse the system's BIOS at boot time. We do this using sgdisk
:
This will make any existing partitions inaccessible! You are strongly cautioned and advised to backup any critical data before proceeding.
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.
This output is also nothing to worry about, as the command still succeded:
*************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format in memory. ***************************************************************
Partitioning
Now we will use fdisk
to create the MBR partition table and partitions:
root # fdisk /dev/sda
Within fdisk
, follow these steps:
Empty the partition table:
Command (m for help): o ↵
Create Partition 1 (boot):
Command (m for help): n ↵ Partition type (default p): ↵ Partition number (1-4, default 1): ↵ First sector: ↵ Last sector: +128M ↵
Create Partition 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 ↵
Create the root partition:
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.
Creating filesystems
Before your newly-created partitions can be used, the block devices 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.
You will not create a filesystem on your swap partition, but will initialize it using the mkswap
command so that it can be used as disk-based virtual memory. Then we'll run the swapon
command to make your newly-initialized swap space active within the live CD environment, in case it is needed during the rest of the install process.
Note that we will not create a filesystem on the GRUB boot loader partition, as GRUB writes binary data directly to that partition when the boot loader is installed, which we'll do later.
You can see the commands you will need to type below. Like the rest of this document, it assumes that you are using a GPT partitioning scheme. If you are using MBR, your root filesystem will likely be created on /dev/sda3
instead and you will need to adjust the target block devices. If you are following our recommendations, then simply do this:
We generally recommend XFS for root filesystems, although ext4 is also a good choice. This tutorial assumes the use of XFS. If you want to use ext4, then be sure that your /etc/fstab
file reflects this.
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.
To use ext4 as your root filesystem:
root # mke2fs -t ext2 /dev/sda1 root # mkfs.ext4 /dev/sda3 root # mkswap /dev/sda2 root # swapon /dev/sda2
To use XFS as your root filesystem:
root # mke2fs -t ext2 /dev/sda1 root # mkfs.xfs /dev/sda3 root # mkswap /dev/sda2 root # swapon /dev/sda2
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
<translate>
Chroot into Funtoo
To set up your Funtoo Linux system, we need to "enter into" it before we boot. If you are using the Funtoo Linux LiveCD, this can be easily done with the fchroot
command:
root # fchroot /mnt/funtoo fchroot #
The fchroot
command will take care of all necessary steps to enter into your new Funtoo Linux system, as well as clean up things when you exit the fchroot by typing
exit
or ctrl-D
.
If you are using another LiveCD or USB media to install Funtoo, you can manually chroot by using the following set of commands:
root # cd /mnt/funtoo root # mount --rbind /proc proc root # mount --rbind /sys sys root # mount --rbind /dev dev root # cp /etc/resolv.conf /mnt/funtoo/etc/ root # chroot . /bin/su --login chroot #
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 to 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 your live CD.
Test internet name resolution from within the chroot:
chroot # ping -c 5 google.com
If you can't ping, make sure that /etc/resolv.conf
specifies a valid IP address for a reachable nameserver in its nameserver
setting.
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. </translate>
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, change SYNC
variable in /etc/make.conf
:
SYNC="https://github.com/funtoo/ports-2012.git"
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 temproarily 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.
Configuring and installing the Linux kernel
Now it's time to build and install a Linux kernel, which is the heart of any Funtoo Linux system. The kernel is loaded by the boot loader, and interfaces directly with your system's hardware, and allows regular (userspace) programs to run.
A kernel must be configured properly for your system's hardware, so that it supports your hard drives, file systems, network cards, and so on. More experienced Linux users can choose to install kernel sources and configure and install their own kernel. If you don't know how to do this, we provide ebuilds that will automatically build a "univeral" kernel, modules and initramfs for booting your system that supports all hardware. This is an extremely simple way of building a kernel that will get your system booted.
What is our goal? To build a kernel that will recognize all the hardware in your system necessary for booting, so that you will be greeted by a friendly login prompt after installation is complete. These instructions will guide you through the process of installing a kernel the "easy" way -- without requiring user configuration, by using a "universal" kernel.
Package Sets
Before we install a kernel, we're going to cover a feature of Portage called package sets. Portage, the package manager/ports system for Funtoo Linux, will keep track of system packages as well as packages you have installed by calling emerge
directly. These packages that are part of the base system are considered part of the "system" package set, while packages that you have installed by typing them on the command line (such as "gnome" in emerge gnome
) will be added to the "world" package set. This provides an easy way to update your entire system.
However, sometimes it's nice to be able to update the kernel all by itself, or leave a kernel update out of your regular whole system update. To do this, we will create a new package set called "kernel".
Kernel Package Set
To create the kernel package set, perform the following steps:
(chroot) # mkdir /etc/portage/sets (chroot) # echo sys-kernel/debian-sources > /etc/portage/sets/kernel
Now, we'll want to set a USE variable to tell debian-sources
to build a "universal" kernel and initramfs for us, to take the guess-work out of getting Funtoo Linux booted. To do this, we're going to set the binary
USE variable for debian-sources
, as follows:
(chroot) # echo "sys-kernel/debian-sources binary" >> /etc/portage/package.use
If USE variables are new to you, you'll be getting a lot more familiar with them as you use Funtoo Linux. At their essence, they are "switches" that you can set to configure options that can be built in to various packages. They're used to customize your Funtoo Linux system to meet your exact needs. We added support for a binary
USE flag to the debian-sources
ebuilds, as well as a few other of our kernel ebuilds, to make it easier for new users to get Funtoo Linux up and running.
Now, when we just want to update our system's packages, we'll type emerge -auDN @world
, and it will update our world set, leaving out the kernel. Likewise, when we just want to update our kernel, we'll type emerge -au @kernel
, and it will update our kernel, leaving out the world set.
Building the Kernel
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 @kernel
Note that while use of the binary
USE flag makes installing a working kernel extremely simple, it is one part of Funtoo Linux that takes a very long time to build from source, because it is building a kernel that supports all hardware that Linux supports! So, get the build started, and then let your machine compile. Slower machines can take up to several hours to build the kernel, and you'll want to make sure that you've set MAKEOPTS
in /etc/make.conf
to the number of processing cores/threads (plus one) in your system before starting to build it as quickly as possible -- see the /etc/make.conf section if you forgot to do this.
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.
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.
Installing a Bootloader
An alternate boot loader called extlinux can be used instead of GRUB if you desire. See the extlinux Guide for information on how to do this.
Installing Grub
The boot loader is responsible for loading the kernel from disk when your computer boots. For new installations, GRUB 2 and Funtoo's boot-update tool should be used as a boot loader. GRUB supports both GPT/GUID and legacy MBR partitioning schemes.
To use this recommended boot method, first emerge boot-update
. This will also cause grub-2
to be merged, since it is a dependency of boot-update
. (You may need to adjust GRUB_PLATFORMS
if you are on a UEFI system. See UEFI Install Guide).
(chroot) # emerge boot-update
Then, edit /etc/boot.conf
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:
boot { generate grub default "Funtoo Linux genkernel" timeout 3 } "Funtoo Linux" { kernel bzImage[-v] # params += nomodeset } "Funtoo Linux genkernel" { # if you use bliss-kernel package # you should change string # kernel kernel[-v] # to # kernel kernel/[-v]/kernel[-v] kernel kernel[-v] initrd initramfs[-v] params += real_root=auto # params += nomodeset }
If you use bliss-kernel, your /etc/boot.conf
should look like:
boot { generate grub default "Funtoo Linux genkernel" timeout 3 } "Funtoo Linux" { kernel bzImage[-v] # params += nomodeset } "Funtoo Linux genkernel" { kernel kernels/[-v]/kernel[-v] initrd initramfs[-v] params += real_root=auto # params += nomodeset }
Please read man boot.conf
for further details.
Running grub-install and boot-update
Finally, we will need to actually install the GRUB boot loader to your disk, and also run boot-update
which will generate your boot loader configuration file:
(chroot) # grub-install --no-floppy /dev/sda (chroot) # boot-update
Now you need to update your boot loader configuration file:
(chroot) # boot-update
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, so your changes are applied on next boot.
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
Using NetworkManager
For laptop/mobile systems where you will be using Wi-Fi and connecting to various networks, NetworkManager is strongly recommended. The Funtoo version of NetworkManager is fully functional even from the command-line, so you can use it even without X or without the Network Manager applet. Here are the steps involved in setting up NetworkManager:
(chroot) # emerge linux-firmware (chroot) # emerge networkmanager (chroot) # rc-update add NetworkManager default
Above, we installed linux-firmware which contains a complete collection of available firmware for many hardware devices including Wi-Fi adapters, plus NetworkManager to manage our network connection. Then we added NetworkManager to the default
runlevel so it will start when Funtoo Linux boots.
After you reboot into Funtoo Linux, you will be able to add a Wi-Fi connection this way:
root # addwifi -S wpa -K 'wifipassword' mywifinetwork
The addwifi
command is used to configure and connect to a WPA/WPA2 Wi-Fi network named mywifinetwork
with the password wifipassword
. This network configuration entry is stored in /etc/NetworkManager/system-connections
so that it will be remembered in the future. You should only need to enter this command once for each Wi-Fi network you connect to.
Using wpa_supplicant
If for some reason you don't want to use a tool such as NetworkManager or wicd
, you can use wpa_supplicant for wireless network connections.
First, emerge wpa_supplicant:
(chroot) # emerge -a wpa_supplicant
Now, edit the wpa_supplicant configuration file, located at /etc/wpa_supplicant.conf. The syntax is very easy:
network={ ssid="MyWifiName" psk="lol42-wifi" } network={ ssid="Other Network" psk="6d96270004515a0486bb7f76196a72b40c55a47f" }
You will need to add both wpa_supplicant
and dhcpcd
to the default runlevel. wpa_supplicant
will connect to your access point, and dhcpcd
will acquire an IP address via DHCP:
(chroot) # rc-update add dhcpcd default (chroot) # rc-update add wpa_supplicant default
Desktop (Wired Ethernet)
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.
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.
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 -l 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.
Funtoo profiles are used to define defaults for Portage specific to your needs. There are 4 basic profile types: arch, build, flavor, and mix-ins:
- arch
- typically
x86-32bit
orx86-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
orexperimental
build.current
systems will have newer packages unmasked thanstable
systems. - flavor
- defines the general type of system, such as
server
ordesktop
, and will set default USE flags appropriate for your needs. - mix-ins
- define 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.
Remember that profiles can often be inherited. For example, the desktop
flavor inherits the workstation
flavor settings, which in turn inherits the X
and audio
mix-ins. You can view this by using eselect:
(chroot) # eselect profile show
Currently set profiles:
arch: gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit
build: gentoo:funtoo/1.0/linux-gnu/build/current
flavor: gentoo:funtoo/1.0/linux-gnu/flavor/desktop
mix-ins: gentoo:funtoo/1.0/linux-gnu/mix-ins/kde
Automatically enabled profiles:
mix-ins: gentoo:funtoo/1.0/linux-gnu/mix-ins/print
mix-ins: gentoo:funtoo/1.0/linux-gnu/mix-ins/X
mix-ins: gentoo:funtoo/1.0/linux-gnu/mix-ins/audio
mix-ins: gentoo:funtoo/1.0/linux-gnu/mix-ins/dvd
mix-ins: gentoo:funtoo/1.0/linux-gnu/mix-ins/media
mix-ins: gentoo:funtoo/1.0/linux-gnu/mix-ins/console-extras
To view installed profiles:
(chroot) # eselect profile list
To change the profile flavor:
(chroot) # eselect profile set-flavor 7
To add a mix-in:
(chroot) # eselect profile add 10
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, which you can find below. If you are interested in adding a page to this list, add it to the "First Steps" MediaWiki category.
{{#ask: | format=ul }}
If your system did not boot correctly, see Installation Troubleshooting for steps you can take to resolve the problem.