From: forsyth@caldo.demon.co.uk forsyth@caldo.demon.co.uk
Subject: [9fans] no free mount rpc buffer
Date: Sat, 20 Mar 1999 08:03:45 +0000 [thread overview]
Message-ID: <19990320080345.X9IRc8DewXCbS9fB8YGhWRh-vUT9RNVfXy9WAlfEB98@z> (raw)
>>and I'm wondering if one of the problems is the fact that I don't have
>>a prep'ed disk, and therefore have no nvram location to read/write.
no, it will simply prompt for the information it needs.
(you can put some of it in the plan9.ini file on the boot diskette, though i don't think
the details are documented.)
most of my cpu servers are diskless, with just a boot diskette.
>> aux/listen: no free mount rpc buffer
>> bind: no free mount rpc buffer
the kernel has run out of memory and thus buffer space.
the EOFs probably result from that, too.
i'd check the allocation sizes printed at startup.
you can see the current state of allocation by typing
control-t control-t x
on the console.
since the system has only just started, it seems likely
that it is confused about how much memory it has got
(or reserved for the kernel).
next reply other threads:[~1999-03-20 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-20 8:03 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-03-24 23:18 James
1999-03-20 10:08 forsyth
1999-03-20 9:07 James
1999-03-20 6:00 James
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=19990320080345.X9IRc8DewXCbS9fB8YGhWRh-vUT9RNVfXy9WAlfEB98@z \
--to=forsyth@caldo.demon.co.uk \
/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).