From: segaloco via TUHS <tuhs@tuhs.org>
To: jnc@mercury.lcs.mit.edu
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780
Date: Wed, 15 Mar 2023 22:39:09 +0000 [thread overview]
Message-ID: <PORaCz54MSPdf6IM_ybCXiMje3dDQpyfdpw81tH88_OBZe7h7WukMxqfSr0PcRzSZ7M2EReYSGzmoQuyUX7L7OxMxlRYYXOfkI_xkj2HuDo=@protonmail.com> (raw)
In-Reply-To: <20230315222552.3D2B818C07E@mercury.lcs.mit.edu>
Whatever survives of the UnixWare IP holder is still making money, I think, at least on support. Isn't that where the "upstream" SysV code base went to die after SVR4?
- Matt G.
------- Original Message -------
On Wednesday, March 15th, 2023 at 3:25 PM, jnc@mercury.lcs.mit.edu <jnc@mercury.lcs.mit.edu> wrote:
> > From: Larry McVoy
>
>
> > If there are no commercial users of that source base, you have a chance
>
>
> When was the last VAX sold? Maybe the VAX version people would be willing to
> let go of.
>
> Noel
next prev parent reply other threads:[~2023-03-15 22:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 22:25 Noel Chiappa
2023-03-15 22:39 ` segaloco via TUHS [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-15 11:59 Noel Chiappa
2023-03-15 21:03 ` Warren Toomey via TUHS
2023-03-15 21:08 ` Clem Cole
2023-03-15 21:15 ` Luther Johnson
2023-03-15 21:18 ` Seth Morabito
2023-03-15 21:22 ` Larry McVoy
2023-03-15 21:27 ` Clem Cole
2023-03-15 21:38 ` KenUnix
2023-03-16 23:18 ` Clem Cole
2023-03-16 23:48 ` Charles H. Sauer (he/him)
2023-03-17 1:08 ` Steve Nickolas
2023-03-15 21:46 ` Steve Nickolas
2023-03-15 21:50 ` Luther Johnson
2023-03-15 21:56 ` steve jenkin
2023-03-15 22:15 ` Larry McVoy
2023-03-15 23:30 ` Warner Losh
2023-03-15 23:41 ` Luther Johnson
2023-03-16 0:29 ` Warner Losh
2023-03-16 0:36 ` Rich Salz
2023-03-16 1:55 ` G. Branden Robinson
2023-03-16 21:14 ` Dave Horsfall
2023-03-17 0:33 ` Rich Salz
2023-03-17 1:05 ` segaloco via TUHS
2023-03-17 2:03 ` G. Branden Robinson
2023-03-17 3:17 ` Dave Horsfall
2023-03-16 1:15 ` Larry McVoy
2023-03-16 2:14 ` Luther Johnson
2023-03-15 23:44 ` Brad Spencer
2023-03-16 4:37 ` Dave Horsfall
2023-03-15 0:59 Noel Chiappa
2023-03-15 8:05 ` arnold
2023-03-15 8:52 ` Dave Horsfall
2023-03-15 11:09 ` KenUnix
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='PORaCz54MSPdf6IM_ybCXiMje3dDQpyfdpw81tH88_OBZe7h7WukMxqfSr0PcRzSZ7M2EReYSGzmoQuyUX7L7OxMxlRYYXOfkI_xkj2HuDo=@protonmail.com' \
--to=tuhs@tuhs.org \
--cc=jnc@mercury.lcs.mit.edu \
--cc=segaloco@protonmail.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).