Date: Wed, 19 Apr 1995 12:03:11 -0700 (PDT) From: Poul-Henning Kamp <phk@ref.tfs.com> To: dufault@hda.com (Peter Dufault) Cc: terry@cs.weber.edu, hackers@freefall.cdrom.com Subject: Re: DEVFS ownership and permissions Message-ID: <199504191903.MAA09677@ref.tfs.com> In-Reply-To: <199504191859.OAA05945@hda.com> from "Peter Dufault" at Apr 19, 95 02:59:42 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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. So that any holes made by users will persist over boot-up ? Hmm, seems like an unusual request to me :-) > > 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. Well, devfs will be hashed out in several rounds, so don't worry you will have plenty of time... -- Poul-Henning Kamp <phk@login.dknet.dk> -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504191903.MAA09677>