The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: dds@aueb.gr (Diomidis Spinellis)
Subject: [TUHS] Bell Labs Computer Science Technical Reports
Date: Tue, 21 Mar 2017 19:38:05 +0200	[thread overview]
Message-ID: <f0119d91-aa3f-1321-2052-daba5a082be1@aueb.gr> (raw)

I was searching today to find where the Unix pipeline spell checking 
method "tr | sort | uniq | comm" was first published.  I found it in a 
document by Brian Kernighan titled "UNIX for Beginners".

"The pipe mechanism lets you fabricate quite complicated operations out 
of spare parts already built. For example, the first draft of the spell 
program was (roughly) [...]"

http://www.psue.uni-hannover.de/wise2014_2015/material/Unix-Beginners.pdf#page=11

Then my problem became properly citing the document.  Searching on 
Google, Google Scholar, and IEEE Xplore didn't help me.  In the end I 
found the reference in a 1993 refer file of all Bell Labs Computer 
Science Technical Reports I had saved from my student days.

%cstr 75
%report Comp. Sci. Tech. Rep. No. 75
%keyword CSTR OBS
%author B. W. Kernighan
%title UNIX for Beginners
%date February 1979
%journal UNIX Programmer's Manual
%volume 2
%other Section 3
%date January 1979
%type techreport obsolete

I couldn't find the refer file online, so I'll send a copy to Warren for 
archiving.

However, I'm wondering whether we should/could do something to also 
archive the actual pages of all the Bell Labs Computer Science Technical 
Reports.  I think some are the only authoritative primary source for 
many Unix-related gems and a lack of an electronic archive means they 
will slowly fade into non-existence.  I remember we had many of those at 
the library of Imperial College London.  Any suggestions on what we can 
do to archive this material?

Diomidis


             reply	other threads:[~2017-03-21 17:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21 17:38 Diomidis Spinellis [this message]
2017-03-21 20:29 ` Warren Toomey
2017-03-21 22:55   ` Larry McVoy
2017-03-22  1:31     ` Toby Thain

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=f0119d91-aa3f-1321-2052-daba5a082be1@aueb.gr \
    --to=dds@aueb.gr \
    /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).