The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: rp@servium.ch (Rico Pajarola)
Subject: [TUHS] Oracle euthanizes Solaris 12, expunging it from roadmap
Date: Mon, 23 Jan 2017 22:51:49 -0500	[thread overview]
Message-ID: <CACwAiQkGjAWvX2My30f49HqaSoVjY-sfSCCxMMZwGt_Qy2_NLA@mail.gmail.com> (raw)
In-Reply-To: <ca2b245e-132d-ec3e-9528-8fbf2b898ae3@kilonet.net>

On Sat, Jan 21, 2017 at 12:32 PM, Arthur Krewat <krewat at kilonet.net> wrote:

> 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 used Solaris 2.5.1, 8, 10, and 11 extensively. The pkg command was
cool (and so was blastwave's pkg-get before pkg was incorporated into the
base system), but it was always some kind of "poor-mans" yum/apt-get (with
occasional manual surgery required to make stuff work).

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.

that wasn't my experience. HW support in Solaris 11 was orders of magnitude
better than older versions, especially (and surprisingly) on laptops, but
any random network card or SATA/SAS controller (if it wasn't
3com/Realtek/Intel/LSI) had a good chance of not working out of the box, or
at all.

Solaris 11 had a lot of cool, even "linux-y" things, but it was too little,
too late, and Oracle immediately killed whatever velocity they had when
they took over. But at this point, we were already actively getting rid of
it anyway (10 was the last version we deployed in production before jumping
ship).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170123/fba255c1/attachment.html>


  reply	other threads:[~2017-01-24  3:51 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
2017-01-24  3:51                             ` Rico Pajarola [this message]
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=CACwAiQkGjAWvX2My30f49HqaSoVjY-sfSCCxMMZwGt_Qy2_NLA@mail.gmail.com \
    --to=rp@servium.ch \
    /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).