The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wkt@tuhs.org (Warren Toomey)
Subject: [TUHS] 4.3BSD TAHOE aka what is a TAHOE?!
Date: Fri, 24 Feb 2017 13:38:13 +1000	[thread overview]
Message-ID: <20170224033813.GA11542@minnie.tuhs.org> (raw)
In-Reply-To: <7ef5abf3-8e66-4755-b7ee-c8ddf13f3bf6@SG2APC01FT029.eop-APC01.prod.protection.outlook.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]

On Fri, Feb 24, 2017 at 11:33:54AM +0800, jsteve at superglobalmegacorp.com wrote:
>    I’ve always wondered what on earth a TAHOE was, as they disappeared
>    just about as quickly as they came out.  As we all know that they were
>    instrumental from separating out the VAX code from 4.3BSD in the
>    official CSRG source.  I was looking through old usenet stuff when I
>    typed in something wrong, and came across people looking for GCC for
>    the Tahoe running BSD.
>    ([1]http://altavista.superglobalmegacorp.com/usenet/b128/comp/sys/tahoe
>    /79.txt)

I've exploded the Unix-related parts of the Usenet archive from UTZoo,
so you can look here for more Tahoe postings:

http://www.tuhs.org/Usenet/comp.sys.tahoe/

Cheers, Warren

P.S Also http://www.tuhs.org/Usenet
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170224/8decc2a0/attachment.sig>


  reply	other threads:[~2017-02-24  3:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24  3:33 jsteve
2017-02-24  3:38 ` Warren Toomey [this message]
2017-02-24  3:51   ` jsteve
2017-02-24  4:23 ` Erik E. Fair
2017-02-24  4:27   ` Cory Smelosky
2017-02-24  4:35     ` jsteve
2017-02-24  4:36       ` Cory Smelosky
2017-02-24  4:33   ` jsteve
2017-02-24 21:30   ` Dave Horsfall

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=20170224033813.GA11542@minnie.tuhs.org \
    --to=wkt@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).