From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <a4e6962a0604011044p34f6f49axa524bd24a0c60747@mail.gmail.com>
Date: Sat,  1 Apr 2006 12:44:06 -0600
From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] v9fs and Russ tra
In-Reply-To: <442EB7D4.2050202@asgaard.homelinux.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <1d5d51400603312138x7e132fdbx9ef49f823ee2a7b9@mail.gmail.com>
	<442EB7D4.2050202@asgaard.homelinux.org>
Cc:
Topicbox-Message-UUID: 2b220ede-ead1-11e9-9d60-3106f5b1d025

You are also likely running into auth problems -- easiest thing is to
export without auth, but that may not be desirable.  If you are using
auth, you'll need plan9ports and lucho's mount utility (9p.mount)

     -ericvh

On 4/1/06, "Nils O. Sel=E5sdal" <noselasd@asgaard.homelinux.org> wrote:
> Fernan Bolando wrote:
> > Hi all
> >
> > I have 3 new set of questions. :)
> >
> > Is it possible to mount a plan9 namespace or directory of a cpu server
> > on to a linux terminal using v9fs or should I just use nfsserver?
> > I have been trying to make v9fs by doing
> > mount -t 9P -o proto=3Dtcp 192.168.0.1 /mnt/9
> > and it always says connection refused.
> > I also tried exportfs and the mount command still refused. However when
> > I tried to do 9fs 192.168.0.1 on the cpu server it worked fine.
>
> Make sure fossil is indeed listening on for network connections.
> fossilcons(8) should have the details.
>
>