From: Paul Borman prb@bsdi.com
Subject: cant start 9pcfs
Date: Wed, 13 Mar 1996 23:45:18 -0500 [thread overview]
Message-ID: <19960314044518.EEOHNCeG_mpkfNQ6k7vGZmCdH6WYJAgkzCBNkfh6mxU@z> (raw)
Thanks to daveb@tkg.com who suggested I use a camcorder to "catch"
the screen. I was putzing with trying to get it to freeze on the
right frame when jim mckie pointed out I could use a serial console.
The problem text was:
iobufinit
-3290 buffers; -409 hashes
This is most certainly due to a memory sizing problem (heaven knows
we have made the rounds with this one with BSD/OS...) For now I
have just hacked fs/pc.c and limited it to search only the first 16MB,
which is all I have. It would probably be nice to have the ability
to specify the maximum amount of memory available in the plan9.ini file.
(BSD/OS still has this sort of escape hatch as some machine are just
too bizarre for words).
The great experiment continues on :-)
-Paul Borman
prb@bsdi.com
next reply other threads:[~1996-03-14 4:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-14 4:45 Paul [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-03-14 18:29 Paul
1996-03-14 9:32 forsyth
1996-03-14 1:46 jim
1996-03-13 21:39 Paul
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=19960314044518.EEOHNCeG_mpkfNQ6k7vGZmCdH6WYJAgkzCBNkfh6mxU@z \
--to=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).