The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] Oracle euthanizes Solaris 12, expunging it from roadmap
Date: Sat, 21 Jan 2017 12:32:55 -0500	[thread overview]
Message-ID: <ca2b245e-132d-ec3e-9528-8fbf2b898ae3@kilonet.net> (raw)
In-Reply-To: <CACwAiQndHrhFzt=J77Y84D-O31rDTzBANLwNxO_a1fV30TVRVQ@mail.gmail.com>

Take another look at Solaris 11 - the pkg command is basically the same 
thing. Install PHP, MYSQL, Apache, update the system, do almost anything.

I've booted Solaris 11 on a slew of servers and PC's since it came out. 
 From Intel SATA to LSI SAS, Emulex fiber channel cards, Qlogic fiber 
cards, Intel 10Gbe NICs, etc.

It just "works". While you had to pay attention to the HCL back in the 
Solaris 7/8/9 and early 10 days, and adjust accordingly, Solaris has 
been pretty decent in the past few years in terms of hardware 
compatibility.  Except for one horrid instance where the Emulex driver 
would fail if virtualization was turned on - but in 11.3, that seems to 
have been fixed (or, the hardware changed, I installed it on newer M630 
Dell hardware).

For the "desktop" however, I just don't use it as a desktop. Windows won 
that war for me.

As for performance, I'll have to look into that - I remember a while 
back that Oracle's best practices for it's database was to turn off NUMA 
under Linux, but not Solaris. Either way, virtualization (VMware mostly) 
has made that a moot point in many of the environments I administer.

On 1/20/2017 8:58 PM, Rico Pajarola wrote:
> And there's another kind of elegance in being able to boot Linux on 
> any random PC and have at least graphics, network, and storage work 
> out of the box (most of the time anyway. Solaris never stood a chance 
> on that front). Software gets installed with a simple "yum install 
> foo" or "apt-get install foo" command. At some point Solaris also lost 
> the performance race and that was pretty much it.



  reply	other threads:[~2017-01-21 17:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19  7:53 Kay Parker   
2017-01-19  8:49 ` Wesley Parish
2017-01-19 14:40   ` Arthur Krewat
2017-01-19 16:39     ` Tim Bradshaw
2017-01-19 17:02       ` Arthur Krewat
2017-01-20  2:00     ` Nick Downing
2017-01-20 11:24       ` Joerg Schilling
2017-01-20 13:26         ` Random832
2017-01-20 14:23           ` Joerg Schilling
2017-01-20 14:29             ` Steve Nickolas
2017-01-20 15:20               ` Arthur Krewat
2017-01-20 15:45                 ` Andy Kosela
2017-01-20 16:30                   ` tfb
2017-01-20 19:38                     ` Nemo
2017-01-21  0:25                       ` Tim Bradshaw
2017-01-21  1:58                         ` Rico Pajarola
2017-01-21 17:32                           ` Arthur Krewat [this message]
2017-01-24  3:51                             ` Rico Pajarola
2017-01-21 15:43                         ` Nemo
2017-01-20 20:30                   ` Steffen Nurpmeso
2017-01-20 22:30                     ` Kay Parker   
2017-01-20 23:50                       ` Steffen Nurpmeso
2017-01-21  0:09                         ` Steve Nickolas
2017-01-21  1:03                           ` Kurt H Maier
2017-01-20 11:54       ` Tim Bradshaw
2017-01-19 18:17   ` Joerg Schilling
2017-01-20 14:58 Rudi Blom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ca2b245e-132d-ec3e-9528-8fbf2b898ae3@kilonet.net \
    --to=krewat@kilonet.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).