Re: Network Cards

["Dines, Eric" <Eric.Dines@iluka.com> writes:]

>Can you forward to me the correct config. files to get the network card
>happening please?
>autoexec.net
>inittab

They should be in /vsta/etc.

>How close a clone to a 'true' NE2000 should the card be? I have a Kingston
>ISA NE2000 compatible...I assume that should be OK.

Most generic NE2000 cards have worked OK for me. The only hard part is
knowing what the I/O base and IRQ are. If they're soft configurable, you
have to grit your teeth and boot a Mickeysoft OS to set up the cards.

>Any pointers on getting the networking functional!?!%

Edit /vsta/etc/autoexec.net. Mostly set up your IP address, hostname,
domain name, and a domain server.

Then run "/vsta/boot/ne <base>,<irq>" for instance: "ne 0x300,3 &"
(ampersand, i.e., run in background). Once the server prints out a
reasonable MAC address for your card (found it OK, it'll take it about a
second), then run "net" from /vsta/srv/srv/ka9q. By default it should use
/vsta/etc/autoexec.net, and by default the ethernet driver should be found
OK by the "attach eth eth0 1500" line of the autoexec.net.

You should now be at the prompt for ka9q, with TCP/IP up. You should be
able to "ping <addr>" and get a response showing how much time it took.
From here you'll need to start referring to the source of ka9q to see all
the commands which are available. If you log into another VSTa console as
root, you should be able to run the "telnetd" command in the ka9q/cmd
subdirectory, and once that's running, you should be able to telnet into
the system and log in.

You can also run ka9q/cmd/proxyd, after which if you set up ka9q on a
second system, you should be able to do "mount //fs/root@<addr> /rem",
after which the remote's root filesystem is available under /rem. You
could also do "mount //fs/proc@<addr> /proc2", and then kill remote
processes by "echo -n kill > /proc2/<pid>/note". proxyd needs to run on
the system you're mounting *from*.

FYI, on the side, I've been hacking on getting VSTa booting under the x86
CPU emulator "bochs". I can boot up the microkernel, console, and testsh,
and am looking at a bug in bochs' handling of interrupts versus "rep insw"
for transferring multiple sectors from IDE. I'll hopefully get a little
more time to fix it up, submit the patches back to the author, and then
this'll be a nice extra option for doing VSTa hacking without having to
deal with disk partitions (or even rebooting your hardware!).

Andy Valencia
Received on Fri Sep 24 19:36:14 1999