The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] SCO reveals major UNIXT IP violations
Date: Fri, 21 Nov 2003 11:02:50 +1030	[thread overview]
Message-ID: <20031121003250.GD32267@wantadilla.lemis.com> (raw)
In-Reply-To: <20031121002625.6376A1F3D@minnie.tuhs.org>

On Thursday, 20 November 2003 at 19:25:50 -0500, Norman Wilson wrote:
> Gregg C Levine:
>
>   Kenneth, doesn't that mean, that their case can be closed, because
>   they themselves are the guilty party? Caldera was bought by SCO.
>
> I thought it was the other way around: Caldera bought the UNIX-OS part
> of SCO, then (around the time the current fracas started) renamed
> themselves The SCO Group.

Yes, that's correct.  The Caldera that gave away ancient UNIX last
year is the SCO that is going to sue the BSDs for using it this year.

Greg
--
Note: The opinions expressed here are my own and have no relationship
with the opinions or official viewpoints of any organization with
which I am associated.

Finger grog at lemis.com for PGP public key.
See complete headers for address and phone numbers.
-------------- 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/20031121/bb3c7453/attachment.sig>


  reply	other threads:[~2003-11-21  0:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-21  0:25 Norman Wilson
2003-11-21  0:32 ` Greg 'groggy' Lehey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-20 21:38 [TUHS] SCO reveals major UNIX™ " Kenneth Stailey
2003-11-20 21:44 ` [TUHS] SCO reveals major UNIXT " Gregg C Levine
2003-11-20 22:01   ` Andreas Krennmair
2003-11-20 23:21   ` Roger Willcocks

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=20031121003250.GD32267@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).