9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Francisco J Ballesteros" <nemo@lsub.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Re: Re: Re: [9fans] Aquarela usage
Date: Tue,  5 Sep 2006 23:03:07 +0200	[thread overview]
Message-ID: <8ccc8ba40609051403x657fc309r8c6a3108c86095f3@mail.gmail.com> (raw)
In-Reply-To: <676c3c4f0609051353l56b7c49en774533c5367ef8a4@mail.gmail.com>

anyone actually exporting nfs from plan 9 to linux?
Or are you all using the linux 9p implementation?

thanks

On 9/5/06, Richard Bilson <rcbilson@gmail.com> wrote:
> On 9/5/06, David Leimbach <leimy2k@gmail.com> wrote:
> > On 9/5/06, Richard Bilson <rcbilson@gmail.com> wrote:
> > > I've never had to add any special keys in order to access an aquarela
> > > share from a Windows machine -- I can connect to the share using the
> > > same password I use for drawterm.
> > >
> >
> > I've been trying that, drawterm works, aquarela isn't working.
> >
> > > I have also never had a need for aquarela's -n flag.
> > >
> >
> > I'm trying to connect to the local filesystem using \\ip\local or
> > smb://<ip>/local.
> >
> > So far no luck.  Do I have to do something special to /n in the
> > namespace I launch aquarela in?
> >
> > Dave
>
> If your problem is authentication, no. But if your credentials are
> accepted, my message from July 18th might be relevant:
>
> > On 7/14/06, Richard Bilson <rcbilson@gmail.com> wrote:
> > >
> > > I assume that "\\host\local" is supposed to refer to some namespace
> > > constructed for the authenticated user. Probably it should contain
> > > files and such. How do I achieve this?
> >
> > Ok, I figured this out. "\\host\local" refers to "/n/local". But, by
> > default, there is nothing mounted at or bound to /n/local. Putting
> > "bind / /n/local" into /lib/namespace.local gives me the behavior I
> > expected.
>
> I was going to find somewhere in the wiki to put this, but I'm still
> not completely sure that this is the way it's meant to work. Of
> course, it's nice and flexible in the sense that you can create a
> custom namespace for use by smb clients, but it ought to be
> documented.
>
> One way to make sure that the authentication is working is to browse
> \\host\sources or \\host\dump, or another share name corresponding to
> a 9fs argument.
>
>


  reply	other threads:[~2006-09-05 21:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-05 18:41 David Leimbach
2006-09-05 18:59 ` Richard Miller
2006-09-05 19:46   ` David Leimbach
2006-09-05 20:05     ` Richard Miller
2006-09-05 20:29       ` David Leimbach
2006-09-05 20:38         ` Richard Bilson
2006-09-05 20:41           ` David Leimbach
2006-09-05 20:53             ` Richard Bilson
2006-09-05 21:03               ` Francisco J Ballesteros [this message]
2006-09-06 20:33                 ` geoff
2006-09-06 20:44                 ` Tim Wiess
2006-09-05 21:17             ` Re: Re: " Richard Miller
2006-09-05 21:36               ` David Leimbach
2006-09-06  0:06                 ` arisawa
2006-09-06  0:10                   ` David Leimbach
2006-09-06  1:07                     ` erik quanstrom
2006-09-06  2:31                       ` Anthony Sorace
2006-09-06 13:53                       ` David Leimbach

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=8ccc8ba40609051403x657fc309r8c6a3108c86095f3@mail.gmail.com \
    --to=nemo@lsub.org \
    --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).