The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: random832@fastmail.com (Random832)
Subject: [TUHS] Why Linux not another PC/UNIX [was Mach for i386 ...]
Date: Thu, 23 Feb 2017 15:31:04 -0500	[thread overview]
Message-ID: <1487881864.3245413.890885432.69DE979F@webmail.messagingengine.com> (raw)
In-Reply-To: <CAC20D2MnDo8U8AYR2mgH+m_kRRMDQ8H8k6nSDyDbz8AhBymw1Q@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3054 bytes --]

On Thu, Feb 23, 2017, at 14:15, Clem Cole wrote:
> On Wed, Feb 22, 2017 at 6:51 PM, Paul Ruizendaal <pnr at planet.nl> wrote:
> 
> > I'm not a lawyer, but wasn't part of the background that prior to 1988
> > in US law one could not claim both copyright and trade secret protection,
> > and that for something to be copyrighted it had to expressly claim to
> > be copyrighted material, and be registered as such?
> >
> ​Take this with what its worth (it came for free and I'm not a lawyer
> ....) > Your comment got me thinking, why would try to change and can you.  So I
> asked on our patent counsel this am to explain the difference.  For
> context in the USA we have Patent, Trade Secret, Copyright Registration and
> Copyright Protection.   Her reply to me was:
> 
> Copyright *protection* is automatic – as soon as the code is written it
> is
> considered protected.  Copyright *registration* is just a formality
> necessary to instigate litigation.  There is no time limit for
> registration.

That's true today, but to my understanding wasn't true in 1988. (Well,
registration wasn't a requirement to be copyrighted - that requirement
went away retroactively in 1978, and only applied to unpublished works
then.) The change seems to have been March 1, 1989 from what I can find.

I think AT&T *tried* to construct a basis to claim that UNIX source code
was "unpublished", even when distributed to source licensees (or e.g.
shell scripts which were by necessity distributed to all licensees),
possibly in service of this trade secret theory. Remember, the infamous
comment on the otherwise empty SVR2 /bin/true had two lines of copyright
notice and three lines of assertion that it was unpublished.

And if that attempt involved removing all copyright notices from V6, V7,
and 32V (and presumably not registering any copyright on any
"unpublished" works pre-1978) then that might have killed any
copyright-based case. By the time the actual lawsuit happened, they were
fully committed to the trade secret theory.


> Dennis Ritchie wrote:
> >
> > "Paul" <pssawyer at comcast.net.INVALID> wrote in message >>
> >   ....
> >> ISTR there was a copyright notice in a Sys V /bin/true; explaining
> >> why we thought this was funny might be a violation of that copyright!
> >
> > The local lawyers here also flip-flopped over the copyright issue.
> > I can't recall whether it was because of law changes or reinterpretation
> > or whether they just changed their minds.  The issue partly had to do
> > with the question of whether a copyright claim amounted to publication,
> > while their primary protection theory had to do with trade secret
> > protection, and its possible conflict with publication.
> >
> > At any rate, here is the whole contents of /bin/true in SVr2:
> >
> > # Copyright (c) 1984 AT&T
> > #   All Rights Reserved
> >
> > # THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF AT&T
> > # The copyright notice above does not evidence any
> > # actual or intended publication of such source code.
> >
> > #ident "@(#)true:true.sh 1.4"


  reply	other threads:[~2017-02-23 20:31 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22  3:38 Clem Cole
2017-02-22  4:28 ` Dan Cross
2017-02-22 15:36   ` Clem Cole
2017-02-22 16:11     ` Larry McVoy
2017-02-22 17:00       ` Clem Cole
2017-02-22 17:06         ` Chet Ramey
2017-02-22 18:24         ` Larry McVoy
2017-02-22 19:35           ` Clem Cole
2017-02-22 20:18             ` arnold
2017-02-22 22:11               ` Clem Cole
2017-02-22 21:34             ` Larry McVoy
2017-02-22 22:56               ` Clem Cole
2017-02-22 23:13                 ` Larry McVoy
2017-02-22 23:51                   ` Clem Cole
2017-02-22 23:51           ` Paul Ruizendaal
2017-02-23 19:15             ` Clem Cole
2017-02-23 20:31               ` Random832 [this message]
2017-02-23 22:48                 ` Joerg Schilling
2017-02-24  2:07                   ` Jason Stevens
2017-02-23 23:06                 ` Wesley Parish
2017-02-22 17:41       ` Arthur Krewat
2017-02-22 21:00     ` Michael Kerpan
2017-02-22 22:03       ` Arno Griffioen
2017-02-22 22:51         ` Larry McVoy
2017-02-22 23:29         ` Clem Cole
2017-02-23  4:53           ` Gregg Levine
2017-02-22 22:18       ` Clem Cole
2017-02-24  3:53     ` Dan Cross
2017-02-22  5:56 ` Steve Nickolas
2017-02-24  5:31   ` John Labovitz

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=1487881864.3245413.890885432.69DE979F@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).