The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warren Toomey <wkt@tuhs.org>
To: Warner Losh <imp@bsdimp.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Speaking of legality...
Date: Wed, 5 Sep 2018 13:48:05 +1000	[thread overview]
Message-ID: <20180905034805.GA23662@minnie.tuhs.org> (raw)
In-Reply-To: <CANCZdfq0R1EtVQ4=MhAB4M+F7pPxCq=fCDXUcP516=xxRV3=2g@mail.gmail.com>

On Tue, Sep 04, 2018 at 09:39:40PM -0600, Warner Losh wrote:
>    I'm trying to recreate "a" source representation of the Venix for
>    Rainbow that I have. It's a v7 port, and I have all the .o's for it.
>    Most of the .o's compile, with the proper compiler, to the same code
>    that are in the .o's, at least judging from the .c file of the same
>    name in the TUHS archive.
>    The question is, what are the legal ramifications of publishing my
>    reconstruction?

Good question. IANAL of course. Obviously, it's a port of V7 and the
vanilla V7 is now under a free license. So I would guess that you only
have to worry about the files in Venix which are different: drivers etc.

Cheers, Warren

  reply	other threads:[~2018-09-05  3:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-05  3:39 Warner Losh
2018-09-05  3:48 ` Warren Toomey [this message]
2018-09-05 19:17   ` Clem Cole
2018-09-05 19:37     ` 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=20180905034805.GA23662@minnie.tuhs.org \
    --to=wkt@tuhs.org \
    --cc=imp@bsdimp.com \
    --cc=tuhs@minnie.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).