From owner-freebsd-current@freebsd.org  Mon Oct 26 18:04:03 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 E7EA884F9
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Mon, 26 Oct 2015 18:04:03 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id C34E41790;
 Mon, 26 Oct 2015 18:04:03 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net
 [73.231.226.104])
 by bigwig.baldwin.cx (Postfix) with ESMTPSA id D43A3B94A;
 Mon, 26 Oct 2015 14:04:02 -0400 (EDT)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-current@freebsd.org
Cc: Adrian Chadd <adrian.chadd@gmail.com>, Lev Serebryakov <lev@freebsd.org>,
 NGie Cooper <yaneurabeya@gmail.com>
Subject: Re: What changed in rc.d infrastructure in last months?
Date: Mon, 26 Oct 2015 10:58:12 -0700
Message-ID: <10965004.5DFcuHMnDm@ralph.baldwin.cx>
User-Agent: KMail/4.14.3 (FreeBSD/10.2-PRERELEASE; KDE/4.14.3; amd64; ; )
In-Reply-To: <CAJ-VmomdSBD93dtnVfqNCc+NGknrcGsyW66_QeEcUMyHhPqmVA@mail.gmail.com>
References: <16610120144.20151025222025@serebryakov.spb.ru>
 <1648746569.20151026112745@serebryakov.spb.ru>
 <CAJ-VmomdSBD93dtnVfqNCc+NGknrcGsyW66_QeEcUMyHhPqmVA@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7
 (bigwig.baldwin.cx); Mon, 26 Oct 2015 14:04:02 -0400 (EDT)
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 18:04:04 -0000

On Monday, October 26, 2015 04:38:21 AM Adrian Chadd wrote:
> On 26 October 2015 at 01:27, Lev Serebryakov <lev@freebsd.org> wrote:=

> > 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=99=
s (even though
> >> ifconfig itself doesn=E2=80=99t support hostap =E2=80=94 only `wla=
nmode ap`). I don=E2=80=99t
> >  ifconfig doesn't support dhcp either, but dhclient is run via "DHC=
P" in
> >  `ficonfig_<foo>`
> >
> >> understand why it was done this way instead of just creating addit=
ional
> >> variables for `hostapd_<foo>`
> >  Long time ago there was simple `hostapd_enable` and `hostapd_inter=
faces` :)
> >  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
> This sounds like the same issue as double-running wpa_supplicant.
>=20
> I thought this was fixed already :( Would someone please figure out a=

> cleanish solution to this? I'd really appreciate it.

Note that /etc/pccard_ether bails right away if the interface is marked=
 up
without doing anything.  That is what is supposed to make devd events a=
t
boot get ignored.  (See the initial loop in pccard_ether_start().)

--=20
John Baldwin