Disclaimer :
This handbook has been replaced by a newer version and is not maintained anymore.
|
[ << ]
[ < ]
[ Home ]
[ > ]
[ >> ]
8. Configuring your System
Content:
8.a. Filesystem Information
What is fstab?
Under Linux, all partitions used by the system must be listed in
/etc/fstab. This file contains the mountpoints of those partitions
(where they are seen in the file system structure), how they should be mounted
and with what special options (automatically or not, whether users can mount
them or not, etc.)
Creating /etc/fstab
/etc/fstab uses a special syntax. Every line consists of six
fields, separated by whitespace (space(s), tabs or a mixture). Each field has
its own meaning:
-
The first field shows the partition described (the path to the device
file)
-
The second field shows the mountpoint at which the partition should be
mounted
-
The third field shows the filesystem used by the partition
-
The fourth field shows the mountoptions used by mount when it
wants to mount the partition. As every filesystem has its own mountoptions,
you are encouraged to read the mount man page (man mount) for a full
listing. Multiple mountoptions are comma-separated.
-
The fifth field is used by dump to determine if the partition needs to
be dumped or not. You can generally leave this as 0 (zero).
-
The sixth field is used by fsck to determine the order in which
filesystems should be checked if the system wasn't shut down properly.
The root filesystem should have 1 while the rest should have 2
(or 0 if a filesystem check isn't necessary).
The default /etc/fstab file provided by Gentoo is not a valid
fstab file, so start nano (or your favorite editor) to create your
/etc/fstab:
Code Listing 1.1: Opening /etc/fstab |
# nano -w /etc/fstab
|
Let us take a look at how we write down the options for the /boot
partition. If your architecture doesn't require a seperate /boot
partition (such as Apple PowerPC machines) or you have elected not to create
one, don't include a boot line in your fstab. The Apple Bootstrap partition
is not a /boot partition.
In our default x86 partitioning example /boot is the
/dev/hda1 partition, with ext2 as filesystem.
It needs to be checked during boot, so we would write down:
Code Listing 1.2: An example /boot line for /etc/fstab |
/dev/hda1 /boot ext2 defaults 1 2
|
Some users don't want their /boot partition to be mounted
automatically to improve their system's security. Those people should
substitute defaults with noauto. This does mean that you need to
manually mount this partition every time you want to use it.
Now, to improve performance, most users would want to add the noatime
option as mountoption, which results in a faster system since access times
aren't registered (you don't need those generally anyway):
Code Listing 1.3: An improved /boot line for /etc/fstab |
/dev/hda1 /boot ext2 defaults,noatime 1 2
|
If we continue with this, we would end up with the following three lines (for
/boot, / and the swap partition):
Code Listing 1.4: Three /etc/fstab lines |
/dev/hda1 /boot ext2 defaults,noatime 1 2
/dev/hda2 none swap sw 0 0
/dev/hda3 / ext3 noatime 0 1
|
To finish up, you should add a rule for /proc, tmpfs
(required) and for your CD-ROM drive (and of course, if you have other
partitions or drives, for those too):
Code Listing 1.5: A full /etc/fstab example |
/dev/hda1 /boot ext2 defaults,noatime 1 2
/dev/hda2 none swap sw 0 0
/dev/hda3 / ext3 noatime 0 1
proc /proc proc defaults 0 0
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,user 0 0
|
auto makes mount guess for the filesystem (recommended for
removable media as they can be created with one of many filesystems) and
user makes it possible for non-root users to mount the CD.
Now use the above example to create your /etc/fstab. If you are a
SPARC-user, you should add the following line to your
/etc/fstab
too:
Code Listing 1.6: Adding openprom filesystem to /etc/fstab |
openprom /proc/openprom openpromfs defaults 0 0
|
Double-check your /etc/fstab, save and quit to continue.
8.b. Networking Information
Hostname, Domainname etc.
One of the choices the user has to make is name his/her PC. This seems to be
quite easy, but lots of users are having difficulties finding the
appropriate name for their Linux-pc. To speed things up, know that any name you
choose can be changed afterwards. For all we care, you can just call your system
tux and domain homenetwork.
We use these values in the next examples. First we set the hostname:
Code Listing 2.1: Setting the hostname |
# nano -w /etc/conf.d/hostname
HOSTNAME="tux"
|
Second, if you need a domainname, set it in /etc/conf.d/net.
You only need a domain if your ISP or network administrator says so, or if you
have a DNS server but not a DHCP server. You don't need to worry about DNS or
domainnames if your networking is setup for DHCP.
Code Listing 2.2: Setting the domainname |
# nano -w /etc/conf.d/net
dns_domain_lo="homenetwork"
|
If you have a NIS domain (if you don't know what that is, then you don't have
one), you need to define that one too:
Code Listing 2.3: Setting the NIS domainname |
# nano -w /etc/conf.d/net
nis_domain_lo="my-nisdomain"
|
Note:
For more information on configuring DNS and NIS, please read the examples
provided in /etc/conf.d/net.example. Also, you may want to emerge
resolvconf-gentoo to help manage your DNS/NIS setup.
|
Configuring your Network
Before you get that "Hey, we've had that already"-feeling, you should remember
that the networking you set up in the beginning of the Gentoo installation was
just for the installation. Right now you are going to configure networking for
your Gentoo system permanently.
Note:
More detailed information about networking, including advanced topics like
bonding, bridging, 802.1Q VLANs or wireless networking is covered in the Gentoo Network Configuration section.
|
All networking information is gathered in /etc/conf.d/net. It uses
a straightforward yet not intuitive syntax if you don't know how to set up
networking manually. But don't fear, we'll explain everything. A fully
commented example that covers many different configurations is available in
/etc/conf.d/net.example.
DHCP is used by default and does not require any further configuration.
If you need to configure your network connection either because you need
specific DHCP options or because you do not use DHCP at all, open
/etc/conf.d/net with your favorite editor (nano is used in
this example):
Code Listing 2.4: Opening /etc/conf.d/net for editing |
# nano -w /etc/conf.d/net
|
You will see the following file:
Code Listing 2.5: Default /etc/conf.d/net |
# This blank configuration will automatically use DHCP for any net.*
# scripts in /etc/init.d. To create a more complete configuration,
# please review /etc/conf.d/net.example and save your configuration
# in /etc/conf.d/net (this file :]!).
|
To enter your own IP address, netmask and gateway, you need
to set both config_eth0 and routes_eth0:
Code Listing 2.6: Manually setting IP information for eth0 |
config_eth0=( "192.168.0.2 netmask 255.255.255.0 brd 192.168.0.255" )
routes_eth0=( "default gw 192.168.0.1" )
|
To use DHCP and add specific DHCP options, define config_eth0 and
dhcp_eth0:
Code Listing 2.7: Automatically obtaining an IP address for eth0 |
config_eth0=( "dhcp" )
dhcp_eth0="nodns nontp nonis"
|
Please read /etc/conf.d/net.example for a list of all available
options.
If you have several network interfaces repeat the above steps for
config_eth1, config_eth2, etc.
Now save the configuration and exit to continue.
Automatically Start Networking at Boot
To have your network interfaces activated at boot, you need to add them to the
default runlevel. If you have PCMCIA interfaces you should skip this action as
the PCMCIA interfaces are started by the PCMCIA init script.
Code Listing 2.8: Adding net.eth0 to the default runlevel |
# rc-update add net.eth0 default
|
If you have several network interfaces, you need to create the appropriate
net.eth1, net.eth2 etc. initscripts for those. You can
use ln to do this:
Code Listing 2.9: Creating extra initscripts |
# cd /etc/init.d
# ln -s net.lo net.eth1
# rc-update add net.eth1 default
|
Writing Down Network Information
You now need to inform Linux about your network. This is defined in
/etc/hosts and helps in resolving hostnames to IP addresses for
hosts that aren't resolved by your nameserver. You need to define your system.
You may also want to define other systems on your network if you don't want to
set up your own internal DNS system.
Code Listing 2.10: Opening /etc/hosts |
# nano -w /etc/hosts
|
Code Listing 2.11: Filling in the networking information |
127.0.0.1 tux.homenetwork tux localhost
192.168.0.5 jenny.homenetwork jenny
192.168.0.6 benny.homenetwork benny
|
Save and exit the editor to continue.
If you don't have PCMCIA, you can now continue with System Information. PCMCIA-users should read the
following topic on PCMCIA.
Optional: Get PCMCIA Working
Note:
pcmcia-cs is only available for x86, amd64 and ppc platforms.
|
PCMCIA-users should first install the pcmcia-cs package. This also
includes users who will be working with a 2.6 kernel (even though they won't be
using the PCMCIA drivers from this package). The USE="-X" is necessary
to avoid installing xorg-x11 at this moment:
Code Listing 2.12: Installing pcmcia-cs |
# USE="-X" emerge pcmcia-cs
|
When pcmcia-cs is installed, add pcmcia to the default
runlevel:
Code Listing 2.13: Adding pcmcia to the default runlevel |
# rc-update add pcmcia default
|
8.c. System Information
Root Password
First we set the root password by typing:
Code Listing 3.1: Setting the root password |
# passwd
|
If you want root to be able to log on through the serial console, add
tts/0 to /etc/securetty:
Code Listing 3.2: Adding tts/0 to /etc/securetty |
# echo "tts/0" >> /etc/securetty
|
System Information
Gentoo uses /etc/rc.conf for general, system-wide configuration.
Open up /etc/rc.conf and enjoy all the comments in that file :)
Code Listing 3.3: Opening /etc/rc.conf |
# nano -w /etc/rc.conf
|
When you're finished configuring /etc/rc.conf, save and exit.
As you can see, this file is well commented to help you set up the necessary
configuration variables. You can configure your system to use unicode and
define your default editor and your display manager (like gdm or kdm).
Gentoo uses /etc/conf.d/keymaps to handle keyboard configuration.
Edit it to configure your keyboard.
Code Listing 3.4: Opening /etc/conf.d/keymaps |
# nano -w /etc/conf.d/keymaps
|
Take special care with the KEYMAP variable. If you select the wrong
KEYMAP, you will get weird results when typing on your keyboard.
Note:
Users of SPARC systems and SPARC clones should choose old-style,
sparc-specific keymaps if they have 2.4 kernel. But if you go for 2.6 kernel
(which is default), you should rather choose pc-style i386 keymaps (like "us").
PPC uses x86 keymaps on most systems. Users who want to be able to use
ADB keymaps on boot have to enable ADB keycode sendings in their kernel and
have to set a mac/ppc keymap in /etc/conf.d/keymaps.
|
When you're finished configuring /etc/conf.d/keymaps, save and
exit.
Gentoo uses /etc/conf.d/clock to set clock options. Edit it
according to your needs.
Code Listing 3.5: Opening /etc/conf.d/clock |
# nano -w /etc/conf.d/clock
|
If your hardware clock is not using UTC, you need to add CLOCK="local" to
the file. Otherwise you will notice some clock skew.
When you're finished configuring /etc/conf.d/clock, save and
exit.
If you are not installing Gentoo on IBM PPC64 hardware, continue with
Installing Necessary System Tools.
Configuring the Console
Note:
The following section applies to the IBM PPC64 hardware platforms.
|
If you are running Gentoo on IBM PPC64 hardware and using a virtual console
you must uncomment the appropriate line in /etc/inittab for the
virtual console to spawn a login prompt.
Code Listing 3.6: Enabling hvc or hvsi support in /etc/inittab |
hvc0:12345:respawn:/sbin/agetty -L 9600 hvc0
hvsi:12345:respawn:/sbin/agetty -L 19200 hvsi0
|
You should also take this time to verify that the appropriate console is
listed in /etc/securetty.
You may now continue with Installing Necessary
System Tools.
[ << ]
[ < ]
[ Home ]
[ > ]
[ >> ]
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.
|