If you don't mind, I'd like to just post this feedback from our
conversation.â I didn't realize I had skipped the mailing list! Thank you!
[...]
James Stortz:
> Do you know if there's a way to do this and still keep the rw layer on the
> root fs itself?
Essentially, the layers cannot have the parent-child relationship on the
single fs. By using a loopback-mounted fs image file, you can. I guess
you will need to apply aufsN-loopback.patch.
# just to show the scenario (didn't test actually)
file=/rw-layper-image.ext2
truncate xxxMB $file
mkfs -t ext2 $file
mount -o loop $file /rw
mount -t aufs -o br:/rw:/ none /
J. R. Okajima
[...]
James Stortz:
> Or better yet, maybe there could be an "exclude" option or something of
the
> like. That would be really nice. Maybe I can write a patch. I just don't
> have the time right now to get into it I think.
Exclude?
I am not sure what you mean, but generally you can exclude something
by bind-mount.
# mount -t aufs -o br:/rw:/ro none /aufs
# mount -o bind /ro/dirA /aufs/dirA
# mount -o bind /rw/dirB /aufs/dirB
# mount -o bind /ro/fileA /aufs/fileA
    :::
All these dirA, dirB and fileA are provided directly from /ro and /rw.
Aufs doesn't provide them to users.
J. R. Okajima
On Thu, Jul 9, 2015 at 8:58 PM, <[1]sf...@users.sourceforge.net> wrote:
Hello James,
James Stortz:
> What is a standard method for mounting a rw layer over the top of my
root
> fs?
I'd suggest you check these as a first step.
- samples in aufs-util.git as well as the old aufs1 CVS tree on
 SourceForget.
- LiveCDs, SLAX, Knoppix and other distributinos.
J. R. Okajima
References
1. mailto:sf...@users.sourceforge.net
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
