James Carlson wrote:
Dick Davies writes:
On 02/06/06, James Carlson <[EMAIL PROTECTED]> wrote:
UNIX admin writes:
One of the rare things I like is how Linux solved this: regardless
of the networking HW, all interfaces are named "eth[0-N]", for
example eth0, eth1, ... , ethN.
Linux isn't the only one to do this. AIX, BSD, and other variants do
it as well.
BSD doesn't. At least the 3 free ones name their interfaces after the hardware
(ne0, ipw0, wi0, etc).
My mistake. I'd _thought_ I'd seen that behavior ("net0", "net1") on
FreeBSD at one point due to the "ifconfig name" option. Perhaps that
feature no longer exists.
However, Linux does this ("eth0"), and AIX does ("en0" and "et0"), as
does HP/UX ("lan0"). It's not uncommon.
Nit there are more than 3 freely available BSD systems now (there is
also PC-BSD, DragonFly BSD and Darwin). Darwin is a BSD derivate and it
does use a hybrid of the two approaches - or so it appears to me.
On Darwin/MacOS X systems it appears that your ethernet devices are all
named en0 (my wired interface), en1 (my wireless interface). lo0 is
loopback. I also have fw0 which is for IP over IEEE 1394 believe. I
also see gif0 - generic tunnel interface and stf (the 6to4 tunnel
interface). All of those interfaces are plumbed on my system just now
but only en0 has an address.
--
Darren J Moffat
_______________________________________________
opensolaris-discuss mailing list
[email protected]
