Note

The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.

Difference between revisions of "Install/pl"

From Funtoo
Jump to navigation Jump to search
(Created page with "Żeby zainstalować system Funtoo Linux, musisz uruchomić komputer za pomocą dystrybucji Linuxowej typu Live CD. Rekomendowanym systemem jest dystrybucja bazująca na Gentoo...")
(Updating to match new version of source page)
Tag: Replaced
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
<languages/>
<div lang="en" dir="ltr" class="mw-content-ltr">
{{Note|Translators: Thank you for your help! Please use the {{Install|section-by-section guide}} as the basis for your translations. Thanks again!}}
{{DISPLAYTITLE:Funtoo Linux Installation Guide}}
</div>
{{#widget:AddThis}}
{{#widget:AddThis}}
= Install Funtoo Linux =
{{translated_subpage|Install|Introduction}}
__NOTITLE__
{{translated_subpage|Install|Download LiveCD}}
<languages/>
{{translated_subpage|Install|Prepare Disk}}
{{Announce|To help us translate this documentation, {{CreateAccount}}, log in to the wiki. Then go to Actions -> Translate in the menu, or click the "Translate this page" link, above. You will be able to select small parts of the install docs and translate these parts to your native language.}}
{{translated_subpage|Install|MBR Partitioning}}
== Wprowadzenie == 
{{translated_subpage|Install|GPT Partitioning}}
{{translated_subpage|Install|Creating Filesystems}}
{{translated_subpage|Install|Mounting Filesystems}}
{{translated_subpage|Install|Setting the Date}}
{{translated_subpage|Install|Download and Extract Stage3}}
{{translated_subpage|Install|Chroot}}
{{translated_subpage|Install|Download Portage Tree}}
{{translated_subpage|Install|Configuration Files}}
{{translated_subpage|Install|Introducing Portage}}
{{translated_subpage|Install|Kernel}}
{{translated_subpage|Install|Bootloader}}
{{translated_subpage|Install|Network}}
{{translated_subpage|Install|Finishing}}
{{translated_subpage|Install|Profiles}}
{{translated_subpage|Install|Done}}


Ten dokument został przygotowany aby pomóc Ci w instalacji systemu Funtoo Linux na platformie kompatybilnej z PC. Konfiguracja systemu została ograniczona do minimum.
[[Category:HOWTO]]
 
[[Category:Install]]
Jeśli masz doświadczenie w instalacji dystrybucji Gentoo Linux wiele opisanych kroków będzie Ci znajomych. Mimo wszystko jest kilka różnic i dlatego przeczytaj dokument w całości. Jeśli nie masz doświadczenia w instalacji systemu bazującego na Getnoo lub dopiero zaznajamiasz się z systemem Linux - Witaj! Poniższa instrukcja została przygotowana aby była zrozumiała dla nowych użytkowników.
[[Category:Official Documentation]]
 
{{Note| Jeśli instalujesz Funtoo Linux na architekturze ARM, zajrzyj do dokumentu [[Funtoo Linux Installation on ARM]] gdzie zostały przedstawione różnice dotyczące wsparacia ARM. }}
 
== Przegląd kroków instalacji ==
 
Proces instalacji systemu Funtoo składa się z:
 
# Pobranie oraz uruchomienie systemu z live CD.
# Przygotowanie dysku.
# Utworzenie i podmontowanie systemu plików.
# Rozpakowanie archiwum Stage 3.
# Chrootowanie do nowego systemu.
# Pobranie drzewa Portage.
# Konfiguracja sieci.
# Instalacja kernela.
# Instalacja bootloadera.
# Finalizacja instalacji.
# Restart systemu.
 
=== Live CD ===
 
Żeby zainstalować system Funtoo Linux, musisz uruchomić komputer za pomocą dystrybucji Linuxowej typu Live CD. Rekomendowanym systemem jest dystrybucja bazująca na Gentoo [http://www.sysresccd.org/ System Rescue CD]. Wspiera ona systemy 32 i 64 bitowe i zawiera dużo przydatnych narzędzi. Po pobraniu można ją wypalić na CD/DVD lub zainstalować na USB. Dystrybucje można pobrać:
 
* Download from '''[http://ftp.osuosl.org/pub/funtoo/distfiles/sysresccd/sysresccd-4.7.0_zfs_0.6.5.4.iso osuosl.org]'''
* Download from '''[http://build.funtoo.org/distfiles/sysresccd/sysresccd-4.7.0_zfs_0.6.5.4.iso funtoo.org]'''
 
{{Important|'''NO VIDEO''': System Rescue CD may not initialize video properly when booting from UEFI (See {{bug|FL-2030}}.) In this case, at the System Rescue CD GRUB menu, press {{c|e}} to edit the menu entry and add a GRUB boot line that reads {{c|insmod all_video}} and then boot. This bug has been reported upstream to System Rescue CD developers.}}
 
{{Note|If using an older version of System Rescue CD, '''be sure to select the <code>rescue64</code> 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.}}
 
==== Network Access ====
 
Once you have booted System Rescue CD, see if you have Internet access. Internet access is required for installing Funtoo Linux:
 
<console>
# ##i##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
</console>
 
If the ping is successful (you see <code>64 bytes</code> messages as above,) then your Network is set up. Hit Control-C to stop the ping.
 
If you need to set up a WiFi connection for Internet access, then this needs to be done using the System Rescue CD graphical environment. Run <code>startx</code> to start a graphical session:
<console>
# ##i##startx
</console>
 
[[File:NetworkManagerIcon.PNG|left|caption]]
 
Then, use the NetworkManager applet (icon in lower right of graphical session, in taskbar) to connect to a WiFi network of your choice. Next, open a terminal inside your graphical environment, and you should be able to use the terminal to complete the rest of the steps.
 
==== Remote Install ====
 
Alternatively, you can log into System Rescue CD over the network via SSH to perform the install from another computer, and this may be more convenient way to install Funtoo Linux.
 
If you'd like to complete the install remotely, here's how. First, you will need to ensure that System Rescue CD has a functioning network connection. Then, you will need to set a root password for System Rescue CD:
{{console|body=
###i## passwd
New password: ##i##********
Retype new password: ##i##********
passwd: password updated successfully
}}
Once you have typed in a password, you will now need to determine the IP address of System Rescue CD, and then you can use {{c|ssh}} to connect to it. To determine the IP address currently being used by System Rescue CD, type {{c|ifconfig}}:
 
{{console|body=
###i## ifconfig
}}
One of the interfaces should have an IP address (listed as {{c|inet addr:}}) from your LAN. You can then connect remotely, from another system on your LAN, to System Rescue CD, and perform steps from the comfort of an existing OS. On your remote system, type the following, replacing {{c|1.2.3.4}} with the IP address of System Rescue CD. Connecting from an existing Linux or MacOS system would look something like this:
 
{{console|body=
(remote system) $ ##i##ssh root@1.2.3.4
Password: ##i##**********}}
{{Note|If you'd like to connect remotely from an existing Microsoft Windows system, you'll need to download an SSH client for Windows, such as [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY].}}
 
After you've logged in via SSH, you're now connected remotely to System Rescue CD and can perform the installation steps.
 
=== Prepare Hard Disk ===
 
In this section, we'll learn about the different ways that Funtoo Linux can boot from a hard disk. By "boot", we mean the process by which Linux starts after you press the power button on your desktop, laptop or server. You can think of "booting" as a process that starts with your computer's firmware (built-in software) running, and then "finding" the Linux kernel and running it. The Linux kernel then takes over, identifies all your hardware, and starts.
 
==== Background ====
 
{{Note|If you are an absolute beginner to Linux, you may be less confused if you skip to the next section, [[#Which to Use?|Which to Use?]]}}
 
In earlier times, there was only one way to boot a PC-compatible computer. All of our desktops and servers had standard firmware called the "PC BIOS," all our hard drives used Master Boot Records at the beginning of the disk, where the PC BIOS would "look" to find boot loader code which would in turn load Linux, and our hard drives were partitioned into different regions using the standard MBR partition scheme. That was just how it was done. And we liked it that way!
 
Then, along came EFI and UEFI, which are new-style firmware designed to boot systems, along with GPT partition tables to define disk partitions on disks larger than 2.2TB. All of the sudden, we had a variety of options for installing and booting Linux systems, turning what once was a one-method-fits-all approach into something a lot more complex.
 
Let's take a moment to review the options available to you for configuring a hard drive to boot Funtoo Linux. This Install Guide uses, and recommends, the old-school method of BIOS booting and using an MBR. It works and (except for rare cases) is universally supported. There's nothing wrong with it. If your system disk is 2TB or smaller in size, it won't prevent you from using all of your disk's capacity, either.
 
But, there are some situations where the old-school method isn't optimal. If you have a system disk >2TB in size, then MBR partitions won't allow you to access all your storage. So that's one reason. Another reason is that there are some so-called "PC" systems out there that don't support BIOS booting anymore, and force you to use UEFI to boot. So, out of compassion for people who fall into this predicament, this Install Guide documents UEFI booting too.
 
Our recommendation is still to go old-school unless you have reason not to. The boot loader we will be using to load the Linux kernel in this guide is called GRUB, so we call this method the '''BIOS + GRUB (MBR)''' method. It's the traditional method of setting up a PC-compatible system to boot Linux.
 
If you need to use UEFI to boot, we recommend not using the MBR at all for booting, as some systems support this, but others don't. Instead, we recommend using UEFI to boot GRUB, which in turn will load Linux. We refer to this method as the '''UEFI + GRUB (GPT)''' method.
 
And yes, there are even more methods, some of which are documented on the [[Boot Methods]] page. We used to recommend a '''BIOS + GRUB (GPT)''' method but it is not consistently supported across a wide variety of hardware.
 
==== Which to Use? ====
 
'''The big question is -- which boot method should you use?''' Here's how to tell.
 
;Principle 1 - Old School: If you can reliably boot System Rescue CD and it shows you an initial light blue menu, you are booting the CD using the BIOS, and it's likely that you can thus boot Funtoo Linux using the BIOS. So, go old-school and use BIOS booting, ''unless'' you have some reason to use UEFI, such as having a >2.2TB system disk. In that case, see Principle 2, as your system may also support UEFI booting.
 
;Principle 2 - New School: If you can reliably boot System Rescue CD and it shows you an initial black and white menu -- congratulations, your system is configured to support UEFI booting. This means that you are ready to install Funtoo Linux to boot via UEFI. Your system may still support BIOS booting, but just be trying UEFI first. You can poke around in your BIOS boot configuration and play with this.
 
{{Note|'''Advanced Users May Wonder:''' What's the Big Difference between Old School and New School?: Here's the deal. If you go with old-school MBR partitions, your {{f|/boot}} partition will be an ext2 filesystem, and you'll use {{c|fdisk}} to create your MBR partitions. If you go with new-school GPT partitions and UEFI booting, your {{f|/boot}} partition will be a vfat filesystem, because this is what UEFI is able to read, and you will use {{c|gdisk}} to create your GPT partitions. And you'll install GRUB a bit differently. That's about all it comes down to, in case you were curious.}}
 
To install Funtoo Linux to boot via the New School UEFI method, you must boot System Rescue CD using UEFI. If you successfully boot sysresccd with UEFI, you will see an initial black and white screen to select the mode in which you will boot system rescue cd. Otherwise, if you see a blue screen with black text, UEFI will not be active and you will not be able to set up UEFI booting later in the install process!
 
{{Note|'''Some motherboards may appear to support UEFI, but don't.''' Do your research. For example, the Award BIOS in my Gigabyte GA-990FXA-UD7 rev 1.1 has an option to enable UEFI boot for CD/DVD. '''This is not sufficient for enabling UEFI boot for hard drives and installing Funtoo Linux.''' UEFI must be supported for both removable media (so you can boot System Rescue CD using UEFI) as well as fixed media (so you can boot your new Funtoo Linux installation.) It turns out that later revisions of this board (rev 3.0) have a new BIOS that fully supports UEFI boot.  This may point to a third principle -- know thy hardware.}}
 
==== Old-School (BIOS/MBR) Method ====
 
{{Note|Use this method if you are booting using your BIOS, and if your System Rescue CD initial boot menu was light blue. If you're going to use the new-school method, [[#New-School (UEFI/GPT) Method|click here to jump down to UEFI/GPT.]]}}
 
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 {{f|/dev/sda}} is the disk that you want to partition:
{{console|body=
###i## 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
 
#        Start          End    Size  Type            Name
1        2048  1250263694  596.2G  Linux filesyste Linux filesystem
}}
Now, it is 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 accomplish this using {{c|sgdisk}}:
{{Warning|This will make any existing partitions inaccessible! You are '''strongly''' cautioned and advised to backup any critical data before proceeding.}}
 
{{console|body=
###i## 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:
 
{{console|body=
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************
}}Now we will use {{c|fdisk}} to create the MBR partition table and partitions:
{{console|body=
###i## fdisk /dev/sda
}}
Within {{c|fdisk}}, follow these steps:
 
'''Empty the partition table''':
{{console|body=
Command (m for help): ##i##o ↵
}}
'''Create Partition 1''' (boot):
 
{{console|body=
Command (m for help): ##i##n ↵
Partition type (default p): ##i##↵
Partition number (1-4, default 1): ##i##↵
First sector: ##i##↵
Last sector: ##i##+128M ↵
}}
'''Create Partition 2''' (swap):
 
{{console|body=
Command (m for help): ##i##n ↵
Partition type (default p): ##i##↵
Partition number (2-4, default 2): ##i##↵
First sector: ##i##↵
Last sector: ##i##+2G ↵
Command (m for help): ##i##t ↵
Partition number (1,2, default 2): ##i## ↵
Hex code (type L to list all codes): ##i##82 ↵
}}
'''Create the root partition:'''
 
{{console|body=
Command (m for help): ##i##n ↵
Partition type (default p): ##i##↵
Partition number (3,4, default 3): ##i##↵
First sector: ##i##↵
Last sector: ##i##↵
}}
'''Verify the partition table:'''
 
{{console|body=
Command (m for help): ##i##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:'''
 
{{console|body=Command (m for help): ##i##w}}
Your new MBR partition table will now be written to your system disk.
 
{{Note|You're done with partitioning! Now, jump over to [[#Creating filesystems|Creating filesystems]].}}
 
==== New-School (UEFI/GPT) Method ====
 
{{Note|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 {{c|gdisk}} commands to create a GPT partition table are as follows. Adapt sizes as necessary, although these defaults will work for most users. Start {{c|gdisk}}:
{{console|body=###i## gdisk /dev/sda}}
Within {{c|gdisk}}, follow these steps:
 
'''Create a new empty partition table''' (This ''will'' erase all data on the disk when saved):
{{console|body=
Command: ##i##o ↵
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): ##i##y ↵
}}
'''Create Partition 1''' (boot):
 
{{console|body=
Command: ##i##n ↵
Partition Number: ##i##1 ↵
First sector: ##i##↵
Last sector: ##i##+500M ↵
Hex Code: ##i##EF00 ↵
}}
'''Create Partition 2''' (swap):
 
{{console|body=
Command: ##i##n ↵
Partition Number: ##i##2 ↵
First sector: ##i##↵
Last sector: ##i##+4G ↵
Hex Code: ##i##8200 ↵
}}
'''Create Partition 3''' (root):
 
{{console|body=
Command: ##i##n ↵
Partition Number: ##i##3 ↵
First sector: ##i##↵
Last sector: ##i##↵##!i## (for rest of disk)
Hex Code: ##i##↵
}}
Along the way, you can type "{{c|p}}" and hit Enter to view your current partition table. If you make a mistake, you can type "{{c|d}}" to delete an existing partition that you created. When you are satisfied with your partition setup, type "{{c|w}}" to write your configuration to disk:
 
'''Write Partition Table To Disk''':
{{console|body=
Command: ##i##w ↵
Do you want to proceed? (Y/N): ##i##Y ↵
}}The partition table will now be written to the disk and {{c|gdisk}} will close.
 
Now, your GPT/GUID partitions have been created, and will show up as the following ''block devices'' under Linux:
 
* {{c|/dev/sda1}}, which will be used to hold the {{c|/boot}} filesystem,
 
* {{c|/dev/sda2}}, which will be used for swap space, and
 
* {{c|/dev/sda3}}, which will hold your root filesystem.
 
{{Tip|You can verify that the block devices above were correctly created by running the command {{c|lsblk}}.}}
==== Creating filesystems ====
 
{{Note|This section covers both BIOS ''and'' UEFI installs. Don't skip it!}}
 
Before your newly-created partitions can be used, the block devices that were created in the previous step need to be initialized with filesystem ''metadata''. This process is known as ''creating a filesystem'' on the block devices. After filesystems are created on the block devices, they can be mounted and used to store files.
 
Let's keep this simple. Are you using old-school MBR partitions? If so, let's create an ext2 filesystem on {{f|/dev/sda1}}:
{{console|body=###i## mkfs.ext2 /dev/sda1}}
If you're using new-school GPT partitions for UEFI, you'll want to create a vfat filesystem on {{c|/dev/sda1}}, because this is what UEFI is able to read:
{{console|body=###i## 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 {{c|mkswap}} command. Then we'll run the {{c|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:
{{console|body=
# ##i##mkswap /dev/sda2
# ##i##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:
 
{{console|body=###i## mkfs.ext4 /dev/sda3}}
...and here's how to create an XFS root filesystem, if you prefer to use XFS instead of ext4:
 
{{console|body=###i## mkfs.xfs /dev/sda3}}
Your filesystems (and swap) have all now been initialized, so that that can be mounted (attached to your existing directory heirarchy) and used to store files. We are ready to begin installing Funtoo Linux on these brand-new filesystems.
 
{{Warning|When deploying an OpenVZ host, please use ext4 exclusively. The Parallels development team tests extensively with ext4, and modern versions of {{c|openvz-rhel6-stable}} are '''not''' compatible with XFS, and you may experience kernel bugs.}}
 
==== Mounting filesystems ====
 
Mount the newly-created filesystems as follows, creating {{c|/mnt/funtoo}} as the installation mount point:
{{console|body=
###i## mkdir /mnt/funtoo
###i## mount /dev/sda3 /mnt/funtoo
###i## mkdir /mnt/funtoo/boot
###i## mount /dev/sda1 /mnt/funtoo/boot
}}
Optionally, if you have a separate filesystem for {{f|/home}} or anything else:
 
{{console|body=
###i## mkdir /mnt/funtoo/home
###i## mount /dev/sda4 /mnt/funtoo/home
}}
If you have {{f|/tmp}} or {{f|/var/tmp}} on a separate filesystem, be sure to change the permissions of the mount point to be globally-writeable after mounting, as follows:
{{console|body=###i## chmod 1777 /mnt/funtoo/tmp}}
==== Setting the Date ====
 
{{Important|If your system's date and time are too far off (typically by months or years,) then it may prevent Portage from properly downloading source tarballs. This is because some of our sources are downloaded via HTTPS, which use SSL certificates and are marked with an activation and expiration date. However, if your system time is relatively close to correct, you can probably skip this step for now.}}
 
Now is a good time to verify the date and time are correctly set to UTC. Use the {{c|date}} command to verify the date and time:
{{console|body=
###i## date
Fri Jul 15 19:47:18 UTC 2011
}}
If the date and/or time need to be corrected, do so using {{c|date MMDDhhmmYYYY}}, keeping in mind {{c|hhmm}} are in 24-hour format. The example below changes the date and time to "July 16th, 2011 @ 8:00PM" UTC:
 
{{console|body=
###i## 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:
 
{{console|body=###i## 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 {{c|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 {{c|funtoo-current}}.'''
 
Funtoo Linux has various different 'builds':
 
{{TableStart}}
{{2ColHead|Build|Description}}
<tr><td>{{c|funtoo-current}}</td><td>The most commonly-selected build of Funtoo Linux. Receives rapid updates and preferred by desktop users.</td></tr>
<tr><td>{{c|funtoo-stable}}</td><td>Emphasizes less-frequent package updates and trusted, reliable versions of packages over the latest versions.</td></tr>
{{TableEnd}}
 
==== Which Variant? ====
 
'''If you're not sure, pick {{c|standard}}.'''
 
Our "regular" stage3's are listed with a variant of {{c|standard}}. The following variant builds are available:
 
{{TableStart}}
{{2ColHead|Variant|Description}}
<tr><td>{{c|standard}}</td><td>The "standard" version of Funtoo Linux</td></tr>
<tr><td>{{c|pure64}}</td><td>A 64-bit build that drops multilib (32-bit compatibility) support. Can be ideal for server systems.</td></tr>
<tr><td>{{c|hardened}}</td><td>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.</td></tr>
{{TableEnd}}
 
==== Download the Stage3 ====
 
Once you have found the stage3 that you would like to download, use {{c|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 {{f|/mnt/funtoo}} directory as follows:
{{console|body=
###i## cd /mnt/funtoo
###i## 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 {{c|generic_64}} or {{c|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:
{{console|body=
###i## tar xpf stage3-latest.tar.xz
}}{{Important|It is very important to use {{c|tar's}} "{{c|'''p'''}}" option when extracting the Stage 3 tarball - it tells {{c|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 {{c|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 {{f|/proc}}, {{f|/sys}} and {{f|/dev}} inside your new system. Use the following commands to do so:
{{console|body=
# ##i##cd /mnt/funtoo
# ##i##mount -t proc none proc
# ##i##mount --rbind /sys sys
# ##i##mount --rbind /dev dev
}}You'll also want to copy over {{f|resolv.conf}} in order to have proper resolution of Internet hostnames from inside the chroot:
{{console|body=
# ##i##cp /etc/resolv.conf /mnt/funtoo/etc/
}}Now you can chroot into your new system. Use <code>env</code> before <code>chroot</code> to ensure that no environment settings from the installation media are pulled in to your new system:
 
{{console|body=###i## env -i HOME=/root TERM=$TERM chroot . bash -l}}
{{Note|For users of live CDs with 64-bit kernels installing 32-bit systems: Some software may use {{c|uname -r}} to check whether the system is 32 or 64-bit. You may want append linux32 to the chroot command as a workaround, but it's generally not needed.}}
{{Important|If you receive the error "{{c|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:
{{console|body=# ##i##export PS1="(chroot) $PS1"}}
Test internet name resolution from within the chroot:
{{console|body=###i## ping -c 5 google.com}}
If you can't ping, make sure {{f|/etc/resolv.conf}} doesn't contain things like {{c|127.0.x.x}} addresses, if it does, change the {{c|127.0.x.x}} entry to {{c|8.8.8.8}} -- Google's public dns address.  Make sure to replace this with your dns of choice once the system is installed.
 
 
Congratulations! You are now chrooted inside a Funtoo Linux system. Now it's time to get Funtoo Linux properly configured so that Funtoo Linux will start successfully, without any manual assistance, when your system is restarted.
=== Downloading the Portage tree ===
 
{{note|For an alternative way to do this, see [[Installing Portage From Snapshot]].}}
Now it's time to install a copy of the Portage repository, which contains package scripts (ebuilds) that tell portage how to build and install thousands of different software packages. To create the Portage repository, simply run <code>emerge --sync</code> from within the chroot. This will automatically clone the portage tree from [https://github.com/funtoo/ports-2012 GitHub]:
 
{{console|body=
(chroot) ###i## emerge --sync
}}
{{important|If you receive the error with initial {{c|emerge --sync}} due to git protocol restrictions, set the {{c|SYNC}} variable in {{c|/etc/portage/make.conf}} to
{{c|"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 {{f|/etc/fstab}}. The others are optional.
 
==== Using Nano ====
 
The default editor included in the chroot environment is called {{c|nano}}. To edit one of the files below, run nano as follows:
 
{{console|body=
(chroot) ###i## 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 {{c|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:
{{TableStart}}
{{3ColHead|File|Do I need to change it?|Description}}
<tr  class="danger">
<td>{{c|/etc/fstab}}</td>
<td>'''YES - required'''</td>
<td>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.</td>
</tr><tr>
<td>{{c|/etc/localtime}}</td>
<td>''Maybe - recommended''</td>
<td>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) </td>
</tr><tr>
<td>{{c|/etc/make.conf}} (symlink) - also known as:<br/>{{c|/etc/portage/make.conf}}</td>
<td>''Maybe - recommended''</td>
<td>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.''</td>
</tr><tr>
<td>{{c|/etc/conf.d/hostname}}</td>
<td>''Maybe - recommended''</td>
<td>Used to set system hostname. Set the {{c|hostname}} variable to the fully-qualified (with dots, ie. {{c|foo.funtoo.org}}) name if you have one. Otherwise, set to the local system hostname (without dots, ie. {{c|foo}}). Defaults to {{c|localhost}} if not set.</td>
</tr><tr>
<td>{{c|/etc/hosts}}</td>
<td>''No''</td>
<td> You no longer need to manually set the hostname in this file. This file is automatically generated by {{c|/etc/init.d/hostname}}.</td>
</tr><tr>
<td>{{c|/etc/conf.d/keymaps}}</td>
<td>Optional</td>
<td>Keyboard mapping configuration file (for console pseudo-terminals). Set if you have a non-US keyboard. See [[Funtoo Linux Localization]].</td>
</tr><tr>
<td>{{c|/etc/conf.d/hwclock}}</td>
<td>Optional</td>
<td>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.</td>
</tr><tr>
<td>{{c|/etc/conf.d/modules}}</td>
<td>Optional</td>
<td>Kernel modules to load automatically at system startup. Typically not required. See [[Additional Kernel Resources]] for more info.</td>
</tr><tr>
<td>{{c|/etc/conf.d/consolefont}}</td>
<td>Optional</td>
<td>Allows you to specify the default console font. To apply this font, enable the consolefont service by running rc-update add consolefont.</td>
</tr><tr>
<td>{{c|profiles}}</td>
<td>Optional</td>
<td>Some useful portage settings that may help speed up intial configuration.</td>
</tr>
{{TableEnd}}
 
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 portal|Community]])
 
Let's go ahead and see what we have to do. Use {{c|nano -w <name_of_file>}} to edit files -- the "{{c|-w}}" argument disables word-wrapping, which is handy when editing configuration files. You can copy and paste from the examples.
 
{{Warning|It's important to edit your {{c|/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 {{c|gdisk}} or {{c|fdisk}}. Skipping this step may prevent Funtoo Linux from booting successfully.}}
 
==== /etc/fstab ====
 
{{f|/etc/fstab}} is used by the {{c|mount}} command which is run when your system boots. Lines in this file inform {{c|mount}} about filesystems to be mounted and how they should be mounted. In order for the system to boot properly, you must edit {{f|/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 {{c|lsblk}} command may be of help to you:
{{console|body=
(chroot) ###i## nano -w /etc/fstab
}}
{{file|name=/etc/fstab|desc=An example fstab file|body=
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
#
# See the manpage fstab(5) for more information.
#
# <fs>     <mountpoint>  <type>  <opts>        <dump/pass>
 
/dev/sda1    /boot        ext2    noauto,noatime 1 2
/dev/sda2    none          swap    sw            0 0
/dev/sda3    /            ext4    noatime        0 1
#/dev/cdrom  /mnt/cdrom    auto    noauto,ro      0 0
}}
{{Note|Currently, our default {{f|/etc/fstab}}file  has the root filesystem as {{c|/dev/sda4}} and the swap partition as {{c|/dev/sda3}}. These will need to be changed to {{c|/dev/sda3}} and {{c|/dev/sda2}}, respectively.}}
 
{{Note|If you're using UEFI to boot, change the {{f|/dev/sda1}} line so that it says {{c|vfat}} instead of {{c|ext2}}. Similarly, make sure that the {{f|/dev/sda3}} line specifies either {{c|xfs}} or {{c|ext4}}, depending on which filesystem you chose earlier on in the installation process when you created filesystems.}}
 
==== /etc/localtime ====
 
{{f|/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 {{f|/etc/localtime}} with a symbolic link to the timezone that you wish to use.
 
{{console|body=
(chroot) ###i## ln -sf /usr/share/zoneinfo/MST7MDT /etc/localtime
}}
The above sets the timezone to Mountain Standard Time (with daylight savings). Type {{c|ls /usr/share/zoneinfo}} to list available timezones. There are also sub-directories containing timezones described by location.
 
==== /etc/portage/make.conf ====
 
{{c|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 [[wikipedia:Hyper-threading|hyper-threading]], then you would set {{c|MAKEOPTS}} to 3:
 
<pre>
MAKEOPTS="-j3"
</pre>
 
If you are unsure about how many processors/threads you have, then use {{c|nproc}} to help you.
{{console|body=
(chroot) ###i## nproc
16
}}
Set {{c|MAKEOPTS}} to this number plus one:
 
<pre>
MAKEOPTS="-j17"
</pre>
 
{{c|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 ("{{c|-}}") 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 [http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=2&chap=2 Gentoo Handbook].
 
{{c|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:
 
<pre>
LINGUAS="fr"
</pre>
 
==== /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.
{{console|body=
(chroot) ###i## 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 <code>emerge</code> 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:
 
<console>
(chroot) # ##i##emerge packagename
</console>
 
When you install a package by specifying its name in the command-line, Portage records its name in the <code>/var/lib/portage/world</code> 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 <code>world</code> set, we can update our entire system by typing:
 
<console>
(chroot) # ##i##emerge --sync
(chroot) # ##i##emerge -auDN @world
</console>
 
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 <code>world</code> set of packages. The options specified tell <code>emerge</code> to:
 
* '''<code>a</code>''' - show us what will be emerged, and '''ask''' us if we want to proceed
* '''<code>u</code>''' - '''update''' the packages we specify -- don't emerge them again if they are already emerged.
* '''<code>D</code>''' - Consider the entire dependency tree of packages when looking for updates. In other words, do a '''deep''' update.
* '''<code>N</code>''' - Update any packages that have changed ('''new''') USE settings.
 
You should also consider passing <code>--with-bdeps=y</code> 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 <code>world</code> 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:
 
<console>
(chroot) # ##i##emerge -1 packagename
</console>
 
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.
 
<console>
(chroot) # ##i##emerge --sync
(chroot) # ##i##emerge -auDN @world
</console>
 
{{fancyimportant|1=
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 {{c|debian-sources}} kernel to make installation faster and easier. To see if debian-sources is installed, type:
{{console|body=
(chroot) # ##i##emerge -s debian-sources
Searching...   
[ Results for search key : ##b##debian-sources##!b## ]
[ Applications found : ##b##1##!b## ]
 
*  ##b##sys-kernel/debian-sources##!b##
      ##g##Latest version available:##!g## 3.19.3
      ##g##Latest version installed:##!g## 3.19.3
      ##g##Size of files:##!g## 81,292 kB
      ##g##Homepage:##!g##      http://www.debian.org
      ##g##Description:##!g##  Debian Sources (and optional binary kernel)
      ##g##License:##!g##      GPL-2
}}
If a version is listed under {{c|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|Installing a Bootloader section]].
 
==== Building the Kernel ====
 
If you need to build a kernel for Funtoo Linux, please follow these steps:
 
{{Fancynote|1=
See [[Funtoo Linux Kernels]] for a full list of kernels supported in Funtoo Linux. We recommend <code>debian-sources</code> for new users.}}
 
{{fancyimportant|1=
<code>debian-sources</code> with <code>binary</code> USE flag requires at least 14GB free in <code>/var/tmp</code> and takes around 1 hour to build on a Intel Core i7 Processor.}}
 
Let's emerge our kernel:
 
<console>
(chroot) # ##i##emerge debian-sources
</console>
 
Once <code>emerge</code> completes, you'll have a brand new kernel and initramfs installed to <code>/boot</code>, plus kernel headers installed in <code>/usr/src/linux</code>, and you'll be ready to configure the boot loader to load these to boot your Funtoo Linux system.
 
{{warning|If you have a RAID in your machine, the kernel installation will pull in the <code>mdadm</code> tool as a dependency. It is important to edit the <code>/etc/mdadm.conf</code> 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 <code>man mdadm</code> or the [[Package:Mdadm|mdadm]] ebuild page.}}
 
{{fancynote|NVIDIA card users: the <code>binary</code> 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 <code>/etc/modprobe.d/</code>.}}
 
{{fancynote|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 [http://www.funtoo.org/wiki/Funtoo_Linux_Kernels#Using_Debian-Sources_with_Genkernel genkernel] would be useful. Also be sure to see [[:Category:Hardware Compatibility|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.
{{#css:
 
firstHeading {
First, emerge <code>boot-update</code>. This will also cause <code>grub-2</code> and {{c|efibootmgr}} to be merged, since they are dependencies:
  display: none;
 
<console>
(chroot) # ##i##emerge boot-update
</console>
 
Then, edit <code>/etc/boot.conf</code> using {{c|nano}} and specify "<code>Funtoo Linux genkernel</code>" as the <code>default</code> setting at the top of the file, replacing <code>"Funtoo Linux"</code>.
 
<code>/etc/boot.conf</code> should now look like this:
{{file|name=/etc/boot.conf|body=
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 <code>man boot.conf</code> 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 {{c|/boot/grub/grub.cfg}} configuration file that GRUB will use for booting:
<console>
(chroot) # ##i##grub-install --target=i386-pc --no-floppy /dev/sda
(chroot) # ##i##boot-update
</console>
==== 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:
<console>
(chroot) # ##i##grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda
(chroot) # ##i##boot-update
</console>
For x86-32bit systems:
<console>
(chroot) # ##i##grub-install --target=i386-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda
(chroot) # ##i##boot-update
</console>
==== First Boot, and in the future... ====
OK -- you are ready to boot!
You only need to run <code>grub-install</code> when you first install Funtoo Linux, but you need to re-run <code>boot-update</code> every time you modify your <code>/etc/boot.conf</code> file or add new kernels to your system. This will regenerate {{c|/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:
{{console|body=(chroot) # ##i##emerge linux-firmware networkmanager
(chroot) ###i## 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 {{c|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:
{{console|body=# ##i##nmtui}}
For more information about NetworkManager, see the [[Package:NetworkManager|NetworkManager package page]].
{{Note|wpa_supplicant is also a good choice for wireless network connections. See the {{package|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 {{c|dhcpcd}} to the default runlevel:
{{console|body=
(chroot) # ##i##rc-update add dhcpcd default}}
When you reboot, {{c|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
{{console|body=
(chroot) # ##i##nano /etc/conf.d/hostname
}}
Look for the line starting with hostname and change the entry between the quotes. Save the file, on the next boot Funtoo will use the new hostname.
{{warning|Do not use special characters in the hostname, as the shell may interpret these, leading to unpredictable results. Use the Latin alphabet: a-z, A-Z, 0-9}}
{{tip|Use short hostnames (up to 8 or 10 characters) to prevent the terminal screen being filled with the hostname, leaving little space for the command itself. This become particularly poignant when coding long command strings in various programming languages like Bash, Python, SQL and Perl}}
=== Finishing Steps ===
==== Set your root password ====
It's imperative that you set your root password before rebooting so that you can log in.
<console>
(chroot) # ##i##passwd
</console>
===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.
<console>
(chroot) # ##i##exit
# ##i##cd /mnt
# ##i##umount -lR funtoo
# ##i##reboot
</console>
{{fancynote|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 <code>login:</code> 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:
{{TableStart}}
{{2ColHead|Sub-Profile Type|Description}}
{{2Col|{{c|arch}}|Typically {{c|x86-32bit}} or {{c|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.}}
{{2Col|{{c|build}}|Defines whether your system is a {{c|current}}, {{c|stable}} or {{c|experimental}} build. {{c|current}} systems will have newer packages unmasked than {{c|stable}} systems. This is defined when your stage is built and is typically not changed.}}
{{2Col|{{c|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.}}
{{2Col|{{c|flavor}}|Defines the general type of system, such as {{c|server}} or {{c|desktop}}, and will set default USE flags appropriate for your needs.}}
{{2Col|{{c|mix-ins}}|Defines various optional settings that you may be interested in enabling.}}
{{TableEnd}}
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 {{c|epro show}} to view your current profile settings, in addition to any inheritance information:
{{console|body=
(chroot) # ##i## epro show
=== ##g##Enabled Profiles##!g##: ===
        arch: ##c## x86-64bit
      build: ##c## current
    subarch: ##c## intel64-haswell
      flavor: ##c## desktop
    mix-ins: ##c## gnome
=== ##g##All inherited flavors from desktop flavor##!g##: ===
                    ##c##workstation##!c## (from desktop flavor)
                            ##c##core##!c## (from workstation flavor)
                        ##c##minimal##!c## (from core flavor)
=== ##g##All inherited mix-ins from desktop flavor##!g##: ===
                              ##c##X##!c## (from workstation flavor)
                          ##c##audio##!c## (from workstation flavor)
                            ##c##dvd##!c## (from workstation flavor)
                          ##c##media##!c## (from workstation flavor)
      ##c##mediadevice-audio-consumer##!c## (from media mix-in)
                ##c##mediadevice-base##!c## (from mediadevice-audio-consumer mix-in)
      ##c##mediadevice-video-consumer##!c## (from media mix-in)
                ##c##mediadevice-base##!c## (from mediadevice-video-consumer mix-in)
        ##c##mediaformat-audio-common##!c## (from media mix-in)
          ##c##mediaformat-gfx-common##!c## (from media mix-in)
        ##c##mediaformat-video-common##!c## (from media mix-in)
                  ##c##console-extras##!c## (from workstation flavor)
                          ##c##print##!c## (from desktop flavor)
}}
Here are some basic examples of {{c|epro}} usage:
{{TableStart}}
{{2ColHead|Description|Command}}
{{2Col|View available profiles. Enabled profiles will be highlighted in cyan. Directly enabled profiles will be in bold and have a {{c|*}} appended.|{{console|body=(chroot) # ##i##epro list}}}}
{{2Col|Change the system flavor.|{{console|body=(chroot) # ##i##epro flavor desktop}}}}
{{2Col|Add a mix-in.|{{console|body=(chroot) # ##i##epro mix-in +gnome}}}}
{{TableEnd}}
===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 [[:Category:Official Documentation|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 [[:Category:First Steps|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.
[[Category:HOWTO]]
[[Category:Install]]
[[Category:Official Documentation]]

Latest revision as of 04:08, November 21, 2021

Other languages:
Deutsch • ‎English • ‎Türkçe • ‎español • ‎français • ‎italiano • ‎polski • ‎português • ‎slovenčina • ‎Ελληνικά • ‎русский • ‎українська • ‎հայերեն • ‎עברית • ‎ไทย • ‎中文（中国大陆）‎ • ‎中文（台灣）‎ • ‎日本語 • ‎한국어
   Note

Translators: Thank you for your help! Please use the section-by-section guide as the basis for your translations. Thanks again!

Wprowadzenie

root # Witamy w Funtoo Linux!

Dokument został przygotowany, aby pomóc Tobie w instalacji systemu operacyjnego Funtoo na komputerze typu PC. Konfigurację środowiska ograniczyliśmy do minimum.

If you're new to installing a Gentoo-based Linux, or new to Linux entirely -- welcome! We have attempted to make these installation instructions understandable to new users as well. We encourage all new users to read Wolf Pack Philosophy to understand some of the distinctives of the Funtoo community.

Zanim zaczniemy, przejrzyj następujące ważne informacje:

Our desktop environment stages (GNOME, Cinnamon, etc.) now support seamless installation on VMware Workstation Pro virtual machines. We highly recommend you enable 3D Accelerated Video for your VM, which is not enabled by default. Click here for more info.
Wydanie Aktualne
Obecna wersja 1.4, czasami nazywana 1.4-release lub 1.4-release-std.
Model rozwoju
Funtoo Linux jest to opracowana przez społeczność (kompilująca kod źródłowy) meta-dystrybucja Linuksa.

Używając Funtoo jesteś zaproszony do uczestniczenia w rozwoju systemu. Mile widziani są użytkownicy dołączający do deweloperów za pośrednictwem strony code.funtoo.org, nie ma potrzeby przeprowadzania specjalnej procedury lub skomplikowanego procesu zatwierdzania. Zobacz Development Guide , aby uzyskać więcej informacji. Są też YouTube video tutorials , które pomogą Ci zacząć.

Support Matrix
Please use our Support Matrix to familiarize yourself with the technologies we do -- and do not -- support.
Styl dokumentacji
Proponujemy teraz wybór read and browse the Install Guide section-by-section. Może on być bardziej odpowiedni dla użytkowników "on-line".
Uruchamianie (platformy) Steam
Niedawno zostało wydane oficjalnie wsparcie dla Steam Docker images , tak samo jak wsparcie dla 'Steam' na 'Flatpak' u, są one oficjalnie wspieranym rozwiązaniem umożliwiającym działanie Steam na systemie Funtoo. Zobacz Steam, aby zasięgnąć więcej informacji.
Kontenery
Oficjalnie wspierane jest zarządzanie kontenerami LXD i Docker. Proszę obejrzeć listę wspieranych Chroot and Containers. Nie jest ona kompletna, jednak ciągle rośnie o nowe dostępne technologie kontenerów wraz z linkami do dalszej dokumentacji.
Nowe narzędzie Fchroot
Teraz dostępne jest nasze nowe fchroot tool , które umożliwi Ci uruchamianie środowiska ARM i RISCV na sprzęcie typu PC. Jest to bardzo efektywne narzędzie przyspieszające kompilowanie dużych kawałków programów dla sytemów ARM o ograniczonych zasobach. Zobacz code.funtoo.org page, Frankenchroot i Frankenchroot/Live_NFS_Frankenchroot , żeby uzyskać informacje o konfigurowaniu środowiska.

Teraz, gdy zostały omówione wszystkie ważne informacje, czas zacząć instalacje Funtoo Linux!

Proces Instalacji

Oto podstawowy przegląd procesu instalacji Funtoo:

  1. Pobierz i uruchom komputer z wybranego 'LiveCD/DVD/USB'.
  2. Przygotowanie dysku.
  3. Partycjonowanie dysku (MBR).
  4. Partycjonowanie dysku (GPT).
  5. Utwórz i zamontuj system plików.
  6. Ustawienie aktualnej Daty.
  7. Pobieranie i rozpakowanie archiwum 'stage 3'.
  8. 'chroot' do nowego systemu.
  9. Pobieranie drzewa menadżera pakietów 'Portage'.
  10. Konfiguracja systemu.
  11. Wprowadzenie do korzystania z 'Portage'.
  12. Instalacja jądra (kernel'a).
  13. Instalacja startowego bootloader'a.
  14. Konfiguracja Sieci.
  15. Wykonanie ostatnich kroków.
  16. Konfiguracja wybranego Profilu.
  17. Wszystko Gotowe! Miłego korzystania z systemu Funtoo Linux!

Pobieranie obrazu LiveCD/DVD/USB

Żeby zainstalować Funtoo Linux, najpierw musisz uruchomić komputer przy użyciu 'Live CD/DVD' lub pamięci USB z systemem Linux. Zalecamy użycie dystrybucji opartej na Funtoo Funtoo:New Install Experience/LiveCD ponieważ zawiera nowoczesne jądro, a także pełne środowisko graficzne. Można ją nagrać na CD / DVD lub zainstalować na USB. Obraz pobierzesz tutaj:

When installing Funtoo Linux on x86-64bit, we highly recommend the official Funtoo Linux LiveCD/LiveUSB, which can always be downloaded here:

While any modern bootable Linux image should be sufficient to install Funtoo Linux, the Funtoo LiveCD has several advantages over other options. Because it natively runs Funtoo Linux, and includes our official debian-sources kernel with very good hardware support, the hardware it supports is going to match the hardware that Funtoo Linux supports -- thus allowing you to identify any hardware compatibility issues immediately.

In addition, our LiveCD is regularly updated, and includes NetworkManager which allows the use of the easy nmtui command to configure your network. It also includes our innovative Fchroot tool, which allows you to use QEMU to "chroot" into non-x86 systems such as arm-64bit and riscv-64bit. This allows the Funtoo LiveCD to be used to even rescue and set up systems with different instruction sets!

Aby skopiować obraz na pamięć USB, użyj następującego polecenia: 

root # dd if=funtoo-livecd-area31-5.1-beta.iso of=/dev/sdx bs=4k status=progress

Musisz wstawić /dev/sdx , zamieniając "x" na literę wskazującą na podłączoną pamięć USB (pendrive).

Dostęp do Sieci

For steps on setting up network access from the LiveCD, please see the Funtoo:New Install Experience/LiveCD page.

Instalacja Zdalna

Alternatywną możliwością jest zalogowanie się do Area31 Funtoo LiveCD poprzez sieć za pomocą SSH. Może to być bardziej wygodny sposób przeprowadzenia instalacji z innego komputera.

First ensure that sshd is running. You may need to start sshd as follows: 

root # /etc/init.d/sshd start

Jeśli chcesz zainstalować zdalnie Funtoo Linux, oto jak to zrobić. Najpierw musisz upewnić się, że Area31 LiveCD ma działające połączenie sieciowe. Następnie wymagane jest ustawienie hasła root 'a: 

root # passwd
Nowe hasło : ********
Proszę ponownie wpisać nowe hasło : ********
passwd: hasło zostało zmienione


Kiedy wpiszesz nowe hasło, niezbędnym jest określenie adresu IP uruchomionego LiveCD/DVD/USB. Później możesz użyć ssh do połączenia się z nim przez sieć. Żeby określić aktualnie używany adres IP, wpisz ifconfig: 

root # ifconfig

Inną możliwością ustalenia obecnego adresu IP jest użycie narzędzia ip iproute2: 

root # ip addr show

Jeden z interfejsów powinien mieć adres IP (wyświetlony jako inet addr:) z Twojej sieci LAN. W następnym kroku możesz połączyć się zdalnie z LiveCD za pomocą innego komputera i wygodnie podejmować działania z Linuksa albo MacOS. Aby zainicjować połączenie zdalne z systemu "gościa", wpisz następującą komendę, zastępując 1.2.3.4 adresem IP środowiska LiveCD/DVD/USB: 

remote system $ ssh root@1.2.3.4
Password: **********
   Note

Jeśli chciałbyś połączyć się zdalnie z systemu Microsoft Windows, powinieneś zainstalować klienta SSH dla Windows'a, takiego jak OpenSSH.

Po zalogowaniu przy użyciu SSH, jesteś zdalnie połączony z LiveCD/DVD/USB i możesz kontynuować proces instalacji.

Przygotowanie Dysku

W tej sekcji musisz wybrać format dysku używany do uruchomiania systemu (oraz partycjonowania) - MBR lub UEFI/GPT. Jeżeli nie znasz różnic pomiędzy nimi, przejrzyj naszą stronę Disk Formats, żeby zapoznać się z opisem każdej z opcji i możliwych ograniczeń formatu. Zwykle bezpieczniej jest wybrać starszą metodę MBR dla dysków systemowych o rozmiarze mniejszym niż 2 TB. Większość nowoczesnych systemów komputerowych obsługuje zarówno MBR, jak i rozruch z UEFI.

MBR is the traditional way of booting a PC. It works by installing executable code on the boot sector of your hard drive, which starts the boot process. When you use MBR to boot, you must have BIOS booting enabled in your BIOS, use traditional MBR partitions on your disk which are created using the fdisk tool.

UEFI is the more modern way to boot a PC. It works using a boot loader that is built into your computer. Boot entries are created and stored in your computer's non-volatile memory. When you use UEFI to boot, you must have UEFI enabled in your BIOS, and use more modern GPT partitions which are created using the gdisk tool.

Generally, it's usually safe to pick the legacy MBR method for system disks under 2TB in size and most modern PC systems support MBR as well as UEFI booting.

   Note

For more information on differences between MBR and UEFI, see our Disk Formats page for an overview of each option and the trade-offs.

Ale przede wszystkim...

Przed wykonaniem jakichkolwiek czynności na dyskach upewnij się, że partycjonujesz właściwy dysk. Użyj komendy lsblk, aby wyświetlić listę wszystkich urządzeń blokowych w Twoim systemie, jak również partycji na tych urządzeniach blokowych: 

root # lsblk
NAME          MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda             8:0    0  1.8T  0 disk 
├─sda1          8:1    0  512M  0 part 
├─sda2          8:2    0    8G  0 part [SWAP]
└─sda3          8:3    0  1.8T  0 part 
  ├─main-root 254:0    0  500G  0 lvm  /
  └─main-data 254:1    0  1.3T  0 lvm  /home
   Note

Jeżeli nie jesteś pewien który dysk jest który, możesz użyć polecenia lsblk -o MODEL,NAME,SIZE aby wyświetlić modele urządzeń przypisane do nazw /dev/sd? a, b, c ...

Upewnij się, że nie nadpiszesz żadnych ważnych danych i że wybrałeś właściwe urządzenie /dev/sd?. Powyżej, możesz zobaczyć, że dysk SATA sda zawiera trzy partycje: sda1, sda2 i sda3; oraz to, że sda3 zawiera woluminy LVM. Jeśli używasz dysku NVME, wtedy możesz zobaczyć opis urządzenia w podobnej postaci: nvme0n1, a Twoje partycje (jeśli istnieją) zostanią nazwane odpowiednio nvme0n1p1, nvme0n1p2, itd. Jeśli instalujesz system na karcie microSD do Raspberry Pi, urządzenie blokowe będzie miało zwykle przypisaną nazwę mmcblk0, a partycje będą miały końcówki (przyrostki) p1, p2, itd.

Po dwukrotnym skontrolowaniu docelowego urządzenia blokowego i upewnieniu się, że partycjonujesz właściwy dysk, przejdź do następnego kroku.

Partycjonowanie (MBR)

Starsza metoda (BIOS/MBR)

   Note

Użyj tej metody, jeżeli uruchamiasz system przy użyciu BIOS-u i jeżeli menu początkowe 'Funtoo LiveCD/DVD/USB' miało kolor jasnoniebieski. Jeśli zamierzasz użyć na dysku formatu UEFI/GPT, przejdź do następnego rozdziału Przewodnika.

Po pierwsze, dobrym pomysłem jest upewnienie się, że wybrałeś właściwy dysk twardy do partycjonowania. Wypróbuj poniższe polecenie i sprawdź, czy /dev/sda odpowiada urządzeniu, które chcesz podzielić na partycje: 

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

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

Teraz zaleca się usunięcie wszelkich istniejących tablic partycji MBR lub GPT na dysku, może to spowodować dezorientację systemu BIOS podczas uruchamiania komputera. Wpisujemy polecenie sgdisk:

   Warning

OSTRZEŻENIE: Spowoduje to, że wszelkie istniejące partycje będą wymazane! Zaleca się utworzenie kopii zapasowej ważnych danych przed kontynuowaniem. 

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.

Ta informacja również nie powinna Cię martwić, ponieważ operacja się powiodła: 

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

Teraz użyjemy fdisk żeby utworzyć tablicę partycji MBR oraz partycje: 

root # fdisk /dev/sda

W programie fdisk, wykonaj następujące kroki:

Utwórz nową tablicę partycji: 

Command (m for help): o ↵

Utwórz Partycję Rozruchową (boot): 

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

Utwórz Partycję Wymiany (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 ↵

Utwórz Partycję Główną (root): 

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

Zweryfikuj poprawność utworzonych partycji (docelowych wpisów w tablicy partycji): 

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

Zapisz tablicę partycji na dysk: 

Command (m for help): w

Twoja nowa tablica partycji zostanie teraz zapisana na dysk.

   Note

Partycjonowanie zakończone! Teraz, przejdź do rozdziału Tworzenie systemu plików.

Partycjonowanie (MBR)

UEFI/GPT Method

   Note

Use this method if you are interested in booting using UEFI, and if your Funtoo LiveCD initial boot menu was black and white, or the system booted without a boot menu. If it was light blue, this method will not work. Instead, use the instructions in the previous section then skip this section, or reboot LiveCD in UEFI mode first.

   Note

You can build legacy mode into your GPT partition table but it requires a BIOS Boot partition. see Talk:Install/GPT_Partitioning

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: +128M ↵
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 /boot filesystem,
  • /dev/sda2, which will be used for swap space, and
  • /dev/sda3, which will hold your root filesystem.
   Tip

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

Tworzenie systemu plików

   Note

Ten rozdział zawiera instrukcję instalacji dla obydwu formatów dysku: MBR oraz GPT/UEFI. Nie omijaj go!

Przed użyciem nowo utworzonych (w poprzednim rozdziale) partycji muszą być one zainicjowane. Ten proces nazwany jest tworzeniem systemu plików na urządzeniach blokowych. Po utworzeniu metadanych systemu plików na partycjach, można je zamontować i wykorzystać do przechowywania informacji.

Zróbmy to najprościej. Czy korzystasz ze starszego typu tablicy partycji MBR? Jeżeli tak, stwórzmy system plików ext2 na /dev/sda1: 

root # mkfs.ext2 /dev/sda1

Jeżeli używasz partycji GPT dla UEFI lub instalujesz system dla Raspberry Pi, będziesz chciał utworzyć system plików vfat na pierwszej partycji (w przypadku Raspberry Pi będzie to mmcblk0p1): 

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

Teraz zainicjujmy partycję wymiany. Ta partycja będzie używana jako pamięć wirtualna dla Twojego systemu Funtoo.

Na partycji wymiany nie jest możliwe utworzenie systemu plików, ponieważ nie jest ona używana do przechowywania plików. Inicjujemy ją za pomocą komendy mkswap. Następnie komendą swapon natychmiastowo aktywujemy w naszym środowisku, na wypadek gdyby była potrzebna podczas dalszego procesu instalacji: 

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

System plików na partycji głównej (root)

Teraz musimy utworzyć system plików na głównej partycji (root). To tutaj zagości Funtoo. Zalecamy system plików ext4 lub XFS. Pamiętaj, że niektóre systemy plików wymagają kompilacji (emerge) dodatkowych narzędzi przed ponownym uruchomieniem komputera. Więcej informacji znajduje się w poniższej tabeli:

System plikówRekomendowany do użycia na partycji root?Wymagana kompilacja (emerge) dodatkowych narzędzi
ext4TakBrak
XFSTaksys-fs/xfsprogs
reiserfsTak -- zwykle wymaga włączenia wsparcia w jądrze sys-fs/reiserfsprogs
zfsNie - tylko zaawansowani użytkownicysys-fs/zfs
btrfsNie - tylko zaawansowani użytkownicysys-fs/btrfs-progs
   Important

Nie zalecamy użytkownikom ustawiania ZFS lub BTRFS jako głównego systemu plików. Jest to o wiele bardziej złożone i zwykle nie jest konieczne. Zamiast tego wybierz XFS lub ext4. Systemy plików ZFS oraz BTRFS są wspierane na partycjach innych niż partycja główna root ponieważ jest to o wiele, wiele łatwiejsze do skonfigurowania. Zobacz ZFS i BTRFS po zakończeniu konfiguracji systemu Funtoo w celu skonfigurowania ZFS lub BTRFS jako dodatkowego magazynu danych.

Jeśli nie jesteś pewien, wybierz ext4. Oto jak utworzyć główny system plików ext4: 

root # mkfs.ext4 /dev/sda3

... a oto jak stworzyć główny system plików XFS, jeśli wolisz używać XFS zamiast ext4: 

root # mkfs.xfs /dev/sda3

Wszystkie systemy plików i partycja wymiany pamięci wirtualnej zostały zainicjowane, dzięki czemu można je zamontować (dołączyć do istniejącej hierarchii katalogów) i użyć do przechowywania danych. Jesteśmy gotowi, aby rozpocząć instalację Funtoo Linux na tych nowo utworzonych systemach plików.

Dodatkowe systemy plików

   Note

Może to być bardzo przydatne dla systemów na Raspberry Pi!

You may want to create additional filesystems for various parts of your Funtoo filesystem tree. It is not uncommon to place /home or /var on separate filesystems.

For Raspberry Pi, you may not have a lot of spare room on the card depending on the capacity of your microSD card, and it may make a lot of sense to put the entire /var filesystem on an external hard drive or solid state disk. This will not only ensure you don't run out of disk space, but can also improve performance since writes to the microSD card typically aren't that fast.

To do this, you will want to use fdisk or gdisk to create a partition on your external drive, and then use the mkfs.xfs or mkfs.ext4 commands to create a filesystem on the new partition. We will mount this new filesystem in the next step prior to extracting the stage3 tarball.

Montowanie systemu plików

Zamontuj nowo utworzone systemy plików w następujący sposób, tworząc punkt montowania /mnt/funtoo przeznaczony do instalacji: 

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

Jeżeli masz dodatkowe systemy plików utworzone wcześniej (takie jak /home albo /var), powinieneś je teraz zamontować, żeby po rozpakowaniu 'stage3' (co zrobimy w późniejszym etapie) systemy te zostały wypełnione potrzebnymi plikami. Wykonuje się to w następujący sposób: 

root # mkdir /mnt/funtoo/var
root # mount /dev/sdb1 /mnt/funtoo/var

Ustawianie Daty

   Important

WAŻNE: Jeżeli data i godzina w Twoim systemie jest odległa od aktualnej (zwykle o miesiące lub lata), może to uniemożliwić menadżerowi pakietów 'Portage' prawidłowe pobieranie archiwów (tarballs) z kodem źródłowym. Wynika to z faktu, że niektóre paczki są pobierane przez protokół HTTPS, który używa certyfikatów SSL i są one oznaczone datą aktywacji i wygaśnięcia. Jeśli jednak czas systemowy jest stosunkowo bliski poprawnemu, prawdopodobnie na razie możesz pominąć ten krok.

Teraz nastąpił dobry moment na sprawdzenie, czy data i godzina są ustawione poprawnie na czas UTC (Uniwersalny Czas Koordynowany). Użyj polecenia date, aby zweryfikować ustawioną datę i godzinę: 

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

Jeżeli data lub godzina wymagają korekty, zrób to używając date MMDDhhmmYYYY, pamiętając o formacie 24-godzinnym. Poniższy przykład zmienia datę i godzinę na „lipiec, 16, godzina 20:00, 2011r.” UTC: 

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

Kiedy ustawisz zegar systemowy, bardzo dobrym pomysłem jest skopiowanie ustawień do zegara sprzętowego, żeby były one zachowane po ponownym uruchomieniu komputera: 

root # hwclock --systohc

Pobieranie i rozpakowanie 'Stage3'

Teraz, gdy utworzyliśmy system plików oraz ustawiony został zegar sprzętowy i systemowy, następnym krokiem jest pobranie paczki inicjującej 'stage3'. Jest to wstępnie skompilowany system używany jako punkt wyjścia do instalacji Funtoo Linux.

Żeby pobrać poprawną wersję Funtoo dla swojego komputera, przejdź na stronę Subarches. Sub-architektury zawierają kompilacje, które zostały zaprojektowane do działania na określonym typie procesora, aby zapewnić najlepszą możliwą wydajność. Korzystają one również z zestawów instrukcji dostępnych dla danego CPU.

Co to są sub-architektury?

Z listy 'subarch' w Subarches wybierz pożądany poziom optymalizacji. System zbudowany specjalnie dla Twojego procesora będzie działał szybciej niż system mniej zoptymalizowany. W przypadku nowoczesnego systemu Intel lub AMD można bezpiecznie wybrać dokładny poziom optymalizacji dla rodziny posiadanego przez Ciebie procesora (processor family). Zapewni to najlepszą możliwą wydajność.

Jeśli używasz technologii wirtualizacji, aby uruchomić Funtoo i Twoja Maszyna Wirtualna (VM) może być używana na komputerach różnego typu, wtedy zalecane jest użycie paczki 'stage3', która jest zoptymalizowana dla najstarszego typu CPU na którym uruchomi się VM. Bardziej ogólny obraz (generic), jeśli będzie ona uruchamiana na obydwu typach procesora: AMD i Intel.

Jak już znajdziesz odpowiedni 'subarch' w Subarches, prawdopodobnie będziesz miał do wyboru kilka paczek instalacyjnych. Kolejna część pomoże Tobie zrozumieć, którą wybrać.

Która paczka z obrazem systemu?

Our desktop environment stages (GNOME, Cinnamon, etc.) now support seamless installation on VMware Workstation Pro virtual machines. We highly recommend you enable 3D Accelerated Video for your VM, which is not enabled by default. Click here for more info.

Zawsze możesz samemu wybrać obraz instalacyjny za pośrednictwem https://build.funtoo.org, a także korzystając ze strony Subarches . Oto kilka wskazówek dotyczących wyboru najlepszego archiwum .tar.xz do pobrania. Dokonaj wyboru:

Wybierz 1.4-release-std.
Jest to wydanie 1.4 Funtoo, nasze obecne wydanie.
Wybierz odpowiednią sub-architekturę dla rodziny procesora (processor family) posiadanego komputera.
To zapewni najszybsze działanie systemu.
Wybierz stage3, gdy...
Tarball stage3 jest bardziej tradycyjny, cechuje się minimalną instalacją w trybie tekstowym. Następnie kompilujesz system do pożądanej funkcjonalności używając emerge.
Wybierz gnome, gdy...
Paczka obrazu gnome (jeżeli jest dostępna) zawiera pełne środowisko graficzne GNOME, a także przeglądarkę Firefox zoptymalizowaną dla Twojego sprzętu. Po instalacji możesz dodatkowo spersonalizować system.
The lxd image for...
The lxd image is for use with LXD, and is not used for installing directly on a desktop or laptop, so you should not select this option for regular installs. To install, first download and then lxc image import <name>.tar.xz --alias funtoo and then you can lxc launch funtoo my_container.

Pobieranie i rozpakowanie 'stage3'

Gdy tylko znajdziesz odpowiednią paczkę, użyj wget żeby pobrać obraz, który wybrałeś jako podstawę dla nowego systemu Funtoo Linux. Powinien on zostać zapisany w katalogu /mnt/funtoo, co nastąpi po wpisaniu:

   Note

If you are using the Funtoo LiveCD, you can use a text-based browser to download your preferred stage. Type links https://build.funtoo.org rather than the wget command below. Hit enter to select the appropriate directories and stage3. 

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

Zweryfikuj pobrane archiwum (tarball)

Archiwa 'stage' są podpisane za pomocą GPG przez serwer na którym zostały stworzone. Dobrą praktyką jest weryfikacja authenticity and integrity pobranych plików, jeżeli jest to możliwe. Instrukcję, jak importować i uwierzytelniać klucze GPG, znajdziesz our wiki page about GPG signatures.

Then, you can download the stage3's GPG signature and use the gpg --verify command in order to verify your tarball: 

root # wget https://build.funtoo.org/next/x86-64bit/generic_64/stage3-latest.tar.xz.gpg
root # gpg --verify stage3-latest.tar.xz.gpg stage3-latest.tar.xz

Po pobraniu 'tarbal'a i jego weryfikacji, wyodrębnij zawartość przy pomocy następującej komendy, zastępując nazwę archiwum rzeczywistą nazwą pobranego pliku: 

root # tar --numeric-owner --xattrs --xattrs-include='*' -xpf stage3-latest.tar.xz
   Important

BARDZO WAŻNE jest użycie wszystkich parametrów zawartych wyżej. Zobacz poniżej szczegóły.

Oto, co powoduje dopisanie następującego parametru do programu tar:

--numeric-owner
Without this option, tar will map ownership and group ownership based on the UID to user and GID to group mappings as defined on the LiveCD. We don't want this -- we want the numeric values of the UIDs and GIDs in the tarball to be preserved on disk, so when your Funtoo Linux system boots, the UIDs and GIDs are set correctly for Funtoo. That is what this option tells tar to do.
--xattrs --xattrs-include='*'
Funtoo Linux uses filesystem extended attributes to set Linux capabilities, which allow for certain programs such as ping to have enhanced privileges without having to be fully 'suid root'. Even with the -p option, tar will not restore extended attributes we need unless these two options are specified.
-xpf
This instructs tar to extract (x), preserve regular permissions and ownership (p), and use the filename (f) specified.

'chroot' do nowego systemu

Żeby zainstalować Funtoo, najpierw używamy chroot. Polecenie "przełącza" na nowy system Funtoo Linux. Wpisywane odtąd komendy będą uruchomiać się na nowo rozpakowanym systemie. 

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:

Przed 'chroot'owaniem, należy wykonać kilka czynności aby skonfigurować środowisko 'chroot'. Trzeba będzie zamontować /proc, /sys oraz /dev wewnątrz nowego systemu. Aby to zrobić, użyj następujących poleceń: 

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

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

   Important

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

Pobieranie drzewa menadżera pakietów 'Portage'

Teraz nadszedł czas na zainstalowanie repozytorium - zbioru zawierającego skrypty (ebuild'y) informujące o sposobie kompilacji i instalacji tysięcy różnego rodzaju pakietów oprogramowania. W celu pobrania repozytorium uruchomiamy ego sync Spowoduje to automatyczne sklonowanie GitHub (portage tree and all kits). 

chroot # ego sync

Konfiguracja Systemu

Jak można by się spodziewać po dystrybucji Linuksa, pliki konfiguracyjne w Funtoo mają swój udział. Edycja jednego pliku jest absolutnie wymagana, żeby zapewnić pomyślny start systemu Funtoo Linux, jest to /etc/fstab. Pozostałe są opcjonalne.

Używanie edytora Nano

Domyślny edytor zawarty w środowisku 'chroot' nazywa się nano. Aby edytować jeden z plików z tabeli poniżej, uruchom 'nano' w następujący sposób: 

chroot # nano -w /etc/fstab

Kiedy jesteś w edytorze, możesz używać klawiszy strzałek aby poruszać kursorem, pospolite klawisze takie jak [BACKSPACE] i [DELETE] działają zgodnie z oczekiwaniem. Aby zapisać plik naciśnij [CTRL-X] i wybierz t kiedy wyświetli się pytanie "Zapisać zmodyfikowany bufor?".

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.

We will edit the /etc/fstab file later, when we set up the boot loader.

Pliki konfiguracyjne

Oto pełna lista plików, które możesz edytować, w zależności od Twoich potrzeb:

PlikCzy muszę edytować?Opis
/etc/fstab TAK - wymagane Punkty montowania wszystkich systemów plików używanych podczas uruchamiania systemu. Ten plik musi odzwierciedlać konfigurację partycji na dysku. Poniżej poprowadzimy Cię w celu modyfikacji tego pliku.
/etc/localtime Możesz - zalecane Twoja strefa czasowa, która jest domyślnie ustawiona na UTC jeśli nie została zmieniona. Powinien to być symboliczny link do czegoś znajdującego się w /usr/share/zoneinfo (np. /usr/share/zoneinfo/Europe/Warsaw).
/etc/portage/make.conf Możesz - zalecane Parametry używane przez gcc (kompilator), portage i make. "Zauważ że normalnym jest, gdy ten plik jest pusty, ponieważ w Funtoo wiele ustawień przeszło do naszego rozszerzonego Systemu Profili."
/etc/conf.d/hostname Możesz - zalecane Używany do ustawienia systemowej nazwy hosta. Ustaw odpowiednią zmienną hostname, jeżeli taką posiadasz (z kropkami, np. foo.funtoo.org). W przeciwnym wypadku ustaw nazwę lokalnego systemu bez kropek, np. foo. Domyślną nazwą jest localhost jeśli nie została zmieniona.
/etc/hosts NIE 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 Opcjonalnie Keyboard mapping configuration file (for console pseudo-terminals). Set if you have a non-US keyboard. See Funtoo Linux Localization.
/etc/conf.d/hwclock Opcjonalnie 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 Opcjonalnie Kernel modules to load automatically at system startup. Typically not required. See Additional Kernel Resources for more info.
/etc/conf.d/consolefont Opcjonalnie Allows you to specify the default console font. To apply this font, enable the consolefont service by running rc-update add consolefont.
profiles Opcjonalnie Some useful portage settings that may help speed up intial configuration.

Jeśli instalujesz angielską wersję Funtoo, masz szczęście, ponieważ większość plików konfiguracyjnych może być używana bez żadnych zmian. Jeżeli instalujesz system dla innego języka, nie martw się. Przeprowadzimy Cię przez niezbędne kroki konfiguracji na stronie Funtoo Linux Localization, a jeśli zajdzie taka potrzeba, zawsze znajdziesz wiele przyjaznego, pomocnego wsparcia. (Zobacz Getting Help)

Pójdźmy naprzód i zobaczmy co mamy do zrobienia. Użyj nano -w <name_of_file> do edycji plików, argument "-w" wyłącza zawijanie wierszy, co jest przydatne podczas edycji plików konfiguracyjnych. Możesz wykonać operację kopiuj-wklej z przytoczonych tutaj przykładów.

   Warning

WAŻNE JEST ŻEBY EDYTOWAĆ PLIK /etc/fstab PRZED PONOWNYM URUCHOMIENIEM KOMPUTERA!!! Potrzebujesz modyfikacji obydwu kolumn „fs” i „type”, aby dopasować ustawienia partycji i systemów plików utworzonych za pomocą gdisk albo fdisk. Ominięcie tego kroku może uniemożliwić pomyślne uruchomienie Funtoo Linux.

/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 # rm -f /etc/localtime
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/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 # ego 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 proceed
  • u - update the packages we specify -- don't emerge them again if they are already emerged.
  • D - Consider the entire dependency tree of packages when looking for updates. In other words, do a deep update.
  • N - Update any packages that have changed (new) USE settings.

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 dependency 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.

Prepare Disk

Funtoo Linux stage3's include a pre-built debian-sources kernel to make installation faster and easier. To see what kernel version is pre-installed, type: 

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

*  sys-kernel/debian-sources
      Latest version available: 5.9.6_p1
      Latest version installed: 5.9.6_p1
      Size of files: 118,723 kB
      Homepage:      https://packages.debian.org/unstable/kernel/
      Description:   Debian Sources (and optional binary kernel)
      License:       GPL-2

Firmware

At this point it is wise to emerge the latest sys-kernel/linux-firmware package, because various drivers rely on firmware blobs and instructions. Hardware like Wi-Fi cards, graphic cards, network cards, and others will not work properly or at all if firmware is not available. If using the stage3 image, perform the following to install it. linux-firmware will be already installed if using the gnome image: 

chroot # emerge -av linux-firmware

Bootloader

How Booting Works

In order for Funtoo Linux to boot, it must detect the boot filesystem, root filesystem and swap. The most reliable way to do this is to use the UUID, or unique identifier, of the partitions holding these filesystems. We will use these UUID values in the /etc/fstab, which we will set up next.

The UUID allows Linux to find the right filesystem, even if it detects the disks differently or you move them around in your computer. Funtoo Linux uses a Linux kernel and initial RAM disk to boot, and to get everything set up, we need to set up /etc/fstab correctly, and then install the GRUB boot loader -- and there are two different commands for this, depending on whether you are using MBR or UEFI. Then, finally, we run ego boot update which is a Funtoo command that configures everything for us.

Label partitions

To see the UUIDs for your existing filesystems, type the following command: 

root # ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Jan 27 13:42 6883428138129353569 -> ../../sdb1
lrwxrwxrwx 1 root root 15 Jan 27 13:42 CE4B-855D -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Jan 27 13:42 ac280eb5-1ea7-4742-9e71-9c7addd35c54 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Jan 27 13:42 e5a76428-8b3f-4349-81af-cbe29c7f7d09 -> ../../nvme0n1p3

The UUIDs are listed to the left-hand side of the ->. Use these values for setting up the /etc/fstab file, below.

/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: 

chroot # nano -w /etc/fstab
   /etc/fstab - An example fstab file
UUID=CE4B-855D                                  /boot         vfat    noauto,noatime  1 2
UUID=ac280eb5-1ea7-4742-9e71-9c7addd35c54       none          swap    sw              0 0
UUID=e5a76428-8b3f-4349-81af-cbe29c7f7d09       /             ext4    noatime         0 1
   Important

Be sure to use the actual UUIDs from your system, not the example values above!

   Note

If you mounted a /var or /home partition, add them to your fstab, or your system may not boot correctly.

boot.conf

/etc/boot.conf controls boot loader configuration in Funtoo and is used by ego boot. The default configuration is probably fine for you, so most can skip to the appropriate "GRUB Install" section, later on this page.

Here is what is in the file by default:

   /etc/boot.conf 
boot {
	generate grub
	default "Funtoo Linux"
	timeout 3
}

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

"Funtoo Linux (nomodeset)" {
	kernel kernel[-v]
	initrd initramfs[-v]
	params += real_root=auto rootfstype=auto nomodeset
}

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

nomodeset

You will notice after booting that you there will be a boot option in the GRUB menu for a "nomodeset" mode. We don't recommend you use this mode by default but it is available to you for a couple of good reasons:

  • For users with HiDPI (4K+) displays, especially laptops: If you have not set up a graphical environment, when the kernel automatically changes graphics modes, the console font can be tiny and unreadable.
  • For users with incompatible graphics cards: Some graphics cards don't handle mode setting properly and this can result in a blank screen after reboot. Use this boot option as a temporary workaround.

To use the nomodeset option, simply select that option from the GRUB menu when your system boots.

rootwait

If you are using a root partition on an nvme device, add the rootwait kernel parameter to force the kernel to wait for it to asynchronously initialize or the kernel will panic on some hardware.

Intel Microcode

ego boot will ensure that you have the most recent Intel CPU microcode installed on your system if you emerge the following packages. These will be merged for you already if you are using a desktop stage3: 

chroot # emerge -av intel-microcode iucode_tool

This is not necessary for AMD systems.

GRUB Install: 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/sdX

GRUB Install: 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 # mount -o remount,rw /sys/firmware/efi/efivars
chroot # grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck

For x86-32bit systems: 

chroot # mount -o remount,rw /sys/firmware/efi/efivars
chroot # grub-install --target=i386-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck

Ego!

Now, let's run Funtoo's ego boot update command to get everything configured. This will detect the current kernel(s) on your system and create the necessary GRUB boot entries to get your system booted: 

chroot # ego boot update

You only need to run grub-install when you first install Funtoo Linux, but you need to re-run ego boot update every time you modify your /etc/boot.conf. When you emerge updated kernels, ego boot update will be run automatically as part of the install process. This will regenerate /boot/grub/grub.cfg so that you will have new kernels available in your GRUB boot menu upon your next reboot.

Post reboot UEFI troubleshooting

In case UEFI NVRAM boot entry is missing in BIOS and grub does not start you can try moving an already installed GRUB EFI executable to the default/fallback path 

chroot # mv -v '/boot/EFI/Funtoo Linux [GRUB]' /boot/EFI/BOOT
chroot # mv -v /boot/EFI/BOOT/grubx64.efi /boot/EFI/BOOT/BOOTX64.EFI

First Boot, and in the future...

OK -- you are almost ready to boot!

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

   Note

If using the gnome or other desktop install image, linux-firmware and NetworkManager are already installed and available. You can use nmtui to get Wi-Fi going if you need network connectivity prior to getting X and GNOME fully up and running. In addition, desktop stage3's have ZeroConf/Bonjour multicast DNS lookups enabled by default. Both these things will not be set up yet if you are using the basic stage3 image.

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 if you have not done so already: 

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: 

chroot # nmtui

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

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 the supported option for network configuration, and they have their own documentation. They are optimized for static configurations and things like virtual Ethernet bridging for virtualization setups. See Funtoo Linux Networking for information on how to use Funtoo Linux's template-based network configuration system.

Hostname

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

chroot # nano /etc/conf.d/hostname

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

   Warning

Hostnames can be up to 63 characters long and may use the following characters: a-z, 0-9 and hyphens (-). However, the hyphen may not be the first or last character.

Finishing Up

Set your root password

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

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

Create a Regular User

It's also a good idea to create a regular user for daily use. If you're using GNOME, this is a requirement as you cannot log in to GDM (The GNOME Display Manager) as root. This can be accomplished as follows: 

chroot # useradd -m drobbins

You will also likely want to add your primary user to one or more supplemental groups. Here is a list of important groups and their effect:

GroupDescription
wheelAllows your user account to 'su' to root. Recommended on your primary user account for easy maintenance. Also used with sudo.
audioAllows your user account to directly access audio devices. Required if using ALSA; otherwise optional.
videoAllows your user account to directly access video devices. Required for certain video drivers and webcams.
plugdevAllows your user account work with various removable devices. Allows adding of a WiFi network in GNOME without providing root password. Recommended for desktop users.
portageAllows extended use of Portage as regular user. Recommended.

To add your user to multiple groups, use the usermod command, specifying a complete group list: 

chroot # usermod -G wheel,audio,video,plugdev,portage drobbins

As with your root account, don't forget to set a password: 

chroot # passwd drobbins
New password: **********
Retype new password: **********
passwd: password updated successfully

Install an Entropy Generator

The Linux kernel uses various sources such as user input to generate entropy, which is in turn used for generating random numbers. Encrypted communications can use a lot of entropy, and often the amount of entropy generated by your system will not be sufficient. This is commonly an issue on headless server systems, which can also include ARM systems such as Raspberry Pi, and can result in slower than normal ssh connections among other issues.

To compensate for this, a user-space entropy generator can be emerged and enabled at boot time. We will use haveged in this example, although others are available, such as rng-tools. 

chroot # emerge haveged
chroot # rc-update add haveged default

Haveged will now start at boot and will augment the Linux kernel's entropy pool.

Restart your system

Now is the time to leave fchroot, 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.

To leave the fchroot, simply type exit and you will be returned back to your LiveCD shell.

If you used manual chroot steps, you can use the following sequence of commands prepare to restart: 

chroot # exit
root # cd /mnt
root # umount -lR funtoo

Now, you are ready to reboot into Funtoo: 

root # reboot

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 TypeDescription
archTypically 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.
buildDefines whether your system is a current, stable or experimental build. At the moment, all Funtoo Linux builds use the funtoo-current build profile.
subarchDefines 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.
flavorDefines the general type of system, such as server or desktop, and will set default USE flags appropriate for your needs.
mix-insDefines 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.

   Note

It's recommended that your run this command now, particularly if you are using the gnome install image, in order to familiarize yourself with the current profile settings on your system. 

root # 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:

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

Graphics Settings

   Note

The gnome install image will have additional graphic support already enabled for you, but you will still need to set up X and your display manager (covered in the next section.)

Funtoo Linux 1.4 features the following mix-ins to allow simplified configuration of your graphics settings. It's recommended to use these mix-ins rather than manually placing USE and VIDEO_CARDS settings in /etc/make.conf. You can learn more about Funtoo's graphics configuration and the design approach of these settings at the make.conf/VIDEO_CARDS page.

Funtoo Graphics Mix-Ins

gfxcard-intel
This mix-in is equivalent to gfxcard-intel-classic or gfxcard-intel-iris, depending on the release you're running. Currently, it defaults to gfxcard-intel-classic on 1.4-release and to gfxcard-intel-classic on Next release. Do not enable more than 1 gfxcard-intel* mix-in at the same time. The result is not what you might expect.
gfxcard-intel-classic
This mix-in enables Intel graphics support based on the older i915 mesa driver (not to be confused with the i915 kernel driver). Choose this if you have a Gen3 or older chipset.
gfxcard-intel-iris
This mix-in enables Intel graphics support for cards with glamor modesetting support (drivers i965 or iris), including support OpenGL ES (>=Gen4) and OpenCL and Vulkan (>=Gen7) and video acceleration where available. If your card is >=Gen5, do an emerge libva-intel-driver or emerge media-libs/libva-intel-media-driver (for >=Gen8) afterwards to ensure you have full video acceleration support.
gfxcard-amdgpu
This mix-in enables support for modern Radeon cards, Southern Islands -- GFX Core 6 (see this x.org reference) and greater. Includes Vulkan and video acceleration where available. Drivers are built for both the Gallium framework (modern replacement for DRI framework) and DRI framework. Glamor is used to accelerate 2D operations.
gfxcard-radeon
This mix-in enables support for modern Radeon cards, R600 through Northern Islands -- GFX Core 4 and 5 (see this x.org reference). Drivers are built for the Gallium framework (modern replacement for DRI framework) as well as DRI framework. Glamor is used to accelerate 2D operations.
gfxcard-older-ati
Use this mix-in to enable support for R300 up to (but not including) R600 Radeon cards -- -- GFX Core 3 (see this x.org reference). DRI as well as Gallium-based drivers are enabled.
gfxcard-ancient-ati
Use this mix-in to enable support pre-R300 cards -- GFX Core 1 and 2 (see this x.org reference). These drivers are DRI-based.
gfxcard-nvidia
Use this to enable support for proprietary NVIDIA drivers. You will also need to emerge nvidia-kernel-modules, blacklist nouveau and add yourself to the video group. See this documentation for more details. Note that Funtoo now has two catpkgs for NVIDIA proprietary graphics -- nvidia-drivers and nvidia-kernel-modules -- to aid the use of NVIDIA acceleration on containers.
gfxcard-nvidia-legacy
Proprietary NVIDIA drivers like above, but the legacy version of the driver that supports older hardware. See https://www.nvidia.com/en-us/drivers/unix/ and browse the specific driver version that emerge is installing to get detailed compatibility information.
gfxcard-nouveau
Use this mix-in to enable support for Open Source nouveau drivers.

Enable the appropriate graphics options for your hardware as follows: 

root # epro mix-in +gfxcard-intel

Once this has been done, proceed to set up X, KDE, GNOME or another desktop environment on your system, as desired. See the next section for more information on this.

All Done!

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.

   Important

If you are using the gnome install image, please see the "A few finishing touches" section of the GNOME setup docs in order to continue setting up your graphical environment.

You may also be interested in the following resources:

  • Chroot_and_Containers setting up 32 bit containers to run wine, and STEAM.
  • Security - tips for securing your system
  • Btrfs - a simple guide for setting up btrfs on your new Funtoo Linux system.
  • 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 the First Steps Category 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.


Retrieved from "https://www.funtoo.org/index.php?title=Install/pl&oldid=37737"