From owner-freebsd-hackers Wed Oct 22 02:09:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA18315 for hackers-outgoing; Wed, 22 Oct 1997 02:09:08 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA18310 for ; Wed, 22 Oct 1997 02:09:04 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.6/8.6.12) with SMTP id CAA13732; Wed, 22 Oct 1997 02:09:46 -0700 (PDT) Message-Id: <199710220909.CAA13732@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: "Jamil J. Weatherbee" Cc: Joerg Wunsch , FreeBSD hackers Subject: Re: Possible SERIOUS bug in open()? Reply-To: Jason Thorpe From: Jason Thorpe Date: Wed, 22 Oct 1997 02:09:44 -0700 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 22 Oct 1997 01:38:11 -0700 (PDT) "Jamil J. Weatherbee" wrote: > How exactly did you fix it, this is related to what I was saying about > opening a file as RD_ONLY and WR_ONLY, because if oflags = -1 then fflags > = 0 and that means the file is not open for read or write which my point > was that it should be forced to be open for one or the other. I don't > rememer who, but someone seemed to think that it could be actually useful > to hav a file not open for read or write How would opening for !read !write be useful? What else could you possibly want to do? (Yes, this is a trick question :-) Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-6 Work: +1 415 604 0935 Moffett Field, CA 94035 Pager: +1 415 428 6939