[9fans] Wiki standalone CPU/Auth instructions

[9fans] Wiki standalone CPU/Auth instructions

[Claudio Leite]

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

Re: [9fans] Wiki standalone CPU/Auth instructions

[John Floren]

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

Re: [9fans] Wiki standalone CPU/Auth instructions

[Paul Lalonde]

-----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-----

Re: [9fans] Wiki standalone CPU/Auth instructions

[John Floren]

On 12/21/06, Paul Lalonde <plalonde@telus.net> wrote:
> -----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
>
<snip>

Huh. Well, it's definitely been over two weeks since I've set up a
cpu/auth server, so maybe things are happier now.



John
-- 
Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn

Re: [9fans] Wiki standalone CPU/Auth instructions

[Claudio Leite]

OK, I changed ownership of /adm/keys and keys.who to bootes and was able
to remove -AWP from fossil. I have a good system now, but I didn't quite
follow the instructions since I had -AWP set while setting it up. I will
try on another machine from scratch to see if I can get it while
following the current instructions.

Also, is it 'bad form' to have bootes (or whatever) in group sys? I
didn't see this mentioned anywhere but I set it so I could update
/sys/src, among other things.

Thanks for the help--much appreciated.
-Claudio

Re: [9fans] Wiki standalone CPU/Auth instructions

[Paul Lalonde]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

That said, I have vague recollections of adding bootes to the adm  
group - I don't recall if that is in the wiki.

Paul

On 21-Dec-06, at 1:49 PM, John Floren wrote:

> On 12/21/06, Paul Lalonde <plalonde@telus.net> wrote:
>> -----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
>>
> <snip>
>
> Huh. Well, it's definitely been over two weeks since I've set up a
> cpu/auth server, so maybe things are happier now.
>
>
>
> John
> -- 
> Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFFixbppJeHo/Fbu1wRAvuLAKDmj2HuTI56kJ/auhTnFTI1TbzqHACfSW8P
Ox7ClJ1XNImw5jq6C9Gr8q8=
=NCcl
-----END PGP SIGNATURE-----

Re: [9fans] Wiki standalone CPU/Auth instructions

[Claudio Leite]

* Paul Lalonde (plalonde@telus.net) wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> That said, I have vague recollections of adding bootes to the adm  
> group - I don't recall if that is in the wiki.

It's not. The only reference to group membership is that the user which
you begin with (in the terminal) must be in sys.

-Claudio

> 
> On 21-Dec-06, at 1:49 PM, John Floren wrote:
> 
> > On 12/21/06, Paul Lalonde <plalonde@telus.net> wrote:
> >> -----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
> >>
> > <snip>
> >
> > Huh. Well, it's definitely been over two weeks since I've set up a
> > cpu/auth server, so maybe things are happier now.
> >
> >
> >
> > John
> > -- 
> > Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (Darwin)
> 
> iD8DBQFFixbppJeHo/Fbu1wRAvuLAKDmj2HuTI56kJ/auhTnFTI1TbzqHACfSW8P
> Ox7ClJ1XNImw5jq6C9Gr8q8=
> =NCcl
> -----END PGP SIGNATURE-----

Re: [9fans] Wiki standalone CPU/Auth instructions

[John Floren]

On 12/21/06, Claudio Leite <leitec@bughlt.org> wrote:
> * Paul Lalonde (plalonde@telus.net) wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > That said, I have vague recollections of adding bootes to the adm
> > group - I don't recall if that is in the wiki.
>
> It's not. The only reference to group membership is that the user which
> you begin with (in the terminal) must be in sys.
>
> -Claudio
>

I remember that on my system, I ended up adding bootes to adm, sys,
and upas before I was able to do what I wanted to.


John
-- 
Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn

Re: [9fans] Wiki standalone CPU/Auth instructions

[Georg Lehner]

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

-- 
    Jorge-León

Re: [9fans] Wiki standalone CPU/Auth instructions

[Philip Dye]

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
>>    
>>
>
>  
>

Re: [9fans] Wiki standalone CPU/Auth instructions

[erik quanstrom]

eve on your cpu servers needs to be in the adm group.

- erik
On Thu Dec 21 17:35:42 EST 2006, leitec@bughlt.org wrote:
> OK, I changed ownership of /adm/keys and keys.who to bootes and was able
> to remove -AWP from fossil. I have a good system now, but I didn't quite
> follow the instructions since I had -AWP set while setting it up. I will
> try on another machine from scratch to see if I can get it while
> following the current instructions.
> 
> Also, is it 'bad form' to have bootes (or whatever) in group sys? I
> didn't see this mentioned anywhere but I set it so I could update
> /sys/src, among other things.
> 
> Thanks for the help--much appreciated.
> -Claudio

Re: [9fans] Wiki standalone CPU/Auth instructions

[Claudio Leite]

* Steve Simon (steve@quintile.net) wrote:
> Claudio,
> 
> WRT Eric's email:
> 
> > --rw-rw---- M 9 mach0 adm 2125 Dec 18 08:13 /adm/keys
> > --rw-rw---- M 9 mach0 adm 1539 Dec 18 08:14 /adm/keys.who

I think that's what's wrong: /adm/keys and /adm/keys.who are owned by
"adm" on my server. I will try to change the owner to bootes and see
what happens. 

> 
> I think he is onto somthing here, my permissions are a little different,
> my CPU servers boot as the user 'bootes' - its like root on a unix box, its a
> name which is used by convention for the owner of a machine but everything
> still works if you use a different name, you just have to rembember to use the
> same name as the owner of all your cpu and auth servers. It seems Eric uses
> mach0 as the hostowner for his cpu server, and from your description
> you have chosen glenda.

I actually used 'bootes' for the server owner, but by using glenda I
meant that was the user from which I did the initial setup (pre-reboot).

> 
> I also allow the world to read keys.who as this does not contain secrets, only
> admin info (real name email address etc).
> 
> --rw------- M 17739 bootes sys 300 Jan  3  2006 /adm/keys
> --rw-rw-r-- M 17739 bootes sys 166 Aug 17  2005 /adm/keys.who
> 
> As I rembember it I had to create these files using the
> fossil console. This was years ago though and the distribution may
> now create these correctly.
> 
> 	cpu% con -l /srv/fscons
> 	  prompt:  fsys main create /active/adm/keys bootes sys 600
> 	  prompt:  fsys main create /active/adm/keys.who bootes sys 664
> 	ctrl-\ q
> 
> Note: ``prompt:'' is the default prompt printed by the fossil console
> 
> -Steve

Re: [9fans] Wiki standalone CPU/Auth instructions

[Steve Simon]

Claudio,

WRT Eric's email:

> --rw-rw---- M 9 mach0 adm 2125 Dec 18 08:13 /adm/keys
> --rw-rw---- M 9 mach0 adm 1539 Dec 18 08:14 /adm/keys.who

I think he is onto somthing here, my permissions are a little different,
my CPU servers boot as the user 'bootes' - its like root on a unix box, its a
name which is used by convention for the owner of a machine but everything
still works if you use a different name, you just have to rembember to use the
same name as the owner of all your cpu and auth servers. It seems Eric uses
mach0 as the hostowner for his cpu server, and from your description
you have chosen glenda.

I also allow the world to read keys.who as this does not contain secrets, only
admin info (real name email address etc).

--rw------- M 17739 bootes sys 300 Jan  3  2006 /adm/keys
--rw-rw-r-- M 17739 bootes sys 166 Aug 17  2005 /adm/keys.who

As I rembember it I had to create these files using the
fossil console. This was years ago though and the distribution may
now create these correctly.

	cpu% con -l /srv/fscons
	  prompt:  fsys main create /active/adm/keys bootes sys 600
	  prompt:  fsys main create /active/adm/keys.who bootes sys 664
	ctrl-\ q

Note: ``prompt:'' is the default prompt printed by the fossil console

-Steve

Re: [9fans] Wiki standalone CPU/Auth instructions

[erik quanstrom]

i'm not sure i know exactly what your problem is.  (where are you running 
auth/changeuser and as whom?  also which user is eve on your cpu server?)

however, have you checked the owner and permissions on these files?
fossilcons(8) should have instructions on forcing owners and permissions.
the fileserver i am currently using has these permissions:

--rw-rw---- M 9 mach0 adm 2125 Dec 18 08:13 /adm/keys
--rw-rw---- M 9 mach0 adm 1539 Dec 18 08:14 /adm/keys.who

where mach0 is eve.

hopefully this helps.

- erik
On Thu Dec 21 16:29:37 EST 2006, 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