nath...@aconex.com wrote: Hi,
> Have you considered using the device cgroup to address this issue? > If so, what happened there - did it not work? That would seem to > be able to address this (maybe?) and could be done with use of the > existing /bin tools (mkdir/echo). > > Docs are: linux/Documentation/cgroups/devices.txt This looks like a nightmare both for me as upstream/maintainer and the users, which makes it even more of a nightmare for me :) > Are you advocating moving all of: libacl.so, libattr.so, chacl, > getfacl, setfacl, attr, getfattr, and setfattr? I'm just interested in the *acl binaries right now. > I'm not sure what the rules are for putting additional binaries and > shared libraries out of usr into the root are - can you point me to Libraries are already there, as you've noted in your second mail :) > them? Is "increased use" really a valid reason? I had a look in > Debian Policy and couldn't find the section covering this stuff. I'm not sure there are any rules covering this, besides the common sense stuff like "raise it on -devel, if nobody objects, go ahead" which I just did :-) JB. -- Julien BLACHE <jbla...@debian.org> | Debian, because code matters more Debian & GNU/Linux Developer | <http://www.debian.org> Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
