From owner-freebsd-questions@FreeBSD.ORG Thu Apr 29 21:05:24 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C1CB71065672 for ; Thu, 29 Apr 2010 21:05:24 +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 6FBE88FC19 for ; Thu, 29 Apr 2010 21:05:24 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id o3TL5NdA025918; Thu, 29 Apr 2010 15:05:23 -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 o3TL5NKJ025915; Thu, 29 Apr 2010 15:05:23 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Thu, 29 Apr 2010 15:05:23 -0600 (MDT) From: Warren Block To: David DEMELIER In-Reply-To: Message-ID: References: <20100428182223.GA34355@slackbox.erewhon.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-902635197-2034957245-1272574693=:25778" Content-ID: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (wonkity.com [127.0.0.1]); Thu, 29 Apr 2010 15:05:23 -0600 (MDT) Cc: Marco Beishuizen , freebsd-questions@freebsd.org Subject: Re: Using a scanner (USB) as user and not as root X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Apr 2010 21:05:24 -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-2034957245-1272574693=:25778 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-15; FORMAT=flowed Content-Transfer-Encoding: 8BIT Content-ID: On Thu, 29 Apr 2010, David DEMELIER wrote: > 2010/4/28 Warren Block : >> devfs.rules don't apply to devices that are created dynamically after >> boot-up.  Or I guess they might be if you reload the ruleset with applyset >> after the device is created, but devd is a lot more capable. >> > from devfs.rules(5) : > > NAME > devfs.rules ? devfs configuration information > > DESCRIPTION > The devfs.rules file provides an easy way to create and apply devfs(8) > rules, *even for devices that are not available at boot.* > > But devfs.rules is specially made for device not available at boot > such as usb keys. Apparently I was thinking of devfs.conf. But I have had difficulties with devfs.rules and USB devices. -Warren Block * Rapid City, South Dakota USA ---902635197-2034957245-1272574693=:25778--