From: Larry McVoy <lm@mcvoy.com>
To: Seth Morabito <web@loomcom.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780
Date: Wed, 15 Mar 2023 14:22:01 -0700 [thread overview]
Message-ID: <20230315212201.GY27975@mcvoy.com> (raw)
In-Reply-To: <984bc9a1-70ea-4032-be21-b99f8d40e897@app.fastmail.com>
On Wed, Mar 15, 2023 at 02:18:30PM -0700, Seth Morabito wrote:
> On Wed, Mar 15, 2023, at 2:08 PM, Clem Cole wrote:
> > On Wed, Mar 15, 2023 at 5:03???PM Warren Toomey via TUHS <tuhs@tuhs.org> wrote:
> >> I'm still worried about my legal butt :-(
> > Probably a good idea.
> >>
> >> But I'd be interested in the viewpoints of people here on the list.
> > The Ancient UNIX license does not release anything beyond V7 - as the document you have on the site (https://www.tuhs.org/ancient.html) says:
> >
> >> 1.9 SUCCESSOR OPERATING SYSTEM means a SCO software offering that is (i) specifically designed for a 16-Bit computer, or (ii) the 32V version, and (iii) specifically excludes UNIX System V and successor operating systems.
> > SVR4 is by definition System V.
>
> Do we know with any certainty who currently owns the System V intellectual property? I think (probably) it's now the Canadian company OpenText, who just bought Micro Focus in January, who absorbed the Attachmate Group in 2014, who bought Novell in 2011, who gobbled up USL in 1992... what a tangled web. I don't even know where one would begin trying to track down someone to give permission to archive System V source code.
Is there any market for System V at this point? I would think it's
Windows, MacOS, Linux and anything else is an also ran at this point.
Can anyone point to a machine that was sold in the last few years that
ran some System V based OS?
next prev parent reply other threads:[~2023-03-15 21:22 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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:03 ` [TUHS] copyright (was: Re: UNIX System V Release 2.2 gdts Vax-780) G. Branden Robinson
2023-03-17 1:05 ` [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780 segaloco via TUHS
2023-03-17 2:03 ` G. Branden Robinson
2023-03-17 3:17 ` Dave Horsfall
2023-03-17 3:30 ` [TUHS] Reply-To and Mail-Followup-To (was: Re: UNIX System V Release 2.2 gdts Vax-780) G. Branden Robinson
2023-03-17 15:12 ` [TUHS] " Pete Turnbull
2023-03-17 15:33 ` segaloco via TUHS
2023-03-17 16:42 ` Steve Nickolas
2023-03-17 18:27 ` Marc Donner
2023-03-16 1:15 ` [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780 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 23:56 ` [TUHS] Re: OSF/1.0 Sources Joseph Holsten
2023-03-17 2:28 ` [TUHS] Re: UNIX System V Warren Toomey via TUHS
-- strict thread matches above, loose matches on Subject: below --
2023-03-15 22:25 [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780 Noel Chiappa
2023-03-15 22:39 ` segaloco via TUHS
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=20230315212201.GY27975@mcvoy.com \
--to=lm@mcvoy.com \
--cc=tuhs@tuhs.org \
--cc=web@loomcom.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).