pi cpu server

pi cpu server

[Frank D. Engel, Jr.]

I am trying to set up a standalone (sd card boot) 9front installation on 
a Raspberry Pi 3 (using the pi3/4 image) to boot as a cpu server, but I 
can't figure out where to put the service=cpu and bootargs=... options.

The pi uses /n/pidos instead of /n/9fat, and I tried placing these in 
both config.txt and cmdline.txt within that mount, but they seem to be 
ignored in both places, and I am not finding any documentation on this - 
everything relevant seems to be written assuming the x64/amd64 situation...?

Re: [9fans] pi cpu server

[ori]

> I am trying to set up a standalone (sd card boot) 9front installation on 
> a Raspberry Pi 3 (using the pi3/4 image) to boot as a cpu server, but I 
> can't figure out where to put the service=cpu and bootargs=... options.
> 
> The pi uses /n/pidos instead of /n/9fat, and I tried placing these in 
> both config.txt and cmdline.txt within that mount, but they seem to be 
> ignored in both places, and I am not finding any documentation on this - 
> everything relevant seems to be written assuming the x64/amd64 situation...?
> 

I don't currently have a pi that I can use, but I seem to remember that
cmdline.txt is the right place to put it, but you need to put all the
arguments on one line, instead of multiple lines.

Something like:

	bootfile=9pi4 'nobootprompt=local!/dev/sdN0/fscache -a tcp!*!564' mouseport=none service=cpu ...

Re: [9fans] pi cpu server

[Frank D. Engel, Jr.]

Thanks, that is what I was missing - I had them on separate lines.

Now I need to puzzle through this "tlsclient: auth_proxy: auth_proxy rpc 
write: interrupted" error whenever I try to use rcpu to connect back to 
the server as a different user (from a drawterm connection).  If I just 
"rcpu" by itself it works, but "rcpu -u glenda" for example gives me 
that error.


On 9/4/20 6:38 PM, ori@eigenstate.org wrote:
>> I am trying to set up a standalone (sd card boot) 9front installation on
>> a Raspberry Pi 3 (using the pi3/4 image) to boot as a cpu server, but I
>> can't figure out where to put the service=cpu and bootargs=... options.
>>
>> The pi uses /n/pidos instead of /n/9fat, and I tried placing these in
>> both config.txt and cmdline.txt within that mount, but they seem to be
>> ignored in both places, and I am not finding any documentation on this -
>> everything relevant seems to be written assuming the x64/amd64 situation...?
>>
> I don't currently have a pi that I can use, but I seem to remember that
> cmdline.txt is the right place to put it, but you need to put all the
> arguments on one line, instead of multiple lines.
>
> Something like:
>
>          bootfile=9pi4 'nobootprompt=local!/dev/sdN0/fscache -a tcp!*!564' mouseport=none service=cpu ...
>
>
> ------------------------------------------
> 9fans: 9fans
> Permalink: https://9fans.topicbox.com/groups/9fans/Tc236964f02eb4e55-M649f73dcc2153563cd787358
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
>

Re: [9fans] pi cpu server

[ori]

> Thanks, that is what I was missing - I had them on separate lines.
> 
> Now I need to puzzle through this "tlsclient: auth_proxy: auth_proxy rpc 
> write: interrupted" error whenever I try to use rcpu to connect back to 
> the server as a different user (from a drawterm connection).  If I just 
> "rcpu" by itself it works, but "rcpu -u glenda" for example gives me 
> that error.

First, make sure that your auth server is actually set up and found
correctly -- auth/debug can help here. Note that you'll probably be
able to auth as hostowner even if your auth server is misconfigured.

Re: [9fans] pi cpu server

[Frank D. Engel, Jr.]

Thanks, auth/debug was indeed useful.

Somehow I missed the authdom= entry in /lib/ndb/local and it was 
complaining that it could not find an auth server for my authdom.

I added that and rebooted, and now all is well.


On 9/4/20 11:38 PM, ori@eigenstate.org wrote:
>> Thanks, that is what I was missing - I had them on separate lines.
>>
>> Now I need to puzzle through this "tlsclient: auth_proxy: auth_proxy rpc
>> write: interrupted" error whenever I try to use rcpu to connect back to
>> the server as a different user (from a drawterm connection).  If I just
>> "rcpu" by itself it works, but "rcpu -u glenda" for example gives me
>> that error.
> First, make sure that your auth server is actually set up and found
> correctly -- auth/debug can help here. Note that you'll probably be
> able to auth as hostowner even if your auth server is misconfigured.
>
>
> ------------------------------------------
> 9fans: 9fans
> Permalink: https://9fans.topicbox.com/groups/9fans/Tc236964f02eb4e55-Md17a69450b891a9e1aa49f9c
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
>