From owner-freebsd-current@FreeBSD.ORG Thu Sep 15 03:35:55 2005 Return-Path: X-Original-To: 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 0369116A41F for ; Thu, 15 Sep 2005 03:35:55 +0000 (GMT) (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 2707A43D6B for ; Thu, 15 Sep 2005 03:35:48 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j8F3YLXY026282; Wed, 14 Sep 2005 21:34:23 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 14 Sep 2005 21:34:29 -0600 (MDT) Message-Id: <20050914.213429.44985299.imp@bsdimp.com> To: Kirk.Davis@epsb.ca From: "M. Warner Losh" In-Reply-To: <04C71268DFDAA8499EC1A248A44B6A2B34C132@Exchange21.EDU.epsb.ca> References: <04C71268DFDAA8499EC1A248A44B6A2B34C132@Exchange21.EDU.epsb.ca> 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-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 14 Sep 2005 21:34:31 -0600 (MDT) Cc: freebsd-current@freebsd.org Subject: Re: Using devd to automate wireless | wired network connections 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: Thu, 15 Sep 2005 03:35:55 -0000 In message: <04C71268DFDAA8499EC1A248A44B6A2B34C132@Exchange21.EDU.epsb.ca> Kirk Davis writes: : : : > -----Original Message----- : > From: owner-freebsd-current@freebsd.org : > [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Brooks Davis : > Sent: September 14, 2005 9:54 AM : > To: Jochen Gensch : > Cc: freebsd-current@freebsd.org : > Subject: Re: Using devd to automate wireless | wired network : > connections : > : > On Wed, Sep 14, 2005 at 11:54:45AM +0200, Jochen Gensch wrote: : > > Am Mittwoch 14 September 2005 02:41 schrieben Sie: : > > : > > > Have you tried those changes? If so, are your devices : > > > actually generating media events? If not, that has to be : > fixed and : > > > that's a kernel issue. : > > : : Is there any diagnostic tools that can show the messages that get passed : from the kernel to devd? devd republishes everything it gets via /var/run/devd.pipe. : I have though of some other uses for devd where I : would like to run a script on a device up/down or new device insert but I'm : not sure if there is an event sent to devd for that. *ALL* devices that are added to or removed from the system get a devd event. It isn't like other systems where you have to add support to each bus. : It would be nice to : have a tool that would show if devd was getting an even for that device. : This might also help show the devices that do not yet generate media events. Many don't, that's true :-(. Warner