[cups.general] Two issues: one annoying, one confusing

[Rob Tanner]

On 01/31/2006 08:57 PM, Michael Sweet wrote:
> Rob Tanner wrote:
>> Michael Sweet said the following on 01/31/2006 01:09 PM:
>>
>>> Rob Tanner wrote:
>>>
>>>> 2.  I'm running the version of CUPS (v1.1.23) that comes bundled 
>>>> with Fedora Core and I'm using the system-config-printer command 
>>>> and the GUI it brings up to add new printers, setup the drivers, 
>>>> etc.  Whenever I do that, I loose the ability to access the web 
>>>> interface from my workstation and in order to get access back, I 
>>>> have to manually edit the cupsd.conf file and add back in a Listen 
>>>> <hostname>:631 option so it can be accessed by other than localhost 
>>>> (no, I do not delete the Listen 127.0.01:631 line).  What do I do 
>>>> to keep that from happening all the time.
>>>
>>>
>>> Don't use system-config-printer, but instead use the web interface
>>> to add your printers.
>>>
>> But using the web interface means I don't have access to the drivers 
>> tailored for the printer model (the web interface gives you only 3 
>> CUPS choices as opposed to printer model specif foomatic drivers).  
>> Doesn't that constitute something of a downside to using the web 
>> interface to add new printers?
>
> Only on Red Hat, where they don't ship printer-specific PPDs but
> instead generate PPDs from a Foomatic XML database, so you're really
> not getting the right/best driver for a printer (and if you follow
> this group, you'll see a LOT of problems that people are having with
> this setup...)
>

I certainly admit to being new to CUPS and playing with the details of 
drivers in general.  This is my first time building a large-scale 
printer server that will also be providing printing (and cost 
charge-back) to PCs and MACs.  So, I'm spending most of my time lately 
in areas that are new to me.  I also noticed that on an HP8000, just 
printing a text file the quality of the CUPS driver was really poor.  
Brady Adams also pointed out that I can add driver to 
/usr/share/cups/model and then access them while still using the web 
interface.  That means I can download the model specific drivers from 
foomatic and still use the web interface -- I think that's called my 
cake and eat it to, and I'm very pleased with that. 

And my next trick will getting accsnmp (a backend wrapper) to work right.

Thanks,
Rob