The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Fwd: Re: Early BSD license thread
Date: Wed, 21 Sep 2022 17:46:58 -0400	[thread overview]
Message-ID: <CAC20D2MeRe5cOau9bTwzJOJTuQfcAjsAWZbpvuJh6bkD8YNByA@mail.gmail.com> (raw)
In-Reply-To: <Yyt+nhCR7ZL2y5ZR@mit.edu>

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

Sure.  And of course there will always be interpretations of how much one
idea salted another.  But the seeds of the discomfort come from these
various solutions and frankly how much the original authors were bought
into/part of the integration process.


On Wed, Sep 21, 2022 at 5:14 PM Theodore Ts'o <tytso@mit.edu> wrote:

> On Wed, Sep 21, 2022 at 10:57:51AM -0400, Clem Cole wrote:
> > The legal term '*copyright*' and historical term of '*provenance*.'    I
> > agree with Warner that I know of few if any cases where copyright was not
> > maintained when it was in the code itself.  And as he points out, please
> > grep through the archives and I think that will be found to hold true.
> >
> > But I also think Rob rankle comment is fair.  Joy and was noted for
> > recognizing cool ideas and adding them into 'Berkeley UNIX.  The line at
> > the time was he took ideas and '*peed on them to make them smell like
> > Berkeley*.' For example, 'Berkeley Joy Control' came from Kulp via Europe
> > and MIT, the network stack famously started at BBN, and a lot of the
> > support for limits and user controllers from Australia.
> >
> > Yes, the CSRG team did do a great deal of innovation as well as
> > integration, but the line between the two was not always easy to see from
> > the outside.
>
> Well, there can be a huge spectrum here, isn't there?   Ranging from:
>
> * Take the code wholesale with no changes.
>
> * Take the code and make changes to match with local coding style.
>
> * Take the code and serially rewrite it so when you're done it
>   only vaguely resembles the original contribution.
>
> * Look at the code, get the ideas, and the reimplement it from
>   scratch, keeping the existing interface (or using the existing
>   interface as a starting point before extending it)
>
> * Look at the code, get the ideas, and reimplent it from scratch
>   with radically different interfaces.
>
> It sounds like all of these were used to some extent as part of the
> BSD/CSRG integration process; is that right?
>
>                                                 - Ted
>
-- 
Sent from a handheld expect more typos than usual

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

  reply	other threads:[~2022-09-21 21:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 10:10 [TUHS] " Warner Losh
2022-09-21 12:36 ` [TUHS] " Rob Pike
2022-09-21 13:33   ` Marc Donner
2022-09-21 13:46   ` Warner Losh
2022-09-21 14:50     ` Rich Salz
2022-09-21 14:58       ` Warner Losh
2022-09-21 15:06         ` Miod Vallat
2022-09-21 14:57     ` [TUHS] Fwd: " Clem Cole
2022-09-21 15:09       ` [TUHS] " Larry McVoy
2022-09-21 15:25       ` Warner Losh
2022-09-21 22:06         ` [TUHS] " Bakul Shah
2022-09-21 22:20           ` Warner Losh
2022-09-21 21:14       ` [TUHS] Re: Fwd: " Theodore Ts'o
2022-09-21 21:46         ` Clem Cole [this message]
2022-09-21 21:49   ` [TUHS] " Phil Budne
2022-09-21 22:07     ` Rich Salz
2022-09-21 22:24       ` Warner Losh
2022-09-21 22:09     ` Dan Cross
2022-09-21 22:19       ` Steve Nickolas
2022-09-21 22:44         ` Joseph Holsten
2022-09-21 23:53           ` Chet Ramey
2022-09-22  0:32             ` Rob Pike
2022-09-22  7:08       ` [TUHS] " Andy Kosela
2022-09-22 17:44         ` [TUHS] " Dan Cross
2022-09-22 18:44           ` Bakul Shah

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=CAC20D2MeRe5cOau9bTwzJOJTuQfcAjsAWZbpvuJh6bkD8YNByA@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=tuhs@tuhs.org \
    --cc=tytso@mit.edu \
    /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).