Network connection for NetBSD under Fusion

[Paul Newhouse]

Apologies this is more a Fusion/OS X question than a NetBSD
question.

I can create a NetBSD boot CD and boot it under Fusion but, I
can't get connected to the network to install with FTP. There
doesn't seem to be any device available. Can someone give me
a heads how to get a network device exported into NetBSD from
Fusion/OS X?? The VM Tools options don't seem to do it even
though they kind of sound like they will.

Also, I noticed picking "Other" as the guest OS doesn't have
any VM Tools. I tried FreeBSD that has tools but, still no
network. What is the right/better choice of OSes for the tools
to work for NetBSD?

TIA,
Paul N.

[James K. Lowden]

Post by Paul Newhouse
There
doesn't seem to be any device available. Can someone give me
a heads how to get a network device exported into NetBSD from
Fusion/OS X??

As you know, NetBSD is booting on a machine, probing it to find out what
the "hardware" has that it can use. The first place to look is in the
dmesg, to see what devices it found. (Perhaps you know that; it wasn't
clear from your message.)

Poking around, it looks like you might be able to use le(4).

http://pubs.vmware.com/guestnotes/wwhelp/wwhimpl/js/html/wwhelp.htm

The MS-DOS notes say to use "Advanced Micro Devices PCNET Family
(NDIS2/NDIS3) Ethernet driver"

http://www.netbsd.org/support/hardware/pci.html includes:

Advanced Micro Devices Am79c970 PCnet-PCI and other members of the
PCnet-PCI family (le(4))

HTH....

--jkl

[Paul Newhouse]

Post by James K. Lowden

There doesn't seem to be any device available. Can someone give me
a heads how to get a network device exported into NetBSD from
Fusion/OS X??

As you know, NetBSD is booting on a machine, probing it to find out what
the "hardware" has that it can use. The first place to look is in the
dmesg, to see what devices it found. (Perhaps you know that; it wasn't
clear from your message.)

Thanks, I did know that just didn't think of it.

Post by James K. Lowden
Poking around, it looks like you might be able to use le(4).

found it pcn(4)

A little more screwing around and I can probably get X working *8^)

Paul N.

Post by James K. Lowden
http://pubs.vmware.com/guestnotes/wwhelp/wwhimpl/js/html/wwhelp.htm
The MS-DOS notes say to use "Advanced Micro Devices PCNET Family
(NDIS2/NDIS3) Ethernet driver"
Advanced Micro Devices Am79c970 PCnet-PCI and other members of the
PCnet-PCI family (le(4))
HTH....
--jkl