The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] Status of, and licensing of the so called "Ancient UNIX" products
Date: Thu, 27 Feb 2003 09:14:58 +1030	[thread overview]
Message-ID: <20030226224458.GN66520@wantadilla.lemis.com> (raw)
In-Reply-To: <002401c2ddd8$af4e1680$38c5580c@who5>

On Wednesday, 26 February 2003 at 15:50:06 -0500, Gregg C Levine wrote:
> Hello again from Gregg C Levine
> I know I asked this question early on, and I remember, and have the
> original answer filed someplace.... But that was about a year ago.
> Since then I had heard a rumor that the current Copyright Owner of the
> "Ancient UNIX" products had in fact re-released the products under the
> exact same license that both Minix, and BSD use.

That's not possible.  The licenses aren't the same.

> In fact they could called a freely releasable product. Can someone
> on this list confirm this?

Yes.  It went around on this list at the time.  I'll attach the
message again below.

Greg
--
Finger grog at lemis.com for PGP public key
See complete headers for address and phone numbers
Please note: we block mail from major spammers, notably yahoo.com.
See http://www.lemis.com/yahoospam.html for further details.
-------------- next part --------------
An embedded message was scrubbed...
From: Dion Johnson <dionj@caldera.com>
Subject: Liberal license for ancient UNIX sources
Date: Wed, 23 Jan 2002 15:03:37 -0800
Size: 26173
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20030227/84de5aaf/attachment.mht>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20030227/84de5aaf/attachment.sig>


      reply	other threads:[~2003-02-26 22:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26 20:50 Gregg C Levine
2003-02-26 22:44 ` Greg 'groggy' Lehey [this message]

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=20030226224458.GN66520@wantadilla.lemis.com \
    --to=grog@lemis.com \
    /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).