----- "Julien BLACHE" <jbla...@debian.org> wrote:

> Package: acl
> Version: 2.2.49-3
> Severity: normal
> 
> Hi,
> 
> The ACL utilities currently reside in /usr/bin, meaning they can't be
> used
> during the early boot process when /usr is not guaranteed to be
> available.
> 
> I'm trying to fix a longstanding issue with multifunction devices
> (printer +
> scanner) and the fix is to use ACLs in udev rules. As udev's

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

> coldplugging
> happens very early during boot, I can't apply this fix until/unless
> the ACL utilities are moved to /bin.

Are you advocating moving all of: libacl.so, libattr.so, chacl,
getfacl, setfacl, attr, getfattr, and setfattr?

> Moreover, with the increased use of ACLs, I think it would be
> consistent to move the utilities to /bin alongside chown/chmod.

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
them?  Is "increased use" really a valid reason?  I had a look in
Debian Policy and couldn't find the section covering this stuff.

cheers.

-- 
Nathan



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to