On Tue, 10 Aug 2010 02:25:17 +0000, T o n g wrote: > >> Here I'd suggest you another approach. > >> > >> mount -t aufs -o br:rw:ro_mid=ro+wh:ro_bot none u mount -t aufs -o > >> br:ro_mid:ro_bot none u2 aubrsync move u rw u2 umount u2 > > > > I am afraid that it won't be accumulative either. > > I don't understand what you want to say.
Ok, back to ground 0. Please refer to the following previous posts (that I gathered from different places): ,----- | >> . . . can the above aubrsync move be accumulative? | >> | >> I mean, if I move my modification down in shutdown script today, then I | >> wish that tomorrow I can move my new modification down in shutdown | >> script without affecting my today's changes. | > | > I guess so, as long as you don't specify the rsync option to remove the | > old contents of the lower branch. | | then I guess the script is not working as expected: | | umount /dev/shm/aumt/u | mount -t aufs -o br:./rw:./ro2=wh:./ro1 none ./u | | $ ls u/d? | . . . | | % aubrsync _move u rw/ ro1/ '--remove-source-files --exclude=.wh..wh.* | rw/ ro2' | : : : | | $ find ro2 | ro2 | ro2/d1 | ro2/d1/.wh.6 | ro2/d1/.wh.7 | | See, all the previous content have gone. `----- > If you are talking about whiteout, then try shwh as I wrote. No, I want to preserve previous changes after move -- so that one move won't wipe out my previous changes. -- Tong (remove underscore(s) to reply) http://xpt.sourceforge.net/techdocs/ http://xpt.sourceforge.net/tools/ ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
