From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bind -c
Date: Fri, 7 Mar 2003 16:07:18 -0500 [thread overview]
Message-ID: <38f6304f0448ab7a2c49acc0d6293169@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0303071558540.8127-100000@athena>
> Why shouldn't this work?
> term% mkdir replica; cd replica
> term% bind -c . .
> term% bind -a /sys/src/cmd/replica .
> term% cp mkfile . #obtain a local copy
> cp: mkfile and mkfile are the same file
Because the first thing cp does is basically
ls -lq mkfile ./mkfile
and discovers that the source and destination
are the same. Binding with -c only changes
where _new_ files are created. When you create()
an existing file that directory entry is used.
In this case it's probably significantly easier just to
mkdir replica
cp /sys/src/cmd/replica/* replica
and not worry about union directories.
What I usually do for things like this is:
cd /sys/src/cmd/replica
bind -bc $home/replica .
and then
cp mkfile $home/replica
etc.
to make copies of the files I want to change.
Russ
next prev parent reply other threads:[~2003-03-07 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 21:02 Sam
2003-03-07 21:07 ` Russ Cox [this message]
2003-03-08 13:22 Keith Nash
2003-03-08 20:12 ` Sam
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=38f6304f0448ab7a2c49acc0d6293169@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).