hal-resmgr is used as callout from hald and resmgrd to install ACLs
on device files.

Devices that should be processed by hal-resmgr need to be tagged.
The fdi file resmgr.fdi (installed as
/usr/share/hal/fdi/policy/10osvendor/80-resmgr.fdi) does that by
merging resmgr specific properties into hal.

The following properties are supported:

- resmgr.class (string): the resmgr class the device should added to
- resmgr.flags (strlist): list of flags (see add command in resmgr(1))
- resmgr.device (string): the path to the device node that should be
  used. If it's empty the properties block.device, linux.device_file
  and usbraw.device are checked in that order instead.

To make hald actually run hal-resmgr one needs to add hal-resmgr to
the strlist properties info.callouts.add and info.callouts.remove.
/etc/hal/fdi/policy/90osvendor/80-resmgr.fdi does that automatically
for all devices that have resmgr.class set.

EXAMPLE:
To tell hal-resmgr that a device with vendor id 0x1234 and product
id 0x5678 should be treated as class scanner, create a file
/etc/hal/fdi/policy/20user/50-scanner.fdi with the following
content:

<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
  <device>
    <match key="info.category" string="usbraw">
      <match key="@info.parent:usb_device.vendor_id" int="0x1234">
        <match key="@info.parent:usb_device.product_id" int="0x5678">
          <merge key="resmgr.class" type="string">scanner</merge>
        </match>
      </match>
    </match>
  </device>
</deviceinfo>
