9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: <vdharani@infernopark.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] fossil/venti
Date: Sun, 28 Dec 2003 03:22:44 -0500	[thread overview]
Message-ID: <33139.138.89.177.17.1072599764.squirrel@www.infernopark.com> (raw)
In-Reply-To: <e3b8236575e2b3c680457b85177030e1@granite.cias.osakafu-u.ac.jp>

>> - plan 9 installation is getting complex. the easiest one i did was
>> the first free version (just a standalone system with kfs). as
>> features are added, it getting tougher.
>
> I agree, and that is the reason why I posted my example for someone who
> will have the same problem, too.
yeah, i found the note you have posted only after sending my request.

> Complicated, because we have three kinds of file servers, and the last
> one, which is expected to active now, is still in the progress.   If
> you just want to try Plan 9, you can choose kfs version, because it's
> easier.
No, no. I have been using kfs (and venti) for a long time. I wanted to try
fossil with venti now.

>> - i think kfs file system is needed anyway atleast till fossil kernel
>> is built and the config files are modified accordingly. it is not
>> possible or easy to setup fossil/venti without kfs. am i right?

> If you don't have working Plan 9 network, I think you need kfs system
> first, from which you can fill the things into venti archive disk.☺
ah, now i get it. i was wondering how you have all tried fossil and
started discussing about it. i didnt know you have to use kfs initially or
some working plan 9 machine before fossil is in place.

this is what i tried to do:
the boot floppy asked whether i want kfs or fossil. i chose fossil. I was
thinking, instead of kfs, I can use fossil (with venti). looks like
fossil/venti can be up and running only after necessary steps are taken.

>> (instead of
>> installation-process-assisted fossil installation).
>
> I don't know this.  Is there?
yes.






  reply	other threads:[~2003-12-28  8:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-26 23:05 [9fans] hyperthreading andrey mirtchovski
2003-12-27  0:00 ` jmk
2003-12-27 18:39   ` jmk
2003-12-28 16:11   ` ron minnich
2003-12-28 22:12     ` Joel Salomon
2003-12-29  1:47       ` William Josephson
2003-12-31 17:08       ` ron minnich
2004-01-05 11:03     ` Vasile Rotaru
2004-01-05 14:31       ` David Presotto
2004-01-05 15:32         ` ron minnich
2003-12-27  4:10 ` [9fans] fossil/venti vdharani
2003-12-27  4:49   ` okamoto
2003-12-27  7:52     ` vdharani
2003-12-27  5:20       ` mirtchov
2003-12-28  4:47       ` okamoto
2003-12-28  8:22         ` vdharani [this message]
2003-12-28  6:40           ` andrey mirtchovski
2010-03-26  4:35 [9fans] Fossil/Venti lucio

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=33139.138.89.177.17.1072599764.squirrel@www.infernopark.com \
    --to=vdharani@infernopark.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).