The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: kstailey@yahoo.com (Kenneth Stailey)
Subject: [TUHS] This is too weird
Date: Tue, 10 Jun 2003 20:02:05 -0700 (PDT)	[thread overview]
Message-ID: <20030611030205.67622.qmail@web10010.mail.yahoo.com> (raw)
In-Reply-To: <20030610222421.GA63364@minnie.tuhs.org>

--- Warren Toomey <wkt at tuhs.org> wrote:
> On Tue, Jun 10, 2003 at 11:49:05AM -0700, Kenneth Stailey wrote:
> > It just keeps getting weirder:
> > http://www.sco.com/scosource/unixtree/unixhistory01.html
> 
> Well, if SCO is claiming intellecutal property rights to Linux, why
> are they intimating that they will sue Linus?
> 
> This is becoming an alternate reality.
> 
> 	Warren

When we find out that there's SCO code in Cygwin call me. ;)

The chart is a good way to confuse things.  The poor guy that made the original
must be crying that he let SCO use it years ago.

The part that confuses me is that I remember there were dotted lines one on the
original UNIX history chart that showed non-source-code-copying influences and
now even the real UNIX history chart is using only solid lines.  It makes MINIX
look like it has 7th Ed code in it instead of just being a 7th Ed API
implementation from scratch like it is.

That's the part that's really on drugs by the time SCO is using it as evidence
that there is a Linux pedigree or whatever that connects 7th Ed to Linux.

I think the real story is that they want to make as much press as they can
since it boosts their stock.

Meanwhile every time they say they own UNIX they are complete liars because:

> http://www.sco.com/scosource/linuxqanda.html
> 
> As the owners of the UNIX operating system, it is incumbent upon SCO to

To what?  Violate their agreements with The Open Group?

http://www.smh.com.au/articles/2003/05/23/1053585678840.html

"Reference to the SCO web site shows that they own certain intellectual
property and that they correctly attribute the trademark to The Open Group. 
SCO has never owned "UNIX".  SCO is licensed to use the registered trademark
UNIX "on and in connection" with their products that have been certified by The
Open Group, as are all other licensees," the statement said.

"These are the only circumstances in which a licensee may use the trademark
UNIX on and in connection with its products.  Statements that SCO 'owns the
UNIX operating system', has 'licensed UNIX to XYZ' are clearly inaccurate and
misleading."



__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com


  parent reply	other threads:[~2003-06-11  3:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-10 18:49 Kenneth Stailey
2003-06-10 19:16 ` Jeroen Ruigrok/asmodai
2003-06-10 20:15   ` Paul Ward
2003-06-10 20:38     ` Jeroen Ruigrok/asmodai
2003-06-10 20:39     ` Jeroen Ruigrok/asmodai
2003-06-10 22:24 ` Warren Toomey
2003-06-10 22:57   ` Gregg C Levine
2003-06-11  1:19   ` Greg 'groggy' Lehey
2003-06-11  6:10     ` Jeroen Ruigrok/asmodai
2003-06-11  6:18       ` Greg 'groggy' Lehey
2003-06-11  3:02   ` Kenneth Stailey [this message]
2003-06-11 11:52     ` Wesley Parish
2003-06-11 17:17       ` Gregg C Levine

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=20030611030205.67622.qmail@web10010.mail.yahoo.com \
    --to=kstailey@yahoo.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).