Comments on Matt's blog: Idea #27250: Auto eth0 isn't very user friendly. M...

@winniemiel05, Yup, this was what mpt was referri...

2011-04-22T10:43:30.993-04:00

@winniemiel05,

Yup, this was what mpt was referring to in his comment ;)

Is there any link with this spec ? https://wiki.ub...

2011-04-21T15:13:20.660-04:00

Is there any link with this spec ? https://wiki.ubuntu.com/Networking

That's how it works in the nm-applet menu, exc...

2011-03-25T12:35:29.653-04:00

That's how it works in the nm-applet menu, except device names (model and such) are used instead of interface name when there is more than one device. I mention changing this to interface names for brevity.

I did not know there was a Brainstorm item for thi...

2011-03-25T10:32:25.323-04:00

I did not know there was a Brainstorm item for this. I have already specified that a wired connection should be labelled “Wired Connection” if there’s only one, or “Wired Connection (eth0)” in the rare case that there is more than one.

Yeah, I tested this on my system... Not sure it...

2011-03-24T18:15:27.284-04:00

Yeah, I tested this on my system... Not sure it's quite what I expected though, as here it returns pci1p2; although it's a laptop with only one ethernet port on the back (Dell Vostro V130).

Regardless, I think this isn't so much of an issue, as whatever device name that is available to NM via the kernel or udev is what would be presented as an "interface name". In this sense, it's actually also helping our users have clear names for the actual port this uses. It's the whole purpose of biosdevname.

biosdevname is coming in Natty so 'eth0' m...

2011-03-24T17:42:50.211-04:00

biosdevname is coming in Natty so 'eth0' may really be something more hardware-specific soon.

https://bugs.launchpad.net/ubuntu/+source/biosdevname/+bug/723870

That sounds like a great topic for a spec and disc...

2011-03-24T13:04:03.611-04:00

That sounds like a great topic for a spec and discussion at UDS.