A couple of observations: A work-around I could use is to mount a small tmpfs, e.g. "mount -t tmpfs -o size=300k ext4 /dummy" and use that as the first (rw) entry. At least that would mount my share, and the actual shares would still be read-only, although a few mount-long changes would still be possible if I'm not careful that writes and deletes aren't done in /Archive.
I also noticed while trying out different sizes of dummy tmpfses to find the minimum size needed for aufs to mount successfully, that if the tmpfs rw target is too small, say 256k, the mount will fail (with the "wrong fs type, ..." message), but the target will be populated with ".wh..wh.aufs", ".wh..wh.orph/", and ".wh..wh.plnk/", and any attempt at unmounting it will fail with "target is busy", even though aufs never mounted... Not sure if that's helpful at all, just thought I'd let you know :) Cheers, Daniel ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net
