I will/should also follow the en0 convention.
I encounter some new problems now: ( My driver name is devn-oc.so)
mount -Tio-net -overbose devn-oc.so
mount: Can’t mount / (type io-net)
mount: possible reason: No such device or address
All I did was I just was switching between the tiny tcpip and the bigger one
in /etc/system/enum/include/net. But again i reverted back to ttcpip.
“Sean Boudreau” <email@example.com> wrote in message
Jalaja <> firstname.lastname@example.org> > wrote:
: I tried loading a network device driver devn.oc.so in the following
: # io-net &
:  626718
: # mount -Tio-net -overbose devn.oc.so
:  + Done
: # mount -Tio-net -oif=jal0:11.2 npm- ttcpip.so
: mount: can’t mount npm-ttcpip.so (type io-net)
: mount: Possible reason: resource busy.
You can only mount the stack once. If you’ve done everything right and
it’s already mounted, the stack will learn of your driver coming in
below it and create the interface in its tables (cat /proc/ipstats).
However, if this is an ethernet driver, I’d stick to the ‘en’ naming
convention (lose the jal0). If it isn’t, you have more than a
driver to write.
: And also, could anyone please tell me what are the debugging tools
: to debug the Network PCI driver code.