From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] u9fs query
Date: Tue, 13 May 2003 08:47:16 +0100 [thread overview]
Message-ID: <ba4d895bc7df04afb0af826f5e7689a6@caldo.demon.co.uk> (raw)
In-Reply-To: <049e01c318d1$02194d70$3f00a8c0@MERCURY>
[-- Attachment #1: Type: text/plain, Size: 25 bytes --]
i'd say it's a mistake.
[-- Attachment #2: Type: message/rfc822, Size: 2161 bytes --]
From: "Andrew Simmons" <andrew.simmons@monitorbm.co.nz>
To: <9fans@cse.psu.edu>
Subject: [9fans] u9fs query
Date: Tue, 13 May 2003 09:54:05 +1200
Message-ID: <049e01c318d1$02194d70$3f00a8c0@MERCURY>
In the source I'm looking at for useropen, I see:
case OREAD:
a = R_OK;
...
case OWRITE:
a = R_OK;
and subsequently
if(S_ISDIR(fid->st.st_mode)){
if(a != R_OK){
fprint(2, "attempt by %s to open dir %d\n", fid->u->name, omode);
*ep = Eperm;
return -1;
which seems to indicate that it's ok to open a directory for writing as well
as reading, which I took open(5) to say was not allowed. Could some kind
soul explain? Thanks.
prev parent reply other threads:[~2003-05-13 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 21:54 Andrew Simmons
2003-05-12 22:08 ` Russ Cox
2003-05-13 7:47 ` Charles Forsyth [this message]
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=ba4d895bc7df04afb0af826f5e7689a6@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--cc=9fans@cse.psu.edu \
/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).