9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Frank D. Engel, Jr." <fde101@fjrhome.net>
To: 9fans@9fans.net
Subject: Re: [9fans] pi cpu server
Date: Fri, 4 Sep 2020 22:35:12 -0400	[thread overview]
Message-ID: <2cb9d239-0071-619a-a176-32267ec7e017@fjrhome.net> (raw)
In-Reply-To: <CA85FD2245C9DC7B0BB79C279AC16E85@eigenstate.org>

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
>


  reply	other threads:[~2020-09-05  2:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04 21:53 Frank D. Engel, Jr.
2020-09-04 22:38 ` [9fans] " ori
2020-09-05  2:35   ` Frank D. Engel, Jr. [this message]
2020-09-05  3:38     ` ori
2020-09-05 11:45       ` Frank D. Engel, Jr.

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=2cb9d239-0071-619a-a176-32267ec7e017@fjrhome.net \
    --to=fde101@fjrhome.net \
    --cc=9fans@9fans.net \
    /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).