9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] out of physical memory; no swap configured
Date: Fri, 19 Mar 2010 07:27:36 -0700	[thread overview]
Message-ID: <3e1162e61003190727n45f314dbkfe96db232f8ddc16@mail.gmail.com> (raw)
In-Reply-To: <4ecada1e1003190136o347809b3s4f8d225d47b6c26d@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]

On Fri, Mar 19, 2010 at 1:36 AM, Bela Valek <bvalek2@gmail.com> wrote:

> 2010/3/12 erik quanstrom <quanstro@labs.coraid.com>:
> >> How do other operating systems detect the available RAM? Could Plan 9
> >> use the same method?
> >
> > plan 9 uses the same methods for detecting ram
> > everyone else does.  perhaps we trust bios too much,
> > but 8mb isn't impossible, either.
> >
> > try
> >        a *noe820scan=1
> > at the 9load menu prompt.
> >
> > - erik
> >
> >
>
> Hi,
>
> I tried it and didnt work, I got the same output. Maybe its time to
> trust BIOS less... :(
>


I had this error on VMWare recently.  The solution was to disable Venti and
just use fossil.  Venti is of questionable value when I'm already
snapshotting my host's filesystem anyway.

I think the real correct answer is to set Venti up with the correct
parameters by hand before restarting.  I didn't try that though.

Dave

>
> Greetings: Bela
>
>

[-- Attachment #2: Type: text/html, Size: 1550 bytes --]

  reply	other threads:[~2010-03-19 14:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-27 11:47 Bela Valek
2010-02-27 16:28 ` erik quanstrom
2010-03-12 11:06   ` Bela Valek
2010-03-12 16:37     ` erik quanstrom
2010-03-19  8:36       ` Bela Valek
2010-03-19 14:27         ` David Leimbach [this message]
2010-03-19 14:30           ` erik quanstrom
2010-03-01 22:53 ` Georg Lehner

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=3e1162e61003190727n45f314dbkfe96db232f8ddc16@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --cc=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).