From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <94f205013a016ce4c61d4c589c30aaa9@quintile.net>
From: "Steve Simon" <steve@quintile.net>
Date: Thu,  9 Dec 2010 23:26:03 +0000
To: 9fans@9fans.net
In-Reply-To: <475051C5-92F9-42B8-AC80-3EAA7E08EBE0@xmission.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] have installed plan 9 on many hosts,
	can't get any of them to "share".
Topicbox-Message-UUID: 8a814890-ead6-11e9-9d60-3106f5b1d025

Its good top remember the learning curve, ir does feel steep,
and then suddenly...

How far have you got installing your plan9 file/cpu/auth server?
I assume you have booted a terminal successfully?

here are some rough steps:
	install a terminal

	edit /lib/ndb/local to set up networking

	partitioned the hard disk, adding an nvram partition.

	modify your plan9.ini - I suggest you add a boot menu to allow you
	to boot as a terminal or as server (different kernels).

	create  /cfg/$sysname/cpurc, I have put mine from my server
	in http://www.quintile.net/doorstep/cpurc, I don't suggest you use this without
	working out what it all does but it should provide a useful template.

	create accounts in fossil for yourself and bootes.

	write the nvram partition using auth/wrkry - hostowner is, by convention,
	"bootes" the authdom is a name for your authentication domain, mine is
	home.quintile.net but your could be anything you like.

	edit /lib/ndb/auth to allow processes running as bootes to become other people.

	set passwords for bootes (same as you used in wrkey) and for yourself
	using auth/changeuser

you will want to set up secstore but that is optional so leave it till later.

there are some nice options to allow the boot sequence (defined in plan9.ini)
to run unattended but these can wait.

you might want to use mirrored drives for reliability, see fs(4).

hope this helps.

-Steve