From: William Gunnells <gunnells@gmail.com>
To: 9front@9front.org
Subject: Re: drawterm stuck
Date: Mon, 13 Jul 2020 15:15:40 -0700 [thread overview]
Message-ID: <FCD393D3-E8B6-4083-9A02-ED20008EAA99@gmail.com> (raw)
In-Reply-To: <D988D96E-F4AB-49F2-8C97-1D81DE10B650@gmail.com>
Is this just another dead channel?
> On Jul 13, 2020, at 12:12 AM, William Gunnells <gunnells@gmail.com> wrote:
>
> Does not work in OpenBSD either. Seems like the same problem
>
> Sent from my iPhone
>
>> On Jul 12, 2020, at 7:48 PM, William Gunnells <gunnells@gmail.com> wrote:
>>
>> I think I have this setup correctly in Qemu with service=cpu, and network setup correctly.
>> I run the following on my mac
>> ./drawterm -a tcp\!127.0.0.1\!9567 -h tcp\!127.0.0.1\!9567 -u glenda
>>
>> I get no errors and no prompt. I know that glenda is setup correctly. I know that its making a connection because if I do an fshalt -r I see an error in drawterm right away.
>>
>> ./drawterm: bad p9any domain
>> panic: ending
>>
>> can anyone give me a hint as to what is going on.
>>
>> this is in my plan9.ini
>> bootfile=9pc
>> bootargs=local!/dev/sdC0/fscache -a tcp!*!567
>> mouseport=ps2
>> monitor=vesa
>> vgasize=1024x768x16
>> service=cpu
>>
>> /lib/ndb/local
>>
>> all the usual stuff including
>> ip=127.0.0.1 sys=localhost dom=localhost
>> auth=cirno authdom=9front
>> ipnet=9front ip=10.0.2.0 ipmask=255.255.255.0
>> ipgw=10.0.2.2
>> dns=10.0.2.3
>> auth=cirno
>> dnsdom=9front
>> cpu-cirno
>> smtp=cirno
>> ip=10.0.2.15 sys=cirno dom=cirno.9front ether=525300123456
>> sys=cirno ether=525400123456
next prev parent reply other threads:[~2020-07-13 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 2:48 William Gunnells
2020-07-13 7:12 ` William Gunnells
2020-07-13 22:15 ` William Gunnells [this message]
2020-07-13 22:22 ` [9front] " Ori Bernstein
2020-07-13 22:44 ` Amavect
2020-07-13 22:24 ` [9front] " Kurt H Maier
2020-07-13 22:47 ` William Gunnells
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=FCD393D3-E8B6-4083-9A02-ED20008EAA99@gmail.com \
--to=gunnells@gmail.com \
--cc=9front@9front.org \
/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).