From: steve jenkin <sjenkin@canb.auug.org.au>
To: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780
Date: Thu, 16 Mar 2023 08:56:23 +1100 [thread overview]
Message-ID: <C5B04CCD-D814-4064-A9AF-46B734691828@canb.auug.org.au> (raw)
In-Reply-To: <20230315212201.GY27975@mcvoy.com>
> On 16 Mar 2023, at 08:22, Larry McVoy <lm@mcvoy.com> wrote:
>
> 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.
Is this the right question, treating System V as commercial?
"What “uses” would SysV codebase have now?" may be a better Q.
Minor commercial use, restricted to old hardware.
A platform for research and hobbyist non-commercial use.
And for the intellectually curious,
to document the evolution of the codebase through time.
[ for ‘completeness’ of the git repo ]
At best, academically it might enable a comparative code course
and some PhD’s.
I think it’d be quite some legacy to leave a complete tree
of the evolution of Unix, from the earliest versions,
out to the end.
But having corporates give up any “Intellectual Property”
isn’t likely. Not until a bunch of people have died :)
--
Steve Jenkin, IT Systems and Design
0412 786 915 (+61 412 786 915)
PO Box 38, Kippax ACT 2615, AUSTRALIA
mailto:sjenkin@canb.auug.org.au http://members.tip.net.au/~sjenkin
next prev parent reply other threads:[~2023-03-15 21:56 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
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 [this message]
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=C5B04CCD-D814-4064-A9AF-46B734691828@canb.auug.org.au \
--to=sjenkin@canb.auug.org.au \
--cc=tuhs@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).