Devil-Linux offers a console based configuration program. Just invoke the the command setup.
Whenever you modify the configuration of the system, you have to save it to the configuration media, otherwise the changes wouldn't survive a reboot.
Saving the configuration is done via the command save-config .
save-config does nothing else then creating a bzip2 compressed tar archive and copies it to the configuration media under the name etc.tar.bz2.
save-config does support the parameter -q. This stands for quiet and quick.
Table 1.1. Local setup
Parameter | Description | Values | Sample |
---|---|---|---|
UTC | Defines if the local clock is UTC (GMT) or to the local time | yes/no | yes |
TIMEZONE | Defines the local time zone. Available timezones can be found in the /usr/share/zoneinfo | string value | US/Eastern |
KEYBOARD_LAYOUT | Defines which keyboard layout should be loaded. | string value | de-latin1 |
INITRD_MODULES | Defines which modules should be loaded during boot time. This parameter is to support SCSI or BLOCK devices. | string value | BusLogic |
Table 1.2. Network setup
Parameter | Description | Values | Sample |
---|---|---|---|
HOSTNAME | hostname | string value | devil |
DEFAULTGATEWAY | IP address of the default gateway. | IP address in dotted notation | 10.90.1.1 |
DEFAULTGATEWAY_IF | Interface on which we reach the default gateway. | string value | eth0 |
START_ROUTING | Should routing be enabled on boot time ? | yes/no | yes |
START_FIREWALL | Should the script /etc/init.d/firewall.rules be executed at boot time ? | yes/no | yes |
DISABLE_ECN | Disable ECN (early congestion notification) ? This is needed if you have problems connecting to some websites. | yes/no | yes |
The configuration files are located in /etc/sysconfig/nic directory.
You need one file for each interface. The filename has to begin with ifcfg-.
There are a few samples available in the NIC configuration directory, which give you real-world examples on how to use the settings.
If you don't know which modules supports your network card, you can try using the command modprobe -t net \* . After that you can check the console and syslog messages and check which modules are loaded (lsmod).
Table 1.3. Network interface configuration
Parameter | Description | Values | Sample |
---|---|---|---|
ONBOOT | Should the interface started at boot time ? | yes/no | yes |
DEVICE | Device name of the interface (eth0, eth0:0, eth1 ...) | string value | eth0 |
DHCP | Should the IP address be requested from a DHCP server ? Or should even a DHCP server run on this interface ? NOTE: for a DHCP server you need to assign a static IP address. | yes/no/server | no |
IP | IP address of the defined interface. Leave empty to bring interface up without an IP address. | IP address in dotted notation / empty | 10.90.1.2 |
NETMASK | Network mask for this interface | IP address in dotted notation | 255.255.255.0 |
BROADCAST | broadcast address for this interface leave this setting empty for an automatic assignment | IP address in dotted notation | 10.90.1.255 |
MAC | Changes the MAC address of the interface | MAC address with colons | 12:34:56:67:91:11 |
MODULE | Name of the module to load for this interface. Leave this setting empty when module is already loaded or this interface is an IP alias. | string value | pcnet32 |
ROUTE | Define routing entries for this interface. See section Routing for details. | string value | 10.90.1.253:192.168.2.0/255.255.255.0 |
VLAN | Set the VLAN ID for this interface | numeric value (0 < vlanid < 4095) | 100 |
BR_IF | Defines which interfaces should be bridged. Note: the interface name for this interface needs to be brX, e.g. br0 | string values with the interface names | eth2 eth3 |
Routing is defined in the network interface configuration files.
The format for an routing entry is: GATEWAY:NET/MASK , i.e. ROUTE="10.90.1.253:192.168.2.0/255.255.255.0"
See this example for some more details:
### ROUTE="GATEWAY:NET/MASK" #ROUTE="10.90.1.253:192.168.2.0/255.255.255.0" ### if you don't have a gateway use: #ROUTE=":192.168.2.0/255.255.255.0" ### for more than one route use: #ROUTE="$ROUTE 10.90.1.252:192.168.3.0/255.255.255.0" # ## if you have only a host: #ROUTE="$ROUTE 10.90.1.251:172.16.3.14"
The best and safest way when upgrading is to start with the new etc.tar.bz2 file. Next, you can recover previous configurations files with caution : don't forget to check changes log to see which services could be affected with the new release. Files you may want to recover :
/etc/passwd
/etc/shadow
/etc/ipsec.*
/etc/sshd/*
/etc/sysconfig/nic/ifcfg-*
/etc/init.d/rc.firewall