On 01/23/2014 06:40 PM, Rejy M Cyriac wrote:
On 01/23/2014 06:21 PM, poma wrote:
On 23.01.2014 07:40, Rejy M Cyriac wrote:
On 01/20/2014 10:28 AM, Ranjan Maitra wrote:
…
While I am here, I also wanted to know the answer to the question as to how the interfaces are decided in latter-day Fedoras: to elucidate, it used to be that eth0 and wlan0 and ppp0 were the interfaces. Now it seems to depend (and vary from one machine to the other). How do these get decided nowadays? Is there a generic way to get to the correct interface to use in programming? I am thinking of conky which requires the interface (from ifconfig, say) to set up signal strength, etc.
That would be biosdevname. It has been around for some time now.
$ rpm -q biosdevname package biosdevname is not installed ;)
Predictable Network Interface Names [1] $ man 7 udev
$ nmcli device status DEVICE TYPE STATE enp1s9 ethernet connected
poma
[1] http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... http://cgit.freedesktop.org/systemd/systemd/tree/src/udev/udev-builtin-net_i...
Interesting. I stand corrected. Thanks poma. :-)
Does that mean we cannot disable the feature by a kernel parameter any more ?
Hold on. But I do see it on my Fedora 20 system.
$ rpm -q biosdevname biosdevname-0.5.0-2.fc20.x86_64
- rejy (rmc)