From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <0f58ba5950b496a52e75d7fa252263c4@quintile.net> References: <201012101413.aa61820@salmon.maths.tcd.ie> <0f58ba5950b496a52e75d7fa252263c4@quintile.net> Date: Fri, 10 Dec 2010 10:42:09 -0500 Message-ID: From: John Floren To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] have installed plan 9 on many hosts, can't get any of them to "share". Topicbox-Message-UUID: 8b0b95ae-ead6-11e9-9d60-3106f5b1d025 On Fri, Dec 10, 2010 at 10:34 AM, Steve Simon wrote: >> I'm not really asking people to write better howtos. =C2=A0I think >> the idea is fundamentally broken. =C2=A0What we really need is some >> less narrative and more expository. > > I agree completely with this, my opinion is we need somthing that explain= s the > concepts of what has to be done and why, and provides pointers to where t= o get > the detailed information. > > I find once I understand what somthing is trying to do and why, debugging= the > details is easy. > > For what its worth the biggest problem I ever had setting up a plan9 netw= ork > was failing to ensure bootes password was the same in the nvram as in key= fs. > > -Steve > My problem was always forgetting to uncomment the keyfs line in cpurc. I'd be able to log in as bootes but nothing else. I've done it often enough that I might be able to write a decent document about setting up a standalone server and some terminals with explanations of what needs to be done, followed by actual commands to do it... I think the existing standalone CPU howto document actually does a pretty good job with that, it's just a little hasty/haphazard sometimes. John