[[ShowPath]] [[PageOutline]] = Usage = If the ''pxeconfigd'' works and you want to install, memtest, etc.. 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: * 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. * If default is a symbolic link to for example [source:trunk/pxemenu/pxelinux.cfg/default.menu default.menu], then ''default.menu'' is not included in the list where the user can choose from. * You can give a command line switch to specify where the pxe config files reside: {{{ pxeconfig -d /// }}} == Systemimager activation == To activate this on a client depends on your version of systemimager and your preferred method === Telnet method === To 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. Telnet is not included in the 3.X versions: {{{ # Remove the 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 }}} === Post install script method === With systemimager version 3.7 and higher it easier to setup. In the systemimager server examples directory there is an pxeconfig post installation script (Author: Ole Holm Nielsen), eg: {{{ cp /usr/share/doc/systemimager-server/examples/post-install/30all.pxeconfig \\ /scripts/post-install }}}