multiple ethernet interfaces, naming

[G. David Butler gdb@dbSystems.com]

>From: presotto@plan9.bell-labs.com
>
>For brazil, jmk got multiple ether interfaces working.
>You might as well make things compatible since we
>should eventually release this cruft.

I don't think that matters any more.  My Plan9 will be
sooo different by then that it won't do me any good.
I'm even changing 9P, but more on that later.  I'm
really tired of hearing about brazil.

>                                       They bind as
>'#l0', '#l1', '#l2', ...  The directory names
>are ether0, ether1, ether2, ...

That is consistent with #w[0-6] for sd[0-6]partition, etc.

Lets say you add FDDI.  Do you do #l3 and ether3 is
really fddi, or does #l3 get fddi0?  Would it not be
better to do #lfddi0?  Or would you do #F0 (whatever
letter you choose for fddi) for fddi0?  See below.

>an ls of /net yields
...
>/net/gre

What is this, another brazil thingy?

>In plan9.ini we have
>
>ether0=type=elnk3 port=0xE000
>ether1=type=elnk3 port=0x0300

So, if you have:

ether0=...
ether1=...
fddi0=...
atm0=...
atm1=...

Should each name have a different #.? scsi0=... does.  Or
do we do:

ether0=type=elnk3 ...
ether1=type=decfddi ...

Then #l[0-9] works.

Thanks.

David Butler
gdb@dbSystems.com