9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Scott Schwartz schwartz@galapagos.cse.psu.edu
Subject: no need for cd
Date: Wed,  8 Mar 1995 19:09:34 -0500	[thread overview]
Message-ID: <19950309000934.DfaKaSierzw4YLNe9eG8CnzFSigMin4fVNNq1Emwt6A@z> (raw)

serge writes:
| (Didn't the Plan9 people say that mount entries are hashed,
| so that ".." can refer to arbitrary directories, depending on what
| you've mounted?  E.g. this won't change any semantics.)

Yes, they did.  I find the idea of ".." in a union mount directory
confusing.  It certainly breaks e.g. tar.  A nice file tree walk
library could at least encapsulate strategies for avoiding lossage,
but if your filesystem is not a tree, is having ubiquitous ".."
entries the right thing?  Maybe "set default prefix" is a better
abstraction.  [My plan 9 manpages are stored in an old VMS binder;
there must be leakage.:-)]






             reply	other threads:[~1995-03-09  0:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-03-09  0:09 Scott [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-03-11  1:06 serge
1995-03-09  8:18 David
1995-03-09  7:30 David
1995-03-09  4:49 rob
1995-03-08 21:27 serge

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=19950309000934.DfaKaSierzw4YLNe9eG8CnzFSigMin4fVNNq1Emwt6A@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).