From: Thomas Riemer triemer@babbitt.bernstein.com
Subject: CPU server
Date: Sat, 16 Mar 1996 20:27:29 -0500 [thread overview]
Message-ID: <19960317012729.qYFll9PhjnYKt1Jwc9pDg4fwJdoP2_FATgQsOLV8u7g@z> (raw)
I'm sorry to clutter the bandwidth here... but since
the next thing that I have to deal with is setting up a CPU
server... is there a magic memory requirement for CPU servers
too?
-Tmo
---- Where theory and reality meet.
---- Thomas Riemer, triemer@wesleyan.edu
next reply other threads:[~1996-03-17 1:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-17 1:27 Thomas [this message]
1996-03-17 12:51 forsyth
1996-03-17 19:03 Scott
1996-03-17 20:03 jim
1996-03-17 21:37 Scott
1996-03-18 0:44 jim
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=19960317012729.qYFll9PhjnYKt1Jwc9pDg4fwJdoP2_FATgQsOLV8u7g@z \
--to=9fans@9fans.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).