From: kokamoto@hera.eonet.ne.jp
To: 9fans@9fans.net
Subject: [9fans] How to mange cwfs on 9front?
Date: Fri, 2 Dec 2011 20:04:42 +0900 [thread overview]
Message-ID: <dd662fc63fb5f464eca7096cf7d8396f@hera.eonet.ne.jp> (raw)
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...
Kenji
next reply other threads:[~2011-12-02 11:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 11:04 kokamoto [this message]
2011-12-02 11:18 ` Iruatã Souza
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=dd662fc63fb5f464eca7096cf7d8396f@hera.eonet.ne.jp \
--to=kokamoto@hera.eonet.ne.jp \
--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).