On Wed, Jun 26, 2019 at 08:01:56PM -0400, The Wanderer wrote:
On 2019-06-26 at 14:49, Michael Stone wrote:
And never changed anything, because locking the names via udev was
necessary to keep them from renaming themselves. So if you bought a
new nic it would never, ever show up as eth0 without some edits.
Which isn't possible anyway if the network device is hardwired into the
motherboard, as is the case on every consumer-targeted system I remember
encountering for as long as I've been paying conscious attention.
I guess you never swapped a motherboard due to a failure. I did, and it
meant reconfiguring the network after the machine came back. This was
much more of a pain in the neck than simply having a service tech swap
the motherboard and turn the machine back on (in many places it means
that you need one hardware support person and one software support
person on hand instead of just one hardware support person). With the
new scheme, if it was eno1 on the old motherboard, it will be eno1 on
the new motherboard. The fact that you never ran into the problems
doesn't mean they didn't exist.
