Hello shawn, shawn wilson: > However, I an issue - I don't know how to make rules for which fs gets > updated. I'm thinking everything needs to overlay at the same point, > so directory writes might go to one fs or another - I think the base > should generally be ro, but the automation config and the 'thin' image > will both update /etc and I need some way of saying "this file gets > updated on fs, this file gets updated on another, and this file goes > to both". And then as I 'strace -e trace=stat64' or whatever and see > what the process touches, I'm going to want to copy it from one fs to > the other (kinda the same issue). > > Is there some mechanism to do this?
Unforunately I don't fully understand what you want. Basically aufs has severaly policies to select among multiple RW branches and you can specify one of them at mount/remount time. See ".SH Policies to Select One among Multiple Writable Branches" in aufs manual for details. Do you want something like this? - /u = /rw2 + /rw1 + /ro0 - create a file /u/fileA - then both of /rw2/fileA and /rw1/fileA are created If so, aufs doesn't have such feature. But these features may help you. - "aubrsync" script in aufs-util.git - "aumvdown" command in aufs-util.git Hope this helps. J. R. Okajima ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems
