9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Boris Maryshev <bmaroshe@itcollege.ee>
To: Vester Thacker <vester.thacker@gmail.com>,
	Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Creating new documents on KFS, Fossil,	and Venti implementation and etc...
Date: Sun, 26 Sep 2004 10:50:21 +0300	[thread overview]
Message-ID: <Pine.LNX.4.61.0409261042030.8403@fastmover> (raw)
In-Reply-To: <32a656c204092600075a443a7d@mail.gmail.com>



On Sun, 26 Sep 2004, Vester Thacker wrote:

> 1.  Does Fossil replace kfs on all Plan 9 computers? Or should Fossil
> be used only on file servers, while terminals and cpu servers use kfs?
Wiki says that you should use fossil on cpu servers: "If you have 
installed your system with a fossil file system (as you should have)", 
probably it doesn't matter much for terminals...

> Would anyone be interested in creating a Plan 9 documentation group? I
> know several folks have been doing little by little on the side and I
> applaud their efforts. But is anyone interested in starting a
> documentation project? This might lead to greater colaboration and
> lead to economy of effort. Let the programmers write code and the rest
> of us write or update the docs.   Comments?
I think Wiki is the best place for it.

>
> Sincerely,
> Vester "Vic" Thacker
>
Boris Maryshev


  reply	other threads:[~2004-09-26  7:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-26  7:07 Vester Thacker
2004-09-26  7:50 ` Boris Maryshev [this message]
2004-09-26  8:06   ` Vester Thacker
2004-09-26  8:02 ` [9fans] Creating new documents on KFS, Fossil, andrey mirtchovski
2004-09-26  8:37   ` geoff
2004-09-27  2:08     ` Kenji Okamoto
2004-09-27  4:39       ` geoff

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=Pine.LNX.4.61.0409261042030.8403@fastmover \
    --to=bmaroshe@itcollege.ee \
    --cc=9fans@cse.psu.edu \
    --cc=vester.thacker@gmail.com \
    /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).