From owner-freebsd-hackers Wed Apr 19 11:46:21 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA25941 for hackers-outgoing; Wed, 19 Apr 1995 11:46:21 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA25935 for ; Wed, 19 Apr 1995 11:46:18 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id LAA09577; Wed, 19 Apr 1995 11:46:09 -0700 From: Poul-Henning Kamp Message-Id: <199504191846.LAA09577@ref.tfs.com> Subject: Re: DEVFS ownership and permissions To: dufault@hda.com (Peter Dufault) Date: Wed, 19 Apr 1995 11:46:08 -0700 (PDT) Cc: terry@cs.weber.edu, hackers@freefall.cdrom.com In-Reply-To: <199504191837.OAA05851@hda.com> from "Peter Dufault" at Apr 19, 95 02:37:38 pm Content-Type: text Content-Length: 940 Sender: hackers-owner@FreeBSD.org Precedence: bulk > Terry Lambert writes: > > > > > BTW: How the heck do permissions work? > > > > Ownership and permissions should be specified by the device itself as > > part of the registration information. > > Bill has a raw disk partition he collects his image data on. It is > owned by bill and read write by Bill. It is /dev/rsd1e. Where is > the persistence of the ownership and the permissions of this raw device > which is owned by a regular user? Is it stored on disk someplace and > gets established as the system comes up? Contrary to to Terry, I have talked with Julian about his ideas :-) I belive we will make it part of the boot procedure to have a shell script set the permissions. Permissions are policy, and policy does not belong in the kernel. -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'