The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jrvalverde@cnb.uam.es (Jose R. Valverde)
Subject: [TUHS] SunOS 4.1.1?
Date: Tue, 25 Sep 2007 16:06:47 +0200	[thread overview]
Message-ID: <20070925160647.65053bd4@veda.cnb.uam.es> (raw)
In-Reply-To: <20070925015247.GD25048@mercury.ccil.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]

On Mon, 24 Sep 2007 21:52:47 -0400
John Cowan <cowan at ccil.org> wrote:
> Tim Bradshaw scripsit:
> 
> > I'm assuming that the source isn't available at all (I wonder if Sun  
> > still have it?)
> 
> It is not *legally* available, but it is *actually* available.
> Like, say, _The Lord of the Rings_ in HTML.
> 
The funny thing, if I did read correctly the filings and agreements from
Groklaw is that a legal third party could probably release this code 
*legally* if it is *acually* available.

I'm talking about something that popped up in the SCO vs IBM case: as I
remember, the agreement stated that IBM was required to held confidential 
all information except in the case it had been made widely available by
some third party.

>The exception is set forth in Section 7.06(a) of the standard software agreement:
>
>    If information relating to a SOFTWARE PRODUCT subject to this Agreement at any 
>time becomes available without restriction to the general public by acts not 
>attributable to LICENSEE or its employees, LICENSEE'S obligations under this 
>section shall not apply to such information after such time.  

Thus it seems possible that UNIX source code licensees would -in the case the
code had been made available *by others* have no longer obligation to keep it
confidential.

But, and this is IMPORTANT, IANAL, so don't take my word for it. My guess is 
that even if so, most licensses will be reluctant to take any action without 
legal counsel, which is costly and unless they had a compelling reason to, 
they would therefore rather not ask, not act and not risk.

				j

-- 
	These opinions are mine and only mine. Hey man, I saw them first!

			    José R. Valverde

	De nada sirve la Inteligencia Artificial cuando falta la Natural
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20070925/faaa29f3/attachment.sig>


  reply	other threads:[~2007-09-25 14:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3367693331-1097@e4ward.com>
2007-09-20 13:48 ` Andrew Warkentin
2007-09-20 17:22   ` asbesto
2007-09-21 14:44     ` Tim Bradshaw
2007-09-21 14:58       ` John Cowan
2007-09-21 16:41         ` asbesto
2007-09-21 16:46           ` John Cowan
2007-09-21 17:22             ` asbesto
2007-09-21 17:29               ` M. Warner Losh
2007-09-21 19:11                 ` asbesto
2007-09-21 17:23           ` Seth Morabito
2007-09-21 17:47             ` Brantley Coile
2007-09-21 16:48         ` Tim Bradshaw
2007-09-21 17:12           ` John Cowan
2007-09-21 17:14           ` M. Warner Losh
2007-09-21 17:30             ` Brantley Coile
2007-09-21 18:24               ` M. Warner Losh
2007-09-21 20:58                 ` Bill Pechter
2007-09-22  9:32                   ` Wesley Parish
2007-09-25  1:52           ` John Cowan
2007-09-25 14:06             ` Jose R. Valverde [this message]
2007-09-25 14:38               ` M. Warner Losh
2007-09-25 15:37                 ` John Cowan
2007-09-25 15:41 Jose R. Valverde
  -- strict thread matches above, loose matches on Subject: below --
2007-09-20  2:20 Larry McVoy
2007-09-20  7:58 ` asbesto

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=20070925160647.65053bd4@veda.cnb.uam.es \
    --to=jrvalverde@cnb.uam.es \
    /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).