Till Kamppeter wrote on 2007-12-18:
Yes, in Hardy we have full DNS-SD support. I have written a simple DNS-SD backend for CUPS based on avahi-browse, so that CUPS discovers network printers and DNS-SD-only broadcasted CUPS queues (for example from Mac OS X boxes) via DNS-SD. system-config-printer distinguishes between network printers and CUPS queues discovered via DNS-SD and in case of CUPS queues it does not assign a driver so that the driver from the server gets used. On the server side CUPS 1.3 broadcasts the local printers via DNS-SD and so Mac clients will find them.
This bug is a regression from Hardy, as per https:/ /bugs.launchpad .net/ubuntu/ +source/ cupsys/ +bug/50230, #8:
Till Kamppeter wrote on 2007-12-18: config- printer distinguishes between network printers and CUPS queues discovered via DNS-SD and in case of CUPS queues it does not assign a driver so that the driver from the server gets used. On the server side CUPS 1.3 broadcasts the local printers via DNS-SD and so Mac clients will find them.
Yes, in Hardy we have full DNS-SD support. I have written a simple DNS-SD backend for CUPS based on avahi-browse, so that CUPS discovers network printers and DNS-SD-only broadcasted CUPS queues (for example from Mac OS X boxes) via DNS-SD. system-