Re: [sisuite-users] ANNOUNCE: New version of pxeconfig utilities (1.0.0)
Some additional information regarding the announcement of the new version of pxeconfig utilities (1.0.0): * There is a new PXE menu system (contributed by yours truly) which allows you to control the computer's booting interactively at the console. Very, very useful. * The pxeconfig homepage is at https://subtrac.sara.nl/oss/pxeconfig where you'll find documentation etc. * Download the pxeconfig utilities from ftp://ftp.sara.nl/pub/outgoing/ We look forward to your feedback on the sisuite mailing list ! Best regards, Ole Bas van der Vlies wrote: > 1.0.0 >- List of pxeconfig files are now sorted alphabetically >- Use GNU getopt. This means that option and non-option arguments may be > intermixed. > >- hexls now sorts its output > Suggested by : Ole Holm Nielsen > Implemented by : Bas van der Vlies > >- hexls now also display link info for hex files shorter dan 8 characters. > Some hex files can point to a subnet IP adddress > Suggested by : Ole Holm Nielsen > Implemented by : Bas van der Vlies > >- Added -b/--basename option. This is for host with a common prefix, eg: >pxeconfig --basename gb-r40n --start 1 --end 2 --filename > default.install > > Will create links to default.install for hosts: > gb-r40n1 > gb-r40n2 > > Implemented by: Bas van der Vlies > >- Added pxe-menu tools: > """ > The PXE-menu tools are used to control the booting of networked computers > directly from the computer's console at the BIOS level before any operating > system has been loaded. This is extremely useful for diagnostic purposes, > or for selecting an operating system installation method, of an individual > computer. For further information please read the files README-pxemenu and > INSTALL-pxemenu. > """ > Implemented by: Ole Holm Nielsen -- Ole Holm Nielsen Department of Physics, Technical University of Denmark, Building 307, DK-2800 Kongens Lyngby, Denmark - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] ANNOUNCE: New version of pxeconfig utilities (1.0.0)
1.0.0 - List of pxeconfig files are now sorted alphabetically - Use GNU getopt. This means that option and non-option arguments may be intermixed. - hexls now sorts its output Suggested by : Ole Holm Nielsen Implemented by : Bas van der Vlies - hexls now also display link info for hex files shorter dan 8 characters. Some hex files can point to a subnet IP adddress Suggested by : Ole Holm Nielsen Implemented by : Bas van der Vlies - Added -b/--basename option. This is for host with a common prefix, eg: pxeconfig --basename gb-r40n --start 1 --end 2 --filename default.install Will create links to default.install for hosts: gb-r40n1 gb-r40n2 Implemented by: Bas van der Vlies - Added pxe-menu tools: """ The PXE-menu tools are used to control the booting of networked computers directly from the computer's console at the BIOS level before any operating system has been loaded. This is extremely useful for diagnostic purposes, or for selecting an operating system installation method, of an individual computer. For further information please read the files README-pxemenu and INSTALL-pxemenu. """ Implemented by: Ole Holm Nielsen Here is the README: = PXE-utilities - This is a release of the SARA package of utilities that we use to boot our nodes with PXE-enabled network cards. This was developed because we always want to use the PXE-enabled network card as our first boot device. With pxelinux, which is a derivative of syslinux, you can specify with a PXE configuration file how the node must boot. This configuration is placed in, e.g. '/tftpboot/pxelinux.cfg' directory. The PXE-menu tools are used to control the booting of networked computers directly from the computer's console at the BIOS level before any operating system has been loaded. This is extremely useful for diagnostic purposes, or for selecting an operating system installation method, of an individual computer. For further information please read the files README-pxemenu and INSTALL-pxemenu. In our setup we have a default setup. The default setup is to boot from harddisk. When a node boots it fetches the default configuration file and the configuration file tells the node to boot from the harddisk. This setup is used for nodes that have already been installed by systemimager. At SARA we have developed the following strategy how to install a fresh node. 1) The ip-address in our setup is known for the new node. So we make a link in the '/tftpboot/pxelinux.cfg' directory to a pxe config file which tells that it has to fetch the kernel en root filesystem from our bootserver, eg: 0A000A02 ---> default.node_install (10.0.10.2) 2) The client starts and uses the systemimager software to install the node. The last line of installation script connects to a daemon on the bootserver. This daemon will remove the PXE config filefor this node. 3) The node reboots and will use the default pxe config file which will instruct the node to boot from harddisk. This release contains the following utilities: pxeconfigd) This is daemon that removes the pxe configuration file of a node. pxeconfig) With this program we can specify which pxe config file a node or nodes must use. This utility will create the links in '/tftpboot/pxelinux.cfg' hexls) Is a utility that diplays a directory, and, if in this directory contains HEX files, it will convert them to IP-numbers. All these utilities are written in Python. Comments or Suggestions mail them to: pxeconfig at sara dot nl http://www.sara.nl for more info about SARA. -- -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] ANNOUNCE: New version of pxeconfig utilities(1.0.0)
1.0.0 - List of pxeconfig files are now sorted alphabetically - Use GNU getopt. This means that option and non-option arguments may be intermixed. - hexls now sorts its output Suggested by : Ole Holm Nielsen Implemented by : Bas van der Vlies - hexls now also display link info for hex files shorter dan 8 characters. Some hex files can point to a subnet IP adddress Suggested by : Ole Holm Nielsen Implemented by : Bas van der Vlies - Added -b/--basename option. This is for host with a common prefix, eg: pxeconfig --basename gb-r40n --start 1 --end 2 --filename default.install Will create links to default.install for hosts: gb-r40n1 gb-r40n2 Implemented by: Bas van der Vlies - Added pxe-menu tools: """ The PXE-menu tools are used to control the booting of networked computers directly from the computer's console at the BIOS level before any operating system has been loaded. This is extremely useful for diagnostic purposes, or for selecting an operating system installation method, of an individual computer. For further information please read the files README-pxemenu and INSTALL-pxemenu. """ Implemented by: Ole Holm Nielsen Here is the README: = PXE-utilities - This is a release of the SARA package of utilities that we use to boot our nodes with PXE-enabled network cards. This was developed because we always want to use the PXE-enabled network card as our first boot device. With pxelinux, which is a derivative of syslinux, you can specify with a PXE configuration file how the node must boot. This configuration is placed in, e.g. '/tftpboot/pxelinux.cfg' directory. The PXE-menu tools are used to control the booting of networked computers directly from the computer's console at the BIOS level before any operating system has been loaded. This is extremely useful for diagnostic purposes, or for selecting an operating system installation method, of an individual computer. For further information please read the files README-pxemenu and INSTALL-pxemenu. In our setup we have a default setup. The default setup is to boot from harddisk. When a node boots it fetches the default configuration file and the configuration file tells the node to boot from the harddisk. This setup is used for nodes that have already been installed by systemimager. At SARA we have developed the following strategy how to install a fresh node. 1) The ip-address in our setup is known for the new node. So we make a link in the '/tftpboot/pxelinux.cfg' directory to a pxe config file which tells that it has to fetch the kernel en root filesystem from our bootserver, eg: 0A000A02 ---> default.node_install (10.0.10.2) 2) The client starts and uses the systemimager software to install the node. The last line of installation script connects to a daemon on the bootserver. This daemon will remove the PXE config filefor this node. 3) The node reboots and will use the default pxe config file which will instruct the node to boot from harddisk. This release contains the following utilities: pxeconfigd) This is daemon that removes the pxe configuration file of a node. pxeconfig) With this program we can specify which pxe config file a node or nodes must use. This utility will create the links in '/tftpboot/pxelinux.cfg' hexls) Is a utility that diplays a directory, and, if in this directory contains HEX files, it will convert them to IP-numbers. All these utilities are written in Python. Comments or Suggestions mail them to: pxeconfig at sara dot nl http://www.sara.nl for more info about SARA. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] ANNOUNCE: New version of pxeconfig utilities (0.7.0)]
0.7.0: - Added default.memtest and default.flashqla as example how to use pxeconfig utilities for other purposes then for systemimager. - Added configure script (autoconf tools). - Replaced the debian build package system by a better one that uses the added configure script. It must now be easy to build also a rpm package. - Added a configuraton file pxeconfig.conf, eg to specify the location of pxe config directory. Closes ticket #3. - Removed the -d/--directory option for pxeconfig. It is replaced by the configuration file pxeconfig.conf (pxe_config_dir). == This version can be downloaded from: ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz Information, documentation and reporting bugs for the package: https://subtrac.sara.nl/oss/pxeconfig Here is the README: = PXE-utilities - This is a release of the SARA package of utilities that we use to boot our nodes with PXE-enabled network cards. This was developed because we always want to use the PXE-enabled network card as our first boot device. With pxelinux, which is a derivative of syslinux, you can specify with a PXE configuration file how the node must boot. This configuration is placed in, e.g. '/tftpboot/pxelinux.cfg' directory. In our setup we have a default setup. The default setup is to boot from harddisk. When a node boots it fetches the default configuration file and the configuration file tells the node to boot from the harddisk. This setup is used for nodes that have already been installed by systemimager. At SARA we have developed the following strategy how to install a fresh node. 1) The ip-address in our setup is known for the new node. So we make a link in the '/tftpboot/pxelinux.cfg' directory to a pxe config file which tells that it has to fetch the kernel en root filesystem from our bootserver, eg: 0A000A02 ---> default.node_install (10.0.10.2) 2) The client starts and uses the systemimager software to install the node. The last line of installation script connects to a daemon on the bootserver. This daemon will remove the PXE config filefor this node. 3) The node reboots and will use the default pxe config file which will instruct the node to boot from harddisk. This release contains the following utilities: pxeconfigd) This is daemon that removes the pxe configuration file of a node. pxeconfig) With this program we can specify which pxe config file a node or nodes must use. This utility will create the links in '/tftpboot/pxelinux.cfg' hexls) Is a utility that diplays a directory, and, if in this directory contains HEX files, it will convert them to IP-numbers. All these utilities are written in Python. Comments or Suggestions mail them to: Bas van der Vlies http://www.sara.nl for more info about SARA. -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - SF.net email is sponsored by: A Better Job is Waiting for You - Find it Now. Check out Slashdot's new job board. Browse through tons of technical jobs posted by companies looking to hire people just like you. http://jobs.slashdot.org/ ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=joi
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities (0.6.6)
0.6.6: - Fixed an error in postinst script for Debian. - Setup a wiki environment for documentation/tickets and source == This version can be downloaded from: ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz Information, documentation and reporting bugs for the package: https://subtrac.sara.nl/oss/pxeconfig Here is the README: = PXE-utilities - This is a release of the SARA package of utilities that we use to boot our nodes with PXE-enabled network cards. This was developed because we always want to use the PXE-enabled network card as our first boot device. With pxelinux, which is a derivative of syslinux, you can specify with a PXE configuration file how the node must boot. This configuration is placed in, e.g. '/tftpboot/pxelinux.cfg' directory. In our setup we have a default setup. The default setup is to boot from harddisk. When a node boots it fetches the default configuration file and the configuration file tells the node to boot from the harddisk. This setup is used for nodes that have already been installed by systemimager. At SARA we have developed the following strategy how to install a fresh node. 1) The ip-address in our setup is known for the new node. So we make a link in the '/tftpboot/pxelinux.cfg' directory to a pxe config file which tells that it has to fetch the kernel en root filesystem from our bootserver, eg: 0A000A02 ---> default.node_install (10.0.10.2) 2) The client starts and uses the systemimager software to install the node. The last line of installation script connects to a daemon on the bootserver. This daemon will remove the PXE config filefor this node. 3) The node reboots and will use the default pxe config file which will instruct the node to boot from harddisk. This release contains the following utilities: pxeconfigd) This is daemon that removes the pxe configuration file of a node. pxeconfig) With this program we can specify which pxe config file a node or nodes must use. This utility will create the links in '/tftpboot/pxelinux.cfg' hexls) Is a utility that diplays a directory, and, if in this directory contains HEX files, it will convert them to IP-numbers. All these utilities are written in Python. Comments or Suggestions mail them to: Bas van der Vlies http://www.sara.nl for more info about SARA. -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - SF.net email is sponsored by: A Better Job is Waiting for You - Find it Now. Check out Slashdot's new job board. Browse through tons of technical jobs posted by companies looking to hire people just like you. http://jobs.slashdot.org/ ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities (0.6.6)
0.6.6: - Fixed an error in postinst script for Debian. - Setup a wiki environment for documentation/tickets and source == This version can be downloaded from: ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz Information, documentation and reporting bugs for the package: https://subtrac.sara.nl/oss/pxeconfig Here is the README: = PXE-utilities - This is a release of the SARA package of utilities that we use to boot our nodes with PXE-enabled network cards. This was developed because we always want to use the PXE-enabled network card as our first boot device. With pxelinux, which is a derivative of syslinux, you can specify with a PXE configuration file how the node must boot. This configuration is placed in, e.g. '/tftpboot/pxelinux.cfg' directory. In our setup we have a default setup. The default setup is to boot from harddisk. When a node boots it fetches the default configuration file and the configuration file tells the node to boot from the harddisk. This setup is used for nodes that have already been installed by systemimager. At SARA we have developed the following strategy how to install a fresh node. 1) The ip-address in our setup is known for the new node. So we make a link in the '/tftpboot/pxelinux.cfg' directory to a pxe config file which tells that it has to fetch the kernel en root filesystem from our bootserver, eg: 0A000A02 ---> default.node_install (10.0.10.2) 2) The client starts and uses the systemimager software to install the node. The last line of installation script connects to a daemon on the bootserver. This daemon will remove the PXE config filefor this node. 3) The node reboots and will use the default pxe config file which will instruct the node to boot from harddisk. This release contains the following utilities: pxeconfigd) This is daemon that removes the pxe configuration file of a node. pxeconfig) With this program we can specify which pxe config file a node or nodes must use. This utility will create the links in '/tftpboot/pxelinux.cfg' hexls) Is a utility that diplays a directory, and, if in this directory contains HEX files, it will convert them to IP-numbers. All these utilities are written in Python. Comments or Suggestions mail them to: Bas van der Vlies http://www.sara.nl for more info about SARA. -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
0.6.4: - Fixed a bug in hexls with non resolving hostnames Reported by: Ole Holm Nielsen This version can be downloaded from: ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz Here is the README: = PXE-utilities - This is a release of the SARA package of utilities that we use to boot our nodes with PXE-enabled network cards. This was developed because we always want to use the PXE-enabled network card as our first boot device. With pxelinux, which is a derivative of syslinux, you can specify with a PXE configuration file how the node must boot. This configuration is placed in,e.g. '/tftpboot/pxelinux.cfg' directory. In our setup we have a default setup. The default setup is to boot from harddisk. When a node boots it fetches the default configuration file and the configuration file tells the node to boot from the harddisk. This setup is used for nodes that have already been installed by systemimager. At SARA we have developed the following strategy how to install a fresh node. 1) The ip-address in our setup is known for the new node. So we make a link in the '/tftpboot/pxelinux.cfg' directory to a pxe config file which tells that it has to fetch the kernel en root filesystem from our bootserver, eg: 0A000A02 ---> default.node_install (10.0.10.2) 2) The client starts and uses the systemimager software to install the node. The last line of installation script connects to a daemon on the bootserver. This daemon will remove the PXE config file for this node. 3) The node reboots and will use the default pxe config file which will instruct the node to boot from harddisk. This release contains the following utilities: pxeconfigd) This is daemon that removes the pxe configuration file of a node. pxeconfig) With this program we can specify which pxe config file a node or nodes must use. This utility will create the links in '/tftpboot/pxelinux.cfg' hexls) Is a utility that diplays a directory, and, if in this directory contains HEX files, it will convert them to IP-numbers. All these utilities are written in Python. Comments or Suggestions mail them to: Bas van der Vlies <[EMAIL PROTECTED]> http://www.sara.nl for more info about SARA. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
0.6.3: - Added hostname lookup feature to hexls. If succes it will display the HEX address, ip-number, hostname, eg: C0A811DD => 192.168.17.221 => gb-r13n5.irc.sara.nl This version can be downloaded from: ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz Here is the README: = PXE-utilities - This is a release of the SARA package of utilities that we use to boot our nodes with PXE-enabled network cards. This was developed because we always want to use the PXE-enabled network card as our first boot device. With pxelinux, which is a derivative of syslinux, you can specify with a PXE configuration file how the node must boot. This configuration is placed in,e.g. '/tftpboot/pxelinux.cfg' directory. In our setup we have a default setup. The default setup is to boot from harddisk. When a node boots it fetches the default configuration file and the configuration file tells the node to boot from the harddisk. This setup is used for nodes that have already been installed by systemimager. At SARA we have developed the following strategy how to install a fresh node. 1) The ip-address in our setup is known for the new node. So we make a link in the '/tftpboot/pxelinux.cfg' directory to a pxe config file which tells that it has to fetch the kernel en root filesystem from our bootserver, eg: 0A000A02 ---> default.node_install (10.0.10.2) 2) The client starts and uses the systemimager software to install the node. The last line of installation script connects to a daemon on the bootserver. This daemon will remove the PXE config file for this node. 3) The node reboots and will use the default pxe config file which will instruct the node to boot from harddisk. This release contains the following utilities: pxeconfigd) This is daemon that removes the pxe configuration file of a node. pxeconfig) With this program we can specify which pxe config file a node or nodes must use. This utility will create the links in '/tftpboot/pxelinux.cfg' hexls) Is a utility that diplays a directory, and, if in this directory contains HEX files, it will convert them to IP-numbers. All these utilities are written in Python. Comments or Suggestions mail them to: Bas van der Vlies <[EMAIL PROTECTED]> http://www.sara.nl for more info about SARA. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
0.6.2: - Fixed a bug in the non-interactive mode reported by and fixed by: Charles Galpin from defenderhosting.com This version can be downloaded from: ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz Here is the README: = PXE-utilities - This is a release of the SARA package of utilities that we use to boot our nodes with PXE-enabled network cards. This was developed because we always want to use the PXE-enabled network card as our first boot device. With pxelinux, which is a derivative of syslinux, you can specify with a PXE configuration file how the node must boot. This configuration is placed in,e.g. '/tftpboot/pxelinux.cfg' directory. In our setup we have a default setup. The default setup is to boot from harddisk. When a node boots it fetches the default configuration file and the configuration file tells the node to boot from the harddisk. This setup is used for nodes that have already been installed by systemimager. At SARA we have developed the following strategy how to install a fresh node. 1) The ip-address in our setup is known for the new node. So we make a link in the '/tftpboot/pxelinux.cfg' directory to a pxe config file which tells that it has to fetch the kernel en root filesystem from our bootserver, eg: 0A000A02 ---> default.node_install (10.0.10.2) 2) The client starts and uses the systemimager software to install the node. The last line of installation script connects to a daemon on the bootserver. This daemon will remove the PXE config file for this node. 3) The node reboots and will use the default pxe config file which will instruct the node to boot from harddisk. This release contains the following utilities: pxeconfigd) This is daemon that removes the pxe configuration file of a node. pxeconfig) With this program we can specify which pxe config file a node or nodes must use. This utility will create the links in '/tftpboot/pxelinux.cfg' hexls) Is a utility that diplays a directory, and, if in this directory contains HEX files, it will convert them to IP-numbers. All these utilities are written in Python. Comments or Suggestions mail them to: Bas van der Vlies <[EMAIL PROTECTED]> http://www.sara.nl for more info about SARA. --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
0.6.1: - Interactive mode did not work anymore. Fixed it by adding -i/--interactive command line options. Thanks to: Walter de Jong This version can be downloaded from: ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz Here is the README: = PXE-utilities - This is a release of the SARA package of utilities that we use to boot our nodes with PXE-enabled network cards. This was developed because we always want to use the PXE-enabled network card as our first boot device. With pxelinux, which is a derivative of syslinux, you can specify with a PXE configuration file how the node must boot. This configuration is placed in,e.g. '/tftpboot/pxelinux.cfg' directory. In our setup we have a default setup. The default setup is to boot from harddisk. When a node boots it fetches the default configuration file and the configuration file tells the node to boot from the harddisk. This setup is used for nodes that have already been installed by systemimager. At SARA we have developed the following strategy how to install a fresh node. 1) The ip-address in our setup is known for the new node. So we make a link in the '/tftpboot/pxelinux.cfg' directory to a pxe config file which tells that it has to fetch the kernel en root filesystem from our bootserver, eg: 0A000A02 ---> default.node_install (10.0.10.2) 2) The client starts and uses the systemimager software to install the node. The last line of installation script connects to a daemon on the bootserver. This daemon will remove the PXE config file for this node. 3) The node reboots and will use the default pxe config file which will instruct the node to boot from harddisk. This release contains the following utilities: pxeconfigd) This is daemon that removes the pxe configuration file of a node. pxeconfig) With this program we can specify which pxe config file a node or nodes must use. This utility will create the links in '/tftpboot/pxelinux.cfg' hexls) Is a utility that diplays a directory, and, if in this directory contains HEX files, it will convert them to IP-numbers. All these utilities are written in Python. Comments or Suggestions mail them to: Bas van der Vlies <[EMAIL PROTECTED]> http://www.sara.nl for more info about SARA. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
0.6: - Added -r|--remove option. Now it is possible to remove the pxe boot file, eg: pxeconfig --remove dummy.sara.nl Works also for the other options. This version can be downloaded from: ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz Here is the README: = PXE-utilities - This is a release of the SARA package of utilities that we use to boot our nodes with PXE-enabled network cards. This was developed because we always want to use the PXE-enabled network card as our first boot device. With pxelinux, which is a derivative of syslinux, you can specify with a PXE configuration file how the node must boot. This configuration is placed in,e.g. '/tftpboot/pxelinux.cfg' directory. In our setup we have a default setup. The default setup is to boot from harddisk. When a node boots it fetches the default configuration file and the configuration file tells the node to boot from the harddisk. This setup is used for nodes that have already been installed by systemimager. At SARA we have developed the following strategy how to install a fresh node. 1) The ip-address in our setup is known for the new node. So we make a link in the '/tftpboot/pxelinux.cfg' directory to a pxe config file which tells that it has to fetch the kernel en root filesystem from our bootserver, eg: 0A000A02 ---> default.node_install (10.0.10.2) 2) The client starts and uses the systemimager software to install the node. The last line of installation script connects to a daemon on the bootserver. This daemon will remove the PXE config file for this node. 3) The node reboots and will use the default pxe config file which will instruct the node to boot from harddisk. This release contains the following utilities: pxeconfigd) This is daemon that removes the pxe configuration file of a node. pxeconfig) With this program we can specify which pxe config file a node or nodes must use. This utility will create the links in '/tftpboot/pxelinux.cfg' hexls) Is a utility that diplays a directory, and, if in this directory contains HEX files, it will convert them to IP-numbers. All these utilities are written in Python. Comments or Suggestions mail them to: Bas van der Vlies <[EMAIL PROTECTED]> http://www.sara.nl for more info about SARA. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
0.5 - Added support for hostnames on the command line instead of network numbers, eg: pxeconfig -f default.node_install bas.ka.sara.nl walter.ka.sara.nl This version can be downloaded from: ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz Here is the README: = PXE-utilities - This is a release of the SARA package of utilities that we use to boot our nodes with PXE-enabled network cards. This was developed because we always want to use the PXE-enabled network card as our first boot device. With pxelinux, which is a derivative of syslinux, you can specify with a PXE configuration file how the node must boot. This configuration is placed in,e.g. '/tftpboot/pxelinux.cfg' directory. In our setup we have a default setup. The default setup is to boot from harddisk. When a node boots it fetches the default configuration file and the configuration file tells the node to boot from the harddisk. This setup is used for nodes that have already been installed by systemimager. At SARA we have developed the following strategy how to install a fresh node. 1) The ip-address in our setup is known for the new node. So we make a link in the '/tftpboot/pxelinux.cfg' directory to a pxe config file which tells that it has to fetch the kernel en root filesystem from our bootserver, eg: 0A000A02 ---> default.node_install (10.0.10.2) 2) The client starts and uses the systemimager software to install the node. The last line of installation script connects to a daemon on the bootserver. This daemon will remove the PXE config file for this node. 3) The node reboots and will use the default pxe config file which will instruct the node to boot from harddisk. This release contains the following utilities: pxeconfigd) This is daemon that removes the pxe configuration file of a node. pxeconfig) With this program we can specify which pxe config file a node or nodes must use. This utility will create the links in '/tftpboot/pxelinux.cfg' hexls) Is a utility that diplays a directory, and, if in this directory contains HEX files, it will convert them to IP-numbers. All these utilities are written in Python. Comments or Suggestions mail them to: Bas van der Vlies <[EMAIL PROTECTED]> http://www.sara.nl for more info about SARA. --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
0.4.4 - Updated documentation for xinetd support + example config - Added support for xinetd in the debian package scripts Implemented by: Ramon Bastiaans This version can be downloaded from: ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz Here is the README: = PXE-utilities - This is a release of the SARA package of utilities that we use to boot our nodes with PXE-enabled network cards. This was developed because we always want to use the PXE-enabled network card as our first boot device. With pxelinux, which is a derivative of syslinux, you can specify with a PXE configuration file how the node must boot. This configuration is placed in,e.g. '/tftpboot/pxelinux.cfg' directory. In our setup we have a default setup. The default setup is to boot from harddisk. When a node boots it fetches the default configuration file and the configuration file tells the node to boot from the harddisk. This setup is used for nodes that have already been installed by systemimager. At SARA we have developed the following strategy how to install a fresh node. 1) The ip-address in our setup is known for the new node. So we make a link in the '/tftpboot/pxelinux.cfg' directory to a pxe config file which tells that it has to fetch the kernel en root filesystem from our bootserver, eg: 0A000A02 ---> default.node_install (10.0.10.2) 2) The client starts and uses the systemimager software to install the node. The last line of installation script connects to a daemon on the bootserver. This daemon will remove the PXE config file for this node. 3) The node reboots and will use the default pxe config file which will instruct the node to boot from harddisk. This release contains the following utilities: pxeconfigd) This is daemon that removes the pxe configuration file of a node. pxeconfig) With this program we can specify which pxe config file a node or nodes must use. This utility will create the links in '/tftpboot/pxelinux.cfg' hexls) Is a utility that diplays a directory, and, if in this directory contains HEX files, it will convert them to IP-numbers. All these utilities are written in Python. Comments or Suggestions mail them to: Bas van der Vlies <[EMAIL PROTECTED]> http://www.sara.nl for more info about SARA. --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
Thanks for the notice, Bas! -Brian Thus spake Bas van der Vlies ([EMAIL PROTECTED]): 0.4.3 - Added make_deb_pkg.sh utility to make an DEBIAN package - changed port number to 6611 for pxeconfigd. Webmin is using the 1 port number. This version can be downloaded from: ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz Here is the README: = PXE-utilities - This is a release of the SARA package of utilities that we use to boot our nodes with PXE-enabled network cards. This was developed because we always want to use the PXE-enabled network card as our first boot device. With pxelinux, which is a derivative of syslinux, you can specify with a PXE configuration file how the node must boot. This configuration is placed in,e.g. '/tftpboot/pxelinux.cfg' directory. In our setup we have a default setup. The default setup is to boot from harddisk. When a node boots it fetches the default configuration file and the configuration file tells the node to boot from the harddisk. This setup is used for nodes that have already been installed by systemimager. At SARA we have developed the following strategy how to install a fresh node. 1) The ip-address in our setup is known for the new node. So we make a link in the '/tftpboot/pxelinux.cfg' directory to a pxe config file which tells that it has to fetch the kernel en root filesystem from our bootserver, eg: 0A000A02 ---> default.node_install (10.0.10.2) 2) The client starts and uses the systemimager software to install the node. The last line of installation script connects to a daemon on the bootserver. This daemon will remove the PXE config file for this node. 3) The node reboots and will use the default pxe config file which will instruct the node to boot from harddisk. This release contains the following utilities: pxeconfigd) This is daemon that removes the pxe configuration file of a node. pxeconfig) With this program we can specify which pxe config file a node or nodes must use. This utility will create the links in '/tftpboot/pxelinux.cfg' hexls) Is a utility that diplays a directory, and, if in this directory contains HEX files, it will convert them to IP-numbers. All these utilities are written in Python. Comments or Suggestions mail them to: Bas van der Vlies <[EMAIL PROTECTED]> http://www.sara.nl for more info about SARA. --- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users -- -- Brian Elliott Finley Argonne, MCS Division Mobile: 630.631.6621 Office: 630.252.4742 gpg --keyserver wwwkeys.pgp.net --recv-keys 10F8EE52 -- --- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
0.4.3 - Added make_deb_pkg.sh utility to make an DEBIAN package - changed port number to 6611 for pxeconfigd. Webmin is using the 1 port number. This version can be downloaded from: ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz Here is the README: = PXE-utilities - This is a release of the SARA package of utilities that we use to boot our nodes with PXE-enabled network cards. This was developed because we always want to use the PXE-enabled network card as our first boot device. With pxelinux, which is a derivative of syslinux, you can specify with a PXE configuration file how the node must boot. This configuration is placed in,e.g. '/tftpboot/pxelinux.cfg' directory. In our setup we have a default setup. The default setup is to boot from harddisk. When a node boots it fetches the default configuration file and the configuration file tells the node to boot from the harddisk. This setup is used for nodes that have already been installed by systemimager. At SARA we have developed the following strategy how to install a fresh node. 1) The ip-address in our setup is known for the new node. So we make a link in the '/tftpboot/pxelinux.cfg' directory to a pxe config file which tells that it has to fetch the kernel en root filesystem from our bootserver, eg: 0A000A02 ---> default.node_install (10.0.10.2) 2) The client starts and uses the systemimager software to install the node. The last line of installation script connects to a daemon on the bootserver. This daemon will remove the PXE config file for this node. 3) The node reboots and will use the default pxe config file which will instruct the node to boot from harddisk. This release contains the following utilities: pxeconfigd) This is daemon that removes the pxe configuration file of a node. pxeconfig) With this program we can specify which pxe config file a node or nodes must use. This utility will create the links in '/tftpboot/pxelinux.cfg' hexls) Is a utility that diplays a directory, and, if in this directory contains HEX files, it will convert them to IP-numbers. All these utilities are written in Python. Comments or Suggestions mail them to: Bas van der Vlies <[EMAIL PROTECTED]> http://www.sara.nl for more info about SARA. --- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
While we're extremely happy with the pxeconfig utilities for SI 2.X, I wonder why you would opt to use them with SI 3.X which has its own utilities for automatic installation. Would you care to describe the pros and cons of using either method with SI 3.X ? Bas van der Vlies <[EMAIL PROTECTED]> wrote: To: [EMAIL PROTECTED] Subject: [Sisuite-users] ANNOUNCE: New version of pxeconfig utilities 0.4.2 Minor change to pxeconfig/pxeconfigd utiltites. Added '-V/--version' flag for printing version info. Updated the INSTALL instructions. Howto use it for systemimager 3.X versions Ole Holm Nielsen Department of Physics, Technical University of Denmark, Building 307, DK-2800 Kongens Lyngby, Denmark --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
Ole Holm Nielsen wrote: While we're extremely happy with the pxeconfig utilities for SI 2.X, I wonder why you would opt to use them with SI 3.X which has its own utilities for automatic installation. Would you care to describe the pros and cons of using either method with SI 3.X ? Bas van der Vlies <[EMAIL PROTECTED]> wrote: To: [EMAIL PROTECTED] Subject: [Sisuite-users] ANNOUNCE: New version of pxeconfig utilities 0.4.2 Minor change to pxeconfig/pxeconfigd utiltites. Added '-V/--version' flag for printing version info. Updated the INSTALL instructions. Howto use it for systemimager 3.X versions First of all we are used to our own pxeconfig tools ;-) Here are the main differences between the systemimager 3 approach and ours: - ) In the systemimager 3 setup there is a link for every succesful installed host. If you have a huge cluster then there are a lot of links. Try to find which host did not installed properly or to reinstall a node you have to scan the directory and remove the link. - ) With our tools you can select which pxe config file to use, eg: install a node, boot from hardisk or perform a memtest ... with systemimager 3 there are two options install or boot from hardisk. - ) Our tools manage the pxelinux.cfg directory you can select what to do. In systemimager 3 there is automatic imstallation method, but there are no tools that manage the directory. You have to write your own tools to eg. remove the links. PS) I am also porting the tools to the IA64 platform. -- -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
0.4.2 Minor change to pxeconfig/pxeconfigd utiltites. Added '-V/--version' flag for printing version info. Updated the INSTALL instructions. Howto use it for systemimager 3.X versions This version can be downloaded from: ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz Here is the README: = PXE-utilities - This is a release of the SARA package of utilities that we use to boot our nodes with PXE-enabled network cards. This was developed because we always want to use the PXE-enabled network card as our first boot device. With pxelinux, which is a derivative of syslinux, you can specify with a PXE configuration file how the node must boot. This configuration is placed in, e.g. '/tftpboot/pxelinux.cfg' directory. In our setup we have a default setup. The default setup is to boot from harddisk. When a node boots it fetches the default configuration file and the configuration file tells the node to boot from the harddisk. This setup is used for nodes that have already been installed by systemimager. At SARA we have developed the following strategy how to install a fresh node. 1) The ip-address in our setup is known for the new node. So we make a link in the '/tftpboot/pxelinux.cfg' directory to a pxe config file which tells that it has to fetch the kernel en root filesystem from our bootserver, eg: 0A000A02 ---> default.node_install (10.0.10.2) 2) The client starts and uses the systemimager software to install the node. The last line of installation script connects to a daemon on the bootserver. This daemon will remove the PXE config file for this node. 3) The node reboots and will use the default pxe config file which will instruct the node to boot from harddisk. This release contains the following utilities: pxeconfigd) This is daemon that removes the pxe configuration file of a node. pxeconfig) With this program we can specify which pxe config file a node or nodes must use. This utility will create the links in '/tftpboot/pxelinux.cfg' hexls) Is a utility that diplays a directory, and, if in this directory contains HEX files, it will convert them to IP-numbers. All these utilities are written in Python. Comments or Suggestions mail them to: Bas van der Vlies <[EMAIL PROTECTED]> http://www.sara.nl for more info about SARA. -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
Bas van der Vlies wrote: First of all we are used to our own pxeconfig tools ;-) Here are the main differences between the systemimager 3 approach and ours: - ) In the systemimager 3 setup there is a link for every succesful installed host. If you have a huge cluster then there are a lot of links. Try to find which host did not installed properly or to reinstall a node you have to scan the directory and remove the link. Yes, I completely agree that the Systemimager 3.X design as you describe is clumsy and must be reversed into 1 link per host *to be installed*, and no links for properly working hosts. - ) With our tools you can select which pxe config file to use, eg: install a node, boot from hardisk or perform a memtest ... with systemimager 3 there are two options install or boot from hardisk. Yes, we need the ability to configure multiple PXE boot configurations. Besides node reinstall we're also happy to be able to PXE boot into the Memtest86 memory-tester, see details at http://www.fysik.dtu.dk/CAMP/Niflheim/diagnostics.html - ) Our tools manage the pxelinux.cfg directory you can select what to do. In systemimager 3 there is automatic imstallation method, but there are no tools that manage the directory. You have to write your own tools to eg. remove the links. Yes, the pxeconfig tool "hexls" is indeed useful for listing the hex-encoded IP-addresses in /tftpboot/pxelinux.cfg. My conclusion: The Systemimager 3 PXE-installation tool should be redesigned slightly so that it'll use the clever ideas of the pxeconfig package. I would certainly opt to use pxeconfig with Systemimager 3.X ! Ole Holm Nielsen Department of Physics, Technical University of Denmark, Building 307, DK-2800 Kongens Lyngby, Denmark --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
