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 systemd-journald service. The systemd-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, such as the case of forwarding logs to a central host, it may be important to include redundant system logging mechanisms on a systemd-based system. This is a irregular occurrence for the handbook's typical audience and considered an advanced use case. It is therefore not covered by the handbook.

OpenRC
Although it is optional and not required for every system, it is wise to install a cron daemon.

A cron daemon executes commands on scheduled intervals. Internals could be daily, weekly, or monthly, once every Tuesday, once every other week, etc. A wise system administrator will leverage the cron daemon to automate routine system maintenance tasks.

All cron daemons support high levels of granularity for scheduled tasks, and generally include the ability to send an email or other form of notification if a scheduled task does not complete as expected.

Gentoo offers several possible cron daemons, including:


 * - cronie is based on the original cron and has security and configuration enhancements like the ability to use PAM and SELinux.
 * - This lightweight cron daemon aims to be simple and secure, with just enough features to stay useful.
 * - A command scheduler with extended capabilities over cron and anacron.
 * - A younger cron system designed with secure operations in mind. To do this, the system is divided into several separate programs, each responsible for a separate task, with strictly controlled communications between parts.

cronie
The following example uses :

Add cronie to the default system runlevel, which will automatically start it on power up:

Alternative: dcron
If dcron is the go forward cron agent, an additional initialization command needs to be executed:

Alternative: fcron
If fcron is the selected scheduled task handler, an additional emerge step is required:

Alternative: bcron
bcron is a younger cron agent with built-in privilege separation.

systemd
Similar to system logging, systemd-based systems include support for scheduled tasks out-of-the-box in the form of timers. systemd timers can run at a system-level or a user-level and include the same functionality that a traditional cron daemon would provide. Unless redundant capabilities are necessary, installing an additional task scheduler such as a cron daemon is generally unnecessary and can be safely skipped.

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

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

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

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

Uncomment the serial console section in :

systemd
To enable the SSH server, run:

To enable serial console support, 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:

OpenRC
On OpenRC, run:

systemd
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 (see also dhcpcd):

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.