From owner-freebsd-questions@FreeBSD.ORG Wed Jun 25 11:49:22 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39CCD37B401 for ; Wed, 25 Jun 2003 11:49:22 -0700 (PDT) Received: from zeus.acuson.com (ac17860.acuson.com [157.226.71.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C0D243FFD for ; Wed, 25 Jun 2003 11:49:21 -0700 (PDT) (envelope-from DavidJohnson@Siemens.com) Received: from mvaexch02 ([157.226.230.209]:1215 helo=mvaexch02.acuson.com) by zeus.acuson.com with esmtp (Exim 4.14) id 19VFKX-0004UB-3K for freebsd-questions@freebsd.org; Wed, 25 Jun 2003 11:49:17 -0700 Received: by mvaexch02.acuson.com with Internet Mail Service (5.5.2653.19) id ; Wed, 25 Jun 2003 11:36:35 -0700 Received: from dhcp-46-117.acuson.com ([157.226.46.117]) by mvaexch01.acuson.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id NQS4NZFM; Wed, 25 Jun 2003 11:37:44 -0700 From: Johnson David To: freebsd-questions@freebsd.org Organization: Siemens Medical Systems Date: Wed, 25 Jun 2003 11:48:31 -0700 User-Agent: KMail/1.5.2 MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200306251148.31504.DavidJohnson@Siemens.com> X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *19VFKX-0004UB-3K*7jkf60SEfDM* X-SA-Exim-Rcpt-To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-99.1 required=2.0 tests=AWL,BAYES_20,USER_AGENT_KMAIL,USER_IN_WHITELIST version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-SA-Exim-Scanned: Yes Subject: devfs and umass devices X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2003 18:49:22 -0000 I just upgraded to 5.1-RELEASE last night. I have a Jungsoft Nexdisk USB memory stick that is being successfully recognized. Since I want the memory stick to be usable by users of group operator, I need the /dev/da0s1 device to be mode 0664. Then they can mount the device on one of their own directories (via vfs.usermount=1). Under 5.0, I used rc.devfs to add a ruleset to devfs using the following commands. This worked fine: ruleset 99 rule add path da0s1 mode 664 rule -s 99 applyset Under 5.1 I tried doing a similar action with devfs.conf: perm da0s1 0664 This does not work, and after looking over rc.d/devfs, I realized that this only works for devices present at boot time, and not for umass devices inserted later. Is there an accepted means of adding a ruleset using the new rc system? Is there another way of doing what I want? I understand that rc.devfs is deprecated, so I don't really want to use it unless I have to. Thanks, David