From: Marc Rochkind <mrochkind@gmail.com>
To: imp@bsdimp.com
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: SCO's "evidence" (was: RIP Darl McBride former CEO of SCO)
Date: Mon, 4 Nov 2024 20:14:19 -0700 [thread overview]
Message-ID: <CAOkr1zU6jXf9hXqyHNt7OiqyCkaRggBo+pQJkQYbU6omqDstNQ@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfoxAjm3Qn+WAUhUF7ZZiU9OG9dnHuep7RT7xdifqDixGQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3630 bytes --]
Just to repeat, because of a bunch of confused posts here: The breach of
contract case was not about System V code in Linux. It was about non-AT&T
code from System V derivatives (e.g., AIX, Dynix) into Linux. (The
copyright case was completely different.) You may wonder why non-AT&T code
from a System V derivative into LInux should be a legal issue. To find the
answer you have to read the contract. If it sounds bonkers, then we can
agree that the contract was bonkers.
I don't know how strong the copyright case was. I didn't work on it.
Marc
On Mon, Nov 4, 2024 at 7:13 PM Warner Losh <imp@bsdimp.com> wrote:
>
>
> On Mon, Nov 4, 2024, 6:54 PM Larry McVoy <lm@mcvoy.com> wrote:
>
>> On Mon, Nov 04, 2024 at 06:35:30PM -0700, Warner Losh wrote:
>> > On Mon, Nov 4, 2024 at 6: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.
>> > >
>> >
>> > The short answer is that ffs_bmap.c was one of the 70 files that had
>> > a AT&T copyright notice added to it as part of the AT&T vs Regents suit.
>> > By the time 4.4BSD had been released, the file had been substantially
>> > rewritten, but some traces of original AT&T code remained.
>>
>> Yeah, this is completely a false claim. It was identical. At least
>> in 4.3 BSD, I can imagine that 4.4 changed it because I was pointing
>> this out around then.
>>
>
> 4.3bsd wasn't claimed to be a rewrite. 4.4bsd definitely was very
> different. I checked before I posted. So what i said is not false. I
> literally had the code up side by side 20 minutes ago. It is definitely
> different though clearly related and derived a bit. That function is
> absolutely not 100% copied.
>
> For the record, I'm a BSD guy, my OS was SunOS 4.x, it was a bug fixed
>> BSD. If there ever was a guy that wanted this to be true, it's me.
>> It's not true, BSD ripped off Bell Labs code, that's a fact.
>>
>
> Except not in 4.4. 4.3 never was claimed to be a rewrite. You needed a
> AT&T license, prior to the ancient Unix license to get that. So there was
> no claim to originality prior to 4.4. I didn't look at net/2 though.
>
> I'll check after dinner for 4.3bsd and 4.2bsd, but since FFS/UFS is on
> disk different than v7fs I don't expect it to be identical.
>
> Warner
>
>>
--
*My new email address is mrochkind@gmail.com <mrochkind@gmail.com>*
[-- Attachment #2: Type: text/html, Size: 5414 bytes --]
next prev parent reply other threads:[~2024-11-05 3:14 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
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 [this message]
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=CAOkr1zU6jXf9hXqyHNt7OiqyCkaRggBo+pQJkQYbU6omqDstNQ@mail.gmail.com \
--to=mrochkind@gmail.com \
--cc=imp@bsdimp.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).