From owner-freebsd-questions@FreeBSD.ORG Thu May 28 10:10:48 2009 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 4269C106566C for ; Thu, 28 May 2009 10:10:48 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [IPv6:2001:4070:101:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 8F67F8FC08 for ; Thu, 28 May 2009 10:10:47 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [IPv6:::1]) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3) with ESMTP id n4SAAXTG058984; Thu, 28 May 2009 12:10:33 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3/Submit) with ESMTP id n4SA9wb3058968; Thu, 28 May 2009 12:09:58 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Thu, 28 May 2009 12:09:57 +0200 (CEST) From: Wojciech Puchar To: Polytropon In-Reply-To: <20090528111158.aee9a44d.freebsd@edvax.de> Message-ID: References: <20061208042111.GA709@host.my.domain> <23685866.post@talk.nabble.com> <20090524104618.0a62a935@scorpio> <23711563.post@talk.nabble.com> <20090525154816.3cee4b9a@scorpio> <20090526144939.d21275c2.freebsd@edvax.de> <20090527133706.1a6e4612@scorpio> <20090528111158.aee9a44d.freebsd@edvax.de> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-questions@freebsd.org Subject: Re: Canon printer and TurboPrint 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: Thu, 28 May 2009 10:10:48 -0000 >> 2) The technology exists, as demonstrated by Microsoft, to easily >> configure a printer. > > It's because MICROS~1 are part of the system that builds the > concepts for the printers, and the printers itself. Because > of their monopoly positzion, they can say: "If you build a > printer, make drivers for our 'Windows', and it will sell > well. If you make drivers for FreeBSD, which doesn't exist, > then it won't sell." indeed. actually if printers would simply support standards like PCL or postscript and standard USB protocol it would not be need for ANY drivers both for windoze and FreeBSD. The problem is that most buyers are more happy when they get "added value" "for free" like tons of CD's Manufacturers do what market required, no matter how dumb it is. Those who didn't already failed. But again it wouldn't be that hard to make printer conforming to standard AND produce (click-generate) few gigs of add on software for windows. As windows user may get scared hearing the word "unix", even in context like "supports both windows and unix", they could sell the same printer as 2 products - printer for windows (bundled with this few gigs of addons) and printer for unix, bundled with 1 page instruction with an example how to make ghostscript filter and how to configure lpd. > included) doesn't make the situation better. I prefer the > system that FreeBSD uses: You install ONE (!) printer actually i never used things like cups, turboprint, whatever. i just run lpr to print postscript file, or print directly from programs through lpr > system that supports all (standard compliant) printers, > and you don't have to do any more work. On a system with There are lot of compliant second-hand printers for <100$. For example i have HP LaserJet 4, which printed 85000 pages when i bought it, and i printed over 15000. And it works flawlessy, so i don't have new printer every year. >> Having to perform Herculean tasks, load extra >> software; i.e. cups for instance, etc is not productive. > > CUPS isn't extra software in my opinions. Printer drivers are. exactly. it's not needed for printing. In unix many many years ago printing subsystem was already written. it's called lpd, and it has support for filters that can be considered "drivers". >> 4) My time is valuable. I don't feel like wasting it trying to get a >> printer to work correctly when it is easier to do on a Win32 box. It >> is not time well spent. assuming someone has windows box handy. one more computer just to print doesn't make much sense :)