From: Warner Losh <imp@bsdimp.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Speaking of legality...
Date: Wed, 5 Sep 2018 13:37:07 -0600 [thread overview]
Message-ID: <CANCZdfr_nK-grF5_sXfAb-YUr0xmWHhdgJPWvOitJA6KW-GzqA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2OP9svQUm01d0r6UPF_=8nrg46HfMoTiu_T+Ek=rTBe9Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
On Wed, Sep 5, 2018 at 1:17 PM Clem Cole <clemc@ccc.com> wrote:
>
>
> On Tue, Sep 4, 2018 at 11:48 PM Warren Toomey <wkt@tuhs.org> wrote:
>
>> 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.
>>
>> Right, but the AT&T parts you need to be sure to attribute them,
>
>
Of course...
Warner
> ᐧ
>
[-- Attachment #2: Type: text/html, Size: 2151 bytes --]
prev parent reply other threads:[~2018-09-05 19:37 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
2018-09-05 19:17 ` Clem Cole
2018-09-05 19:37 ` Warner Losh [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=CANCZdfr_nK-grF5_sXfAb-YUr0xmWHhdgJPWvOitJA6KW-GzqA@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=clemc@ccc.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).