From owner-freebsd-mobile@FreeBSD.ORG Mon Sep 27 18:56:35 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA51B16A4CE for ; Mon, 27 Sep 2004 18:56:35 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id A099B43D31 for ; Mon, 27 Sep 2004 18:56:35 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 21986 invoked from network); 27 Sep 2004 18:56:35 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 27 Sep 2004 18:56:33 -0000 Received: from [10.50.40.210] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i8RIsVY6014057; Mon, 27 Sep 2004 14:56:21 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-mobile@FreeBSD.org Date: Mon, 27 Sep 2004 12:55:26 -0400 User-Agent: KMail/1.6.2 References: <415720FD.8080603@samsco.org> <200409271053.47904.jhb@FreeBSD.org> <41583D40.3030008@gmx.de> In-Reply-To: <41583D40.3030008@gmx.de> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200409271255.26828.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Jochen Gensch Subject: Re: FreeBSD 5.3-BETA6 available X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Sep 2004 18:56:35 -0000 On Monday 27 September 2004 12:18 pm, Jochen Gensch wrote: > John Baldwin wrote: > > You need to use persistent devfs rules rather than the one-time boot fix > > that devfs.conf does to get the devfs permissions you want/need. > > Could you tell where to find information about that? devfs(8) and (5) > don't help me very much with this. Err, the third paragraph and beyond are all about rules. DEVFS(8) FreeBSD System Manager's Manual DEVFS(8) NAME devfs -- DEVFS control SYNOPSIS devfs [-m mount-point] keyword argument ... DESCRIPTION The devfs utility provides an interface to manipulate properties of devfs(5) mounts. The keyword argument determines the context for the rest of the argu- ments. For example, most of the commands related to the rule subsystem must be preceded by the rule keyword. The following flags are common to all keywords: -m mount-point Operate on mount-point, which is expected to be a devfs(5) mount. If this option is not specified, devfs operates on /dev. Rule Subsystem The devfs(5) rule subsystem provides a way for the administrator of a system to control the attributes of DEVFS nodes. Each DEVFS mount-point has a ``ruleset'', or a list of rules, associated with it. When a device driver creates a new node, all the rules in the ruleset associated with each mount-point are applied (see below) before the node becomes visible to the userland. This permits the administrator to change the proper- ties, including the visibility, of certain nodes. For example, one might want to hide all disk nodes in a jail(2)'s /dev. As far as having these actions done automatically on boot, look at the /etc/defaults/devfs.rules file. You can make a custom one in /etc. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org