From owner-freebsd-fs Tue Sep 24 10:58:22 1996 Return-Path: owner-fs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA18441 for fs-outgoing; Tue, 24 Sep 1996 10:58:22 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA18170; Tue, 24 Sep 1996 10:57:31 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id SAA20849; Tue, 24 Sep 1996 18:54:47 +0100 Date: Tue, 24 Sep 1996 18:54:46 +0100 (BST) From: Doug Rabson To: Bruce Evans cc: michaelh@cet.co.jp, fs@FreeBSD.org, lite2@FreeBSD.org Subject: Re: New d_type field in *devsw In-Reply-To: <199609241719.DAA07851@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-fs@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 25 Sep 1996, Bruce Evans wrote: > >There is an existing unused field in bdevsw, d_flags which can be used to > >identify disks and tapes for securelevel and ioctl or alternatively the > >existing FreeBSD behaviour of calling isdisk() is still possible. The > >current behaviour of dead_read is probably also adequate. > > >Needless to say, these hacks should be first against the wall after the > >devfs revolution :-). > > They are high quality compared with isdisk(). My current hack derives the correct value for d_flags at initialisation time from isdisk :-). Not ideal. > > The cross pointers in the devsw's can be be used to share d_flags with > the cdevs. However, to use them we would have to modify a lot of > device drivers with a temporary change. Except for ttys which don't have a bdevsw. Still, I think the existing FreeBSD behaviour is almost OK there. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 734 3761 FAX: +44 171 734 6426