The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: rdkeys@unity.ncsu.edu (rdkeys@unity.ncsu.edu)
Subject: PUPS/TUHS UNIX scope.....
Date: Mon, 19 Jun 2000 16:06:24 -0400 (EDT)	[thread overview]
Message-ID: <200006192006.QAA21903@uni02du.unity.ncsu.edu> (raw)
In-Reply-To: <0006191425.AA05387@ivan.Harhan.ORG> from "Michael Sokolov" at Jun 19, 2000 09:25:44 AM

> According to Warren's Charter, PUPS and TUHS are both specifically for UNIX.
> His Charter defines UNIX as follows:
> 
> "Unix is defined as the set of operating systems who can trace their source
> code ancestry back to the 1st to 7th Editions of research UNIX from Bell Labs."
> 
> Any system that fits this definition automatically falls under the original
> UNIX copyright and may not be distributed outside the circle of UNIX source
> licensees. Therefore, if you think that FreeBSD fits this definition and
> belongs in this group, you must stop publicly distributing it. Otherwise, it
> does not belong in the archive or on these lists.

One might easily consider Warren's Charter definition, following the wording
closely, to mean that it includes successor derivatives of V1-V7.  That
might particularly include the BSD's, be they original CSRG code or
derived code, which can be traced back through CSRG, to V1-V7.

All of the x86ish derivations can be traced back to Jolitz's port which
had its beginnings around 4.3 or 4.3-Tahoe, if I am remembering the source
tree structure in one of my source trees.

Thus, technically, a direct lineal descent case of 386BSD, NetBSD, and
FreeBSD, up through the point of unencumbering, could be made as subject
to Warren's Charter definition, and subject to our archiving scope.

Bob




           reply	other threads:[~2000-06-19 20:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <0006191425.AA05387@ivan.Harhan.ORG>]

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=200006192006.QAA21903@uni02du.unity.ncsu.edu \
    --to=rdkeys@unity.ncsu.edu \
    /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).