10. The module is loaded using
modprobe
. Any dependencies to other modules are
resolved at that time.
11. The network interface is set up via DHCP.
12. After the interface has been established, the DHCP variables are exported into the
/var/lib/dhcpcd/dhcpcd-eth0.info
file and the contents of DOMAIN
and DNS are used to generate an
/etc/resolv.conf
file.
13. The TFTP server address is acquired.
During this step, a check is first made to determine whether the hostname
tftp
.
DOMAIN
can be resolved. If not, the DHCP server is used as the TFTP server.
Forcing another TFTP server is possible with a kernel parameter such as
kiwitftp=
IP_ADDRESS
or set this kernel parameter in the
pxelinux.cfg/
default
file.
14. The Point of Service configuration file,
config.
MAC
, is loaded from the Branch
Server's
/srv/tftpboot/CR
directory over TFTP.
If this is the Point of Service terminal's first time booting, its
config.
MAC
file
does not yet exist. The Point of Service terminal must first register on the system.
A new Point of Service terminal registers as follows:
a. An optional alias name can be set for the new Point of Service terminal. During
the creation of one of the boot images, you can enable the system alias setting
using the
POSSetAlias
feature module. By default, there is no question for
the system alias name.
b. A Point of Service control file (
hwtype.
MAC
) is uploaded to the TFTP server's
upload directory:
/srv/tftpboot/upload
.
The
hwtype.
MAC
file indicates the Point of Service hardware type, the BIOS
version, and the Point of Service alias name. The system uses this information
to create the terminal's
config.
MAC
file. For more information on this process,
see Section 7.7.3, “The hwtype.
MAC
File” (page 100).
106
SUSE Linux Enterprise Point of Service Guide
