From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] kfs bug
Date: Thu, 9 Sep 2010 14:58:42 +0100 [thread overview]
Message-ID: <1023d4c768c8748eb15f14ff85786cf7@terzarima.net> (raw)
In-Reply-To: <20100909133941.BA57165D98@server.hemiola.co.uk>
>Would I be right in thinking that 9p originally had 16 bit fids? If
>so, it suggests that no-one has used kfs in anger for a while.
how are you using the kfs? just locally?
a plan 9 client normally re-used fids, so i'd have thought you'd need to have >32767 active files,
which most people probably haven't done.
mind you, that reminds me that i'd noticed something odd when looking at 9p
traces earlier in the summer, which i'd failed to note to track down later
(unless i did work it out and decided there wasn't a problem).
next prev parent reply other threads:[~2010-09-09 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 13:39 rod
2010-09-09 13:58 ` Charles Forsyth [this message]
2010-09-09 14:26 ` rod
2010-09-09 22:28 ` erik quanstrom
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=1023d4c768c8748eb15f14ff85786cf7@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).