The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: random832@fastmail.com (Random832)
Subject: [TUHS] GNU vs BSD before the lawsuit and before Linux
Date: Sat, 18 Mar 2017 13:45:33 -0400	[thread overview]
Message-ID: <1489859133.340763.915600080.44C5EE3F@webmail.messagingengine.com> (raw)
In-Reply-To: <201703181625.v2IGPq1X066486@tahoe.cs.Dartmouth.EDU>

On Sat, Mar 18, 2017, at 12:25, Doug McIlroy wrote:
> Nick asked for an exmple of AT&T code in Gnu.
> Warner explained a spectrum of ways and degrees of innocence
> by which that might happen.
> 
> The example I have in mind is "calendar" from v7, whose very
> idiosyncratic implementation appeared in Gnu with only
> cosmetic changes. It has been modified since by discarding
> archaic efficiency hacks, but still uses the same quirky
> basic method.

The "calendar" available my Linux machine is from the "bsdmainutils"
package (which has never been put under the GPL, incidentally) which is
stuff copied with attribution from FreeBSD/NetBSD/OpenBSD, and
calendar.c has a UCB copyright/license and OpenBSD RCS ID at the top of
the file. (In the TUHS archive, this implementation first appears in
4.3BSD-Reno, with earlier versions having code clearly derived from V7).

The earliest version (from Debian 1.1) that I can find has a UCB
copyright dated 1993 and SCCS ID 8.3 3/25/94, not much removed from
4.4BSD in the archive (which has SCCS ID 8.1 6/6/93) - my guess is that
the actual source is 4.4BSD-Lite, which is mentioned in the bsdmainutils
README.

In the converted-to-git CSRG archive, the implementation first appears
in 1989 by "bostic" (Keith Bostic, presumably)
https://github.com/weiss/original-bsd/commit/46857f6fe723eff85f22986beb78063f05b60f78
with the change note "redone from scratch as a C program to fix cpp
security problem" - this is the first version to have a UCB copyright
notice. [Using cpp seems to have itself been a BSD innovation circa
4.1cBSD]

V7 calendar consists of a C program that outputs a set of regexes, and a
shell script that runs egrep. Unless by "same quirky basic method" you
mean the fact that it reads events from a text file at all, I'm not sure
what you're referring to... but that's functionality rather than
implementation.

There's a lot of code in a handful of not-part-of-GNU-proper core
utility packages used in Linux distributions - bsdmainutils, bsdgames,
bsdutils, and util-linux [only the last of which has the GPL] - which
come from some BSD or another and mostly have intact UCB copyright
statements and licenses at the top. If any of these are improperly
attributed, it's likely that UCB is to blame.

> Conceivably Gnu's implementation was done only after v7
> code was made public. But in any event, it has been
> distributed without attribution.
> 
> Doug


  reply	other threads:[~2017-03-18 17:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18 13:07 Doug McIlroy
2017-03-18 13:27 ` Nick Downing
2017-03-18 15:19   ` Warner Losh
2017-03-18 16:25     ` Doug McIlroy
2017-03-18 17:45       ` Random832 [this message]
2017-03-18 19:23         ` Warner Losh
  -- strict thread matches above, loose matches on Subject: below --
2017-03-18 12:45 Doug McIlroy
2017-03-14 14:43 [TUHS] System Economics (was is Linux "officially branded UNIX") Clem Cole
2017-03-14 15:38 ` Larry McVoy
2017-03-14 15:51   ` Arthur Krewat
2017-03-14 15:57     ` Michael Kjörling
2017-03-14 16:20       ` Arthur Krewat
2017-03-14 18:41         ` Warner Losh
2017-03-17 18:16           ` [TUHS] GNU vs BSD before the lawsuit and before Linux Tony Finch
2017-03-17 18:52             ` Jeremy C. Reed
2017-03-19  7:18               ` arnold
2017-03-19  9:05                 ` Wesley Parish
2017-03-19 18:37                 ` Warner Losh
2017-03-17 19:54             ` Ron Natalie

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=1489859133.340763.915600080.44C5EE3F@webmail.messagingengine.com \
    --to=random832@fastmail.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).