Just FYI, I wanted to verify that this works and I just did.
Having a 9vx function as the fs for an Ovaro (TI OMAP)
sudo ~/src/plan9/vx32/src/9vx/9vx -r ~/src/9vx-0.12/
The sudo is important.
Then in the 9vx instance:
aux/listen1 -v tcp!*!564 /bin/exportfs -s
Then I boot the Ovaro:
Filename '9beagletxt'.
Load address: 0x80310000
Loading: #################################################################
#########################
done
Bytes transferred = 1315056 (1410f0 hex)
Overo # tftpboot 80300000 0015c928d6a1
smc911x: detected LAN9221 controller
smc911x: phy initialized
smc911x: MAC 00:15:c9:28:d6:a1
Using smc911x-0 device
TFTP from server 192.168.2.1; our IP address is 192.168.2.5
Filename '0015c928d6a1'.
Load address: 0x80300000
Loading: T #
done
Bytes transferred = 207 (cf hex)
Overo # go 80310000
and then it all comes up with prompts:
filesystem IP address[no default]: 192.168.2.1
authentication server IP address[no default]: 192.168.2.1
bad nvram key
bad authentication id
bad authentication domain
authid: bootes
authdom: YOURNAMEHERE
secstore key:
password:
can't write key to nvram: jmk added reentrancy for threads
version...time...
Password:
Confirm password:
192.168.2.5 Jan 15 15:03:21 cron for upas owned by rminnich
192.168.2.5 Jan 15 15:03:21 cron for root owned by rminnich
192.168.2.5 Jan 15 15:03:21 cron for sys owned by rminnich
init: starting /bin/rc
192.168.2.5#
The point being that 9vx is a perfectly capable way to have an fs
for all your service needs :-)
Thanks to Geoff for his infinite patience with my questions ...
ron
