-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, Aug 30, 2015 at 03:07:44PM +0100, Brian wrote: > On Sun 30 Aug 2015 at 09:31:50 +0200, to...@tuxteam.de wrote: > > > On Sat, Aug 29, 2015 at 11:00:51PM +0100, Brian wrote: > > > > [...] > > > > > None of these. Bonjour plays a central role in printing over a network. > > > Discarding it as a very useful tool isn't very helpful. > > > > It aids in printer discovery. If your configuration is somewhat static, > > it's totally superfluous. In a highly dynamic environment it's convenient. > > The distinction between static and dynamic is a useful one when it comes > to printing. With a policy of only printing to a local USB connected > printer or a designated server in client.conf the need for service > discovery with avahi-daemon is, as you say, superfluous. Whether it can > be removed depends on the system setup. On GNOME its purging will take > gnome-core with it. That doesn't look good. :), so disabling it looks a > better bet.
I remember something like that. Actually, my wrangling to get rid of Avahi, and the realization of how intertwined things had become was the first nail in Gnome's coffin (for me, that is!). A couple more nails, and I'm now Gnome-free. Farewell, it was nice while it lasted. Too complex, to many dependencies and too hard to debug [1] > In a dynamic environment (moving from site to site, for example) I'd see > the status of avahi-daemon as essential, not simply convenient [...] > > I know for sure: my printing runs perfectly fine without Avahi [...] > This is a static configuration equivalent to the CUPS one outlined > above. It has the same drawbacks. There is no reason why either setup > shouldn't produce a satisfactory printing experience. I believe LPRNG > cannot do service discovery so a roaming user may have the trouble of > needing to get a server name for every new situation. Correct. LPRNG doesn't service discovery. I do that discovery (e.g. I walk in the office to the copier-printer and look at the label slapped on it where its IP is printed on). I gladly do that discovery. > > Pick your tools. Know why. > > Indeed; but banning one of them reduces the possibilities of effortless > printing. "Banning" is a loaded word. I choose simplicity (and am ready to pay some price for it). I don't tell others to do likewise, I just offer help in making a choice. I can only ban it from my computer. - - - - - [1] A case in point: at home we have a postscript network printer. For one file, my SO's computer (a fresh Debian installation, with all the Mate and Cups goodnes isn't able to print one specific PDF. My box, with LPRNG and apsfilter does print it. The CUPS log files say that yes, everything is fine. I've the hunch that the printer's Postscript implementation is crappy, and the CUPS variant is sending some Postscript Level 2 the printer can't digest (it prints an error message instead of the wanted document, so it seems to be the interpreter in the printer freaking out). With LPRNG/apsfilter, I'd be able to debug the thing. With all this CUPS mess, I don't even know where to start. Ick. Regards - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlXjLx4ACgkQBcgs9XrR2kZTGgCfdLm6A73a718kWqyJx6HjiDR5 ZG4An2VHT4+16jfSPhQydfpvjFhUtTc7 =3vun -----END PGP SIGNATURE-----
