From owner-freebsd-current@freebsd.org  Mon Oct 26 08:27:57 2015
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51563846D
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Mon, 26 Oct 2015 08:27:57 +0000 (UTC) (envelope-from lev@FreeBSD.org)
Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru
 [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 172011E9F
 for <freebsd-current@freebsd.org>; Mon, 26 Oct 2015 08:27:57 +0000 (UTC)
 (envelope-from lev@FreeBSD.org)
Received: from lion.home.serebryakov.spb.ru (unknown
 [IPv6:2001:470:923f:1:3c23:bcdc:5292:fa5f])
 (Authenticated sender: lev@serebryakov.spb.ru)
 by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 7A9832D68;
 Mon, 26 Oct 2015 11:27:48 +0300 (MSK)
Date: Mon, 26 Oct 2015 11:27:45 +0300
From: Lev Serebryakov <lev@FreeBSD.org>
Reply-To: lev@FreeBSD.org
Organization: FreeBSD
X-Priority: 3 (Normal)
Message-ID: <1648746569.20151026112745@serebryakov.spb.ru>
To: NGie Cooper <yaneurabeya@gmail.com>
CC: freebsd-current <freebsd-current@freebsd.org>
Subject: Re: What changed in rc.d infrastructure in last months?
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2015 08:27:57 -0000

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