Byard%dca-ems@sri-unix.UUCP (10/26/83)
Date: October 26, 1983 Re: EUUG? Text: I don't know, but I'm also interested. Larry Byard Stuttgart
jdb%s1-c@sri-unix.UUCP (12/16/83)
Please remove me (jdb@s1-c) from the INFO-UNIX mailing list. Thanks.
MCB%mit-mc@sri-unix.UUCP (01/09/84)
From: Michael A. Bloom <MCB@mit-mc> The termcap entry for the adm42 specifies 270 ms padding for insert-line and none for delete line. This seems kind of odd (it also produces a quick upward motion with a slow corresponding downward motion) Has anyone modified this entry for their own use? It looks like someone just forced in a 'worst-case' value. Is there any reason not to use a smaller pad value with * to multiply it by the number of affected lines? Thanks, Michael Bloom (mcb@mit-mc) ( v.sdcrdcf!randvax!ttidca!mab@ucla-net ) arpa ( ..!ucla-vax!sdcrdcf!randvax!ttidca!mab ) uucp
cpr%su-shasta@imagen.UUCP (01/27/84)
If you want hairy DECtape stories, ask the old-time PDP-10'ers. Harvard ran their KA-10 for years with just a 256K Burroughs swapping drum, and DECtapes for all program and data access. It wasn't as bad as it sounds; they were still doing it as late as 1973 (oops, that makes me an old-timer). --Chris Ryland, IMAGEN
gwyn%brl-vld@sri-unix.UUCP (02/05/84)
From: Doug Gwyn (VLD/VMB) <gwyn@brl-vld>
Here is a brief review of "The UNIX Programming Environment" by Brian
W. Kernighan & Rob Pike (1984, Prentice-Hall, ISBN 0-13-937681-X {PBK}).
(The authors work at Bell Labs and are well known to the UNIX community.)
This is the best book I have ever seen for UNIX programmers. The
first few chapters can be read profitably by any intelligent first-time
UNIX user, but the book overall is targeted for professional programmers
who are encountering UNIX for the first time. I must say that many old-
timers could learn something from this book, too.
The chapter titles are:
UNIX for Beginners
The File System
Using the Shell
Filters
Shell Programming
Programming with Standard I/O
UNIX System Calls
Program Development
Document Preparation
Epilog
with appendices
Editor summary
"hoc" Manual
"hoc" Listing
"hoc" is an interpreter for a programmable calculator language, used as
a real-world example of program development.
This book is not just a description of features available on UNIX;
instead, the authors explain what is going on and why. Anyone familiar
with "Software Tools" will recognize the approach.
Roughly half the book emphasizes the use of existing tools in shell
programs. This is as it should be; it is perhaps the single greatest
contribution of UNIX to program development.
It is remarkable how little dependency on the particular version of
UNIX there is. The few variations that matter are dealt with as needed.
I would recommend this book as THE book for all UNIX programmers.warner%clemson.csnet@CSNET-RELAY.ARPA (07/05/84)
From: Daniel Warner <warner%clemson.csnet@CSNET-RELAY.ARPA> Please add WARNER@CLEMSON to the INFO-UNIX special interest group. Clemson is on CSNET. Thanks. Dan Warner
sde@MITRE-BEDFORD.ARPA (08/09/84)
Re S1 OS: There is an article on it in Comp. Design, 1984 July, and another article that makes reference to S1 in a comparison table. David sde@mitre-bedford
bblue@NOSC.ARPA (09/22/84)
I was looking through my uucp log the other day and noticed a syntax I've
never seen used before (or since). I can't find any reference to it or
what it might mean in any documentation I have.
In the THEM/ME fields, what would normally appear:
THEM (S D.xxxxx X.xxxxx .... etc.
In this occurrence, I got:
THEM (S D.xxxxx X.xxxxx **NSC**)
When that particular piece of mail and its header were done, I would usually
get this in the logfile:
daemon XQT (PATH= .... etc.
However in this occurrence:
**NSC** XQT (PATH= ....
The mail was posted correctly, and no other peculiarities were noticed.
Now, uucp wizards, WHAT does **NSC** mean?
--Bill Blue {ihnp4, sdcsvax!bang}!crash!bblue
bang!crash!bblue@nosc