From: tuhs@cuzuco.com (Brian S Walden)
Subject: [TUHS] Graphic Systems C/A/T phototypesetter
Date: Tue, 10 Dec 2013 12:32:35 -0500 (EST) [thread overview]
Message-ID: <201312101732.rBAHWZet027950@cuzuco.com> (raw)
the one at WH was directly connected to a vax 11/780, no paper tape either.
so that now finally explains why /dev/cat was write only, it was substituted
for a paper tape reader. it was always a curiosity that you could write
to it, yet never read it (i.e. get a status). a "cat /dev/cat" would
get you a "cat: cannot open /dev/cat" while a "cat /some/file > /dev/cat"
would succeed, but act like you used /dev/null instead
(as /some/file was not valid phototypeseter input)
> From: Doug McIlroy
>
> > The wikipedia description
> > <http://en.wikipedia.org/wiki/CAT_(phototypesetter)>
> > seems pretty accurate although I have never seen the beast myself.
>
> I can confirm the wikipedia description. At Bell Labs, however, we
> did not use paper tape input. As soon as the machine arrived, Joe
> Ossanna bypassed the tape reader so the C/A/T could be driven
> directly from the PDP-11. The manufacturer was astonished.
>
> The only operational difficulty we had was with the separate
> developer. If you didn't hand feed the end of the paper perfectly
> straight into that machine, the paper would tear. Joe Condon
> fixed that by arranging for the canister to sit on rollers so
> it could give when the paper pulled sideways.
>
> The first technical paper that came off the C/A/T drew a query
> from the journal editor, who'd never seen a phototypeset
> manuscript before: had it been published elsewhere?
>
> Doug
>
next reply other threads:[~2013-12-10 17:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 17:32 Brian S Walden [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-11 0:30 Doug McIlroy
2013-12-10 14:45 Doug McIlroy
2013-12-10 15:37 ` Larry McVoy
2013-12-10 16:36 ` Clem Cole
2013-12-11 14:15 ` Ronald Natalie
2013-12-11 14:33 ` Warner Losh
2013-12-10 22:11 ` scj
2013-12-11 14:12 ` Clem Cole
2013-12-11 0:03 ` Nick Downing
2013-12-11 2:26 ` Armando Stettner
2013-12-10 6:21 Brian S Walden
2013-12-10 7:28 ` Armando Stettner
2013-12-09 21:29 Jacob Goense
2013-12-09 21:59 ` Jaap Akkerhuis
2013-12-09 22:20 ` Gregg Levine
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=201312101732.rBAHWZet027950@cuzuco.com \
--to=tuhs@cuzuco.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).