From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <46368.192.11.226.116.1070484805.squirrel@www.infernopark.com> Subject: Re: [9fans] Auth/CPU/Fossil From: To: <9fans@cse.psu.edu> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Wed, 3 Dec 2003 15:53:25 -0500 Content-Transfer-Encoding: quoted-printable Topicbox-Message-UUID: 9bb1aa74-eacc-11e9-9e20-41e7f4b1d025 Hi Ballestros, Sorry for the delay in replying. I wasnt able to use the internet for sometime. I think I should first try fossil based Plan 9 installation before I help someone located elsewhere. I will do that as soon as I can. I will take your help off-list as needed. Also, seeing the mails on fossil/venti woes, I am getting worried about i= ts stability. I am not sure how stable the system will be but atleast I woul= d like to try it. Thanks dharani > 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