[mythtv-users] kernel upgrade broke networking

[Gary Buhrmaster]

On Fri, Oct 3, 2014 at 3:23 PM, Tom Dexter <digitalaudiorock at gmail.com> wrote:

> Yes...that was a udev change...I recall getting burned by that one.
....
> Yet something else handled very poorly

I do not think there was a way to transparently "win"
on that migration regarding in-place upgrades (for the
majority of real systems) because of a too complex
networking environment and too many unusual edge
cases (and too many places some apps store the
names that would have to be changed; in IPv6, the
stored network address may contain the interface
zone definiion, as in 2001:db8:1::1%eth0).

In past attempts at "auto-migration" of network names,
only simple desktops might have been able to be
migrated, and desktops are a very small percentage
of the total number of installed linux systems (which
are mostly servers in large clusters).  Given that
real vendors target real (paying) customers, and
that (mostly) means servers, I am not surprised
no vendor stepped up to attempt to provide
transparent migration.  Most vendors did provide
information about the changes in the release notes,
but many users do not read those in detail (and
that goes for all "users" in the terms of the desktop
users, and for all too many senior system
administrators).  A horse and water problem.  And,
to be honest, large (server) customers do not upgrade,
they re-install, so there is no migration to do (presuming
your ansible/puppet/cf-engine/chef/etc rules are correct).