Quoting Craig Sanders ([email protected]):
> You can't rely on the kernel assigning any name to any particular network
> interface - same as you can't rely on a hard disk getting the same /dev/sdX
> name on every reboot.
For the record, over decades of administering Linux servers, I've just
never had a problem with (by which I mean, not encountered) either
network interfaces or hard disks / SSDs getting a new device name upon
reboot. So, I think this risk is massively overstated.
I'd speculate that it primarily relates to the effect of hardware
changes (adding/removing internal hardware) and, most of all,
hotpluggable devices such as (most notably) USB. And yes, _of course_
USB devices change device nodes upon reuse. ;->
I vaguely recall that a system swapped eth0 and eth1 when replacing a
2.0.x kernel with a 2.2.x kernel (or 2.4 to 2.6, or something like
that). Which didn't surprise me much, and is why God made rc files
editable.
And ifrename is cool.
So, in short, I greatly doubt there's a significant need, except for
people highly reliant on USB for critical infrastructure (you poor
sods!) to have the Freedesktop.org Predicatble Network Interface Names
kludge^W scheme, nor the Freedesktop.org
/dev/disk/by-{path,id,label,partlabel,partuuid,uuid} scheme, either.
In my experience, the Linux kernel can do just fine managing automated
device nodes, and automatic loading of firmware, by itself, using its own
devtmpfs code
(https://unix.stackexchange.com/questions/77933/using-devtmpfs-for-dev),
which IIRC Torvalds and company wrote as a reaction to ongoing bad
behaviour from the systemd/udev people.
Along those lines, I also greatly doubt here's a significant need,
except for people highly reliant on USB for critical infrastructure, for
udev, either. Especially for server deployments, I'm not even convinced
mdev is necessary. One Ulrich Dangel is quoted at the StackExchange
link as saying udev is needed because it manages permissions and adds
meaningful symlinks as well as running external scripts. Well, I've
always been able to manage permissions perfectly fine by myself, the
'meaningful symlinks' appears to refer to the
/dev/disk/by-{path,id,label,partlabel,partuuid,uuid} stuff I can do
without, and the 'running external scripts' bit I can either handle
myself or have mdev do as a hotplug handler referenced via
/proc/sys/kernel/hotplug.
https://wiki.gentoo.org/wiki/Mdev
https://github.com/slashbeast/mdev-like-a-boss
> I switched from using ifrename to this udev method years ago. so long
> ago I've forgotten when.
ifrename is cool. ;->
> Anyway, I'll be switching to dual Intel NICs when І get my new ryzen
> threadripper X399 motherboard in a month or two. I've been waiting for years
> (since 2011 or so) for AMD to come out with a new CPU that's both affordable
> and worth upgrading to, and Intel's so overpriced that I would have had to
> spend ~$1000 just to get similar performance to what I already have with
> my Phenom II 1090T...if i'm going to spend that kind of money, I want an
> *upgrade* worth that much.
It's too bad about AMD Platform Security Processor (PSP).
https://libreboot.org/faq.html#amd
Seems that we're on our way to being able to totally neuter Intel Management
Engine, but not yet PSP. (Personally, I like the thought of my systems
not being able to be remotely controlled by others invisibly.)
_______________________________________________
luv-main mailing list
[email protected]
https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
