From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan9 box
Date: Thu, 30 Nov 2000 10:25:19 +0000 [thread overview]
Message-ID: <20001130102425.8B42C199F9@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 222 bytes --]
i use AMD K6-2, K6-3 and Athlon without fuss.
they've had speeds ranging from 250 to 750.
500/550 should be fine for an all-in-one box;
i use them in terminals but that's mainly because
i can't get anything slower.
[-- Attachment #2: Type: message/rfc822, Size: 2203 bytes --]
From: Bob Solomon <wogsolNOSPAM@bestweb.net>
To: 9fans@cse.psu.edu
Subject: [9fans] plan9 box
Date: Thu, 30 Nov 2000 09:53:32 GMT
Message-ID: <Pine.LNX.4.10.10011300041550.994-100000@betty.bw.org>
I'm thinking of building a plan9 box as this one has 2 OS's
already installed, an incompatible video card and no free
primary partition.
How fast a processor is needed, I'm patient, and are AMD chips
supported? I was thinking of a socket7 chip...
Thanks
next reply other threads:[~2000-11-30 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 10:25 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-30 9:53 Bob Solomon
2000-12-01 5:05 ` Milan Zimmermann
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=20001130102425.8B42C199F9@mail.cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--cc=9fans@cse.psu.edu \
/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).