Handbook:Parts/Installation/Tools

OpenRC
Some tools are missing from the stage3 archive because several packages provide the same functionality. It is now up to the user to choose which ones to install.

The first tool to decision is a logging mechanism for the system. Unix and Linux have an excellent history of logging capabilities - if needed, everything that happens on the system can be logged in a log file.

Gentoo offers several system logger utilities. A few of these include:


 * - Offers the traditional set of system logging daemons. The default logging configuration works well out of the box which makes this package a good option for beginners.
 * - An advanced system logger. Requires additional configuration for anything beyond logging to one big file. More advanced users may choose this package based on its logging potential; be aware additional configuration is a necessity for any kind of smart logging.
 * - A highly-configurable system logger.

There may be other system logging utilities available through the Gentoo ebuild repository as well, since the number of available packages increases on a daily basis.

To install the system logger of choice, emerge it. On OpenRC, add it to the default runlevel using. The following example installs and activates as the system's syslog utility:

systemd
While a selection of logging mechanisms are presented for OpenRC-based systems, systemd includes a built-in logger called the journald service. The journald service is capable of handling most of the logging functionality outlined in the previous system logger section. That is to say, the majority of installations that will run systemd as the system and service manager can safely skip adding a additional syslog utilities. See for more details on using  to query and review the systems logs.

For a number of reasons, it may be important to include redundant system logging mechanisms on a systemd-based system. This is a irregular occurrence and is not covered by the handbook, but is a real use case.

Optional: Cron daemon
Next is the cron daemon. Although it is optional and not required for every system, it is wise to install one.

A cron daemon executes scheduled commands. It is very handy if some command needs to be executed regularly (for instance daily, weekly or monthly).

Gentoo offers several possible cron daemons, including, , , and. Installing one of them is similar to installing a system logger. The following example uses :

On OpenRC:

Or on systemd:

If dcron is used, an additional initialization command needs to be executed:

If fcron is used, an additional emerge step is required:

Optional: File indexing
In order to index the file system to provide faster file location capabilities, install.

Optional: Remote access
To be able to access the system remotely after installation, must be configured to start on boot.

To add the init script to the default runlevel on OpenRC:

And on systemd:

If serial console access is needed (which is possible in case of remote servers), must be configured.

On OpenRC, uncomment the serial console section in :

On systemd, run:

Time synchronization
It is important to use some method of synchronizing the system clock. This is usually done via the NTP protocol and software. Other implementations using the NTP protocol exist, like Chrony.

To set up Chrony, for example:

On OpenRC, run:

On systemd, run:

Alternatively, systemd users may wish to use the simpler SNTP client which is installed by default.

Filesystem tools
Depending on the filesystems used, it is necessary to install the required file system utilities (for checking the filesystem integrity, creating additional file systems etc.). Note that tools for managing ext4 filesystems are already installed as a part of the @system set.

The following table lists the tools to install if a certain filesystem is used:

Networking tools
If networking was previously configured in the Configuring the system step and network setup is complete, then this 'networking tools' section can be safely skipped. In this case, proceed with the section on Configuring a bootloader.

Installing a DHCP client
In order for the system to automatically obtain an IP address for one or more network interface(s) using netifrc scripts, it is necessary to install a DHCP client. We recommend the use of although many other DHCP clients are available through the Gentoo repository:

More information on can be found in the dhcpcd article.

Optional: Installing a PPPoE client
If PPP is used to connect to the internet, install the package:

Optional: Install wireless networking tools
If the system will be connecting to wireless networks, install the package for Open or WEP networks and/or the  package for WPA or WPA2 networks. is also a useful basic diagnostic tool for scanning wireless networks.

Now continue with Configuring the bootloader.