9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Francisco J Ballesteros" <nemo@lsub.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Re: [9fans] system crash during compile
Date: Tue, 11 Jul 2006 20:41:21 +0200	[thread overview]
Message-ID: <8ccc8ba40607111141q26d2c319if09ba79e217d1924@mail.gmail.com> (raw)
In-Reply-To: <7d3530220607110815p4a4b49dci9e19effe5612067c@mail.gmail.com>

You said your stats for memory usage did remain low. Was this the case?
Couldn´t it be running out of the % of memory used by the kernel?
You could try increasing kernelpcent if that was the case.

On 7/11/06, John Floren <slawmaster@gmail.com> wrote:
> On 7/10/06, andrey mirtchovski <mirtchovski@gmail.com> wrote:
> > On 7/10/06, John Floren <slawmaster@gmail.com> wrote:
> > > So far, nobody can shed any light on the problem? Bugger.
> >
> > didn't russ?
> >
> > anyway, you haven't told us what architecture you have, how much ram,
> > how much hard disk space available and what time of day you're running
> > the command at (don't ask, sometimes it matters)... back in the day
> > ghostscript linking would panic a machine with no swap turned on and
> > only 64MB of ram, but those days are long gone, right?
> >
> > right?!? i mean, i haven't had a need for a swap device since 2002!
> > what is that beastly node on which you must have a kernel compiled,
> > and why can't you just run plan9 in qemu on your main machine?
> >
> Okay, the node is an IBM machine, Pentium 2 processor @ ~300 Mhz, 64
> MB of RAM, ~3 GB of hard drive space. I have a fossil+venti
> configuration set up; exact numbers, I can't tell you, because I'm
> currently 200 miles away from the damn thing. I've tried running the
> command at various times of day.
> I can't run Plan 9 in qemu on my main machine because my main machine
> is somewhere in Ohio at the moment (I think) and I won't have access
> until fall. Besides, it just isn't the same when you're emulating it
> ;-)
>
> John
> --
> TANSTAAFL! (There Ain't No Such Thing As A Free Lunch!)
>
>

  reply	other threads:[~2006-07-11 18:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-09 16:01 John Floren
2006-07-09 18:57 ` Russ Cox
2006-07-09 21:41   ` John Floren
2006-07-11  5:05     ` John Floren
2006-07-11  5:21       ` andrey mirtchovski
2006-07-11 15:15         ` John Floren
2006-07-11 18:41           ` Francisco J Ballesteros [this message]
2006-07-11 22:46             ` David Leimbach
2006-07-12  0:46               ` John Floren
2006-07-12  0:59                 ` andrey mirtchovski
2006-07-12 14:51                   ` John Floren
2006-07-12 21:10                     ` Russ Cox
2006-07-13  0:15                       ` John Floren
2006-07-13  0:17                         ` Francisco J Ballesteros
2006-07-13  2:27                           ` John Floren
2006-07-13  4:09                             ` Russ Cox
2006-07-13  4:10                               ` Russ Cox
2006-07-13 13:44                               ` Brantley Coile
2006-07-13 14:52                                 ` John Floren

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=8ccc8ba40607111141q26d2c319if09ba79e217d1924@mail.gmail.com \
    --to=nemo@lsub.org \
    --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).