Re: [9fans] Setting 9pi Start State / Drawterm to 9pi

[Brian Vito <brian.vito2@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2889 bytes --]

So if I were to want to connect to my 9pi at home from my office, would I
have to make the 9pi into a cpu server? I'm looking for the simplest way to
be able to have access to my 9pi files/system from another computer (and
use the Plan 9 environment while doing so).

Also, I was wondering if Plan 9 uses the Raspberry Pi's GPU. In other
words, should I allocate the smallest amount of memory to the GPU (I think
16 is the minimum) rather than the default of 64? And in that case, I would
also assume that overclocking the GPU wouldn't be of any benefit.

Thanks again. 𝔹


On Fri, Feb 21, 2014 at 6:00 AM, <9fans-request@9fans.net> wrote:
>
>
> Date: Fri, 21 Feb 2014 10:28:23 +0000
> From: Richard Miller <9fans@hamnavoe.com>
> To: 9fans@9fans.net
> Subject: Re: [9fans] Setting 9pi Start State / Drawterm to 9pi
> Message-ID: <e00c3dd558dedeb67f80b0a110799636@hamnavoe.com>
> Content-Type: text/plain; charset="US-ASCII"
>
> > i'm not sure what type of kernel is on the stock 9Pi image.
>
> The 9pi.img has both types of kernel in the dos partition.  To boot
> the pi as a cpu server instead of a terminal, change 'kernel=9pi' to
> 'kernel=9picpu' in config.txt, and copy cmdline-cpu.txt to cmdline.txt
>
> But I think the query was about a simple way to connect to your own
> plan 9 terminal with drawterm, without making it into a cpu server.
>
> > if it's a term
> > kernel, you can't drawterm to it;
>
> Actually that's not so.  For example, a quick-and-dirty method posted
> to 9fans by Luke Evans on 10 Dec 2012 (which applies to any Plan 9
> terminal, not just the pi):
>
>         echo 'key proto=p9sk1 dom=plan9 user=glenda !password=MYPASS'
> >/mnt/factotum/ctl
>         aux/listen -t tcp!*!ncpu /bin/cpu -R &
>
> This will only allow the terminal owner to connect.  For more general
> cpu-like service on a terminal, I use this script (which requires some
> prior setup with auth/changeuser to create the lib/keys file):
>
>         #!/bin/rc
>         auth/factotum -g 'user=miller dom=hamnavoe.com proto=p9sk1
> !password?'
>         rfork ne
>         echo auth server password:
>         auth/keyfs -p $home/lib/keys
>         aux/listen1 -t tcp!*!ticket /bin/rc -c '/bin/auth/authsrv -d $net'
> &
>         service=cpu aux/listen1 tcp!*!17007 /bin/exportfs -a&
>         service=cpu aux/listen1 tcp!*!cpu /bin/cpu -O &
>         service=cpu aux/listen1 tcp!*!ncpu /bin/cpu -R &
>
> Nowadays there's hardly any difference between cpu and terminal
> kernels, and in fact I would advocate combining the two.  Only a few
> lines of kernel source code need to be changed to allow it to decide
> at boot time whether to behave as a cpu server or terminal, depending
> on the setting of service= in plan9.ini.
>
>
>
>
> End of 9fans Digest, Vol 118, Issue 29
> **************************************
>

[-- Attachment #2: Type: text/html, Size: 4340 bytes --]