Funtoo Linux Installation

2012-11-28T16:55:28Z

Jeanfrancis: /* Wi-Fi */ - Typo

== Introduction ==

This document briefly explains all of the steps required to set up a typical Funtoo Linux installation on a "PC compatible" computer system. If you've had previous experience installing Gentoo Linux then a lot of steps will be familiar, but you should still read through as there are a few differences.

=== Additional Resources ===

This document was written to help you install Funtoo Linux as efficiently as possible, with a minimum number of distracting options regarding system configuration.

Those who prefer a longer, more thorough tutorial-style installation may want to check out our beta [[Installation (Tutorial)|Installation Tutorial]] instead. It explores more installation possibilities and options such as encrypted filesystems, and includes screenshots.

An experimental Funtoo Linux build exists for [[Funtoo Linux Installation on SPARC|SPARC]] platforms. See [[Funtoo Linux Installation on SPARC]] for notable differences regarding SPARC support.

== Installation Overview ==

This is a basic overview of the Funtoo installation process:

# [[#Live CD|Download and boot the live CD of your choice]].
# [[#Prepare Hard Disk|Prepare your disk]].
# [[#Creating filesystems|Create]] and [[#Mounting filesystems|mount]] filesystems.
# [[#Installing the Stage 3 tarball|Install the Funtoo stage tarball]] of your choice.
# [[#Chroot into Funtoo|Chroot into your new system]].
# [[#Downloading the Portage tree|Download the Portage tree]].
# [[#Configuring your system|Configure your system]] and [[#Configuring your network|network]].
# [[#Configuring and installing the Linux kernel|Install a kernel]].
# [[#Installing a Bootloader|Install a bootloader]].
# [[#Finishing Steps|Complete final steps]].
# [[#Restart your system|Reboot and enjoy]].

=== Live CD ===
Funtoo doesn't provide an "official" Funtoo Live CD, but there are plenty of good ones out there to choose from. A great choice is the Gentoo-based [http://www.sysresccd.org/ SystemRescueCd] as it contains lots of tools and utilities and supports both 32-bit and 64-bit systems.

It is also possible to install Funtoo Linux using many other Linux-based live CDs. Generally, any modern bootable Linux live CD or live USB media will work. See [[Requirements|requirements]] for an overview of what the Live Media must provide to allow a problem-free install of Funtoo Linux.

To begin a Funtoo Linux installation, download and burn [http://www.sysresccd.org/ SystemRescueCd] or your preferred live media. Insert it into your disc drive, and boot from it. If using SystemRescueCd, '''be sure to select the <tt>rescue64</tt> kernel at the boot menu if you are installing a 64-bit system'''. By default, SystemRescueCd boots in 32-bit mode.

=== Prepare Hard Disk ===
==== Partitions ====

Funtoo Linux fully supports traditional MBR partitions, as well as newer GPT/GUID partition formats. Funtoo Linux recommends the use of the GPT partitioning scheme, since it is newer and more flexible. Here are the various trade-offs between each partitioning scheme:

===== GPT Partitions =====

* Newer, preferred format for Linux systems
* Supports 2 TB+ hard drives for booting
* Supports hundreds of partitions per disk of any size
* Requires legacy BIOS boot partition (~32 MB) to be created if system does not use EFI
* Requires bootloader with support for GPT such as GRUB 2, EXTLINUX, or a patched version of GRUB Legacy

===== MBR Partitions =====

* Legacy, DOS partitioning scheme
* Only 4 primary partitions per disk; after that, you must use "logical" partitions
* Does not support 2 TB+ disks for booting
* Compatible with certain problematic systems (such as the HP ProBook 4520)
* Dual-boot with Windows for BIOS systems (Windows handle GPT only on true EFI systems, whatever version it is)
* Multiple boot loader options, e.g. GRUB 2, GRUB Legacy, lilo

{{fancyimportant|If you plan to use partitions of 2 TB or greater, you ''must'' partition using the GPT/GUID format. Also note that there are small percentage of PCs that will not boot properly with GPT. For these systems, using MBR partitions or a primary drive with an MBR partition may be required in order to boot.}}

==== Partitioning Using gdisk ====

===== Notes Before We Begin =====

These install instructions assume you are installing Funtoo Linux to an empty hard disk using GUID partition tables (GPT). If you are installing Funtoo Linux on a machine where another OS is installed, or there is an existing Linux distribution on your system that you want to keep, then you will need to adapt these instructions to suit your needs.

If you are going to create a legacy MBR partition table instead of GUID/GPT, you will use the <tt>fdisk</tt> command instead of <tt>gdisk</tt>, and you will not need to create the GRUB boot loader partition. See the table under [[#Partitioning Recommendations|Partitioning Recommendations]], in particular the
'''MBR Block Device (<tt>fdisk</tt>)''' and '''MBR Code''' columns. <tt>fdisk</tt> works just like <tt>gdisk</tt>, but creates legacy MBR partition tables instead of the newer GPT/GUID partition tables.

Advanced users may be interested in the following topics:

* [[GUID Booting Guide]]
* [[Rootfs over encrypted lvm]]
* [[Rootfs over encrypted lvm over raid-1 on GPT]]

===== Using gdisk =====

The first step after booting SystemRescueCd is to use <tt>gdisk</tt> to create GPT (also known as GUID) partitions, specifying the disk you want to use, which is typically <tt>/dev/sda</tt>, the first disk in the system:

<console># ##i##gdisk /dev/sda</console>
You should find <tt>gdisk</tt> very similar to <tt>fdisk</tt>. Here is the partition table we want to end up with:

<console>Command (? for help): ##i##p
Disk /dev/sda: 234441648 sectors, 111.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): A4E5208A-CED3-4263-BB25-7147DC426931
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 234441614
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number Start (sector) End (sector) Size Code Name
1 2048 206847 500.0 MiB 8300 Linux filesystem
2 206848 272383 32.0 MiB EF02 BIOS boot partition
3 272384 8660991 4.0 GiB 8200 Linux swap
4 8660992 234441614 107.7 GiB 8300 Linux filesystem

Command (? for help): </console>

Above, you'll see that we have a 500 MiB boot partition, a 32 MiB "BIOS boot partition" (also known as the GRUB boot loader partition), 4 GiB of swap, and the remaining disk used by a 107.7 GiB root partition.

===== For new <tt>gdisk</tt> users =====

These partitions were created using the "<tt>n</tt>" command from within <tt>gdisk</tt>. The <tt>gdisk</tt> commands to create the partition table above are as follows. Adapt sizes as necessary, although these defaults will work for most users. The partition codes entered below can be found in the [[#Partitioning Recommendations|Partitioning Recommendations]] table below, in the GPT Code column.

Within <tt>gdisk</tt>, follow these steps:

'''Create Partition 1''' (boot):

<console>
Command: ##i##n ↵
Partition Number: ##i##1 ↵
First sector: ##i##↵
Last sector: ##i##+500M ↵
Hex Code: ##i##↵
</console>

'''Create Partition 2''' (GRUB):

<console>
Command: ##i##n ↵
Partition Number: ##i##2 ↵
First sector: ##i##↵
Last sector: ##i##+32M ↵
Hex Code: ##i##EF02 ↵
</console>

'''Create Partition 3''' (swap):

<console>
Command: ##i##n ↵
Partition Number: ##i##3 ↵
First sector: ##i##↵
Last sector: ##i##+4G ↵
Hex Code: ##i##8200 ↵
</console>

'''Create Partition 4''' (root):

<console>
Command: ##i##n ↵
Partition Number: ##i##4 ↵
First sector: ##i##↵
Last sector: ##i##↵##!i## (for rest of disk)
Hex Code: ##i##↵
</console>

Along the way, you can type "<tt>p</tt>" and hit Enter to view your current partition table. If you make a mistake, you can type "<tt>d</tt>" to delete an existing partition that you created. When you are satisfied with your partition setup, type "<tt>w</tt>" to write your configuration to disk:

'''Write Partition Table To Disk''':

<console>
Command: ##i##w ↵
Do you want to proceed? (Y/N): ##i##Y ↵
</console>

The partition table will now be written to disk and <tt>gdisk</tt> will close.

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

* <tt>/dev/sda1</tt>, which will be used to hold the <tt>/boot</tt> filesystem,
* <tt>/dev/sda2</tt>, which will be used directly by the new GRUB,
* <tt>/dev/sda3</tt>, which will be used for swap space, and
* <tt>/dev/sda4</tt>, which will hold your root filesystem.

===== For Previous fdisk users =====

If you have installed Gentoo Linux before, the one thing that is likely new to you here is the GRUB boot loader partition, which is listed as "BIOS boot partition" within <tt>gdisk</tt>. This partition is required for GRUB 2 to boot GPT/GUID boot disks. What is it? In GRUB-speak, this partition is essentially the location of the meat of GRUB's boot loading code. If you've used GRUB Legacy in the past, this partition is where the new GRUB stores the equivalent of the <tt>stage1_5</tt> and <tt>stage2</tt> files in legacy GRUB. Since GPT-based partition tables have less dead space at the beginning of the disk than their MBR equivalents, an explicitly defined partition of code <tt>EF02</tt> is required to hold the guts of the boot loader.

In all other respects, the partition table is similar to that which you might create for an MBR-based disk during a Gentoo Linux installation. We have a boot and a root partition with code <tt>0700</tt>, and a Linux swap partition with code <tt>8200</tt>.

===== Partitioning Recommendations =====

Below are our partitioning recommendations in table form. For GPT-based partitions, use the GPT Block Device and GPT Code columns with <tt>gdisk</tt>. For legacy MBR-based partitions, use the MBR Block Device and MBR code columns with <tt>fdisk</tt>:

{| {{table}}
!Partition
!Size
!MBR Block Device (<tt>fdisk</tt>)
!GPT Block Device (<tt>gdisk</tt>)
!Filesystem
!MBR Code
!GPT Code
|-
|<tt>/boot</tt>
|500 MB
|<tt>/dev/sda1</tt>
|<tt>/dev/sda1</tt>
|ext2
|83
|8300
|-
|GRUB boot loader partition
|32 MB
| ''not required for MBR''
|<tt>/dev/sda2</tt>
|For GPT/GUID only, skip for MBR - no filesystem.
|''N/A''
|EF02
|-
|swap
|2x RAM for low-memory systems and production servers; otherwise 2GB.
|<tt>/dev/sda2</tt>
|<tt>/dev/sda3</tt>
|swap (default)
|82
|8200
|-
|<tt>/</tt> (root)
|Rest of the disk, minimum of 10GB.
|<tt>/dev/sda3</tt>
|<tt>/dev/sda4</tt>
|XFS recommended, alternatively ext4
|83
|8300
|-
|<tt>/home</tt> (optional)
|User storage and media. Typically most of the disk.
|<tt>/dev/sda4</tt> (if created)
|<tt>/dev/sda5</tt> (if created)
|XFS recommended, alternatively ext4
|83
|8300
|-
| LVM (optional)
| If you want to create an LVM volume.
| <tt>/dev/sda4</tt> (PV, if created)
| <tt>/dev/sda5</tt> (PV, if created)
| LVM PV
| 8E
| 8E00
|}

==== Creating filesystems ====

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

You will not create a filesystem on your swap partition, but will initialize it using the <tt>mkswap</tt> command so that it can be used as disk-based virtual memory. Then we'll run the <tt>swapon</tt> command to make your newly-initialized swap space active within the live CD environment, in case it is needed during the rest of the install process.

Note that we will not create a filesystem on the GRUB boot loader partition, as GRUB writes binary data directly to that partition when the boot loader is installed, which we'll do later.

You can see the commands you will need to type below. Like the rest of this document, it assumes that you are using a GPT partitioning scheme. If you are using MBR, your root filesystem will likely be created on <tt>/dev/sda3</tt> instead and you will need to adjust the target block devices. If you are following our recommendations, then simply do this:

<console>
# ##i##mke2fs -t ext2 /dev/sda1
# ##i##mkfs.xfs /dev/sda4
# ##i##mkswap /dev/sda3
# ##i##swapon /dev/sda3
</console>

==== Mounting filesystems ====

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

<console>
# ##i##mkdir /mnt/funtoo
# ##i##mount /dev/sda4 /mnt/funtoo
# ##i##mkdir /mnt/funtoo/boot
# ##i##mount /dev/sda1 /mnt/funtoo/boot
</console>

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

<console>
# ##i##mkdir /mnt/funtoo/home
# ##i##mount /dev/sda5 /mnt/funtoo/home
</console>

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

<console>
# ##i##chmod 1777 /mnt/funtoo/tmp
</console>

=== Installing the Stage 3 tarball ===
==== Stage 3 tarball ====

After creating filesystems, 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. Visit the [[Download]] page and copy the URL to the Stage 3 tarball you want to use. We will download it soon.

{{fancyimportant|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.}}

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

<console>
# ##i##date
Fri Jul 15 19:47:18 UTC 2011
</console>

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

<console>
# ##i##date 071620002011
Fri Jul 16 20:00:00 UTC 2011
</console>

Once you are in your Funtoo Linux root filesystem, use <tt>wget</tt> to download the Stage 3 tarball you have chosen from the [[Download]] page to use as the basis for your new Funtoo Linux system. It should be saved to the <tt>/mnt/funtoo</tt> directory as follows:

<console>
# ##i##cd /mnt/funtoo
# ##i##wget http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-64bit/generic_64/stage3-latest.tar.xz
</console>

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 <tt>generic_64</tt> or <tt>generic_32</tt> stage. Consult the [[Download]] 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># ##i##tar xJpf stage3-latest.tar.xz</console>

{{fancyimportant|It is very important to use <tt>tar</tt>'s "<tt>p</tt>" option when extracting the Stage 3 tarball - it tells <tt>tar</tt> 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 ===
Before chrooting into your new system, there's a few things that need to be done first. You will need to mount /proc and /dev inside your new system. Use the following commands:
<console>
# ##i##cd /mnt/funtoo
# ##i##mount --bind /proc proc
# ##i##mount --bind /dev dev
</console>

You'll also want to copy over <tt>resolv.conf</tt> in order to have proper DNS name resolution from inside the chroot:
<console>
# ##i##cp /etc/resolv.conf etc
</console>

Now you can chroot into your new system. Use <tt>env</tt> before <tt>chroot</tt> to ensure that no environment variables from the installation media are used by your new system:

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

{{fancynote|Users of live CDs with 64-bit kernels: Some software may use <tt>uname -r</tt> 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.}}

{{fancyimportant|If you receive the error "<tt>chroot: failed to run command `/bin/bash': Exec format error</tt>", it is probably because you are running a 32-bit kernel and trying to execute 64-bit code. SystemRescueCd boots with a 32-bit kernel by default.}}

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>
# ##i##export PS1="(chroot) $PS1"
</console>

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 boot successfully when your system is restarted.

=== Downloading the Portage tree ===

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 <tt>emerge --sync</tt> from within the chroot. This will automatically clone the portage tree from [http://github.com/ GitHub]:

<console>
(chroot) # ##i##emerge --sync
</console>

{{fancynote|For an alternative way to do this, see [[Installing Portage From Snapshot]].}}

=== 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 <tt>/etc/fstab</tt>. The others are optional. Here are a list of files that you should consider editing:

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

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

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

{{fancywarning|It's important to edit your <tt>/etc/fstab</tt> 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 <tt>gdisk</tt> or <tt>fdisk</tt>. Skipping this step may prevent Funtoo Linux from booting successfully.}}

==== /etc/fstab ====

<tt>/etc/fstab</tt> is used by the <tt>mount</tt> command which is ran when your system boots. Statements of this file inform <tt>mount</tt> about partitions to be mounted and how they are mounted. In order for the system to boot properly, you must edit <tt>/etc/fstab</tt> and ensure that it reflects the partition configuration you used earlier:

<console>
(chroot) # ##i##nano -w /etc/fstab
</console>

You can use arrow keys to move around and hit Control-X to exit. If you want to save your changes, type "<tt>Y</tt>" when asked if you want to save the modified buffer, or hit Control-O before closing <tt>nano</tt>. Otherwise your changes will be discarded.

<pre>
# 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 noatime 1 2
/dev/sda3 none swap sw 0 0
/dev/sda4 / xfs noatime 0 1
#/dev/cdrom /mnt/cdrom auto noauto,ro 0 0
</pre>

==== /etc/localtime ====

<tt>/etc/localtime</tt> 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 <tt>/etc/localtime</tt> with a symbolic link to the timezone that you wish to use.

<pre>
(chroot) # ln -sf /usr/share/zoneinfo/America/Montreal /etc/localtime
</pre>

The above sets the timezone to Eastern Time Canada. Go to <tt>/usr/share/zoneinfo</tt> to see which values to use.

==== /etc/portage/make.conf ====

{{fancynote|This file may also be found at /etc/make.conf. /etc/portage/make.conf is the new location.}}

This file contains something similar to the following:

<pre>
ACCEPT_KEYWORDS="~amd64"
CHOST="x86_64-pc-linux-gnu"
</pre>

<tt>ACCEPT_KEYWORDS</tt> defines what branch of the package tree to be used. If you are using funtoo-current, it will be prefixed with a tilde ('<tt>~</tt>'). This will make more recent ebuilds visible to Portage. You should typically not change this value, and you should also not change <tt>CHOST</tt>.

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 MAKEOPTS to 3:

<pre>
MAKEOPTS="-j3"
</pre>

If you are unsure about how many processors/threads you have then use /proc/cpuinfo to help you.
<console>
(chroot) # ##i##grep "processor" /proc/cpuinfo | wc -l
16
</console>

Set MAKEOPTS to this number plus one:

<pre>
MAKEOPTS="-j17"
</pre>

USE flags define what functionality is enabled when packages are built. It is not recommended to add a lot of them during installation; you should wait until you have a working, bootable system before changing your USE flags. A USE flag prefixed with a minus ("<tt>-</tt>") 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].

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 '''clock''' 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>
(chroot) # ##i##nano -w /etc/conf.d/hwclock
</console>

==== 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]].

==== Profiles ====

[[Funtoo 1.0 Profile|Funtoo profiles]] are used to bring customization to your systems, that much quicker, think of it like not having to add two or three or ten things to your make.conf or package.use file. There are 4 basic profile types: arch, build, [[Flavors and Mix-ins|flavor, and mix-ins]]. With the exception of mix-ins you will pick one from each category. Thankfully you cannot change your architecture.

* build is essentially the stability of your system, "How bleeding edge are you?" experimental will unmask a number of masked packages. It's recommended, that you stay with current, which has keyword <tt>unmask</tt>.
* flavor is some default packages, desktop is essentially the X server, and workstation includes cups/printing.
* mix-ins are options for adding in things, like X, sound or gnome.

Remember profiles are inherited, workstation inherits desktop and desktop inherits X and audio, and so forth.

To view installed profiles:
<console>
(chroot) # ##i##eselect profile list
</console>

Adding a profile is simple:
<console>
(chroot) # ##i##eselect profile add 7
</console>

remember if you add by string; add a 'gentoo:' to the beginning of the profile name ie:
<console>
(chroot) # ##i## eselect profile add gentoo:funtoo/1.0/linux-gnu/mix-ins/console-extras
</console>

=== Configuring and installing the Linux kernel ===

Now it's time to build and install a Linux kernel, which is the heart of any Funtoo Linux system. In the past, the process of creating a kernel that actually booted your system could be time-consuming and require a great deal of trial and error. Fortunately, Funtoo Linux offers an option to automatically build a kernel for you that will boot nearly all systems.

If you are unfamiliar with how to manually configure your own kernel, or you simply want to get your system up and running quickly, you can emerge <tt>debian-sources</tt> with the <tt>binary</tt> USE flag set, which will automatically build the kernel and an initrd that will boot nearly all Funtoo Linux systems. This kernel is based on a linux-3.2 LTS official debian kernel package and is an easy way to get your system up and running relatively quickly.

{{fancyimportant|<tt>debian-sources</tt> with <tt>binary</tt> USE flag requires at least 12GB in /var/tmp}}

<console>
(chroot) # ##i##echo "sys-kernel/debian-sources binary" >> /etc/portage/package.use
(chroot) # ##i##emerge debian-sources
</console>

All done!

{{fancynote|NVIDIA card users: the <tt>binary</tt> 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 <tt>/etc/modprobe.d/</tt>.}}

For an overview of other kernel options for Funtoo Linux, see [[Funtoo Linux Kernels]]. Also be sure to see [[:Category:Hardware Compatibility|hardware compatibility]] information. We have compiled a very good reference for [[Dell PowerEdge 11G Servers]] that includes kernel compatibility information as well.

The next step is to configure your boot loader so that your new kernel loads when the system boots.

=== Installing a Bootloader ===

==== Installing Grub ====

The boot loader is responsible for loading the kernel from disk when your computer boots. For new installations, GRUB 2 and Funtoo's boot-update tool should be used as a boot loader. GRUB supports both GPT/GUID and legacy MBR partitioning schemes.

To use this recommended boot method, first emerge <tt>boot-update</tt>. This will also cause <tt>grub-2</tt> to be merged, since it is a dependency of <tt>boot-update</tt>.

<console>
(chroot) # ##i##emerge boot-update
</console>

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

<tt>/etc/boot.conf</tt> should now look like this:

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

"Funtoo Linux" {
kernel bzImage[-v]
# params += nomodeset
}

"Funtoo Linux genkernel" {
kernel kernel[-v]
initrd initramfs[-v]
params += real_root=auto
# params += nomodeset
}
</pre>

Please read <tt>man boot.conf</tt> for further details.

===== Running grub-install and boot-update =====

Finally, we will need to actually install the GRUB boot loader to your disk, and also run <tt>boot-update</tt> which will generate your boot loader configuration file:

<console>
(chroot) # ##i##grub-install --no-floppy /dev/sda
(chroot) # ##i##boot-update
</console>

You only need to run <tt>grub-install</tt> when you first install Funtoo Linux, but you need to re-run <tt>boot-update</tt> every time you modify your <tt>/etc/boot.conf</tt> file, so your changes are applied on next boot.

OK - your system should be ready to boot! Well, there are a few more loose ends...

==== Installing Syslinux/Extlinux ====

An alternate Bootloader is Extlinux, for installing it see the [[Extlinux|extlinux Guide]].

=== 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 and connecting to various networks, NetworkManager is strongly recommended. The Funtoo version of NetworkManager is fully functional even from the command-line, so you can use it even without X or without the Network Manager applet. Here are the steps involved in setting up NetworkManager:

<console>
# ##i##emerge linux-firmware
# ##i##emerge networkmanager
# ##i##rc-update add NetworkManager default
</console>

Above, we installed linux-firmware which contains a complete collection of available firmware for many hardware devices including Wi-Fi adapters, plus NetworkManager to manage our network connection. Then we added NetworkManager to the <tt>default</tt> runlevel so it will start when Funtoo Linux boots.

After you reboot into Funtoo Linux, you will be able to add a Wi-Fi connection this way:

<console>
# ##i##addwifi -S wpa -K 'wifipassword' mywifinetwork
</console>

The <tt>addwifi</tt> command is used to configure and connect to a WPA/WPA2 Wi-Fi network named <tt>mywifinetwork</tt> with the password <tt>wifipassword</tt>. This network configuration entry is stored in <tt>/etc/NetworkManager/system-connections</tt> so that it will be remembered in the future. You should only need to enter this command once for each Wi-Fi network you connect to.

==== Desktop (Wired Ethernet) ====

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

<console>
# ##i##rc-update add dhcpcd default
</console>

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

==== Server (Static IP) ====

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

=== Finishing Steps ===

==== Set your root password ====
It's imperative that you set your root password before rebooting so that you can log in.
<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 /, unmount your Funtoo partitions, and reboot.
<console>
(chroot) # exit
# ##i##cd /
# ##i##umount /mnt/funtoo/boot /mnt/funtoo/dev /mnt/funtoo/proc /mnt/funtoo
# ##i##reboot
</console>

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 <tt>login:</tt> prompt. Funtoo Linux has been successfully installed!

===Next Steps===

To learn how to customize and start using Funtoo Linux, see [[Funtoo Linux First Steps]].

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

[[Category:HOWTO]]
[[Category:Install]]

User:Jeanfrancis

2012-11-12T04:04:24Z

Jeanfrancis:

User:Jeanfrancis

2012-11-12T04:03:44Z

Jeanfrancis:

2012-10-11T16:10:29Z

Jeanfrancis:

Litecoin mining is a fun and easy way that you can help support the Funtoo Linux project. Litecoin is a virtual cryptographic currency that is generated using CPUs and video card GPU computational power, and can be converted into a traditional currency like US dollars. Typically, it is mined by pools of computers, and Funtoo is part of the ozco.in pool.

Here's how to get started and convert your idle CPU power into a contribution to the Funtoo Linux project.

=== Install Miner ===

The "miner" is the program that performs the computation to generate litecoins. It receives blocks from a server, which it performs computations on. Miners are designed to run continually in the background, where they use up idle CPU only, and will not impact the speed of your system. A significant contribution to Funtoo Linux is only realized when miners are run continually for days and weeks -- so running a miner for an hour or so is typically not effective.

=== Manual installation ===

Use your favorite CFLAGS to compile the cpuminer program. Note that <tt>-O2</tt> seems to work much better than <tt>-O3</tt>:

<console>
# ##i##wget https://github.com/downloads/pooler/cpuminer/pooler-cpuminer-2.2.3.tar.gz
# ##i##tar xf pooler-cpuminer-2.2.3.tar.gz
# ##i##cd cpuminer-2.2.3
# ##i##./configure CFLAGS="-O2 -march=corei7"
# ##i##make -j4
# ##i##cp minerd /usr/local/bin
</console>

=== Installation using Portage ===

This method will use CFLAGS from /etc/portage/make.conf. Note that <tt>-O2</tt> seems to work much better than <tt>-O3</tt>.

<console>
# ##i##emerge pooler-cpuminer
</console>

=== Set up go.sh ===

Create the following <tt>go.sh</tt> script to start the miner:

<pre>
#!/bin/bash
threads=$(cat /proc/cpuinfo | grep -c "^processor" )
while true;
do
minerd --algo scrypt -s 45 --retry-pause 5 --threads $threads --url http://lc.ozco.in:9332 --userpass funtoo.public:p
done
</pre>

Make it executable:

<console>
# ##i##chmod +x go.sh
</console>

=== Run go.sh ===

Run <tt>go.sh</tt> to start the miner. The cpuminer will only use idle CPU and will not slow down your system. Modern systems will generate somewhere from 15 to 60 KHash/sec total, which will result in $10 to Funtoo Linux per month for a Core i7 system at current exchange rates, when run continually.

=== Track our Progress ===

You can check the rank and hashrate of Funtoo on the following page: https://lc.ozco.in/stats.php

Keep those miners running and thanks for supporting Funtoo Linux!