NYT Ponders the Future of Solaris In a Linux/Windows World

JerkBoB links to a story at the New York Times about the future prospects of Sun's Solaris, excerpting: "Linux is enjoying growth, with a contingent of devotees too large to be called a cult following at this point. Solaris, meanwhile, has thrived as a longstanding, primary Unix platform geared to enterprises. But with Linux the object of all the buzz in the industry, can Sun's rival Solaris Unix OS hang on, or is it destined to be displaced by Linux altogether?"

Comments

Re:Performance

[Anonymous Coward]

Got the balls to drop an strace on your production Oracle database? I tried strace on an Oracle database on RHEL 5 and the damn process deadlocked and the box needed a reboot to clear it up. Good thing it was a development DB.

I've put a truss (and now dtrace) on PRODUCTION Oracle databases running on Solaris many times.

I don't dare do that on Linux.

Solaris is as far beyond Linux in stability as Linux is beyond Win2K.

Re:Or else...

[Saint Aardvark]

Blastwave...heh. Which Blastwave are you talking about?

Sorry, this is a bit of a sore point for me. At work, we have a Solaris 10 machine that powers about 30 SunRays for mathematicians. JDS is fine, but adding other programs is a pain. (Disclaimer coming up, so bear with me.)

• Blastwave: They just had the split. But before that there were problems. Upgrading CUPS broke printing; they'd moved around some Ghostscript filters. Upgrading Postfix broke Postfix, because they'd moved the config files to play nicer with zones, and their script that should've dropped everything in the right place didn't. These were stable versions, not the unstable.
• pkg-src: Great until you trip over something that won't compile and spend days trying to track down what it is -- say, 1 package in 20. Sounds like good odds? Try compiling Firefox or Kile, with dependencies stretching back to libc and the Dead Sea scrolls. I'm guessing they just aren't able to do as much testing on Solaris...and fair enough; the job of making umpty thousand packages compile on mumble different OS' is hard enough.
• compile from source: fine, unless it's obscure (say, some mathematical package) that assumes GNU tools all the way, or a Linux OS, and weird, obscure things break.
• download binaries: yes, if they've got 'em.

And now for the disclaimers: No, this isn't enterprise (which was your point; I was looking for a place to jump into this discussion, and the mention of Blastwave got me). Yes, a real sysadmin could compile all this from scratch without problem. Yes, this is an edge case on top of an edge case (desktops for mathematicians? How obscure!). Yes, ZFS and dtrace are seriously, jaw-droppingly awesome.

But this is my experience; so far, I simply have not done anything remotely enterprise. It's all been server + desktop in small shops. And for that environment, requirements are changing all the time. The mail server now needs to do spam filtering and DNS. Yes, they should be split up, but there isn't the budget. The new guy wants KDE on his machine instead of Gnome, or needs to try out a new library to see if it works.

And for these, it's not "set it and forget it"; we need new packages, or updates to the old ones, all the time. If all the heartache I described was a one-time thing, I'd do it and be done...but in this environment, it'll need to be done again in three months. That means a good package manager (hello, Debian!), or a good ports tree (*BSD), or an environment that everyone is familiar with (Linux, because it has just that much mindshare).

Bit of a rant, and less coherent than I'd like. But it's 6am, I haven't had my coffee yet, and my kid's about to wake up...so I'll have to leave it there.