Here are some basic instructions for installation. See for
more info:
	https://subtrac.sara.nl/oss/svn/pxeconfig

If you are using DEBIAN then you can run the following utility:
 - debian/rules binary
 - dpkg -i <packagename>

Else:
 - ./configure
 - make install

 - To activate the 'pxeconfigd' daemon utility on other platforms use this
   procedure:
 1) edit '/etc/services', eg:
      pxeconfigd      6611/tcp                       # pxe config daemon

 2) Install the server:
    a) inetd.conf
      - edit '/etc/inetd.conf', eg:
        pxeconfigd stream  tcp nowait  root.sys /usr/sbin/tcpd \
          /usr/sara/sbin/pxeconfigd

      - /etc/init.d/inetd reload 

    b) xinetd
      - cp pxeconfigd.xinetd /etc/xinetd.d/pxeconfigd
      - /etc/init.d/xinetd reload 
       
    NOTE: the pxeconfigd can only be started from inetd or xinetd!!!


 4) You can test it by: 
     telnet localhost pxeconfigd (or port number)

     output:
       Trying 127.0.0.1...
       Connected to localhost.
       Escape character is '^]'.
       ip = 127.0.0.1, hex = 7F000001
       file = /tftpboot/pxelinux.cfg/7F000001
       Connection closed by foreign host.

     In syslog a line will be added if the removal is succesful:
      Feb 20 09:32:40 test pxeconfigd: /tftpboot/pxelinux.cfg/7F000001

 4) As you can see '/tftpboot/pxelinux.cfg/' is the default directory. If
    you placed the config files somewhere else you can add the 
    '-d/--directory' option, eg:
       pxeconfigd stream  tcp nowait  root.sys /usr/sbin/tcpd \
        /usr/sara/sbin/pxeconfigd -d /<some>/<other>/<place>

If the daemon works and you want to install/reinstall a node, a link
must be placed in the '/tftpboot/pxelinux.cfg' directory. This can
be done with the 'pxeconfig' utility. This utility will ask some
questions and will make the links for you. The utility requires the following
setup:
  1) All the pxe configuration files must start with the keyword 'default.' 
     N.B.: yes, the dot after 'default' is part and parcel of the keyword!
     In this distribution two examples are included. Pxeconfig lets the
     user decide which 'default.' config file to use.

  2) If default is a symbolic link to for example default.harddisk, then
     default.harddisk is not included in the list where the user can
     choose from.

  3) You can give a command line switch to specify where the
     pxe config files reside:
        pxeconfig -d /<some>/<other>/<place>

The last utility is 'hexls'. This utility will display the hex pxe config
file with the corresponding ip-addresses.

To activate this on a client you must add the following line to the 'master'
script of the node. It will remove the pxe config file for the node
from the pxe bootserver. I personally place the line just before the umount
commands. See below which command to use for which systemimager version.
Telnet is not included in the 3.X versions.
   # Remove the <hex_ipaddr> file from the pxelinux.cfg directory.
   # So the client will boot from disk
   #        
   3.X)  chroot /a telnet $IMAGESERVER 6611
   2.X)  telnet $IMAGESERVER 6611


Comments or Suggestions mail them to:
 pxeconfig@sara.nl
 http://www.sara.nl for more info about SARA
