The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "John P. Linderman" <jpl.jpl@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] ksh88 source code?
Date: Tue, 22 Dec 2020 20:29:49 -0500	[thread overview]
Message-ID: <CAC0cEp-VhPnQVz0gm=XihJHB-F09XwjaRF2u31SvXsC2pCudmQ@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2M4zjcktxdCcp4AdX4sFDreSLqPb-e334AbJWTEkPNhdA@mail.gmail.com>

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

Does it have to be ksh88? https://github.com/att/ast has ksh93 source. --
jpl

On Tue, Dec 22, 2020 at 6:03 PM Clem Cole <clemc@ccc.com> wrote:

> If you were outside of AT&T, it was distributed via AT&T Summit's
> 'toolchest' thingy (and were as a single license to join it and but
> separate fees for each tool - if you wanted sub-license there was a
> secondary process which I forget the details -- I remember used it so we
> could make ksh, mk and ditroff standard on the MASSCOMP and later Stellar
> boxes).
>
> My memory is that the toolchest was created before SVR4, I want to say
> SVR2 (maybe as late as SVR3) timeframe.  Its origin is it was a way to get
> some of the tools that came from different teams around the labs out
> without having to including them in a full release. Earlier, Brian's
> ditroff and Dennis's compiler were licensed (together) but using the
> original licensing/distribution scheme.   As tools like ksh and mk came on
> the scene, Otis Wilson asked a number of us customers what to do.      The
> toolchest was born from that discussion.  It was cool in the after you
> ordered, you go a uucp address to 'pull' the bits for your site from the
> toolchest.  No tapes were written - which is why I think find things now
> may be hard.
>
> That said, I've not found a repository of the toolchest stuff as I'm not
> so sure ATT really released all of it in the sense of the basic system
> itself.  For instance, the support for the JERQ (including the games) were
> all in the toolchest and last spring a few of us were looking for the GBACA
> sources.  I'm not sure if they were found.
>
> Basically, you need to find someone that had had a toolchest license for
> that specific tool and still has the bits somewhere.
>
> Clem
>
> On Tue, Dec 22, 2020 at 5:44 PM Warren Toomey <wkt@tuhs.org> wrote:
>
>> Hi all, I received an e-mail looking for the ksh-88 source code. A quick
>> search for it on-line doesn't reveal it. Does anybody have a copy?
>>
>> Cheers, Warren
>>
>> Original e-mail:
>>    I recently built a PiDP11 and have been enjoying going back in time
>>    to 2.11BSD..  I was at UC Davis in the the early 1980's and we had
>>    a few PDP-11/70's running 2.8/2.9 BSD. Back then we reached out to
>>    David Korn and he sent us the source for KSH -- this would have been
>>    in 1985ish if I remember, and we compiled it for 2.9 & 4.1BSD, Xenix,
>>    and some other variants that used K&R C.  It may have been what was
>>    later called ksh88.  I wish I still had the files from then..
>>
>>    I was wondering if you might know if there's an older version like this
>>    or one that's been ported for 2.11BSD?
>>    Many thanks,
>>    Joe
>>
>

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

  reply	other threads:[~2020-12-23  1:31 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22 22:43 Warren Toomey
2020-12-22 23:01 ` Clem Cole
2020-12-23  1:29   ` John P. Linderman [this message]
2020-12-23 22:57     ` Warren Toomey
2020-12-23  3:30 ` Rico Pajarola
2020-12-23  9:03   ` Thomas Paulsen
2020-12-23  9:14     ` Rico Pajarola
2020-12-23  5:46 ` Scot Jenkins via TUHS
2020-12-23  7:19   ` Efton Collins
2021-12-21 13:55     ` Cyrille Lefevre via TUHS
2021-12-21 16:21       ` Larry McVoy
2021-12-21 16:27         ` Warner Losh
2021-12-21 17:15           ` Grant Taylor via TUHS
2021-12-21 17:31             ` Boyd Lynn Gerber
2021-12-21 19:09               ` Richard Salz
2021-12-22  6:23             ` jason-tuhs
2021-12-24 22:51               ` Grant Taylor via TUHS
2021-12-24 23:15                 ` Richard Salz
2021-12-24 23:34                 ` Michael Huff
2021-12-21 16:42         ` John Cowan
2021-12-21 16:47           ` Chet Ramey
2021-12-21 17:09             ` John Cowan
2021-12-22 11:11           ` Cyrille Lefevre via TUHS
2021-12-21 22:15         ` Thomas Paulsen
2021-12-22  7:44           ` arnold
2021-12-22 14:35           ` Cyrille Lefevre via TUHS
2021-12-22 14:36             ` Chet Ramey
2021-12-23 13:39       ` [TUHS] Bourne shell source code (was Re: ksh88 source code?) Cyrille Lefevre via TUHS
2020-12-23  6:56 ` [TUHS] ksh88 source code? arnold
2021-12-22 14:40 Norman Wilson
2021-12-23 17:23 ` John Cowan
2021-12-23 20:08   ` silas poulson
2021-12-23 19:10 Norman Wilson

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='CAC0cEp-VhPnQVz0gm=XihJHB-F09XwjaRF2u31SvXsC2pCudmQ@mail.gmail.com' \
    --to=jpl.jpl@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).