Installation alternatives/en

This guide is meant to be a repository of alternative Gentoo installation methods, for those with special installation needs such as lack of a CD-ROM or a computer that cannot boot CDs.

About this guide
If the standard boot-from-CD install method doesn't work (or just impossible to use, or is just disliked), some help can be found here. This guide serves to provide a repository of alternative Gentoo Linux installation techniques to those who need them. Or, if preferred, it serves as a place to put wacky installation methods. If there is an installation method that has been found useful, or the reader has devised an amusing way of installing Gentoo, please don't hesitate to write something up here, in this article.

Booting the Install CD with Smart BootManager
Download Smart BootManager available from http://btmgr.sourceforge.net/download.html. Linux source or binary format and windows versions are available as well as many language packs. However, at this time, the preferred method would be to use the binary format, as the source will not compile with newer versions of NASM.

Either compile the package from source or just grab the binary. There are several options that can be utilized while creating a boot floppy, as seen below.

Use to build the boot floppy:

Now simply place the floppy in the floppy drive of the computer, as well as placing the Install CD in the CD-ROM and boot the computer.

The Smart BootManager dialog will appear. Select the CD-ROM and press the (Return) key to boot the Install CD. Once booted proceed with the standard installation instructions.

Further information on Smart BootManager may be found at http://btmgr.sourceforge.net/.

Introduction
Users can boot other LiveCDs besides the Gentoo-provided CDs. Regardless, these LiveCDs provide a functional environment to use while compiling and installing Gentoo. The instructions provided here should work in principle with just about any other LiveCD.

There are too many LiveCDs out there to list, but an option might be to try out Knoppix. It provides a full graphical desktop, with office applications, web browsers, and games to keep busy. Knoppix is only available for users, so depending on the user's requirements another LiveCD or method may need to be used.

Installation instructions
Boot from the LiveCD. Open a terminal and run so the password can be changed. This allows to set the root password for the CD. The sshd daemon can now be configured for remote login if required. Next, creating the mount point is necessary.

At this point, the standard install documentation can be picked up at Preparing the Disks. However, when asked to mount the proc system, issue the following command instead:

When unpacking the stage tarball in Unpacking the stage tarball, be sure to use the following command options to ensure that proper group IDs are enforced on the unpacked stage:

If Ubuntu is being used, note that is a symbolic link to. It must be bind-mounted or a tmpfs mount has to be set at this location (within the chroot path). To bind-mount the location, run the following command (before chrooting):

This is to avoid where Python sees   as broken (due to lack of ) and Portage seeing that as an error (technically Python configuration would continue and build assuming the POSIX_SEMAPHORES_NOT_ENABLED variable has been enabled but this would lead to a very undesired Python build).

Once ready to chroot into the unpacked stage in Installing Base System, a different chroot command sequence will need to be used. This ensures that the environment variables are properly setup.

Finally, know that some Portage FEATURES may not work in the LiveCD. Especially watch out for  and   values. If there are errors, try disabling some or all of the optional FEATURES.

Diskless install using PXE and kernel/initrd/squashfs from the LiveCD
This method is easier to configure than PXE boot based on iSCSI or NFS. Multiple machines can boot from the same set of images distributed via TFTP and can be easily extended to also work over HTTP or other protocol.

Having a nice router or one capable of running open source firmware such as LEDE, the successor to OpenWRT, is one way to centralize TFTP and DHCP. Getting the firmware online could be an uphill battle, depending on your experience.

Some other distributions including Fedora already distribute images needed to bootstrap a live or installation CD. With Gentoo, this is not the case. Instead, users need to


 * 1) Extract kernel, initrd and squashfs from the live CD.
 * 2) Patch initrd contents.
 * 3) Merge squashfs into initrd.

Only then can a PXE based boot loader be configured that will load the images and boot into a live system.

There are different flavors of PXE, but all of them are going to need the kernel and initrd file, so let's create those files now. Download the minimal installation CD. Then, execute the following script as root. The new files initrd and kernel will be created in your specified output directory.

If you know what you're doing, you can be on your way! Enjoy Gentoo on PXE. Otherwise, see below for more directions depending on the PXE flavor you're using.

TFTP
This will be needed in tandem with a DHCP server for most PCs equipped with PXE boot. However, realize that you could use iPXE to boot without a TFTP or DHCP server! See ipxe.org for info on embedding scripts, chainloading, and manual booting. There are still merits to TFTP booting such as wide-range device support, so let's get to serving TFTP!

Install, make sure it serves and start it.

Now the TFTP boot service is ready, so the next step is to configure a DHCP service.

DHCP
Setting up a DHCP server on the same machine is possible - just make sure that the booted machines are connected to it. Or just tweak the configuration of an existing router.

Example configuration for OpenWRT DHCP service follows:

From here, directions will change depending on what flavor your PXE is (i.e. GRUB, iPXE).

GRUB
After executing the pxe-craft-initrd-kernel script, run the following pxe-install-grub to output proper files into your tftp root directory.

iPXE
Here are relevant stanzas for iPXE.

Requirements
PXE (Preboot eXecution Environment) is a method for booting computers over a PXE-capable network interface (and using a PXE-supporting BIOS). In case the system does not support PXE boot from the network interface or BIOS, PXE can also be used as a boot method from block devices (like CDs or USBs). In such cases, a minimal boot environment mimics the PXE supporting network card (see also Etherboot/gPXE).

Server base setup
Create directories: The first thing to do is to create the directories where the diskless system will be stored. Create a directory called which houses a directory for each diskless client. For the remainder of this howto, the client that is being worked on will be called 'eta'.

DHCP and TFTP setup: The client will get boot information using DHCP and download all the required files using TFTP.

For dhcpd, just run (or any other DHCP server of choice). Make sure that the correct interface is selected in, and configure it accordingly. Then, add the following on.

Next configure the interface in so that it doesn't get cleared at bootup. See for more information.

For TFTP, emerge. In, put the following:

Emerge GRUB:

Once GRUB is compiled, create the diskless client's boot directory:

Original way was to copy the PXE image to the diskless client but the path does not seem to exit anymore.

Then edit its config file.

NFS is quite easy to configure. The only thing that has to be done is to add a line on the config file:

One important thing to do now is to modify the file to fit requirements.

Creating the system on the server
A next step is to reboot the server with a Gentoo installation CD (although experienced administrators can continue without if they are sufficiently versed in Gentoo installations). Follow the standard install procedure as explained in the Gentoo Handbook BUT with the following differences: when mounting the file system, execute the next step (where is the partition where the  directory was created).

Mounting any other partition is not needed as all of the files will reside in the directory.

This example uses a stage3 tarball. Mount to the diskless directory and chroot into it to continue with the install. Then follow the installation manual until kernel configuration.

When doing the of the kernel configuration, don't forget to enable the following options with the others recommended into the install guide.

Save the kernel in the chrooted (not in ) according to the pxegrub setting defined earlier. Next configure the diskless client's.

Now to prevent the client from running a filesystem check:

Install since the client will heavily depend on it:

Do not install another bootloader because there is already one - pxegrub. Simply finish the install and restart the server. Start the services that are needed to boot the new client: DHCP, TFTPD, and NFS.

Booting the new client
For the new client to boot properly, the BIOS and the network card need to be configured to use PXE as the first boot method - before CD-ROM or floppy. For help with this consult the hardware manuals or manufacturers website. The network card should get an IP address using DHCP and download the GRUB PXE image using TFTP. Then, a nice black and white GRUB bootmenu should be displayed from where users can select the kernel to boot and press the (Return) key. If everything is okay the kernel should boot, mount the root filesystem using NFS and provide a login prompt. Enjoy.

Requirements
In order to install Gentoo from an existing Linux distribution it needs to have the chroot command installed, and have a copy of the Gentoo installation or ISO that's desired to install. A network connection is highly recommended as otherwise the installation can only work with the files available in the installation media. By the way, a tarball is just a file ending in or. Let's get started!

Overview
First allocate a partition to Gentoo by resizing an existing Linux partition, mount the partition, untar the tarball to the partition that is mounted, chroot inside the pseudo-system and start building. Once the bootstrap process is done, do some final configuration on the system so as to make sure it boots, then reboot and use Gentoo.

How to make space for Gentoo?
The root partition is the filesystem mounted under. The first example shows the output of on a system. The second example uses (disk free) to see how much space there is left and how it will be resized. Note that resizing the root partition is not mandatory! Anything else supported by the resizer can be resized, but let's talk about that later.

As can be seen, the partition mounted as named  has 2.4 GB free. In this case, it was decided to be resized as to leave 400 MB of free space, therefore allocating 2 GB for Gentoo. Not bad, it could have quite some stuff installed. However, 1 GB is deemed enough for most users. So now partition this thing!

Building parted to resize partition
is extremely useful for resizing partitions. It is included on the minimal installation CD.

Look up on that page the type of file system to resize and see if can do it. If not: tough luck, some partitions might need to be destroyed to make space for Gentoo, and reinstall back. Go ahead by downloading the software and install it. In the next step, a problem arises. The Linux root partition needs to be resized, therefore a floppy disk with a minimal Linux system must be booted and to use a previously-compiled parted copied to a diskette in order to resize. If the partition can be unmounted while still running in Linux then the following steps are not needed. Just compile parted and run it on a chosen unmounted partition to resize. Here's how it was done on this system.

Get the mininux boot/root disk (a 2.4-powered mini Linux distribution on a floppy - free of charge) from http://mininux.free.fr/uk/, create a floppy as suggested in the Documentation that accompanies the software package and insert a new floppy in the drive for the next step.

Proceed with the build of parted. Download and untar the utility, and into the corresponding directory. Now run the following set of commands to build the utility and copy it to the floppy disk.

Time to reboot and resize the partition. Do this only after taking a quick look at the parted documentation on the GNU website. The resize should take under 30 minutes for the largest hard-drives, be patient. Reboot the system with the mininux boot disk (just pop it inside), and once logged in, switch the disk in the drive with the utility disk that was created above and type to have parted under. Run parted to be able to resize the partition. Once this lengthy process is done, continue with installing Gentoo. Reboot back into the old Linux system for now. The drive to operate on is the drive containing the partition that is going to be resized. For example, if the partition to be resized is, the drive is.

Once the resize has finished, boot back into the old Linux as described. Then go to The Gentoo Handbook: Preparing the Disks and follow the instructions. When chrooting, use the following command to flush the environment:

Enjoy!