From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] fsconfig man page
Date: Mon, 1 Dec 2014 15:34:58 +0900 [thread overview]
Message-ID: <6fc0a58f82fe219cc98f3f1dfb29c3f2@titan.jitaku.localdomain> (raw)
In-Reply-To: <8135de0c426db0a88fde90665ff40857@x230.inri>
> What is the problem, exactly?
I'm trying to run a local cwfs based terminal with another auth
server. I get an error code of like 'no route to auth server'.
Then, I have to clarify what is the real difference between the Ken's
fs and cwfs. In Ken's fs, we have to make fsconfig to set ipaddresses
etc.
9front's fsconfig man page says for an example:
service fsb
config w0
filsys main cw2j(w4w5)(l<0-31>)
filsys dump o
filsys hp40fx cw3j(w1.<3-4>.0)(l<0-31>)
filsys hp40fxdump o
filsys other w0
ipauth 0.0.0.0
ipsntp 10.9.0.3
ip0 10.9.0.2
ipgw0 10.9.0.3
ipmask0 255.255.0.0
ip1 10.0.0.2
ipgw1 10.0.0.1
ipmask1 255.255.0.0
ream main
ream hp40fx
ream other
end.
However, this is no true in case of 9front cwfs.
Then, I want real manual page for fsconfig of plan9front.
Kenji
prev parent reply other threads:[~2014-12-01 6:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 6:54 sl
2014-12-01 6:34 ` kokamoto [this message]
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=6fc0a58f82fe219cc98f3f1dfb29c3f2@titan.jitaku.localdomain \
--to=kokamoto@hera.eonet.ne.jp \
--cc=9front@9front.org \
/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).