Just as an FYI to any Ubuntu server users, I had to go through the pain
of updating a web server to Ubuntu 16.04. 16.04 really should not be
used in production unless you're willing to work around breakages during
the upgrade.
I've had minor issues in the past with obscure bits but MySQL, PHP and
Apache all breaking/not installing properly on the update is something
obvious I think should have been fixed before release. Hopefully it will
change with the first point release as previously I've updated various
machines as far back as 10.04 over the years without issue so this break
was completely unexpected.
On 09/06/16 12:00, Cowboy wrote:
On Thursday 09 June 2016 06:30:44 am Robert Jeffares wrote:
run updates on a non essential machine, then
others one by one. Generally I don't make any changes until they have
been out for a month or so.
Same here, ever since the notorious WinNT SP2 update which broke
NT hopelessly on many mission critical machines world wide, and was
almost immediately recalled, but not before much damage was done.
Now, it's very true, that *was* Micro$oft, but these days when too many
"programmers" have a Micro$oft mentality, automatic updates has
proven too often to be a very bad thing !
I've had some trouble with all versions of anyone's distro, no matter the OS,
including CentOS 7, which most recently broke the stock included e-mail
client, while fixing the Vbox DKMS which the previous update broke.
M$ recently seems to be deliberately breaking everything by putting
a forced update to the seriously flawed Win10 into everything.
Bottom line : If you're going to assume the responsibility of being
or acting like a sysadmin, then it's YOUR responsibility to test and
re-test any and everything deployed into the revenue stream.
"Automatic updates" is just irresponsible, almost to a criminally negligent
level.
Red Hat does a pretty good job, but you have to remember who they
are doing it for, and it's not you !
Debian is much better, but they do have their political agenda.
Ubuntu, well, not even worth mentioning.
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
