From: kvik@a-b.xyz
To: 9front@9front.org
Subject: Re: [9front] [PATCH] Fix incorrect Tversion handling by pre-lib9p file servers
Date: Sun, 12 Jul 2020 22:46:34 +0200 [thread overview]
Message-ID: <CE193BD80036623601BE44F813218D50@a-b.xyz> (raw)
In-Reply-To: <CB88E8749E366DB68F9F505A8A99665C@eigenstate.org>
> How have you tested the mismatched versions?
Where possible, by something like:
; aux/9pcon -c 'exportfs -r /'
Tversion 256 9P2000
-> Tversion tag 65535 msize 256 version '9P2000'
<- Rversion tag 65535 msize 256 version '9P2000'
Tversion 256 9P2020
-> Tversion tag 65535 msize 256 version '9P2020'
<- Rversion tag 65535 msize 256 version '9P2000'
Tversion 256 8½P2000
-> Tversion tag 65535 msize 256 version '8½P2000'
<- Rversion tag 65535 msize 256 version 'unknown'
I will admit to not having tested every file server. Some of
which like aux/searchfs I have no idea how to run, and some of
which aren't amenable to be run under 9pcon due to not posting
to /srv nor talking 9p on stdio.
prev parent reply other threads:[~2020-07-12 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 17:18 kvik
2020-07-12 19:33 ` [9front] " ori
2020-07-12 20:46 ` kvik [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=CE193BD80036623601BE44F813218D50@a-b.xyz \
--to=kvik@a-b.xyz \
--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).