From: Kevin Bowling <kevin.bowling@kev009.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: tuhs@minnie.tuhs.org, Josh Good <pepe@naleco.com>
Subject: Re: [TUHS] Micnet Was: Re: Surprised about Unix System V in the 80's - so sparse!
Date: Sat, 20 Mar 2021 18:42:50 -0700 [thread overview]
Message-ID: <CAK7dMtD+VSeUkX5FX6pWubAJFCAUo-HT9xOoYJOz9gkqRZsorg@mail.gmail.com> (raw)
In-Reply-To: <20210321013126.GY2912@mcvoy.com>
[-- Attachment #1: Type: text/plain, Size: 2059 bytes --]
SCO is still around in some form. I believe it’s mostly just a support
offering. They converged on two products in the ‘90s: OpenServer (SVR3)
and UnixWare (SVR4). It seems like most people preferred or were stuck on
OpenServer while UnixWare would have eventually been a nicer system but I
don’t know first hand. They also shipped a version of FreeBSD 10
commercially a handful of years ago.
On Sat, Mar 20, 2021 at 6:32 PM Larry McVoy <lm@mcvoy.com> wrote:
> So this is just me, I'm not a fan of SCO even though I was the guy that
> added TCP/IP to that OS.
>
> SCO just felt like it was the back burner. Sun felt like it was the
> front burner that was pushing things forward. SCO was the team that
> said they had this and did nothing with it.
>
> On Sun, Mar 21, 2021 at 12:12:17PM +1100, Greg 'groggy' Lehey wrote:
> > On Saturday, 20 March 2021 at 17:18:43 -0700, Larry McVoy wrote:
> > > Yeah, but wouldn't that mean that SCO Unix had to be open sourced?
> > > Or did they buy the rights?
> >
> > They didn't "open source" SCO, but in January 2002 they released
> > "ancient Unix" under a "BSD-style" license. See
> > http://www.lemis.com/grog/UNIX/
> > But I'm sure everybody knows that.
> >
> > > While I mostly can't believe anyone would want SCO Unix, I do know that
> > > they ran a lot of cash registers, or maybe they were the server, I
> dunno,
> > > somehow point of sale and SCO was a thing a long time ago. So maybe it
> > > is a legacy thing?
> >
> > I haven't been following SCO recently, but at some point they had
> > taken UnixWare from Novell. I'm sure that, too, is common knowledge.
> >
> > 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
>
>
>
> --
> ---
> Larry McVoy lm at mcvoy.com
> http://www.mcvoy.com/lm
>
[-- Attachment #2: Type: text/html, Size: 2991 bytes --]
next prev parent reply other threads:[~2021-03-21 1:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 9:44 Paul Ruizendaal via TUHS
2021-03-18 11:27 ` Mike Knell via TUHS
2021-03-18 12:04 ` Jim Capp
2021-03-20 11:50 ` Josh Good
2021-03-20 15:16 ` Larry McVoy
2021-03-21 0:08 ` Wesley Parish
2021-03-21 0:18 ` Larry McVoy
2021-03-21 1:12 ` Greg 'groggy' Lehey
2021-03-21 1:31 ` Larry McVoy
2021-03-21 1:42 ` Kevin Bowling [this message]
2021-03-21 2:38 ` [TUHS] SCO marketing FreeBSD (was: Micnet, Was: Surprised about Unix System V in the 80's - so sparse!) Greg 'groggy' Lehey
2021-03-21 2:43 ` Kevin Bowling
2021-03-21 3:02 ` Warner Losh
2021-03-21 3:04 ` Greg 'groggy' Lehey
2021-03-21 3:09 ` Warner Losh
2021-03-21 6:53 ` Dave Horsfall
2021-03-21 11:01 ` Harald Arnesen
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=CAK7dMtD+VSeUkX5FX6pWubAJFCAUo-HT9xOoYJOz9gkqRZsorg@mail.gmail.com \
--to=kevin.bowling@kev009.com \
--cc=lm@mcvoy.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).