9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] python and lua
Date: Fri,  5 Jan 2001 16:10:59 +0900	[thread overview]
Message-ID: <20010105071116.B4A97199D7@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]

>Kfs is not so robust as real fileserver.  I'm now facing this many times.

I should have been more specific ont his problem.   I guess this is concerned
with memory swapping on a swap partition of local disk same with that kfs system 
residing.

My /dev/sdC0 directory shows as:

--rw-r----- S 0 okamoto okamoto      10486784 Jan 5 09:47 /dev/sdC0/9fat
--rw-r----- S 0 okamoto okamoto                      0 Jan 5 09:47 /dev/sdC0/ctl
--rw-r----- S 0 okamoto okamoto  1440940032 Jan 5 09:47 /dev/sdC0/data
--rw-r----- S 0 okamoto okamoto       12354048 Jan 5 09:47 /dev/sdC0/dos
--rw-r----- S 0 okamoto okamoto  1428553728 Jan 5 09:47 /dev/sdC0/plan9
-lrw------- S 0 okamoto okamoto                       0 Jan 5 09:47 /dev/sdC0/raw
--rw-r----- S 0 okamoto okamoto       29863936 Jan 5 09:47 /dev/sdC0/swap

I'm using this 30MB swap partition for swap region when I use kfs filesystem.

When I tried to compile 9pcdisk with rio, ktrans etc (full spec of my machine),
link loader may face dead lock, and then, I have to type ^^t on the way of 
linking.
Another more occuring situation is tar-ing a large compressed file such as linux 
kernel source to my home directory.

When I load root filesystem from our fileserver for this same machine, on the contrary, 
I have no probelem.

Kenji


[-- Attachment #2: Type: message/rfc822, Size: 2004 bytes --]

From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] python and lua
Date: Fri, 5 Jan 2001 12:44:31 0900
Date: Fri, 5 Jan 2001 12:44:31 0900
Message-ID: <20010105034447.E920B199D7@mail.cse.psu.edu>

>I'm running a local kfs, would these go away with a real
>fileserver?

Kfs is not so robust as real fileserver.  I'm now facing this many times.
This is my first time to use kfs efficiently, and got a different view on
Plan 9.  :-)  (I'm kidding)

However, I found sam runnes without rio.  Why I know that?  Because
I have to set an environment for sys user without rio etc. to compile
pcdisk kernel in Toshiba Tecra 48MB memory, local swap system.

Kenji

             reply	other threads:[~2001-01-05  7:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05  7:10 okamoto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-08  5:26 okamoto
2001-01-08  4:51 okamoto
2001-01-08  4:12 Russ Cox
2001-01-08  4:02 okamoto
2001-01-05 12:37 forsyth
2001-01-05 11:58 forsyth
2001-01-05  7:16 okamoto
2001-01-05  4:32 okamoto
2001-01-05  4:17 rob pike
2001-01-05  3:44 okamoto
2001-01-05  3:31 rob pike
2001-01-05  1:48 rob pike
2001-01-02 17:39 [9fans] A Plan 9 Python Interest Group? Randolph Fritz
2001-01-05  3:39 ` [9fans] python and lua Quinn Dunkan
2001-01-05  2:50   ` arisawa

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=20010105071116.B4A97199D7@mail.cse.psu.edu \
    --to=okamoto@granite.cias.osakafu-u.ac.jp \
    --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).