From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Wiki standalone CPU/Auth instructions
Date: Thu, 21 Dec 2006 13:35:37 -0800 [thread overview]
Message-ID: <018FF32A-3294-4F54-BEE3-3CBE0E0F7D31@telus.net> (raw)
In-Reply-To: <7d3530220612211331w46baecb3w8c1ad17a27a035c3@mail.gmail.com>
-----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 <leitec@bughlt.org> 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-----
next prev parent reply other threads:[~2006-12-21 21:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 21:28 Claudio Leite
2006-12-21 21:31 ` John Floren
2006-12-21 21:35 ` Paul Lalonde [this message]
2006-12-21 21:49 ` John Floren
2006-12-21 23:21 ` Paul Lalonde
2006-12-21 23:36 ` Claudio Leite
2006-12-21 23:41 ` John Floren
2006-12-21 22:33 ` Claudio Leite
2006-12-22 0:12 ` Georg Lehner
2007-01-06 8:15 ` Philip Dye
2006-12-21 21:39 erik quanstrom
2006-12-21 22:05 ` Steve Simon
2006-12-21 22:26 ` Claudio Leite
2006-12-21 22:44 erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=018FF32A-3294-4F54-BEE3-3CBE0E0F7D31@telus.net \
--to=plalonde@telus.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).