From owner-freebsd-current@FreeBSD.ORG Sun Oct 25 03:52:32 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DECF9106568B for ; Sun, 25 Oct 2009 03:52:32 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 992CB8FC18 for ; Sun, 25 Oct 2009 03:52:32 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id n9P3qV5g024302; Sat, 24 Oct 2009 21:52:31 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id n9P3qUUK024299; Sat, 24 Oct 2009 21:52:31 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sat, 24 Oct 2009 21:52:30 -0600 (MDT) From: Warren Block To: Justin Hibbits In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-902635197-712873081-1256442751=:24264" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (wonkity.com [127.0.0.1]); Sat, 24 Oct 2009 21:52:31 -0600 (MDT) Cc: current@freebsd.org Subject: Re: Creating /dev links to dynamic devices 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: Sun, 25 Oct 2009 03:52:33 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---902635197-712873081-1256442751=:24264 Content-Type: TEXT/PLAIN; format=flowed; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT On Sat, 24 Oct 2009, Justin Hibbits wrote: > On Sat, Oct 24, 2009 at 11:19 PM, Warren Block wrote: > On Sat, 24 Oct 2009, Justin Hibbits wrote: > > On Sat, Oct 24, 2009 at 10:00 PM, Warren Block wrote: > > devfs.conf allows creating static device links: > > link    acd0    cdrom > > This only runs on devfs startup, so it's useless for creating a link to a > dynamic device. > > I guess I misread your original post.  Why do you want to add actions based on the creation of the uscanner node?  In this case, so I can run scanbuttond on creation of uscanner0. Yes, that could be done on detection of the vendor and product IDs and using the ugen device for this example. But it seems to show that either the ability to dynamically create "static device links" isn't there, or I just haven't found it yet. -Warren Block * Rapid City, South Dakota USA ---902635197-712873081-1256442751=:24264--