From: rob@atvetsystems.com
To: Warner Losh <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: Sat, 9 Nov 2024 00:40:22 +0000 [thread overview]
Message-ID: <C5450DDC-2C03-4EE0-9AF1-7607989F02C9@atvetsystems.com> (raw)
In-Reply-To: <CANCZdfoEHm51r=7YiGaWS7rWJssw9RPchJgh+K2z+mNRjhpXng@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2960 bytes --]
I went to one of the SCO forum events at Santa Cruz at the time and I vaguely remember someone having a chat to use and saying that the dispute was that SCO and IBM were working on project Monterey and some of the SCO SMP code found its way into Linux.
At the time SCO felt that Linux was several years behind on SMP so getting the SMP code would remove the SCO advantage at a time when processors were getting more cores. This may have been more to do with the IBM -vs- SCO contract case.
Regards, Rob.
> On 8 Nov 2024, at 23:18, Warner Losh <imp@bsdimp.com> wrote:
>
>
>
> ---------- Forwarded message ---------
> From: Warner Losh <imp@bsdimp.com <mailto:imp@bsdimp.com>>
> Date: Fri, Nov 8, 2024 at 3:17 PM
> Subject: Re: [TUHS] SCO's "evidence" (was: RIP Darl McBride former CEO of SCO)
> To: David Barto <barto@kdbarto.org <mailto:barto@kdbarto.org>>
>
>
>
>
> On Fri, Nov 8, 2024 at 1:07 PM David Barto <barto@kdbarto.org <mailto:barto@kdbarto.org>> wrote:
>
>
>> On Nov 8, 2024, at 12:27 PM, Warner Losh <imp@bsdimp.com <mailto:imp@bsdimp.com>> wrote:
>>
>>
>>
>> On Fri, Nov 8, 2024, 6:20 AM Dan Cross <crossd@gmail.com <mailto:crossd@gmail.com>> wrote:
>> On Tue, Nov 5, 2024 at 2:02 PM Warner Losh <imp@bsdimp.com <mailto:imp@bsdimp.com>> wrote:
>> > On Tue, Nov 5, 2024 at 11:52 AM ron minnich <rminnich@gmail.com <mailto:rminnich@gmail.com>> wrote:
>> >> I keep wondering if this assertion of code difference or lack thereof can be tested. Are not all these sources available? Which bits are missing?
>> >
>> > Yes. Great question.
>> >
>> > https://people.freebsd.org/~imp/pmap/pmap.32v <https://people.freebsd.org/~imp/pmap/pmap.32v>
>> > https://people.freebsd.org/~imp/pmap/pmap.4.2 <https://people.freebsd.org/~imp/pmap/pmap.4.2>
>> > https://people.freebsd.org/~imp/pmap/pmap.4.3 <https://people.freebsd.org/~imp/pmap/pmap.4.3>
>> > https://people.freebsd.org/~imp/pmap/pmap.net.2 <https://people.freebsd.org/~imp/pmap/pmap.net.2>
>>
>> Hmm; these all 404 for me?
>>
>> Doh! Too much muscle memory. Those should all be bmap:
>>
>> https://people.freebsd.org/~imp/bmap/bmap.32v <https://people.freebsd.org/~imp/pmap/pmap.32v>
>> https://people.freebsd.org/~imp/bmap/bmap.4.2 <https://people.freebsd.org/~imp/pmap/pmap.4.2>
>> https://people.freebsd.org/~imp/bmap/bmap.4.3 <https://people.freebsd.org/~imp/pmap/pmap.4.3>
>> https://people.freebsd.org/~imp/bmap/bmap.net.2 <https://people.freebsd.org/~imp/pmap/pmap.net.2>
> https://people.freebsd.org/~imp/bmap/bmap.32v <https://people.freebsd.org/~imp/bmap/bmap.32v>
> https://people.freebsd.org/~imp/bmap/bmap.4.2 <https://people.freebsd.org/~imp/bmap/bmap.4.2>
> https://people.freebsd.org/~imp/bmap/bmap.4.3 <https://people.freebsd.org/~imp/bmap/bmap.4.3>
> https://people.freebsd.org/~imp/bmap/bmap.net.2 <https://people.freebsd.org/~imp/bmap/bmap.net.2>
>
> Not sure why the previous...
>
> Warner
[-- Attachment #2: Type: text/html, Size: 6647 bytes --]
next prev parent reply other threads:[~2024-11-09 0:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 17:55 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 ` rob [this message]
2024-11-05 18:58 ` [TUHS] " Warner Losh
2024-11-05 20:25 ` [TUHS] Copyrights and copying.. [was SCO's "evidence" (was: RIP Darl McBride former CEO of SCO)] Christian Hopps
2024-11-05 20:35 ` [TUHS] " Warner Losh
-- strict thread matches above, loose matches on Subject: below --
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
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=C5450DDC-2C03-4EE0-9AF1-7607989F02C9@atvetsystems.com \
--to=rob@atvetsystems.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).