From: Kevin Bowling <kevin.bowling@kev009.com>
To: Josh Good <pepe@naleco.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Zombified SCO comes back from the dead, brings trial back to life against IBM
Date: Thu, 1 Apr 2021 19:16:09 -0700 [thread overview]
Message-ID: <CAK7dMtC_CvbJVHangYVdLf1JNwzZecPR-SSfaQ0BBXEfky2oKg@mail.gmail.com> (raw)
In-Reply-To: <20210401152738.GB1202@naleco.com>
On Thu, Apr 1, 2021 at 8:28 AM Josh Good <pepe@naleco.com> wrote:
>
> On 2021 Apr 1, 09:12, Warner Losh wrote:
> > The other set of claims made, which may be stronger, was that IBM and
> > Redhat used their dominant position to lock out OSes other than Linux,
> > including FreeBSD from their cloud platform.
>
> I don't think IBM has a dominant position in the cloud business. Microsoft's
> Azure and Amazon's AWS are the dominant forces in the cloud business.
>
> I don't see merit on that claim from XinuOS. They are just firing in all
> directions to find out if by chance they hit some target with money to milk.
Yup, it seems flimsy IBM arranged over $100k a few years ago at my
request to do the initial FreeBSD bringup on powernv in addition to
time and hooking us up with Eldorado Institute. Had there been a
commercial deployment there would have been a lot more help and PR.
They have and use pfsense in the IBM cloud. It seems like the lawyers
didn't do any discovery. It will be interesting to watch.
This list will enjoy digging through this
http://tenox.pdp-11.ru/monterey/ -- whoever made these business
decisions to dump Monterey/IA64 before shipping was good at decision
making in a way I haven't seen in my own career. I've long suspected
the purchase of Sequent was the real downfall to working with SCO.
That too was a great decision.
Regards,
Kevin
> --
> Josh Good
>
next prev parent reply other threads:[~2021-04-02 2:17 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 14:50 Josh Good
2021-04-01 15:12 ` Warner Losh
2021-04-01 15:27 ` Josh Good
2021-04-01 15:33 ` Larry McVoy
2021-04-01 16:14 ` Kevin Bowling
2021-04-01 16:26 ` John Cowan
2021-04-01 17:54 ` Thomas Paulsen
2021-04-01 16:27 ` Nemo Nusquam
2021-04-02 2:16 ` Kevin Bowling [this message]
2021-04-02 3:52 ` Wesley Parish
2021-04-02 5:26 ` Kevin Bowling
2021-04-02 16:03 ` Clem Cole
2021-04-02 16:11 ` Larry McVoy
2021-04-02 16:39 ` Heinz Lycklama
2021-04-02 17:14 ` Clem Cole
2021-04-02 17:17 ` [TUHS] AIX repeat [was " Charles H Sauer
2021-04-03 1:24 ` [TUHS] " Wesley Parish
2021-04-04 2:46 ` Adam Thornton
2021-04-04 2:50 ` Adam Thornton
2021-04-04 5:29 ` [TUHS] How to Kill a Technical Conference (was: Zombified SCO comes back from the dead, brings trial back to life against IBM) G. Branden Robinson
2021-04-04 18:22 ` Clem Cole
2021-04-04 20:54 ` Richard Salz
2021-04-04 21:11 ` Clem Cole
2021-04-05 0:36 ` John Cowan
2021-04-05 2:19 ` Warner Losh
2021-04-05 18:07 ` [TUHS] How to Kill a Technical Conference John Gilmore
2021-04-05 19:30 ` Clem Cole
2021-04-05 20:34 ` Richard Salz
2021-04-05 20:42 ` William Cheswick
2021-04-06 4:37 ` Ed Bradford
2021-04-05 20:39 ` Larry McVoy
2021-04-05 21:11 ` Theodore Ts'o
2021-04-05 21:17 ` Dan Cross
2021-04-06 15:39 ` Theodore Ts'o
2021-04-06 5:49 ` Dave Horsfall
2021-04-05 7:48 ` [TUHS] Whither Usenix [was How To Kill A Technical Conference] arnold
2021-04-05 14:05 ` [TUHS] How to Kill a Technical Conference (was: Zombified SCO comes back from the dead, brings trial back to life against IBM) Theodore Ts'o
2021-04-05 22:26 ` David Arnold
2021-04-04 23:30 ` A. P. Garcia
2021-04-04 3:41 ` [TUHS] Zombified SCO comes back from the dead, brings trial back to life against IBM Gregg Levine
2021-04-04 3:57 ` Adam Thornton
2021-04-02 5:41 ` David Arnold
2021-04-02 6:09 ` Steve Nickolas
2021-04-02 7:00 ` arnold
2021-04-02 9:53 ` Steve Nickolas
2021-04-02 10:26 ` arnold
2021-04-02 14:02 ` Josh Good
2021-04-02 14:17 ` Steve Nickolas
2021-04-02 15:16 ` Larry McVoy
2021-04-02 15:28 ` Fabio Scotoni
2021-04-03 1:50 ` Dave Horsfall
2021-04-03 1:55 ` Warner Losh
2021-04-03 2:23 ` Larry McVoy
2021-04-03 2:34 ` Earl Baugh
2021-04-03 6:16 ` Dan Stromberg
2021-04-04 16:18 ` Tony Finch
2021-04-04 1:48 ` David Arnold
2021-04-04 2:23 ` Larry McVoy
2021-04-04 8:55 ` Josh Good
2021-04-04 14:43 ` Michael Parson
2021-04-04 15:36 ` Warner Losh
2021-04-04 16:15 ` Clem Cole
2021-04-04 22:25 ` David Arnold
2021-04-04 22:55 ` Clem Cole
2021-04-05 2:30 ` Dave Horsfall
2021-04-04 23:00 ` Bakul Shah
2021-04-04 23:33 ` Clem Cole
2021-04-05 1:34 ` Bakul Shah
2021-04-05 2:58 ` Kenneth Goodwin
2021-04-05 12:35 ` John Cowan
2021-04-05 20:44 ` Kevin Bowling
2021-04-04 23:34 ` Josh Good
2021-04-04 20:08 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-04-04 21:00 ` Jon Steinhart
2021-04-04 21:40 ` Clem Cole
2021-04-04 21:54 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-04-04 22:02 ` Jon Steinhart
2021-04-04 21:58 ` Clem Cole
2021-04-04 23:48 ` Dave Horsfall
2021-04-04 23:53 ` Larry McVoy
2021-04-07 5:15 ` Dan Stromberg
2021-04-05 13:37 ` Theodore Ts'o
2021-04-07 1:52 ` Adam Thornton
2021-04-02 15:25 ` Josh Good
2021-04-03 3:10 ` John Cowan
2021-04-02 16:40 ` Boyd Lynn Gerber
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=CAK7dMtC_CvbJVHangYVdLf1JNwzZecPR-SSfaQ0BBXEfky2oKg@mail.gmail.com \
--to=kevin.bowling@kev009.com \
--cc=pepe@naleco.com \
--cc=tuhs@minnie.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).