Our senior tech guys do the patch Tuesday meeting but a big chunk of our kit is internet facing. If you're offline or behind a (decent content filtering) firewall then the impact is potentially lower or non existent.
Impact analysis is essential to discover whether or not the issue is serious.
Our dev team use powershell for all sorts of things from data processing and clean up to fuzzing. It's great because it tries to preserve both the Unix semantics and introduce and object model which means it bridges the world of raw data and COM etc which has traditionally been pretty sticky. It can be quite slow in some circumstances though which is my only concern (this is usually due to the fact strings are immutable on the CLR). I used python for a bit as well but it doesn't hit the spot for COM.
regarding cost, the only major issue for us is SQL Server licensing but we argued with them and waved a postgresql server around and got a hefty discount ;)
We don't use Azure at all mainly due to security concerns (we store financial data). I use it for a couple of side projects as it's cheaper than a couple of dedicated servers.
I've not encountered any major trust issues with Azure despite the whole NSA controversy. I don't get much love for OSS other than from people who want to cut costs and they usually don't pay up.
It was a small company (family farm machinery outfit) but their requirement is far more common than a massive software deployment. There are literally millions of servers churning away on trivial jobs in people's offices etc.
Powershell allows automated maintenance and edge cases to be dealt with efficiently. DSC allows repeatable deployments i.e you can use it to represent all your basic tenets of a reliable secure system. You don't build a system then throw it in the field with fingers crossed that you remembered every step when you built it. I have personally written hundreds of pages on procedural documentation on this and I can now script up that knowledge easily.
RedHat is an option but the system is fragmented and randomly documented. Microsoft documentation is absolutely wonderful in comparison. Not only that, I can grab a competent sysadmin for the windows platform easily here in the UK. The Linux guys are few and far between and generally cowboys from experience (even at the £60k level).
Windows rarely needs rebooting unless you are doing something wrong. Not all updates need to be applied. We pick individual ones in scope with what is being deployed and used and push them out rather than use windows update. This is standard practice on servers. Desktops get windows updates on time as the attack window is usually way larger.
It is feasible not to update windows server if configured properly and if it's on a corporate LAN for example.
It's important because it is the last bastion of simplicity in the UNIX world. It's open, a single cohesive system, is cleanly documented, cleanly engineered and small enough to retain knowledge on.
It's the ideal foundation to build research upon which is where standards can be developed.
Everyone has benefitted from NetBSD being around and will probably continue to for a long time yet.
I would, probably controversially, use Windows Server 2012 on mid-range HP DL or ML series kit. Since Windows 2008 R2 and the scriptability provided with PowerShell and PowerShell DSC have come around, it's a better compromise on usability versus automation that anything else I've seen so far. Not only that, it has a huge supported lifecycle.
Bear in mind I come from a very strong UNIX background going right back to M68K Sun3 era, through Solaris/HPUX and Linux and have used all on the desktop.
According to the logs, quite a few telnet attempts until about 2003 then it tailed off. Connection was up for around 2-3 hours a day. No incoming calls and wardialers as the modem was set not to answer.
No statistics on SSH though as it wasn't even running and possibly wasn't even installed. I didn't check! :)
Probably quite a low percentage however it seems to be used as the proving ground for new tech such as IPv6 and ISC seem heavily into it so it's still really important regardless of market share.
I set up a dialup gateway for a company with NetBSD 1.3 in 1998 on a compaq pentium 90 desktop with 32MiB of RAM. I got a call last year (!) from the owner saying it stopped working suddenly. Pulled the disk on it and plugged it into an IDE/USB adapter and looked at the syslog as I had no ps2 keyboard and it didn't have USB.
Suspected hardware failure at that age.
Max uptime: 8 years, 122 days!
It was still being used (on a dialup). It stopped working due to the dialup company stopping service rather than a hardware failure.
Has been replaced by a cheap ADSL connection and router. Ironically this had only been an option for about 6 months due to the rural location and no DSLAM at the local exchange.
Wonderful OS although I'm ashamed to say I left telnet open to the public internet.
The same can actually be said for Windows NT4 as well which tends to show up unexpectedly sticking things together.
Edit: some other notes that might be of interest to long running UNIX admins: Firstly the log files had eaten up nearly all the disk space (2Gb) so rotate them! Secondly the clock had drifted by about 5 days so use ntp. Thirdly, don't assume that if you leave something that it'll be sensibly secure in a few years so they need to be kept religiously up to date. Fourthly, plan for connectivity modes to change over time and keep them up to date; the company was down for 4 days whilst BT got their arse in gear (not that they cared as they had 3G that worked reasonably well). Fifthly, buy good quality hardware - it does last!
Most people don't know the difference between Windows and Word. This is just going to confuse them further which is not a great way to win market share.
Whilst this is a post of derision, I do think people only know the highest level abstraction mankind can accomplish these days. It's embarrassing really. There is elegance in simplicity.
Please continue to take the piss out of it :)
I actually knocked up a single new static error page for our main web application a few weeks ago in 620 bytes including inline css (quite big if you ask me). It had no dependencies. My coworkers were actually astounded that it was so small!?!?!
Spot on. If I could upvote this a hundred times I would.
I had a certain well know recruitment agent basically begging for me to go and work for them a couple of years ago. The agent was completely incapable of understanding why I "would turn away such a great opportunity" and just kept pushing so I told her to fuck off.
Absolute arsehole recruiters and companies.
for ref, I refuse to work for gambling and gaming outfits as well as they're just as bad
Impact analysis is essential to discover whether or not the issue is serious.
Our dev team use powershell for all sorts of things from data processing and clean up to fuzzing. It's great because it tries to preserve both the Unix semantics and introduce and object model which means it bridges the world of raw data and COM etc which has traditionally been pretty sticky. It can be quite slow in some circumstances though which is my only concern (this is usually due to the fact strings are immutable on the CLR). I used python for a bit as well but it doesn't hit the spot for COM.
regarding cost, the only major issue for us is SQL Server licensing but we argued with them and waved a postgresql server around and got a hefty discount ;)
We don't use Azure at all mainly due to security concerns (we store financial data). I use it for a couple of side projects as it's cheaper than a couple of dedicated servers.
I've not encountered any major trust issues with Azure despite the whole NSA controversy. I don't get much love for OSS other than from people who want to cut costs and they usually don't pay up.