The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: asmodai@wxs.nl (Jeroen Ruigrok/asmodai)
Subject: [TUHS] This is too weird
Date: Tue, 10 Jun 2003 21:16:33 +0200	[thread overview]
Message-ID: <20030610191633.GJ81568@nexus.ninth-circle.org> (raw)
In-Reply-To: <20030610184905.66504.qmail@web10001.mail.yahoo.com>

-On [20030610 21:02], Kenneth Stailey (kstailey at yahoo.com) wrote:
>http://www.sco.com/scosource/linuxqanda.html
>
>Q: What is SVR6?
>A: SVR6 is the code name for the next-generation operating platform designed to
>take advantage of Web services and is the foundation of our SCOx strategy. As
>the owners of the UNIX operating system, it is incumbent upon SCO to advance
>the UNIX kernel for both 32-bit and 64-bit architectures. This will be
>accomplished through the support of key industry partners who will also
>contribute to this next-generation platform. SVR6 will be formally announced at
>our upcoming SCO Forum event to be held in Las Vegas, Nevada on August 17-19 at
>the MGM Grand Hotel.

OK, I am trying to maintain a neutral stance to SCO, even though they're
making it hard to do, but why does the above sound to me like trying to
get extra ammo they can use in court?  I mean I can already envision the
way the talks will go: "But your honour, we are heavily dependent on our
source code, since we are planning to unveil the SVR6 product in August
and the things which happened with IBM and Linux put our plans in
jeopardy..."

>It just keeps getting weirder:
>
>http://www.sco.com/scosource/unixtree/unixhistory01.html

Ohh, now I get it.  Where on earth do they get the SCO Linux pedigree
and heritage from?  I very much doubt that Linus was doing stuff based
on SCO.  (Hey, everyone with a bit of clue of what happened knows it was
based upon Minix, sort of, but definately not SCO stuff.)

I seriously, seriously wonder where this is leading to.  The USA does
not have the best track record where it comes to sensible court rulings,
but if they have any Unix expert present he can refute a lot of the
so-called claims SCO is making.

This reminds me a lot of U-571, where Hollywood rewrote part of the real
world history for storyline sake.

-- 
Jeroen Ruigrok van der Werven <asmodai(at)wxs.nl> / asmodai / a capoeirista
PGP fingerprint: 2D92 980E 45FE 2C28 9DB7  9D88 97E6 839B 2EAC 625B
http://www.tendra.org/   | http://www.in-nomine.org/~asmodai/diary/
E pluribus unum...


  reply	other threads:[~2003-06-10 19:16 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 [this message]
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
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=20030610191633.GJ81568@nexus.ninth-circle.org \
    --to=asmodai@wxs.nl \
    /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).