From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200304301402.h3UE2nY25059@zamenhof.cs.utwente.nl> To: 9fans@cse.psu.edu Subject: Re: [9fans] Venti/fossil running, what now? In-reply-to: Your message of "Wed, 30 Apr 2003 12:23:57 +0200." <502774ec03a42585555db834571ca948@plan9.escet.urjc.es> References: <502774ec03a42585555db834571ca948@plan9.escet.urjc.es> From: Axel Belinfante MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25055.1051711369.1@zamenhof.cs.utwente.nl> Date: Wed, 30 Apr 2003 16:02:49 +0200 Topicbox-Message-UUID: 9c38c208-eacb-11e9-9e20-41e7f4b1d025 I just set up a standalone fossil at home. I followed the info in the wiki, and glanced at nemo's config files on the web, and only had to fiddle a few things: - for the `bootstrapping' key entered in factotum I replaced rsc by `{cat '#c/user'} # add a key so mount and fossil can authenticate each other # remove this key once factotum is initialized with other keys factotum -g 'proto=p9sk1 user='^`{cat '#c/user'}^\ ' dom=localhost !password=localhost' - I changed 'ipconfig loopback ...' to just 'ipconfig' (use DHCP). I used some rc scripting to find `our' ip address needed to set the venti variable (hmmm... can I just use $sysname ?) Even nicer would be to add a check to see if ipconfig fails, and if so, do the 'ipconfig loopback ...' ipconfig ifs=' ' for (h in `{cat /net/ipselftab}) { ifs=' ' j=`{echo $h} if (~ $j(3) 6u) ipself=$j(1) } ... venti=tcp!^$ipself^!17034 - as suggested by the wiki, to make sure the disk layout is known I used fdisk and prep lines like in /rc/bin/termrc (so I also added /386/bin/test, /386/bin/prep and /386/bin/disk/fdisk to the bootdir section of the copy I made of /sys/src/9/pc/pcfl ) One thing I noted: my /dev/ now lists each disk twice, as both the boot script and my /rc/bin/termrc bind -a '#S' /dev Another thing: the nightly automatic 'snap -a' gave me console message: disk: io=10000 at -952.927ms where the negative time surprised me. The machine takes time via ntp. Axel. > In the wiki there's a section on setting up a standalone fossil. > I use that way and boot everything else off the network. > > But that involves creating a kernel with fossil (and venti, perhaps) on > it so you can boot that kernel from a fossil.