From: Philip Dye <philip.dye@cs.cmu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Wiki standalone CPU/Auth instructions
Date: Sat, 6 Jan 2007 03:15:00 -0500 [thread overview]
Message-ID: <459F5A84.5020202@cs.cmu.edu> (raw)
In-Reply-To: <87odpwkcu4.fsf@jorgito.magma.com.ni>
http://www.magma.com.ni/moin/Plan9Tutorial is no longer available.
Does anyone have a copy available ?
Thanks,
Philip Dye
Georg Lehner wrote:
>Hello!
>
>the user running auth/changeuser needs to be in the adm group. If you
>follow the standard instructions auth/changeuse is run by bootes, the
>hostowner of the auth server.
>
>Changeing the ownership of the adm files seems the wrong way to go
>for me. The "sys" group is for filesystem administration, and the
>"adm" group for authentication, these should be kept separate.
>
>I have put together setup instructions at:
>
> http://www.magma.com.ni/moin/Plan9Tutorial
>
>trying to smooth the rough edges of the Plan 9 setup instructions.
>Everything there is taken from the original Plan 9 Wiki and other Plan 9
>documentation, nothing new there, just put nicely together (I hope).
>
>Regards,
>
> Jorge-León
>
>Claudio Leite <leitec@bughlt.org> writes:
>
>
>
>>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
>>
>>
>
>
>
next prev parent reply other threads:[~2007-01-06 8:15 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
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 [this message]
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=459F5A84.5020202@cs.cmu.edu \
--to=philip.dye@cs.cmu.edu \
--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).