From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] Installed Plan 9, now what? In-Reply-To: Your message of "Mon, 08 Dec 2003 13:36:51 +0200." <81132473206F3A46A72BD6116E1A06AE056157@black.aprote.com> From: "Russ Cox" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4039.1070895658.1@t40.swtch.com> Message-Id: Date: Mon, 8 Dec 2003 10:00:58 -0500 Topicbox-Message-UUID: 9cbee54e-eacc-11e9-9e20-41e7f4b1d025 > > I recently installed plan 9 on my dell dimension desktop using the > > wiki notes. I used fossil as my filesystem. How do I stay upto date? > > The notes on the webpage seems to be for kfs. > > OK, I don't get it. There seems to be some consensus that clientmount() > shoud be 'mount -c /srv/boot /n/boot'. But in /sys/src/9/boot/local.c > /srv/boot is created as 'srv -A fboot', which means only authentication > is off; permission checking and arbitrary wstats are still standard. = > This is clearly > not enough for replica (confirmed by in vivo experiments).=20 > So, what's the deal? the deal is that for the local file system, it's okay not to do authentication. kfs never did, for bootstrapping reasons, and so i made the fossil boot process do the same. otherwise you'd need to run an auth server just to boot a standalone laptop. it's only for booting, not for pulling. i just put myself in sys and remove the -u from the proto file, and then that's enough for replica (and all the created files get owned by me, which is no problem for me). if you have a special system account you could still do the same, as long as you're willing to give up on things being owned by sys. russ