Compatibility and installation

Linuxconf works for a.out and ELF systems. It installs currently directly on

Linuxconf is distributed in a tar.gz format (binary distribution) which may be installed on almost any distribution. Distribution specific packages (RPM for one) are also available, see below.

The version 1.10r34 is known to be stable. Check here to get it here.

RedHat 5.1 users must use the 1.11 release from RedHat. Version 1.12 will be available shortly and will be the recommend version for all distributions, including RedHat 5.1. So for now, all distribution must use 1.10, except RedHat 5.1. A small FAQ was written to explain how linuxconf works on redhat 5.1 and what is the story with linuxconf 1.11. You will find it here .

Installing from the linuxconf-xxx.bin-elf/aout.tar.gz distribution

For distribution other than RedHat and Caldera, this is the appropriate install method.

To install the tar.gz package, just do (assuming you put the package in /tmp the 1.9r25-9 release)

	cd /
	tar zxvf /tmp/linuxconf-1.9r25-9.bin-elf.tar.gz

The install script is quite verbose and ask quite a few questions. Answering yes to all is the recommend practice. When installing from the source distribution, the "make install" command does the same thing and run the /install/ script at the end.

Uninstalling the tar.gz distribution

You simply run the /install/ script. Linuxconf users who have installed the tar.gz distribution and would like to move to the native packaging technology of their linux system (RPM for redhat or DEB for debian) may uninstall from this script and install using the native package.


Linuxconf install with the tar.gz distribution on Slackware. Slackware does not use any special packaging format.

Slackware users should read the "installation issues" at the end of this page. This is especially important for Slackware systems because most of the networking configuration is buried in rc.inet1 and rc.inet2. Linuxconf has no way to probe those files and the operation done in those files are sometime conflicting with linuxconf. So under linuxconf, those scripts are not executes anymore.

Installing the RPM distribution

There are two RPMs for linuxconf. One provide the core functionnality and the other, the GUI frontend. You can install only the core if you do not expect to run X with linuxconf.

To install the RPM version, simply do (like any RPM)

	rpm -i linuxconf-1.9r27.2-1.i386.rpm
	rpm -i linuxconf-gui-1.9r27.2-1.i386.rpm

To uninstall linuxconf, simply do (as any other RPM)

	rpm -e linuxconf
	rpm -e linuxconf-gui

To upgrade to a new linuxconf release, simply do

	rpm -U linuxconf-xxxxx.i386.rpm
	rpm -U linuxconf-gui-xxxxx.i386.rpm


For RedHat (an other RPM based distribution), an RPM is available. With it, you can install, upgrade and uninstall linuxconf.

Since linuxconf 1.9r25, linuxconf fully supports Sysv style startup scripts used by redhat (and other distribution as well). This let linuxconf seamlessly integrate in RedHat.

The RPM for redhat is now maintained by Jacques Gélinas. Production of the RPM is now a builtin feature of the standard linuxconf source. This means that since 1.9r26.17, linuxconf is always distributed as a tar.gz package and RPM, side by side.

RedHat 5.0

For RedHat 5.0, a special RPM is available. It is compiled with glibc. Note that the other RPM for RedHat 4.2 will work fine. So it is not a big mistake to install this one. The RPM is identified with the suffix rh5>. For example, for redhat 4.2 (and all other RPM based distributions), you have


And for Red Hat 5, you have


Redhat on Sparc-linux

The RPM is available since 1.9r27. is a sparc-linux :-). To install, uninstall and upgrade, use the same commands as with the PC version (i386).

Redhat on Alpha-linux

The RPM is available since 1.10r7. It operates on RedHat 5.0. To install, uninstall and upgrade, use the same commands as with the PC version (i386).


Since 1.9r26.17, installation on Caldera system is supported with the same RPM as the one used for RedHat. The RPM is fully aware of both distributions. This was tested on Caldera Open Linux Standard 1.1.

Use the same command as with a RedHat system. Again, this is the same RPM file which works on both.


A DEB package is available from in /pub/debian/project/experimental . This DEB package is new and supports the Sysv init script found on Debian system. You may wish to contact the maintainer of this DEB package Martin Alonso Soto Jacome at before installing.

The tar.gz distribution is also Debian aware, but has not been tested as much on Debian.

This DEB package is getting older and older now.


Since 1.10r3, installation on SuSE system (5.1) is supported with the same RPM as the one used for RedHat and Caldera. The RPM is fully aware of the three distributions. The bin-elf.tar.gz distribution may also be used to install on a SuSE system. This was tested on SuSE 5.1.

Use the same command as with a RedHat system. Again, this is the same RPM file which works on both.

A quick note for SuSE users. YaST does not collaborate well with other administration system. To avoid conflict, you should edit the file /etc/rc.config and modify the line


Unless you do that, YaST will happily overwrite many configuration changes you have done with linuxconf, making its usage pointless.

Some issues related to installation

Linuxconf manages quite a few things which are generally left as a "do it yourself" in all/most linux distributions. Some admins will choose to configure those various services using quite a few different strategies. Most will add the configuration commands in the rc.local script.

Linuxconf goes further than simple configuration. It is an activator. It fully controls the boot process, providing all kind of added value to it, including full logging, errors logging and operator bypass. You can even change the configuration of your system while it is booting...

Linuxconf supports the native boot strategy of the various distributions as much as possible, but it is possible that one custom service is not enabled after installing linuxconf. So installing linuxconf on a heavily customised linux system should be done carefully. When installing on such servers. the following steps should be done. This is important to avoid unpleasant surprise. Most glitches you may find are easily fix in a minute using linuxconf. If you don't pay attention, the glitches may be left unfixed for a long time.

List of non standard configuration features

Linuxconf provides a frontend to configure quite a few things that are generally done in an adhoc way. This is generally true for services which are lacking a standard configuration file. If your current installation has such configurations, you may wish to revise them using linuxconf after installation.