Date: Sun, 30 Sep 2018 16:49:07 +0200 From: Guido Falsi <mad@madpilot.net> To: Alexey Dokuchaev <danfe@FreeBSD.org> Cc: Cy Schubert <Cy.Schubert@cschubert.com>, Rene Ladan <rene@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r480950 - in head: . archivers archivers/freeze print print/apsfilter print/hpijs Message-ID: <f7abcb38-369d-f9d8-93e9-d1fdb77ac6aa@madpilot.net> In-Reply-To: <20180930142448.GA83081@FreeBSD.org> References: <201809301338.w8UDcNcu066031@slippy.cwsent.com> <c75b5646-23f9-475c-e8b3-194039eeae5b@madpilot.net> <20180930142448.GA83081@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/30/18 4:24 PM, Alexey Dokuchaev wrote: > On Sun, Sep 30, 2018 at 04:07:25PM +0200, Guido Falsi wrote: >> ... >> I'm using lpr/lpd at home for printing, and sharing a single printer. >> lpd is useful with windows machines too, since they can natively talk to >> an lpd server. So avoiding samba which is overly complicated for simple >> setups. > > Can you share your configs or add missing bits to the Handbook chapter[*]? > I remember I've tried to follow it while sharing an HP printer which lacks > post-XP drivers for Windows 7 users but got stumbled with somewhere. :-( My printer natively understands PostScript (under a different brand name, but it's the same language). Having a printer which understands postscript makes finding a driver for windows easy, any generic postscript driver will work. I did use a ghostscript filter in the past, I should have all bits saved somewhere(in subversion history at worst), I can mail something to you later. However I'll also try to have a look at the printing handbook chapter, if I can add anything to that. -- Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f7abcb38-369d-f9d8-93e9-d1fdb77ac6aa>