9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Amavect <amavect@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Re: drawterm stuck
Date: Mon, 13 Jul 2020 17:44:46 -0500	[thread overview]
Message-ID: <af4c8cf2-8091-c8e6-6e13-e9496344e73c@gmail.com> (raw)
In-Reply-To: <FCD393D3-E8B6-4083-9A02-ED20008EAA99@gmail.com>

Will,

Have patience, I was typing this out...

First, try running netaudit(8) and see if it complains about anything.
Having the -a announce string in bootargs is probably unnecessary since 
you're trying to run a cpu server, not a disk file server. Remove that flag.
Consider changing bootargs into nobootprompt, per the plan9.ini(8) man page.
If possible, setting up a bridged network connection makes life a lot 
easier than using NAT and connecting to localhost. Bridged gives the VM 
its own IP address, as opposed to sharing it with the host.

My ndb/local looks like this:

sys=cirno ether=000c296361f3
	ip=10.0.0.104
	dom=grove

ipnet=grove ip=10.0.0.0 ipmask=255.255.255.0
	ipgw=10.0.0.1
	dns=10.0.0.1
	auth=pine authdom=grove

netaudit only complains about grove not having a dot. That's fine.
Per http://fqa.9front.org/fqa7.html#7.4.1
auth/debug only works for dp9ik. That's good.
Typing in my password that I set with auth/changeuser works.
Per http://fqa.9front.org/fqa7.html#7.4.2
auth/asaudit checks that auth/wrkey was set up right.
3 GOODs and 1 key read in AES format.
Per http://fqa.9front.org/fqa7.html#7.3.2

I connect with
drawterm -h 10.0.0.104 -a 10.0.0.104 -u glenda

Thanks,
Amavect


  parent reply	other threads:[~2020-07-13 22:44 UTC|newest]

Thread overview: 12+ 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
2020-07-13 22:22     ` [9front] " Ori Bernstein
2020-07-13 22:44     ` Amavect [this message]
2020-07-13 22:24 ` [9front] " Kurt H Maier
2020-07-13 22:47   ` William Gunnells
2020-07-13 23:02 [9front] " William Gunnells
2020-07-14  0:21 ` hiro
2020-07-14  0:25 ` Amavect
2020-07-14  0:28   ` hiro
2020-07-14  0:34     ` hiro

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=af4c8cf2-8091-c8e6-6e13-e9496344e73c@gmail.com \
    --to=amavect@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).