From: thinktankworkspaces@gmail.com
To: 9front@9front.org
Subject: 9fs
Date: Sat, 8 Aug 2020 13:44:22 -0700 [thread overview]
Message-ID: <F702DC278B1A9CA14CF5F9A0A772158D@gmail.com> (raw)
so I though by default serving 9p even as read only would
occur by default in cpurc script as cpu+auth server
# cpu+auth server
auth/keyfs -wp -m /mnt/keys /adm/keys
aux/listen -q -t /rc/bin/service.auth -d $serviced tcp
ipnet=yoda ip=192.168.1.0 ipmask=255.255.255.0
ipgw=192.168.1.1
dns=8.8.8.8
auth=192.168.1.172
dnsdom=yoda
authdom=yoda
fs=192.168.1.1
cpu=foo
smtp=foo
sys=localhost dom=localhost ip=127.0.0.1
sys=foo dom=foo.yoda ether=525400123336 ip=192.168.1.172
sys=cirno dom=cirno.thinktank ether=080027f9ec98 ip=172.27.0.67
sys=cpubar dom=foo.yoda ether=525400124242 ip=192.168.1.42
There is nothing in /cfg/$sysname including no default
so how is this working as CPU/Auth but then when I dial
from my second CPU i get rejected. The port should be 564 right?. Not 9999
cpu% 9fs foo.yoda
srv: dial net!foo.yoda!9fs: connection rejected
next reply other threads:[~2020-08-08 20:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 20:44 thinktankworkspaces [this message]
2020-08-08 21:26 ` [9front] 9fs hiro
2020-08-08 21:28 ` thinktankworkspaces
2020-08-08 21:49 ` hiro
2020-08-08 22:00 ` thinktankworkspaces
2020-08-08 22:10 ` hiro
2020-08-08 22:43 ` thinktankworkspaces
2020-08-08 22:52 ` thinktankworkspaces
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=F702DC278B1A9CA14CF5F9A0A772158D@gmail.com \
--to=thinktankworkspaces@gmail.com \
--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).