From: Anthony Martin <ality@pbrane.org>
To: 9front@9front.org
Subject: [9front] Re: /proc/n/fd format clarification
Date: Sat, 5 Jun 2021 14:04:03 -0700 [thread overview]
Message-ID: <YLvmw/chsIvG9BDu@alice> (raw)
In-Reply-To: <CAHtSCHJi2LtJBcos6JjeEpSSypspnPABazS10wHH_nQgDirFVw@mail.gmail.com>
binary cat <dogedoge61@gmail.com> once said:
> So this mentions 3 things, a path, a version, and a type. This
> checks out, until you look at the supposed lengths. The path is
> supposed to be 8 bytes, which would be 16 hex digits, that's ok,
> but it says 4 bytes for the version, which would be 8 hex digits,
> and we don't see anything like that here. What's going on here?
The qid version is a decimal integer. The other
components of the qid are printed in hexadecimal.
It's just a very old convention. Note that ls(1)
with the -q flag will display the qid in the
same format.
Cheers,
Anthony
next prev parent reply other threads:[~2021-06-05 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 13:26 [9front] " binary cat
2021-06-05 21:04 ` Anthony Martin [this message]
2021-06-05 21:58 ` nicolagi
2021-06-07 17:16 ` binary cat
2021-06-07 23:37 ` ori
2021-06-07 23:46 ` Anthony Martin
2021-06-09 21:24 ` binary cat
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=YLvmw/chsIvG9BDu@alice \
--to=ality@pbrane.org \
--cc=9front@9front.org \
/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).