Novell LINUX ENTERPRISE DESKTOP 10 SP2 - DEPLOYMENT GUIDE 08-05-2008 Deployment Manual page 407

changing the root file system, it is necessary to regenerate the devices. This is done by
boot.udev with the command udevtrigger.
If you need to change hardware (e.g. hard disks) in an installed system and this hardware
requires different drivers to be present in the kernel at boot time, you must update the
initramfs file. This is done in the same way as with its predecessor, initrd—by
calling mkinitrd. Calling mkinitrd without any argument creates an initramfs.
Calling mkinitrd -R creates an initrd. In SUSE Linux Enterprise®, the modules to
load are specified by the variable INITRD_MODULES in /etc/sysconfig/
kernel. After installation, this variable is automatically set to the correct value. The
modules are loaded in exactly the order in which they appear in INITRD_MODULES.
This is only important if you rely on the correct setting of the device files /dev/sd?.
However, in current systems you also may use the device files below /dev/disk/
that are sorted in several subdirectories, named by-id, by-path and by-uuid, and
always represent the same disk. This is also possible at install time by specifying the
respective mount option.
IMPORTANT: Updating initramfs or initrd
The boot loader loads initramfs or initrd in the same way as the kernel. It is
not necessary to reinstall GRUB after updating initramfs or initrd, because GRUB
searches the directory for the right file when booting.
17.1.2 init on initramfs
The main purpose of init on initramfs is to prepare the mounting of and access to the
real root file system. Depending on your system configuration, init is responsible for
the following tasks.
Loading Kernel Modules
Depending on your hardware configuration, special drivers may be needed to access
the hardware components of your computer (especially your hard drive). To access
the root file system, the kernel needs to load the proper file system drivers.
Providing Block Special Files
For each loaded module, the kernel generates device events. udev handles these
events and generates the required block special files on a RAM file system in /dev.
Without those special files, the file system and other devices would not be accessi-
ble.
Booting and Configuring a Linux System 391