Re: [9front] another CPU

[thinktankworkspaces@gmail.com]

[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]

So I have it working. But maybe i'm missing something. Much
of the documentation talks about

cd /cfg; mkdir $sysname; dircp example $sysname

This seems old and deprecated. I'm not really sure what we
are supposed to have in /cfg/$sysname

I tried copying cpurc and termrc and booting with each of them
the results were strange and buggy. However I made not changes
to those files as well. 

The booting part was the tricky part. I did have two dhcp server
running. One for my internet and one for the CPU/Auth.

ipnet=yoda ip=192.168.1.0 ipmask=255.255.255.0
	ipgw=192.168.1.1
	dns=8.8.8.8
	auth=192.168.1.172
	dnsdom=yoda
	authdom=yoda
	fs=192.168.1.1
	cpu=foo
	smtp=foo

sys=localhost dom=localhost ip=127.0.0.1
sys=foo dom=foo.yoda ether=525400123336 ip=192.168.1.172
sys=cirno dom=cirno.thinktank ether=080027f9ec98 ip=172.27.0.67
#sys=cpubar dom=foo.yoda ether=525400124242 ip=192.168.1.42 bootf=/386/bootx64.efi
sys=cpubar dom=foo.yoda ether=525400124242 ip=192.168.1.42

I did have to make a change to cpubar below. evidently bootx64.efi does not work. 

When I do manage to boot cpubar it takes the name of foo. However
the file system is different as expected. 

netaudit
checking this host's tuple:
	ip=192.168.1.42 looks ok
	dom=foo.yoda looks ok
	no ether entry
checking the network tuple:
	we are not in an ipnet, so looking for entries in host tuple only
	ipgw=192.168.1.1 looks ok
	dns=8.8.8.8 looks ok
	auth=192.168.1.172 looks ok
	fs=192.168.1.1 looks ok
checking auth server configuration:
	we are not the auth server 192.168.1.172
	if this is a mistake, set auth=foo or auth=foo.yoda
	run auth/debug to test the auth server

But i don't see a default mount for the cpu to copy data over 
/n/other/ is the same for both 

When I look back the only thing I did or the only change I made is one
line to /lib/ndb/local and an install on another system. It seems the less
I do the more results as opposed to following a lot of the old 
documentation. But I still seem to be missing a few things. 

Any thoughts?

[-- Attachment #2: Type: message/rfc822, Size: 5411 bytes --]

From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] another CPU
Date: Mon, 3 Aug 2020 08:47:45 +0200
Message-ID: <CAFSF3XPoMzizmFY7Uss=mYWHFMkmxSqjri3MjqHyF5iK3U90JQ@mail.gmail.com>

make sure you're not running 2 dhcp servers.
you need to setup 9front as cpu server, fileserver and dhcp server.
plan9 dhcp server will give above ip=192.168.1.100 to any PC that
requests an IP if they have 123456789 ethernet address.
i don't see any ip subnet, network info above, so perhaps the local
routes are missing, too.