From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew To: 9fans@cse.psu.edu Subject: Re: [9fans] more silly fossil questions Message-ID: <20030624172649.GA9492@thefrayedknot.armory.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Date: Tue, 24 Jun 2003 10:26:49 -0700 Topicbox-Message-UUID: d9e093ba-eacb-11e9-9e20-41e7f4b1d025 fwiw I currently do the standalone fossil setup. It seems to work reasonably well except you are kinda screwed if you mess up the boot scripts or something. I had to reload from a seperate system with kfs. The system does cpu/fossil, i have a seperate auth server. Basically what happens is the files you need to boot up get on the network and run fossil/venti all get compiled into the kernel, which unfortunatly makes it fairly big and bulky, and you get to recompile everytime something gets updated or you want to change some of the initial settings. I had to go this route because i lacked the drives/space at the time to do anything else. I will probably swap over to booting onto kfs then exporting fossil now that i have some extra drives, hopefully things will be easier that way.