From: Pavel Klinkovsky <pavel.klinkovsky@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] QTEXCL/DMEXCL redundancy
Date: Wed, 5 Dec 2012 09:41:48 +0000 [thread overview]
Message-ID: <af3d20ce-0b0c-45c5-b657-6ac5910ad865@googlegroups.com> (raw)
Hi all,
first time I am trying to create a "synthetic" file system.
I want to have "synthetic" files with the exclusive flag.
In my getdirent (called from dirread9p) function I have:
>d->qid = (Qid){n, 0, QTFILE|QTEXCL};
>d->mode = 0666;
This does not work (ls -l did not show 'l' flag).
When I made a modification:
>d->qid = (Qid){n, 0, QTFILE|QTEXCL};
>d->mode = DMEXCL|0666;
This works (ls -l shows 'l' flag).
I thought the DMEXCL in 'mode' is a unnecessary since QTEXCL is already present in 'Qid'. I was apparently wrong...
Can you recommend me e.g. the manual page or document explaining such matter?
I really do not understand why such a redundancy (QTEXCL/qid and DMEXCL/mode) is there...
Thanks.
Pavel
next reply other threads:[~2012-12-05 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 9:41 Pavel Klinkovsky [this message]
2012-12-05 11:01 ` Charles Forsyth
2012-12-05 11:02 ` Charles Forsyth
2012-12-05 12:39 ` erik quanstrom
2012-12-05 13:06 ` Charles Forsyth
2012-12-05 13:45 ` erik quanstrom
2012-12-05 13:58 ` Charles Forsyth
2012-12-05 11:37 ` Pavel Klinkovsky
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=af3d20ce-0b0c-45c5-b657-6ac5910ad865@googlegroups.com \
--to=pavel.klinkovsky@gmail.com \
--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).