On Fri, 10 Sep 2010 21:06:45 +0200 Julien Laffaye <kimelto_at_gmail.com> wrote: > On Fri, Sep 10, 2010 at 8:36 PM, Doug Barton <dougb_at_freebsd.org> wrote: > > As I've said many times, I'm ready to have it out when there is consensus to > > do so. The usual discussion goes like this: > > > > 1. Get BIND out of the base! > > 2. If we remove it, the command line tools (dig, host, nslookup) go with it. > > DragonflyBSD chose to remove BIND and to use drill as a replacement [1]. > Don't know if it meet our requirements, though. > > [1]: http://leaf.dragonflybsd.org/mailarchive/submit/2010-03/msg00003.html > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" Hi, another argument about hostapd :) if have access point we must have way to assign IP for AP clients. Last spring I made firmware based on FreeBSD for router with only 4MB NOR flash (D-Link DIR-320). Since this device is router I must be able to serve DHCP. And current implementation of dhcpclient, that we have, is same isc-dhcp, and I replace system dhcpclient with ports one+dhcpd but with small patch that put basic dhcp utils onto libdhcp.so. So: 1. We already have code for libdhcp in base. 2. We already use isc-dhcp as dhcpclient. 3. We already build small-size embedded routers firmware with DHCP server. 4. We have hostap and other router/AP functionality. So why not include dhcpd in base now? -- Aleksandr Rybalko <ray_at_ddteam.net>Received on Fri Sep 10 2010 - 19:19:28 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:07 UTC