Daniel Pielmeier <billie <at> gentoo.org> writes:
> You don't need avahi or zeroconf for hplip, which does not work for current
> versions of hplip due to bugs in cups anyway. This is only needed if you have
> a
> networked printer. You can still detect the printer without the mDNS
> (avahi,zeroconf) method through SLP. You should be able to select the
> detection
> method at run time with hp-setup.
hplip and cups are working fine together. Here are my flags
(for now) that are working fine:
net-print/cups-1.4.2-r1 USE="X acl dbus java jpeg ldap pam
perl php png python slp ssl tiff
net-print/hplip-3.9.12-r1 USE="gtk hpcups qt4 scanner snmp
Agreed. My printers all have ethernet; work off of the socket.
However, the printer supports mDNS (from the embedded web server)
"
Enable mDNS
This specifies the mDNS service name assigned to the device. This name
is a
string that can consist of any UTF-8 characters and can be up to 63 bytes in
length. (If ASCII characters are used, the name can be up to 63 characters long,
but if other characters are used, the name might be shorter.) This name is
persistent and is used to resolve a particular device if socket information
(such as the IP address) changes from session to session. Apple Bonjour uses
this service. The default service name is the printer model and the LAN Hardware
(MAC) address.
mDNS Service Name: "
My experience is embedded software development companies are all
over "zeroconf".
Open source folks are all about avahi.
Most are confused, but not on this list, folks did a good job
of fleshing out the minutia.....
The whole zeroconf thing is very similar to the functions of
snmp, just extended and repackaged, methinks.
The printer is very cool.....
and less than $200 US at costco....
Thanks to all concerning zeroconf et all.
Thanks for the flags discussion.
Working great.
James
