From: thinktankworkspaces@gmail.com
To: 9front@9front.org
Subject: another CPU
Date: Sun, 2 Aug 2020 23:13:46 -0700 [thread overview]
Message-ID: <CA3E6054DB5AFD24F4EBAC845C7D43F1@gmail.com> (raw)
Rather than doing another 9front install to native install. Can't I just
use the 9front.iso and pick tcp from the menu give it
user[glenda]:
fs address is? 192.168.1.172
auth address is? [192.168.1.172]
srv: dial tcp!192.168.1.172!564: connection refused
mount: can't open #s/boot: '#s/boot' file does not exist
mount -c #s/boot /root: mount 176: open
I kind of feel like i'm missing some info here. Do I just put another
entry in my cpu/auth
sys=cpufoo dom=foo.yoda ether=123456789 ip=192.168.1.100
bootf=/386/9bootpxe
I'm guessing it won't get to it because booting from the iso it doesn't
know anything about the network because no network stack has been
setup? This is why you kind of need a full install so you can setup a network stack and give it the same address you specify
on the cpu/auth as another cpu?
I kind of feel like more is also missing on the fs side like a mount
point or something I must have skipped. my CPU/Auth is on Qemu
and I thought rather than change what I have I could create another
cpu for speed/performance. And learn at the same time on how to get
another node on the grid?
next reply other threads:[~2020-08-03 6:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 6:13 thinktankworkspaces [this message]
2020-08-03 6:47 ` [9front] " hiro
2020-08-08 5:44 ` thinktankworkspaces
2020-08-08 8:48 ` Ethan Gardener
2020-08-08 17:57 ` thinktankworkspaces
2020-08-08 18:45 ` thinktankworkspaces
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=CA3E6054DB5AFD24F4EBAC845C7D43F1@gmail.com \
--to=thinktankworkspaces@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).