> 1) If it aint broke, don't fix it. It works, has worked reliably for > several years, and was working fine yesterday. It's uptime is
And now it's broken. So you have to fix it. Life on the edge is scary for some sysadmins, eh? > currently 405 days, and then the last downtime was to physically move > the server. So for 405 days you've done no kernel patches? Awesome. I bet that server's a bunch of remote exploits waiting to happen (if they haven't already). Using massive uptimes to prove how cool your server is actually just shows that you're not doing the right maintenance. > 2) If it aint broke - don't fix it. There's no way I'd attempt a > major upgrade in-place when it's a live server used 24*7. For various > internal reasons (which I'm sure you can guess) I don't have the > resources to do anything but an in-place upgrade if I want to upgrade. Well if they don't want patches on it, and they're not prepared to give you money to have a backup server to do upgrades on, then it can't be as critical as they're telling you. > 3) I can accept that software will go out of support - but I never > expected a Miscrosoft-esque remote shutdown. You should have expected it 6 months ago when the announcement was made.
signature.asc
Description: PGP signature
_______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
