From owner-freebsd-hackers Wed Apr 19 12:00:39 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA26270 for hackers-outgoing; Wed, 19 Apr 1995 12:00:39 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA26260 for ; Wed, 19 Apr 1995 12:00:36 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id OAA05945; Wed, 19 Apr 1995 14:59:42 -0400 From: Peter Dufault Message-Id: <199504191859.OAA05945@hda.com> Subject: Re: DEVFS ownership and permissions To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Wed, 19 Apr 1995 14:59:42 -0400 (EDT) Cc: terry@cs.weber.edu, hackers@freefall.cdrom.com In-Reply-To: <199504191846.LAA09577@ref.tfs.com> from "Poul-Henning Kamp" at Apr 19, 95 11:46:08 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 856 Sender: hackers-owner@FreeBSD.org Precedence: bulk Poul-Henning Kamp writes: > I believe we will make it part of the boot procedure to have a shell > script set the permissions. That is kind of klunky. How about a utility that snapshots the permissions and reestablishes them at boot up? You could try to run it at a clean shutdown if we ever get beyond a "10 seconds before you're dead" shutdown. > > Permissions are policy, and policy does not belong in the kernel. Site policy doesn't belong in the kernel. Other policy does, which is why I think I prefer a devfs versus a symlink approach of establishing aliases for the "shallow" (/dev/*) device names. I'm being wimpy because I haven't thought about this much yet. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267