From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <06d4e4a17483e1524a94ef3d8fe909fa@granite.cias.osakafu-u.ac.jp>
To: 9fans@cse.psu.edu
From: okamoto@granite.cias.osakafu-u.ac.jp
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Subject: [9fans] how to make coexit fossil+venti and fs
Date: Thu, 17 Jul 2003 14:29:17 +0900
Content-Transfer-Encoding: quoted-printable
Topicbox-Message-UUID: f964c490-eacb-11e9-9e20-41e7f4b1d025

I'm now going to make fossil+venti fileserver to our
Plan 9 network, because now I'm in the summer vacation
season lastly. =E2=98=BA

I have make strategy at first how to make the two file sertvers
coexit in our Plan 9 network, and I'm wondering it now.

If the fossil+venti is believed to be robust as comparable as
release 4 file server, I have no hesitation on this decision.
When I downloaded the sources two days ago, considerable
amounts of venti and fossil sources were changed.   Furthermore,
I suppose Bell-Labs is still using Release 4 file server as their
primary file server.

Then, I think I should hold our present file server further.
In this case, I have to install new fossil+venti into a temporal
machine which also has local kfs filesystem.  The new fossil+
venti will be used only from that very machine in this case,
which is mostly for testing environment of new fossil+venti
system.   However, I'm not a kernel/operating system person...

What is your configuration of this situation out there?
Any other recommendations to me?

Kenji