From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] Auth/CPU/Fossil From: Fco.J.Ballesteros In-Reply-To: <9406.135.214.150.100.1069276506.squirrel@www.infernopark.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-mgccqjuaswfmesflzmwinngoqo" Date: Thu, 20 Nov 2003 09:08:51 +0100 Topicbox-Message-UUID: 8f994102-eacc-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-mgccqjuaswfmesflzmwinngoqo Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit 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 --upas-mgccqjuaswfmesflzmwinngoqo Content-Type: message/rfc822 Content-Disposition: inline Received: from mail.cse.psu.edu ([130.203.4.6]) by aquamar; Wed Nov 19 21:01:42 MET 2003 Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001) id 8441E19B40; Wed, 19 Nov 2003 15:01:35 -0500 (EST) Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.20.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 9A77D19AE0; Wed, 19 Nov 2003 15:01:14 -0500 (EST) X-Original-To: 9fans@cse.psu.edu Delivered-To: 9fans@cse.psu.edu Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001) id BC26E19A21; Wed, 19 Nov 2003 15:00:26 -0500 (EST) Received: from ensim.rackshack.net (unknown [216.127.72.23]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 53BD119AA1 for <9fans@cse.psu.edu>; Wed, 19 Nov 2003 15:00:14 -0500 (EST) Received: from infernopark.com (localhost [127.0.0.1]) (authenticated (0 bits)) by ensim.rackshack.net (8.11.6/8.11.6) with ESMTP id hAJLF0n10079 for <9fans@cse.psu.edu>; Wed, 19 Nov 2003 16:15:06 -0500 Received: from 135.214.150.100 (SquirrelMail authenticated user vdharani@infernopark.com) by www.infernopark.com with HTTP; Wed, 19 Nov 2003 16:15:06 -0500 (EST) Message-ID: <9406.135.214.150.100.1069276506.squirrel@www.infernopark.com> From: To: <9fans@cse.psu.edu> X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal X-Mailer: SquirrelMail (version 1.2.5) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: [9fans] Auth/CPU/Fossil Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Wed, 19 Nov 2003 16:15:06 -0500 (EST) X-Spam-Status: No, hits=3.3 required=5.0 tests=MISSING_MIMEOLE,MISSING_OUTLOOK_NAME,NO_REAL_NAME, RCVD_IN_NJABL,X_NJABL_OPEN_PROXY version=2.55 X-Spam-Level: *** X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Content-Transfer-Encoding: quoted-printable Hi, I wanted to motivate students to learn and use Plan 9 and Inferno in Indi= a. 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 th= e 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 --upas-mgccqjuaswfmesflzmwinngoqo--