Roy Marples
2008-04-23 08:29:40 UTC
And hopefully the last!
http://roy.marples.name/dhcpcd/dhcpcd-4.0.0-alpha2.tar.bz2
Changes from alpha1
dhcpcd.sh is now looking slick and minimal.
ntp, nis and hostname lookup have been moved into example hook scripts.
dhcpcd.conf is now installed by default to request everything dhcpcd.sh needs,
and ntp-servers also.
classless_static_routes="1.2.3.4/8 5.6.7.8/16" is now exported to the script.
dhcpcd.sh and dhcpcd.conf now have man pages.
The last thing todo is decide on the following
Do we want per interface conigs in dhcpcd.conf? If so provide an example.
We currently trim leading and trailing whitespace in dhcpcd.conf. Should we
provide a complex mechanism to allow spaces at the start/end of values?
If the hostname is an FQDN (foo.bar.com) should we transmit it as such by
default?
Thanks
Roy
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
http://roy.marples.name/dhcpcd/dhcpcd-4.0.0-alpha2.tar.bz2
Changes from alpha1
dhcpcd.sh is now looking slick and minimal.
ntp, nis and hostname lookup have been moved into example hook scripts.
dhcpcd.conf is now installed by default to request everything dhcpcd.sh needs,
and ntp-servers also.
classless_static_routes="1.2.3.4/8 5.6.7.8/16" is now exported to the script.
dhcpcd.sh and dhcpcd.conf now have man pages.
The last thing todo is decide on the following
Do we want per interface conigs in dhcpcd.conf? If so provide an example.
We currently trim leading and trailing whitespace in dhcpcd.conf. Should we
provide a complex mechanism to allow spaces at the start/end of values?
If the hostname is an FQDN (foo.bar.com) should we transmit it as such by
default?
Thanks
Roy
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de