Date: Wed, 19 Apr 1995 14:59:42 -0400 (EDT) From: Peter Dufault <dufault@hda.com> To: phk@ref.tfs.com (Poul-Henning Kamp) Cc: terry@cs.weber.edu, hackers@freefall.cdrom.com Subject: Re: DEVFS ownership and permissions Message-ID: <199504191859.OAA05945@hda.com> In-Reply-To: <199504191846.LAA09577@ref.tfs.com> from "Poul-Henning Kamp" at Apr 19, 95 11:46:08 am
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504191859.OAA05945>