I *like* eth0..n (I'd like net0..n better). And I *can't* ask what
eth0 and eth1 are, by the way, but I should be able to (Jeff Garzik
has proposed an extension to ethtool to help out this lack, but it's
not in Linux today, and needs concrete implementation anyway).
But that's not my point. I'm *not* proposing that we exchange eth0
for geographic names. I'm suggesting, though, that the location of
the device is *not* meaningless, because it's the physically-located
RJ45 socket (or whatever) that I have to connect a particular cable
to. Sure, no big deal for systems with a single connection, but it
becomes a real pain when you've got a dozen, which is a reasonable
number for some network-infrastructure functions (eg firewalls).
When I ifconfig one of a collection of interfaces, I'm very much
talking about the specific physical interface connected via a
specific physical cable to a specific physical switch port.
Bob Glamm is on the right track with
At 5:35 PM -0500 2001-05-15, Bob Glamm wrote:
> # start up networking
> for i in eth0 eth1 eth2; do
> identify device $i
> get configuration/config procedure for device $i identity
> configure $i
...it's just that right now the connection between eth* and its
physical identity isn't made.
-- /Jonathan Lundell. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/