The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jason Stevens <jsteve@superglobalmegacorp.com>
To: Greg 'groggy' Lehey <grog@lemis.com>, Warner Losh <imp@bsdimp.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Status of Net/2
Date: Tue, 18 May 2021 09:33:40 +0800	[thread overview]
Message-ID: <2d3a0a5a-bd46-4a8d-bf1d-8f95f949a316@PU1APC01FT027.eop-APC01.prod.protection.outlook.com> (raw)
In-Reply-To: <20200516013930.GG1670@eureka.lemis.com>

[-- Attachment #1: Type: text/plain, Size: 2751 bytes --]

Nobody ever said peep when I ‘mashed’ enough 386BSD and what was available from NetBSD 0.9 and the NetBSD 0.8 to make 0.8 work…  The closest I got is ‘why do you want that we have version 17!’ or whatever $HEAD is .  I guess in the same way I was more interested in preserving 386BSD 0.0, and again nobody ever told me to stop.

I guess in the same way nobody told me to stop making Mach 2.6 available, or even Darwin 0.3 for i386.

I wanted to take that IBM 4.4BSD and try to replace enough of 386BSD 0.1 pl32 to have something more akin to ‘real’ 4.4 BSD.  Although I have a bunch of things I need to wrap up before I take that on (people are actually looking for bug fixes for Quake II on MS-DOS of all things….).

I don’t think its exactly policed like 1984, although I think people are more excited about RIAA/MPAA than things like Unix.

(shrug)


From: Greg 'groggy' Lehey
Sent: Saturday, May 16, 2020 9:41 AM
To: Warner Losh
Cc: The Eunuchs Hysterical Society
Subject: Re: [TUHS] Status of Net/2

On Friday, 15 May 2020 at 18:49:44 -0600, Warner Losh wrote:
> What's the current status of net/2?
>
> I ask because I have a FreeBSD 1.1.5.1 CVS repo that I'd like to make
> available. Some of the files in it are encumbered, though, and the
> University of California has communicated that fact. But what does
that
> actually mean now that V7 has been released and that's what the files
were
> based on? Are they no longer encumbered?

To the best of my knowledge, Net/2 would be covered by the license
granted by Caldera on 23 January 2002:

  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

I'm attaching the PDF of the license agreement, along with an email
from Dion Johnson to wkt (misspelt as wht) the following day.

It doesn't specifically address any particular operating system, but
it was my understanding that this would free all BSD versions.

Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA



[-- Attachment #2: Type: text/html, Size: 5574 bytes --]

  parent reply	other threads:[~2021-05-18  1:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16  0:49 Warner Losh
2020-05-16  0:56 ` Clem Cole
2020-05-16  1:39 ` Greg 'groggy' Lehey
2020-05-16  2:28   ` Jeremy C. Reed
2021-05-18  1:33   ` Jason Stevens [this message]
2021-05-19 22:36     ` Warner Losh

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=2d3a0a5a-bd46-4a8d-bf1d-8f95f949a316@PU1APC01FT027.eop-APC01.prod.protection.outlook.com \
    --to=jsteve@superglobalmegacorp.com \
    --cc=grog@lemis.com \
    --cc=imp@bsdimp.com \
    --cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).