From owner-freebsd-current@FreeBSD.ORG  Tue Jan 25 17:11:07 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 158A016A4F0; Tue, 25 Jan 2005 17:11:07 +0000 (GMT)
Received: from harmony.village.org (rover.village.org [168.103.84.182])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 8E43943D58; Tue, 25 Jan 2005 17:11:06 +0000 (GMT)
	(envelope-from imp@harmony.village.org)
Received: from localhost (localhost [IPv6:::1])
	by harmony.village.org (8.13.1/8.13.1) with ESMTP id j0PHALi0053467;
	Tue, 25 Jan 2005 10:10:21 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Date: Tue, 25 Jan 2005 10:10:21 -0700 (MST)
Message-Id: <20050125.101021.41686898.imp@harmony.village.org>
To: rwatson@FreeBSD.org
From: Warner Losh <imp@harmony.village.org>
In-Reply-To: <Pine.NEB.3.96L.1050125170138.3036H-100000@fledge.watson.org>
References: <20050125.095536.104086303.imp@harmony.village.org>
	<Pine.NEB.3.96L.1050125170138.3036H-100000@fledge.watson.org>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 26 Jan 2005 13:11:07 +0000
cc: pete@altadena.net
cc: imp@rover.village.org
cc: phk@phk.freebsd.dk
cc: current@FreeBSD.org
cc: imp@bsdimp.com
Subject: Re: Devd event from GEOM? 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jan 2005 17:11:07 -0000

> It depends a bit on where we sit: we probably want a neteventd that knows
> about this sort of thing and performs unified network interface
> management.  In the mean time, I just want dhclient launched, because
> dhclient already knows about ssid's, link state, etc. 

We don't neet yet another daemon around for that.

> The idea behind the class information is that the application can use a
> combination of the class, name, configuration data, and direct
> communication with the object to do useful things.  However, to
> communicate with an object today, you first need the class information,
> which is why you want it early as part of the event notification.

Right now we can't even get the class information out of the userland
interfaces we have.  We should correct that problem, rather than
complicate things prematurely because it is expedient to do so today.

Warner