9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Fernan Bolando" <fernanbolando@mailc.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] v9fs and Russ tra
Date: Sun,  2 Apr 2006 03:35:56 +0800	[thread overview]
Message-ID: <1d5d51400604011135w53273453vd493784c2b61146d@mail.gmail.com> (raw)
In-Reply-To: <a4e6962a0604011044p34f6f49axa524bd24a0c60747@mail.gmail.com>

running listen tcp!*!564 and il!*!17008 did the trick with the
fossil not listening. Now I am getting "permission denied" so I guess
this is is what you meant by auth problems.

I can't seem to find any reference to 9p.mount even in google.


On 4/2/06, Eric Van Hensbergen <ericvh@gmail.com> wrote:
> 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åsdal" <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=tcp 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.
> >
> >
>


--
Public PGP/GnuPG key (http://www.fernski.com)
pub 1024D/3576CA71 2006-02-02 Fernan Bolando
Key fingerprint = FDFE C9A8 FFED C1A5 2F5C EFEB D595 AF1C 3576 CA71


  reply	other threads:[~2006-04-01 19:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-01  5:38 Fernan Bolando
2006-04-01 17:26 ` "Nils O. Selåsdal"
2006-04-01 18:44   ` Eric Van Hensbergen
2006-04-01 19:35     ` Fernan Bolando [this message]
2006-04-01 21:14       ` Russ Cox
2006-04-03  3:57         ` Jeff Sickel
2006-04-03 18:46           ` Ronald G Minnich
2006-04-03 19:10             ` Bakul Shah
2006-04-03 19:34               ` Ronald G Minnich
2006-04-04 17:31                 ` Tim Wiess
2006-04-04 17:44                   ` Tim Wiess
2006-04-05  2:16                     ` Ronald G Minnich
2006-04-05 16:20                       ` Tim Wiess
2006-04-02  2:46 ` Russ Cox
2006-04-02  3:16 erik quanstrom
2006-04-02  3:40 ` Russ Cox
2006-04-04  4:19 YAMANASHI Takeshi

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=1d5d51400604011135w53273453vd493784c2b61146d@mail.gmail.com \
    --to=fernanbolando@mailc.net \
    --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).