Gentoo Linux x86 Quick Install Guide
1.
Introduction
This guide contains all the commands you should use to complete a stage3
installation of Gentoo. You need a connection to the Internet to download the
stage3 and Portage snapshots.
Important:
New users should read the Handbook
as it gives a better overview about the installation process. The Quick Install
guide is designed for experienced users who just need a checklist to follow.
|
Timing output follows all commands that take more than a couple of seconds to
finish. Commands were timed on an AMD 2000 1.66 Ghz PC with 512 MB of RAM and
two SATA disks connected to a hardware controller.
Code Listing 1.1: Test box specs |
# grep bogo /proc/cpuinfo
bogomips : 3337.81
# hdparm -tT /dev/sda
/dev/sda:
Timing cached reads: 1100 MB in 2.00 seconds = 549.97 MB/sec
Timing buffered disk reads: 224 MB in 3.01 seconds = 74.36 MB/sec
# grep MemTotal /proc/meminfo
MemTotal: 509248 kB
|
2.
Quick Install Guide
Installation Media
Download a CD from one of our mirrors.
You can find the minimal CD ISO in releases/x86/current-iso/. The
minimal installation CD is only useful for Internet-based installations.
This guide will use the minimal CD.
Burn the CD and boot it.
Booting the CD
Press F2 at the boot screen to find out what boot options exist. You can
either start gentoo or gentoo-nofb, the latter disables the
framebuffer. If you booted the LiveCD, don't forget to add the nox option
to prevent the X graphical environment from starting. Several options allow to
enable or disable some features. If all goes well, your hardware will be
detected and all modules will be loaded. If the kernel fails to boot properly or
if your computer hangs during the boot procedure, you may have to experiment
with different configurations. The safest way is probably to use the
nodetect option and then load required modules explicitly.
Code Listing 2.1: Boot the minimal CD |
Gentoo Linux Installation LiveCD http://www.gentoo.org
Enter to Boot; F1 for kernels F2 for options.
boot: gentoo-nofb
boot: gentoo-nofb nodetect
|
Optional: loading modules
If you used the nodetect option, once booted, load the required modules.
You need to enable networking and have access to your disks. The lspci
command can help you identify your hardware.
Code Listing 2.2: Load required modules |
livecd root # lspci
livecd root # modprobe 3w-9xxx
livecd root # modprobe r8169
|
Network Configuration
If your network does not work already, you can use net-setup to
configure your network. You might need to load support for your network card
using modprobe prior to the configuration. If you have ADSL, use
pppoe-setup and pppoe-start. For PPTP support, first edit
/etc/ppp/chap-secrets and /etc/ppp/options.pptp and
then use pptp <server ip>.
For wireless access, use iwconfig to set the wireless parameters and then
use either net-setup again or run ifconfig, dhcpcd and/or
route manually.
If you are behind a proxy, do not forget to initialize your system using
export http_proxy, ftp_proxy and RSYNC_PROXY.
Code Listing 2.3: Configure networking the guided way |
livecd root # net-setup eth0
|
Alternatively, you can start networking manually. The following example assigns
the IP address 192.168.1.10 to your PC and defines 192.168.1.1 as your router
and name server.
Code Listing 2.4: Configure networking the manual way |
livecd root # ifconfig eth0 192.168.1.10/24
livecd root # route add default gw 192.168.1.1
livecd root # echo nameserver 192.168.1.1 > /etc/resolv.conf
|
The installation CD allows you to start an sshd server, add additional
users, run irssi (a command-line chat client) and surf the web using
links.
Optional: connect to your new box over ssh
The most interesting feature is of course sshd. You can start it and
then connect from another machine and cut and paste commands from this guide.
Code Listing 2.5: Start sshd |
livecd root # time /etc/init.d/sshd start
* Generating hostkey ...
* starting sshd ... [ok]
real 0m13.688s
user 0m9.420s
sys 0m0.090s
|
Now, set the root password on the liveCD so that you can connect to it from
another PC. Please note that allowing root to connect over ssh is not
recommended under normal circumstances. If you can't trust your local network,
use a long and complex password, you should use it only once as it will
disappear after your first reboot.
Code Listing 2.6: Set the root password |
livecd root # passwd
New UNIX password:
Retype new UNIX password:
passwd: password updated successfully
|
Now, you can start a terminal on another PC and connect to your new box, follow
the rest of this guide in another window, and cut and paste commands.
Code Listing 2.7: Connect to your new box from another PC |
$ ssh root@192.168.1.10
The authenticity of host '192.168.1.10 (192.168.1.10)' can't be established.
RSA key fingerprint is 96:e7:2d:12:ac:9c:b0:94:90:9f:40:89:b0:45:26:8f.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.1.10' (RSA) to the list of known hosts.
Password:
|
Preparing the Disks
Use fdisk or cfdisk to create your partition layout. You need at
least a swap partition (type 82) and one Linux partition (type 83). The
following scenario creates a /boot, a swap and a main partition as
used in our handbook. Replace sda with your disk. Most systems
ignore the bootable flag, but a few need it. Set this flag on your boot
partition with fdisk's a command.
Code Listing 2.8: Create the partitions |
livecd ~ # fdisk /dev/sda
livecd ~ # fdisk -l /dev/sda
Disk /dev/sda: 599.9 GB, 599978409984 bytes
255 heads, 63 sectors/track, 72943 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 12 96358+ 83 Linux
/dev/sda2 13 110 787185 82 Linux swap / Solaris
/dev/sda3 111 72943 585031072+ 83 Linux
|
Use mkfs.ext2, mkfs.ext3, mkfs.ext4, mkreiserfs,
mkfs.xfs and mkfs.jfs to create file systems on your Linux
partitions. Initialize your swap partition using mkswap and swapon.
Code Listing 2.9: Create the file systems and activate swap |
livecd ~ # mkfs.ext2 /dev/sda1
livecd ~ # mkfs.ext3 /dev/sda3
livecd ~ # mkswap /dev/sda2 && swapon /dev/sda2
|
Mount the freshly created file systems on /mnt/gentoo. Create
directories for the other mount points (like /mnt/gentoo/boot) if
you need them and mount them too.
Code Listing 2.10: Mount the file systems |
livecd ~ # mount /dev/sda3 /mnt/gentoo
livecd ~ # mkdir /mnt/gentoo/boot
livecd ~ # mount /dev/sda1 /mnt/gentoo/boot
livecd ~ # cd /mnt/gentoo
|
Setting Up The Stage
First make sure your date and time is set correctly using date
MMDDhhmmYYYY. Use UTC time.
Code Listing 2.11: Set the date and UTC time |
livecd gentoo # date
Mon Mar 6 00:14:13 UTC 2006
livecd gentoo # date 030600162006
Mon Mar 6 00:16:00 UTC 2006
|
Next, download a stage from one of our mirrors:
Code Listing 2.12: Download a stage3 archive |
livecd gentoo # links http://www.gentoo.org/main/en/mirrors.xml
livecd gentoo # wget ftp://distfiles.gentoo.org/pub/gentoo/releases/x86/current-stage3/stage3-i686-*.tar.bz2
|
Go to /mnt/gentoo and unpack the stage using tar xjpf <stage3
tarball>.
Code Listing 2.13: Unpack the stage3 archive |
livecd gentoo # time tar xjpf stage3*
real 1m14.157s
user 1m2.920s
sys 0m7.530s
|
Chrooting
Mount the /proc, /dev, and /sys file
systems, copy over the /etc/resolv.conf file, then chroot into
your Gentoo environment.
Code Listing 2.14: Chroot |
livecd usr # cd /
livecd / # mount -t proc proc /mnt/gentoo/proc
livecd / # mount --rbind /dev /mnt/gentoo/dev
livecd / # mount --rbind /sys /mnt/gentoo/sys
livecd / # cp -L /etc/resolv.conf /mnt/gentoo/etc/
livecd / # chroot /mnt/gentoo /bin/bash
livecd / # source /etc/profile
|
Fetch the latest portage snapshot from the mirrors using emerge-webrsync.
Code Listing 2.15: Running emerge-webrsync to install a Portage snapshot |
livecd / # mkdir /usr/portage
livecd / # emerge-webrsync
|
Set your time zone
Set your time zone information by using the correct listing in
/usr/share/zoneinfo.
Code Listing 2.16: Setting your timezone |
livecd / # ls /usr/share/zoneinfo
livecd / # cp /usr/share/zoneinfo/Europe/Brussels /etc/localtime
livecd / # echo "Europe/Brussels" > /etc/timezone
livecd / # date
Wed Mar 8 00:46:05 CET 2006
|
Select your profile
Choose your profile using eselect. This is an example of the output you might
see.
Code Listing 2.17: Verifying System Profile |
livecd / # eselect profile list
Available profile symlink targets:
[1] default/linux/x86/13.0 *
[2] default/linux/x86/13.0/desktop
[3] default/linux/x86/13.0/desktop/gnome
[4] default/linux/x86/13.0/desktop/kde
[5] default/linux/x86/13.0/server
|
Choose the appropriate profile. Keep in mind that default USE flags are
determined based on the profile you pick.
Code Listing 2.18: Changing Profile |
livecd / # eselect profile set 2
|
Set your host name and domain name
Set your host name in /etc/conf.d/hostname and
/etc/hosts. In the following example, we use
mybox as host name and at.myplace as domain name. You can either
edit the config files with nano or use the following commands:
Code Listing 2.19: Set host and domain name |
livecd / # cd /etc
livecd etc # echo "127.0.0.1 mybox.at.myplace mybox localhost" > hosts
livecd etc # sed -i -e 's/hostname.*/hostname="mybox"/' conf.d/hostname
livecd etc # hostname mybox
livecd etc # hostname -f
mybox.at.myplace
|
Kernel Configuration
Install a kernel source (usually gentoo-sources), configure it, compile
it and copy the arch/i386/boot/bzImage file to /boot.
Code Listing 2.20: Install a kernel source, compile it and install the kernel |
livecd etc # time emerge gentoo-sources
real 2m51.435s
user 0m58.220s
sys 0m29.890s
livecd etc # cd /usr/src/linux
livecd linux # make menuconfig
livecd linux # time make -j2
real 3m51.962s
user 3m27.060s
sys 0m24.310s
livecd linux # make modules_install
livecd linux # cp arch/i386/boot/bzImage /boot/kernel
|
Optionally build an initramfs to boot from:
Code Listing 2.21: Building an initramfs |
# emerge genkernel
# genkernel --install --no-ramdisk-modules initramfs
|
Configure the system
Edit your /etc/fstab and replace BOOT, ROOT and
SWAP with the actual partition names. Don't forget to check that the
file systems match your installation.
Code Listing 2.22: Example fstab |
livecd linux # cd /etc
livecd etc # nano -w fstab
/dev/sda1 /boot ext2 noauto,noatime 1 2
/dev/sda3 / ext3 noatime 0 1
/dev/sda2 none swap sw 0 0
|
Configure your network in /etc/conf.d/net. Add the net.eth0
init script to the default run level. If you have multiple NICs, symlink them
to the net.lo init script and add them to the default run level as
well. Don't forget to set your hostname too. Either edit
/etc/conf.d/net and /etc/conf.d/hostname with
nano or use the following commands:
Code Listing 2.23: Configure networking |
livecd etc # cd init.d
livecd init.d # ln -s net.lo net.eth0
livecd init.d # cd ../conf.d
livecd conf.d # echo 'config_eth0="192.168.1.10 netmask 255.255.255.0 brd 192.168.1.255"' >> net
livecd conf.d # echo 'routes_eth0="default via 192.168.1.1"' >> net
livecd conf.d # echo 'hostname="myhostname"' > hostname
livecd conf.d # rc-update add net.eth0 default
livecd conf.d # echo 'modules="r8169"' >> /etc/conf.d/modules
livecd conf.d # rc-update add sshd default
|
Note:
Emerge pcmciautils if you need support for PCMCIA cards.
|
Set the root password using passwd.
Code Listing 2.24: Set the root password |
livecd conf.d # passwd
New UNIX password:
Retype new UNIX password:
passwd: password updated successfully
|
Edit /etc/conf.d/hwclock to set clock options.
Code Listing 2.25: Edit /etc/conf.d/hwclock |
livecd # nano -w /etc/conf.d/hwclock
|
Check the system configuration in /etc/rc.conf and
/etc/conf.d/keymaps and edit any of those files if required.
Code Listing 2.26: Optional: edit some config files |
livecd conf.d # nano -w /etc/rc.conf
livecd conf.d # nano -w /etc/conf.d/keymaps
|
Installing System Tools
Install a system logger like syslog-ng and a cron daemon like
vixie-cron, and add them to the default run level.
Note:
Cron daemons depend on an MTA. mail-mta/ssmtp will be pulled in as a
dependency. If you want to use a more advanced MTA, you might want to install
it now. If you are in a hurry, let ssmtp be installed and remove it later when
you install the MTA of your choice.
|
Code Listing 2.27: Install a syslogger and a cron daemon |
livecd conf.d # time emerge syslog-ng vixie-cron
real 1m54.099s
user 1m2.630s
sys 0m34.620s
livecd conf.d # rc-update add syslog-ng default
livecd conf.d # rc-update add vixie-cron default
|
Install the necessary file system tools (xfsprogs, reiserfsprogs
or jfsutils) and networking tools (dhcpcd or ppp) if you
need any.
Code Listing 2.28: Install extra tools if required |
livecd conf.d # emerge xfsprogs
livecd conf.d # emerge jfsutils
livecd conf.d # emerge reiserfsprogs
livecd conf.d # emerge dhcpcd
livecd conf.d # emerge ppp
|
Configuring the Bootloader
Emerge grub and configure it. Do not forget to update the necessary boot
parameters if you are using an initramfs.
Code Listing 2.29: Emerge grub and edit its configuration file |
livecd conf.d # time emerge grub
real 1m4.634s
user 0m39.460s
sys 0m15.280s
livecd conf.d # nano -w /boot/grub/grub.conf
|
Code Listing 2.30: Example grub.conf |
default 0
timeout 10
title Gentoo
root (hd0,0)
kernel /boot/kernel root=/dev/sda3
initrd /boot/initramfs
|
Code Listing 2.31: Install grub |
livecd conf.d # grub
Probing devices to guess BIOS drives. This may take a long time.
grub> root (hd0,0)
Filesystem type is ext2fs, partition type 0xfd
grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,0)/boot/grub/stage2 /boot/
grub/menu.lst"... succeeded
Done.
grub> quit
|
Reboot
Exit the chrooted environment, unmount all file systems and reboot:
Code Listing 2.32: Reboot |
livecd conf.d # exit
livecd / # umount -l /mnt/gentoo/dev{/shm,/pts,}
livecd / # umount -l /mnt/gentoo{/proc,/boot,/sys,}
livecd / # reboot
|
Finalizing the Installation
Note:
The total elapsed time between the display of the boot prompt on the
minimal CD and the display of the login prompt after the reboot was
00:42:31 on our test box. Yes, less than one hour! Note that this time
also includes the stage3, Portage snapshot and several packages download time
and the time spent configuring the kernel.
|
Log in as root, then add one or more users for daily use with
useradd.
Code Listing 2.33: Connect to your new box from another PC |
$ nano -w ~/.ssh/known_hosts
$ ssh root@192.168.1.10
The authenticity of host '192.168.1.10 (192.168.1.10)' can't be established.
RSA key fingerprint is 96:e7:2d:12:ac:9c:b0:94:90:9f:40:89:b0:45:26:8f.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.1.10' (RSA) to the list of known hosts.
Password:
|
Code Listing 2.34: Add a new user |
mybox ~ # useradd -g users -G lp,wheel,audio,cdrom,portage,cron -m john
mybox ~ # passwd john
New UNIX password:
Retype new UNIX password:
passwd: password updated successfully
|
Last configuration touches
Start by selecting nearby mirrors either by defining the SYNC and
GENTOO_MIRRORS variables in /etc/portage/make.conf or by using
mirrorselect. You can also define the number of concurrent compilation
processes at this point.
Code Listing 2.35: Use mirrorselect and set MAKEOPTS |
mybox ~ # emerge mirrorselect
mybox ~ # mirrorselect -i -o >> /etc/portage/make.conf
mybox ~ # mirrorselect -i -r -o >> /etc/portage/make.conf
mybox ~ # echo 'MAKEOPTS="-j2"' >> /etc/portage/make.conf
|
Now is a good time to enable or disable some USE flags. Run emerge -vpe
world to list all currently installed packages and their enabled and
disabled USE flags. Either edit /etc/portage/make.conf or use the
following command to define the USE variable:
Code Listing 2.36: View USE flags in use and enable or disable some |
mybox ~ # emerge -vpe world
mybox ~ # echo 'USE="nptl nptlonly ipv6 -fortran unicode"' >> /etc/portage/make.conf
|
Recent versions of glibc use /etc/locale.gen to define locale
settings.
Code Listing 2.37: Define locales |
mybox ~ # cd /etc
mybox etc # nano -w locale.gen
mybox etc # locale-gen
|
Last but not least, you may want to alter the CFLAGS variable in your
/etc/portage/make.conf to optimise the code to your specific needs. Please
note that using a long list of flags is rarely needed and can even lead to a
broken system. It is recommended to specify the processor type in the
march option and stick to -O2 -pipe.
You may also want to switch to ~x86. You should only do this if you can
deal with the odd broken ebuild or package. If you'd rather keep your system
stable, don't add the ACCEPT_KEYWORDS variable.
Code Listing 2.38: Last edit of make.conf |
mybox etc # cd portage
mybox portage # nano -w make.conf
CFLAGS="-O2 -march=athlon-xp -pipe"
ACCEPT_KEYWORDS="~x86"
|
You might want to recompile your whole system twice to make full use of your
latest configuration changes. It would take quite a long time to complete and
yield minimal speed benefits. You can let your system optimise itself gradually
over time when new versions of packages are released. However, recompiling is
a still good idea from the standpoint of maintaining system consistency. Please
see the Gentoo GCC Upgrading Guide
for a discussion on the benefits of ensuring a consistently built system and
world.
Recompiling only the packages that have already been updated since the release
or that are affected by your new USE flags will take enough time. You might
also have to remove packages that block your upgrade. Look for "[blocks
B ]" in the output of emerge -vpuD --newuse world and
use emerge -C to remove them.
Code Listing 2.39: Update your packages |
mybox etc # emerge -vpuD --newuse world
mybox etc # time emerge -vuD --newuse world
real 180m13.276s
user 121m22.905s
sys 36m31.472s
mybox etc # emerge --oneshot libtool
mybox etc # dispatch-conf
mybox etc # time perl-cleaner all
real 1m6.495s
user 0m42.699s
sys 0m10.641s
mybox etc # python-updater
|
What to do next
Depending on what your new Gentoo machine is supposed to do, you will probably
want to install server applications or a desktop system. Just as an example,
emerge gnome and emerge kde have been timed on the ~x86 system
installed as describe above. Both have been installed from the same starting
point.
You should check our documentation index to find out
how to install and configure the applications of your choice.
Important:
The following is only an example. It is in no way meant as a recommended setup.
|
Code Listing 2.40: Emerge GNOME |
mybox etc # emerge -vp gnome
mybox etc # nano -w /etc/portage/make.conf
USE="-fortran dbus -kde -qt4 -eds "
mybox etc # time emerge gnome
real 520m44.532s
user 339m21.144s
sys 146m22.337s
|
Code Listing 2.41: Emerge KDE |
mybox etc # emerge -vp kde-meta
mybox etc # nano -w /etc/portage/make.conf
USE="-fortran -eds -gnome -gstreamer -gtk -firefox"
mybox etc # time emerge kde-meta
real 1171m25.318s
user 851m26.393s
sys 281m45.629s
|
The contents of this document, unless otherwise expressly stated, are licensed under the CC-BY-SA-2.5 license. The Gentoo Name and Logo Usage Guidelines apply.
|