From: hansolofalcon@worldnet.att.net (Gregg C Levine)
Subject: 32V update (was Re: [TUHS] While on the subject of 32V ...)
Date: Fri, 31 Oct 2003 18:53:32 -0500 [thread overview]
Message-ID: <004801c3a00a$44e548a0$0100a8c0@who5> (raw)
In-Reply-To: <1d3.138fde73.2cd43e3b@aol.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1655 bytes --]
Hello (again) from Gregg C Levine
I don't know, it makes sense. Sort of. There's nothing wrong with
thinking out loud, I do that all the time here.
As for recreating that world, all I can say is why not? There's
technology out there waiting to be used, and talent to provide for it.
-------------------
Gregg C Levine hansolofalcon at worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke." Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )
> -----Original Message-----
> From: tuhs-bounces at minnie.tuhs.org
[mailto:tuhs-bounces at minnie.tuhs.org] On
> Behalf Of Robertdkeys at aol.com
> Sent: Friday, October 31, 2003 5:38 PM
> To: Pat.Villani at hp.com; wes.parish at paradise.net.nz
> Cc: tuhs at tuhs.org
> Subject: Re: 32V update (was Re: [TUHS] While on the subject of 32V
...)
>
> Or, for something really wierd...., how about porting 32V to
> the modern VAXen, such as the scsi 3000 or 4000 class
> machines? x86 is nice, and good to do because of its
> generic ubiquity, but somehow it ought to roll again on
> something, VAX, too.....(:+}}... just for usable posterity.
> How much of a chore would it be to port from say an
> Ultrix box? The tool chain should be basically intact.
> Mebbie it is time to dust off our old VAX 3000 M38 crates.
>
> There I go thinking out loud...., again.....
>
> Bob Keys
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> http://minnie.tuhs.org/mailman/listinfo/tuhs
next prev parent reply other threads:[~2003-10-31 23:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 22:37 Robertdkeys
2003-10-31 23:53 ` Gregg C Levine [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-04 18:18 macbiesz
2003-11-05 10:23 ` Wesley Parish
2003-10-20 13:35 [TUHS] While on the subject of 32V Pat Villani
2003-10-22 8:10 ` Wesley Parish
2003-10-24 13:41 ` Pat Villani
2003-10-30 12:56 ` 32V update (was Re: [TUHS] While on the subject of 32V ...) Pat Villani
2003-10-31 10:13 ` Wesley Parish
2003-10-31 14:26 ` Pat Villani
2003-11-05 2:22 ` Greg Lehey
2003-11-05 12:53 ` Pat Villani
[not found] ` <200311022346.34747.wes.parish@paradise.net.nz>
[not found] ` <oprx0h6gtdrveh1e@smtp.borf.com>
2003-11-03 10:48 ` Wesley Parish
2003-11-03 15:34 ` Pat Villani
2003-11-04 9:56 ` Wesley Parish
2003-11-04 13:51 ` Pat Villani
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='004801c3a00a$44e548a0$0100a8c0@who5' \
--to=hansolofalcon@worldnet.att.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).