Computer History Museum curator Dag Spicer passed along a question from former CHM curator Alex Bochannek that I thought someone on this list might be able to answer. The paper "The M4 Macro Processor” by Kernighan and Ritchie says:
> The M4 macro processor is an extension of a macro processor called M3 which was written by D. M. Ritchie for the AP-3 minicomputer; M3 was in turn based on a macro processor implemented for [B. W. Kernighan and P. J. Plauger, Software Tools, Addison-Wesley, Inc., 1976].
Alex and Dag would like to learn more about this AP-3 minicomputer — can anyone help?
I sense a hint of confusion in some of the messages
here. To lay that to rest if necessary (and maybe
others are interested in the history anyway):
As I understand it, the Blit was the original terminal,
hardware done by Bart Locanthi (et al?), software by
Rob Pike (et al?). It used an MC68000 CPU. Western
Electric made a small production run of these terminals
for use within AT&T. I don't think it was sold to the
general public.
By the time I arrived at Bell Labs in late 1984, the
Standard Terminal of 1127 was the AT&T 5620, locally
called the Jerq. This was a makeover with hardware
redesigned by a product group to use a Bellmac 32 CPU,
and software heavily reworked by a product group.
This is the terminal that was manufactured for general
sale.
I'm not sure, but I think the Blit's ROM was very basic,
just enough to be some sort of simple glass-tty or
perhaps smartass-terminal* plus an escape sequence to
let you load in new code. The Jerq had a fancier ROM,
which was a somewhat-flaky ANSI-ish terminal by default,
but an escape sequence put it into graphics-window-manager
mode, more or less like what had run a few years earlier
on the Blit.
By then the code used in Research had evolved considerably,
in particular allowing the tty driver to be exported to
the terminal (those familiar with 9term should know what
I mean). In 1127 we used a different escape sequence to
download a standalone program into the terminal and
replace the ROM window manager entirely, so we could run
our newer and (to my taste anyway) appreciably better code.
The downloaded code lived in RAM; you had to reload it
whenever the terminal was power-cycled or lost its connection
or whatnot. (It took a minute or so at 9600bps, rather
longer at 1200. This is not the only reason we jumped at
the chance to upgrade our home-computing scheme to use
9600bps over leased lines, but it was an important one.)
The V8 tape was made in late 1984 (I know that for sure
because I helped make it). It is unlikely to have anything
for the MC68000 Blit, only stuff for the Mac-32 Jerq.
Likewise for the not-really-a-release snapshots from the
9/e and 10/e eras. The 5620 ROM code is very unlikely to
be there anywhere, but the replacement stuff we used should
be somewhere.
Norman Wilson
Toronto ON
> If 5620s were called Jerqs, it was an accident. All the software with that
> name would be for the original, Locanthi-built and -designed 68K machines.
>
> The sequence is thus Jerq, Blit, DMD-5620
Maybe the “Jerq” name had a revival. If the processor switch came with some upheaval it is not hard to see how that revival could have happened.
The Dan Cross tar archive with the source code has two top level directories, one named “blit" with the 68K based source and another one named “jerq" with the Bellmac based source. The tar archive seems to have been made in the summer of 1985, or at least those dates are on the top level directories.
I am of course not disputing that the original name was Jerq. There are many clues in the source supporting that, among which this funny comment in mcc.c:
int jflag, mflag=1; /* Used for jerq. Rob Pike (read comment as you will) */
Bit hard to classify this one; separate posts since COFF was created?
Augusta Ada King-Noel, Countess of Lovelace (and daughter of Lord Byron), was
born on this day in 1815; arguably the world's first computer programmer and a
highly independent woman, she saw the potential in Charles Babbage's
new-fangled invention.
J.F.Ossanna was given unto us on this day in 1928; a prolific programmer, he
not only had a hand in developing Unix but also gave us the ROFF series.
Who'ld've thought that two computer greats would share the same birthday?
-- Dave
Moo and hunt-the-wumpus got quite a lot of play
both in the lab and at home. Wump was an instant
hit with my son who was 4 or 5 years old at the
time.
Amusingly, I speculated on how to generate degree-3
graphs for wump, but obviously not very deeply. It
was only much later that I realized the graph
always had the same topology--a dodecahedron.
Doug\
We lost Dr. John Lions on this day in 1998; he was one of my Comp Sci
lecturers (yes, I helped him write The Book, and yes, you'll find my name
in the back).
-- Dave
I’m looking for the origins of SLIP and PPP on Unix. Both seem to have been developed long before their RFC’s appeared.
As far as I can tell, SLIP originally appeared in 3COM’s UNET for the PDP11, around 1980. From the TUHS Unix tree, first appearance in BSD seems to be 4.3 (1986).
Not sure when PPP first appeared, but the linux man page for pppd has a credit that goes back to Carnegie Mellon 1984. First appearance in BSD seems to be FreeBSD 5.3 (2004), which seems improbably late (same source).
Paul
Hello All.
Anyone who pulled the code for v10spell that I made available a few
months ago should 'make clean', 'git pull', and 'make'.
A critical bug has been fixed for 64 bit systems, and the code has
had some additional cleanups and the doc updated some as well.
The repos is at git://github.com/arnoldrobbins/v10spell.
Enjoy,
Arnold
> From: Paul Ruizendaal
> I'm looking for the origins of SLIP and PPP on Unix. Both seem to have
> been developed long before their RFC's appeared.
You're dealing with an epoch when the IETF motto - "rough consensus and
running code" - really meant something. Formal RFC's way lagged protocol
development; they're the last step in the process, pretty much.
If you want to study the history, you'd need to look at Internet Drafts (if
they're still online). Failing that, look at the IETF Proceedings; I think
all the ones from this period have been scanned in. They won't have the
detail that the I-D's would have, but they should give the rough outlines
of the history.
Noel
I've been fixing and enhancing James Youngman's git-sccsimport to use
with some of my SCCS archives, and I thought it might be the ultimate
stress test of it to convert the CSRG BSD SCCS archives.
The conversion takes about an hour to run on my old-ish Dell server.
This conversion is unlike others -- there is some mechanical compression
of related deltas into a single Git commit.
https://github.com/robohack/ucb-csrg-bsdhttps://github.com/robohack/git-sccsimport
--
Greg A. Woods <gwoods(a)acm.org>
Kelowna, BC +1 250 762-7675 RoboHack <woods(a)robohack.ca>
Planix, Inc. <woods(a)planix.com> Avoncote Farms <woods(a)avoncote.ca>
We lost J.F. Ossanna on this day in 1977; he had a hand in developing Unix, and
was responsible for "roff" and its descendants. Remember him, the next time
you see "jfo" in Unix documentation.
He also accomplished a lot more, too much to summarise here.
-- Dave
We retired gets from Research UNIX back in 1984 or perhaps
earlier, with no serious pain because replacing it wasn't
hard and everybody agreed with the reason.
I'm glad to hear some part of the rest of the world is
catching up.
We also decided to retire the old Enigma-derived crypt(1),
except we didn't want to throw it out entirely in case
someone had an old encrypted file and wanted the contents
back. So it was removed from the manual and the binary
moved to /usr/games.
Norman Wilson
Toronto ON
Seen in the FreeBSD Quarterly Report:
gets(3) retirement
Contact: Ed Maste <emaste(a)FreeBSD.org>
gets is an obsolete C library routine for reading a string from
standard input. It was removed from the C standard as of C11 because
there was no way to use it safely. Prompted by a comment during Paul
Vixie's talk at vBSDCon 2017 I started investigating what it would take
to remove gets from libc.
The patch was posted to Phabricator and refined several times, and the
portmgr team performed several exp-runs to identify ports broken by the
removal. Symbol versioning is used to preserve binary compatibility for
existing software that uses gets.
The change was committed in September, and will be in FreeBSD 13.0.
This project was sponsored by The FreeBSD Foundation.
And the world is a slightly safer place...
-- Dave
I'm looking for a reference to any Unix ports where the kernel ran in
a non-paged address space and user mode was paged. I could swear this
was done at some point, and memory says it was on a soft-TLB system
like the MIPS, to avoid TLB pollution and TLB fault overhead.
But maybe I'm nuts. I am happy to hear either answer.
I had a hand-held degausser, but lent it to someone years ago
and never got it back.
It was actually Exabyte that made me buy it. I bought a new
8505 through a reseller to supersede the 8200 I was using for
home backups. It turned out the 8505's firmware refused to
overwrite a tape already written at any but the highest density,
so I couldn't reuse any of my existing backup tapes. Exabyte
insisted it was a feature, not a bug. So I gave up and bought
a degausser so I could turn a used tape into a blank tape so
the damn tape drive would write on it.
For further vintage-computing amusement: I decided to buy at
that time because the reseller had arranged a deal with Exabyte:
trade in any old tape drive, working or not, and get a couple of
hundred bucks off on a brand-new 8505. So I gave the reseller
an old, broken TK05 I had lying around. My sales contact for
the reseller was a former service tech at the same company, so
I figured (correctly) he'd get the joke.
Norman Wilson
Toronto ON
Snotty remarks aside, I have a couple of Exabyte drives in my
home world. They haven't been used for a long time, but when
they were (for some years I used them as a regular backup device)
they worked just fine.
I've pinged the guy.
Norman Wilson
Toronto ON
I keep a copy of the utzoo files.
And then I hacked the altavista desktop search the files using Apache to filter content inline.
https://altavista.superglobalmegacorp.com/altavista
I know I'd love to feed it more data, the utzoo stuff is massive for 1991, but it's really trivial for 2019. It's around 10GB decompressed.
From: TUHS <tuhs-bounces(a)minnie.tuhs.org> on behalf of Larry McVoy <lm(a)mcvoy.com>
Sent: Thursday, November 21, 2019, 11:53 AM
To: Bakul Shah
Cc: tuhs(a)tuhs.org
Subject: Re: [TUHS] Steve Bellovin recounts the history of USENET
On Wed, Nov 20, 2019 at 07:50:53PM -0800, Bakul Shah wrote:
> On Wed, 20 Nov 2019 19:14:23 -0800 Larry McVoy wrote:
> > Yeah, I'd be super happy if he joined the list. I enjoyed reading
> > those, wished he had gone into more detail.
> >
> > On the Usenet topic, does anyone remember dejanews? Searchable
> > archive of all the posts to Usenet. Google bought them and then,
> > so far as I know, the searchable part went away.
> >
> > If someone knows how to search back to the beginnings of Usenet,
> > my early tech life is all there, I'd love to be able to show my kids
> > that. Big arguing with Mash on comp.arch, following Guy Harris on
> > comp.unix-wizards, etc.
>
> I have occasionally downloaded some mbox.zip files from
> https://archive.org/details/usenet
> But there are too many files there. Would be nice if there
> was a collaborative effort to organize them in a more usable,
> searchable state. Pretty much all of it (minus binaries
> groups) can be stored locally (or using some global
> namespace.
So is that all of Usenet?
--
---
Larry McVoy lm at mcvoy.comhttp://www.mcvoy.com/lm
Dear All:
I was wondering if anyone had any first-hand information about the early decisions at Western Electric to make an education license for Unix that was both royalty-free and with an extremely modest “service charge”/delivery fee, or if anyone knows the names of key people who made these decisions.
Best wishes,
David
..............
David C. Brock
Director and Curator
Software History Center
Computer History Museum
computerhistory.org/softwarehistory<http://computerhistory.org/softwarehistory>
Email: dbrock(a)computerhistory.org
Twitter: @dcbrock
Skype: dcbrock
1401 N. Shoreline Blvd.
Mountain View, CA 94943
(650) 810-1010 main
(650) 810-1886 direct
Pronouns: he, him, his
> From: Arnold Robbins
> The Bell Labs guys in some ways were too.
And there's the famous? story about the Multics error messages in Latin,
courtesty of Bernie Greenberg. One actually appeared at a customer site once,
whereupon hilarity ensued.
Noel
Clem Cole:
Al Arms
wrote and administer the license BTW.
====
Aside for entertainment purposes: at one point, the root
password for the UNIX systems I ran in the Caltech High
Energy Physics group was derived from Al's name, but through
a level of punning indirection. I believe Mark Bartelt
came up with it.
Later we decided to change it. I believe I chose the
successor, which continued the UNIX-licensing scheme, but
in a different direction:
*UiaTMoBL
The systems that had either of these passwords are long-
since turned off.
Norman Wilson
Toronto ON