Re: [9front] drawterm stuck

[William Gunnells <gunnells@gmail.com>]

I don’t get a prompt or anything. I can however type on the screen. But commands don’t work. I would send a screenshot but I think that is filtered by the list server or something. I know that I make a connection but nothing is in the /sys/log/auth except for when I added glenda a few days ago using auth/changeuser

when I do an fshalt -r it gives an error in drawterm window
./drawterm: bad p9any domain
panic: ending

This is just a base install using 9front documentation online. I guess I did the following:
1. run the qemu install -> this seemed to be straightforward
2. initially i didn’t mess with compiler because I thought the default kernel would be fine. I did give up and compile this thinking maybe I’m missing something. 
3. change /n/9fat/plan9.ini -> service=cpu
4. change /lib/ndb/local -> the details of that would be in a previous thread. But in short its just the ip’s I found from ndb/query 
which were 10.0.2.0 etc…
5. I was not sure if I need to change authdom. I left it 9front I guess I could change it to whatever I wanted. 
6. I left everything cirno
7. as soon as I reboot i believe I had bad nvram. i did authid glenda and authdom 9front sec key some_password and password some password
Really everything is the same password because I didn’t understand that part
i made sure to have bootargs=local!/dev/sdXX/fscache -a tcp!*!564

Honestly that should be it
I checked netstat -na | grep -i listen | grep tcp which shows:
127.0.0.1.9567
127.0.0.1.17010

and i run drawterm -a tcp\!127.0.0.1\!9567 -h tcp\!127.0.0.1\!9567 
It seems I needed to put escape the ! and I was not sure if I needed a different port for -a 17010 neither of them seem to work
no errors. 

I’m trying to think if I miss anything. firewall is off. Drawterm compiled fine on mac. 

I didn’t think i needed to mess with any other filer like /rc/bin/cpurc ? 
Back in the old days you had to mess with a lot of files just to get things working. Honestly I forgot how to use this. 

here is something I just noticed in /sys/log/listen

started on tcp
giving up on tcp!*!567: (**

what’s up with that and why?




> On Jul 13, 2020, at 3:24 PM, Kurt H Maier <khm@sciops.net> wrote:
> 
> On Sun, Jul 12, 2020 at 07:48:42PM -0700, William Gunnells wrote:
>> 
>> I get no errors and no prompt. 
> 
> What prompt are you expecting to get?
> 
> khm