3. The Point of Service terminal downloads the Linux kernel from the
netboot
image which consists of several files (the Linux kernel and a symbolic link, the
initrd, and the initrd's md5sum), for example:
initrd-netboot-SLEPOS11.i686-3.1.8.gz
initrd-netboot-SLEPOS11.i686-3.1.8.kernel.2.6.16.46-0.12-default
initrd-netboot-SLEPOS11.i686-3.1.8.kernel
initrd-netboot-SLEPOS11.i686-3.1.8.md5
The naming scheme of the kernel is
initrd-
netboot_image
_name
-SLEPOS11.i686-
image_version
.kernel.
kernel
_version
-default
. The Linux kernel is used to PXE boot the Point of Service
terminals.
4. Using PXE network boot or boot manager (GRUB), the Point of Service terminal
boots the initrd (e. g.
initrd-netboot-SLEPOS11.i686-3.1.8.gz
) that
it receives from the Branch Server.
If no PXE boot is possible, the Point of Service terminal tries to boot via hard disk,
if accessible.
5. The
linuxrc
script begins.
6. The file systems required to receive system data are mounted; for example, the
/proc
file system.
7. The Point of Service hardware type (
hwtype
) is detected.
The Point of Service hardware manufacturer provides a program to do this. The
first time the Point of Service terminal boots, this information is used to register
the Point of Service terminal and create the terminal's
config.
MAC
file. This in-
formation is also used to determine which configuration files the terminal should
use.
8. The Point of Service BIOS version (
hwbios
) is detected. The Point of Service
hardware manufacturer provides a program to do this.
9. Network support is activated. The required kernel module is determined from a
static table by selecting the entry corresponding to the hardware type. If no known
hardware type is detected, a default list of modules is used and types are tried one
after the other. Forcing loading a driver is possible using boot parameters such as
kiwikernelmodule=ide-disk
.
Deploying Point of Service Terminals
105