Hi KatolaZ. Thank you for your answers.
KatolaZ - 10.05.18, 15:34: > On Thu, May 10, 2018 at 01:24:01PM +0200, Martin Steigerwald wrote: […] > > I´d like to switch over my backup VM first and wonder whether the > > network device with Devuan ASCII will be called "eth0" again. Thats > > totally fine with me, however I´d like to know before hand, so I can […] > the default in ASCII is to use the traditional names "eth0", "wlan0" > etc. You can change it if you want. Indeed it is. I am fine with that. So I have my first server, my backup server, with Devuan Ascii + OpenRC. :) I will be seeing how that works out in the next weeks. I understand that default names may cause clashes for device renaming via udev if several network drivers initialize network interfaces at the same time. However I don´t agree with the complexity of the new systemd naming scheme. In RHEL Networking Guide they have a whole chapter + sub chapter explaining this mess. I think something like en0, en1, en2, configurable with persistency might be nice, but just don´t overdo this. [1] Chapter 8. Consistent Network Device Naming, and no this is no joke https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/ 7/html/networking_guide/ch-consistent_network_device_naming Thanks, -- Martin _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
