From mboxrd@z Thu Jan 1 00:00:00 1970 X-Received: by 10.66.156.227 with SMTP id wh3mr26263461pab.23.1423048600597; Wed, 04 Feb 2015 03:16:40 -0800 (PST) X-BeenThere: voidlinux@googlegroups.com Received: by 10.140.41.104 with SMTP id y95ls65330qgy.19.gmail; Wed, 04 Feb 2015 03:16:40 -0800 (PST) X-Received: by 10.140.91.104 with SMTP id y95mr38978qgd.8.1423048600382; Wed, 04 Feb 2015 03:16:40 -0800 (PST) Date: Wed, 4 Feb 2015 03:16:40 -0800 (PST) From: Stefan Beyer To: voidlinux@googlegroups.com Message-Id: Subject: I want my eth0 back MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_238_1222986486.1423048600125" ------=_Part_238_1222986486.1423048600125 Content-Type: multipart/alternative; boundary="----=_Part_239_1167884765.1423048600125" ------=_Part_239_1167884765.1423048600125 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit To have the ethernet devices called enp3s0 and enp5s0 (on my machine), rather than eth0 and eth1, is annoying. Appending *biosdevname=0 net.ifnames=0* to the kernel command line improves quality of life. Some solutions I feel are out of proportion to the problem they supposedly solve; often they introduce new ones. Imagine a help page, telling a beginner to dhcpcd rather than simply dhcpcd eth0 ------=_Part_239_1167884765.1423048600125 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
To have the ethernet devices called enp3s0 and enp5s0 (on my machine), rather than eth0 and eth1, is annoying.
Appending biosdevname=0 net.ifnames=0 to the kernel command line improves quality of life.

Some solutions I feel are out of proportion to the problem they supposedly solve; often they introduce new ones.
Imagine a help page, telling a beginner to dhcpcd <insert_your_device_name> rather than simply dhcpcd eth0



------=_Part_239_1167884765.1423048600125-- ------=_Part_238_1222986486.1423048600125--