From: Daniel Egnor egnor@whip.ugcs.caltech.edu
Subject: 387 required? *and* Memory errors? Mothra sucks?
Date: Sat, 5 Aug 1995 12:20:12 -0400 [thread overview]
Message-ID: <19950805162012.8up1qPdHz1Qv8urECTqm6XL-o-yEE_82722Xz4lCTKI@z> (raw)
In article <95Aug5.024030edt.46619@colossus.cse.psu.edu>,
<9fans@cse.psu.edu> wrote:
>The "no physical memory" messages can be removed by turning on swapping.
>Choose a swap partition and point swap at it; see swap(8). It is not enabled
>by default because the system cannot safely identify a partition to use; you
>must set one up. The announcement about how much swap space reflects the size
>of an internal data structure.
Neato! I will do this, thanks (though I will have to wait for the CD).
People who have done this, what happens when some process starts chewing up
VM? Can you set process limits in Plan 9?
>A `urlfs' would be folly, because URLs are not a real name space and the
>semantics are utterly unmanageable.
What is meant by this, in particular? Maybe I will re-read some of the papers
to try to understand more fully the concept of a Plan 9 "name space"...
>The argument is analogous to that which prevented us from putting network
>names in the file name space. As for mothra, the interface may be lame but
>I wonder why you think that, given that you have not got the CD
>and therefore probably haven't seen it.
A version of mothra comes with the four disk set.
>Its bugs, as said in the manual, are because it is a very new program.
*nod* -- "early alpha".
Dan
next reply other threads:[~1995-08-05 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-05 16:20 Daniel [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-05 16:10 philw
1995-08-05 8:33 mkc
1995-08-05 7:49 Steven
1995-08-05 6:33 rob
1995-08-05 5:36 Daniel
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=19950805162012.8up1qPdHz1Qv8urECTqm6XL-o-yEE_82722Xz4lCTKI@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).