The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tfb@tfeb.org (Tim Bradshaw)
Subject: [TUHS] Does this mean Linux is now "officially branded UNIX"?
Date: Tue, 14 Mar 2017 11:35:35 +0000	[thread overview]
Message-ID: <42280A7B-067C-4BE7-A028-685D89BEC0A1@tfeb.org> (raw)
In-Reply-To: <CAC20D2MO-fwNq2qg0DAbPr4NTX5aTwcN_+SQ=MWu5jiL2RVBwg@mail.gmail.com>

On 13 Mar 2017, at 21:35, Clem Cole <clemc at ccc.com> wrote:
> 
> Or in there case, negative value.   RH likes to have the world believe they are Linux.   They don't want anything lessening their brand.  Certification would make RH < UNIX I suspect which is not what they want.   Certification has always been about the ISV's, and if they can convince the ISV to test on their implementation directly (and they have) they don't need it.
> 

Well, in particular a lot of the kind of organisations RH sell to (banks) had experiences with Unix which were not that good: places I worked spent an enormous amount of money on very expensive machines with hardware-redundancy features which were at best marginally functional, and certainly not functional enough to rely on.  These features compared very badly with the things that IBM Z-series machines could do (it might be that the IBM/AIX machines were better in this regard: I didn't deal with them very much).

Of course we'd argue that this is not the fault of Unix, and that's a different discussion.  But the people who have spent 9-figure sums on all this marginally-functional tin that the Unix vendors foisted on them don't look at it that way: they just want something which is not Unix, and which runs on cheap tin.  Linux is not Unix, and runs on cheap tin.

--tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170314/da0c5c7f/attachment.html>


  parent reply	other threads:[~2017-03-14 11:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 15:04 Josh Good
2017-03-13 10:15 ` Joerg Schilling
2017-03-14 13:58   ` Nemo
2017-03-14 14:14     ` Joerg Schilling
2017-03-14 23:27       ` Josh Good
2017-03-15 11:11         ` Joerg Schilling
2017-03-15 13:42           ` Random832
2017-03-15 14:14             ` Joerg Schilling
2017-03-15 15:16               ` Random832
2017-03-13 21:06 ` Michael-John Turner
2017-03-13 21:35   ` Clem Cole
2017-03-14 10:20     ` Joerg Schilling
2017-03-14 11:35     ` Tim Bradshaw [this message]
2017-03-13 21:51   ` Josh Good
2017-03-14  0:11     ` Wesley Parish
2017-03-13 22:30   ` Arthur Krewat

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=42280A7B-067C-4BE7-A028-685D89BEC0A1@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).