From owner-freebsd-questions@FreeBSD.ORG Fri Oct 28 18:12:24 2011 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 E4107106564A for ; Fri, 28 Oct 2011 18:12:24 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) by mx1.freebsd.org (Postfix) with ESMTP id A78BE8FC15 for ; Fri, 28 Oct 2011 18:12:24 +0000 (UTC) Received: from r56.edvax.de (port-92-195-104-16.dynamic.qsc.de [92.195.104.16]) by mx01.qsc.de (Postfix) with ESMTP id E631C3D083; Fri, 28 Oct 2011 20:12:20 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id p9SICKPs001919; Fri, 28 Oct 2011 20:12:20 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Fri, 28 Oct 2011 20:12:20 +0200 From: Polytropon To: Warren Block Message-Id: <20111028201220.90a63627.freebsd@edvax.de> In-Reply-To: References: <23575.1319749979@tristatelogic.com> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org, "Ronald F. Guilmette" Subject: Re: Fast personal printing _without_ CUPS X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2011 18:12:25 -0000 On Fri, 28 Oct 2011 00:53:44 -0600 (MDT), Warren Block wrote: > A better example would be a web browser or word processor. The program > stops responding to further input until the printer has received the > entire print job. This bothered people enough that they came up with > lpd/lpr, which is part of the base FreeBSD system and works well. It's > been around long enough for problems to have been worked out. Furthermore, this system's mechanism allows the use of "user plugins", i. e. custom printer filters that talk to the device directly. This means that as soon as the printer spooler has received the data from the application program, any delays just happen to the processing and transmitting job (to the printer), not to the originating program. For example, I've written a simple "search & replace filter" to send data directly to the parallel port where a daisywheel printer is attached. It's easy to combine this with the system's tools lpr / lpd / lpq / lprm, in combination with the /etc/printcap file and a shell script. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...