From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] Early Clones / Rewrites for TUHS archives
Date: Wed, 13 Dec 2017 08:58:14 -0800 [thread overview]
Message-ID: <20171213165814.GJ26887@mcvoy.com> (raw)
In-Reply-To: <CAC20D2OEfYozFZ5EJ9eHOe=aU_aDHkPrkYVSmLJZSRWR3c_LLg@mail.gmail.com>
On Wed, Dec 13, 2017 at 08:46:41AM -0500, Clem Cole wrote:
> I remember Leor bringing BDS C <http://www.bdsoft.com/resources/bdsc.html>and
> his Unix emulation for CP/M to a Boston USENIX
I wrote a lot of code in BDS C, remember it fondly (even though it's stdio
was non-stdio :)
I never heard about any Unix emulation from him, do you mean the libraries
or something else.
I ask because I wrote a bunch of tiny CP/M programms, in assembler because
I was using every trick I could to make them small. I believe the ones I
had on every floppy were:
ls
cp
mv
rm
and each one of those I made fit in either one or two 512 byte sectors
because they weren't memory resident, it had to spin up the floppy and
read them in each time I ran them. So I wanted them small for two
reasons: speed of reading them in and not taking up precious space on
the floppy.
I had a utils floppy that had larger programs on it, like grep, my quicknet
terminal emulator/file transfer tool (I wish I had saved the source to that).
my CP/M machine was an Okidata with a color(!) monitor and a built in
printer with two floppies so I could do work on one floppy and get the
utils on the other. Hmm, wonder if there is picture of that machine
on the net? Of course there is:
http://www.old-computers.com/museum/computer.asp?c=94
So Clem, did Leor do any utilities that I didn't know about or are you
talking about his not so standard C library?
--lm
next prev parent reply other threads:[~2017-12-13 16:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 15:16 Noel Chiappa
2017-12-12 16:01 ` Warner Losh
2017-12-13 2:15 ` Nigel Williams
2017-12-13 13:46 ` Clem Cole
2017-12-13 16:58 ` Larry McVoy [this message]
2017-12-13 19:03 ` Clem Cole
2017-12-16 4:50 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
2017-12-12 14:40 Clem Cole
2017-12-12 16:29 ` Random832
2017-12-12 16:41 ` Random832
2017-12-13 4:16 ` Jason Stevens
2017-12-13 21:22 ` Nemo
2017-12-14 0:26 ` Robert Swierczek
2017-12-18 10:10 ` Peter Jeremy
2017-12-18 15:46 ` Larry McVoy
2017-12-18 15:57 ` Steve Nickolas
2017-12-18 15:59 ` Larry McVoy
2017-12-18 16:13 ` Steve Simon
2017-12-18 16:18 ` Arthur Krewat
2017-12-18 16:15 ` Henry Bent
2017-12-18 16:34 ` Andy Kosela
2017-12-18 16:39 ` Gregg Levine
2017-12-18 17:35 ` Steve Simon
2017-12-18 17:41 ` Toby Thain
2017-12-18 18:41 ` Brad Spencer
2017-12-18 16:37 ` Gregg Levine
2017-12-18 18:32 ` Bakul Shah
2017-12-18 16:53 ` Clem Cole
2017-12-18 17:08 ` Kurt H Maier
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=20171213165814.GJ26887@mcvoy.com \
--to=lm@mcvoy.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).