From: ron@ronnatalie.com (Ron Natalie)
Subject: [TUHS] Ksh and SVR4
Date: Tue, 10 Jan 2017 11:34:09 -0500 [thread overview]
Message-ID: <008401d26b5f$5e927f50$1bb77df0$@ronnatalie.com> (raw)
In-Reply-To: <7d852156-56aa-432d-a235-a3c5fb5002df.maildroid@localhost>
I believe that was indeed the first UNIX release to have it included.
From: TUHS [mailto:tuhs-bounces@minnie.tuhs.org] On Behalf Of pechter@gmail.com
Sent: Tuesday, January 10, 2017 11:19 AM
To: Tuhs
Subject: [TUHS] Ksh and SVR4
Wasn't ksh SVR4... It was in the Xelos sources @Concurrent Computer which was an SVR2 port. Xelos didn't do paging but the source in 87 or 88 or so had ksh in it.
I. built it for SVR4 on my Xelos 3230 back in the day.
Bill
Sent from my android device.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170110/e5bb73da/attachment.html>
next prev parent reply other threads:[~2017-01-10 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 16:19 pechter
2017-01-10 16:34 ` Ron Natalie [this message]
2017-01-10 16:41 ` pechter
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='008401d26b5f$5e927f50$1bb77df0$@ronnatalie.com' \
--to=ron@ronnatalie.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).