
Feb 16th, 1997 (updated for TCP/IP 4.24)

The QNX TCP/IP product 4.23 or later is required to setup a QNX
BOOTP server.  Please refer to the TCP/IP manuals for more
information regarding the following programs and configuration files
as well as any other TCP/IP related configuration options.

Server Configuration Files:
---------------------------

/etc/bootptab    - configuration file read by bootpd 
                   ( similar to QNX netboot/netmap )

Notes:
------

1)  bootpd should be started either in your netstart or your sysinit.

2)  tftpd must be run as a non root user.  bin is one possibility.
    The example inetd.conf in /etc/config/socket/inetd.conf does this.

3) The "/etc/bootptab" file has an example entry for "node206". Note that
   the filename specified is non-standard. We have added an extension to the
   BOOTP standard to allow the use of the QNX "buildqnx" utility with BOOTP.
   The changes to support this were made to the "tftpd" utility. 

   This QNX extension works as follows : 
   If the filename given to "tftpd" begins with a "|" and the request is a
   READ request and the tftpd isn't running as root, then open a pipe (popen()) 
   rather than a file (open()). 

   This change allows an existing QNX user to use virtually the same "build"
   files whether using BOOTP or QNX NETBOOT. See the example build file for
   node 206 below. (e.g. node206.ws).

   Without this extension, you would need to prebuild all of your bootp image
   files and have them reside on your server's local disk. This could be
   cumbersome and consume much disk in a large network configuration.

NOTE: The Lanworks BOOTP ROM expects that you've build your image
for offset 0x10000 (-b0x10000 to buildqnx).

node206.ws (Note: If using this example CHANGE the -m option to Net)
----------

sys/Proc32
$ 0 Proc32 -l 206

sys/Slib16
$ 1 Slib16

sys/Slib32
$ 1 Slib32

/bin/Net
$ 1 Net -m "1 2 00001a abc123"

/bin/Net.ether1000
$ 1 Net.ether1000 -l 2 -i10 -p300 -vvvv

/bin/sinit
$ 1 sinit -r //1/  TERM=qansi
