From owner-freebsd-hackers  Fri Oct 24 13:46:32 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id NAA19096
          for hackers-outgoing; Fri, 24 Oct 1997 13:46:32 -0700 (PDT)
          (envelope-from owner-freebsd-hackers)
Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA19091
          for <freebsd-hackers@FreeBSD.ORG>; Fri, 24 Oct 1997 13:46:30 -0700 (PDT)
          (envelope-from gdonl@tsc.tdk.com)
Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191])
          by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP
	  id NAA09415; Fri, 24 Oct 1997 13:45:35 -0700 (PDT)
Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194])
	by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id NAA22945;
	Fri, 24 Oct 1997 13:45:20 -0700 (PDT)
Received: (from gdonl@localhost)
	by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id NAA18723;
	Fri, 24 Oct 1997 13:45:08 -0700 (PDT)
From: Don Lewis <Don.Lewis@tsc.tdk.com>
Message-Id: <199710242045.NAA18723@salsa.gv.tsc.tdk.com>
Date: Fri, 24 Oct 1997 13:45:02 -0700
In-Reply-To: Terry Lambert <tlambert@primenet.com>
       "Re: Possible SERIOUS bug in open()? (Big time bug)" (Oct 24,  5:41pm)
X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95)
To: Terry Lambert <tlambert@primenet.com>,
        jamil@trojanhorse.ml.org (Jamil J. Weatherbee)
Subject: Re: Possible SERIOUS bug in open()? (Big time bug)
Cc: thorpej@nas.nasa.gov, joerg_wunsch@uriah.heep.sax.de,
        freebsd-hackers@FreeBSD.ORG
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Oct 24,  5:41pm, Terry Lambert wrote:
} Subject: Re: Possible SERIOUS bug in open()? (Big time bug)

} Permission dictate whether the user may read the file or write the file;
} the open method specific to the file dictates wheher the user can open
} the file.  There aren't permission bits associated with "openable", only
} "readable" and "writeable".
} 
} For /dev/io, where opening has side effects

Opening files has side effects, too.  For instance, space isn't
recovered if a file is unlinked if the file is open.  There is
also the issue of O_EXLOCK and O_SHLOCK.  I don't want another
user to have the ability to do either with my mode 0600 files.