From: "Brad Frank" <brad.frank@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] Explanation of binding from ftpfs
Date: Sat, 6 Dec 2008 15:44:29 -0500 [thread overview]
Message-ID: <cca2e5880812061244m4ea907e5v81b8c4ca2c397b75@mail.gmail.com> (raw)
When I use ftpfs to mount a ftp site and then bind /n/ftp to another
location. All appears to work fine in /n/ftp and in the other
location. When I type ns, I can clearly see the pipe bind for ftpfs
mounted to /n/ftp. When I unmount /n/ftp I can type ls on /n/ftp and
not see anything there. But if I ls on the other location that I bound
to /n/ftp, it still can access the ftp server. How is the other
location able to do this, when I don't see any indication of a pipe
bind still listed in ns? I do see the ftpfs process running, though.
next reply other threads:[~2008-12-06 20:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 20:44 Brad Frank [this message]
2008-12-06 21:39 ` Iruata Souza
2008-12-06 22:17 ` Brad Frank
2008-12-06 22:27 ` Iruata Souza
2008-12-06 22:39 ` erik quanstrom
2008-12-06 22:52 ` Brad Frank
2008-12-06 22:53 ` Brad Frank
2008-12-06 23:06 ` Russ Cox
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=cca2e5880812061244m4ea907e5v81b8c4ca2c397b75@mail.gmail.com \
--to=brad.frank@gmail.com \
--cc=9fans@9fans.net \
/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).