Danek Duvall wrote:
> On Wed, Aug 29, 2007 at 04:19:46PM -0500, Norm Jacobs wrote:
>
>
>> The hald-addon-network-discovery module could be used to detect other types
>> of network attached devices, like scanners or storage, but it is
>> specifically looking for printers. The hald-probe-network-printer module
>> is tied to printers and only looks for printer specific data on the device
>> it's probing.
>>
>
> Okay. Isn't it strange, then, that you're assigning the Printer Management
> profile to the SMF service instances when those instances could be
> discovering things other than Printers?
>
Control of network attached device discovery requires the
solaris.smf.manage.discovery.snmp
solaris.smf.value.discovery.snmp
authorizations.
I added them to the "Printer Management" profile so that someone that
already has the ability to manage printing could also manage the
discovery of network attached printers.
> Would "Device Management" be more appropriate? Or would it be preferable
> to restructure the service so that the device types are the instance names,
> and the discovery protocols are properties on those instances? (Or
> something like that.)
>
The HAL addon, hald-addon-network-discovery, doesn't currently discovery
anything other than printers and we don't have plans to extend it to
look for anything else. I can envision a time when we might want to
update it to recognize more device types. If we were to break this down
to device-type and method, I would change the service name and
authorization as follows:
svc:/network/device-discovery/printers:snmp
solaris.smf.{manage|value}.discovery.printers.snmp
I would also change the D-BUS method names to
EnablePrinterScanningViaSNMP(), DisablePrinterScanningViaSNMP(), and
ScanForPrintersViaSNMP()
I don't see a great need to control this by device type in the future,
but it's a relatively minor change to make now.
-Norm
