From owner-freebsd-current@FreeBSD.ORG Fri Oct 1 03:41:46 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D67D106566C for ; Fri, 1 Oct 2010 03:41:46 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id ECFCB8FC21 for ; Fri, 1 Oct 2010 03:41:45 +0000 (UTC) Received: (qmail 31357 invoked by uid 399); 1 Oct 2010 03:41:44 -0000 Received: from localhost (HELO ?192.168.0.142?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 1 Oct 2010 03:41:44 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4CA55875.9060904@FreeBSD.org> Date: Thu, 30 Sep 2010 20:41:41 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: Garrett Cooper References: <20100929211253.GA1250@freebsd.org> <4CA3B393.8060206@icyb.net.ua> <4CA3BD7C.9080306@feral.com> <4CA4FC05.3020407@FreeBSD.org> <4CA5011D.8080804@FreeBSD.org> <4CA50283.4000601@FreeBSD.org> <4CA50363.2030500@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.2a1pre OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: letting glabel recognise a media change X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Oct 2010 03:41:46 -0000 On 9/30/2010 3:20 PM, Garrett Cooper wrote: > The problem is that the current system proposed for Device Kit is > based on file system notification. I know we can do this with kqueues > to some degree, but we do some of our best work via sysctls, and using > other methods of attack, so it would be nice if these were > `abstracted' out into generic events with OS specific callback > handlers. I'm not a kernel developer so I'm not going to tell anyone _how_ to implement the internals of this idea. My point is that if we're going to implement something that the API should be compatible so that all of the client software that already works with HAL doesn't have to be rewritten, patched, or abandoned. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/