9front - general discussion about 9front
 help / color / mirror / Atom feed
From: William Gunnells <gunnells@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] drawterm stuck
Date: Tue, 14 Jul 2020 23:05:38 -0700	[thread overview]
Message-ID: <8C8DBC11-DFFD-4408-B3C7-3942EA88DC04@gmail.com> (raw)
In-Reply-To: <5452a71f-4964-2374-74c1-8a279eb010cd@gmail.com>

Okay I got it to work in virtual box. I struggled with qemu and tap/bridge to no end. 

I remember that virtual box handled bridge a little differently. So I gave it a shot and boom up and running. 

I do have OpenBSD on my laptop perhaps I can qemu working with tap and bridge.  But honestly I’m not sure what I want to do
in the grand scheme of things. 

I think it would have worked without the bridge but the qemu string would have been long because I think I needed to open up a range of ports for ingress and egress.

Thanks for all the help

Does httpd work and is it fast I was thinking of running this in AWS on a custom AMI at some point

Just looking for something different and something that could potentially be fast. I plan on serving controversial pages.

Its just hard to find bench marks but more importantly I didn’t want this to be the usual nix distributions. 



> On Jul 13, 2020, at 5:25 PM, Amavect <amavect@gmail.com> wrote:
> 
>> oh my net audit show everything seems to be fine except
>> ether=3D525400123456 does not belong to any network interface
>> no fs=3D entry  (needed for pls boot)=20
> Refer to my example from my last message and modify to your own setup.
> You have duplicate sys=cirno lines, the cpu= line is not a '=', and your dom should be 9front, not cirno.9front.
> Your ipgw and dns is your router's ip address, which is probably 10.0.2.1
> No fs is fine if you're not planning to need tls boot.
> 
>> auth server seems to be fine i think it reads
>> someone is listening on port 567
> That's good. The cpu server is trying to listen for connections.
> Clearly not succeeding, though.
> 
>> auth/asaudit shows 1 problem
>> BAD: key in keyfs does not match nvram
>> trying nvram key for 9front@glenda with factotum
>> GOOD: key in factotum matches nvram
> I'm guessing you didn't set up glenda's password with auth/changeuser
> Or, if you did, the key didn't match. Run auth/wrkey again.
> Refer to the fqa links that I had put in my last message.
> 
> Thanks,
> Amavect



  parent reply	other threads:[~2020-07-15  6:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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
2020-07-15  6:05   ` William Gunnells [this message]
2020-07-15  8:15     ` [9front] " hiro
2020-07-15 13:21       ` Steve Simon
2020-07-15 13:43         ` hiro
2020-07-15 17:02           ` William Gunnells
2020-07-15 17:13             ` Kurt H Maier
2020-07-15 17:43               ` hiro
2020-07-15 19:10             ` ori
2020-07-17 10:51             ` Ethan Gardener
  -- strict thread matches above, loose matches on Subject: below --
2020-07-13  2:48 William Gunnells
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=8C8DBC11-DFFD-4408-B3C7-3942EA88DC04@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).