On Sat, Sep 04, 2004 at 11:04:22AM -0400, Andy Stewart wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi everybody,
While I happen to use CUPS, I'd like to note that there is at least one other person who had an unhappy first experience. Eric Raymond documents his experience here: http://www.catb.org/~esr/writings/cups-horror.html
Even though I do have a couple of disagreements with his various points, it was a very good article and probably doubly helpful in that it allows people to admit that they are having trouble with something (If ESR can't get it to work, why would they be afraid to admit it? His followup article mentions this effect a bit.).
Perhaps Chapter 3 of "The User's Guide to the Gimp-Print Top Quality Printer Drivers" (authored by yours truly) would be of help in configuring CUPS for a very basic installation. This document is available here: http://gimp-print.sourceforge.net/users-guide.pdf
Admittedly, this doesn't cover the "login" window presented by the CUPS interface. After searching the web for some time, I can't find the documentation which describes how to setup accounts which give users permission to modify certain aspects of CUPS. It must be somewhere on the CUPS website.
The CUPS website FAQ had a reference that I stumbled across while looking something up for my response earlier. (http://cups.org/faq.php?16)
When I first configured CUPS, I couldn't for the life of me figure out whether to use http, IPP, or otherwise, in describing my printer, and there was no guidance to help determine the proper choice. The CUPS admin web page asking for "device URI" confounded me for quite some time. I found the examples on that web page unhelpful.
Now that I have it working, I am happy with it, but admittedly it was rather frustrating to do the first time. In my opinion, the web interface should be so simple that I don't *need* to read the manual - at least for a very basic installation.
Later,
Andy <SNIP>
I think this is where the CUPS web interface does begin to fall down. They have a lot of documentation elsewhere and you end up having to read a large portion of it to be able to configure things using the web interface. Frank