From: Warner Losh <imp@bsdimp.com>
To: Clem Cole <clemc@ccc.com>
Cc: segaloco <segaloco@protonmail.com>, TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Re-implementations/Clean-Rooms et al.
Date: Thu, 8 Sep 2022 16:17:42 -0600 [thread overview]
Message-ID: <CANCZdfrhcQeBw3jGGt3op-rG4veLv-ffbJm4EKQYDYL57-73rg@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2Mqmg9uvVxPdGKJocceW8c22zz1sM0RobJTkbhF5ywi1w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1583 bytes --]
On Thu, Sep 8, 2022 at 3:52 PM Clem Cole <clemc@ccc.com> wrote:
> On Thu, Sep 8, 2022 at 12:51 PM segaloco via TUHS <tuhs@tuhs.org> wrote:
>
>> Both Coherent and 4.4BSD have stuck out to me as examples of
>> not-quite-so-clean-room implementations that did well enough (more than
>> enough for BSD) and didn't die a fiery death in litigation (as much as USL
>> tried...).
>
> BSDi/UCB *vs. *USL was a different kettle of fish altogether. As has
> been discussed here extensively (and needs not to be repeated), that suit
> was about *Trade Secrets and >>ideas<< that make up what we call UNIX.*
> The real interesting thing about that case is that had USL/AT&T won, the
> repercussions for the industry would have been way beyond just BSDi - *but
> all of the UNIX clones* and many of us on this list who had been
> "mentally contaminated" with AT&T's ideas (I still have my 'mental
> contamination' button somewhere in my archives).
>
Yes. Indeed. It devolved to a copyright battle with the ultimate result
being a preliminary ruling that 32V (and V6 and V7 likely) had no copyright
protection because AT&T had distributed too many copies without the
required (at the time) copyright notices... That preliminary ruling is
what forced the settlement of the suit, and is the reason that 4.4BSD-lite
had a bunch of files with AT&T copyrights on them with permission to
redistribute liberally...
These days, in open source cleanroom is rarely done except in extraordinary
cases. It's easier to read the code and reimplement because copyright
covers only the typing...
Warner
>
[-- Attachment #2: Type: text/html, Size: 2776 bytes --]
prev parent reply other threads:[~2022-09-08 22:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 21:50 Clem Cole
2022-09-08 22:16 ` Larry McVoy
2022-09-08 22:26 ` Warner Losh
2022-09-08 22:28 ` Warner Losh
2022-09-08 23:30 ` Steve Nickolas
2022-09-08 23:42 ` Warner Losh
2022-09-09 0:05 ` Steve Nickolas
2022-09-09 0:17 ` Larry McVoy
2022-09-09 0:52 ` Steve Nickolas
2022-09-09 2:16 ` Larry McVoy
2022-09-08 23:34 ` Clem Cole
2022-09-08 22:17 ` 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=CANCZdfrhcQeBw3jGGt3op-rG4veLv-ffbJm4EKQYDYL57-73rg@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=clemc@ccc.com \
--cc=segaloco@protonmail.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).