Changes between Initial Version and Version 1 of PxeUsage


Ignore:
Timestamp:
11/14/06 11:22:34 (17 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PxeUsage

    v1 v1  
     1[[ShowPath]]
     2[[PageOutline]]
     3
     4= Usage =
     5
     6If 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:
     7  * 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.
     8
     9  * 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.
     10
     11  * You can give a command line switch to specify where the pxe config files reside:
     12{{{
     13        pxeconfig -d /<some>/<other>/<place>
     14}}}
     15
     16The last utility is ''hexls''. This utility will display the hex pxe config file with the corresponding ip-addresses and hostnames
     17
     18
     19== Systemimager activation ==
     20To activate this on a client you must add the following line to the ''systemimageer 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.
     21
     22Telnet is not included in the 3.X versions:
     23{{{
     24   # Remove the <hex_ipaddr> file from the pxelinux.cfg directory.
     25   # So the client will boot from disk
     26   #
     27   3.X)  chroot /a telnet $IMAGESERVER 6611
     28   2.X)  telnet $IMAGESERVER 6611
     29}}}
     30