I've just installed Plan 9 on a new terminal that will soon become my
new auth/cpu/file server. It's a [EMAIL PROTECTED], 128MB of RAM, and a 500GB
hard drive. I made a 10GB fossil and gave the rest to venti. When I
boot, I find that pretty much all of the 128 megs is being used, and
of
From the wiki page: http://netlib.bell-labs.com/wiki/plan9/papers/
You can obtain the sources documented in this book from:
http://plan9.escet.urjc.es/plan9jun.tgz
-Original Message-
From: [EMAIL PROTECTED] on behalf of Michaelian Ennis
Sent: Tue 8/12/2008 1:46 PM
To: 9fans@9fans.net
hola,
if you accept the license
http://plan9.bell-labs.com/plan9/license.html
you can fetch it from URJC's site
http://plan9.escet.urjc.es/plan9jun.tgz
On Tue, Aug 12, 2008 at 5:46 PM, Michaelian Ennis
[EMAIL PROTECTED] wrote:
I am reading Nemo's Notes on the Plan 9 3rd edition Kernel Source.
I have found another piece of code I don't understand in the kernel.
syscalls are all fed through a single trap, and the common code which
processes them performs a waserror():
/sys/src/9/pc/trap.c:694
A few lines down this function (after the system call has been
executed up-nerrlab
this is fine for most calls, however rfork() explicitly sets up-nerrlab
to zero rather than copying it and memmove()ing up-errlab from the parent
proc to the child:
/sys/src/9/port/sysproc.c:90
Surely this means that rfork will always fail with a bad errstack [19]: -1
extra
I tried setting mem, bcmem, and icmem all to 1M but no improvement.
They are not set by default, and trying the configuration shown in the
man page actually prevents the system from booting (out of memory).
John
perhaps i'm pointing out the obvious. have you tried something as simple
as ps
