I think there is some sort of censorship going on (thereby forcing me to get my slashdot password reset) so i can repost my comments, this time not as an AC.
- Package manager was brain dead. apt, yum are far better. ( Sorry Solaris 11 was too late. Too much legacy out there. )
Only major shortcoming with pkg manager in solaris' 11 was with the fact that there was no directly accessible repository of software that could be used (albeit the dependency checks etc were missing too). That has been fixed in Solaris 11. You have to remember that Solaris 10 was released in 2004 (10 years ago). If you want to use Solaris today, you should switch to an opensolaris variant or Solaris 11.1
- Patching made no sense. You have no idea what packages are patched with a patch. Patches were just binary disk vomit that spewed crud all over the system. Impossible in the real world to build any sort of verification around them. ( Sorry Solaris 11 was too late. Too much legacy out there. )
It's an easy enough thing to fix. Use zones to convert physical servers into solaris 10 branded zones. All of a sudden you patching becomes non-sequiter and generally painless. In my shop we automate patching of 100s of solaris (yes 10) boxes at a time and using ZFS root + Iive upgrade we patch them all under 30 minutes. With Solaris 11, this is down to a 2 minute window. We literally patch Solaris 11 LDOMs in under 2 minutes flat, including reboot. And Solaris 11 has gone away from Patch IDs etc...they are all pkgs, just the same as Linux.
- Zones: Are a nightmare of security and privilege. I don't care what any says a zone is just a change root jail. Which means you will only every be as up-to-date as the host system. And it means you must be compatible and tested against the host system. Which is really no different than not having zones. Zones are a horrible horrible mess.
Zones are a very very cool technology. You can do a lot of powerful things with zones at zero additional cost. And with the advent of Solaris 11, you can now P2V physical hosts into Solaris 10 branded zones, and circumvent the whole patch/package issue. I have used zones with great success (100s of them running multi-TB DWH on M-class, T-class and x86 hardware). They are not a nightmare of security and privilege. The rules are very very clear and concise. There are things you can do within zones and things you cannot. It calls for a little old thing called RTFM, that's all.
- No dependable only repository of packages that is robust or up to date. Far to much package hunting still required to locate software for solaris. Most packages are
months to years behind there linux counterparts.
Not anymore. Solaris 11 SRUs are released at regular intervals and upgrading is as easy saying 1, 2, 3 ;-)
- Java performs better on x64 than Solaris/SPARC. This has boggled me for years. Only recent sparc architectures let java and other highly threaded applications stacks really perform well. Why do I even have to know about processor binding for processes?
Try running you java apps within zones with dedicated vcpu and memory grants. And Solaris runs on x64 as well. Consider running java on the T4s and T5s and see how they run.