The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: KenUnix <ken.unix.guy@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Compatibility question
Date: Mon, 18 Dec 2023 03:24:07 +0000	[thread overview]
Message-ID: <bnJtLvdMIdonBawzwrKYb-y3TCIrS_N1wwNDFZUprwkfsICse-nte3-HGFlgq0GhI8IBhjp4w6fHD9_nbP0L3oCoFnKL7dSqAYOsNKdGioE=@protonmail.com> (raw)
In-Reply-To: <CAJXSPs_bYDPZEj9op6vtH5OoTMWJ7z3iQF0p1meOG2bsT9zrOg@mail.gmail.com>

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

For the record Ken's scripting appears to work with my copy of SimH vax780 albeit with some non-fatal errors, probably different configure flags vs. the static copy in this archive. I'm on aarch64 so can't use the vax780 binary in there but after boot the images seem to run fine for me. Dunno what distros do, my copy is upstream.

Typing "unix" at the double "$" prompt starts the bootstrap. Running uname(1) returns the expected properties for SVR2 for the VAX-11/780.

- Matt G.

P.S. SVR2 is post-1983 so a little touchier, so just some caution on distribution. Not sure if there's any IP ownership differences concerning materials that said "Western Electric" and/or "Bell Laboratories" in their licenses vs materials that said "AT&T". Some clarity from the interested parties would be helpful but I have no clue what the likelihood of a second round of free-to-study licensing of later SysV codebases looks like. I would have to wonder if the licensing of illumos has some technicality where all code SVR4 and back (that being the split point) is technically covered under their license. I'm no lawyer so *shrug*
On Sunday, December 17th, 2023 at 4:35 PM, KenUnix <ken.unix.guy@gmail.com> wrote:

> Here is what I ended up doing. Creating a putty session with locked size. Aso
> using the vi as designed it works well. I have included the putty.defs, putty.notes
> and vi.notes.
>
> Now everything is fine. Thanks for your help.
>
> See attachments
>
> Getting System-V-r2-VAX780:
>
> For those running Arch the tar file is here. Simply download, untar
> cd to it , type in ./unix
>
> https://drive.google.com/file/d/1XToKXIxZvs9LKNerkVbTNspMik7OnLrs/view?usp=drive_link
>
> For other 64 bit Unix's use this image
>
> https://drive.google.com/file/d/1L-M8dGXogDpKutR0fpSkOkaEfNNH-1SZ/view?usp=drive_link
>
> Getting System-V-r3-3b2-700 64bit:
>
> https://drive.google.com/file/d/16zJrq3USLFAVnoGtbh4GCIj685o_UQER/view?usp=drive_link
>
> The above packages do not require any special software. It is all self contained.
>
> -ken
>
> On Sun, Dec 17, 2023 at 6:08 PM Warner Losh <imp@bsdimp.com> wrote:
>
>> On Sun, Dec 17, 2023, 4:00 PM Ron Natalie <ron@ronnatalie.com> wrote:
>>
>>> That’s not entirely true. The VT100 could switch modes from 80x24 to 132x14 (the latter was pretty ugly) or with the AVO 132x24.
>>
>> I recall some VMS programs in v3.2 misbehaving when run in 132x24 mode...
>>
>> Warner
>>
>>> ------ Original Message ------
>>> From "Mary Ann Horton" <mah@mhorton.net>
>>> To tuhs@tuhs.org
>>> Date 12/17/23, 5:51:00 PM
>>> Subject [TUHS] Re: Compatibility question
>>>
>>>> The concept of a resizable window didn't appear until GUI interfaces. Originally the hardware terminal had one specific size and vi depended on the screen being that exact size. I suspect that SVr2 was in that category, as the Sun merger of SVr4 would have been the reason to incorporate it. So try a 24x80 window and see if it behaves.
>
> --
>
> End of line
> JOB TERMINATED

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

  reply	other threads:[~2023-12-18 16:49 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-17  2:01 [TUHS] " KenUnix
2023-12-17 18:13 ` [TUHS] " Seth Morabito
2023-12-17 18:23   ` segaloco via TUHS
2023-12-17 22:51     ` Mary Ann Horton
2023-12-17 22:59       ` Ron Natalie
2023-12-17 23:08         ` Warner Losh
2023-12-18  0:35           ` KenUnix
2023-12-18  3:24             ` segaloco via TUHS [this message]
2023-12-18 17:05         ` Paul Winalski
2023-12-18 22:29           ` Jon Forrest
2023-12-19  1:46           ` Dave Horsfall
2023-12-19  7:56             ` Harald Arnesen
2023-12-19 17:40             ` Paul Winalski
2023-12-19 18:07               ` Tom Lyon
2023-12-19 20:23                 ` Clem Cole
2023-12-19 21:31                   ` Paul Winalski
2023-12-19 23:52                     ` Bakul Shah
2023-12-20  0:05                       ` Greg 'groggy' Lehey
2023-12-20  1:03                         ` Bakul Shah
2023-12-20  1:32                           ` Greg 'groggy' Lehey
2023-12-20  6:05                             ` Wesley Parish
2023-12-20  0:15                       ` Mary Ann Horton
2023-12-20 16:07                         ` Adam Thornton
2023-12-20 16:22                           ` Clem Cole
2023-12-20 18:11                           ` Alan D. Salewski
2023-12-20 16:34                         ` Paul Winalski
2023-12-20 18:15                           ` Jon Forrest
2023-12-20  1:11                       ` Steffen Nurpmeso
2023-12-20  1:23                         ` Tom Lyon
2023-12-21  3:53                     ` Rod Bartlett via TUHS
2023-12-19 21:34                   ` Rob Pike
2023-12-17  5:55 David Arnold
2023-12-17  8:08 ` segaloco via TUHS
2023-12-17 18:04   ` James Frew
2023-12-17 18:18     ` Lars Brinkhoff
2023-12-17 19:14       ` Brad Spencer
2023-12-17 18:48     ` Paul Winalski
2023-12-17 18:59       ` Warner Losh
2023-12-17 20:24       ` Dave Horsfall
2023-12-17 19:26     ` Dan Cross
2023-12-17 20:08       ` Warner Losh
2023-12-17 14:07 ` Brad Spencer
2023-12-17 14:47   ` Arrigo Triulzi 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='bnJtLvdMIdonBawzwrKYb-y3TCIrS_N1wwNDFZUprwkfsICse-nte3-HGFlgq0GhI8IBhjp4w6fHD9_nbP0L3oCoFnKL7dSqAYOsNKdGioE=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=ken.unix.guy@gmail.com \
    --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).