From owner-freebsd-current Sun Mar 3 12:26:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 674B637B405 for ; Sun, 3 Mar 2002 12:26:23 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g23KQBLv027343; Sun, 3 Mar 2002 21:26:11 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: David Malone Cc: cjclark@alum.mit.edu, current@FreeBSD.ORG Subject: Re: devfs(5) Permissions In-Reply-To: Your message of "Sun, 03 Mar 2002 20:23:21 GMT." <200203032023.aa92755@salmon.maths.tcd.ie> Date: Sun, 03 Mar 2002 21:26:11 +0100 Message-ID: <27342.1015187171@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200203032023.aa92755@salmon.maths.tcd.ie>, David Malone writes: >> Not really, the basic idea is just a linked list of rules: > >> name=="/dev/uscanner*" -> chmod 0644 >> driver=="bpf" -> chown user > >> It's not too much work, I just havn't had the time for it yet. >> (Junior Kernel Hackers can apply here :-) > >OK - I thought you had something much more complex in mind after >your example: "plugging the nuclear reactor into the serial port >where you had a a modem plugged in yesterday". No, that was to show why "persistence" is a bad idea. >I presume you'd push the rules in using sysclt or did you have >something more filesystem like in mind? Nope, just a sysctl. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message