From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] QTEXCL/DMEXCL redundancy
Date: Wed, 5 Dec 2012 11:01:19 +0000 [thread overview]
Message-ID: <CAOw7k5h1PPpjqP+KJWC+zbdOZ2OPhWe=aG-SEdV9cfSC+5pPrQ@mail.gmail.com> (raw)
In-Reply-To: <af3d20ce-0b0c-45c5-b657-6ac5910ad865@googlegroups.com>
The qid.type is defined to be the top 8 bits of the mode.
See the end of intro(5) and the discussion in stat(5).
On 5 December 2012 09:41, Pavel Klinkovsky <pavel.klinkovsky@gmail.com> wrote:
> I really do not understand why such a redundancy (QTEXCL/qid and DMEXCL/mode) is there...
next prev parent reply other threads:[~2012-12-05 11:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 9:41 Pavel Klinkovsky
2012-12-05 11:01 ` Charles Forsyth [this message]
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='CAOw7k5h1PPpjqP+KJWC+zbdOZ2OPhWe=aG-SEdV9cfSC+5pPrQ@mail.gmail.com' \
--to=charles.forsyth@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).