The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jsteve@superglobalmegacorp.com (jsteve@superglobalmegacorp.com)
Subject: [TUHS] 4.3BSD TAHOE aka what is a TAHOE?!
Date: Fri, 24 Feb 2017 11:33:54 +0800	[thread overview]
Message-ID: <7ef5abf3-8e66-4755-b7ee-c8ddf13f3bf6@SG2APC01FT029.eop-APC01.prod.protection.outlook.com> (raw)

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

It’s embarrassing to mention this, but I thought I’d share.

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. (http://altavista.superglobalmegacorp.com/usenet/b128/comp/sys/tahoe/79.txt)


In article <2287 at trantor.harris-atd.com>, bbadger at x102c (Badger BA 64810) writes:
 `We have a Harris HCX-9 computer, also known as a Tahoe, and we'd like to 
 `get gcc and g++ up and running.  I haven't seen anything refering to 
 `the HCX or any Tahoe machines in the gcc distribution.  Anyone have it?
 `Working on it?  Pointers to who might?  Know if Berkely cc/ld/asm is PD?

Turns out they were using Harris mini’s called the HCX-9.  That’s when I went back to the source and saw this:

#
# GENERIC POWER 6/32 (HCX9)
#
machine		tahoe
cpu		"TAHOE"
ident		GENERIC

So if anyone else is wondering what was a Tahoe, did it exist, was there actual sales, is their pictures of it, etc, the answer is yes, it was a real machine, yes it was sold, and there are even print ads in Computer world.

I thought it was interesting though.


Sent from Mail for Windows 10

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170224/6a18de91/attachment-0001.html>


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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24  3:33 jsteve [this message]
2017-02-24  3:38 ` Warren Toomey
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=7ef5abf3-8e66-4755-b7ee-c8ddf13f3bf6@SG2APC01FT029.eop-APC01.prod.protection.outlook.com \
    --to=jsteve@superglobalmegacorp.com \
    /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).