On 03/09/2010 08:05:17 AM, David Sommerseth wrote:
> On the other hand, ./configure
> could try to detect which DHCP client the system got and could use
> that
> as a default client to kick off.
I think this might cause more problems than it solves because
there's no guarantee that build hosts will have the same,
or any, dhcp client that is ultimately used. I'm with
Peter Stuge regarding being able to support a choice
of clients, and having the wrong default in place can
just complicate things.
Maybe what makes the most sense from a package
management standpoint is to have the package installation
process autodetect the existing dhcp client so that whatever
the user has installed will be used (once the feature
is turned on with --route-gateway.) I'm not sure how
to best facilitate this with OpenVPN. Perhaps OpenVPN
should default to using something like
/etc/openvpn/route-gateway-dhcp-client and then
package installation can softlink that to whatever
dhcp client is installed.
Over-automating things will cause people headaches.
You don't want to willy-nilly startup a dhcp client
and have all your interfaces configured with dhcp without
your consent.
Karl <k...@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
