> Network Device Discovery
> ------------------------
>
> Actual network device discovery will be handled by the HAL addon module
> named hald-addon-network-discovery. This module will be tied into the
> HAL device tree at /org/freedesktop/hal/devices/network_attached by
> configuration stored in a HAL configuration file,
> /etc/hal/fdi/policy/10osvendor/10-network-attached.fdi. At startup,
> this module will claim the org.freedesktop.Hal.Device.NetworkDiscovery
All these names (as well as the SMF method) don't include "printer" in
them. Does this mean that they're more generic than that? It seems like
that might be the case from some of the rest of your material, but it's not
entirely clear to me.
How is this expected to be used in an environment like Sun's, where network
printers are managed by an IT department and added to the NIS maps?
Along the same lines, should this project be discovering new printers from
the NIS map, too (or should there be a project to do so)?
> HAL device tree at /org/freedesktop/hal/devices/network_attached/{addr}.
Your example gives {addr} as being an IPv4 dotted quad, replacing the dots
with underscores. Is there any reason to believe that IPv6 devices would
be discovered and placed here? Is there any sense of a uuid that might
enable the system to recognize when a printer changes its IP address
(presumably some use DHCP)?
Danek
