The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: "Greg 'groggy' Lehey" <grog@lemis.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>, Josh Good <pepe@naleco.com>
Subject: Re: [TUHS] SCO marketing FreeBSD (was: Micnet, Was: Surprised about Unix System V in the 80's - so sparse!)
Date: Sat, 20 Mar 2021 21:09:10 -0600	[thread overview]
Message-ID: <CANCZdfpQB1O-3hiCbexWxrW65D_xckCGtBCxpfHTmKTw7z23ag@mail.gmail.com> (raw)
In-Reply-To: <20210321030425.GD60525@eureka.lemis.com>

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

On Sat, Mar 20, 2021, 9:04 PM Greg 'groggy' Lehey <grog@lemis.com> wrote:

> On Saturday, 20 March 2021 at 21:02:35 -0600, Warner Losh wrote:
> > On Sat, Mar 20, 2021, 8:44 PM Kevin Bowling <kevin.bowling@kev009.com>
> > wrote:
> >
> >> The Wikipedia article isn???t bad:
> >> https://en.wikipedia.org/wiki/OpenServer
> >>
> >> The only first hand info I can add is the money guy passed away a couple
> >> years ago, which probably put things into limbo and I???m not sure who
> is at
> >> the helm of Xinuos now.  When I last talked to their engineering
> director
> >> they had non-trivial revenue supporting the old products, enough to run
> >> several product development engineers apart from whatever else it took
> to
> >> keep the lights on.
> >
> > I'd love to hear more recent news...
>
> So would I.  I wonder if they're still basing on FreeBSD 10.
>
> > Ps I sent off a message to the FreeBSD developer list to see any one
> > there knows. Hope I'm not stepping on any toes...
>
> You didn't exactly mention your sources.  Looks fine to me.
>

True. I couldn't recall if Kevin has a commit bit still or not.... if need
be, I'll send a follow up...

Warner

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
>

[-- Attachment #2: Type: text/html, Size: 2529 bytes --]

  reply	other threads:[~2021-03-21  3:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18  9:44 [TUHS] Micnet Was: Re: Surprised about Unix System V in the 80's - so sparse! 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
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 [this message]
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=CANCZdfpQB1O-3hiCbexWxrW65D_xckCGtBCxpfHTmKTw7z23ag@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=grog@lemis.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).