From owner-freebsd-hackers  Sun Jan 18 13:24:06 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA14222
          for hackers-outgoing; Sun, 18 Jan 1998 13:24:06 -0800 (PST)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from red.juniper.net (red.juniper.net [208.197.169.254])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14193
          for <hackers@freebsd.org>; Sun, 18 Jan 1998 13:23:58 -0800 (PST)
          (envelope-from pst@juniper.net)
Received: from red.juniper.net (localhost.juniper.net [127.0.0.1])
	by red.juniper.net (8.8.5/8.8.5) with ESMTP id NAA08288;
	Sun, 18 Jan 1998 13:22:55 -0800 (PST)
Message-Id: <199801182122.NAA08288@red.juniper.net>
To: Sean Eric Fagan <sef@kithrup.com>
cc: hackers@FreeBSD.ORG
Subject: Re: isdisk() kludge in kernel 
In-reply-to: Your message of "Sat, 17 Jan 1998 15:56:03 PST."
             <199801172356.PAA18827@kithrup.com> 
Date: Sun, 18 Jan 1998 13:22:55 -0800
From: Paul Traina <pst@juniper.net>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk


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.