HP Neoware e140 Neoware Image Manager 4.6 User Manual - Page 272
Keywords, The Include Keyword, The Include - linux 256 256
View all HP Neoware e140 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 272 highlights
The mPXELdr Configuration File Keywords The Include Keyword Syntax: Include = Examples: 1 Include = MyIncludeFile.ininc 2 Include = /MyIncludeFile.ininc 3 Include = SomeRelativePath/MyIncludeFile.ininc 4 Include = /SomeAbsolutePath/MyIncludeFile.ininc Default value: None The is either absolute (expressed starting relative to the TFTP root directory) or relative (to the directory where the mPXELdr boot program resides). A leading '/' or '\' in the indicates an absolute path which will be passed "as is" to the TFTP server, while anything else indicates a relative path which will be prepended to whatever is set in the data part of the Include parameter. Therefore, using examples 1 to 4 above and assuming mPXELdr.bin is located in subdirectory LdrPath of the TFTP root directory (i.e. the TFTP path of mPXELdr is LdrPath\mPXELdr.bin: 1 will resolve to: LdrPath/MyIncludeFile.ininc 2 will resolve to: /MyIncludeFile.ininc 3 will resolve to: LdrPath/SomeRelativePath/MyIncludeFile.ininc 4 will resolve to: /SomeAbsolutePath/MyIncludeFile.ininc As the TFTP OS can be hosted in either a Windows, Linux or UNIX server, mPXELdr will get the default .ini file path from the mPXELdr file path (that comes from the DHCP information), and use the path separators ('/' or '\') that it finds there. mPXELdr will also use the path separators that it finds in the .ini file, whatever they are, and never alters them either. In other words, mPXELdr never inserts or removes any path separators. It merely uses those that it collects 256 Keywords