From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] p9p factotum available for plan 9
Date: Tue, 9 Nov 2010 11:17:47 -0800 [thread overview]
Message-ID: <20101109191747.5CEB75B8C@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Tue, 09 Nov 2010 09:41:26 PST." <AANLkTik0LMeWaT5wo2RRWcrzqRz+RX2a_o45UjcFSMgs@mail.gmail.com>
On Tue, 09 Nov 2010 09:41:26 PST David Leimbach <leimy2k@gmail.com> wrote:
>
> Also the one time I tried to set up venti from p9p I basically failed
> horribly, and wasn't really sure what I did wrong. (I should read the
> installation scripts for Plan 9 and the man pages but haven't had time to
> get back to it).
See $PLAN9/src/cmd/venti/srv/tester.
When I was first playing with venti about 5 years back, I
used a `newventi' script like the one below. It creates all
the necessary data & conf files in $PWD. Modify as per
taste. Once set up, start as
$PLAN9/bin/venti/venti -c $conf
You have to be a bit careful when shutting things down
(flush dcache or something -- can't remember).
If you decide to back up ffs/ffs2/hfs/ext2fs/fat filesystems,
Russ's backup scripts are pretty handy.
---
#!/bin/sh
PATH=$PATH:$PLAN9/bin:$PLAN9/bin/venti
export PATH
d=$PWD
bs=8k
conf=venti.conf
echo index main > $conf
for i in 0 1 2 3
do
rm -f arenas$i; touch arenas$i; truncate -s 32G arenas$i;
fmtarenas -b $bs arenas$i. arenas$i
echo arenas arenas$i >> $conf
done
isect=$d/isect0
rm -f $isect; touch $isect; truncate -s 8G $isect
fmtisect -b $bs isect0. $isect
echo isect $isect >> $conf
bloom=$d/bloom
rm -f $bloom; touch $bloom; truncate -s 64M $bloom;
fmtbloom $bloom
echo bloom $bloom >> $conf
cat >> $conf <<EOF
mem 128M
bcmem 64M
icmem 64M
queuewrites
webroot $d/www
httpaddr tcp!*!9091
EOF
fmtindex $conf
next prev parent reply other threads:[~2010-11-09 19:17 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 21:13 erik quanstrom
2010-11-09 3:37 ` erik quanstrom
2010-11-09 17:41 ` David Leimbach
2010-11-09 17:51 ` erik quanstrom
2010-11-10 0:37 ` erik quanstrom
2010-11-10 1:49 ` Russ Cox
2010-11-10 6:46 ` erik quanstrom
2010-11-10 14:31 ` Russ Cox
2010-11-12 3:35 ` Noah Evans
2010-11-12 5:34 ` erik quanstrom
2010-11-12 5:46 ` Noah Evans
2010-11-12 6:03 ` Noah Evans
2010-11-12 6:19 ` Russ Cox
2010-11-12 6:25 ` Noah Evans
2010-11-12 9:07 ` EBo
2010-11-12 15:12 ` David Leimbach
2010-11-12 15:19 ` Eric Van Hensbergen
2010-11-12 15:35 ` erik quanstrom
2010-11-12 15:55 ` Russ Cox
2010-11-12 16:22 ` Eric Van Hensbergen
2010-11-12 19:55 ` ron minnich
2010-11-12 20:23 ` erik quanstrom
2010-11-12 20:31 ` Eric Van Hensbergen
2010-11-12 20:37 ` ron minnich
2010-11-12 20:30 ` Eric Van Hensbergen
2010-11-12 20:41 ` ron minnich
2010-11-12 22:15 ` Eric Van Hensbergen
2010-11-12 22:20 ` ron minnich
2010-11-12 22:36 ` Russ Cox
2010-11-13 8:31 ` tlaronde
2010-11-13 23:42 ` Dave Eckhardt
2010-11-14 22:49 ` Nathaniel W Filardo
2010-11-15 16:22 ` erik quanstrom
2010-11-15 17:40 ` Nathaniel W Filardo
2010-11-15 17:50 ` John Floren
2010-11-12 21:12 ` Russ Cox
2010-11-09 18:08 ` yy
2010-11-09 19:17 ` Bakul Shah [this message]
2010-11-09 19:27 ` Russ Cox
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=20101109191747.5CEB75B8C@mail.bitblocks.com \
--to=bakul+plan9@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).