From: erik quanstrom <quanstro@quanstro.net>
To: csant@csant.info, 9fans@cse.psu.edu
Subject: Re: [9fans] fossil+venti installation troubles
Date: Sat, 29 Jul 2006 10:23:02 -0500 [thread overview]
Message-ID: <514855759a00788ef3f9b5bac557c742@quanstro.net> (raw)
In-Reply-To: <op.tdggq3dbd84skq@fiore.malebolge>
are you specifying your venti server as net!localhost!venti?
if so, just droping the -a flag or the ventiaddr in the configuration
file should work.
- erik
On Sat Jul 29 09:49:14 CDT 2006, csant@csant.info wrote:
> Hi,
>
> I have been running a fossil only Plan 9 installation for a bit now,
> without troubles. Today I decided for the second time (after failing
> already the first time) to try to install a fossil+venti system - but
> cannot report success. I closely followed the installation instructions on
> the wiki, but after reboot, I get the following errors:
>
> fossil(#S/sdC1-fossil)...warning: connecting to venti: '/net/net/clone'
> file does not exist
> version...time...
>
> init: starting /bin/rc
> flushthread found nothing to flush - 1 dirty
> ventiSend vtWrite block 0xa failed: not connected to venti server
> archWalk 0xa failed; ptr is in 0x7 offset 0
> archWalk 0x7 failed; ptr is in 0x5 offset 0
> archWalk 0xae71 failed; ptr is in 0xae70 offset 0
> archWalk 0xae70 failed; ptr is in 0xae6f offset 0
> archiveBlock 0xae6f: not connected to Venti server
>
> et caetera... What have I done wrong? and how can I fix it? Is it a
> problem on my hardware, or of the installation? If the latter is the case,
> is it a problem in the installer, or in the instructions? I could fix the
> latter, once I'd know how to do it right. :)
>
> Any help greatly appreciated.
> /c
next prev parent reply other threads:[~2006-07-29 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-29 14:48 csant
2006-07-29 15:23 ` erik quanstrom [this message]
2006-07-29 15:56 ` csant
2006-07-29 17:59 ` csant
2006-07-29 18:17 ` csant
2006-07-29 18:24 ` Steve Simon
2006-07-29 18:41 ` csant
2006-07-29 18:19 ` Steve Simon
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=514855759a00788ef3f9b5bac557c742@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=csant@csant.info \
/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).