From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Any dual or quad motherboard recommendations...
Date: Mon, 27 Aug 2001 11:18:21 -0400 [thread overview]
Message-ID: <20010827151827.E33E5199E7@mail.cse.psu.edu> (raw)
On Mon Aug 27 11:15:37 EDT 2001, cross@math.psu.edu wrote:
> In article <20010827040514.78FCF19A35@mail.cse.psu.edu> you write:
> >It cost ~$30K in 1998 with 2GB memory.
>
> Somewhere I remember reading that Plan 9 would only support machines
> with up to some strange amount of RAM; something along the lines of
> 1.5 or 1.75GB. This would seem to contradict that; what's the max
> amount of RAM that Plan 9 *can* support?
>
> - Dan C.
There's 2GB physical but because of the way we currently map things
we can only use 1.75GB. It's on the list of things to fix.
next reply other threads:[~2001-08-27 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 15:18 jmk [this message]
2001-08-27 16:23 ` Dan Cross
-- strict thread matches above, loose matches on Subject: below --
2001-08-27 4:05 jmk
2001-08-27 15:14 ` Dan Cross
2001-08-25 10:03 Fariborz 'Skip' Tavakkolian
2001-08-26 21:34 ` John Packer
2001-08-28 5:36 ` Eric Dorman
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=20010827151827.E33E5199E7@mail.cse.psu.edu \
--to=jmk@plan9.bell-labs.com \
--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).