The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tfb@tfeb.org (tfb@tfeb.org)
Subject: [TUHS] Oracle euthanizes Solaris 12, expunging it from roadmap
Date: Fri, 20 Jan 2017 16:30:14 +0000	[thread overview]
Message-ID: <2684AF1F-8B33-4646-BF9C-0FCAD6C70D5A@tfeb.org> (raw)
In-Reply-To: <CALMnNGiWy2k7SxHmmVYQTageXVgb9DHJ8aXoMuq+wP-QFE=91A@mail.gmail.com>

On 20 Jan 2017, at 15:45, Andy Kosela <akosela at andykosela.com> wrote:
> 
> I understand that Linux can still be called a new kid on the block, but it is actually not "a new platform" anymore.  It has been deployed (along with FreeBSD) in large corporations for around 20 years now.  It really became the Standard OS from embedded world to supercomputers.

The people I'm talking about (who might be characterised as 'COBOL shops') are not early adopters: 20 years is about how long it takes for them to decide something is safe.  Yes, of course Linux has been everywhere for a long time, but ten years ago it almost certainly was not involved in running your bank account, while today it almost certainly is.

> Personally I do not find this to be a bad thing, because with OS standardization comes uniformity, and I would rather have one true Unix standard than hundreds of incompatible ones.

'Linux' and 'OS standardisation' are funny phrases to see in the same sentence.  (Note: I work in an exclusively Linux HPC environment: I am not some anti-Linux holdout, I just have previously worked in the above-mentioned environments and I appreciate their needs and fears).

I think this is probably off-topic tor TUHS, sorry.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170120/a22b59a5/attachment.html>


  reply	other threads:[~2017-01-20 16:30 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 [this message]
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
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=2684AF1F-8B33-4646-BF9C-0FCAD6C70D5A@tfeb.org \
    --to=tfb@tfeb.org \
    /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).