The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Greg 'groggy' Lehey" <grog@lemis.com>
To: Will Senn <will.senn@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: RIP Darl McBride former CEO of SCO
Date: Mon, 4 Nov 2024 13:31:51 +1100	[thread overview]
Message-ID: <ZygyF2yFKVZT9DrR@hydra.lemis.com> (raw)
In-Reply-To: <f25b8e86-54c1-408f-ab0c-0824616fcd79@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]

On Sunday,  3 November 2024 at 19:17:03 -0600, Will Senn wrote:
> It happened in September, apparently, but is only now making the rounds.
> Darl McBride, known for taking everybody and his brother to court over
> stolen code, has passed away.
>
> https://fossforce.com/2024/11/once-linuxs-biggest-enemy-darl-mcbride-dies-and-nobody-notices/

Oh.  As you say, RIP.

> I actually remember liking SCO back in the day, before the company
> leadership went dark-side. These days, we get to play with ancient unix cuz
> of their license.

Yes.  SCO really changed between 2002 and 2003.

> Is there a concise summary of the SCO suits and fallout out there? I've seen
> a lot on the AT&T side of things, but other than having lived through it,
> I've not seen much on what eventually happened and why it all sort of just
> dissappeared.

Not quite what you're looking for, but at the time I kept quite a bit
of information at http://www.lemis.com/grog/SCO/

It's a bit of a mess, and a lot of the links have atrophied, but some
of it could be interesting.  Potentially the reference to BSD code in
the fossforce article could be related to
http://www.lemis.com/grog/SCO/code-comparison.php

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 --]

  reply	other threads:[~2024-11-04  2:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04  1:17 [TUHS] " Will Senn
2024-11-04  2:31 ` Greg 'groggy' Lehey [this message]
2024-11-04  3:34   ` [TUHS] " 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

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=ZygyF2yFKVZT9DrR@hydra.lemis.com \
    --to=grog@lemis.com \
    --cc=tuhs@tuhs.org \
    --cc=will.senn@gmail.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).