From: Cyrille Lefevre via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@tuhs.org
Subject: Re: [TUHS] ksh88 source code?
Date: Tue, 21 Dec 2021 14:55:55 +0100 [thread overview]
Message-ID: <1653639b-8e41-7437-8c0e-32564dfdd788@laposte.net> (raw)
In-Reply-To: <CAGkfwV+kabBZZT=q9_mA9LtHPZ3xC0C2VybTW2bLFiYkJ2=oow@mail.gmail.com>
Hi, Here are some ksh versions...
http://cyrillelefevre.free.fr/ksh/
ksh86a-toolchest.tar.bz2 314427
ksh88c-hpux-9.10.tar.bz2 169413
ksh88d-svr4.tar.bz2 132718
ksh88f-i18n-irix-6.5.5.tar.bz2 160563
ksh88f-irix-6.5.7.tar.bz2 215090
ksh88g-sco-unixware7.tar.bz2 195282
ksh88h-sco-unixware7.tar.bz2 147194
ksh88i-solaris-2.5.tar.bz2 149477
ksh88i-solaris-2.6.tar.bz2 159219
ksh88i-solaris-2.7.tar.bz2 163976
ksh88i-solaris-2.8.tar.bz2 164771
ksh93e-sco-unixware7.tar.bz2 542380
Le 23/12/2020 à 08:19, Efton Collins a écrit :
> here is a link to a ksh version that seems to predate ksh88, msg.c
> says "Version 06/03/86a":
> https://github.com/weiss/original-bsd/tree/master/local/toolchest/ksh
>
> I found the link at the bottom of this interesting page:
> https://www.in-ulm.de/~mascheck/various/shells/ksh_versions.html
>
> and this link contains a surprising amount of information on many
> shell versions released over the years -
> https://www.in-ulm.de/~mascheck/various/shells
>
> On 12/22/20, Scot Jenkins via TUHS <tuhs at minnie.tuhs.org> wrote:
>> Warren Toomey <wkt at 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?
>> https://archive.org/details/ATTUNIXSystemVRelease4Version2
>> has source for several releases.
>>
>> click "show all" on the right under "download options",
>> the file sysvr4.tar.bz2 has source for ksh88:
>>
>> from cmd/ksh/sh/msg.c:
>> msg.c: MSG e_version = "\n@(#)Version M-11/16/88d\0\n";
>>
>> I think this was for x86 PCs. I haven't tried to build it.
>> The date on the files is Jan 25 1993.
>>
>> scot
>>
>
--
mailto:Cyrille.Lefevre-lists@laposte.net
next prev parent reply other threads:[~2021-12-21 15:57 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
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 [this message]
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=1653639b-8e41-7437-8c0e-32564dfdd788@laposte.net \
--to=tuhs@minnie.tuhs.org \
--cc=cyrille.lefevre-lists@laposte.net \
--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).