Datasheet

“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 321 — #347
i
i
i
i
i
i
i
i
14
The Hotplug System
14.5 Network Devices and Interface
Designations
If a computer has more than one network device with different drivers, it is
possible for the interface designations to change after the boot process has
completed if another driver has been loaded more quickly. For this reason,
network devices in SUSE LINUX are administered via a queue. Alter this
behavior by setting HOTPLUG_PCI_QUEUE_NIC_EVENTS=no in /etc/
sysconfig/hotplug.
However, the best way to ensure consistent interface designations is to
specify the desired name in the configuration files of the individual inter-
faces. Information about how to do this is contained in file /usr/share/
doc/packages/sysconfig/README.
14.6 Hotplug with PCI
Some computers also allow hotplug for PCI devices. To make full use of
this, it is necessary for special kernel modules to be loaded. However, on
non-PCI hotplug computers, these modules could cause problems. Unfor-
tunately, hotplug PCI slots cannot be automatically detected, so you have
to configure this function manually. To do this, set variable HOTPLUG_DO_-
REAL_PCI_HOTPLUG in file /etc/sysconfig/hotplug.
14.7 Coldplug
Coldplug is responsible for all devices connected before the hotplug system
is enabled during the boot process. It also takes care of devices that are not
easy to detect.
First, the script rccoldplug calls the command hwup for every static
hardware configuration /etc/sysconfig/hardware/hwcfg-static-
*. Then the scripts /etc/hotplug/*.rc search for devices not yet ini-
tialized and create hotplug events. For PCI devices there is both a pos-
itive and a negative list of device types which should be initialized or
skipped coldplug. Detailed comments for this are contained in the file
/etc/sysconfig/hotplug.
The scan scripts output one character on the screen for every device that
has been checked, as follows:
321SUSE LINUX Enterprise Server