From owner-p4-projects@FreeBSD.ORG Thu Feb 1 15:37:07 2007 Return-Path: X-Original-To: p4-projects@freebsd.org Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 5E0F016A408; Thu, 1 Feb 2007 15:37:07 +0000 (UTC) X-Original-To: perforce@FreeBSD.org Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1FC3416A400; Thu, 1 Feb 2007 15:37:07 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id AE94913C4B3; Thu, 1 Feb 2007 15:37:06 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l11FX8Qc060852; Thu, 1 Feb 2007 08:33:08 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 01 Feb 2007 08:33:37 -0700 (MST) Message-Id: <20070201.083337.1645217922.imp@bsdimp.com> To: rwatson@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <20070201133157.X12827@fledge.watson.org> References: <200702010631.l116VFBJ006811@repoman.freebsd.org> <20070201133157.X12827@fledge.watson.org> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 01 Feb 2007 08:33:08 -0700 (MST) Cc: perforce@FreeBSD.org Subject: Re: PERFORCE change 113809 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2007 15:37:07 -0000 In message: <20070201133157.X12827@fledge.watson.org> Robert Watson writes: : : On Thu, 1 Feb 2007, Warner Losh wrote: : : > http://perforce.freebsd.org/chv.cgi?CH=113809 : > : > Change 113809 by imp@imp_lighthouse on 2007/02/01 06:30:17 : > : > Kinky new idea: run pccard_ether in the background. This allows devd : > to respond to things that are happening while pccard_ether is running. : : Hmm. Perhaps it would be better to serialize all events associated with a : particular device in a particular process or thread, so that events from ed0 : and ed1 can run concurrently, but not two events for ed0? I realize that's : quite a bit more complicated than slapping '&' in there, but it might provide : some useful consistency from the perspective of people writing scripts to : start and stop file systems, etc, on removable storage (for example). I'm pretty sure that devd isn't the place for this. Such cooridnation are best done with the scripts that do the configuration. How does devd know to enforce this? Only one fs at a time can run? Only one device + unit? Only one device? If there are issues, then things like pccard_ether will need to get smarter about them. I'm sure there will be issues with link UP/DOWN events. Warner : Robert N M Watson : Computer Laboratory : University of Cambridge : : > : > Affected files ... : > : > .. //depot/projects/arm/src/etc/devd.conf#2 edit : > : > Differences ... : > : > ==== //depot/projects/arm/src/etc/devd.conf#2 (text+ko) ==== : > : > @@ -34,13 +34,13 @@ : > notify 0 { : > match "system" "IFNET"; : > match "type" "ATTACH"; : > - action "/etc/pccard_ether $subsystem start"; : > + action "/etc/pccard_ether $subsystem start &"; : > }; : > : > notify 0 { : > match "system" "IFNET"; : > match "type" "DETACH"; : > - action "/etc/pccard_ether $subsystem stop"; : > + action "/etc/pccard_ether $subsystem stop &"; : > }; : > : > # : > @@ -63,11 +63,11 @@ : > # : > detach 0 { : > media-type "802.11"; : > - action "/etc/pccard_ether $device-name stop"; : > + action "/etc/pccard_ether $device-name stop &"; : > }; : > attach 0 { : > media-type "802.11"; : > - action "/etc/pccard_ether $device-name start"; : > + action "/etc/pccard_ether $device-name start &"; : > }; : > notify 0 { : > match "system" "IFNET"; : > :