From: ron minnich <rminnich@gmail.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: Marc Rochkind <mrochkind@gmail.com>, tuhs@tuhs.org
Subject: [TUHS] Re: SCO's "evidence" (was: RIP Darl McBride former CEO of SCO)
Date: Mon, 4 Nov 2024 17:32:19 -0800 [thread overview]
Message-ID: <CAP6exY+V5nYiCN_b1Kxn49kkedcFaEiiDuAQu-nAr2zefRGh7w@mail.gmail.com> (raw)
In-Reply-To: <20241105010937.GC18296@mcvoy.com>
[-- Attachment #1: Type: text/plain, Size: 1969 bytes --]
I had people relate to me, at least once, cases of utterly independent
implementations of a function that were byte for byte the same, as found in
one court case a friend of mine (now deceased) got pulled into. He had to
prove he'd written his code from scratch. But these were pretty simple
functions. I don't know if bmap qualifies ...
How could this happen? I don't know, but the court case that long predated
SCO. The only conclusion I can reach
is that when enough techniques, ideas, mailling lists, discussions, and
documents become part of a shared culture, the code which
people create might be the same. A weird parallel evolution of code.
On Mon, Nov 4, 2024 at 5:09 PM Larry McVoy <lm@mcvoy.com> wrote:
> The thing I never got a reasonable answer to was I found code in BSD that
> was identical to code going back to at least V7. Find bmap() in the UFS
> code and then find the same in V7. I might be wrong about V7, might be
> 32V, might be V6. I don't think it matters, it's the same in all of them.
>
> bmap() is the code that maps a logical block to a phsyical block,
> I'm quite familiar with it because I rewrote it to bmap_write() and
> bmap_read() as part of making UFS do extents:
>
> http://mcvoy.com/lm/papers/SunOS.ufs_clustering.pdf
>
> When all the lawsuits were going on, since I knew that code really well,
> I went off and looked and the BSD code at that time had bit for bit
> identical bmap() implementations.
>
> I never understood why BSD could claim they rewrote everything when they
> clearly had not rewritten that.
>
> I've raised this question before and I just went and looked, bmap() has
> changed. I'm pretty sure I have Kirk's BSD source releases, if I do,
> I'm 100% sure I can back up what I'm saying. Not sure I care enough to
> do so, it's all water under the bridge at this point.
> --
> ---
> Larry McVoy Retired to fishing
> http://www.mcvoy.com/lm/boat
>
[-- Attachment #2: Type: text/html, Size: 2635 bytes --]
next prev parent reply other threads:[~2024-11-05 1:32 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 1:17 [TUHS] RIP Darl McBride former CEO of SCO Will Senn
2024-11-04 2:31 ` [TUHS] " Greg 'groggy' Lehey
2024-11-04 3:34 ` Wesley Parish
2024-11-04 17:35 ` Marc Rochkind
2024-11-04 22:50 ` [TUHS] SCO's "evidence" (was: RIP Darl McBride former CEO of SCO) Greg 'groggy' Lehey
2024-11-05 0:05 ` [TUHS] " Marc Rochkind
2024-11-05 0:39 ` Warner Losh
2024-11-05 1:09 ` Larry McVoy
2024-11-05 1:32 ` ron minnich [this message]
2024-11-05 1:39 ` Warner Losh
2024-11-05 3:14 ` Larry McVoy
2024-11-05 5:00 ` Warner Losh
2024-11-05 1:35 ` Warner Losh
2024-11-05 1:54 ` Larry McVoy
2024-11-05 2:13 ` Warner Losh
2024-11-05 3:14 ` Marc Rochkind
2024-11-07 20:41 ` ron minnich
2024-11-07 20:59 ` Marc Rochkind
2024-11-08 0:03 ` Theodore Ts'o
2024-11-08 0:35 ` Warner Losh
2024-11-09 18:29 ` G. Branden Robinson
2024-11-09 20:30 ` Theodore Ts'o
2024-11-09 22:23 ` G. Branden Robinson
2024-11-10 4:27 ` Theodore Ts'o
2024-11-12 1:55 ` Kevin Bowling
2024-11-12 2:34 ` Kevin Bowling
2024-11-12 18:12 ` Marc Rochkind
2024-11-05 1:31 ` [TUHS] IBM's involvement (was: SCO's "evidence" (was: RIP Darl McBride former CEO of SCO)) Greg 'groggy' Lehey
2024-11-05 3:04 ` [TUHS] " Marc Rochkind
2024-11-06 4:00 ` Greg 'groggy' Lehey
2024-11-05 17:55 [TUHS] Re: SCO's "evidence" (was: RIP Darl McBride former CEO of SCO) Noel Chiappa
2024-11-05 18:52 ` ron minnich
2024-11-05 19:01 ` Warner Losh
[not found] ` <CAEoi9W66zUf8RvzEYQG7qNXN-BX6gyDejXCrHw3rk46UM_-XPg@mail.gmail.com>
2024-11-08 20:27 ` Warner Losh
[not found] ` <61F8BCE5-44C5-49D2-BEFE-B8717E3DDEA8@kdbarto.org>
[not found] ` <CANCZdfrJExbrJqp3MgE0Tp9-a=PYTeFpkULk8NnPfBTeoyLW-g@mail.gmail.com>
2024-11-08 23:18 ` [TUHS] Fwd: " Warner Losh
2024-11-09 0:40 ` [TUHS] " rob
2024-11-05 18:58 ` Warner Losh
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=CAP6exY+V5nYiCN_b1Kxn49kkedcFaEiiDuAQu-nAr2zefRGh7w@mail.gmail.com \
--to=rminnich@gmail.com \
--cc=lm@mcvoy.com \
--cc=mrochkind@gmail.com \
--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).