The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] SCO sues IBM?
Date: Mon, 10 Mar 2003 11:51:47 +1030	[thread overview]
Message-ID: <20030310012147.GB94647@wantadilla.lemis.com> (raw)

I'm sure I'm not the only person who sees SCO's recent legal
activities with dismay.  For those of you still looking for facts,
take a look at the links off http://www.sco.com/scosource/, and
particularly the complaint at
http://www.sco.com/scosource/complaint3.06.03.html.  There are a
number of things there which concern me, but particularly:

   85.  For example, Linux is currently capable of coordinating the
        simultaneous performance of 4 computer processors.  UNIX, on
        the other hand, commonly links 16 processors and can
        successfully link up to 32 processors for simultaneous
        operation.  This difference in memory management performance
        is very significant to enterprise customers who need extremely
        high computing capabilities for complex tasks.  The ability to
        accomplish this task successfully has taken AT&T, Novell and
        SCO at least 20 years, with access to expensive equipment for
        design and testing, well-trained UNIX engineers and a wealth
        of experience in UNIX methods and concepts.

Apart from the fact that I can't see any factual evidence that System
V as licensed from SCO or its predecessors had any competitive SMP
scalability, the "20 years" concerns me.  That could go back to the
days of the Seventh Edition.

Which brings me to the real point: a little over a year ago, we
received a message from Dion Johnson releasing Ancient UNIX under a
BSD licence.  For those of you who have misplaced it, I'm attaching it
again.  While none of us doubt that it is genuine, SCO has no record
of it on their web site, nor (as far as I know) do any of us have this
in signed form.  In view of SCO's aggression, I think we should
contact them and ask them to at least put the statement somewhere on
their web site.

Comments?

Greg
--
Finger grog at lemis.com for PGP public key
See complete headers for address and phone numbers
-------------- next part --------------
An embedded message was scrubbed...
From: Dion Johnson <dionj@caldera.com>
Subject: Liberal license for ancient UNIX sources
Date: Wed, 23 Jan 2002 15:03:37 -0800
Size: 26173
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20030310/8355c19a/attachment.mht>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20030310/8355c19a/attachment.sig>


             reply	other threads:[~2003-03-10  1:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10  1:21 Greg 'groggy' Lehey [this message]
2003-03-10  2:33 ` David C. Jenner
2003-03-10  3:28   ` Peter Jeremy
2003-03-10 20:23     ` Jeffrey Sharp
2003-03-10  3:13 ` Michael Davidson
2003-03-10 20:21   ` Jeffrey Sharp
2003-03-10 21:15     ` Peter Jeremy
2003-03-10 21:54       ` David C. Jenner
2003-03-10 23:45       ` Greg 'groggy' Lehey
2003-03-11  0:22         ` Peter Jeremy
2003-03-11  1:14           ` Gregg C Levine
2003-03-11  1:51             ` Warren Toomey
2003-03-11  1:59               ` Greg 'groggy' Lehey
2003-03-11  3:51                 ` Warren Toomey
2003-03-11  4:11       ` Michael Davidson
2003-03-11  9:44         ` Sven Mascheck
2003-03-11 15:40           ` Gregg C Levine
2003-03-12  4:05             ` Jeffrey Sharp
2003-03-12  4:46       ` Jeffrey Sharp
2003-03-12  5:03         ` Greg 'groggy' Lehey
2003-03-12 20:31           ` Peter Jeremy
2003-03-12 20:33           ` Wm. G. McGrath
2003-03-11  3:51 ` Wm. G. McGrath
2003-03-10 21:52 Wesley Parish
2003-03-11  5:25 Dennis Ritchie
2003-03-11  6:01 ` Greg 'groggy' Lehey
2003-03-12  4:34 ` Jeffrey Sharp

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=20030310012147.GB94647@wantadilla.lemis.com \
    --to=grog@lemis.com \
    /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).