The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: KenUnix <ken.unix.guy@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780
Date: Wed, 15 Mar 2023 17:38:20 -0400	[thread overview]
Message-ID: <CAJXSPs93zVfEgu8ph8vdfHxYPBCC4FnkMmJZwGSOGZL3N1p2=Q@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2Mm0x5fcsDFduywaBTt=VciA1fapYOn7G44i8wSSbRW3A@mail.gmail.com>

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

So, at this point what is the safest road to take?

Stick with v7?

Ken


On Wed, Mar 15, 2023 at 5:28 PM Clem Cole <clemc@ccc.com> wrote:

>
>
> On Wed, Mar 15, 2023 at 5:22 PM Larry McVoy <lm@mcvoy.com> wrote:
>
>>
>> Is there any market for System V at this point?
>
> Unlikely, but ... companies are funny about IP rights.    A number of us
> are working on a more general solution that if we can identify the holders
> of the System V IP might help solve this issue.    As my father you to say,
> "make haste ... slowly."
> ᐧ
>


-- 
End of line
JOB TERMINATED

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

  reply	other threads:[~2023-03-15 21:38 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 [this message]
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='CAJXSPs93zVfEgu8ph8vdfHxYPBCC4FnkMmJZwGSOGZL3N1p2=Q@mail.gmail.com' \
    --to=ken.unix.guy@gmail.com \
    --cc=clemc@ccc.com \
    --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).