Something strange happened here today. I'm not sure I get some of the reasons of why it happened.. partly Client company politics, I guess.
I've been pushing the use of Solaris 10 quite heavily recently, and after trying to drum up enthusaism for a while, found an ideal project to make the first production machines.
This was all well and good, and the techies that I'd spoken to on the subject were keen.
However - it seemed that this move worried some management, and it took a meeting to drill down to what the concerns were.
Solaris 10 has had a lot of good publicity since its' launch.. we all know it's got some great things in it (and some great things to come). However - with such huge advances over Solaris 9 - it's gotta be a whole heap different from the previous release, and therefore difficult to manage the transition, right?
In truth - from an operational perspective, there isn't much difference in a Solaris 10 build from its' predecessor.
Yes, there are a whole bunch of interesting features out there to try out, but the vast majority of them are optional - take for example, containers - it's a piece that I find intriguing, and lined with opportunities, but it's still developing... I'm not yet convinced that I would advocate their use on an important production system.
Dtrace - a great troubleshooting tool, which is going to be desparately useful, it's there if you want it. You can ignore it, and the system will run just fine.
There is however, one exception.. the SMF. This is the biggest change to the operational interface, and it's going to be the one that trips up those coming to Solaris 10 for the first time.
Goodness knows what the vendors are going to make of it.. hell, they still can't get to grips with normal init.d/rc?.d scripts..
(Don't get me wrong - I like the SMF.. it's just going to be funny seeing a Solaris machine silently boot.... quickly).
0 Trackbacks