Date: Sun, 18 Jan 1998 13:22:55 -0800 From: Paul Traina <pst@juniper.net> To: Sean Eric Fagan <sef@kithrup.com> Cc: hackers@FreeBSD.ORG Subject: Re: isdisk() kludge in kernel Message-ID: <199801182122.NAA08288@red.juniper.net> In-Reply-To: Your message of "Sat, 17 Jan 1998 15:56:03 PST." <199801172356.PAA18827@kithrup.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199801172356.PAA18827@kithrup.com>, Sean Eric Fagan writes: > In article <199801172038.MAA24817.kithrup.freebsd.hackers@red.juniper.net> yo > u write: > >I'd like to propose changing spec_open to simply NEVER allowing the open of > >a block device, or character device, if a character device has a block > >device associated with it and eliminate isdisk() in kern_conf entirely. > > > >Objections? (p.s. I found this in 2.2.5, haven't checked 3.0 yet to see if > >it was fixed, if it was, sorry for bothering you). > > The comment seems to indicate what *should* be done -- namely, the driver > should be asked whether it's a disk or not. > > Sean. Yes, but can you think of ANY block device that you would want to be allowed open once secureleve > 2? I think the distinction is moot.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801182122.NAA08288>