From: lm@bitmover.com (Larry McVoy)
Subject: [TUHS] Uwisc4.3 question...
Date: Tue, 24 Mar 2009 20:37:16 -0700 [thread overview]
Message-ID: <20090325033716.GG25141@bitmover.com> (raw)
In-Reply-To: <200903240914.n2O9EJOa004453@skeeve.com>
> Ah, those were the days, when men were real men, and computers
> were vaxen. :-)
Heh. When I was in undergrad we were all on an 11/780 with 1MB of ram
and about 30-40 terminals talking to it.
As strange as it may sound, to this day I miss that. Terminal rooms
were the ultimate communication zone. Looking over someone's shoulder
and saying "how did you do that?" when they did !}fmt
Those were the days... Where is Henry Spencer when you need him?
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
next prev parent reply other threads:[~2009-03-25 3:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 9:14 Aharon Robbins
2009-03-24 11:00 ` Jason Stevens
2009-03-24 14:33 ` Larry McVoy
2009-03-25 3:37 ` Larry McVoy [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-27 7:39 Aharon Robbins
2009-03-22 4:53 Jason Stevens
2009-03-22 15:31 ` Larry McVoy
2009-03-22 17:32 ` Jason Stevens
2009-03-22 18:11 ` Al Kossow
2009-03-25 3:44 ` Larry McVoy
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=20090325033716.GG25141@bitmover.com \
--to=lm@bitmover.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).