From: Scott Schwartz schwartz@galapagos.cse.psu.edu
Subject: bind vs pwd
Date: Thu, 17 Nov 1994 14:35:45 -0500 [thread overview]
Message-ID: <19941117193545.v6j1ECdxX5aT92k2HR_6swNLzVAmoN2NzZzM9HGDuhc@z> (raw)
Phil writes:
| pwd may give either answer. there is no way of remembering how you
| got somewhere because the mount table is stored by a hash. So '..'
| searches through the table and gives you the first answer.
I was caught by this when I tried to tar up my home directory and my
bin and tmp both sent tar rampaging through the filesystem. This is
even trickier than symbolic links.
next reply other threads:[~1994-11-17 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-11-17 19:35 Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-11-17 2:05 philw
1994-11-17 1:21 philw
1994-11-16 22:47 Philip
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=19941117193545.v6j1ECdxX5aT92k2HR_6swNLzVAmoN2NzZzM9HGDuhc@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).