On Sunday, 10 April 2022 02:33:21 EDT to...@tuxteam.de wrote: > On Sat, Apr 09, 2022 at 08:21:12PM -0400, The Wanderer wrote: > > [...] > > > I honestly don't know the subject very well myself, but I'd > > definitely > > like to know it better than I do. > > > > One aspect of Windows printer sharing is that it makes it possible to > > connect a printer not directly to the network, but locally to a > > particular computer, and then configure that computer to advertise > > the > > printer over the network. Other computers can then send jobs to that > > printer via that computer, which is de-facto a print server for that > > printer. > > > > Do you know whether CUPS is capable of interacting with printers > > which > > are shared in that way? (This is a tangent to the topic of the > > thread, > > but it fits this local context and it's a thing I'd be interested > > in.) > > If that local printer is known to CUPS and the local sysadmin has > marked it as shareable (however you do that in CUPS), that would, > as I have understood it, be Avahi's job, which is a service > (advertisement and) discovery protocol. Then why, after a decade and change of bitching about it because it insists on putting a 169.254.xx,yy address in ones routing table that only removing avahi fixes, has it not been fixed? You can spec the correct address other places such as in /etc/networking/interfaces.d/ anyfilename, or in the last two paragraphs of /etc/dhcpcd.conf, but if avahi is executable, it will override your settings and kill your networking setup dead in the water.
And what I mean is that removing it is done behind apt's back by hunting it down and rm-ing it. apt will not remove it w/o destroying the rest of the system. For those of us using hosts files for networking on our little home networks of less that say 16 machines, avahi is the first thing we hunt down and rm after the installers reboot. Only then can we spec a 192.168.xx.yy address to our local gateway and make it stick. Of note is that NOTHING else in the system considers a missing avahi as a loggable event. ONLY apt thinks it is valuable enough to cause its dependencies to destroy the system if you try to remove it with apt as the package manager. Which suits me just fine as its been a headache, looking for a problem that does not exist since it came on the scene. Here, at the coyote.den domain, it does not exist in executable form. Except to pull my trigger when someone recommends that broken concept utility for anything. This, FWIW, has nothing to do with cups and printer sharing, cups does its own advertising. All printers here are attached to this machine, marked as shareable and I can put stuff on their output trays from any machine including the rpi4 on my local network. The missing avahi has nothing to do with that. The only disadvantage is the long walk to retrieve the printout, but I probably needed the exercise anyway. > Cheers > -- > t Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
