From owner-freebsd-current@FreeBSD.ORG  Sun Oct 25 03:19:44 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 31255106566B
	for <current@freebsd.org>; Sun, 25 Oct 2009 03:19:44 +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 E3C8F8FC0A
	for <current@freebsd.org>; Sun, 25 Oct 2009 03:19:43 +0000 (UTC)
Received: from wonkity.com (localhost [127.0.0.1])
	by wonkity.com (8.14.3/8.14.3) with ESMTP id n9P3JdD9024186;
	Sat, 24 Oct 2009 21:19:39 -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 n9P3JdId024183;
	Sat, 24 Oct 2009 21:19:39 -0600 (MDT)
	(envelope-from wblock@wonkity.com)
Date: Sat, 24 Oct 2009 21:19:39 -0600 (MDT)
From: Warren Block <wblock@wonkity.com>
To: Justin Hibbits <jrh29@alumni.cwru.edu>
In-Reply-To: <fd9cd3450910241907k5661e1b3jfdcf6f59d73a4e5f@mail.gmail.com>
Message-ID: <alpine.BSF.2.00.0910242102400.24135@wonkity.com>
References: <alpine.BSF.2.00.0910241934310.23784@wonkity.com>
	<fd9cd3450910241907k5661e1b3jfdcf6f59d73a4e5f@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2
	(wonkity.com [127.0.0.1]); Sat, 24 Oct 2009 21:19:39 -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
	<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: Sun, 25 Oct 2009 03:19:44 -0000

On Sat, 24 Oct 2009, Justin Hibbits wrote:

> On Sat, Oct 24, 2009 at 10:00 PM, Warren Block <wblock@wonkity.com> 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.
>>
>> The specific example is for scanners.  My scanner is ugen2.3, but only as
>> long as it is plugged into the same USB hub/port each time.  I can manually
>> create a uscanner0 link in /dev with devd.conf:
>>
>> attach 20 {
>>        device-name "ugen[0-9]+";
>>        match "vendor" "0x04b8";
>>        match "product" "0x010a";
>>        action "/bin/ln -sf /dev/$device-name /dev/uscanner0; /sbin/devfs
>> rule applyset";
>> };
>>
>> Using /dev/uscanner0 then works in place of ugen2.3.
>>
>> Now the second part of the example: I want devd to recognize the attach or
>> creation of uscanner0.  But it's not a true devfs device; devd doesn't see
>> an attach event, or a notify CDEV/CREATE event.
>>
>> Is there a method to create a true devfs link to a dynamic device?
>
> Check devfs.rules(5)

I did, but maybe missed the relevant information.  There are conditions 
to match and modify (perm/owner) a node, but none to create or delete 
one.  Maybe something with unhide?  Could you post an example?

-Warren Block * Rapid City, South Dakota USA