DHCPD-UPDATE explained as far i know :-)

[nilakhya chatterjee]

dhcpd-update script is actually used to modify the values of ip pool
in the "dhcpd.conf" file located in the /etc/ltsp directory
particularly in case when we modify the ltspbr0 ip address ( address
of the ltsp server) in ifcfg-ltspbr0 (/etc/sysconfig/network-scripts/)

previously when we used eth0 device in case of a bridge device  the
administrator himself or with the ltsp-utils package set the ip of the
eth0 device which was constantly referenced for dhcpd.conf  file
modification suitable for ltsp server based processes.

now as the default dhcpd.conf & ifcfg-ltspbr0 file is bundled with
LTSP-SERVER distribution using the ip pool 172.31.100.0/24 along with
the default ip of 172.31.100.254 for the ltspbr0 device instead of
192.168.0.0/24  ip pool used previously. ltsp-server-initialise ,
dhcpd-update script was left unedited with the default pool still
192.168.0.0 /24 which creates the whole confusion.

either we dont touch the ltsp-server-initialize part and continue
doing manual /etc/export (nfs) and /etc/hosts configuration or we
carefully use the new updated dhcpd-update script,that also requires
the understanding of ltsp-server.conf and ifcfg-ltspbr0  files.

i think while not using the ltsp-server-initialize script makes us
more responsive in terms of creating all configurations , it also
somehow limits the customization of  ip pool we may use with the
bridge so the updated ltsp-server-initialise not only helps auto
configuration thats what nubies like, it actually helps customize our
server ip pool that we all administrators love.

thanks for writing warren
-------------- next part --------------
A non-text attachment was scrubbed...
Name: diff file dhcpd update
Type: application/octet-stream
Size: 1825 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/k12linux-devel-list/attachments/20080715/c3772c6c/attachment.obj>