Peter, it seems the issue you have is with FUSE-Unionfs. This mailing list is for the older in-kernel stackable file system module called “Unionfs.”.
Erez. > On Jul 11, 2016, at 11:40 AM, Peter Maloney > <[email protected]> wrote: > > root@peter:~/tmp/unionfs # mkdir root root.rw > root@peter:~/tmp/unionfs # unionfs -o allow_root -o dirs=/=RO:root.rw=RW > root > root@peter:~/tmp/unionfs # ls root > boot/ dev/ fs1/ home/ media/ opt/ root/ srv/ usr/ > bin@ ... > root@peter:~/tmp/unionfs # touch root/testfile > touch: cannot touch 'root/testfile': Permission denied > root@peter:~/tmp/unionfs # mount | grep union > unionfs on /root/tmp/unionfs/root type fuse.unionfs > (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other) > root@peter:~/tmp/unionfs # umount root > > it mounts with allow_other, not allow_root. > All I want to do is run potentially destructive commands in a chroot (in > this case "make install" and "make uninstall"), and then look in root.rw > to see what was changed, and not have to copy my whole fs to do it. It > has to modify directories like /usr/lib64/ and /lib/modules/ so I need root. > > $ unionfs --version > unionfs-fuse version: 1.0 > (compiled with xattr support) > FUSE library version: 2.9.6 > fusermount version: 2.9.6 > using FUSE kernel interface version 7.19 > > I am not on the list, so please CC me. > > Thanks, > Peter > _______________________________________________ > unionfs mailing list: http://unionfs.filesystems.org/ > [email protected] > http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs > _______________________________________________ unionfs mailing list: http://unionfs.filesystems.org/ [email protected] http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
