From owner-freebsd-current Sun Apr 21 3:25:56 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id D790037B416 for ; Sun, 21 Apr 2002 03:25:50 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id UAA13463; Sun, 21 Apr 2002 20:25:44 +1000 Date: Sun, 21 Apr 2002 20:26:29 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Craig Boston Cc: current@FreeBSD.ORG Subject: Re: Adding a 'bpf' group for /dev/bpf* In-Reply-To: <014601c1e8e8$8defe350$5f45a8c0@auir.gank.org> Message-ID: <20020421201257.L579-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Sat, 20 Apr 2002, Craig Boston wrote: > Since -current by default uses devfs, is there a standard way to make the > ownership/permissions of device nodes "sticky" so that they persist across > boots? No. Or should we just put the appropriate commands in rc.local ? The problem has been moved to putting them in devfs. > Besides bpf, this would be useful, for example, for people who want to > change permissions on cd-rom devices to 644 so that non-root users can make > iso images (or give a special group cd burner rights). I think you mean mode 660. acd devices already have the insecure permissions 644 in devfs. These are even more insecure than they should be, since read permission is enough to do most ioctls. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message