Fedora 15, new and exciting plans (biosdevname)

Chris Adams cmadams at hiwaay.net
Tue Nov 16 14:48:09 UTC 2010

Once upon a time, Jon Masters <jonathan at jonmasters.org> said:
> I've had a few off-list conversations with various community members
> about this. One thing that came up was that the alternative namespace is
> necessary,

I'm not sold on this, but:

> but also that "lom" is a sub-optimal choice. One idea that
> did come up was simply to call them "net" (net0, etc.) or perhaps "net"
> followed by another letter like "netm" or something.

If you are adding a letter, stick with tried-and-true "eth".

Also, if your intention is to name the motherboard NICs, don't start
with 0 - I haven't seen a motherboard that does.  If you are trying to
distinguish the motherboard NICs and make them easier to ID, follow what
the motherboard makers use (1, 2, ..., not 0-based).

> To avoid
> bikeshedding this to death though, I think Matt's "lom" naming is fine
> for the moment unless we happen to all agree on something else.

There are legitimate concerns with "lom" being an established
abbreviation already associated with built-in NICs, so it is hardly
"bikeshedding" to disagree with that.

In any case, is this going to be something that can be disabled easily?
We have something like 18 years of Linux networking history that says
ethernet devices are "eth[0-9]+", and I'm not really interested in
auditing all the tools and scripts I use to make sure they handle
something different at this time.

Chris Adams <cmadams at hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.

More information about the devel mailing list