Date: Fri, 9 Feb 1996 12:25:15 -0800 (PST) From: Julian Elischer <julian@ref.tfs.com> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: phk@critter.tfs.com, terry@lambert.org, current@freebsd.org Subject: Re: FS PATCHES: THE NEXT GENERATION Message-ID: <199602092025.MAA00293@ref.tfs.com> In-Reply-To: <20406.823877228@time.cdrom.com> from "Jordan K. Hubbard" at Feb 9, 96 06:47:08 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > > I want to be able to define a policy for permissions in /dev, and no > > form is more unix-like and suitable than > > > > chmod 644 tty* > > chown root.dev disk/* > > Actually, when we stood around discussing this, we agreed that the > "journaling" mechanism would have to deal with the addition of > wildcard rules like this. I understand the need to define permissions > for entire classes of devices, not just single ones. > > It's also not a question of smart or not smart, it's a question of > upholding the Principle of Least Astonishment and also not opening the > can of worms any farther than it has to be opened. By preserving the > old semantics, all your various shell scripts and system admin hacks > survive and you don't have the "multiple incarnation of /dev (say for > chroots) initialization problem" to worry about, either. I think that the principal of least astonishment has to be balanced against the problem of staying in the dark ages. I think that mount_devfs should be able to look somewhere for a configuration script regarding the filesystem it's making. however there is NO ANSWER anywhere, for what to do about a new device that just pops up... > > Jordan >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602092025.MAA00293>