From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil dies?
Date: Mon, 15 Oct 2007 08:56:49 -0400 [thread overview]
Message-ID: <015e947ebe45f8537b2b99086bb524ea@quanstro.net> (raw)
In-Reply-To: <e2f969e10710150059w610a393je058d9c379ac49a0@mail.gmail.com>
> I have 64MB on the box. However, the reason of the fault was out of
> memory condition.
> I was wondered that there was no swap configured in cpurc (termrc do have this).
> Copying lines which configure swap from termrc to cpurc have solved the problem.
>
> Thanks to everybody,
> Yaroslav.
i am currently using an underpowered machine like this with ken's fileserver and
the fact that it's a special kernel is a boon for stability. the fs doesn't overcommit
memory or even use dynamic allocation.
- erik
next prev parent reply other threads:[~2007-10-15 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 9:58 Yaroslav
2007-10-12 14:10 ` erik quanstrom
2007-10-14 4:39 ` sqweek
2007-10-14 16:54 ` geoff
2007-10-15 7:59 ` Yaroslav
2007-10-15 12:50 ` erik quanstrom
2007-10-15 12:56 ` erik quanstrom [this message]
2007-10-23 9:47 Bituman
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=015e947ebe45f8537b2b99086bb524ea@quanstro.net \
--to=quanstro@quanstro.net \
--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).