Are you using any virtual ethernet device with 9vx? Because if you are
not, 9vx will use the ip stack of the host. In this case, 9vx /net
will include some files, but ipselftab is not one of them.
You will also get errors if you try to run ndb/dns or ip/ipconfig from
a 9vx booted with 9atom or plan9. The difference is that they do not
try to start the network by default.
You could comment a few lines in termrc to avoid the error. Networking
should be working fine.
--
- yiyus || JGL .
i dont have a linux installation to test right now...
as you describe it, seems to be mostly a matter of detecting 9vx and not
doing ip/ipconfig and dns at all because 9vx provides these files for you
in #I right?
--
cinap
A solution would be to test if $sysname is 'vx32' AND there is no
/net/eth0. You probably want to start the network if you are using
virtual ethernet devices.
I don't have a 9front tree in my 9vx machine just now, but I will try later.
> A solution would be to test if $sysname is 'vx32' AND there is no
> /net/eth0. You probably want to start the network if you are using
> virtual ethernet devices.
$sysname may be set before any scripts are run. 9vx can use some
equivalent of plan9.ini.
You are right, an user could overwrite the value of sysname. A better
test to know if we are inside 9vx may be to check for '#Z'
Let's just run 8l 10 times and see if it crashes at once point ...