From: Rob Pike <robpike@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: Jonathan Gray <jsg@jsg.id.au>, tuhs@tuhs.org
Subject: [TUHS] Re: Was curses ported to Seventh Edition Unix?
Date: Sun, 26 May 2024 09:06:25 +1000 [thread overview]
Message-ID: <CAKzdPgznQAOV=CFpBY6Fp5VJeO+-NZH5aGdnstrRtaqbaa6cAQ@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2NGJHs4RDiZjXWSN4JG0TixDB2DTcGygmn-CYxEUofq+Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1987 bytes --]
Reminds me of my typesetting story (search the list's archives for versatec
and vegents, that should find it.)
-rob
On Sat, May 25, 2024 at 10:17 PM Clem Cole <clemc@ccc.com> wrote:
> Oh how I hate history rewrites. Job control was developed by Kulp on V7
> in Europe and MIT. Joy saw it and added it what would become 4BSD.
>
> The others were all developed on V7 (PDP11)at UCB. They were not back
> ported either. The vax work inherited them from V7.
>
> It is true, The public tended to see these as 4BSD features as that was
> the vehicle that got larger distribution.
>
> Sent from a handheld expect more typos than usual
>
>
> On Sat, May 25, 2024 at 6:49 AM Jonathan Gray <jsg@jsg.id.au> wrote:
>
>> On Fri, May 24, 2024 at 07:03:48PM -0500, G. Branden Robinson wrote:
>> > Hi folks,
>> >
>> > I'm finding it difficult to find any direct sources on the question in
>> > the subject line.
>> >
>> > Does anyone here have any source material they can point me to
>> > documenting the existence of a port of BSD curses to Unix Version 7?
>>
>> "In particular, the C shell, curses, termcap, vi and job control were
>> ported back to Version 7 (and later System III) so that it was not
>> unusual to find these features on otherwise pure Bell releases."
>> from Documentation/Books/Life_with_Unix_v2.pdf
>>
>> in some v7ish distributions: unisoft, xenix, nu machine, venix?
>>
>> https://bitsavers.org/pdf/codata/Unisoft_UNIX_Vol_1_Aug82.pdf pg 437
>>
>> https://archive.org/details/bitsavers_codataUnis_28082791/page/n435/mode/2up
>>
>>
>> https://bitsavers.org/pdf/forwardTechnology/xenix/Xenix_System_Volume_2_Software_Development_1982.pdf
>> pg 580
>>
>> https://archive.org/details/bitsavers_forwardTecstemVolume2SoftwareDevelopment1982_27714599/page/n579/mode/2up
>>
>> https://bitsavers.org/pdf/lmi/LMI_Docs/UNIX_1.pdf pg 412
>>
>> https://archive.org/details/bitsavers_lmiLMIDocs_20873181/page/n411/mode/2up
>>
>
[-- Attachment #2: Type: text/html, Size: 3820 bytes --]
next prev parent reply other threads:[~2024-05-25 23:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 0:03 [TUHS] " G. Branden Robinson
2024-05-25 0:46 ` [TUHS] " Clem Cole
2024-05-25 0:57 ` G. Branden Robinson
2024-05-25 10:48 ` Jonathan Gray
2024-05-25 11:08 ` Arrigo Triulzi via TUHS
2024-05-25 12:16 ` Clem Cole
2024-05-25 23:06 ` Rob Pike [this message]
2024-05-25 15:06 ` [TUHS] " Douglas McIlroy
2024-05-25 15:11 ` [TUHS] " Rich Salz
2024-05-25 15:40 ` Clem Cole
2024-05-25 15:43 ` Clem Cole
2024-05-25 15:51 ` Clem Cole
2024-05-25 15:57 ` G. Branden Robinson
2024-05-25 16:06 ` Clem Cole
2024-05-25 16:13 ` G. Branden Robinson
2024-05-25 16:21 ` Clem Cole
2024-05-25 16:38 ` G. Branden Robinson
2024-05-25 17:02 ` Warner Losh
2024-05-25 16:14 ` Clem Cole
2024-05-25 16:25 ` G. Branden Robinson
2024-05-25 18:07 ` Adam Sampson
2024-05-27 18:31 ` Mary Ann Horton
2024-05-25 15:28 ` G. Branden Robinson
2024-05-25 17:24 Steve Simon
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='CAKzdPgznQAOV=CFpBY6Fp5VJeO+-NZH5aGdnstrRtaqbaa6cAQ@mail.gmail.com' \
--to=robpike@gmail.com \
--cc=clemc@ccc.com \
--cc=jsg@jsg.id.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).