From: erik quanstrom <quanstro@coraid.com>
To: paurea@gmail.com, alcortes@it.uc3m.es, 9fans@cse.psu.edu
Subject: Re: [9fans] how to build a file server?
Date: Tue, 9 Jan 2007 14:07:33 -0500 [thread overview]
Message-ID: <846f58bb31c1c79be0e8c03140f5e26e@coraid.com> (raw)
that's an easy mistake to make, but it's a big confusion.
kfs is not the fileserver kernel. thus, kfscmd is for kfs
which runs on terminals. the fileserver's commands are in fsconfig(8).
- erik
On Tue Jan 9 14:02:56 EST 2007, paurea@gmail.com wrote:
> kfscmd is for kfs the old file server. You should be using fossil.
> Take a look at the fossil(4), specifically the command fossil/conf and
> fossilcons(8) man pages.
>
>
> --
> - curiosity sKilled the cat
next reply other threads:[~2007-01-09 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 19:07 erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-09 17:25 Alberto Cortés
2007-01-09 17:59 ` Gabriel Diaz
2007-01-09 19:01 ` Gorka guardiola
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=846f58bb31c1c79be0e8c03140f5e26e@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
--cc=alcortes@it.uc3m.es \
--cc=paurea@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).