Artem Kachitchkine writes: > In order to better support these devices, this case seeks to extend the > current HAL offering by adding a network attached device discovery > service addon module and a probe module to probe network attached > printers for identifying data. These modules will be connected to HAL > via .fdi files.
Just to clarify: we're only discovering printers on the network. If we have a printer (attached via some other method, such as USB), we won't be advertising that device to others, right? > Since virtually all network attached printers (or attachment devices) > seem to support SNMP v1, the initial implementation will support an > SNMP_GET broadcast mechanism for device discovery. The SNMP discovery > method will use the following SMF service instance/properties, and > D-BUS methods/arguments I didn't see a reference here to RFC 1759 or 3805. Will this project use any of the standardized Printer MIB interfaces, or does it only support the enumerated vendor MIB entries and Host Resources? What about Avahi? > svc:/network/device-discovery:snmp org.freedesktop.Hal.Device. Enabled or disabled by default? And under what system profile? > interval specifies the number of seconds to wait between active SNMP > scans. community specifies the SNMP community string to use in > SNMP_GET requests. network specifies the network broadcast address to > use in the SNMP_GET request. What's the default for config/network? Why does that need to be specified anyway? You should be able to use SIOCGIF* ioctls to get every bit of information needed to perform broadcast-based queries. > libnetsnmp Stable Core SNMP library Nit: should be Committed. > PSARC/2006/467 Printers Devfs Events How is this related to devfs? (Is it just because of the reference to USB printers, or is there something deeper here?) -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
