[9fans] what should 'fileserver' be set to in fossil?

[9fans] what should 'fileserver' be set to in fossil?

[andrey mirtchovski]

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%

Re: [9fans] what should 'fileserver' be set to in fossil?

[David Presotto]

What's the value of /env/fileserver when you're running fossil?

Re: [9fans] what should 'fileserver' be set to in fossil?

[andrey mirtchovski]

it's not set -- i've commented it out in /rc/bin/cpurc (the first line of
the long paste in my previous message illustrates that)..

it's also not set in /sys/lib/sysconfig/<myconfig>/boot


i've resorted for now to doing 'srv <fossil ip> kfs' and setting
'fileserver=kfs' in /rc/bin/cpurc, which shuts 'lp' up.

looking at how lp wants to connect to net!$fileserver!9fs and then mount it
at /n/$fileserver^'other' i suspect that 'fileserver=kfs' is a special case
that lp (or whatever's doing all those mounts) knows how to handle -- after
all it works fine if the name is 'kfs' and doesn't work fine if the name is
anything else, regardless of whether the /srv/ file descriptor points to a
kfs or a fossil file server:


plan9% fileserver=blah
plan9% srv plan9 blah # fossil
post...
plan9% man -P kfs
converting from troff to postscript...
mount: mount /n/blahother: '/n/blahother' does not exist
cannot mount /n/blahother filesystem
reading through postscript...
cannot find end of first line
plan9% fileserver=kfs
plan9% srv plan9 kfs  # again fossil, just use the right name
post...
plan9% man -P kfs     # works!
converting from troff to postscript...
reading through postscript...
plan9%

andrey

ps: sorry for being so wordy, just trying to explain as best as i can

On Fri, 27 Jun 2003, David Presotto wrote:

> What's the value of /env/fileserver when you're running fossil?
>

Re: [9fans] what should 'fileserver' be set to in fossil?

[David Presotto]

Our lp is just rediculously dependent on our local setup.
I'll fix that.

Re: [9fans] what should 'fileserver' be set to in fossil?

[andrey mirtchovski]

same thing but with the 'hpost' postscript preprocessor -- if it doesn't
find a machine name in .machinelist it assumes that the users are from
'astro', which you guys have defined for all bell-labs machines. net effect
is that everybody here gets 'u/unknown.1' (rabbit ears).

i'm not sure of a proper fix for this -- i changed 'astro' to 'unknown' and
defined the few plan9 users as unknown/username in .dict..

andrey

On Fri, 27 Jun 2003, David Presotto wrote:

> Our lp is just rediculously dependent on our local setup.
> I'll fix that.
>

Re: [9fans] what should 'fileserver' be set to in fossil?

[David Presotto]

On Fri Jun 27 15:08:29 EDT 2003, mirtchov@cpsc.ucalgary.ca wrote:
> same thing but with the 'hpost' postscript preprocessor -- if it doesn't
> find a machine name in .machinelist it assumes that the users are from
> 'astro', which you guys have defined for all bell-labs machines. net effect
> is that everybody here gets 'u/unknown.1' (rabbit ears).
>

I changed hpost to just use the machine name if it can't find the entry in
.machinelist.  This is what it should have been all along.

> i'm not sure of a proper fix for this -- i changed 'astro' to 'unknown' and
> defined the few plan9 users as unknown/username in .dict..

.machinelist is just a local aliasing mechanism.  If you have a list of
ucalgary people, you should probably add an entry that looks like:

(.*\.)?ucalgary\.ca	ucalgary.ca

or

(.*\.)?ucalgary\.ca	ucalgary

I would have suggested ucal but then you'ld clash with all those
californians.  If you pick one, we can add

I'ld change us from astro to something else, but that would probably
screw everyone that have modified the .dict files for themselves.
Astro was short sighted of us, though it survived a company split and
the domain name wouldn't have.

Re: [9fans] what should 'fileserver' be set to in fossil?

[andrey mirtchovski]

On Sun, 29 Jun 2003, David Presotto wrote:

> I would have suggested ucal but then you'ld clash with all those
> californians.  If you pick one, we can add

ucalgary.ca is fine, though nobody else but me posts to 9fans from here.
chances are this will stay for a while :)

what i'd like to have is a generalized way of adding faces to a main
repository -- for example, i think we sent our LANL faces to nemo in spain,
but i don't know whether they were added at all to the main plan9 distro...

there are three faces for the lanl group at this address:

	http://www.acl.lanl.gov/plan9/who.html

i like faces' idea, i'd like to see it expand :)

Re: [9fans] what should 'fileserver' be set to in fossil?

[David Presotto]

I copied the faces into ours.  I noticed we've drifted from
the .dict on sources so I won't get around to merging in all
the changes till tomorrow.  Thanks for the faces.

Re: [9fans] what should 'fileserver' be set to in fossil?

[David Presotto]

If anyone emails faces/names to me, I'll stick them in the
distribution.