>There are security fixes, there are > application updates. Banks already know, love, > and use Solaris, but there are different business > environments with different needs. A quick CVE > search for solaris gave me 20 security issues this > year, at least 5 of which I'd probably want to > patch on my systems. That's a lot more work > than leaving it alone for so long that I forget > it's there.
Don't get me wrong; I'm not arguing in favor of "fire-and-forget" and don't patch policy. But it is a reality in many shops, simply because with Solaris, it's easily feasible. I take patching very seriously. So seriously in fact, that patches go through engineering cycles of whole releases. > Similarly, there are a lot of > environments and apps out there that expect to be a > lot more dynamic than a banking environment. I seriously doubt you could get any more dynamic than a bank environment. I used to consult for banks which had 5-10 servers come alive every week. My point is, if the ad-hoc shops implemented bank methodologies in managing IT and systems, they would be able to respond much faster to their customer's needs, would be able to be more agile in time-to-market, and would be able to consistenly improve on the quality of service delivered, not to mention the amount of money and time saved. And most importantly, they would be able to deliver both stability and provide extreme agility, which is normally a dichotomy in the IT world. > Rolling out updates can be a lot easier (in my > experience) on Linux systems -- it may be that it got > that way because they needed more updating, but it > doesn't change that it's better. I guess that would depend on one's idea of productivity. To me, it's a waste of my time and resources to go and "update" system-by-system piecemeal. I'd much rather produce a next Solaris Flash(TM) build or run an upgrade and bring hundreds or even thousands of systems to exactly the same system state all at the same time. I would think that even you couldn't argue with the shere, brute force speed of that. This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
