From owner-freebsd-current Sun Mar 3 12:23:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id BAB1337B41A for ; Sun, 3 Mar 2002 12:23:22 -0800 (PST) Received: from hamilton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 3 Mar 2002 20:23:22 +0000 (GMT) To: Poul-Henning Kamp Cc: cjclark@alum.mit.edu, current@FreeBSD.ORG Subject: Re: devfs(5) Permissions In-reply-to: Your message of "Sun, 03 Mar 2002 21:16:59 +0100." <25568.1015186619@critter.freebsd.dk> X-Request-Do: Date: Sun, 03 Mar 2002 20:23:21 +0000 From: David Malone Message-ID: <200203032023.aa92755@salmon.maths.tcd.ie> 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 > >Do you have any designs for this ruleset stuff? From what you said > >at BSDconEurope it will have to be fairly complicated to achieve > >the your aim of being better than a static permission for a given > >device. > 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". I presume you'd push the rules in using sysclt or did you have something more filesystem like in mind? > >Otherwise, one option would just be to have devfs check for a file > >in the /dev directory it is mounted over and then use that files > >permissions as a default. That would at least get us back the > >features of the old /dev which we're missing now. > This is much harder than you think... I didn't for a moment think it might be easy ;-) David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message