From: Philip Guenther guenther@stolaf.edu
Subject: bind vs pwd
Date: Wed, 16 Nov 1994 17:47:26 -0500 [thread overview]
Message-ID: <19941116224726.q_Wo6-YDdC9qeP_NfUxngvDGPnwr4VVoNLGujiIKoLk@z> (raw)
>Given bind -c /usr/$user/tmp /tmp
>if I cd to /usr/$user/tmp and then cd .., pwd says that I'm now in /.
>I expected to be in /usr/$user. Is that how it's supposed to work,
>or am I all confused about something?
bind is not like ln -s. The bind command shown above makes /tmp into
a union directory, containing the union of the previous contents of /tmp
(probably nothing in this case), and the contents of /usr/$user/tmp.
In addition, the -c flag specifies that files created in /tmp should
*really* be created in /usr/$user/tmp. This is critical here as /tmp
is unwritable previous to this.
However, /tmp is still /tmp. It's contents are really somewhere else,
but as far as the shell is concerned, nothing has happened. The kernel
may catch readdir() a lie a little, but cd is unaffected.
I think you may be able to "trick" it with something like:
bind -c /usr/tor/tmp /tmp
mkdir /tmp/foo
cd /tmp/foo
cd ..
I think that will leave you in /usr/tor, as the cd takes you to
/usr/tor/tmp/foo. At least that's what it appears to me...
Philip Guenther
guenther@stolaf.edu (Philip Guenther) St Olaf College, Northfield, MN 55057
(defun sig-hook () (insert-disclaimer 'my-opinion-only 'powerless-student))
"To go outside the mythos is to become insane..." -Robert Pirsig
next reply other threads:[~1994-11-16 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-11-16 22:47 Philip [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-11-17 19:35 Scott
1994-11-17 2:05 philw
1994-11-17 1:21 philw
1994-11-16 22:02 Scott
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=19941116224726.q_Wo6-YDdC9qeP_NfUxngvDGPnwr4VVoNLGujiIKoLk@z \
--to=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).