From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: Re: [9fans] standalone cpu server wiki
Date: Wed, 21 Jan 2004 19:20:17 -0700 [thread overview]
Message-ID: <e30f6c5e15cf86c2fa1fa6cf38eb9afc@plan9.ucalgary.ca> (raw)
In-Reply-To: <200401211853.19584.jhorey@cs.unm.edu>
the wiki is relatively up-to-date. give it a shot and if you see any
problems try the 9fans archives.
cpu servers are very easy -- all they need to know is where the auth
and file servers are (auth= and fs= settings in plan9.ini).
installing a file server takes a bit more work. in your case (when
you don't need a standalone auth/cpu/fs server) I'd say your standard
installation could very easily be turned into a file server by telling
fossil to listen to the right port and starting keyfs and listen on
service.auth from cpurc:
auth/keyfs -wp -m /mnt/keys /adm/keys >/dev/null >[2=1]
aux/listen -q -t /rc/bin/service.auth -d /rc/bin/service tcp
still do check the documentation on the wiki -- there are some details
like compiling an auth/cpu server kernel that you may want to get
right...
the standalone file server refers to the old Plan 9 file server
written by Ken Thompson -- it's the one described in all the papers.
fossil is a replacement which doesn't require that you dedicate an
entire machine to it (the main machine at ucalgary serves as both an
auth and file server, and allows me to login to it). the 'kfs' file
server was used as a standalone plan9 terminal before fossil was
written.
my advice is to start by adding menuconfig to plan9.ini (see the man
page) so that you can go choose and boot an old kernel you know works
whenever there's something broken in the new one -- having a sane
/rc/bin/termrc when you're editing /rc/bin/cpurc may save you a few
hours of grief :)
andrey
> Hello everybody,
>
> I am going to attempt to install a Plan 9 network with two CPU servers, one
> fileserver, and of course one terminal. I've never done this before, so I was
> wondering if anybody knew if the Wiki page for installing a standalone CPU
> server was up to date. Also is the Wiki page for "Installing a Plan 9 File
> Server" still relevant? The Wiki paged mentioned
> "that this is for a stand alone fileserver. The new (Jan 2003) Fossil
> fileserver is described in setting_up_fossil". What advantages does Fossil
> offer over what this page describes? Thanks for anybody that can offer
> advice!
>
> -James Horey
next prev parent reply other threads:[~2004-01-22 2:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 1:53 James Horey
2004-01-22 2:20 ` mirtchov [this message]
2004-01-22 8:27 ` vdharani
2004-01-22 5:58 ` mirtchov
2004-01-22 21:00 ` vdharani
2004-01-23 5:00 ` Jack Johnson
2004-01-23 5:33 ` mirtchov
2004-01-23 11:52 ` a
2004-01-22 16:27 ` David Presotto
2004-01-22 21:19 ` vdharani
2004-01-22 19:13 ` David Presotto
2004-01-22 19:14 ` David Presotto
2004-01-23 2:02 ` James Horey
2004-01-23 2:27 ` okamoto
2004-01-23 5:17 ` Jack Johnson
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=e30f6c5e15cf86c2fa1fa6cf38eb9afc@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).