Neoware e140 - Thin Client User Manual page 273

from the PXE TFTP file path and the
because mPXELdr has no idea whether the TFPT server is talking to
a Windows, Linux or UNIX server. Even if the TFTP specification
allowed such information to be known, the PXE specification is not
designed to relay such information to mPXELdr.
It is the user's responsibility to use the correct separator in the
DHCP parameters and
implementations are also path separator indifferent. This is how it
should be because the TFTP client OS might be Windows, Linux or
UNIX, and the TFTP client typically doesn't know either what OS
and path separator convention the TFTP server is running.
Finally, it should be noted that the above rules are applied to gener-
ate a filepath (which must be no more than the PXE specification
limitation of 127 bytes), and in the end that filepath is sent to the
TFTP server. The result of the operation may then depend on the
behavior of the TFTP server. This should not be overlooked, espe-
cially in the following areas:
Absolute path definitions:
•
If an include path definition starts with a path separator, the
TFTP server might interpret the path separator as relative to the
TFTP root directory OR to the host OS directory. For security
reasons, the TFTP software and/or launching script should
implement the former, but this should be checked with the TFTP
server administrator.
Use of ' ' and '
•
. ..
TFTP server may or may not accept or require the use of '
indicate the current directory and/or '
(higher) directory in the directory tree.
When mPXELdr processes an
the file passed as a parameter. If the attempt succeeds, the contents
of the file is processed exactly as if it had been found in the
Include
file being processed, at the point the
.ini
found.
The mPXELdr Configuration File
.ini
file. However, some TFTP server
.ini
' in paths.
..
directive, it attempts to open
Include
file. This is important
' to
.
' to indicate a previous
directive was
Include
Keywords 257