From: "Greg 'groggy' Lehey" <grog@lemis.com>
To: Marc Rochkind <mrochkind@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: IBM's involvement (was: SCO's "evidence" (was: RIP Darl McBride former CEO of SCO))
Date: Wed, 6 Nov 2024 15:00:34 +1100 [thread overview]
Message-ID: <Zyrp4l1ag_-XcvAC@hydra.lemis.com> (raw)
In-Reply-To: <CAOkr1zVmDOwv5fF+nem331OsFy7TW_5DfhnfcV4AzLHcMq826g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3262 bytes --]
On Monday, 4 November 2024 at 20:04:38 -0700, Marc Rochkind wrote:
> Hi Greg! Now I remember where I had seen your name before. Perhaps I
> read your deposition (if there was one)? Or just on a list of LTC
> staffers?
My guess is that you saw it elsewhere. I didn't make a deposition,
and I left IBM 6 months before the announcement of the case.
> To do justice to your post and all your questions would require too much
> writing and thinking, so I'll just clarify a few things.
>
> 1. The breach of contract part of the case wasn't about IBM putting System
> V code into Linux. It was about IBM putting IBM code into Linux, and
> McKinney's RCU was a good example.
Oh. That changes everything. Rather like the "viral" GPL? The
Wikipedia page still claims
SCO claimed that IBM had, without authorization, contributed SCO's
intellectual property to the codebase of the open source, Unix-like
Linux operating system.
> Nobody thought this was System V code or that it had anything at all
> to do with AT&T. I think the LTC was staffed with a lot of former
> Dynix (not sure I remember the name correctly) people, right?
I don't know. It's possible, but LTC was geographically distributed,
and we (Ozlabs) were in Canberra. I don't even know where Paul was,
though I have some recollection that it was in the NW of USA.
> 2. Examples that got widely talked about, such as malloc, were not good
> examples of what the copyright case was about. As I said, I didn't work on
> it, but I got briefed sometimes. This is an example of what I was talking
> about: People thinking they knew what the issues were based on the issues
> that they knew about. 99% of the evidence was sealed.
That makes it all the stranger that SCO presented the malloc()
lookalike as an example, especially since they (as Caldera) had
released it a year before. Could it be that there were two teams, one
doing the publicity and one doing the real investigation?
> 3. JFS (1 or 2, don't remember) as I recall was a tricky
> case. Something like what you say, that it was developed in a clean
> room, but then put into AIX and subsequently into Linux. If any
> AIXness got into Linux, then it was also (like RCU) a case of IBM
> putting into Linux code that had come from a System V derivative.
JFS 1 and 2 were two very different beasts. JFS 1 never made it to
Linux. JFS 2 was written for Linux and (I think) later backported to
AIX. I had initially thought that JFS 2 was a "JFS 1 lite", but in
fact it was a much better implementation.
> I would like to make it clear to the whole TUHS community that I
> personally am not arguing one way or another about the ethics or
> legality of any of this stuff.
Understood. From my point of view this is a technical discussion.
> I think the contribution that LTC made to Linux was enormous, not
> least because it told the world that Linux was ready for prime time
> (e.g., mission critical server farms).
... as long as you didn't mind riding bicycles.
Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2024-11-06 4:00 UTC|newest]
Thread overview: 30+ 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
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 [this message]
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=Zyrp4l1ag_-XcvAC@hydra.lemis.com \
--to=grog@lemis.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).