On Tue, Sep 04, 2007 at 02:12:18PM -0500, Norm Jacobs wrote:
> Danek Duvall wrote:
>> 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.
Okay.
>> 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.
Is that "we" the printing folks or the more general set of people working
on HAL? I don't think I'd expect the printing folks to have any plans like
that. :)
> 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
Okay. My only question here, then, is whether the migration from the
proposed FMRI and authorization strings to these potential future ones is
painless. Can both FMRIs exist on a system at the same time? I can't
think of too many network devices at the moment -- only scanners come to
mind (would storage fall in this category?) -- so maybe it's okay not to
prepare for them immediately.
Danek
