Void Linux discussion
 help / color / mirror / Atom feed
* I want my eth0 back
@ 2015-02-04 11:16 Stefan Beyer
  2015-02-04 12:03 ` Juan RP
  0 siblings, 1 reply; 2+ messages in thread
From: Stefan Beyer @ 2015-02-04 11:16 UTC (permalink / raw)
  To: voidlinux


[-- Attachment #1.1: Type: text/plain, Size: 445 bytes --]

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




[-- Attachment #1.2: Type: text/html, Size: 485 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: I want my eth0 back
  2015-02-04 11:16 I want my eth0 back Stefan Beyer
@ 2015-02-04 12:03 ` Juan RP
  0 siblings, 0 replies; 2+ messages in thread
From: Juan RP @ 2015-02-04 12:03 UTC (permalink / raw)
  To: voidlinux


[-- Attachment #1.1: Type: text/plain, Size: 232 bytes --]

This has been udev's default for a long while... personally I find the 
interface naming good enough.

If you don't like this, use net.ifnames=0 in the kernel cmdline via 
/etc/default/grub, not sure what I can do about it :-)

[-- Attachment #1.2: Type: text/html, Size: 255 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-02-04 12:03 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-04 11:16 I want my eth0 back Stefan Beyer
2015-02-04 12:03 ` Juan RP

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).