2
The POS machine uploads the
hwtype.
MAC
file (for example
hwtype.00:
11:25:A7:D6:0D
) into the
/srv/tftpboot/upload
directory.
3
The
posleases2ldap.pl
script uses this file and the information in the
LDAP database to create the
config.
MAC
file (for example
config.00:
11:25:A7:D6:0D
) in the
/srv/tftpboot/CR
directory.
4
The POS machine uses the information in the
config.
MAC
file to load the
correct image, and boots up.
The third step is the most important part of this process. The following conditions must
be met to complete it successfully:
• The
hwtype.
MAC
file must be present in the
/srv/tftpboot/upload
direc-
tory.
NOTE: Configuration Without an External DHCP Server
If an external DHCP server is not used, the terminal must get the IP address
from the Branch Server (its MAC address must be listed in the
/var/lib/
dhcp/db/dhcpd.leases
file).
This occurs when the system was set by
posInitBranchserver.sh
with
EXT_DHCP=FALSE
in the LDAP database under
scLocation
corre-
sponding to this Branch Server. POS terminal then gets its IP address from
the DHCP server on the Branch Server.
• The correct image file and its checksum file must be located on the Branch Server
in the in the
/srv/tftpboot/image
directory. These files should be download-
ed before from the Administration Server. For more information, see chapters
Section 6.5, “Downloading Images from the Administration Server” (page 64).
Example 3.1
Example Image and Checksum Files
/srv/tftpboot/image/myGraphical_test.i686-3.1.4
/srv/tftpboot/image/myGraphical_test.i686-3.1.4.md5
• An associated object representing the used image file must exist in the LDAP
database.
Basic Configuration
31