From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: [9fans] what should 'fileserver' be set to in fossil?
Date: Fri, 27 Jun 2003 11:12:02 -0600 [thread overview]
Message-ID: <Pine.LNX.4.44.0306271107440.32274-100000@fbsd.cpsc.ucalgary.ca> (raw)
with kfs things like 'man -P kfs' work fine (fileserver=kfs), with fossil we
run into some problems:
plan9% echo $fileserver
plan9% man -P kfs
converting from troff to postscript...
srv: dial net!emelie!9fs: cs: can't translate address: dns: resource does not exist
mount: can't open /srv/emelie: '/srv/emelie' file does not exist
cannot mount /n/emelieother filesystem
reading through postscript...
cannot find end of first line
plan9% fileserver=boot
plan9% ls /srv/boot # this is my fossil srv point
/srv/boot
plan9% man -P kfs
converting from troff to postscript...
mount: mount /n/bootother: fsys: 'other' not found
cannot mount /n/bootother filesystem
reading through postscript...
cannot find end of first line
plan9% fileserver=kfs
plan9% man -P kfs
converting from troff to postscript...
srv: dial net!kfs!9fs: cs: can't translate address: dns: resource does not exist
mount: can't open /srv/kfs: '/srv/kfs' file does not exist
cannot mount /n/kfs filesystem
reading through postscript...
cannot find end of first line
plan9% srv 136.159.220.110 kfs # this machine actually is a kfs file server
post...
plan9% man -P kfs # this works, hail plan9 :)
converting from troff to postscript...
reading through postscript...
plan9% rm /srv/kfs
plan9% srv tcp!sources.cs.bell-labs.com kfs # this is funny :)
post...
plan9% man -P kfs
converting from troff to postscript...
bind: /n/kfs/lp: '/n/kfs/lp' file does not exist
cannot bind /n/kfs/lp onto /sys/lib/lp
reading through postscript...
cannot find end of first line
plan9%
plan9% fileserver=192.168.1.3 # this is the machine with fossil
plan9% man -P kfs # this _should_ work
converting from troff to postscript...
srv: dial net!192.168.1.3!9fs: connection rejected
mount: can't open /srv/192.168.1.3: '/srv/192.168.1.3' file does not exist
cannot mount /n/192.168.1.3other filesystem
reading through postscript...
cannot find end of first line
plan9%
plan9% fileserver=plan9 # aka this very same machine
plan9% man -P kfs
converting from troff to postscript...
post...
mount: mount /n/plan9other: '/n/plan9other' does not exist
cannot mount /n/plan9other filesystem
reading through postscript...
cannot find end of first line
plan9% fileserver=192.168.1.3 # same thing
plan9% man -P kfs
converting from troff to postscript...
post...
mount: mount /n/192.168.1.3other: '/n/192.168.1.3other' does not exist
cannot mount /n/192.168.1.3other filesystem
reading through postscript...
cannot find end of first line
plan9% srv plan9 kfs # now just serve it under kfs
post...
plan9% fileserver=kfs
plan9% man -P kfs # and it works...
converting from troff to postscript...
reading through postscript...
plan9%
next reply other threads:[~2003-06-27 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 17:12 andrey mirtchovski [this message]
2003-06-27 18:19 David Presotto
[not found] <f69c3ec05fb9176abd7083cccea1597c@plan9.bell-labs.com>
2003-06-27 18:35 ` andrey mirtchovski
2003-06-27 19:01 ` David Presotto
2003-06-27 19:07 ` andrey mirtchovski
2003-06-29 16:25 ` David Presotto
2003-06-29 16:35 ` andrey mirtchovski
2003-06-30 3:13 ` David Presotto
2003-06-29 16:42 David Presotto
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=Pine.LNX.4.44.0306271107440.32274-100000@fbsd.cpsc.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).