Date: Mon, 26 Oct 2015 11:27:45 +0300 From: Lev Serebryakov <lev@FreeBSD.org> To: NGie Cooper <yaneurabeya@gmail.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: What changed in rc.d infrastructure in last months? Message-ID: <1648746569.20151026112745@serebryakov.spb.ru> In-Reply-To: <731AEB43-6519-4FC4-A115-E45FCFAE8F72@gmail.com> References: <16610120144.20151025222025@serebryakov.spb.ru> <DA78289A-176E-44EF-A2A2-1CEE10DF54ED@gmail.com> <28FF29D6-A2D9-46C0-A419-DB433BB9F54A@gmail.com> <606144753.20151025224636@serebryakov.spb.ru> <BDF13153-4947-49C4-8AD8-D6F82368563C@gmail.com> <562C2E44-DA31-450F-B867-607047697EFE@gmail.com> <731AEB43-6519-4FC4-A115-E45FCFAE8F72@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello NGie, Sunday, October 25, 2015, 11:09:03 PM, you wrote: > Ok, this is really not making sense from a design perspective. > `ifconfig_<foo>` is being overloaded for starting up hostap=E2=80=99s (ev= en though > ifconfig itself doesn=E2=80=99t support hostap =E2=80=94 only `wlanmode a= p`). I don=E2=80=99t ifconfig doesn't support dhcp either, but dhclient is run via "DHCP" in `ficonfig_<foo>` > understand why it was done this way instead of just creating additional > variables for `hostapd_<foo>` Long time ago there was simple `hostapd_enable` and `hostapd_interfaces` :) But it doesn't allow to automagically start hostapd for hotplugged (i.e. USB) interfaces. On the other hand, automatic DHCP on hot-plugged interfaces have sense and automatic hostapd doesn't, IMHO. --=20 Best regards, Lev mailto:lev@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1648746569.20151026112745>