[systemd-devel] Network Interface Names: solution for a desktop OS
Xen
list at xenhideout.nl
Tue Apr 12 01:37:48 UTC 2016
Xen schreef op 11-04-16 23:13:
> No. You are causing pain and suffering to millions of people.
>
> You (...) have not inquired with anyone whether they really wanted this.
>
> So you push something and then you say "oh, but you can opt out".
>
> So you place the burden on the user. It doesn't belong there.
>
> It's the same with email spam marketeers. They send you unsollicited
> spam, and then they say "You only have to press this link to opt out".
> Courts throw these practices out the window, in business it is not legal.
>
> It doesn't take much effort to think of a better scheme. But you don't
> think along, you only try to prove that my scheme can't work. And it is
> really not hard to imagine something that will work.
>
> But now I am going to test my interface name stability. See ya.
So I put it to the test.
I remove an addon card that has nothing to do with networking, and my
interface name has changed from enp3s0 to enp2s0, as predicted.
So the system is not stable AND it is not predictable.
FAIL.
THIS IS WORSE THAN BEFORE.
You people (the ones who have designed it) you can really in all
seriousness maintain you have done a good job?
I am sorry I have held back.
You have created a system that is stable across reboots (probably) BUT
now it is unstable with regards to any hardware change to the system.
Yes, blame my motherboard manufacturor.
Well I guess I have already silenced myself here. Sorry about that.
The trick to turn it off on the website doesn't work:
ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
So in order to do the remapping we have access to PCI, which is
unstable, and MAC which prevents redeployable images. We could map the
biosdev to a linear list or set of lists, which would solve most
problems for everyone, except if you use multiple USB devices, so you
just use a different scheme for that. Problem solved right.
Does anyone know how I can disable the renaming in some other way than
using kernel options? The above doesn't work. I cannot find the answer
anywhere.
Thanks.
More information about the systemd-devel
mailing list