The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wkt@henry.cs.adfa.edu.au (Warren Toomey)
Subject: SCO Source license tainting?
Date: Wed, 24 Feb 1999 08:52:15 +1100 (EST)	[thread overview]
Message-ID: <199902232152.IAA04722@henry.cs.adfa.edu.au> (raw)
In-Reply-To: <Pine.LNX.4.05-df.9902231646390.8684-100000@bartlet.df.lth.se> from Jesper Nilsson at "Feb 23, 1999  5: 0:54 pm"

In article by Jesper Nilsson:
> I'm thinking about getting myself a SCO Source license,
> but I'm worried that I might get "tainted" by this
> since my day job involves writing operating systems...
> My employer would not appreciate getting sued because of
> my hobbies...:-)

As long as you don't reuse tainted Unix source code in your job, you will
be ok. There are so many books covering the Unix kernel: Lions, Bach,
Goodheart, Vahalia etc., that any concerns other than source code reuse
are negligible.

That's my feelings, anyway.

	Warren

Received: (from major at localhost)
	by minnie.cs.adfa.edu.au (8.9.1/8.9.1) id LAA25583
	for pups-liszt; Wed, 24 Feb 1999 11:46:21 +1100 (EST)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
	by minnie.cs.adfa.edu.au (8.9.1/8.9.1) with ESMTP id LAA25578
	for <pups at minnie.cs.adfa.edu.au>; Wed, 24 Feb 1999 11:46:12 +1100 (EST)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA20195;
	Wed, 24 Feb 1999 11:16:09 +1030 (CST)
Received: (from grog at localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id LAA51811;
	Wed, 24 Feb 1999 11:16:08 +1030 (CST)
Message-ID: <19990224111607.G93492 at lemis.com>
Date: Wed, 24 Feb 1999 11:16:07 +1030
From: Greg Lehey <grog@lemis.com>
To: wkt at cs.adfa.edu.au, Unix Heritage Society <pups at minnie.cs.adfa.edu.au>
Subject: Re: SCO Source license tainting?
References: <Pine.LNX.4.05-df.9902231646390.8684-100000 at bartlet.df.lth.se> <199902232152.IAA04722 at henry.cs.adfa.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199902232152.IAA04722 at henry.cs.adfa.edu.au>; from Warren Toomey on Wed, Feb 24, 1999 at 08:52:15AM +1100
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-pups at minnie.cs.adfa.edu.au
Precedence: bulk

On Wednesday, 24 February 1999 at  8:52:15 +1100, Warren Toomey wrote:
> In article by Jesper Nilsson:
>> I'm thinking about getting myself a SCO Source license,
>> but I'm worried that I might get "tainted" by this
>> since my day job involves writing operating systems...
>> My employer would not appreciate getting sued because of
>> my hobbies...:-)
>
> As long as you don't reuse tainted Unix source code in your job, you will
> be ok. There are so many books covering the Unix kernel: Lions, Bach,
> Goodheart, Vahalia etc., that any concerns other than source code reuse
> are negligible.

I think this relates to a spectre raised during the USL/BSDI wars.
Somebody suggested that anybody who had been exposed to AT&T source
code was ``tainted'' and could thus not legally develop competitive
systems.  Somewhere I have a button that somebody brought back to me
from a USENIX, with the text ``mentally contaminated''.

Jesper, I don't think you need to worry about the problem.  That kind
of restriction would be unenforceable.

Greg
--
See complete headers for address, home page and phone numbers
finger grog at lemis.com for PGP public key



           reply	other threads:[~1999-02-23 21:52 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <Pine.LNX.4.05-df.9902231646390.8684-100000@bartlet.df.lth.se>]

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=199902232152.IAA04722@henry.cs.adfa.edu.au \
    --to=wkt@henry.cs.adfa.edu.au \
    /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).