From: Clem Cole <clemc@ccc.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: segaloco <segaloco@protonmail.com>, TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Re-implementations/Clean-Rooms et al.
Date: Thu, 8 Sep 2022 19:34:13 -0400 [thread overview]
Message-ID: <CAC20D2Mi_gi5jh-gLCBG9aYSJyXxme5_h9AFAM95pJR4vL0OOQ@mail.gmail.com> (raw)
In-Reply-To: <20220908221639.GR11929@mcvoy.com>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
On Thu, Sep 8, 2022 at 6:16 PM Larry McVoy <lm@mcvoy.com> wrote:
> > It was rewritten over time,
> > which replaced AT&T's implementation. Which is all that was ever
> claimed.
>
> And it's a false claim.
>
I believe you. But BSD's rewrite was good enough. The real key is the
BSDi/UCB *vs.* USL/AT&T case was *not about the code (or copyrights).* That
is the piece most hackers don't seem to understand. The case was about *trade
secrets (or not) *and thus the *ideas*. BSDi/UCB released their system
which clearly had started with code that had originated with AT&T and thus
the *ideas* had to have originated there too.
I think too many hackers get caught up in FOSS, GPL,* et al,* and miss the
point.
The real debt which we can never repay Doug, Ken, Dennis, and friends was
their *ideas* and the way they broke down and solved problems. The code
is a by-product, the existence proof that it was more than theory, but had
a practical use.
ᐧ
[-- Attachment #2: Type: text/html, Size: 2596 bytes --]
next prev parent reply other threads:[~2022-09-08 23:35 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 [this message]
2022-09-08 22:17 ` 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=CAC20D2Mi_gi5jh-gLCBG9aYSJyXxme5_h9AFAM95pJR4vL0OOQ@mail.gmail.com \
--to=clemc@ccc.com \
--cc=lm@mcvoy.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).