archive mirror
 help / color / mirror / Atom feed
From: "Ata, John" <>
To: "Linux Kernel Mailing List" <>
Subject: RE: incompatible open modes
Date: Thu, 31 Jul 2003 14:29:12 -0400	[thread overview]
Message-ID: <> (raw)

Hi Andries,

If that's what's been decided... I presume for backwards compatability,
but it does seem rather odd though.  After all, it seems like O_RDONLY
is supposed to safeguard someone from accidently overwriting a file.
Otherwise why not automatically open everything read/write?  Going down
the same path, what's next: automatically write enabling a file which
has been openend for O_RDONLY the next time someone performs a write
operation on it? ;-)

Take care,

-----Original Message-----
From: Andries Brouwer [] 
Sent: Thursday, July 31, 2003 1:36 PM
To: Zack Brown
Cc: Ata, John; Linux Kernel Mailing List
Subject: Re: incompatible open modes

> On Thu, Jul 31, 2003 at 12:09:14PM -0400, Ata, John wrote:

> >    the manpage on "open" states that if a file is opened
> >    the O_TRUNC is either ignored or an error is returned.  The 2.4
> >    appears to cheerfully truncate the file on open.  I wondered
> >    behavior is actually intended.
> >
> >    O_TRUNC
> >        If the file already exists and is a regular file  and  the
> >        mode  allows  writing  (i.e.,  is O_RDWR or O_WRONLY) it will
> >        truncated to length 0.  
> >        Otherwise the effect of O_TRUNC is unspecified.
> >        (On many Linux versions it will be ignored; on other versions
> >        it will return an error.)

This was just recently discussed, and it became clear that the
remark only led to confusion. It has been deleted. Instead

       The (undefined) effect of O_RDONLY | O_TRUNC various among
       implementations.  On  many  systems  the  file is actually

has been added.


             reply	other threads:[~2003-07-31 18:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-31 18:29 Ata, John [this message]
2003-07-31 19:14 ` incompatible open modes Richard B. Johnson
     [not found] <>
2003-07-31 17:03 ` Zack Brown
2003-07-31 17:35   ` Andries Brouwer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).