This page gives you some sample entries for the bootptab file. Note that
your system may be different.
Sample bootptab File
This
file would normally be located in /etc/bootptab. Note that lines marked
# are comment lines. Note also that the passwords shown here are in
clear text, since the bootp table can be read-protected on the system.
(A configuration file specified by BOOTP cannot be read-protected, since
it must be readable by TFTP, and so any passwords occuring there must be
encrypted. Configuration files loaded directly by the ViewStation can be
read-protected, and so can use clear-text passwords.) The configuration
file is loaded from the host which sent the bootp response.
This sample file contains a section for global settings, which
would apply to everything on the system and/or also a subnet entry,
which would apply to smaller divisions of the entire system. The
entries for individual machines are entered last. Refer to the RFC
documents and your system documents for the specific details of booptab
file syntax. This is sometimes a difficult problem; for instance, some
systems require the boot file name to have a leading slash, others
refuse to read it with the leading slash, and some allow :hd and :bf on
the same line, others do not. Check your system requirements for this
file.# First, we define a system entry (such as
subnet2) which
# specifies the things every host on that subnet uses.
#
subnet2.default:\
:hd=/home/HDSware/hds-fx/image:\
:bf=V30-D.hds:\
:T128="Galahad":\
:T129="test.3.cfg":\
:T130="/home/hdssun1/boot":
#
# Now come the individual ViewStations
#
marketing#1:\
:tc=subnet2.default:\
:ht=ethernet:\
:ha=008096000167:\
:ip=128.91.5.68:
#
marketing#2:\
:tc=subnet2.default:\
:hd=:bf=/home/HDSware/hds-fx/image/V30.hds:\
:ht=ethernet:\
:ha=00809600015d:\
:ip=128.91.5.13:
This sample file has sample entries for Bootp. Note that the
vendor tag fields are present and that the configuration file called
for the marketing#2 unit is test.3.cfg.
When you use BOOTP to specify the download of the boot file
(server code), several different combinations of bootp fields can be
used to attempt the download process. These combinations are listed
below in the order they are tried:
1. T130 and T129
2.
T130 and hds.setup
3. hd and T129 (if there is no T130 field)
4. path of hd and hds.setup (if there are no T129 or T130 fields)
Return to Section Heading Page
Return to the Home Page
If you need more information than is available here, you can reach
HDS via email at info@hds.com, or
call us at 1.800.HDS.1551 in the USA, or at +610.277.8300 from outside
the US. For questions or problems regarding the HDS WWW page, contact
webmaster@hds.com.
© 1996 by HDS Network Systems
Inc.