From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] venti ports and productization
Date: Fri, 10 Oct 2003 22:14:05 -0400 [thread overview]
Message-ID: <E1A89Gf-0001YW-FS@t40.swtch.com> (raw)
In-Reply-To: Your message of "Fri, 10 Oct 2003 20:37:01 EDT." <2ac5be8bf0047fa964b6c7068ab24559@9srv.net>
A while ago I ported vac (not vacfs!) to Windows.
Dave and Eric made the port work a bit better, but
my impression (from afar) is that there hasn't been
any further work, especially not toward commercialization.
[Jmk's recent mail supports this.]
I ported Venti the server to FreeBSD a year ago, though
the port is incomplete and unsatisfactory for various reasons.
I also wrote a program to store FFS file system images
as vac-style streams and another program to parse the backed-up
images and serve them over an NFS loopback server.
We back up just under 200GB of disk every night.
I'm very happy with it.
amsterdam=; hist ~/.profile
Sep 6 22:50:53 EDT 2003 /home/am3/rsc/.profile 900
Sep 6 22:50:53 EDT 2003 /dump/am3/2003/1010/rsc/.profile 900
Apr 10 18:30:26 EDT 2003 /dump/am3/2003/0906/rsc/.profile 851
Jan 27 18:22:32 EST 2003 /dump/am3/2003/0410/rsc/.profile 797
amsterdam=;
These programs use the same unsatisfactory port environment.
Over the next few months I plan to clean them up and make them build
using the new port environment that I used for samterm (which
I'd be packaging right now if I weren't writing this email ;-).
I'm also thinking about various ways to speed up the Venti
server (which is currently dog slow) but again that won't happen
for a few months -- I'm up to my eyeballs in other things.
Russ
next prev parent reply other threads:[~2003-10-11 2:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-11 0:37 a
2003-10-11 1:45 ` jmk
2003-10-11 1:50 ` bs
2003-10-11 2:14 ` Russ Cox [this message]
2003-10-11 17:05 ` a
2003-10-21 10:14 ` Martin C.Atkins
2003-10-21 10:20 ` a
2003-10-21 14:26 ` jmk
2003-10-21 15:35 ` a
2003-10-21 15:50 ` Russ Cox
2003-10-21 18:24 ` rog
2003-10-22 4:33 ` okamoto
2003-10-22 5:15 ` okamoto
2003-10-22 9:48 ` a
2003-10-22 14:57 ` Richard Miller
2003-10-22 16:54 ` jmk
2003-10-21 17:20 ` Scott Schwartz
2003-10-21 21:30 ` C H Forsyth
2003-10-21 22:13 ` Dan Cross
2003-10-21 16:05 ` Rob Pike
2003-10-21 16:50 ` rog
2003-10-22 9:52 ` Martin C.Atkins
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=E1A89Gf-0001YW-FS@t40.swtch.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/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).