The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ecashin@noserose.net (Ed Cashin)
Subject: [TUHS] Fwd: A cameo by UNIX in BSTJ
Date: Wed, 24 Jul 2013 15:30:41 -0400	[thread overview]
Message-ID: <CADvA-dnqem77BvFN1LGrEy7bOw=tWDteZS-weCCnSfORvpLacw@mail.gmail.com> (raw)
In-Reply-To: <20130724024720.GH28626@bitmover.com>

What parts are missing from the archive mentioned by Poul-Henning Kamp?

  http://www3.alcatel-lucent.com/bstj/

It has 1922 to 1983.  I was assuming that missing issues like 1942 issues 2
through 4 were not ever published.

On Tue, Jul 23, 2013 at 10:47 PM, Larry McVoy <lm at bitmover.com> wrote:

> I'd like to know where I can get the entire BSTJ.  For the record,
> Bell Labs was the *the* place when I was growing up.  Reading their
> journals was right up there with having an account on slovax at
> uwisc and reading the bell labs/BSD source.
>
> On Wed, Jul 24, 2013 at 11:34:10AM +1000, Warren Toomey wrote:
> > All, I got this interesting e-mail from Poul-Henning a few days ago.
> >       Warren
> >
> > ----- Forwarded message from Poul-Henning Kamp <phk at phk.freebsd.dk>
> -----
> >
> >    Date: Sat, 20 Jul 2013 13:27:27 +0000
> >    From: Poul-Henning Kamp <phk at phk.freebsd.dk>
> >    To: wkt at tuhs.org
> >    Subject: A cameo by UNIX in BSTJ
> >
> > Some months ago I faced a flight from Denmark to NZ and back again,
> > so I bought a Kobo eBook reader and reformatted the entire BSTJ to fit
> > the screen.
> >
> > That gave me about 100k "pages" to read, plenty for my NZ-flights
> > and a large number of otherwise wasted moments since then.  Highly
> > recommeded.
> >
> > Recently I came over what I belive is the first mention of UNIX in BSTJ.
> >
> > We all know about the v57i6, July-August 1978 "UNIX Time-Sharing System"
> > issue, but it transpires that UNIX made a cameo two years earlier
> > in an article about compression-schemes for TeleFax:
> >
> > www3.alcatel-lucent.com/bstj/vol55-1976/articles/bstj55-10-1539.pdf
> >
> > Enjoy,
> >
> > Poul-Henning
> >
> > --
> > Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> > phk at FreeBSD.ORG         | TCP/IP since RFC 956
> > FreeBSD committer       | BSD since 4.3-tahoe
> > Never attribute to malice what can adequately be explained by
> incompetence.
> >
> > ----- End forwarded message -----
> > _______________________________________________
> > TUHS mailing list
> > TUHS at minnie.tuhs.org
> > https://minnie.tuhs.org/mailman/listinfo/tuhs
>
> --
> ---
> Larry McVoy                lm at bitmover.com
> http://www.bitkeeper.com
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>



-- 
  Ed Cashin <ecashin at noserose.net>
  http://noserose.net/e/
  http://www.coraid.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20130724/96e45fea/attachment.html>


  reply	other threads:[~2013-07-24 19:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24  1:34 Warren Toomey
2013-07-24  2:47 ` Larry McVoy
2013-07-24 19:30   ` Ed Cashin [this message]
2013-07-25 22:10 Doug McIlroy

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='CADvA-dnqem77BvFN1LGrEy7bOw=tWDteZS-weCCnSfORvpLacw@mail.gmail.com' \
    --to=ecashin@noserose.net \
    /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).