9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Iruatã Souza" <iru.muzgo@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] How to mange cwfs on 9front?
Date: Fri,  2 Dec 2011 09:18:45 -0200	[thread overview]
Message-ID: <CABJnqBTzTBjLySGYh+dEDaOWEtq5CZmB2hKu=F2b=sHWSJbdMg@mail.gmail.com> (raw)
In-Reply-To: <dd662fc63fb5f464eca7096cf7d8396f@hera.eonet.ne.jp>

On Fri, Dec 2, 2011 at 9:04 AM,  <kokamoto@hera.eonet.ne.jp> wrote:
> Hi
>
> I just installed 9front on a Celeron 2.8GHz with 1GB mashine
> on a 40GB hard drive. :-)   Yes, I just tried it for test.
> (When I used 528MB memory, I was rejected by insufficient memory).
>
> I know 9front doesn't add anything new to Plan 9.   However, I'm interested
> how they implemented Ken's fs to a user space where any user process can run.
>
> How I can control the cwfs (on the terminal above)?  In the Ken's fileserver
> we have a special console to control the fileserver.   However, I could not
> find such a console on 9front...
>

9front adds new stuff, see http://code.google.com/p/plan9front/wiki/features.
Cwfs(4) (the user space Ken fs) was not written by 9front, and is
available on Plan 9 as well. To use it, please read cwfs(4) and fs(8).



  reply	other threads:[~2011-12-02 11:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02 11:04 kokamoto
2011-12-02 11:18 ` Iruatã Souza [this message]
2011-12-02 12:33   ` cinap_lenrek
2011-12-02 11:22 ` kokamoto
2011-12-02 13:53 ` erik quanstrom
2011-12-05 13:07 kokamoto
2011-12-06  1:12 ` kokamoto
2011-12-08 11:26   ` kokamoto
2011-12-08 16:17     ` stephen wiley
2011-12-08 16:47       ` erik quanstrom
2011-12-09  0:39         ` kokamoto
2011-12-09  0:37       ` kokamoto
2011-12-07 13:07 ` kokamoto

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='CABJnqBTzTBjLySGYh+dEDaOWEtq5CZmB2hKu=F2b=sHWSJbdMg@mail.gmail.com' \
    --to=iru.muzgo@gmail.com \
    --cc=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).