The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
To: Ed Bradford <egbegb2@gmail.com>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Fwd: Trove of CSTR's
Date: Mon, 30 Sep 2024 07:52:57 -0400	[thread overview]
Message-ID: <CAKH6PiVEcfMK=yCQjCzE6ZxYb9B6PhjN_9q9CXhu6PxbHSOSyg@mail.gmail.com> (raw)
In-Reply-To: <CAHTagfEiy44USK=J7CKM0+f7CELj_PeYt5DWf7H4icnmw=k7wQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1839 bytes --]

The Bell Labs archivist, Ed Eckert, ed.eckert@nokia-bell-labs.com, played a
big role in the Labs' Unix50 celebration in 2019. The archives had not only
documents, but also memorabilia from the Unix Room. I obtained a 1970s TM
from him more recently, probably 2022.

An important organizer of Unix50 was martin.carroll@nokia-bell-labs.com. He
also was the inside lead on the release of post-v7 Unix source.

Doug

On Sun, Sep 29, 2024 at 9:23 PM Ed Bradford <egbegb2@gmail.com> wrote:

> Who is/was the professional archivist and where is/was the collection last
> seen?
> Do you have any ideas?
>
> Ed
>
>
> On Sun, Sep 29, 2024 at 9:12 AM Douglas McIlroy <
> douglas.mcilroy@dartmouth.edu> wrote:
>
>> > I wonder what happened to the amazing library at Murray Hill.
>>
>> Last I knew, the Bell Labs archives were intact under supervision of a
>> professional archivist. Formally speaking, the archives and the library
>> were distinct entities. The library, which was open to self service 24
>> hours a day, declined rapidly after the bean counters decreed that it
>> should henceforth support itself on rental fees. Departments immediately
>> turned to buying books rather than borrowing them. It's very likely that
>> this was bad for the Labs' bottom line, but the cost (both monetary and
>> intellectual) was not visible as a budgetary line item.
>>
>> The 24-hour library contributed to one of Ken's programming feats.
>> Spurred by a lunchtime remark that it would be nice to have a
>> unit-conversion program, Ken announced units(1) the next morning. Right
>> from the start, the program knew more than 200 units, thanks to a book Ken
>> grabbed from the library in the middle of the night.
>>
>> Doug
>>
>
>
> --
> Advice is judged by results, not by intentions.
>   Cicero
>
>

[-- Attachment #2: Type: text/html, Size: 3296 bytes --]

  reply	other threads:[~2024-09-30 11:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-29 14:05 Douglas McIlroy
2024-09-30  1:22 ` Ed Bradford
2024-09-30 11:52   ` Douglas McIlroy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-29 12:39 Douglas McIlroy
2024-09-28 23:38 [TUHS] " Warren Toomey via TUHS
2024-09-29  1:30 ` [TUHS] " Rob Pike
2024-09-29  2:18   ` Larry McVoy
2024-09-29  2:20     ` Larry McVoy
2024-09-29  2:25       ` G. Branden Robinson
2024-09-29  4:37         ` Gregg Levine
2024-09-29  2:32 ` Ed Bradford
2024-09-29  2:36 ` G. Branden Robinson
2024-10-01 19:46 ` Chet Ramey via TUHS

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='CAKH6PiVEcfMK=yCQjCzE6ZxYb9B6PhjN_9q9CXhu6PxbHSOSyg@mail.gmail.com' \
    --to=douglas.mcilroy@dartmouth.edu \
    --cc=egbegb2@gmail.com \
    --cc=tuhs@tuhs.org \
    /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).