This is a template that is used as part of the Installation instructions which covers: the process of installing the Stage3 tarball. Templates are being used to allow multiple variant install guides that use most of the same re-usable parts.
Installing the 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. Load one of the following URLs in another browser window:
- http://build.funtoo.org - Master mirror
- http://ftp.osuosl.org/pub/funtoo - US Funtoo Linux Mirror
- http://ftp.heanet.ie/mirrors/funtoo -European Funtoo Linux mirror
Now, let's navigate the directories on the mirrors to find the appropriate build of Funtoo Linux for you.
If you're not sure, pick
Funtoo Linux has various different 'builds', or variants. Here is a list of the various builds that are available, and what their distinctive features are:
|The most commonly-selected build of Funtoo Linux. Receives rapid updates and preferred by desktop users.|
|Same package set as |
|Emphasizes less-frequent package updates and trusted, reliable versions of packages over the latest versions.|
If you want to read more about this, have a look at Differences between stable, current and experimental.
If you're not sure, pick
x86-64bit, or possibly
pure64 for server systems.
For PC-compatible systems, the following choices are available:
|For modern 64-bit processors. Uses new 64-bit instructions and address space. Maintains 32-bit compatibility with multilib.|
|For modern 64-bit processors but with no support for 64-bit compatibility.|
|For older 32-bit systems such as Athlon XP, Pentium 4, or earlier Atom.|
/funtoo-current/x86-64bit/ on one of our mirrors, you'll see a bunch of directories for various subarches of Funtoo Linux.
Subarches are builds of Funtoo Linux that are designed to run on a particular type of CPU, to offer the best possible performance. They take advantage of the instruction sets available for each CPU.
For example, the
corei7-pure64 sub-arches require an Intel Core i7 processor to run (this includes Xeon x3400+ series, or other Nehalem-based CPUs such as Xeon x5500/x5600 series.)
If you are using an AMD-based CPU, download a stage3 from
If you are using an Intel-based CPU, download a stage3 from
Setting the Date
If your system's date and time are too far off (typically by months or years,) then it may prevent Portage from properly downloading source tarballs. This is because some of our sources are downloaded via HTTPS, which use SSL certificates and are marked with an activation and expiration date.
Now is a good time to verify the date and time are correctly set to UTC. Use the
date command to verify the date and time:
# date Fri Jul 15 19:47:18 UTC 2011
If the date and/or time need to be corrected, do so using
date MMDDhhmmYYYY, keeping in mind
hhmm are in 24-hour format. The example below changes the date and time to "July 16th, 2011 @ 8:00PM" UTC:
# date 071620002011 Fri Jul 16 20:00:00 UTC 2011
Download the Stage3
Once you are in your Funtoo Linux root filesystem, use
wget to download the Stage 3 tarball you have chosen to use as the basis for your new Funtoo Linux system. It should be saved to the
/mnt/funtoo directory as follows:
# cd /mnt/funtoo # wget http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-64bit/generic_64/stage3-latest.tar.xz
Note that 64-bit systems can run 32-bit or 64-bit stages, but 32-bit systems can only run 32-bit stages. Make sure that you select a Stage 3 build that is appropriate for your CPU. If you are not certain, it is a safe bet to choose the
generic_32 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:
# tar xpf stage3-latest.tar.xz
It is very important to use
p" option when extracting the Stage 3 tarball - it tells
tar to preserve any permissions and ownership that exist within the archive. Without this option, your Funtoo Linux filesystem permissions will be incorrect.