The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Are there images of any SVR2's available online?
Date: Fri, 24 Dec 2021 10:27:00 -0600	[thread overview]
Message-ID: <5d9a246d-c6ab-fc69-30a1-0995d2d0e4f4@gmail.com> (raw)
In-Reply-To: <CAC20D2NALgG2EogSy6AO8i5ULhTMLhF2PwnF+mP6zguv_vb2xA@mail.gmail.com>

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

On 12/24/21 7:56 AM, Clem Cole wrote:
>
>
> On Thu, Dec 23, 2021 at 11:39 PM Will Senn <will.senn@gmail.com> wrote:
>
>     All,
>
>     Are there any bootable media available for any SVR 2 systems
>     available online?
>
> I'm interested in learning what it is specifically about the SVR2 
> system that you are curious?  As Warner pointed out, the reference 
> system ISA for the folks in Summit, NJ started changing from the 
> PDP-11 to VAX at that point.  By SVR3 it became a WE32000 and by 
> SVR4.2 it was the Intel 386.

Clem,

Ha! I'm curious by nature. I recently was sent a book that references 
SVR2 and that is enough impetus for me to want to try it out 'for real' 
:). Shiny object, for sure.

>
> Besides the ISA changes for the core kernel and the collection of 
> supported user space programs, SYS V took a number twists and turns 
> [for different reasons, some in hindsight, proved questionable] - but 
> nonetheless.
>
> Other than the native support for the Vax, IIRC there really was not a 
> lot special in SVR2 - while SVR1 and SVR3 [and later SVR4.2] were 
> actually substantially different from their predecessors.

Which is why I went looking for SVR2 - substantive (although to me 
completely opaque) differences from SVR1 and SVR3. The book mentions 
SVR2, not SVR1 or SVR3, though, I'm sure it applies equally well to 
those as well, I'm just a sucker for the closest experience I can get 
without driving myself off the rails trying to get things working. Turns 
out it isn't horrible, this time. Angelo's Vax 780 version works about 
like v6/v7 in SIMH - stupid # and @ stuff, but I'm guessing I can change 
it without mucking about in the source this time. - stty'll prolly do it.

Later,

Will

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

  reply	other threads:[~2021-12-24 16:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-24  4:38 Will Senn
2021-12-24  7:09 ` Warner Losh
2021-12-24 16:20   ` Will Senn
2021-12-24 11:20 ` Angelo Papenhoff
2021-12-24 13:56 ` Clem Cole
2021-12-24 16:27   ` Will Senn [this message]
2021-12-24 18:32     ` Grant Taylor via TUHS
2021-12-24 19:26       ` Henry Bent
2021-12-24 19:31         ` Warner Losh
2021-12-24 21:27           ` Grant Taylor via TUHS
2021-12-24 19:35         ` Erik E. Fair
2021-12-24 21:23         ` Grant Taylor via TUHS
2021-12-26 12:37           ` [TUHS] 4.4BSD run on (Re: Are there images of any SVR2's available online?) MOCHIDA Shuji
2021-12-24 16:57 ` [TUHS] Are there images of any SVR2's available online? Seth Morabito
2021-12-24 18:45   ` Will Senn
2021-12-26 15:11   ` Will Senn
2021-12-26 15:17     ` arnold
2021-12-24 18:02 ` Arno Griffioen via TUHS

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=5d9a246d-c6ab-fc69-30a1-0995d2d0e4f4@gmail.com \
    --to=will.senn@gmail.com \
    --cc=clemc@ccc.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).