From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] /bin/true (was basic tools / Universal Unix)
Date: Tue, 28 Nov 2017 15:34:54 -0500 [thread overview]
Message-ID: <CAC20D2MxmsbiwEDgWKHdnpXAckyg_-pfR+rCiuoMcW-uJ2AWWQ@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W4ZDOAJ1KHym6yRbyJh7mAdL3FVD9f292A3R8UYhHKOdw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
I'm not a lawyer nor play one on TV. That said, I talk to a lot of them
and have worked for firms that have to deal with this sort of issue. Your
milage may vary ....
On Tue, Nov 28, 2017 at 2:09 PM, Dan Cross <crossd at gmail.com> wrote:
> I can't think of a great use case for embedding copyright data into an
> object file, however.
>
This is from some one who used to work for TPC who took out a copyright on
every page in the phone directory.
As I understand it from my legal folks, it is all post the Franklin/Apple
case. Making sure all object files also have legally recognized set of
stamps in them.
I suspect one can argue with the judge that a single copyright notice are
coving all of the SCCS stamps on from all the files shipped in the release
(source or binary). But just like putting a copyright on every page in the
phone book, I think the argument is that a page can ripped from the phone
book and a binary and can copied from a system. Because of the 'motion'
of the object, making sure every object has a mark is best.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171128/a1a90a56/attachment.html>
next prev parent reply other threads:[~2017-11-28 20:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 14:52 /bin/true (was [TUHS] " Ron Natalie
2017-10-19 15:01 ` Pete Wright
2017-10-19 15:17 ` Chet Ramey
2017-10-19 21:23 ` Steffen Nurpmeso
2017-10-19 21:43 ` Chet Ramey
2017-10-19 23:00 ` [TUHS] /bin/true (was " Dave Horsfall
2017-10-19 23:14 ` Grant Taylor
2017-10-19 23:23 ` Lyndon Nerenberg
2017-10-19 23:27 ` Kurt H Maier
2017-10-22 4:18 ` Dave Horsfall
2017-10-20 12:10 ` Chet Ramey
2017-10-19 21:43 ` /bin/true (was [TUHS] " Dave Horsfall
2017-10-19 22:04 ` Ronald Natalie
2017-10-19 23:25 ` [TUHS] /bin/true (was " Dave Horsfall
[not found] ` <CAEoi9W7YZ7YXUip0JTMGip3Nd0czgdjqRCMRcK2GYmDJsckuDg@mail.gmail.com>
[not found] ` <CAEoi9W4zdJ3+RXjK5-5rAJ6rwx_0kx6N-bn1U61=txJGyLT_mw@mail.gmail.com>
2017-10-20 1:27 ` Dan Cross
2017-10-20 1:31 ` Lyndon Nerenberg
2017-10-20 2:05 ` Ronald Natalie
2017-11-28 16:21 ` Nemo
2017-11-28 17:56 ` Warner Losh
2017-11-28 18:26 ` Dan Cross
2017-11-28 18:41 ` Warner Losh
2017-11-28 19:09 ` Dan Cross
2017-11-28 20:34 ` Clem Cole [this message]
2017-11-28 22:42 ` Ralph Corderoy
2017-11-28 18:34 ` Bakul Shah
2017-11-28 23:25 ` Ralph Corderoy
2017-10-22 23:00 Doug McIlroy
2017-10-23 1:11 ` Dan Cross
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=CAC20D2MxmsbiwEDgWKHdnpXAckyg_-pfR+rCiuoMcW-uJ2AWWQ@mail.gmail.com \
--to=clemc@ccc.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).