The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: dds@aueb.gr (Diomidis Spinellis)
Subject: [TUHS] Pursuing Bell Labs stuff
Date: Tue, 5 Jul 2016 08:32:51 +0300	[thread overview]
Message-ID: <dd8d1fe4-0307-b8a3-3492-ee4393d3e7c0@aueb.gr> (raw)
In-Reply-To: <1467677821.3548319.656802617.25F4856C@webmail.messagingengine.com>

The following book provides an interesting perspective on many of the 
questions you ask.

Narain Gehani. Bell Labs: Life in the Crown Jewel. Silicon Press, 
Summit, NJ, 2003.

Many of the Bell Labs technical reports related to Unix were also 
published in volume 2 of the Unix Programmer's Manual. Some also 
appeared in the Bell System Technical Journal.  Back issues of the 
latter used to be freely available online, but they now live behind the 
IEEE Xplore Digital Library pay-wall.  Two  issues of BSTJ devoted to 
Unix (volume 57 number 6 July-August 1978 and volume 63, number 8, 
October 1984) were also published in book form (titled "Unix System 
Readings and Applications") by Prentice-Hall in 1987.


On 05/07/2016 03:17, Wendell P wrote:
> Since a few people here are Bell Labs veterans, I'd to ask if someone
> can explain a bit about that place. Sometimes I hear about work done
> there that I'd like to follow up on, but I have no idea where to start.
>
> For starters, I assume that everybody had to write up periodical reports
> on their work. Was that stuff archived and is it still accessible
> someplace? What about software that got to the point that it actually
> had users beyond the developers? I know that major commercial projects
> like UNIX are tied up in licensing limbo, but does that apply to
> absolutely everything made there?
>
> There is the AT&T Archives and History Center in Warren, NJ. Is it worth
> asking if they have old tech reports?
>



  reply	other threads:[~2016-07-05  5:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-05  0:17 Wendell P
2016-07-05  5:32 ` Diomidis Spinellis [this message]
2016-07-05  8:20   ` arnold
2016-07-05 15:28   ` Wendell P

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=dd8d1fe4-0307-b8a3-3492-ee4393d3e7c0@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).