From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Fabian Sturm Subject: Multiple lower layers - presedence? Date: Mon, 05 Jan 2015 02:00:53 +0100 Message-ID: <1997646.dsfVWM3xr5@debian-desktop-mine> Content-Type: multipart/alternative; boundary="nextPart1490347.URqbfjAPgT" Content-Transfer-Encoding: 7Bit To: linux-unionfs@vger.kernel.org Cc: miklos@szeredi.hu List-ID: This is a multi-part message in MIME format. --nextPart1490347.URqbfjAPgT Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" The current documentation states the following: Multiple lower layers --------------------- Multiple lower layers can now be given using the the colon (":") as a separator character between the directory names. For example: mount -t overlay overlay -olowerdir=/lower1:/lower2:/lower3 /merged As the example shows, "upperdir=" and "workdir=" may be omitted. In that case the overlay will be read-only. Consider the case /lower1/A and /lower2/A exist. What is part of the api - that it is undefined or that one takes presedence over the other? It would be nice to have this clarified in the documentation. Thanks, Fabian --nextPart1490347.URqbfjAPgT Content-Transfer-Encoding: 7Bit Content-Type: text/html; charset="us-ascii" 
The current documentation states the following:

Multiple lower layers
---------------------

Multiple lower layers can now be given using the the colon (":") as a
separator character between the directory names.  For example:

  mount -t overlay overlay -olowerdir=/lower1:/lower2:/lower3 /merged

As the example shows, "upperdir=" and "workdir=" may be omitted.  In that case
the overlay will be read-only.

Consider the case /lower1/A and /lower2/A exist.
What is part of the api - that it is undefined or that one takes presedence over the other?
It would be nice to have this clarified in the documentation.

Thanks,
Fabian
--nextPart1490347.URqbfjAPgT--