9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steve Simon <steve@quintile.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Standalone venti, fossil configuration
Date: Fri, 18 Aug 2023 13:17:28 +0200	[thread overview]
Message-ID: <BB813A2A-1311-4A90-93CD-EF87976ED9BC@quintile.net> (raw)
In-Reply-To: <2A34721D-3C65-418E-8AD2-75EA3BDF2D69@germteig.com>

[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]

if fossil and venti are started at boot then the plan9.ini variable venti= is all thats needed.

if you want to start them after boot, booting from another filesystem then the -v option to fossil is what you are after.

i wrote a hand-holding doc about rebuilding a venti/fossil years ago: https://9p.io/sources/contrib/steve/doc/Venti-rescue.pdf this describes how they fit together. note this was more about rebuilding after a disc failure than installation but it might help.

-Steve


> On 18 Aug 2023, at 11:51 am, Marco Feichtinger <marco@germteig.com> wrote:
> 
> I have a standalone venti, which tcp boots from my file server.
>  How do I need to configure my fossil server, so it knows to use that venti machine
> for archiving?
> 
> Is it enough to set the venti environmental variable; venti=ip-address?
> 
> -marco
> 

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Ta60073f3cdef1537-M06e6c7c77ca07f82f8af7da6
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 2479 bytes --]

      reply	other threads:[~2023-08-18 11:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18  9:51 Marco Feichtinger
2023-08-18 11:17 ` Steve Simon [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=BB813A2A-1311-4A90-93CD-EF87976ED9BC@quintile.net \
    --to=steve@quintile.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).