Score! I'm not planning to scan all of these in unless someone really cares
and has a better scanner than I do. I'm going to prioritize the following:
516-10, -11, -18 Ring Formats
516-12 Specifications for the Node Modem Interface
516-22 A Repeater for the Node Modem
516-28 I/O Ring Device Codes
516-36 Node Modem Interface for Computer Terminals
516-72 Node Test
516-73 Node I/O Software
516-57 Format for the 516 Node - TIU Spider Interface
516-67 Node Format for PDP-11
Jon
In my humble-but-correct opinion*, Linux and its
origins fit into the general topic of UNIX history
just as well as those of Research UNIX or BSD or
SVr4.2.2.2.2.2.2.2 or SunOS or IRIX or Ultrix or
Tru64-compaqted-HPSauce or whatever. It all stems
from the same roots, despite the protestations of
purists from all sides.
Warren gets final say, of course, but to encourage
him I will say: Ploooogie!
Norman Wilson
Toronto ON
* One of Peter Weinberger's sayings that I still
enjoy overusing.
Honestly, I'm not quite sure if this is a TUHS, COFF, or IH question. But
since my background with respect to such things is largely Unix centric, I
thought I'd ask in that context, hence asking on TUHS.
I assume some of the regulars on this list have authored RFCs (of the IETF
etc variety). The RFC format seems fairly well fixed: table of contents,
fixed number of lines per page, page numbers and dates in the footer, and
so forth. The format is sufficiently complex that it seems like some
tooling could be usefully employed to aid in producing these documents.
So I'm curious: what tools did people use to produce those documents?
Perhaps `nroff` with custom macros or something?
- Dan C.
