Datasheet

“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 297 — #323
i
i
i
i
i
i
i
i
13
Printer Operation
Upgrading CUPS The existing software packages and the existing con-
figuration files are replaced by the new software packages and their
default configuration files. All new features are immediately avail-
able, but the queues must be created from scratch. The new features
are described in detail in the following articles:
http://portal.suse.com/sdb/en/2004/03/jsmeix_print-
einrichten-91.html
http://portal.suse.com/sdb/en/2003/09/jsmeix_print-
einrichten-90.html
http://portal.suse.com/sdb/en/2003/03/jsmeix_print-
einrichten-82.html
http://portal.suse.com/sdb/en/2002/09/jsmeix_print-
einrichten-81.html
13.1.2 Migrating from LPRng and lpdfilter to CUPS
CUPS and the LPRng and lpdfilter system are fundamentally different.
In the case of CUPS, the configuration data for the queues is stored
in /etc/cups/printers.conf and /etc/cups/ppd/. /etc/
printcap is created by cupsd only for the purpose of compatibility
with printcap-based application programs.
CUPS uses the IPP protocol. LPRng uses the LPD protocol.
CUPS normally needs more computing performance for more power-
ful filtering and the web interface.
Note
LPD Functionality with CUPS
CUPS supports fundamental LPD functionality, both on the re-
cipient side by means of the cups-lpd and on the sender side by
means of the lpd back-end. However, CUPS does not support
full LPRng functionality. It is also possible to use filter scripts of
LPD-based print systems as System V style interface scripts.
Note
297SUSE LINUX Enterprise Server