From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] bind -c
Date: Sat, 8 Mar 2003 15:12:21 -0500 [thread overview]
Message-ID: <Pine.LNX.4.30.0303081459590.11009-100000@athena> (raw)
In-Reply-To: <20030308132205.1201.qmail@mail.dirac.net>
More useful might be a script rebind that
allows you to rebind a union'd directory D
with/without the creation bit by popping
off the ns elements after D then pushing
them back.
This is such a seldom done task that
I doubt it's really necessary, though. If
you've screwed up your namespace creation
order, wipe it and start over.
I didn't realize until yesterday just
how poorly I understood union dirs & -c.
It became much clearer when Russ commented
that one used to have to start a union
directory D with bind D D, which is now
implicit (before the first bind, presumably).
Sam
next prev parent reply other threads:[~2003-03-08 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-08 13:22 Keith Nash
2003-03-08 20:12 ` Sam [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-07 21:02 Sam
2003-03-07 21:07 ` 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=Pine.LNX.4.30.0303081459590.11009-100000@athena \
--to=sah@softcardsystems.com \
--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).