From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 9vx and create (...DMEXCL)
Date: Mon, 21 Dec 2009 22:27:49 -0500 [thread overview]
Message-ID: <2c9ff7e46c74a5faea56c49b88065b08@brasstown.quanstro.net> (raw)
In-Reply-To: <<bcba51a0912211848n63cca76es7a2a42993f3635bd@mail.gmail.com>>
> Is create (2) with DMEXCL mode supported under 9vx?
it seems you've already got the answer ...
> If 9vx maps Plan9 permissions directly to Linux permissions this is
> understandable. But is there any workaround?
it's up to the fileserver to implement DMEXCL, and #Z doesn't.
using a different fileserver (e.g. fossil or cwfs, ken's fs) would solve
the problem. you could also modify ldevfs-posix.c to accept DMEXCL
and map that to O_EXCL|O_CREAT which may actually do the
right thing.
- erik
next parent reply other threads:[~2009-12-22 3:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<bcba51a0912211848n63cca76es7a2a42993f3635bd@mail.gmail.com>
2009-12-22 3:27 ` erik quanstrom [this message]
2009-12-22 9:51 ` Charles Forsyth
2009-12-22 16:31 ` Russ Cox
2009-12-22 15:44 ` Dmitry Golubovsky
[not found] <<1c5f6c9c85185a32b8833d01de47e34d@terzarima.net>
2009-12-22 14:19 ` erik quanstrom
2009-12-22 2:48 Dimitry Golubovsky
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=2c9ff7e46c74a5faea56c49b88065b08@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).