From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Venti on OpenBSD: vtversion: bad format in version string
Date: Tue, 14 Jan 2014 22:48:59 -0800 [thread overview]
Message-ID: <E3092E17-82FC-4FAF-9F8C-B7E63230BFA7@bitblocks.com> (raw)
In-Reply-To: <20140113235913.GA53894@Grants-MacBook.local>
On Jan 13, 2014, at 3:59 PM, Grant Mather <hcaulfield57@gmail.com> wrote:
> I partitioned the disk using fdisk to create one large OpenBSD
> partition, and then created two paritions with disklabel, one for arenas
> and one for isect. I followed the wiki page for setting up venti, and
> have been able to get it working on Plan 9 and other OSes, but not
> OpenBSD.
One suggestion is to use normal files for venti and see if that works.
> Using plan9port-20120508 that is provided with OpenBSD seems to have
> venti working properly on the system, but it does not work across the
> network, when trying to connect with vac/unvac to the server with a
> different OS, I invariably get "vtversion: bad format in version
> string".
>
> Using the most up to date plan9port-20140107, I get the same vtversion
> string when connecting from other OSes, and venti doesn't seem to even
> work on the server, I in turn get "vac: could not connect to server:
> Connection refused".
Have you tried diffing the two versions? Might tell you something. I
use p9p venti on FreeBSD for my plan9 installs with no trouble so far.
One more suggestion is to look at the data on the wire and compare
with a working venti.
>
> Any help would be much appreciated it, I don't know what's going on.
>
> grm
>
next prev parent reply other threads:[~2014-01-15 6:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 23:59 Grant Mather
2014-01-15 6:48 ` Bakul Shah [this message]
2014-01-22 18:32 ` Grant Mather
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=E3092E17-82FC-4FAF-9F8C-B7E63230BFA7@bitblocks.com \
--to=bakul@bitblocks.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).