Menu
▾
▴
sisuite-users
|
From: Bas v. d. V. <ba...@sa...> - 2010-10-29 12:57:31
|
4.0.2:
* Improved error handeling for AdvanceParser.py
Author: Dennis Stam
* debian/postinst. Use /bin/echo instead of echo else
wrong entry in /etc/services, closes #13
Author: Bodo MeiBner <bodo at bodo-m dot de>
Applied by: Bas van der Vlies
* debian/control. Fixed dependecies problems for pxeconfig
package. Added inetd | xinetd, closes #14
Author: Bodo MeiBner <bodo at bodo-m dot de>
Applied by: Bas van der Vlies
* pxemenu has been updated. See:
- INSTALL-pxemenu
- README-pxemenu
- Updates for SYSLINUX version 4.02.
- Some obsolete menus (UBC,Ghost) have been removed.
Author: Ole Holm Nielsen
* Added support for hosts that only can use mac address for
pxelinux configuration. This is used in environments
where dynamic ip's are used. To enable this you must set in
pxeconfig.conf:
[DEFAULT]
arp_command : /usr/sbin/arp -n
You can use host labels as shortcuts. Edit pxelinux.conf and add
for eg:
[bas]
mac_address: 00:19:b9:de:21:47
Now you can use:
'pxeconfig bas' instead of 'pxeconfig 00:19:b9:de:21:47'
You can mix hostnames and mac-addresses on the command line
Author: Bas van der Vlies
For more info about the package see the pxeconfig homepage:
* https://subtrac.sara.nl/oss/pxeconfig
You can download the latest release 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.
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 or sali.
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 or sali 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.
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: ba...@sa... *
* SARA - Academic Computing Services Amsterdam, The Netherlands *
********************************************************************
|
|
From: Bas v. d. V. <ba...@sa...> - 2012-08-22 12:56:10
Attachments:
smime.p7s
|
4.1.0:
* Added two new configuration options for pxeconfig.conf file: closes #17
- client_script_hook_add : The script that must be run when we create
a pxeconfig file for a host(s). This option
replaces client_script_hook.
- client_script_hook_remove : The script that must be run when we remove
a pxeconfig file for a host(s)
Both options are useful for firewall setups. To open/close ports.
Reported by: Ramon Bastiaans (SARA)
Fixed by: Bas van der Vlies
=====================================================================
For more info about the package see the pxeconfig homepage:
* https://subtrac.sara.nl/oss/pxeconfig
You can download the latest release 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.
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 or sali.
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 or sali 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.
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: ba...@sa... *
* SARA - Academic Computing Services Amsterdam, The Netherlands *
********************************************************************
------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
sisuite-users mailing list
sis...@li...
https://lists.sourceforge.net/lists/listinfo/sisuite-users
|
Thanks for helping keep SourceForge clean.
X