From owner-freebsd-current Sat Apr 20 15: 2:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [216.123.203.186]) by hub.freebsd.org (Postfix) with ESMTP id B7F4E37B417; Sat, 20 Apr 2002 15:02:13 -0700 (PDT) Received: from orthanc.ab.ca (localhost.orthanc.ab.ca [127.0.0.1]) by orthanc.ab.ca (8.11.6/8.11.6) with ESMTP id g3KM2DJ93468; Sat, 20 Apr 2002 16:02:13 -0600 (MDT) (envelope-from lyndon@orthanc.ab.ca) Message-Id: <200204202202.g3KM2DJ93468@orthanc.ab.ca> From: Lyndon Nerenberg Organization: The Frobozz Magic Homing Pigeon Company To: "Crist J. Clark" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Adding a 'bpf' group for /dev/bpf* In-reply-to: Your message of "Sat, 20 Apr 2002 14:51:39 PDT." <20020420145139.D76898@blossom.cjclark.org> X-Mailer: mh-e 5.0.92; MH 6.8.4; Emacs 21.1 Date: Sat, 20 Apr 2002 16:02:13 -0600 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 >>>>> "Crist" == Crist J Clark writes: Crist> I do this a lot too on systems where it makes sense. But I'm Crist> not sure I understand what you are asking to be done. Is it Crist> asking too much of an administrator to do, There are two ways to handle this. One is to modify the ports builds to conditionally create a 'bpf' group. This requires the ports all agree on the group, and I don't like the idea of a port install messing with permissions and ownerships of things in /dev (which aren't sticky across reboots, anyway). If the OS sets the access policy there cannot be any confusion. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message