http://www.funtoo.org/api.php?action=feedcontributions&user=Oleg&feedformat=atomFuntoo Linux - User contributions [en]2013-06-20T01:45:11ZUser contributionsMediaWiki 1.20.6http://www.funtoo.org/wiki/Creating_System_Rescue_CD_ZFS_ModulesCreating System Rescue CD ZFS Modules2013-06-15T17:55:44Z<p>Oleg: /* Using the premade iso */</p>
<hr />
<div>This HOWTO will show you how to create your own zfs srm or download the prebuilt zfs srm module from my website.<br />
<br />
== Adding the overlay ==<br />
There are scripts that I've written that will make this process much easier for you. So we will first set up the overlay to a directory on your machine, let's say '''"/home/example/overlays/fearedbliss"''':<br />
<br />
<br />
<console><br />
# Make the overlays directory if it doesn't exist<br />
# ##i##mkdir /home/example/overlays<br />
<br />
# Clone my overlay into this directory<br />
# ##i##git clone git://github.com/fearedbliss/funtoo-overlay.git<br />
<br />
# Rename the "funtoo-overlay" folder to "fearedbliss"<br />
# ##i##mv funtoo-overlay fearedbliss<br />
<br />
# Add the overlay to your /etc/portage/make.conf so portage knows its existence.<br />
# ##i##echo 'PORTDIR_OVERLAY="/home/example/overlays/fearedbliss ${PORTDIR_OVERLAY}"' >> /etc/portage/make.conf<br />
</console><br />
<br />
<br />
Now that the overlay has been added, let's continue.<br />
<br />
== Compiling a compatible kernel ==<br />
<br />
The first thing you need to do is decide for which version of System Rescue CD you will be building for. Each System Rescue CD version has a different set of kernels. Specifically each version has a Stable kernel and an Alternate Kernel. The stable kernels get minor version increments every release (Sometimes major ones but usually doesn't happen too quickly), the Alternate kernels tend to move up much faster. For example System Rescue CD had the following stable/alternate kernels:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Version !! Stable !! Alternate<br />
|-<br />
| 3.7.0 || 3.4.47 || 3.9.4<br />
|-<br />
| 3.5.0 || 3.4.37 || 3.8.4<br />
|}<br />
<br />
===Download kernel and patches===<br />
Once you decide which version you want to use, you can go to http://kernel.sysresccd.org/ and pick the version you want. After you do this, download all the stuff in that directory and put them in their own folder (a work directory). The files that are named std-sources are the patches for the regular stable kernel, the patches named alt-sources are the patches for the alternate kernel. Once you have the patches, go to kernel.org and also download the initial release of the kernel sources you want. For example, if you want to build an srm for 3.4.2 which uses the 3.4.35 kernel, just download the 3.4 (3.4.0) kernel. You just need to download the initial release because one of the patches you downloaded earlier is the patch to update the 3.4.0 to 3.4.35.<br />
<br />
Once you download the kernel you want, let's extract and patch it.<br />
<br />
<console><br />
# ##i##tar xf linux-3.4.tar.bz2<br />
# ##i##mv linux-3.4 linux-3.4.35-std342-amd64<br />
# ##i##bzcat std-sources-3.4-01-stable-3.4.35.patch.bz2 | patch -p1 -d linux-3.4.35-std342-amd64<br />
# ##i##bzcat std-sources-3.4-02-fc16.patch.bz2 | patch -p1 -d linux-3.4.35-std342-amd64<br />
# ##i##bzcat std-sources-3.4-03-aufs.patch.bz2 | patch -p1 -d linux-3.4.35-std342-amd64<br />
</console><br />
<br />
===Retrieve kernel configuration===<br />
Once that is complete, you will need to get the kernel config specifically for the kernel and architecture you want. The easiest way I found to do this was to download the System Rescue CD you want, and then boot it inside a VM. Once you are inside the VM, go to the /root directory, and it will be a file named kernel-<version>.conf. Copy this file over SSH and put it in a safe location. Also copy it over into the linux kernel directory and rename it to .config.<br />
<br />
===Build the kernel===<br />
Once you copy the kernel config over, do a make menuconfig to begin. You will only need to change two settings inside the config, add the proper kernel name, and remove the old initramfs source files directory. This directory doesn't exist locally. This is a remnant of upstream's build process.<br />
<br />
Follow the below tree structure, and make it equal to what is below:<br />
<br />
<console><br />
General Setup -><br />
(-std342-amd64) Local version - append to kernel release<br />
[*] Initial RAM filesystem and RAM disk (initramfs/initrd) support () Initramfs source file(s)<br />
</console><br />
<br />
The Local version above will end up making the kernel modules directory be 3.4.35-std342-amd64. The reason the kernel modules directory has to be equal to this is because our directory will be merged into the System Rescue CD later on, so the names need to be exactly the same so that the System Rescue CD system can find our kernel modules.<br />
<br />
If you want to build an srm (which you do), you also need to change the following inside the kernel config so that squashfs-tools can work later on:<br />
<br />
<console><br />
File Systems -><br />
Miscellaneous Filesystems -><br />
<*> SquashFS 4.0 - Squashed file system support<br />
[*] Squashfs XATTR support<br />
[*] Include support for ZLIB compressed file systems<br />
[*] Include support for LZO compressed file systems<br />
[*] Include support for XZ compressed file systems<br />
[ ] Use 4K device block size?<br />
[ ] Additional option for memory-constrained systems<br />
</console><br />
<br />
Now save and exit, and continue to build your kernel.<br />
<br />
<console><br />
# ##i##make bzImage modules<br />
# ##i##make modules_install<br />
</console><br />
<br />
{{fancynote|If you have multiple cores, do a make -j<# of processors+1> to build faster. Example: '''make -j9''' for an 8 core machine.}}<br />
<br />
=== Using the overlay ===<br />
Inside the overlay, there are ebuilds already prepared that will download the kernel, patch it, and perform any required substitutions. Afterwards you literally just go into your /usr/src/<kernel> directory, and run make. To see the available versions, run the following:<br />
<br />
<console><br />
Versions available for standard kernel<br />
# ##i##equery y -O std-sources<br />
<br />
[I]3.4.37-r1 | o ~ o o o o o o o o o o o | o 3.4.37 | fearedbliss<br />
<br />
Versions available for alternate kernel<br />
# ##i##equery y -O alt-sources<br />
<br />
[I]3.8.4 | o ~ o o o o o o o o o o o | o 3.8.4 | fearedbliss<br />
</console><br />
<br />
I haven't written the ebuilds in a way where it's easy to tell (at first glance) what System Rescue CD version you need. However, you can check the ebuild and you will see the version of the CD inside there. You can also check the chart above.<br />
<br />
If you wanted to install the standard kernel sources, you just emerge it like any other application:<br />
<br />
<console><br />
# ##i##emerge std-sources<br />
</console><br />
<br />
Once the kernel and the kernel module are installed, you need to make the SRM.<br />
<br />
== Creating the SRM ==<br />
It's time to gather the required files and pack them together in order for it to become an SRM. An SRM is nothing more than a directory that has been compressed with squashfs. Thankfully I've written a script that will build it for you, and you can install it from the overlay.<br />
<br />
<br />
You also need to have spl, zfs, and zfs-kmod installed on your system before you try to make the srm. Emerging '''"bliss-initramfs"''' should automatically pull those packages. If it doesn't, make sure you install them.<br />
<br />
<console><br />
# ##i##echo "sys-kernel/bliss-initramfs srm" >> /etc/portage/package.use<br />
# ##i##emerge bliss-initramfs<br />
</console><br />
<br />
<br />
You should now have the following directory layout inside the '''/opt/bliss-initramfs''' folder:<br />
<br />
<console><br />
octopus bliss-initramfs # ls -l<br />
total 117<br />
-rw-r--r-- 1 root root 6718 May 23 18:05 CHANGES<br />
-rw-r--r-- 1 root root 176 May 23 18:05 CREDITS<br />
-rw-r--r-- 1 root root 431 May 23 18:05 HELP<br />
-rw-r--r-- 1 root root 1397 May 23 18:05 LICENSE<br />
-rw-r--r-- 1 root root 1852 May 23 18:05 README<br />
-rw-r--r-- 1 root root 3194 May 23 18:05 USAGE<br />
-rwxr-xr-x 1 root root 2891 May 23 18:05 createInit<br />
drwxr-xr-x 3 root root 4 May 23 18:11 files<br />
drwxr-xr-x 3 root root 6 May 23 18:11 hooks<br />
drwxr-xr-x 2 root root 5 May 23 22:01 resources<br />
</console><br />
<br />
<br />
Then run the '''createInit''' script and follow the instructions for the kernel you want to make the srm for (In this case it's '''3.4.37-std350-amd64'''):<br />
<br />
<console><br />
-----------------------------------<br />
| Bliss Initramfs Creator - v1.8.1<br />
| Author: Jonathan Vasquez <jvasquez1011@gmail.com><br />
| Distributed under the Simplified BSD License<br />
-----------------------------------<br />
<br />
>>> Which initramfs would you like to generate:<br />
>> 1. ZFS<br />
>> 2. Encrypted ZFS (LUKS + ZFS)<br />
>> 3. More Options<br />
>> 4. Exit Program<br />
<br />
>>> Current choice [1]: ##i##3 ↵<br />
<br />
>>> More Options:<br />
<br />
>> 1. ZFS - System Rescue Module<br />
>> 2. Back<br />
>> 3. Exit Program<br />
<br />
>>> Current choice [1]: ##i##↵<br />
<br />
>>> Creating a ZFS System Rescue Module!<br />
<br />
>>> Do you want to use the current kernel: 3.8.13-ALL? [Y/n]: ##i##n ↵<br />
<br />
>>> Please enter the kernel name: ##i##3.4.37-std350-amd64 ↵<br />
<br />
>>> Detected 64 bit platform<br />
>>> Checking to see if modules directory exists for 3.4.37-std350-amd64...<br />
>>> Creating SRMs for 3.4.37-std350-amd64...<br />
>>> Creating directory structure for initramfs...<br />
>>> Checking preliminary binaries...<br />
>>> Checking binaries...<br />
>>> Using ZFS<br />
>>> Checking modules...<br />
>>> Copying binaries...<br />
>>> Copying modules...<br />
>>> Copying documentation...<br />
>>> Copying udev rules...<br />
>>> Compressing kernel modules...<br />
>>> Getting dependencies...<br />
>>> Copying dependencies...<br />
>>> Configuring files...<br />
>>> Creating and Packing SRMs...<br />
>>> Complete :)<br />
</console><br />
<br />
<br />
Now you should have two new files:<br />
<br />
<console><br />
-rw-r--r-- 1 root root 2068480 May 24 01:05 zfs-core-3.4.37-std350-amd64.srm<br />
-rw-r--r-- 1 root root 483328 May 24 01:05 zfs-kmod-3.4.37-std350-amd64.srm<br />
</console><br />
<br />
<br />
Now all you need to do is put those two files in the root of your USB directory.<br />
<br />
If you are making srms for both the standard and alternate kernels, you will end up with two zfs-core files and two zfs-kmod files (1 set for each kernel). You don't need to put the zfs-core that it makes for one of the kernels. The zfs-core srm only has zfs program binaries, man pages, udev rules, and a few other things. The zfs-kmod is the srm that has the kernel modules (and only the kernel modules). So you can easily just put two zfs-kmods (one for each kernel version) and just re-use the same zfs-core for both of them.<br />
<br />
== Using the prebuilt srm ==<br />
<br />
=== Download the SRM ===<br />
If you didn't build your own srm and want to use the prebuilt one, just emerge '''"zfs-srm"''' from the overlay:<br />
<br />
(Instructions on [[Creating_System_Rescue_CD_ZFS_Modules#Adding_the_overlay|adding the overlay]] can be found at the top of this page)<br />
<br />
<console><br />
# ##i##emerge zfs-srm<br />
</console><br />
<br />
You can check available versions just as you did above for the kernels:<br />
<br />
<console><br />
Available versions of the zfs-srm<br />
# ##i##equery y -O zfs-srm<br />
<br />
[I]3.5.0 | o ~ o o o o o o o o o o o | o 3.5.0 | fearedbliss<br />
</console><br />
<br />
(These versions match the version of the System Rescue CD).<br />
<br />
Installing the zfs-srm will automatically pull the '''"bliss-isomaker"''' package which is just a script that assists you with rebuilding the System Rescue CD ISO so that the ISO includes the ZFS srms. The script lets you make a bootable ISO or a bootable USB.<br />
<br />
Once it's installed, switch to the /opt/bliss-isomaker folder <br />
<br />
<console><br />
# ##i##cd /opt/bliss-isomaker<br />
</console><br />
<br />
You should now see a directory layout that looks similar to this:<br />
<br />
<console><br />
octopus bliss-isomaker # ls -l<br />
total 100<br />
drwxr-xr-x 2 root root 5 May 24 01:41 3.5.0<br />
-rw-r--r-- 1 root root 1397 May 24 01:31 LICENSE<br />
-rw-r--r-- 1 root root 312 May 24 01:31 README<br />
-rw-r--r-- 1 root root 576 May 24 01:31 USAGE<br />
-rwxr-xr-x 1 root root 3228 May 24 01:31 create<br />
drwxr-xr-x 2 root root 3 May 24 01:41 iso<br />
drwxr-xr-x 2 root root 4 May 24 01:41 resources<br />
drwxr-xr-x 2 root root 3 May 24 01:41 srm<br />
</console><br />
<br />
The layout is as follows:<br />
* 3.5.0 - This folder contains the System Rescue CD 3.5.0 specific srms for both the standard and alternate kernel that were installed by emerge.<br />
* create - A script to automatically recreate the system rescue cd iso or usb with the zfs stuff included<br />
* iso - directory to place your system rescue cd iso in<br />
* srm - directory that has the srms<br />
* resources - the files in this folder contain function calls that the 'create' script uses. You don't need to worry about these.<br />
<br />
=== Installing the SRM ===<br />
There are a few ways to do this, you can either use one of the scripts, or you can do it manually. Before anything, make sure to copy the SRMs from the <Version> folder to the srm folder if you are using a prebuilt one:<br />
<br />
<console><br />
# ##i##cp 3.5.0/* srm<br />
</console><br />
<br />
==== Generating a new iso ====<br />
If you just want to remake a new iso so that you can burn onto a cd or use in a virtual machine, just copy your iso over to the iso directory, and run the 'create' script. The new iso will be located in the iso directory as well with a -zfs ending. <br />
<br />
<console><br />
Running the script with 1 (or iso) chooses to make an iso. You can also pass the version as well.<br />
# ##i##./create 1<br />
<br />
or<br />
<br />
# ##i##./create iso 3.5.0<br />
</console><br />
<br />
==== Creating a fresh usb ====<br />
If you want to have zfs on a usb with system rescue cd, put the iso in your iso dir, and then run the usb script. It will ask you what usb you want to format (This will delete everything), and then install system rescue cd onto it. Once that is done it will copy the zfs stuff over.<br />
<br />
<br />
<console><br />
Running the script with 2 (or usb) chooses to make an usb. You can also pass the version as well.<br />
# ##i##./create 2<br />
<br />
or<br />
<br />
# ##i##./create usb 3.5.0<br />
</console><br />
<br />
==== Manual installation onto a usb ====<br />
Assuming that your installing to a flash drive and that the flash drive is mounted in /mnt<br />
<br />
1. Mount your usb drive<br />
<br />
<console><br />
# ##i##mount /dev/sdX# /mnt/usbstick<br />
</console><br />
<br />
'''Where X# is the letter and number of your device. Immediately after you plug your usb in, type `dmesg | tail` in the console and you should see it.'''<br />
<br />
<br />
2. Copy the zfs .srms to /mnt/usbstick<br />
<br />
<console><br />
# ##i##cp zfs-core-3.4.37-std350-amd64.srm zfs-kmod-3.4.37-std350-amd64.srm zfs-kmod-3.8.4-alt350-amd64.srm /mnt/usbstick<br />
</console><br />
<br />
3. List your /mnt/usbstick directory and you should see something similar to the following in your /mnt/usbstick<br />
<br />
<console><br />
octopus 3.5.0 # ls -l /mnt/usbstick<br />
total 305028<br />
drwxr-xr-x 3 root root 4096 May 23 20:51 boot<br />
drwxr-xr-x 2 root root 4096 May 23 20:51 bootdisk<br />
drwxr-xr-x 2 root root 4096 May 23 20:51 bootprog<br />
drwxr-xr-x 3 root root 4096 May 23 20:51 efi<br />
drwxr-xr-x 2 root root 4096 May 23 20:51 ntpasswd<br />
-rwxr-xr-x 1 root root 2349 May 23 20:51 readme.txt<br />
drwxr-xr-x 3 root root 4096 May 23 20:52 syslinux<br />
-rwxr-xr-x 1 root root 309252096 May 23 20:51 sysrcd.dat<br />
-rwxr-xr-x 1 root root 45 May 23 20:51 sysrcd.md5<br />
drwxr-xr-x 2 root root 4096 May 23 20:51 usb_inst<br />
-rwxr-xr-x 1 root root 15889 May 23 20:51 usb_inst.sh<br />
-rwxr-xr-x 1 root root 877 May 23 20:51 usbstick.htm<br />
-rwxr-xr-x 1 root root 6 May 23 20:51 version<br />
-rwxr-xr-x 1 root root 2068480 May 23 20:51 zfs-core-3.4.37-std350-amd64.srm<br />
-rwxr-xr-x 1 root root 483328 May 23 20:51 zfs-kmod-3.4.37-std350-amd64.srm<br />
-rwxr-xr-x 1 root root 483328 May 23 20:51 zfs-kmod-3.8.4-alt350-amd64.srm<br />
</console><br />
<br />
Now un-mount your flash drive and boot it into the machine that you want to use ZFS on.<br />
<br />
<console><br />
# ##i##umount /mnt/usbstick<br />
</console><br />
<br />
== Booting into the correct kernel ==<br />
'''If you are using the standard srm:'''<br />
<console><br />
C) Standard 64bit kernel (rescue64) with more choice... ><br />
1. SystemRescueCd with default options<br />
</console><br />
<br />
'''If you are using the alternative srm:'''<br />
<console><br />
E) Alternative 64bit kernel (altker64) with more choice... ><br />
1. SystemRescueCd with default options<br />
</console><br />
<br />
2. Run 'depmod' so that the new modules can be seen by the kernel.<br />
<br />
<console><br />
# ##i##depmod<br />
</console><br />
<br />
{{fancywarning|You must run '''depmod'''. If you don't, then you will get failed to load the ZFS stack error!}}<br />
<br />
3. Use ZFS as usual. If you type '''zpool status''' and then type '''dmesg | tail''',<br />
<br />
you should see something that says:<br />
<br />
<console><br />
ZFS: Loaded module v0.6.1-1, ZFS pool version 5000, ZFS filesystem version 5<br />
</console><br />
<br />
If you see the above, then the modules loaded successfully!<br />
<br />
Enjoy System Rescue CD with ZFS :)<br />
<br />
<br />
== Using the premade iso ==<br />
<br />
<big>If you don't want to do any of the above stuff but just want the ISO with the ZFS SRMs already included, simply [http://ftp.osuosl.org/pub/funtoo/distfiles/sysresccd/systemrescuecd-x86-3.7.0-zfs.iso/ Download the ISO].</big><br />
<br />
[[Category:HOWTO]]</div>Oleghttp://www.funtoo.org/wiki/ExtlinuxExtlinux2013-06-12T15:44:39Z<p>Oleg: /* GPT */</p>
<hr />
<div>= What is ExtLinux? =<br />
<br />
ExtLinux is a pretty simple and modern systemloader, bundled with the syslinux tools, installation is really simple for it and fast, and thanks to our CoreTeam member Slashbeast the configuration runs automated in an awesome way.<br />
<br />
= Installing ExtLinux for funtoo =<br />
<br />
Installing ExtLinux for funtoo is known to work and supported too. If you like to try it just emerge syslinux<br />
<br />
<console><br />
# ##i##emerge syslinux<br />
</console><br />
<br />
with that you have the complete syslinux tools installed. Another helpful tool you should merge with syslinux is slashbeast's lazykernel tool, so let us merge it too:<br />
<br />
<console><br />
# ##i##emerge lazykernel<br />
</console><br />
<br />
== Installing extlinux ==<br />
<br />
to install extlinux just follow these steps:<br />
<br />
<console><br />
# ##i##install -d /boot/extlinux<br />
# ##i##extlinux --install /boot/extlinux<br />
# ##i##cd /boot<br />
# ##i##ln -s . boot<br />
</console><br />
<br />
the next steps are different depending if you use an MBR or GPT setup and the HDD you installed on and want to boot from. Let us now for general take /dev/sda as your boot device.<br />
<br />
=== MBR ===<br />
<br />
If you set up your disk with MBR partition scheme just do the next steps:<br />
<br />
<console><br />
# ##i##dd bs=440 conv=notrunc count=1 if=/usr/share/syslinux/mbr.bin of=/dev/sda<br />
# ##i##cp /usr/share/syslinux/menu.c32 /boot/extlinux/<br />
# ##i##cp /usr/share/syslinux/libutil.c32 /boot/extlinux/<br />
# ##i##touch /boot/extlinux/extlinux.conf<br />
</console><br />
<br />
=== GPT ===<br />
<br />
<console><br />
# ##i##sgdisk /dev/sda --attributes=1:set:2<br />
# ##i##sgdisk /dev/sda --attributes=1:show<br />
1:2:1 (legacy BIOS bootable)<br />
# ##i##dd bs=440 conv=notrunc count=1 if=/usr/share/syslinux/gptmbr.bin of=/dev/sda<br />
# ##i##cp /usr/share/syslinux/menu.c32 /boot/extlinux/<br />
# ##i##cp /usr/share/syslinux/libutil.c32 /boot/extlinux/<br />
# ##i##touch /boot/extlinux/extlinux.conf<br />
</console><br />
<br />
== Setting up the Kernel ==<br />
<br />
Now if you followed our advice to install lazykernel we have a pretty nice way to solve all the setup with a bit of prework and finish it then. If not you should go to the manual part. :)<br />
<br />
=== lazykernel way ===<br />
<br />
As you setup lazykernel, we now need to edit /etc/lazykernel.conf<br />
<br />
make it to look like somethink like that:<br />
<br />
<pre><br />
# After configuring, hash or remove line below.<br />
#CONFIGUREFIRST<br />
<br />
# Number of the kernels to keep so `lazykernel clean` will not propose to remove them. Default: 3<br />
keep_kernels=5<br />
<br />
# Sort kernels by 'version' (biggest version first) or by 'mtime' (latest images first). Default: mtime<br />
# Sorting by version may fail and 3.3.0-rc2 will be marked as newer than 3.3.0.<br />
#sort_by='version'<br />
sort_by=mtime<br />
<br />
# The name for menu entry.<br />
menu_entry_name="Funtoo Linux"<br />
<br />
# Specify what initramfs image to use, if any. (Optional)<br />
initramfs='initramfs.cpio.gz'<br />
<br />
# Append kernel params, usualy you use it to specify rootfs device, but you can use it to pass switches to initramfs as well. (Optional)<br />
#kernel_params='root=/dev/sda2'<br />
#kernel_params="rootfstype=ext4 luks enc_root=/dev/sda2 lvm root=/dev/mapper/vg-rootfs uswsusp resume=/dev/mapper/vg-swap"<br />
kernel_params="rootfstype=ext4 luks enc_root=/dev/sdb3 lvm root=/dev/mapper/vg-root uswsusp resume=/dev/mapper/vg-swap"<br />
</pre><br />
<br />
please make sure to comment out or delete the second line of the config file, else it will spit out an error for you... :)<br />
<br />
Now let us setup our kernel with lazykernel if you have a manual kernel just run:<br />
<br />
<console><br />
# ##i##cd <kernel build dir><br />
# ##i##lazykernel auto<br />
</console><br />
<br />
that will generate the modules for you, copy your kernel form /usr/src/linux over to /boot and generate the /boot/extlinux/extlinux.conf for you. The manual kernel will be the only supported one by lazykernel.<br />
<br />
That's all you are ready to boot. :)<br />
<br />
=== manual extlinux.conf ===<br />
<br />
For other kernels, like those created by genkernel or by the binary USE-flag you need to edit your config by yourself. Just open /boot/extlinux/extlinux.conf in your favorite editor and setup something like the following:<br />
<br />
<pre><br />
TIMEOUT 30<br />
UI menu.c32<br />
<br />
MENU TITLE Boot Menu<br />
MENU COLOR title 1;37;40<br />
MENU COLOR border 30;40<br />
MENU COLOR unsel 37;40<br />
<br />
LABEL funtoo1<br />
MENU LABEL Funtoo Linux KERNEL-VERSION<br />
LINUX /<kernel><br />
INITRD /<initramfs><br />
APPEND rootfstype=ext4 luks enc_root=/dev/sdb3 lvm root=/dev/mapper/vg-root uswsusp resume=/dev/mapper/vg-swap<br />
</pre><br />
<br />
That's all again you are ready for boot. You can also define several LABELs in that list to have multiple kernels been booted... :)<br />
<br />
[[Category:HOWTO]]</div>Oleghttp://www.funtoo.org/wiki/ExtlinuxExtlinux2013-06-12T15:44:14Z<p>Oleg: /* MBR */</p>
<hr />
<div>= What is ExtLinux? =<br />
<br />
ExtLinux is a pretty simple and modern systemloader, bundled with the syslinux tools, installation is really simple for it and fast, and thanks to our CoreTeam member Slashbeast the configuration runs automated in an awesome way.<br />
<br />
= Installing ExtLinux for funtoo =<br />
<br />
Installing ExtLinux for funtoo is known to work and supported too. If you like to try it just emerge syslinux<br />
<br />
<console><br />
# ##i##emerge syslinux<br />
</console><br />
<br />
with that you have the complete syslinux tools installed. Another helpful tool you should merge with syslinux is slashbeast's lazykernel tool, so let us merge it too:<br />
<br />
<console><br />
# ##i##emerge lazykernel<br />
</console><br />
<br />
== Installing extlinux ==<br />
<br />
to install extlinux just follow these steps:<br />
<br />
<console><br />
# ##i##install -d /boot/extlinux<br />
# ##i##extlinux --install /boot/extlinux<br />
# ##i##cd /boot<br />
# ##i##ln -s . boot<br />
</console><br />
<br />
the next steps are different depending if you use an MBR or GPT setup and the HDD you installed on and want to boot from. Let us now for general take /dev/sda as your boot device.<br />
<br />
=== MBR ===<br />
<br />
If you set up your disk with MBR partition scheme just do the next steps:<br />
<br />
<console><br />
# ##i##dd bs=440 conv=notrunc count=1 if=/usr/share/syslinux/mbr.bin of=/dev/sda<br />
# ##i##cp /usr/share/syslinux/menu.c32 /boot/extlinux/<br />
# ##i##cp /usr/share/syslinux/libutil.c32 /boot/extlinux/<br />
# ##i##touch /boot/extlinux/extlinux.conf<br />
</console><br />
<br />
=== GPT ===<br />
<br />
<console><br />
# ##i##sgdisk /dev/sda --attributes=1:set:2<br />
# ##i##sgdisk /dev/sda --attributes=1:show<br />
1:2:1 (legacy BIOS bootable)<br />
# ##i##dd bs=440 conv=notrunc count=1 if=/usr/share/syslinux/gptmbr.bin of=/dev/sda<br />
# ##i##cp /usr/share/syslinux/menu.c32 /boot/extlinux/<br />
# ##i##touch /boot/extlinux/extlinux.conf<br />
</console><br />
<br />
== Setting up the Kernel ==<br />
<br />
Now if you followed our advice to install lazykernel we have a pretty nice way to solve all the setup with a bit of prework and finish it then. If not you should go to the manual part. :)<br />
<br />
=== lazykernel way ===<br />
<br />
As you setup lazykernel, we now need to edit /etc/lazykernel.conf<br />
<br />
make it to look like somethink like that:<br />
<br />
<pre><br />
# After configuring, hash or remove line below.<br />
#CONFIGUREFIRST<br />
<br />
# Number of the kernels to keep so `lazykernel clean` will not propose to remove them. Default: 3<br />
keep_kernels=5<br />
<br />
# Sort kernels by 'version' (biggest version first) or by 'mtime' (latest images first). Default: mtime<br />
# Sorting by version may fail and 3.3.0-rc2 will be marked as newer than 3.3.0.<br />
#sort_by='version'<br />
sort_by=mtime<br />
<br />
# The name for menu entry.<br />
menu_entry_name="Funtoo Linux"<br />
<br />
# Specify what initramfs image to use, if any. (Optional)<br />
initramfs='initramfs.cpio.gz'<br />
<br />
# Append kernel params, usualy you use it to specify rootfs device, but you can use it to pass switches to initramfs as well. (Optional)<br />
#kernel_params='root=/dev/sda2'<br />
#kernel_params="rootfstype=ext4 luks enc_root=/dev/sda2 lvm root=/dev/mapper/vg-rootfs uswsusp resume=/dev/mapper/vg-swap"<br />
kernel_params="rootfstype=ext4 luks enc_root=/dev/sdb3 lvm root=/dev/mapper/vg-root uswsusp resume=/dev/mapper/vg-swap"<br />
</pre><br />
<br />
please make sure to comment out or delete the second line of the config file, else it will spit out an error for you... :)<br />
<br />
Now let us setup our kernel with lazykernel if you have a manual kernel just run:<br />
<br />
<console><br />
# ##i##cd <kernel build dir><br />
# ##i##lazykernel auto<br />
</console><br />
<br />
that will generate the modules for you, copy your kernel form /usr/src/linux over to /boot and generate the /boot/extlinux/extlinux.conf for you. The manual kernel will be the only supported one by lazykernel.<br />
<br />
That's all you are ready to boot. :)<br />
<br />
=== manual extlinux.conf ===<br />
<br />
For other kernels, like those created by genkernel or by the binary USE-flag you need to edit your config by yourself. Just open /boot/extlinux/extlinux.conf in your favorite editor and setup something like the following:<br />
<br />
<pre><br />
TIMEOUT 30<br />
UI menu.c32<br />
<br />
MENU TITLE Boot Menu<br />
MENU COLOR title 1;37;40<br />
MENU COLOR border 30;40<br />
MENU COLOR unsel 37;40<br />
<br />
LABEL funtoo1<br />
MENU LABEL Funtoo Linux KERNEL-VERSION<br />
LINUX /<kernel><br />
INITRD /<initramfs><br />
APPEND rootfstype=ext4 luks enc_root=/dev/sdb3 lvm root=/dev/mapper/vg-root uswsusp resume=/dev/mapper/vg-swap<br />
</pre><br />
<br />
That's all again you are ready for boot. You can also define several LABELs in that list to have multiple kernels been booted... :)<br />
<br />
[[Category:HOWTO]]</div>Oleghttp://www.funtoo.org/wiki/ZFS_Install_GuideZFS Install Guide2013-06-11T00:54:33Z<p>Oleg: /* Downloading the ISO (With ZFS) */</p>
<hr />
<div>== Introduction ==<br />
<br />
This tutorial will show you how to install Funtoo on ZFS (rootfs). This tutorial is meant to be an "overlay" over the [[Funtoo_Linux_Installation|Regular Funtoo Installation]]. Follow the normal installation and only use this guide for steps 2, 3, and 8.<br />
<br />
=== Introduction to ZFS ===<br />
<br />
Since ZFS is a new technology for Linux, it can be helpful to understand some of its benefits, particularly in comparison to BTRFS, another popular next-generation Linux filesystem:<br />
<br />
* On Linux, the ZFS code can be updated independently of the kernel to obtain the latest fixes. btrfs is exclusive to Linux and you need to build the latest kernel sources to get the latest fixes.<br />
<br />
* ZFS is supported on multiple platforms. The platforms with the best support are Solaris, FreeBSD and Linux. Other platforms with varying degrees of support are NetBSD, Mac OS X and Windows. btrfs is exclusive to Linux.<br />
<br />
* ZFS has the Adaptive Replacement Cache replacement algorithm while btrfs uses the linux kernel's Last Recently Used replacement algorithm. The former often has an overwhelmingly superior hit rate, which means fewer disk accesses.<br />
<br />
* ZFS has the ZFS Intent Log and SLOG devices, which accelerates small synchronous write performance.<br />
<br />
* ZFS handles internal fragmentation gracefully, such that you can fill it until 100%. Internal fragmentation in btrfs can make btrfs think it is full at 10%. Btrfs has no automatic rebalancing code, so it requires a manual rebalance to correct it.<br />
<br />
* ZFS has raidz, which is like RAID 5/6 (or a hypothetical RAID 7 that supports 3 parity disks), except it does not suffer from the RAID write hole issue thanks to its use of CoW and a variable stripe size. btrfs gained integrated RAID 5/6 functionality in Linux 3.9. However, its implementation uses a stripe cache that can only partially mitigate the effect of the RAID write hole.<br />
<br />
* ZFS send/receive implementation supports incremental update when doing backups. btrfs' send/receive implementation requires sending the entire snapshot.<br />
<br />
* ZFS supports data deduplication, which is a memory hog and only works well for specialized workloads. btrfs has no equivalent.<br />
<br />
* ZFS datasets have a hierarchical namespace while btrfs subvolumes have a flat namespace.<br />
<br />
* ZFS has the ability to create virtual block devices called zvols in its namespace. btrfs has no equivalent and must rely on the loop device for this functionality, which is cumbersome.<br />
<br />
The only area where btrfs is ahead of ZFS is in the area of small file<br />
efficiency. btrfs supports a feature called block suballocation, which<br />
enables it to store small files far more efficiently than ZFS. It is<br />
possible to use another filesystem (e.g. reiserfs) on top of a ZFS zvol<br />
to obtain similar benefits (with arguably better data integrity) when<br />
dealing with many small files (e.g. the portage tree).<br />
<br />
=== Disclaimers ===<br />
<br />
{{fancywarning|This guide is a work in progress. Expect some quirks.}}<br />
{{fancyimportant|'''Since ZFS was really designed for 64 bit systems, we are only recommending and supporting 64 bit platforms and installations. We will not be supporting 32 bit platforms'''!}}<br />
<br />
== Video Tutorial ==<br />
<br />
As a companion to the install instructions below, a YouTube video ZFS install tutorial is now available:<br />
<br />
{{#widget:YouTube|id=MXyBamArues|width=640|height=360}}<br />
<br />
== Downloading the ISO (With ZFS) ==<br />
In order for us to install Funtoo on ZFS, you will need an environment that provides the ZFS tools. Therefore we will download the premade System Rescue CD with ZFS SRMs (System Rescue Modules) already included.<br />
<br />
This is just a file that when combined with System Rescue CD, gives you those tools.<br />
<br />
<pre><br />
Name: systemrescuecd-x86-3.7.0-zfs (402 MiB)<br />
Release Date: 2013-06-09<br />
md5sum 62605474641ce2b1a07fec8330377208<br />
</pre><br />
<br />
<br />
'''[http://ftp.osuosl.org/pub/funtoo/distfiles/sysresccd/systemrescuecd-x86-3.7.0-zfs.iso Download System Rescue CD 3.7.0 with ZFS]'''<br /><br />
<br />
== Creating partitions ==<br />
There are two ways to partition your disk: You can use your entire drive and let ZFS automatically partition it for you, or you can do it manually.<br />
<br />
We will be showing you how to partition it '''manually''' because if you partition it manually you get to create your own layout, you get to have your own separate /boot partition (Which is nice since not every bootloader supports booting from ZFS pools), and you get to boot into RAID10, RAID5 (RAIDZ) pools and any other layouts due to you having a separate /boot partition.<br />
<br />
==== fdisk (MBR Style) ====<br />
<br />
'''A Fresh Start''':<br />
<br />
First lets make sure that the disk is completely wiped from any previous disk labels and partitions.<br />
We will also assume that <tt>/dev/sda</tt> is the target drive.<br /><br />
<br />
<console><br />
Command (m for help): ##i##o ↵<br />
Building a new DOS disklabel with disk identifier 0xbeead864.<br />
</console><br />
<br />
{{fancywarning|This is a destructive operation. Make sure you really don't want anything on this disk.}}<br />
<br />
Now that we have a clean drive, we will create the new layout.<br />
<br />
'''Create Partition 1''' (boot):<br />
<console><br />
Command: ##i##n ↵<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M ↵<br />
</console><br />
<br />
'''Create Partition 2''' (ZFS):<br />
<console><br />
Command: ##i##n ↵<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
<br />
Command: ##i##t ↵<br />
Partition number: ##i##2 ↵<br />
Hex code: ##i##bf ↵<br />
<br />
Command: ##i##p ↵<br />
<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 2048 514047 256000 83 Linux<br />
/dev/sda2 514048 1953525167 976505560 bf Solaris<br />
</console><br />
<br />
==== gdisk (GPT Style) ====<br />
<br />
'''A Fresh Start''':<br />
<br />
First lets make sure that the disk is completely wiped from any previous disk labels and partitions.<br />
We will also assume that <tt>/dev/sda</tt> is the target drive.<br /><br />
<br />
<console><br />
# ##i##gdisk /dev/sda<br />
<br />
Command: ##i##x ↵<br />
Expert command: ##i##z ↵<br />
About to wipe out GPT on /dev/sda. Proceed?: ##i##y ↵<br />
GPT data structures destroyed! You may now partition the disk using fdisk or other utilities.<br />
Blank out MBR?: ##i##y ↵<br />
</console><br />
<br />
{{fancywarning|This is a destructive operation. Make sure you really don't want anything on this disk.}}<br />
<br />
Now that we have a clean drive, we will create the new layout.<br />
<br />
'''Create Partition 1''' (boot):<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M ↵<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
'''Create Partition 2''' (BIOS Boot Partition):<br />
<console>Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+32M ↵<br />
Hex Code: ##i##EF02 ↵<br />
</console><br />
{{fancyimportant|Only make the above BIOS Boot Partition if you are using GRUB 2 on GPT. If you are using the extlinux bootloader, this partition is not necessary.}}<br />
<br />
'''Create Partition 3''' (ZFS):<br />
<console>Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
Hex Code: ##i##bf00 ↵<br />
<br />
Command: ##i##p ↵<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 514047 250.0 MiB 8300 Linux filesystem<br />
2 514048 579583 32.0 MiB EF02 BIOS boot partition<br />
3 579584 1953525134 931.2 GiB BF00 Solaris root<br />
<br />
Command: ##i##w ↵<br />
</console><br />
<br />
<br />
=== Format your boot volume ===<br />
Format your separate /boot partition:<br />
<console># ##i##mkfs.ext2 /dev/sda1</console><br />
<br />
<br />
=== Encryption (Optional) ===<br />
If you want encryption, then create your encrypted vault(s) now by doing the following:<br />
<br />
<console><br />
# ##i##cryptsetup -c aes-xts-plain64 luksFormat /dev/sda2<br />
# ##i##cryptsetup luksOpen /dev/sda2 vault_1<br />
</console><br />
<br />
{{fancyimportant|If you followed the manual GPT partitioning instructions, you should change '''/dev/sda2 to /dev/sda3'''.}}<br />
=== Create the zpool ===<br />
We will first create the pool. The pool will be named `rpool` and the disk will be aligned to 4096 (using ashift=12)<br />
<console># ##i##zpool create -f -o ashift=12 -o cachefile= -O compression=on -m none -R /mnt/funtoo rpool /dev/sda2</console><br />
<br />
{{fancyimportant|If you followed the manual GPT partitioning instructions, you should change '''/dev/sda2 to /dev/sda3'''. If you are using encrypted root, then change '''/dev/sda2 to vault_1'''.}}<br />
<br />
{{fancynote|If you have a previous pool that you would like to import, you can do a: '''zpool import -f -R /mnt/funtoo <pool_name>'''}}<br />
=== Create the zfs datasets ===<br />
We will now create some datasets. For this installation, we will create a small but future proof amount of datasets. We will have a dataset for the OS (/), and your swap. We will also show you how to create some optional datasets: /home, /var, /usr/src, and /usr/portage.<br />
<br />
<console><br />
Create some empty containers for organization purposes, and make the dataset that will hold /<br />
# ##i##zfs create -o mountpoint=none rpool/ROOT<br />
# ##i##zfs create -o mountpoint=/ rpool/ROOT/funtoo<br />
<br />
Optional, but recommended datasets: /home, /root<br />
# ##i##zfs create -o mountpoint=/home rpool/HOME<br />
# ##i##zfs create -o mountpoint=/root rpool/HOME/root<br />
<br />
Optional datasets: /usr/src, /var<br />
# ##i##zfs create -o mountpoint=none rpool/FUNTOO<br />
# ##i##zfs create -o mountpoint=/usr/src rpool/FUNTOO/src<br />
# ##i##zfs create -o mountpoint=/var rpool/FUNTOO/var<br />
</console><br />
<br />
<br />
==== Creating a separate portage dataset (optional) ====<br />
Creating a separate portage dataset could be useful if you would like to keep your portage tree, distfiles (source code files), and packages (your compiled binaries if you have FEATURES="buildpkg" enabled) in a safe place (or if you want to back up this directory up easily). <br />
<br />
Create the datasets:<br />
<br />
<console><br />
# ##i##zfs create -o mountpoint=/usr/portage -o compression=off rpool/FUNTOO/portage<br />
# ##i##zfs create -o mountpoint=/usr/portage/distfiles -o compression=off rpool/FUNTOO/distfiles<br />
</console><br />
<br />
=== Create your swap zvol ===<br />
'''Make your swap +1G greater than your RAM. An 8G machine would have 9G of SWAP (This is kinda big though).'''<br />
<console><br />
# ##i##zfs create -o sync=always -o primarycache=metadata -o secondarycache=none -o volblocksize=4K -V 9G rpool/swap<br />
</console><br />
<br />
=== Format your swap zvol ===<br />
<console><br />
# ##i##mkswap -f /dev/zvol/rpool/swap<br />
# ##i##swapon /dev/zvol/rpool/swap<br />
</console><br />
<br />
<br />
=== Last minute checks and touches ===<br />
Check to make sure everything appears fine:<br />
<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
Copy the '''zpool.cache''' file to your new environment.<br />
<console><br />
# ##i##mkdir -p /mnt/funtoo/etc/zfs<br />
# ##i##cp /etc/zfs/zpool.cache /mnt/funtoo/etc/zfs<br />
</console><br />
<br />
Make an empty mtab file<br />
<console># ##i##touch /mnt/funtoo/etc/mtab</console><br />
<br />
Now we will continue to install funtoo.<br />
<br />
== Installing Funtoo ==<br />
[[Funtoo_Linux_Installation|Download and install the Funtoo stage3 and continue installation as normal.]]<br />
<br />
Then chroot into your new funtoo environment:<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
<br />
Mount your boot drive<br />
# ##i##mount /dev/sda1 /mnt/funtoo/boot<br />
<br />
Bind the kernel related directories<br />
# ##i##mount --rbind /proc proc<br />
# ##i##mount --rbind /dev dev<br />
# ##i##mount --rbind /sys sys<br />
<br />
Copy network settings<br />
# ##i##cp /etc/resolv.conf etc/<br />
<br />
chroot into your new funtoo environment<br />
# ##i##env -i HOME=/root TERM=$TERM chroot . /bin/bash -l<br />
<br />
Sync your tree<br />
# ##i##emerge --sync<br />
</console><br />
<br />
== Kernel Configuration ==<br />
{{fancynote|The below configurations are the requirements for "Bliss Initramfs Creator". Some of these might not be needed for genkernel.}}<br />
<br />
Tested with kernels 2.6.32 - 3.9.X<br />
<br />
When you get up to the kernel, make sure that you disable the CFQ scheduler, and turn on No-op (It's the default one once you disable all schedulers). The reason for this is because ZFS has its own scheduler and the CFQ one conflicts with it. Go to your kernel config, and make sure you have the following: (there should be a /usr/src/linux symlink as well)<br />
<br />
<pre>- Linux Kernel<br />
ZLIB_INFLATE/DEFLATE must be compiled into the kernel (not as a module).<br />
> ZLIB_INFLATE [=y], ZLIB_DEFLATE [=y]<br />
<br />
General setup ---><br />
> [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support<br />
> () Initramfs source file(s)<br />
<br />
Device Drivers ---><br />
> Generic Driver Options ---><br />
>> [*] Maintain a devtmpfs filesystem to mount at /dev<br />
>> [*] Automount devtmpfs at /dev, after the kernel mounted the rootfs<br />
<br />
# Only if you want to make an SRM<br />
> File systems ---><br />
>> Miscellaneous filesystems ---><br />
>>> <*> SquashFS 4.0 - Squashed file system support<br />
>>> [*] Squashfs XATTR support<br />
>>> [*] Include support for ZLIB compressed file systems<br />
>>> [*] Include support for LZO compressed file systems<br />
>>> [*] Include support for XZ compressed file systems<br />
<br />
* All other drivers required to see your PATA/SATA drives must be compiled in.<br />
<br />
- app-arch/cpio<br />
- sys-apps/busybox<br />
- sys-kernel/spl<br />
- sys-fs/zfs<br />
- sys-fs/zfs-kmod<br />
<br />
For SRM creation:<br />
- sys-fs/squashfs-tools<br />
<br />
For LUKS support:<br />
- sys-fs/cryptsetup<br />
<br />
- Linux Kernel<br />
Device Drivers ---><br />
[*] Multiple devices driver support (RAID and LVM) ---><br />
<*> Device mapper support<br />
<*> Crypt target support<br />
<br />
Cryptographic API ---><br />
<*> XTS support<br />
-*- AES cipher algorithms<br />
</pre><br />
<br />
Continue and compile/install your kernel:<br />
<br />
<console><br />
# ##i##make bzImage modules<br />
# ##i##make install<br />
# ##i##make modules_install<br />
</console><br />
<br />
== Installing the ZFS userspace tools ==<br />
<br />
<console># ##i##emerge -av zfs</console><br />
<br />
Check to make sure that the zfs tools are working, the zpool.cache file that you copied before should be displayed.<br />
<br />
<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
If everything worked, continue.<br />
<br />
== Install the bootloader ==<br />
<br />
=== GRUB 2 ===<br />
Before you do this, make sure this checklist is followed:<br />
* Installed kernel and kernel modules<br />
* Installed zfs package from the tree<br />
* /dev, /proc, /sys are mounted in the chroot environment<br />
<br />
Once all this is checked, let's install grub2. First we need to enable the "libzfs" use flag so zfs support is compiled for grub2.<br />
<br />
<console># ##i##echo "sys-boot/grub libzfs" >> /etc/portage/package.use</console><br />
<br />
Then we will compile grub2:<br />
<br />
<console># ##i##emerge -av grub</console><br />
<br />
Once this is done, you can check that grub is version 2.00 by doing the following command:<br />
<console><br />
# ##i##grub-install --version<br />
grub-install (GRUB) 2.00<br />
</console><br />
<br />
Now try to install grub2:<br />
<console># ##i##grub-install --no-floppy /dev/sda</console><br />
<br />
You should receive the following message<br />
<console>Installation finished. No error reported.</console><br />
<br />
If not, then go back to the above checklist.<br />
<br />
=== Extlinux ===<br />
There are four things we need to do for extlinux:<br />
<br />
# Install extlinux bootloader<br />
# Write the .bin to the front of the target disk<br />
# Toggle BIOS partition flag<br />
# Write a extlinux configuration file<br />
<br />
First emerge extlinux:<br />
<console># ##i##emerge -av syslinux</console><br />
<br />
Then create a /boot/extlinux directory:<br />
<console><br />
# ##i##cd /boot<br />
# ##i##mkdir /boot/extlinux<br />
</console><br />
<br />
Change into the extlinux dir and install the bootloader:<br />
<console><br />
# ##i##cd /boot/extlinux<br />
# ##i##extlinux --install .<br />
</console><br />
<br />
==== MBR ====<br />
<console><br />
# ##i##fdisk /dev/sda<br />
<br />
Command: ##i##a ↵<br />
Partition number: ##i##1 ↵<br />
Command: ##i##w ↵<br />
</console><br />
<br />
Printing the <tt>fdisk</tt> partition layout should show a star next to <tt>/dev/sda1</tt>:<br />
<console>/dev/sda * 2048 514047 256000 83 Linux</console><br />
<br />
Flash the .bin to the front of the disk:<br />
<console># ##i##dd conv=notrunc bs=440 count=1 if=/usr/share/syslinux/mbr.bin of=/dev/sda</console><br />
<br />
=== GPT ===<br />
<console># ##i##sgdisk /dev/sda --attributes=1:set:2</console><br />
<br />
Flash the .bin to the front of the disk:<br />
<console># ##i##dd conv=notrunc bs=440 count=1 if=/usr/share/syslinux/gptmbr.bin of=/dev/sda</console><br />
<br />
We will write the extlinux/grub configuration file in the next section.<br />
<br />
=== Create a boot symlink ===<br />
We will create a boot symlink so that we can have "consistent" boot configurations without any errors.<br />
<br />
<console><br />
# ##i##cd /boot<br />
# ##i##ln -s . boot<br />
</console><br />
<br />
You should now have a symlink called 'boot' inside /boot that points to /boot :).<br />
<br />
== Create the initramfs ==<br />
There are two ways to do this, you can use genkernel, or you can use my bliss initramfs creator. I will show you both.<br />
<br />
=== genkernel ===<br />
<console><br />
# ##i##emerge -av sys-kernel/genkernel<br />
# ##i##genkernel --zfs initramfs<br />
</console><br />
<br />
<br />
<pre><br />
Example: kernel name is: vmlinuz-3.8.5-ALL<br />
initramfs name is: initramfs-genkernel-x86_64-3.8.5-ALL<br />
/boot partition is: /dev/sda1 (on GPT)<br />
pool name is: rpool<br />
</pre><br />
<br />
<br />
'''genkernel entries need verification'''<br />
'''grub.cfg''':<br />
<console><br />
set timeout=3<br />
set default=0<br />
<br />
# Funtoo<br />
menuentry "Funtoo - 3.8.5" {<br />
insmod part_gpt<br />
insmod ext2<br />
<br />
set root=(hd0,gpt1)<br />
<br />
linux /vmlinuz-3.8.5-ALL real_root=ZFS=rpool/ROOT/funtoo dozfs=force<br />
initrd /initramfs-genkernel-x86_64-3.8.5-ALL<br />
}<br />
</console><br />
<br />
<br />
If you followed the way to set up a separate partition to boot of (/dev/sda1 in this guid) you need to modify the entries in your grub.cfg, since grub will now not search inside zfs: <br />
<console><br />
set timeout=3<br />
set default=0<br />
<br />
# Funtoo<br />
menuentry "Funtoo - 3.8.5" { <br />
insmod zfs<br />
linux /vmlinuz-3.8.5-ALL real_root=ZFS=rpool/ROOT/funtoo dozfs=force<br />
initrd /initramfs-genkernel-x86_64-3.8.5-ALL<br />
}<br />
</console><br />
<br />
<br />
'''extlinux.conf''':<br />
<console><br />
LABEL funtoo<br />
MENU LABEL Funtoo 3.8.5-ALL<br />
KERNEL /vmlinuz-3.8.5-ALL<br />
INITRD /initramfs-genkernel-x86_64-3.8.5-ALL<br />
APPEND real_root=ZFS=rpool/ROOT/funtoo dozfs=force<br />
</console><br />
<br />
<br />
=== Bliss Initramfs Creator ===<br />
I've written an ebuild to install the creator for you on your machine. The ebuild is in my overlay so we will first add my overlay to your machine. <br />
<br />
First we will clone it to a directory on your machine, let's say "/home/example/overlays/fearedbliss":<br />
<br />
<console><br />
# Make the overlays directory if it doesn't exist<br />
# ##i##mkdir /home/example/overlays<br />
<br />
# Clone my overlay into this directory<br />
# ##i##git clone git://github.com/fearedbliss/funtoo-overlay.git<br />
<br />
# Rename the "funtoo-overlay" folder to "fearedbliss"<br />
# ##i##mv funtoo-overlay fearedbliss<br />
<br />
# Add the overlay to your /etc/portage/make.conf so portage knows its existence.<br />
# ##i##echo 'PORTDIR_OVERLAY="/home/example/overlays/fearedbliss ${PORTDIR_OVERLAY}"' >> /etc/portage/make.conf<br />
</console><br />
<br />
<br />
Now you can install the creator, but before we do that, if you are encrypting your drives, then add the "luks" use flag to your package.use:<br />
<br />
<console><br />
# ##i##echo "sys-kernel/bliss-initramfs luks" >> /etc/portage/package.use<br />
</console><br />
<br />
<br />
Now install the creator:<br />
<br />
<console><br />
# ##i##emerge bliss-initramfs<br />
</console><br />
<br />
<br />
Then go into the install directory, run the script as root, and place it into /boot:<br />
<console># ##i##cd /opt/bliss-initramfs<br />
# ##i##./createInit<br />
# ##i##mv initrd-<kernel_name>.img /boot<br />
</console><br />
<br />
<br />
'''<kernel_name>''' is the name of what you selected in the initramfs creator, and the name of the outputted file. Once you do this just go to your bootloader config, and add it in there.<br />
<br />
<pre><br />
Example: Kernel name is: vmlinuz-3.8.5-ALL<br />
initramfs name is: initrd-3.8.5-ALL.img<br />
/boot partition is: /dev/sda1 (on GPT)<br />
Encrypted partitions (If any, example: /dev/sda2, /dev/sdb3, /dev/sdc4)<br />
Pool root is: rpool/ROOT/funtoo<br />
</pre><br />
<br />
<br />
'''grub.cfg''':<br />
<console><br />
set timeout=3<br />
set default=0<br />
<br />
# Funtoo<br />
menuentry "Funtoo - 3.8.5" {<br />
insmod part_gpt<br />
insmod ext2<br />
<br />
set root=(hd0,gpt1)<br />
<br />
linux /vmlinuz-3.8.5-ALL root=rpool/ROOT/funtoo quiet<br />
# Let's say you have 3 drives that are encrypted, and your pool (which also contains your root) is on here<br />
# linux /vmlinuz-3.8.5-ALL root=rpool/ROOT/funtoo enc_root=/dev/sda2,/dev/sdb3,/dev/sdc4 quiet<br />
initrd /initrd-3.8.5-ALL.img<br />
}<br />
</console><br />
<br />
<br />
'''extlinux.conf:'''<br />
<console><br />
LABEL funtoo <br />
MENU LABEL Funtoo 3.8.5-ALL <br />
KERNEL /vmlinuz-3.8.5-ALL <br />
INITRD /initrd-3.8.5-ALL.img <br />
APPEND root=rpool/ROOT/funtoo quiet<br />
# Let's say you have 3 drives that are encrypted, and your pool (which also contains your root) is on here<br />
# APPEND root=rpool/ROOT/funtoo enc_root=/dev/sda2,/dev/sdb3,/dev/sdc4 quiet<br />
</console><br />
<br />
== Final configuration ==<br />
=== Add the zfs tools to openrc ===<br />
<console># ##i##rc-update add zfs boot</console><br />
<br />
=== Add filesystems to /etc/fstab ===<br />
<console><br />
# ##i##nano /etc/fstab<br />
<br />
# <fs> <mountpoint> <type> <opts> <dump/pass><br />
# Do not add the /boot line below if you are using whole-disk zfs<br />
/dev/sda1 /boot ext2 defaults 0 2<br />
/dev/zvol/rpool/swap none swap sw 0 0<br />
</console><br />
<br />
=== Clean up and reboot ===<br />
We are almost done, we are just going to clean up, '''set our root password''', and unmount whatever we mounted and get out.<br />
<br />
<console><br />
Delete the stage3/portage tarballs you downloaded earlier so they don't take up space.<br />
# ##i##cd /<br />
# ##i##rm stage3-latest.tar.xz<br />
# ##i##rm /usr/portage-latest.tar.xz<br />
<br />
Set your root password<br />
# ##i##passwd<br />
>> Enter your password, you won't see what you are writing (for security reasons), but it is there!<br />
<br />
Get out of the chroot environment<br />
# ##i##exit<br />
<br />
Unmount all the kernel filesystem stuff and boot (if you have a separate /boot)<br />
# ##i##cd /mnt/funtoo<br />
# ##i##umount -l proc dev sys boot<br />
<br />
Turn off the swap<br />
# ##i##swapoff /dev/zvol/rpool/swap<br />
<br />
Export the zpool<br />
# ##i##cd /<br />
# ##i##zpool export -f rpool<br />
<br />
Reboot<br />
# ##i##reboot<br />
</console><br />
<br />
{{fancyimportant|'''Don't forget to set your root password as stated above before exiting chroot and rebooting. If you don't set the root password, you won't be able to log into your new system.'''}}<br />
<br />
and that should be enough to get your system to boot on ZFS.<br />
<br />
== Extra: After reboot ==<br />
After you restart your machine and your inside your desktop, continue to set up anything you need in terms of /etc configurations. Once you have everything the way you like it, take a snapshot of your system. You will be using this snapshot to revert back to this state if anything ever happens to your system down the road. The snapshots are cheap, and almost instant. <br />
<br />
To take the snapshot of your rootfs, type the following:<br />
<console># ##i##zfs snapshot rpool/ROOT/funtoo@install</console><br />
<br />
To see if your snapshot was taken, type:<br />
<console># ##i##zfs list -t snapshot</console><br />
<br />
If your machine ever fails and you need to get back to this state, just type:<br />
<console># ##i##zfs rollback rpool/ROOT/funtoo@install</console><br />
<br />
[[Category:HOWTO]]<br />
[[Category:Filesystems]]<br />
[[Category:Featured]]<br />
<br />
<br />
__NOTOC__<br />
__NOTITLE__</div>Oleghttp://www.funtoo.org/wiki/WelcomeWelcome2013-06-10T04:43:18Z<p>Oleg: </p>
<hr />
<div><div style="float:right; width: 35%"><br />
{{#widget:Donate|blurb=Your support helps Funtoo grow! Donate Today.}}<br />
<div class="boxy"><br />
== Get on the UserMap! ==<br />
{{#compound_query:[[Category:People]] [[Role type::Staff]];?Geoloc;icon=Purplemarker.png;limit=9999<br />
|[[Category:People]][[Role type::Contributor]];?Geoloc;icon=Orangemarker.png;limit=9999<br />
|[[Category:People]][[Role type::User]];?Geoloc;icon=Greenmarker.png;limit=9999<br />
|format=googlemaps3|height=275|zoom=1|type=hybrid|markercluster=yes}}<br />
See our full-size [[Usermap]] and find out how to become part of the Funtoo Universe!<br />
</div><br />
{{Litecoin|blurb=Check it out: Mine litecoins for Funtoo!}}<br />
<div class="boxy"><br />
=== Latest Commits: ===<br />
<ul><br />
<feed entries=7 url="https://github.com/funtoo/funtoo-overlay/commits/master.atom"><br />
<li>[{PERMALINK} <nowiki>{TITLE}</nowiki>]<br />
</feed><br />
</ul><br />
</div><br />
<br />
<div class="boxy"><br />
=== Featured Resources: ===<br />
<DynamicPageList><br />
category = Featured<br />
</DynamicPageList><br />
</div><br />
<br />
<div class="boxy2"><br />
=== [[image:Feed-icon-28x28.png|link=http://forums.funtoo.org/extern.php?action=feed&type=atom]] Latest Forum Posts ===<br />
<ul><br />
<feed entries=6 url="http://forums.funtoo.org/extern.php?action=feed&type=atom"><br />
<li>[{PERMALINK} <nowiki>{TITLE}</nowiki>]<br />
</feed><br />
</ul><br />
</div><br />
<br />
<div class="boxy2"><br />
=== [[image:Feed-icon-28x28.png|link=http://feeds.feedburner.com/planet_larry]] Planet Larry ===<br />
<ul><br />
<feed type="planet" entries=6 url="http://feeds.feedburner.com/planet_larry"><br />
<li>[{PERMALINK} <nowiki>{TITLE}</nowiki>]<br />
</feed><br />
</ul><br />
</div><br />
<br />
<br />
</div><br />
<br />
= Welcome to the Funtoo Wiki! =<br />
<br />
[[Funtoo Linux]] is a Linux-based operating system created by [[user:Drobbins|Daniel Robbins]], the creator and former Chief Architect of Gentoo Linux. Funtoo Linux is a Free software, or "Open Source" operating system. All distribution source code is freely available, and it can be used and distributed free of charge.<br />
<br />
Who develops and improves Funtoo Linux? '''You do.''' We are a completely open, self-serve meta-distribution that centers around the needs of our users. Any user can contribute code and help improve Funtoo Linux functionality on our [http://bugs.funtoo.org bug tracker]. Submitted code is reviewed for quality by Daniel Robbins and a small group of Funtoo Linux staff.<br />
<br />
== Featured Video ==<br />
<br />
In this video, Jonathan Vasquez ([[User:Fearedbliss|fearedbliss]]) walks you through the process of installing Funtoo Linux with ZFS. See the [[ZFS Install Guide]] for detailed instructions.<br />
<br />
{{#widget:YouTube|id=SuCjLjVV800|width=640|height=360}}<br />
<br />
== Meta-Distribution, Optimized ==<br />
<br />
Funtoo Linux is also a ''meta''-distribution, which means that it is built automatically from source code and is customized with the functionality that ''you'' want it to have, and ''without'' the unnecessary features and "bloat" that you want to avoid. <br />
<br />
In addition, a Funtoo Linux system is [[Download|optimized for your CPU]], and we offer optimized versions for ''Intel Core i7'', ''Intel Atom'', ''AMD Opteron'', and other processors and architectures. <br />
<br />
These combination of factors work together to create an extremely high-performance and flexible computing platform -- a platform where ''you'' are in control, and your system performs optimally. We believe that Funtoo Linux is the most ideal expression of how operating system technology "should" work, and we continually strive to make it better.<br />
<br />
== The Gentoo Ecosystem ==<br />
<br />
We are committed to maintaining high-levels of compatibility and collaboration with the Gentoo Linux project, and challenge ourselves to innovate while providing new approaches that can be easily leveraged by the Gentoo Community. We appreciate the support we receive from members of the Gentoo Community and strive to contribute back to the larger [[Gentoo Ecosystem]].<br />
<br />
== Ultimate Flexibility for Developers ==<br />
<br />
Does your Linux distribution allow multiple versions of <tt>php</tt>, <tt>[[python]]</tt> or <tt>ruby</tt> installed happily alongside each other? Funtoo Linux does. Are you tired of hand-building key packages from source to configure them exactly the way you want? Funtoo Linux allows you to tweak the build-time features of packages using handy things called USE variables. Other distributions are forced to either leave stuff out that you want, or include stuff you don't want.<br />
<br />
== Virtualization ==<br />
<br />
We support the [[OpenVZ]] project and build up-to-date Funtoo Linux OpenVZ containers that you can [[Download|download]]. Also see [[VagrantUp]] for a nice way to deploy VirtualBox-based Funtoo Linux systems. [[Metro]], our automated distro build tool, is capable of building OpenVZ, Linux VServer and [[Linux Containers]] (LXC) images. Funtoo Linux also makes an excellent virtualization host system for [[Xen]].<br />
<br />
== Features ==<br />
<br />
[[Funtoo Linux]] features native [[wikipedia:UTF-8|UTF-8]] support enabled by default, a [[wikipedia:Git (software)|git]]-based, [[Portage Tree|distributed Portage Tree]] and funtoo overlay, an enhanced [[Portage]] with more compact mini-manifest tree, automated imports of new [http://www.gentoo.org Gentoo] changes every 12 hours, [[GUID Booting Guide|GPT/GUID boot support]] and [[Boot-Update|streamlined boot configuration]], [[Funtoo Linux Networking|enhanced network configuration]], up-to-date [http://ftp.osuosl.org/pub/funtoo/funtoo-stable/ stable] and [http://ftp.osuosl.org/pub/funtoo/funtoo-current/ current] Funtoo [[Stage Tarball|stages]], all built using Funtoo's [[Metro]] build tool. We also offer Ubuntu Server, Debian, RHEL and Fedora-based [[Funtoo Linux Kernels|kernels]].<br />
<br />
Funtoo is currently supported on the following processor families :<br />
* PC-compatible, both 32 and 64-bit (''x86-32bit'', ''x86-64bit'')<br />
<br />
== Resources ==<br />
<br />
* Learn more about [[Funtoo Linux]].<br />
* Why you should [[Choose Funtoo]]: ...and how its different than other distros.<br />
* Visit [[:Category:Projects|Funtoo Linux Projects]] and also look at the stuff online for [[Metro]].<br />
* Learn [[:Category:Linux Core Concepts| Core Linux concepts]] from articles originally written by Daniel Robbins.<br />
<br />
<br />
__NOTOC__<br />
__NOTITLE__<br />
__NOEDITSECTION__<br />
<br />
[[Category:Funtoo|*]]</div>Oleghttp://www.funtoo.org/wiki/ZFS_Install_GuideZFS Install Guide2013-06-08T18:18:20Z<p>Oleg: changed correct genkernel line (was example for freadbliss initramfs)</p>
<hr />
<div>== Introduction ==<br />
<br />
This tutorial will show you how to install Funtoo on ZFS (rootfs). This tutorial is meant to be an "overlay" over the [[Funtoo_Linux_Installation|Regular Funtoo Installation]]. Follow the normal installation and only use this guide for steps 2, 3, and 8.<br />
<br />
=== Introduction to ZFS ===<br />
<br />
Since ZFS is a new technology for Linux, it can be helpful to understand some of its benefits, particularly in comparison to BTRFS, another popular next-generation Linux filesystem:<br />
<br />
* On Linux, the ZFS code can be updated independently of the kernel to obtain the latest fixes. btrfs is exclusive to Linux and you need to build the latest kernel sources to get the latest fixes.<br />
<br />
* ZFS is supported on multiple platforms. The platforms with the best support are Solaris, FreeBSD and Linux. Other platforms with varying degrees of support are NetBSD, Mac OS X and Windows. btrfs is exclusive to Linux.<br />
<br />
* ZFS has the Adaptive Replacement Cache replacement algorithm while btrfs uses the linux kernel's Last Recently Used replacement algorithm. The former often has an overwhelmingly superior hit rate, which means fewer disk accesses.<br />
<br />
* ZFS has the ZFS Intent Log and SLOG devices, which accelerates small synchronous write performance.<br />
<br />
* ZFS handles internal fragmentation gracefully, such that you can fill it until 100%. Internal fragmentation in btrfs can make btrfs think it is full at 10%. Btrfs has no automatic rebalancing code, so it requires a manual rebalance to correct it.<br />
<br />
* ZFS has raidz, which is like RAID 5/6 (or a hypothetical RAID 7 that supports 3 parity disks), except it does not suffer from the RAID write hole issue thanks to its use of CoW and a variable stripe size. btrfs gained integrated RAID 5/6 functionality in Linux 3.9. However, its implementation uses a stripe cache that can only partially mitigate the effect of the RAID write hole.<br />
<br />
* ZFS send/receive implementation supports incremental update when doing backups. btrfs' send/receive implementation requires sending the entire snapshot.<br />
<br />
* ZFS supports data deduplication, which is a memory hog and only works well for specialized workloads. btrfs has no equivalent.<br />
<br />
* ZFS datasets have a hierarchical namespace while btrfs subvolumes have a flat namespace.<br />
<br />
* ZFS has the ability to create virtual block devices called zvols in its namespace. btrfs has no equivalent and must rely on the loop device for this functionality, which is cumbersome.<br />
<br />
The only area where btrfs is ahead of ZFS is in the area of small file<br />
efficiency. btrfs supports a feature called block suballocation, which<br />
enables it to store small files far more efficiently than ZFS. It is<br />
possible to use another filesystem (e.g. reiserfs) on top of a ZFS zvol<br />
to obtain similar benefits (with arguably better data integrity) when<br />
dealing with many small files (e.g. the portage tree).<br />
<br />
=== Disclaimers ===<br />
<br />
{{fancywarning|This guide is a work in progress. Expect some quirks.}}<br />
{{fancyimportant|'''Since ZFS was really designed for 64 bit systems, we are only recommending and supporting 64 bit platforms and installations. We will not be supporting 32 bit platforms'''!}}<br />
<br />
== Video Tutorial ==<br />
<br />
As a companion to the install instructions below, a YouTube video ZFS install tutorial is now available:<br />
<br />
{{#widget:YouTube|id=MXyBamArues|width=640|height=360}}<br />
<br />
== Setting up your environment ==<br />
In order for us to install Funtoo on ZFS, you will need an environment that provides the ZFS tools. We will be downloading two things: <br />
<br />
# System Rescue CD, <br />
# ZFS System Rescue Module (SRM)<br />
<br />
<br />
This is just a file that when combined with System Rescue CD, gives you those tools.<br />
<pre><br />
Name: SystemRescueCd-x86-3.5.0 (390 MiB)<br />
Release Date: 2013-03-25<br />
md5sum 48552b9e905872bd5061eb112b73ea20<br />
</pre><br />
<br />
<br />
Funtoo now has mirrored copies of System Rescue CD and the ZFS SRM at the links below.<br />
<br />
[http://ftp.osuosl.org/pub/funtoo/distfiles/sysrescuecd/systemrescuecd-x86-3.5.0.iso Download System Rescue CD 3.5.0]<br /><br />
[http://ftp.osuosl.org/pub/funtoo/distfiles/sysrescuecd/zfs-3.4.37-std350-amd64_0.6.1.tar.xz Download the ZFS System Rescue Module]<br />
<br />
[[Creating_System_Rescue_CD_ZFS_Modules|Follow the instructions here to download and place the srm into your flash drive]].<br />
<br />
== Creating partitions ==<br />
There are two ways to partition your disk: You can use your entire drive and let ZFS automatically partition it for you, or you can do it manually.<br />
<br />
We will be showing you how to partition it '''manually''' because if you partition it manually you get to create your own layout, you get to have your own separate /boot partition (Which is nice since not every bootloader supports booting from ZFS pools), and you get to boot into RAID10, RAID5 (RAIDZ) pools and any other layouts due to you having a separate /boot partition.<br />
<br />
==== fdisk (MBR Style) ====<br />
<br />
'''A Fresh Start''':<br />
<br />
First lets make sure that the disk is completely wiped from any previous disk labels and partitions.<br />
We will also assume that <tt>/dev/sda</tt> is the target drive.<br /><br />
<br />
<console><br />
Command (m for help): ##i##o ↵<br />
Building a new DOS disklabel with disk identifier 0xbeead864.<br />
</console><br />
<br />
{{fancywarning|This is a destructive operation. Make sure you really don't want anything on this disk.}}<br />
<br />
Now that we have a clean drive, we will create the new layout.<br />
<br />
'''Create Partition 1''' (boot):<br />
<console><br />
Command: ##i##n ↵<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M ↵<br />
</console><br />
<br />
'''Create Partition 2''' (ZFS):<br />
<console><br />
Command: ##i##n ↵<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
<br />
Command: ##i##t ↵<br />
Partition number: ##i##2 ↵<br />
Hex code: ##i##bf ↵<br />
<br />
Command: ##i##p ↵<br />
<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 2048 514047 256000 83 Linux<br />
/dev/sda2 514048 1953525167 976505560 bf Solaris<br />
</console><br />
<br />
==== gdisk (GPT Style) ====<br />
<br />
'''A Fresh Start''':<br />
<br />
First lets make sure that the disk is completely wiped from any previous disk labels and partitions.<br />
We will also assume that <tt>/dev/sda</tt> is the target drive.<br /><br />
<br />
<console><br />
# ##i##gdisk /dev/sda<br />
<br />
Command: ##i##x ↵<br />
Expert command: ##i##z ↵<br />
About to wipe out GPT on /dev/sda. Proceed?: ##i##y ↵<br />
GPT data structures destroyed! You may now partition the disk using fdisk or other utilities.<br />
Blank out MBR?: ##i##y ↵<br />
</console><br />
<br />
{{fancywarning|This is a destructive operation. Make sure you really don't want anything on this disk.}}<br />
<br />
Now that we have a clean drive, we will create the new layout.<br />
<br />
'''Create Partition 1''' (boot):<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M ↵<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
'''Create Partition 2''' (BIOS Boot Partition):<br />
<console>Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+32M ↵<br />
Hex Code: ##i##EF02 ↵<br />
</console><br />
{{fancyimportant|Only make the above BIOS Boot Partition if you are using GRUB 2 on GPT. If you are using the extlinux bootloader, this partition is not necessary.}}<br />
<br />
'''Create Partition 3''' (ZFS):<br />
<console>Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
Hex Code: ##i##bf00 ↵<br />
<br />
Command: ##i##p ↵<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 514047 250.0 MiB 8300 Linux filesystem<br />
2 514048 579583 32.0 MiB EF02 BIOS boot partition<br />
3 579584 1953525134 931.2 GiB BF00 Solaris root<br />
<br />
Command: ##i##w ↵<br />
</console><br />
<br />
=== Format your boot volume ===<br />
Format your separate /boot partition:<br />
<console># ##i##mkfs.ext2 /dev/sda1</console><br />
<br />
=== Create the zpool ===<br />
We will first create the pool. The pool will be named `rpool` and the disk will be aligned to 4096 (using ashift=12)<br />
<br />
<console># ##i##zpool create -f -o ashift=12 -o cachefile= -O compression=on -m none -R /mnt/funtoo rpool /dev/sda2</console><br />
{{fancyimportant|If you followed the manual GPT partitioning instructions, you should change /dev/sda2 to /dev/sda3.}}{{fancynote|If you have a previous pool that you would like to import, you can do a: '''zpool import -f -R /mnt/funtoo <pool_name>'''}}<br />
<br />
=== Create the zfs datasets ===<br />
We will now create some datasets. For this installation, we will create a small but future proof amount of datasets. We will have a dataset for the OS (/), and your swap. We will also show you how to create some optional datasets: /home, /var, /usr/src, and /usr/portage.<br />
<br />
<console><br />
Create some empty containers for organization purposes, and make the dataset that will hold /<br />
# ##i##zfs create -o mountpoint=none rpool/ROOT<br />
# ##i##zfs create -o mountpoint=/ rpool/ROOT/funtoo<br />
<br />
Optional, but recommended datasets: /home, /root<br />
# ##i##zfs create -o mountpoint=/home rpool/HOME<br />
# ##i##zfs create -o mountpoint=/root rpool/HOME/root<br />
<br />
Optional datasets: /usr/src, /var<br />
# ##i##zfs create -o mountpoint=none rpool/FUNTOO<br />
# ##i##zfs create -o mountpoint=/usr/src rpool/FUNTOO/src<br />
# ##i##zfs create -o mountpoint=/var rpool/FUNTOO/var<br />
</console><br />
<br />
<br />
==== Creating a separate portage dataset (optional) ====<br />
Creating a separate portage dataset could be useful if you would like to keep your portage tree, distfiles (source code files), and packages (your compiled binaries if you have FEATURES="buildpkg" enabled) in a safe place (or if you want to back up this directory up easily). <br />
<br />
Create the datasets:<br />
<br />
<console><br />
# ##i##zfs create -o mountpoint=/usr/portage -o compression=off rpool/FUNTOO/portage<br />
# ##i##zfs create -o mountpoint=/usr/portage/distfiles -o compression=off rpool/FUNTOO/distfiles<br />
</console><br />
<br />
=== Create your swap zvol ===<br />
'''Make your swap +1G greater than your RAM. An 8G machine would have 9G of SWAP (This is kinda big though).'''<br />
<console><br />
# ##i##zfs create -o sync=always -o primarycache=metadata -o secondarycache=none -o volblocksize=4K -V 9G rpool/swap<br />
</console><br />
<br />
=== Format your swap zvol ===<br />
<console><br />
# ##i##mkswap -f /dev/zvol/rpool/swap<br />
# ##i##swapon /dev/zvol/rpool/swap<br />
</console><br />
<br />
<br />
=== Last minute checks and touches ===<br />
Check to make sure everything appears fine:<br />
<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
Copy the '''zpool.cache''' file to your new environment.<br />
<console><br />
# ##i##mkdir -p /mnt/funtoo/etc/zfs<br />
# ##i##cp /etc/zfs/zpool.cache /mnt/funtoo/etc/zfs<br />
</console><br />
<br />
Make an empty mtab file<br />
<console># ##i##touch /mnt/funtoo/etc/mtab</console><br />
<br />
Now we will continue to install funtoo.<br />
<br />
== Installing Funtoo ==<br />
[[Funtoo_Linux_Installation|Download and install the Funtoo stage3 and continue installation as normal.]]<br />
<br />
Then chroot into your new funtoo environment:<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
<br />
Mount your boot drive<br />
# ##i##mount /dev/sda1 /mnt/funtoo/boot<br />
<br />
Bind the kernel related directories<br />
# ##i##mount --rbind /proc proc<br />
# ##i##mount --rbind /dev dev<br />
# ##i##mount --rbind /sys sys<br />
<br />
Copy network settings<br />
# ##i##cp /etc/resolv.conf etc/<br />
<br />
chroot into your new funtoo environment<br />
# ##i##env -i HOME=/root TERM=$TERM chroot . /bin/bash -l<br />
<br />
Sync your tree<br />
# ##i##emerge --sync<br />
</console><br />
<br />
== Kernel Configuration ==<br />
{{fancynote|The below configurations are the requirements for "Bliss Initramfs Creator". Some of these might not be needed for genkernel.}}<br />
<br />
Tested with kernel 2.6.32, 3.2.34, 3.6.X, 3.7.X, 3.8.X.<br />
<br />
When you get up to the kernel, make sure that you disable the CFQ scheduler, and turn on No-op (It's the default one once you disable all schedulers). The reason for this is because ZFS has its own scheduler and the CFQ one conflicts with it. Go to your kernel config, and make sure you have the following: (there should be a /usr/src/linux symlink as well)<br />
<br />
<pre>ZLIB_INFLATE/DEFLATE must be compiled into the kernel (not as a module).<br />
> ZLIB_INFLATE [=y], ZLIB_DEFLATE [=y]<br />
<br />
General setup ---><br />
> [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support<br />
> () Initramfs source file(s)<br />
<br />
[*] Enable loadable module support ---><br />
[*] Module unloading<br />
<br />
Device Drivers ---><br />
> Generic Driver Options ---><br />
>> [*] Maintain a devtmpfs filesystem to mount at /dev<br />
<br />
Cryptographic API ---><br />
<*> Deflate compression algorithm<br />
<*> Zlib compression algorithm<br />
<br />
* All other drivers required to see your PATA/SATA drives must be compiled in.</pre><br />
<br />
Continue and compile/install your kernel:<br />
<console><br />
# ##i##make bzImage modules<br />
# ##i##make install<br />
# ##i##make modules_install<br />
</console><br />
<br />
== Installing the ZFS userspace tools ==<br />
<br />
<console># ##i##emerge -av zfs</console><br />
<br />
Check to make sure that the zfs tools are working, the zpool.cache file that you copied before should be displayed.<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
If everything worked, continue.<br />
<br />
== Install the bootloader ==<br />
<br />
=== GRUB 2 ===<br />
Before you do this, make sure this checklist is followed:<br />
* Installed kernel and kernel modules<br />
* Installed zfs package from the tree<br />
* /dev, /proc, /sys are mounted in the chroot environment<br />
<br />
Once all this is checked, let's install grub2. First we need to enable the "libzfs" use flag so zfs support is compiled for grub2.<br />
<br />
<console># ##i##echo "sys-boot/grub libzfs" >> /etc/portage/package.use</console><br />
<br />
Then we will compile grub2:<br />
{{fancyimportant|GRUB should be _at least_ version 2.0.0 since 2.0.0 added zfs support. 1.99,.98 will not work.}}<br />
<console># ##i##emerge -av grub</console><br />
<br />
Once this is done, you can check that grub is version 2.00 by doing the following command:<br />
<console><br />
# ##i##grub-install --version<br />
grub-install (GRUB) 2.00<br />
</console><br />
<br />
Now try to install grub2:<br />
<console># ##i##grub-install --no-floppy /dev/sda</console><br />
<br />
You should receive the following message<br />
<console>Installation finished. No error reported.</console><br />
<br />
If not, then go back to the above checklist.<br />
=== Extlinux ===<br />
There are four things we need to do for extlinux:<br />
<br />
# Install extlinux bootloader<br />
# Write the .bin to the front of the target disk<br />
# Toggle BIOS partition flag<br />
# Write a extlinux configuration file<br />
<br />
First emerge extlinux:<br />
<console># ##i##emerge -av syslinux</console><br />
<br />
Then create a /boot/extlinux directory:<br />
<console><br />
# ##i##cd /boot<br />
# ##i##mkdir /boot/extlinux<br />
</console><br />
<br />
Change into the extlinux dir and install the bootloader:<br />
<console><br />
# ##i##cd /boot/extlinux<br />
# ##i##extlinux --install .<br />
</console><br />
<br />
==== MBR ====<br />
<console><br />
# ##i##fdisk /dev/sda<br />
<br />
Command: ##i##a ↵<br />
Partition number: ##i##1 ↵<br />
Command: ##i##w ↵<br />
</console><br />
<br />
Printing the <tt>fdisk</tt> partition layout should show a star next to <tt>/dev/sda1</tt>:<br />
<console>/dev/sda * 2048 514047 256000 83 Linux</console><br />
<br />
Flash the .bin to the front of the disk:<br />
<console># ##i##dd conv=notrunc bs=440 count=1 if=/usr/share/syslinux/mbr.bin of=/dev/sda</console><br />
<br />
=== GPT ===<br />
<console># ##i##sgdisk /dev/sda --attributes=1:set:2</console><br />
<br />
Flash the .bin to the front of the disk:<br />
<console># ##i##dd conv=notrunc bs=440 count=1 if=/usr/share/syslinux/gptmbr.bin of=/dev/sda</console><br />
<br />
We will write the extlinux/grub configuration file in the next section.<br />
<br />
=== Create a boot symlink ===<br />
We will create a boot symlink so that we can have "consistent" boot configurations without any errors.<br />
<br />
<console><br />
# ##i##cd /boot<br />
# ##i##ln -s . boot<br />
</console><br />
<br />
You should now have a symlink called 'boot' inside /boot that points to /boot :).<br />
<br />
== Create the initramfs ==<br />
There are two ways to do this, you can use genkernel, or you can use my bliss initramfs creator. I will show you both.<br />
<br />
=== genkernel ===<br />
<console><br />
# ##i##emerge -av sys-kernel/genkernel<br />
# ##i##genkernel --zfs initramfs<br />
</console><br />
<br />
<br />
<pre><br />
Example: kernel name is: vmlinuz-3.8.5-ALL<br />
initramfs name is: initramfs-genkernel-x86_64-3.8.5-ALL<br />
/boot partition is: /dev/sda1 (on GPT)<br />
pool name is: rpool<br />
</pre><br />
<br />
<br />
'''genkernel entries need verification'''<br />
'''grub.cfg''':<br />
<console><br />
set timeout=3<br />
set default=0<br />
<br />
# Funtoo<br />
menuentry "Funtoo - 3.8.5" {<br />
insmod part_gpt<br />
insmod ext2<br />
<br />
set root=(hd0,gpt1)<br />
<br />
linux /boot/vmlinuz-3.8.5-ALL real_root=ZFS=rpool/ROOT/funtoo dozfs=force<br />
initrd /boot/initramfs-genkernel-x86_64-3.8.5-ALL<br />
}<br />
</console><br />
<br />
If you followed the way to set up a separate partition to boot of (/dev/sda1 in this guid) you need to modify the entries in your grub.cfg, since grub will now not search inside zfs: <br />
<console><br />
set timeout=3<br />
set default=0<br />
<br />
# Funtoo<br />
menuentry "Funtoo - 3.8.5" { <br />
insmod zfs<br />
linux /vmlinuz-3.8.5-ALL real_root=ZFS=rpool/ROOT/funtoo dozfs=force<br />
initrd /initramfs-genkernel-x86_64-3.8.5-ALL<br />
}<br />
</console><br />
<br />
'''extlinux.conf''':<br />
<console><br />
LABEL funtoo<br />
MENU LABEL Funtoo 3.8.5-ALL<br />
KERNEL /boot/vmlinuz-3.8.5-ALL<br />
INITRD /boot/initramfs-genkernel-x86_64-3.8.5-ALL<br />
APPEND real_root=ZFS=rpool/ROOT/funtoo dozfs=force<br />
</console><br />
<br />
=== Bliss Initramfs Creator ===<br />
I've written an ebuild to install the creator for you on your machine. The ebuild is in my overlay so we will first add my overlay to your machine. <br />
<br />
First we will clone it to a directory on your machine, let's say "/home/example/overlays/fearedbliss":<br />
<br />
<console><br />
# Make the overlays directory if it doesn't exist<br />
# ##i##mkdir /home/example/overlays<br />
<br />
# Clone my overlay into this directory<br />
# ##i##git clone git://github.com/fearedbliss/funtoo-overlay.git<br />
<br />
# Rename the "funtoo-overlay" folder to "fearedbliss"<br />
# ##i##mv funtoo-overlay fearedbliss<br />
<br />
# Add the overlay to your /etc/portage/make.conf so portage knows its existence.<br />
# ##i##echo 'PORTDIR_OVERLAY="/home/example/overlays/fearedbliss ${PORTDIR_OVERLAY}"' >> /etc/portage/make.conf<br />
</console><br />
<br />
Now you can install the creator with the following command:<br />
<br />
<console><br />
# ##i##emerge bliss-initramfs<br />
</console><br />
<br />
Then go into the install directory, run the script as root, and place it into /boot:<br />
<console># ##i##cd /opt/bliss-initramfs<br />
# ##i##./createInit<br />
# ##i##mv initrd-<kernel_name>.img /boot<br />
</console><br />
<br />
'''<kernel_name>''' is the name of what you selected in the initramfs creator, and the name of the outputted file. Once you do this just go to your bootloader config, and add it in there.<br />
<br />
<pre><br />
Example: Kernel name is: vmlinuz-3.8.5-ALL<br />
initramfs name is: initrd-3.8.5-ALL.img<br />
/boot partition is: /dev/sda1 (on GPT)<br />
Pool root is: rpool/ROOT/funtoo<br />
</pre><br />
<br />
'''grub.cfg''':<br />
<console><br />
set timeout=3<br />
set default=0<br />
<br />
# Funtoo<br />
menuentry "Funtoo - 3.8.5" {<br />
insmod part_gpt<br />
insmod ext2<br />
<br />
set root=(hd0,gpt1)<br />
<br />
linux /boot/vmlinuz-3.8.5-ALL root=rpool/ROOT/funtoo quiet<br />
initrd /boot/initrd-3.8.5-ALL.img<br />
}<br />
</console><br />
<br />
'''extlinux.conf:'''<br />
<console><br />
LABEL funtoo <br />
MENU LABEL Funtoo 3.8.5-ALL <br />
KERNEL /boot/vmlinuz-3.8.5-ALL <br />
INITRD /boot/initrd-3.8.5-ALL.img <br />
APPEND root=rpool/ROOT/funtoo quiet<br />
</console><br />
<br />
== Final configuration ==<br />
=== Add the zfs tools to openrc ===<br />
<console># ##i##rc-update add zfs boot</console><br />
<br />
=== Add filesystems to /etc/fstab ===<br />
<console><br />
# ##i##nano /etc/fstab<br />
<br />
# <fs> <mountpoint> <type> <opts> <dump/pass><br />
# Do not add the /boot line below if you are using whole-disk zfs<br />
/dev/sda1 /boot ext2 defaults 0 2<br />
/dev/zvol/rpool/swap none swap sw 0 0<br />
</console><br />
<br />
=== Clean up and reboot ===<br />
We are almost done, we are just going to clean up, '''set our root password''', and unmount whatever we mounted and get out.<br />
<br />
<console><br />
Delete the stage3/portage tarballs you downloaded earlier so they don't take up space.<br />
# ##i##cd /<br />
# ##i##rm stage3-latest.tar.xz<br />
# ##i##rm /usr/portage-latest.tar.xz<br />
<br />
Set your root password<br />
# ##i##passwd<br />
>> Enter your password, you won't see what you are writing (for security reasons), but it is there!<br />
<br />
Get out of the chroot environment<br />
# ##i##exit<br />
<br />
Unmount all the kernel filesystem stuff and boot (if you have a separate /boot)<br />
# ##i##cd /mnt/funtoo<br />
# ##i##umount -l proc dev sys boot<br />
<br />
Turn off the swap<br />
# ##i##swapoff /dev/zvol/rpool/swap<br />
<br />
Export the zpool<br />
# ##i##cd /<br />
# ##i##zpool export -f rpool<br />
<br />
Reboot<br />
# ##i##reboot<br />
</console><br />
<br />
{{fancyimportant|'''Don't forget to set your root password as stated above before exiting chroot and rebooting. If you don't set the root password, you won't be able to log into your new system.'''}}<br />
<br />
and that should be enough to get your system to boot on ZFS.<br />
<br />
== Extra: After reboot ==<br />
After you restart your machine and your inside your desktop, continue to set up anything you need in terms of /etc configurations. Once you have everything the way you like it, take a snapshot of your system. You will be using this snapshot to revert back to this state if anything ever happens to your system down the road. The snapshots are cheap, and almost instant. <br />
<br />
To take the snapshot of your rootfs, type the following:<br />
<console># ##i##zfs snapshot rpool/ROOT/funtoo@install</console><br />
<br />
To see if your snapshot was taken, type:<br />
<console># ##i##zfs list -t snapshot</console><br />
<br />
If your machine ever fails and you need to get back to this state, just type:<br />
<console># ##i##zfs rollback rpool/ROOT/funtoo@install</console><br />
<br />
=== Recovery Environment ===<br />
On ZFS it is extremely easy to create a recovery environment using an already working snapshot. So that's what we will be doing. Create a clone of the @install snapshot which you will use for recovery purposes. If something happens to your main install, you can boot into this clone and fix the main one. One of the differences (maybe the only difference) between a clone and a snapshot is that a clone is rewritable while a snapshot is only read-only.<br />
<br />
<console># ##i##zfs clone rpool/ROOT/funtoo@install rpool/ROOT/recovery</console><br />
<br />
==== Add the clone to your grub.cfg ====<br />
<br />
<console><br />
set timeout=3<br />
set default=0<br />
<br />
# Funtoo Recovery<br />
menuentry "Funtoo Recovery - 3.7.3" { <br />
insmod zfs<br />
linux /ROOT/funtoo/@/boot/vmlinuz-3.7.3-ALL root=rpool/ROOT/recovery quiet<br />
initrd /ROOT/funtoo/@/boot/initrd-3.7.3-ALL.img<br />
}<br />
</console><br />
<br />
==== Add the clone to your extlinux.conf ====<br />
<console><br />
LABEL funtoo-recovery <br />
MENU LABEL Funtoo Recovery <br />
KERNEL /boot/vmlinuz-3.7.3-ALL <br />
INITRD /boot/initrd-3.7.3-ALL.img <br />
APPEND root=rpool/ROOT/recovery<br />
</console><br />
<br />
==== Things to watch out for ====<br />
Since your recovery clone will tend to get old as you use your main system, and since your recovery and other stuff are on the same pool, we don't want the new pool stuff to be mounted when we launch recovery. We also don't want video drivers to be conflicting.<br />
# Make sure that nvidia/nouveau stuff are blacklisted.<br />
# Make sure that your /boot and /lib/modules for the kernel in your 'recovery' are matching.<br />
# Disable the zfs openrc script so that nothing else gets automatically mounted. Only your rootfs.<br />
<br />
You can do the above stuff by mounting your copy and chrooting into it.<br />
<br />
<console><br />
Mount the recovery clone<br />
# ##i##mkdir /mnt/recovery<br />
# ##i##mount -t zfs -o zfsutil rpool/ROOT/recovery /mnt/recovery<br />
# ##i##cd /mnt/recovery<br />
<br />
Mount the kernel devices<br />
# ##i##mount --rbind /proc ./proc<br />
# ##i##mount --rbind /dev ./dev<br />
# ##i##mount --rbind /sys ./sys<br />
<br />
Copy zpool.cache<br />
# ##i##cp /etc/zfs/zpool.cache etc/zfs<br />
<br />
Chroot into the new environment<br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash --login<br />
<br />
Disable zfs/zfs-shutdown openrc scripts<br />
# ##i##rc-config delete zfs boot<br />
<br />
Blacklist nouveau/nvidia drivers<br />
# ##i##echo "blacklist nouveau" >> /etc/modprobe.d/blacklist.conf<br />
# ##i##echo "blacklist nvidia" >> /etc/modprobe.d/blacklist.conf<br />
</console><br />
<br />
Once you are done doing your changes, just umount and exit the chroot:<br />
<br />
<console><br />
# ##i##cd /<br />
# ##i##umount -l proc dev sys<br />
# ##i##exit<br />
</console><br />
<br />
==== Getting into the recovery ====<br />
Just start your machine and pick the '''Funtoo Recovery''' option from the Boot Menu.<br />
<br />
Enjoy your new install on ZFS :)<br />
<br />
[[Category:HOWTO]]<br />
[[Category:Filesystems]]<br />
[[Category:Featured]]<br />
<br />
<br />
__NOTOC__<br />
__NOTITLE__</div>Oleghttp://www.funtoo.org/wiki/PandaboardPandaboard2013-06-08T14:02:33Z<p>Oleg: Undo revision 9351 by Oleg (talk)</p>
<hr />
<div><a href=http://www.michaelkorsbuybags2013jp.com/>マイケルコース バッグ 2013</a><br />
<br />
<a href=http://www.michaelkorsbuybags2013jp.com/>マイケルコース バッグ 2013</a><br />
<br />
<a href=http://www.seikojpsale.com/>セイコー ブライツ</a></div>Oleghttp://www.funtoo.org/wiki/PandaboardPandaboard2013-06-08T13:57:33Z<p>Oleg: Reverted edits by 175.42.11.98 (talk) to last revision by Oleg</p>
<hr />
<div><a href=http://www.burberrystoreoutlet2013jp.com/>バーバリー メンズ</a><br />
<br />
<a href=http://www.coachbagsguka2013.com/>コーチ 財布 </a><br />
<br />
<a href=http://www.coachcheaponline2013.com/>coach 財布</a></div>Oleghttp://www.funtoo.org/wiki/PandaboardPandaboard2013-06-07T16:11:12Z<p>Oleg: Reverted edits by 175.42.11.98 (talk) to last revision by 112.111.54.187</p>
<hr />
<div><a href=http://www.burberrystoreoutlet2013jp.com/>バーバリー メンズ</a><br />
<br />
<a href=http://www.coachbagsguka2013.com/>コーチ 財布 </a><br />
<br />
<a href=http://www.coachcheaponline2013.com/>coach 財布</a></div>Oleghttp://www.funtoo.org/wiki/PandaboardPandaboard2013-06-02T14:08:26Z<p>Oleg: Reverted edits by 36.248.102.115 (talk) to last revision by Oleg</p>
<hr />
<div>The '''PandaBoard''' is a low-power, low-cost single-board computer development platform based on the Texas Instruments OMAP4430 system on a chip (SoC). The board has been available to the public since 27 October 2010. It is a community supported development platform.<br />
<br />
The '''PandaBoard ES''' is a newer version based on the OMAP4460 SoC, with the CPU and GPU running at higher clock rates. The board has been available to the public since 16 November 2011. Like its predecessor, it is a community supported development platform.<br />
<br />
== Features ==<br />
The OMAP4430 SoC on the PandaBoard features a dual-core 1&nbsp;GHz ARM Cortex-A9 MPCore CPU, a 304&nbsp;MHz PowerVR SGX540 graphics processing unit (GPU), a Texas Instruments TMS320C6400 digital signal processor (DSP), and 1&nbsp;GiB of DDR2 SDRAM. <br />
<br />
The PandaBoard ES uses a newer SoC, with a dual-core 1.2&nbsp;GHz CPU and 384&nbsp;MHz GPU. Primary persistent storage is via an Secure Digital (SD) Card slot allowing SDHC cards up to 32&nbsp;GB to be used. The board includes wired 10/100 Ethernet as well as wireless Ethernet and bluetooth connectivity. The board can output video signals via Digital Visual Interface (DVI) and HDMI interfaces. It also has 3.5&nbsp;mm audio connectors. It has two Universal Serial Bus (USB) host ports and one USB On-The-Go port, supporting USB 2.0.<br />
<br />
=== CPUinfo ===<br />
* Pandaboard<br />
<pre><br />
Processor : ARMv7 Processor rev 2 (v7l)<br />
processor : 0<br />
BogoMIPS : 599.22<br />
<br />
processor : 1<br />
BogoMIPS : 582.68<br />
<br />
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls<br />
CPU implementer : 0x41<br />
CPU architecture: 7<br />
CPU variant : 0x1<br />
CPU part : 0xc09<br />
CPU revision : 2<br />
<br />
Hardware : OMAP4 Panda board<br />
Revision : 0020<br />
Serial : 0000000000000000<br />
</pre><br />
<br />
== Funtoo Linux Instalation ==<br />
First of all you have to prepare/format your SD card (ALL DATA WILL BE LOST!).<br />
<br />
<pre><br />
sdcardsetup.sh <br />
# sdcardsetup.sh script<br />
#!/bin/sh<br />
<br />
if [ ! "$1" = "/dev/sda" ] ; then<br />
DRIVE=$1<br />
if [ -b "$DRIVE" ] ; then<br />
dd if=/dev/zero of=$DRIVE bs=1024 count=1024<br />
SIZE=`fdisk -l $DRIVE | grep Disk | awk '{print $5}'`<br />
echo DISK SIZE - $SIZE bytes<br />
CYLINDERS=`echo $SIZE/255/63/512 | bc`<br />
echo CYLINDERS - $CYLINDERS<br />
{<br />
echo ,9,0x0C,*<br />
echo ,,,-<br />
} | sfdisk -D -H 255 -S 63 -C $CYLINDERS $DRIVE<br />
mkfs.vfat -F 32 -n "boot" ${DRIVE}1<br />
mke2fs -j -L "rootfs" ${DRIVE}2<br />
fi <br />
fi<br />
</pre><br />
<br />
Follow the general steps from [[Funtoo on ARM#Installing Funtoo]].<br />
<br />
These steps include:<br />
* Extract stage3 to the 2nd partition of the SD card<br />
* Extract portage snapshot (required to emerge things and ntp(see below))<br />
* Setup fstab<br />
* Setup root password<br />
* Configure hostname and networking (optional, but recommended)<br />
* Enable SSH access (optional, but recommended)<br />
* Enable serial console access (optional, but recommended)<br />
* Correct RTC "bug" with swclock<br />
<br />
<br />
=== Enabling serial console access ===<br />
These are instructions specific for Pandaboard.<br />
nano -w /mnt/SD_root/etc/inittab<br />
s0:12345:respawn:/sbin/agetty 115200 ttyO2 vt100<br />
<br />
=== Kernel and bootloader ===<br />
Here you can find kernel and bootloader files for a quick start.<br />
Put these on first partition of your SD card. Archive name boot.tar.xz<br />
<br />
* http://www.mediafire.com/?h5m1mnqqdrnyb<br />
<br />
Of course you can build your own kernel and U-Boot files, but these are provided here so you don't have to go through the cross-compiling pains and can use your Pandaboard to do native compiling once running.<br />
<br />
=== Modules and firmware ===<br />
Put these inside /lib folder on second partition. Archive name modules.tar.xz<br />
<br />
* http://www.mediafire.com/?h5m1mnqqdrnyb<br />
<br />
[[Category:ARM]]<br />
[[Category:Pandaboard]]</div>Oleghttp://www.funtoo.org/wiki/MATE_DesktopMATE Desktop2013-05-27T04:47:17Z<p>Oleg: </p>
<hr />
<div>== Setting up MATE profile ==<br />
As many of you have read recently, we have brought MATE into our main tree. Which can be added via profile mix-in. It is simple to do so:<br />
<console><br />
# ##i##eselect profile list<br />
##i##Currently available arch profiles:<br />
[1] funtoo/1.0/linux-gnu/arch/x86-64bit * <br />
[2] funtoo/1.0/linux-gnu/arch/x86-64bit/pure64<br />
##i##Currently available build profiles:<br />
[3] funtoo/1.0/linux-gnu/build/stable<br />
[4] funtoo/1.0/linux-gnu/build/current *<br />
[5] funtoo/1.0/linux-gnu/build/experimental<br />
##i##Currently available flavor profiles: <br />
[6] funtoo/1.0/linux-gnu/flavor/minimal<br />
[7] funtoo/1.0/linux-gnu/flavor/core * <br />
[8] funtoo/1.0/linux-gnu/flavor/desktop<br />
[9] funtoo/1.0/linux-gnu/flavor/workstation<br />
##i##Currently available mix-ins profiles:<br />
[10] funtoo/1.0/linux-gnu/mix-ins/audio<br />
[11] funtoo/1.0/linux-gnu/mix-ins/console-extras<br />
[12] funtoo/1.0/linux-gnu/mix-ins/dvd<br />
[13] funtoo/1.0/linux-gnu/mix-ins/gnome<br />
[14] funtoo/1.0/linux-gnu/mix-ins/kde<br />
[15] funtoo/1.0/linux-gnu/mix-ins/mate<br />
[16] funtoo/1.0/linux-gnu/mix-ins/media<br />
[17] funtoo/1.0/linux-gnu/mix-ins/print<br />
[18] funtoo/1.0/linux-gnu/mix-ins/python3-only<br />
[19] funtoo/1.0/linux-gnu/mix-ins/rhel5-compat<br />
[20] funtoo/1.0/linux-gnu/mix-ins/server-db<br />
[21] funtoo/1.0/linux-gnu/mix-ins/server-mail<br />
[22] funtoo/1.0/linux-gnu/mix-ins/server-web<br />
[23] funtoo/1.0/linux-gnu/mix-ins/X<br />
[24] funtoo/1.0/linux-gnu/mix-ins/xfce<br />
[25] funtoo/1.0/linux-gnu/mix-ins/vmware-guest<br />
# ##i##eselect profile add funtoo/1.0/linux-gnu/mix-ins/mate<br />
# ##i##emerge -uDNav @world<br />
</console><br />
== USE flags ==<br />
There is a use.mask on GTK3 for libcanberra which is required for a clean merge of MATE. A quick work around would be adding this to <tt>/etc/portage/</tt>:<br />
<console><br />
# ##i##install -d /etc/portage/profile/<br />
# ##i##echo "media-libs/libcanberra -gtk3" >> /etc/portage/profile/package.use.mask<br />
# ##i##echo "media-libs/libcanberra gtk gtk3" >> /etc/portage/package.use<br />
</console><br />
== MATE set ==<br />
MATE desktop set require manual step as described below<br />
<console><br />
# ##i##install -d /etc/portage/sets/<br />
# ##i##cp /usr/portage/sets/mate /etc/portage/sets<br />
# ##i##emerge @mate<br />
</console><br />
You're good to go!</div>Oleghttp://www.funtoo.org/wiki/MATE_DesktopMATE Desktop2013-05-27T04:44:38Z<p>Oleg: </p>
<hr />
<div>== Setting up MATE profile ==<br />
As many of you have read recently, we have brought MATE into our main tree. Which can be added via profile mix-in. It is simple to do so:<br />
<console><br />
# ##i##eselect profile list<br />
##i##Currently available arch profiles:<br />
[1] funtoo/1.0/linux-gnu/arch/x86-64bit * <br />
[2] funtoo/1.0/linux-gnu/arch/x86-64bit/pure64<br />
##i##Currently available build profiles:<br />
[3] funtoo/1.0/linux-gnu/build/stable<br />
[4] funtoo/1.0/linux-gnu/build/current *<br />
[5] funtoo/1.0/linux-gnu/build/experimental<br />
##i##Currently available flavor profiles: <br />
[6] funtoo/1.0/linux-gnu/flavor/minimal<br />
[7] funtoo/1.0/linux-gnu/flavor/core * <br />
[8] funtoo/1.0/linux-gnu/flavor/desktop<br />
[9] funtoo/1.0/linux-gnu/flavor/workstation<br />
##i##Currently available mix-ins profiles:<br />
[10] funtoo/1.0/linux-gnu/mix-ins/audio<br />
[11] funtoo/1.0/linux-gnu/mix-ins/console-extras<br />
[12] funtoo/1.0/linux-gnu/mix-ins/dvd<br />
[13] funtoo/1.0/linux-gnu/mix-ins/gnome<br />
[14] funtoo/1.0/linux-gnu/mix-ins/kde<br />
[15] funtoo/1.0/linux-gnu/mix-ins/mate<br />
[16] funtoo/1.0/linux-gnu/mix-ins/media<br />
[17] funtoo/1.0/linux-gnu/mix-ins/print<br />
[18] funtoo/1.0/linux-gnu/mix-ins/python3-only<br />
[19] funtoo/1.0/linux-gnu/mix-ins/rhel5-compat<br />
[20] funtoo/1.0/linux-gnu/mix-ins/server-db<br />
[21] funtoo/1.0/linux-gnu/mix-ins/server-mail<br />
[22] funtoo/1.0/linux-gnu/mix-ins/server-web<br />
[23] funtoo/1.0/linux-gnu/mix-ins/X<br />
[24] funtoo/1.0/linux-gnu/mix-ins/xfce<br />
[25] funtoo/1.0/linux-gnu/mix-ins/vmware-guest<br />
# ##i##eselect profile add funtoo/1.0/linux-gnu/mix-ins/mate<br />
# ##i##emerge -uDNav @world<br />
</console><br />
== USE flags ==<br />
There is a use.mask on GTK3 for libcanberra which is required for a clean merge of MATE. A quick work around would be adding this to <tt>/etc/portage/</tt>:<br />
<console><br />
# ##i##install -d /etc/portage/profile/<br />
# ##i##echo "media-libs/libcanberra -gtk3" >> /etc/portage/profile/package.use.mask<br />
# ##i##echo "media-libs/libcanberra gtk3" >> /etc/portage/package.use<br />
</console><br />
== MATE set ==<br />
MATE desktop set require manual step as described below<br />
<console><br />
# ##i##install -d /etc/portage/sets/<br />
# ##i##cp /usr/portage/sets/mate /etc/portage/sets<br />
# ##i##emerge @mate<br />
</console><br />
You're good to go!</div>Oleghttp://www.funtoo.org/wiki/PandaboardPandaboard2013-05-25T08:04:35Z<p>Oleg: Reverted edits by 112.111.13.185 (talk) to last revision by Oleg</p>
<hr />
<div>The '''PandaBoard''' is a low-power, low-cost single-board computer development platform based on the Texas Instruments OMAP4430 system on a chip (SoC). The board has been available to the public since 27 October 2010. It is a community supported development platform.<br />
<br />
The '''PandaBoard ES''' is a newer version based on the OMAP4460 SoC, with the CPU and GPU running at higher clock rates. The board has been available to the public since 16 November 2011. Like its predecessor, it is a community supported development platform.<br />
<br />
== Features ==<br />
The OMAP4430 SoC on the PandaBoard features a dual-core 1&nbsp;GHz ARM Cortex-A9 MPCore CPU, a 304&nbsp;MHz PowerVR SGX540 graphics processing unit (GPU), a Texas Instruments TMS320C6400 digital signal processor (DSP), and 1&nbsp;GiB of DDR2 SDRAM. <br />
<br />
The PandaBoard ES uses a newer SoC, with a dual-core 1.2&nbsp;GHz CPU and 384&nbsp;MHz GPU. Primary persistent storage is via an Secure Digital (SD) Card slot allowing SDHC cards up to 32&nbsp;GB to be used. The board includes wired 10/100 Ethernet as well as wireless Ethernet and bluetooth connectivity. The board can output video signals via Digital Visual Interface (DVI) and HDMI interfaces. It also has 3.5&nbsp;mm audio connectors. It has two Universal Serial Bus (USB) host ports and one USB On-The-Go port, supporting USB 2.0.<br />
<br />
=== CPUinfo ===<br />
* Pandaboard<br />
<pre><br />
Processor : ARMv7 Processor rev 2 (v7l)<br />
processor : 0<br />
BogoMIPS : 599.22<br />
<br />
processor : 1<br />
BogoMIPS : 582.68<br />
<br />
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls<br />
CPU implementer : 0x41<br />
CPU architecture: 7<br />
CPU variant : 0x1<br />
CPU part : 0xc09<br />
CPU revision : 2<br />
<br />
Hardware : OMAP4 Panda board<br />
Revision : 0020<br />
Serial : 0000000000000000<br />
</pre><br />
<br />
== Funtoo Linux Instalation ==<br />
First of all you have to prepare/format your SD card (ALL DATA WILL BE LOST!).<br />
<br />
<pre><br />
sdcardsetup.sh <br />
# sdcardsetup.sh script<br />
#!/bin/sh<br />
<br />
if [ ! "$1" = "/dev/sda" ] ; then<br />
DRIVE=$1<br />
if [ -b "$DRIVE" ] ; then<br />
dd if=/dev/zero of=$DRIVE bs=1024 count=1024<br />
SIZE=`fdisk -l $DRIVE | grep Disk | awk '{print $5}'`<br />
echo DISK SIZE - $SIZE bytes<br />
CYLINDERS=`echo $SIZE/255/63/512 | bc`<br />
echo CYLINDERS - $CYLINDERS<br />
{<br />
echo ,9,0x0C,*<br />
echo ,,,-<br />
} | sfdisk -D -H 255 -S 63 -C $CYLINDERS $DRIVE<br />
mkfs.vfat -F 32 -n "boot" ${DRIVE}1<br />
mke2fs -j -L "rootfs" ${DRIVE}2<br />
fi <br />
fi<br />
</pre><br />
<br />
Follow the general steps from [[Funtoo on ARM#Installing Funtoo]].<br />
<br />
These steps include:<br />
* Extract stage3 to the 2nd partition of the SD card<br />
* Extract portage snapshot (required to emerge things and ntp(see below))<br />
* Setup fstab<br />
* Setup root password<br />
* Configure hostname and networking (optional, but recommended)<br />
* Enable SSH access (optional, but recommended)<br />
* Enable serial console access (optional, but recommended)<br />
* Correct RTC "bug" with swclock<br />
<br />
<br />
=== Enabling serial console access ===<br />
These are instructions specific for Pandaboard.<br />
nano -w /mnt/SD_root/etc/inittab<br />
s0:12345:respawn:/sbin/agetty 115200 ttyO2 vt100<br />
<br />
=== Kernel and bootloader ===<br />
Here you can find kernel and bootloader files for a quick start.<br />
Put these on first partition of your SD card. Archive name boot.tar.xz<br />
<br />
* http://www.mediafire.com/?h5m1mnqqdrnyb<br />
<br />
Of course you can build your own kernel and U-Boot files, but these are provided here so you don't have to go through the cross-compiling pains and can use your Pandaboard to do native compiling once running.<br />
<br />
=== Modules and firmware ===<br />
Put these inside /lib folder on second partition. Archive name modules.tar.xz<br />
<br />
* http://www.mediafire.com/?h5m1mnqqdrnyb<br />
<br />
[[Category:ARM]]<br />
[[Category:Pandaboard]]</div>Oleghttp://www.funtoo.org/wiki/Funtoo_LinuxFuntoo Linux2013-05-25T08:03:00Z<p>Oleg: Gentoo buuilds no longer provided</p>
<hr />
<div>= Getting Started =<br />
Start by [[Funtoo Linux Installation|installing Funtoo]]. If you have questions, someone has probably asked them already in our [[Funtoo Linux FAQ]]. Otherwise, there are other [[Funtoo Wiki:Community portal|community resources]] available. For more information on the vision of Funtoo, see: [[vision]]<br />
<br />
= Differences between Funtoo Linux and Gentoo Linux =<br />
<br />
From an installation perspective, the main difference between Funtoo Linux and Gentoo Linux is that Funtoo Linux has a different Portage tree. We store our Portage tree in a git repository. Our Portage tree does track the Gentoo repository (we import Gentoo changes almost every day,) but our tree does contain some significant changes from Gentoo's tree.<br />
<br />
For the purpose of users Funtoo Linux decided to run a three modeled tree, the stable, the current and the experimental tree. Experimental tree is designed for Core Team in general to work on new features and is a seperated tree not available by keywords, for stable Funtoo uses the "*" arch-keyword and for current the "~*" arch-keyword. Most of the time current and experimental do not differ, but in cases of new features or toolchain updates both differ as some testings might break your system, so we like to keep this away from users while we test. Read more about it under [[Funtoo Linux#What are the differences between 'stable', 'current' and 'experimental' ?|What are the differences between 'stable', 'current' and 'experimental' ?]]<br />
<br />
Here is a basic overview of how Funtoo Linux differ from Gentoo Linux:<br />
<br />
{| {{Table}}<br />
!||colspan="4" align="center" style="background-color: #ddf;"|stable||colspan="4" align="center" style="background-color: #f78888;"|current||colspan="4" align="center" style="background-color: #f70088;"|experimental<br />
|-<br />
!Category<br />
|colspan="1" style="background-color: #ddf;"| <br />
|style="background-color:#87CEEB;" |Gentoo Linux<br />
|style="background-color:#A0E75A;" |Funtoo Linux<br />
|style="background-color: #ddf;"|<br />
|style="background-color: #f78888;"|<br />
|style="background-color:#87CEEB;" |Gentoo Linux<br />
|style="background-color:#A0E75A;" |Funtoo Linux<br />
|style="background-color: #f78888;"|<br />
|style="background-color: #f70088;"|<br />
|style="background-color:#87CEEB;" |Gentoo Linux<br />
|style="background-color:#A0E75A;" |Funtoo Linux<br />
|style="background-color: #f70088;"|<br />
|-<br />
!portage<br />
|colspan="1" style="background-color: #ddf;"| <br />
|style="background-color:#87CEEB;" |2.1.11.31<br />
|style="background-color:#A0E75A;" |2.3.5-r5 (funtoo)<br />
|style="background-color: #ddf;"|<br />
|style="background-color: #f78888;"|<br />
|style="background-color:#87CEEB;" | 2.1.11.40<br />
|style="background-color:#A0E75A;" |2.3.5-r5 (funtoo)<br />
|style="background-color: #f78888;"|<br />
|style="background-color: #f70088;"|<br />
|style="background-color:#87CEEB;" |N/A<br />
|style="background-color:#A0E75A;" |2.3.5-r5 (funtoo)<br />
|style="background-color: #f70088;"|<br />
|-<br />
!portage tree<br />
|colspan="1" style="background-color: #ddf;"| <br />
|style="background-color:#87CEEB;" |rsync-based<br />
|style="background-color:#A0E75A;" |git-based<br />
|style="background-color: #ddf;"|<br />
|style="background-color: #f78888;"|<br />
|style="background-color:#87CEEB;" |rsync-based<br />
|style="background-color:#A0E75A;" |git-based<br />
|style="background-color: #f78888;"|<br />
|style="background-color: #f70088;"|<br />
|style="background-color:#87CEEB;" |N/A<br />
|style="background-color:#A0E75A;" |git-based<br />
|style="background-color: #f70088;"|<br />
|-<br />
!glibc<br />
|colspan="1" style="background-color: #ddf;"| <br />
|style="background-color:#87CEEB;" |2.15-r3<br />
|style="background-color:#A0E75A;" |2.15-r3<br />
|style="background-color: #ddf;"|<br />
|style="background-color: #f78888;"|<br />
|style="background-color:#87CEEB;" |2.16.0<br />
|style="background-color:#A0E75A;" |2.15-r3<br />
|style="background-color: #f78888;"|<br />
|style="background-color: #f70088;"|<br />
|style="background-color:#87CEEB;" |N/A<br />
|style="background-color:#A0E75A;" |2.15-r3<br />
|style="background-color: #f70088;"|<br />
|-<br />
!gcc<br />
|colspan="1" style="background-color: #ddf;"| <br />
|style="background-color:#87CEEB;" |4.6.3<br />
|style="background-color:#A0E75A;" |4.6.3<br />
|style="background-color: #ddf;"|<br />
|style="background-color: #f78888;"|<br />
|style="background-color:#87CEEB;" |4.6.3<br />
|style="background-color:#A0E75A;" |4.6.3<br />
|style="background-color: #f78888;"|<br />
|style="background-color: #f70088;"|<br />
|style="background-color:#87CEEB;" |N/A<br />
|style="background-color:#A0E75A;" |4.6.3<br />
|style="background-color: #f70088;"|<br />
|-<br />
!udev<br />
|colspan="1" style="background-color: #ddf;"| <br />
|style="background-color:#87CEEB;" |171-r9<br />
|style="background-color:#A0E75A;" |171-r8<br />
|style="background-color: #ddf;"| <br />
|style="background-color: #f78888;"|<br />
|style="background-color:#87CEEB;" |197-r1<br />
|style="background-color:#A0E75A;" |171-r8<br />
|style="background-color: #f78888;"|<br />
|style="background-color: #f70088;"|<br />
|style="background-color:#87CEEB;" |N/A<br />
|style="background-color:#A0E75A;" |171-r8<br />
|style="background-color: #f70088;"|<br />
|-<br />
!init scripts<br />
|colspan="1" style="background-color: #ddf;"| <br />
|style="background-color:#87CEEB;" |openrc<br />
|style="background-color:#A0E75A;" |openrc<br />
|style="background-color: #ddf;"|<br />
|style="background-color: #f78888;"|<br />
|style="background-color:#87CEEB;" |openrc<br />
|style="background-color:#A0E75A;" |openrc<br />
|style="background-color: #f78888;"|<br />
|style="background-color: #f70088;"|<br />
|style="background-color:#87CEEB;" |N/A<br />
|style="background-color:#A0E75A;" |openrc<br />
|style="background-color: #f70088;"|<br />
|-<br />
!perl<br />
|colspan="1" style="background-color: #ddf;"| <br />
|style="background-color:#87CEEB;" |5.12.4-r1<br />
|style="background-color:#A0E75A;" |5.12.4-r1<br />
|style="background-color: #ddf;"|<br />
|style="background-color: #f78888;"|<br />
|style="background-color:#87CEEB;" |5.16.1<br />
|style="background-color:#A0E75A;" |5.16.1<br />
|style="background-color: #f78888;"|<br />
|style="background-color: #f70088;"|<br />
|style="background-color:#87CEEB;" |N/A<br />
|style="background-color:#A0E75A;" |5.16.1<br />
|style="background-color: #f70088;"|<br />
|-<br />
!ruby<br />
|colspan="1" style="background-color: #ddf;"| <br />
|style="background-color:#87CEEB;" |1.8.7_p370<br />
|style="background-color:#A0E75A;" |1.8.7_p370<br />
|style="background-color: #ddf;"|<br />
|style="background-color: #f78888;"| <br />
|style="background-color:#87CEEB;" |1.8.7_p371<br />
|style="background-color:#A0E75A;" |1.8.7_p371<br />
|style="background-color: #f78888;"|<br />
|style="background-color: #f70088;"|<br />
|style="background-color:#87CEEB;" |N/A<br />
|style="background-color:#A0E75A;" |1.8.7_p371<br />
|style="background-color: #f70088;"|<br />
|-<br />
!core openresolv<br />
|colspan="1" style="background-color: #ddf;"| <br />
|style="background-color:#87CEEB;" |no<br />
|style="background-color:#A0E75A;" |yes<br />
|style="background-color: #ddf;"| <br />
|style="background-color: #f78888;"|<br />
|style="background-color:#87CEEB;" |no<br />
|style="background-color:#A0E75A;" |yes<br />
|style="background-color: #f78888;"|<br />
|style="background-color: #f70088;"|<br />
|style="background-color:#87CEEB;" |N/A<br />
|style="background-color:#A0E75A;" |yes<br />
|style="background-color: #f70088;"|<br />
|-<br />
!custom pkgs<br />
|colspan="1" style="background-color: #ddf;"| <br />
|style="background-color:#87CEEB;" |N/A<br />
|style="background-color:#A0E75A;" |[[Portage (Funtoo)|portage]], udev, grub, coreboot, openrc, and [http://github.com/funtoo/funtoo-overlay more]<br />
|style="background-color: #ddf;"| <br />
|style="background-color: #f78888;"|<br />
|style="background-color:#87CEEB;" |N/A<br />
|style="background-color:#A0E75A;" |[[Portage (Funtoo)|portage]], udev, grub, coreboot, openrc, and [http://github.com/funtoo/funtoo-overlay more]<br />
|style="background-color: #f78888;"|<br />
|style="background-color: #f70088;"|<br />
|style="background-color:#87CEEB;" |N/A<br />
|style="background-color:#A0E75A;" |[[Portage (Funtoo)|portage]], udev, grub, coreboot, openrc, and [http://github.com/funtoo/funtoo-overlay more]<br />
|style="background-color: #f70088;"|<br />
|-<br />
!merged overlays<br />
|colspan="1" style="background-color: #ddf;"| <br />
|style="background-color:#87CEEB;" |None<br />
|style="background-color:#A0E75A;" |[https://github.com/slashbeast/foo-overlay slashbeast], [https://github.com/adessemond/bar-overlay A. Dessemond], [https://github.com/funtoo/flora flora]<br />
|style="background-color: #ddf;"| <br />
|style="background-color: #f78888;"|<br />
|style="background-color:#87CEEB;" |None<br />
|style="background-color:#A0E75A;" |[https://github.com/slashbeast/foo-overlay slashbeast], [https://github.com/adessemond/bar-overlay A. Dessemond], [https://github.com/funtoo/flora flora]<br />
|style="background-color: #f78888;"|<br />
|style="background-color: #f70088;"|<br />
|style="background-color:#87CEEB;" |N/A<br />
|style="background-color:#A0E75A;" |[https://github.com/slashbeast/foo-overlay slashbeast], [https://github.com/adessemond/bar-overlay A. Dessemond], [https://github.com/funtoo/flora flora]<br />
|style="background-color: #f70088;"|<br />
|-<br />
!upstream tree<br />
|colspan="1" style="background-color: #ddf;"| <br />
|style="background-color:#87CEEB;" |None<br />
|style="background-color:#A0E75A;" |gentoo stable<br />
|style="background-color: #ddf;"|<br />
|style="background-color: #f78888;"|<br />
|style="background-color:#87CEEB;" |None<br />
|style="background-color:#A0E75A;" |gentoo unstable<br />
|style="background-color: #f78888;"|<br />
|style="background-color: #f70088;"|<br />
|style="background-color:#87CEEB;" |N/A<br />
|style="background-color:#A0E75A;" |gentoo unstable<br />
|style="background-color: #f70088;"|<br />
|-<br />
!||colspan="4" align="center" style="background-color: #ddf;"|stable||colspan="4" align="center" style="background-color: #f78888;"|current||colspan="4" align="center" style="background-color: #f70088;"|experimental<br />
|}<br />
<br />
= What are the differences between 'stable', 'current' and 'experimental' ? =<br />
<br />
Funtoo Linux follows a continuous development cycle. This means that new packages are continuously added to the [[Portage Tree]] and others are periodically improved with patches and bug fixes. <br />
<br />
When a package is considered to be stable, it is tagged as such, and means that you are very unlikely to have trouble with it during installation and in daily usage. All other packages are typically tagged as 'current' meaning they have undergone less widespread testing and you are more likely to experience issues with the software itself, or a package build failure. However, in day-to-day experience:<br />
<br />
* Funtoo 'experimental' is the the development tree for CoreTeam members, it generally is the Funtoo 'current' tree to which tools are added that are right now at a testing, if one of these testing circles is done and finished the 'experimental' tree is merged into the 'current' tree and will so long not difer from it, until new packages with heavy impact are there for being tested. This tree is just designed for CoreTeam members as troubles might be more common here than in 'current'.<br />
<br />
* '''Funtoo 'current' is almost as stable as Funtoo 'stable'''', although some troubles may appear from time to time. Some distributions name their 'current' branch 'unstable' but we do not because it implies that "unstable == unusable" (Funtoo current '''IS''' usable for a daily usage in production environments, depending on your requirements). <br />
<br />
* Funtoo 'stable' can, per definition, lag '''a long ways behind''' 'current'. This branch is recommended for setting up servers which have standard and very well supported hardware for a long time. If you have a desktop machine which requires the most recent drivers / kernel available using 'stable' may not be a solution for you. Efforts are also made to ensure compatibility with stable Red Hat Enterprise Linux 5 kernels for use in environments where stability is of the utmost importance.<br />
<br />
= What's Been Done So Far =<br />
<br />
My technical goals for Funtoo Linux are to focus on improving the core Gentoo system, ie. what you'd find inside a stage3. I also have been working to improve general Gentoo technologies, such as migrating Portage to git, and ensuring that Funtoo is easily buildable in an automated way, by creating Metro. These changes are intended to empower me to improve Funtoo more easily, and are shared with you so that you can benefit from them as well.<br />
<br />
These improvements are detailed below:<br />
<br />
== Git-based Portage Tree ==<br />
<br />
One of the first things I did was migrate Gentoo's development Portage tree from cvs to git, and migrate Gentoo's user Portage tree from rsync to git. This was done to help me work more effectively, since git is simply a much more powerful and efficient tool than cvs.<br />
<br />
Zack Medico, Portage/emerge maintainer, has enhanced the 2.2 version of Portage so that it is compatible with git. This allows ''users'' to pull a Portage tree from a git repository. This can often be more efficient than rsync, although the git repository does take up more space on disk. But I did not switch away from rsync because it wasn't fast enough.<br />
<br />
More important for me is the fact that users can pull from the same repositories that I use for Funtoo development. This simplifies Funtoo infrastructure considerably, keeping things more fun for me :)<br />
<br />
Git also provides integrity-checking functionality that is superior to that which currently exists in Portage, which will allow improved data integrity checks in future versions of Portage. This work is not yet finished, or even really started, but by using git we are starting to move in this direction. This work will continue as I have time.<br />
<br />
== Forked Tree ==<br />
<br />
Funtoo has its own Portage tree that is 99% identical to Gentoo's Portage tree. I merge changes from Gentoo into our tree every 12 hours, using an automated process. Our tree has a few significant differences from the Gentoo Portage tree.<br />
<br />
I created my own Portage tree for a multitude of reasons. The main reason for creating the tree was so I could get improvements into my Portage tree immediately, changes which Gentoo developers may or may not be interested in adding to the official Gentoo tree. I don't want to wait around or try to convince someone to add a fix I need.<br />
<br />
== Metro and Daily Builds ==<br />
<br />
[[Metro]] is a tool I created to build Gentoo and Funtoo releases in an automated way. For around a year, I have been using Gentoo's catalyst, and now [[Metro]] to build daily releases of Funtoo. These stages are available on the [[Download|Download page]].<br />
<br />
Metro is a big improvement over Gentoo's automated build tool, catalyst, which I originally wrote but has not aged well over the years. Metro is still missing some functionality that exists in catalyst, most notably LiveCD support (I haven't created a Funtoo LiveCD yet, which is why :) but in nearly all other respects is much more capable than catalyst. I will continue to maintain and improve Metro as I have time. The daily builds serve as a good ongoing test for Metro as well as the integrity of the Funtoo Portage tree.<br />
<br />
== Forkable - Empowering Developers ==<br />
<br />
Combine the transition to git with Metro, and Funtoo is now actually quite easy to fork, unlike Gentoo. If you wanted to create your own derivative of Funtoo or Gentoo, you could simply clone my git repository and then set up Metro to build releases of this variant. With some basic familiarity with git, this can all be accomplished by an single individual in a single day.<br />
<br />
Why is this important? If you love Gentoo like I do, but want to work on Gentoo independently, so that you have your own personal &quot;fun, too&quot; project where ''you'' are Chief Architect, you have all the tools you need to make this happen. There is no longer a need to become an official Gentoo developer in order to grow in your Gentoo knowledge.<br />
<br />
<br />
<br />
== Core System Changes ==<br />
Funtoo has several core system changes, and I plan to continue to focus on improving the core system quite a bit. Funtoo has its own <tt>sys-fs/udev</tt> package, its own <tt>sys-apps/baselayout</tt>, its own <tt>sys-apps/openrc</tt> (which is used by default), along with various other packages and improvements. Work is currently under way on a [[Unified Configuration]] structure as well as new, improved profile method which allows specifying multiple profiles (See [[Multiple Profiles]]).<br />
<br />
== Articles ==<br />
On the [[:Category:Articles|Articles]] page, you'll notice a number of technical articles and HOWTOs. My original IBM developerWorks Linux articles are gradually being added to the site and updated as time permits.<br />
<br />
Every now and then, I will be adding interesting new content, such as the intriguing [http://www.funtoo.org/en/security/slowloris/ Slowloris DOS Mitigation Guide], which details various mitigations for the Slowloris DOS that affects the Apache Web server. This article was co-authored with Ryan Vick, a security researcher who is a friend of mine.<br />
<br />
= What's in the Works =<br />
In addition to various ongoing [[:Category:Projects|Funtoo Linux Projects]], there are other efforts.<br />
<br />
== Funtoo Filesystem Hierarchy ==<br />
<br />
The [[Funtoo Filesystem Hierarchy]] seeks to document the specific nuances of the Funtoo fileystem hierarchy beyond what is in the [http://pathname.com/fhs/ Filesystem Hierarchy Standard] already.<br />
<br />
[[Category:Funtoo]]</div>Oleghttp://www.funtoo.org/wiki/MATE_DesktopMATE Desktop2013-05-21T16:50:53Z<p>Oleg: </p>
<hr />
<div>As many of you have read recently, we have brought MATE into our main tree. Which can be added via profile mix-in. It is simple to do so:<br />
<console><br />
# ##i##eselect profile list<br />
##i##Currently available arch profiles:<br />
[1] funtoo/1.0/linux-gnu/arch/x86-64bit * <br />
[2] funtoo/1.0/linux-gnu/arch/x86-64bit/pure64<br />
##i##Currently available build profiles:<br />
[3] funtoo/1.0/linux-gnu/build/stable<br />
[4] funtoo/1.0/linux-gnu/build/current *<br />
[5] funtoo/1.0/linux-gnu/build/experimental<br />
##i##Currently available flavor profiles: <br />
[6] funtoo/1.0/linux-gnu/flavor/minimal<br />
[7] funtoo/1.0/linux-gnu/flavor/core * <br />
[8] funtoo/1.0/linux-gnu/flavor/desktop<br />
[9] funtoo/1.0/linux-gnu/flavor/workstation<br />
##i##Currently available mix-ins profiles:<br />
[10] funtoo/1.0/linux-gnu/mix-ins/audio<br />
[11] funtoo/1.0/linux-gnu/mix-ins/console-extras<br />
[12] funtoo/1.0/linux-gnu/mix-ins/dvd<br />
[13] funtoo/1.0/linux-gnu/mix-ins/gnome<br />
[14] funtoo/1.0/linux-gnu/mix-ins/kde<br />
[15] funtoo/1.0/linux-gnu/mix-ins/mate<br />
[16] funtoo/1.0/linux-gnu/mix-ins/media<br />
[17] funtoo/1.0/linux-gnu/mix-ins/print<br />
[18] funtoo/1.0/linux-gnu/mix-ins/python3-only<br />
[19] funtoo/1.0/linux-gnu/mix-ins/rhel5-compat<br />
[20] funtoo/1.0/linux-gnu/mix-ins/server-db<br />
[21] funtoo/1.0/linux-gnu/mix-ins/server-mail<br />
[22] funtoo/1.0/linux-gnu/mix-ins/server-web<br />
[23] funtoo/1.0/linux-gnu/mix-ins/X<br />
[24] funtoo/1.0/linux-gnu/mix-ins/xfce<br />
[25] funtoo/1.0/linux-gnu/mix-ins/vmware-guest<br />
# ##i##eselect profile add funtoo/1.0/linux-gnu/mix-ins/mate<br />
# ##i##emerge -uDNav @world<br />
</console><br />
There is a use.mask on GTK3 for libcanberra which is required for a clean merge of MATE. A quick work around would be adding this to <tt>/etc/portage/</tt>:<br />
<console><br />
# ##i##install -d /etc/portage/profile/<br />
# ##i##echo "media-libs/libcanberra -gtk3" >> /etc/portage/profile/package.use.mask<br />
# ##i##echo "media-libs/libcanberra gtk3" >> /etc/portage/package.use<br />
# ##i##emerge -av mate<br />
</console><br />
You're good to go!</div>Oleghttp://www.funtoo.org/wiki/PandaboardPandaboard2013-05-17T02:08:45Z<p>Oleg: Reverted edits by 36.248.100.88 (talk) to last revision by Oleg</p>
<hr />
<div>The '''PandaBoard''' is a low-power, low-cost single-board computer development platform based on the Texas Instruments OMAP4430 system on a chip (SoC). The board has been available to the public since 27 October 2010. It is a community supported development platform.<br />
<br />
The '''PandaBoard ES''' is a newer version based on the OMAP4460 SoC, with the CPU and GPU running at higher clock rates. The board has been available to the public since 16 November 2011. Like its predecessor, it is a community supported development platform.<br />
<br />
== Features ==<br />
The OMAP4430 SoC on the PandaBoard features a dual-core 1&nbsp;GHz ARM Cortex-A9 MPCore CPU, a 304&nbsp;MHz PowerVR SGX540 graphics processing unit (GPU), a Texas Instruments TMS320C6400 digital signal processor (DSP), and 1&nbsp;GiB of DDR2 SDRAM. <br />
<br />
The PandaBoard ES uses a newer SoC, with a dual-core 1.2&nbsp;GHz CPU and 384&nbsp;MHz GPU. Primary persistent storage is via an Secure Digital (SD) Card slot allowing SDHC cards up to 32&nbsp;GB to be used. The board includes wired 10/100 Ethernet as well as wireless Ethernet and bluetooth connectivity. The board can output video signals via Digital Visual Interface (DVI) and HDMI interfaces. It also has 3.5&nbsp;mm audio connectors. It has two Universal Serial Bus (USB) host ports and one USB On-The-Go port, supporting USB 2.0.<br />
<br />
=== CPUinfo ===<br />
* Pandaboard<br />
<pre><br />
Processor : ARMv7 Processor rev 2 (v7l)<br />
processor : 0<br />
BogoMIPS : 599.22<br />
<br />
processor : 1<br />
BogoMIPS : 582.68<br />
<br />
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls<br />
CPU implementer : 0x41<br />
CPU architecture: 7<br />
CPU variant : 0x1<br />
CPU part : 0xc09<br />
CPU revision : 2<br />
<br />
Hardware : OMAP4 Panda board<br />
Revision : 0020<br />
Serial : 0000000000000000<br />
</pre><br />
<br />
== Funtoo Linux Instalation ==<br />
First of all you have to prepare/format your SD card (ALL DATA WILL BE LOST!).<br />
<br />
<pre><br />
sdcardsetup.sh <br />
# sdcardsetup.sh script<br />
#!/bin/sh<br />
<br />
if [ ! "$1" = "/dev/sda" ] ; then<br />
DRIVE=$1<br />
if [ -b "$DRIVE" ] ; then<br />
dd if=/dev/zero of=$DRIVE bs=1024 count=1024<br />
SIZE=`fdisk -l $DRIVE | grep Disk | awk '{print $5}'`<br />
echo DISK SIZE - $SIZE bytes<br />
CYLINDERS=`echo $SIZE/255/63/512 | bc`<br />
echo CYLINDERS - $CYLINDERS<br />
{<br />
echo ,9,0x0C,*<br />
echo ,,,-<br />
} | sfdisk -D -H 255 -S 63 -C $CYLINDERS $DRIVE<br />
mkfs.vfat -F 32 -n "boot" ${DRIVE}1<br />
mke2fs -j -L "rootfs" ${DRIVE}2<br />
fi <br />
fi<br />
</pre><br />
<br />
Follow the general steps from [[Funtoo on ARM#Installing Funtoo]].<br />
<br />
These steps include:<br />
* Extract stage3 to the 2nd partition of the SD card<br />
* Extract portage snapshot (required to emerge things and ntp(see below))<br />
* Setup fstab<br />
* Setup root password<br />
* Configure hostname and networking (optional, but recommended)<br />
* Enable SSH access (optional, but recommended)<br />
* Enable serial console access (optional, but recommended)<br />
* Correct RTC "bug" with swclock<br />
<br />
<br />
=== Enabling serial console access ===<br />
These are instructions specific for Pandaboard.<br />
nano -w /mnt/SD_root/etc/inittab<br />
s0:12345:respawn:/sbin/agetty 115200 ttyO2 vt100<br />
<br />
=== Kernel and bootloader ===<br />
Here you can find kernel and bootloader files for a quick start.<br />
Put these on first partition of your SD card. Archive name boot.tar.xz<br />
<br />
* http://www.mediafire.com/?h5m1mnqqdrnyb<br />
<br />
Of course you can build your own kernel and U-Boot files, but these are provided here so you don't have to go through the cross-compiling pains and can use your Pandaboard to do native compiling once running.<br />
<br />
=== Modules and firmware ===<br />
Put these inside /lib folder on second partition. Archive name modules.tar.xz<br />
<br />
* http://www.mediafire.com/?h5m1mnqqdrnyb<br />
<br />
[[Category:ARM]]<br />
[[Category:Pandaboard]]</div>Oleghttp://www.funtoo.org/wiki/MuttMutt2013-05-10T04:23:04Z<p>Oleg: /* Mutt postfix setup */</p>
<hr />
<div>Mutt is a popular mail reader for Linux systems. This page is being created as a good place for people to place their mutt configurations to share with others. These configuration settings go in the user's <tt>~/.muttrc</tt> file.<br />
<br />
== Essential Mutt ==<br />
<br />
<pre><br />
set pager_stop<br />
</pre><br />
<br />
This turns off the default behavior of mutt where hitting space to scroll will automatically move to the next message when the end of the current message is reached. This is very annoying when scrolling in long emails like cron jobs, and the line above sets this behavior to off.<br />
<br />
== angry_vincent's .muttrc ==<br />
<br />
<pre><br />
# General config<br />
# ---------------<br />
<br />
set folder=~/Mail # mail folder<br />
set alias_file=~/.mail_aliases # alises file<br />
set arrow_cursor # cursor is '->'<br />
set attribution="%d, %n wrote:" # beginning of mail answer<br />
set copy=yes # save mail copies<br />
set edit_headers # edit mail header<br />
set editor="vim" # editor<br />
set folder_format="%t%N %-30.30f %8s" # folder list look<br />
set index_format="%4C %Z %{%b %d} %-31.31F %N (%4c) %s" # mail list look <br />
set mailcap_path="~/.mailcap" # path to .mailcap<br />
set menu_scroll # scroll list by one line<br />
set mail_check=5 # mail check interval<br />
set pager_stop # at the end of mail do not move to next message <br />
set postponed=+drafts # postponed mails<br />
set print=ask-yes # ask before print<br />
set print_command=lpr # print command<br />
set record=+sent # where to save sent mails <br />
set signature="~/.signature" # signature file<br />
set visual=vim # editor caled by ~v<br />
<br />
# mail sort<br />
set sort=threads<br />
set sort_aux=reverse-date-received<br />
set sort_browser=reverse-date<br />
ignore * # ignore headers so the mail body is not overloaded<br />
unignore from: subject to cc mail-followup-to \<br />
date x-mailer x-url user-agent reply-to # fieids i like to see in mail body<br />
<br />
# Colors<br />
color index brightcyan black ~N<br />
color index brightyellow black ~F<br />
color index black green ~T<br />
color index brightred black ~D<br />
mono index bold ~N<br />
mono index bold ~F<br />
mono index bold ~T<br />
mono index bold ~D<br />
<br />
# Highlights inside the body of a message.<br />
<br />
# URLs<br />
color body brightgreen black "(http|ftp|news|telnet|finger)://[^ \"\t\r\n]*"<br />
color body brightgreen black "mailto:[-a-z_0-9.]+@[-a-z_0-9.]+"<br />
mono body bold "(http|ftp|news|telnet|finger)://[^ \"\t\r\n]*"<br />
mono body bold "mailto:[-a-z_0-9.]+@[-a-z_0-9.]+"<br />
<br />
# email addresses<br />
color body brightgreen black "[-a-z_0-9.%$]+@[-a-z_0-9.]+\\.[-a-z][-a-z]+"<br />
mono body bold "[-a-z_0-9.%$]+@[-a-z_0-9.]+\\.[-a-z][-a-z]+"<br />
<br />
# header<br />
color header green black "^from:"<br />
color header green black "^to:"<br />
color header green black "^cc:"<br />
color header green black "^date:"<br />
color header yellow black "^newsgroups:"<br />
color header yellow black "^reply-to:"<br />
color header brightcyan black "^subject:"<br />
color header red black "^x-spam-rule:"<br />
color header green black "^x-mailer:"<br />
color header yellow black "^message-id:"<br />
color header yellow black "^Organization:"<br />
color header yellow black "^Organisation:"<br />
color header yellow black "^User-Agent:"<br />
color header yellow black "^message-id: .*pine"<br />
color header yellow black "^X-Fnord:"<br />
color header yellow black "^X-WebTV-Stationery:"<br />
color header yellow black "^X-Message-Flag:"<br />
color header yellow black "^X-Spam-Status:"<br />
color header yellow black "^X-SpamProbe:"<br />
color header red black "^X-SpamProbe: SPAM"<br />
<br />
# Coloring quoted text - coloring the first 7 levels:<br />
color quoted cyan black<br />
color quoted1 yellow black</pre><br />
<br />
== Interesting Color Options ==<br />
<br />
http://github.com/altercation/mutt-colors-solarized<br />
<br />
== golodhrim's mutt config ==<br />
<br />
First I split up my muttconfig in several subfiles under <tt>~/.mutt</tt>. The resulting files will be:<br />
<br />
* ~/.mutt/account_hooks<br />
* ~/.mutt/colors<br />
* ~/.mutt/folder_hooks<br />
* ~/.mutt/gpg<br />
* ~/.mutt/lists<br />
* ~/.mutt/macros<br />
* ~/.mutt/mutt-alias<br />
* ~/.mutt/muttrc<br />
* ~/.mutt/sidebar<br />
* ~/.secret/.passwd.gpg<br />
<br />
=== ~/.mutt/account_hooks ===<br />
<pre><br />
#------------------------------------------------------------------------- <br />
#<br />
# Account Hooks<br />
#-------------------------------------------------------------------------<br />
account-hook . 'unset imap_user imap_pass'<br />
account-hook 'imap://user@imaphost/' "set imap_user=user imap_pass=$my_pass1 "<br />
</pre><br />
<br />
=== ~/.mutt/colors ===<br />
<pre><br />
#------------------------------------------------------------------------- <br />
# Set colors<br />
#-------------------------------------------------------------------------<br />
color attachment brightmagenta default<br />
color error brightred default<br />
color hdrdefault red default<br />
color indicator brightyellow red<br />
color markers brightcyan default<br />
color message brightcyan default<br />
color normal default default<br />
color quoted brightblue default<br />
color search default green<br />
color signature red default<br />
color status yellow blue<br />
color tilde magenta default<br />
color tree magenta default<br />
</pre><br />
<br />
=== ~/.mutt/folder_hooks ===<br />
<pre><br />
#-------------------------------------------------------------------------- <br />
#<br />
# Folders, mailboxes and folder hooks<br />
#--------------------------------------------------------------------------<br />
# Setup for imap-user in account_hooks<br />
set folder="imap://user@imaphost/"<br />
mailboxes =INBOX =INBOX/Archives =INBOX/Drafts =INBOX/Sent =INBOX/Trash<br />
folder-hook 'imap://user@imaphost/' " \<br />
set folder=imap://user@imaphost/ \<br />
postponed=+INBOX/Drafts \<br />
record=+INBOX/Sent \<br />
smtp_url=smtp://user@smtphost \<br />
smtp_pass=$my_pass1 \<br />
#signature=~/.sig/pr.txt \<br />
from='Name Familyname <name@host> ' \<br />
realname='Realname' \<br />
pgp_sign_as='PGP-signature' \<br />
spoolfile='imap://user@imaphost/' "<br />
</pre><br />
<br />
=== ~/.mutt/gpg ===<br />
<pre><br />
# vim:syn=muttrc <br />
##<br />
<br />
set smime_decrypt_use_default_key=yes<br />
<br />
# Decode application/pgp attachments like so:<br />
set pgp_decode_command="/usr/bin/gpg %?p?--passphrase-fd 0? --no-verbose --batch --output - %f"<br />
<br />
# And use this to verify pgp signatures:<br />
set pgp_verify_command="/usr/bin/gpg --no-verbose --batch --output - --verify %s %f"<br />
<br />
# How to decrypt pgp encrypted messages:<br />
set pgp_decrypt_command="/usr/bin/gpg --passphrase-fd 0 --no-verbose --batch --output - %f"<br />
<br />
# How to pgp sign a message:<br />
set pgp_sign_command="/usr/bin/gpg --no-verbose --batch --output - --passphrase-fd 0 --armor --detach-sign --textmode %?a?-u %a? %f"<br />
<br />
# How to pgp clearsign a message:<br />
set pgp_clearsign_command="/usr/bin/gpg --no-verbose --batch --output - --passphrase-fd 0 --armor --textmode --clearsign %?a?-u %a? %f"<br />
<br />
# Import a pgp key from a message into my public keyring as follows:<br />
set pgp_import_command="/usr/bin/gpg --no-verbose --import -v %f"<br />
<br />
# Use this to export a key from my public keyring:<br />
set pgp_export_command="/usr/bin/gpg --no-verbose --export --armor %r"<br />
<br />
# Verify key information (from the key selection menu):<br />
set pgp_verify_key_command="/usr/bin/gpg --verbose --batch --fingerprint --check-sigs %r"<br />
<br />
# List my public keyring like so:<br />
set pgp_list_pubring_command="/usr/bin/gpg --no-verbose --batch --with-colons --list-keys %r" <br />
<br />
# List my private keyring like so:<br />
set pgp_list_secring_command="/usr/bin/gpg --no-verbose --batch --with-colons --list-secret-keys %r" <br />
<br />
# Automatically sign outgoing messages<br />
set pgp_autosign=yes<br />
<br />
# Timeout (in seconds) for cached passphrases:<br />
set pgp_timeout=1800<br />
<br />
# Text to show before a good signature:<br />
set pgp_good_sign="^gpg: Good signature from"<br />
</pre><br />
<br />
=== ~/.mutt/lists ===<br />
<pre><br />
#------------------------------------------------------------------------- <br />
# Mailinglist Subscriptions<br />
#-------------------------------------------------------------------------<br />
# Syntax:<br />
# subscribe mailinglist@domain.com<br />
</pre><br />
<br />
=== ~/.mutt/macros ===<br />
<pre><br />
# Macros to toggle the sidebar visibility <br />
macro index b '<enter-command>toggle sidebar_visible<enter><refresh>'<br />
macro pager b '<enter-command>toggle sidebar_visible<enter><redraw-screen>'<br />
<br />
# abook query<br />
macro index,pager A "<pipe-message>abook --add-email-quiet<return>" "add the sender address to abook"<br />
macro generic,index,pager \Cb "abook" "launch abook"<br />
</pre><br />
<br />
=== ~/.mutt/alias ===<br />
multiple lines like<br />
<pre><br />
alias nick Realname <email@host.tld><br />
</pre><br />
<br />
=== ~/.mutt/muttrc ===<br />
<pre><br />
# Some minimal Mutt settings, Gentoo-style. These reflect the Gentoo<br />
# predilection for maildir folders.<br />
#<br />
# Please don't add settings to this file to change other user<br />
# preferences (such as colors), since those can be hard for a user to<br />
# undo if their preference doesn't match yours! For example, it is<br />
# *impossible* currently in mutt to remove color settings from objects<br />
# other than the index.<br />
<br />
#-------------------------------------------------------------------------<br />
# Process the password file first<br />
#-------------------------------------------------------------------------<br />
set my_tmp=`gpg -o ~/.secret/.tmp -d ~/.secret/.passwd.gpg` <br />
set my_pass1=`awk '/user:/ {print $2}' ~/.secret/.tmp`<br />
set my_del=`rm -f ~/.secret/.tmp`<br />
<br />
#-------------------------------------------------------------------------<br />
# Further customisations<br />
#-------------------------------------------------------------------------<br />
set smart_wrap = yes<br />
set sort = 'threads'<br />
set sort_aux = 'last-date-received'<br />
set imap_check_subscribed<br />
<br />
ignore "Authentication-Results:"<br />
ignore "DoaminKey-Signature:"<br />
ignore "DKIM-Signature:"<br />
hdr_order Date From To Cc<br />
<br />
#-------------------------------------------------------------------------<br />
# Configuration variables<br />
#-------------------------------------------------------------------------<br />
set abort_nosubject=yes<br />
set abort_unmodified=yes<br />
set query_command="abook --mutt-query '%s'"<br />
set alias_file="~/.mutt/mutt-alias"<br />
set alias_format="%4n %t %a %r"<br />
source $alias_file<br />
set assumed_charset="utf-8"<br />
set attach_charset="utf-8"<br />
set charset="utf-8"<br />
set date_format=""<br />
set edit_headers=yes<br />
set editor='vim + -c "set textwidth=72" -c "set wrap" -c "set nocp" -c "?^$" '<br />
set folder="~/.offlineimap"<br />
set forward_quote=yes<br />
set header_cache=~/.mutt/cache/headers<br />
set message_cachedir=~/.mutt/cache/bodies<br />
set certificate_file=~/.mutt/certificates<br />
set help=yes<br />
set imap_idle=yes<br />
set imap_peek=yes<br />
set imap_servernoise=no<br />
set include=yes<br />
set mail_check=60<br />
set mbox_type=Maildir<br />
set menu_move_off=no<br />
set menu_scroll=no<br />
set mime_forward=ask-no<br />
set pager_context=2<br />
set pager_stop=yes<br />
set postponed="~/.mutt/mail/postponed"<br />
set realname="Martin 'golodhrim' Scholz"<br />
set record="~/.mutt/mail/sent"<br />
set reply_regexp="^(re([\[0-9\]+])*|betr):[ \t]*"<br />
#set reply_to=yes<br />
set tilde=yes<br />
<br />
#--------------------------------------------------------------------------<br />
# muttprint for printing<br />
#--------------------------------------------------------------------------<br />
set print_command="muttprint"<br />
<br />
#--------------------------------------------------------------------------<br />
# Automatically process html mails<br />
#--------------------------------------------------------------------------<br />
auto_view text/html<br />
<br />
#--------------------------------------------------------------------------<br />
# Other configuration files<br />
#--------------------------------------------------------------------------<br />
source ~/.mutt/account_hooks<br />
source ~/.mutt/folder_hooks<br />
source ~/.mutt/colors<br />
source ~/.mutt/sidebar<br />
source ~/.mutt/gpg<br />
source ~/.mutt/macros<br />
source ~/.mutt/lists <br />
</pre><br />
<br />
=== ~/.mutt/sidebar ===<br />
<pre><br />
#-------------------------------------------------------------------------- <br />
# Sidebar configuration<br />
#--------------------------------------------------------------------------<br />
set sidebar_width=30<br />
set sidebar_visible=yes<br />
set sidebar_delim='|'<br />
color sidebar_new yellow default<br />
<br />
#--------------------------------------------------------------------------<br />
# Sidebar keys<br />
#--------------------------------------------------------------------------<br />
bind index \CP sidebar-prev<br />
bind index \CN sidebar-next<br />
bind index \CO sidebar-open<br />
bind pager \CP sidebar-prev<br />
bind pager \CN sidebar-next<br />
bind pager \CO sidebar-open<br />
</pre><br />
<br />
=== ~/.secret/.passwd.gpg ===<br />
For this file follow the next steps:<br />
* Step 1:<br />
Create a folder <tt>~/.secret</tt> and inside a file <tt>.passwd</tt> and enter the following into it:<br />
<pre><br />
user1: passwd1<br />
user2: passwd2<br />
</pre><br />
where user1 and user2 are your identifiers for the accounts you added in account_hooks and folder_hooks and at the start of muttrc.<br />
* Step 2:<br />
Now encrypt the file with your gpg-key, if you don't have one execute <tt>gpg --gen-key</tt> and create one first. After that don't forget to delete your unencrypted passwordstorage.<br />
<pre><br />
$ gpg -r 0x<Your-ID-fingerprint> -o .passwd.gpg --encrypt .passwd<br />
$ rm -f .passwd<br />
</pre><br />
=== Mutt postfix setup ===<br />
Postfix is another popular and powerful mail transfer agent which somehow easier to configure than sendmail. Let's start a quick postfix mail transfer setup that will work with mutt. Set <tt>sasl,berkdb</tt> USE flags to <tt>mail-mta/potsfix</tt> and <tt>mail-client/mutt</tt><br />
<console><br />
# ##i##echo "mail-mta/postfix berkdb sasl" >> /etc/portage/package.use/mail<br />
# ##i##echo "mail-client/mutt berkdb sasl" >> /etc/portage/package.use/mail<br />
# ##i##emerge -uN1 mutt postfix<br />
</console><br />
Edit <tt>/etc/postfix/main.cf</tt> and add the following lines:<br />
<pre><br />
relayhost = smtp.gmail.com:587<br />
smtp_use_tls = yes<br />
smtp_sasl_auth_enable = yes<br />
smtp_sasl_password_maps = hash:/etc/postfix/gmail_passwd<br />
smtp_sasl_security_options = noanonymous<br />
</pre><br />
Create and edit above mentioned authorization file <tt>gmail_passwd</tt><br />
<console><br />
# ##i##touch /etc/postfix/gmail_passwd<br />
# ##i##echo "smtp.gmail.com:587 my.name@gmail.com:password" >> /etc/postfix/gmail_passwd<br />
</console><br />
Where <my.name> is gmail account and passwd is account password.<br />
Convert <tt>gmail_passwd</tt> into Berkeley DB format, secure the file and finaly restart the postfix daemon<br />
<console><br />
# ##i##postmap /etc/postfix/gmail_passwd<br />
# ##i##chown root:postfix /etc/postfix/gmail_passwd*<br />
# ##i##chmod 0640 /etc/postfix/gmail_passwd*<br />
# ##i##/etc/init.d/postfix restart<br />
</console><br />
<br />
[[Category:HOWTO]]<br />
[[Category:Featured]]</div>Oleghttp://www.funtoo.org/wiki/Metro_Quick_Start_TutorialMetro Quick Start Tutorial2013-05-10T04:08:11Z<p>Oleg: /* Step 0: Optional Quick Copy of Portage Tree */</p>
<hr />
<div>[[Metro]] is the build system for [[Funtoo Linux]] and [[Gentoo Linux]] stages. It automates the bootstrapping process.<br />
<br />
This tutorial will take you through installing, setting up and running [[Metro]].<br />
<br />
= Preface = <br />
<br />
== How Metro Works == <br />
<br />
You may be wondering how [[Metro]] creates its first stage tarball. As you may have guessed, [[Metro]] cannot create a stage tarball out of thin air. To build a new stage tarball, [[Metro]] must use an existing, older stage tarball called a &quot;seed&quot; stage. This &quot;seed&quot; stage typically is used as the ''build environment'' for creating the stage we want.<br />
<br />
[[Metro]] can use two kinds of seed stages. Traditionally, [[Metro]] has used a stage3 as a seed stage. This stage3 is then used to build a new stage1, which in turn is used to build a new stage2, and then a new stage3. This is generally the most reliable way to build [[Gentoo Linux]] or [[Funtoo Linux]], so it's the recommended approach.<br />
{{fancyimportant|'''After switching metro builds to Funtoo profile, Gentoo stages are no longer provided'''!}}<br />
<br />
== Seeds and Build Isolation ==<br />
<br />
Another important concept to mention here is something called ''build isolation''. Because [[Metro]] creates an isolated build environment, and the build environment is explicitly defined using existing, tangible entities -- a seed stage and a portage snapshot -- you will get consistent, repeatable results. In other words, the same seed stage, portage snapshot and build instructions will generate an essentially identical result, even if you perform the build a month later on someone else's workstation.<br />
<br />
== Local Build == <br />
<br />
Say you wanted to build a new <tt>pentium4</tt> stage3 tarball. The recommended method of doing this would be to grab an existing <tt>pentium4</tt> stage3 tarball to use as your seed stage. [[Metro]] will be told to use this existing <tt>pentium4</tt> stage3 to build a new stage1 for the same <tt>pentium4</tt>. For this process, the generic <tt>pentium4</tt> stage3 would provide the ''build environment'' for creating our new stage1. Then, the new stage1 would serve as the build environment for creating the new <tt>pentium4</tt> stage2. And the new <tt>pentium4</tt> stage2 would serve as the build environment for creating the new <tt>pentium4</tt> stage3.<br />
<br />
In the [[Metro]] terminology this is called a '''local build''', which means a stage3 of a given architecture is used to seed a brand new build of the same architecture. Incidentally this will be the first exercise we are going to perform in this tutorial.<br />
<br />
A week later, you may want to build a brand new <tt>pentium4</tt> stage3 tarball. Rather than starting from the original <tt>pentium4</tt> stage3 again, you'd probably configure [[Metro]] to use the most-recently-built <tt>pentium4</tt> stage3 as the seed. [[Metro]] has built-in functionality to make this easy, allowing it to easily find and track the most recent stage3 seed available.<br />
<br />
== Remote Build == <br />
<br />
[[Metro]] can also perform '''remote build''', where a stage3 of a different, but binary compatible, architecture is used as a seed to build a different architecture stage3. Consequentiality the second exercise we are going to perform in this tutorial will be to build a <tt>core2 32bit</tt> stage3 tarball from the <tt>pentium4</tt> stage3 tarball we have just built.<br />
<br />
TODO: add caveats about what archs can be seeded and what can be not (maybe a table?)<br />
<br />
== Tailored Build == <br />
<br />
Last, it's also worthy noting that both in <tt>local</tt> and <tt>remote builds</tt>, [[Metro]] can be configured to add and/or remove individual packages to the final tarball.<br />
Let's say you can't live without <tt>app-misc/screen</tt>, at the end of this tutorial, we will show how to have your tailored stage3 to include it.<br />
<br />
= Installing Metro =<br />
<br />
Today the '''recommended and supported method''' is to use the Git repository of [[Metro]]. First ensure you remove the <tt>dev-util/metro</tt> package if you had installed it:<br />
<br />
<pre><br />
(~) # emerge -aC dev-util/metro<br />
</pre><br />
<br />
Then ensure that <tt>dev-vcs/git</tt> and <tt>dev-python/boto</tt> installed on your system:<br />
<br />
<pre><br />
(~) # emerge dev-vcs/git<br />
(~) # emerge dev-python/boto<br />
</pre><br />
<br />
Next, clone the master git repository as follows:<br />
<br />
<pre><br />
(~) # install -d /root/git<br />
(~) # cd /root/git<br />
(~/git) # git clone git://github.com/funtoo/metro.git<br />
(~/git) # ln -s /root/git/metro /usr/lib/metro<br />
(~/git) # ln -s /root/git/metro/metro /usr/bin/metro<br />
</pre><br />
<br />
You will now have a directory called <tt>/root/git/metro</tt> that contains all the [[Metro]] source code.<br />
Installation complete!<br />
<br />
= Configuring Metro =<br />
<br />
[[User:Drobbins|Daniel Robbins]] maintains [[Metro]], so it comes pre-configured to successfully build both [[Gentoo Linux]] and [[Funtoo Linux]] releases. Before reading farther, you might want to customize some basic settings like the number of concurrent jobs to fit your hardware's capabilities or the directory to use for produced stage archives. This is accomplished by editing <tt>/root/git/metro/etc/metro.conf</tt> which is the [[Metro]]'s master configuration file. The <tt>[path/mirror]</tt> section defines where [[Metro]] will look for things it needs and also dump things it creates. As initially configured, [[Metro]] is set up to build [[Funtoo Linux]] and [[Gentoo Linux]] stage tarballs and place them in the <tt>/home/mirror/linux</tt> directory:<br />
<br />
<pre><br />
# Mirror Paths - where to find required files and where to put created files<br />
<br />
[section path/mirror]<br />
<br />
: /home/mirror/linux<br />
</pre><br />
<br />
If you want to change the location of your mirror on disk, then edit the <tt>/home/mirror/linux</tt> line (which defines the path/mirror variable) to point to another directory.<br />
<br />
For the purpose of the following steps, set an environment variable:<br />
<br />
<pre><br />
(~) # export METRO_MIRROR=/home/mirror/linux<br />
</pre> <br />
<br />
Of course, set the environment variable to whatever location you used in the configuration file.<br />
<br />
== Arch and Subarch ==<br />
<br />
In the following example we are creating a pentium4 stage 3 compiled for x86-32bit binary compatibility. Pentium4 is a subarch of the x86-32bit architecture. Once you have metro installed you may find a full list of each subarch in your <tt>/usr/lib/metro/subarch</tt> directory each subarch will have the file extension .spec<br />
Example:<br />
<pre> <br />
# ls /usr/lib/metro/subarch/<br />
amd64-k10.spec athlon-tbird.spec generic_32.spec native_32.spec pentium-mmx.spec<br />
amd64-k8_32.spec athlon-xp.spec generic_64.spec native_64.spec pentium-m.spec<br />
amd64-k8.spec atom_32.spec generic_sparcv9.spec niagara2.spec pentiumpro.spec<br />
amd64-k8+sse3_32.spec atom_64.spec geode.spec niagara.spec pentium.spec<br />
amd64-k8+sse3.spec btver1_64.spec i486.spec nocona.spec prescott.spec<br />
armv7a.spec btver1.spec i686.spec opteron_64.spec ultrasparc3.spec<br />
athlon-4.spec core2_32.spec k6-2.spec pentium2.spec ultrasparc.spec<br />
athlon-mp.spec core2_64.spec k6-3.spec pentium3.spec xen-pentium4+sse3_64.spec<br />
athlon.spec corei7.spec k6.spec pentium4.spec xen-pentium4+sse3.spec<br />
</pre><br />
<br />
For an example list of Architectures, take a look at the directory listing on the [http://ftp.osuosl.org/pub/funtoo/funtoo-current/ Funtoo-Current Mirror].<br />
<br />
= First stages build (local build) =<br />
<br />
To get this all started, we need to bootstrap the process by downloading an initial seed stage3 to use for building and place it in is proper location in <tt>/home/mirror/linux</tt>, so that [[Metro]] can find it. We will also need to create some special &quot;control&quot; files in <tt>/home/mirror/linux</tt>, which will allow [[Metro]] to understand how it is supposed to proceed.<br />
<br />
== Step 0: Optional Quick Copy of Portage Tree ==<br />
<br />
There is a quick step you can perform to avoid having Metro re-clone the entire Portage tree. Perform this as root:<br />
<br />
<pre><br />
# cd /usr/portage; git checkout origin/master<br />
# install -d /var/tmp/metro/cache/cloned-repositories<br />
# cat /root/git/metro/etc/builds/funtoo-current/build.conf | grep name<br />
name: portage-mini-2011<br />
# cp -a /usr/portage /var/tmp/metro/cache/cloned-repositories/ports-2012<br />
# cd /usr/portage; git checkout funtoo.org<br />
</pre><br />
<br />
== Step 1: Set up pentium4 repository (local build) ==<br />
<br />
Assuming we're following the basic steps outlined in the previous section, and building an unstable funtoo (<tt>funtoo-current</tt>) build for the <tt>pentium4</tt>, using a generic <tt>pentium4</tt> stage3 as a seed stage, then here the first set of steps we'd perform:<br />
<br />
<pre><br />
(~) # install -d "${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"<br />
(~) # cd "${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # install -d 2011-12-13<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # cd 2011-12-13<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4/2011-12-13) # wget -c http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-32bit/pentium4/2011-12-13/stage3-pentium4-funtoo-current-2011-12-13.tar.xz<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4/2011-12-13) # cd ..<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # install -d .control/version<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # echo &quot;2011-12-13&quot; &gt; .control/version/stage3<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # install -d .control/strategy<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # echo &quot;local&quot; &gt; .control/strategy/build<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # echo &quot;stage3&quot; &gt; .control/strategy/seed<br />
</pre><br />
<br />
OK, let's review the steps above. First, we create the directory <tt>"${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"</tt>, which is where Metro will expect to find unstable <tt>funtoo-current</tt> pentium4 builds -- it is configured to look here by default. Then we create a specially-named directory to house our seed x86 stage3. Again, by default, Metro expects the directory to be named this way. We enter this directory, and download our seed x86 stage3 from funtoo.org. Note that the <tt>2010-12-24</tt> version stamp matches. Make sure that your directory name matches the stage3 name too. Everything has been set up to match Metro's default filesystem layout.<br />
<br />
Next, we go back to the <tt>"${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"</tt> directory, and inside it, we create a <tt>.control</tt> directory. This directory and its subdirectories contain special files that Metro references to determine certain aspects of its behavior. The <tt>.control/version/stage3</tt> file is used by Metro to track the most recently-built stage3 for this particular build and subarch. Metro will automatically update this file with a new version stamp after it successfully builds a new stage3. But because Metro didn't actually ''build'' this stage3, we need to set up the <tt>.control/version/stage3</tt> file manually. This will allow Metro to find our downloaded stage3 when we set up our pentium4 build to use it as a seed. Also note that Metro will create a similar <tt>.control/version/stage1</tt> file after it successfully builds an pentium4 funtoo-current stage1.<br />
<br />
We also set up <tt>.control/strategy/build</tt> and <tt>.control/strategy/seed</tt> files with values of <tt>local</tt> and <tt>stage3</tt> respectively. These files define the building strategy Metro will use when we build pentium4 funtoo-current stages. With a build strategy of <tt>local</tt>, Metro will source its seed stage from funtoo-current pentium4, the current directory. And with a seed strategy of <tt>stage3</tt>, Metro will use a stage3 as a seed, and use this seed to build a new stage1, stage2 and stage3.<br />
<br />
== Step 2: Building the pentium4 stages ==<br />
<br />
Incidentally, if all you wanted to do at this point was to build a new pentium4 funtoo-current stage1/2/3 (plus openvz and vserver templates). You would begin the process by typing:<br />
<br />
<pre><br />
# cd /root/git/metro<br />
# scripts/ezbuild.sh funtoo-current pentium4<br />
</pre><br />
<br />
If you have a slow machine, it could take several hours to be completed because several "heavy" components like gcc or glibc have to be recompiled in each stage. Once a stage has been successfully completed, it is placed in the <tt>"${METRO_MIRROR}/funtoo-current/x32-bit/pentium4/YYYY-MM-DD"</tt> subdirectory, where <tt>YYYY-MM-DD</tt> is today's date at the time the <tt>ezbuild.sh</tt> script was started or the date you put on the ezscript.sh command line.<br />
<br />
== Step 3: The next build ==<br />
<br />
At this point, you now have a new pentium4 stage3. If you'd like, you can reconfigure Metro to use the most recently-built pentium4 stage3 as a seed for any pentium4 builds. To do this, simply type:<br />
<br />
<pre>(~) # echo &quot;local&quot; &gt; /home/mirror/linux/funtoo-current/x86-32bit/pentium4/.control/strategy/build</pre><br />
Now, Metro will use the most recentpentium4 stage3 as a seed. The <tt>.control/remote</tt> files you created will be ignored by Metro, since it's no longer going to perform a remote build.<br />
<br />
= Building for another binary compatible architecture (remote build) =<br />
<br />
As written above, [[Metro]] is able to perform '''remote build''' building different architecture stage3 from a binary compatible seeding stage3 (e.g. using a pentium4 stage3 to seed a <tt>Intel Core2 32bits</tt> stage3). <br />
<br />
In the Metro terminology this is called a '''remote build''' (a stage 3 of a different, but binary compatible, architecture is used as a seed). <br />
What's not compatible? You can't use a <tt>Sparc</tt> architecture to generate an <tt>x86</tt> or <tt>ARM</tt> based stage and vice-versa. If you use a 32bit stage then you don't want to seed a 64bit build from it. Be sure that you are using a stage from the same architecture that you are trying to seed. Check [http://ftp.osuosl.org/pub/funtoo/funtoo-current/ Funtoo-current FTP Mirror] for a stage that is from the same Architecture that you will be building. <br />
<br />
== Step 1: Set up Core_2 32bit repository ==<br />
<br />
In this example, we're going to use this pentium4 funtoo-current stage3 to seed a new Core_2 32bit funtoo-current build. To get that done, we need to set up the pentium4 build directory as follows:<br />
<br />
<pre><br />
(~) # cd "${METRO_MIRROR}/funtoo-current/x86-32bit"<br />
(/home/mirror/linux/funtoo-current/x86-32bit) # install -d core2_32<br />
(/home/mirror/linux/funtoo-current/x86-32bit) # cd core2_32<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # install -d .control/strategy<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;remote&quot; &gt; .control/strategy/build<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;stage3&quot; &gt; .control/strategy/seed<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # install -d .control/remote<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;funtoo-current&quot; &gt; .control/remote/build<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;pentium4&quot; &gt; .control/remote/subarch<br />
</pre><br />
<br />
The steps we follow are similar to those we performed for a ''local build'' to set up our pentium4 directory for local build. However, note the differences. We didn't download a stage, because we are going to use the pentium4 stage to build a new Core_2 32bit stage. We also didn't create the <tt>.control/version/stage{1,3}</tt> files because Metro will create them for us after it successfully builds a new stage1 and stage3. We are still using a <tt>stage3</tt> seed strategy, but we've set the build strategy to <tt>remote</tt>, which means that we're going to use a seed stage that's not from this particular subdirectory. Where are we going to get it from? The <tt>.control/remote</tt> directory contains this information, and lets Metro know that it should look for its seed stage3 in the <tt>"${METRO_MIRROR}/home/mirror/linux/funtoo-current/x86-32bit/pentium4"</tt> directory. Which one will it grab? You guessed it -- the most recently built ''stage3'' (since our seed strategy was set to <tt>stage3</tt>) that has the version stamp of <tt>2010-12-24</tt>, as recorded in <tt>"${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4/.control/version/stage3"</tt>. Now you can see how all those control files come together to direct Metro to do the right thing.<br />
<br />
== Step 2: Building the Core_2 32bit stages ==<br />
<br />
Now, you could start building your new Core_2 32bit stage1/2/3 (plus openvz and vserver templates) by typing the following:<br />
<br />
<pre><br />
(~) # /root/git/metro/scripts/ezbuild.sh funtoo-current core2_32<br />
</pre><br />
<br />
In that case, the produced stages are placed in the <tt>"${METRO_MIRROR}/funtoo-current/x32-bit/core2_32/YYYY-MM-DD"</tt> subdirectory.<br />
<br />
== Step 3: The Next Build ==<br />
<br />
At this point, you now have a new Core_2 32bit stage3. If you'd like, you can reconfigure Metro to use the most recently-built Core_2 32bit stage3 as a seed for any new Core_2 32bit builds. <br />
<br />
In the Metro terminology this is called a '''local build''' (a stage 3 of a a given architecture is used to seed a brand new build of the same architecture). <br />
<br />
To do this, simply type:<br />
<br />
<pre><br />
(~) # echo &quot;local&quot; &gt; /home/mirror/linux/funtoo-current/x86-32bit/core2_32/.control/strategy/build<br />
</pre><br />
<br />
Now, Metro will use the most recent Core_2 32bit stage3 as a seed. The <tt>.control/remote</tt> files you created will be ignored by Metro, since it's no longer going to perform a remote build.<br />
<br />
= Build your own tailored stage3 =<br />
<br />
Metro can be easily configured for building custom stage3 by including additional packages. Notice that including packages with heavy dependencies such as gnome, kde, xorg-server is not recommended (not tested so far). Well tested packages are <tt>app-misc/mc</tt>, <tt>app-misc/screen</tt>, <tt>sys-process/htop</tt>, <tt>sys-apps/dstat</tt>. An example for funtoo-current stage. Edit the following configuration file <tt>/root/git/metro/etc/builds/funtoo-current/build.conf</tt>:<br />
<br />
<pre><br />
[collect ../../fslayouts/funtoo/layout.conf]<br />
<br />
[section local]<br />
<br />
author: Daniel Robbins <drobbins@funtoo.org><br />
<br />
[section target]<br />
<br />
build: funtoo-current<br />
compression: xz<br />
<br />
[section portage]<br />
<br />
stable: ~<br />
MAKEOPTS: -j12<br />
FEATURES: mini-manifest<br />
SYNC: $[snapshot/source/remote]<br />
USE:<br />
profile: default/linux/$[target/arch:zap]/2008.0<br />
<br />
[section emerge]<br />
<br />
options: --jobs=4 --load-average=3 --keep-going=n<br />
packages: [<br />
dev-vcs/git <br />
net-misc/dhcpcd<br />
sys-fs/reiserfsprogs<br />
net-misc/bridge-utils<br />
sys-devel/bc<br />
sys-apps/pciutils<br />
app-portage/gentoolkit<br />
app-misc/mc<br />
app-misc/screen<br />
sys-process/htop<br />
sys-apps/dstat <br />
<br />
]<br />
<br />
[section snapshot]</pre><br />
<br />
As you can see MAKEOPTS and emerge default options are additional strings to tweak, --keep-going=n is recommended, if something breaking during the stage building process, you can quickly diagnose the problem.<br />
<br />
Distfiles location can be specified in <tt>/root/git/metro/etc/metro.conf</tt><br />
<br />
<pre><br />
# Main metro configuration file<br />
# <br />
# Path configuration:<br />
<br />
[collect ../targets/$[metro/target]/$[target:zap].spec]<br />
[collect ./builds/$[metro/build]/build.conf]<br />
[collect ../subarch/$[target/subarch:zap].spec]<br />
<br />
# General Paths<br />
<br />
[section path]<br />
tmp: /var/tmp/metro<br />
distfiles: /var/portage/distfiles<br />
work: $[path/tmp]/work/$[metro/build]/$[target/name]<br />
<br />
[section path/cache]<br />
</pre><br />
<br />
[[Category:HOWTO]]<br />
[[Category:Metro]]</div>Oleghttp://www.funtoo.org/wiki/Metro_Quick_Start_TutorialMetro Quick Start Tutorial2013-05-10T04:06:59Z<p>Oleg: /* Installing Metro */</p>
<hr />
<div>[[Metro]] is the build system for [[Funtoo Linux]] and [[Gentoo Linux]] stages. It automates the bootstrapping process.<br />
<br />
This tutorial will take you through installing, setting up and running [[Metro]].<br />
<br />
= Preface = <br />
<br />
== How Metro Works == <br />
<br />
You may be wondering how [[Metro]] creates its first stage tarball. As you may have guessed, [[Metro]] cannot create a stage tarball out of thin air. To build a new stage tarball, [[Metro]] must use an existing, older stage tarball called a &quot;seed&quot; stage. This &quot;seed&quot; stage typically is used as the ''build environment'' for creating the stage we want.<br />
<br />
[[Metro]] can use two kinds of seed stages. Traditionally, [[Metro]] has used a stage3 as a seed stage. This stage3 is then used to build a new stage1, which in turn is used to build a new stage2, and then a new stage3. This is generally the most reliable way to build [[Gentoo Linux]] or [[Funtoo Linux]], so it's the recommended approach.<br />
{{fancyimportant|'''After switching metro builds to Funtoo profile, Gentoo stages are no longer provided'''!}}<br />
<br />
== Seeds and Build Isolation ==<br />
<br />
Another important concept to mention here is something called ''build isolation''. Because [[Metro]] creates an isolated build environment, and the build environment is explicitly defined using existing, tangible entities -- a seed stage and a portage snapshot -- you will get consistent, repeatable results. In other words, the same seed stage, portage snapshot and build instructions will generate an essentially identical result, even if you perform the build a month later on someone else's workstation.<br />
<br />
== Local Build == <br />
<br />
Say you wanted to build a new <tt>pentium4</tt> stage3 tarball. The recommended method of doing this would be to grab an existing <tt>pentium4</tt> stage3 tarball to use as your seed stage. [[Metro]] will be told to use this existing <tt>pentium4</tt> stage3 to build a new stage1 for the same <tt>pentium4</tt>. For this process, the generic <tt>pentium4</tt> stage3 would provide the ''build environment'' for creating our new stage1. Then, the new stage1 would serve as the build environment for creating the new <tt>pentium4</tt> stage2. And the new <tt>pentium4</tt> stage2 would serve as the build environment for creating the new <tt>pentium4</tt> stage3.<br />
<br />
In the [[Metro]] terminology this is called a '''local build''', which means a stage3 of a given architecture is used to seed a brand new build of the same architecture. Incidentally this will be the first exercise we are going to perform in this tutorial.<br />
<br />
A week later, you may want to build a brand new <tt>pentium4</tt> stage3 tarball. Rather than starting from the original <tt>pentium4</tt> stage3 again, you'd probably configure [[Metro]] to use the most-recently-built <tt>pentium4</tt> stage3 as the seed. [[Metro]] has built-in functionality to make this easy, allowing it to easily find and track the most recent stage3 seed available.<br />
<br />
== Remote Build == <br />
<br />
[[Metro]] can also perform '''remote build''', where a stage3 of a different, but binary compatible, architecture is used as a seed to build a different architecture stage3. Consequentiality the second exercise we are going to perform in this tutorial will be to build a <tt>core2 32bit</tt> stage3 tarball from the <tt>pentium4</tt> stage3 tarball we have just built.<br />
<br />
TODO: add caveats about what archs can be seeded and what can be not (maybe a table?)<br />
<br />
== Tailored Build == <br />
<br />
Last, it's also worthy noting that both in <tt>local</tt> and <tt>remote builds</tt>, [[Metro]] can be configured to add and/or remove individual packages to the final tarball.<br />
Let's say you can't live without <tt>app-misc/screen</tt>, at the end of this tutorial, we will show how to have your tailored stage3 to include it.<br />
<br />
= Installing Metro =<br />
<br />
Today the '''recommended and supported method''' is to use the Git repository of [[Metro]]. First ensure you remove the <tt>dev-util/metro</tt> package if you had installed it:<br />
<br />
<pre><br />
(~) # emerge -aC dev-util/metro<br />
</pre><br />
<br />
Then ensure that <tt>dev-vcs/git</tt> and <tt>dev-python/boto</tt> installed on your system:<br />
<br />
<pre><br />
(~) # emerge dev-vcs/git<br />
(~) # emerge dev-python/boto<br />
</pre><br />
<br />
Next, clone the master git repository as follows:<br />
<br />
<pre><br />
(~) # install -d /root/git<br />
(~) # cd /root/git<br />
(~/git) # git clone git://github.com/funtoo/metro.git<br />
(~/git) # ln -s /root/git/metro /usr/lib/metro<br />
(~/git) # ln -s /root/git/metro/metro /usr/bin/metro<br />
</pre><br />
<br />
You will now have a directory called <tt>/root/git/metro</tt> that contains all the [[Metro]] source code.<br />
Installation complete!<br />
<br />
= Configuring Metro =<br />
<br />
[[User:Drobbins|Daniel Robbins]] maintains [[Metro]], so it comes pre-configured to successfully build both [[Gentoo Linux]] and [[Funtoo Linux]] releases. Before reading farther, you might want to customize some basic settings like the number of concurrent jobs to fit your hardware's capabilities or the directory to use for produced stage archives. This is accomplished by editing <tt>/root/git/metro/etc/metro.conf</tt> which is the [[Metro]]'s master configuration file. The <tt>[path/mirror]</tt> section defines where [[Metro]] will look for things it needs and also dump things it creates. As initially configured, [[Metro]] is set up to build [[Funtoo Linux]] and [[Gentoo Linux]] stage tarballs and place them in the <tt>/home/mirror/linux</tt> directory:<br />
<br />
<pre><br />
# Mirror Paths - where to find required files and where to put created files<br />
<br />
[section path/mirror]<br />
<br />
: /home/mirror/linux<br />
</pre><br />
<br />
If you want to change the location of your mirror on disk, then edit the <tt>/home/mirror/linux</tt> line (which defines the path/mirror variable) to point to another directory.<br />
<br />
For the purpose of the following steps, set an environment variable:<br />
<br />
<pre><br />
(~) # export METRO_MIRROR=/home/mirror/linux<br />
</pre> <br />
<br />
Of course, set the environment variable to whatever location you used in the configuration file.<br />
<br />
== Arch and Subarch ==<br />
<br />
In the following example we are creating a pentium4 stage 3 compiled for x86-32bit binary compatibility. Pentium4 is a subarch of the x86-32bit architecture. Once you have metro installed you may find a full list of each subarch in your <tt>/usr/lib/metro/subarch</tt> directory each subarch will have the file extension .spec<br />
Example:<br />
<pre> <br />
# ls /usr/lib/metro/subarch/<br />
amd64-k10.spec athlon-tbird.spec generic_32.spec native_32.spec pentium-mmx.spec<br />
amd64-k8_32.spec athlon-xp.spec generic_64.spec native_64.spec pentium-m.spec<br />
amd64-k8.spec atom_32.spec generic_sparcv9.spec niagara2.spec pentiumpro.spec<br />
amd64-k8+sse3_32.spec atom_64.spec geode.spec niagara.spec pentium.spec<br />
amd64-k8+sse3.spec btver1_64.spec i486.spec nocona.spec prescott.spec<br />
armv7a.spec btver1.spec i686.spec opteron_64.spec ultrasparc3.spec<br />
athlon-4.spec core2_32.spec k6-2.spec pentium2.spec ultrasparc.spec<br />
athlon-mp.spec core2_64.spec k6-3.spec pentium3.spec xen-pentium4+sse3_64.spec<br />
athlon.spec corei7.spec k6.spec pentium4.spec xen-pentium4+sse3.spec<br />
</pre><br />
<br />
For an example list of Architectures, take a look at the directory listing on the [http://ftp.osuosl.org/pub/funtoo/funtoo-current/ Funtoo-Current Mirror].<br />
<br />
= First stages build (local build) =<br />
<br />
To get this all started, we need to bootstrap the process by downloading an initial seed stage3 to use for building and place it in is proper location in <tt>/home/mirror/linux</tt>, so that [[Metro]] can find it. We will also need to create some special &quot;control&quot; files in <tt>/home/mirror/linux</tt>, which will allow [[Metro]] to understand how it is supposed to proceed.<br />
<br />
== Step 0: Optional Quick Copy of Portage Tree ==<br />
<br />
There is a quick step you can perform to avoid having Metro re-clone the entire Portage tree. Perform this as root:<br />
<br />
<pre><br />
# cd /usr/portage; git checkout origin/master<br />
# install -d /var/tmp/metro/cache/cloned-repositories<br />
# cat /root/git/metro/etc/builds/funtoo-current/build.conf | grep name<br />
name: portage-mini-2011<br />
# cp -a /usr/portage /var/tmp/metro/cache/cloned-repositories/portage-mini-2011<br />
# cd /usr/portage; git checkout funtoo.org<br />
</pre><br />
<br />
== Step 1: Set up pentium4 repository (local build) ==<br />
<br />
Assuming we're following the basic steps outlined in the previous section, and building an unstable funtoo (<tt>funtoo-current</tt>) build for the <tt>pentium4</tt>, using a generic <tt>pentium4</tt> stage3 as a seed stage, then here the first set of steps we'd perform:<br />
<br />
<pre><br />
(~) # install -d "${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"<br />
(~) # cd "${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # install -d 2011-12-13<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # cd 2011-12-13<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4/2011-12-13) # wget -c http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-32bit/pentium4/2011-12-13/stage3-pentium4-funtoo-current-2011-12-13.tar.xz<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4/2011-12-13) # cd ..<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # install -d .control/version<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # echo &quot;2011-12-13&quot; &gt; .control/version/stage3<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # install -d .control/strategy<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # echo &quot;local&quot; &gt; .control/strategy/build<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # echo &quot;stage3&quot; &gt; .control/strategy/seed<br />
</pre><br />
<br />
OK, let's review the steps above. First, we create the directory <tt>"${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"</tt>, which is where Metro will expect to find unstable <tt>funtoo-current</tt> pentium4 builds -- it is configured to look here by default. Then we create a specially-named directory to house our seed x86 stage3. Again, by default, Metro expects the directory to be named this way. We enter this directory, and download our seed x86 stage3 from funtoo.org. Note that the <tt>2010-12-24</tt> version stamp matches. Make sure that your directory name matches the stage3 name too. Everything has been set up to match Metro's default filesystem layout.<br />
<br />
Next, we go back to the <tt>"${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"</tt> directory, and inside it, we create a <tt>.control</tt> directory. This directory and its subdirectories contain special files that Metro references to determine certain aspects of its behavior. The <tt>.control/version/stage3</tt> file is used by Metro to track the most recently-built stage3 for this particular build and subarch. Metro will automatically update this file with a new version stamp after it successfully builds a new stage3. But because Metro didn't actually ''build'' this stage3, we need to set up the <tt>.control/version/stage3</tt> file manually. This will allow Metro to find our downloaded stage3 when we set up our pentium4 build to use it as a seed. Also note that Metro will create a similar <tt>.control/version/stage1</tt> file after it successfully builds an pentium4 funtoo-current stage1.<br />
<br />
We also set up <tt>.control/strategy/build</tt> and <tt>.control/strategy/seed</tt> files with values of <tt>local</tt> and <tt>stage3</tt> respectively. These files define the building strategy Metro will use when we build pentium4 funtoo-current stages. With a build strategy of <tt>local</tt>, Metro will source its seed stage from funtoo-current pentium4, the current directory. And with a seed strategy of <tt>stage3</tt>, Metro will use a stage3 as a seed, and use this seed to build a new stage1, stage2 and stage3.<br />
<br />
== Step 2: Building the pentium4 stages ==<br />
<br />
Incidentally, if all you wanted to do at this point was to build a new pentium4 funtoo-current stage1/2/3 (plus openvz and vserver templates). You would begin the process by typing:<br />
<br />
<pre><br />
# cd /root/git/metro<br />
# scripts/ezbuild.sh funtoo-current pentium4<br />
</pre><br />
<br />
If you have a slow machine, it could take several hours to be completed because several "heavy" components like gcc or glibc have to be recompiled in each stage. Once a stage has been successfully completed, it is placed in the <tt>"${METRO_MIRROR}/funtoo-current/x32-bit/pentium4/YYYY-MM-DD"</tt> subdirectory, where <tt>YYYY-MM-DD</tt> is today's date at the time the <tt>ezbuild.sh</tt> script was started or the date you put on the ezscript.sh command line.<br />
<br />
== Step 3: The next build ==<br />
<br />
At this point, you now have a new pentium4 stage3. If you'd like, you can reconfigure Metro to use the most recently-built pentium4 stage3 as a seed for any pentium4 builds. To do this, simply type:<br />
<br />
<pre>(~) # echo &quot;local&quot; &gt; /home/mirror/linux/funtoo-current/x86-32bit/pentium4/.control/strategy/build</pre><br />
Now, Metro will use the most recentpentium4 stage3 as a seed. The <tt>.control/remote</tt> files you created will be ignored by Metro, since it's no longer going to perform a remote build.<br />
<br />
= Building for another binary compatible architecture (remote build) =<br />
<br />
As written above, [[Metro]] is able to perform '''remote build''' building different architecture stage3 from a binary compatible seeding stage3 (e.g. using a pentium4 stage3 to seed a <tt>Intel Core2 32bits</tt> stage3). <br />
<br />
In the Metro terminology this is called a '''remote build''' (a stage 3 of a different, but binary compatible, architecture is used as a seed). <br />
What's not compatible? You can't use a <tt>Sparc</tt> architecture to generate an <tt>x86</tt> or <tt>ARM</tt> based stage and vice-versa. If you use a 32bit stage then you don't want to seed a 64bit build from it. Be sure that you are using a stage from the same architecture that you are trying to seed. Check [http://ftp.osuosl.org/pub/funtoo/funtoo-current/ Funtoo-current FTP Mirror] for a stage that is from the same Architecture that you will be building. <br />
<br />
== Step 1: Set up Core_2 32bit repository ==<br />
<br />
In this example, we're going to use this pentium4 funtoo-current stage3 to seed a new Core_2 32bit funtoo-current build. To get that done, we need to set up the pentium4 build directory as follows:<br />
<br />
<pre><br />
(~) # cd "${METRO_MIRROR}/funtoo-current/x86-32bit"<br />
(/home/mirror/linux/funtoo-current/x86-32bit) # install -d core2_32<br />
(/home/mirror/linux/funtoo-current/x86-32bit) # cd core2_32<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # install -d .control/strategy<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;remote&quot; &gt; .control/strategy/build<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;stage3&quot; &gt; .control/strategy/seed<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # install -d .control/remote<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;funtoo-current&quot; &gt; .control/remote/build<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;pentium4&quot; &gt; .control/remote/subarch<br />
</pre><br />
<br />
The steps we follow are similar to those we performed for a ''local build'' to set up our pentium4 directory for local build. However, note the differences. We didn't download a stage, because we are going to use the pentium4 stage to build a new Core_2 32bit stage. We also didn't create the <tt>.control/version/stage{1,3}</tt> files because Metro will create them for us after it successfully builds a new stage1 and stage3. We are still using a <tt>stage3</tt> seed strategy, but we've set the build strategy to <tt>remote</tt>, which means that we're going to use a seed stage that's not from this particular subdirectory. Where are we going to get it from? The <tt>.control/remote</tt> directory contains this information, and lets Metro know that it should look for its seed stage3 in the <tt>"${METRO_MIRROR}/home/mirror/linux/funtoo-current/x86-32bit/pentium4"</tt> directory. Which one will it grab? You guessed it -- the most recently built ''stage3'' (since our seed strategy was set to <tt>stage3</tt>) that has the version stamp of <tt>2010-12-24</tt>, as recorded in <tt>"${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4/.control/version/stage3"</tt>. Now you can see how all those control files come together to direct Metro to do the right thing.<br />
<br />
== Step 2: Building the Core_2 32bit stages ==<br />
<br />
Now, you could start building your new Core_2 32bit stage1/2/3 (plus openvz and vserver templates) by typing the following:<br />
<br />
<pre><br />
(~) # /root/git/metro/scripts/ezbuild.sh funtoo-current core2_32<br />
</pre><br />
<br />
In that case, the produced stages are placed in the <tt>"${METRO_MIRROR}/funtoo-current/x32-bit/core2_32/YYYY-MM-DD"</tt> subdirectory.<br />
<br />
== Step 3: The Next Build ==<br />
<br />
At this point, you now have a new Core_2 32bit stage3. If you'd like, you can reconfigure Metro to use the most recently-built Core_2 32bit stage3 as a seed for any new Core_2 32bit builds. <br />
<br />
In the Metro terminology this is called a '''local build''' (a stage 3 of a a given architecture is used to seed a brand new build of the same architecture). <br />
<br />
To do this, simply type:<br />
<br />
<pre><br />
(~) # echo &quot;local&quot; &gt; /home/mirror/linux/funtoo-current/x86-32bit/core2_32/.control/strategy/build<br />
</pre><br />
<br />
Now, Metro will use the most recent Core_2 32bit stage3 as a seed. The <tt>.control/remote</tt> files you created will be ignored by Metro, since it's no longer going to perform a remote build.<br />
<br />
= Build your own tailored stage3 =<br />
<br />
Metro can be easily configured for building custom stage3 by including additional packages. Notice that including packages with heavy dependencies such as gnome, kde, xorg-server is not recommended (not tested so far). Well tested packages are <tt>app-misc/mc</tt>, <tt>app-misc/screen</tt>, <tt>sys-process/htop</tt>, <tt>sys-apps/dstat</tt>. An example for funtoo-current stage. Edit the following configuration file <tt>/root/git/metro/etc/builds/funtoo-current/build.conf</tt>:<br />
<br />
<pre><br />
[collect ../../fslayouts/funtoo/layout.conf]<br />
<br />
[section local]<br />
<br />
author: Daniel Robbins <drobbins@funtoo.org><br />
<br />
[section target]<br />
<br />
build: funtoo-current<br />
compression: xz<br />
<br />
[section portage]<br />
<br />
stable: ~<br />
MAKEOPTS: -j12<br />
FEATURES: mini-manifest<br />
SYNC: $[snapshot/source/remote]<br />
USE:<br />
profile: default/linux/$[target/arch:zap]/2008.0<br />
<br />
[section emerge]<br />
<br />
options: --jobs=4 --load-average=3 --keep-going=n<br />
packages: [<br />
dev-vcs/git <br />
net-misc/dhcpcd<br />
sys-fs/reiserfsprogs<br />
net-misc/bridge-utils<br />
sys-devel/bc<br />
sys-apps/pciutils<br />
app-portage/gentoolkit<br />
app-misc/mc<br />
app-misc/screen<br />
sys-process/htop<br />
sys-apps/dstat <br />
<br />
]<br />
<br />
[section snapshot]</pre><br />
<br />
As you can see MAKEOPTS and emerge default options are additional strings to tweak, --keep-going=n is recommended, if something breaking during the stage building process, you can quickly diagnose the problem.<br />
<br />
Distfiles location can be specified in <tt>/root/git/metro/etc/metro.conf</tt><br />
<br />
<pre><br />
# Main metro configuration file<br />
# <br />
# Path configuration:<br />
<br />
[collect ../targets/$[metro/target]/$[target:zap].spec]<br />
[collect ./builds/$[metro/build]/build.conf]<br />
[collect ../subarch/$[target/subarch:zap].spec]<br />
<br />
# General Paths<br />
<br />
[section path]<br />
tmp: /var/tmp/metro<br />
distfiles: /var/portage/distfiles<br />
work: $[path/tmp]/work/$[metro/build]/$[target/name]<br />
<br />
[section path/cache]<br />
</pre><br />
<br />
[[Category:HOWTO]]<br />
[[Category:Metro]]</div>Oleghttp://www.funtoo.org/wiki/Metro_Quick_Start_TutorialMetro Quick Start Tutorial2013-05-10T04:06:08Z<p>Oleg: /* Installing Metro */</p>
<hr />
<div>[[Metro]] is the build system for [[Funtoo Linux]] and [[Gentoo Linux]] stages. It automates the bootstrapping process.<br />
<br />
This tutorial will take you through installing, setting up and running [[Metro]].<br />
<br />
= Preface = <br />
<br />
== How Metro Works == <br />
<br />
You may be wondering how [[Metro]] creates its first stage tarball. As you may have guessed, [[Metro]] cannot create a stage tarball out of thin air. To build a new stage tarball, [[Metro]] must use an existing, older stage tarball called a &quot;seed&quot; stage. This &quot;seed&quot; stage typically is used as the ''build environment'' for creating the stage we want.<br />
<br />
[[Metro]] can use two kinds of seed stages. Traditionally, [[Metro]] has used a stage3 as a seed stage. This stage3 is then used to build a new stage1, which in turn is used to build a new stage2, and then a new stage3. This is generally the most reliable way to build [[Gentoo Linux]] or [[Funtoo Linux]], so it's the recommended approach.<br />
{{fancyimportant|'''After switching metro builds to Funtoo profile, Gentoo stages are no longer provided'''!}}<br />
<br />
== Seeds and Build Isolation ==<br />
<br />
Another important concept to mention here is something called ''build isolation''. Because [[Metro]] creates an isolated build environment, and the build environment is explicitly defined using existing, tangible entities -- a seed stage and a portage snapshot -- you will get consistent, repeatable results. In other words, the same seed stage, portage snapshot and build instructions will generate an essentially identical result, even if you perform the build a month later on someone else's workstation.<br />
<br />
== Local Build == <br />
<br />
Say you wanted to build a new <tt>pentium4</tt> stage3 tarball. The recommended method of doing this would be to grab an existing <tt>pentium4</tt> stage3 tarball to use as your seed stage. [[Metro]] will be told to use this existing <tt>pentium4</tt> stage3 to build a new stage1 for the same <tt>pentium4</tt>. For this process, the generic <tt>pentium4</tt> stage3 would provide the ''build environment'' for creating our new stage1. Then, the new stage1 would serve as the build environment for creating the new <tt>pentium4</tt> stage2. And the new <tt>pentium4</tt> stage2 would serve as the build environment for creating the new <tt>pentium4</tt> stage3.<br />
<br />
In the [[Metro]] terminology this is called a '''local build''', which means a stage3 of a given architecture is used to seed a brand new build of the same architecture. Incidentally this will be the first exercise we are going to perform in this tutorial.<br />
<br />
A week later, you may want to build a brand new <tt>pentium4</tt> stage3 tarball. Rather than starting from the original <tt>pentium4</tt> stage3 again, you'd probably configure [[Metro]] to use the most-recently-built <tt>pentium4</tt> stage3 as the seed. [[Metro]] has built-in functionality to make this easy, allowing it to easily find and track the most recent stage3 seed available.<br />
<br />
== Remote Build == <br />
<br />
[[Metro]] can also perform '''remote build''', where a stage3 of a different, but binary compatible, architecture is used as a seed to build a different architecture stage3. Consequentiality the second exercise we are going to perform in this tutorial will be to build a <tt>core2 32bit</tt> stage3 tarball from the <tt>pentium4</tt> stage3 tarball we have just built.<br />
<br />
TODO: add caveats about what archs can be seeded and what can be not (maybe a table?)<br />
<br />
== Tailored Build == <br />
<br />
Last, it's also worthy noting that both in <tt>local</tt> and <tt>remote builds</tt>, [[Metro]] can be configured to add and/or remove individual packages to the final tarball.<br />
Let's say you can't live without <tt>app-misc/screen</tt>, at the end of this tutorial, we will show how to have your tailored stage3 to include it.<br />
<br />
= Installing Metro =<br />
<br />
Today the '''recommended and supported method''' is to use the Git repository of [[Metro]]. First ensure you remove the <tt>dev-util/metro</tt> package if you had installed it:<br />
<br />
<pre><br />
(~) # emerge -aC dev-util/metro<br />
</pre><br />
<br />
Then ensure that <tt>dev-vcs/git</tt> is installed on your system:<br />
<br />
<pre><br />
(~) # emerge dev-vcs/git<br />
(~) # emerge dev-python/boto<br />
</pre><br />
<br />
Next, clone the master git repository as follows:<br />
<br />
<pre><br />
(~) # install -d /root/git<br />
(~) # cd /root/git<br />
(~/git) # git clone git://github.com/funtoo/metro.git<br />
(~/git) # ln -s /root/git/metro /usr/lib/metro<br />
(~/git) # ln -s /root/git/metro/metro /usr/bin/metro<br />
</pre><br />
<br />
You will now have a directory called <tt>/root/git/metro</tt> that contains all the [[Metro]] source code.<br />
Installation complete!<br />
<br />
= Configuring Metro =<br />
<br />
[[User:Drobbins|Daniel Robbins]] maintains [[Metro]], so it comes pre-configured to successfully build both [[Gentoo Linux]] and [[Funtoo Linux]] releases. Before reading farther, you might want to customize some basic settings like the number of concurrent jobs to fit your hardware's capabilities or the directory to use for produced stage archives. This is accomplished by editing <tt>/root/git/metro/etc/metro.conf</tt> which is the [[Metro]]'s master configuration file. The <tt>[path/mirror]</tt> section defines where [[Metro]] will look for things it needs and also dump things it creates. As initially configured, [[Metro]] is set up to build [[Funtoo Linux]] and [[Gentoo Linux]] stage tarballs and place them in the <tt>/home/mirror/linux</tt> directory:<br />
<br />
<pre><br />
# Mirror Paths - where to find required files and where to put created files<br />
<br />
[section path/mirror]<br />
<br />
: /home/mirror/linux<br />
</pre><br />
<br />
If you want to change the location of your mirror on disk, then edit the <tt>/home/mirror/linux</tt> line (which defines the path/mirror variable) to point to another directory.<br />
<br />
For the purpose of the following steps, set an environment variable:<br />
<br />
<pre><br />
(~) # export METRO_MIRROR=/home/mirror/linux<br />
</pre> <br />
<br />
Of course, set the environment variable to whatever location you used in the configuration file.<br />
<br />
== Arch and Subarch ==<br />
<br />
In the following example we are creating a pentium4 stage 3 compiled for x86-32bit binary compatibility. Pentium4 is a subarch of the x86-32bit architecture. Once you have metro installed you may find a full list of each subarch in your <tt>/usr/lib/metro/subarch</tt> directory each subarch will have the file extension .spec<br />
Example:<br />
<pre> <br />
# ls /usr/lib/metro/subarch/<br />
amd64-k10.spec athlon-tbird.spec generic_32.spec native_32.spec pentium-mmx.spec<br />
amd64-k8_32.spec athlon-xp.spec generic_64.spec native_64.spec pentium-m.spec<br />
amd64-k8.spec atom_32.spec generic_sparcv9.spec niagara2.spec pentiumpro.spec<br />
amd64-k8+sse3_32.spec atom_64.spec geode.spec niagara.spec pentium.spec<br />
amd64-k8+sse3.spec btver1_64.spec i486.spec nocona.spec prescott.spec<br />
armv7a.spec btver1.spec i686.spec opteron_64.spec ultrasparc3.spec<br />
athlon-4.spec core2_32.spec k6-2.spec pentium2.spec ultrasparc.spec<br />
athlon-mp.spec core2_64.spec k6-3.spec pentium3.spec xen-pentium4+sse3_64.spec<br />
athlon.spec corei7.spec k6.spec pentium4.spec xen-pentium4+sse3.spec<br />
</pre><br />
<br />
For an example list of Architectures, take a look at the directory listing on the [http://ftp.osuosl.org/pub/funtoo/funtoo-current/ Funtoo-Current Mirror].<br />
<br />
= First stages build (local build) =<br />
<br />
To get this all started, we need to bootstrap the process by downloading an initial seed stage3 to use for building and place it in is proper location in <tt>/home/mirror/linux</tt>, so that [[Metro]] can find it. We will also need to create some special &quot;control&quot; files in <tt>/home/mirror/linux</tt>, which will allow [[Metro]] to understand how it is supposed to proceed.<br />
<br />
== Step 0: Optional Quick Copy of Portage Tree ==<br />
<br />
There is a quick step you can perform to avoid having Metro re-clone the entire Portage tree. Perform this as root:<br />
<br />
<pre><br />
# cd /usr/portage; git checkout origin/master<br />
# install -d /var/tmp/metro/cache/cloned-repositories<br />
# cat /root/git/metro/etc/builds/funtoo-current/build.conf | grep name<br />
name: portage-mini-2011<br />
# cp -a /usr/portage /var/tmp/metro/cache/cloned-repositories/portage-mini-2011<br />
# cd /usr/portage; git checkout funtoo.org<br />
</pre><br />
<br />
== Step 1: Set up pentium4 repository (local build) ==<br />
<br />
Assuming we're following the basic steps outlined in the previous section, and building an unstable funtoo (<tt>funtoo-current</tt>) build for the <tt>pentium4</tt>, using a generic <tt>pentium4</tt> stage3 as a seed stage, then here the first set of steps we'd perform:<br />
<br />
<pre><br />
(~) # install -d "${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"<br />
(~) # cd "${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # install -d 2011-12-13<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # cd 2011-12-13<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4/2011-12-13) # wget -c http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-32bit/pentium4/2011-12-13/stage3-pentium4-funtoo-current-2011-12-13.tar.xz<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4/2011-12-13) # cd ..<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # install -d .control/version<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # echo &quot;2011-12-13&quot; &gt; .control/version/stage3<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # install -d .control/strategy<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # echo &quot;local&quot; &gt; .control/strategy/build<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # echo &quot;stage3&quot; &gt; .control/strategy/seed<br />
</pre><br />
<br />
OK, let's review the steps above. First, we create the directory <tt>"${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"</tt>, which is where Metro will expect to find unstable <tt>funtoo-current</tt> pentium4 builds -- it is configured to look here by default. Then we create a specially-named directory to house our seed x86 stage3. Again, by default, Metro expects the directory to be named this way. We enter this directory, and download our seed x86 stage3 from funtoo.org. Note that the <tt>2010-12-24</tt> version stamp matches. Make sure that your directory name matches the stage3 name too. Everything has been set up to match Metro's default filesystem layout.<br />
<br />
Next, we go back to the <tt>"${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"</tt> directory, and inside it, we create a <tt>.control</tt> directory. This directory and its subdirectories contain special files that Metro references to determine certain aspects of its behavior. The <tt>.control/version/stage3</tt> file is used by Metro to track the most recently-built stage3 for this particular build and subarch. Metro will automatically update this file with a new version stamp after it successfully builds a new stage3. But because Metro didn't actually ''build'' this stage3, we need to set up the <tt>.control/version/stage3</tt> file manually. This will allow Metro to find our downloaded stage3 when we set up our pentium4 build to use it as a seed. Also note that Metro will create a similar <tt>.control/version/stage1</tt> file after it successfully builds an pentium4 funtoo-current stage1.<br />
<br />
We also set up <tt>.control/strategy/build</tt> and <tt>.control/strategy/seed</tt> files with values of <tt>local</tt> and <tt>stage3</tt> respectively. These files define the building strategy Metro will use when we build pentium4 funtoo-current stages. With a build strategy of <tt>local</tt>, Metro will source its seed stage from funtoo-current pentium4, the current directory. And with a seed strategy of <tt>stage3</tt>, Metro will use a stage3 as a seed, and use this seed to build a new stage1, stage2 and stage3.<br />
<br />
== Step 2: Building the pentium4 stages ==<br />
<br />
Incidentally, if all you wanted to do at this point was to build a new pentium4 funtoo-current stage1/2/3 (plus openvz and vserver templates). You would begin the process by typing:<br />
<br />
<pre><br />
# cd /root/git/metro<br />
# scripts/ezbuild.sh funtoo-current pentium4<br />
</pre><br />
<br />
If you have a slow machine, it could take several hours to be completed because several "heavy" components like gcc or glibc have to be recompiled in each stage. Once a stage has been successfully completed, it is placed in the <tt>"${METRO_MIRROR}/funtoo-current/x32-bit/pentium4/YYYY-MM-DD"</tt> subdirectory, where <tt>YYYY-MM-DD</tt> is today's date at the time the <tt>ezbuild.sh</tt> script was started or the date you put on the ezscript.sh command line.<br />
<br />
== Step 3: The next build ==<br />
<br />
At this point, you now have a new pentium4 stage3. If you'd like, you can reconfigure Metro to use the most recently-built pentium4 stage3 as a seed for any pentium4 builds. To do this, simply type:<br />
<br />
<pre>(~) # echo &quot;local&quot; &gt; /home/mirror/linux/funtoo-current/x86-32bit/pentium4/.control/strategy/build</pre><br />
Now, Metro will use the most recentpentium4 stage3 as a seed. The <tt>.control/remote</tt> files you created will be ignored by Metro, since it's no longer going to perform a remote build.<br />
<br />
= Building for another binary compatible architecture (remote build) =<br />
<br />
As written above, [[Metro]] is able to perform '''remote build''' building different architecture stage3 from a binary compatible seeding stage3 (e.g. using a pentium4 stage3 to seed a <tt>Intel Core2 32bits</tt> stage3). <br />
<br />
In the Metro terminology this is called a '''remote build''' (a stage 3 of a different, but binary compatible, architecture is used as a seed). <br />
What's not compatible? You can't use a <tt>Sparc</tt> architecture to generate an <tt>x86</tt> or <tt>ARM</tt> based stage and vice-versa. If you use a 32bit stage then you don't want to seed a 64bit build from it. Be sure that you are using a stage from the same architecture that you are trying to seed. Check [http://ftp.osuosl.org/pub/funtoo/funtoo-current/ Funtoo-current FTP Mirror] for a stage that is from the same Architecture that you will be building. <br />
<br />
== Step 1: Set up Core_2 32bit repository ==<br />
<br />
In this example, we're going to use this pentium4 funtoo-current stage3 to seed a new Core_2 32bit funtoo-current build. To get that done, we need to set up the pentium4 build directory as follows:<br />
<br />
<pre><br />
(~) # cd "${METRO_MIRROR}/funtoo-current/x86-32bit"<br />
(/home/mirror/linux/funtoo-current/x86-32bit) # install -d core2_32<br />
(/home/mirror/linux/funtoo-current/x86-32bit) # cd core2_32<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # install -d .control/strategy<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;remote&quot; &gt; .control/strategy/build<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;stage3&quot; &gt; .control/strategy/seed<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # install -d .control/remote<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;funtoo-current&quot; &gt; .control/remote/build<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;pentium4&quot; &gt; .control/remote/subarch<br />
</pre><br />
<br />
The steps we follow are similar to those we performed for a ''local build'' to set up our pentium4 directory for local build. However, note the differences. We didn't download a stage, because we are going to use the pentium4 stage to build a new Core_2 32bit stage. We also didn't create the <tt>.control/version/stage{1,3}</tt> files because Metro will create them for us after it successfully builds a new stage1 and stage3. We are still using a <tt>stage3</tt> seed strategy, but we've set the build strategy to <tt>remote</tt>, which means that we're going to use a seed stage that's not from this particular subdirectory. Where are we going to get it from? The <tt>.control/remote</tt> directory contains this information, and lets Metro know that it should look for its seed stage3 in the <tt>"${METRO_MIRROR}/home/mirror/linux/funtoo-current/x86-32bit/pentium4"</tt> directory. Which one will it grab? You guessed it -- the most recently built ''stage3'' (since our seed strategy was set to <tt>stage3</tt>) that has the version stamp of <tt>2010-12-24</tt>, as recorded in <tt>"${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4/.control/version/stage3"</tt>. Now you can see how all those control files come together to direct Metro to do the right thing.<br />
<br />
== Step 2: Building the Core_2 32bit stages ==<br />
<br />
Now, you could start building your new Core_2 32bit stage1/2/3 (plus openvz and vserver templates) by typing the following:<br />
<br />
<pre><br />
(~) # /root/git/metro/scripts/ezbuild.sh funtoo-current core2_32<br />
</pre><br />
<br />
In that case, the produced stages are placed in the <tt>"${METRO_MIRROR}/funtoo-current/x32-bit/core2_32/YYYY-MM-DD"</tt> subdirectory.<br />
<br />
== Step 3: The Next Build ==<br />
<br />
At this point, you now have a new Core_2 32bit stage3. If you'd like, you can reconfigure Metro to use the most recently-built Core_2 32bit stage3 as a seed for any new Core_2 32bit builds. <br />
<br />
In the Metro terminology this is called a '''local build''' (a stage 3 of a a given architecture is used to seed a brand new build of the same architecture). <br />
<br />
To do this, simply type:<br />
<br />
<pre><br />
(~) # echo &quot;local&quot; &gt; /home/mirror/linux/funtoo-current/x86-32bit/core2_32/.control/strategy/build<br />
</pre><br />
<br />
Now, Metro will use the most recent Core_2 32bit stage3 as a seed. The <tt>.control/remote</tt> files you created will be ignored by Metro, since it's no longer going to perform a remote build.<br />
<br />
= Build your own tailored stage3 =<br />
<br />
Metro can be easily configured for building custom stage3 by including additional packages. Notice that including packages with heavy dependencies such as gnome, kde, xorg-server is not recommended (not tested so far). Well tested packages are <tt>app-misc/mc</tt>, <tt>app-misc/screen</tt>, <tt>sys-process/htop</tt>, <tt>sys-apps/dstat</tt>. An example for funtoo-current stage. Edit the following configuration file <tt>/root/git/metro/etc/builds/funtoo-current/build.conf</tt>:<br />
<br />
<pre><br />
[collect ../../fslayouts/funtoo/layout.conf]<br />
<br />
[section local]<br />
<br />
author: Daniel Robbins <drobbins@funtoo.org><br />
<br />
[section target]<br />
<br />
build: funtoo-current<br />
compression: xz<br />
<br />
[section portage]<br />
<br />
stable: ~<br />
MAKEOPTS: -j12<br />
FEATURES: mini-manifest<br />
SYNC: $[snapshot/source/remote]<br />
USE:<br />
profile: default/linux/$[target/arch:zap]/2008.0<br />
<br />
[section emerge]<br />
<br />
options: --jobs=4 --load-average=3 --keep-going=n<br />
packages: [<br />
dev-vcs/git <br />
net-misc/dhcpcd<br />
sys-fs/reiserfsprogs<br />
net-misc/bridge-utils<br />
sys-devel/bc<br />
sys-apps/pciutils<br />
app-portage/gentoolkit<br />
app-misc/mc<br />
app-misc/screen<br />
sys-process/htop<br />
sys-apps/dstat <br />
<br />
]<br />
<br />
[section snapshot]</pre><br />
<br />
As you can see MAKEOPTS and emerge default options are additional strings to tweak, --keep-going=n is recommended, if something breaking during the stage building process, you can quickly diagnose the problem.<br />
<br />
Distfiles location can be specified in <tt>/root/git/metro/etc/metro.conf</tt><br />
<br />
<pre><br />
# Main metro configuration file<br />
# <br />
# Path configuration:<br />
<br />
[collect ../targets/$[metro/target]/$[target:zap].spec]<br />
[collect ./builds/$[metro/build]/build.conf]<br />
[collect ../subarch/$[target/subarch:zap].spec]<br />
<br />
# General Paths<br />
<br />
[section path]<br />
tmp: /var/tmp/metro<br />
distfiles: /var/portage/distfiles<br />
work: $[path/tmp]/work/$[metro/build]/$[target/name]<br />
<br />
[section path/cache]<br />
</pre><br />
<br />
[[Category:HOWTO]]<br />
[[Category:Metro]]</div>Oleghttp://www.funtoo.org/wiki/MATE_DesktopMATE Desktop2013-05-04T04:10:30Z<p>Oleg: Created page with "WIP"</p>
<hr />
<div>WIP</div>Oleghttp://www.funtoo.org/wiki/PandaboardPandaboard2013-05-01T05:51:46Z<p>Oleg: Reverted edits by 36.248.101.52 (talk) to last revision by Oleg</p>
<hr />
<div>The '''PandaBoard''' is a low-power, low-cost single-board computer development platform based on the Texas Instruments OMAP4430 system on a chip (SoC). The board has been available to the public since 27 October 2010. It is a community supported development platform.<br />
<br />
The '''PandaBoard ES''' is a newer version based on the OMAP4460 SoC, with the CPU and GPU running at higher clock rates. The board has been available to the public since 16 November 2011. Like its predecessor, it is a community supported development platform.<br />
<br />
== Features ==<br />
The OMAP4430 SoC on the PandaBoard features a dual-core 1&nbsp;GHz ARM Cortex-A9 MPCore CPU, a 304&nbsp;MHz PowerVR SGX540 graphics processing unit (GPU), a Texas Instruments TMS320C6400 digital signal processor (DSP), and 1&nbsp;GiB of DDR2 SDRAM. <br />
<br />
The PandaBoard ES uses a newer SoC, with a dual-core 1.2&nbsp;GHz CPU and 384&nbsp;MHz GPU. Primary persistent storage is via an Secure Digital (SD) Card slot allowing SDHC cards up to 32&nbsp;GB to be used. The board includes wired 10/100 Ethernet as well as wireless Ethernet and bluetooth connectivity. The board can output video signals via Digital Visual Interface (DVI) and HDMI interfaces. It also has 3.5&nbsp;mm audio connectors. It has two Universal Serial Bus (USB) host ports and one USB On-The-Go port, supporting USB 2.0.<br />
<br />
=== CPUinfo ===<br />
* Pandaboard<br />
<pre><br />
Processor : ARMv7 Processor rev 2 (v7l)<br />
processor : 0<br />
BogoMIPS : 599.22<br />
<br />
processor : 1<br />
BogoMIPS : 582.68<br />
<br />
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls<br />
CPU implementer : 0x41<br />
CPU architecture: 7<br />
CPU variant : 0x1<br />
CPU part : 0xc09<br />
CPU revision : 2<br />
<br />
Hardware : OMAP4 Panda board<br />
Revision : 0020<br />
Serial : 0000000000000000<br />
</pre><br />
<br />
== Funtoo Linux Instalation ==<br />
First of all you have to prepare/format your SD card (ALL DATA WILL BE LOST!).<br />
<br />
<pre><br />
sdcardsetup.sh <br />
# sdcardsetup.sh script<br />
#!/bin/sh<br />
<br />
if [ ! "$1" = "/dev/sda" ] ; then<br />
DRIVE=$1<br />
if [ -b "$DRIVE" ] ; then<br />
dd if=/dev/zero of=$DRIVE bs=1024 count=1024<br />
SIZE=`fdisk -l $DRIVE | grep Disk | awk '{print $5}'`<br />
echo DISK SIZE - $SIZE bytes<br />
CYLINDERS=`echo $SIZE/255/63/512 | bc`<br />
echo CYLINDERS - $CYLINDERS<br />
{<br />
echo ,9,0x0C,*<br />
echo ,,,-<br />
} | sfdisk -D -H 255 -S 63 -C $CYLINDERS $DRIVE<br />
mkfs.vfat -F 32 -n "boot" ${DRIVE}1<br />
mke2fs -j -L "rootfs" ${DRIVE}2<br />
fi <br />
fi<br />
</pre><br />
<br />
Follow the general steps from [[Funtoo on ARM#Installing Funtoo]].<br />
<br />
These steps include:<br />
* Extract stage3 to the 2nd partition of the SD card<br />
* Extract portage snapshot (required to emerge things and ntp(see below))<br />
* Setup fstab<br />
* Setup root password<br />
* Configure hostname and networking (optional, but recommended)<br />
* Enable SSH access (optional, but recommended)<br />
* Enable serial console access (optional, but recommended)<br />
* Correct RTC "bug" with swclock<br />
<br />
<br />
=== Enabling serial console access ===<br />
These are instructions specific for Pandaboard.<br />
nano -w /mnt/SD_root/etc/inittab<br />
s0:12345:respawn:/sbin/agetty 115200 ttyO2 vt100<br />
<br />
=== Kernel and bootloader ===<br />
Here you can find kernel and bootloader files for a quick start.<br />
Put these on first partition of your SD card. Archive name boot.tar.xz<br />
<br />
* http://www.mediafire.com/?h5m1mnqqdrnyb<br />
<br />
Of course you can build your own kernel and U-Boot files, but these are provided here so you don't have to go through the cross-compiling pains and can use your Pandaboard to do native compiling once running.<br />
<br />
=== Modules and firmware ===<br />
Put these inside /lib folder on second partition. Archive name modules.tar.xz<br />
<br />
* http://www.mediafire.com/?h5m1mnqqdrnyb<br />
<br />
[[Category:ARM]]<br />
[[Category:Pandaboard]]</div>Oleghttp://www.funtoo.org/wiki/PandaboardPandaboard2013-04-27T04:40:46Z<p>Oleg: Reverted edits by 175.42.10.246 (talk) to last revision by 217.195.169.249</p>
<hr />
<div>The '''PandaBoard''' is a low-power, low-cost single-board computer development platform based on the Texas Instruments OMAP4430 system on a chip (SoC). The board has been available to the public since 27 October 2010. It is a community supported development platform.<br />
<br />
The '''PandaBoard ES''' is a newer version based on the OMAP4460 SoC, with the CPU and GPU running at higher clock rates. The board has been available to the public since 16 November 2011. Like its predecessor, it is a community supported development platform.<br />
<br />
== Features ==<br />
The OMAP4430 SoC on the PandaBoard features a dual-core 1&nbsp;GHz ARM Cortex-A9 MPCore CPU, a 304&nbsp;MHz PowerVR SGX540 graphics processing unit (GPU), a Texas Instruments TMS320C6400 digital signal processor (DSP), and 1&nbsp;GiB of DDR2 SDRAM. <br />
<br />
The PandaBoard ES uses a newer SoC, with a dual-core 1.2&nbsp;GHz CPU and 384&nbsp;MHz GPU. Primary persistent storage is via an Secure Digital (SD) Card slot allowing SDHC cards up to 32&nbsp;GB to be used. The board includes wired 10/100 Ethernet as well as wireless Ethernet and bluetooth connectivity. The board can output video signals via Digital Visual Interface (DVI) and HDMI interfaces. It also has 3.5&nbsp;mm audio connectors. It has two Universal Serial Bus (USB) host ports and one USB On-The-Go port, supporting USB 2.0.<br />
<br />
=== CPUinfo ===<br />
* Pandaboard<br />
<pre><br />
Processor : ARMv7 Processor rev 2 (v7l)<br />
processor : 0<br />
BogoMIPS : 599.22<br />
<br />
processor : 1<br />
BogoMIPS : 582.68<br />
<br />
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls<br />
CPU implementer : 0x41<br />
CPU architecture: 7<br />
CPU variant : 0x1<br />
CPU part : 0xc09<br />
CPU revision : 2<br />
<br />
Hardware : OMAP4 Panda board<br />
Revision : 0020<br />
Serial : 0000000000000000<br />
</pre><br />
<br />
== Funtoo Linux Instalation ==<br />
First of all you have to prepare/format your SD card (ALL DATA WILL BE LOST!).<br />
<br />
<pre><br />
sdcardsetup.sh <br />
# sdcardsetup.sh script<br />
#!/bin/sh<br />
<br />
if [ ! "$1" = "/dev/sda" ] ; then<br />
DRIVE=$1<br />
if [ -b "$DRIVE" ] ; then<br />
dd if=/dev/zero of=$DRIVE bs=1024 count=1024<br />
SIZE=`fdisk -l $DRIVE | grep Disk | awk '{print $5}'`<br />
echo DISK SIZE - $SIZE bytes<br />
CYLINDERS=`echo $SIZE/255/63/512 | bc`<br />
echo CYLINDERS - $CYLINDERS<br />
{<br />
echo ,9,0x0C,*<br />
echo ,,,-<br />
} | sfdisk -D -H 255 -S 63 -C $CYLINDERS $DRIVE<br />
mkfs.vfat -F 32 -n "boot" ${DRIVE}1<br />
mke2fs -j -L "rootfs" ${DRIVE}2<br />
fi <br />
fi<br />
</pre><br />
<br />
Follow the general steps from [[Funtoo on ARM#Installing Funtoo]].<br />
<br />
These steps include:<br />
* Extract stage3 to the 2nd partition of the SD card<br />
* Extract portage snapshot (required to emerge things and ntp(see below))<br />
* Setup fstab<br />
* Setup root password<br />
* Configure hostname and networking (optional, but recommended)<br />
* Enable SSH access (optional, but recommended)<br />
* Enable serial console access (optional, but recommended)<br />
* Correct RTC "bug" with swclock<br />
<br />
<br />
=== Enabling serial console access ===<br />
These are instructions specific for Pandaboard.<br />
nano -w /mnt/SD_root/etc/inittab<br />
s0:12345:respawn:/sbin/agetty 115200 ttyO2 vt100<br />
<br />
=== Kernel and bootloader ===<br />
Here you can find kernel and bootloader files for a quick start.<br />
Put these on first partition of your SD card. Archive name boot.tar.xz<br />
<br />
* http://www.mediafire.com/?h5m1mnqqdrnyb<br />
<br />
Of course you can build your own kernel and U-Boot files, but these are provided here so you don't have to go through the cross-compiling pains and can use your Pandaboard to do native compiling once running.<br />
<br />
=== Modules and firmware ===<br />
Put these inside /lib folder on second partition. Archive name modules.tar.xz<br />
<br />
* http://www.mediafire.com/?h5m1mnqqdrnyb<br />
<br />
[[Category:ARM]]<br />
[[Category:Pandaboard]]</div>Oleghttp://www.funtoo.org/wiki/Building_a_Kernel_from_SourceBuilding a Kernel from Source2013-04-20T11:19:06Z<p>Oleg: Reverted edits by 90.227.134.5 (talk) to last revision by Drobbins</p>
<hr />
<div>Setting up a proper kernel yourself - lean, mean and tailored to your hardware, is the challenge by which a linux user can graduate to becoming a Funtoo knight ;-)<br />
<br />
Even though many of us are using enterprise-ready kernels in datacenters, there is almost nobody who hasn't at least considered building a kernel for his laptop / PC.<br />
We are showing here how an intermediate Linux user can use an alternative to the standard beginners "genkernel" approach, to compile a custom kernel, in a relatively still speedy and easy set up.<br />
<br />
'''minimum requirements'''<br />
You should understand the way how things work in a terminal and how to use an editor and tweak config files. This is crucial.<br />
You don't need much knowledge about the linux kernel and it's internals. Nevertheless, you have to know at least where the files are located, how they are used and what is the file logic behind the overall structure. Otherwise you should consider using a non source based linux distribution.<br />
If you are scared now, don't worry - we are going to build a kernel the Funtoo way and you will pick up everthing necessary to accomplish this challenge, step by step, so the next time you do it yourself and become a real Funtoo knight!<br />
<br />
'''assumptions'''<br />
You start from an installed Funtoo system on the disk, or at least, you are on stage3 in a chrooted environment from a live cd, following somehow the Funto [[Installation (Tutorial)|Installation Tutorial]].<br />
<br />
In this case we are building a kernel that is booting root in LVM over encrypted LUKS container.<br />
If you don't have this setup, don't worry, you just don't need all the modules, but everything else is similar.<br />
<br />
<br />
= Getting everything in order to start =<br />
<br />
First there is the decision which linux kernel sources we need.<br />
There are plenty of them in the repositories around, often it is not easy to distinguish between them.<br />
<br />
I would always trust my distribution of choice and take what is has to offer - and funtoo has a lot to offer!<br />
<br />
I really do recommend (especially if it is your first time) to build a debian-sourced genkernel like described in chapter 5 "Using Debian-Sources with Genkernel" in the [[Funtoo_Linux_Kernels| Funtoo Kernels Tutorial]].<br />
<br />
From there you should have a running system booting nicely from your own build (just little bit bloated) kernel. This is more than you can expect from any other ready to go distribution.<br />
<br />
'''Attention'''<br />
We are using RedHat's dracut in order to build a nice initramfs (containing all the necessary tools and extra drivers our kernel might need to start the system).<br />
<br />
Although dracut is the way to go, more sophisticated and not as buggy as gentoo's genkernel approach, more and more funtoo geeks start using slashbeast's better-initramfs, which we will cover at the end of this howto!<br />
<br />
So after having set up a genkernel from debian or gentoo sources we are going to build a kernel with either (or both) dracut or/and better-initramfs.<br />
So gentoo sources with genkernel is always my backup if anything is not working correctly on my system. For the slightly more geeky approach with my own initram I am using pf-sources, ck-sources or any other more or less heavily patched sources.<br />
<br />
Let's go!<br />
<br />
== kernel sources ==<br />
We are going to use the kernel sources from the funtoo git repository.<br />
<br />
Which sources you like to use is up to you, and your needs.<br />
For my laptop or desktop system I am recommending any one of:<br />
<br />
sys-kernel/pf-sources<br />
sys-kernel/ck-sources<br />
sys-kernel/gentoo-sources<br />
sys-kernel/git-sources<br />
sys-kernel/sysrescue-std-sources<br />
sys-kernel/debian-sources<br />
<br />
Please, have a look in the ebuild description, look onto their homepage and take the one that suits you best!<br />
If you are unsure for now, use sys-kernel/gentoo-sources. That's always a safe bet for a general system.<br />
<br />
It is not a problem to have various kernels installed parallel, so go on with any one of them.<br />
<br />
I am going to use the sys-kernel/pf-sources now, as I already had the gentoo-sources installed.<br />
<br />
== prerequisites ==<br />
<br />
I don't know which tools you have already installed, so some information here might be redundant.<br />
It doesn't harm to just copy and paste and do some steps again.<br />
<br />
First, we look into our /etc/make.conf:<br />
<br />
<pre><br />
#These compiler flags are just tweaking (optimazation) and NOT necessary:<br />
CFLAGS="-O2 -pipe -march=native -ftracer -fforce-addr"<br />
CXXFLAGS="${CFLAGS} -fpermissive -fomit-frame-pointer"<br />
<br />
KDIR=/usr/src/linux<br />
<br />
KERNEL="symlink build"<br />
USE="$KERNEL ....here are your use flags...."<br />
## These modules are available:<br />
## DRACUT_MODULES="dracut_modules_biosdevname dracut_modules_btrfs dracut_modules_caps dracut_modules_crypt dracut_modules_crypt-gpg dracut_modules_dmraid dracut_modules_dmsquash-live dracut_modules_gensplash dracut_modules_iscsi dracut_modules_livenet dracut_modules_lvm dracut_modules_mdraid dracut_modules_multipath dracut_modules_nbd dracut_modules_nfs dracut_modules_plymouth dracut_modules_ssh-client dracut_modules_syslog"<br />
## We are using this ones for LVM / LUKS<br />
DRACUT_MODULES="crypt lvm plymouth biosdevname dmraid crypt-gpg dmsquash-live ssh-client syslog"<br />
</pre><br />
<br />
Now we are setting the package keywords:<br />
<pre><br />
/etc/portage/package.use/dracut:<br />
<console><br />
sys-kernel/dracut dm net device-mapper crypt lvm<br />
</console><br />
</pre><br />
If you don't have lvm over encrypted LUKS you probably just add the "net" keyword here, or "selinux".<br />
<br />
<br />
After that we are going to build our packages:<br />
<console><br />
# ##i##emerge -av app-portage/gentoolkit sys-kernel/pf-sources sys-kernel/dracut sys-boot/plymouth sys-boot/plymouth-openrc-plugin<br />
</console><br />
<br />
Finished? Well, then let's go on and<br />
<br />
== preparing the kernel ==<br />
<br />
We go now to the sources directory and enter the following commands to update the kernel's .config file:<br />
<console><br />
# ##i##cd /usr/src/linux/<br />
# ##i##make clean<br />
CLEAN .<br />
CLEAN arch/x86/kernel/acpi/realmode<br />
CLEAN arch/x86/kernel/cpu<br />
CLEAN arch/x86/kernel<br />
CLEAN arch/x86/vdso<br />
CLEAN arch/x86/lib<br />
CLEAN drivers/gpu/drm/radeon<br />
CLEAN drivers/net/wan<br />
CLEAN drivers/scsi/aic7xxx<br />
CLEAN drivers/tty/vt<br />
CLEAN drivers/video/logo<br />
CLEAN firmware<br />
CLEAN kernel<br />
CLEAN lib/raid6<br />
CLEAN lib<br />
CLEAN security/apparmor<br />
CLEAN security/selinux<br />
CLEAN usr<br />
CLEAN arch/x86/boot/compressed<br />
CLEAN arch/x86/boot<br />
CLEAN .tmp_versions<br />
CLEAN vmlinux System.map .tmp_kallsyms2.S .tmp_kallsyms1.o .tmp_kallsyms2.o .tmp_kallsyms1.S .tmp_vmlinux1 .tmp_vmlinux2 .tmp_System.map<br />
# ##i##zcat /proc/config.gz > /usr/src/linux/.config<br />
</console><br />
<br />
<console><br />
# ##i##make localmodconfig<br />
</console><br />
<br />
You will get some questions which you can answer mostly with either M (compiled as a module) or Y (compiled directly into the kernel).<br />
<br />
Enable different security models (SECURITY) [Y/n/?] y<br />
Enable the securityfs filesystem (SECURITYFS) [Y/?] y<br />
Socket and Networking Security Hooks (SECURITY_NETWORK) [Y/?] y<br />
Security hooks for pathname based access control (SECURITY_PATH) [Y/?] y<br />
Low address space for LSM to protect from user allocation (LSM_MMAP_MIN_ADDR) [65536] 65536<br />
NSA SELinux Support (SECURITY_SELINUX) [Y/n/?] y<br />
NSA SELinux boot parameter (SECURITY_SELINUX_BOOTPARAM) [N/y/?] n<br />
NSA SELinux runtime disable (SECURITY_SELINUX_DISABLE) [N/y/?] n<br />
NSA SELinux Development Support (SECURITY_SELINUX_DEVELOP) [Y/n/?] y<br />
NSA SELinux AVC Statistics (SECURITY_SELINUX_AVC_STATS) [Y/n/?] y<br />
NSA SELinux checkreqprot default value (SECURITY_SELINUX_CHECKREQPROT_VALUE) [1] 1<br />
NSA SELinux maximum supported policy format version (SECURITY_SELINUX_POLICYDB_VERSION_MAX) [Y/n/?] y<br />
NSA SELinux maximum supported policy format version value (SECURITY_SELINUX_POLICYDB_VERSION_MAX_VALUE) [19] 19<br />
TOMOYO Linux Support (SECURITY_TOMOYO) [Y/n/?] y<br />
Default maximal count for learning mode (SECURITY_TOMOYO_MAX_ACCEPT_ENTRY) [2048] 2048<br />
Default maximal count for audit log (SECURITY_TOMOYO_MAX_AUDIT_LOG) [1024] 1024<br />
Activate without calling userspace policy loader. (SECURITY_TOMOYO_OMIT_USERSPACE_LOADER) [Y/n/?] y<br />
AppArmor support (SECURITY_APPARMOR) [Y/n/?] y<br />
AppArmor boot parameter default value (SECURITY_APPARMOR_BOOTPARAM_VALUE) [1] 1<br />
Integrity Measurement Architecture(IMA) (IMA) [Y/n/?] y<br />
EVM support (EVM) [N/y/?] (NEW)<br />
Default security module<br />
1. SELinux (DEFAULT_SECURITY_SELINUX)<br />
2. TOMOYO (DEFAULT_SECURITY_TOMOYO)<br />
3. AppArmor (DEFAULT_SECURITY_APPARMOR)<br />
> 4. Unix Discretionary Access Controls (DEFAULT_SECURITY_DAC)<br />
choice[1-4?]: 4<br />
warning: (ACPI_HOTPLUG_CPU) selects ACPI_CONTAINER which has unmet direct dependencies (ACPI && EXPERIMENTAL)<br />
warning: (MEDIA_TUNER) selects MEDIA_TUNER_TEA5761 which has unmet direct dependencies (MEDIA_SUPPORT && VIDEO_MEDIA && I2C && EXPERIMENTAL)<br />
#<br />
# configuration written to .config<br />
#<br />
warning: (GFS2_FS) selects DLM which has unmet direct dependencies (EXPERIMENTAL && INET && SYSFS && CONFIGFS_FS && (IPV6 || IPV6=n))<br />
warning: (IMA) selects TCG_TPM which has unmet direct dependencies (HAS_IOMEM && EXPERIMENTAL)<br />
warning: (MEDIA_TUNER) selects MEDIA_TUNER_TEA5761 which has unmet direct dependencies (MEDIA_SUPPORT && VIDEO_MEDIA && I2C && EXPERIMENTAL)<br />
warning: (ACPI_HOTPLUG_CPU) selects ACPI_CONTAINER which has unmet direct dependencies (ACPI && EXPERIMENTAL)<br />
root@[~src/linux] #<br />
<br />
</pre><br />
<br />
Now comes the most adventurous part!<br />
<br />
= Building the Kernel =<br />
<console><br />
# ##i##make -j8 bzImage<br />
# ##i##make -j8 modules<br />
# ##i##make modules_install<br />
# ##i##make install<br />
</console><br />
<br />
<br />
'''Building an initramfs or not?'''<br />
<br />
The reason to build a kernel with an initramfs is mostly for interoperability (e.g. live-cd's) and special features like an included busybox, ssh, etc. But mostly, and that's why we are doing this here now, to have a proper kernel up and running quick'n dirty in a reasonable time without fighting hours and days until a more or less exotic hardware is perfectly run by the kernel. <br />
After having a proper basic kernel running with the help of an initramfs, I really recommend you to go a step further and build a true kernel with all features includes without an initramfs. But this could be pain in the ass and very time consuming - so we do it the funtoo way here - at least in the second example when we stick to better-initramfs instead of Red-Hat's ''dracut''.<br />
<br />
= Option one: Initrd with dracut =<br />
<br />
To build the initrd we just execute<br />
<br />
<console><br />
# ##i##dracut -f --fstab --xz /boot/initramfs-3.2.6-pf.img 3.2.6-pf<br />
</console><br />
<br />
Generally, this really should be enough!<br />
If you experience booting problems like missing modules / drivers then just boot from the genkernel section and fix the initrd building. You can look into the man page to tweak the command a bit (e.g. --add-drivers "xz dm_crypt" etc...).<br />
<br />
Ok let's go on and finish the taks, we are going to tell now grub how to boot off correctly!<br />
<br />
<pre><br />
root@[~src/linux] # nano /etc/boot.conf<br />
<br />
boot {<br />
generate grub<br />
default "Funtoo Linux dracut"<br />
timeout 3<br />
}<br />
<br />
"Funtoo Linux genkernel" {<br />
kernel kernel-genkernel[-v]<br />
initrd initramfs-genkernel[-v]<br />
params = quiet rootfstype=ext4<br />
params += luks enc_root=/dev/sda3<br />
params += lvm root=/dev/mapper/vg-root<br />
}<br />
<br />
"Funtoo Linux dracut" {<br />
kernel vmlinuz[-v]<br />
## this is the better-initramfs generated initrd<br />
initrd initramfs[-v].img<br />
params = quiet rootfstype=ext4<br />
params += luks enc_root=/dev/sda3<br />
params += lvm root=/dev/mapper/vg-root<br />
}<br />
<br />
</pre><br />
<br />
That's it almost!<br />
<br />
Now write to the grub.cfg with the new handy boot-update script from funtoo:<br />
<console><br />
root@[~src/linux] # boot-update -v<br />
</console><br />
<pre><br />
root@[~src/linux] # sudo boot-update -v<br />
<br />
boot-update 1.5.2 / Copyright 2009-2011 Funtoo Technologies<br />
<br />
[use option "-l" for license info, "-h" for help]<br />
<br />
* Generating config for grub...<br />
<br />
DEFAULT > Funtoo Linux - vmlinuz-3.2.6-pf<br />
Funtoo Linux genkernel - kernel-genkernel-x86_64-3.2.6-pf<br />
<br />
* Completed successfully.<br />
</pre><br />
<br />
Okay,... here you go..! :)<br />
<br />
Reboot and see how it works!<br />
<br />
= Option two: using better-initramfs =<br />
<br />
Piotr's better-initramfs is another approach that is tiny, nice and shiny and seems to become more and more a favourite among funtoo'ers. The biggest plus is that, once built it is kernel version independant.<br />
<br />
For using this you just do the following steps:<br />
<pre><br />
1. download sources<br />
2. build kernel with "make bzImage"<br />
3. download better-initramfs<br />
4. run better-initramfs<br />
5. adjust /etc/boot.conf<br />
</pre><br />
<br />
Here is how in detail:<br />
<br />
Assuming you did install already a genkernel backup or at least you have a working bzImage + modules installed, we rush forward to step 3:<br />
<br />
=== download better-initramfs ===<br />
<br />
<console><br />
➜ # cd /usr/src/;<br />
➜ # git clone https://github.com/slashbeast/better-initramfs.git<br />
<br />
➜ # /src # cd better-initramfs<br />
➜ # better-initramfs git:(master) ls<br />
AUTHORS LICENSE README.rst bootstrap output sourceroot<br />
ChangeLog Makefile TODO examples scripts<br />
</console><br />
<br />
=== build the better-initramfs ===<br />
<console><br />
➜ # better-initramfs git:(master) sudo bootstrap/bootstrap-all<br />
Passwort: xxx <br />
# from here go and grab a coffee<br />
➜ # sudo make prepare<br />
➜ # sudo make image<br />
➜ # sudo mv output/initramfs.cpio.gz /boot<br />
</console><br />
<br />
=== adjust grub ===<br />
<br />
Taking the above setup we edit the /etc/boot.conf<br />
as I installed genkernel first, and dracut after - you see this setup:<br />
<br />
<pre><br />
boot {<br />
generate grub<br />
default "Funtoo Linux"<br />
timeout 3<br />
}<br />
<br />
# Rootfs over lvm over luks<br />
# /dev/sda3 - encrypted lvm's pv<br />
# /dev/mapper/vg-root - rootfs's lv<br />
<br />
"Funtoo Linux" {<br />
kernel bzImage[-v]<br />
## this is the better-initramfs generated initrd<br />
initrd initramfs.cpio.gz<br />
params = quiet rootfstype=ext4<br />
params += luks enc_root=/dev/sda3<br />
params += lvm root=/dev/mapper/vg-root<br />
}<br />
<br />
"Funtoo Linux dracut" {<br />
kernel vmlinuz[-v]<br />
## this is the dracut generated initrd<br />
initrd initramfs[-v].img<br />
params = quiet rootfstype=ext4<br />
params += luks enc_root=/dev/sda3<br />
params += lvm root=/dev/mapper/vg-root<br />
}<br />
<br />
<br />
"Funtoo Linux genkernel" {<br />
kernel kernel-genkernel[-v]<br />
initrd initramfs-genkernel[-v]<br />
params = quiet rootfstype=ext4<br />
params += luks enc_root=/dev/sda3<br />
params += lvm root=/dev/mapper/vg-root<br />
}<br />
</pre><br />
Okay,... here you go..! :)<br />
<br />
update the grub.cfg, then reboot and see how it works!<br />
<br />
<console><br />
root@[~src/linux-3.2.6-pf] # boot-update -v <br />
<br />
boot-update 1.5.2 / Copyright 2009-2011 Funtoo Technologies<br />
<br />
[use option "-l" for license info, "-h" for help]<br />
<br />
* Generating config for grub...<br />
<br />
DEFAULT > Funtoo Linux better-initramfs - vmlinuz-3.2.6-pf<br />
Funtoo Linux dracut - vmlinuz-3.2.6-pf<br />
Funtoo Linux genkernel - kernel-genkernel-x86_64-3.2.6-ck<br />
<br />
* Completed successfully.<br />
<br />
root@[~src/linux-3.2.6-pf] #<br />
<br />
root@[~src/linux-3.2.6-pf] # reboot<br />
<br />
System going down for reboot!<br />
<br />
</console><br />
<br />
<br />
[[Category:HOWTO]]<br />
[[Category:Featured]]<br />
[[Category:Kernel]]</div>Oleghttp://www.funtoo.org/wiki/WelcomeWelcome2013-04-13T12:17:05Z<p>Oleg: Reverted edits by Rommersick101 (talk) to last revision by Palica</p>
<hr />
<div><div style="float:right; width: 35%"><br />
{{#widget:Donate|blurb=Your support helps Funtoo grow! Donate Today.}}<br />
<div class="boxy"><br />
== Get on the UserMap! ==<br />
{{#compound_query:[[Category:People]] [[Role type::Staff]];?Geoloc;icon=Purplemarker.png<br />
|[[Category:People]][[Role type::Contributor]];?Geoloc;icon=Orangemarker.png<br />
|[[Category:People]][[Role type::User]];?Geoloc;icon=Greenmarker.png<br />
|format=googlemaps3|height=275|zoom=1|type=hybrid|markercluster=yes}}<br />
See our full-size [[Usermap]] and find out how to become part of the Funtoo Universe!<br />
</div><br />
{{Litecoin|blurb=Check it out: Mine litecoins for Funtoo!}}<br />
<div class="boxy"><br />
=== Latest Commits: ===<br />
<ul><br />
<feed entries=7 url="https://github.com/funtoo/funtoo-overlay/commits/master.atom"><br />
<li>[{PERMALINK} <nowiki>{TITLE}</nowiki>]<br />
</feed><br />
</ul><br />
</div><br />
<br />
<div class="boxy"><br />
=== Featured Resources: ===<br />
<DynamicPageList><br />
category = Featured<br />
</DynamicPageList><br />
</div><br />
<br />
<div class="boxy2"><br />
=== [[image:Feed-icon-28x28.png|link=http://forums.funtoo.org/extern.php?action=feed&type=atom]] Latest Forum Posts ===<br />
<ul><br />
<feed entries=6 url="http://forums.funtoo.org/extern.php?action=feed&type=atom"><br />
<li>[{PERMALINK} <nowiki>{TITLE}</nowiki>]<br />
</feed><br />
</ul><br />
</div><br />
<br />
<div class="boxy2"><br />
=== [[image:Feed-icon-28x28.png|link=http://feeds.feedburner.com/planet_larry]] Planet Larry ===<br />
<ul><br />
<feed type="planet" entries=6 url="http://feeds.feedburner.com/planet_larry"><br />
<li>[{PERMALINK} <nowiki>{TITLE}</nowiki>]<br />
</feed><br />
</ul><br />
</div><br />
<br />
<br />
</div><br />
<br />
= Welcome to the Funtoo Wiki! =<br />
<br />
[[Funtoo Linux]] is a Linux-based operating system created by [[user:Drobbins|Daniel Robbins]], the creator and former Chief Architect of Gentoo Linux. <br />
<br />
Funtoo Linux is a Free software, or "Open Source" operating system. All distribution source code is freely available, and it can be used and distributed free of charge.<br />
<br />
== Featured Video ==<br />
<br />
In this video, Jonathan Vasquez ([[User:Fearedbliss|fearedbliss]]) of the Funtoo Linux Core Team walks you through the process of installing Funtoo Linux with ZFS. See the [[ZFS Install Guide]] for detailed instructions.<br />
<br />
{{#widget:YouTube|id=MXyBamArues|width=640|height=360}}<br />
<br />
== Meta-Distribution, Optimized ==<br />
<br />
Funtoo Linux is also a ''meta''-distribution, which means that it is built automatically from source code and is customized with the functionality that ''you'' want it to have, and ''without'' the unnecessary features and "bloat" that you want to avoid. <br />
<br />
In addition, a Funtoo Linux system is [[Download|optimized for your CPU]], and we offer optimized versions for ''Intel Core i7'', ''Intel Atom'', ''AMD Opteron'', and other processors and architectures. <br />
<br />
These combination of factors work together to create an extremely high-performance and flexible computing platform -- a platform where ''you'' are in control, and your system performs optimally. We believe that Funtoo Linux is the most ideal expression of how operating system technology "should" work, and we continually strive to make it better.<br />
<br />
== The Gentoo Ecosystem ==<br />
<br />
Our [[Core Team]] is focused on advancing the state-of-the-art in Linux distributions by developing our own improvements to Gentoo Linux, while remaining compatible with the upstream changes from the Gentoo Linux project. <br />
<br />
We are committed to maintaining high-levels of compatibility and collaboration with the Gentoo Linux project, and challenge ourselves to innovate while providing new approaches that can be easily leveraged by the Gentoo Community. We appreciate the support we receive from members of the Gentoo Community and strive to contribute back to the larger [[Gentoo Ecosystem]].<br />
<br />
== Ultimate Flexibility for Developers ==<br />
<br />
Does your Linux distribution allow multiple versions of <tt>php</tt>, <tt>[[python]]</tt> or <tt>ruby</tt> installed happily alongside each other? Funtoo Linux does. Are you tired of hand-building key packages from source to configure them exactly the way you want? Funtoo Linux allows you to tweak the build-time features of packages using handy things called USE variables. Other distributions are forced to either leave stuff out that you want, or include stuff you don't want.<br />
<br />
== Virtualization ==<br />
<br />
We support the [[OpenVZ]] project and build up-to-date Funtoo Linux OpenVZ containers that you can [[Download|download]]. Also see [[VagrantUp]] for a nice way to deploy VirtualBox-based Funtoo Linux systems. [[Metro]], our automated distro build tool, is capable of building OpenVZ, Linux VServer and [[Linux Containers]] (LXC) images. Funtoo Linux also makes an excellent virtualization host system for [[Xen]].<br />
<br />
== Features ==<br />
<br />
[[Funtoo Linux]] features native [[wikipedia:UTF-8|UTF-8]] support enabled by default, a [[wikipedia:Git (software)|git]]-based, [[Portage Tree|distributed Portage Tree]] and funtoo overlay, an enhanced [[Portage]] with more compact mini-manifest tree, automated imports of new [http://www.gentoo.org Gentoo] changes every 12 hours, [[GUID Booting Guide|GPT/GUID boot support]] and [[Boot-Update|streamlined boot configuration]], [[Funtoo Linux Networking|enhanced network configuration]], up-to-date [http://ftp.osuosl.org/pub/funtoo/funtoo-stable/ stable] and [http://ftp.osuosl.org/pub/funtoo/funtoo-current/ current] Funtoo [[Stage Tarball|stages]], all built using Funtoo's [[Metro]] build tool. We also offer Ubuntu Server, Debian, RHEL and Fedora-based [[Funtoo Linux Kernels|kernels]].<br />
<br />
Funtoo is currently supported on the following processor families :<br />
* PC-compatible, both 32 and 64-bit (''x86-32bit'', ''x86-64bit'')<br />
<br />
== Resources ==<br />
<br />
* Learn more about [[Funtoo Linux]].<br />
* Why you should [[Choose Funtoo]]: ...and how its different than other distros.<br />
* Visit [[:Category:Projects|Funtoo Linux Projects]] and also look at the stuff online for [[Metro]].<br />
* Learn [[:Category:Linux Core Concepts| Core Linux concepts]] from articles originally written by Daniel Robbins.<br />
<br />
<br />
__NOTOC__<br />
__NOTITLE__<br />
__NOEDITSECTION__<br />
<br />
[[Category:Funtoo|*]]</div>Oleghttp://www.funtoo.org/wiki/Funtoo_Linux_InstallationFuntoo Linux Installation2013-03-24T04:58:46Z<p>Oleg: /* /etc/make.conf */</p>
<hr />
<div>== Introduction ==<br />
<br />
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.<br />
<br />
=== Additional Resources === <br />
<br />
This document was written to help you install Funtoo Linux as efficiently as possible, with a minimum number of distracting options regarding system configuration. <br />
<br />
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.<br />
<br />
If you are installing Funtoo Linux on [[Funtoo Linux Installation on ARM|ARM]] architecture, please see [[Funtoo Linux Installation on ARM]] for notable differences regarding ARM support. An experimental Funtoo Linux build also exists for [[Funtoo Linux Installation on SPARC|SPARC]] platforms. See [[Funtoo Linux Installation on SPARC]]<br />
<br />
== Installation Overview ==<br />
<br />
This is a basic overview of the Funtoo installation process:<br />
<br />
# [[#Live CD|Download and boot the live CD of your choice]].<br />
# [[#Prepare Hard Disk|Prepare your disk]].<br />
# [[#Creating filesystems|Create]] and [[#Mounting filesystems|mount]] filesystems.<br />
# [[#Installing the Stage 3 tarball|Install the Funtoo stage tarball]] of your choice.<br />
# [[#Chroot into Funtoo|Chroot into your new system]].<br />
# [[#Downloading the Portage tree|Download the Portage tree]].<br />
# [[#Configuring your system|Configure your system]] and [[#Configuring your network|network]].<br />
# [[#Configuring and installing the Linux kernel|Install a kernel]].<br />
# [[#Installing a Bootloader|Install a bootloader]].<br />
# [[#Finishing Steps|Complete final steps]].<br />
# [[#Restart your system|Reboot and enjoy]].<br />
<br />
=== Live CD ===<br />
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.<br />
<br />
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.<br />
<br />
To begin a Funtoo Linux installation, download SystemRescueCD from:<br />
<br />
* Main US mirror: [http://ftp.osuosl.org/pub/funtoo/distfiles/sysrescuecd/systemrescuecd-x86-3.4.2.iso The Oregon State University Open Source Lab]<br />
* Main EU mirror: [http://ftp.heanet.ie/mirrors/funtoo/distfiles/sysrescuecd/systemrescuecd-x86-3.4.2.iso HEAnet] or use your preferred live media. Insert it into your disc drive, and boot from it. If using an older version of 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 used to boot in 32-bit mode though the latest version attempts to automatically detect 64-bit processors.<br />
<br />
=== Prepare Hard Disk ===<br />
==== Partitions ====<br />
<br />
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:<br />
<br />
===== GPT Partitions =====<br />
<br />
* Newer, preferred format for Linux systems<br />
* Supports 2 TB+ hard drives for booting<br />
* Supports hundreds of partitions per disk of any size<br />
* Requires legacy BIOS boot partition (~32 MB) to be created if system does not use EFI<br />
* Requires bootloader with support for GPT such as GRUB 2, EXTLINUX, or a patched version of GRUB Legacy<br />
<br />
===== MBR Partitions =====<br />
<br />
* Legacy, DOS partitioning scheme<br />
* Only 4 primary partitions per disk; after that, you must use "logical" partitions<br />
* Does not support 2 TB+ disks for booting<br />
* Compatible with certain problematic systems (such as the HP ProBook 4520)<br />
* Dual-boot with Windows for BIOS systems (Windows handle GPT only on true EFI systems, whatever version it is)<br />
* Multiple boot loader options, e.g. GRUB 2, GRUB Legacy, lilo<br />
<br />
{{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.}}<br />
<br />
==== Partitioning Using gdisk ====<br />
<br />
===== Notes Before We Begin =====<br />
<br />
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.<br />
<br />
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 <br />
'''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.<br />
<br />
Advanced users may be interested in the following topics:<br />
<br />
* [[GUID Booting Guide]]<br />
* [[Rootfs over encrypted lvm]]<br />
* [[Rootfs over encrypted lvm over raid-1 on GPT]]<br />
* '''NEW!''' '''[[ZFS Install Guide]]'''<br />
* '''NEW!''' '''[[ZFS rootfs over encrypted container]]'''<br />
<br />
===== Using gdisk =====<br />
<br />
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:<br />
<br />
<console># ##i##gdisk /dev/sda</console><br />
You should find <tt>gdisk</tt> very similar to <tt>fdisk</tt>. Here is the partition table we want to end up with:<br />
<br />
<console>Command (? for help): ##i##p<br />
Disk /dev/sda: 234441648 sectors, 111.8 GiB<br />
Logical sector size: 512 bytes<br />
Disk identifier (GUID): A4E5208A-CED3-4263-BB25-7147DC426931<br />
Partition table holds up to 128 entries<br />
First usable sector is 34, last usable sector is 234441614<br />
Partitions will be aligned on 2048-sector boundaries<br />
Total free space is 2014 sectors (1007.0 KiB)<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 206847 500.0 MiB 8300 Linux filesystem<br />
2 206848 272383 32.0 MiB EF02 BIOS boot partition<br />
3 272384 8660991 4.0 GiB 8200 Linux swap<br />
4 8660992 234441614 107.7 GiB 8300 Linux filesystem<br />
<br />
Command (? for help): </console><br />
<br />
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.<br />
<br />
===== For new <tt>gdisk</tt> users =====<br />
<br />
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.<br />
<br />
Within <tt>gdisk</tt>, follow these steps:<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##1 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+500M ↵<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
'''Create Partition 2''' (GRUB):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##2 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+32M ↵<br />
Hex Code: ##i##EF02 ↵<br />
</console><br />
<br />
'''Create Partition 3''' (swap):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##3 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+4G ↵<br />
Hex Code: ##i##8200 ↵<br />
</console><br />
<br />
'''Create Partition 4''' (root):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##4 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵##!i## (for rest of disk)<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
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:<br />
<br />
'''Write Partition Table To Disk''':<br />
<br />
<console><br />
Command: ##i##w ↵<br />
Do you want to proceed? (Y/N): ##i##Y ↵<br />
</console><br />
<br />
The partition table will now be written to disk and <tt>gdisk</tt> will close.<br />
<br />
Now, your GPT/GUID partitions have been created, and will show up as the following ''block devices'' under Linux:<br />
<br />
* <tt>/dev/sda1</tt>, which will be used to hold the <tt>/boot</tt> filesystem, <br />
* <tt>/dev/sda2</tt>, which will be used directly by the new GRUB,<br />
* <tt>/dev/sda3</tt>, which will be used for swap space, and <br />
* <tt>/dev/sda4</tt>, which will hold your root filesystem.<br />
<br />
===== For Previous fdisk users =====<br />
<br />
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.<br />
<br />
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>.<br />
<br />
===== Partitioning Recommendations =====<br />
<br />
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>:<br />
<br />
{| {{table}} <br />
!Partition<br />
!Size<br />
!MBR Block Device (<tt>fdisk</tt>)<br />
!GPT Block Device (<tt>gdisk</tt>)<br />
!Filesystem<br />
!MBR Code<br />
!GPT Code<br />
|-<br />
|<tt>/boot</tt><br />
|500 MB<br />
|<tt>/dev/sda1</tt><br />
|<tt>/dev/sda1</tt><br />
|ext2<br />
|83<br />
|8300<br />
|-<br />
|GRUB boot loader partition<br />
|32 MB<br />
| ''not required for MBR''<br />
|<tt>/dev/sda2</tt><br />
|For GPT/GUID only, skip for MBR - no filesystem.<br />
|''N/A''<br />
|EF02<br />
|-<br />
|swap<br />
|2x RAM for low-memory systems and production servers; otherwise 2GB.<br />
|<tt>/dev/sda2</tt><br />
|<tt>/dev/sda3</tt><br />
|swap (default)<br />
|82<br />
|8200<br />
|-<br />
|<tt>/</tt> (root)<br />
|Rest of the disk, minimum of 10GB.<br />
|<tt>/dev/sda3</tt><br />
|<tt>/dev/sda4</tt><br />
|XFS recommended, alternatively ext4<br />
|83<br />
|8300<br />
|-<br />
|<tt>/home</tt> (optional) <br />
|User storage and media. Typically most of the disk.<br />
|<tt>/dev/sda4</tt> (if created)<br />
|<tt>/dev/sda5</tt> (if created)<br />
|XFS recommended, alternatively ext4<br />
|83<br />
|8300<br />
|-<br />
| LVM (optional)<br />
| If you want to create an LVM volume.<br />
| <tt>/dev/sda4</tt> (PV, if created)<br />
| <tt>/dev/sda5</tt> (PV, if created)<br />
| LVM PV<br />
| 8E<br />
| 8E00<br />
|}<br />
<br />
==== Creating filesystems ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<br />
<console><br />
# ##i##mke2fs -t ext2 /dev/sda1 <br />
# ##i##mkfs.xfs /dev/sda4<br />
# ##i##mkswap /dev/sda3<br />
# ##i##swapon /dev/sda3<br />
</console><br />
<br />
==== Mounting filesystems ====<br />
<br />
Mount the newly-created filesystems as follows, creating <tt>/mnt/funtoo</tt> as the installation mount point:<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo<br />
# ##i##mount /dev/sda4 /mnt/funtoo<br />
# ##i##mkdir /mnt/funtoo/boot<br />
# ##i##mount /dev/sda1 /mnt/funtoo/boot<br />
</console><br />
<br />
Optionally, if you have a separate filesystem for <tt>/home</tt> or anything else:<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo/home<br />
# ##i##mount /dev/sda5 /mnt/funtoo/home<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##chmod 1777 /mnt/funtoo/tmp<br />
</console><br />
<br />
=== Installing the Stage 3 tarball ===<br />
==== Stage 3 tarball ====<br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
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:<br />
<br />
<console><br />
# ##i##date<br />
Fri Jul 15 19:47:18 UTC 2011<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##date 071620002011<br />
Fri Jul 16 20:00:00 UTC 2011<br />
</console><br />
<br />
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:<br />
<br />
<console># ##i##cd /mnt/funtoo<br />
# ##i##wget http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-64bit/generic_64/stage3-latest.tar.xz<br />
</console><br />
<br />
<br />
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.<br />
<br />
Once the stage is downloaded, extract the contents with the following command, substituting in the actual name of your stage 3 tarball:<br />
<console><br />
# ##i##tar xJpf stage3-latest.tar.xz<br />
</console><br />
<br />
{{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.}}<br />
<br />
=== Chroot into Funtoo ===<br />
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:<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
# ##i##mount --bind /proc proc<br />
# ##i##mount --bind /dev dev<br />
</console><br />
<br />
You'll also want to copy over <tt>resolv.conf</tt> in order to have proper DNS name resolution from inside the chroot:<br />
<console><br />
# ##i##cp /etc/resolv.conf etc<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l<br />
</console><br />
<br />
{{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.}}<br />
{{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.}}<br />
<br />
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:<br />
<console><br />
# ##i##export PS1="(chroot) $PS1"<br />
</console><br />
<br />
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.<br />
<br />
=== Downloading the Portage tree ===<br />
<br />
{{fancynote|For an alternative way to do this, see [[Installing Portage From Snapshot]].}}<br />
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]:<br />
<br />
<console><br />
(chroot) # ##i##emerge --sync<br />
</console><br />
<br />
{{fancyimportant|If you receive the error with initial <tt>emerge --sync</tt> due to git protocol restrictions, change <tt>SYNC</tt> variable in <tt>/etc/portage/make.conf</tt>}}<br />
<pre><br />
SYNC="https://github.com/funtoo/ports-2012.git"<br />
</pre><br />
<br />
<br />
=== Configuring your system ===<br />
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:<br />
<br />
{| {{table}}<br />
!File<br />
!Do I need to change it?<br />
!Description<br />
|-<br />
|<tt>/etc/fstab</tt><br />
|'''YES - required'''<br />
|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.<br />
|-<br />
|<tt>/etc/localtime</tt><br />
|''Maybe - recommended''<br />
|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) <br />
|-<br />
|<tt>/etc/make.conf<br/>/etc/portage/make.conf&nbsp;(new&nbsp;location)</tt><br />
|''Maybe - recommended''<br />
|Parameters used by gcc (compiler), portage, and make. It's a good idea to set MAKEOPTS. This is covered later in this document.<br />
|-<br />
|<tt>/etc/conf.d/hostname</tt><br />
|''Maybe - recommended''<br />
|Used to set system hostname. Set to the fully-qualified (with dots) name. Defaults to <tt>localhost</tt> if not set.<br />
|-<br />
|<tt>/etc/hosts</tt><br />
|''No''<br />
| You no longer need to manually set the hostname in this file. This file is automatically generated by <tt>/etc/init.d/hostname</tt>.<br />
|-<br />
|<tt>/etc/conf.d/keymaps</tt><br />
|Optional<br />
|Keyboard mapping configuration file (for console pseudo-terminals). Set if you have a non-US keyboard. See [[Funtoo Linux Localization]].<br />
|-<br />
|<tt>/etc/conf.d/hwclock</tt><br />
|Optional<br />
|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.<br />
|-<br />
|<tt>/etc/conf.d/modules</tt><br />
|Optional<br />
|Kernel modules to load automatically at system startup. Typically not required. See [[Additional Kernel Resources]] for more info.<br />
|-<br />
|<tt>profiles</tt><br />
|Optional<br />
|Some useful portage settings that may help speed up intial configuration.<br />
|}<br />
<br />
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]])<br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
==== /etc/fstab ====<br />
<br />
<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:<br />
<br />
<console><br />
(chroot) # ##i##nano -w /etc/fstab<br />
</console><br />
<br />
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.<br />
<br />
<pre><br />
# The root filesystem should have a pass number of either 0 or 1.<br />
# All other filesystems should have a pass number of 0 or greater than 1.<br />
#<br />
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.<br />
#<br />
# See the manpage fstab(5) for more information.<br />
#<br />
# <fs> <mountpoint> <type> <opts> <dump/pass><br />
<br />
/dev/sda1 /boot ext2 noatime 1 2<br />
/dev/sda3 none swap sw 0 0<br />
/dev/sda4 / xfs noatime 0 1<br />
#/dev/cdrom /mnt/cdrom auto noauto,ro 0 0<br />
</pre><br />
<br />
==== /etc/localtime ====<br />
<br />
<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. <br />
<br />
<pre><br />
(chroot) # ln -sf /usr/share/zoneinfo/America/Montreal /etc/localtime<br />
</pre><br />
<br />
The above sets the timezone to Eastern Time Canada. Go to <tt>/usr/share/zoneinfo</tt> to see which values to use.<br />
<br />
==== /etc/make.conf ====<br />
<br />
{{fancynote|This file is the symlink to /etc/portage/make.conf, new default location, edit /etc/portage/make.conf.}}<br />
<br />
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:<br />
<br />
<pre><br />
MAKEOPTS="-j3" <br />
</pre><br />
<br />
If you are unsure about how many processors/threads you have then use /proc/cpuinfo to help you.<br />
<console><br />
(chroot) # ##i##grep "processor" /proc/cpuinfo | wc -l<br />
16<br />
</console><br />
<br />
Set MAKEOPTS to this number plus one:<br />
<br />
<pre><br />
MAKEOPTS="-j17"<br />
</pre><br />
<br />
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].<br />
<br />
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:<br />
<br />
<pre><br />
LINGUAS="fr"<br />
</pre><br />
<br />
==== /etc/conf.d/hwclock ====<br />
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.<br />
<console><br />
(chroot) # ##i##nano -w /etc/conf.d/hwclock<br />
</console><br />
<br />
==== Localization ====<br />
<br />
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]].<br />
<br />
==== Profiles ====<br />
<br />
[[Funtoo 1.0 Profile|Funtoo profiles]] are used to define defaults for Portage specific to your needs. There are 4 basic profile types: arch, build, [[Flavors and Mix-ins|flavor, and mix-ins]]:<br />
<br />
;arch: typically <tt>x86-32bit</tt> or <tt>x86-64bit</tt>, this defines the processor type and support of your system. This is defined when your stage was built and should not be changed.<br />
;build: defines whether your system is a <tt>current</tt>, <tt>stable</tt> or <tt>experimental</tt> build. <tt>current</tt> systems will have newer packages unmasked than <tt>stable</tt> systems.<br />
;flavor: defines the general type of system, such as <tt>server</tt> or <tt>desktop</tt>, and will set default USE flags appropriate for your needs.<br />
;mix-ins: define various optional settings that you may be interested in enabling.<br />
<br />
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.<br />
<br />
Remember that profiles can often be inherited. For example, the <tt>desktop</tt> flavor inherits the <tt>workstation</tt> flavor settings, which in turn inherits the <tt>X</tt> and <tt>audio</tt> mix-ins. You can view this by inspecting the <tt>parent</tt> files defined in each profile, which can be found in <tt>/usr/portage/profiles/funtoo/1.0/linux-gnu</tt>:<br />
<br />
<console><br />
(chroot) # ##i##cd /usr/portage/profiles/funtoo/1.0/linux-gnu/<br />
(chroot) # ##i##ls<br />
arch/ eapi make.defaults package.use/ packages.build use.force<br />
build/ flavor/ mix-ins/ package.use.mask/ parent <br />
(chroot) # ##i##cat flavor/desktop/parent <br />
../workstation<br />
../../mix-ins/print<br />
(chroot) # ##i##cat flavor/workstation/parent <br />
../core<br />
../../mix-ins/X<br />
../../mix-ins/audio<br />
../../mix-ins/dvd<br />
../../mix-ins/media<br />
../../mix-ins/console-extras<br />
(chroot) # <br />
</console><br />
<br />
To view installed profiles:<br />
<console><br />
(chroot) # ##i##eselect profile list<br />
</console><br />
<br />
To change the profile flavor:<br />
<console><br />
(chroot) # ##i##eselect profile set-flavor 7<br />
</console><br />
<br />
To add a mix-in:<br />
<br />
<console><br />
(chroot) # ##i##eselect profile add 10<br />
</console><br />
<br />
Remember if you add by string; add a 'gentoo:' to the beginning of the profile name ie:<br />
<console><br />
(chroot) # ##i## eselect profile add gentoo:funtoo/1.0/linux-gnu/mix-ins/console-extras<br />
</console><br />
<br />
=== Configuring and installing the Linux kernel ===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Click [http://wiki.debian.org/DebianKernel here] for a list of all architectures the Debian kernel supports. <br />
<br />
{{fancyimportant|<tt>debian-sources</tt> with <tt>binary</tt> USE flag requires at least 12GB in /var/tmp}}<br />
<br />
<console><br />
(chroot) # ##i##echo "sys-kernel/debian-sources binary" >> /etc/portage/package.use<br />
(chroot) # ##i##emerge debian-sources<br />
</console><br />
<br />
All done!<br />
<br />
{{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>.}}<br />
<br />
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.<br />
<br />
The next step is to configure your boot loader so that your new kernel loads when the system boots.<br />
<br />
=== Installing a Bootloader ===<br />
<br />
==== Installing Grub ====<br />
<br />
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.<br />
<br />
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>.<br />
<br />
<console><br />
(chroot) # ##i##emerge boot-update<br />
</console><br />
<br />
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>. <br />
<br />
<tt>/etc/boot.conf</tt> should now look like this:<br />
<br />
<pre><br />
boot {<br />
generate grub<br />
default "Funtoo Linux genkernel"<br />
timeout 3 <br />
}<br />
<br />
"Funtoo Linux" {<br />
kernel bzImage[-v]<br />
# params += nomodeset<br />
}<br />
<br />
"Funtoo Linux genkernel" {<br />
kernel kernel[-v]<br />
initrd initramfs[-v]<br />
params += real_root=auto <br />
# params += nomodeset<br />
} <br />
</pre><br />
<br />
Please read <tt>man boot.conf</tt> for further details.<br />
<br />
===== Running grub-install and boot-update =====<br />
<br />
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:<br />
<br />
<console><br />
(chroot) # ##i##grub-install --no-floppy /dev/sda<br />
(chroot) # ##i##boot-update<br />
</console><br />
<br />
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.<br />
<br />
OK - your system should be ready to boot! Well, there are a few more loose ends...<br />
<br />
==== Installing Syslinux/Extlinux ====<br />
<br />
An alternate Bootloader is Extlinux, for installing it see the [[Extlinux|extlinux Guide]].<br />
<br />
=== Configuring your network ===<br />
<br />
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.<br />
<br />
==== Wi-Fi ====<br />
<br />
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:<br />
<br />
<console><br />
# ##i##emerge linux-firmware<br />
# ##i##emerge networkmanager<br />
# ##i##rc-update add NetworkManager default<br />
</console><br />
<br />
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.<br />
<br />
After you reboot into Funtoo Linux, you will be able to add a Wi-Fi connection this way:<br />
<br />
<console><br />
# ##i##addwifi -S wpa -K 'wifipassword' mywifinetwork<br />
</console><br />
<br />
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.<br />
<br />
==== Desktop (Wired Ethernet) ====<br />
<br />
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:<br />
<br />
<console><br />
# ##i##rc-update add dhcpcd default<br />
</console><br />
<br />
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.<br />
<br />
==== Server (Static IP) ====<br />
<br />
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.<br />
<br />
=== Finishing Steps ===<br />
<br />
==== Set your root password ====<br />
It's imperative that you set your root password before rebooting so that you can log in.<br />
<console><br />
(chroot) # ##i##passwd<br />
</console><br />
<br />
===Restart your system ===<br />
<br />
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.<br />
<br />
Leave the chroot, change directory to /, unmount your Funtoo partitions, and reboot.<br />
<console><br />
(chroot) # ##i##exit<br />
# ##i##cd /<br />
# ##i##umount /mnt/funtoo/boot /mnt/funtoo/dev /mnt/funtoo/proc /mnt/funtoo<br />
# ##i##reboot<br />
</console><br />
<br />
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!<br />
<br />
===Next Steps===<br />
<br />
To learn how to customize and start using Funtoo Linux, see [[Funtoo Linux First Steps]].<br />
<br />
If your system did not boot correctly, see [[Installation Troubleshooting]] for steps you can take to resolve the problem.<br />
<br />
[[Category:HOWTO]]<br />
[[Category:Install]]</div>Oleghttp://www.funtoo.org/wiki/Funtoo_Linux_InstallationFuntoo Linux Installation2013-03-23T04:38:11Z<p>Oleg: Reverted edits by Ipodsoft (talk) to last revision by Fearedbliss</p>
<hr />
<div>== Introduction ==<br />
<br />
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.<br />
<br />
=== Additional Resources === <br />
<br />
This document was written to help you install Funtoo Linux as efficiently as possible, with a minimum number of distracting options regarding system configuration. <br />
<br />
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.<br />
<br />
If you are installing Funtoo Linux on [[Funtoo Linux Installation on ARM|ARM]] architecture, please see [[Funtoo Linux Installation on ARM]] for notable differences regarding ARM support. An experimental Funtoo Linux build also exists for [[Funtoo Linux Installation on SPARC|SPARC]] platforms. See [[Funtoo Linux Installation on SPARC]]<br />
<br />
== Installation Overview ==<br />
<br />
This is a basic overview of the Funtoo installation process:<br />
<br />
# [[#Live CD|Download and boot the live CD of your choice]].<br />
# [[#Prepare Hard Disk|Prepare your disk]].<br />
# [[#Creating filesystems|Create]] and [[#Mounting filesystems|mount]] filesystems.<br />
# [[#Installing the Stage 3 tarball|Install the Funtoo stage tarball]] of your choice.<br />
# [[#Chroot into Funtoo|Chroot into your new system]].<br />
# [[#Downloading the Portage tree|Download the Portage tree]].<br />
# [[#Configuring your system|Configure your system]] and [[#Configuring your network|network]].<br />
# [[#Configuring and installing the Linux kernel|Install a kernel]].<br />
# [[#Installing a Bootloader|Install a bootloader]].<br />
# [[#Finishing Steps|Complete final steps]].<br />
# [[#Restart your system|Reboot and enjoy]].<br />
<br />
=== Live CD ===<br />
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.<br />
<br />
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.<br />
<br />
To begin a Funtoo Linux installation, download SystemRescueCD from:<br />
<br />
* Main US mirror: [http://ftp.osuosl.org/pub/funtoo/distfiles/sysrescuecd/systemrescuecd-x86-3.4.2.iso The Oregon State University Open Source Lab]<br />
* Main EU mirror: [http://ftp.heanet.ie/mirrors/funtoo/distfiles/sysrescuecd/systemrescuecd-x86-3.4.2.iso HEAnet] or use your preferred live media. Insert it into your disc drive, and boot from it. If using an older version of 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 used to boot in 32-bit mode though the latest version attempts to automatically detect 64-bit processors.<br />
<br />
=== Prepare Hard Disk ===<br />
==== Partitions ====<br />
<br />
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:<br />
<br />
===== GPT Partitions =====<br />
<br />
* Newer, preferred format for Linux systems<br />
* Supports 2 TB+ hard drives for booting<br />
* Supports hundreds of partitions per disk of any size<br />
* Requires legacy BIOS boot partition (~32 MB) to be created if system does not use EFI<br />
* Requires bootloader with support for GPT such as GRUB 2, EXTLINUX, or a patched version of GRUB Legacy<br />
<br />
===== MBR Partitions =====<br />
<br />
* Legacy, DOS partitioning scheme<br />
* Only 4 primary partitions per disk; after that, you must use "logical" partitions<br />
* Does not support 2 TB+ disks for booting<br />
* Compatible with certain problematic systems (such as the HP ProBook 4520)<br />
* Dual-boot with Windows for BIOS systems (Windows handle GPT only on true EFI systems, whatever version it is)<br />
* Multiple boot loader options, e.g. GRUB 2, GRUB Legacy, lilo<br />
<br />
{{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.}}<br />
<br />
==== Partitioning Using gdisk ====<br />
<br />
===== Notes Before We Begin =====<br />
<br />
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.<br />
<br />
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 <br />
'''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.<br />
<br />
Advanced users may be interested in the following topics:<br />
<br />
* [[GUID Booting Guide]]<br />
* [[Rootfs over encrypted lvm]]<br />
* [[Rootfs over encrypted lvm over raid-1 on GPT]]<br />
* '''NEW!''' '''[[ZFS Install Guide]]'''<br />
* '''NEW!''' '''[[ZFS rootfs over encrypted container]]'''<br />
<br />
===== Using gdisk =====<br />
<br />
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:<br />
<br />
<console># ##i##gdisk /dev/sda</console><br />
You should find <tt>gdisk</tt> very similar to <tt>fdisk</tt>. Here is the partition table we want to end up with:<br />
<br />
<console>Command (? for help): ##i##p<br />
Disk /dev/sda: 234441648 sectors, 111.8 GiB<br />
Logical sector size: 512 bytes<br />
Disk identifier (GUID): A4E5208A-CED3-4263-BB25-7147DC426931<br />
Partition table holds up to 128 entries<br />
First usable sector is 34, last usable sector is 234441614<br />
Partitions will be aligned on 2048-sector boundaries<br />
Total free space is 2014 sectors (1007.0 KiB)<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 206847 500.0 MiB 8300 Linux filesystem<br />
2 206848 272383 32.0 MiB EF02 BIOS boot partition<br />
3 272384 8660991 4.0 GiB 8200 Linux swap<br />
4 8660992 234441614 107.7 GiB 8300 Linux filesystem<br />
<br />
Command (? for help): </console><br />
<br />
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.<br />
<br />
===== For new <tt>gdisk</tt> users =====<br />
<br />
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.<br />
<br />
Within <tt>gdisk</tt>, follow these steps:<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##1 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+500M ↵<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
'''Create Partition 2''' (GRUB):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##2 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+32M ↵<br />
Hex Code: ##i##EF02 ↵<br />
</console><br />
<br />
'''Create Partition 3''' (swap):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##3 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+4G ↵<br />
Hex Code: ##i##8200 ↵<br />
</console><br />
<br />
'''Create Partition 4''' (root):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##4 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵##!i## (for rest of disk)<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
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:<br />
<br />
'''Write Partition Table To Disk''':<br />
<br />
<console><br />
Command: ##i##w ↵<br />
Do you want to proceed? (Y/N): ##i##Y ↵<br />
</console><br />
<br />
The partition table will now be written to disk and <tt>gdisk</tt> will close.<br />
<br />
Now, your GPT/GUID partitions have been created, and will show up as the following ''block devices'' under Linux:<br />
<br />
* <tt>/dev/sda1</tt>, which will be used to hold the <tt>/boot</tt> filesystem, <br />
* <tt>/dev/sda2</tt>, which will be used directly by the new GRUB,<br />
* <tt>/dev/sda3</tt>, which will be used for swap space, and <br />
* <tt>/dev/sda4</tt>, which will hold your root filesystem.<br />
<br />
===== For Previous fdisk users =====<br />
<br />
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.<br />
<br />
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>.<br />
<br />
===== Partitioning Recommendations =====<br />
<br />
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>:<br />
<br />
{| {{table}} <br />
!Partition<br />
!Size<br />
!MBR Block Device (<tt>fdisk</tt>)<br />
!GPT Block Device (<tt>gdisk</tt>)<br />
!Filesystem<br />
!MBR Code<br />
!GPT Code<br />
|-<br />
|<tt>/boot</tt><br />
|500 MB<br />
|<tt>/dev/sda1</tt><br />
|<tt>/dev/sda1</tt><br />
|ext2<br />
|83<br />
|8300<br />
|-<br />
|GRUB boot loader partition<br />
|32 MB<br />
| ''not required for MBR''<br />
|<tt>/dev/sda2</tt><br />
|For GPT/GUID only, skip for MBR - no filesystem.<br />
|''N/A''<br />
|EF02<br />
|-<br />
|swap<br />
|2x RAM for low-memory systems and production servers; otherwise 2GB.<br />
|<tt>/dev/sda2</tt><br />
|<tt>/dev/sda3</tt><br />
|swap (default)<br />
|82<br />
|8200<br />
|-<br />
|<tt>/</tt> (root)<br />
|Rest of the disk, minimum of 10GB.<br />
|<tt>/dev/sda3</tt><br />
|<tt>/dev/sda4</tt><br />
|XFS recommended, alternatively ext4<br />
|83<br />
|8300<br />
|-<br />
|<tt>/home</tt> (optional) <br />
|User storage and media. Typically most of the disk.<br />
|<tt>/dev/sda4</tt> (if created)<br />
|<tt>/dev/sda5</tt> (if created)<br />
|XFS recommended, alternatively ext4<br />
|83<br />
|8300<br />
|-<br />
| LVM (optional)<br />
| If you want to create an LVM volume.<br />
| <tt>/dev/sda4</tt> (PV, if created)<br />
| <tt>/dev/sda5</tt> (PV, if created)<br />
| LVM PV<br />
| 8E<br />
| 8E00<br />
|}<br />
<br />
==== Creating filesystems ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<br />
<console><br />
# ##i##mke2fs -t ext2 /dev/sda1 <br />
# ##i##mkfs.xfs /dev/sda4<br />
# ##i##mkswap /dev/sda3<br />
# ##i##swapon /dev/sda3<br />
</console><br />
<br />
==== Mounting filesystems ====<br />
<br />
Mount the newly-created filesystems as follows, creating <tt>/mnt/funtoo</tt> as the installation mount point:<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo<br />
# ##i##mount /dev/sda4 /mnt/funtoo<br />
# ##i##mkdir /mnt/funtoo/boot<br />
# ##i##mount /dev/sda1 /mnt/funtoo/boot<br />
</console><br />
<br />
Optionally, if you have a separate filesystem for <tt>/home</tt> or anything else:<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo/home<br />
# ##i##mount /dev/sda5 /mnt/funtoo/home<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##chmod 1777 /mnt/funtoo/tmp<br />
</console><br />
<br />
=== Installing the Stage 3 tarball ===<br />
==== Stage 3 tarball ====<br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
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:<br />
<br />
<console><br />
# ##i##date<br />
Fri Jul 15 19:47:18 UTC 2011<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##date 071620002011<br />
Fri Jul 16 20:00:00 UTC 2011<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
# ##i##wget -O - http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-64bit/generic_64/stage3-latest.tar.xz | tar xfvJp -<br />
</console><br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
=== Chroot into Funtoo ===<br />
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:<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
# ##i##mount --bind /proc proc<br />
# ##i##mount --bind /dev dev<br />
</console><br />
<br />
You'll also want to copy over <tt>resolv.conf</tt> in order to have proper DNS name resolution from inside the chroot:<br />
<console><br />
# ##i##cp /etc/resolv.conf etc<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l<br />
</console><br />
<br />
{{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.}}<br />
{{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.}}<br />
<br />
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:<br />
<console><br />
# ##i##export PS1="(chroot) $PS1"<br />
</console><br />
<br />
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.<br />
<br />
=== Downloading the Portage tree ===<br />
<br />
{{fancynote|For an alternative way to do this, see [[Installing Portage From Snapshot]].}}<br />
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]:<br />
<br />
<console><br />
(chroot) # ##i##emerge --sync<br />
</console><br />
<br />
{{fancyimportant|If you receive the error with initial <tt>emerge --sync</tt> due to git protocol restrictions, change <tt>SYNC</tt> variable in <tt>/etc/portage/make.conf</tt>}}<br />
<pre><br />
SYNC="https://github.com/funtoo/ports-2012.git"<br />
</pre><br />
<br />
<br />
=== Configuring your system ===<br />
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:<br />
<br />
{| {{table}}<br />
!File<br />
!Do I need to change it?<br />
!Description<br />
|-<br />
|<tt>/etc/fstab</tt><br />
|'''YES - required'''<br />
|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.<br />
|-<br />
|<tt>/etc/localtime</tt><br />
|''Maybe - recommended''<br />
|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) <br />
|-<br />
|<tt>/etc/make.conf<br/>/etc/portage/make.conf&nbsp;(new&nbsp;location)</tt><br />
|''Maybe - recommended''<br />
|Parameters used by gcc (compiler), portage, and make. It's a good idea to set MAKEOPTS. This is covered later in this document.<br />
|-<br />
|<tt>/etc/conf.d/hostname</tt><br />
|''Maybe - recommended''<br />
|Used to set system hostname. Set to the fully-qualified (with dots) name. Defaults to <tt>localhost</tt> if not set.<br />
|-<br />
|<tt>/etc/hosts</tt><br />
|''No''<br />
| You no longer need to manually set the hostname in this file. This file is automatically generated by <tt>/etc/init.d/hostname</tt>.<br />
|-<br />
|<tt>/etc/conf.d/keymaps</tt><br />
|Optional<br />
|Keyboard mapping configuration file (for console pseudo-terminals). Set if you have a non-US keyboard. See [[Funtoo Linux Localization]].<br />
|-<br />
|<tt>/etc/conf.d/hwclock</tt><br />
|Optional<br />
|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.<br />
|-<br />
|<tt>/etc/conf.d/modules</tt><br />
|Optional<br />
|Kernel modules to load automatically at system startup. Typically not required. See [[Additional Kernel Resources]] for more info.<br />
|-<br />
|<tt>profiles</tt><br />
|Optional<br />
|Some useful portage settings that may help speed up intial configuration.<br />
|}<br />
<br />
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]])<br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
==== /etc/fstab ====<br />
<br />
<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:<br />
<br />
<console><br />
(chroot) # ##i##nano -w /etc/fstab<br />
</console><br />
<br />
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.<br />
<br />
<pre><br />
# The root filesystem should have a pass number of either 0 or 1.<br />
# All other filesystems should have a pass number of 0 or greater than 1.<br />
#<br />
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.<br />
#<br />
# See the manpage fstab(5) for more information.<br />
#<br />
# <fs> <mountpoint> <type> <opts> <dump/pass><br />
<br />
/dev/sda1 /boot ext2 noatime 1 2<br />
/dev/sda3 none swap sw 0 0<br />
/dev/sda4 / xfs noatime 0 1<br />
#/dev/cdrom /mnt/cdrom auto noauto,ro 0 0<br />
</pre><br />
<br />
==== /etc/localtime ====<br />
<br />
<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. <br />
<br />
<pre><br />
(chroot) # ln -sf /usr/share/zoneinfo/America/Montreal /etc/localtime<br />
</pre><br />
<br />
The above sets the timezone to Eastern Time Canada. Go to <tt>/usr/share/zoneinfo</tt> to see which values to use.<br />
<br />
==== /etc/portage/make.conf ====<br />
<br />
{{fancynote|This file may also be found at /etc/make.conf. /etc/portage/make.conf is the new location.}}<br />
<br />
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:<br />
<br />
<pre><br />
MAKEOPTS="-j3" <br />
</pre><br />
<br />
If you are unsure about how many processors/threads you have then use /proc/cpuinfo to help you.<br />
<console><br />
(chroot) # ##i##grep "processor" /proc/cpuinfo | wc -l<br />
16<br />
</console><br />
<br />
Set MAKEOPTS to this number plus one:<br />
<br />
<pre><br />
MAKEOPTS="-j17"<br />
</pre><br />
<br />
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].<br />
<br />
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:<br />
<br />
<pre><br />
LINGUAS="fr"<br />
</pre><br />
<br />
==== /etc/conf.d/hwclock ====<br />
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.<br />
<console><br />
(chroot) # ##i##nano -w /etc/conf.d/hwclock<br />
</console><br />
<br />
==== Localization ====<br />
<br />
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]].<br />
<br />
==== Profiles ====<br />
<br />
[[Funtoo 1.0 Profile|Funtoo profiles]] are used to define defaults for Portage specific to your needs. There are 4 basic profile types: arch, build, [[Flavors and Mix-ins|flavor, and mix-ins]]:<br />
<br />
;arch: typically <tt>x86-32bit</tt> or <tt>x86-64bit</tt>, this defines the processor type and support of your system. This is defined when your stage was built and should not be changed.<br />
;build: defines whether your system is a <tt>current</tt>, <tt>stable</tt> or <tt>experimental</tt> build. <tt>current</tt> systems will have newer packages unmasked than <tt>stable</tt> systems.<br />
;flavor: defines the general type of system, such as <tt>server</tt> or <tt>desktop</tt>, and will set default USE flags appropriate for your needs.<br />
;mix-ins: define various optional settings that you may be interested in enabling.<br />
<br />
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.<br />
<br />
Remember that profiles can often be inherited. For example, the <tt>desktop</tt> flavor inherits the <tt>workstation</tt> flavor settings, which in turn inherits the <tt>X</tt> and <tt>audio</tt> mix-ins. You can view this by inspecting the <tt>parent</tt> files defined in each profile, which can be found in <tt>/usr/portage/profiles/funtoo/1.0/linux-gnu</tt>:<br />
<br />
<console><br />
(chroot) # ##i##cd /usr/portage/profiles/funtoo/1.0/linux-gnu/<br />
(chroot) # ##i##ls<br />
arch/ eapi make.defaults package.use/ packages.build use.force<br />
build/ flavor/ mix-ins/ package.use.mask/ parent <br />
(chroot) # ##i##cat flavor/desktop/parent <br />
../workstation<br />
../../mix-ins/print<br />
(chroot) # ##i##cat flavor/workstation/parent <br />
../core<br />
../../mix-ins/X<br />
../../mix-ins/audio<br />
../../mix-ins/dvd<br />
../../mix-ins/media<br />
../../mix-ins/console-extras<br />
(chroot) # <br />
</console><br />
<br />
To view installed profiles:<br />
<console><br />
(chroot) # ##i##eselect profile list<br />
</console><br />
<br />
To change the profile flavor:<br />
<console><br />
(chroot) # ##i##eselect profile set-flavor 7<br />
</console><br />
<br />
To add a mix-in:<br />
<br />
<console><br />
(chroot) # ##i##eselect profile add 10<br />
</console><br />
<br />
Remember if you add by string; add a 'gentoo:' to the beginning of the profile name ie:<br />
<console><br />
(chroot) # ##i## eselect profile add gentoo:funtoo/1.0/linux-gnu/mix-ins/console-extras<br />
</console><br />
<br />
=== Configuring and installing the Linux kernel ===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Click [http://wiki.debian.org/DebianKernel here] for a list of all architectures the Debian kernel supports. <br />
<br />
{{fancyimportant|<tt>debian-sources</tt> with <tt>binary</tt> USE flag requires at least 12GB in /var/tmp}}<br />
<br />
<console><br />
(chroot) # ##i##echo "sys-kernel/debian-sources binary" >> /etc/portage/package.use<br />
(chroot) # ##i##emerge debian-sources<br />
</console><br />
<br />
All done!<br />
<br />
{{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>.}}<br />
<br />
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.<br />
<br />
The next step is to configure your boot loader so that your new kernel loads when the system boots.<br />
<br />
=== Installing a Bootloader ===<br />
<br />
==== Installing Grub ====<br />
<br />
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.<br />
<br />
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>.<br />
<br />
<console><br />
(chroot) # ##i##emerge boot-update<br />
</console><br />
<br />
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>. <br />
<br />
<tt>/etc/boot.conf</tt> should now look like this:<br />
<br />
<pre><br />
boot {<br />
generate grub<br />
default "Funtoo Linux genkernel"<br />
timeout 3 <br />
}<br />
<br />
"Funtoo Linux" {<br />
kernel bzImage[-v]<br />
# params += nomodeset<br />
}<br />
<br />
"Funtoo Linux genkernel" {<br />
kernel kernel[-v]<br />
initrd initramfs[-v]<br />
params += real_root=auto <br />
# params += nomodeset<br />
} <br />
</pre><br />
<br />
Please read <tt>man boot.conf</tt> for further details.<br />
<br />
===== Running grub-install and boot-update =====<br />
<br />
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:<br />
<br />
<console><br />
(chroot) # ##i##grub-install --no-floppy /dev/sda<br />
(chroot) # ##i##boot-update<br />
</console><br />
<br />
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.<br />
<br />
OK - your system should be ready to boot! Well, there are a few more loose ends...<br />
<br />
==== Installing Syslinux/Extlinux ====<br />
<br />
An alternate Bootloader is Extlinux, for installing it see the [[Extlinux|extlinux Guide]].<br />
<br />
=== Configuring your network ===<br />
<br />
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.<br />
<br />
==== Wi-Fi ====<br />
<br />
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:<br />
<br />
<console><br />
# ##i##emerge linux-firmware<br />
# ##i##emerge networkmanager<br />
# ##i##rc-update add NetworkManager default<br />
</console><br />
<br />
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.<br />
<br />
After you reboot into Funtoo Linux, you will be able to add a Wi-Fi connection this way:<br />
<br />
<console><br />
# ##i##addwifi -S wpa -K 'wifipassword' mywifinetwork<br />
</console><br />
<br />
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.<br />
<br />
==== Desktop (Wired Ethernet) ====<br />
<br />
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:<br />
<br />
<console><br />
# ##i##rc-update add dhcpcd default<br />
</console><br />
<br />
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.<br />
<br />
==== Server (Static IP) ====<br />
<br />
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.<br />
<br />
=== Finishing Steps ===<br />
<br />
==== Set your root password ====<br />
It's imperative that you set your root password before rebooting so that you can log in.<br />
<console><br />
(chroot) # ##i##passwd<br />
</console><br />
<br />
===Restart your system ===<br />
<br />
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.<br />
<br />
Leave the chroot, change directory to /, unmount your Funtoo partitions, and reboot.<br />
<console><br />
(chroot) # ##i##exit<br />
# ##i##cd /<br />
# ##i##umount /mnt/funtoo/boot /mnt/funtoo/dev /mnt/funtoo/proc /mnt/funtoo<br />
# ##i##reboot<br />
</console><br />
<br />
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!<br />
<br />
===Next Steps===<br />
<br />
To learn how to customize and start using Funtoo Linux, see [[Funtoo Linux First Steps]].<br />
<br />
If your system did not boot correctly, see [[Installation Troubleshooting]] for steps you can take to resolve the problem.<br />
<br />
[[Category:HOWTO]]<br />
[[Category:Install]]</div>Oleghttp://www.funtoo.org/wiki/Funtoo_Linux_InstallationFuntoo Linux Installation2013-03-20T07:03:23Z<p>Oleg: Reverted edits by Fearedbliss (talk) to last revision by 178.36.91.35</p>
<hr />
<div>== Introduction ==<br />
<br />
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.<br />
<br />
=== Additional Resources === <br />
<br />
This document was written to help you install Funtoo Linux as efficiently as possible, with a minimum number of distracting options regarding system configuration. <br />
<br />
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.<br />
<br />
If you are installing Funtoo Linux on [[Funtoo Linux Installation on ARM|ARM]] architecture, please see [[Funtoo Linux Installation on ARM]] for notable differences regarding ARM support. An experimental Funtoo Linux build also exists for [[Funtoo Linux Installation on SPARC|SPARC]] platforms. See [[Funtoo Linux Installation on SPARC]]<br />
<br />
== Installation Overview ==<br />
<br />
This is a basic overview of the Funtoo installation process:<br />
<br />
# [[#Live CD|Download and boot the live CD of your choice]].<br />
# [[#Prepare Hard Disk|Prepare your disk]].<br />
# [[#Creating filesystems|Create]] and [[#Mounting filesystems|mount]] filesystems.<br />
# [[#Installing the Stage 3 tarball|Install the Funtoo stage tarball]] of your choice.<br />
# [[#Chroot into Funtoo|Chroot into your new system]].<br />
# [[#Downloading the Portage tree|Download the Portage tree]].<br />
# [[#Configuring your system|Configure your system]] and [[#Configuring your network|network]].<br />
# [[#Configuring and installing the Linux kernel|Install a kernel]].<br />
# [[#Installing a Bootloader|Install a bootloader]].<br />
# [[#Finishing Steps|Complete final steps]].<br />
# [[#Restart your system|Reboot and enjoy]].<br />
<br />
=== Live CD ===<br />
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.<br />
<br />
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.<br />
<br />
To begin a Funtoo Linux installation, download SystemRescueCD from:<br />
<br />
* Main US mirror: [http://ftp.osuosl.org/pub/funtoo/distfiles/sysrescuecd/systemrescuecd-x86-3.3.0.iso The Oregon State University Open Source Lab]<br />
* Main EU mirror: [http://ftp.heanet.ie/mirrors/funtoo/distfiles/sysrescuecd/systemrescuecd-x86-3.3.0.iso HEAnet] or use your preferred live media. Insert it into your disc drive, and boot from it. If using an older version of 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 used to boot in 32-bit mode though the latest version attempts to automatically detect 64-bit processors.<br />
<br />
=== Prepare Hard Disk ===<br />
==== Partitions ====<br />
<br />
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:<br />
<br />
===== GPT Partitions =====<br />
<br />
* Newer, preferred format for Linux systems<br />
* Supports 2 TB+ hard drives for booting<br />
* Supports hundreds of partitions per disk of any size<br />
* Requires legacy BIOS boot partition (~32 MB) to be created if system does not use EFI<br />
* Requires bootloader with support for GPT such as GRUB 2, EXTLINUX, or a patched version of GRUB Legacy<br />
<br />
===== MBR Partitions =====<br />
<br />
* Legacy, DOS partitioning scheme<br />
* Only 4 primary partitions per disk; after that, you must use "logical" partitions<br />
* Does not support 2 TB+ disks for booting<br />
* Compatible with certain problematic systems (such as the HP ProBook 4520)<br />
* Dual-boot with Windows for BIOS systems (Windows handle GPT only on true EFI systems, whatever version it is)<br />
* Multiple boot loader options, e.g. GRUB 2, GRUB Legacy, lilo<br />
<br />
{{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.}}<br />
<br />
==== Partitioning Using gdisk ====<br />
<br />
===== Notes Before We Begin =====<br />
<br />
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.<br />
<br />
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 <br />
'''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.<br />
<br />
Advanced users may be interested in the following topics:<br />
<br />
* [[GUID Booting Guide]]<br />
* [[Rootfs over encrypted lvm]]<br />
* [[Rootfs over encrypted lvm over raid-1 on GPT]]<br />
* '''NEW!''' '''[[ZFS Install Guide]]'''<br />
* '''NEW!''' '''[[ZFS rootfs over encrypted container]]'''<br />
<br />
===== Using gdisk =====<br />
<br />
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:<br />
<br />
<console># ##i##gdisk /dev/sda</console><br />
You should find <tt>gdisk</tt> very similar to <tt>fdisk</tt>. Here is the partition table we want to end up with:<br />
<br />
<console>Command (? for help): ##i##p<br />
Disk /dev/sda: 234441648 sectors, 111.8 GiB<br />
Logical sector size: 512 bytes<br />
Disk identifier (GUID): A4E5208A-CED3-4263-BB25-7147DC426931<br />
Partition table holds up to 128 entries<br />
First usable sector is 34, last usable sector is 234441614<br />
Partitions will be aligned on 2048-sector boundaries<br />
Total free space is 2014 sectors (1007.0 KiB)<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 206847 500.0 MiB 8300 Linux filesystem<br />
2 206848 272383 32.0 MiB EF02 BIOS boot partition<br />
3 272384 8660991 4.0 GiB 8200 Linux swap<br />
4 8660992 234441614 107.7 GiB 8300 Linux filesystem<br />
<br />
Command (? for help): </console><br />
<br />
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.<br />
<br />
===== For new <tt>gdisk</tt> users =====<br />
<br />
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.<br />
<br />
Within <tt>gdisk</tt>, follow these steps:<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##1 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+500M ↵<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
'''Create Partition 2''' (GRUB):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##2 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+32M ↵<br />
Hex Code: ##i##EF02 ↵<br />
</console><br />
<br />
'''Create Partition 3''' (swap):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##3 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+4G ↵<br />
Hex Code: ##i##8200 ↵<br />
</console><br />
<br />
'''Create Partition 4''' (root):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##4 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵##!i## (for rest of disk)<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
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:<br />
<br />
'''Write Partition Table To Disk''':<br />
<br />
<console><br />
Command: ##i##w ↵<br />
Do you want to proceed? (Y/N): ##i##Y ↵<br />
</console><br />
<br />
The partition table will now be written to disk and <tt>gdisk</tt> will close.<br />
<br />
Now, your GPT/GUID partitions have been created, and will show up as the following ''block devices'' under Linux:<br />
<br />
* <tt>/dev/sda1</tt>, which will be used to hold the <tt>/boot</tt> filesystem, <br />
* <tt>/dev/sda2</tt>, which will be used directly by the new GRUB,<br />
* <tt>/dev/sda3</tt>, which will be used for swap space, and <br />
* <tt>/dev/sda4</tt>, which will hold your root filesystem.<br />
<br />
===== For Previous fdisk users =====<br />
<br />
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.<br />
<br />
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>.<br />
<br />
===== Partitioning Recommendations =====<br />
<br />
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>:<br />
<br />
{| {{table}} <br />
!Partition<br />
!Size<br />
!MBR Block Device (<tt>fdisk</tt>)<br />
!GPT Block Device (<tt>gdisk</tt>)<br />
!Filesystem<br />
!MBR Code<br />
!GPT Code<br />
|-<br />
|<tt>/boot</tt><br />
|500 MB<br />
|<tt>/dev/sda1</tt><br />
|<tt>/dev/sda1</tt><br />
|ext2<br />
|83<br />
|8300<br />
|-<br />
|GRUB boot loader partition<br />
|32 MB<br />
| ''not required for MBR''<br />
|<tt>/dev/sda2</tt><br />
|For GPT/GUID only, skip for MBR - no filesystem.<br />
|''N/A''<br />
|EF02<br />
|-<br />
|swap<br />
|2x RAM for low-memory systems and production servers; otherwise 2GB.<br />
|<tt>/dev/sda2</tt><br />
|<tt>/dev/sda3</tt><br />
|swap (default)<br />
|82<br />
|8200<br />
|-<br />
|<tt>/</tt> (root)<br />
|Rest of the disk, minimum of 10GB.<br />
|<tt>/dev/sda3</tt><br />
|<tt>/dev/sda4</tt><br />
|XFS recommended, alternatively ext4<br />
|83<br />
|8300<br />
|-<br />
|<tt>/home</tt> (optional) <br />
|User storage and media. Typically most of the disk.<br />
|<tt>/dev/sda4</tt> (if created)<br />
|<tt>/dev/sda5</tt> (if created)<br />
|XFS recommended, alternatively ext4<br />
|83<br />
|8300<br />
|-<br />
| LVM (optional)<br />
| If you want to create an LVM volume.<br />
| <tt>/dev/sda4</tt> (PV, if created)<br />
| <tt>/dev/sda5</tt> (PV, if created)<br />
| LVM PV<br />
| 8E<br />
| 8E00<br />
|}<br />
<br />
==== Creating filesystems ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<br />
<console><br />
# ##i##mke2fs -t ext2 /dev/sda1 <br />
# ##i##mkfs.xfs /dev/sda4<br />
# ##i##mkswap /dev/sda3<br />
# ##i##swapon /dev/sda3<br />
</console><br />
<br />
==== Mounting filesystems ====<br />
<br />
Mount the newly-created filesystems as follows, creating <tt>/mnt/funtoo</tt> as the installation mount point:<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo<br />
# ##i##mount /dev/sda4 /mnt/funtoo<br />
# ##i##mkdir /mnt/funtoo/boot<br />
# ##i##mount /dev/sda1 /mnt/funtoo/boot<br />
</console><br />
<br />
Optionally, if you have a separate filesystem for <tt>/home</tt> or anything else:<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo/home<br />
# ##i##mount /dev/sda5 /mnt/funtoo/home<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##chmod 1777 /mnt/funtoo/tmp<br />
</console><br />
<br />
=== Installing the Stage 3 tarball ===<br />
==== Stage 3 tarball ====<br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
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:<br />
<br />
<console><br />
# ##i##date<br />
Fri Jul 15 19:47:18 UTC 2011<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##date 071620002011<br />
Fri Jul 16 20:00:00 UTC 2011<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
# ##i##wget -O - http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-64bit/generic_64/stage3-latest.tar.xz | tar xfvJp -<br />
</console><br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
=== Chroot into Funtoo ===<br />
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:<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
# ##i##mount --bind /proc proc<br />
# ##i##mount --bind /dev dev<br />
</console><br />
<br />
You'll also want to copy over <tt>resolv.conf</tt> in order to have proper DNS name resolution from inside the chroot:<br />
<console><br />
# ##i##cp /etc/resolv.conf etc<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l<br />
</console><br />
<br />
{{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.}}<br />
{{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.}}<br />
<br />
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:<br />
<console><br />
# ##i##export PS1="(chroot) $PS1"<br />
</console><br />
<br />
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.<br />
<br />
=== Downloading the Portage tree ===<br />
<br />
{{fancynote|For an alternative way to do this, see [[Installing Portage From Snapshot]].}}<br />
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]:<br />
<br />
<console><br />
(chroot) # ##i##emerge --sync<br />
</console><br />
<br />
{{fancyimportant|If you receive the error with initial <tt>emerge --sync</tt> due to git protocol restrictions, change <tt>SYNC</tt> variable in <tt>/etc/portage/make.conf</tt>}}<br />
<pre><br />
SYNC="https://github.com/funtoo/ports-2012.git"<br />
</pre><br />
<br />
<br />
=== Configuring your system ===<br />
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:<br />
<br />
{| {{table}}<br />
!File<br />
!Do I need to change it?<br />
!Description<br />
|-<br />
|<tt>/etc/fstab</tt><br />
|'''YES - required'''<br />
|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.<br />
|-<br />
|<tt>/etc/localtime</tt><br />
|''Maybe - recommended''<br />
|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) <br />
|-<br />
|<tt>/etc/make.conf<br/>/etc/portage/make.conf&nbsp;(new&nbsp;location)</tt><br />
|''Maybe - recommended''<br />
|Parameters used by gcc (compiler), portage, and make. It's a good idea to set MAKEOPTS. This is covered later in this document.<br />
|-<br />
|<tt>/etc/conf.d/hostname</tt><br />
|''Maybe - recommended''<br />
|Used to set system hostname. Set to the fully-qualified (with dots) name. Defaults to <tt>localhost</tt> if not set.<br />
|-<br />
|<tt>/etc/hosts</tt><br />
|''No''<br />
| You no longer need to manually set the hostname in this file. This file is automatically generated by <tt>/etc/init.d/hostname</tt>.<br />
|-<br />
|<tt>/etc/conf.d/keymaps</tt><br />
|Optional<br />
|Keyboard mapping configuration file (for console pseudo-terminals). Set if you have a non-US keyboard. See [[Funtoo Linux Localization]].<br />
|-<br />
|<tt>/etc/conf.d/hwclock</tt><br />
|Optional<br />
|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.<br />
|-<br />
|<tt>/etc/conf.d/modules</tt><br />
|Optional<br />
|Kernel modules to load automatically at system startup. Typically not required. See [[Additional Kernel Resources]] for more info.<br />
|-<br />
|<tt>profiles</tt><br />
|Optional<br />
|Some useful portage settings that may help speed up intial configuration.<br />
|}<br />
<br />
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]])<br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
==== /etc/fstab ====<br />
<br />
<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:<br />
<br />
<console><br />
(chroot) # ##i##nano -w /etc/fstab<br />
</console><br />
<br />
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.<br />
<br />
<pre><br />
# The root filesystem should have a pass number of either 0 or 1.<br />
# All other filesystems should have a pass number of 0 or greater than 1.<br />
#<br />
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.<br />
#<br />
# See the manpage fstab(5) for more information.<br />
#<br />
# <fs> <mountpoint> <type> <opts> <dump/pass><br />
<br />
/dev/sda1 /boot ext2 noatime 1 2<br />
/dev/sda3 none swap sw 0 0<br />
/dev/sda4 / xfs noatime 0 1<br />
#/dev/cdrom /mnt/cdrom auto noauto,ro 0 0<br />
</pre><br />
<br />
==== /etc/localtime ====<br />
<br />
<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. <br />
<br />
<pre><br />
(chroot) # ln -sf /usr/share/zoneinfo/America/Montreal /etc/localtime<br />
</pre><br />
<br />
The above sets the timezone to Eastern Time Canada. Go to <tt>/usr/share/zoneinfo</tt> to see which values to use.<br />
<br />
==== /etc/portage/make.conf ====<br />
<br />
{{fancynote|This file may also be found at /etc/make.conf. /etc/portage/make.conf is the new location.}}<br />
<br />
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:<br />
<br />
<pre><br />
MAKEOPTS="-j3" <br />
</pre><br />
<br />
If you are unsure about how many processors/threads you have then use /proc/cpuinfo to help you.<br />
<console><br />
(chroot) # ##i##grep "processor" /proc/cpuinfo | wc -l<br />
16<br />
</console><br />
<br />
Set MAKEOPTS to this number plus one:<br />
<br />
<pre><br />
MAKEOPTS="-j17"<br />
</pre><br />
<br />
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].<br />
<br />
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:<br />
<br />
<pre><br />
LINGUAS="fr"<br />
</pre><br />
<br />
==== /etc/conf.d/hwclock ====<br />
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.<br />
<console><br />
(chroot) # ##i##nano -w /etc/conf.d/hwclock<br />
</console><br />
<br />
==== Localization ====<br />
<br />
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]].<br />
<br />
==== Profiles ====<br />
<br />
[[Funtoo 1.0 Profile|Funtoo profiles]] are used to define defaults for Portage specific to your needs. There are 4 basic profile types: arch, build, [[Flavors and Mix-ins|flavor, and mix-ins]]:<br />
<br />
;arch: typically <tt>x86-32bit</tt> or <tt>x86-64bit</tt>, this defines the processor type and support of your system. This is defined when your stage was built and should not be changed.<br />
;build: defines whether your system is a <tt>current</tt>, <tt>stable</tt> or <tt>experimental</tt> build. <tt>current</tt> systems will have newer packages unmasked than <tt>stable</tt> systems.<br />
;flavor: defines the general type of system, such as <tt>server</tt> or <tt>desktop</tt>, and will set default USE flags appropriate for your needs.<br />
;mix-ins: define various optional settings that you may be interested in enabling.<br />
<br />
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.<br />
<br />
Remember that profiles can often be inherited. For example, the <tt>desktop</tt> flavor inherits the <tt>workstation</tt> flavor settings, which in turn inherits the <tt>X</tt> and <tt>audio</tt> mix-ins. You can view this by inspecting the <tt>parent</tt> files defined in each profile, which can be found in <tt>/usr/portage/profiles/funtoo/1.0/linux-gnu</tt>:<br />
<br />
<console><br />
(chroot) # ##i##cd /usr/portage/profiles/funtoo/1.0/linux-gnu/<br />
(chroot) # ##i##ls<br />
arch/ eapi make.defaults package.use/ packages.build use.force<br />
build/ flavor/ mix-ins/ package.use.mask/ parent <br />
(chroot) # ##i##cat flavor/desktop/parent <br />
../workstation<br />
../../mix-ins/print<br />
(chroot) # ##i##cat flavor/workstation/parent <br />
../core<br />
../../mix-ins/X<br />
../../mix-ins/audio<br />
../../mix-ins/dvd<br />
../../mix-ins/media<br />
../../mix-ins/console-extras<br />
(chroot) # <br />
</console><br />
<br />
To view installed profiles:<br />
<console><br />
(chroot) # ##i##eselect profile list<br />
</console><br />
<br />
To change the profile flavor:<br />
<console><br />
(chroot) # ##i##eselect profile set-flavor 7<br />
</console><br />
<br />
To add a mix-in:<br />
<br />
<console><br />
(chroot) # ##i##eselect profile add 10<br />
</console><br />
<br />
Remember if you add by string; add a 'gentoo:' to the beginning of the profile name ie:<br />
<console><br />
(chroot) # ##i## eselect profile add gentoo:funtoo/1.0/linux-gnu/mix-ins/console-extras<br />
</console><br />
<br />
=== Configuring and installing the Linux kernel ===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Click [http://wiki.debian.org/DebianKernel here] for a list of all architectures the Debian kernel supports. <br />
<br />
{{fancyimportant|<tt>debian-sources</tt> with <tt>binary</tt> USE flag requires at least 12GB in /var/tmp}}<br />
<br />
<console><br />
(chroot) # ##i##echo "sys-kernel/debian-sources binary" >> /etc/portage/package.use<br />
(chroot) # ##i##emerge debian-sources<br />
</console><br />
<br />
All done!<br />
<br />
{{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>.}}<br />
<br />
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.<br />
<br />
The next step is to configure your boot loader so that your new kernel loads when the system boots.<br />
<br />
=== Installing a Bootloader ===<br />
<br />
==== Installing Grub ====<br />
<br />
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.<br />
<br />
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>.<br />
<br />
<console><br />
(chroot) # ##i##emerge boot-update<br />
</console><br />
<br />
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>. <br />
<br />
<tt>/etc/boot.conf</tt> should now look like this:<br />
<br />
<pre><br />
boot {<br />
generate grub<br />
default "Funtoo Linux genkernel"<br />
timeout 3 <br />
}<br />
<br />
"Funtoo Linux" {<br />
kernel bzImage[-v]<br />
# params += nomodeset<br />
}<br />
<br />
"Funtoo Linux genkernel" {<br />
kernel kernel[-v]<br />
initrd initramfs[-v]<br />
params += real_root=auto <br />
# params += nomodeset<br />
} <br />
</pre><br />
<br />
Please read <tt>man boot.conf</tt> for further details.<br />
<br />
===== Running grub-install and boot-update =====<br />
<br />
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:<br />
<br />
<console><br />
(chroot) # ##i##grub-install --no-floppy /dev/sda<br />
(chroot) # ##i##boot-update<br />
</console><br />
<br />
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.<br />
<br />
OK - your system should be ready to boot! Well, there are a few more loose ends...<br />
<br />
==== Installing Syslinux/Extlinux ====<br />
<br />
An alternate Bootloader is Extlinux, for installing it see the [[Extlinux|extlinux Guide]].<br />
<br />
=== Configuring your network ===<br />
<br />
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.<br />
<br />
==== Wi-Fi ====<br />
<br />
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:<br />
<br />
<console><br />
# ##i##emerge linux-firmware<br />
# ##i##emerge networkmanager<br />
# ##i##rc-update add NetworkManager default<br />
</console><br />
<br />
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.<br />
<br />
After you reboot into Funtoo Linux, you will be able to add a Wi-Fi connection this way:<br />
<br />
<console><br />
# ##i##addwifi -S wpa -K 'wifipassword' mywifinetwork<br />
</console><br />
<br />
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.<br />
<br />
==== Desktop (Wired Ethernet) ====<br />
<br />
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:<br />
<br />
<console><br />
# ##i##rc-update add dhcpcd default<br />
</console><br />
<br />
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.<br />
<br />
==== Server (Static IP) ====<br />
<br />
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.<br />
<br />
=== Finishing Steps ===<br />
<br />
==== Set your root password ====<br />
It's imperative that you set your root password before rebooting so that you can log in.<br />
<console><br />
(chroot) # ##i##passwd<br />
</console><br />
<br />
===Restart your system ===<br />
<br />
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.<br />
<br />
Leave the chroot, change directory to /, unmount your Funtoo partitions, and reboot.<br />
<console><br />
(chroot) # ##i##exit<br />
# ##i##cd /<br />
# ##i##umount /mnt/funtoo/boot /mnt/funtoo/dev /mnt/funtoo/proc /mnt/funtoo<br />
# ##i##reboot<br />
</console><br />
<br />
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!<br />
<br />
===Next Steps===<br />
<br />
To learn how to customize and start using Funtoo Linux, see [[Funtoo Linux First Steps]].<br />
<br />
If your system did not boot correctly, see [[Installation Troubleshooting]] for steps you can take to resolve the problem.<br />
<br />
[[Category:HOWTO]]<br />
[[Category:Install]]</div>Oleghttp://www.funtoo.org/wiki/Funtoo_Linux_InstallationFuntoo Linux Installation2013-02-23T16:06:24Z<p>Oleg: </p>
<hr />
<div>== Introduction ==<br />
<br />
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.<br />
<br />
=== Additional Resources === <br />
<br />
This document was written to help you install Funtoo Linux as efficiently as possible, with a minimum number of distracting options regarding system configuration. <br />
<br />
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.<br />
<br />
If you are installing Funtoo Linux on [[Funtoo Linux Installation on ARM|ARM]] architecture, please see [[Funtoo Linux Installation on ARM]] for notable differences regarding ARM support. An experimental Funtoo Linux build also exists for [[Funtoo Linux Installation on SPARC|SPARC]] platforms. See [[Funtoo Linux Installation on SPARC]]<br />
<br />
== Installation Overview ==<br />
<br />
This is a basic overview of the Funtoo installation process:<br />
<br />
# [[#Live CD|Download and boot the live CD of your choice]].<br />
# [[#Prepare Hard Disk|Prepare your disk]].<br />
# [[#Creating filesystems|Create]] and [[#Mounting filesystems|mount]] filesystems.<br />
# [[#Installing the Stage 3 tarball|Install the Funtoo stage tarball]] of your choice.<br />
# [[#Chroot into Funtoo|Chroot into your new system]].<br />
# [[#Downloading the Portage tree|Download the Portage tree]].<br />
# [[#Configuring your system|Configure your system]] and [[#Configuring your network|network]].<br />
# [[#Configuring and installing the Linux kernel|Install a kernel]].<br />
# [[#Installing a Bootloader|Install a bootloader]].<br />
# [[#Finishing Steps|Complete final steps]].<br />
# [[#Restart your system|Reboot and enjoy]].<br />
<br />
=== Live CD ===<br />
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.<br />
<br />
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.<br />
<br />
To begin a Funtoo Linux installation, download SystemRescueCD from:<br />
<br />
* Main US mirror: [http://ftp.osuosl.org/pub/funtoo/distfiles/sysrescuecd/systemrescuecd-x86-3.3.0.iso The Oregon State University Open Source Lab]<br />
* Main EU mirror: [http://ftp.heanet.ie/mirrors/funtoo/distfiles/sysrescuecd/systemrescuecd-x86-3.3.0.iso HEAnet] or use 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.<br />
<br />
=== Prepare Hard Disk ===<br />
==== Partitions ====<br />
<br />
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:<br />
<br />
===== GPT Partitions =====<br />
<br />
* Newer, preferred format for Linux systems<br />
* Supports 2 TB+ hard drives for booting<br />
* Supports hundreds of partitions per disk of any size<br />
* Requires legacy BIOS boot partition (~32 MB) to be created if system does not use EFI<br />
* Requires bootloader with support for GPT such as GRUB 2, EXTLINUX, or a patched version of GRUB Legacy<br />
<br />
===== MBR Partitions =====<br />
<br />
* Legacy, DOS partitioning scheme<br />
* Only 4 primary partitions per disk; after that, you must use "logical" partitions<br />
* Does not support 2 TB+ disks for booting<br />
* Compatible with certain problematic systems (such as the HP ProBook 4520)<br />
* Dual-boot with Windows for BIOS systems (Windows handle GPT only on true EFI systems, whatever version it is)<br />
* Multiple boot loader options, e.g. GRUB 2, GRUB Legacy, lilo<br />
<br />
{{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.}}<br />
<br />
==== Partitioning Using gdisk ====<br />
<br />
===== Notes Before We Begin =====<br />
<br />
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.<br />
<br />
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 <br />
'''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.<br />
<br />
Advanced users may be interested in the following topics:<br />
<br />
* [[GUID Booting Guide]]<br />
* [[Rootfs over encrypted lvm]]<br />
* [[Rootfs over encrypted lvm over raid-1 on GPT]]<br />
* '''NEW!''' '''[[ZFS Install Guide]]'''<br />
* '''NEW!''' '''[[ZFS rootfs over encrypted container]]'''<br />
<br />
===== Using gdisk =====<br />
<br />
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:<br />
<br />
<console># ##i##gdisk /dev/sda</console><br />
You should find <tt>gdisk</tt> very similar to <tt>fdisk</tt>. Here is the partition table we want to end up with:<br />
<br />
<console>Command (? for help): ##i##p<br />
Disk /dev/sda: 234441648 sectors, 111.8 GiB<br />
Logical sector size: 512 bytes<br />
Disk identifier (GUID): A4E5208A-CED3-4263-BB25-7147DC426931<br />
Partition table holds up to 128 entries<br />
First usable sector is 34, last usable sector is 234441614<br />
Partitions will be aligned on 2048-sector boundaries<br />
Total free space is 2014 sectors (1007.0 KiB)<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 206847 500.0 MiB 8300 Linux filesystem<br />
2 206848 272383 32.0 MiB EF02 BIOS boot partition<br />
3 272384 8660991 4.0 GiB 8200 Linux swap<br />
4 8660992 234441614 107.7 GiB 8300 Linux filesystem<br />
<br />
Command (? for help): </console><br />
<br />
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.<br />
<br />
===== For new <tt>gdisk</tt> users =====<br />
<br />
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.<br />
<br />
Within <tt>gdisk</tt>, follow these steps:<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##1 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+500M ↵<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
'''Create Partition 2''' (GRUB):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##2 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+32M ↵<br />
Hex Code: ##i##EF02 ↵<br />
</console><br />
<br />
'''Create Partition 3''' (swap):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##3 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+4G ↵<br />
Hex Code: ##i##8200 ↵<br />
</console><br />
<br />
'''Create Partition 4''' (root):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##4 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵##!i## (for rest of disk)<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
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:<br />
<br />
'''Write Partition Table To Disk''':<br />
<br />
<console><br />
Command: ##i##w ↵<br />
Do you want to proceed? (Y/N): ##i##Y ↵<br />
</console><br />
<br />
The partition table will now be written to disk and <tt>gdisk</tt> will close.<br />
<br />
Now, your GPT/GUID partitions have been created, and will show up as the following ''block devices'' under Linux:<br />
<br />
* <tt>/dev/sda1</tt>, which will be used to hold the <tt>/boot</tt> filesystem, <br />
* <tt>/dev/sda2</tt>, which will be used directly by the new GRUB,<br />
* <tt>/dev/sda3</tt>, which will be used for swap space, and <br />
* <tt>/dev/sda4</tt>, which will hold your root filesystem.<br />
<br />
===== For Previous fdisk users =====<br />
<br />
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.<br />
<br />
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>.<br />
<br />
===== Partitioning Recommendations =====<br />
<br />
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>:<br />
<br />
{| {{table}} <br />
!Partition<br />
!Size<br />
!MBR Block Device (<tt>fdisk</tt>)<br />
!GPT Block Device (<tt>gdisk</tt>)<br />
!Filesystem<br />
!MBR Code<br />
!GPT Code<br />
|-<br />
|<tt>/boot</tt><br />
|500 MB<br />
|<tt>/dev/sda1</tt><br />
|<tt>/dev/sda1</tt><br />
|ext2<br />
|83<br />
|8300<br />
|-<br />
|GRUB boot loader partition<br />
|32 MB<br />
| ''not required for MBR''<br />
|<tt>/dev/sda2</tt><br />
|For GPT/GUID only, skip for MBR - no filesystem.<br />
|''N/A''<br />
|EF02<br />
|-<br />
|swap<br />
|2x RAM for low-memory systems and production servers; otherwise 2GB.<br />
|<tt>/dev/sda2</tt><br />
|<tt>/dev/sda3</tt><br />
|swap (default)<br />
|82<br />
|8200<br />
|-<br />
|<tt>/</tt> (root)<br />
|Rest of the disk, minimum of 10GB.<br />
|<tt>/dev/sda3</tt><br />
|<tt>/dev/sda4</tt><br />
|XFS recommended, alternatively ext4<br />
|83<br />
|8300<br />
|-<br />
|<tt>/home</tt> (optional) <br />
|User storage and media. Typically most of the disk.<br />
|<tt>/dev/sda4</tt> (if created)<br />
|<tt>/dev/sda5</tt> (if created)<br />
|XFS recommended, alternatively ext4<br />
|83<br />
|8300<br />
|-<br />
| LVM (optional)<br />
| If you want to create an LVM volume.<br />
| <tt>/dev/sda4</tt> (PV, if created)<br />
| <tt>/dev/sda5</tt> (PV, if created)<br />
| LVM PV<br />
| 8E<br />
| 8E00<br />
|}<br />
<br />
==== Creating filesystems ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<br />
<console><br />
# ##i##mke2fs -t ext2 /dev/sda1 <br />
# ##i##mkfs.xfs /dev/sda4<br />
# ##i##mkswap /dev/sda3<br />
# ##i##swapon /dev/sda3<br />
</console><br />
<br />
==== Mounting filesystems ====<br />
<br />
Mount the newly-created filesystems as follows, creating <tt>/mnt/funtoo</tt> as the installation mount point:<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo<br />
# ##i##mount /dev/sda4 /mnt/funtoo<br />
# ##i##mkdir /mnt/funtoo/boot<br />
# ##i##mount /dev/sda1 /mnt/funtoo/boot<br />
</console><br />
<br />
Optionally, if you have a separate filesystem for <tt>/home</tt> or anything else:<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo/home<br />
# ##i##mount /dev/sda5 /mnt/funtoo/home<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##chmod 1777 /mnt/funtoo/tmp<br />
</console><br />
<br />
=== Installing the Stage 3 tarball ===<br />
==== Stage 3 tarball ====<br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
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:<br />
<br />
<console><br />
# ##i##date<br />
Fri Jul 15 19:47:18 UTC 2011<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##date 071620002011<br />
Fri Jul 16 20:00:00 UTC 2011<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
# ##i##wget -O - http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-64bit/generic_64/stage3-latest.tar.xz | tar xfvJp -<br />
</console><br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
=== Chroot into Funtoo ===<br />
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:<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
# ##i##mount --bind /proc proc<br />
# ##i##mount --bind /dev dev<br />
</console><br />
<br />
You'll also want to copy over <tt>resolv.conf</tt> in order to have proper DNS name resolution from inside the chroot:<br />
<console><br />
# ##i##cp /etc/resolv.conf etc<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l<br />
</console><br />
<br />
{{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.}}<br />
{{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.}}<br />
<br />
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:<br />
<console><br />
# ##i##export PS1="(chroot) $PS1"<br />
</console><br />
<br />
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.<br />
<br />
=== Downloading the Portage tree ===<br />
<br />
{{fancynote|For an alternative way to do this, see [[Installing Portage From Snapshot]].}}<br />
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]:<br />
<br />
<console><br />
(chroot) # ##i##emerge --sync<br />
</console><br />
<br />
{{fancyimportant|If you receive the error with initial <tt>emerge --sync</tt> due to git protocol restrictions, change <tt>SYNC</tt> variable in <tt>/etc/portage/make.conf</tt>}}<br />
<pre><br />
SYNC="https://github.com/funtoo/ports-2012.git"<br />
</pre><br />
<br />
<br />
=== Configuring your system ===<br />
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:<br />
<br />
{| {{table}}<br />
!File<br />
!Do I need to change it?<br />
!Description<br />
|-<br />
|<tt>/etc/fstab</tt><br />
|'''YES - required'''<br />
|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.<br />
|-<br />
|<tt>/etc/localtime</tt><br />
|''Maybe - recommended''<br />
|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) <br />
|-<br />
|<tt>/etc/make.conf<br/>/etc/portage/make.conf&nbsp;(new&nbsp;location)</tt><br />
|''Maybe - recommended''<br />
|Parameters used by gcc (compiler), portage, and make. It's a good idea to set MAKEOPTS. This is covered later in this document.<br />
|-<br />
|<tt>/etc/conf.d/hostname</tt><br />
|''Maybe - recommended''<br />
|Used to set system hostname. Set to the fully-qualified (with dots) name. Defaults to <tt>localhost</tt> if not set.<br />
|-<br />
|<tt>/etc/hosts</tt><br />
|''No''<br />
| You no longer need to manually set the hostname in this file. This file is automatically generated by <tt>/etc/init.d/hostname</tt>.<br />
|-<br />
|<tt>/etc/conf.d/keymaps</tt><br />
|Optional<br />
|Keyboard mapping configuration file (for console pseudo-terminals). Set if you have a non-US keyboard. See [[Funtoo Linux Localization]].<br />
|-<br />
|<tt>/etc/conf.d/hwclock</tt><br />
|Optional<br />
|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.<br />
|-<br />
|<tt>/etc/conf.d/modules</tt><br />
|Optional<br />
|Kernel modules to load automatically at system startup. Typically not required. See [[Additional Kernel Resources]] for more info.<br />
|-<br />
|<tt>profiles</tt><br />
|Optional<br />
|Some useful portage settings that may help speed up intial configuration.<br />
|}<br />
<br />
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]])<br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
==== /etc/fstab ====<br />
<br />
<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:<br />
<br />
<console><br />
(chroot) # ##i##nano -w /etc/fstab<br />
</console><br />
<br />
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.<br />
<br />
<pre><br />
# The root filesystem should have a pass number of either 0 or 1.<br />
# All other filesystems should have a pass number of 0 or greater than 1.<br />
#<br />
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.<br />
#<br />
# See the manpage fstab(5) for more information.<br />
#<br />
# <fs> <mountpoint> <type> <opts> <dump/pass><br />
<br />
/dev/sda1 /boot ext2 noatime 1 2<br />
/dev/sda3 none swap sw 0 0<br />
/dev/sda4 / xfs noatime 0 1<br />
#/dev/cdrom /mnt/cdrom auto noauto,ro 0 0<br />
</pre><br />
<br />
==== /etc/localtime ====<br />
<br />
<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. <br />
<br />
<pre><br />
(chroot) # ln -sf /usr/share/zoneinfo/America/Montreal /etc/localtime<br />
</pre><br />
<br />
The above sets the timezone to Eastern Time Canada. Go to <tt>/usr/share/zoneinfo</tt> to see which values to use.<br />
<br />
==== /etc/portage/make.conf ====<br />
<br />
{{fancynote|This file may also be found at /etc/make.conf. /etc/portage/make.conf is the new location.}}<br />
<br />
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:<br />
<br />
<pre><br />
MAKEOPTS="-j3" <br />
</pre><br />
<br />
If you are unsure about how many processors/threads you have then use /proc/cpuinfo to help you.<br />
<console><br />
(chroot) # ##i##grep "processor" /proc/cpuinfo | wc -l<br />
16<br />
</console><br />
<br />
Set MAKEOPTS to this number plus one:<br />
<br />
<pre><br />
MAKEOPTS="-j17"<br />
</pre><br />
<br />
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].<br />
<br />
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:<br />
<br />
<pre><br />
LINGUAS="fr"<br />
</pre><br />
<br />
==== /etc/conf.d/hwclock ====<br />
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.<br />
<console><br />
(chroot) # ##i##nano -w /etc/conf.d/hwclock<br />
</console><br />
<br />
==== Localization ====<br />
<br />
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]].<br />
<br />
==== Profiles ====<br />
<br />
[[Funtoo 1.0 Profile|Funtoo profiles]] are used to define defaults for Portage specific to your needs. There are 4 basic profile types: arch, build, [[Flavors and Mix-ins|flavor, and mix-ins]]:<br />
<br />
;arch: typically <tt>x86-32bit</tt> or <tt>x86-64bit</tt>, this defines the processor type and support of your system. This is defined when your stage was built and should not be changed.<br />
;build: defines whether your system is a <tt>current</tt>, <tt>stable</tt> or <tt>experimental</tt> build. <tt>current</tt> systems will have newer packages unmasked than <tt>stable</tt> systems.<br />
;flavor: defines the general type of system, such as <tt>server</tt> or <tt>desktop</tt>, and will set default USE flags appropriate for your needs.<br />
;mix-ins: define various optional settings that you may be interested in enabling.<br />
<br />
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.<br />
<br />
Remember that profiles can often be inherited. For example, the <tt>desktop</tt> flavor inherits the <tt>workstation</tt> flavor settings, which in turn inherits the <tt>X</tt> and <tt>audio</tt> mix-ins. You can view this by inspecting the <tt>parent</tt> files defined in each profile, which can be found in <tt>/usr/portage/profiles/funtoo/1.0/linux-gnu</tt>:<br />
<br />
<console><br />
(chroot) # ##i##cd /usr/portage/profiles/funtoo/1.0/linux-gnu/<br />
(chroot) # ##i##ls<br />
arch/ eapi make.defaults package.use/ packages.build use.force<br />
build/ flavor/ mix-ins/ package.use.mask/ parent <br />
(chroot) # ##i##cat flavor/desktop/parent <br />
../workstation<br />
../../mix-ins/print<br />
(chroot) # ##i##cat flavor/workstation/parent <br />
../core<br />
../../mix-ins/X<br />
../../mix-ins/audio<br />
../../mix-ins/dvd<br />
../../mix-ins/media<br />
../../mix-ins/console-extras<br />
(chroot) # <br />
</console><br />
<br />
To view installed profiles:<br />
<console><br />
(chroot) # ##i##eselect profile list<br />
</console><br />
<br />
To change the profile flavor:<br />
<console><br />
(chroot) # ##i##eselect profile set-flavor 7<br />
</console><br />
<br />
To add a mix-in:<br />
<br />
<console><br />
(chroot) # ##i##eselect profile add 10<br />
</console><br />
<br />
Remember if you add by string; add a 'gentoo:' to the beginning of the profile name ie:<br />
<console><br />
(chroot) # ##i## eselect profile add gentoo:funtoo/1.0/linux-gnu/mix-ins/console-extras<br />
</console><br />
<br />
=== Configuring and installing the Linux kernel ===<br />
<br />
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.<br />
<br />
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.<br />
<br />
Click [http://wiki.debian.org/DebianKernel here] for a list of all architectures the Debian kernel supports. <br />
<br />
{{fancyimportant|<tt>debian-sources</tt> with <tt>binary</tt> USE flag requires at least 12GB in /var/tmp}}<br />
<br />
<console><br />
(chroot) # ##i##echo "sys-kernel/debian-sources binary" >> /etc/portage/package.use<br />
(chroot) # ##i##emerge debian-sources<br />
</console><br />
<br />
All done!<br />
<br />
{{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>.}}<br />
<br />
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.<br />
<br />
The next step is to configure your boot loader so that your new kernel loads when the system boots.<br />
<br />
=== Installing a Bootloader ===<br />
<br />
==== Installing Grub ====<br />
<br />
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.<br />
<br />
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>.<br />
<br />
<console><br />
(chroot) # ##i##emerge boot-update<br />
</console><br />
<br />
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>. <br />
<br />
<tt>/etc/boot.conf</tt> should now look like this:<br />
<br />
<pre><br />
boot {<br />
generate grub<br />
default "Funtoo Linux genkernel"<br />
timeout 3 <br />
}<br />
<br />
"Funtoo Linux" {<br />
kernel bzImage[-v]<br />
# params += nomodeset<br />
}<br />
<br />
"Funtoo Linux genkernel" {<br />
kernel kernel[-v]<br />
initrd initramfs[-v]<br />
params += real_root=auto <br />
# params += nomodeset<br />
} <br />
</pre><br />
<br />
Please read <tt>man boot.conf</tt> for further details.<br />
<br />
===== Running grub-install and boot-update =====<br />
<br />
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:<br />
<br />
<console><br />
(chroot) # ##i##grub-install --no-floppy /dev/sda<br />
(chroot) # ##i##boot-update<br />
</console><br />
<br />
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.<br />
<br />
OK - your system should be ready to boot! Well, there are a few more loose ends...<br />
<br />
==== Installing Syslinux/Extlinux ====<br />
<br />
An alternate Bootloader is Extlinux, for installing it see the [[Extlinux|extlinux Guide]].<br />
<br />
=== Configuring your network ===<br />
<br />
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.<br />
<br />
==== Wi-Fi ====<br />
<br />
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:<br />
<br />
<console><br />
# ##i##emerge linux-firmware<br />
# ##i##emerge networkmanager<br />
# ##i##rc-update add NetworkManager default<br />
</console><br />
<br />
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.<br />
<br />
After you reboot into Funtoo Linux, you will be able to add a Wi-Fi connection this way:<br />
<br />
<console><br />
# ##i##addwifi -S wpa -K 'wifipassword' mywifinetwork<br />
</console><br />
<br />
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.<br />
<br />
==== Desktop (Wired Ethernet) ====<br />
<br />
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:<br />
<br />
<console><br />
# ##i##rc-update add dhcpcd default<br />
</console><br />
<br />
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.<br />
<br />
==== Server (Static IP) ====<br />
<br />
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.<br />
<br />
=== Finishing Steps ===<br />
<br />
==== Set your root password ====<br />
It's imperative that you set your root password before rebooting so that you can log in.<br />
<console><br />
(chroot) # ##i##passwd<br />
</console><br />
<br />
===Restart your system ===<br />
<br />
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.<br />
<br />
Leave the chroot, change directory to /, unmount your Funtoo partitions, and reboot.<br />
<console><br />
(chroot) # ##i##exit<br />
# ##i##cd /<br />
# ##i##umount /mnt/funtoo/boot /mnt/funtoo/dev /mnt/funtoo/proc /mnt/funtoo<br />
# ##i##reboot<br />
</console><br />
<br />
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!<br />
<br />
===Next Steps===<br />
<br />
To learn how to customize and start using Funtoo Linux, see [[Funtoo Linux First Steps]].<br />
<br />
If your system did not boot correctly, see [[Installation Troubleshooting]] for steps you can take to resolve the problem.<br />
<br />
[[Category:HOWTO]]<br />
[[Category:Install]]</div>Oleghttp://www.funtoo.org/wiki/Metro_Quick_Start_TutorialMetro Quick Start Tutorial2013-02-01T10:24:48Z<p>Oleg: /* How Metro Works */</p>
<hr />
<div>[[Metro]] is the build system for [[Funtoo Linux]] and [[Gentoo Linux]] stages. It automates the bootstrapping process.<br />
<br />
This tutorial will take you through installing, setting up and running [[Metro]].<br />
<br />
= Preface = <br />
<br />
== How Metro Works == <br />
<br />
You may be wondering how [[Metro]] creates its first stage tarball. As you may have guessed, [[Metro]] cannot create a stage tarball out of thin air. To build a new stage tarball, [[Metro]] must use an existing, older stage tarball called a &quot;seed&quot; stage. This &quot;seed&quot; stage typically is used as the ''build environment'' for creating the stage we want.<br />
<br />
[[Metro]] can use two kinds of seed stages. Traditionally, [[Metro]] has used a stage3 as a seed stage. This stage3 is then used to build a new stage1, which in turn is used to build a new stage2, and then a new stage3. This is generally the most reliable way to build [[Gentoo Linux]] or [[Funtoo Linux]], so it's the recommended approach.<br />
{{fancyimportant|'''After switching metro builds to Funtoo profile, Gentoo stages are no longer provided'''!}}<br />
<br />
== Seeds and Build Isolation ==<br />
<br />
Another important concept to mention here is something called ''build isolation''. Because [[Metro]] creates an isolated build environment, and the build environment is explicitly defined using existing, tangible entities -- a seed stage and a portage snapshot -- you will get consistent, repeatable results. In other words, the same seed stage, portage snapshot and build instructions will generate an essentially identical result, even if you perform the build a month later on someone else's workstation.<br />
<br />
== Local Build == <br />
<br />
Say you wanted to build a new <tt>pentium4</tt> stage3 tarball. The recommended method of doing this would be to grab an existing <tt>pentium4</tt> stage3 tarball to use as your seed stage. [[Metro]] will be told to use this existing <tt>pentium4</tt> stage3 to build a new stage1 for the same <tt>pentium4</tt>. For this process, the generic <tt>pentium4</tt> stage3 would provide the ''build environment'' for creating our new stage1. Then, the new stage1 would serve as the build environment for creating the new <tt>pentium4</tt> stage2. And the new <tt>pentium4</tt> stage2 would serve as the build environment for creating the new <tt>pentium4</tt> stage3.<br />
<br />
In the [[Metro]] terminology this is called a '''local build''', which means a stage3 of a given architecture is used to seed a brand new build of the same architecture. Incidentally this will be the first exercise we are going to perform in this tutorial.<br />
<br />
A week later, you may want to build a brand new <tt>pentium4</tt> stage3 tarball. Rather than starting from the original <tt>pentium4</tt> stage3 again, you'd probably configure [[Metro]] to use the most-recently-built <tt>pentium4</tt> stage3 as the seed. [[Metro]] has built-in functionality to make this easy, allowing it to easily find and track the most recent stage3 seed available.<br />
<br />
== Remote Build == <br />
<br />
[[Metro]] can also perform '''remote build''', where a stage3 of a different, but binary compatible, architecture is used as a seed to build a different architecture stage3. Consequentiality the second exercise we are going to perform in this tutorial will be to build a <tt>core2 32bit</tt> stage3 tarball from the <tt>pentium4</tt> stage3 tarball we have just built.<br />
<br />
TODO: add caveats about what archs can be seeded and what can be not (maybe a table?)<br />
<br />
== Tailored Build == <br />
<br />
Last, it's also worthy noting that both in <tt>local</tt> and <tt>remote builds</tt>, [[Metro]] can be configured to add and/or remove individual packages to the final tarball.<br />
Let's say you can't live without <tt>app-misc/screen</tt>, at the end of this tutorial, we will show how to have your tailored stage3 to include it.<br />
<br />
= Installing Metro =<br />
<br />
Today the '''recommended and supported method''' is to use the Git repository of [[Metro]]. First ensure you remove the <tt>dev-util/metro</tt> package if you had installed it:<br />
<br />
<pre><br />
(~) # emerge -aC dev-util/metro<br />
</pre><br />
<br />
Then ensure that <tt>dev-vcs/git</tt> is installed on your system:<br />
<br />
<pre><br />
(~) # emerge dev-vcs/git<br />
</pre><br />
<br />
Next, clone the master git repository as follows:<br />
<br />
<pre><br />
(~) # install -d /root/git<br />
(~) # cd /root/git<br />
(~/git) # git clone git://github.com/funtoo/metro.git<br />
(~/git) # ln -s /root/git/metro /usr/lib/metro<br />
(~/git) # ln -s /root/git/metro/metro /usr/bin/metro<br />
</pre><br />
<br />
You will now have a directory called <tt>/root/git/metro</tt> that contains all the [[Metro]] source code.<br />
Installation complete!<br />
<br />
= Configuring Metro =<br />
<br />
[[User:Drobbins|Daniel Robbins]] maintains [[Metro]], so it comes pre-configured to successfully build both [[Gentoo Linux]] and [[Funtoo Linux]] releases. Before reading farther, you might want to customize some basic settings like the number of concurrent jobs to fit your hardware's capabilities or the directory to use for produced stage archives. This is accomplished by editing <tt>/root/git/metro/etc/metro.conf</tt> which is the [[Metro]]'s master configuration file. The <tt>[path/mirror]</tt> section defines where [[Metro]] will look for things it needs and also dump things it creates. As initially configured, [[Metro]] is set up to build [[Funtoo Linux]] and [[Gentoo Linux]] stage tarballs and place them in the <tt>/home/mirror/linux</tt> directory:<br />
<br />
<pre><br />
# Mirror Paths - where to find required files and where to put created files<br />
<br />
[section path/mirror]<br />
<br />
: /home/mirror/linux<br />
</pre><br />
<br />
If you want to change the location of your mirror on disk, then edit the <tt>/home/mirror/linux</tt> line (which defines the path/mirror variable) to point to another directory.<br />
<br />
For the purpose of the following steps, set an environment variable:<br />
<br />
<pre><br />
(~) # export METRO_MIRROR=/home/mirror/linux<br />
</pre> <br />
<br />
Of course, set the environment variable to whatever location you used in the configuration file.<br />
<br />
== Arch and Subarch ==<br />
<br />
In the following example we are creating a pentium4 stage 3 compiled for x86-32bit binary compatibility. Pentium4 is a subarch of the x86-32bit architecture. Once you have metro installed you may find a full list of each subarch in your <tt>/usr/lib/metro/subarch</tt> directory each subarch will have the file extension .spec<br />
Example:<br />
<pre> <br />
# ls /usr/lib/metro/subarch/<br />
amd64-k10.spec athlon-tbird.spec generic_32.spec native_32.spec pentium-mmx.spec<br />
amd64-k8_32.spec athlon-xp.spec generic_64.spec native_64.spec pentium-m.spec<br />
amd64-k8.spec atom_32.spec generic_sparcv9.spec niagara2.spec pentiumpro.spec<br />
amd64-k8+sse3_32.spec atom_64.spec geode.spec niagara.spec pentium.spec<br />
amd64-k8+sse3.spec btver1_64.spec i486.spec nocona.spec prescott.spec<br />
armv7a.spec btver1.spec i686.spec opteron_64.spec ultrasparc3.spec<br />
athlon-4.spec core2_32.spec k6-2.spec pentium2.spec ultrasparc.spec<br />
athlon-mp.spec core2_64.spec k6-3.spec pentium3.spec xen-pentium4+sse3_64.spec<br />
athlon.spec corei7.spec k6.spec pentium4.spec xen-pentium4+sse3.spec<br />
</pre><br />
<br />
For an example list of Architectures, take a look at the directory listing on the [http://ftp.osuosl.org/pub/funtoo/funtoo-current/ Funtoo-Current Mirror].<br />
<br />
= First stages build (local build) =<br />
<br />
To get this all started, we need to bootstrap the process by downloading an initial seed stage3 to use for building and place it in is proper location in <tt>/home/mirror/linux</tt>, so that [[Metro]] can find it. We will also need to create some special &quot;control&quot; files in <tt>/home/mirror/linux</tt>, which will allow [[Metro]] to understand how it is supposed to proceed.<br />
<br />
== Step 0: Optional Quick Copy of Portage Tree ==<br />
<br />
There is a quick step you can perform to avoid having Metro re-clone the entire Portage tree. Perform this as root:<br />
<br />
<pre><br />
# cd /usr/portage; git checkout origin/master<br />
# install -d /var/tmp/metro/cache/cloned-repositories<br />
# cat /root/git/metro/etc/builds/funtoo-current/build.conf | grep name<br />
name: portage-mini-2011<br />
# cp -a /usr/portage /var/tmp/metro/cache/cloned-repositories/portage-mini-2011<br />
# cd /usr/portage; git checkout funtoo.org<br />
</pre><br />
<br />
== Step 1: Set up pentium4 repository (local build) ==<br />
<br />
Assuming we're following the basic steps outlined in the previous section, and building an unstable funtoo (<tt>funtoo-current</tt>) build for the <tt>pentium4</tt>, using a generic <tt>pentium4</tt> stage3 as a seed stage, then here the first set of steps we'd perform:<br />
<br />
<pre><br />
(~) # install -d "${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"<br />
(~) # cd "${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # install -d 2011-12-13<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # cd 2011-12-13<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4/2011-12-13) # wget -c http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-32bit/pentium4/2011-12-13/stage3-pentium4-funtoo-current-2011-12-13.tar.xz<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4/2011-12-13) # cd ..<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # install -d .control/version<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # echo &quot;2011-12-13&quot; &gt; .control/version/stage3<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # install -d .control/strategy<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # echo &quot;local&quot; &gt; .control/strategy/build<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # echo &quot;stage3&quot; &gt; .control/strategy/seed<br />
</pre><br />
<br />
OK, let's review the steps above. First, we create the directory <tt>"${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"</tt>, which is where Metro will expect to find unstable <tt>funtoo-current</tt> pentium4 builds -- it is configured to look here by default. Then we create a specially-named directory to house our seed x86 stage3. Again, by default, Metro expects the directory to be named this way. We enter this directory, and download our seed x86 stage3 from funtoo.org. Note that the <tt>2010-12-24</tt> version stamp matches. Make sure that your directory name matches the stage3 name too. Everything has been set up to match Metro's default filesystem layout.<br />
<br />
Next, we go back to the <tt>"${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"</tt> directory, and inside it, we create a <tt>.control</tt> directory. This directory and its subdirectories contain special files that Metro references to determine certain aspects of its behavior. The <tt>.control/version/stage3</tt> file is used by Metro to track the most recently-built stage3 for this particular build and subarch. Metro will automatically update this file with a new version stamp after it successfully builds a new stage3. But because Metro didn't actually ''build'' this stage3, we need to set up the <tt>.control/version/stage3</tt> file manually. This will allow Metro to find our downloaded stage3 when we set up our pentium4 build to use it as a seed. Also note that Metro will create a similar <tt>.control/version/stage1</tt> file after it successfully builds an pentium4 funtoo-current stage1.<br />
<br />
We also set up <tt>.control/strategy/build</tt> and <tt>.control/strategy/seed</tt> files with values of <tt>local</tt> and <tt>stage3</tt> respectively. These files define the building strategy Metro will use when we build pentium4 funtoo-current stages. With a build strategy of <tt>local</tt>, Metro will source its seed stage from funtoo-current pentium4, the current directory. And with a seed strategy of <tt>stage3</tt>, Metro will use a stage3 as a seed, and use this seed to build a new stage1, stage2 and stage3.<br />
<br />
== Step 2: Building the pentium4 stages ==<br />
<br />
Incidentally, if all you wanted to do at this point was to build a new pentium4 funtoo-current stage1/2/3 (plus openvz and vserver templates). You would begin the process by typing:<br />
<br />
<pre><br />
# cd /root/git/metro<br />
# scripts/ezbuild.sh funtoo-current pentium4<br />
</pre><br />
<br />
If you have a slow machine, it could take several hours to be completed because several "heavy" components like gcc or glibc have to be recompiled in each stage. Once a stage has been successfully completed, it is placed in the <tt>"${METRO_MIRROR}/funtoo-current/x32-bit/pentium4/YYYY-MM-DD"</tt> subdirectory, where <tt>YYYY-MM-DD</tt> is today's date at the time the <tt>ezbuild.sh</tt> script was started or the date you put on the ezscript.sh command line.<br />
<br />
== Step 3: The next build ==<br />
<br />
At this point, you now have a new pentium4 stage3. If you'd like, you can reconfigure Metro to use the most recently-built pentium4 stage3 as a seed for any pentium4 builds. To do this, simply type:<br />
<br />
<pre>(~) # echo &quot;local&quot; &gt; /home/mirror/linux/funtoo-current/x86-32bit/pentium4/.control/strategy/build</pre><br />
Now, Metro will use the most recentpentium4 stage3 as a seed. The <tt>.control/remote</tt> files you created will be ignored by Metro, since it's no longer going to perform a remote build.<br />
<br />
= Building for another binary compatible architecture (remote build) =<br />
<br />
As written above, [[Metro]] is able to perform '''remote build''' building different architecture stage3 from a binary compatible seeding stage3 (e.g. using a pentium4 stage3 to seed a <tt>Intel Core2 32bits</tt> stage3). <br />
<br />
In the Metro terminology this is called a '''remote build''' (a stage 3 of a different, but binary compatible, architecture is used as a seed). <br />
What's not compatible? You can't use a <tt>Sparc</tt> architecture to generate an <tt>x86</tt> or <tt>ARM</tt> based stage and vice-versa. If you use a 32bit stage then you don't want to seed a 64bit build from it. Be sure that you are using a stage from the same architecture that you are trying to seed. Check [http://ftp.osuosl.org/pub/funtoo/funtoo-current/ Funtoo-current FTP Mirror] for a stage that is from the same Architecture that you will be building. <br />
<br />
== Step 1: Set up Core_2 32bit repository ==<br />
<br />
In this example, we're going to use this pentium4 funtoo-current stage3 to seed a new Core_2 32bit funtoo-current build. To get that done, we need to set up the pentium4 build directory as follows:<br />
<br />
<pre><br />
(~) # cd "${METRO_MIRROR}/funtoo-current/x86-32bit"<br />
(/home/mirror/linux/funtoo-current/x86-32bit) # install -d core2_32<br />
(/home/mirror/linux/funtoo-current/x86-32bit) # cd core2_32<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # install -d .control/strategy<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;remote&quot; &gt; .control/strategy/build<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;stage3&quot; &gt; .control/strategy/seed<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # install -d .control/remote<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;funtoo-current&quot; &gt; .control/remote/build<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;pentium4&quot; &gt; .control/remote/subarch<br />
</pre><br />
<br />
The steps we follow are similar to those we performed for a ''local build'' to set up our pentium4 directory for local build. However, note the differences. We didn't download a stage, because we are going to use the pentium4 stage to build a new Core_2 32bit stage. We also didn't create the <tt>.control/version/stage{1,3}</tt> files because Metro will create them for us after it successfully builds a new stage1 and stage3. We are still using a <tt>stage3</tt> seed strategy, but we've set the build strategy to <tt>remote</tt>, which means that we're going to use a seed stage that's not from this particular subdirectory. Where are we going to get it from? The <tt>.control/remote</tt> directory contains this information, and lets Metro know that it should look for its seed stage3 in the <tt>"${METRO_MIRROR}/home/mirror/linux/funtoo-current/x86-32bit/pentium4"</tt> directory. Which one will it grab? You guessed it -- the most recently built ''stage3'' (since our seed strategy was set to <tt>stage3</tt>) that has the version stamp of <tt>2010-12-24</tt>, as recorded in <tt>"${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4/.control/version/stage3"</tt>. Now you can see how all those control files come together to direct Metro to do the right thing.<br />
<br />
== Step 2: Building the Core_2 32bit stages ==<br />
<br />
Now, you could start building your new Core_2 32bit stage1/2/3 (plus openvz and vserver templates) by typing the following:<br />
<br />
<pre><br />
(~) # /root/git/metro/scripts/ezbuild.sh funtoo-current core2_32<br />
</pre><br />
<br />
In that case, the produced stages are placed in the <tt>"${METRO_MIRROR}/funtoo-current/x32-bit/core2_32/YYYY-MM-DD"</tt> subdirectory.<br />
<br />
== Step 3: The Next Build ==<br />
<br />
At this point, you now have a new Core_2 32bit stage3. If you'd like, you can reconfigure Metro to use the most recently-built Core_2 32bit stage3 as a seed for any new Core_2 32bit builds. <br />
<br />
In the Metro terminology this is called a '''local build''' (a stage 3 of a a given architecture is used to seed a brand new build of the same architecture). <br />
<br />
To do this, simply type:<br />
<br />
<pre><br />
(~) # echo &quot;local&quot; &gt; /home/mirror/linux/funtoo-current/x86-32bit/core2_32/.control/strategy/build<br />
</pre><br />
<br />
Now, Metro will use the most recent Core_2 32bit stage3 as a seed. The <tt>.control/remote</tt> files you created will be ignored by Metro, since it's no longer going to perform a remote build.<br />
<br />
= Build your own tailored stage3 =<br />
<br />
Metro can be easily configured for building custom stage3 by including additional packages. Notice that including packages with heavy dependencies such as gnome, kde, xorg-server is not recommended (not tested so far). Well tested packages are <tt>app-misc/mc</tt>, <tt>app-misc/screen</tt>, <tt>sys-process/htop</tt>, <tt>sys-apps/dstat</tt>. An example for funtoo-current stage. Edit the following configuration file <tt>/root/git/metro/etc/builds/funtoo-current/build.conf</tt>:<br />
<br />
<pre><br />
[collect ../../fslayouts/funtoo/layout.conf]<br />
<br />
[section local]<br />
<br />
author: Daniel Robbins <drobbins@funtoo.org><br />
<br />
[section target]<br />
<br />
build: funtoo-current<br />
compression: xz<br />
<br />
[section portage]<br />
<br />
stable: ~<br />
MAKEOPTS: -j12<br />
FEATURES: mini-manifest<br />
SYNC: $[snapshot/source/remote]<br />
USE:<br />
profile: default/linux/$[target/arch:zap]/2008.0<br />
<br />
[section emerge]<br />
<br />
options: --jobs=4 --load-average=3 --keep-going=n<br />
packages: [<br />
dev-vcs/git <br />
net-misc/dhcpcd<br />
sys-fs/reiserfsprogs<br />
net-misc/bridge-utils<br />
sys-devel/bc<br />
sys-apps/pciutils<br />
app-portage/gentoolkit<br />
app-misc/mc<br />
app-misc/screen<br />
sys-process/htop<br />
sys-apps/dstat <br />
<br />
]<br />
<br />
[section snapshot]</pre><br />
<br />
As you can see MAKEOPTS and emerge default options are additional strings to tweak, --keep-going=n is recommended, if something breaking during the stage building process, you can quickly diagnose the problem.<br />
<br />
Distfiles location can be specified in <tt>/root/git/metro/etc/metro.conf</tt><br />
<br />
<pre><br />
# Main metro configuration file<br />
# <br />
# Path configuration:<br />
<br />
[collect ../targets/$[metro/target]/$[target:zap].spec]<br />
[collect ./builds/$[metro/build]/build.conf]<br />
[collect ../subarch/$[target/subarch:zap].spec]<br />
<br />
# General Paths<br />
<br />
[section path]<br />
tmp: /var/tmp/metro<br />
distfiles: /var/portage/distfiles<br />
work: $[path/tmp]/work/$[metro/build]/$[target/name]<br />
<br />
[section path/cache]<br />
</pre><br />
<br />
[[Category:HOWTO]]<br />
[[Category:Metro]]</div>Oleghttp://www.funtoo.org/wiki/Funtoo_Linux_InstallationFuntoo Linux Installation2013-01-29T14:10:53Z<p>Oleg: /* Live CD */</p>
<hr />
<div>== Introduction ==<br />
<br />
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.<br />
<br />
=== Additional Resources === <br />
<br />
This document was written to help you install Funtoo Linux as efficiently as possible, with a minimum number of distracting options regarding system configuration. <br />
<br />
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.<br />
<br />
If you are installing Funtoo Linux on [[Funtoo Linux Installation on ARM|ARM]] architecture, please see [[Funtoo Linux Installation on ARM]] for notable differences regarding ARM support. An experimental Funtoo Linux build also exists for [[Funtoo Linux Installation on SPARC|SPARC]] platforms. See [[Funtoo Linux Installation on SPARC]]<br />
<br />
== Installation Overview ==<br />
<br />
This is a basic overview of the Funtoo installation process:<br />
<br />
# [[#Live CD|Download and boot the live CD of your choice]].<br />
# [[#Prepare Hard Disk|Prepare your disk]].<br />
# [[#Creating filesystems|Create]] and [[#Mounting filesystems|mount]] filesystems.<br />
# [[#Installing the Stage 3 tarball|Install the Funtoo stage tarball]] of your choice.<br />
# [[#Chroot into Funtoo|Chroot into your new system]].<br />
# [[#Downloading the Portage tree|Download the Portage tree]].<br />
# [[#Configuring your system|Configure your system]] and [[#Configuring your network|network]].<br />
# [[#Configuring and installing the Linux kernel|Install a kernel]].<br />
# [[#Installing a Bootloader|Install a bootloader]].<br />
# [[#Finishing Steps|Complete final steps]].<br />
# [[#Restart your system|Reboot and enjoy]].<br />
<br />
=== Live CD ===<br />
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.<br />
<br />
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.<br />
<br />
To begin a Funtoo Linux installation, download SystemRescueCD from:<br />
<br />
* Main US mirror: [http://ftp.osuosl.org/pub/funtoo/distfiles/sysrescuecd/systemrescuecd-x86-3.3.0.iso The Oregon State University Open Source Lab]<br />
* Main EU mirror: [http://ftp.heanet.ie/mirrors/funtoo/distfiles/sysrescuecd/systemrescuecd-x86-3.3.0.iso HEAnet] or use 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.<br />
<br />
=== Prepare Hard Disk ===<br />
==== Partitions ====<br />
<br />
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:<br />
<br />
===== GPT Partitions =====<br />
<br />
* Newer, preferred format for Linux systems<br />
* Supports 2 TB+ hard drives for booting<br />
* Supports hundreds of partitions per disk of any size<br />
* Requires legacy BIOS boot partition (~32 MB) to be created if system does not use EFI<br />
* Requires bootloader with support for GPT such as GRUB 2, EXTLINUX, or a patched version of GRUB Legacy<br />
<br />
===== MBR Partitions =====<br />
<br />
* Legacy, DOS partitioning scheme<br />
* Only 4 primary partitions per disk; after that, you must use "logical" partitions<br />
* Does not support 2 TB+ disks for booting<br />
* Compatible with certain problematic systems (such as the HP ProBook 4520)<br />
* Dual-boot with Windows for BIOS systems (Windows handle GPT only on true EFI systems, whatever version it is)<br />
* Multiple boot loader options, e.g. GRUB 2, GRUB Legacy, lilo<br />
<br />
{{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.}}<br />
<br />
==== Partitioning Using gdisk ====<br />
<br />
===== Notes Before We Begin =====<br />
<br />
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.<br />
<br />
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 <br />
'''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.<br />
<br />
Advanced users may be interested in the following topics:<br />
<br />
* [[GUID Booting Guide]]<br />
* [[Rootfs over encrypted lvm]]<br />
* [[Rootfs over encrypted lvm over raid-1 on GPT]]<br />
* '''NEW!''' '''[[ZFS Install Guide]]'''<br />
* '''NEW!''' '''[[ZFS rootfs over encrypted container]]'''<br />
<br />
===== Using gdisk =====<br />
<br />
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:<br />
<br />
<console># ##i##gdisk /dev/sda</console><br />
You should find <tt>gdisk</tt> very similar to <tt>fdisk</tt>. Here is the partition table we want to end up with:<br />
<br />
<console>Command (? for help): ##i##p<br />
Disk /dev/sda: 234441648 sectors, 111.8 GiB<br />
Logical sector size: 512 bytes<br />
Disk identifier (GUID): A4E5208A-CED3-4263-BB25-7147DC426931<br />
Partition table holds up to 128 entries<br />
First usable sector is 34, last usable sector is 234441614<br />
Partitions will be aligned on 2048-sector boundaries<br />
Total free space is 2014 sectors (1007.0 KiB)<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 206847 500.0 MiB 8300 Linux filesystem<br />
2 206848 272383 32.0 MiB EF02 BIOS boot partition<br />
3 272384 8660991 4.0 GiB 8200 Linux swap<br />
4 8660992 234441614 107.7 GiB 8300 Linux filesystem<br />
<br />
Command (? for help): </console><br />
<br />
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.<br />
<br />
===== For new <tt>gdisk</tt> users =====<br />
<br />
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.<br />
<br />
Within <tt>gdisk</tt>, follow these steps:<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##1 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+500M ↵<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
'''Create Partition 2''' (GRUB):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##2 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+32M ↵<br />
Hex Code: ##i##EF02 ↵<br />
</console><br />
<br />
'''Create Partition 3''' (swap):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##3 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+4G ↵<br />
Hex Code: ##i##8200 ↵<br />
</console><br />
<br />
'''Create Partition 4''' (root):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##4 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵##!i## (for rest of disk)<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
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:<br />
<br />
'''Write Partition Table To Disk''':<br />
<br />
<console><br />
Command: ##i##w ↵<br />
Do you want to proceed? (Y/N): ##i##Y ↵<br />
</console><br />
<br />
The partition table will now be written to disk and <tt>gdisk</tt> will close.<br />
<br />
Now, your GPT/GUID partitions have been created, and will show up as the following ''block devices'' under Linux:<br />
<br />
* <tt>/dev/sda1</tt>, which will be used to hold the <tt>/boot</tt> filesystem, <br />
* <tt>/dev/sda2</tt>, which will be used directly by the new GRUB,<br />
* <tt>/dev/sda3</tt>, which will be used for swap space, and <br />
* <tt>/dev/sda4</tt>, which will hold your root filesystem.<br />
<br />
===== For Previous fdisk users =====<br />
<br />
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.<br />
<br />
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>.<br />
<br />
===== Partitioning Recommendations =====<br />
<br />
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>:<br />
<br />
{| {{table}} <br />
!Partition<br />
!Size<br />
!MBR Block Device (<tt>fdisk</tt>)<br />
!GPT Block Device (<tt>gdisk</tt>)<br />
!Filesystem<br />
!MBR Code<br />
!GPT Code<br />
|-<br />
|<tt>/boot</tt><br />
|500 MB<br />
|<tt>/dev/sda1</tt><br />
|<tt>/dev/sda1</tt><br />
|ext2<br />
|83<br />
|8300<br />
|-<br />
|GRUB boot loader partition<br />
|32 MB<br />
| ''not required for MBR''<br />
|<tt>/dev/sda2</tt><br />
|For GPT/GUID only, skip for MBR - no filesystem.<br />
|''N/A''<br />
|EF02<br />
|-<br />
|swap<br />
|2x RAM for low-memory systems and production servers; otherwise 2GB.<br />
|<tt>/dev/sda2</tt><br />
|<tt>/dev/sda3</tt><br />
|swap (default)<br />
|82<br />
|8200<br />
|-<br />
|<tt>/</tt> (root)<br />
|Rest of the disk, minimum of 10GB.<br />
|<tt>/dev/sda3</tt><br />
|<tt>/dev/sda4</tt><br />
|XFS recommended, alternatively ext4<br />
|83<br />
|8300<br />
|-<br />
|<tt>/home</tt> (optional) <br />
|User storage and media. Typically most of the disk.<br />
|<tt>/dev/sda4</tt> (if created)<br />
|<tt>/dev/sda5</tt> (if created)<br />
|XFS recommended, alternatively ext4<br />
|83<br />
|8300<br />
|-<br />
| LVM (optional)<br />
| If you want to create an LVM volume.<br />
| <tt>/dev/sda4</tt> (PV, if created)<br />
| <tt>/dev/sda5</tt> (PV, if created)<br />
| LVM PV<br />
| 8E<br />
| 8E00<br />
|}<br />
<br />
==== Creating filesystems ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<br />
<console><br />
# ##i##mke2fs -t ext2 /dev/sda1 <br />
# ##i##mkfs.xfs /dev/sda4<br />
# ##i##mkswap /dev/sda3<br />
# ##i##swapon /dev/sda3<br />
</console><br />
<br />
==== Mounting filesystems ====<br />
<br />
Mount the newly-created filesystems as follows, creating <tt>/mnt/funtoo</tt> as the installation mount point:<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo<br />
# ##i##mount /dev/sda4 /mnt/funtoo<br />
# ##i##mkdir /mnt/funtoo/boot<br />
# ##i##mount /dev/sda1 /mnt/funtoo/boot<br />
</console><br />
<br />
Optionally, if you have a separate filesystem for <tt>/home</tt> or anything else:<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo/home<br />
# ##i##mount /dev/sda5 /mnt/funtoo/home<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##chmod 1777 /mnt/funtoo/tmp<br />
</console><br />
<br />
=== Installing the Stage 3 tarball ===<br />
==== Stage 3 tarball ====<br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
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:<br />
<br />
<console><br />
# ##i##date<br />
Fri Jul 15 19:47:18 UTC 2011<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##date 071620002011<br />
Fri Jul 16 20:00:00 UTC 2011<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
# ##i##wget -O - http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-64bit/generic_64/stage3-latest.tar.xz | tar xfvJp -<br />
</console><br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
=== Chroot into Funtoo ===<br />
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:<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
# ##i##mount --bind /proc proc<br />
# ##i##mount --bind /dev dev<br />
</console><br />
<br />
You'll also want to copy over <tt>resolv.conf</tt> in order to have proper DNS name resolution from inside the chroot:<br />
<console><br />
# ##i##cp /etc/resolv.conf etc<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l<br />
</console><br />
<br />
{{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.}}<br />
{{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.}}<br />
<br />
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:<br />
<console><br />
# ##i##export PS1="(chroot) $PS1"<br />
</console><br />
<br />
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.<br />
<br />
=== Downloading the Portage tree ===<br />
<br />
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]:<br />
<br />
<console><br />
(chroot) # ##i##emerge --sync<br />
</console><br />
<br />
{{fancynote|For an alternative way to do this, see [[Installing Portage From Snapshot]].}}<br />
<br />
=== Configuring your system ===<br />
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:<br />
<br />
{| {{table}}<br />
!File<br />
!Do I need to change it?<br />
!Description<br />
|-<br />
|<tt>/etc/fstab</tt><br />
|'''YES - required'''<br />
|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.<br />
|-<br />
|<tt>/etc/localtime</tt><br />
|''Maybe - recommended''<br />
|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) <br />
|-<br />
|<tt>/etc/make.conf<br/>/etc/portage/make.conf&nbsp;(new&nbsp;location)</tt><br />
|''Maybe - recommended''<br />
|Parameters used by gcc (compiler), portage, and make. It's a good idea to set MAKEOPTS. This is covered later in this document.<br />
|-<br />
|<tt>/etc/conf.d/hostname</tt><br />
|''Maybe - recommended''<br />
|Used to set system hostname. Set to the fully-qualified (with dots) name. Defaults to <tt>localhost</tt> if not set.<br />
|-<br />
|<tt>/etc/hosts</tt><br />
|''No''<br />
| You no longer need to manually set the hostname in this file. This file is automatically generated by <tt>/etc/init.d/hostname</tt>.<br />
|-<br />
|<tt>/etc/conf.d/keymaps</tt><br />
|Optional<br />
|Keyboard mapping configuration file (for console pseudo-terminals). Set if you have a non-US keyboard. See [[Funtoo Linux Localization]].<br />
|-<br />
|<tt>/etc/conf.d/hwclock</tt><br />
|Optional<br />
|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.<br />
|-<br />
|<tt>/etc/conf.d/modules</tt><br />
|Optional<br />
|Kernel modules to load automatically at system startup. Typically not required. See [[Additional Kernel Resources]] for more info.<br />
|-<br />
|<tt>profiles</tt><br />
|Optional<br />
|Some useful portage settings that may help speed up intial configuration.<br />
|}<br />
<br />
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]])<br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
==== /etc/fstab ====<br />
<br />
<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:<br />
<br />
<console><br />
(chroot) # ##i##nano -w /etc/fstab<br />
</console><br />
<br />
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.<br />
<br />
<pre><br />
# The root filesystem should have a pass number of either 0 or 1.<br />
# All other filesystems should have a pass number of 0 or greater than 1.<br />
#<br />
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.<br />
#<br />
# See the manpage fstab(5) for more information.<br />
#<br />
# <fs> <mountpoint> <type> <opts> <dump/pass><br />
<br />
/dev/sda1 /boot ext2 noatime 1 2<br />
/dev/sda3 none swap sw 0 0<br />
/dev/sda4 / xfs noatime 0 1<br />
#/dev/cdrom /mnt/cdrom auto noauto,ro 0 0<br />
</pre><br />
<br />
==== /etc/localtime ====<br />
<br />
<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. <br />
<br />
<pre><br />
(chroot) # ln -sf /usr/share/zoneinfo/America/Montreal /etc/localtime<br />
</pre><br />
<br />
The above sets the timezone to Eastern Time Canada. Go to <tt>/usr/share/zoneinfo</tt> to see which values to use.<br />
<br />
==== /etc/portage/make.conf ====<br />
<br />
{{fancynote|This file may also be found at /etc/make.conf. /etc/portage/make.conf is the new location.}}<br />
<br />
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:<br />
<br />
<pre><br />
MAKEOPTS="-j3" <br />
</pre><br />
<br />
If you are unsure about how many processors/threads you have then use /proc/cpuinfo to help you.<br />
<console><br />
(chroot) # ##i##grep "processor" /proc/cpuinfo | wc -l<br />
16<br />
</console><br />
<br />
Set MAKEOPTS to this number plus one:<br />
<br />
<pre><br />
MAKEOPTS="-j17"<br />
</pre><br />
<br />
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].<br />
<br />
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:<br />
<br />
<pre><br />
LINGUAS="fr"<br />
</pre><br />
<br />
==== /etc/conf.d/hwclock ====<br />
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.<br />
<console><br />
(chroot) # ##i##nano -w /etc/conf.d/hwclock<br />
</console><br />
<br />
==== Localization ====<br />
<br />
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]].<br />
<br />
==== Profiles ====<br />
<br />
[[Funtoo 1.0 Profile|Funtoo profiles]] are used to define defaults for Portage specific to your needs. There are 4 basic profile types: arch, build, [[Flavors and Mix-ins|flavor, and mix-ins]]:<br />
<br />
;arch: typically <tt>x86-32bit</tt> or <tt>x86-64bit</tt>, this defines the processor type and support of your system. This is defined when your stage was built and should not be changed.<br />
;build: defines whether your system is a <tt>current</tt>, <tt>stable</tt> or <tt>experimental</tt> build. <tt>current</tt> systems will have newer packages unmasked than <tt>stable</tt> systems.<br />
;flavor: defines the general type of system, such as <tt>server</tt> or <tt>desktop</tt>, and will set default USE flags appropriate for your needs.<br />
;mix-ins: define various optional settings that you may be interested in enabling.<br />
<br />
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.<br />
<br />
Remember that profiles can often be inherited. For example, the <tt>desktop</tt> flavor inherits the <tt>workstation</tt> flavor settings, which in turn inherits the <tt>X</tt> and <tt>audio</tt> mix-ins. You can view this by inspecting the <tt>parent</tt> files defined in each profile, which can be found in <tt>/usr/portage/profiles/funtoo/1.0/linux-gnu</tt>:<br />
<br />
<console><br />
(chroot) # ##i##cd /usr/portage/profiles/funtoo/1.0/linux-gnu/<br />
(chroot) # ##i##ls<br />
arch/ eapi make.defaults package.use/ packages.build use.force<br />
build/ flavor/ mix-ins/ package.use.mask/ parent <br />
(chroot) # ##i##cat flavor/desktop/parent <br />
../workstation<br />
../../mix-ins/print<br />
(chroot) # ##i##cat flavor/workstation/parent <br />
../core<br />
../../mix-ins/X<br />
../../mix-ins/audio<br />
../../mix-ins/dvd<br />
../../mix-ins/media<br />
../../mix-ins/console-extras<br />
(chroot) # <br />
</console><br />
<br />
To view installed profiles:<br />
<console><br />
(chroot) # ##i##eselect profile list<br />
</console><br />
<br />
To change the profile flavor:<br />
<console><br />
(chroot) # ##i##eselect profile set-flavor 7<br />
</console><br />
<br />
To add a mix-in:<br />
<br />
<console><br />
(chroot) # ##i##eselect profile add 10<br />
</console><br />
<br />
Remember if you add by string; add a 'gentoo:' to the beginning of the profile name ie:<br />
<console><br />
(chroot) # ##i## eselect profile add gentoo:funtoo/1.0/linux-gnu/mix-ins/console-extras<br />
</console><br />
<br />
=== Configuring and installing the Linux kernel ===<br />
<br />
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.<br />
<br />
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.<br />
<br />
{{fancyimportant|<tt>debian-sources</tt> with <tt>binary</tt> USE flag requires at least 12GB in /var/tmp}}<br />
<br />
<console><br />
(chroot) # ##i##echo "sys-kernel/debian-sources binary" >> /etc/portage/package.use<br />
(chroot) # ##i##emerge debian-sources<br />
</console><br />
<br />
All done!<br />
<br />
{{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>.}}<br />
<br />
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.<br />
<br />
The next step is to configure your boot loader so that your new kernel loads when the system boots.<br />
<br />
=== Installing a Bootloader ===<br />
<br />
==== Installing Grub ====<br />
<br />
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.<br />
<br />
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>.<br />
<br />
<console><br />
(chroot) # ##i##emerge boot-update<br />
</console><br />
<br />
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>. <br />
<br />
<tt>/etc/boot.conf</tt> should now look like this:<br />
<br />
<pre><br />
boot {<br />
generate grub<br />
default "Funtoo Linux genkernel"<br />
timeout 3 <br />
}<br />
<br />
"Funtoo Linux" {<br />
kernel bzImage[-v]<br />
# params += nomodeset<br />
}<br />
<br />
"Funtoo Linux genkernel" {<br />
kernel kernel[-v]<br />
initrd initramfs[-v]<br />
params += real_root=auto <br />
# params += nomodeset<br />
} <br />
</pre><br />
<br />
Please read <tt>man boot.conf</tt> for further details.<br />
<br />
===== Running grub-install and boot-update =====<br />
<br />
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:<br />
<br />
<console><br />
(chroot) # ##i##grub-install --no-floppy /dev/sda<br />
(chroot) # ##i##boot-update<br />
</console><br />
<br />
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.<br />
<br />
OK - your system should be ready to boot! Well, there are a few more loose ends...<br />
<br />
==== Installing Syslinux/Extlinux ====<br />
<br />
An alternate Bootloader is Extlinux, for installing it see the [[Extlinux|extlinux Guide]].<br />
<br />
=== Configuring your network ===<br />
<br />
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.<br />
<br />
==== Wi-Fi ====<br />
<br />
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:<br />
<br />
<console><br />
# ##i##emerge linux-firmware<br />
# ##i##emerge networkmanager<br />
# ##i##rc-update add NetworkManager default<br />
</console><br />
<br />
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.<br />
<br />
After you reboot into Funtoo Linux, you will be able to add a Wi-Fi connection this way:<br />
<br />
<console><br />
# ##i##addwifi -S wpa -K 'wifipassword' mywifinetwork<br />
</console><br />
<br />
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.<br />
<br />
==== Desktop (Wired Ethernet) ====<br />
<br />
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:<br />
<br />
<console><br />
# ##i##rc-update add dhcpcd default<br />
</console><br />
<br />
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.<br />
<br />
==== Server (Static IP) ====<br />
<br />
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.<br />
<br />
=== Finishing Steps ===<br />
<br />
==== Set your root password ====<br />
It's imperative that you set your root password before rebooting so that you can log in.<br />
<console><br />
(chroot) # ##i##passwd<br />
</console><br />
<br />
===Restart your system ===<br />
<br />
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.<br />
<br />
Leave the chroot, change directory to /, unmount your Funtoo partitions, and reboot.<br />
<console><br />
(chroot) # ##i##exit<br />
# ##i##cd /<br />
# ##i##umount /mnt/funtoo/boot /mnt/funtoo/dev /mnt/funtoo/proc /mnt/funtoo<br />
# ##i##reboot<br />
</console><br />
<br />
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!<br />
<br />
===Next Steps===<br />
<br />
To learn how to customize and start using Funtoo Linux, see [[Funtoo Linux First Steps]].<br />
<br />
If your system did not boot correctly, see [[Installation Troubleshooting]] for steps you can take to resolve the problem.<br />
<br />
[[Category:HOWTO]]<br />
[[Category:Install]]</div>Oleghttp://www.funtoo.org/wiki/Funtoo_Linux_InstallationFuntoo Linux Installation2013-01-29T06:37:11Z<p>Oleg: </p>
<hr />
<div>== Introduction ==<br />
<br />
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.<br />
<br />
=== Additional Resources === <br />
<br />
This document was written to help you install Funtoo Linux as efficiently as possible, with a minimum number of distracting options regarding system configuration. <br />
<br />
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.<br />
<br />
If you are installing Funtoo Linux on [[Funtoo Linux Installation on ARM|ARM]] architecture, please see [[Funtoo Linux Installation on ARM]] for notable differences regarding ARM support. An experimental Funtoo Linux build also exists for [[Funtoo Linux Installation on SPARC|SPARC]] platforms. See [[Funtoo Linux Installation on SPARC]]<br />
<br />
== Installation Overview ==<br />
<br />
This is a basic overview of the Funtoo installation process:<br />
<br />
# [[#Live CD|Download and boot the live CD of your choice]].<br />
# [[#Prepare Hard Disk|Prepare your disk]].<br />
# [[#Creating filesystems|Create]] and [[#Mounting filesystems|mount]] filesystems.<br />
# [[#Installing the Stage 3 tarball|Install the Funtoo stage tarball]] of your choice.<br />
# [[#Chroot into Funtoo|Chroot into your new system]].<br />
# [[#Downloading the Portage tree|Download the Portage tree]].<br />
# [[#Configuring your system|Configure your system]] and [[#Configuring your network|network]].<br />
# [[#Configuring and installing the Linux kernel|Install a kernel]].<br />
# [[#Installing a Bootloader|Install a bootloader]].<br />
# [[#Finishing Steps|Complete final steps]].<br />
# [[#Restart your system|Reboot and enjoy]].<br />
<br />
=== Live CD ===<br />
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.<br />
<br />
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.<br />
<br />
To begin a Funtoo Linux installation, download and burn [http://ftp.osuosl.org/pub/funtoo/distfiles/sysrescuecd/systemrescuecd-x86-3.3.0.iso 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.<br />
<br />
=== Prepare Hard Disk ===<br />
==== Partitions ====<br />
<br />
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:<br />
<br />
===== GPT Partitions =====<br />
<br />
* Newer, preferred format for Linux systems<br />
* Supports 2 TB+ hard drives for booting<br />
* Supports hundreds of partitions per disk of any size<br />
* Requires legacy BIOS boot partition (~32 MB) to be created if system does not use EFI<br />
* Requires bootloader with support for GPT such as GRUB 2, EXTLINUX, or a patched version of GRUB Legacy<br />
<br />
===== MBR Partitions =====<br />
<br />
* Legacy, DOS partitioning scheme<br />
* Only 4 primary partitions per disk; after that, you must use "logical" partitions<br />
* Does not support 2 TB+ disks for booting<br />
* Compatible with certain problematic systems (such as the HP ProBook 4520)<br />
* Dual-boot with Windows for BIOS systems (Windows handle GPT only on true EFI systems, whatever version it is)<br />
* Multiple boot loader options, e.g. GRUB 2, GRUB Legacy, lilo<br />
<br />
{{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.}}<br />
<br />
==== Partitioning Using gdisk ====<br />
<br />
===== Notes Before We Begin =====<br />
<br />
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.<br />
<br />
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 <br />
'''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.<br />
<br />
Advanced users may be interested in the following topics:<br />
<br />
* [[GUID Booting Guide]]<br />
* [[Rootfs over encrypted lvm]]<br />
* [[Rootfs over encrypted lvm over raid-1 on GPT]]<br />
* '''NEW!''' '''[[ZFS Install Guide]]'''<br />
* '''NEW!''' '''[[ZFS rootfs over encrypted container]]'''<br />
<br />
===== Using gdisk =====<br />
<br />
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:<br />
<br />
<console># ##i##gdisk /dev/sda</console><br />
You should find <tt>gdisk</tt> very similar to <tt>fdisk</tt>. Here is the partition table we want to end up with:<br />
<br />
<console>Command (? for help): ##i##p<br />
Disk /dev/sda: 234441648 sectors, 111.8 GiB<br />
Logical sector size: 512 bytes<br />
Disk identifier (GUID): A4E5208A-CED3-4263-BB25-7147DC426931<br />
Partition table holds up to 128 entries<br />
First usable sector is 34, last usable sector is 234441614<br />
Partitions will be aligned on 2048-sector boundaries<br />
Total free space is 2014 sectors (1007.0 KiB)<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 206847 500.0 MiB 8300 Linux filesystem<br />
2 206848 272383 32.0 MiB EF02 BIOS boot partition<br />
3 272384 8660991 4.0 GiB 8200 Linux swap<br />
4 8660992 234441614 107.7 GiB 8300 Linux filesystem<br />
<br />
Command (? for help): </console><br />
<br />
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.<br />
<br />
===== For new <tt>gdisk</tt> users =====<br />
<br />
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.<br />
<br />
Within <tt>gdisk</tt>, follow these steps:<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##1 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+500M ↵<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
'''Create Partition 2''' (GRUB):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##2 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+32M ↵<br />
Hex Code: ##i##EF02 ↵<br />
</console><br />
<br />
'''Create Partition 3''' (swap):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##3 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+4G ↵<br />
Hex Code: ##i##8200 ↵<br />
</console><br />
<br />
'''Create Partition 4''' (root):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##4 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵##!i## (for rest of disk)<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
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:<br />
<br />
'''Write Partition Table To Disk''':<br />
<br />
<console><br />
Command: ##i##w ↵<br />
Do you want to proceed? (Y/N): ##i##Y ↵<br />
</console><br />
<br />
The partition table will now be written to disk and <tt>gdisk</tt> will close.<br />
<br />
Now, your GPT/GUID partitions have been created, and will show up as the following ''block devices'' under Linux:<br />
<br />
* <tt>/dev/sda1</tt>, which will be used to hold the <tt>/boot</tt> filesystem, <br />
* <tt>/dev/sda2</tt>, which will be used directly by the new GRUB,<br />
* <tt>/dev/sda3</tt>, which will be used for swap space, and <br />
* <tt>/dev/sda4</tt>, which will hold your root filesystem.<br />
<br />
===== For Previous fdisk users =====<br />
<br />
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.<br />
<br />
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>.<br />
<br />
===== Partitioning Recommendations =====<br />
<br />
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>:<br />
<br />
{| {{table}} <br />
!Partition<br />
!Size<br />
!MBR Block Device (<tt>fdisk</tt>)<br />
!GPT Block Device (<tt>gdisk</tt>)<br />
!Filesystem<br />
!MBR Code<br />
!GPT Code<br />
|-<br />
|<tt>/boot</tt><br />
|500 MB<br />
|<tt>/dev/sda1</tt><br />
|<tt>/dev/sda1</tt><br />
|ext2<br />
|83<br />
|8300<br />
|-<br />
|GRUB boot loader partition<br />
|32 MB<br />
| ''not required for MBR''<br />
|<tt>/dev/sda2</tt><br />
|For GPT/GUID only, skip for MBR - no filesystem.<br />
|''N/A''<br />
|EF02<br />
|-<br />
|swap<br />
|2x RAM for low-memory systems and production servers; otherwise 2GB.<br />
|<tt>/dev/sda2</tt><br />
|<tt>/dev/sda3</tt><br />
|swap (default)<br />
|82<br />
|8200<br />
|-<br />
|<tt>/</tt> (root)<br />
|Rest of the disk, minimum of 10GB.<br />
|<tt>/dev/sda3</tt><br />
|<tt>/dev/sda4</tt><br />
|XFS recommended, alternatively ext4<br />
|83<br />
|8300<br />
|-<br />
|<tt>/home</tt> (optional) <br />
|User storage and media. Typically most of the disk.<br />
|<tt>/dev/sda4</tt> (if created)<br />
|<tt>/dev/sda5</tt> (if created)<br />
|XFS recommended, alternatively ext4<br />
|83<br />
|8300<br />
|-<br />
| LVM (optional)<br />
| If you want to create an LVM volume.<br />
| <tt>/dev/sda4</tt> (PV, if created)<br />
| <tt>/dev/sda5</tt> (PV, if created)<br />
| LVM PV<br />
| 8E<br />
| 8E00<br />
|}<br />
<br />
==== Creating filesystems ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<br />
<console><br />
# ##i##mke2fs -t ext2 /dev/sda1 <br />
# ##i##mkfs.xfs /dev/sda4<br />
# ##i##mkswap /dev/sda3<br />
# ##i##swapon /dev/sda3<br />
</console><br />
<br />
==== Mounting filesystems ====<br />
<br />
Mount the newly-created filesystems as follows, creating <tt>/mnt/funtoo</tt> as the installation mount point:<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo<br />
# ##i##mount /dev/sda4 /mnt/funtoo<br />
# ##i##mkdir /mnt/funtoo/boot<br />
# ##i##mount /dev/sda1 /mnt/funtoo/boot<br />
</console><br />
<br />
Optionally, if you have a separate filesystem for <tt>/home</tt> or anything else:<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo/home<br />
# ##i##mount /dev/sda5 /mnt/funtoo/home<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##chmod 1777 /mnt/funtoo/tmp<br />
</console><br />
<br />
=== Installing the Stage 3 tarball ===<br />
==== Stage 3 tarball ====<br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
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:<br />
<br />
<console><br />
# ##i##date<br />
Fri Jul 15 19:47:18 UTC 2011<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##date 071620002011<br />
Fri Jul 16 20:00:00 UTC 2011<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
# ##i##wget -O - http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-64bit/generic_64/stage3-latest.tar.xz | tar xfvJp -<br />
</console><br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
=== Chroot into Funtoo ===<br />
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:<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
# ##i##mount --bind /proc proc<br />
# ##i##mount --bind /dev dev<br />
</console><br />
<br />
You'll also want to copy over <tt>resolv.conf</tt> in order to have proper DNS name resolution from inside the chroot:<br />
<console><br />
# ##i##cp /etc/resolv.conf etc<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l<br />
</console><br />
<br />
{{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.}}<br />
{{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.}}<br />
<br />
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:<br />
<console><br />
# ##i##export PS1="(chroot) $PS1"<br />
</console><br />
<br />
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.<br />
<br />
=== Downloading the Portage tree ===<br />
<br />
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]:<br />
<br />
<console><br />
(chroot) # ##i##emerge --sync<br />
</console><br />
<br />
{{fancynote|For an alternative way to do this, see [[Installing Portage From Snapshot]].}}<br />
<br />
=== Configuring your system ===<br />
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:<br />
<br />
{| {{table}}<br />
!File<br />
!Do I need to change it?<br />
!Description<br />
|-<br />
|<tt>/etc/fstab</tt><br />
|'''YES - required'''<br />
|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.<br />
|-<br />
|<tt>/etc/localtime</tt><br />
|''Maybe - recommended''<br />
|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) <br />
|-<br />
|<tt>/etc/make.conf<br/>/etc/portage/make.conf&nbsp;(new&nbsp;location)</tt><br />
|''Maybe - recommended''<br />
|Parameters used by gcc (compiler), portage, and make. It's a good idea to set MAKEOPTS. This is covered later in this document.<br />
|-<br />
|<tt>/etc/conf.d/hostname</tt><br />
|''Maybe - recommended''<br />
|Used to set system hostname. Set to the fully-qualified (with dots) name. Defaults to <tt>localhost</tt> if not set.<br />
|-<br />
|<tt>/etc/hosts</tt><br />
|''No''<br />
| You no longer need to manually set the hostname in this file. This file is automatically generated by <tt>/etc/init.d/hostname</tt>.<br />
|-<br />
|<tt>/etc/conf.d/keymaps</tt><br />
|Optional<br />
|Keyboard mapping configuration file (for console pseudo-terminals). Set if you have a non-US keyboard. See [[Funtoo Linux Localization]].<br />
|-<br />
|<tt>/etc/conf.d/hwclock</tt><br />
|Optional<br />
|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.<br />
|-<br />
|<tt>/etc/conf.d/modules</tt><br />
|Optional<br />
|Kernel modules to load automatically at system startup. Typically not required. See [[Additional Kernel Resources]] for more info.<br />
|-<br />
|<tt>profiles</tt><br />
|Optional<br />
|Some useful portage settings that may help speed up intial configuration.<br />
|}<br />
<br />
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]])<br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
==== /etc/fstab ====<br />
<br />
<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:<br />
<br />
<console><br />
(chroot) # ##i##nano -w /etc/fstab<br />
</console><br />
<br />
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.<br />
<br />
<pre><br />
# The root filesystem should have a pass number of either 0 or 1.<br />
# All other filesystems should have a pass number of 0 or greater than 1.<br />
#<br />
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.<br />
#<br />
# See the manpage fstab(5) for more information.<br />
#<br />
# <fs> <mountpoint> <type> <opts> <dump/pass><br />
<br />
/dev/sda1 /boot ext2 noatime 1 2<br />
/dev/sda3 none swap sw 0 0<br />
/dev/sda4 / xfs noatime 0 1<br />
#/dev/cdrom /mnt/cdrom auto noauto,ro 0 0<br />
</pre><br />
<br />
==== /etc/localtime ====<br />
<br />
<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. <br />
<br />
<pre><br />
(chroot) # ln -sf /usr/share/zoneinfo/America/Montreal /etc/localtime<br />
</pre><br />
<br />
The above sets the timezone to Eastern Time Canada. Go to <tt>/usr/share/zoneinfo</tt> to see which values to use.<br />
<br />
==== /etc/portage/make.conf ====<br />
<br />
{{fancynote|This file may also be found at /etc/make.conf. /etc/portage/make.conf is the new location.}}<br />
<br />
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:<br />
<br />
<pre><br />
MAKEOPTS="-j3" <br />
</pre><br />
<br />
If you are unsure about how many processors/threads you have then use /proc/cpuinfo to help you.<br />
<console><br />
(chroot) # ##i##grep "processor" /proc/cpuinfo | wc -l<br />
16<br />
</console><br />
<br />
Set MAKEOPTS to this number plus one:<br />
<br />
<pre><br />
MAKEOPTS="-j17"<br />
</pre><br />
<br />
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].<br />
<br />
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:<br />
<br />
<pre><br />
LINGUAS="fr"<br />
</pre><br />
<br />
==== /etc/conf.d/hwclock ====<br />
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.<br />
<console><br />
(chroot) # ##i##nano -w /etc/conf.d/hwclock<br />
</console><br />
<br />
==== Localization ====<br />
<br />
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]].<br />
<br />
==== Profiles ====<br />
<br />
[[Funtoo 1.0 Profile|Funtoo profiles]] are used to define defaults for Portage specific to your needs. There are 4 basic profile types: arch, build, [[Flavors and Mix-ins|flavor, and mix-ins]]:<br />
<br />
;arch: typically <tt>x86-32bit</tt> or <tt>x86-64bit</tt>, this defines the processor type and support of your system. This is defined when your stage was built and should not be changed.<br />
;build: defines whether your system is a <tt>current</tt>, <tt>stable</tt> or <tt>experimental</tt> build. <tt>current</tt> systems will have newer packages unmasked than <tt>stable</tt> systems.<br />
;flavor: defines the general type of system, such as <tt>server</tt> or <tt>desktop</tt>, and will set default USE flags appropriate for your needs.<br />
;mix-ins: define various optional settings that you may be interested in enabling.<br />
<br />
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.<br />
<br />
Remember that profiles can often be inherited. For example, the <tt>desktop</tt> flavor inherits the <tt>workstation</tt> flavor settings, which in turn inherits the <tt>X</tt> and <tt>audio</tt> mix-ins. You can view this by inspecting the <tt>parent</tt> files defined in each profile, which can be found in <tt>/usr/portage/profiles/funtoo/1.0/linux-gnu</tt>:<br />
<br />
<console><br />
(chroot) # ##i##cd /usr/portage/profiles/funtoo/1.0/linux-gnu/<br />
(chroot) # ##i##ls<br />
arch/ eapi make.defaults package.use/ packages.build use.force<br />
build/ flavor/ mix-ins/ package.use.mask/ parent <br />
(chroot) # ##i##cat flavor/desktop/parent <br />
../workstation<br />
../../mix-ins/print<br />
(chroot) # ##i##cat flavor/workstation/parent <br />
../core<br />
../../mix-ins/X<br />
../../mix-ins/audio<br />
../../mix-ins/dvd<br />
../../mix-ins/media<br />
../../mix-ins/console-extras<br />
(chroot) # <br />
</console><br />
<br />
To view installed profiles:<br />
<console><br />
(chroot) # ##i##eselect profile list<br />
</console><br />
<br />
To change the profile flavor:<br />
<console><br />
(chroot) # ##i##eselect profile set-flavor 7<br />
</console><br />
<br />
To add a mix-in:<br />
<br />
<console><br />
(chroot) # ##i##eselect profile add 10<br />
</console><br />
<br />
Remember if you add by string; add a 'gentoo:' to the beginning of the profile name ie:<br />
<console><br />
(chroot) # ##i## eselect profile add gentoo:funtoo/1.0/linux-gnu/mix-ins/console-extras<br />
</console><br />
<br />
=== Configuring and installing the Linux kernel ===<br />
<br />
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.<br />
<br />
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.<br />
<br />
{{fancyimportant|<tt>debian-sources</tt> with <tt>binary</tt> USE flag requires at least 12GB in /var/tmp}}<br />
<br />
<console><br />
(chroot) # ##i##echo "sys-kernel/debian-sources binary" >> /etc/portage/package.use<br />
(chroot) # ##i##emerge debian-sources<br />
</console><br />
<br />
All done!<br />
<br />
{{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>.}}<br />
<br />
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.<br />
<br />
The next step is to configure your boot loader so that your new kernel loads when the system boots.<br />
<br />
=== Installing a Bootloader ===<br />
<br />
==== Installing Grub ====<br />
<br />
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.<br />
<br />
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>.<br />
<br />
<console><br />
(chroot) # ##i##emerge boot-update<br />
</console><br />
<br />
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>. <br />
<br />
<tt>/etc/boot.conf</tt> should now look like this:<br />
<br />
<pre><br />
boot {<br />
generate grub<br />
default "Funtoo Linux genkernel"<br />
timeout 3 <br />
}<br />
<br />
"Funtoo Linux" {<br />
kernel bzImage[-v]<br />
# params += nomodeset<br />
}<br />
<br />
"Funtoo Linux genkernel" {<br />
kernel kernel[-v]<br />
initrd initramfs[-v]<br />
params += real_root=auto <br />
# params += nomodeset<br />
} <br />
</pre><br />
<br />
Please read <tt>man boot.conf</tt> for further details.<br />
<br />
===== Running grub-install and boot-update =====<br />
<br />
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:<br />
<br />
<console><br />
(chroot) # ##i##grub-install --no-floppy /dev/sda<br />
(chroot) # ##i##boot-update<br />
</console><br />
<br />
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.<br />
<br />
OK - your system should be ready to boot! Well, there are a few more loose ends...<br />
<br />
==== Installing Syslinux/Extlinux ====<br />
<br />
An alternate Bootloader is Extlinux, for installing it see the [[Extlinux|extlinux Guide]].<br />
<br />
=== Configuring your network ===<br />
<br />
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.<br />
<br />
==== Wi-Fi ====<br />
<br />
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:<br />
<br />
<console><br />
# ##i##emerge linux-firmware<br />
# ##i##emerge networkmanager<br />
# ##i##rc-update add NetworkManager default<br />
</console><br />
<br />
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.<br />
<br />
After you reboot into Funtoo Linux, you will be able to add a Wi-Fi connection this way:<br />
<br />
<console><br />
# ##i##addwifi -S wpa -K 'wifipassword' mywifinetwork<br />
</console><br />
<br />
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.<br />
<br />
==== Desktop (Wired Ethernet) ====<br />
<br />
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:<br />
<br />
<console><br />
# ##i##rc-update add dhcpcd default<br />
</console><br />
<br />
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.<br />
<br />
==== Server (Static IP) ====<br />
<br />
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.<br />
<br />
=== Finishing Steps ===<br />
<br />
==== Set your root password ====<br />
It's imperative that you set your root password before rebooting so that you can log in.<br />
<console><br />
(chroot) # ##i##passwd<br />
</console><br />
<br />
===Restart your system ===<br />
<br />
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.<br />
<br />
Leave the chroot, change directory to /, unmount your Funtoo partitions, and reboot.<br />
<console><br />
(chroot) # ##i##exit<br />
# ##i##cd /<br />
# ##i##umount /mnt/funtoo/boot /mnt/funtoo/dev /mnt/funtoo/proc /mnt/funtoo<br />
# ##i##reboot<br />
</console><br />
<br />
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!<br />
<br />
===Next Steps===<br />
<br />
To learn how to customize and start using Funtoo Linux, see [[Funtoo Linux First Steps]].<br />
<br />
If your system did not boot correctly, see [[Installation Troubleshooting]] for steps you can take to resolve the problem.<br />
<br />
[[Category:HOWTO]]<br />
[[Category:Install]]</div>Oleghttp://www.funtoo.org/wiki/ZFS_Install_GuideZFS Install Guide2013-01-20T18:20:14Z<p>Oleg: </p>
<hr />
<div>This tutorial will show you how to install Funtoo on ZFS (rootfs).<br />
<br />
This tutorial is meant to be an "overlay" over the [[Funtoo_Linux_Installation|Regular Funtoo Installation]]. Follow the normal installation and only use this guide for steps 2, 3, and 8. This guide is a Work in Progress, expect some quirks :)<br />
<br />
{{fancyimportant|'''Since ZFS was really designed for 64 bit systems, we are only recommending and supporting 64 bit platforms and installations. We will not be supporting 32 bit platforms'''!}}<br />
<br />
== Setting up your environment ==<br />
In order for us to install Funtoo on ZFS, you will need an environment that provides the ZFS tools. We will be downloading two things: System Rescue CD, <br /><br />
and the ZFS System Rescue Module (SRM). This is just a file that when combined with System Rescue CD, gives you those tools.<br />
<br />
[https://sourceforge.net/projects/systemrescuecd/files/sysresccd-x86/3.2.0/systemrescuecd-x86-3.2.0.iso/download Download System Rescue CD 3.2.0]<br />
<br />
[http://jonathanvasquez.com/files/sysresccd/ Download the ZFS System Rescue Module]<br />
<br />
<pre><br />
Name: SystemRescueCd-x86-3.2.0 (353 MiB)<br />
Release Date: 2013-01-07<br />
<br />
md5sum 90528f0c4b861363992fd9cbcc52d00a<br />
</pre><br />
<br />
[[Creating_System_Rescue_CD_Modules|Follow the instructions here to download and place the srm into your flash drive]].<br />
<br />
== Creating partitions ==<br />
<br />
There are two ways to partition your disk. You can use your entire drive and let ZFS automatically partition it for you, or you can do it manually. Using your entire disk drive is recommended since ZFS turns on/off a few settings. For one, if you use your whole-disk, ZFS will set the I/O elevator for the drive automatically. On Solaris machines, ZFS also enables the disk's write cache.<br />
<br />
If you partition it manually, you should set your I/O scheduler to no-op so it doesn't conflict with the ZFS scheduler. Partitioning manually also gives you the advantage of putting your /boot outside the ZFS pool so that you can use a bootloader that doesn't support booting from ZFS.<br />
<br />
We will be creating two partitions, /boot, and the remaining disk space will be for ZFS.<br />
<br />
(All commands will be ran as root).<br />
<br />
=== Whole Disk ===<br />
<br />
This is the easiest method and the recommended method. First lets make sure that the disk is completely wiped from any previous disk labels and partitions.<br />
<br />
We will also assume that /dev/sda is the target drive.<br />
<br />
<console><br />
# ##i##gdisk /dev/sda<br />
<br />
Command: ##i##x ↵<br />
Expert command: ##i##z ↵<br />
About to wipe out GPT on /dev/sda. Proceed?: ##i##y ↵<br />
GPT data structures destroyed! You may now partition the disk using fdisk or other utilities.<br />
Blank out MBR?: ##i##y ↵<br />
</console><br />
<br />
{{fancywarning|This is a destructive operation. Make sure you really don't want anything on this disk.}}<br />
<br />
Now that we have a clean drive, we will create the new pool in it while letting zfs automatically partition it.<br />
<br />
Create the pool as normal<br />
<br />
<br />
<console><br />
# ##i##zpool create -f -o ashift=12 -o cachefile= -O compression=on -m none -R /mnt/funtoo rpool /dev/sda<br />
</console><br />
<br />
Doing this will let ZFS create a GPT style disk with two partitions. We will also slightly modify this to add a BIOS Boot Partition so that grub can be installed successfully. <br />
<br />
<br />
First lets export the pool so that the kernel can use the new partition table without rebooting.<br />
<br />
<br />
<console><br />
# ##i##zpool export rpool<br />
</console><br />
<br />
<br />
And now lets create a new BIOS Boot Partition at partition 2 from sectors '''48''' to '''2047''':<br />
<br />
<br />
<console><br />
# ##i##gdisk /dev/sda<br />
<br />
<br />
GPT fdisk (gdisk) version 0.8.5<br />
<br />
<br />
Partition table scan:<br />
MBR: protective<br />
BSD: not present<br />
APM: not present<br />
GPT: present<br />
<br />
<br />
Found valid GPT with protective MBR; using GPT.<br />
<br />
<br />
Command (? for help): ##i##p ↵<br />
Disk /dev/sda: 16777216 sectors, 8.0 GiB<br />
Logical sector size: 512 bytes<br />
Disk identifier (GUID): 09DA0F98-A486-424F-A87D-B3B409381428<br />
Partition table holds up to 128 entries<br />
First usable sector is 34, last usable sector is 16777182<br />
Partitions will be aligned on 2048-sector boundaries<br />
Total free space is 4029 sectors (2.0 MiB)<br />
<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 16758783 8.0 GiB BF01 zfs<br />
9 16758784 16775167 8.0 MiB BF07 <br />
<br />
<br />
Command (? for help): ##i##n ↵<br />
Partition number (2-128, default 2): ##i##↵<br />
First sector (34-16777182, default = 16775168) or {+-}size{KMGTP}: ##i##48 ↵<br />
Last sector (48-2047, default = 2047) or {+-}size{KMGTP}: ##i## ↵<br />
Current type is 'Linux filesystem'<br />
Hex code or GUID (L to show codes, Enter = 8300): ##i##EF02 ↵<br />
Changed type of partition to 'BIOS boot partition'<br />
<br />
<br />
Command (? for help): ##i##w ↵<br />
<br />
<br />
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING<br />
PARTITIONS!!<br />
<br />
<br />
Do you want to proceed? (Y/N): ##i##y<br />
OK; writing new GUID partition table (GPT) to /dev/sda.<br />
The operation has completed successfully.<br />
</console><br />
<br />
If you were to check gdisk /dev/sda again, you would see these 3 partitions:<br />
<br />
<console><br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 16758783 8.0 GiB BF01 zfs<br />
2 48 2047 1000.0 KiB EF02 BIOS boot partition<br />
9 16758784 16775167 8.0 MiB BF07<br />
</console><br />
<br />
Let's import the pool again:<br />
<br />
<console><br />
# ##i##zpool import -f -o cachefile= -R /mnt/funtoo rpool<br />
</console><br />
<br />
[[ZFS_Install_Guide#Create_the_zfs_datasets|Now continue with creating your datasets.]]<br />
<br />
=== Manual partitioning ===<br />
==== fdisk (MBR Style) ====<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M ↵<br />
</console><br />
<br />
'''Create Partition 2''' (ZFS):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
<br />
Command: ##i##t ↵<br />
Partition number: ##i##2 ↵<br />
Hex code (type L to list codes): ##i##bf ↵<br />
<br />
Command: ##i##p ↵<br />
<br />
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes<br />
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors<br />
Units = sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
Disk identifier: 0x3e954df7<br />
<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 2048 514047 256000 83 Linux<br />
/dev/sda2 514048 1953525167 976505560 bf Solaris<br />
<br />
</console><br />
<br />
==== gdisk (GPT Style) ====<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M ↵<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
'''Create Partition 2''' (BIOS Boot Partition):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+32M ↵<br />
Hex Code: ##i##EF02 ↵<br />
</console><br />
<br />
{{fancyimportant|Only make the above BIOS Boot Partition if you are using GRUB 2 on GPT. If you are using the extlinux bootloader, this partition is not necessary. The below instructions continue as if you did not create this partition and assumes you are using extlinux as the bootloader.}}<br />
<br />
'''Create Partition 2''' (ZFS):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
Hex Code: ##i##bf01 ↵<br />
<br />
Command: ##i##p ↵<br />
Disk /dev/sda: 1953525168 sectors, 931.5 GiB<br />
Logical sector size: 512 bytes<br />
Disk identifier (GUID): C0C1E56A-B24F-492F-95DB-2E227676F228<br />
Partition table holds up to 128 entries<br />
First usable sector is 34, last usable sector is 1953525134<br />
Partitions will be aligned on 2048-sector boundaries<br />
Total free space is 2014 sectors (1007.0 KiB)<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 514047 250.0 MiB 8300 Linux filesystem<br />
2 514048 1953525134 931.3 GiB BF01 Solaris /usr & Mac ZFS<br />
<br />
Command: ##i##w ↵<br />
</console><br />
<br />
=== Format your boot volume ===<br />
<br />
<console><br />
# ##i##mkfs.ext4 /dev/sda1<br />
</console><br />
<br />
=== Create the zpool ===<br />
We will first create the pool. The pool will be named `rpool` and the disk will be aligned to 4096 (using ashift=12)<br />
<br />
<console><br />
# ##i##zpool create -f -o ashift=12 -o cachefile= -O compression=on -m none -R /mnt/funtoo rpool /dev/sda2<br />
</console><br />
<br />
{{fancyimportant|If you followed the GPT partitioning instructions, you should change /dev/sda2 to /dev/sda3.}}<br />
<br />
{{fancynote|If you have a previous pool that you would like to import, you can do a: '''zpool import -R /mnt/funtoo -f <pool_name>'''}}<br />
<br />
=== Create the zfs datasets ===<br />
We will now create some datasets. For this installation, we will create a small but future proof amount of datasets. We will have a dataset for the OS (/), and your swap. We will also show you how to create some optional datasets: /home, /var, /usr/src, and /usr/portage.<br />
<br />
<console><br />
Create some empty containers for organization purposes, and make the dataset that will hold /<br />
# ##i##zfs create -o mountpoint=none rpool/ROOT<br />
# ##i##zfs create -o mountpoint=/ rpool/ROOT/funtoo<br />
<br />
Optional, but recommended datasets: /home, /root <br />
# ##i##zfs create -o mountpoint=/home rpool/HOME<br />
# ##i##zfs create -o mountpoint=/root rpool/HOME/root<br />
<br />
Optional datasets: /usr/src, /var<br />
# ##i##zfs create -o mountpoint=none rpool/FUNTOO<br />
# ##i##zfs create -o mountpoint=/usr/src rpool/FUNTOO/src<br />
# ##i##zfs create -o mountpoint=/var rpool/FUNTOO/var<br />
</console><br />
<br />
==== Creating a separate portage dataset (optional) ====<br />
<br />
Creating a separate portage dataset could be useful if you would like to keep your portage tree, distfiles (source code files), and packages (your compiled binaries if you have FEATURES="buildpkg" enabled) in a safe place (or if you want to back up this directory up easily).<br />
<br />
This requires a few extra steps because we can't just do a regular emerge --sync when we initially chroot. We will need to download a portage snapshot tarball and extract it into the directory.<br />
<br />
The required steps for getting and extracting the snapshot will be shown later on in the guide once you chroot into the environment. For now just create the datasets:<br />
<br />
<console><br />
# ##i##zfs create -o mountpoint=/usr/portage -o compression=off rpool/FUNTOO/portage<br />
# ##i##zfs create -o mountpoint=/usr/portage/distfiles -o compression=off rpool/FUNTOO/distfiles<br />
</console><br />
<br />
=== Create your swap zvol ===<br />
<br />
'''Make your swap +1G greater than your RAM. An 8G machine would have 9G of RAM (This is kinda big though).'''<br />
Be warned - zfs is memory hungry. Specially when used with compression=on. A machine with just 4GB can come in troubles while compiling big packages and/or a graphical desktop running. You definitly should have swap running.<br />
<br />
<console><br />
# ##i##zfs create -o sync=always -o primarycache=metadata -o secondarycache=none -V 9G rpool/swap<br />
</console><br />
<br />
=== Format your swap zvol ===<br />
<br />
<console><br />
# ##i##mkswap -f /dev/zvol/rpool/swap<br />
# ##i##swapon /dev/zvol/rpool/swap<br />
</console><br />
<br />
Alright that finishes the creation of the zpool and zfs datasets. <br />
<br />
Check to make sure everything appears fine:<br />
<br />
<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
Copy the zpool.cache file to your new environment.<br />
<br />
<console><br />
# ##i##mkdir -p /mnt/funtoo/etc/zfs<br />
# ##i##cp /etc/zfs/zpool.cache /mnt/funtoo/etc/zfs<br />
</console><br />
<br />
Make an empty mtab file<br />
<br />
<console><br />
# ##i##touch /mnt/funtoo/etc/mtab<br />
</console><br />
<br />
Now we will continue to install funtoo.<br />
<br />
== Installing Funtoo ==<br />
<br />
[[Funtoo_Linux_Installation|Download and install the Funtoo stage3 and continue installation as normal.]]<br />
<br />
Then chroot into your new funtoo environment:<br />
<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
<br />
Mount your boot drive ** You don't need to do this if you're using whole-disk zfs **<br />
# ##i##mount /dev/sda1 /mnt/funtoo/boot<br />
<br />
Bind the kernel related directories<br />
# ##i##mount --bind /proc ./proc<br />
# ##i##mount --bind /dev ./dev<br />
# ##i##mount --bind /sys ./sys<br />
<br />
Copy network settings<br />
# ##i##cp /etc/resolv.conf etc/<br />
<br />
chroot into your new funtoo environment<br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l<br />
</console><br />
<br />
=== Syncing your portage tree ===<br />
<br />
==== If you didn't create a separate portage dataset, then just sync your portage tree as normal. ====<br />
<br />
<console><br />
# ##i##emerge --sync<br />
</console><br />
<br />
==== If you did create a separate portage dataset, let's now get the portage snapshot set up. ====<br />
<br />
<console><br />
Change into your /usr directory<br />
# ##i##cd /usr<br />
<br />
Download and extract the portage snapshot<br />
# ##i##wget http://ftp.osuosl.org/pub/funtoo/funtoo-current/snapshots/portage-latest.tar.xz<br />
# ##i##tar xf portage-latest.tar.xz<br />
<br />
Change into your portage directory and checkout the funtoo branch<br />
# ##i##cd portage<br />
# ##i##git checkout funtoo.org<br />
<br />
Now sync your portage tree<br />
# ##i##emerge --sync<br />
</console><br />
<br />
== Kernel Configuration ==<br />
<br />
{{fancynote|The below configurations are the requirements for "Bliss Initramfs Creator". Some of these might not be needed for genkernel.}}<br />
<br />
Tested with kernel 2.6.32, 3.2.34, 3.6.9, 3.7.[1-3].<br />
<br />
When you get up to the kernel, make sure that you disable the CFQ scheduler, and turn<br />
on No-op (It's the default one once you disable all schedulers). The reason for this is because ZFS has its<br />
own scheduler and the CFQ one conflicts with it.<br />
<br />
Go to your kernel config, and make sure you have the following: (there should be a /usr/src/linux symlink as well)<br />
<br />
<pre>ZLIB_INFLATE/DEFLATE must be compiled into the kernel (not as a module).<br />
> ZLIB_INFLATE [=y], ZLIB_DEFLATE [=y]<br />
<br />
General setup ---><br />
> [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support<br />
> () Initramfs source file(s)<br />
<br />
[*] Enable loadable module support ---><br />
[*] Module unloading<br />
<br />
Enable the block layer ---><br />
IO Schedulers ---><br />
< > Deadline I/O scheduler<br />
< > CFQ I/O scheduler<br />
Default I/O scheduler (No-op)<br />
<br />
Device Drivers ---><br />
> Generic Driver Options ---><br />
>> [*] Maintain a devtmpfs filesystem to mount at /dev<br />
>> [*] Automount devtmpfs at /dev, after the kernel mounted the rootfs<br />
<br />
Cryptographic API ---><br />
<*> Deflate compression algorithm<br />
<*> Zlib compression algorithm<br />
<br />
* All other drivers required to see your PATA/SATA drives must be compiled in.<br />
</pre><br />
<br />
Continue and compile/install your kernel:<br />
<br />
<console><br />
# ##i##make bzImage modules<br />
# ##i##make install<br />
# ##i##make modules_install<br />
</console><br />
<br />
== Installing the ZFS userspace tools ==<br />
<br />
<console><br />
# ##i##emerge -av zfs<br />
</console><br />
<br />
Check to make sure that the zfs tools are working, the zpool.cache file that you copied before should be displayed.<br />
<br />
<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
If everything worked, continue.<br />
<br />
== Create the initramfs ==<br />
<br />
There are two ways to do this, you can use genkernel, or you can use my bliss initramfs creator. I will<br />
show you both.<br />
<br />
<br />
=== genkernel ===<br />
<br />
<console><br />
# ##i##emerge -av sys-kernel/genkernel<br />
# ##i##genkernel --zfs initramfs<br />
</console><br />
<br />
<br />
<pre><br />
Example: <br />
kernel name is: vmlinuz-3.7.3-ALL<br />
initramfs name is: initramfs-genkernel-x86_64-3.7.3-ALL<br />
pool name is: rpool<br />
</pre><br />
<br />
<br />
grub.cfg:<br />
<br />
<console><br />
set timeout=3<br />
set default=0<br />
<br />
<br />
# Funtoo<br />
menuentry "Funtoo - 3.7.3" {<br />
insmod zfs<br />
<br />
<br />
linux /ROOT/funtoo/@/boot/vmlinuz-3.7.3-ALL root=rpool/ROOT/funtoo real_root=ZFS=rpool/ROOt/funtoo dozfs=force<br />
initrd /ROOT/funtoo/@/boot/initramfs-genkernel-x86_64-3.7.3-ALL<br />
}<br />
</console><br />
<br />
extlinux.conf:<br />
<br />
<console><br />
LABEL funtoo<br />
MENU LABEL Funtoo 3.7.3-ALL<br />
KERNEL /boot/vmlinuz-3.7.3-ALL<br />
INITRD /boot/initramfs-genkernel-x86_64-3.7.3-ALL<br />
APPEND real_root=ZFS=rpool/ROOT/funtoo dozfs=force<br />
</console><br />
<br />
=== Bliss Initramfs Creator ===<br />
<br />
Clone my creator which is located at: git://github.com/fearedbliss/Bliss-Initramfs-Creator.git<br />
<br />
<console><br />
# ##i##git clone git://github.com/fearedbliss/Bliss-Initramfs-Creator.git<br />
</console><br />
<br />
Then go into this new directory, run the script as root, and place it into /boot<br />
<br />
<console><br />
# ##i##cd Bliss-Initramfs-Creator<br />
# ##i##./createInit<br />
# ##i##mv initrd-<kernel_name>.img /boot<br />
</console><br />
<br />
'''<kernel_name>''' is the name of what you selected in the initramfs creator, and the name of the outputted file.<br />
<br />
Once you do this just go to your bootloader config, and add it in there.<br />
<br />
<br />
<pre><br />
Example:<br />
<br />
Kernel name is: vmlinuz-3.7.3-ALL<br />
initramfs name is: initrd-3.7.3-ALL.img<br />
Pool root is: rpool/ROOT/funtoo<br />
</pre><br />
<br />
grub.cfg:<br />
<br />
<console><br />
set timeout=3<br />
set default=0<br />
<br />
<br />
# Funtoo<br />
menuentry "Funtoo - 3.7.3" {<br />
insmod zfs<br />
<br />
<br />
linux /ROOT/funtoo/@/boot/vmlinuz-3.7.3-ALL root=rpool/ROOT/funtoo quiet<br />
initrd /ROOT/funtoo/@/boot/initrd-3.7.3-ALL.img<br />
}</console><br />
<br />
extlinux.conf:<br />
<br />
<console><br />
LABEL funtoo<br />
MENU LABEL Funtoo 3.7.1-ALL<br />
KERNEL /boot/vmlinuz-3.7.1-ALL<br />
INITRD /boot/initrd-3.7.1-ALL.img<br />
APPEND pool_root=rpool/ROOT/funtoo<br />
</console><br />
<br />
== Final configuration ==<br />
<br />
=== Add the zfs tools to openrc ===<br />
<br />
<console><br />
# ##i##rc-update add zfs boot<br />
</console><br />
<br />
=== Add filesystems to /etc/fstab ===<br />
<br />
<console><br />
# ##i##nano /etc/fstab<br />
<br />
# <fs> <mountpoint> <type> <opts> <dump/pass><br />
<br />
# Do not add the /boot line below if you are using whole-disk zfs<br />
/dev/sda1 /boot ext4 defaults 1 2<br />
/dev/zvol/rpool/swap none swap sw 0 0<br />
</console><br />
<br />
=== Clean up and reboot ===<br />
We are almost done, we are just going to clean up, '''set our root password''', and unmount whatever we mounted and get out.<br />
<br />
<console><br />
Delete the stage3/portage tarballs you downloaded earlier so they don't take up space.<br />
# ##i##cd /<br />
# ##i##rm stage3-latest.tar.xz<br />
# ##i##rm /usr/portage-latest.tar.xz<br />
<br />
Set your root password<br />
# ##i##passwd<br />
>> Enter your password, you won't see what you are writing (for security reasons), but it is there!<br />
<br />
Get out of the chroot environment<br />
# ##i##exit<br />
<br />
Unmount all the kernel filesystem stuff and boot<br />
# ##i##cd /mnt/funtoo<br />
# ##i##umount proc dev sys boot<br />
<br />
Turn off the swap<br />
# ##i##swapoff /dev/zvol/rpool/swap<br />
<br />
Export the zpool<br />
# ##i##cd /<br />
# ##i##zpool export -f rpool<br />
<br />
Reboot<br />
# ##i##reboot<br />
</console><br />
<br />
{{fancyimportant|'''Don't forget to set your root password as stated above before exiting chroot and rebooting. If you don't set the root password, you won't be able to log into your new system.'''}}<br />
and that should be enough to get your system to boot on ZFS.<br />
<br />
== Extra: After reboot ==<br />
<br />
After you restart your machine and your inside your desktop, continue to set up anything you need in terms of /etc configurations. Once you have everything the way you like it, take a snapshot of your system. You will be using this snapshot to revert back to this state if anything ever happens to your system down the road. The snapshots are cheap, and almost instant. To take the snapshot of your rootfs, type the following:<br />
<br />
<console><br />
# ##i##zfs snapshot rpool/ROOT/funtoo@install<br />
</console><br />
<br />
To see if your snapshot was taken, type:<br />
<br />
<console><br />
# ##i##zfs list -t snapshot<br />
</console><br />
<br />
If your machine ever fails and you need to get back to this state, just type:<br />
<br />
<console><br />
# ##i##zfs rollback rpool/ROOT/funtoo@install<br />
</console><br />
<br />
=== Recovery Environment ===<br />
On ZFS it is extremely easy to create a recovery environment using an already working snapshot. So that's what we will be doing. <br />
<br />
Create a clone of the @install snapshot which you will use for recovery purposes. If something happens to your main install, you can boot into this clone and fix the main one. One of the differences (maybe the only difference) between a clone and a snapshot is that a clone is rewritable while a snapshot is only read-only.<br />
<br />
<console><br />
# ##i##zfs clone rpool/ROOT/funtoo@install rpool/ROOT/recovery<br />
</console><br />
<br />
==== Add the clone to your extlinux.conf ====<br />
<br />
<console><br />
LABEL funtoo-recovery<br />
MENU LABEL Funtoo Recovery<br />
KERNEL /boot/vmlinuz-3.7.1-ALL<br />
INITRD /boot/initrd-3.7.1-ALL.img<br />
APPEND pool_root=rpool/ROOT/recovery<br />
</console><br />
<br />
==== Things to watch out for ====<br />
<br />
Since your recovery clone will tend to get old as you use your main system, and since <br />
your recovery and other stuff are on the same pool, we don't want the new pool stuff<br />
to be mounted when we launch recovery. We also don't want video drivers to be<br />
conflicting.<br />
<br />
1. Make sure that nvidia/nouveau stuff are blacklisted.<br />
2. Make sure that your /boot and /lib/modules for the kernel in your 'recovery' are<br />
matching.<br />
3. Disable the zfs openrc script so that nothing else gets automatically mounted.<br />
Only your rootfs.<br />
<br />
You can do the above stuff by mounting your copy and chrooting into it.<br />
<br />
<console><br />
Mount the recovery clone<br />
# ##i##mkdir /mnt/recovery<br />
# ##i##mount -t zfs -o zfsutil rpool/ROOT/recovery /mnt/recovery<br />
# ##i##cd /mnt/recovery<br />
<br />
Mount the kernel devices<br />
# ##i##mount --bind /proc ./proc<br />
# ##i##mount --bind /dev ./dev<br />
# ##i##mount --bind /sys ./sys<br />
<br />
Copy zpool.cache<br />
# ##i##cp /etc/zfs/zpool.cache etc/zfs<br />
<br />
Chroot into the new environment<br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash --login<br />
<br />
Disable zfs/zfs-shutdown openrc scripts<br />
# ##i##rc-config delete zfs boot<br />
<br />
Blacklist nouveau/nvidia drivers<br />
# ##i##echo "blacklist nouveau" >> /etc/modprobe.d/blacklist.conf<br />
# ##i##echo "blacklist nvidia" >> /etc/modprobe.d/blacklist.conf<br />
</console><br />
<br />
==== Getting into the recovery ====<br />
Just start your machine and pick the '''Funtoo Recovery''' option from the Boot Menu.<br />
<br />
Enjoy your new install on ZFS :)<br />
<br />
[[Category:HOWTO]]<br />
[[Category:Filesystems]]<br />
<br />
[[Category:Featured]]</div>Oleghttp://www.funtoo.org/wiki/ZFS_Install_GuideZFS Install Guide2013-01-06T15:57:26Z<p>Oleg: /* Things to watch out for */</p>
<hr />
<div>This tutorial will show you how to install Funtoo on ZFS (rootfs).<br />
<br />
This tutorial is meant to be an "overlay" over the [[Funtoo_Linux_Installation|Regular Funtoo Installation]]. Follow the normal installation and only use this guide for steps 2, 3, and 8.<br />
<br />
{{fancyimportant|'''Since ZFS was really designed for 64 bit systems, we are only recommending and supporting 64 bit platforms and installations. We will not be supporting 32 bit platforms'''!}}<br />
<br />
== Setting up your environment ==<br />
In order for us to install Funtoo on ZFS, you will need an environment that provides the ZFS userspace tools. We will be downloading two things, System Rescue CD 3.1.2, and the ZFS SRM (System Rescue Module). This is just a file that when combined with System Rescue CD, gives you ZFS functionality.<br />
<br />
[https://sourceforge.net/projects/systemrescuecd/files/sysresccd-x86/3.1.2/systemrescuecd-x86-3.1.2.iso/download Download System Rescue CD 3.1.2]<br />
<br />
[http://jonathanvasquez.com/files/sysresccd/ Download the ZFS System Rescue Module]<br />
<br />
<pre><br />
Name: SystemRescueCd-x86-3.1.2 (350 MiB)<br />
Release Date: 2012-12-05<br />
<br />
md5sum 3c1ddfe5f26bb2f979a2ed9dfb504ee3<br />
sha1sum 217cf7a81380d894b2433c59451787c16bc0af2f<br />
sha256sum ec0a995875e64ff9816a043737e5cbbb689b7f596b48679116f0a779f3dce673<br />
</pre><br />
<br />
Once you place the ISO on your USB flash drive, extract the modules from the tarball, and place the .srm and .md5 at the root of your USB filesystem. Further instructions can be found [[Creating_System_Rescue_CD_Modules#Using_the_prebuilt_srm|here]]. <br />
<br />
We will now start to partition the system. Open up a terminal, and type in the following (We will assume it's a fresh drive for simplicity).<br />
<br />
== Creating partitions ==<br />
<br />
We will be creating two partitions, /boot, and the remaining disk space will be for ZFS.<br />
<br />
(All commands will be ran as root).<br />
<br />
=== fdisk (MBR Style) ===<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M ↵<br />
</console><br />
<br />
'''Create Partition 2''' (ZFS):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
<br />
Command: ##i##t ↵<br />
Partition number: ##i##2 ↵<br />
Hex code (type L to list codes): ##i##bf ↵<br />
<br />
Command: ##i##p ↵<br />
<br />
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes<br />
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors<br />
Units = sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
Disk identifier: 0x3e954df7<br />
<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 2048 514047 256000 83 Linux<br />
/dev/sda2 514048 1953525167 976505560 bf Solaris<br />
<br />
</console><br />
<br />
=== gdisk (GPT Style) ===<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M ↵<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
'''Create Partition 2''' (BIOS Boot Partition):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+32M ↵<br />
Hex Code: ##i##EF02 ↵<br />
</console><br />
<br />
{{fancyimportant|Only make the above BIOS Boot Partition if you are using GRUB 2 on GPT. If you are using the extlinux bootloader, this partition is not necessary. The below instructions continue as if you did not create this partition and assumes you are using extlinux as the bootloader.}}<br />
<br />
'''Create Partition 2''' (ZFS):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
Hex Code: ##i##bf01 ↵<br />
<br />
Command: ##i##p ↵<br />
Disk /dev/sda: 1953525168 sectors, 931.5 GiB<br />
Logical sector size: 512 bytes<br />
Disk identifier (GUID): C0C1E56A-B24F-492F-95DB-2E227676F228<br />
Partition table holds up to 128 entries<br />
First usable sector is 34, last usable sector is 1953525134<br />
Partitions will be aligned on 2048-sector boundaries<br />
Total free space is 2014 sectors (1007.0 KiB)<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 514047 250.0 MiB 8300 Linux filesystem<br />
2 514048 1953525134 931.3 GiB BF01 Solaris /usr & Mac ZFS<br />
<br />
</console><br />
<br />
=== Format your boot volume ===<br />
<br />
<console><br />
# ##i##mkfs.ext4 /dev/sda1<br />
</console><br />
<br />
=== Create the zpool ===<br />
We will first create the pool. The pool will be named `rpool` and the disk will be aligned to 4096 (using ashift=12)<br />
<br />
<console><br />
# ##i##zpool create -f -o ashift=12 -o cachefile= -O compression=on -m none -R /mnt/funtoo rpool /dev/sda2<br />
</console><br />
<br />
{{fancyimportant|If you followed the GPT partitioning instructions, you should change /dev/sda2 to /dev/sda3.}}<br />
<br />
{{fancynote|If you have a previous pool that you would like to import, you can do a: '''zpool import -R /mnt/funtoo <pool_name>'''}}<br />
<br />
=== Create the zfs datasets ===<br />
We will now create some datasets. For this installation, we will create a small but future proof amount of datasets. We will have a dataset for the OS (/), and your swap. We will also show you how to create some optional datasets: /home, /var, /usr/src, and /usr/portage.<br />
<br />
<console><br />
Create some empty containers for organization purposes, and make the dataset that will hold /<br />
# ##i##zfs create -o mountpoint=none rpool/ROOT<br />
# ##i##zfs create -o mountpoint=/ rpool/ROOT/funtoo<br />
<br />
Optional, but recommended datasets: /home, /root <br />
# ##i##zfs create -o mountpoint=/home rpool/HOME<br />
# ##i##zfs create -o mountpoint=/root rpool/HOME/root<br />
<br />
Optional datasets: /usr/src, /var<br />
# ##i##zfs create -o mountpoint=none rpool/FUNTOO<br />
# ##i##zfs create -o mountpoint=/usr/src rpool/FUNTOO/src<br />
# ##i##zfs create -o mountpoint=/var rpool/FUNTOO/var<br />
</console><br />
<br />
==== Creating a separate portage dataset (optional) ====<br />
<br />
Creating a separate portage dataset could be useful if you would like to keep your portage tree, distfiles (source code files), and packages (your compiled binaries if you have FEATURES="buildpkg" enabled) in a safe place (or if you want to back up this directory up easily).<br />
<br />
This requires a few extra steps because we can't just do a regular emerge --sync when we initially chroot. We will need to download a portage snapshot tarball and extract it into the directory.<br />
<br />
The required steps for getting and extracting the snapshot will be shown later on in the guide once you chroot into the environment. For now just create the datasets:<br />
<br />
<console><br />
# ##i##zfs create -o mountpoint=/usr/portage -o compression=off rpool/FUNTOO/portage<br />
# ##i##zfs create -o mountpoint=/usr/portage/distfiles -o compression=off rpool/FUNTOO/distfiles<br />
</console><br />
<br />
=== Create your swap zvol ===<br />
<br />
'''Make your swap +1G greater than your RAM. An 8G machine would have 9G of RAM (This is kinda big though).'''<br />
<br />
<console><br />
# ##i##zfs create -o sync=always -o primarycache=metadata -o secondarycache=none -V 9G rpool/swap<br />
</console><br />
<br />
=== Format your swap zvol ===<br />
<br />
<console><br />
# ##i##mkswap -f /dev/zvol/rpool/swap<br />
# ##i##swapon /dev/zvol/rpool/swap<br />
</console><br />
<br />
Alright that finishes the creation of the zpool and zfs datasets. <br />
<br />
Check to make sure everything appears fine:<br />
<br />
<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
Copy the zpool.cache file to your new environment.<br />
<br />
<console><br />
# ##i##mkdir -p /mnt/funtoo/etc/zfs<br />
# ##i##cp /etc/zfs/zpool.cache /mnt/funtoo/etc/zfs<br />
</console><br />
<br />
Make an empty mtab file<br />
<br />
<console><br />
# ##i##touch /mnt/funtoo/etc/mtab<br />
</console><br />
<br />
Now we will continue to install funtoo.<br />
<br />
== Installing Funtoo ==<br />
<br />
[[Funtoo_Linux_Installation|Download and install the Funtoo stage3 and continue installation as normal.]]<br />
<br />
Then chroot into your new funtoo environment:<br />
<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
<br />
Mount your boot drive<br />
# ##i##mount /dev/sda1 /mnt/funtoo/boot<br />
<br />
Bind the kernel related directories<br />
# ##i##mount --bind /proc ./proc<br />
# ##i##mount --bind /dev ./dev<br />
# ##i##mount --bind /sys ./sys<br />
<br />
Copy network settings<br />
# ##i##cp /etc/resolv.conf etc/<br />
<br />
chroot into your new funtoo environment<br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l<br />
</console><br />
<br />
=== Syncing your portage tree ===<br />
<br />
==== If you didn't create a separate portage dataset, then just sync your portage tree as normal. ====<br />
<br />
<console><br />
# ##i##emerge --sync<br />
</console><br />
<br />
==== If you did create a separate portage dataset, let's now get the portage snapshot set up. ====<br />
<br />
<console><br />
Change into your /usr directory<br />
# ##i##cd /usr<br />
<br />
Download and extract the portage snapshot<br />
# ##i##wget http://ftp.osuosl.org/pub/funtoo/funtoo-current/snapshots/portage-latest.tar.xz<br />
# ##i##tar xf portage-latest.tar.xz<br />
<br />
Change into your portage directory and checkout the funtoo branch<br />
# ##i##cd portage<br />
# ##i##git checkout funtoo.org<br />
<br />
Now sync your portage tree<br />
# ##i##emerge --sync<br />
</console><br />
<br />
== Kernel Configuration ==<br />
<br />
Tested with kernel 2.6.32, 3.2.34, 3.6.9, 3.7.1.<br />
<br />
When you get up to the kernel, make sure that you disable the CFQ scheduler, and turn<br />
on No-op (It's the default one once you disable all schedulers). The reason for this is because ZFS has its<br />
own scheduler and the CFQ one conflicts with it.<br />
<br />
Go to your kernel config, and make sure you have the following: (there should be a /usr/src/linux symlink as well)<br />
<br />
<pre>ZLIB_INFLATE/DEFLATE must be compiled into the kernel (not as a module).<br />
> ZLIB_INFLATE [=y], ZLIB_DEFLATE [=y]<br />
<br />
General setup ---><br />
> [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support<br />
> () Initramfs source file(s)<br />
<br />
[*] Enable loadable module support ---><br />
[*] Module unloading<br />
<br />
Enable the block layer ---><br />
IO Schedulers ---><br />
< > Deadline I/O scheduler<br />
< > CFQ I/O scheduler<br />
Default I/O scheduler (No-op)<br />
<br />
Device Drivers ---><br />
> Generic Driver Options ---><br />
>> [*] Maintain a devtmpfs filesystem to mount at /dev<br />
>> [*] Automount devtmpfs at /dev, after the kernel mounted the rootfs<br />
<br />
* All other drivers required to see your PATA/SATA drives must be compiled in.<br />
</pre><br />
<br />
Continue and compile/install your kernel:<br />
<br />
<console><br />
# ##i##make bzImage modules<br />
# ##i##make install<br />
# ##i##make modules_install<br />
</console><br />
<br />
== Installing the ZFS userspace tools ==<br />
<br />
<console><br />
# ##i##emerge -av zfs<br />
</console><br />
<br />
Check to make sure that the zfs tools are working, the zpool.cache file that you copied before should be displayed.<br />
<br />
<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
If everything worked, continue.<br />
<br />
== Create the initramfs ==<br />
<br />
There are two ways to do this, you can use genkernel, or you can use my bliss initramfs creator. I will<br />
show you both.<br />
<br />
=== Bliss Initramfs Creator ===<br />
<br />
Make sure you compile sys-apps/busybox with the static flag.<br />
<br />
<console><br />
# ##i##echo "sys-apps/busybox static" >> /etc/portage/package.use<br />
# ##i##emerge -av sys-apps/busybox<br />
</console><br />
<br />
Clone my creator which is located at: git://github.com/fearedbliss/Bliss-Initramfs-Creator.git<br />
<br />
<console><br />
# ##i##git clone git://github.com/fearedbliss/Bliss-Initramfs-Creator.git<br />
</console><br />
<br />
Then go into this new directory, run the script as root, and place it into /boot<br />
<br />
<console><br />
# ##i##cd Bliss-Initramfs-Creator<br />
# ##i##./createInit<br />
# ##i##mv initrd-<kernel_name>.img /boot<br />
</console><br />
<br />
'''<kernel_name>''' is the name of what you selected in the initramfs creator, and the name of the outputted file.<br />
<br />
Once you do this just go to your bootloader config, and add it in there.<br />
<br />
<pre><br />
Example:<br />
<br />
Kernel name is: vmlinuz-3.7.1-ALL<br />
initramfs name is: initrd-3.7.1-ALL.img<br />
Pool root is: rpool/ROOT/funtoo<br />
</pre><br />
<br />
extlinux.conf:<br />
<br />
<console><br />
LABEL funtoo<br />
MENU LABEL Funtoo 3.7.1-ALL<br />
KERNEL /boot/vmlinuz-3.7.1-ALL<br />
INITRD /boot/initrd-3.7.1-ALL.img<br />
APPEND pool_root=rpool/ROOT/funtoo<br />
</console><br />
<br />
=== genkernel ===<br />
<br />
<console><br />
# ##i##emerge -av sys-kernel/genkernel<br />
# ##i##genkernel --zfs initramfs<br />
</console><br />
<br />
Example: <br />
kernel name is: vmlinuz-3.7.1-ALL<br />
initramfs name is: initramfs-genkernel-x86_64-3.7.1-ALL<br />
pool name is: rpool<br />
<br />
extlinux.conf:<br />
<br />
<console><br />
LABEL funtoo<br />
MENU LABEL Funtoo 3.7.1-ALL<br />
KERNEL /boot/vmlinuz-3.7.1-ALL<br />
INITRD /boot/initramfs-genkernel-x86_64-3.7.1-ALL<br />
APPEND real_root=ZFS=rpool/ROOT/funtoo dozfs=force<br />
</console><br />
<br />
== Final configuration ==<br />
<br />
=== Add the zfs tools to openrc ===<br />
<br />
<console><br />
# ##i##rc-update add zfs boot<br />
</console><br />
<br />
=== Add filesystems to /etc/fstab ===<br />
<br />
<console><br />
# ##i##nano /etc/fstab<br />
<br />
# <fs> <mountpoint> <type> <opts> <dump/pass><br />
<br />
/dev/sda1 /boot ext4 defaults 1 2<br />
/dev/zvol/rpool/swap none swap sw 0 0<br />
</console><br />
<br />
=== Clean up and reboot ===<br />
We are almost done, we are just going to clean up, '''set our root password''', and unmount whatever we mounted and get out.<br />
<br />
<console><br />
Delete the stage3/portage tarballs you downloaded earlier so they don't take up space.<br />
# ##i##cd /<br />
# ##i##rm stage3-latest.tar.xz<br />
# ##i##rm /usr/portage-latest.tar.xz<br />
<br />
Set your root password<br />
# ##i##passwd<br />
>> Enter your password, you won't see what you are writing (for security reasons), but it is there!<br />
<br />
Get out of the chroot environment<br />
# ##i##exit<br />
<br />
Unmount all the kernel filesystem stuff and boot<br />
# ##i##cd /mnt/funtoo<br />
# ##i##umount proc dev sys boot<br />
<br />
Turn off the swap<br />
# ##i##swapoff /dev/zvol/rpool/swap<br />
<br />
Export the zpool<br />
# ##i##cd /<br />
# ##i##zpool export -f rpool<br />
<br />
Reboot<br />
# ##i##reboot<br />
</console><br />
<br />
{{fancyimportant|'''Don't forget to set your root password as stated above before exiting chroot and rebooting. If you don't set the root password, you won't be able to log into your new system.'''}}<br />
and that should be enough to get your system to boot on ZFS.<br />
<br />
== Extra: After reboot ==<br />
<br />
After you restart your machine and your inside your desktop, continue to set up anything you need in terms of /etc configurations. Once you have everything the way you like it, take a snapshot of your system. You will be using this snapshot to revert back to this state if anything ever happens to your system down the road. The snapshots are cheap, and almost instant. To take the snapshot of your rootfs, type the following:<br />
<br />
<console><br />
# ##i##zfs snapshot rpool/ROOT/funtoo@install<br />
</console><br />
<br />
To see if your snapshot was taken, type:<br />
<br />
<console><br />
# ##i##zfs list -t snapshot<br />
</console><br />
<br />
If your machine ever fails and you need to get back to this state, just type:<br />
<br />
<console><br />
# ##i##zfs rollback rpool/ROOT/funtoo@install<br />
</console><br />
<br />
=== Recovery Environment ===<br />
On ZFS it is extremely easy to create a recovery environment using an already working snapshot. So that's what we will be doing. <br />
<br />
Create a clone of the @install snapshot which you will use for recovery purposes. If something happens to your main install, you can boot into this clone and fix the main one. One of the differences (maybe the only difference) between a clone and a snapshot is that a clone is rewritable while a snapshot is only read-only.<br />
<br />
<console><br />
# ##i##zfs clone rpool/ROOT/funtoo@install rpool/ROOT/recovery<br />
</console><br />
<br />
==== Add the clone to your extlinux.conf ====<br />
<br />
<console><br />
LABEL funtoo-recovery<br />
MENU LABEL Funtoo Recovery<br />
KERNEL /boot/vmlinuz-3.7.1-ALL<br />
INITRD /boot/initrd-3.7.1-ALL.img<br />
APPEND pool_root=rpool/ROOT/recovery<br />
</console><br />
<br />
==== Things to watch out for ====<br />
<br />
Since your recovery clone will tend to get old as you use your main system, and since <br />
your recovery and other stuff are on the same pool, we don't want the new pool stuff<br />
to be mounted when we launch recovery. We also don't want video drivers to be<br />
conflicting.<br />
<br />
1. Make sure that nvidia/nouveau stuff are blacklisted.<br />
2. Make sure that your /boot and /lib/modules for the kernel in your 'recovery' are<br />
matching.<br />
3. Disable the zfs openrc script so that nothing else gets automatically mounted.<br />
Only your rootfs.<br />
<br />
You can do the above stuff by mounting your copy and chrooting into it.<br />
<br />
<console><br />
Mount the recovery clone<br />
# ##i##mkdir /mnt/recovery<br />
# ##i##mount -t zfs -o zfsutil rpool/ROOT/recovery /mnt/recovery<br />
# ##i##cd /mnt/recovery<br />
<br />
Mount the kernel devices<br />
# ##i##mount --bind /proc ./proc<br />
# ##i##mount --bind /dev ./dev<br />
# ##i##mount --bind /sys ./sys<br />
<br />
Copy zpool.cache<br />
# ##i##cp /etc/zfs/zpool.cache etc/zfs<br />
<br />
Chroot into the new environment<br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash --login<br />
<br />
Disable zfs/zfs-shutdown openrc scripts<br />
# ##i##rc-config delete zfs boot<br />
<br />
Blacklist nouveau/nvidia drivers<br />
# ##i##echo "blacklist nouveau" >> /etc/modprobe.d/blacklist.conf<br />
# ##i##echo "blacklist nvidia" >> /etc/modprobe.d/blacklist.conf<br />
</console><br />
<br />
==== Getting into the recovery ====<br />
Just start your machine and pick the '''Funtoo Recovery''' option from the Boot Menu.<br />
<br />
Enjoy your new install on ZFS :)<br />
[[Category:HOWTO]]<br />
[[Category:Filesystems]]</div>Oleghttp://www.funtoo.org/wiki/ZFS_Install_GuideZFS Install Guide2013-01-06T15:56:08Z<p>Oleg: shutdown is not working properly and shouldn't be used (by Ryao)</p>
<hr />
<div>This tutorial will show you how to install Funtoo on ZFS (rootfs).<br />
<br />
This tutorial is meant to be an "overlay" over the [[Funtoo_Linux_Installation|Regular Funtoo Installation]]. Follow the normal installation and only use this guide for steps 2, 3, and 8.<br />
<br />
{{fancyimportant|'''Since ZFS was really designed for 64 bit systems, we are only recommending and supporting 64 bit platforms and installations. We will not be supporting 32 bit platforms'''!}}<br />
<br />
== Setting up your environment ==<br />
In order for us to install Funtoo on ZFS, you will need an environment that provides the ZFS userspace tools. We will be downloading two things, System Rescue CD 3.1.2, and the ZFS SRM (System Rescue Module). This is just a file that when combined with System Rescue CD, gives you ZFS functionality.<br />
<br />
[https://sourceforge.net/projects/systemrescuecd/files/sysresccd-x86/3.1.2/systemrescuecd-x86-3.1.2.iso/download Download System Rescue CD 3.1.2]<br />
<br />
[http://jonathanvasquez.com/files/sysresccd/ Download the ZFS System Rescue Module]<br />
<br />
<pre><br />
Name: SystemRescueCd-x86-3.1.2 (350 MiB)<br />
Release Date: 2012-12-05<br />
<br />
md5sum 3c1ddfe5f26bb2f979a2ed9dfb504ee3<br />
sha1sum 217cf7a81380d894b2433c59451787c16bc0af2f<br />
sha256sum ec0a995875e64ff9816a043737e5cbbb689b7f596b48679116f0a779f3dce673<br />
</pre><br />
<br />
Once you place the ISO on your USB flash drive, extract the modules from the tarball, and place the .srm and .md5 at the root of your USB filesystem. Further instructions can be found [[Creating_System_Rescue_CD_Modules#Using_the_prebuilt_srm|here]]. <br />
<br />
We will now start to partition the system. Open up a terminal, and type in the following (We will assume it's a fresh drive for simplicity).<br />
<br />
== Creating partitions ==<br />
<br />
We will be creating two partitions, /boot, and the remaining disk space will be for ZFS.<br />
<br />
(All commands will be ran as root).<br />
<br />
=== fdisk (MBR Style) ===<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M ↵<br />
</console><br />
<br />
'''Create Partition 2''' (ZFS):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
<br />
Command: ##i##t ↵<br />
Partition number: ##i##2 ↵<br />
Hex code (type L to list codes): ##i##bf ↵<br />
<br />
Command: ##i##p ↵<br />
<br />
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes<br />
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors<br />
Units = sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
Disk identifier: 0x3e954df7<br />
<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 2048 514047 256000 83 Linux<br />
/dev/sda2 514048 1953525167 976505560 bf Solaris<br />
<br />
</console><br />
<br />
=== gdisk (GPT Style) ===<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M ↵<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
'''Create Partition 2''' (BIOS Boot Partition):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+32M ↵<br />
Hex Code: ##i##EF02 ↵<br />
</console><br />
<br />
{{fancyimportant|Only make the above BIOS Boot Partition if you are using GRUB 2 on GPT. If you are using the extlinux bootloader, this partition is not necessary. The below instructions continue as if you did not create this partition and assumes you are using extlinux as the bootloader.}}<br />
<br />
'''Create Partition 2''' (ZFS):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
Hex Code: ##i##bf01 ↵<br />
<br />
Command: ##i##p ↵<br />
Disk /dev/sda: 1953525168 sectors, 931.5 GiB<br />
Logical sector size: 512 bytes<br />
Disk identifier (GUID): C0C1E56A-B24F-492F-95DB-2E227676F228<br />
Partition table holds up to 128 entries<br />
First usable sector is 34, last usable sector is 1953525134<br />
Partitions will be aligned on 2048-sector boundaries<br />
Total free space is 2014 sectors (1007.0 KiB)<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 514047 250.0 MiB 8300 Linux filesystem<br />
2 514048 1953525134 931.3 GiB BF01 Solaris /usr & Mac ZFS<br />
<br />
</console><br />
<br />
=== Format your boot volume ===<br />
<br />
<console><br />
# ##i##mkfs.ext4 /dev/sda1<br />
</console><br />
<br />
=== Create the zpool ===<br />
We will first create the pool. The pool will be named `rpool` and the disk will be aligned to 4096 (using ashift=12)<br />
<br />
<console><br />
# ##i##zpool create -f -o ashift=12 -o cachefile= -O compression=on -m none -R /mnt/funtoo rpool /dev/sda2<br />
</console><br />
<br />
{{fancyimportant|If you followed the GPT partitioning instructions, you should change /dev/sda2 to /dev/sda3.}}<br />
<br />
{{fancynote|If you have a previous pool that you would like to import, you can do a: '''zpool import -R /mnt/funtoo <pool_name>'''}}<br />
<br />
=== Create the zfs datasets ===<br />
We will now create some datasets. For this installation, we will create a small but future proof amount of datasets. We will have a dataset for the OS (/), and your swap. We will also show you how to create some optional datasets: /home, /var, /usr/src, and /usr/portage.<br />
<br />
<console><br />
Create some empty containers for organization purposes, and make the dataset that will hold /<br />
# ##i##zfs create -o mountpoint=none rpool/ROOT<br />
# ##i##zfs create -o mountpoint=/ rpool/ROOT/funtoo<br />
<br />
Optional, but recommended datasets: /home, /root <br />
# ##i##zfs create -o mountpoint=/home rpool/HOME<br />
# ##i##zfs create -o mountpoint=/root rpool/HOME/root<br />
<br />
Optional datasets: /usr/src, /var<br />
# ##i##zfs create -o mountpoint=none rpool/FUNTOO<br />
# ##i##zfs create -o mountpoint=/usr/src rpool/FUNTOO/src<br />
# ##i##zfs create -o mountpoint=/var rpool/FUNTOO/var<br />
</console><br />
<br />
==== Creating a separate portage dataset (optional) ====<br />
<br />
Creating a separate portage dataset could be useful if you would like to keep your portage tree, distfiles (source code files), and packages (your compiled binaries if you have FEATURES="buildpkg" enabled) in a safe place (or if you want to back up this directory up easily).<br />
<br />
This requires a few extra steps because we can't just do a regular emerge --sync when we initially chroot. We will need to download a portage snapshot tarball and extract it into the directory.<br />
<br />
The required steps for getting and extracting the snapshot will be shown later on in the guide once you chroot into the environment. For now just create the datasets:<br />
<br />
<console><br />
# ##i##zfs create -o mountpoint=/usr/portage -o compression=off rpool/FUNTOO/portage<br />
# ##i##zfs create -o mountpoint=/usr/portage/distfiles -o compression=off rpool/FUNTOO/distfiles<br />
</console><br />
<br />
=== Create your swap zvol ===<br />
<br />
'''Make your swap +1G greater than your RAM. An 8G machine would have 9G of RAM (This is kinda big though).'''<br />
<br />
<console><br />
# ##i##zfs create -o sync=always -o primarycache=metadata -o secondarycache=none -V 9G rpool/swap<br />
</console><br />
<br />
=== Format your swap zvol ===<br />
<br />
<console><br />
# ##i##mkswap -f /dev/zvol/rpool/swap<br />
# ##i##swapon /dev/zvol/rpool/swap<br />
</console><br />
<br />
Alright that finishes the creation of the zpool and zfs datasets. <br />
<br />
Check to make sure everything appears fine:<br />
<br />
<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
Copy the zpool.cache file to your new environment.<br />
<br />
<console><br />
# ##i##mkdir -p /mnt/funtoo/etc/zfs<br />
# ##i##cp /etc/zfs/zpool.cache /mnt/funtoo/etc/zfs<br />
</console><br />
<br />
Make an empty mtab file<br />
<br />
<console><br />
# ##i##touch /mnt/funtoo/etc/mtab<br />
</console><br />
<br />
Now we will continue to install funtoo.<br />
<br />
== Installing Funtoo ==<br />
<br />
[[Funtoo_Linux_Installation|Download and install the Funtoo stage3 and continue installation as normal.]]<br />
<br />
Then chroot into your new funtoo environment:<br />
<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
<br />
Mount your boot drive<br />
# ##i##mount /dev/sda1 /mnt/funtoo/boot<br />
<br />
Bind the kernel related directories<br />
# ##i##mount --bind /proc ./proc<br />
# ##i##mount --bind /dev ./dev<br />
# ##i##mount --bind /sys ./sys<br />
<br />
Copy network settings<br />
# ##i##cp /etc/resolv.conf etc/<br />
<br />
chroot into your new funtoo environment<br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l<br />
</console><br />
<br />
=== Syncing your portage tree ===<br />
<br />
==== If you didn't create a separate portage dataset, then just sync your portage tree as normal. ====<br />
<br />
<console><br />
# ##i##emerge --sync<br />
</console><br />
<br />
==== If you did create a separate portage dataset, let's now get the portage snapshot set up. ====<br />
<br />
<console><br />
Change into your /usr directory<br />
# ##i##cd /usr<br />
<br />
Download and extract the portage snapshot<br />
# ##i##wget http://ftp.osuosl.org/pub/funtoo/funtoo-current/snapshots/portage-latest.tar.xz<br />
# ##i##tar xf portage-latest.tar.xz<br />
<br />
Change into your portage directory and checkout the funtoo branch<br />
# ##i##cd portage<br />
# ##i##git checkout funtoo.org<br />
<br />
Now sync your portage tree<br />
# ##i##emerge --sync<br />
</console><br />
<br />
== Kernel Configuration ==<br />
<br />
Tested with kernel 2.6.32, 3.2.34, 3.6.9, 3.7.1.<br />
<br />
When you get up to the kernel, make sure that you disable the CFQ scheduler, and turn<br />
on No-op (It's the default one once you disable all schedulers). The reason for this is because ZFS has its<br />
own scheduler and the CFQ one conflicts with it.<br />
<br />
Go to your kernel config, and make sure you have the following: (there should be a /usr/src/linux symlink as well)<br />
<br />
<pre>ZLIB_INFLATE/DEFLATE must be compiled into the kernel (not as a module).<br />
> ZLIB_INFLATE [=y], ZLIB_DEFLATE [=y]<br />
<br />
General setup ---><br />
> [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support<br />
> () Initramfs source file(s)<br />
<br />
[*] Enable loadable module support ---><br />
[*] Module unloading<br />
<br />
Enable the block layer ---><br />
IO Schedulers ---><br />
< > Deadline I/O scheduler<br />
< > CFQ I/O scheduler<br />
Default I/O scheduler (No-op)<br />
<br />
Device Drivers ---><br />
> Generic Driver Options ---><br />
>> [*] Maintain a devtmpfs filesystem to mount at /dev<br />
>> [*] Automount devtmpfs at /dev, after the kernel mounted the rootfs<br />
<br />
* All other drivers required to see your PATA/SATA drives must be compiled in.<br />
</pre><br />
<br />
Continue and compile/install your kernel:<br />
<br />
<console><br />
# ##i##make bzImage modules<br />
# ##i##make install<br />
# ##i##make modules_install<br />
</console><br />
<br />
== Installing the ZFS userspace tools ==<br />
<br />
<console><br />
# ##i##emerge -av zfs<br />
</console><br />
<br />
Check to make sure that the zfs tools are working, the zpool.cache file that you copied before should be displayed.<br />
<br />
<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
If everything worked, continue.<br />
<br />
== Create the initramfs ==<br />
<br />
There are two ways to do this, you can use genkernel, or you can use my bliss initramfs creator. I will<br />
show you both.<br />
<br />
=== Bliss Initramfs Creator ===<br />
<br />
Make sure you compile sys-apps/busybox with the static flag.<br />
<br />
<console><br />
# ##i##echo "sys-apps/busybox static" >> /etc/portage/package.use<br />
# ##i##emerge -av sys-apps/busybox<br />
</console><br />
<br />
Clone my creator which is located at: git://github.com/fearedbliss/Bliss-Initramfs-Creator.git<br />
<br />
<console><br />
# ##i##git clone git://github.com/fearedbliss/Bliss-Initramfs-Creator.git<br />
</console><br />
<br />
Then go into this new directory, run the script as root, and place it into /boot<br />
<br />
<console><br />
# ##i##cd Bliss-Initramfs-Creator<br />
# ##i##./createInit<br />
# ##i##mv initrd-<kernel_name>.img /boot<br />
</console><br />
<br />
'''<kernel_name>''' is the name of what you selected in the initramfs creator, and the name of the outputted file.<br />
<br />
Once you do this just go to your bootloader config, and add it in there.<br />
<br />
<pre><br />
Example:<br />
<br />
Kernel name is: vmlinuz-3.7.1-ALL<br />
initramfs name is: initrd-3.7.1-ALL.img<br />
Pool root is: rpool/ROOT/funtoo<br />
</pre><br />
<br />
extlinux.conf:<br />
<br />
<console><br />
LABEL funtoo<br />
MENU LABEL Funtoo 3.7.1-ALL<br />
KERNEL /boot/vmlinuz-3.7.1-ALL<br />
INITRD /boot/initrd-3.7.1-ALL.img<br />
APPEND pool_root=rpool/ROOT/funtoo<br />
</console><br />
<br />
=== genkernel ===<br />
<br />
<console><br />
# ##i##emerge -av sys-kernel/genkernel<br />
# ##i##genkernel --zfs initramfs<br />
</console><br />
<br />
Example: <br />
kernel name is: vmlinuz-3.7.1-ALL<br />
initramfs name is: initramfs-genkernel-x86_64-3.7.1-ALL<br />
pool name is: rpool<br />
<br />
extlinux.conf:<br />
<br />
<console><br />
LABEL funtoo<br />
MENU LABEL Funtoo 3.7.1-ALL<br />
KERNEL /boot/vmlinuz-3.7.1-ALL<br />
INITRD /boot/initramfs-genkernel-x86_64-3.7.1-ALL<br />
APPEND real_root=ZFS=rpool/ROOT/funtoo dozfs=force<br />
</console><br />
<br />
== Final configuration ==<br />
<br />
=== Add the zfs tools to openrc ===<br />
<br />
<console><br />
# ##i##rc-update add zfs boot<br />
</console><br />
<br />
=== Add filesystems to /etc/fstab ===<br />
<br />
<console><br />
# ##i##nano /etc/fstab<br />
<br />
# <fs> <mountpoint> <type> <opts> <dump/pass><br />
<br />
/dev/sda1 /boot ext4 defaults 1 2<br />
/dev/zvol/rpool/swap none swap sw 0 0<br />
</console><br />
<br />
=== Clean up and reboot ===<br />
We are almost done, we are just going to clean up, '''set our root password''', and unmount whatever we mounted and get out.<br />
<br />
<console><br />
Delete the stage3/portage tarballs you downloaded earlier so they don't take up space.<br />
# ##i##cd /<br />
# ##i##rm stage3-latest.tar.xz<br />
# ##i##rm /usr/portage-latest.tar.xz<br />
<br />
Set your root password<br />
# ##i##passwd<br />
>> Enter your password, you won't see what you are writing (for security reasons), but it is there!<br />
<br />
Get out of the chroot environment<br />
# ##i##exit<br />
<br />
Unmount all the kernel filesystem stuff and boot<br />
# ##i##cd /mnt/funtoo<br />
# ##i##umount proc dev sys boot<br />
<br />
Turn off the swap<br />
# ##i##swapoff /dev/zvol/rpool/swap<br />
<br />
Export the zpool<br />
# ##i##cd /<br />
# ##i##zpool export -f rpool<br />
<br />
Reboot<br />
# ##i##reboot<br />
</console><br />
<br />
{{fancyimportant|'''Don't forget to set your root password as stated above before exiting chroot and rebooting. If you don't set the root password, you won't be able to log into your new system.'''}}<br />
and that should be enough to get your system to boot on ZFS.<br />
<br />
== Extra: After reboot ==<br />
<br />
After you restart your machine and your inside your desktop, continue to set up anything you need in terms of /etc configurations. Once you have everything the way you like it, take a snapshot of your system. You will be using this snapshot to revert back to this state if anything ever happens to your system down the road. The snapshots are cheap, and almost instant. To take the snapshot of your rootfs, type the following:<br />
<br />
<console><br />
# ##i##zfs snapshot rpool/ROOT/funtoo@install<br />
</console><br />
<br />
To see if your snapshot was taken, type:<br />
<br />
<console><br />
# ##i##zfs list -t snapshot<br />
</console><br />
<br />
If your machine ever fails and you need to get back to this state, just type:<br />
<br />
<console><br />
# ##i##zfs rollback rpool/ROOT/funtoo@install<br />
</console><br />
<br />
=== Recovery Environment ===<br />
On ZFS it is extremely easy to create a recovery environment using an already working snapshot. So that's what we will be doing. <br />
<br />
Create a clone of the @install snapshot which you will use for recovery purposes. If something happens to your main install, you can boot into this clone and fix the main one. One of the differences (maybe the only difference) between a clone and a snapshot is that a clone is rewritable while a snapshot is only read-only.<br />
<br />
<console><br />
# ##i##zfs clone rpool/ROOT/funtoo@install rpool/ROOT/recovery<br />
</console><br />
<br />
==== Add the clone to your extlinux.conf ====<br />
<br />
<console><br />
LABEL funtoo-recovery<br />
MENU LABEL Funtoo Recovery<br />
KERNEL /boot/vmlinuz-3.7.1-ALL<br />
INITRD /boot/initrd-3.7.1-ALL.img<br />
APPEND pool_root=rpool/ROOT/recovery<br />
</console><br />
<br />
==== Things to watch out for ====<br />
<br />
Since your recovery clone will tend to get old as you use your main system, and since <br />
your recovery and other stuff are on the same pool, we don't want the new pool stuff<br />
to be mounted when we launch recovery. We also don't want video drivers to be<br />
conflicting.<br />
<br />
1. Make sure that nvidia/nouveau stuff are blacklisted.<br />
2. Make sure that your /boot and /lib/modules for the kernel in your 'recovery' are<br />
matching.<br />
3. Disable the zfs openrc script so that nothing else gets automatically mounted.<br />
Only your rootfs.<br />
<br />
You can do the above stuff by mounting your copy and chrooting into it.<br />
<br />
<console><br />
Mount the recovery clone<br />
# ##i##mkdir /mnt/recovery<br />
# ##i##mount -t zfs -o zfsutil rpool/ROOT/recovery /mnt/recovery<br />
# ##i##cd /mnt/recovery<br />
<br />
Mount the kernel devices<br />
# ##i##mount --bind /proc ./proc<br />
# ##i##mount --bind /dev ./dev<br />
# ##i##mount --bind /sys ./sys<br />
<br />
Copy zpool.cache<br />
# ##i##cp /etc/zfs/zpool.cache etc/zfs<br />
<br />
Chroot into the new environment<br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash --login<br />
<br />
Disable zfs/zfs-shutdown openrc scripts<br />
# ##i##rc-config delete zfs boot<br />
# ##i##rc-config delete zfs-shutdown shutdown<br />
<br />
Blacklist nouveau/nvidia drivers<br />
# ##i##echo "blacklist nouveau" >> /etc/modprobe.d/blacklist.conf<br />
# ##i##echo "blacklist nvidia" >> /etc/modprobe.d/blacklist.conf<br />
</console><br />
<br />
==== Getting into the recovery ====<br />
Just start your machine and pick the '''Funtoo Recovery''' option from the Boot Menu.<br />
<br />
Enjoy your new install on ZFS :)<br />
[[Category:HOWTO]]<br />
[[Category:Filesystems]]</div>Oleghttp://www.funtoo.org/wiki/ZFS_Install_GuideZFS Install Guide2013-01-05T05:06:47Z<p>Oleg: </p>
<hr />
<div>This tutorial will show you how to install Funtoo on ZFS (rootfs).<br />
<br />
This tutorial is meant to be an "overlay" over the [[Funtoo_Linux_Installation|Regular Funtoo Installation]]. Follow the normal installation and only use this guide for steps 2, 3, and 8.<br />
<br />
{{fancyimportant|'''Since ZFS was really designed for 64 bit systems, we are only recommending and supporting 64 bit platforms and installations. We will not be supporting 32 bit platforms'''!}}<br />
<br />
== Setting up your environment ==<br />
In order for us to install Funtoo on ZFS, you will need an environment that provides the ZFS userspace tools. We will be downloading two things, System Rescue CD 3.1.2, and the ZFS SRM (System Rescue Module). This is just a file that when combined with System Rescue CD, gives you ZFS functionality.<br />
<br />
[https://sourceforge.net/projects/systemrescuecd/files/sysresccd-x86/3.1.2/systemrescuecd-x86-3.1.2.iso/download Download System Rescue CD 3.1.2]<br />
<br />
[http://jonathanvasquez.com/files/sysresccd/ Download the ZFS System Rescue Module]<br />
<br />
<pre><br />
Name: SystemRescueCd-x86-3.1.2 (350 MiB)<br />
Release Date: 2012-12-05<br />
<br />
md5sum 3c1ddfe5f26bb2f979a2ed9dfb504ee3<br />
sha1sum 217cf7a81380d894b2433c59451787c16bc0af2f<br />
sha256sum ec0a995875e64ff9816a043737e5cbbb689b7f596b48679116f0a779f3dce673<br />
</pre><br />
<br />
Once you place the ISO on your USB flash drive, extract the modules from the tarball, and place the .srm and .md5 at the root of your USB filesystem. Further instructions can be found [[Creating_System_Rescue_CD_Modules#Using_the_prebuilt_srm|here]]. <br />
<br />
We will now start to partition the system. Open up a terminal, and type in the following (We will assume it's a fresh drive for simplicity).<br />
<br />
== Creating partitions ==<br />
<br />
We will be creating two partitions, /boot, and the remaining disk space will be for ZFS.<br />
<br />
(All commands will be ran as root).<br />
<br />
=== fdisk (MBR Style) ===<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M ↵<br />
</console><br />
<br />
'''Create Partition 2''' (ZFS):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
<br />
Command: ##i##t ↵<br />
Partition number: ##i##2 ↵<br />
Hex code (type L to list codes): ##i##bf ↵<br />
<br />
Command: ##i##p ↵<br />
<br />
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes<br />
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors<br />
Units = sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
Disk identifier: 0x3e954df7<br />
<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 2048 514047 256000 83 Linux<br />
/dev/sda2 514048 1953525167 976505560 bf Solaris<br />
<br />
</console><br />
<br />
=== gdisk (GPT Style) ===<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M ↵<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
'''Create Partition 2''' (BIOS Boot Partition):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+32M ↵<br />
Hex Code: ##i##EF02 ↵<br />
</console><br />
<br />
{{fancyimportant|Only make the above BIOS Boot Partition if you are using GRUB 2 on GPT. If you are using the extlinux bootloader, this partition is not necessary. The below instructions continue as if you did not create this partition and assumes you are using extlinux as the bootloader.}}<br />
<br />
'''Create Partition 2''' (ZFS):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
Hex Code: ##i##bf01 ↵<br />
<br />
Command: ##i##p ↵<br />
Disk /dev/sda: 1953525168 sectors, 931.5 GiB<br />
Logical sector size: 512 bytes<br />
Disk identifier (GUID): C0C1E56A-B24F-492F-95DB-2E227676F228<br />
Partition table holds up to 128 entries<br />
First usable sector is 34, last usable sector is 1953525134<br />
Partitions will be aligned on 2048-sector boundaries<br />
Total free space is 2014 sectors (1007.0 KiB)<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 514047 250.0 MiB 8300 Linux filesystem<br />
2 514048 1953525134 931.3 GiB BF01 Solaris /usr & Mac ZFS<br />
<br />
</console><br />
<br />
=== Format your boot volume ===<br />
<br />
<console><br />
# ##i##mkfs.ext4 /dev/sda1<br />
</console><br />
<br />
=== Create the zpool ===<br />
We will first create the pool. The pool will be named `rpool` and the disk will be aligned to 4096 (using ashift=12)<br />
<br />
<console><br />
# ##i##zpool create -f -o ashift=12 -o cachefile= -O compression=on -m none -R /mnt/funtoo rpool /dev/sda2<br />
</console><br />
<br />
{{fancynote|If you have a previous pool that you would like to import, you can do a: '''zpool import -R /mnt/funtoo <pool_name>'''}}<br />
<br />
=== Create the zfs datasets ===<br />
We will now create some datasets. For this installation, we will create a small but future proof amount of datasets. We will have a dataset for the OS (/), and your swap. We will also show you how to create some optional datasets: /home, /var, /usr/src, and /usr/portage.<br />
<br />
<console><br />
Create some empty containers for organization purposes, and make the dataset that will hold /<br />
# ##i##zfs create -o mountpoint=none rpool/ROOT<br />
# ##i##zfs create -o mountpoint=/ rpool/ROOT/funtoo<br />
<br />
Optional, but recommended datasets: /home, /root <br />
# ##i##zfs create -o mountpoint=/home rpool/HOME<br />
# ##i##zfs create -o mountpoint=/root rpool/HOME/root<br />
<br />
Optional datasets: /usr/src, /var<br />
# ##i##zfs create -o mountpoint=none rpool/FUNTOO<br />
# ##i##zfs create -o mountpoint=/usr/src rpool/FUNTOO/src<br />
# ##i##zfs create -o mountpoint=/var rpool/FUNTOO/var<br />
</console><br />
<br />
==== Creating a separate portage dataset (optional) ====<br />
<br />
Creating a separate portage dataset could be useful if you would like to keep your portage tree, distfiles (source code files), and packages (your compiled binaries if you have FEATURES="buildpkg" enabled) in a safe place (or if you want to back up this directory up easily).<br />
<br />
This requires a few extra steps because we can't just do a regular emerge --sync when we initially chroot. We will need to download a portage snapshot tarball and extract it into the directory.<br />
<br />
The required steps for getting and extracting the snapshot will be shown later on in the guide once you chroot into the environment. For now just create the datasets:<br />
<br />
<console><br />
# ##i##zfs create -o mountpoint=/usr/portage -o compression=off rpool/FUNTOO/portage<br />
# ##i##zfs create -o mountpoint=/usr/portage/distfiles -o compression=off rpool/FUNTOO/distfiles<br />
</console><br />
<br />
=== Create your swap dataset ===<br />
<br />
'''Make your swap +1G greater than your RAM. An 8G machine would have 9G of RAM (This is kinda big though).'''<br />
<br />
<console><br />
# ##i##zfs create -o sync=always -o primarycache=metadata -o secondarycache=none -V 9G rpool/swap<br />
</console><br />
<br />
=== Format your swap dataset ===<br />
<br />
<console><br />
# ##i##mkswap -f /dev/zvol/rpool/swap<br />
# ##i##swapon /dev/zvol/rpool/swap<br />
</console><br />
<br />
Alright that finishes the creation of the zpool and zfs datasets. <br />
<br />
Check to make sure everything appears fine:<br />
<br />
<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
Copy the zpool.cache file to your new environment.<br />
<br />
<console><br />
# ##i##mkdir -p /mnt/funtoo/etc/zfs<br />
# ##i##cp /etc/zfs/zpool.cache /mnt/funtoo/etc/zfs<br />
</console><br />
<br />
Make an empty mtab file<br />
<br />
<console><br />
# ##i##touch /mnt/funtoo/etc/mtab<br />
</console><br />
<br />
Now we will continue to install funtoo.<br />
<br />
== Installing Funtoo ==<br />
<br />
[[Funtoo_Linux_Installation|Download and install the Funtoo stage3 and continue installation as normal.]]<br />
<br />
Then chroot into your new funtoo environment:<br />
<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
<br />
Mount your boot drive<br />
# ##i##mount /dev/sda1 /mnt/funtoo/boot<br />
<br />
Bind the kernel related directories<br />
# ##i##mount --bind /proc ./proc<br />
# ##i##mount --bind /dev ./dev<br />
# ##i##mount --bind /sys ./sys<br />
<br />
Copy network settings<br />
# ##i##cp /etc/resolv.conf etc/<br />
<br />
chroot into your new funtoo environment<br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l<br />
</console><br />
<br />
=== Syncing your portage tree ===<br />
<br />
==== If you didn't create a separate portage dataset, then just sync your portage tree as normal. ====<br />
<br />
<console><br />
# ##i##emerge --sync<br />
</console><br />
<br />
==== If you did create a separate portage dataset, let's now get the portage snapshot set up. ====<br />
<br />
<console><br />
Change into your /usr directory<br />
# ##i##cd /usr<br />
<br />
Download and extract the portage snapshot<br />
# ##i##wget http://ftp.osuosl.org/pub/funtoo/funtoo-current/snapshots/portage-latest.tar.xz<br />
# ##i##tar xf portage-latest.tar.xz<br />
<br />
Change into your portage directory and checkout the funtoo branch<br />
# ##i##cd portage<br />
# ##i##git checkout funtoo.org<br />
<br />
Now sync your portage tree<br />
# ##i##emerge --sync<br />
</console><br />
<br />
== Kernel Configuration ==<br />
<br />
Tested with kernel 2.6.32, 3.2.34, 3.6.9, 3.7.1.<br />
<br />
When you get up to the kernel, make sure that you disable the CFQ scheduler, and turn<br />
on No-op (It's the default one once you disable all schedulers). The reason for this is because ZFS has its<br />
own scheduler and the CFQ one conflicts with it.<br />
<br />
Go to your kernel config, and make sure you have the following: (there should be a /usr/src/linux symlink as well)<br />
<br />
<pre>ZLIB_INFLATE/DEFLATE must be compiled into the kernel (not as a module).<br />
> ZLIB_INFLATE [=y], ZLIB_DEFLATE [=y]<br />
<br />
General setup ---><br />
> [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support<br />
> () Initramfs source file(s)<br />
<br />
[*] Enable loadable module support ---><br />
[*] Module unloading<br />
<br />
Enable the block layer ---><br />
IO Schedulers ---><br />
< > Deadline I/O scheduler<br />
< > CFQ I/O scheduler<br />
Default I/O scheduler (No-op)<br />
<br />
Device Drivers ---><br />
> Generic Driver Options ---><br />
>> [*] Maintain a devtmpfs filesystem to mount at /dev<br />
>> [*] Automount devtmpfs at /dev, after the kernel mounted the rootfs<br />
<br />
* All other drivers required to see your PATA/SATA drives must be compiled in.<br />
</pre><br />
<br />
Continue and compile/install your kernel:<br />
<br />
<console><br />
# ##i##make bzImage modules<br />
# ##i##make install<br />
# ##i##make modules_install<br />
</console><br />
<br />
== Installing the ZFS userspace tools ==<br />
<br />
<console><br />
# ##i##emerge -av zfs<br />
</console><br />
<br />
Check to make sure that the zfs tools are working, the zpool.cache file that you copied before should be displayed.<br />
<br />
<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
If everything worked, continue.<br />
<br />
== Create the initramfs ==<br />
<br />
There are two ways to do this, you can use genkernel, or you can use my bliss initramfs creator. I will<br />
show you both.<br />
<br />
=== Bliss Initramfs Creator ===<br />
<br />
Make sure you compile sys-apps/busybox with the static flag.<br />
<br />
<console><br />
# ##i##echo "sys-apps/busybox static" >> /etc/portage/package.use<br />
# ##i##emerge -av sys-apps/busybox<br />
</console><br />
<br />
Clone my creator which is located at: git://github.com/fearedbliss/Bliss-Initramfs-Creator.github<br />
<br />
<console><br />
# ##i##git clone git://github.com/fearedbliss/Bliss-Initramfs-Creator.git<br />
</console><br />
<br />
Then go into this new directory, run the script as root, and place it into /boot<br />
<br />
<console><br />
# ##i##cd Bliss-Initramfs-Creator<br />
# ##i##./createInit<br />
# ##i##mv initrd-<kernel_name>.img /boot<br />
</console><br />
<br />
'''<kernel_name>''' is the name of what you selected in the initramfs creator, and the name of the outputted file.<br />
<br />
Once you do this just go to your bootloader config, and add it in there.<br />
<br />
<pre><br />
Example:<br />
<br />
Kernel name is: vmlinuz-3.7.1-ALL<br />
initramfs name is: initrd-3.7.1-ALL.img<br />
Pool root is: rpool/ROOT/funtoo<br />
</pre><br />
<br />
extlinux.conf:<br />
<br />
<console><br />
LABEL funtoo<br />
MENU LABEL Funtoo 3.7.1-ALL<br />
KERNEL /boot/vmlinuz-3.7.1-ALL<br />
INITRD /boot/initrd-3.7.1-ALL.img<br />
APPEND pool_root=rpool/ROOT/funtoo<br />
</console><br />
<br />
=== genkernel ===<br />
<br />
<console><br />
# ##i##emerge -av sys-kernel/genkernel<br />
# ##i##genkernel --zfs initramfs<br />
</console><br />
<br />
Example: <br />
kernel name is: vmlinuz-3.7.1-ALL<br />
initramfs name is: initramfs-genkernel-x86_64-3.7.1-ALL<br />
pool name is: rpool<br />
<br />
extlinux.conf:<br />
<br />
<console><br />
LABEL funtoo<br />
MENU LABEL Funtoo 3.7.1-ALL<br />
KERNEL /boot/vmlinuz-3.7.1-ALL<br />
INITRD /boot/initramfs-genkernel-x86_64-3.7.1-ALL<br />
APPEND real_root=ZFS=rpool/ROOT/funtoo dozfs=force<br />
</console><br />
<br />
== Final configuration ==<br />
<br />
=== Add the zfs tools to openrc ===<br />
<br />
<console><br />
# ##i##rc-update add zfs boot<br />
# ##i##rc-update add zfs-shutdown shutdown<br />
</console><br />
<br />
=== Add filesystems to /etc/fstab ===<br />
<br />
<console><br />
# ##i##nano /etc/fstab<br />
<br />
# <fs> <mountpoint> <type> <opts> <dump/pass><br />
<br />
/dev/sda1 /boot ext4 defaults 1 2<br />
/dev/zvol/rpool/swap none swap sw 0 0<br />
</console><br />
<br />
=== Clean up and reboot ===<br />
We are almost done, we are just going to clean up, '''set our root password''', and unmount whatever we mounted and get out.<br />
<br />
<console><br />
Delete the stage3/portage tarballs you downloaded earlier so they don't take up space.<br />
# ##i##cd /<br />
# ##i##rm stage3-latest.tar.xz<br />
# ##i##rm /usr/portage-latest.tar.xz<br />
<br />
Set your root password<br />
# ##i##passwd<br />
>> Enter your password, you won't see what you are writing (for security reasons), but it is there!<br />
<br />
Get out of the chroot environment<br />
# ##i##exit<br />
<br />
Unmount all the kernel filesystem stuff and boot<br />
# ##i##cd /mnt/funtoo<br />
# ##i##umount proc dev sys boot<br />
<br />
Turn off the swap<br />
# ##i##swapoff /dev/zvol/rpool/swap<br />
<br />
Export the zpool<br />
# ##i##cd /<br />
# ##i##zpool export -f rpool<br />
<br />
Reboot<br />
# ##i##reboot<br />
</console><br />
<br />
{{fancyimportant|'''Don't forget to set your root password as stated above before exiting chroot and rebooting. If you don't set the root password, you won't be able to log into your new system.'''}}<br />
and that should be enough to get your system to boot on ZFS.<br />
<br />
== Extra: After reboot ==<br />
<br />
After you restart your machine and your inside your desktop, continue to set up anything you need in terms of /etc configurations. Once you have everything the way you like it, take a snapshot of your system. You will be using this snapshot to revert back to this state if anything ever happens to your system down the road. The snapshots are cheap, and almost instant. To take the snapshot of your rootfs, type the following:<br />
<br />
<console><br />
# ##i##zfs snapshot rpool/ROOT/funtoo@install<br />
</console><br />
<br />
To see if your snapshot was taken, type:<br />
<br />
<console><br />
# ##i##zfs list -t snapshot<br />
</console><br />
<br />
If your machine ever fails and you need to get back to this state, just type:<br />
<br />
<console><br />
# ##i##zfs rollback rpool/ROOT/funtoo@install<br />
</console><br />
<br />
=== Recovery Environment ===<br />
On ZFS it is extremely easy to create a recovery environment using an already working snapshot. So that's what we will be doing. <br />
<br />
Create a clone of the @install snapshot which you will use for recovery purposes. If something happens to your main install, you can boot into this clone and fix the main one. One of the differences (maybe the only difference) between a clone and a snapshot is that a clone is rewritable while a snapshot is only read-only.<br />
<br />
<console><br />
# ##i##zfs clone rpool/ROOT/funtoo@install rpool/ROOT/recovery<br />
</console><br />
<br />
==== Add the clone to your extlinux.conf ====<br />
<br />
<console><br />
LABEL funtoo-recovery<br />
MENU LABEL Funtoo Recovery<br />
KERNEL /boot/vmlinuz-3.7.1-ALL<br />
INITRD /boot/initrd-3.7.1-ALL.img<br />
APPEND pool_root=rpool/ROOT/recovery<br />
</console><br />
<br />
==== Things to watch out for ====<br />
<br />
Since your recovery clone will tend to get old as you use your main system, and since <br />
your recovery and other stuff are on the same pool, we don't want the new pool stuff<br />
to be mounted when we launch recovery. We also don't want video drivers to be<br />
conflicting.<br />
<br />
1. Make sure that nvidia/nouveau stuff are blacklisted.<br />
2. Make sure that your /boot and /lib/modules for the kernel in your 'recovery' are<br />
matching.<br />
3. Disable the zfs openrc script so that nothing else gets automatically mounted.<br />
Only your rootfs.<br />
<br />
You can do the above stuff by mounting your copy and chrooting into it.<br />
<br />
<console><br />
Mount the recovery clone<br />
# ##i##mkdir /mnt/recovery<br />
# ##i##mount -t zfs -o zfsutil rpool/ROOT/recovery /mnt/recovery<br />
# ##i##cd /mnt/recovery<br />
<br />
Mount the kernel devices<br />
# ##i##mount --bind /proc ./proc<br />
# ##i##mount --bind /dev ./dev<br />
# ##i##mount --bind /sys ./sys<br />
<br />
Copy zpool.cache<br />
# ##i##cp /etc/zfs/zpool.cache etc/zfs<br />
<br />
Chroot into the new environment<br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash --login<br />
<br />
Disable zfs/zfs-shutdown openrc scripts<br />
# ##i##rc-config delete zfs boot<br />
# ##i##rc-config delete zfs-shutdown shutdown<br />
<br />
Blacklist nouveau/nvidia drivers<br />
# ##i##echo "blacklist nouveau" >> /etc/modprobe.d/blacklist.conf<br />
# ##i##echo "blacklist nvidia" >> /etc/modprobe.d/blacklist.conf<br />
</console><br />
<br />
==== Getting into the recovery ====<br />
Just start your machine and pick the '''Funtoo Recovery''' option from the Boot Menu.<br />
<br />
Enjoy your new install on ZFS :)<br />
[[Category:HOWTO]]</div>Oleghttp://www.funtoo.org/wiki/LocalpatchLocalpatch2013-01-03T00:43:45Z<p>Oleg: </p>
<hr />
<div>{{Template:Fancynote|This is just workprint. Feel free to contribute.}}<br />
{{fancyimportant|'''Localpatch feature is severely outdated and removed from portage, use foobashrc ebuild'''!}}<br />
<br />
== Installation ==<br />
localpatch is no longer part of portage. You need to install foobashrc: <br />
<console># ##i##emerge app-portage/foobashrc</console><br />
This will install the script foobashrc.bashrc at /etc/portage/. It is intended to be used in the emerge process through /etc/portage/bashrc (see [http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=3&chap=6#doc_chap3 Hooking In the Emerge Process (Gentoo Manual)]). If you do not have your own bashrc yet, you can just link it to foobashrc.bashrc:<br />
<console># ##i##ln -s /etc/portage/foobashrc.bashrc /etc/portage/bashrc</console><br />
To complete the installation you need to add <br />
<br />
<pre><br />
foobashrc_modules = "localpatch"<br />
</pre><br />
to your make.conf. By un-/commenting this line you can easily activate/deactivate localepatch.<br />
== How it works ==<br />
<br />
By default, localpatch will look into /etc/portage/localpatches in order to search for patches. This can be changed by setting LOCALPATCH_OVERLAY variable within make.conf.<br />
<br />
The actual patches for a package are placed in subdirectories with one of the following naming shemata:<br />
# ${CATEGORY}/${PN}-${PV}-${PR} - example 'app-foo/bar-1.0-r1'<br />
# ${CATEGORY}/${PN}-${PV} - example 'app-foo/bar-1.0'<br />
# ${CATEGORY}/${PN} - example 'app-foo/bar'<br />
Only the patches within the first matching shema are used and are applied within numerical order.<br />
<br />
== See Also ==<br />
<br />
[[Localpatch_(Tutorial)]]<br /><br />
http://forums.funtoo.org/viewtopic.php?id=193<br />
<br />
[[Category:Projects]]<br />
[[Category:Portage]]<br />
[[Category:Labs]]</div>Oleghttp://www.funtoo.org/wiki/Talk:WelcomeTalk:Welcome2013-01-02T16:03:56Z<p>Oleg: Reverted edits by Engly22 (talk) to last revision by 120.85.194.203</p>
<hr />
<div>Hello. And Bye.</div>Oleghttp://www.funtoo.org/wiki/ZFS_Install_GuideZFS Install Guide2013-01-01T13:23:08Z<p>Oleg: /* Kernel Configuration */</p>
<hr />
<div>This tutorial will show you how to install Funtoo on ZFS (rootfs).<br />
<br />
This tutorial is meant to be an "overlay" over the [[Funtoo_Linux_Installation|Regular Funtoo Installation]]. Follow the normal installation and only use this guide for steps 2, 3, and 8.<br />
<br />
{{fancyimportant|'''Since ZFS was really designed for 64 bit systems, we are only recommending and supporting 64 bit platforms and installations. We will not be supporting 32 bit platforms'''!}}<br />
<br />
== Setting up your environment ==<br />
In order for us to install Funtoo on ZFS, you will need an environment that provides the ZFS userspace tools. We will be downloading two things, System Rescue CD 3.1.2, and the zfs srm (System Rescue Module). This is just a file that when combined with System Rescue CD, gives you ZFS functionality.<br />
<br />
[https://sourceforge.net/projects/systemrescuecd/files/sysresccd-x86/3.1.2/systemrescuecd-x86-3.1.2.iso/download Download System Rescue CD 3.1.2]<br />
<br />
[http://jonathanvasquez.com/files/sysresccd/ Download the ZFS System Rescue Module]<br />
<br />
<pre><br />
Name: SystemRescueCd-x86-3.1.2 (350 MiB)<br />
Release Date: 2012-12-05<br />
<br />
md5sum 3c1ddfe5f26bb2f979a2ed9dfb504ee3<br />
sha1sum 217cf7a81380d894b2433c59451787c16bc0af2f<br />
sha256sum ec0a995875e64ff9816a043737e5cbbb689b7f596b48679116f0a779f3dce673<br />
</pre><br />
<br />
Once you place the iso on your usb flash drive, extract the modules from the tarball, and place the .srm and .md5 at the root of your usb. Further instructions can be found [[Creating_System_Rescue_CD_Modules#Using_the_prebuilt_srm|here]]. <br />
<br />
We will now start to partition the system. Open up a terminal, and type in the following (We will assume it's a fresh drive for simplicity).<br />
<br />
== Creating partitions ==<br />
<br />
We will be creating two partitions, /boot, and the remaining disk space will be for ZFS.<br />
<br />
(All commands will be ran as root).<br />
<br />
=== fdisk (MBR Style) ===<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M ↵<br />
</console><br />
<br />
'''Create Partition 2''' (ZFS):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
<br />
Command: ##i##t ↵<br />
Partition number: ##i##2 ↵<br />
Hex code (type L to list codes): ##i##bf ↵<br />
<br />
Command: ##i##p ↵<br />
<br />
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes<br />
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors<br />
Units = sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
Disk identifier: 0x3e954df7<br />
<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 2048 514047 256000 83 Linux<br />
/dev/sda2 514048 1953525167 976505560 bf Solaris<br />
<br />
</console><br />
<br />
=== gdisk (GPT Style) ===<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M ↵<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
'''Create Partition 2''' (BIOS Boot Partition):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+32M ↵<br />
Hex Code: ##i##EF02 ↵<br />
</console><br />
<br />
{{fancyimportant|Only make the above BIOS Boot Partition if you are using GRUB 2 on GPT. If you are using the extlinux bootloader, this partition is not necessary. The below instructions continue as if you did not create this partition and assumes you are using extlinux as the bootloader.}}<br />
<br />
'''Create Partition 2''' (ZFS):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
Hex Code: ##i##bf01 ↵<br />
<br />
Command: ##i##p ↵<br />
Disk /dev/sda: 1953525168 sectors, 931.5 GiB<br />
Logical sector size: 512 bytes<br />
Disk identifier (GUID): C0C1E56A-B24F-492F-95DB-2E227676F228<br />
Partition table holds up to 128 entries<br />
First usable sector is 34, last usable sector is 1953525134<br />
Partitions will be aligned on 2048-sector boundaries<br />
Total free space is 2014 sectors (1007.0 KiB)<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 514047 250.0 MiB 8300 Linux filesystem<br />
2 514048 1953525134 931.3 GiB BF01 Solaris /usr & Mac ZFS<br />
<br />
</console><br />
<br />
=== Format your boot volume ===<br />
<br />
<console><br />
# ##i##mkfs.ext4 /dev/sda1<br />
</console><br />
<br />
=== Create the zpool ===<br />
We will first create the pool. The pool will be named `rpool` and the disk will be aligned to 4096 (using ashift=12)<br />
<br />
<console><br />
# ##i##zpool create -f -o ashift=12 -o cachefile= -O compression=on -m none -R /mnt/funtoo rpool /dev/sda2<br />
</console><br />
<br />
=== Create the zfs datasets ===<br />
We will now create some datasets. For this installation, we will create a small but future proof amount of datasets. We will have a dataset for the OS (/), and your swap. We will also show you how to create some optional datasets: /home, /var, /usr/src, and /usr/portage.<br />
<br />
<console><br />
Create some empty containers for organization purposes, and make the dataset that will hold /<br />
# ##i##zfs create -o mountpoint=none rpool/ROOT<br />
# ##i##zfs create -o mountpoint=/ rpool/ROOT/funtoo<br />
<br />
Optional, but recommended datasets: /home, /root <br />
# ##i##zfs create -o mountpoint=/home rpool/HOME<br />
# ##i##zfs create -o mountpoint=/root rpool/HOME/root<br />
<br />
Optional datasets: /usr/src, /var<br />
# ##i##zfs create -o mountpoint=none rpool/FUNTOO<br />
# ##i##zfs create -o mountpoint=/usr/src rpool/FUNTOO/src<br />
# ##i##zfs create -o mountpoint=/var rpool/FUNTOO/var<br />
</console><br />
<br />
==== Creating a separate portage dataset (optional) ====<br />
<br />
Creating a separate portage dataset could be useful if you would like to keep your portage tree, distfiles (source code files), and packages (your compiled binaries if you have FEATURES="buildpkg" enabled) in a safe place (or if you want to back up this directory up easily).<br />
<br />
This requires a few extra steps because we can't just do a regular emerge --sync when we initially chroot. We will need to download a portage snapshot tarball and extract it into the directory.<br />
<br />
The required steps for getting and extracting the snapshot will be shown later on in the guide once you chroot into the environment. For now just create the datasets:<br />
<br />
<console><br />
# ##i##zfs create -o mountpoint=/usr/portage -o compression=off rpool/FUNTOO/portage<br />
# ##i##zfs create -o mountpoint=/usr/portage/distfiles -o compression=off rpool/FUNTOO/distfiles<br />
</console><br />
<br />
=== Create your swap dataset ===<br />
<br />
'''Make your swap +1G greater than your RAM. An 8G machine would have 9G of RAM (This is kinda big though).'''<br />
<br />
<console><br />
# ##i##zfs create -o sync=always -o primarycache=metadata -o secondarycache=none -V 9G rpool/swap<br />
</console><br />
<br />
=== Format your swap dataset ===<br />
<br />
<console><br />
# ##i##mkswap -f /dev/zvol/rpool/swap<br />
# ##i##swapon /dev/zvol/rpool/swap<br />
</console><br />
<br />
Alright that finishes the creation of the zpool and zfs datasets. <br />
<br />
Check to make sure everything appears fine:<br />
<br />
<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
Copy the zpool.cache file to your new environment.<br />
<br />
<console><br />
# ##i##mkdir -p /mnt/funtoo/etc/zfs<br />
# ##i##cp /etc/zfs/zpool.cache /mnt/funtoo/etc/zfs<br />
</console><br />
<br />
Make an empty mtab file<br />
<br />
<console><br />
# ##i##touch /mnt/funtoo/etc/mtab<br />
</console><br />
<br />
Now we will continue to install funtoo.<br />
<br />
== Installing Funtoo ==<br />
<br />
[[Funtoo_Linux_Installation|Download and install the Funtoo stage3 and continue installation as normal.]]<br />
<br />
Then chroot into your new funtoo environment:<br />
<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
<br />
Mount your boot drive<br />
# ##i##mount /dev/sda1 /mnt/funtoo/boot<br />
<br />
Bind the kernel related directories<br />
# ##i##mount --bind /proc ./proc<br />
# ##i##mount --bind /dev ./dev<br />
# ##i##mount --bind /sys ./sys<br />
<br />
Copy network settings<br />
# ##i##cp /etc/resolv.conf etc/<br />
<br />
chroot into your new funtoo environment<br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l<br />
</console><br />
<br />
=== Syncing your portage tree ===<br />
<br />
==== If you didn't create a separate portage dataset, then just sync your portage tree as normal. ====<br />
<br />
<console><br />
# ##i##emerge --sync<br />
</console><br />
<br />
==== If you did create a separate portage dataset, let's now get the portage snapshot set up. ====<br />
<br />
<console><br />
Change into your /usr directory<br />
# ##i##cd /usr<br />
<br />
Download and extract the portage snapshot<br />
# ##i##wget http://ftp.osuosl.org/pub/funtoo/funtoo-current/snapshots/portage-latest.tar.xz<br />
# ##i##tar xf portage-latest.tar.xz<br />
<br />
Change into your portage directory and checkout the funtoo branch<br />
# ##i##cd portage<br />
# ##i##git checkout funtoo.org<br />
<br />
Now sync your portage tree<br />
# ##i##emerge --sync<br />
</console><br />
<br />
== Kernel Configuration ==<br />
<br />
Tested with kernel 2.6.32, 3.2.34, 3.6.9, 3.7.1.<br />
<br />
When you get up to the kernel, make sure that you disable the CFQ scheduler, and turn<br />
on No-op (It's the default one once you disable all schedulers). The reason for this is because ZFS has its<br />
own scheduler and the CFQ one conflicts with it.<br />
<br />
Go to your kernel config, and make sure you have the following: (there should be a /usr/src/linux symlink as well)<br />
<br />
<pre>ZLIB_INFLATE/DEFLATE must be compiled into the kernel (not as a module).<br />
> ZLIB_INFLATE [=y], ZLIB_DEFLATE [=y]<br />
<br />
General setup ---><br />
> [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support<br />
> () Initramfs source file(s)<br />
<br />
[*] Enable loadable module support ---><br />
[*] Module unloading<br />
<br />
Enable the block layer ---><br />
IO Schedulers ---><br />
< > Deadline I/O scheduler<br />
< > CFQ I/O scheduler<br />
Default I/O scheduler (No-op)<br />
<br />
Device Drivers ---><br />
> Generic Driver Options ---><br />
>> [*] Maintain a devtmpfs filesystem to mount at /dev<br />
>> [*] Automount devtmpfs at /dev, after the kernel mounted the rootfs<br />
<br />
* All other drivers required to see your PATA/SATA drives must be compiled in.<br />
</pre><br />
<br />
Continue and compile/install your kernel:<br />
<br />
<console><br />
# ##i##make bzImage modules<br />
# ##i##make install<br />
# ##i##make modules_install<br />
</console><br />
<br />
== Installing the ZFS userspace tools ==<br />
<br />
<console><br />
# ##i##emerge -av spl zfs zfs-kmod<br />
</console><br />
<br />
Check to make sure that the zfs tools are working, the zpool.cache file that you copied before should be<br />
displayed.<br />
<br />
<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
If everything worked, continue.<br />
<br />
== Create the initramfs ==<br />
<br />
There are two ways to do this, you can use genkernel, or you can use my zfs initramfs creator. I will<br />
show you both.<br />
<br />
=== Bliss Initramfs Creator ===<br />
<br />
Make sure you compile sys-apps/busybox with the static flag.<br />
<br />
<console><br />
# ##i##echo "sys-apps/busybox static" >> /etc/portage/package.use<br />
# ##i##emerge -av sys-apps/busybox<br />
</console><br />
<br />
Clone my creator which is located at: git://github.com/fearedbliss/Bliss-Initramfs-Creator.github<br />
<br />
<console><br />
# ##i##git clone git://github.com/fearedbliss/Bliss-Initramfs-Creator.git<br />
</console><br />
<br />
Then go into this new directory, run the script as root, and place it into /boot<br />
<br />
<console><br />
# ##i##cd Bliss-Initramfs-Creator<br />
# ##i##./createInit<br />
# ##i##mv initrd-<kernel_name>.img /boot<br />
</console><br />
<br />
'''<kernel_name>''' is the name of what you selected in the initramfs creator, and the name of the outputted file.<br />
<br />
Once you do this just go to your bootloader config, and add it in there.<br />
<br />
Example: <br />
kernel name is: vmlinuz-3.7.1-ALL<br />
initramfs name is: initrd-3.7.1-ALL.img<br />
pool name is: rpool<br />
<br />
extlinux.conf:<br />
<br />
<console><br />
LABEL funtoo<br />
MENU LABEL Funtoo 3.7.1-ALL<br />
KERNEL /boot/vmlinuz-3.7.1-ALL<br />
INITRD /boot/initrd-3.7.1-ALL.img<br />
APPEND pool_name=rpool<br />
</console><br />
<br />
=== genkernel ===<br />
<br />
<console><br />
# ##i##emerge -av sys-kernel/genkernel<br />
# ##i##genkernel --zfs initramfs<br />
</console><br />
<br />
Example: <br />
kernel name is: vmlinuz-3.7.1-ALL<br />
initramfs name is: initramfs-genkernel-x86_64-3.7.1-ALL<br />
pool name is: rpool<br />
<br />
extlinux.conf:<br />
<br />
<console><br />
LABEL funtoo<br />
MENU LABEL Funtoo 3.7.1-ALL<br />
KERNEL /boot/vmlinuz-3.7.1-ALL<br />
INITRD /boot/initramfs-genkernel-x86_64-3.7.1-ALL<br />
APPEND real_root=ZFS=rpool/ROOT/funtoo dozfs=force<br />
</console><br />
<br />
== Final configuration ==<br />
<br />
=== Add the zfs tools to openrc ===<br />
<br />
<console><br />
# ##i##rc-update add zfs boot<br />
# ##i##rc-update add zfs-shutdown shutdown<br />
</console><br />
<br />
=== Add filesystems to /etc/fstab ===<br />
<br />
<console><br />
# ##i##nano /etc/fstab<br />
<br />
# <fs> <mountpoint> <type> <opts> <dump/pass><br />
<br />
/dev/sda1 /boot ext4 defaults 1 2<br />
/dev/zvol/rpool/swap none swap sw 0 0<br />
</console><br />
<br />
=== Clean up and reboot ===<br />
We are almost done, we are just going to clean up and unmount whatever we mounted and get out.<br />
<br />
<console><br />
Delete the stage3/portage tarballs you downloaded earlier so they don't take up space.<br />
# ##i##cd /<br />
# ##i##rm stage3-latest.tar.xz<br />
# ##i##rm /usr/portage-latest.tar.xz<br />
<br />
Get out of the chroot environment<br />
# ##i##exit<br />
<br />
Unmount all the kernel filesystem stuff and boot<br />
# ##i##cd /mnt/funtoo<br />
# ##i##umount proc dev sys boot<br />
<br />
Turn off the swap<br />
# ##i##swapoff /dev/zvol/rpool/swap<br />
<br />
Export the zpool<br />
# ##i##cd /<br />
# ##i##zpool export -f rpool<br />
<br />
Reboot<br />
# ##i##reboot<br />
</console><br />
<br />
and that should be enough to get your system to boot on ZFS.<br />
<br />
== Extra: After reboot ==<br />
<br />
After you restart your machine and your inside your desktop, continue to set up anything you need in terms of /etc configurations. Once you have everything the way you like it, take a snapshot of your system. You will be using this snapshot to revert back to this state if anything ever happens to your system down the road. The snapshots are cheap, and almost instant. To take the snapshot of your rootfs, type the following:<br />
<br />
<console><br />
# ##i##zfs snapshot rpool/ROOT/funtoo@install<br />
</console><br />
<br />
To see if your snapshot was taken, type:<br />
<br />
<console><br />
# ##i##zfs list -t snapshot<br />
</console><br />
<br />
If your machine ever fails and you need to get back to this state, just type:<br />
<br />
<console><br />
# ##i##zfs rollback rpool/ROOT/funtoo@install<br />
</console><br />
<br />
Enjoy your new install on ZFS :)</div>Oleghttp://www.funtoo.org/wiki/ZFS_Install_GuideZFS Install Guide2012-12-30T08:35:55Z<p>Oleg: /* Create the zfs datasets */</p>
<hr />
<div>This tutorial will show you how to install Funtoo on ZFS (rootfs).<br />
<br />
This tutorial is meant to be an "overlay" over the [[Funtoo_Linux_Installation|Regular Funtoo Installation]]. Follow the normal installation and only use this guide for steps 2, 3, and 8.<br />
<br />
== Setting up your environment ==<br />
In order for us to install Funtoo on ZFS, you will need an environment that provides the ZFS userspace tools. We will be downloading two things, System Rescue CD 3.1.2, and the zfs srm (System Rescue Module). This is just a file that when combined with System Rescue CD, gives you ZFS functionality.<br />
<br />
[https://sourceforge.net/projects/systemrescuecd/files/sysresccd-x86/3.1.2/systemrescuecd-x86-3.1.2.iso/download Download System Rescue CD 3.1.2]<br />
<br />
[http://jonathanvasquez.com/files/sysresccd/3.1.2/zfs-3.2.34-std312-amd64.tar.bz2 Download the ZFS System Rescue Module]<br />
<br />
<pre><br />
Name: SystemRescueCd-x86-3.1.2 (350 MiB)<br />
Release Date: 2012-12-05<br />
<br />
md5sum 3c1ddfe5f26bb2f979a2ed9dfb504ee3<br />
sha1sum 217cf7a81380d894b2433c59451787c16bc0af2f<br />
sha256sum ec0a995875e64ff9816a043737e5cbbb689b7f596b48679116f0a779f3dce673<br />
<br />
Name: zfs-3.2.34-std312-amd64.tar.bz2<br />
md5sum 448d3eb40eb0c253962baa423a072103<br />
</pre><br />
<br />
Once you place the iso on your usb flash drive, extract the modules from the tarball, and place the .srm and .md5 at the root of your usb. Further instructions can be found [[Creating_System_Rescue_CD_Modules#Using_the_prebuilt_srm|here]]. <br />
<br />
We will now start to partition the system. Open up a terminal, and type in the following (We will assume it's a fresh drive for simplicity).<br />
<br />
== Creating partitions ==<br />
<br />
We will be creating two partitions, /boot, and the remaining disk space will be for ZFS.<br />
<br />
(All commands will be ran as root).<br />
<br />
=== fdisk (MBR Style) ===<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M ↵<br />
</console><br />
<br />
'''Create Partition 2''' (ZFS):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
<br />
Command: ##i##t ↵<br />
Partition number: ##i##2 ↵<br />
Hex code (type L to list codes): ##i##bf ↵<br />
<br />
Command: ##i##p ↵<br />
<br />
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes<br />
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors<br />
Units = sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
Disk identifier: 0x3e954df7<br />
<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 2048 514047 256000 83 Linux<br />
/dev/sda2 514048 1953525167 976505560 bf Solaris<br />
<br />
</console><br />
<br />
=== gdisk (GPT Style) ===<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M ↵<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
'''Create Partition 2''' (BIOS Boot Partition):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+32M ↵<br />
Hex Code: ##i##EF02 ↵<br />
</console><br />
<br />
{{fancyimportant|Only make the above BIOS Boot Partition if you are using GRUB 2 on GPT. If you are using the extlinux bootloader, this partition is not necessary. The below instructions continue as if you did not create this partition and assumes you are using extlinux as the bootloader.}}<br />
<br />
'''Create Partition 2''' (ZFS):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
Hex Code: ##i##bf01 ↵<br />
<br />
Command: ##i##p ↵<br />
Disk /dev/sda: 1953525168 sectors, 931.5 GiB<br />
Logical sector size: 512 bytes<br />
Disk identifier (GUID): C0C1E56A-B24F-492F-95DB-2E227676F228<br />
Partition table holds up to 128 entries<br />
First usable sector is 34, last usable sector is 1953525134<br />
Partitions will be aligned on 2048-sector boundaries<br />
Total free space is 2014 sectors (1007.0 KiB)<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 514047 250.0 MiB 8300 Linux filesystem<br />
2 514048 1953525134 931.3 GiB BF01 Solaris /usr & Mac ZFS<br />
<br />
</console><br />
<br />
=== Format your boot volume ===<br />
<br />
<console><br />
# ##i##mkfs.ext4 /dev/sda1<br />
</console><br />
<br />
=== Create the zpool ===<br />
We will first create the pool. The pool will be named `rpool` and the disk will be aligned to 4096 (using ashift=12)<br />
<br />
<console><br />
# ##i##zpool create -f -o ashift=12 -o cachefile= -O compression=on -m none -R /mnt/funtoo rpool /dev/sda2<br />
</console><br />
<br />
=== Create the zfs datasets ===<br />
We will now create some datasets. For this installation, we will create a small but future proof amount of datasets. We will have a dataset for the OS (/), /home, /var, /usr/portage, /usr/src, and your swap.<br />
<br />
<console><br />
Create some empty containers for organization purposes, and make the dataset that will hold /<br />
# ##i##zfs create -o mountpoint=none rpool/ROOT<br />
# ##i##zfs create -o mountpoint=/ rpool/ROOT/funtoo<br />
<br />
Optional datasets. /usr/portage, /usr/src, /var<br />
# ##i##zfs create -o mountpoint=none rpool/FUNTOO<br />
# ##i##zfs create -o mountpoint=/usr/portage -o compression=off rpool/FUNTOO/portage<br />
# ##i##zfs create -o mountpoint=/usr/portage/distfiles -o compression=off rpool/FUNTOO/distfiles<br />
# ##i##zfs create -o mountpoint=/usr/src rpool/FUNTOO/src<br />
# ##i##zfs create -o mountpoint=/var rpool/FUNTOO/var<br />
<br />
Optional but recommended dataset for /home<br />
# ##i##zfs create -o mountpoint=/home rpool/HOME<br />
# ##i##zfs create -o mountpoint=/root rpool/HOME/root<br />
</console><br />
<br />
=== Create your swap dataset ===<br />
<br />
'''Make your swap +1G greater than your RAM. An 8G machine would have 9G of RAM (This is kinda big though).'''<br />
<br />
<console><br />
# ##i##zfs create -o sync=always -o primarycache=metadata -o secondarycache=none -V 9G rpool/swap<br />
</console><br />
<br />
=== Format your swap dataset ===<br />
<br />
<console><br />
# ##i##mkswap -f /dev/zvol/rpool/swap<br />
# ##i##swapon /dev/zvol/rpool/swap<br />
</console><br />
<br />
Alright that finishes the creation of the zpool and zfs datasets. <br />
<br />
Check to make sure everything appears fine:<br />
<br />
<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
Copy the zpool.cache file to your new environment.<br />
<br />
<console><br />
# ##i##mkdir -p /mnt/funtoo/etc/zfs<br />
# ##i##cp /etc/zfs/zpool.cache /mnt/funtoo/etc/zfs<br />
</console><br />
<br />
Make an empty mtab file<br />
<br />
<console><br />
# ##i##touch /mnt/funtoo/etc/mtab<br />
</console><br />
<br />
Now we will continue to install funtoo.<br />
<br />
== Installing Funtoo ==<br />
<br />
Make a directory for your boot partition and mount it<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo/boot<br />
# ##i##mount /dev/sda1 /mnt/funtoo/boot<br />
</console><br />
<br />
Everything is currently mounted in /mnt/funtoo. <br />
[[Funtoo_Linux_Installation|So download and install the funtoo stage3 and continue installation as normal.]]<br />
<br />
Then chroot into your new funtoo environment:<br />
<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
# ##i##mount --bind /proc ./proc<br />
# ##i##mount --bind /dev ./dev<br />
# ##i##mount --bind /sys ./sys<br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l<br />
</console><br />
<br />
and finally sync your portage tree<br />
<br />
<console><br />
# ##i##emerge --sync<br />
</console><br />
<br />
<br />
== Kernel Configuration ==<br />
<br />
Tested with kernel 3.2.34, 3.7.1.<br />
<br />
When you get up to the kernel, make sure that you disable the CFQ scheduler, and turn<br />
on No-op (It's the default one once you disable all schedulers). The reason for this is because ZFS has its<br />
own scheduler and the CFQ one conflicts with it.<br />
<br />
Go to your kernel config, and make sure you have the following: (there should be a /usr/src/linux symlink as well)<br />
<br />
<pre>ZLIB_INFLATE/DEFLATE must be compiled into the kernel (not as a module).<br />
> ZLIB_INFLATE [=y], ZLIB_DEFLATE [=y]<br />
<br />
General setup ---><br />
> [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support<br />
> () Initramfs source file(s)<br />
<br />
[*] Enable loadable module support ---><br />
[*] Module unloading<br />
<br />
Enable the block layer ---><br />
IO Schedulers ---><br />
< > Deadline I/O scheduler<br />
< > CFQ I/O scheduler<br />
Default I/O scheduler (No-op)<br />
<br />
Device Drivers ---><br />
> Generic Driver Options ---><br />
>> [*] Maintain a devtmpfs filesystem to mount at /dev<br />
>> [*] Automount devtmpfs at /dev, after the kernel mounted the rootfs<br />
<br />
* All other drivers required to see your PATA/SATA drives must be compiled in.<br />
</pre><br />
<br />
Continue and compile/install your kernel:<br />
<br />
<console><br />
# ##i##make bzImage modules<br />
# ##i##make install<br />
# ##i##make modules_install<br />
</console><br />
<br />
== Installing the ZFS userspace tools ==<br />
<br />
<console><br />
# ##i##emerge -av =sys-kernel/spl =sys-fs/zfs =sys-fs/zfs-kmod<br />
</console><br />
<br />
Check to make sure that the zfs tools are working, the zpool.cache file that you copied before should be<br />
displayed.<br />
<br />
<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
If everything worked, continue.<br />
<br />
== Create the initramfs ==<br />
<br />
There are two ways to do this, you can use genkernel, or you can use my zfs initramfs creator. I will<br />
show you both.<br />
<br />
=== Bliss Initramfs Creator ===<br />
<br />
Make sure that you have cpio installed (Funtoo has this by default)<br />
Make sure you compile sys-apps/busybox with the static flag.<br />
<br />
<console><br />
# ##i##echo "sys-apps/busybox static" >> /etc/portage/package.use<br />
# ##i##emerge -av sys-apps/busybox<br />
</console><br />
<br />
Clone my creator which is located at: git://github.com/fearedbliss/Bliss-Initramfs-Creator.github<br />
<br />
<console><br />
# ##i##git clone git://github.com/fearedbliss/Bliss-Initramfs-Creator.git<br />
</console><br />
<br />
Then go into this new directory, run the script as root, and place it into /boot<br />
<br />
<console><br />
# ##i##cd Bliss-Initramfs-Creator<br />
# ##i##./createInit<br />
# ##i##mv initrd-<kernel_name>.img /boot<br />
</console><br />
<br />
'''<kernel_name>''' is the name of what you selected in the initramfs creator, and the name of the outputted file.<br />
<br />
Once you do this just go to your bootloader config, and add it in there.<br />
<br />
Example: <br />
kernel name is: vmlinuz-3.7.1-ALL<br />
initramfs name is: initrd-3.7.1-ALL.img<br />
pool name is: rpool<br />
<br />
extlinux.conf:<br />
<br />
<console><br />
LABEL funtoo<br />
MENU LABEL Funtoo 3.7.1-ALL<br />
KERNEL /boot/vmlinuz-3.7.1-ALL<br />
INITRD /boot/initrd-3.7.1-ALL.img<br />
APPEND pool_name=rpool<br />
</console><br />
<br />
=== genkernel ===<br />
<br />
<console><br />
# ##i##emerge -av sys-kernel/genkernel<br />
# ##i##genkernel --zfs initramfs<br />
</console><br />
<br />
Example: <br />
kernel name is: vmlinuz-3.7.1-ALL<br />
initramfs name is: initramfs-genkernel-x86_64-3.7.1-ALL<br />
pool name is: rpool<br />
<br />
extlinux.conf:<br />
<br />
<console><br />
LABEL funtoo<br />
MENU LABEL Funtoo 3.7.1-ALL<br />
KERNEL /boot/vmlinuz-3.7.1-ALL<br />
INITRD /boot/initramfs-genkernel-x86_64-3.7.1-ALL<br />
APPEND real_root=ZFS=rpool/ROOT/funtoo dozfs=force<br />
</console><br />
<br />
== Final configuration ==<br />
<br />
=== Add the zfs tools to openrc ===<br />
<br />
<console><br />
# ##i##rc-update add zfs boot<br />
</console><br />
<br />
=== Add filesystems to /etc/fstab ===<br />
<br />
<console><br />
# ##i##nano /etc/fstab<br />
<br />
# <fs> <mountpoint> <type> <opts> <dump/pass><br />
<br />
/dev/sda1 /boot ext4 defaults 1 2<br />
/dev/zvol/rpool/swap none swap sw 0 0<br />
</console><br />
<br />
=== Clean up and reboot ===<br />
We are almost done, we are just going to unmount whatever we mounted and get out.<br />
<br />
<console><br />
Get out of the chroot environment<br />
# ##i##exit<br />
<br />
Unmount all the kernel filesystem stuff and boot<br />
# ##i##cd /mnt/funtoo<br />
# ##i##umount proc dev sys boot<br />
<br />
Turn off the swap<br />
# ##i##swapoff /dev/zvol/rpool/swap<br />
<br />
Export the zpool<br />
# ##i##cd /<br />
# ##i##zpool export -f rpool<br />
<br />
Reboot<br />
# ##i##reboot<br />
</console><br />
<br />
and that should be enough to get your system to boot on ZFS.<br />
<br />
== Extra: After reboot ==<br />
<br />
After you restart your machine and your inside your desktop, continue to set up anything you need in terms of /etc configurations. Once you have everything the way you like it, take a snapshot of your system. You will be using this snapshot to revert back to this state if anything ever happens to your system down the road. The snapshots are cheap, and almost instant. To take the snapshot of your rootfs, type the following:<br />
<br />
<console><br />
# ##i##zfs snapshot rpool/ROOT/funtoo@install<br />
</console><br />
<br />
To see if your snapshot was taken, type:<br />
<br />
<console><br />
# ##i##zfs list -t snapshot<br />
</console><br />
<br />
If your machine ever fails and you need to get back to this state, just type:<br />
<br />
<console><br />
# ##i##zfs rollback rpool/ROOT/funtoo@install<br />
</console><br />
<br />
Enjoy your new install on ZFS :)</div>Oleghttp://www.funtoo.org/wiki/ZFS_Install_GuideZFS Install Guide2012-12-27T15:28:01Z<p>Oleg: </p>
<hr />
<div>This tutorial will show you how to install Funtoo on ZFS. In order for us to install Funtoo on ZFS,<br />
you will need an environment that provides the ZFS userspace tools. System Rescue CD 2.5.1 had the ZFS<br />
tools but they were removed. Thus we will be using the Gentoo Live DVD 12/12/2012 - End of the World Edition.<br />
This Live DVD does not have `gptfdisk`. So if you need that application to create GPT partitions, you will<br />
need to emerge it.<br />
<br />
This tutorial is meant to be an "overlay" over the [[Funtoo_Linux_Installation|Regular Funtoo Installation]]. Follow the normal installation and only use this guide for steps 2, 3, and 8.<br />
<br />
[http://ftp.snt.utwente.nl/pub/os/linux/gentoo/releases/amd64/20121221/ Download the Gentoo LiveDVD]<br />
<br />
<pre><br />
# MD5 HASH<br />
e86da868be423283ec167725390faefc livedvd-amd64-multilib-20121221.iso<br />
afbbcfc4c440ef5857a9144ab1e18251 livedvd-amd64-multilib-20121221.iso.CONTENTS<br />
26cde567e977ef1f4645f2f33dbad39b livedvd-amd64-multilib-20121221.iso.CONTENTS-squashfs.gz<br />
38f0954203934175f751fe15ab80891c livedvd-amd64-multilib-20121221.iso.CREDITS<br />
8becbfcecaa8423eaa196b544be9fa5a livedvd-amd64-multilib-20121221.iso.PACKAGES<br />
</pre><br />
<br />
Once you burn the DVD and boot it, we will start to partition the system. Open up a terminal, and type<br />
in the following (We will assume it's a fresh drive for simplicity).<br />
<br />
== Creating partitions ==<br />
<br />
We will be creating two partitions, /boot, and the remaining disk space will be for ZFS.<br />
<br />
(All commands will be ran as root).<br />
<br />
=== fdisk (MBR Style) ===<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command (m for help): ##i##n<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M<br />
</console><br />
<br />
'''Create Partition 2''' (swap):<br />
<br />
Make this partition twice the amount of RAM you have.<br />
<br />
<console><br />
Command (m for help): ##i##n<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+4G<br />
<br />
Command (m for help): ##i##t<br />
Partition number (1-4): ##i##2<br />
Hex code (type L to list codes): ##i##82<br />
</console><br />
<br />
'''Create Partition 3''' (ZFS):<br />
<br />
<console><br />
Command (m for help): ##i##n<br />
Partition type: ##i##↵<br />
Partition number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
<br />
Command (m for help): ##i##t<br />
Partition number (1-4): ##i##3<br />
Hex code (type L to list codes): ##i##bf<br />
<br />
Command (m for help): ##i##p<br />
<br />
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes<br />
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors<br />
Units = sectors of 1 * 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 512 bytes<br />
I/O size (minimum/optimal): 512 bytes / 512 bytes<br />
Disk identifier: 0x390225b5<br />
<br />
Device Boot Start End Blocks Id System<br />
<br />
/dev/sda1 2048 514047 256000 83 Linux<br />
/dev/sda2 514048 8902655 4194304 82 Linux swap / Solaris<br />
/dev/sda3 8902656 1953525167 972311256 bf Solaris<br />
</console><br />
<br />
=== gdisk (GPT Style) ===<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+250M<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
'''Create Partition 2''' (swap):<br />
<br />
<console><br />
Command: ##i##n<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+4G<br />
Hex Code: ##i##8200<br />
</console><br />
<br />
'''Create Partition 3''' (ZFS):<br />
<br />
<console><br />
Command: ##i##n<br />
Partition Number: ##i##↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵<br />
Hex Code: ##i##bf01<br />
<br />
Command (? for help): ##i##p<br />
Disk /dev/sda: 1953525168 sectors, 931.5 GiB<br />
Logical sector size: 512 bytes<br />
Disk identifier (GUID): 5A4D6576-FEF4-4693-B48B-C390FF3B1077<br />
Partition table holds up to 128 entries<br />
First usable sector is 34, last usable sector is 1953525134<br />
Partitions will be aligned on 2048-sector boundaries<br />
Total free space is 2014 sectors (1007.0 KiB)<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 514047 250.0 MiB 8300 Linux filesystem<br />
2 514048 8902655 4.0 GiB 8200 Linux swap<br />
3 8902656 1953525134 927.3 GiB BF01 Solaris /usr & Mac ZFS<br />
</console><br />
<br />
=== Format your boot volume ===<br />
<br />
<console><br />
# ##i##mkfs.ext4 /dev/sda1<br />
</console><br />
<br />
=== Format your swap partition ===<br />
<br />
<console><br />
# ##i##mkswap -f /dev/sda2<br />
# ##i##swapon /dev/sda2<br />
</console><br />
<br />
=== Create the zpool ===<br />
We will first create the pool. The pool will be named `rpool` and the disk will be aligned to 4096 (using ashift=12)<br />
<br />
<console><br />
# ##i##zpool create -f -o ashift=12 -o cachefile= -m none -R /mnt/funtoo rpool /dev/sda3<br />
</console><br />
<br />
=== Create the zfs datasets ===<br />
We will now create some datasets. For this installation, it will just be a basic dataset that has only /. You can create more datasets depending on your needs as you become familiar with ZFS.<br />
<br />
<console><br />
# ##i##zfs create -o mountpoint=none rpool/ROOT<br />
# ##i##zfs create -o mountpoint=/ rpool/ROOT/funtoo<br />
</console><br />
<br />
Alright that finishes the creation of the zpool and zfs datasets. <br />
<br />
Check to make sure everything appears fine:<br />
<br />
<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
Copy the zpool.cache file to your new environment.<br />
<br />
<console><br />
# ##i##mkdir -p /mnt/funtoo/etc/zfs<br />
# ##i##cp /etc/zfs/zpool.cache /mnt/funtoo/etc/zfs<br />
</console><br />
<br />
Make an empty mtab file<br />
<br />
<console><br />
# ##i##touch /mnt/funtoo/etc/mtab<br />
</console><br />
<br />
Now we will continue to install funtoo.<br />
<br />
== Installing Funtoo ==<br />
<br />
Make a directory for your boot partition and mount it<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo/boot<br />
# ##i##mount /dev/sda1 /mnt/funtoo/boot<br />
</console><br />
<br />
Everything is currently mounted in /mnt/funtoo. <br />
[[Funtoo_Linux_Installation|So download and install the funtoo stage3 and continue installation as normal.]]<br />
<br />
Then chroot into your new funtoo environment:<br />
<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
# ##i##mount --bind /proc ./proc<br />
# ##i##mount --bind /dev ./dev<br />
# ##i##mount --bind /sys ./sys<br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l<br />
</console><br />
<br />
and finally sync your portage tree<br />
<br />
<console><br />
# ##i##emerge --sync<br />
</console><br />
<br />
<br />
== Kernel Configuration ==<br />
<br />
Tested with kernel 3.7.1.<br />
<br />
When you get up to the kernel, make sure that you disable the CFQ scheduler, and turn<br />
on No-op (It's the default one once you disable all schedulers). The reason for this is because ZFS has its<br />
own scheduler and the CFQ one conflicts with it.<br />
<br />
Go to your kernel config, and make sure you have the following: (there should be a /usr/src/linux symlink as well)<br />
<br />
<pre><br />
General setup ---><br />
[*] Initial RAM filesystem and RAM disk (initramfs/initrd) support<br />
<br />
[*] Enable loadable module support ---><br />
[*] Module unloading<br />
<br />
Enable the block layer ---><br />
IO Schedulers ---><br />
< > Deadline I/O scheduler<br />
< > CFQ I/O scheduler<br />
Default I/O scheduler (No-op)<br />
<br />
Device Drivers ---><br />
Generic Driver Options ---><br />
[*] Maintain a devtmpfs filesystem to mount at /dev<br />
[*] Automount devtmpfs at /dev, after the kernel mounted the rootfs<br />
</pre><br />
<br />
'''Very important, make sure that ZLIB_DEFLATE is compiled as a module.'''<br />
<br />
'''ZLIB_INFLATE [=y], ZLIB_DEFLATE [=m]'''<br />
<br />
'''Anything required to see your hard drives should be compiled into the kernel'''<br />
'''This includes all filesystem drivers etc'''<br />
<br />
Continue and compile/install your kernel:<br />
<br />
<console><br />
# ##i##make bzImage modules<br />
# ##i##make install<br />
# ##i##make modules_install<br />
</console><br />
<br />
== Installing the ZFS userspace tools ==<br />
<br />
<console><br />
# ##i##emerge -av =sys-kernel/spl =sys-fs/zfs =sys-fs/zfs-kmod<br />
</console><br />
<br />
Check to make sure that the zfs tools are working, the zpool.cache file that you copied before should be<br />
displayed.<br />
<br />
<console><br />
# ##i##zpool status<br />
# ##i##zfs list<br />
</console><br />
<br />
If everything worked, continue.<br />
<br />
== Create the initramfs ==<br />
<br />
There are two ways to do this, you can use genkernel, or you can use my zfs initramfs creator. I will<br />
show you both.<br />
<br />
=== Bliss Initramfs Creator ===<br />
<br />
Make sure that you have cpio installed (Funtoo has this by default)<br />
Make sure you compile sys-apps/busybox with the static flag.<br />
<br />
<console><br />
# ##i##echo "sys-apps/busybox static" >> /etc/portage/package.use<br />
# ##i##emerge -av sys-apps/busybox<br />
</console><br />
<br />
Clone my creator which is located at: git://github.com/fearedbliss/Bliss-Initramfs-Creator.github<br />
<br />
<console><br />
# ##i##git clone git://github.com/fearedbliss/Bliss-Initramfs-Creator.git<br />
</console><br />
<br />
Then go into this new directory, run the script as root, and place it into /boot<br />
<br />
<console><br />
# ##i##cd Bliss-Initramfs-Creator<br />
# ##i##./createInit<br />
# ##i##mv initrd-zfs.img /boot<br />
</console><br />
<br />
Once you do this just go to your bootloader config, and add it in there.<br />
<br />
Example: <br />
kernel name is: vmlinuz-3.7.1-ALL<br />
initramfs name is: initrd-zfs.img<br />
pool name is: rpool<br />
<br />
extlinux.conf:<br />
<br />
<console><br />
LABEL funtoo<br />
MENU LABEL Funtoo 3.7.1-ALL<br />
KERNEL /boot/vmlinuz-3.7.1-ALL<br />
INITRD /boot/initrd-zfs.img<br />
APPEND pool_name=rpool<br />
</console><br />
<br />
=== genkernel ===<br />
<br />
<console><br />
# ##i##emerge -av sys-kernel/genkernel<br />
# ##i##genkernel --zfs initramfs<br />
</console><br />
<br />
Example: <br />
kernel name is: vmlinuz-3.7.1-ALL<br />
initramfs name is: initramfs-genkernel-x86_64-3.7.1-ALL<br />
pool name is: rpool<br />
<br />
extlinux.conf:<br />
<br />
<console><br />
LABEL funtoo<br />
MENU LABEL Funtoo 3.7.1-ALL<br />
KERNEL /boot/vmlinuz-3.7.1-ALL<br />
INITRD /boot/initramfs-genkernel-x86_64-3.7.1-ALL<br />
APPEND real_root=ZFS=rpool/ROOT/funtoo dozfs=force<br />
</console><br />
<br />
== Final configuration ==<br />
<br />
=== Add the zfs tools to openrc ===<br />
<br />
<console><br />
# ##i##rc-update add zfs boot<br />
</console><br />
<br />
=== Add filesystems to /etc/fstab ===<br />
<br />
<console><br />
# ##i##nano /etc/fstab<br />
<br />
# <fs> <mountpoint> <type> <opts> <dump/pass><br />
<br />
/dev/sda1 /boot ext4 defaults 1 2<br />
/dev/sda2 none swap sw 0 0<br />
</console><br />
<br />
That should be enough to get your system to boot on ZFS.<br />
<br />
== Extra: After reboot ==<br />
<br />
After you restart your machine and your inside your desktop, continue to set up anything you need in terms of /etc configurations. Once you have everything the way you like it, take a snapshot of your system. You will be using this snapshot to revert back to this state if anything ever happens to your system down the road. The snapshots are cheap, and almost instant. To take the snapshot of your rootfs, type the following:<br />
<br />
<console><br />
# ##i##zfs snapshot rpool/ROOT/funtoo@install<br />
</console><br />
<br />
To see if your snapshot was taken, type:<br />
<br />
<console><br />
# ##i##zfs list -t snapshot<br />
</console><br />
<br />
If your machine ever fails and you need to get back to this state, just type:<br />
<br />
<console><br />
# ##i##zfs rollback rpool/ROOT/funtoo@install<br />
</console><br />
<br />
Enjoy your new install on ZFS :)</div>Oleghttp://www.funtoo.org/wiki/Funtoo_Linux_InstallationFuntoo Linux Installation2012-12-24T23:45:36Z<p>Oleg: /* Chroot into Funtoo */</p>
<hr />
<div>== Introduction ==<br />
<br />
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.<br />
<br />
=== Additional Resources === <br />
<br />
This document was written to help you install Funtoo Linux as efficiently as possible, with a minimum number of distracting options regarding system configuration. <br />
<br />
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.<br />
<br />
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.<br />
<br />
== Installation Overview ==<br />
<br />
This is a basic overview of the Funtoo installation process:<br />
<br />
# [[#Live CD|Download and boot the live CD of your choice]].<br />
# [[#Prepare Hard Disk|Prepare your disk]].<br />
# [[#Creating filesystems|Create]] and [[#Mounting filesystems|mount]] filesystems.<br />
# [[#Installing the Stage 3 tarball|Install the Funtoo stage tarball]] of your choice.<br />
# [[#Chroot into Funtoo|Chroot into your new system]].<br />
# [[#Downloading the Portage tree|Download the Portage tree]].<br />
# [[#Configuring your system|Configure your system]] and [[#Configuring your network|network]].<br />
# [[#Configuring and installing the Linux kernel|Install a kernel]].<br />
# [[#Installing a Bootloader|Install a bootloader]].<br />
# [[#Finishing Steps|Complete final steps]].<br />
# [[#Restart your system|Reboot and enjoy]].<br />
<br />
=== Live CD ===<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Prepare Hard Disk ===<br />
==== Partitions ====<br />
<br />
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:<br />
<br />
===== GPT Partitions =====<br />
<br />
* Newer, preferred format for Linux systems<br />
* Supports 2 TB+ hard drives for booting<br />
* Supports hundreds of partitions per disk of any size<br />
* Requires legacy BIOS boot partition (~32 MB) to be created if system does not use EFI<br />
* Requires bootloader with support for GPT such as GRUB 2, EXTLINUX, or a patched version of GRUB Legacy<br />
<br />
===== MBR Partitions =====<br />
<br />
* Legacy, DOS partitioning scheme<br />
* Only 4 primary partitions per disk; after that, you must use "logical" partitions<br />
* Does not support 2 TB+ disks for booting<br />
* Compatible with certain problematic systems (such as the HP ProBook 4520)<br />
* Dual-boot with Windows for BIOS systems (Windows handle GPT only on true EFI systems, whatever version it is)<br />
* Multiple boot loader options, e.g. GRUB 2, GRUB Legacy, lilo<br />
<br />
{{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.}}<br />
<br />
==== Partitioning Using gdisk ====<br />
<br />
===== Notes Before We Begin =====<br />
<br />
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.<br />
<br />
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 <br />
'''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.<br />
<br />
Advanced users may be interested in the following topics:<br />
<br />
* [[GUID Booting Guide]]<br />
* [[Rootfs over encrypted lvm]]<br />
* [[Rootfs over encrypted lvm over raid-1 on GPT]]<br />
<br />
===== Using gdisk =====<br />
<br />
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:<br />
<br />
<console># ##i##gdisk /dev/sda</console><br />
You should find <tt>gdisk</tt> very similar to <tt>fdisk</tt>. Here is the partition table we want to end up with:<br />
<br />
<console>Command (? for help): ##i##p<br />
Disk /dev/sda: 234441648 sectors, 111.8 GiB<br />
Logical sector size: 512 bytes<br />
Disk identifier (GUID): A4E5208A-CED3-4263-BB25-7147DC426931<br />
Partition table holds up to 128 entries<br />
First usable sector is 34, last usable sector is 234441614<br />
Partitions will be aligned on 2048-sector boundaries<br />
Total free space is 2014 sectors (1007.0 KiB)<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 206847 500.0 MiB 8300 Linux filesystem<br />
2 206848 272383 32.0 MiB EF02 BIOS boot partition<br />
3 272384 8660991 4.0 GiB 8200 Linux swap<br />
4 8660992 234441614 107.7 GiB 8300 Linux filesystem<br />
<br />
Command (? for help): </console><br />
<br />
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.<br />
<br />
===== For new <tt>gdisk</tt> users =====<br />
<br />
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.<br />
<br />
Within <tt>gdisk</tt>, follow these steps:<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##1 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+500M ↵<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
'''Create Partition 2''' (GRUB):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##2 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+32M ↵<br />
Hex Code: ##i##EF02 ↵<br />
</console><br />
<br />
'''Create Partition 3''' (swap):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##3 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+4G ↵<br />
Hex Code: ##i##8200 ↵<br />
</console><br />
<br />
'''Create Partition 4''' (root):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##4 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵##!i## (for rest of disk)<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
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:<br />
<br />
'''Write Partition Table To Disk''':<br />
<br />
<console><br />
Command: ##i##w ↵<br />
Do you want to proceed? (Y/N): ##i##Y ↵<br />
</console><br />
<br />
The partition table will now be written to disk and <tt>gdisk</tt> will close.<br />
<br />
Now, your GPT/GUID partitions have been created, and will show up as the following ''block devices'' under Linux:<br />
<br />
* <tt>/dev/sda1</tt>, which will be used to hold the <tt>/boot</tt> filesystem, <br />
* <tt>/dev/sda2</tt>, which will be used directly by the new GRUB,<br />
* <tt>/dev/sda3</tt>, which will be used for swap space, and <br />
* <tt>/dev/sda4</tt>, which will hold your root filesystem.<br />
<br />
===== For Previous fdisk users =====<br />
<br />
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.<br />
<br />
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>.<br />
<br />
===== Partitioning Recommendations =====<br />
<br />
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>:<br />
<br />
{| {{table}} <br />
!Partition<br />
!Size<br />
!MBR Block Device (<tt>fdisk</tt>)<br />
!GPT Block Device (<tt>gdisk</tt>)<br />
!Filesystem<br />
!MBR Code<br />
!GPT Code<br />
|-<br />
|<tt>/boot</tt><br />
|500 MB<br />
|<tt>/dev/sda1</tt><br />
|<tt>/dev/sda1</tt><br />
|ext2<br />
|83<br />
|8300<br />
|-<br />
|GRUB boot loader partition<br />
|32 MB<br />
| ''not required for MBR''<br />
|<tt>/dev/sda2</tt><br />
|For GPT/GUID only, skip for MBR - no filesystem.<br />
|''N/A''<br />
|EF02<br />
|-<br />
|swap<br />
|2x RAM for low-memory systems and production servers; otherwise 2GB.<br />
|<tt>/dev/sda2</tt><br />
|<tt>/dev/sda3</tt><br />
|swap (default)<br />
|82<br />
|8200<br />
|-<br />
|<tt>/</tt> (root)<br />
|Rest of the disk, minimum of 10GB.<br />
|<tt>/dev/sda3</tt><br />
|<tt>/dev/sda4</tt><br />
|XFS recommended, alternatively ext4<br />
|83<br />
|8300<br />
|-<br />
|<tt>/home</tt> (optional) <br />
|User storage and media. Typically most of the disk.<br />
|<tt>/dev/sda4</tt> (if created)<br />
|<tt>/dev/sda5</tt> (if created)<br />
|XFS recommended, alternatively ext4<br />
|83<br />
|8300<br />
|-<br />
| LVM (optional)<br />
| If you want to create an LVM volume.<br />
| <tt>/dev/sda4</tt> (PV, if created)<br />
| <tt>/dev/sda5</tt> (PV, if created)<br />
| LVM PV<br />
| 8E<br />
| 8E00<br />
|}<br />
<br />
==== Creating filesystems ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<br />
<console><br />
# ##i##mke2fs -t ext2 /dev/sda1 <br />
# ##i##mkfs.xfs /dev/sda4<br />
# ##i##mkswap /dev/sda3<br />
# ##i##swapon /dev/sda3<br />
</console><br />
<br />
==== Mounting filesystems ====<br />
<br />
Mount the newly-created filesystems as follows, creating <tt>/mnt/funtoo</tt> as the installation mount point:<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo<br />
# ##i##mount /dev/sda4 /mnt/funtoo<br />
# ##i##mkdir /mnt/funtoo/boot<br />
# ##i##mount /dev/sda1 /mnt/funtoo/boot<br />
</console><br />
<br />
Optionally, if you have a separate filesystem for <tt>/home</tt> or anything else:<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo/home<br />
# ##i##mount /dev/sda5 /mnt/funtoo/home<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##chmod 1777 /mnt/funtoo/tmp<br />
</console><br />
<br />
=== Installing the Stage 3 tarball ===<br />
==== Stage 3 tarball ====<br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
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:<br />
<br />
<console><br />
# ##i##date<br />
Fri Jul 15 19:47:18 UTC 2011<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##date 071620002011<br />
Fri Jul 16 20:00:00 UTC 2011<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
# ##i##wget http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-64bit/generic_64/stage3-latest.tar.xz<br />
</console><br />
<br />
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.<br />
<br />
Once the stage is downloaded, extract the contents with the following command, substituting in the actual name of your stage 3 tarball:<br />
<console># ##i##tar xJpf stage3-latest.tar.xz</console><br />
<br />
{{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.}}<br />
<br />
=== Chroot into Funtoo ===<br />
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:<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
# ##i##mount --bind /proc proc<br />
# ##i##mount --bind /dev dev<br />
</console><br />
<br />
You'll also want to copy over <tt>resolv.conf</tt> in order to have proper DNS name resolution from inside the chroot:<br />
<console><br />
# ##i##cp /etc/resolv.conf etc<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l<br />
</console><br />
<br />
{{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.}}<br />
{{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.}}<br />
<br />
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:<br />
<console><br />
# ##i##export PS1="(chroot) $PS1"<br />
</console><br />
<br />
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.<br />
<br />
=== Downloading the Portage tree ===<br />
<br />
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]:<br />
<br />
<console><br />
(chroot) # ##i##emerge --sync<br />
</console><br />
<br />
{{fancynote|For an alternative way to do this, see [[Installing Portage From Snapshot]].}}<br />
<br />
=== Configuring your system ===<br />
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:<br />
<br />
{| {{table}}<br />
!File<br />
!Do I need to change it?<br />
!Description<br />
|-<br />
|<tt>/etc/fstab</tt><br />
|'''YES - required'''<br />
|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.<br />
|-<br />
|<tt>/etc/localtime</tt><br />
|''Maybe - recommended''<br />
|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) <br />
|-<br />
|<tt>/etc/make.conf<br/>/etc/portage/make.conf&nbsp;(new&nbsp;location)</tt><br />
|''Maybe - recommended''<br />
|Parameters used by gcc (compiler), portage, and make. It's a good idea to set MAKEOPTS. This is covered later in this document.<br />
|-<br />
|<tt>/etc/conf.d/hostname</tt><br />
|''Maybe - recommended''<br />
|Used to set system hostname. Set to the fully-qualified (with dots) name. Defaults to <tt>localhost</tt> if not set.<br />
|-<br />
|<tt>/etc/hosts</tt><br />
|''No''<br />
| You no longer need to manually set the hostname in this file. This file is automatically generated by <tt>/etc/init.d/hostname</tt>.<br />
|-<br />
|<tt>/etc/conf.d/keymaps</tt><br />
|Optional<br />
|Keyboard mapping configuration file (for console pseudo-terminals). Set if you have a non-US keyboard. See [[Funtoo Linux Localization]].<br />
|-<br />
|<tt>/etc/conf.d/hwclock</tt><br />
|Optional<br />
|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.<br />
|-<br />
|<tt>/etc/conf.d/modules</tt><br />
|Optional<br />
|Kernel modules to load automatically at system startup. Typically not required. See [[Additional Kernel Resources]] for more info.<br />
|-<br />
|<tt>profiles</tt><br />
|Optional<br />
|Some useful portage settings that may help speed up intial configuration.<br />
|}<br />
<br />
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]])<br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
==== /etc/fstab ====<br />
<br />
<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:<br />
<br />
<console><br />
(chroot) # ##i##nano -w /etc/fstab<br />
</console><br />
<br />
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.<br />
<br />
<pre><br />
# The root filesystem should have a pass number of either 0 or 1.<br />
# All other filesystems should have a pass number of 0 or greater than 1.<br />
#<br />
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.<br />
#<br />
# See the manpage fstab(5) for more information.<br />
#<br />
# <fs> <mountpoint> <type> <opts> <dump/pass><br />
<br />
/dev/sda1 /boot ext2 noatime 1 2<br />
/dev/sda3 none swap sw 0 0<br />
/dev/sda4 / xfs noatime 0 1<br />
#/dev/cdrom /mnt/cdrom auto noauto,ro 0 0<br />
</pre><br />
<br />
==== /etc/localtime ====<br />
<br />
<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. <br />
<br />
<pre><br />
(chroot) # ln -sf /usr/share/zoneinfo/America/Montreal /etc/localtime<br />
</pre><br />
<br />
The above sets the timezone to Eastern Time Canada. Go to <tt>/usr/share/zoneinfo</tt> to see which values to use.<br />
<br />
==== /etc/portage/make.conf ====<br />
<br />
{{fancynote|This file may also be found at /etc/make.conf. /etc/portage/make.conf is the new location.}}<br />
<br />
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:<br />
<br />
<pre><br />
MAKEOPTS="-j3" <br />
</pre><br />
<br />
If you are unsure about how many processors/threads you have then use /proc/cpuinfo to help you.<br />
<console><br />
(chroot) # ##i##grep "processor" /proc/cpuinfo | wc -l<br />
16<br />
</console><br />
<br />
Set MAKEOPTS to this number plus one:<br />
<br />
<pre><br />
MAKEOPTS="-j17"<br />
</pre><br />
<br />
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].<br />
<br />
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:<br />
<br />
<pre><br />
LINGUAS="fr"<br />
</pre><br />
<br />
==== /etc/conf.d/hwclock ====<br />
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.<br />
<console><br />
(chroot) # ##i##nano -w /etc/conf.d/hwclock<br />
</console><br />
<br />
==== Localization ====<br />
<br />
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]].<br />
<br />
==== Profiles ====<br />
<br />
[[Funtoo 1.0 Profile|Funtoo profiles]] are used to define defaults for Portage specific to your needs. There are 4 basic profile types: arch, build, [[Flavors and Mix-ins|flavor, and mix-ins]]:<br />
<br />
;arch: typically <tt>x86-32bit</tt> or <tt>x86-64bit</tt>, this defines the processor type and support of your system. This is defined when your stage was built and should not be changed.<br />
;build: defines whether your system is a <tt>current</tt>, <tt>stable</tt> or <tt>experimental</tt> build. <tt>current</tt> systems will have newer packages unmasked than <tt>stable</tt> systems.<br />
;flavor: defines the general type of system, such as <tt>server</tt> or <tt>desktop</tt>, and will set default USE flags appropriate for your needs.<br />
;mix-ins: define various optional settings that you may be interested in enabling.<br />
<br />
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.<br />
<br />
Remember that profiles can often be inherited. For example, the <tt>desktop</tt> flavor inherits the <tt>workstation</tt> flavor settings, which in turn inherits the <tt>X</tt> and <tt>audio</tt> mix-ins. You can view this by inspecting the <tt>parent</tt> files defined in each profile, which can be found in <tt>/usr/portage/profiles/funtoo/1.0/linux-gnu</tt>:<br />
<br />
<console><br />
(chroot) # ##i##cd /usr/portage/profiles/funtoo/1.0/linux-gnu/<br />
(chroot) # ##i##ls<br />
arch/ eapi make.defaults package.use/ packages.build use.force<br />
build/ flavor/ mix-ins/ package.use.mask/ parent <br />
(chroot) # ##i##cat flavor/desktop/parent <br />
../workstation<br />
../../mix-ins/print<br />
(chroot) # ##i##cat flavor/workstation/parent <br />
../core<br />
../../mix-ins/X<br />
../../mix-ins/audio<br />
../../mix-ins/dvd<br />
../../mix-ins/media<br />
../../mix-ins/console-extras<br />
(chroot) # <br />
</console><br />
<br />
To view installed profiles:<br />
<console><br />
(chroot) # ##i##eselect profile list<br />
</console><br />
<br />
Adding a profile is simple:<br />
<console><br />
(chroot) # ##i##eselect profile add 7<br />
</console><br />
<br />
remember if you add by string; add a 'gentoo:' to the beginning of the profile name ie:<br />
<console><br />
(chroot) # ##i## eselect profile add gentoo:funtoo/1.0/linux-gnu/mix-ins/console-extras<br />
</console><br />
<br />
=== Configuring and installing the Linux kernel ===<br />
<br />
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.<br />
<br />
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.<br />
<br />
{{fancyimportant|<tt>debian-sources</tt> with <tt>binary</tt> USE flag requires at least 12GB in /var/tmp}}<br />
<br />
<console><br />
(chroot) # ##i##echo "sys-kernel/debian-sources binary" >> /etc/portage/package.use<br />
(chroot) # ##i##emerge debian-sources<br />
</console><br />
<br />
All done!<br />
<br />
{{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>.}}<br />
<br />
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.<br />
<br />
The next step is to configure your boot loader so that your new kernel loads when the system boots.<br />
<br />
=== Installing a Bootloader ===<br />
<br />
==== Installing Grub ====<br />
<br />
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.<br />
<br />
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>.<br />
<br />
<console><br />
(chroot) # ##i##emerge boot-update<br />
</console><br />
<br />
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>. <br />
<br />
<tt>/etc/boot.conf</tt> should now look like this:<br />
<br />
<pre><br />
boot {<br />
generate grub<br />
default "Funtoo Linux genkernel"<br />
timeout 3 <br />
}<br />
<br />
"Funtoo Linux" {<br />
kernel bzImage[-v]<br />
# params += nomodeset<br />
}<br />
<br />
"Funtoo Linux genkernel" {<br />
kernel kernel[-v]<br />
initrd initramfs[-v]<br />
params += real_root=auto <br />
# params += nomodeset<br />
} <br />
</pre><br />
<br />
Please read <tt>man boot.conf</tt> for further details.<br />
<br />
===== Running grub-install and boot-update =====<br />
<br />
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:<br />
<br />
<console><br />
(chroot) # ##i##grub-install --no-floppy /dev/sda<br />
(chroot) # ##i##boot-update<br />
</console><br />
<br />
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.<br />
<br />
OK - your system should be ready to boot! Well, there are a few more loose ends...<br />
<br />
==== Installing Syslinux/Extlinux ====<br />
<br />
An alternate Bootloader is Extlinux, for installing it see the [[Extlinux|extlinux Guide]].<br />
<br />
=== Configuring your network ===<br />
<br />
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.<br />
<br />
==== Wi-Fi ====<br />
<br />
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:<br />
<br />
<console><br />
# ##i##emerge linux-firmware<br />
# ##i##emerge networkmanager<br />
# ##i##rc-update add NetworkManager default<br />
</console><br />
<br />
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.<br />
<br />
After you reboot into Funtoo Linux, you will be able to add a Wi-Fi connection this way:<br />
<br />
<console><br />
# ##i##addwifi -S wpa -K 'wifipassword' mywifinetwork<br />
</console><br />
<br />
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.<br />
<br />
==== Desktop (Wired Ethernet) ====<br />
<br />
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:<br />
<br />
<console><br />
# ##i##rc-update add dhcpcd default<br />
</console><br />
<br />
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.<br />
<br />
==== Server (Static IP) ====<br />
<br />
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.<br />
<br />
=== Finishing Steps ===<br />
<br />
==== Set your root password ====<br />
It's imperative that you set your root password before rebooting so that you can log in.<br />
<console><br />
(chroot) # ##i##passwd<br />
</console><br />
<br />
===Restart your system ===<br />
<br />
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.<br />
<br />
Leave the chroot, change directory to /, unmount your Funtoo partitions, and reboot.<br />
<console><br />
(chroot) # ##i##exit<br />
# ##i##cd /<br />
# ##i##umount /mnt/funtoo/boot /mnt/funtoo/dev /mnt/funtoo/proc /mnt/funtoo<br />
# ##i##reboot<br />
</console><br />
<br />
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!<br />
<br />
===Next Steps===<br />
<br />
To learn how to customize and start using Funtoo Linux, see [[Funtoo Linux First Steps]].<br />
<br />
If your system did not boot correctly, see [[Installation Troubleshooting]] for steps you can take to resolve the problem.<br />
<br />
[[Category:HOWTO]]<br />
[[Category:Install]]</div>Oleghttp://www.funtoo.org/wiki/ZFS_Install_GuideZFS Install Guide2012-12-24T23:44:25Z<p>Oleg: Created page with "WIP"</p>
<hr />
<div>WIP</div>Oleghttp://www.funtoo.org/wiki/WelcomeWelcome2012-12-04T11:24:10Z<p>Oleg: Reverted edits by MikeGreen (talk) to last revision by 65.204.229.11</p>
<hr />
<div><div style="float:right; width: 40%"><br />
{{#widget:Donate|blurb=Your support helps Funtoo grow! Donate Today!}}<br />
{{Litecoin|blurb=Check it out: Mine litecoins for Funtoo!}}<br />
<div class="boxy"><br />
=== Latest Commits: ===<br />
<ul><br />
<feed entries=7 url="https://github.com/funtoo/funtoo-overlay/commits/master.atom"><br />
<li>[{PERMALINK} <nowiki>{TITLE}</nowiki>]<br />
</feed><br />
</ul><br />
</div><br />
<br />
<div class="boxy"><br />
=== Featured Resources: ===<br />
<DynamicPageList><br />
category = Featured<br />
</DynamicPageList><br />
</div><br />
<br />
<div class="boxy2"><br />
=== [[image:Feed-icon-28x28.png|link=http://forums.funtoo.org/extern.php?action=feed&type=atom]] Latest Forum Posts ===<br />
<ul><br />
<feed entries=6 url="http://forums.funtoo.org/extern.php?action=feed&type=atom"><br />
<li>[{PERMALINK} <nowiki>{TITLE}</nowiki>]<br />
</feed><br />
</ul><br />
</div><br />
<br />
<div class="boxy2"><br />
=== [[image:Feed-icon-28x28.png|link=http://feeds.feedburner.com/planet_larry]] Planet Larry ===<br />
<ul><br />
<feed type="planet" entries=6 url="http://feeds.feedburner.com/planet_larry"><br />
<li>[{PERMALINK} <nowiki>{TITLE}</nowiki>]<br />
</feed><br />
</ul><br />
</div><br />
<br />
<br />
</div><br />
= Welcome to the Funtoo Wiki! =<br />
<br />
[[Funtoo Linux]] is a Linux-based operating system created by [[user:Drobbins|Daniel Robbins]], the creator and former Chief Architect of Gentoo Linux. <br />
<br />
Funtoo Linux is a Free software, or "Open Source" operating system. All distribution source code is freely available, and it can be used and distributed free of charge.<br />
<br />
== Meta-Distribution, Optimized ==<br />
<br />
Funtoo Linux is also a ''meta''-distribution, which means that it is built automatically from source code and is customized with the functionality that ''you'' want it to have, and ''without'' the unnecessary features and "bloat" that you want to avoid. <br />
<br />
In addition, a Funtoo Linux system is [[Download|optimized for your CPU]], and we offer optimized versions for ''Intel Core i7'', ''Intel Atom'', ''AMD Opteron'', and other processors and architectures. <br />
<br />
These combination of factors work together to create an extremely high-performance and flexible computing platform -- a platform where ''you'' are in control, and your system performs optimally. We believe that Funtoo Linux is the most ideal expression of how operating system technology "should" work, and we continually strive to make it better.<br />
<br />
== The Gentoo Ecosystem ==<br />
<br />
Our [[Core Team]] is focused on advancing the state-of-the-art in Linux distributions by developing our own improvements to Gentoo Linux, while remaining compatible with the upstream changes from the Gentoo Linux project. <br />
<br />
We are committed to maintaining high-levels of compatibility and collaboration with the Gentoo Linux project, and challenge ourselves to innovate while providing new approaches that can be easily leveraged by the Gentoo Community. We appreciate the support we receive from members of the Gentoo Community and strive to contribute back to the larger [[Gentoo Ecosystem]].<br />
<br />
== Ultimate Flexibility for Developers ==<br />
<br />
Does your Linux distribution allow multiple versions of <tt>php</tt>, <tt>[[python]]</tt> or <tt>ruby</tt> installed happily alongside each other? Funtoo Linux does. Are you tired of hand-building key packages from source to configure them exactly the way you want? Funtoo Linux allows you to tweak the build-time features of packages using handy things called USE variables. Other distributions are forced to either leave stuff out that you want, or include stuff you don't want.<br />
<br />
== Virtualization ==<br />
<br />
We support the [[OpenVZ]] project and build up-to-date Funtoo Linux OpenVZ containers that you can [[Download|download]]. Also see [[VagrantUp]] for a nice way to deploy VirtualBox-based Funtoo Linux systems. [[Metro]], our automated distro build tool, is capable of building OpenVZ, Linux VServer and [[Linux Containers]] (LXC) images. Funtoo Linux also makes an excellent virtualization host system for [[Xen]].<br />
<br />
== Features ==<br />
<br />
[[Funtoo Linux]] features native [[wikipedia:UTF-8|UTF-8]] support enabled by default, a [[wikipedia:Git (software)|git]]-based, [[Portage Tree|distributed Portage Tree]] and funtoo overlay, an enhanced [[Portage]] with more compact mini-manifest tree, automated imports of new [http://www.gentoo.org Gentoo] changes every 12 hours, [[GUID Booting Guide|GPT/GUID boot support]] and [[Boot-Update|streamlined boot configuration]], [[Funtoo Linux Networking|enhanced network configuration]], up-to-date [http://ftp.osuosl.org/pub/funtoo/funtoo-stable/ stable] and [http://ftp.osuosl.org/pub/funtoo/funtoo-current/ current] Funtoo [[Stage Tarball|stages]], all built using Funtoo's [[Metro]] build tool. We also offer Ubuntu Server, Debian, RHEL and Fedora-based [[Funtoo Linux Kernels|kernels]].<br />
<br />
Funtoo is currently supported on the following processor families :<br />
* PC-compatible, both 32 and 64-bit (''x86-32bit'', ''x86-64bit'')<br />
<br />
== Resources ==<br />
<br />
* Learn more about [[Funtoo Linux]].<br />
* Why you should [[Choose Funtoo]]: ...and how its different than other distros.<br />
* Visit [[:Category:Projects|Funtoo Linux Projects]] and also look at the stuff online for [[Metro]].<br />
* Learn [[:Category:Linux Core Concepts| Core Linux concepts]] from articles originally written by Daniel Robbins.<br />
<br />
=== Latest Funtoo News from Twitter ===<br />
<br />
<div class="tweets"><br />
<ul><br />
<feed entries=8 url="http://search.twitter.com/search.atom?q=from%3Afuntoo"><br />
<li>[{PERMALINK} <nowiki>{TITLE}</nowiki>]<br />
</feed><br />
</ul><br />
</div><br />
<br />
__NOTOC__<br />
__NOTITLE__<br />
<br />
[[Category:Funtoo|*]]<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
[[image:Feed-icon-28x28.png|link=http://bit.ly/UXJ87l|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/iWCDzp|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/UA0cBZ|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/XM0rQe|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/S0Ziyi|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/T4wd38|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/U2XEM4|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/QfQd68|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/QAPH4g|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/TkhyVx|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/WIlTnG|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/TluoBY|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/TlunxP|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/TluqK8|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/10JK6Jm|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/XM0NGl|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/WIm7Ls|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/T4wCTh|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/10JKl7t|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/TluvgP|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/TUqlJ0|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/Tb7Dhq|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/TkhKUN|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/V2Vcdb|2px]] [[image:Feed-icon-28x28.png|link=http://bit.ly/WImjua|2px]]</div>Oleghttp://www.funtoo.org/wiki/Linux_Fundamentals,_Part_2Linux Fundamentals, Part 22012-12-04T05:33:28Z<p>Oleg: Reverted edits by 117.240.182.23 (talk) to last revision by Big Fun</p>
<hr />
<div>== Before You Start ==<br />
<br />
=== About this tutorial ===<br />
Welcome to "Basic administration," the second of four tutorials designed to prepare you for the Linux Professional Institute's 101 exam. In this tutorial, we'll show you how to use regular expressions to search files for text patterns. Next, we'll introduce you to the Filesystem Hierarchy Standard (FHS), and then show you how to locate files on your system. Then, we'll show you how to take full control of Linux processes by running them in the background, listing processes, detaching processes from the terminal, and more. Next, we'll give you a whirlwind introduction to shell pipelines, redirection, and text processing commands. Finally, we'll introduce you to Linux kernel modules.<br />
<br />
This particular tutorial (Part 2) is ideal for those who have a good basic knowledge of bash and want to receive a solid introduction to basic Linux administration tasks. If you are new to Linux, we recommend that you complete [[Linux Fundamentals, Part 1|Part 1]] of this tutorial series first before continuing. For some, much of this material will be new, but more experienced Linux users may find this tutorial to be a great way of "rounding out" their basic Linux administration skills.<br />
<br />
For those who have taken the release 1 version of this tutorial for reasons other than LPI exam preparation, you probably don't need to take this one. However, if you do plan to take the exams, you should strongly consider reading this revised tutorial.<br />
<br />
== Regular Expressions ==<br />
<br />
=== What is a regular expression? ===<br />
A regular expression (also called a "regex" or "regexp") is a special syntax used to describe text patterns. On Linux systems, regular expressions are commonly used to find patterns of text, as well as to perform search-and-replace operations on text streams.<br />
<br />
=== Glob comparison ===<br />
As we take a look at regular expressions, you may find that regular expression syntax looks similar to the filename "globbing" syntax that we looked at in Part 1. However, don't let this fool you; their similarity is only skin deep. Both regular expressions and filename globbing patterns, while they may look similar, are fundamentally different beasts.<br />
<br />
=== The simple substring ===<br />
With that caution, let's take a look at the most basic of regular expressions, the simple substring. To do this, we're going to use <span style="color:green">grep</span>, a command that scans the contents of a file for a particular regular expression. <span style="color:green">grep</span> prints every line that matches the regular expression, and ignores every line that doesn't:<br />
<pre><br />
$ grep bash /etc/passwd<br />
operator:x:11:0:operator:/root:/bin/bash<br />
root:x:0:0::/root:/bin/bash<br />
ftp:x:40:1::/home/ftp:/bin/bash<br />
</pre><br />
Above, the first parameter to <span style="color:green">grep</span> is a regex; the second is a filename. <span style="color:green">grep</span> read each line in /etc/passwd and applied the simple substring regex bash to it, looking for a match. If a match was found, <span style="color:green">grep</span> printed out the entire line; otherwise, the line was ignored.<br />
<br />
=== Understanding the simple substring ===<br />
In general, if you are searching for a substring, you can just specify the text verbatim without supplying any "special" characters. The only time you'd need to do anything special would be if your substring contained a +, ., *, [, ], or \, in which case these characters would need to be enclosed in quotes and preceded by a backslash. Here are a few more examples of simple substring regular expressions:<br />
<br />
* /tmp (scans for the literal string /tmp)<br />
* "\[box\]" (scans for the literal string [box])<br />
* "\*funny\*" (scans for the literal string *funny*)<br />
* "ld\.so" (scans for the literal string ld.so)<br />
<br />
=== Metacharacters ===<br />
With regular expressions, you can perform much more complex searches than the examples we've looked at so far by taking advantage of metacharacters. One of these metacharacters is the . (a period), which matches any single character:<br />
<pre><br />
$ grep dev.sda /etc/fstab<br />
/dev/sda3 / reiserfs noatime,ro 1 1<br />
/dev/sda1 /boot reiserfs noauto,noatime,notail 1 2<br />
/dev/sda2 swap swap sw 0 0<br />
#/dev/sda4 /mnt/extra reiserfs noatime,rw 1 1<br />
</pre><br />
In this example, the literal text dev.sda didn't appear on any of the lines in /etc/fstab. However, grep wasn't scanning them for the literal dev.sda string, but for the dev.sda pattern. Remember that the . will match any single character. As you can see, the . metacharacter is functionally equivalent to how the ? metacharacter works in "glob" expansions.<br />
<br />
=== Using [] ===<br />
If we wanted to match a character a bit more specifically than ., we could use [ and ] (square brackets) to specify a subset of characters that should be matched:<br />
<pre><br />
$ grep dev.sda[12] /etc/fstab<br />
/dev/sda1 /boot reiserfs noauto,noatime,notail 1 2<br />
/dev/sda2 swap swap sw 0 0<br />
</pre><br />
As you can see, this particular syntactical feature works identically to the [] in "glob" filename expansions. Again, this is one of the tricky things about learning regular expressions -- the syntax is similar but not identical to "glob" filename expansion syntax, which often makes regexes a bit confusing to learn.<br />
<br />
=== Using [^] ===<br />
You can reverse the meaning of the square brackets by putting a ^ immediately after the [. In this case, the brackets will match any character that is not listed inside the brackets. Again, note that we use [^] with regular expressions, but [!] with globs:<br />
<pre><br />
$ grep dev.sda[^12] /etc/fstab<br />
/dev/sda3 / reiserfs noatime,ro 1 1<br />
#/dev/sda4 /mnt/extra reiserfs noatime,rw 1 1<br />
</pre><br />
<br />
=== Differing syntax ===<br />
It's important to note that the syntax inside square brackets is fundamentally different from that in other parts of the regular expression. For example, if you put a . inside square brackets, it allows the square brackets to match a literal ., just like the 1 and 2 in the examples above. In comparison, a literal . outside the square brackets is interpreted as a metacharacter unless prefixed by a \. We can take advantage of this fact to print a list of all lines in '''/etc/fstab''' that contain the literal string dev.sda by typing:<br />
<pre><br />
$ grep dev[.]sda /etc/fstab<br />
</pre><br />
Alternately, we could also type:<br />
<pre><br />
$ grep "dev\.sda" /etc/fstab<br />
</pre><br />
Neither regular expression is likely to match any lines in your '''/etc/fstab''' file.<br />
<br />
=== The "*" metacharacter ===<br />
Some metacharacters don't match anything in themselves, but instead modify the meaning of a previous character. One such metacharacter is * (asterisk), which is used to match zero or more repeated occurrences of the previous character. Note that this means that the * has a different meaning in a regex than it does with globs. Here are some examples, and play close attention to instances where these regex matches differ from globs:<br />
<br />
* ab*c matches abbbbc but not abqc (if a glob, it would match both strings -- can you figure out why?)<br />
* ab*c matches abc but not abbqbbc (again, if a glob, it would match both strings)<br />
* ab*c matches ac but not cba (if a glob, ac would not be matched, nor would cba)<br />
* b[cq]*e matches bqe and be (if a glob, it would match bqe but not be)<br />
* b[cq]*e matches bccqqe but not bccc (if a glob, it would match the first but not the second as well)<br />
* b[cq]*e matches bqqcce but not cqe (if a glob, it would match the first but not the second as well)<br />
* b[cq]*e matches bbbeee (this would not be the case with a glob)<br />
* .* will match any string. (if a glob, it would match any string starting with .)<br />
* foo.* will match any string that begins with foo (if a glob, it would match any string starting with the four literal characters foo..)<br />
<br />
Now, for a quick brain-twisting review: the line ac matches the regex ab*c because the asterisk also allows the preceding expression (b) to appear zero times. Again, it's critical to note that the * regex metacharacter is interpreted in a fundamentally different way than the * glob character.<br />
<br />
=== Beginning and end of line ===<br />
The last metacharacters we will cover in detail here are the ^ and $ metacharacters, used to match the beginning and end of line, respectively. By using a ^ at the beginning of your regex, you can cause your pattern to be "anchored" to the start of the line. In the following example, we use the ^# regex to match any line beginning with the # character:<br />
<pre><br />
$ grep ^# /etc/fstab<br />
# /etc/fstab: static file system information.<br />
#<br />
</pre><br />
<br />
=== Full-line regexes ===<br />
^ and $ can be combined to match an entire line. For example, the following regex will match a line that starts with the # character and ends with the . character, with any number of other characters in between:<br />
<pre><br />
$ grep '^#.*\.$' /etc/fstab<br />
# /etc/fstab: static file system information.<br />
</pre><br />
In the above example, we surrounded our regular expression with single quotes to prevent $ from being interpreted by the shell. Without the single quotes, the $ will disappear from our regex before grep even has a chance to take a look at it.<br />
<br />
== FHS and finding files ==<br />
<br />
=== Filesystem Hierarchy Standard ===<br />
The Filesystem Hierarchy Standard is a document that specifies the layout of directories on a Linux system. The FHS was devised to provide a common layout to simplify distribution-independent software development -- so that stuff is in generally the same place across Linux distributions. The FHS specifies the following directory tree (taken directly from the FHS specification):<br />
<br />
* / (the root directory)<br />
* /boot (static files of the boot loader)<br />
* /dev (device files)<br />
* /etc (host-specific system configuration)<br />
* /lib (essential shared libraries and kernel modules)<br />
* /mnt (mount point for mounting a filesystem temporarily)<br />
* /opt (add-on application software packages)<br />
* /sbin (essential system binaries)<br />
* /tmp (temporary files)<br />
* /usr (secondary hierarchy)<br />
* /var (variable data)<br />
<br />
=== The two independent FHS categories ===<br />
The FHS bases its layout specification on the idea that there are two independent categories of files: shareable vs. unshareable, and variable vs. static. Shareable data can be shared between hosts; unshareable data is specific to a given host (such as configuration files). Variable data can be modified; static data is not modified (except at system installation and maintenance).<br />
<br />
The following grid summarizes the four possible combinations, with examples of directories that would fall into those categories. Again, this table is straight from the FHS specification:<br />
<pre><br />
+---------+-----------------+-------------+<br />
| | shareable | unshareable |<br />
+---------+-----------------+-------------+<br />
|static | /usr | /etc |<br />
| | /opt | /boot |<br />
+---------+-----------------+-------------+<br />
|variable | /var/mail | /var/run |<br />
| | /var/spool/news | /var/lock |<br />
+---------+-----------------+-------------+<br />
</pre><br />
<br />
=== Secondary hierarchy at /usr ===<br />
Under '''/usr''' you'll find a secondary hierarchy that looks a lot like the root filesystem. It isn't critical for '''/usr''' to exist when the machine powers up, so it can be shared on a network (shareable), or mounted from a CD-ROM (static). Most Linux setups don't make use of sharing '''/usr''', but it's valuable to understand the usefulness of distinguishing between the primary hierarchy at the root directory and the secondary hierarchy at '''/usr'''.<br />
<br />
This is all we'll say about the Filesystem Hierarchy Standard. The document itself is quite readable, so you should go take a look at it. You'll understand a lot more about the Linux filesystem if you read it. Find it at http://www.pathname.com/fhs/.<br />
<br />
=== Finding files ===<br />
Linux systems often contain hundreds of thousands of files. Perhaps you are savvy enough to never lose track of any of them, but it's more likely that you will occasionally need help finding one. There are a few different tools on Linux for finding files. This introduction will help you choose the right tool for the job.<br />
<br />
=== The PATH ===<br />
When you run a program at the command line, bash actually searches through a list of directories to find the program you requested. For example, when you type ls, bash doesn't intrinsically know that the ls program lives in '''/usr/bin'''. Instead, bash refers to an environment variable called PATH, which is a colon-separated list of directories. We can examine the value of PATH:<br />
<pre><br />
$ echo $PATH<br />
/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11R6/bin<br />
</pre><br />
Given this value of PATH (yours may differ,) bash would first check '''/usr/local/bin''', then '''/usr/bin''' for the ls program. Most likely, ls is kept in /usr/bin, so bash would stop at that point.<br />
<br />
=== Modifying PATH ===<br />
You can augment your PATH by assigning to it on the command line:<br />
<pre><br />
$ PATH=$PATH:~/bin<br />
$ echo $PATH<br />
/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11R6/bin:/home/agriffis/bin<br />
</pre><br />
You can also remove elements from PATH, although it isn't as easy since you can't refer to the existing $PATH. Your best bet is to simply type out the new PATH you want:<br />
<pre><br />
$ PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:~/bin<br />
$ echo $PATH<br />
/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/home/agriffis/bin<br />
</pre><br />
To make your PATH changes available to any future processes you start from this shell, export your changes using the export command:<br />
<pre><br />
$ export PATH<br />
</pre><br />
<br />
=== All about "which" ===<br />
You can check to see if there's a given program in your PATH by using <span style="color:green">which</span>. For example, here we find out that our Linux system has no (common) sense:<br />
<pre><br />
$ which sense<br />
which: no sense in (/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11R6/bin)<br />
</pre><br />
In this example, we successfully locate <span style="color:green">ls</span>:<br />
<pre><br />
$ which ls<br />
/usr/bin/ls<br />
</pre><br />
<br />
=== "which -a" ===<br />
Finally, you should be aware of the <span style="color:green">-a</span> flag, which causes <span style="color:green">which</span> to show you all of the instances of a given program in your PATH:<br />
<pre><br />
$ which -a ls<br />
/usr/bin/ls<br />
/bin/ls<br />
</pre><br />
<br />
=== whereis ===<br />
If you're interested in finding more information than purely the location of a program, you might try the <span style="color:green">whereis</span> program:<br />
<pre><br />
$ whereis ls<br />
ls: /bin/ls /usr/bin/ls /usr/share/man/man1/ls.1.gz<br />
</pre><br />
Here we see that <span style="color:green">ls</span> occurs in two common binary locations, '''/bin''' and '''/usr/bin'''. Additionally, we are informed that there is a manual page located in '''/usr/share/man'''. This is the man-page you would see if you were to type <span style="color:green">man ls</span>.<br />
<br />
The <span style="color:green">whereis</span> program also has the ability to search for sources, to specify alternate search paths, and to search for unusual entries. Refer to the whereis man-page for further information.<br />
<br />
=== find ===<br />
The <span style="color:green">find</span> command is another handy tool for your toolbox. With find you aren't restricted to programs; you can search for any file you want, using a variety of search criteria. For example, to search for a file by the name of README, starting in '''/usr/share/doc''':<br />
<pre><br />
$ find /usr/share/doc -name README<br />
/usr/share/doc/ion-20010523/README<br />
/usr/share/doc/bind-9.1.3-r6/dhcp-dynamic-dns-examples/README<br />
/usr/share/doc/sane-1.0.5/README<br />
</pre><br />
<br />
=== find and wildcards ===<br />
You can use "glob" wildcards in the argument to -name, provided that you quote them or backslash-escape them (so they get passed to find intact rather than being expanded by bash). For example, we might want to search for README files with extensions:<br />
<pre><br />
$ find /usr/share/doc -name README\*<br />
/usr/share/doc/iproute2-2.4.7/README.gz<br />
/usr/share/doc/iproute2-2.4.7/README.iproute2+tc.gz<br />
/usr/share/doc/iproute2-2.4.7/README.decnet.gz<br />
/usr/share/doc/iproute2-2.4.7/examples/diffserv/README.gz<br />
/usr/share/doc/pilot-link-0.9.6-r2/README.gz<br />
/usr/share/doc/gnome-pilot-conduits-0.8/README.gz<br />
/usr/share/doc/gimp-1.2.2/README.i18n.gz<br />
/usr/share/doc/gimp-1.2.2/README.win32.gz<br />
/usr/share/doc/gimp-1.2.2/README.gz<br />
/usr/share/doc/gimp-1.2.2/README.perl.gz<br />
[578 additional lines snipped]<br />
</pre><br />
<br />
=== Ignoring case with find ===<br />
Of course, you might want to ignore case in your search:<br />
<pre><br />
$ find /usr/share/doc -name '[Rr][Ee][Aa][Dd][Mm][Ee]*'<br />
</pre><br />
Or, more simply:<br />
<pre><br />
$ find /usr/share/doc -iname readme\*<br />
</pre><br />
As you can see, you can use <span style="color:green">-iname</span> to do case-insensitive searching.<br />
<br />
=== find and regular expressions ===<br />
If you're familiar with regular expressions, you can use the -regex option to limit the output to filenames that match a pattern. And similar to the <span style="color:green">-iname</span> option, there is a corresponding <span style="color:green">-iregex</span> option that ignores case in the pattern. For example:<br />
<pre><br />
$ find /etc -iregex '.*xt.*'<br />
/etc/X11/xkb/types/extra<br />
/etc/X11/xkb/semantics/xtest<br />
/etc/X11/xkb/compat/xtest<br />
/etc/X11/app-defaults/XTerm<br />
/etc/X11/app-defaults/XTerm-color<br />
</pre><br />
Note that unlike many programs, <span style="color:green">find</span> requires that the regex specified matches the entire path, not just a part of it. For that reason, specifying the leading and trailing .* is necessary; purely using xt as the regex would not be sufficient.<br />
<br />
=== find and types ===<br />
The <span style="color:green">-type</span> option allows you to find filesystem objects of a certain type. The possible arguments to -type are b (block device), c (character device), d (directory), p (named pipe), f (regular file), l (symbolic link), and s (socket). For example, to search for symbolic links in '''/usr/bin''' that contain the string vim:<br />
<pre><br />
$ find /usr/bin -name '*vim*' -type l<br />
/usr/bin/rvim<br />
/usr/bin/vimdiff<br />
/usr/bin/gvimdiff<br />
</pre><br />
<br />
=== find and mtimes ===<br />
The <span style="color:green">-mtime</span> option allows you to select files based on their last modification time. The argument to mtime is in terms of 24-hour periods, and is most useful when entered with either a plus sign (meaning "after") or a minus sign (meaning "before"). For example, consider the following scenario:<br />
<pre><br />
$ ls -l ?<br />
-rw------- 1 root root 0 Jan 7 18:00 a<br />
-rw------- 1 root root 0 Jan 6 18:00 b<br />
-rw------- 1 root root 0 Jan 5 18:00 c<br />
-rw------- 1 root root 0 Jan 4 18:00 d<br />
$ date<br />
Mon Jan 7 18:14:52 EST 2003<br />
</pre><br />
You could search for files that were created in the past 24 hours:<br />
<pre><br />
$ find . -name \? -mtime -1<br />
./a<br />
</pre><br />
Or you could search for files that were created prior to the current 24-hour period:<br />
<pre><br />
$ find . -name \? -mtime +0<br />
./b<br />
./c<br />
./d<br />
</pre><br />
<br />
=== The -daystart option ===<br />
If you additionally specify the <span style="color:green">-daystart</span> option, then the periods of time start at the beginning of today rather than 24 hours ago. For example, here is a set of files created yesterday and the day before:<br />
<pre><br />
$ find . -name \? -daystart -mtime +0 -mtime -3<br />
./b<br />
./c<br />
$ ls -l b c<br />
-rw------- 1 root root 0 Jan 6 18:00 b<br />
-rw------- 1 root root 0 Jan 5 18:00 c<br />
</pre><br />
<br />
=== The -size option ===<br />
The <span style="color:green">-size</span> option allows you to find files based on their size. By default, the argument to <span style="color:green">-size</span> is 512-byte blocks, but adding a suffix can make things easier. The available suffixes are b (512-byte blocks), c (bytes), k (kilobytes), and w (2-byte words). Additionally, you can prepend a plus sign ("larger than") or minus sign ("smaller than").<br />
<br />
For example, to find regular files in '''/usr/bin''' that are smaller than 50 bytes:<br />
<pre><br />
$ find /usr/bin -type f -size -50c<br />
/usr/bin/krdb<br />
/usr/bin/run-nautilus<br />
/usr/bin/sgmlwhich<br />
/usr/bin/muttbug<br />
</pre><br />
<br />
=== Processing found files ===<br />
You may be wondering what you can do with all these files that you find! Well, <span style="color:green">find</span> has the ability to act on the files that it finds by using the <span style="color:green">-exec</span> option. This option accepts a command line to execute as its argument, terminated with ;, and it replaces any occurrences of {} with the filename. This is best understood with an example:<br />
<pre><br />
$ find /usr/bin -type f -size -50c -exec ls -l '{}' ';'<br />
-rwxr-xr-x 1 root root 27 Oct 28 07:13 /usr/bin/krdb<br />
-rwxr-xr-x 1 root root 35 Nov 28 18:26 /usr/bin/run-nautilus<br />
-rwxr-xr-x 1 root root 25 Oct 21 17:51 /usr/bin/sgmlwhich<br />
-rwxr-xr-x 1 root root 26 Sep 26 08:00 /usr/bin/muttbug<br />
</pre><br />
As you can see, <span style="color:green">find</span> is a very powerful command. It has grown through the years of UNIX and Linux development. There are many other useful options to find. You can learn about them in the find manual page.<br />
<br />
=== locate ===<br />
We have covered <span style="color:green">which</span>, <span style="color:green">whereis</span>, and <span style="color:green">find</span>. You might have noticed that find can take a while to execute, since it needs to read each directory that it's searching. It turns out that the <span style="color:green">locate</span> command can speed things up by relying on an external database generated by <span style="color:green">updatedb</span> (which we'll cover in the next panel.)<br />
<br />
The locate command matches against any part of a pathname, not just the file itself. For example:<br />
<pre><br />
$ locate bin/ls<br />
/var/ftp/bin/ls<br />
/bin/ls<br />
/sbin/lsmod<br />
/sbin/lspci<br />
/usr/bin/lsattr<br />
/usr/bin/lspgpot<br />
/usr/sbin/lsof<br />
</pre><br />
<br />
=== Using updatedb ===<br />
Most Linux systems have a "cron job" to update the database periodically. If your <span style="color:green">locate</span> returned an error such as the following, then you will need to run <span style="color:green">updatedb</span> as root to generate the search database:<br />
<pre><br />
$ locate bin/ls<br />
locate: /var/spool/locate/locatedb: No such file or directory<br />
$ su -<br />
Password:<br />
# updatedb<br />
</pre><br />
The <span style="color:green">updatedb</span> command may take a long time to run. If you have a noisy hard disk, you will hear a lot of racket as the entire filesystem is indexed. :)<br />
<br />
=== slocate ===<br />
On many Linux distributions, the <span style="color:green">locate</span> command has been replaced by <span style="color:green">slocate</span>. There is typically a symbolic link to <span style="color:green">locate</span>, so that you don't need to remember which you have. <span style="color:green">slocate</span> stands for "secure locate." It stores permissions information in the database so that normal users can't pry into directories they would otherwise be unable to read. The usage information for <span style="color:green">slocate</span> is essentially the same as for <span style="color:green">locate</span>, although the output might be different depending on the user running the command.<br />
<br />
== Process Control ==<br />
<br />
=== Staring xeyes ===<br />
{{fancynote|You may need to install xeyes on your system first. Consult your distro's documentation for instructions on installing}}<br />
<br />
To learn about process control, we first need to start a process. Make sure that you have X running and execute the following command:<br />
<pre><br />
$ xeyes -center red<br />
</pre><br />
You will notice that an xeyes window pops up, and the red eyeballs follow your mouse around the screen. You may also notice that you don't have a new prompt in your terminal.<br />
<br />
=== Stopping a process ===<br />
To get a prompt back, you could type Control-C (often written as Ctrl-C or ^C):<br />
<br />
You get a new bash prompt, but the xeyes window disappeared. In fact, the entire process has been killed. Instead of killing it with Control-C, we could have just stopped it with Control-Z:<br />
<pre><br />
$ xeyes -center red<br />
Control-Z<br />
[1]+ Stopped xeyes -center red<br />
$<br />
</pre><br />
This time you get a new bash prompt, and the xeyes windows stays up. If you play with it a bit, however, you will notice that the eyeballs are frozen in place. If the xeyes window gets covered by another window and then uncovered again, you will see that it doesn't even redraw the eyes at all. The process isn't doing anything. It is, in fact, "Stopped."<br />
<br />
=== fg and bg ===<br />
To get the process "un-stopped" and running again, we can bring it to the foreground with the bash built-in <span style="color:green">fg</span>:<br />
<pre><br />
$ fg<br />
(test it out, then stop the process again)<br />
Control-Z<br />
[1]+ Stopped xeyes -center red<br />
$<br />
</pre><br />
Now continue it in the background with the bash built-in <span style="color:green">bg</span>:<br />
<pre><br />
$ bg<br />
[1]+ xeyes -center red &<br />
$<br />
</pre><br />
Great! The xeyes process is now running in the background, and we have a new, working bash prompt.<br />
<br />
=== Using "&" ===<br />
If we wanted to start xeyes in the background from the beginning (instead of using Control-Z and bg), we could have just added an "&" (ampersand) to the end of xeyes command line:<br />
<pre><br />
$ xeyes -center blue &<br />
[2] 16224<br />
</pre><br />
<br />
=== Multiple background processes ===<br />
Now we have both a red and a blue xeyes running in the background. We can list these jobs with the bash built-in <span style="color:green">jobs</span>:<br />
<pre><br />
$ jobs -l<br />
[1]- 16217 Running xeyes -center red &<br />
[2]+ 16224 Running xeyes -center blue &<br />
</pre><br />
The numbers in the left column are the job numbers bash assigned when they were started. Job 2 has a + (plus) to indicate that it's the "current job," which means that typing <span style="color:green">fg</span> will bring it to the foreground. You could also foreground a specific job by specifying its number; for example, <span style="color:green">fg 1</span> would make the red xeyes the foreground task. The next column is the process id or pid, included in the listing courtesy of the -l option to jobs. Finally, both jobs are currently "Running," and their command lines are listed to the right.<br />
<br />
=== Introducing signals ===<br />
To kill, stop, or continue processes, Linux uses a special form of communication called "signals." By sending a certain signal to a process, you can get it to terminate, stop, or do other things. This is what you're actually doing when you type Control-C, Control-Z, or use the <span style="color:green">bg</span> or <span style="color:green">fg</span> built-ins -- you're using bash to send a particular signal to the process. These signals can also be sent using the <span style="color:green">kill</span> command and specifying the pid (process id) on the command line:<br />
<pre><br />
$ kill -s SIGSTOP 16224<br />
$ jobs -l<br />
[1]- 16217 Running xeyes -center red &<br />
[2]+ 16224 Stopped (signal) xeyes -center blue<br />
</pre><br />
As you can see, kill doesn't necessarily "kill" a process, although it can. Using the "-s" option, kill can send any signal to a process. Linux kills, stops or continues processes when they are sent the SIGINT, SIGSTOP, or SIGCONT signals respectively. There are also other signals that you can send to a process; some of these signals may be interpreted in an application-dependent way. You can learn what signals a particular process recognizes by looking at its man-page and searching for a SIGNALS section.<br />
<br />
=== SIGTERM and SIGINT ===<br />
If you want to kill a process, you have several options. By default, kill sends SIGTERM, which is not identical to SIGINT of Control-C fame, but usually has the same results:<br />
<pre><br />
$ kill 16217<br />
$ jobs -l<br />
[1]- 16217 Terminated xeyes -center red<br />
[2]+ 16224 Stopped (signal) xeyes -center blue<br />
</pre><br />
<br />
=== The big kill ===<br />
Processes can ignore both SIGTERM and SIGINT, either by choice or because they are stopped or somehow "stuck." In these cases it may be necessary to use the big hammer, the SIGKILL signal. A process cannot ignore SIGKILL:<br />
<pre><br />
$ kill 16224<br />
$ jobs -l<br />
[2]+ 16224 Stopped (signal) xeyes -center blue<br />
$ kill -s SIGKILL<br />
$ jobs -l<br />
[2]+ 16224 Interrupt xeyes -center blue<br />
</pre><br />
<br />
=== nohup ===<br />
The terminal where you start a job is called the job's controlling terminal. Some shells (not bash by default), will deliver a SIGHUP signal to backgrounded jobs when you logout, causing them to quit. To protect processes from this behavior, use the nohup when you start the process:<br />
<pre><br />
$ nohup make &<br />
[1] 15632<br />
$ exit<br />
</pre><br />
<br />
=== Using ps to list processes ===<br />
The <span style="color:green">jobs</span> command we were using earlier only lists processes that were started from your bash session. To see all the processes on your system, use <span style="color:green">ps</span> with the <span style="color:green">a</span> and <span style="color:green">x</span> options together:<br />
<pre><br />
$ ps ax<br />
PID TTY STAT TIME COMMAND<br />
1 ? S 0:04 init [3]<br />
2 ? SW 0:11 [keventd]<br />
3 ? SWN 0:13 [ksoftirqd_CPU0]<br />
4 ? SW 2:33 [kswapd]<br />
5 ? SW 0:00 [bdflush]<br />
</pre><br />
I've only listed the first few because it is usually a very long list. This gives you a snapshot of what the whole machine is doing, but is a lot of information to sift through. If you were to leave off the <span style="color:green">ax</span>, you would see only processes that are owned by you, and that have a controlling terminal. The command <span style="color:green">ps x</span> would show you all your processes, even those without a controlling terminal. If you were to use <span style="color:green">ps a</span>, you would get the list of everybody's processes that are attached to a terminal.<br />
<br />
=== Seeing the forest and the trees ===<br />
You can also list different information about each process. The <span style="color:green">--forest</span> option makes it easy to see the process hierarchy, which will give you an indication of how the various processes on your system interrelate. When a process starts a new process, that new process is called a "child" process. In a <span style="color:green">--forest</span> listing, parents appear on the left, and children appear as branches to the right:<br />
<pre><br />
$ ps x --forest<br />
PID TTY STAT TIME COMMAND<br />
927 pts/1 S 0:00 bash<br />
6690 pts/1 S 0:00 \_ bash<br />
26909 pts/1 R 0:00 \_ ps x --forest<br />
19930 pts/4 S 0:01 bash<br />
25740 pts/4 S 0:04 \_ vi processes.txt<br />
</pre><br />
<br />
=== The "u" and "l" ps options ===<br />
The <span style="color:green">u</span> or <span style="color:green">l</span> options can also be added to any combination of <span style="color:green">a</span> and <span style="color:green">x</span> in order to include more information about each process:<br />
<pre><br />
$ ps au<br />
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND<br />
agriffis 403 0.0 0.0 2484 72 tty1 S 2001 0:00 -bash<br />
chouser 404 0.0 0.0 2508 92 tty2 S 2001 0:00 -bash<br />
root 408 0.0 0.0 1308 248 tty6 S 2001 0:00 /sbin/agetty 3<br />
agriffis 434 0.0 0.0 1008 4 tty1 S 2001 0:00 /bin/sh /usr/X<br />
chouser 927 0.0 0.0 2540 96 pts/1 S 2001 0:00 bash<br />
</pre><br />
<pre><br />
$ ps al<br />
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND<br />
100 1001 403 1 9 0 2484 72 wait4 S tty1 0:00 -bash<br />
100 1000 404 1 9 0 2508 92 wait4 S tty2 0:00 -bash<br />
000 0 408 1 9 0 1308 248 read_c S tty6 0:00 /sbin/ag<br />
000 1001 434 403 9 0 1008 4 wait4 S tty1 0:00 /bin/sh<br />
000 1000 927 652 9 0 2540 96 wait4 S pts/1 0:00 bash<br />
</pre><br />
<br />
=== Using top ===<br />
If you find yourself running ps several times in a row, trying to watch things change, what you probably want is <span style="color:green">top</span>. <span style="color:green">top</span> displays a continuously updated process listing, along with some useful summary information:<br />
<pre><br />
$ top<br />
10:02pm up 19 days, 6:24, 8 users, load average: 0.04, 0.05, 0.00<br />
75 processes: 74 sleeping, 1 running, 0 zombie, 0 stopped<br />
CPU states: 1.3% user, 2.5% system, 0.0% nice, 96.0% idle<br />
Mem: 256020K av, 226580K used, 29440K free, 0K shrd, 3804K buff<br />
Swap: 136544K av, 80256K used, 56288K free 101760K cached<br />
<br />
PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND<br />
628 root 16 0 213M 31M 2304 S 0 1.9 12.5 91:43 X<br />
26934 chouser 17 0 1272 1272 1076 R 0 1.1 0.4 0:00 top<br />
652 chouser 11 0 12016 8840 1604 S 0 0.5 3.4 3:52 gnome-termin<br />
641 chouser 9 0 2936 2808 1416 S 0 0.1 1.0 2:13 sawfish<br />
</pre><br />
<br />
=== nice ===<br />
Each processes has a priority setting that Linux uses to determine how CPU timeslices are shared. You can set the priority of a process by starting it with the <span style="color:green">nice</span> command:<br />
<pre><br />
$ nice -n 10 oggenc /tmp/song.wav<br />
</pre><br />
Since the priority setting is called <span style="color:green">nice</span>, it should be easy to remember that a higher value will be nice to other processes, allowing them to get priority access to the CPU. By default, processes are started with a setting of 0, so the setting of 10 above means oggenc will readily give up the CPU to other processes. Generally, this means that oggenc will allow other processes to run at their normal speed, regardless of how CPU-hungry oggenc happens to be. You can see these niceness levels under the NI column in the ps and top listings above.<br />
<br />
=== renice ===<br />
The <span style="color:green">nice</span> command can only change the priority of a process when you start it. If you want to change the niceness setting of a running process, use <span style="color:green">renice</span>:<br />
<pre><br />
$ ps l 641<br />
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND<br />
000 1000 641 1 9 0 5876 2808 do_sel S ? 2:14 sawfish<br />
$ renice 10 641<br />
641: old priority 0, new priority 10<br />
$ ps l 641<br />
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND<br />
000 1000 641 1 9 10 5876 2808 do_sel S ? 2:14 sawfish<br />
</pre><br />
<br />
== Text processing ==<br />
<br />
=== Redirection revisited ===<br />
Earlier in this tutorial series, we saw an example of how to use the <span style="color:green">></span> operator to redirect the output of a command to a file, as follows:<br />
<pre><br />
$ echo "firstfile" > copyme<br />
</pre><br />
In addition to redirecting output to a file, we can also take advantage of a powerful shell feature called pipes. Using pipes, we can pass the output of one command to the input of another command. Consider the following example:<br />
<pre><br />
$ echo "hi there" | wc<br />
1 2 9<br />
</pre><br />
The <span style="color:green">|</span> character is used to connect the output of the command on the left to the input of the command on the right. In the example above, the <span style="color:green">echo</span> command prints out the string "hi there" followed by a linefeed. That output would normally appear on the terminal, but the pipe redirects it into the <span style="color:green">wc</span> command, which displays the number of lines, words, and characters in its input.<br />
<br />
=== A pipe example ===<br />
Here is another simple example:<br />
<pre><br />
$ ls -s | sort -n<br />
</pre><br />
In this case, <span style="color:green">ls -s</span> would normally print a listing of the current directory on the terminal, preceding each file with its size. But instead we've piped the output into <span style="color:green">sort -n</span>, which sorts the output numerically. This is a really useful way to find large files in your home directory!<br />
<br />
The following examples are more complex, but they demonstrate the power that can be harnessed using pipes. We're going to throw out some commands we haven't covered yet, but don't let that slow you down. Concentrate instead on understanding how pipes work so you can employ them in your daily Linux tasks.<br />
<br />
=== The decompression pipeline ===<br />
Normally to decompress and untar a file, you might do the following:<br />
<pre><br />
$ bzip2 -d linux-2.4.16.tar.bz2<br />
$ tar xvf linux-2.4.16.tar<br />
</pre><br />
The downside of this method is that it requires the creation of an intermediate, uncompressed file on your disk. Since <span style="color:green">tar</span> has the ability to read directly from its input (instead of specifying a file), we could produce the same end-result using a pipeline:<br />
<pre><br />
$ bzip2 -dc linux-2.4.16.tar.bz2 | tar xvf -<br />
</pre><br />
Woo hoo! Our compressed tarball has been extracted and we didn't need an intermediate file.<br />
<br />
=== A longer pipeline ===<br />
Here's another pipeline example:<br />
<pre><br />
$ cat myfile.txt | sort | uniq | wc -l<br />
</pre><br />
We use <span style="color:green">cat</span> to feed the contents of '''myfile.txt''' to the <span style="color:green">sort</span> command. When the sort command receives the input, it sorts all input lines so that they are in alphabetical order, and then sends the output to <span style="color:green">uniq</span>. <span style="color:green">uniq</span> removes any duplicate lines (and requires its input to be sorted, by the way,) sending the scrubbed output to <span style="color:green">wc -l</span>. We've seen the <span style="color:green">wc</span> command earlier, but without command-line options. When given the <span style="color:green">-l</span> option, it only prints the number of lines in its input, instead of also including words and characters. You'll see that this pipeline will print out the number of unique (non-identical) lines in a text file.<br />
<br />
Try creating a couple of test files with your favorite text editor and use this pipeline to see what results you get.<br />
<br />
=== The text processing whirlwind begins ===<br />
Now we embark on a whirlwind tour of the standard Linux text processing commands. Because we're covering a lot of material in this tutorial, we don't have the space to provide examples for every command. Instead, we encourage you to read each command's man page (by typing <span style="color:green">man echo</span>, for example) and learn how each command and it's options work by spending some time playing with each one. As a rule, these commands print the results of any text processing to the terminal rather than modifying any specified files. After we take our whirlwind tour of the standard Linux text processing commands, we'll take a closer look at output and input redirection. So yes, there is light at the end of the tunnel :)<br />
<br />
<span style="color:green">echo</span> prints its arguments to the terminal. Use the <span style="color:green">-e</span> option if you want to embed backslash escape sequences; for example <span style="color:green">echo -e "foo\nfoo"</span> will print foo, then a newline, and then foo again. Use the <span style="color:green">-n</span> option to tell echo to omit the trailing newline that is appended to the output by default.<br />
<br />
<span style="color:green">cat</span> will print the contents of the files specified as arguments to the terminal. Handy as the first command of a pipeline, for example, <span style="color:green">cat foo.txt | blah</span>.<br />
<br />
<span style="color:green">sort</span> will print the contents of the file specified on the command line in alphabetical order. Of course, <span style="color:green">sort</span> also accepts piped input. Type <span style="color:green">man sort</span> to familiarize yourself with its various options that control sorting behavior.<br />
<br />
<span style="color:green">uniq</span> takes an already-sorted file or stream of data (via a pipeline) and removes duplicate lines.<br />
<br />
<span style="color:green">wc</span> prints out the number of lines, words, and bytes in the specified file or in the input stream (from a pipeline). Type <span style="color:green">man wc</span> to learn how to fine-tune what counts are displayed.<br />
<br />
<span style="color:green">head</span> prints out the first ten lines of a file or stream. Use the <span style="color:green">-n</span> option to specify how many lines should be displayed.<br />
<br />
<span style="color:green">tail</span> prints out the last ten lines of a file or stream. Use the <span style="color:green">-n</span> option to specify how many lines should be displayed.<br />
<br />
<span style="color:green">tac</span> is like <span style="color:green">cat</span>, but prints all lines in reverse order; in other words, the last line is printed first.<br />
<br />
<span style="color:green">expand</span> converts input tabs to spaces. Use the <span style="color:green">-t</span> option to specify the tabstop.<br />
<br />
<span style="color:green">unexpand</span> converts input spaces to tabs. Use the <span style="color:green">-t</span> option to specify the tabstop.<br />
<br />
<span style="color:green">cut</span> is used to extract character-delimited fields from each line of an input file or stream.<br />
<br />
The <span style="color:green">nl</span> command adds a line number to every line of input. Useful for printouts.<br />
<br />
<span style="color:green">pr</span> is used to break files into multiple pages of output; typically used for printing.<br />
<br />
<span style="color:green">tr</span> is a character translation tool; it's used to map certain characters in the input stream to certain other characters in the output stream.<br />
<br />
<span style="color:green">sed</span> is a powerful stream-oriented text editor. You can learn more about sed in the following Funtoo articles:<br />
<br />
* [[Sed by Example, Part 1]]<br />
* [[Sed by Example, Part 2]]<br />
* [[Sed by Example, Part 3]]<br />
<br />
If you're planning to take the LPI exam, be sure to read the first two articles of this series.<br />
<br />
<span style="color:green">awk</span> is a handy line-oriented text-processing language. To learn more about awk, read the following Funtoo articles:<br />
<br />
* [[Awk by Example, Part 1]]<br />
* [[Awk by Example, Part 2]]<br />
* [[Awk by Example, Part 3]]<br />
<br />
<span style="color:green">od</span> is designed to transform the input stream into a octal or hex "dump" format.<br />
<br />
<span style="color:green">split</span> is a command used to split a larger file into many smaller-sized, more manageable chunks.<br />
<br />
<span style="color:green">fmt</span> will reformat paragraphs so that wrapping is done at the margin. These days it's less useful since this ability is built into most text editors, but it's still a good one to know.<br />
<br />
<span style="color:green">paste</span> takes two or more files as input, concatenates each sequential line from the input files, and outputs the resulting lines. It can be useful to create tables or columns of text.<br />
<br />
<span style="color:green">join</span> is similar to paste, but it uses a field (by default the first) in each input line to match up what should be combined on a single line.<br />
<br />
<span style="color:green">tee</span> prints its input both to a file and to the screen. This is useful when you want to create a log of something, but you also want to see it on the screen.<br />
<br />
=== Whirlwind over! Redirection ===<br />
Similar to using <span style="color:green">></span> on the bash command line, you can also use <span style="color:green">&lt;</span> to redirect a file into a command. For many commands, you can simply specify the filename on the command line, however some commands only work from standard input.<br />
<br />
Bash and other shells support the concept of a "herefile." This allows you to specify the input to a command in the lines following the command invocation, terminating it with a sentinal value. This is easiest shown through an example:<br />
<pre><br />
$ sort <<END<br />
apple<br />
cranberry<br />
banana<br />
END<br />
apple<br />
banana<br />
cranberry<br />
</pre><br />
In the example above, we typed the words apple, cranberry and banana, followed by "END" to signify the end of the input. The <span style="color:green">sort</span> program then returned our words in alphabetical order.<br />
<br />
=== Using >> ===<br />
You would expect <span style="color:green">>></span> to be somehow analogous to <span style="color:green">&lt;&lt;</span>, but it isn't really. It simply means to append the output to a file, rather than overwrite as <span style="color:green">></span> would. For example:<br />
<pre><br />
$ echo Hi > myfile<br />
$ echo there. > myfile<br />
$ cat myfile<br />
there.<br />
</pre><br />
Oops! We lost the "Hi" portion! What we meant was this:<br />
<pre><br />
$ echo Hi > myfile<br />
$ echo there. >> myfile<br />
$ cat myfile<br />
Hi<br />
there.<br />
</pre><br />
Much better!<br />
<br />
== Kernel Modules ==<br />
<br />
=== Meet "uname" ===<br />
The <span style="color:green">uname</span> command provides a variety of interesting information about your system. Here's what is displayed on my development workstation when I type <span style="color:green">uname -a</span> which tells the <span style="color:green">uname</span> command to print out all of its information in one swoop:<br />
<pre><br />
$ uname -a<br />
Linux inventor 2.4.20-gaming-r1 #1 Fri Apr 11 18:33:35 MDT 2003 i686 AMD Athlon(tm) XP 2100+ AuthenticAMD GNU/Linux<br />
</pre><br />
<br />
=== More uname madness ===<br />
Now, let's look at the information that <span style="color:green">uname</span> provides<br />
<pre><br />
info. option arg example<br />
kernel name -s "Linux"<br />
hostname -n "inventor"<br />
kernel release -r "2.4.20-gaming-r1"<br />
kernel version -v "#1 Fri Apr 11 18:33:35 MDT 2003"<br />
machine -m "i686"<br />
processor -p "AMD Athlon(tm) XP 2100+"<br />
hardware platform -i "AuthenticAMD"<br />
operating system -o "GNU/Linux"<br />
</pre><br />
Intriguing! What does your <span style="color:green">uname -a</span> command print out?<br />
<br />
=== The kernel release ===<br />
Here's a magic trick. First, type <span style="color:green">uname -r</span> to have the uname command print out the release of the Linux kernel that's currently running.<br />
<br />
Now, look in the '''/lib/modules''' directory and --presto!-- I bet you'll find a directory with that exact name! OK, not quite magic, but now may be a good time to talk about the significance of the directories in '''/lib/modules''' and explain what kernel modules are.<br />
<br />
=== The kernel ===<br />
The Linux kernel is the heart of what is commonly referred to as "Linux" -- it's the piece of code that accesses your hardware directly and provides abstractions so that regular old programs can run. Thanks to the kernel, your text editor doesn't need to worry about whether it is writing to a SCSI or IDE disk -- or even a RAM disk. It just writes to a filesystem, and the kernel takes care of the rest.<br />
<br />
=== Introducing kernel modules ===<br />
So, what are kernel modules? Well, they're parts of the kernel that have been stored in a special format on disk. At your command, they can be loaded into the running kernel and provide additional functionality.<br />
<br />
Because the kernel modules are loaded on demand, you can have your kernel support a lot of additional functionality that you may not ordinarily want to be enabled. But once in a blue moon, those kernel modules are likely to come in quite handy and can be loaded -- often automatically -- to support that odd filesystem or hardware device that you rarely use.<br />
<br />
=== Kernel modules in a nutshell ===<br />
In sum, kernel modules allow for the running kernel to enable capabilities on an on-demand basis. Without kernel modules, you'd have to compile a completely new kernel and reboot in order for it to support something new.<br />
<br />
=== lsmod ===<br />
To see what modules are currently loaded on your system, use the <span style="color:green">lsmod</span> command:<br />
<pre><br />
# lsmod<br />
Module Size Used by Tainted: PF<br />
vmnet 20520 5<br />
vmmon 22484 11<br />
nvidia 1547648 10<br />
mousedev 3860 2<br />
hid 16772 0 (unused)<br />
usbmouse 1848 0 (unused)<br />
input 3136 0 [mousedev hid usbmouse]<br />
usb-ohci 15976 0 (unused)<br />
ehci-hcd 13288 0 (unused)<br />
emu10k1 64264 2<br />
ac97_codec 9000 0 [emu10k1]<br />
sound 51508 0 [emu10k1]<br />
usbcore 55168 1 [hid usbmouse usb-ohci ehci-hcd]<br />
</pre><br />
<br />
=== Modules listing ===<br />
As you can see, my system has quite a few modules loaded. the vmnet and vmmon modules provide necessary functionality for [http://www.vmware.com/ VMWare Workstation], which allows me to run a virtual PC in a window on my desktop. The "nvidia" module comes from [http://www.nvidia.com/ NVIDIA] corporation and allows me to use my high-performance 3D-accelerated graphics card under Linux whilst taking advantage of its many neat features.<br />
<br />
Then I have a bunch of modules that are used to provide support for my USB-based input devices -- namely "mousedev," "hid," "usbmouse," "input," "usb-ohci," "ehci-hcd" and "usbcore." It often makes sense to configure your kernel to provide USB support as modules. Why? Because USB devices are "plug and play," and when you have your USB support in modules, then you can go out and buy a new USB device, plug it in to your system, and have the system automatically load the appropriate modules to enable that device. It's a handy way to do things.<br />
<br />
=== Third-party modules ===<br />
Rounding out my list of modules are "emu10k1," "ac97_codec," and "sound," which together provide support for my SoundBlaster Audigy sound card.<br />
<br />
It should be noted that some of my kernel modules come from the kernel sources themselves. For example, all the USB-related modules are compiled from the standard Linux kernel sources. However, the nvidia, emu10k1 and VMWare-related modules come from other sources. This highlights another major benefit of kernel modules -- allowing third parties to provide much-needed kernel functionality and allowing this functionality to "plug in" to a running Linux kernel. No reboot necessary.<br />
<br />
=== depmod and friends ===<br />
In my '''/lib/modules/2.4.20-gaming-r1/''' directory, I have a number of files that start with the string "modules.":<br />
<pre><br />
$ ls /lib/modules/2.4.20-gaming-r1/modules.*<br />
/lib/modules/2.4.20-gaming-r1/modules.dep<br />
/lib/modules/2.4.20-gaming-r1/modules.generic_string<br />
/lib/modules/2.4.20-gaming-r1/modules.ieee1394map<br />
/lib/modules/2.4.20-gaming-r1/modules.isapnpmap<br />
/lib/modules/2.4.20-gaming-r1/modules.parportmap<br />
/lib/modules/2.4.20-gaming-r1/modules.pcimap<br />
/lib/modules/2.4.20-gaming-r1/modules.pnpbiosmap<br />
/lib/modules/2.4.20-gaming-r1/modules.usbmap<br />
</pre><br />
These files contain some lots of dependency information. For one, they record *dependency* information for modules -- some modules require other modules to be loaded first before they will run. This information is recorded in these files.<br />
<br />
=== How you get modules ===<br />
Some kernel modules are designed to work with specific hardware devices, like my "emu10k1" module which is for my SoundBlaster Audigy card. For these types of modules, these files also record the PCI IDs and similar identifying marks of the hardware devices that they support. This information can be used by things like the "hotplug" scripts (which we'll take a look at in later tutorials) to auto-detect hardware and load the appropriate module to support said hardware automatically.<br />
<br />
=== Using depmod ===<br />
If you ever install a new module, this dependency information may become out of date. To make it fresh again, simply type <span style="color:green">depmod -a.</span> The <span style="color:green">depmod</span> program will then scan all the modules in your directories in '''/lib/modules''' and freshen the dependency information. It does this by scanning the module files in '''/lib/modules''' and looking at what are called "symbols" inside the modules.<br />
<br />
=== Locating kernel modules ===<br />
So, what do kernel modules look like? For 2.4 kernels, they're typically any file in the '''/lib/modules''' tree that ends in ".o". To see all the modules in '''/lib/modules''', type the following:<br />
<pre><br />
# find /lib/modules -name '*.o'<br />
/lib/modules/2.4.20-gaming-r1/misc/vmmon.o<br />
/lib/modules/2.4.20-gaming-r1/misc/vmnet.o<br />
/lib/modules/2.4.20-gaming-r1/video/nvidia.o<br />
/lib/modules/2.4.20-gaming-r1/kernel/fs/fat/fat.o<br />
/lib/modules/2.4.20-gaming-r1/kernel/fs/vfat/vfat.o<br />
/lib/modules/2.4.20-gaming-r1/kernel/fs/minix/minix.o<br />
[listing "snipped" for brevity]<br />
</pre><br />
<br />
=== insmod vs. modprobe ===<br />
So, how does one load a module into a running kernel? One way is to use the <span style="color:green">insmod</span> command and specifying the full path to the module that you wish to load:<br />
<pre><br />
# insmod /lib/modules/2.4.20-gaming-r1/kernel/fs/fat/fat.o<br />
# lsmod | grep fat<br />
fat 29272 0 (unused)<br />
</pre><br />
However, one normally loads modules by using the <span style="color:green">modprobe</span> command. One of the nice things about the <span style="color:green">modprobe</span> command is that it automatically takes care of loading any dependent modules. Also, one doesn't need to specify the path to the module you wish to load, nor does one specify the trailing ".o".<br />
<br />
=== rmmod and modprobe in action ===<br />
Let's unload our "fat.o" module and load it using <span style="color:green">modprobe</span>:<br />
<pre><br />
# rmmod fat<br />
# lsmod | grep fat<br />
# modprobe fat<br />
# lsmod | grep fat<br />
fat 29272 0 (unused)<br />
</pre><br />
As you can see, the <span style="color:green">rmmod</span> command works similarly to <span style="color:green">modprobe</span>, but has the opposite effect -- it unloads the module you specify.<br />
<br />
=== Your friend modinfo and modules.conf ===<br />
You can use the <span style="color:green">modinfo</span> command to learn interesting things about your favorite modules:<br />
<pre><br />
# modinfo fat<br />
filename: /lib/modules/2.4.20-gaming-r1/kernel/fs/fat/fat.o<br />
description: <none><br />
author: <none><br />
license: "GPL"<br />
</pre><br />
And make special note of the '''/etc/modules.conf''' file. This file contains configuration information for modprobe. It allows you to tweak the functionality of modprobe by telling it to load modules before/after loading others, run scripts before/after modules load, and more.<br />
<br />
=== modules.conf gotchas ===<br />
The syntax and functionality of '''modules.conf''' is quite complicated, and we won't go into its syntax now (type <span style="color:green">man modules.conf</span> for all the gory details), but here are some things that you *should* know about this file.<br />
<br />
For one, many distributions generate this file automatically from a bunch of files in another directory, like '''/etc/modules.d/'''. For example, Gentoo Linux has an '''/etc/modules.d/''' directory, and running the <span style="color:green">update-modules</span> command will take every file in '''/etc/modules.d/''' and concatenate them to produce a new '''/etc/modules.conf'''. Therefore, make your changes to the files in '''/etc/modules.d/''' and run <span style="color:green">update-modules</span> if you are using Gentoo. If you are using Debian, the procedure is similar except that the directory is called '''/etc/modutils/'''.<br />
<br />
== Summary and Resources ==<br />
<br />
=== Summary ===<br />
Congratulations; you've reached the end of this tutorial on basic Linux administration! We hope that it has helped you to firm up your foundational Linux knowledge. Please join us in our next tutorial covering intermediate administration, where we will build on the foundation laid here, covering topics like the Linux permissions and ownership model, user account management, filesystem creation and mounting, and more. And remember, by continuing in this tutorial series, you'll soon be ready to attain your LPIC Level 1 Certification from the Linux Professional Institute.<br />
<br />
=== Resources ===<br />
Speaking of LPIC certification, if this is something you're interested in, then we recommend that you study the following resources, which have been carefully selected to augment the material covered in this tutorial:<br />
<br />
There are a number of good regular expression resources on the 'net. Here are a couple that we've found:<br />
<br />
* [http://www.zvon.org/other/reReference/Output/ Regular Expressions Reference]<br />
* [http://zez.org/article/articleview/11/ Regular Expressions Explained]<br />
<br />
Be sure to read up on the Filesystem Hierarchy Standard at http://www.pathname.com/fhs/.<br />
<br />
Check out the other articles in this series:<br />
*[[Linux Fundamentals, Part 1]]<br />
*[[Linux Fundamentals, Part 3]]<br />
*[[Linux Fundamentals, Part 4]]<br />
<br />
In the "Bash by Example" article series, Daniel shows you how to use bash programming constructs to write your own bash scripts. This series (particularly Parts 1 and 2) will be good preparation for the LPIC Level 1 exam:<br />
*[[Bash by Example, Part 1]]: Fundamental programming in the Bourne-again shell<br />
*[[Bash by Example, Part 2]]: More bash programming fundamentals<br />
*[[Bash by Example, Part 3]]: Exploring the ebuild system<br />
<br />
You can learn more about sed in the Sed by Example article series. If you're planning to take the LPI exam, be sure to read the first two articles of this series.<br />
*[[Sed by Example, Part 1]]<br />
*[[Sed by Example, Part 2]]<br />
*[[Sed by Example, Part 3]]<br />
<br />
To learn more about awk, read the Awk by Example article series.<br />
*[[Awk by Example, Part 1]]<br />
*[[Awk by Example, Part 2]]<br />
*[[Awk by Example, Part 3]]<br />
<br />
If you're not too familiar with the vi editor, I strongly recommend that you check out my [http://www-106.ibm.com/developerworks/edu/l-dw-linuxvi-i.html Vi -- the cheat sheet method] tutorial. This tutorial will give you a gentle yet fast-paced introduction to this powerful text editor. Consider this must-read material if you don't know how to use vi.<br />
<br />
__NOTOC__<br />
[[Category:Linux Core Concepts]]<br />
[[Category:Articles]]</div>Oleghttp://www.funtoo.org/wiki/User:OlegUser:Oleg2012-11-30T18:01:14Z<p>Oleg: </p>
<hr />
<div>{{Person<br />
|Full name=Oleg Vinichenko<br />
|Nick=angry_vincent<br />
|Geoloc=48.379433, 31.16558<br />
|Location name=Ukraine<br />
|Roles={{Role<br />
|Role type=Staff<br />
|Role desc=Team lead<br />
|Start date=2009/01/01<br />
}}<br />
|Maintains=sys-apps/portage, sys-fs/mdev-bb, toolchain (gcc, glibc, binutils, linux-headers), sys-kernel/*, base-system, media-sound/oss, sys-apps/man-db<br />
|Blogs=<br />
}}<br />
== angry_vincent ==<br />
<br />
[[File:angry_vincent.jpg|top|left|400x3000pxpx]]<br />
<br />
birthdate=11 September, 1981<br />
<br />
== Linux history ==<br />
<br />
First *nix experience was Sun computer with Solaris OS in scientific laboratory. Then I played a lot with Windows XP x64 early betas for fun, then switched to FreeBSD, thx to our university network admin. Next step was Gentoo Linux, since 2006 and then Funtoo,since late 2009<br />
<br />
== Contact ==<br />
<br />
ask angry_vincent for details #funtoo, irc.freenode.net.</div>Oleghttp://www.funtoo.org/wiki/User:OlegUser:Oleg2012-11-30T04:59:55Z<p>Oleg: </p>
<hr />
<div>{{Person<br />
|Full name=Oleg Vinichenko<br />
|Nick=angry_vincent<br />
|Geoloc=48.379433, 31.16558<br />
|Location name=Ukraine<br />
|Roles={{Role<br />
|Role type=Staff<br />
|Role desc=Team lead<br />
|Start date=2009/01/01<br />
}}<br />
|Maintains=sys-apps/portage, sys-fs/mdev-bb, toolchain (gcc, glibc, binutils, linux-headers), sys-kernel/*, media-sound/oss, sys-apps/man-db<br />
|Blogs=<br />
}}<br />
== angry_vincent ==<br />
<br />
[[File:angry_vincent.jpg|top|left|400x3000pxpx]]<br />
<br />
birthdate=11 September, 1981<br />
<br />
== Linux history ==<br />
<br />
First *nix experience was Sun computer with Solaris OS in scientific laboratory. Then I played a lot with Windows XP x64 early betas for fun, then switched to FreeBSD, thx to our university network admin. Next step was Gentoo Linux, since 2006 and then Funtoo,since late 2009<br />
<br />
== Contact ==<br />
<br />
ask angry_vincent for details #funtoo, irc.freenode.net.</div>Oleghttp://www.funtoo.org/wiki/Talk:DownloadTalk:Download2012-11-05T11:46:28Z<p>Oleg: Reverted edits by 103.22.193.154 (talk) to last revision by Whitewolf Fox</p>
<hr />
<div>__NOTITLE__<br />
= Download Funtoo Linux =<br />
<br />
Here are the steps you should follow to download Funtoo Linux stage3 tarball. If you need an install CD, please see [[Funtoo Linux Installation]] for Live Media recommendations. Funtoo Linux currently doesn't have its own LiveCD, but there are many that you can use for installation.<br />
<br />
== First, Pick a Mirror... ==<br />
<br />
Funtoo Linux can be downloaded at the following locations:<br />
<br />
* Main US mirror: [http://ftp.osuosl.org/pub/funtoo/ The Oregon State University Open Source Lab]<br />
* Main EU mirror: [http://ftp.heanet.ie/mirrors/funtoo/ HEAnet]<br />
<br />
== Now... pick a build ==<br />
<br />
'''Now you'll first need to pick a ''build'' of Funtoo Linux to install.''' Builds are like different versions of Funtoo Linux. Our '''funtoo-current''' build is the most up-to-date and recommended build. We also offer '''funtoo-stable'''. Both current and stable share the use the same Portage tree (package repository), but newer packages are unmasked (made available for install) in '''funtoo-current'''.<br />
<br />
There is also a '''funtoo-experimental''', which contains our experimental development work. As you might guess, funtoo-experimental is for developers and testers only, and it has its own experimental Portage tree that is separate from the others.<br />
<br />
If you don't know which one to choose, pick '''funtoo-current'''.<br />
<br />
Picked one? Great! Open a mirror in a new window, and select the appropriate build directory from the list.<br />
<br />
<pre><br />
funtoo-current -><br />
</pre><br />
<br />
== Next... pick an arch ==<br />
<br />
'''Next, it's time to pick an ''architecture'''''. If you have a modern 64-bit PC-compatible desktop or server, you generally want '''x86-64bit'''. If you have an older 32-bit PC-compatible desktop or server, you'll want to use '''x86-32bit'''. Also an option for 64-bit x86 systems.<br />
<br />
We also bundle virtualization directories alongside the architecture directories, so if you want to install an [[OpenVZ]] container of Funtoo Linux, select '''openvz''', then pick the correct ''architecture'' within. Likewise, if you're looking for a [[VagrantUp|Vagrant]] run image of Funtoo Linux, look in the '''vagrant''' directory.<br />
<br />
If you are installing Funtoo Linux on a Sparc64 system, choose '''sparc-64bit'''.<br />
<br />
<pre><br />
funtoo-current -> x86-64bit<br />
</pre><br />
<br />
== Now... select a sub-arch ==<br />
<br />
Now, you'll need to pick a ''sub-architecture'' of Funtoo Linux that suits your needs. A sub-architecture is a build of Funtoo Linux that is optimized for your particular CPU. <br />
<br />
If you are building a Linux-based appliance or grabbing an image for mass-deployment, you might want to choose a generic sub-architecture that will be compatible with a wide range of processors. Otherwise, choose the most optimized sub-architecture that your processor supports.<br />
<br />
Note that we offer the greatest number of choices for '''funtoo-current'''. Other builds will have a more limited number of sub-arches available.<br />
<br />
=== x86-64bit ===<br />
<br />
* '''corei7''': Intel Core i3, Core i5 and Core i7 desktop processors or higher. Xeon 5500, 5600 and 7500 series server processors or higher. (Nehalem, Sandy Bridge) <br />
* '''core2_64''': Intel Core 2 series or higher, which include the Core 2 Solo, Duo, Quad and Extreme. Also suitable for Nehalem.<br />
* '''atom_64''': Intel Atom optimized. Compatible with Core 2 series.<br />
* '''amd64-k8''': AMD Opteron or Athlon 64 processors, or higher<br />
* '''amd64-k10''': AMD Phenom, Phenom II and compatible, or higher<br />
* '''generic_64''' : Generic 64-bit Intel/AMD processor<br />
<br />
=== x86-32bit ===<br />
<br />
*'''core2_32''': Intel Core 2 series or compatible, which include the Core 2 Solo, Duo, Quad and Extreme. Also suitable for Nehalem.<br />
*'''atom_32''': Intel Atom optimized. Compatible with Core 2 series.<br />
*'''amd64-k8_32: AMD Opteron or Athlon 64 processors, or higher.<br />
*'''athlon-xp''': Athlon XP or Opteron/Athlon 64.<br />
*'''i686''': Generic P6-class system<br />
*'''i486''': Intel 80486+ system<br />
<br />
You should now grab the most recent stage3 for the sub-architecture that you've chosen:<br />
<br />
<pre><br />
funtoo-current -> x86-64bit -> corei7 -> stage3-latest.tar.xz<br />
</pre></div>Oleghttp://www.funtoo.org/wiki/Funtoo_Linux_InstallationFuntoo Linux Installation2012-10-18T04:57:17Z<p>Oleg: /* Configuring and installing the Linux kernel */</p>
<hr />
<div>== Introduction ==<br />
<br />
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.<br />
<br />
=== Additional Resources ===<br />
<br />
This document was written to help you install Funtoo Linux as efficiently as possible, with a minimum number of distracting options regarding system configuration. <br />
<br />
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.<br />
<br />
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.<br />
<br />
== Installation Overview ==<br />
<br />
This is a basic overview of the Funtoo installation process:<br />
<br />
# [[#Live CD|Download and boot the live CD of your choice]].<br />
# [[#Prepare Hard Disk|Prepare your disk]].<br />
# [[#Creating filesystems|Create]] and [[#Mounting filesystems|mount]] filesystems.<br />
# [[#Installing the Stage 3 tarball|Install the Funtoo stage tarball]] of your choice.<br />
# [[#Chroot into Funtoo|Chroot into your new system]].<br />
# [[#Downloading the Portage tree|Download the Portage tree]].<br />
# [[#Configuring your system|Configure your system]] and [[#Configuring your network|network]].<br />
# [[#Configuring and installing the Linux kernel|Install a kernel]].<br />
# [[#Installing a Bootloader|Install a bootloader]].<br />
# [[#Finishing Steps|Complete final steps]].<br />
# [[#Restart your system|Reboot and enjoy]].<br />
<br />
=== Live CD ===<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Prepare Hard Disk ===<br />
==== Partitions ====<br />
<br />
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:<br />
<br />
===== GPT Partitions =====<br />
<br />
* Newer, preferred format for Linux systems<br />
* Supports 2 TB+ hard drives for booting<br />
* Supports hundreds of partitions per disk of any size<br />
* Requires legacy BIOS boot partition (~32 MB) to be created if system does not use EFI<br />
* Requires bootloader with support for GPT such as GRUB 2, EXTLINUX, or a patched version of GRUB Legacy<br />
<br />
===== MBR Partitions =====<br />
<br />
* Legacy, DOS partitioning scheme<br />
* Only 4 primary partitions per disk; after that, you must use "logical" partitions<br />
* Does not support 2 TB+ disks for booting<br />
* Compatible with certain problematic systems (such as the HP ProBook 4520)<br />
* Multiple boot loader options, e.g. GRUB 2, GRUB Legacy, lilo<br />
<br />
{{fancyimportant|If you plan to use partitions of 2 TB or greater, you ''must'' partition using the GPT/GUID format.}}<br />
<br />
==== Partitioning Using gdisk ====<br />
<br />
===== Notes Before We Begin =====<br />
<br />
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.<br />
<br />
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 <br />
'''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.<br />
<br />
Advanced users may be interested in the following topics:<br />
<br />
* [[GUID Booting Guide]]<br />
* [[Rootfs over encrypted lvm]]<br />
* [[Rootfs over encrypted lvm over raid-1 on GPT]]<br />
<br />
===== Using gdisk =====<br />
<br />
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:<br />
<br />
<console># ##i##gdisk /dev/sda</console><br />
You should find <tt>gdisk</tt> very similar to <tt>fdisk</tt>. Here is the partition table we want to end up with:<br />
<br />
<console>Command (? for help): ##i##p<br />
Disk /dev/sda: 234441648 sectors, 111.8 GiB<br />
Logical sector size: 512 bytes<br />
Disk identifier (GUID): A4E5208A-CED3-4263-BB25-7147DC426931<br />
Partition table holds up to 128 entries<br />
First usable sector is 34, last usable sector is 234441614<br />
Partitions will be aligned on 2048-sector boundaries<br />
Total free space is 2014 sectors (1007.0 KiB)<br />
<br />
Number Start (sector) End (sector) Size Code Name<br />
1 2048 206847 500.0 MiB 8300 Linux filesystem<br />
2 206848 272383 32.0 MiB EF02 BIOS boot partition<br />
3 272384 8660991 4.0 GiB 8200 Linux swap<br />
4 8660992 234441614 107.7 GiB 8300 Linux filesystem<br />
<br />
Command (? for help): </console><br />
<br />
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.<br />
<br />
===== For new <tt>gdisk</tt> users =====<br />
<br />
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.<br />
<br />
Within <tt>gdisk</tt>, follow these steps:<br />
<br />
'''Create Partition 1''' (boot):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##1 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+500M ↵<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
'''Create Partition 2''' (GRUB):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##2 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+32M ↵<br />
Hex Code: ##i##EF02 ↵<br />
</console><br />
<br />
'''Create Partition 3''' (swap):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##3 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##+4G ↵<br />
Hex Code: ##i##8200 ↵<br />
</console><br />
<br />
'''Create Partition 4''' (root):<br />
<br />
<console><br />
Command: ##i##n ↵<br />
Partition Number: ##i##4 ↵<br />
First sector: ##i##↵<br />
Last sector: ##i##↵##!i## (for rest of disk)<br />
Hex Code: ##i##↵<br />
</console><br />
<br />
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:<br />
<br />
'''Write Partition Table To Disk''':<br />
<br />
<console><br />
Command: ##i##w ↵<br />
Do you want to proceed? (Y/N): ##i##Y ↵<br />
</console><br />
<br />
The partition table will now be written to disk and <tt>gdisk</tt> will close.<br />
<br />
Now, your GPT/GUID partitions have been created, and will show up as the following ''block devices'' under Linux:<br />
<br />
* <tt>/dev/sda1</tt>, which will be used to hold the <tt>/boot</tt> filesystem, <br />
* <tt>/dev/sda2</tt>, which will be used directly by the new GRUB,<br />
* <tt>/dev/sda3</tt>, which will be used for swap space, and <br />
* <tt>/dev/sda4</tt>, which will hold your root filesystem.<br />
<br />
===== For Previous fdisk users =====<br />
<br />
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.<br />
<br />
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>.<br />
<br />
===== Partitioning Recommendations =====<br />
<br />
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>:<br />
<br />
{| {{table}} <br />
!Partition<br />
!Size<br />
!MBR Block Device (<tt>fdisk</tt>)<br />
!GPT Block Device (<tt>gdisk</tt>)<br />
!Filesystem<br />
!MBR Code<br />
!GPT Code<br />
|-<br />
|<tt>/boot</tt><br />
|500 MB<br />
|<tt>/dev/sda1</tt><br />
|<tt>/dev/sda1</tt><br />
|ext2<br />
|83<br />
|8300<br />
|-<br />
|GRUB boot loader partition<br />
|32 MB<br />
| ''not required for MBR''<br />
|<tt>/dev/sda2</tt><br />
|For GPT/GUID only, skip for MBR - no filesystem.<br />
|''N/A''<br />
|EF02<br />
|-<br />
|swap<br />
|2x RAM for low-memory systems and production servers; otherwise 2GB.<br />
|<tt>/dev/sda2</tt><br />
|<tt>/dev/sda3</tt><br />
|swap (default)<br />
|82<br />
|8200<br />
|-<br />
|<tt>/</tt> (root)<br />
|Rest of the disk, minimum of 10GB.<br />
|<tt>/dev/sda3</tt><br />
|<tt>/dev/sda4</tt><br />
|XFS recommended, alternatively ext4<br />
|83<br />
|8300<br />
|-<br />
|<tt>/home</tt> (optional) <br />
|User storage and media. Typically most of the disk.<br />
|<tt>/dev/sda4</tt> (if created)<br />
|<tt>/dev/sda5</tt> (if created)<br />
|XFS recommended, alternatively ext4<br />
|83<br />
|8300<br />
|-<br />
| LVM (optional)<br />
| If you want to create an LVM volume.<br />
| <tt>/dev/sda4</tt> (PV, if created)<br />
| <tt>/dev/sda5</tt> (PV, if created)<br />
| LVM PV<br />
| 8E<br />
| 8E00<br />
|}<br />
<br />
==== Creating filesystems ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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:<br />
<br />
<console><br />
# ##i##mke2fs -t ext2 /dev/sda1 <br />
# ##i##mkfs.xfs /dev/sda4<br />
# ##i##mkswap /dev/sda3<br />
# ##i##swapon /dev/sda3<br />
</console><br />
<br />
==== Mounting filesystems ====<br />
<br />
Mount the newly-created filesystems as follows, creating <tt>/mnt/funtoo</tt> as the installation mount point:<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo<br />
# ##i##mount /dev/sda4 /mnt/funtoo<br />
# ##i##mkdir /mnt/funtoo/boot<br />
# ##i##mount /dev/sda1 /mnt/funtoo/boot<br />
</console><br />
<br />
Optionally, if you have a separate filesystem for <tt>/home</tt> or anything else:<br />
<br />
<console><br />
# ##i##mkdir /mnt/funtoo/home<br />
# ##i##mount /dev/sda5 /mnt/funtoo/home<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##chmod 1777 /mnt/funtoo/tmp<br />
</console><br />
<br />
=== Installing the Stage 3 tarball ===<br />
==== Stage 3 tarball ====<br />
<br />
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.<br />
<br />
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:<br />
<br />
<console><br />
# ##i##date<br />
Fri Jul 15 19:47:18 UTC 2011<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##date 071620002011<br />
Fri Jul 16 20:00:00 UTC 2011<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
# ##i##wget http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-64bit/generic_64/stage3-latest.tar.xz<br />
</console><br />
<br />
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.<br />
<br />
Once the stage is downloaded, extract the contents with the following command, substituting in the actual name of your stage 3 tarball:<br />
<console># ##i##tar xJpf stage3-latest.tar.xz</console><br />
<br />
{{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.}}<br />
<br />
=== Chroot into Funtoo ===<br />
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:<br />
<console><br />
# ##i##cd /mnt/funtoo<br />
# ##i##mount --bind /proc proc<br />
# ##i##mount --bind /dev dev<br />
</console><br />
<br />
You'll also want to copy over <tt>resolv.conf</tt> in order to have proper DNS name resolution from inside the chroot:<br />
<console><br />
# ##i##cp /etc/resolv.conf etc<br />
</console><br />
<br />
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:<br />
<br />
<console><br />
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l<br />
</console><br />
<br />
{{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.}}<br />
<br />
{{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.}}<br />
<br />
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:<br />
<console><br />
# ##i##export PS1="(chroot) $PS1"<br />
</console><br />
<br />
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.<br />
<br />
=== Downloading the Portage tree ===<br />
<br />
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]:<br />
<br />
<console><br />
(chroot) # ##i##emerge --sync<br />
</console><br />
<br />
{{fancynote|For an alternative way to do this, see [[Installing Portage From Snapshot]].}}<br />
<br />
=== Configuring your system ===<br />
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:<br />
<br />
{| {{table}}<br />
!File<br />
!Do I need to change it?<br />
!Description<br />
|-<br />
|<tt>/etc/fstab</tt><br />
|'''YES - required'''<br />
|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.<br />
|-<br />
|<tt>/etc/localtime</tt><br />
|''Maybe - recommended''<br />
|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) <br />
|-<br />
|<tt>/etc/make.conf<br/><br />
/etc/portage/make.conf</tt> (new location)<br />
|''Maybe - recommended''<br />
|Parameters used by gcc (compiler), portage, and make. It's a good idea to set MAKEOPTS. This is covered later in this document.<br />
|-<br />
|<tt>/etc/conf.d/hostname</tt><br />
|''Maybe - recommended''<br />
|Used to set system hostname. Set to the fully-qualified (with dots) name. Defaults to <tt>localhost</tt> if not set.<br />
|-<br />
|<tt>/etc/hosts</tt><br />
|''No''<br />
| You no longer need to manually set the hostname in this file. This file is automatically generated by <tt>/etc/init.d/hostname</tt>.<br />
|-<br />
|<tt>/etc/conf.d/keymaps</tt><br />
|Optional<br />
|Keyboard mapping configuration file (for console pseudo-terminals). Set if you have a non-US keyboard. See [[Funtoo Linux Localization]].<br />
|-<br />
|<tt>/etc/conf.d/hwclock</tt><br />
|Optional<br />
|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.<br />
|-<br />
|<tt>/etc/conf.d/modules</tt><br />
|Optional<br />
|Kernel modules to load automatically at system startup. Typically not required. See [[Additional Kernel Resources]] for more info.<br />
|}<br />
<br />
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]])<br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
==== /etc/fstab ====<br />
<br />
<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:<br />
<br />
<console><br />
(chroot) # ##i##nano -w /etc/fstab<br />
</console><br />
<br />
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.<br />
<br />
<pre><br />
# The root filesystem should have a pass number of either 0 or 1.<br />
# All other filesystems should have a pass number of 0 or greater than 1.<br />
#<br />
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.<br />
#<br />
# See the manpage fstab(5) for more information.<br />
#<br />
# <fs> <mountpoint> <type> <opts> <dump/pass><br />
<br />
/dev/sda1 /boot ext2 noauto,noatime 1 2<br />
/dev/sda3 none swap sw 0 0<br />
/dev/sda4 / xfs noatime 0 1<br />
#/dev/cdrom /mnt/cdrom auto noauto,ro 0 0<br />
none /dev/shm tmpfs nodev,nosuid,noexec 0 0<br />
</pre><br />
<br />
==== /etc/localtime ====<br />
<br />
<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. <br />
<br />
<pre><br />
(chroot) # ln -sf /usr/share/zoneinfo/America/Montreal /etc/localtime<br />
</pre><br />
<br />
The above sets the timezone to Eastern Time Canada. Go to <tt>/usr/share/zoneinfo</tt> to see which values to use.<br />
<br />
==== /etc/portage/make.conf ====<br />
<br />
{{fancynote|This file may also be found at /etc/make.conf. /etc/portage/make.conf is the new location.}}<br />
<br />
This file contains something similar to the following:<br />
<br />
<pre><br />
ACCEPT_KEYWORDS="~amd64"<br />
CHOST="x86_64-pc-linux-gnu"<br />
</pre><br />
<br />
<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>.<br />
<br />
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:<br />
<br />
<pre><br />
MAKEOPTS="-j3" <br />
</pre><br />
<br />
If you are unsure about how many processors/threads you have then use /proc/cpuinfo to help you.<br />
<console><br />
(chroot) # ##i##grep "processor" /proc/cpuinfo | wc -l<br />
16<br />
</console><br />
<br />
Set MAKEOPTS to this number plus one:<br />
<br />
<pre><br />
MAKEOPTS="-j17"<br />
</pre><br />
<br />
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].<br />
<br />
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:<br />
<br />
<pre><br />
LINGUAS="fr"<br />
</pre><br />
<br />
==== /etc/conf.d/hwclock ====<br />
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.<br />
<console><br />
(chroot) # ##i##nano -w /etc/conf.d/hwclock<br />
</console><br />
<br />
==== Localization ====<br />
<br />
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]].<br />
<br />
=== Configuring your network ===<br />
<br />
If you plan on using DHCP for network configuration, it is not necessary to emerge a DHCP client. In fact, it would not even be necessary to perform any manual network configuration at all. Simply add <tt>dhcpcd</tt> to the <tt>default</tt> runlevel, and your network will be configured automatically at boot.<br />
<br />
<console><br />
(chroot) # ##i##rc-update add dhcpcd default<br />
</console><br />
<br />
That's it! If you require more advanced configuration, see [[Funtoo Linux Networking]] for information on how to use Funtoo Linux's template-based network configuration system.<br />
<br />
=== Configuring and installing the Linux kernel ===<br />
<br />
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.<br />
<br />
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.<br />
<br />
{{fancyimportant|<tt>debian-sources</tt> with <tt>binary</tt> USE flag requires at least 12GB in /var/tmp}}<br />
<br />
<console><br />
(chroot) # ##i##echo "sys-kernel/debian-sources binary" >> /etc/portage/package.use<br />
(chroot) # ##i##emerge debian-sources<br />
</console><br />
<br />
All done!<br />
<br />
{{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>.}}<br />
<br />
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.<br />
<br />
The next step is to configure your boot loader so that your new kernel loads when the system boots.<br />
<br />
=== Installing a Bootloader ===<br />
<br />
==== Installing Grub ====<br />
<br />
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.<br />
<br />
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>.<br />
<br />
<console><br />
(chroot) # ##i##emerge boot-update<br />
</console><br />
<br />
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>. <br />
<br />
<tt>/etc/boot.conf</tt> should now look like this:<br />
<br />
<pre><br />
boot {<br />
generate grub<br />
default "Funtoo Linux genkernel"<br />
timeout 3 <br />
}<br />
<br />
"Funtoo Linux" {<br />
kernel bzImage[-v]<br />
# params += nomodeset<br />
}<br />
<br />
"Funtoo Linux genkernel" {<br />
kernel kernel[-v]<br />
initrd initramfs[-v]<br />
params += real_root=auto <br />
# params += nomodeset<br />
} <br />
</pre><br />
<br />
Please read <tt>man boot.conf</tt> for further details.<br />
<br />
===== Running grub-install and boot-update =====<br />
<br />
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:<br />
<br />
<console><br />
(chroot) # ##i##grub-install --no-floppy /dev/sda<br />
(chroot) # ##i##boot-update<br />
</console><br />
<br />
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.<br />
<br />
OK - your system should be ready to boot! Well, there are a few more loose ends...<br />
<br />
==== Installing Syslinux/Extlinux ====<br />
<br />
An alternate Bootloader is Extlinux, for installing it see the [[Extlinux|extlinux Guide]].<br />
<br />
=== Finishing Steps ===<br />
<br />
==== Set your root password ====<br />
It's imperative that you set your root password before rebooting so that you can log in.<br />
<console><br />
(chroot) # ##i##passwd<br />
</console><br />
<br />
===Restart your system ===<br />
<br />
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.<br />
<br />
Leave the chroot, change directory to /, unmount your Funtoo partitions, and reboot.<br />
<console><br />
(chroot) # exit<br />
# ##i##cd /<br />
# ##i##umount /mnt/funtoo/boot /mnt/funtoo/dev /mnt/funtoo/proc /mnt/funtoo<br />
# ##i##reboot<br />
</console><br />
<br />
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!<br />
<br />
===Next Steps===<br />
<br />
To learn how to customize and start using Funtoo Linux, see [[Funtoo Linux First Steps]].<br />
<br />
If your system did not boot correctly, see [[Installation Troubleshooting]] for steps you can take to resolve the problem.<br />
<br />
[[Category:HOWTO]]<br />
[[Category:Install]]</div>Oleghttp://www.funtoo.org/wiki/Funtoo_Linux_KernelsFuntoo Linux Kernels2012-10-18T04:56:22Z<p>Oleg: /* Using Debian-Sources with Genkernel */</p>
<hr />
<div>This Section will give you an overview of kernels used in funtoo.<br />
<br />
Funtoo Linux provides a number of new kernels for your use. This is the official page for all Funtoo Linux kernel information. <br />
<br />
Some points of interest:<br />
<br />
* Most Funtoo Linux kernels support the handy <tt>[[#Binary USE|binary]]</tt> USE flag, described below.<br />
* Funtoo Linux offers quality kernels from other Linux Distributions, like <tt>ubuntu-server</tt> and <tt>debian-sources</tt>.<br />
* A detailed [[#Kernel Features and Stability|Kernel Features and Stability]] table can be found below.<br />
* Advanced users may want to take a look at [[Additional Kernel Resources]].<br />
* There is a quick'n dirty howto to compile your own [[kernel]] with initramfs the funtoo way.<br />
<br />
== Overview of Kernels ==<br />
<br />
=== sysrescue-std-sources ===<br />
<br />
This kernel is from the [http://www.sysresccd.org SystemRescueCD project], and is based on Fedora 14/15, plus some other patches related to booting from a live CD. It is a quality kernel, and is generally pretty stable. It is not suitable for production servers but is a good choice for Funtoo Linux desktops. The [[Funtoo Linux Installation]] Guide recommends this kernel for general users. Note however, that by design all audio functions are removed from SystemRescue, ie no sound when using this kernel.<br />
<br />
=== vanilla-sources ===<br />
<br />
This will install the "vanilla" (unmodified) Linux kernel sources. Current recommended version is 3.x. Funtoo Linux fully supports Linux 3.x. The advantages of this kernel include recent improvements to [[Linux Containers]], a very modern networking stack with lots of bug fixes, and high reliability for desktops and servers. The downside is that this kernel must be manually configured by the user and does not have built-in <tt>genkernel</tt> support via the <tt>binary</tt> USE flag at this time.<br />
<br />
=== openvz-rhel6-stable ===<br />
<br />
This is a RHEL6-based kernel with OpenVZ support. This kernel is now the preferred kernel for production OpenVZ deployments. It requires gcc-4.4.5 to build, which it will use automatically without the user needing to use <tt>gcc-config</tt>. We use this version of gcc since this is the version of gcc used by Red Hat to build this kernel.<br />
<br />
=== openvz-rhel5-stable ===<br />
<br />
This kernel is based on the latest Red Hat Enterprise Linux 5.6 kernel, and contains additional OpenVZ (virtual containers) patches from the [[OpenVZ on Funtoo Linux|OpenVZ]] project. It is a very stable and reliable kernel, and is recommended for use in production environments. The only major downside to this kernel is that it is based on Linux 2.6.18 -- some parts of the kernel are out-of-date, and it is not compatible with modern versions of udev. However, it is pretty trivial to downgrade udev to an earlier version on Funtoo Linux and this kernel has a track-record of being rock-solid. When stability is paramount, you put up with the udev downgrade, use this kernel, and can enjoy hundreds of days of uptime. For more information on how to use this kernel with Funtoo Linux, see the [[RHEL5 Kernel HOWTO]].<br />
<br />
=== ubuntu-server ===<br />
<br />
This is the kernel from Ubuntu Server. Version <tt>2.6.32.32.62</tt> is the same version used in Ubuntu Server 10.04 LTS, and version <tt>2.6.35.28.50</tt> is the one used in Ubuntu Server 10.10 (currently masked). In our testing of <tt>2.6.32.32.62</tt>, it has been very reliable and offers very good performance. One exception, which is common among 2.6.32-based kernels, is that it's recommended that you emerge <tt>broadcom-netxtreme2</tt> if you have any Broadcom-based NICs, as the in-kernel drivers have compatibility issues with certain models. This kernel is a very good option if you want a relatively modern server kernel and do not need [[OpenVZ]] support. We use gcc-4.4.5 to build this kernel. It will use gcc-4.4.5 automatically, without requiring the user to use <tt>gcc-config</tt>.<br />
<br />
=== debian-sources ===<br />
<br />
This is the Debian kernel. '''These ebuilds now support the <tt>binary</tt> USE flag.''' Daniel has added a special <tt>config-extract</tt> command which can be used to list all available official Debian kernel configurations, and generate them from the Debian files included with the kernel. This kernel has optional [[OpenVZ]] support, but it is much better to use <tt>openvz-rhel6-stable</tt> if you want a production-quality OpenVZ installation. For more information about how to use <tt>debian-sources</tt> and <tt>config-extract</tt>, see [[#Using debian-sources with Genkernel|Using debian-sources with Genkernel]] below. <br />
<br />
=== debian-sources-lts ===<br />
<br />
This is the Debian long-term stable kernel. '''These ebuilds now support the <tt>binary</tt> USE flag.''' Daniel has added a special <tt>config-extract</tt> command which can be used to list all available official Debian kernel configurations, and generate them from the Debian files included with the kernel.<br />
<br />
== Binary USE ==<br />
<br />
Many of the kernel ebuilds in Funtoo Linux support the very useful <tt>binary</tt> USE flag. By enabling this USE flag and emerging the kernel, the ebuild will automatically build a binary kernel image, initramfs and kernel modules and install them to <tt>/boot</tt>. The binary kernel image and initramfs can be used to boot your Funtoo Linux system without requiring any additional configuration. This is a great way to get a Funtoo Linux system up and running quickly. Here's how to do it:<br />
<br />
<pre><br />
# echo "sys-kernel/openvz-rhel5-stable binary" >> /etc/portage/package.use<br />
# emerge openvz-rhel5-stable<br />
# nano -w /etc/boot.conf<br />
# boot-update<br />
</pre><br />
<br />
More information can be found in the [[Funtoo Linux Installation]] Guide.<br />
<br />
== Funtoo Linux Genkernel ==<br />
<br />
Funtoo Linux contains a forked/enhanced version of genkernel with the following new capabilities:<br />
<br />
* genkernel can use a build directory that is separate from the kernel source directory. This is enabled using the new <tt>--build-dst</tt> option.<br />
* <tt>--build-src</tt> is a new option that is equivalent to the <tt>--kerneldir</tt> option.<br />
* <tt>--fullname</tt> can be used to specify the entire name of the kernel and initramfs images -- everything after <tt>kernel-</tt> and <tt>initramfs-</tt>.<br />
* <tt>--firmware-src</tt> - a new option that works identically to <tt>--firmware-dir</tt>.<br />
* <tt>--firmware-dst</tt> - a new capability - you can now define where genkernel installs firmware.<br />
* Genkernel uses Funtoo Linux <tt>lvm2</tt> rather than building its own.<br />
* Some compile fixes.<br />
<br />
== Kernel Features and Stability ==<br />
<br />
This page provides an overview of kernel features and stability information:<br />
<br />
{| {{table}} <br />
!Kernel Name<br />
!Version<br />
!USE flags<br />
!Stability<br />
!Extra Features<br />
!Req'd udev<br />
!Notes<br />
|-<br />
|<tt>[[#vanilla-sources|vanilla-sources]]</tt><br />
|3.1.5<br />
|N/A<br />
|'''Excellent''' - recommended for desktops and servers.<br />
|N/A<br />
|Any<br />
|Recommended for modern networking stack, hardware and [[Linux Containers]] support. This kernel must be manually configured by the user.<br />
|-<br />
|<tt>[[#sysrescue-std-sources|sysrescue-std-sources]]</tt><br />
|2.6.35.210<br />
|<tt>binary</tt><br />
|''Good'' - recommended for desktops<br />
|N/A<br />
|Any<br />
|Nvidia card users: binary use flag installs nouveau drivers. Not compatible with nvidia-drivers.<br />
|-<br />
|<tt>[[#openvz-rhel6-stable|openvz-rhel6-stable]]</tt><br />
|2.6.32.042.044.11<br />
|<tt>binary</tt><br />
|'''Excellent''' - recommended for production servers<br />
|N/A<br />
|Any<br />
|This kernel is built with gcc-4.4.5. <tt>emerge broadcom-netxtreme2</tt> for reliable BCM5709+ support (integrated NIC)<br />
|-<br />
|<tt>[[#openvz-rhel5-stable|openvz-rhel5-stable]]</tt><br />
|2.6.18.028.095.1<br />
|<tt>binary</tt><br />
|'''Excellent''' - recommended for production servers<br />
|OpenVZ<br />
|=sys-fs/udev-146*<br />
|Broadcom <tt>bnx2</tt> driver module bundled with kernel appears to be OK. This kernel is built with gcc-4.1.2. Enabling the <tt>binary</tt> USE flag will cause gcc-4.1.2 to be emerged and used for building the kernel.<br />
|-<br />
|<tt>[[#ubuntu-server|ubuntu-server]]</tt><br />
|2.6.32.32.62<br />
|<tt>binary</tt><br />
|'''Excellent''' - recommended for production servers (still in extended testing)<br />
| N/A<br />
|Any<br />
|This kernel is built with gcc-4.4.5. <tt>emerge broadcom-netxtreme2</tt> for reliable BCM5709+ support (integrated NIC)<br />
|-<br />
|<tt>[[#ubuntu-server|ubuntu-server]]</tt><br />
|2.6.35.28.50<br />
|<tt>binary</tt><br />
|''not yet tested''<br />
| N/A<br />
|Any<br />
|This kernel is built with gcc-4.4.5. <tt>emerge broadcom-netxtreme2</tt> for reliable BCM5709+ support (integrated NIC)<br />
|-<br />
|<tt>[[#debian-sources|debian-sources]]</tt><br />
|2.6.32.30<br />
|<tt>openvz</tt><br />
|''Good'' - still being evaluated by Funtoo<br />
|OpenVZ (optional)<br />
|Any<br />
|See [[#Using debian-sources with Genkernel]], below.<br />
|-<br />
|}<br />
<br />
== Using Debian-Sources with Genkernel ==<br />
<br />
{{ fancyimportant|Debian-sources is now fully compatible with ''binary'' USE flag and recommended for desktop users. The below example is valid for manual installation. At least 12G of /var/tmp required to build <br />
}}<br />
This section describes how to build a binary kernel with <tt>debian-sources</tt> and <tt>genkernel</tt>, and it also explains how to use Funtoo Linux's <tt>config-extract</tt> tool to list and create official Debian kernel configurations.<br />
<br />
=== First step: emerging the required packages ===<br />
<br />
The first step is to emerge:<br />
<br />
# The Debian sources<br />
# Genkernel itself<br />
<br />
This is achieved with:<br />
<br />
<pre><br />
# emerge sys-kernel/debian-sources sys-kernel/genkernel<br />
</pre><br />
<br />
Once the Debian kernel sources are deployed, you should find a directory named '''linux-debian-''version''''' (e.g. linux-debian-2.6.32.30) under '''/usr/src'''. Update your the '''linux''' symlink to point on this directory:<br />
<pre><br />
# cd /usr/src<br />
# rm linux<br />
# ln -s linux-debian-2.6.32.30 linux<br />
</pre><br />
Alternatively, emerge the debian-sources with USE="symlink"<br />
=== Second step: Grabbing a configuration file ===<br />
<br />
If is now time to download the kernel configuration file. For this tutorial we will use a configuration file for AMD64 (several others architectures like MIPS or SPARC64 are available.) To view a complete list of available kernel configurations, type <tt>./config-extract -l</tt> in the Debian kernel source directory:<br />
<br />
<pre><br />
ninja1 linux-debian-2.6.32.30 # ./config-extract -l<br />
<br />
====== standard featureset ======<br />
<br />
alpha: alpha-generic, alpha-legacy, alpha-smp<br />
amd64<br />
armel: iop32x, ixp4xx, kirkwood, orion5x, versatile<br />
hppa: parisc, parisc-smp, parisc64, parisc64-smp<br />
i386: 486, 686, 686-bigmem, amd64<br />
ia64: itanium, mckinley<br />
m68k: amiga, atari, bvme6000, mac, mvme147, mvme16x<br />
mips: 4kc-malta, 5kc-malta, r4k-ip22, r5k-ip32, sb1-bcm91250a, sb1a-bcm91480b<br />
mipsel: 4kc-malta, 5kc-malta, r5k-cobalt, sb1-bcm91250a, sb1a-bcm91480b<br />
powerpc: powerpc, powerpc-smp, powerpc64<br />
s390: s390x, s390x-tape<br />
sh4: sh7751r, sh7785lcr<br />
sparc: sparc64, sparc64-smp<br />
sparc64: sparc64, sparc64-smp<br />
<br />
====== vserver featureset ======<br />
<br />
amd64<br />
i386: 686, 686-bigmem<br />
ia64: itanium, mckinley<br />
powerpc: powerpc, powerpc64<br />
s390<br />
sparc<br />
sparc64<br />
<br />
====== xen featureset ======<br />
<br />
amd64<br />
i386<br />
<br />
====== openvz featureset ======<br />
<br />
amd64<br />
i386<br />
</pre><br />
<br />
Type <tt>config-extract -h</tt> for extended usage information:<br />
<br />
<pre><br />
ninja1 linux-debian-2.6.32.30 # ./config-extract -h<br />
This work is free software.<br />
<br />
Copyright 2011 Funtoo Technologies. You can redistribute and/or modify it under<br />
the terms of the GNU General Public License version 3 as published by the Free<br />
Software Foundation. Alternatively you may (at your option) use any other<br />
license that has been publicly approved for use with this program by Funtoo<br />
Technologies (or its successors, if any.)<br />
<br />
usage: config-extract [options] arch [featureset] [subarch]<br />
<br />
-h --help print this usage and exit<br />
-l --list list all available kernel configurations<br />
-o --outfile specify kernel config outfile --<br />
defaults to .config in current directory<br />
[featureset] defaults to "none" if not specified<br />
[subarch] defaults to the only one available; otherwise required<br />
<br />
This program was written by Daniel Robbins for Funtoo Linux, for the purpose of<br />
easily and conveniently extracting Debian kernel configurations. To see a nice<br />
list of all available kernel configurations, use the --list option.<br />
<br />
Debian's kernel configs are specified internally in arch_featureset_flavor<br />
format, such as: "amd64_openvz_amd64". The featureset typically describes an<br />
optional kernel configuration such as "xen" or "openvz", while the flavor in<br />
Debian terminology typically refers to the sub-architecture of the CPU.<br />
<br />
When using this command, you must specify an arch. A featureset of "none" is<br />
assumed unless you specify one, and by default this program will pick the only<br />
available subarch if there is only one to choose from. If not, you will need to<br />
pick one (and the program will remind you to do this.)<br />
<br />
The kernel configuration will be written to ".config" in the current directory,<br />
or the location you specified using the -o/--outfile option.<br />
</pre><br />
<br />
Let's use <tt>config-extract</tt> to create a kernel configuration for an amd64 system:<br />
<br />
<pre><br />
# cd linux<br />
# ./config-extract amd64<br />
Wrote amd64_none_amd64 kernel configuration to /usr/src/linux-debian-2.6.32.30/.config.<br />
</pre><br />
<br />
<tt>config-extract</tt> also allows you to extract special Debian featuresets, such as settings for Xen and [[OpenVZ]] kernels:<br />
<br />
<pre><br />
# ./config-extract amd64 openvz<br />
Wrote amd64_openvz_amd64 kernel configuration to /usr/src/linux-debian-2.6.32.30/.config.<br />
</pre><br />
<br />
After using <tt>config-extract</tt>, run <tt>make oldconfig</tt> and accept all default options by hitting Enter at all prompts.<br />
<br />
=== Third step: Building and installing the kernel ===<br />
<br />
This is simply achieved by:<br />
<br />
<pre><br />
# genkernel --kernel-config=config-2.6.32-5-amd64 all<br />
</pre><br />
<br />
* --kernel-config: use the given configfile. If you only give a filename here, it is searched for in your current working dir. You can also use a relative or an absolute path leading to your configfile here (for example: "--kernel-config=/usr/src/linux/configfile").<br />
* all: rebuild the kernel image and the initramfs ramdisk image (aside of kernel modules, the ramdisk image contains tools such as BusyBox and some generic startup scripts, depending on options you use on the command line several additional tools like lvm or raid volume management can be incorporated as well).<br />
<br />
{{ fancyimportant|Unless explicitly stated via ''--no-clean'' or ''--no-mrproper'', Genkernel will do a '''make mrproper''' in the kernel source tree, thus cleaning a previous build '''and removing the previous kernel configuration file''' in it. <br />
}}<br />
<br />
If you use Genkernel to rebuild a Linux kernel on SPARC64, remember to either:<br />
* Set '''sparc64-unknown-linux-gnu-''' in ''General setup --> Cross-compiler tool prefix'' <br />
* Put '''--kernel-cross-compile=sparc64-unknown-linux-gnu-''' on the Genkernel command line<br />
<br />
Once the kernel has been compiled and the ram disk has been generated, the kernel image plus its companion files (initramfs image and System.map) are placed in the /boot directory. You can use your favourite tool to update your bootloader configuration files.<br />
<br />
[[Category:Internals]]</div>Oleghttp://www.funtoo.org/wiki/Metro_Quick_Start_TutorialMetro Quick Start Tutorial2012-10-14T05:32:20Z<p>Oleg: /* Installing Metro */</p>
<hr />
<div>[[Metro]] is the build system for [[Funtoo Linux]] and [[Gentoo Linux]] stages. It automates the bootstrapping process.<br />
<br />
This tutorial will take you through installing, setting up and running [[Metro]].<br />
<br />
= Preface = <br />
<br />
== How Metro Works == <br />
<br />
You may be wondering how [[Metro]] creates its first stage tarball. As you may have guessed, [[Metro]] cannot create a stage tarball out of thin air. To build a new stage tarball, [[Metro]] must use an existing, older stage tarball called a &quot;seed&quot; stage. This &quot;seed&quot; stage typically is used as the ''build environment'' for creating the stage we want.<br />
<br />
[[Metro]] can use two kinds of seed stages. Traditionally, [[Metro]] has used a stage3 as a seed stage. This stage3 is then used to build a new stage1, which in turn is used to build a new stage2, and then a new stage3. This is generally the most reliable way to build [[Gentoo Linux]] or [[Funtoo Linux]], so it's the recommended approach.<br />
<br />
== Seeds and Build Isolation ==<br />
<br />
Another important concept to mention here is something called ''build isolation''. Because [[Metro]] creates an isolated build environment, and the build environment is explicitly defined using existing, tangible entities -- a seed stage and a portage snapshot -- you will get consistent, repeatable results. In other words, the same seed stage, portage snapshot and build instructions will generate an essentially identical result, even if you perform the build a month later on someone else's workstation.<br />
<br />
== Local Build == <br />
<br />
Say you wanted to build a new <tt>pentium4</tt> stage3 tarball. The recommended method of doing this would be to grab an existing <tt>pentium4</tt> stage3 tarball to use as your seed stage. [[Metro]] will be told to use this existing <tt>pentium4</tt> stage3 to build a new stage1 for the same <tt>pentium4</tt>. For this process, the generic <tt>pentium4</tt> stage3 would provide the ''build environment'' for creating our new stage1. Then, the new stage1 would serve as the build environment for creating the new <tt>pentium4</tt> stage2. And the new <tt>pentium4</tt> stage2 would serve as the build environment for creating the new <tt>pentium4</tt> stage3.<br />
<br />
In the [[Metro]] terminology this is called a '''local build''', which means a stage3 of a given architecture is used to seed a brand new build of the same architecture. Incidentally this will be the first exercise we are going to perform in this tutorial.<br />
<br />
A week later, you may want to build a brand new <tt>pentium4</tt> stage3 tarball. Rather than starting from the original <tt>pentium4</tt> stage3 again, you'd probably configure [[Metro]] to use the most-recently-built <tt>pentium4</tt> stage3 as the seed. [[Metro]] has built-in functionality to make this easy, allowing it to easily find and track the most recent stage3 seed available.<br />
<br />
== Remote Build == <br />
<br />
[[Metro]] can also perform '''remote build''', where a stage3 of a different, but binary compatible, architecture is used as a seed to build a different architecture stage3. Consequentiality the second exercise we are going to perform in this tutorial will be to build a <tt>core2 32bit</tt> stage3 tarball from the <tt>pentium4</tt> stage3 tarball we have just built.<br />
<br />
TODO: add caveats about what archs can be seeded and what can be not (maybe a table?)<br />
<br />
== Tailored Build == <br />
<br />
Last, it's also worthy noting that both in <tt>local</tt> and <tt>remote builds</tt>, [[Metro]] can be configured to add and/or remove individual packages to the final tarball.<br />
Let's say you can't live without <tt>app-misc/screen</tt>, at the end of this tutorial, we will show how to have your tailored stage3 to include it.<br />
<br />
= Installing Metro =<br />
<br />
Today the '''recommended and supported method''' is to use the Git repository of [[Metro]]. First ensure you remove the <tt>dev-util/metro</tt> package if you had installed it:<br />
<br />
<pre><br />
(~) # emerge -aC dev-util/metro<br />
</pre><br />
<br />
Then ensure that <tt>dev-vcs/git</tt> is installed on your system:<br />
<br />
<pre><br />
(~) # emerge dev-vcs/git<br />
</pre><br />
<br />
Next, clone the master git repository as follows:<br />
<br />
<pre><br />
(~) # install -d /root/git<br />
(~) # cd /root/git<br />
(~/git) # git clone git://github.com/funtoo/metro.git<br />
(~/git) # ln -s /root/git/metro /usr/lib/metro<br />
(~/git) # ln -s /root/git/metro/metro /usr/bin/metro<br />
</pre><br />
<br />
You will now have a directory called <tt>/root/git/metro</tt> that contains all the [[Metro]] source code.<br />
Installation complete!<br />
<br />
= Configuring Metro =<br />
<br />
[[User:Drobbins|Daniel Robbins]] maintains [[Metro]], so it comes pre-configured to successfully build both [[Gentoo Linux]] and [[Funtoo Linux]] releases. Before reading farther, you might want to customize some basic settings like the number of concurrent jobs to fit your hardware's capabilities or the directory to use for produced stage archives. This is accomplished by editing <tt>/root/git/metro/etc/metro.conf</tt> which is the [[Metro]]'s master configuration file. The <tt>[path/mirror]</tt> section defines where [[Metro]] will look for things it needs and also dump things it creates. As initially configured, [[Metro]] is set up to build [[Funtoo Linux]] and [[Gentoo Linux]] stage tarballs and place them in the <tt>/home/mirror/linux</tt> directory:<br />
<br />
<pre><br />
# Mirror Paths - where to find required files and where to put created files<br />
<br />
[section path/mirror]<br />
<br />
: /home/mirror/linux<br />
</pre><br />
<br />
If you want to change the location of your mirror on disk, then edit the <tt>/home/mirror/linux</tt> line (which defines the path/mirror variable) to point to another directory.<br />
<br />
For the purpose of the following steps, set an environment variable:<br />
<br />
<pre><br />
(~) # export METRO_MIRROR=/home/mirror/linux<br />
</pre> <br />
<br />
Of course, set the environment variable to whatever location you used in the configuration file.<br />
<br />
== Arch and Subarch ==<br />
<br />
In the following example we are creating a pentium4 stage 3 compiled for x86-32bit binary compatibility. Pentium4 is a subarch of the x86-32bit architecture. Once you have metro installed you may find a full list of each subarch in your <tt>/usr/lib/metro/subarch</tt> directory each subarch will have the file extension .spec<br />
Example:<br />
<pre> <br />
# ls /usr/lib/metro/subarch/<br />
amd64-k10.spec athlon-tbird.spec generic_32.spec native_32.spec pentium-mmx.spec<br />
amd64-k8_32.spec athlon-xp.spec generic_64.spec native_64.spec pentium-m.spec<br />
amd64-k8.spec atom_32.spec generic_sparcv9.spec niagara2.spec pentiumpro.spec<br />
amd64-k8+sse3_32.spec atom_64.spec geode.spec niagara.spec pentium.spec<br />
amd64-k8+sse3.spec btver1_64.spec i486.spec nocona.spec prescott.spec<br />
armv7a.spec btver1.spec i686.spec opteron_64.spec ultrasparc3.spec<br />
athlon-4.spec core2_32.spec k6-2.spec pentium2.spec ultrasparc.spec<br />
athlon-mp.spec core2_64.spec k6-3.spec pentium3.spec xen-pentium4+sse3_64.spec<br />
athlon.spec corei7.spec k6.spec pentium4.spec xen-pentium4+sse3.spec<br />
</pre><br />
<br />
For an example list of Architectures, take a look at the directory listing on the [http://ftp.osuosl.org/pub/funtoo/funtoo-current/ Funtoo-Current Mirror].<br />
<br />
= First stages build (local build) =<br />
<br />
To get this all started, we need to bootstrap the process by downloading an initial seed stage3 to use for building and place it in is proper location in <tt>/home/mirror/linux</tt>, so that [[Metro]] can find it. We will also need to create some special &quot;control&quot; files in <tt>/home/mirror/linux</tt>, which will allow [[Metro]] to understand how it is supposed to proceed.<br />
<br />
== Step 0: Optional Quick Copy of Portage Tree ==<br />
<br />
There is a quick step you can perform to avoid having Metro re-clone the entire Portage tree. Perform this as root:<br />
<br />
<pre><br />
# cd /usr/portage; git checkout origin/master<br />
# install -d /var/tmp/metro/cache/cloned-repositories<br />
# cat /root/git/metro/etc/builds/funtoo-current/build.conf | grep name<br />
name: portage-mini-2011<br />
# cp -a /usr/portage /var/tmp/metro/cache/cloned-repositories/portage-mini-2011<br />
# cd /usr/portage; git checkout funtoo.org<br />
</pre><br />
<br />
== Step 1: Set up pentium4 repository (local build) ==<br />
<br />
Assuming we're following the basic steps outlined in the previous section, and building an unstable funtoo (<tt>funtoo-current</tt>) build for the <tt>pentium4</tt>, using a generic <tt>pentium4</tt> stage3 as a seed stage, then here the first set of steps we'd perform:<br />
<br />
<pre><br />
(~) # install -d "${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"<br />
(~) # cd "${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # install -d 2011-12-13<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # cd 2011-12-13<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4/2011-12-13) # wget -c http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-32bit/pentium4/2011-12-13/stage3-pentium4-funtoo-current-2011-12-13.tar.xz<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4/2011-12-13) # cd ..<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # install -d .control/version<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # echo &quot;2011-12-13&quot; &gt; .control/version/stage3<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # install -d .control/strategy<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # echo &quot;local&quot; &gt; .control/strategy/build<br />
(/home/mirror/linux/funtoo-current/x86-32bit/pentium4) # echo &quot;stage3&quot; &gt; .control/strategy/seed<br />
</pre><br />
<br />
OK, let's review the steps above. First, we create the directory <tt>"${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"</tt>, which is where Metro will expect to find unstable <tt>funtoo-current</tt> pentium4 builds -- it is configured to look here by default. Then we create a specially-named directory to house our seed x86 stage3. Again, by default, Metro expects the directory to be named this way. We enter this directory, and download our seed x86 stage3 from funtoo.org. Note that the <tt>2010-12-24</tt> version stamp matches. Make sure that your directory name matches the stage3 name too. Everything has been set up to match Metro's default filesystem layout.<br />
<br />
Next, we go back to the <tt>"${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"</tt> directory, and inside it, we create a <tt>.control</tt> directory. This directory and its subdirectories contain special files that Metro references to determine certain aspects of its behavior. The <tt>.control/version/stage3</tt> file is used by Metro to track the most recently-built stage3 for this particular build and subarch. Metro will automatically update this file with a new version stamp after it successfully builds a new stage3. But because Metro didn't actually ''build'' this stage3, we need to set up the <tt>.control/version/stage3</tt> file manually. This will allow Metro to find our downloaded stage3 when we set up our pentium4 build to use it as a seed. Also note that Metro will create a similar <tt>.control/version/stage1</tt> file after it successfully builds an pentium4 funtoo-current stage1.<br />
<br />
We also set up <tt>.control/strategy/build</tt> and <tt>.control/strategy/seed</tt> files with values of <tt>local</tt> and <tt>stage3</tt> respectively. These files define the building strategy Metro will use when we build pentium4 funtoo-current stages. With a build strategy of <tt>local</tt>, Metro will source its seed stage from funtoo-current pentium4, the current directory. And with a seed strategy of <tt>stage3</tt>, Metro will use a stage3 as a seed, and use this seed to build a new stage1, stage2 and stage3.<br />
<br />
== Step 2: Building the pentium4 stages ==<br />
<br />
Incidentally, if all you wanted to do at this point was to build a new pentium4 funtoo-current stage1/2/3 (plus openvz and vserver templates). You would begin the process by typing:<br />
<br />
<pre><br />
# cd /root/git/metro<br />
# scripts/ezbuild.sh funtoo-current pentium4<br />
</pre><br />
<br />
If you have a slow machine, it could take several hours to be completed because several "heavy" components like gcc or glibc have to be recompiled in each stage. Once a stage has been successfully completed, it is placed in the <tt>"${METRO_MIRROR}/funtoo-current/x32-bit/pentium4/YYYY-MM-DD"</tt> subdirectory, where <tt>YYYY-MM-DD</tt> is today's date at the time the <tt>ezbuild.sh</tt> script was started or the date you put on the ezscript.sh command line.<br />
<br />
== Step 3: The next build ==<br />
<br />
At this point, you now have a new pentium4 stage3. If you'd like, you can reconfigure Metro to use the most recently-built pentium stage3 as a seed for any pentium4 builds. To do this, simply type:<br />
<br />
<pre>(~) # echo &quot;local&quot; &gt; /home/mirror/linux/funtoo-current/x86-32bit/pentium4/.control/strategy/build</pre><br />
Now, Metro will use the most recentpentium4 stage3 as a seed. The <tt>.control/remote</tt> files you created will be ignored by Metro, since it's no longer going to perform a remote build.<br />
<br />
= Building for another binary compatible architecture (remote build) =<br />
<br />
As written above, [[Metro]] is able to perform '''remote build''' building different architecture stage3 from a binary compatible seeding stage3 (e.g. using a pentium4 stage3 to seed a <tt>Intel Core2 32bits</tt> stage3). <br />
<br />
In the Metro terminology this is called a '''remote build''' (a stage 3 of a different, but binary compatible, architecture is used as a seed). <br />
What's not compatible? You can't use a <tt>Sparc</tt> architecture to generate an <tt>x86</tt> or <tt>ARM</tt> based stage and vice-versa. If you use a 32bit stage then you don't want to seed a 64bit build from it. Be sure that you are using a stage from the same architecture that you are trying to seed. Check [http://ftp.osuosl.org/pub/funtoo/funtoo-current/ Funtoo-current FTP Mirror] for a stage that is from the same Architecture that you will be building. <br />
<br />
== Step 1: Set up Core_2 32bit repository ==<br />
<br />
In this example, we're going to use this pentium4 funtoo-current stage3 to seed a new Core_2 32bit funtoo-current build. To get that done, we need to set up the pentium4 build directory as follows:<br />
<br />
<pre><br />
(~) # cd "${METRO_MIRROR}/funtoo-current/x86-32bit"<br />
(/home/mirror/linux/funtoo-current/x86-32bit) # install -d core2_32<br />
(/home/mirror/linux/funtoo-current/x86-32bit) # cd core2_32<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # install -d .control/strategy<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;remote&quot; &gt; .control/strategy/build<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;stage3&quot; &gt; .control/strategy/seed<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # install -d .control/remote<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;funtoo-current&quot; &gt; .control/remote/build<br />
(/home/mirror/linux/funtoo-current/x86-32bit/core2_32) # echo &quot;pentium4&quot; &gt; .control/remote/subarch<br />
</pre><br />
<br />
The steps we follow are similar to those we performed for a ''local build'' to set up our pentium4 directory for local build. However, note the differences. We didn't download a stage, because we are going to use the pentium4 stage to build a new Core_2 32bit stage. We also didn't create the <tt>.control/version/stage{1,3}</tt> files because Metro will create them for us after it successfully builds a new stage1 and stage3. We are still using a <tt>stage3</tt> seed strategy, but we've set the build strategy to <tt>remote</tt>, which means that we're going to use a seed stage that's not from this particular subdirectory. Where are we going to get it from? The <tt>.control/remote</tt> directory contains this information, and lets Metro know that it should look for its seed stage3 in the <tt>"${METRO_MIRROR}/home/mirror/linux/funtoo-current/x86-32bit/pentium4"</tt> directory. Which one will it grab? You guessed it -- the most recently built ''stage3'' (since our seed strategy was set to <tt>stage3</tt>) that has the version stamp of <tt>2010-12-24</tt>, as recorded in <tt>"${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4/.control/version/stage3"</tt>. Now you can see how all those control files come together to direct Metro to do the right thing.<br />
<br />
== Step 2: Building the Core_2 32bit stages ==<br />
<br />
Now, you could start building your new Core_2 32bit stage1/2/3 (plus openvz and vserver templates) by typing the following:<br />
<br />
<pre><br />
(~) # /root/git/metro/scripts/ezbuild.sh funtoo-current core2_32<br />
</pre><br />
<br />
In that case, the produced stages are placed in the <tt>"${METRO_MIRROR}/funtoo-current/x32-bit/core2_32/YYYY-MM-DD"</tt> subdirectory.<br />
<br />
== Step 3: The Next Build ==<br />
<br />
At this point, you now have a new Core_2 32bit stage3. If you'd like, you can reconfigure Metro to use the most recently-built Core_2 32bit stage3 as a seed for any new Core_2 32bit builds. <br />
<br />
In the Metro terminology this is called a '''local build''' (a stage 3 of a a given architecture is used to seed a brand new build of the same architecture). <br />
<br />
To do this, simply type:<br />
<br />
<pre><br />
(~) # echo &quot;local&quot; &gt; /home/mirror/linux/funtoo-current/x86-32bit/core2_32/.control/strategy/build<br />
</pre><br />
<br />
Now, Metro will use the most recent Core_2 32bit stage3 as a seed. The <tt>.control/remote</tt> files you created will be ignored by Metro, since it's no longer going to perform a remote build.<br />
<br />
= Build your own tailored stage3 =<br />
<br />
Metro can be easily configured for building custom stage3 by including additional packages. Notice that including packages with heavy dependencies such as gnome, kde, xorg-server is not recommended (not tested so far). Well tested packages are <tt>app-misc/mc</tt>, <tt>app-misc/screen</tt>, <tt>sys-process/htop</tt>, <tt>sys-apps/dstat</tt>. An example for funtoo-current stage. Edit the following configuration file <tt>/root/git/metro/etc/builds/funtoo-current/build.conf</tt>:<br />
<br />
<pre><br />
[collect ../../fslayouts/funtoo/layout.conf]<br />
<br />
[section local]<br />
<br />
author: Daniel Robbins <drobbins@funtoo.org><br />
<br />
[section target]<br />
<br />
build: funtoo-current<br />
compression: xz<br />
<br />
[section portage]<br />
<br />
stable: ~<br />
MAKEOPTS: -j12<br />
FEATURES: mini-manifest<br />
SYNC: $[snapshot/source/remote]<br />
USE:<br />
profile: default/linux/$[target/arch:zap]/2008.0<br />
<br />
[section emerge]<br />
<br />
options: --jobs=4 --load-average=3 --keep-going=n<br />
packages: [<br />
dev-vcs/git <br />
net-misc/dhcpcd<br />
sys-fs/reiserfsprogs<br />
net-misc/bridge-utils<br />
sys-devel/bc<br />
sys-apps/pciutils<br />
app-portage/gentoolkit<br />
app-misc/mc<br />
app-misc/screen<br />
sys-process/htop<br />
sys-apps/dstat <br />
<br />
]<br />
<br />
[section snapshot]</pre><br />
<br />
As you can see MAKEOPTS and emerge default options are additional strings to tweak, --keep-going=n is recommended, if something breaking during the stage building process, you can quickly diagnose the problem.<br />
<br />
Distfiles location can be specified in <tt>/root/git/metro/etc/metro.conf</tt><br />
<br />
<pre><br />
# Main metro configuration file<br />
# <br />
# Path configuration:<br />
<br />
[collect ../targets/$[metro/target]/$[target:zap].spec]<br />
[collect ./builds/$[metro/build]/build.conf]<br />
[collect ../subarch/$[target/subarch:zap].spec]<br />
<br />
# General Paths<br />
<br />
[section path]<br />
tmp: /var/tmp/metro<br />
distfiles: /var/portage/distfiles<br />
work: $[path/tmp]/work/$[metro/build]/$[target/name]<br />
<br />
[section path/cache]<br />
</pre><br />
<br />
[[Category:HOWTO]]<br />
[[Category:Metro]]</div>Oleg