From mboxrd@z Thu Jan  1 00:00:00 1970
From: Richard C Bilson <rcbilson@plg2.math.uwaterloo.ca>
Message-Id: <200307171730.NAA16848@plg2.math.uwaterloo.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bind -c[ab] -- what am I doing wrong?
Date: Thu, 17 Jul 2003 13:30:54 -0400
Topicbox-Message-UUID: fa440614-eacb-11e9-9e20-41e7f4b1d025

> From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
>
> given the man page i expect 'bind -ac new /something/i/can/write/to' to
> allow me to continue to write to '/something/i/can/write/to'.

Here's my guess.  To quote bind(1):

	When a new file is created in a union directory, it is placed
	in the first element of the union that has been bound or
	mounted with the -c flag. If that directory does not have write
	permission, the create fails.

In your example, you're creating a new union directory by binding "new"
with the -c flag.  The union has two directories, and only "new" has
been bound with -c.  If you don't have write permission to "new", the
create will fail.

One might expect some other result in the case where the second
argument is not already a union directory, but then again one might
expect the current behavior.