9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Auth/CPU/Fossil
Date: Thu, 20 Nov 2003 09:08:51 +0100	[thread overview]
Message-ID: <b7e5a2e7c18a9d4482c6f3ab54487886@plan9.escet.urjc.es> (raw)
In-Reply-To: <9406.135.214.150.100.1069276506.squirrel@www.infernopark.com>

[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]

In short, you must configure your standalone server to be an auth/cpu
server (it's already a file server given that you ask fossil to accept connections
from the network).

We have a lab running a fossil auth/cpu/file server and diskless terminals.
Since It seems that you want a similar setup, I might help with the details.

In the wiki:

Consider [Setting up Venti] before you start changing the default installation.
If you have a file server you'll want /n/dump, and venti is the usual
way of getting /n/dump these days.

[Configuring a Standalone CPU Server] tells you what to do to convert
your fs also into a cpu/auth server.

You should also read [Network Configuration] so that the server knows
others.

[Setting up Fossil] tells you among other things how to listen for
network connections (i.e. become a file server). It also shows you how
to add users to a fossil file system (you'd also need to create keys
for each user (see auth(8) ).

BTW, you might want to add extra devices to the cpu kernel config file
so you could start the window system in the console while you're
setting it up.

If you need more help, or want to borrow our config files,
I think we could talk off-list and then you might perhaps
update the wiki so that
next time people could now what sections (and which order)
they should follow.


hth

[-- Attachment #2: Type: message/rfc822, Size: 3398 bytes --]

From: <vdharani@infernopark.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] Auth/CPU/Fossil
Date: Wed, 19 Nov 2003 16:15:06 -0500 (EST)
Message-ID: <9406.135.214.150.100.1069276506.squirrel@www.infernopark.com>

Hi,

I wanted to motivate students to learn and use Plan 9 and Inferno in India.
To do this, I am trying to set up a small network with Plan 9 server and
terminals.

I tried to assist in installing Plan 9 and ran into trouble. So far, I am
used to kfs and kfs-based server only. I havent tried to use fossil as the
file server yet. But for this installation, I tried fossil based
installation. After the base installation was done, I didnt know what to do
because the Wiki documentation doesnt clearly say what is the next step. I
am not sure, if I need to use disk/kfscmd (that are specified for kfs) or
not.

Now, I have fossil-based standalone Plan 9 installation ready. I want to
make it auth/cpu/file server.

Now, here are my questions:

- What documentation sections should I follow to make it auth/cpu/file
server?
- Do I have to make flproto file for fossil server or is it automatically
taken care? (I went through "Setting Up Fossil" section but I am not sure
which one to do and not)
- Do I have to start fossil or is it automatic?
- Do I have to start fossil admin process in a window?
- How do I add users?
- How do I shutdown the server reliably?

Any help appreciated.

Thanks
dharani


  reply	other threads:[~2003-11-20  8:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 21:15 vdharani
2003-11-20  8:08 ` Fco.J.Ballesteros [this message]
2003-12-03 20:53   ` vdharani
2003-12-03 19:42     ` andrey mirtchovski
2003-12-03 22:17       ` vdharani
2003-12-03 22:18       ` vdharani
2003-12-03 20:10     ` Fco.J.Ballesteros
2003-11-20  8:10 ` Fco.J.Ballesteros
2003-11-20 17:35 ` [9fans] Help: Newbie deleting /tmp Antonio Vazquez
2003-11-20 17:09   ` Russ Cox

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=b7e5a2e7c18a9d4482c6f3ab54487886@plan9.escet.urjc.es \
    --to=nemo@plan9.escet.urjc.es \
    --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).