[PATCH 3/5] -m <ifname_match> matches interface names via fnmatch(3) and assigns them the default configuration file, like so

Roy Marples roy
Wed May 27 17:50:37 PDT 2009

Sam Leffler wrote:
> FWIW FreeBSD has support in the base system for dealing with hotplug
> devices and all our efforts have been to move away from applications
> growing this sort of functionality.  IMO this is the wrong approach to
> the problem (for BSD at least).

I disagree as it makes replacing a component with an alternative a non
trival task.

Let us take dhclient as an example - it's included in the base FreeBSD
install. Now, how can I replace dhclient with dhcpcd [1]? I not only
have to enable dhcpcd in rc.conf, but I also have to alter other system
scripts and files. Is the user expected to be a programmer for such a
simple task?

In NetBSD you have the choice - enable dhclient or dhcpcd in rc.conf. No
more action should be needed, and I'd like to see the same flexibility
in wpa_supplicant.

IMO FreeBSD has the wrong approach because it entwines programs such
they cannot easily be changed out with alternatives, whether the
alternatives be better or worse.



More information about the Hostap mailing list