From: djenner@earthlink.net (David C. Jenner)
Subject: [TUHS] SCO sues IBM?
Date: Mon, 10 Mar 2003 13:54:37 -0800 [thread overview]
Message-ID: <3E6D099D.A9F4654D@earthlink.net> (raw)
In-Reply-To: <20030310211518.GL90290@gsmx07.alcatel.com.au>
Warren has a signed, dated, and numbered license for Ancient Unix (AU-0).
I have a signed, dated, and numbered license for Ancient Unix (AU-1).
I don't see how Warren can't distribute to me any software covered under the license.
Peter Jeremy wrote:
>
> On 2003-Mar-10 14:21:00 -0600, Jeffrey Sharp <jss at subatomix.com> wrote:
> >On Sunday, March 9, 2003, Michael Davidson wrote:
> >> I will, however, ask for an "official" statement of SCO's current position
> >> on "Ancient UNIX"
> >
> >But once they've released it under a BSD-style license, it is released. They
> >simply can't unrelease it. They don't have to continue distributing it, but
> >they can't stop me from doing what the license explicitly allows. So their
> >current position WRT ancient UNIX may not mave much legal weight. IANAL,
> >TINLA.
>
> AFAIK, the only evidence we have that it is released under a BSD-style
> license is an e-mail allegedly from an authorised person within SCO.
> Warren has not been able to find an equivalent statement on their
> website. I suspect Warren is concerned that they could claim it was
> never released - ie the e-mail is a faked/forged or the sender didn't
> have the authority to make the claims therein.
>
> What would you do if SCO's lawyers came knocking on your door and
> demanded you cease distributing ancient UNIX or derived products?
> Whilst you could probably prove the authenticity of the e-mail, this
> would cost real money - and SCO probably can afford to spend a lot
> more money than you can.
>
> The date of the e-mail may also be a crucial issue - since IBM would
> presumably have the right to use the code after SCO changed the code
> to a BSD license.
>
> IANAL, TINLA etc.
>
> Peter
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> http://minnie.tuhs.org/mailman/listinfo/tuhs
--
David C. Jenner
djenner at earthlink.net
next prev parent reply other threads:[~2003-03-10 21:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 1:21 Greg 'groggy' Lehey
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 [this message]
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=3E6D099D.A9F4654D@earthlink.net \
--to=djenner@earthlink.net \
/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).