From: Zack Brown <zbrown@tumblerings.org>
To: "Ata, John" <John.Ata@DigitalNet.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: incompatible open modes
Date: Thu, 31 Jul 2003 10:03:45 -0700 [thread overview]
Message-ID: <20030731170345.GJ6693@renegade> (raw)
In-Reply-To: <6DED202D454D3B4EB7D98A7439218D610C9AB7@vahqex2.gfgsi.com>
Hi John,
The best place to ask is on the linux-kernel mailing list (CCed).
Good luck,
Zack
On Thu, Jul 31, 2003 at 12:09:14PM -0400, Ata, John wrote:
> Hi Zach,
>
> I don't know if you're the right contact... just wondered how I go about
> getting information as to the intent of the Linux kernel... the manpage on
> "open" states that if a file is opened "O_RDONLY|O_TRUNC", the O_TRUNC is
> either ignored or an error is returned. The 2.4 kernel appears to
> cheerfully truncate the file on open. I wondered which behavior is
> actually intended.
>
> Thanks for your time...
>
> Take care,
> ------
> John G. Ata
> DigitalNet, LLC
> XTS-400 Software Development
> MailTo:John.Ata@DigitalNet.com
> Phone:(703) 563-8092
>
> O_TRUNC
> If the file already exists and is a regular file and the
> open
> mode allows writing (i.e., is O_RDWR or O_WRONLY) it
> will be
> truncated to length 0. If the file is a FIFO or terminal
> device
> file, the O_TRUNC flag is ignored. Otherwise the
> effect of
> O_TRUNC is unspecified. (On many Linux versions it
> will be
> ignored; on other versions it will return an error.)
--
Zack Brown
next parent reply other threads:[~2003-07-31 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6DED202D454D3B4EB7D98A7439218D610C9AB7@vahqex2.gfgsi.com>
2003-07-31 17:03 ` Zack Brown [this message]
2003-07-31 17:35 ` incompatible open modes Andries Brouwer
2003-07-31 18:29 Ata, John
2003-07-31 19:14 ` Richard B. Johnson
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030731170345.GJ6693@renegade \
--to=zbrown@tumblerings.org \
--cc=John.Ata@DigitalNet.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).