The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Caldera ancient UNIX license question
Date: Mon, 13 Aug 2012 08:24:46 -0600	[thread overview]
Message-ID: <D435D051-A0C0-4007-B4E8-552311C9C5C7@bsdimp.com> (raw)
In-Reply-To: <201208130828.q7D8S0Va011757@freefriends.org>


On Aug 13, 2012, at 2:28 AM, arnold at skeeve.com wrote:

> Larry McVoy <lm at bitmover.com> wrote:
> 
>>> I'm
>>> sure there are other (mainly smaller) examples, though since we
>>> used no source-code control mechanism, tracing the details is
>>> non-trivial.
>> 
>> No SCCS?  When did Rochkind do SCCS?  Wasn't it early 70's?  I gotta believe
>> there is SCCS history out there.  And for the record, BitKeeper can read it.
> 
> I think Norman's point was that the Research guys didn't use a source
> code control system.  SCCS was around and documented in System III in 1980,
> so it was probably done before then, but not in the research group.

And even with a source code control system, it can be hard to know if there's an IP issue from commit logs, since they often are of the form "more" or "better" or "latest version" when there's isn't a culture of good commit messages.  And even when there is, if there isn't a good culture of documenting upstream sources, it can be hard.  And until at least a decade into the open source revolution there wasn't a general practice in the open source community about documenting upstream sources.

I defy you, for example, to identify with enough certainty to convince a corporate lawyer who actually wrote any of the code in Linux that's still around from the 0.9x or 1.0 time frame...  You can find all the tar.gz files from the time frame, and use tools to track which lines are still around, but knowing who actually wrote it can be tricky unless the patches hit a mailing list or had some other paper trail...  And the Linux development community was a lot more open and public than developments that happened 25 years ago to some IP that's changed hands a bunch of times...

Warner




  parent reply	other threads:[~2012-08-13 14:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13  2:59 Norman Wilson
2012-08-13  4:02 ` Larry McVoy
2012-08-13  8:28   ` arnold
2012-08-13 11:52     ` Brantley Coile
2012-08-13 13:05     ` Ronald Natalie
2012-08-13 14:24     ` Warner Losh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-08-10 19:30 סטֵפָן פָּבִיקֵבִיק
2012-08-10 20:47 ` ron
2012-08-10 21:42   ` Benjamin Huntsman
2012-08-11  7:51     ` Wesley Parish
2012-08-11 18:33       ` Tim Newsham
2012-08-11 19:08         ` Warner Losh
2012-08-11 23:04           ` A. P. Garcia

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=D435D051-A0C0-4007-B4E8-552311C9C5C7@bsdimp.com \
    --to=imp@bsdimp.com \
    /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).