Re: UID/GID support
Jeff Hanson: Users can't run chown because they are not root. How about writing a wrapper? Allow chown after some tests. - the target path is aufs, or /home/$USER in your case? - the target uid is $USER - etc The warpper may be implemented suid-ed, or customized /etc/sudoers. -- Another problem is that the CIFS mounts show up in Gnome/Nautilus as mounted volumes. Since these are ro mounts that only exist for the UID change they aren't useful to the user and just make a mess of the desktop and Nautilus places sidebar. The aufs mount point is what the user needs. You may want to try fuse, nfs or any other fs which has uid-mapping feature. After some considerations, I could understand why you want such feature in aufs. But as I wrote first, I don't think it is a feature of stackable filesystem. Aufs should follow and should not disturb the native behaviour of brach fs. J. R. Okajima -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb
Re: More complex recepies.
Oliver Schinagl: I'm guessing, if stor1/dirA and stor2/dirB and stor3/DirB would basically be such a solution then, right? if I write to /aufs/dirA it ends up on the one, if i write to /aufs/dirB it will end up on either. Correct? Yes, I think so. But the create= policy works when you newly _create_ something. It means it is _not_ applied when you _modify_ an existing file. And also you should read the Exceptions for Policies section in the aufs manual. J. R. Okajima -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb
aufs2.1 Monday release
o bugfix - possible bugfix, exclude the freeing file o news - mainline 2.6.38-rcN is still buggy. - SSH access to SourceForge is still denied and I cannot update the GIT tree. But updating the web page on sf.net was succeeded. J. R. Okajima -- - aufs2-2.6.git#aufs2.1-31 branch aufs: test bad inode in d_revalidate aufs: tiny, remove an unused variable aufs: possible bugfix, exclude the freeing file - aufs2-2.6.git#aufs2.1-32..aufs2.1-37 branch ditto - aufs2-2.6.git#aufs2.1 branch Addition to above, aufs: for 2.6.38-rcN, protect d_count - aufs2-standalone.git ditto - aufs2-util.git#aufs2.1 branch nothing -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb
