Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

On 09.01.2016 12:41, Anto wrote: > Hello Everybody, > > I have been indoctrinated myself that everything come from systemd gang > are stupid and bad. After reading the above link and some other pages > from systemd supporters, I think I might have to change my mind about > that Predictable Network

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

Anto writes: [...] > It turned out that the eth0 interface was changed to ens3, due to the > implementation of Predictable Network Interface Names > (http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames). > I > can change everything which contain

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

Rainer Weikusat writes: [ethX reordering] > in the relative rare case that more than one network driver actually > has to be loaded, if the order in which the drivers call their init > routines changes. There's nothing which would stop "driver loading > support

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

Jude Nelson writes: >> Isn't the initial identification of network adapters and assignment > originally handled by the Kernel or is this another urban myth that I have > mistakenly hung on to? > > Yes--network interfaces are given a monotonically-increasing sequence > number as

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

Hi, As I am reading this discussion a temptative thought is coming to my mind which is: what can Devuan do to avoid this new device naming scheme breaking breaking software that rely on the old naming convention? As I wrote in my earlier reply, I am ready to offer my help in this, provided the

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

Stephanie Daugherty writes: > Having dealt with systems with half a dozen interfaces in the past there's > a very small number of cases where it even matters, but when it does, it > can be a huge inconvenience either way. Namely, "it matters" because Dell boxes with more

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

Slackware is hard work when you have been used to the ease of debian for so many years... Eventually it all worked OK until one particular bit of music composition software I like to use could only be found in Slackbuilds, and it would not install even after I did some editing of the scripts.

[DNG] Predictable Network Interface Names - Stupid or good idea?

Hello Everybody, I have just rented a KVM VPS. I started with Debian squeeze, pin everything related to systemd to -1, then upgraded to Debian wheezy. After I upgraded udev to version 220 using eudev, I could not connect to my VPS any more after reboot. This has never happened on my other

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

On Saturday, 9 de January de 2016 11:41:27 Anto escribió: > Hello Everybody, > > I have just rented a KVM VPS. I started with Debian squeeze, pin > everything related to systemd to -1, then upgraded to Debian wheezy. > After I upgraded udev to version 220 using eudev, I could not connect to > my

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

On 09/01/16 19:44, shraptor wrote: On 2016-01-09 19:17, Anto wrote: On the topic. It would be quite interesting how vdev will be (or is) managing this network interface naming assignment. Do you have any comment on this, Jude? vdev uses by default old naming convention but has a file called

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

It sounds like a good idea in theory, but I see no reason eth0, eth1, wlan0, wlan1, etc should change. It could be as simple as deciding which of those to use based on some information from the device in the case there is more than one NIC. Changing that for no good reason is clearly a bad

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

On 2016-01-09 19:17, Anto wrote: On the topic. It would be quite interesting how vdev will be (or is) managing this network interface naming assignment. Do you have any comment on this, Jude? vdev uses by default old naming convention but has a file called /etc/vdev/ifnames.conf where you can

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

On 9 Jan 2016, at 17:02, Stephanie Daugherty wrote: > 5 - have udev issue manual (admin-chosen) persistent names by mac address Which, IMO, is the most logical option. Lets face it, how often do people actually change hardware ? And when hardware is changed, it's a

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

On 09/01/16 01:44 PM, shraptor wrote: On 2016-01-09 19:17, Anto wrote: On the topic. It would be quite interesting how vdev will be (or is) managing this network interface naming assignment. Do you have any comment on this, Jude? vdev uses by default old naming convention but has a file

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

On Sat, Jan 09, 2016 at 09:19:33PM +0100, Anto wrote: > > On 09/01/16 19:44, shraptor wrote: > >On 2016-01-09 19:17, Anto wrote: > > > >>On the topic. It would be quite interesting how vdev will be (or is) > >>managing this network interface naming assignment. Do you have any > >>comment on this,

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

On 09/01/16 15:42, Steve Litt wrote: [snip] Seriously, now is the time for everybody to learn the ip command. It's ugly. It's poorly documented. But it's very, very powerful, and enables you do do just about anything in networking. SteveT Steve Litt January 2016 featured book: Twenty Eight

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

Having dealt with systems with half a dozen interfaces in the past there's a very small number of cases where it even matters, but when it does, it can be a huge inconvenience either way. Their (for once, rational) argument is that Interface names of existing interfaces should never change by

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

> Isn't the initial identification of network adapters and assignment originally handled by the Kernel or is this another urban myth that I have mistakenly hung on to? Yes--network interfaces are given a monotonically-increasing sequence number as they are enumerated (e.g. the X in ethX and

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

Forwarded to dng On 10/01/2016, Edward Bartolo wrote: > On 09/01/2016, shraptor wrote: >> On 2016-01-09 19:17, Anto wrote: >> eth0 mac XX:XX:XX:XX:XX:XX >> wlan0 mac XX:XX:XX:XX:XX:XX > > I think, > > this is a good idea to implement a package that creates

Re: [DNG] Predictable Network Interface Names - Stupid or good idea?

On 10/01/16 18:48, Edward Bartolo wrote: > Forwarded to dng > > On 10/01/2016, Edward Bartolo wrote: >> On 09/01/2016, shraptor wrote: >>> On 2016-01-09 19:17, Anto wrote: >>> eth0 mac XX:XX:XX:XX:XX:XX >>> wlan0 mac XX:XX:XX:XX:XX:XX >> >> I think, >> >>