From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@9fans.net From: Richard Miller <9fans@hamnavoe.com> Date: Fri, 21 Feb 2014 10:28:23 +0000 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Setting 9pi Start State / Drawterm to 9pi Topicbox-Message-UUID: bcce5c96-ead8-11e9-9d60-3106f5b1d025 > 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.