Overview Of The Cr Boot Process - Novell SLRS 8 Admin Manual

15.6.3 Overview of the CR Boot Process

The following section describes the steps that take place when the cash regis-
ter is booted with the image determined by its product ID:
Via PXE network boot or boot manager (GRUB), the cash register boots
the initrd (initrd.gz) that it receives from the branch server. If no PXE
boot is possible, the cash register tries to boot via hard disk, if accessible.
Running linuxrc starts the following process:
1. The required file systems to receive system data are mounted. Example:
proc file system.
2. The cash register hardware type (HWTYPE) is detected (the POS hard-
ware manufacturer provides a program for this).
3. The cash register BIOS version (HWBIOS) is detected (the POS hardware
manufacturer provides a program for this).
4. Network support is activated. The required kernel module is determined
from the static table /IBMProduct 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. The re-
quired entries in /IBMproduct correspond to one line each per hardware
type in the following format:
hardware type=module name
The module is loaded using modprobe. Any dependencies to other mod-
ules are cleared at that time.
5. The network interface is set up via DHCP. After the interface has been es-
tablished, the DHCP variables are exported into the file /var/lib/dhcpcd/dhcpcd-
eth0.info and the contents of DOMAIN and DNS are used to generate a
/etc/resolv.conf.
6. The TFTP server address is acquired. During this step, a check is first
made to determine whether the host name tftp.$DOMAIN can be re-
solved. If not, the DHCP server is used as the TFTP server.
7. The configuration file is loaded from the server directory /tftpboot/CR
via TFTP. At this point, the cash register expects the file:
config. MAC Address
15.6 Booting the Cash Registers
151