From owner-freebsd-questions@FreeBSD.ORG Fri Oct 24 06:59:10 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D24B510656A1 for ; Fri, 24 Oct 2008 06:59:10 +0000 (UTC) (envelope-from mapsware@prodigy.net.mx) Received: from nlpiport17.prodigy.net.mx (nlpiport17.prodigy.net.mx [148.235.52.22]) by mx1.freebsd.org (Postfix) with ESMTP id 9B3308FC24 for ; Fri, 24 Oct 2008 06:59:10 +0000 (UTC) (envelope-from mapsware@prodigy.net.mx) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ai44ABMPAUm9pTkhPGdsb2JhbACBdpF3AQEBATUBrVuDUA X-IronPort-AV: E=Sophos;i="4.33,476,1220245200"; d="scan'208";a="139787728" Received: from nlpiport05.prodigy.net.mx (HELO nlpiport19.prodigy.net.mx) ([148.235.52.84]) by nlpiport17.prodigy.net.mx with ESMTP; 24 Oct 2008 01:58:56 -0500 Received: from dsl-189-165-57-33.prod-infinitum.com.mx (HELO morena.maps.mx) ([189.165.57.33]) by nlpiport19.prodigy.net.mx with ESMTP; 24 Oct 2008 01:58:56 -0500 From: Martin Alejandro Paredes Sanchez To: freebsd-questions@freebsd.org Date: Thu, 23 Oct 2008 23:59:08 -0700 User-Agent: KMail/1.9.10 References: <101620082036.391.48F7A5DA0009DFCD0000018722120207849C05020E089F060E@comcast.net> <200810232142.41941.mapsware@prodigy.net.mx> <20081024052257.GA5231@icarus.home.lan> In-Reply-To: <20081024052257.GA5231@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200810232359.08739.mapsware@prodigy.net.mx> Subject: Re: Printing to a Lanier LD160c does not work X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Oct 2008 06:59:10 -0000 El Jue 23 Oct 2008, Jeremy Chadwick escribi=F3: > On Thu, Oct 23, 2008 at 09:42:41PM -0700, Martin Alejandro Paredes Sanche= z=20 wrote: > > El Jue 16 Oct 2008, Jeremy Chadwick escribi=F3: > > > > > > If this printer is hooked up on the network (e.g. via Ethernet), I > > > believe you need to set the lp variable to the hostname or IP address > > > of the printer, e.g.: > > > > > > admincolor|hp|laserjet|LANIER LD160c RPCS:\ > > > > > > =A0=A0=A0=A0=A0=A0:lp=3D192.168.1.100\ > > > =A0=A0=A0=A0=A0=A0:sd=3D/var/spool/output/admincolor:rm=3Dadmincolor:\ > > > =A0=A0=A0=A0=A0=A0:lf=3D/var/log/lpd-errs: > > > > Negative, leave the lp capability blank, explicitly (:lp=3D:). > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/printing-adva= nc > >ed.html#PRINTING-ADVANCED-NETWORK-RM > > Then the printcap(5) man page should reflect this; the existing > explanations for both fields are painfully terse. > > lp str /dev/lp device name to open for > output, or port@machine to > open a TCP socket > rm str NULL machine name for remote > printer > > I can file a PR (to doc) on this if recommended. if you are printing to a remote LPD system, you should use: :lp=3D:\ :rm=3Dhostname-or-ip:\ :rp=3Dprinter-name:\ If you use lp=3Dport@machine, then you should not use rp and rm, but in the= port=20 of the machine should be a program that undestand LPD/LPR protocol. The printcap(5) man page has a section "REMOTE PRINTING". maps