The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: Steve Jenkin <sjenkin@canb.auug.org.au>, TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Has this been discussed on-list? How Unix changed Software.
Date: Thu, 8 Sep 2022 12:47:56 -0400	[thread overview]
Message-ID: <CABH=_VSDKNiwYJ1_fNWuxdcV1DPBNj07tke+PhSqO14AC61GBg@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfri0BPfOcTX+Tcp_CnjcPjOmQZSS8Jet3ZFOuKu6krU_w@mail.gmail.com>

On 9/8/22, Warner Losh <imp@bsdimp.com> wrote:
>
> In addition, when Dennis would talk about Coherent and his evaluation of
> the source code, he said he used the known to him, but not widely known
> bugs in Unix to try to catch copying. If there was copying, those would be
> copied. If it was freshly implemented, there's a high likelihood that they
> wouldn't. His conclusion was that someone had access to a lot of knowledge
> about the Unix system given the fidelity of the implementation, but the
> lack of bugs and novel ways of doing it suggested independent
> implementation.

The software equivalent of a common technique used by mapmakers to
detect copying.  You sprinkle a few fake locations or other deliberate
errors into your map.  If these show up in a competitor's map you know
they were copied.

-Paul W.

  reply	other threads:[~2022-09-08 16:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06 15:07 Douglas McIlroy
2022-09-06 17:13 ` Larry McVoy
2022-09-07  1:40 ` steve jenkin
2022-09-07  2:33   ` segaloco via TUHS
2022-09-07  4:08     ` Steve Jenkin
2022-09-07 13:08   ` Steffen Nurpmeso
2022-09-07 14:56   ` Larry McVoy
2022-09-07 21:27     ` Steve Jenkin
2022-09-07 22:36       ` Larry McVoy
2022-09-08 14:42       ` Paul Winalski
2022-09-08 15:02         ` Larry McVoy
2022-09-08 15:04         ` ron minnich
2022-09-08 15:52           ` Warner Losh
2022-09-08 16:47             ` Paul Winalski [this message]
2022-09-08 16:50             ` segaloco via TUHS
2022-09-08 17:58               ` ron minnich
  -- strict thread matches above, loose matches on Subject: below --
2022-09-06 19:04 Douglas McIlroy
2022-09-05 23:48 [TUHS] " steve jenkin
2022-09-06 16:09 ` [TUHS] " Marc Donner
2022-09-07  4:00   ` steve jenkin
2022-09-07 14:58     ` John Cowan
2022-09-07 17:13     ` Paul Winalski
2022-09-08 14:12       ` Paul Winalski
2022-09-07  5:15   ` steve jenkin
2022-09-07 13:20     ` Dan Cross
2022-09-07 13:52       ` Steve Nickolas

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='CABH=_VSDKNiwYJ1_fNWuxdcV1DPBNj07tke+PhSqO14AC61GBg@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=imp@bsdimp.com \
    --cc=sjenkin@canb.auug.org.au \
    --cc=tuhs@tuhs.org \
    /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).