From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] useful replica messages
Date: Fri, 7 Mar 2003 15:10:08 -0500 [thread overview]
Message-ID: <Pine.LNX.4.30.0303071503230.8127-100000@athena> (raw)
In-Reply-To: <200303071958.h27JwrG23251@augusta.math.psu.edu>
Hrm - ok, then I'm not totally confused.
man 1 bind | sed -n '/ -c/,/^$/p'
states that the creation lands in the union
directory bound with a -c. Russ's suggested
trick gives me the effect I was after, but
feels kinda shifty. What benefit do we
get from specifying this mechanism this way?
Sam
On Fri, 7 Mar 2003, Dan Cross wrote:
> > I suppose I incorrectly presumed I could
> > -a and expect creations to land in $home/replica.
> > Is there no mechanism for this, and/or is the
> > expected usage supposed to be the reverse;
> > that I'ld go to /sys/src/cmd/replica and
> > bind -bc $home/replica?
>
> No, you were correct in your assumption. You just forgot the ``-c''
> option to bind to allow creation in the new union directory.
>
> - Dan C.
>
next prev parent reply other threads:[~2003-03-07 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 19:23 Sam
2003-03-07 19:45 ` Dan Cross
2003-03-07 19:56 ` Sam
2003-03-07 19:58 ` Dan Cross
2003-03-07 20:10 ` Sam [this message]
2003-03-07 20:00 ` 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.0303071503230.8127-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).