The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Install/zh-tw
Install Funtoo Linux
介紹
這份教學能幫助你在PC相容系統上以最簡單的步驟安裝Funtoo Linux。
如果你有Gentoo Linux的安裝經驗，你可能會對安裝流程感到十分熟悉，但是因為兩者之間仍有許多不同，所以還是建議你閱讀整份文件。如果你是第一次安裝Gentoo系發行版或甚至是第一次接觸Linux，我們都非常歡迎你的加入，我們會盡量讓純新手也能看懂這份教學。
如果你想在ARM架構上安裝Funtoo Linux，請參閱Funtoo Linux Installation on ARM 以了解不同之處
概要
安裝Funtoo的基本步驟:
Live CD
要安裝Funtoo Linux，首先你需要一個Linux的Live CD或是隨身碟來啟動你的電腦。我們推薦Gentoo系的System Rescue CD ，因為它附有很多工具而且同時支援32和64位元的系統。你可以將它燒錄進CD/DVD或是安裝在隨身碟裡。在這裡可以下載他們:
- 從 osuosl.org 下載
- 從 funtoo.org 下載
沒有畫面: 在使用UEFI開機時System Rescue CD 可能沒有正確初始化顯示卡 (參閱 FL-2030) 如果碰到這種情況，在System Rescue CD啟動進入GRUB目錄時按下 e 編輯GRUB啟動項目並加入insmod all_video 然後重新啟動。 這個Bug已經回報給System Rescue CD的開發者了。
如果你正在使用舊版本的System Rescue CD, 欲安裝64位元的系統，請確認你在啟動時選擇了rescue64 的內核，System Rescue CD在預設的情況下會以32位元模式啟動，但在最新的版本中 系統會嘗試自動偵測64位元的處理器。
連接網路
如果你已經成功啟動System Rescue CD務必確認是否已經連上網路，因為安裝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來啟動圖形使用者介面。
(譯註: 在新的英文頁面提供了不使用圖形介面的方法-nmtui，但受限於翻譯系統，我們目前無法翻譯，請自行前往英文頁面以了解更多)
root # startx
然後使用NetworkManager程式 (在工具列右下方的小圖示)來連接WiFi網路。接著開啟桌面環境裡的終端機來完成接下來的步驟。
遠端安裝
你也可以透過SSH來遠端登入System Rescue CD來從其他的電腦上安裝，這樣安裝Funtoo Linux可能更加的方便。
如果想要遠端安裝Funtoo，首先你需要去認System Rescue CD已經成功連上網路，然後你會需要設定一組System Rescue CD的root密碼。
root # passwd New password: ******** Retype new password: ******** passwd: password updated successfully
設定完密碼後，你還會需要知道System Rescue CD的ip位址來ssh它。輸入ifconfig來取得System Rescue CD的ip位址:
root # ifconfig
其中一個網路介面應該要擁有一組ip位址(包含字串inet addr:)，你可以從區域網路中的其他電腦遠端連接到System Rescue CD並使用現有的作業系統來完成安裝的工作。在像是MacOS或是Linux等你想用來遠端操作的系統上輸入(將1.2.3.4替換為System Rescue CD的ip位址):
(remote system) $ ssh root@1.2.3.4 Password: **********
如果想從Microsoft Windows連接 你需要下載一個SSH客戶端，例如:PuTTY。
在透過SSH登入System Rescue CD之後你就能遠端的執行下列的安裝步驟了。
準備硬碟
在這個項目中，我們將會學到好幾種Funtoo Linux從硬碟上啟動的方式，"Boot"代表著Linux在你按下電源鍵之後的啟動程序，你可以將"booting"想成一個透過韌體來尋找並啟動Linux內核的程序，再由內核來識別所有的硬體而後啟動系統。
背景知識
如果你從未接觸過Linux, 跳過這個章節也許能夠避免太多的困惑，該用哪個?
以前，要啟動PC相容的電腦只有一種方法，所有的個人電腦和伺服器都擁有一個標準的韌體"PC BIOS"我們所有的硬碟都在首個磁區使用"主開機紀錄(MBR)"，PC BIOS能夠識別出能夠加載LInux的啟動代碼以及磁碟的 多個分割區，而我們都喜歡這種方法!
後來出現了EFI和UEFI，一種全新的開機導引，以及能夠定義大於2.2TB硬碟的的GPT分割表。突然，我們就擁有了一大堆安裝和啟動Linux系統的選擇了，同時也將事情弄得更複雜。
接著我們花一些時間來了解一些能夠用來啟動Funtoo Linux的硬碟設置，這份教學採用並推薦使用MBR的舊式方法，在幾乎所有的電腦上都能運作，只要你的硬碟小於2TB他都不會影響到電腦的使用。
但是在某些狀況下舊式的方法並不是最好的，如果你有一顆大於2TB的硬碟，MBR分割會導致你無法完整使用整顆硬碟空間，還有一個情況是有一些新的主機板強迫你使用UEFI而不再支援舊式的BIOS開機，所以本篇文章也提供了UEFI的教學。
不過除非不得已，我們還是推薦你使用舊的方法。這份教學使用GRUB加載Linux，這種在PC相容機器上啟動Linux的傳統方法被叫做BIOS + GRUB (MBR)
如果你需要使用UEFI來開機，我們建議你完全不要使用MBR，只有少數的系統容許你使用MBR又使用UEFI，我們推薦使用UEFI來啟動GRUB來加載LInux，這種方法被稱為UEFI + GRUB (GPT)
當然還有其他的方法，這些方法我們收錄在Boot Methods頁面，我們曾經推薦使用BIOS + GRUB (GPT)，但他不再被大部分的硬體支援了。
該用哪個?
問題是該選哪一種呢? 這就是答案:
- 一、舊式方法
- 如果你能使用System Rescue CD開機，而且開機後能看到一個藍色選單，這表示System Rescue CD使用BIOS開機，也就是Funtoo也能使用舊式的方法來啟動，選擇舊式方法吧，除非你有像是有超過2.2TB的硬碟等等的理由，那麼看看方法二，也許你的電腦支援UEFI開機。
- 二、新式方法
- 如果你能正確啟動System Rescue CD而且看到了一個黑底白字的選單，恭喜，你的電腦支援UEFI開機，當然他也可能支援BIOS開機，但是你可以先試一試並花一點時間研究一下新的方法。
高手可能想問: 舊式和新式方法最大的不同是什麼: 如果你使用舊式的MBR分割，/boot 分割區會採用ext2檔案系統，而要建立新的MBR分割區需要使用的工具是fdisk，如果你使用的是新式的GPT分割，/boot分割區會採用vfat檔案系統，這樣UEFI才能正確識別，而要創建新的GPT分割區則需要使用gdisk，GRUB的安裝過程也會有些許的不同，接下來會碰到的差異大概就只有這些，希望能滿足你的好奇心。
如果要透過新的UEFI方法來安裝Funtoo Linux，首先必須要使用UEFI來啟動System Rescue CD，如果成功了，你會看到一個黑底白字的選單來選擇你想啟動的模式，但如果是一個藍底黑字的選單，這表示你無法使用UEFI來完成接下來的安裝程序。
某些主機板可能支援UEFI，某些則不，事前做些研究，舉例來說 我的Gigabyte GA-990FXA-UD7 rev 1.1主機板裡的Award BIOS可以透過UEFI來啟動CD/DVD，但這不表示你能透過UEFI從硬碟中啟動Funtoo Linux ，UEFI必須要同時支援移動式硬體(這樣才能啟動System Rescue CD)和固定式硬體(才能從硬碟中啟動Funtoo)， 結果只有更新的版本(rev 3.0)才完整的支援UEFI啟動。這也點出了第三個要點，完全了解你的硬體。
舊式方法 (BIOS/MBR)
這方法適用於使用BIOS來開機的情況，而使用BIOS啟動電腦你會看到一個藍色的選單，如果你想使用新式方法啟動 ， 點擊轉跳到UEFI/GPT章節
首先，你需要找到正確的硬碟來進行分割，使用這個指令來確認/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分割表，否則BIOS在啟動時可能會發生一點錯誤，我們使用sgdisk來完成這項工作:Template:注意
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 ↵
建立分割區1: (boot)
Command (m for help): n ↵ Partition type (default p): ↵ Partition number (1-4, default 1): ↵ First sector: ↵ Last sector: +128M ↵
建立分割區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 ↵
建立root分割區:
Command (m for help): n ↵ Partition type (default p): ↵ Partition number (3,4, default 3): ↵ First sector: ↵ Last sector: ↵
驗證分割表:
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
將分割表寫入硬碟:
Command (m for help): w
全新的MBR分割表將會被寫入你的系統硬碟中。
你已經完成了硬碟分割了! 現在轉跳到建立檔案系統。
新式方法 (UEFI/GPT)
如果你對使用UEFI來啟動很有興趣的話選擇這個方法而System Rescue CD的開機選單會是黑底白字的，如果出現的是藍色的選單，這個方法則不適用於你的電腦。
請依照下列的指示使用gdisk來建立GPT分割區，雖然預設的大小就是用於大部分的使用者，但是選擇適當的分割區大小仍然很重要。啟動 gdisk:
root # gdisk /dev/sda
在gdisk中依照下列指示操作:
建立一個全新的分割表 (這在寫入硬碟後將會清除硬碟上的所有資料):
Command: o ↵ This option deletes all partitions and creates a new protective MBR. Proceed? (Y/N): y ↵
建立分割區1: (boot)
Command: n ↵ Partition Number: 1 ↵ First sector: ↵ Last sector: +500M ↵ Hex Code: EF00 ↵
建立分割區2 (swap):
Command: n ↵ Partition Number: 2 ↵ First sector: ↵ Last sector: +4G ↵ Hex Code: 8200 ↵
建立分割區3 (root):
Command: n ↵ Partition Number: 3 ↵ First sector: ↵ Last sector: ↵ (for rest of disk) Hex Code: ↵
運行的過程中可以輸入"p"接著按下Enter來查看當前的分割表，如果有任何錯誤隨時能輸入"d"來刪除已經建立好的分割區，在完成所有步驟之後，輸入"w"將變更寫入硬碟之中:
將分割表寫入硬碟:
Command: w ↵ Do you want to proceed? (Y/N): Y ↵
分割表將被寫入硬碟，而gdisk會關閉。
現在GPT/GUID分割區已經被建立好了，並且在Linux中會以"block devices"的形式出現。
/dev/sda1將被作為/boot分割區
/dev/sda2將被作為置換空間(swap space)
/dev/sda3則是成為/root分割
你可以透過lsblk指令來查看所有的分割區是否正確
建立檔案系統
這個章節同時適用於"BIOS"和"UEFI"，別不小心跳過他了!
在你新建立的分割區能派上用場之前，這些前一個步驟了產物需要被使用"檔案相關資料"初始化，這個步驟又被稱為"建立檔案系統"，在檔案系統被建立之後，他們才能被掛載，然後用來儲存檔案。
簡單來說，如果你正在使用舊式的MBR分割區，那麼在/dev/sda1上建立一個ext2檔案系統:
root # mkfs.ext2 /dev/sda1
如果你為了使用UEFI而使用新式的GPT分割區，則在/dev/sda1上建立vfat檔案系統，這樣UEFI才有辦法讀取。
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.