9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Dir->type & Dir->dev
Date: Sun, 30 Nov 2008 19:07:06 +0000	[thread overview]
Message-ID: <492a4c702cbede60f5fc30f6b08c2bb2@terzarima.net> (raw)
In-Reply-To: <1a2be9d78c2e736fb1319f7dd41b765c@quanstro.net>

Qid.type is defined to be equal to the top 8 bits of mode (see stat(5))
and type and dev are defined to be for kernel use (also stat(5))
which is fine if you're not in the kernel.
but what if you are? type is just the device [unicode] letter,
and dev is assigned by the device, and might be the index of an instance
(eg, #I0 has dev 0, and #I1 has dev 1).  once exported and
mounted elsewhere such distinctions vanish because the mount driver
rewrites them, more or less thoroughly (ie, in both stat and read-on-directory).



      parent reply	other threads:[~2008-11-30 19:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-30 15:09 Eric Van Hensbergen
2008-11-30 15:18 ` erik quanstrom
2008-11-30 16:26   ` Eric Van Hensbergen
2008-11-30 19:07   ` 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=492a4c702cbede60f5fc30f6b08c2bb2@terzarima.net \
    --to=forsyth@terzarima.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).