Installation guide

Building menu 'rh-automatic-menu'
Adding #1: IPL section 'linux' (default)
kernel image......: /boot/vmlinuz-2.6.7-1.451.2.3 at 0x10000
kernel parmline...: 'root=LABEL=/' at 0x1000
initial ramdisk...: /boot/initrd-2.6.7-1.451.2.3.img at 0x800000
Preparing boot device: dasda (0201).
Preparing boot menu
Interactive prompt......: disabled
Menu timeout............: disabled
Default configuration...: 'linux'
Syncing disks...
Done.
6. Adding a Network Device
The process of adding a network device has changed with the migration of the 2.4 kernel to the
2.6 kernel:
• The proc file system is no longer used to control or obtain status on network devices.
• The new sys file system now provides facilities for controlling devices.
• /sys/class/net/interface_name/device now provides status on active devices.
interface_name is a name such as eth0 or eth2 that is given to a network interface by the
device driver when the device is configured.
• /etc/chandev.conf no longer exists.
The sys file system now contains the information that was placed in /etc/chandev.conf.
• /etc/modules.conf no longer exists.
Network interface alias specifications are now placed in /etc/modprobe.conf.
Section 6.1, “Adding a qeth Device” describes in detail how to add a qeth device to an existing
instance of Red Hat Enterprise Linux. Section 6.2, “Quick Reference for Adding Network
Devices” is a quick reference for installing other IBM System z network interfaces.
6.1. Adding a qeth Device
First, determine whether the qeth device driver modules are loaded.
# lsmod | grep qeth
qeth 135240 0
qdio 45360 2 qeth
ipv6 303984 13 qeth
ccwgroup 15104 1 qeth
If the output of the lsmod command shows that the modules are not loaded, you must run the
modprobe command to load them:
# modprobe qeth
Next, create a qeth group device.
6. Adding a Network Device
206