From owner-freebsd-current@FreeBSD.ORG  Thu May 19 15:19:57 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 F257816A4CE
	for <current@FreeBSD.org>; Thu, 19 May 2005 15:19:56 +0000 (GMT)
Received: from harmony.village.org (rover.village.org [168.103.84.182])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F243D43D67
	for <current@FreeBSD.org>; Thu, 19 May 2005 15:19:55 +0000 (GMT)
	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.13.3/8.13.1) with ESMTP id j4JFIaoK073496;
	Thu, 19 May 2005 09:18:36 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Thu, 19 May 2005 09:18:49 -0600 (MDT)
Message-Id: <20050519.091849.115908750.imp@bsdimp.com>
To: nate@root.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <428C1EA6.7020907@root.org>
References: <428C1EA6.7020907@root.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
cc: fli+freebsd-current@shapeshifter.se
cc: current@FreeBSD.org
Subject: Re: Patch to make powerd(8) devd(8)-aware
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: Thu, 19 May 2005 15:19:57 -0000

In message: <428C1EA6.7020907@root.org>
            Nate Lawson <nate@root.org> writes:
: I appreciate you working on a patch for this.  However, I'd prefer the 
: work on the devd side go into making devctl a clonable device or follow 
: the bpf route and hook up /dev/devctl0,1,2,...  If you start using the 
: /var/run/devd.pipe, it's not available for other consumers.

Actually, you can have multiple devd.pipe consumers.  That's the whole
point of the devd.pipe: to allow as many people as desire the stream
of events from the kernel.  Making devctl clonable in the kernel is
more of a pita because you have one producer and many readers and all
the assoicated bookkeeping.

Warner