public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tupshin Harper <tupshin@tupshin.com>
To: Frank Gevaerts <frank@gevaerts.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SCO's "proof"
Date: Tue, 19 Aug 2003 08:22:08 -0700	[thread overview]
Message-ID: <3F4240A0.1090008@tupshin.com> (raw)
In-Reply-To: <20030819150137.GA22521@gevaerts.be>

Frank Gevaerts wrote:

>On Tue, Aug 19, 2003 at 03:52:13PM +0100, Dr. David Alan Gilbert wrote:
>  
>
>>* Brandon Stewart (rbrandonstewart@yahoo.com) wrote:
>>    
>>
>>>compliments of "d1rkinator" from yahoo finance message board:
>>>
>>>The code SCO finds offending:
>>>
>>>www.heise.de/newsticker/data/jk-19.08.03-000/imh0.jpg
>>>www.heise.de/newsticker/data/jk-19.08.03-000/imh1.jpg
>>>      
>>>
>>Ah I was wondering if anyone had a copy of that.
>>
>>    
>>
>>>Its location in Linux:
>>>
>>>/usr/src/linux-2.4.20/arch/ia64/sn/io/ate_utils.c
>>>
>>>And its heritage:
>>>
>>>minnie.tuhs.org/UnixTree/V7/usr/sys/sys/malloc.c.html
>>>
>>>Ok, SCO: This was easy. Now, show us the other many examples.
>>>      
>>>
>>Is it? What the hell was the copyright on that code?
>>    
>>
>
>AFAIK it was released under a BSD license by Caldera...
>
>Frank
>
http://www.tuhs.org/Archive/Caldera-license.pdf

<quote>
January 23, 2002
Dear UNIX? enthusiasts,
Caldera International, Inc. hereby grants a fee free license that 
includes the rights use, modify and distribute this named
source code, including creating derived binary products created from the 
source code. The source code for which Caldera
International, Inc. grants rights are limited to the following UNIX 
Operating Systems that operate on the 16-Bit PDP-11
CPU and early versions of the 32-Bit UNIX Operating System, with 
specific exclusion of UNIX System III and UNIX
System V and successor operating systems:
32-bit 32V UNIX
16 bit UNIX Versions 1, 2, 3, 4, 5, 6, 7
</quote>

-Tupshin


  reply	other threads:[~2003-08-19 15:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19 13:37 SCO's "proof" Brandon Stewart
2003-08-19 14:52 ` Dr. David Alan Gilbert
2003-08-19 15:01   ` Frank Gevaerts
2003-08-19 15:22     ` Tupshin Harper [this message]
2003-08-19 15:25     ` Colin Paul Adams
2003-08-19 20:46       ` Kurt Wall
2003-08-20 18:27       ` bill davidsen
2003-08-20 18:46         ` Valdis.Kletnieks
2003-08-21  3:09           ` Stuart Longland
2003-08-21 10:22             ` Stephan von Krawczynski
2003-08-19 15:07 ` Bart Samwel
2003-08-19 15:31   ` Richard B. Johnson
2003-08-19 15:14 ` Richard B. Johnson
2003-08-19 15:30 ` Jeff Garzik
2003-08-19 16:52   ` David Mosberger
2003-08-19 17:22   ` Matti Aarnio
2003-08-19 18:00   ` J.A. Magallon
2003-08-19 20:02     ` Richard B. Johnson
2003-08-22  2:31       ` Sulaiman Alhasawi
2003-08-22  7:25         ` Paul Rolland
2003-08-22  8:33         ` Geert Uytterhoeven
2003-08-22 10:35           ` Måns Rullgård
2003-08-23 13:16             ` Leandro Guimarães Faria Corsetti Dutra
2003-08-19 19:18 ` Vojtech Pavlik
2003-08-19 23:34 ` Andrei Barbu "T'Eval"
  -- strict thread matches above, loose matches on Subject: below --
2003-08-22  9:36 P. Christeas
2003-08-22  9:51 ` Christoph Hellwig
2003-08-22 13:58   ` Kurt Wall
2003-08-22 12:37 ` Con Kolivas

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=3F4240A0.1090008@tupshin.com \
    --to=tupshin@tupshin.com \
    --cc=frank@gevaerts.be \
    --cc=linux-kernel@vger.kernel.org \
    /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