c. After the upload, the Point of Service terminal renews the DHCP lease file
(
dhcpcd -n
).
d. The Point of Service terminal attempts to load its new
config.
MAC
file from
the TFTP server.
e. If the
config.
MAC
file is not yet available, the Point of Service terminal waits
60 seconds before repeating steps c and d.
15. When the
config.
MAC
file loads, the system begins an analysis of its contents.
For more information about the content and file format of the
config.
MAC
file,
refer to Section 7.7.1, “The config.
MAC
File” (page 94).
16. The
PART
line in the
config.
MAC
file is analyzed.
If there is a
PART
line in the configuration file, a check is made using the image
version to see whether any local system needs to be updated.
• If no system update is required, no image download occurs and the Point of Service
terminal boots from the hard drive.
• If a system update is required, the Point of Service terminal's hard disk is parti-
tioned according to the parameters specified in the
PART
line.
17. The
SYNC
line in the Point of Service configuration file is evaluated.
The file indicated in the SYNC line is downloaded over TFTP. The only value the
file contains is the number of seconds to wait (sleep) before the multicast download
of the system image starts. If the file is not present, the boot process immediately
proceeds.
18. Indicated images are downloaded with multicast TFTP.
19. If the image is compressed, it is copied then decompressed.
20. The image checksums are verified. If they do not match, the images are re-down-
loaded.
21. The
CONF
line in the Point of Service configuration file is evaluated.
Deploying Point of Service Terminals
107
