From mboxrd@z Thu Jan 1 00:00:00 1970 Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <7d3530220612211331w46baecb3w8c1ad17a27a035c3@mail.gmail.com> References: <20061221162849.N22009@SDF.LONESTAR.ORG> <7d3530220612211331w46baecb3w8c1ad17a27a035c3@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <018FF32A-3294-4F54-BEE3-3CBE0E0F7D31@telus.net> Content-Transfer-Encoding: 7bit From: Paul Lalonde Subject: Re: [9fans] Wiki standalone CPU/Auth instructions Date: Thu, 21 Dec 2006 13:35:37 -0800 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Topicbox-Message-UUID: f848d56e-ead1-11e9-9d60-3106f5b1d025 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As a data point, I followed the cpu/auth server instructions about 2 weeks ago with complete success, and got a server running in a Parallels machine quite easily (thanks to David Leimbach's patches). Paul On 21-Dec-06, at 1:31 PM, John Floren wrote: > On 12/21/06, Claudio Leite wrote: >> Hi, >> >> I attempted once more to set up a CPU server from the >> instructions in >> the wiki and ended up with the same problem. Everything goes as >> planned >> until I reboot with the CPU kernel. I used glenda (which I >> double-checked was in group sys) and made sure to keep track of >> the keys >> I used. Yet, when I reboot (after resetting the nvram), I cannot >> write >> to /adm/keys.who, and thus auth/changeuser fails for any user, >> including >> bootes. So, I can't add anyone to the auth server, and of course >> cannot >> login. >> >> I set options -AWP on my fossil and of course that worked. But the >> current instructions do not mention this (and I didn't quite get what >> was meant in the discussions from Feb. or so when this was removed >> from >> the wiki). Drawterm works fine at this point. >> But when I remove -AWP, it once again cannot read /adm/keys >> and /adm/keys.who, so drawterm and auth/changeuser both fail. >> >> So--what should I do next? >> >> Thanks. >> -Claudio >> > > I'd like to interject that I have experienced this multiple times > myself. > As I'm in the (currently interrupted) process of setting up a CPU/auth > server, I'll probably run into it again soon; let's just hope I can > find the voodoo solution again. > > > John > -- > Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFFiv4ppJeHo/Fbu1wRAt1GAJ9wCwkcUgW/zikrj4NbPs754BYqeQCg1Mz+ X5nioq0FOEB8pFgG7hehd/k= =/8gC -----END PGP SIGNATURE-----